Re: New kernel doesn't complete booting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2009/1/10 David <dgboles@xxxxxxxxxxx>:
> Antonio M wrote:
>> 2009/1/10 David <dgboles@xxxxxxxxxxx>:
>>> Antonio M wrote:
>>>> kernel-2.6.29-0.24.rc0.git13.fc11.i686 doesn' complete booting on my
>>>> i386 system and stops just after writing the very first lines on my
>>>> screen.
>>>> Anyone else with same experience???
>>>
>>> Unless they changed this when I was not looking the last line that
>>> displays is the last 'event' in the loading order that succeeded. The
>>> 'event' that failed does *not* display.
>>>
>>> Reboot with a different kernel and watch the screen the 'event' that
>>> failed the first time will be shown right after the 'event' line were it
>>> stopped before now. And then you know what to 'fix'.  ;-)
>>>
>>> --
>>>
>>>
>>>  David
>>>
>>> --
>>> fedora-test-list mailing list
>>> fedora-test-list@xxxxxxxxxx
>>> To unsubscribe:
>>> https://www.redhat.com/mailman/listinfo/fedora-test-list
>>>
>>
>> the only lines that I get are:
>>
>> Booting....
>> root....
>> [Linux-bzImage, setup=0x3000, size 0x2b18f0]
>> initrd /initrd.......
>> [Linux-initrd @ 0x37cc5000, 0x329315 bytes]
>>
>> and system freezes
>>
>> Precedent kernel boot fine, I am writing from that machine.
>> Tested also with 25 kernel from koij...
>> this is my grub.conf but I do not see any problem..
>>
>>
>> # grub.conf generated by anaconda
>> #
>> # Note that you do not have to rerun grub after making changes to this file
>> # NOTICE:  You have a /boot partition.  This means that
>> #          all kernel and initrd paths are relative to /boot/, eg.
>> #          root (hd0,0)
>> #          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
>> #          initrd /initrd-version.img
>> #boot=/dev/sda
>> default=0
>> timeout=5
>> splashimage=(hd0,0)/grub/splash.xpm.gz
>> hiddenmenu
>> title Fedora (2.6.29-0.25.rc0.git14.fc11.i686)
>>       root (hd0,0)
>>       kernel /vmlinuz-2.6.29-0.25.rc0.git14.fc11.i686 ro
>> root=/dev/VolGroup00/LogVol00 rhgb quiet
>>       initrd /initrd-2.6.29-0.25.rc0.git14.fc11.i686.img
>> title Fedora (2.6.29-0.19.rc0.git9.fc11.i686)
>>       root (hd0,0)
>>       kernel /vmlinuz-2.6.29-0.19.rc0.git9.fc11.i686 ro
>> root=/dev/VolGroup00/LogVol00 rhgb quiet
>>       initrd /initrd-2.6.29-0.19.rc0.git9.fc11.i686.img
>> title Fedora (2.6.28-0.140.rc9.git1.fc11.i686)
>>       root (hd0,0)
>>       kernel /vmlinuz-2.6.28-0.140.rc9.git1.fc11.i686 ro
>> root=/dev/VolGroup00/LogVol00 rhgb quiet
>>       initrd /initrd-2.6.28-0.140.rc9.git1.fc11.i686.img
>> title Fedora (2.6.28-0.138.rc9.fc11.i686)
>>       root (hd0,0)
>>       kernel /vmlinuz-2.6.28-0.138.rc9.fc11.i686 ro
>> root=/dev/VolGroup00/LogVol00 rhgb quiet
>>       initrd /initrd-2.6.28-0.138.rc9.fc11.i686.img
>
>
> Does boot.log offer any hints?
>
> --
>
>
>  David
>
> --
> fedora-test-list mailing list
> fedora-test-list@xxxxxxxxxx
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
>

unfortunately no...

-- 
Antonio Montagnani
Skype : antoniomontag

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux