Kernel 3.6.2-1 Won't Boot - FC16

[SteveT]

Good morning all.
Yesterday, 3.6.2-1 was installed on my laptop (previously on 3.4.11) that is running FC16. The kernel was the PAE version:
Oct 23 07:59:03 retsol610 yum[2861]: Installed: kernel-PAE-devel-3.6.2-1.fc16.i686

On powering up the laptop this morning, GRUB showed the 3.6 kernel ok, but once selected, the screen just went blank (completely black) and the disc light showed no activity. I waited for a few minutes, but no joy.

I restarted the laptop and booted back into the 3.4 kernel ok. Thinking that the problem may have been in the PAE extension, and given that I only have 2GB mem on the laptop, I manually removed the PAE 3.6.2 kernel and installed the base kernel 3.6.2 via yumex. Rebooting came up with the same issue - ie 3.6.2 appears in the GRUB list, but then stalls on selection.

No messages appear on screen at al *, and /var/log/messages doesn't even show the attempt at booting into 3.6.2 at all.

Any ideas as to how I can find out why 3.6.2 is failing?

*EDITED: Two messages appear on screen on select:
Loading Fedora.....
Loading Initial ramdisk

[marriedto51]

I'd try editing the grub kernel line to remove "rhgb" and "quiet" -- you'll then get a chance to see any messages generated by the kernel.

[SteveT]

First, apologies, the boot does come up with the 'standard' - Loading fedora and loading ramdisk messages - but then nothing at all. No Fedora splash, no errors.

I went into GRUB edit on the 3.6 kernel, and don't see any rhgb or quiet lines.

The oddity that I can see though, is although I have now removed the PAE kernel using yumex, and the boot script shows:
initrd /initramfs-3.6.2-1.fc16.i686.img

the initramfs's that I have under /boot/initrd are:
/boot/initramfs-3.4.11-1.fc16.i686.PAE.img
/boot/initramfs-3.4.9-2.fc16.i686.PAE.img
/boot/initramfs-3.6.2-1.fc16.i686.PAE.img

So, I can semi see now why the 'standard' non PAE kernel isn't booting - given that it appears to be trying to load the correct (presumably) ram image on boot, but that ram image doesn't exist.

Unless I hear from anyone otherwise, I'll go back and remove the standard 3.6 kernel and put back the PAE version to see if that boot script then matches the ram img file.



EDITED: I'm losing the plot today. The initramfs discrepancy looks to be caused by me using 'locate' and the db not being updated. I have removed the stnadrd kernel and gone back to the PAE

---------- Post added at 10:54 AM ---------- Previous post was at 10:16 AM ----------

Marriedto51,
Right, hopefully I've got this right this time.

I have removed the std kernel and reinstated the 3.6 PAE.

I see now the quiet and rhgb commands - I was looking for them as 'main' commands, not params to another command. Anyway, I removed them from the 3.6 PAE and booted, the 'Loading Fedora and ramdisk messages appeared followed by a whole list of scolling text - but the screen then went blank again and the boot stopped. So I'm still none the wiser as to what the last messages were before the screen went blank. The messages log:

Oct 24 10:18:40 retsol610 yum[2649]: Erased: kernel-devel-3.6.2-1.fc16.i686
Oct 24 10:18:45 retsol610 yum[2649]: Erased: kernel-3.6.2-1.fc16.i686
Oct 24 10:20:15 retsol610 dbus-daemon[868]: dbus[868]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Oct 24 10:20:15 retsol610 dbus[868]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
Oct 24 10:20:15 retsol610 dbus-daemon[868]: Launching FprintObject
Oct 24 10:20:15 retsol610 dbus-daemon[868]: dbus[868]: [system] Successfully activated service 'net.reactivated.Fprint'
Oct 24 10:20:15 retsol610 dbus[868]: [system] Successfully activated service 'net.reactivated.Fprint'
Oct 24 10:20:15 retsol610 dbus-daemon[868]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Oct 24 10:20:15 retsol610 dbus-daemon[868]: ** Message: entering main loop
Oct 24 10:20:45 retsol610 dbus-daemon[868]: ** Message: No devices in use, exit
Oct 24 10:22:41 retsol610 clamd[991]: SelfCheck: Database status OK.
Oct 24 10:22:41 retsol610 clamd[991]: SelfCheck: Database status OK.
Oct 24 10:25:19 retsol610 yum[2687]: Installed: kernel-PAE-devel-3.6.2-1.fc16.i686
Oct 24 10:25:32 retsol610 yum[2687]: Installed: kernel-PAE-3.6.2-1.fc16.i686
Oct 24 10:31:33 retsol610 systemd-logind[857]: Removed session 2.
Oct 24 10:31:33 retsol610 kernel: Kernel logging (proc) stopped.
Oct 24 10:31:33 retsol610 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="866" x-info="http://www.rsyslog.com"] exiting on signal 15.
Oct 24 10:42:13 retsol610 kernel: imklog 5.8.10, log source = /proc/kmsg started.
Oct 24 10:42:13 retsol610 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="880" x-info="http://www.rsyslog.com"] start
Oct 24 10:42:13 retsol610 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Oct 24 10:42:13 retsol610 kernel: [ 0.000000] Initializing cgroup subsys cpu
Oct 24 10:42:13 retsol610 kernel: [ 0.000000] Linux version 3.4.11-1.fc16.i686.PAE (mockbuild@buildvm-29.phx2.fedoraproject.org) (gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC) ) #1 SMP Sun Sep 16 14:18:46 UTC 2012


Shows me removing the old kernel, installing the PAE - but again doesn't show the attempt at booting the 3.6 PAE - just me then booting back under 3.4 to compose this message.

Is there a way I can 'hold' the screen to see what the boot messages are?

[glennzo]

No need to edit any grub files. It isn't recommended to edit the majority of them anyhow. When booting, if you want to see text instead of the graphical screen just press the escape key.

The log files will provide a lot of information regarding boot errors, etc.

When the new kernel stops booting try to switch to a VT with CTRL/ALT/F2. See if you get a log in prompt.

[SteveT]

Originally Posted by glennzo

No need to edit any grub files. It isn't recommended to edit the majority of them anyhow. When booting, if you want to see text instead of the graphical screen just press the escape key.

The log files will provide a lot of information regarding boot errors, etc.

When the new kernel stops booting try to switch to a VT with CTRL/ALT/F2. See if you get a log in prompt.

Glennzo,
If I press ESC, I don't see any text at all. The boot process appears to stop before it hist the Fedora splash screen. Alt-Ctrl-Fn doesn't give me anything at all. I don't see any alternate log in screens.

After the 'Loading Fedora and ramdisk messages, the screen simply goes blank and the disc light stops. ESC doesn't show anything and the alternate login screens aren't available. There is nothing in the logs (ie /var/log/messages) - the log shows:
Oct 24 10:58:33 retsol610 dbus-daemon[878]: ** Message: No devices in use, exit
Oct 24 11:02:56 retsol610 clamd[1005]: SelfCheck: Database status OK.
Oct 24 11:02:56 retsol610 clamd[1005]: SelfCheck: Database status OK.
Oct 24 11:12:56 retsol610 clamd[1005]: SelfCheck: Database status OK.
Oct 24 11:12:56 retsol610 clamd[1005]: SelfCheck: Database status OK.
Oct 24 11:19:41 retsol610 systemd-logind[866]: Removed session 2.
Oct 24 11:19:41 retsol610 kernel: Kernel logging (proc) stopped.
Oct 24 11:19:41 retsol610 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="880" x-info="http://www.rsyslog.com"] exiting on signal 15.
Oct 24 11:24:42 retsol610 kernel: imklog 5.8.10, log source = /proc/kmsg started.
Oct 24 11:24:42 retsol610 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="872" x-info="http://www.rsyslog.com"] start
Oct 24 11:24:42 retsol610 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Oct 24 11:24:42 retsol610 kernel: [ 0.000000] Initializing cgroup subsys cpu
Oct 24 11:24:42 retsol610 kernel: [ 0.000000] Linux version 3.4.11-1.fc16.i686.PAE (mockbuild@buildvm-29.phx2.fedoraproject.org) (gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC) ) #1 SMP Sun Sep 16 14:18:46 UTC 2012


....that shows the boot under 3.4.11, but not the attempted boots under 3.6 (I tried twice at around the 11:24 mark, before going back to 3.4 to post this message).

Any other ideas as to how I can see what is happening to try to narrow down the problem? Given the nature of the issue, it would be simple to assume that 3.6 doesn't like my monitor or my disc hardware - lspci shows:

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
Subsystem: Dell Dell Latidude C610 [1028:0182]
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0182]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at dff00000 (32-bit, non-prefetchable) [size=512K]
I/O ports at ec38 [size=8]
Memory at c0000000 (32-bit, prefetchable) [size=256M]
Memory at dfec0000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 03)
Subsystem: Dell Device [1028:0182]
Flags: bus master, fast devsel, latency 0
Memory at dff80000 (32-bit, non-prefetchable) [size=512K]
Capabilities: <access denied>

.....
00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 03) (prog-if 80 [Master])
Subsystem: Dell Device [1028:0182]
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 17
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at bfa0 [size=16]
Capabilities: <access denied>
Kernel driver in use: ata_piix


...but obviously that is just a guess based on the symptoms.

[glennzo]

Does the older kernel work OK? O know you said you can boot into it but have you noticed anything odd?

Had you done any updates prior to updating the new kernel?

I doubt if the issue has anything to do with the monitor or the Intel graphics.

[SteveT]

Originally Posted by glennzo

Does the older kernel work OK? O know you said you can boot into it but have you noticed anything odd?

Had you done any updates prior to updating the new kernel?

I doubt if the issue has anything to do with the monitor or the Intel graphics.

The old kernel (and all other kernels under fc16) have worked fine.

As it happens though, I'm posting this now under 3.6.2-1 PAE. I haven't fixed the problem, but I do now have a workaround. The issue does appear to be the monitor. I read this:

http://docs.fedoraproject.org/en-US/...-Plymouth.html
The kernel modesetting drivers are still in development and buggy. If you end up with nothing but a black screen during boot up, or a screen with nothing but random noise on it, then adding nomodeset to the kernel boot prompt in grub disables modesetting.

So I tried a boot with 'nomodeset' added via the grub edit. That got past the Plymouth loader (it showed a block graphic bar at the bottom of the screen showing the boot process - with Fedora 16 legend).

The snag then is, after booting it takes me into fall back mode under Gnome-3.

So does anyone know where I can go to see or get help with getting my monitor to work again (correctly) with 3.6.2 'modesetting'?

[SteveT]

https://bugzilla.redhat.com/show_bug.cgi?id=845745

It looks like the problem is linked to the kernels from 3.5 onwards. I've not used bugzilla before, but I'll try to add my issue with FC16 and 3.6.2-1.