Traditionally kernels were numbered starting from 0 but by default the "new style" of grub boot loading considers each subkernel item to be different so if you have 3 entries for 4.40-148 rather than counting for 1. To get the expected behavior let's show this example and how we can boot it We do a grep on menuentry in /boot/grub/grub.cfg to see all of the bootable kernels rather than scrolling through loads of extra entries we don't care about (thou........

I don't consider a lot of these "extra" kernel modules "nice to have" as they often contain drivers for essential items like your soundcard, your NIC and many other devices that may not work. Sometimes you may find that "sound" or "ethernet" worked before a kernel/OS upgrade and now in the new version they don't. Often it will be because you need to install the "extra" kernel modules. One other weird thing is that sometimes........

I'm not sure why I'm getting these but all memory modules are the exact same and all passed memtest successfully although they are ECC. I've heard that ECC RAM can't be tested as well and the kernel seems to indicate they are non-fatl recoverable errors. I wonder if the BIOS has aggressive RAM timing or maybe the controller or motherboard is bad. [ 12.716515] EDAC MC: Ver: 2.1.0 [ 12.717771] EDAC MC0: Giving out device to........

mount -o bind /proc /sda2/proc mount -o bind /dev/ /sda2/dev mount -o bind /sys /sda2/sys chroot /sda2 mint / # mount -o bind /proc /sda2/proc mint / # mount -o bind /dev/ /sda2/dev mint / # mount -o bind /sys /sda2/sys mint / # chroot /sda2 mint / # cd ~ mint ~ # ls Desktop mint ~ # cd / mint / # ls bin Desktop dev-temp home&nb........

This is one in a series of weird things whichIthought was motherboard related (I RMA'd the motherboard), the RAM tests fine with memtest86 and I used badblocks on both RAID 1 members with no errors and smartctl is happy with them. Basically the array crashes the kernel a lot and has issues when writing. [112322.723465] md0: rw=0, want=14958668696, limit=1887460480 [112322.731077] attempt to access beyond end of device [112322.731087] md........

I took an educated guess because it kept happening at the same spot when loading the XP install. I thought it was the hard drive or motherboard. But it turns out my heavily used but loved NEC 3500 DVD-RW drive was the culprit. After disconnecting it and swapping it for another much beloved Pioneer DVD-RW, everything has gone smoothly. I never ran into this or many issues because I've hardly used this drive since moving it to another Desktop years ago. I actua........