Fedora 29 x86_64 on a Gigabyte Brix. dnf update berfore Xmas, worked fine. Booted it today and it won't boot to the GUI. Shows Gigabyte on the screen. However, I can ssh into it. (Thank goodness for ssh !)
$ uname -a Linux labBrix 4.19.10-300.fc29.x86_64 #1 SMP Mon Dec 17 15:34:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
dmesg stops with: 15.682354] snd_hda_intel 0000:00:03.0: couldn't bind with audio component [ 15.682378] snd_hda_intel 0000:00:03.0: HSW/BDW HD-audio HDMI/DP requires binding with gfx driver
$ lspci 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) 00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) 00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3) 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03) 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03) 02:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
# dnf list kernel Installed Packages kernel.x86_64 4.19.10-200.fc28 @updates kernel.x86_64 4.19.10-300.fc29 @updates kernel.x86_64 4.19.13-300.fc29 @updates
The first two kernel packages are highlighted. What is the significance of that ?
The last package, 4.19.13-300 isn't highlighted. It also doesn't show in the grub menu when the computer boots. Why ?
How do I get it to boot again ?
Thanks
I found this in dmesg:
Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.10-300.fc29.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap nomodeset rhgb quiet LANG=en_US.UTF-8 [ 0.207360] You have booted with nomodeset. This means your GPU drivers are DISABLED [ 0.207361] Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly [ 0.207361] Unless you actually understand what nomodeset does, you should reboot without enabling it
So I booted to the grub menu and then pressed e to edit. I removed nomodeset from the kernel parameters. And it booted to the kdm login.
How do I make this permanent ?
I am going to mark this as solved as removing nomodeset from the kernel parameters causes it to boot properly.
However, how did nomodeset get into the kernel parameters in the first place ?
On Mon, Jan 14, 2019 at 9:37 PM linux guy linuxguy123@gmail.com wrote:
I found this in dmesg:
Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.10-300.fc29.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap nomodeset rhgb quiet LANG=en_US.UTF-8 [ 0.207360] You have booted with nomodeset. This means your GPU drivers are DISABLED [ 0.207361] Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly [ 0.207361] Unless you actually understand what nomodeset does, you should reboot without enabling it
So I booted to the grub menu and then pressed e to edit. I removed nomodeset from the kernel parameters. And it booted to the kdm login.
How do I make this permanent ?
On Tue, 15 Jan 2019 06:39:02 -0700 linux guy linuxguy123@gmail.com wrote:
I am going to mark this as solved as removing nomodeset from the kernel parameters causes it to boot properly.
However, how did nomodeset get into the kernel parameters in the first place ?
A possible answer below.
On Mon, Jan 14, 2019 at 9:37 PM linux guy linuxguy123@gmail.com wrote:
So I booted to the grub menu and then pressed e to edit. I removed nomodeset from the kernel parameters. And it booted to the kdm login.
How do I make this permanent ?
The answer to both questions might be in /etc/default/grub. That is the configuration used for the kernel parameters when the program grub2-mkconfig is run. Is nomodeset in there? If it is remove it, go to /boot/grub2 (assuming you are running legacy boot), and run grub2-mkconfig -o grub.cfg That will create a new grub.cfg file. If your 4.19.13 kernel is correctly installed, it will be included in this new grub.cfg as the first entry. When dnf updates kernels, it uses grubby to update the grub.cfg, and just copies the parameters from the last kernel. So, updates should work fine once you have the grub.cfg in the proper state.
Were there any issues while doing the last update, the update that installed the 4.19.13 kernel? Power burps, error messages, etc. If so, that might be where the problem comes from, since it appears it wasn't properly installed (it isn't in the grub.cfg file menu).
If you don't want to run the grub2-mkconfig, you could try doing a re-install of that failed kernel. Just updating to whatever the latest is in the repositories *might* fix things, but might not either.
-
linux guy -
stan