You are not logged in.
here was similiar problem on Debian unstable based siduction system & on the same generation t400 machine, also ext4 partitions were used. However I don't understand what the guy did to solve the problem
https://forum.siduction.org/index.php?topic=4257.0
I would install kernel from backports in chroot probably. X200 is not new or even middle-age but this 3.16 kernel is really old. Of course trial with kernel reinstall & initframs update could be done earlier as Haos has written.
Offline
I would install kernel from backports
The OP is of course welcome to try this but a newer kernel is far more likely to have deleterious regressions for older hardware (such as an X200) than the Debian stable kernel (which has worked fine for the OP up until this point), this is why we prefer the stable kernel in BunsenLabs.
I don't understand what the guy did to solve the problem
My German is rusty but it looks like the GRUB bootloader was (mistakenly) installed to a partition (rather than the MBR) and the "solution" was to chainload it from the MBR-based bootloader, which seems fairly ridiculous to me but I may have misread things.
Offline
My German is rusty but it looks like ..
^ Your German is not rusty.
The guy has thought with Grub1 and Grub2 three times around the corner.
Offline
he was messing to much, it's very clar ; )
Offline
It's sad (and makes a thread kind of pointless) if there is no feedback in the end regarding a possible solution.
Just came back to this thread after getting kernels messed up (different issue). It was nothing serious, probably grub update thought that a kernel of an other distro on the boot partition belongs to #BĹ and made it in the grub menu as default. Result: Kernel panic at boot. The latest kernel version was working fine though, just had to go to "Advanced" and choose it there. Otherwise changing boot.cfg fixes the menu too.
Offline