Re: [Mactel-linux-users] updating kernel screws up grub?

[Justin P. M. <jus...@gm...>]

On 04/21/2010 11:35 AM, Geoffrey wrote:
> Justin P. Mattock wrote:
>> On 04/21/2010 09:57 AM, Geoffrey wrote:
>>> Justin P. Mattock wrote:
>>>> On 04/21/2010 09:30 AM, Geoffrey wrote:
>>>>> Justin P. Mattock wrote:
>>>>>> On 04/21/2010 09:11 AM, Geoffrey wrote:
>>>>>>> Justin P. Mattock wrote:
>>>>>>>> On 04/21/2010 06:55 AM, Geoffrey wrote:
>>>>>>>>> So I rebuilt my kernel, insuring that I had ext3 support and I
>>>>>>>>> still get
>>>>>>>>> a panic, although it is a different message:
>>>>>>>>>
>>>>>>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>>>>>>>>> unknown-block(0,0)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> check your /etc/fstab and make sure
>>>>>>>> that it's /dev/sda* instead of /dev/hda*
>>>>>>>> (if your using the older ati-piix it's should
>>>>>>>> be /dev/hda* but using the new ati-piix it's
>>>>>>>> /dev/sda*)but could be wrong).
>>>>>>>
>>>>>>> Actually it's using the LABEL nomenclature, do you think this
>>>>>>> could be
>>>>>>> my problem?
>>>>>>>
>>>>>>> LABEL=/ / ext3 defaults 1 1
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> could be..
>>>>>> here's what I have:
>>>>>> cat /etc/fstab
>>>>>>
>>>>>> # file system mount-point type options dump fsck
>>>>>> # order
>>>>>>
>>>>>> /dev/sda3 / ext4 defaults,errors=remount-ro,user_xattr 1 1
>>>>>> /dev/sda4 swap swap pri=1 0 0
>>>>>> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
>>>>>> proc /proc proc defaults 0 0
>>>>>> sysfs /sys sysfs defaults 0 0
>>>>>> devpts /dev/pts devpts gid=4,mode=620 0 0
>>>>>> tmpfs /dev/shm tmpfs defaults 0 0
>>>>>> #none /selinux selinuxfs defaults 0 0
>>>>>> # End /etc/fstab
>>>>>>
>>>>>> does changing LABEL=/ to your device do anything?
>>>>>
>>>>> Just tried that, no difference.
>>>>>
>>>>>>
>>>>>> Justin P. Mattock
>>>>>>
>>>>>
>>>>>
>>>>
>>>> hm.. I'm wondering if your hitting something
>>>> with grub and the kernel i.g. I remember hitting something
>>>> similar because I had no bzimage just raw make install
>>>> vmlinuz(ended up having to upgrade to grub2 so that grub(*)
>>>> was able to read the extra bits and so forth or something
>>>> in that area).
>>>>
>>>> Also hit another issue similar as well with
>>>> PCI_MMCONFIG [=y]
>>>> (but this could already be fixed).
>>>
>>> I changed my grub entry for root from:
>>>
>>> root=LABEL=/
>>>
>>> to
>>>
>>> root=/dev/sda8
>>>
>>> Now I get a spontaneous reboot. I tried to snap a photo of it before it
>>> reboot, but it's blurred. I'll try again. Weird thing is that it says
>>> something about wacom driver and then a reference to reiserfs or some
>>> such. I don't know what the wacom driver would have to do with reiserfs,
>>> but I'm not using reiserfs anyway.
>>>
>>>
>>
>> so changing your grub at-least takes care of the unable to find
>> VFS thing?!
>> and now the system boots up, and then instantly
>> reboot's? I have seen reports of things like that,
>> but have never hit something like that(if you can try early debugging
>> with a remote machine to grab dmesg)
>
> Not exactly sure how to go about that. I will try to video the boot
> process so I can provide better info.
>

I usually use the ohci1394_dma=early boot option via firwire.
that is if the machine crashes early I can see whats going on.
(hopefully)
In your case you probably already have dmesg since the machine
starts up(if this is the case), and then after done with everything
reboots(saving the log file (but could be wrong)).

also looking through bugzilla I think your hitting this:
https://bugzilla.kernel.org/show_bug.cgi?id=14952

(maybe revert this commit and see if you boot up)
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=patch;h=1373411ae4cd0caf2e1a35fb801dd9a00b64dea2

Justin P. Mattock