You are not logged in.
I have two potentially related issues that have to do with the kernel they are:
1. I am currently booting with linux-lts 4.4.39-1. updating linux-lts produces a kernel panic. when I try to boot with higher versions of linux-lts I get as far as the login prompt (I don't have a display manager) and then there is a huge amount of text dumped to the console, the keyboard becomes unresponsive, and the light on the caps lock key begins flashing. I don't know how to access the text that rolls off the screen during the panic. I can post a picture of the bottom lines that are visible if it would help. When I asked for help on reddit it was suggested that I post the contents of dmesg. I cleared the dmesg buffer before updating the kernel and then collected the the panicked dmesg output from a chroot environment. linked here: http://pastebin.com/unikbsWg
my question is: how do I figure out what is causing my kernel panic and how do I fix it?
2. I am currently booting from the lts kernel because the linux kernel refuses to boot. when I install linux-4.8.13-1 the boot process hangs at: "loading initial ramdisk...". this issue has persisted since I set up the system (why I am currently using linux-lts). I have tried using the grub command line to load the linux-4.8.13-1 kernel manually, but the process hung indefinitely at the 'boot' command.
my question is: how do I enable booting with the linux kernel?
some other points:
- I have updated grub and I have run mkinitcpio -P, I am fairly sure that these actions will not fix my problem.
- the problem is not grub (at least for issue 1). grub seems to load stuff properly and it will load win10 just fine
- I'm pretty new to Arch so if you could take your time to explain yourself thoroughly it would be appreciated
***edit:
The kernel panic was caused by my external wifi adapter. For now I've switched to my laptop's internal (and buggier) wifi card. Not sure why the external adapter causes a panic, I'lll try and figure it out and post back here. for anyone who finds this in the future: I was able to determine the cause of the kernel panic by checking the journal (journalctl). the last entry was a mention of udev so I figured it was probably the wifi adapter. also: the boot process was completely successful the panic was caused when netcl attempted to set-up my wifi connection. after successfully starting the system and then plugging in the adapter and running netctl-auto to start the interface I was able to trigger the panic.
still no word on why linux 4.8 (now 4.9) does not boot.
Last edited by ZkSN (2017-01-28 21:42:08)
Offline
What is your setup configuration in terms of disks? Are you using LVM, encryption, etc.? It looks like there's a small-ish 8 GB removable drive (sda) and a large 1 TB drive? The last three lines are a little odd to be happening before a kernel panic:
[ 128.233578] EXT4-fs (sdb5): recovery complete
[ 128.259094] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
[ 133.341691] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.Offline
@twelveeighty: The 8GB drive is probably the live boot environment I used to roll-back to kernel. the 1TB drive is the computer's main drive. I'm a little confused as to how there would be output in the dmesg log referring to the 8GB drive as I only plugged it in after the kernel panic and a hard poweroff. Does chrooting into a system produce output in dmesg?
Last edited by ZkSN (2017-01-24 02:42:39)
Offline
dmesg output is stored in memory so the dmesg is probably from the reboot after the panic and does not contain the panic itself. It may be stored in the journal.
Offline