buut paramerers for seeing the verbose boot process
jd1008 at gmail.com
Fri Apr 8 22:12:16 UTC 2011
On 04/08/2011 02:23 PM, suvayu ali wrote:
> On Fri, Apr 8, 2011 at 1:23 PM, JD<jd1008 at gmail.com> wrote:
>> What happens is at boot, there is a fast scroll
>> of text and suddenly, the screen appears as if it got powered off,
>> but it also behaves that way when switching from bios text mode
>> to graphics mode. It stays blank (black) for about 2.5 or more minutes
>> and then the Gnome login menu pops up.
>> I never get to see the output of the boot process,
>> so I can see what passed and what failed.
> Kevin's prescription should have worked. I don't know what is wrong
> but you can always look at the boot messages after the fact with
> $ less -r /var/log/boot.log
Yeah... I know that.
I would much rather see them as it is booting.
Here is the entry in /boot/grub/grub.conf
title Fedora (188.8.131.52.fc14.i686)
kernel /boot/vmlinuz-184.108.40.206.fc14.i686 ro root=/dev/sda2
I have to admit that the kernel I am using is the
mainline rleased kernel, because the ath9k driver
seems to better support my AR5008 based wifi card
(has AR5614/AR2133 chips). I tried the regular Fedora 14
released kernel from updates (220.127.116.11-83.fc14.i686),
but using it, I was unable to pair with the AP, whereas
18.104.22.168 works just fine.
So, I wonder if my problem might be caused by
one of the boot stages???
More information about the users