[arch-general] kernel linux-4.8.6-1-x86_64 not able to load modules
Hey list, After, as suggested in arch-annoucne, I force-upgrated ttf-dejavu I made a full system upgrade with pacman -Syu. This installed the latest linux kernel. (the one in the subject line) The initram was completed successfully and I procceded to reboot. Then Xserver would complain about my intel module (i915) After a while I figured that nothin was loaded. I had no internet connection (ip link would only show loopback), when I plugged a USB drive the kernel woudln't detect it, and so on... I downgraded to linux-4.8.4 using arch live with arch-chroot. Everything works but when I upgrade to the latest kernel the same thing happens. Since I am prety new to the linux power user world, I have no idea what to do next. Should I file a bug? Ad if yes how do I do that? Also about the kernel upgrade, should I just skip 4.8.6 and get the next one? Since I didn't see anything in the list about linux-4.8.6 I guess it must have something to do with my setup. Any suggestions will be really helpful!
On Sat, 5 Nov 2016 14:50:30 +0200, Anast Gramm via arch-general wrote:
Should I file a bug? Ad if yes how do I do that?
https://wiki.archlinux.org/index.php/Reporting_bug_guidelines
On Sat, 5 Nov 2016 14:50:30 +0200 Anast Gramm via arch-general <arch-general@archlinux.org> wrote:
Hey list,
After, as suggested in arch-annoucne, I force-upgrated ttf-dejavu I made a full system upgrade with pacman -Syu.
This installed the latest linux kernel. (the one in the subject line)
The initram was completed successfully and I procceded to reboot. Then Xserver would complain about my intel module (i915)
After a while I figured that nothin was loaded. I had no internet connection (ip link would only show loopback), when I plugged a USB drive the kernel woudln't detect it, and so on...
This usually happens because the bootloader is finding an old kernel. Either /boot wasn't mounted during the upgrade or the bootloader is looking at the wrong place.
On Sat, Nov 05, 2016 at 08:56:13AM -0500, Doug Newgard wrote:
On Sat, 5 Nov 2016 14:50:30 +0200 Anast Gramm via arch-general <arch-general@archlinux.org> wrote:
Hey list,
After, as suggested in arch-annoucne, I force-upgrated ttf-dejavu I made a full system upgrade with pacman -Syu.
This installed the latest linux kernel. (the one in the subject line)
The initram was completed successfully and I procceded to reboot. Then Xserver would complain about my intel module (i915)
After a while I figured that nothin was loaded. I had no internet connection (ip link would only show loopback), when I plugged a USB drive the kernel woudln't detect it, and so on...
This usually happens because the bootloader is finding an old kernel. Either /boot wasn't mounted during the upgrade or the bootloader is looking at the wrong place.
Yes it was not mounted. I'll try mount it and upgrade again! thanks
That's why I installed the update-grub package a while back since grub then gets automatically updated so it uses the latest kernel to be loaded onto the machine. That's an aur package too. On Sat, 5 Nov 2016, Doug Newgard wrote:
Date: Sat, 5 Nov 2016 09:56:13 From: Doug Newgard <scimmia@archlinux.info> Reply-To: General Discussion about Arch Linux <arch-general@archlinux.org> To: arch-general@archlinux.org Subject: Re: [arch-general] kernel linux-4.8.6-1-x86_64 not able to load modules
On Sat, 5 Nov 2016 14:50:30 +0200 Anast Gramm via arch-general <arch-general@archlinux.org> wrote:
Hey list,
After, as suggested in arch-annoucne, I force-upgrated ttf-dejavu I made a full system upgrade with pacman -Syu.
This installed the latest linux kernel. (the one in the subject line)
The initram was completed successfully and I procceded to reboot. Then Xserver would complain about my intel module (i915)
After a while I figured that nothin was loaded. I had no internet connection (ip link would only show loopback), when I plugged a USB drive the kernel woudln't detect it, and so on...
This usually happens because the bootloader is finding an old kernel. Either /boot wasn't mounted during the upgrade or the bootloader is looking at the wrong place.
--
On Sat, 5 Nov 2016 13:21:53 -0400 (EDT), Jude DaShiell wrote:
That's why I installed the update-grub package a while back since grub then gets automatically updated so it uses the latest kernel to be loaded onto the machine.
For the official Arch kernel packages this makes absolutely no sense ... [rocketmouse@archlinux ~]$ ls -hl /boot/vmlinuz-linux -rw-r--r-- 1 root root 4.6M Oct 31 18:52 /boot/vmlinuz-linux ... since an upgrade of linux changes nothing at all, in regards to the grub.cfg entry or any other bootloaders menu entry. The /boot and root partitions are the same, the kernel file name is kept, too. Regards, Ralf
PS: On Sat, 5 Nov 2016 13:21:53 -0400 (EDT), Jude DaShiell wrote:
That's why I installed the update-grub package a while back since grub then gets automatically updated so it uses the latest kernel to be loaded onto the machine. That's an aur package too.
On Sat, 5 Nov 2016, Doug Newgard wrote:
This usually happens because the bootloader is finding an old kernel. Either /boot wasn't mounted during the upgrade or the bootloader is looking at the wrong place.
What Doug is pointing out here is, that the modules located in /lib/modules get upgraded, but the kernel in /boot doesn't, no grub config could fix this.
participants (4)
-
Anast Gramm
-
Doug Newgard
-
Jude DaShiell
-
Ralf Mardorf