In the grub.cfg below, I fixed "sda1" to "sdb1". Still no go..
On Tuesday, June 25, 2019 at 5:59:54 PM UTC+1, jacksprat wrote:
>
> Lilo? Ii haven't given up trying to get grub.cfg right. here is a
> fragment
>
> #
> menuentry 'Void GNU/Linux 4.18.17 [sda1]' {
> insmod gzio
> insmod part_msdos
> insmod ext2
> set root='hd0,msdos1'
> echo 'Loading Linux 4.18.17_1 ...'
> linux /boot/vmlinuz-4.18.17_1 root=/dev/sda1 ro
> echo 'Loading initial ramdisk ...'
> initrd /boot/initramfs-4.18.17_1.img
> }
>
> It is the "set root" line that I suspect is wrong, but if "msdos1"=1st
> partition, why do both "hd0" and "hd1" fail? Close..
>
> On Tuesday, June 25, 2019 at 4:40:28 PM UTC+1, space pudim wrote:
>>
>> El mar., 25 de jun. de 2019 16:34, jacksprat <pica...@gmail.com>
>> escribió:
>>
>>> Well, I tried install to the identical pen drive that booted Void Linux
>>> Live, and repeated what I did to grub-install, and the resultant USB drive
>>> booted! However, the boot sequence died running the initramfs, just after
>>> running dracut on the first partition of my HD [/dev/sda1]. I have aleady
>>> seen my error in the grub.cfg file [scream]. This is going too be hard
>>> work, but worth it in the end [?]. Just got to remember how grub.cfg is
>>> coded..
>>>
>>
>> Maybe LILO is still an option?
>>
>>>
--
You received this message because you are subscribed to the Google Groups
"voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to voidlinux+unsubscr...@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/voidlinux/1604209a-e984-43ca-b5b8-9b547bd08de5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
