F5F Stay Refreshed Software Operating Systems System freezes during startup on Ubuntu Desktop version 19.04.

System freezes during startup on Ubuntu Desktop version 19.04.

System freezes during startup on Ubuntu Desktop version 19.04.

Pages (3): Previous 1 2 3 Next
S
siph7
Member
79
10-10-2018, 06:04 PM
#11
The detailed output moved very quickly, but everything appeared green. It seems there might be a problem with the built-in driver affecting everything. If this is true, what steps should I take to resolve it?
S
siph7
10-10-2018, 06:04 PM #11

The detailed output moved very quickly, but everything appeared green. It seems there might be a problem with the built-in driver affecting everything. If this is true, what steps should I take to resolve it?

S
Shapse
Junior Member
21
10-11-2018, 01:39 AM
#12
It might be a new version or something different. Make sure to refresh the system during the nomodeset session; this ensures the basic driver is used and fixes problems with the Plymouth boot logo. Once everything is updated, restart your machine. If the problem continues, try rebooting with nomodeset again and install the graphics drivers from the PPA. The relevant PPA link is: https://launchpad.net/~graphics-drivers/...ubuntu/ppa
S
Shapse
10-11-2018, 01:39 AM #12

It might be a new version or something different. Make sure to refresh the system during the nomodeset session; this ensures the basic driver is used and fixes problems with the Plymouth boot logo. Once everything is updated, restart your machine. If the problem continues, try rebooting with nomodeset again and install the graphics drivers from the PPA. The relevant PPA link is: https://launchpad.net/~graphics-drivers/...ubuntu/ppa

N
Nelina
Member
184
10-12-2018, 01:01 AM
#13
I followed all instructions...the issue persists even with the nomodeset enabled.
N
Nelina
10-12-2018, 01:01 AM #13

I followed all instructions...the issue persists even with the nomodeset enabled.

F
Fenitis
Member
196
10-12-2018, 09:57 AM
#14
Can I access your /var/log/kern.log file? Earlier it functioned properly with the nomodeset command.
F
Fenitis
10-12-2018, 09:57 AM #14

Can I access your /var/log/kern.log file? Earlier it functioned properly with the nomodeset command.

M
mrninja
Junior Member
15
10-13-2018, 06:50 PM
#15
It functioned with nomodeset prior to installing the NVIDIA drivers. I’ll need to boot from the USB stick to access the file you’re looking for.
M
mrninja
10-13-2018, 06:50 PM #15

It functioned with nomodeset prior to installing the NVIDIA drivers. I’ll need to boot from the USB stick to access the file you’re looking for.

T
Texas1047
Posting Freak
889
10-20-2018, 01:26 PM
#16
Log file recorded.
T
Texas1047
10-20-2018, 01:26 PM #16

Log file recorded.

I
iTz_JustDizzy
Junior Member
46
10-22-2018, 06:40 AM
#17
Remove vt.handoff=1 first. If still not successful, clear the quiet splash and vt.handoff again, then remove all of them once more before adding nomodeset.
I
iTz_JustDizzy
10-22-2018, 06:40 AM #17

Remove vt.handoff=1 first. If still not successful, clear the quiet splash and vt.handoff again, then remove all of them once more before adding nomodeset.

S
Supermirza12
Junior Member
5
10-23-2018, 02:08 AM
#18
It seems there are some PCI-related warnings. Have you updated the latest BIOS? Have you attempted to switch the GPU to a different PCI slot? Resetting the BIOS? Adjusting PCI settings in the BIOS? https://superuser.com/questions/275050/l...c-to-linux They mention it could be a BIOS setting that doesn’t work well with Linux, noting the exact issue. They installed Linux by following these steps: set default BIOS, install a fresh Linux distribution (we tried Fedora 15 and Ubuntu 10.04, 64 Bit), changed the BIOS configuration (activated RAID). For reference, I encountered the same problem on a Toshiba netbook (model not remembered). Booting from a LiveCD worked, but when I booted from the hard drive it would freeze for over ten minutes before continuing. The fix involved changing the SATA controller to "compatibility". I might be forgetting some details. I’ll update this post tonight with more info. But try what I said earlier first.
S
Supermirza12
10-23-2018, 02:08 AM #18

It seems there are some PCI-related warnings. Have you updated the latest BIOS? Have you attempted to switch the GPU to a different PCI slot? Resetting the BIOS? Adjusting PCI settings in the BIOS? https://superuser.com/questions/275050/l...c-to-linux They mention it could be a BIOS setting that doesn’t work well with Linux, noting the exact issue. They installed Linux by following these steps: set default BIOS, install a fresh Linux distribution (we tried Fedora 15 and Ubuntu 10.04, 64 Bit), changed the BIOS configuration (activated RAID). For reference, I encountered the same problem on a Toshiba netbook (model not remembered). Booting from a LiveCD worked, but when I booted from the hard drive it would freeze for over ten minutes before continuing. The fix involved changing the SATA controller to "compatibility". I might be forgetting some details. I’ll update this post tonight with more info. But try what I said earlier first.

G
g_ft
Member
170
10-24-2018, 02:46 AM
#19
The setup on the Sata controller is already compatible. I eliminated the quiet splash and vt.handoff, then added the nomodeset. It loaded successfully until it reached the message: "Started Update UTMP about System Runlevel Changes," after which it froze again. When I press the power button to shut down the machine, modules appear to unload and drives seem to become unmounted.
G
g_ft
10-24-2018, 02:46 AM #19

The setup on the Sata controller is already compatible. I eliminated the quiet splash and vt.handoff, then added the nomodeset. It loaded successfully until it reached the message: "Started Update UTMP about System Runlevel Changes," after which it froze again. When I press the power button to shut down the machine, modules appear to unload and drives seem to become unmounted.

C
coyote888
Posting Freak
838
10-24-2018, 08:44 AM
#20
It's typical, the system is powering down. Please attempt a BIOS reset first.
C
coyote888
10-24-2018, 08:44 AM #20

It's typical, the system is powering down. Please attempt a BIOS reset first.

Pages (3): Previous 1 2 3 Next