Prev: Re (2): output from udevadm
Next: thinking of installing amd64 Debian: what is its current state?
From: Tom H on 13 Jul 2010 01:30
On Tue, Jul 13, 2010 at 12:37 AM, H.S. <hs.samix(a)gmail.com> wrote:
> On 12/07/10 03:07 PM, H.S. wrote:
>>
>> Curiously though, update-grub is now detecting Fedora 13! It was not
>
> Well, I wrote that too soon.
>
> Here is what update-grub puts in /boot/grub
> /grub.cfg regarding the Fedora 13 installation:
> #######################################################
> menuentry "Fedora release 13 (Goddard) (on /dev/mapper/vg1-lv8)" {
>        insmod part_msdos
>        insmod ext2
>        set root='(hd0,msdos5)'
>        search --no-floppy --fs-uuid --set
> b40b5b7f-6999-4a12-9d3b-62e0fc892a40
>        linux /vmlinuz-2.6.33.6-147.fc13.x86_64 root=/dev/dm-1
> }
> #######################################################
>
> It is missing the initrd line. Without that line the kernel does not
> boot and panics and halts.
>
> I have to put the correct stanza myself in /etc/grub.d/40_custom to get
> the correct grub entry which works:
> #######################################################
> menuentry "Fedora release 13 (on /dev/mapper/vg1-lv8)" {
>        insmod part_msdos
>        insmod ext4
>        set root='(hd0,msdos5)'
>        search --no-floppy --fs-uuid --set
> b40b5b7f-6999-4a12-9d3b-62e0fc892a40
>        linux /vmlinuz-2.6.33.6-147.fc13.x86_64 root=/dev/mapper/vg1-lv8
> ro quiet
>        initrd  /initramfs-2.6.33.6-147.fc13.x86_64.img
>        boot
> }
> #######################################################
>
> So there still appears to be some problem somewhere.

Yes. The Fedora/RHEL initrd names are not recognized by Debian/Ubuntu's grub...


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/AANLkTilIljkgvh8aCuh661HBwVrbof-ZhJqaiRRfTMQM(a)mail.gmail.com
From: Tom H on 13 Jul 2010 02:00
On Tue, Jul 13, 2010 at 1:45 AM, H.S. <hs.samix(a)gmail.com> wrote:
> On 13/07/10 01:28 AM, Tom H wrote:
>> On Tue, Jul 13, 2010 at 12:37 AM, H.S. <hs.samix(a)gmail.com> wrote:
>>>
>>> It is missing the initrd line. Without that line the kernel does not
>>> boot and panics and halts.
>>>
>>> I have to put the correct stanza myself in /etc/grub.d/40_custom to get
>>> the correct grub entry which works:
> <SNIP>
>>>
>>> So there still appears to be some problem somewhere.
>>
>> Yes. The Fedora/RHEL initrd names are not recognized by Debian/Ubuntu's grub...
>
>
> I see. Could you briefly explain why is that?

Quite frankly, I thought that this had been fixed (I read it on either
the Debian or Ubuntu bug reporting system), but I came across this
problem last year and the script was looking for initrds of the form
"initrd.img-..." and therefore ignored "initramfs..." files.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/AANLkTikBOmhjq6HZCY5B-_g4EJlsss4QE8fT8iFsgg9u(a)mail.gmail.com
From: Tom H on 13 Jul 2010 02:20
On Tue, Jul 13, 2010 at 2:02 AM, Sven Joachim <svenjoac(a)gmx.de> wrote:
> On 2010-07-13 07:45 +0200, H.S. wrote:
>
>> On 13/07/10 01:28 AM, Tom H wrote:
>>>
>>> Yes. The Fedora/RHEL initrd names are not recognized by Debian/Ubuntu's grub...
>
> It should work in os-prober 1.39.

Thanks for the info. As I said in a previous email, I thought that it
had been fixed.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/AANLkTilMwpN8oqYGCq5-UJqveTtn38HsyYgNNGLPkKA8(a)mail.gmail.com
 | 
Pages: 1
Prev: Re (2): output from udevadm
Next: thinking of installing amd64 Debian: what is its current state?