Re: Sid on ultra1 status
2018-08-14 18:11 GMT+02:00 Romain Dolbeau <romain@dolbeau.org>:
> Does it mean that when grub 'search' for the /boot UUID, it gets the
> wrong device entry ? (missing @sd1,0)
There's definitely a bug somewhere, as 'ls' in the grub command line
also generates the errors and hang...
However - when loading, 'grub' sets the $root variable to something
similar, starting with ieee1275 and featuring some escapes.
So if I don't set 'root' at all - grub looks in its own partition, and
everything seems to work fine...
The entry that actually works (minus the root UUID):
#####
menuentry 'SIMPLE Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option 'gnulinux-simple' {
load_video
echo 'insmod gzio'
insmod gzio
echo 'insmod part_sun'
insmod part_sun
echo 'insmod ext2'
insmod ext2
echo 'set root'
set root='ieee1275//sbus@1f\,0/SUNW\,fas@e\,8800000/sd@1\,0,sun1'
echo 'Loading Linux 4.17.0-1-sparc64 ...'
linux /vmlinuz-4.17.0-1-sparc64 root=UUID=X-X-X-X-X ro
echo 'Loading initial ramdisk ...'
initrd /initrd.img-4.17.0-1-sparc64
}
#####
So it's the dev name prefixed by ieee1275/, '\' before all ',', and
',sun1' to indicate the partition (no \ on this comma)...
2018-08-14 19:08 GMT+02:00 Gregor Riepl <onitake@gmail.com>:
> I believe this is 'normal', I got the same with two different video adapters.
> (Creator3D and Mach64)
OK, so it's not the source for the messed up 'search' and 'ls', we can suppose.
> I don't think I can help you, but I did have lots of floppy drive problems on
> my system, so I simply unhooked it. Might be that the Linux floppy driver is
> currently broken, or a hardware problem.
There's a floppy slot but no actual drive in there. 'search' has
--no-floppy by default...
Weird that it tries, but that just may be the same bug twice: grub
uses a wrong dev entry?
Cordially,
--
Romain Dolbeau
Reply to: