F5F Stay Refreshed Hardware Desktop Check if the BIOS settings are correct and ensure the hardware is properly connected.

Check if the BIOS settings are correct and ensure the hardware is properly connected.

Check if the BIOS settings are correct and ensure the hardware is properly connected.

J
jenihu
Junior Member
16
09-01-2016, 12:38 AM
#1
Hello! I'm not sure if this is the right spot for sharing, but I haven't used forums like this before, so please let me know if I should look elsewhere. Also, I'm just starting out with troubleshooting and tech in general, and I'm sorry if I missed something important—please be patient! Device: Lenovo ThinkPad T450s
CPU: Intel Core i7-5600U
BIOS: JBET73WW (version 1.37)
OS: Kubuntu 20.04.1

Problem: I've been using Linux (Kubuntu) for about a year without big problems, except for a few minor mistakes that are easy to fix. One day I tried to turn on my laptop and got past the Lenovo splash screen, but then ran into errors (see attached photo). I hadn't updated anything in over a week and didn't change any settings or notice any issues before. I tried these solutions:
- Reinstall OS: Made a new bootable USB with a newer Ubuntu version and tried booting, but got the same screen as the photo.
- BIOS: According to Lenovo, the BIOS is up-to-date, but thought a fresh start might help.
*My lack of experience showed through—I couldn't clearly follow Lenovo's instructions for transferring the BIOS ISO to a USB drive. I followed the same steps as with my Ubuntu ISO, but Rufus didn't recognize Lenovo's format, and tools like Unetbootin didn't work.*

Thoughts?
J
jenihu
09-01-2016, 12:38 AM #1

Hello! I'm not sure if this is the right spot for sharing, but I haven't used forums like this before, so please let me know if I should look elsewhere. Also, I'm just starting out with troubleshooting and tech in general, and I'm sorry if I missed something important—please be patient! Device: Lenovo ThinkPad T450s
CPU: Intel Core i7-5600U
BIOS: JBET73WW (version 1.37)
OS: Kubuntu 20.04.1

Problem: I've been using Linux (Kubuntu) for about a year without big problems, except for a few minor mistakes that are easy to fix. One day I tried to turn on my laptop and got past the Lenovo splash screen, but then ran into errors (see attached photo). I hadn't updated anything in over a week and didn't change any settings or notice any issues before. I tried these solutions:
- Reinstall OS: Made a new bootable USB with a newer Ubuntu version and tried booting, but got the same screen as the photo.
- BIOS: According to Lenovo, the BIOS is up-to-date, but thought a fresh start might help.
*My lack of experience showed through—I couldn't clearly follow Lenovo's instructions for transferring the BIOS ISO to a USB drive. I followed the same steps as with my Ubuntu ISO, but Rufus didn't recognize Lenovo's format, and tools like Unetbootin didn't work.*

Thoughts?

M
Muggy215
Member
147
09-08-2016, 03:14 PM
#2
This situation hasn't been encountered by any expert before. It looks like a bios-related problem or an issue with the drive's formatting. It might be worth revisiting the formatting part if you don't need the drive data.
M
Muggy215
09-08-2016, 03:14 PM #2

This situation hasn't been encountered by any expert before. It looks like a bios-related problem or an issue with the drive's formatting. It might be worth revisiting the formatting part if you don't need the drive data.

N
nuke_master11
Junior Member
36
09-08-2016, 09:21 PM
#3
Remove the CMOS battery and reinstall it. It seems like the main problem is with your hard drive not appearing. Does it function properly now?
N
nuke_master11
09-08-2016, 09:21 PM #3

Remove the CMOS battery and reinstall it. It seems like the main problem is with your hard drive not appearing. Does it function properly now?

O
OvelhaComAVC
Member
54
09-08-2016, 10:42 PM
#4
Use MemTest86 to assess drive health, as this could be a workaround under *nix if direct access isn't possible. Consider removing the drive and testing it elsewhere.
O
OvelhaComAVC
09-08-2016, 10:42 PM #4

Use MemTest86 to assess drive health, as this could be a workaround under *nix if direct access isn't possible. Consider removing the drive and testing it elsewhere.