Re: Sid on ultra1 status
2018-08-14 19:32 GMT+02:00 John Paul Adrian Glaubitz : > Are you booting with a serial console? If yes, try adding "console=ttyS0" > or whatever is your serial device. Although that *should* be added > automatically. No, unfortunately I don't have serial-capable hardware (or cable) were the machine lives at the moment. I boot graphically - type 5 kbd & mouse, 17" 1280x1024 LCD on the FFB2+ (Creator 3D serie 2). At the stage where the systems hangs, linux has already switched the console AFAICT. I can interact with the shells spawned by BOOT_DEBUG=3 with no issue (well, the first two before the hang). Cordially, -- Romain Dolbeau
Re: Sid on ultra1 status
On 08/14/2018 06:05 PM, Romain Dolbeau wrote: > Trying to install from the 2018-05-18 image doesn't work. The system > hangs after displaying "starting syslogd, klogd". I tried > BOOT_DEBUG=3, the first two shells are fine - and it seems the disks > are seen on the ESP SCSI. Immediately after the second shell, the > syslogd/klogd line, and then nothing. Are you booting with a serial console? If yes, try adding "console=ttyS0" or whatever is your serial device. Although that *should* be added automatically. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Sid on ultra1 status
2018-08-14 18:11 GMT+02:00 Romain Dolbeau :
> 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\,880/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 :
> 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
Re: Sid on ultra1 status
> 1) when grub starts, after "GRUB Loading kernel", I have two error lines: > # > error: out of memory. > error: no suitable video mode found. > # > then I get the menu just fine anyway. I believe this is 'normal', I got the same with two different video adapters. (Creator3D and Mach64) > 2) after selecting the Debian entry from the menu I get: > # > Recalibrate failed. The floppy drive is either missing, improperly > connected, or defective. > error: unable to open /sbus/@1f,0/SUNW,fdtwo@f,140. > # > and then nothing. > Sometimes I get a second error, but mentioning a path to a hard drive > - "/sbus/SUNW,fas@e,880/sd", with the final @0,0 (or @1,0) > missing. I'm not able to reproduce this second error at the moment, > don't know why. 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.
Re: Sid on ultra1 status
> 1) when grub starts, after "GRUB Loading kernel", I have two error lines: > # > error: out of memory. > error: no suitable video mode found. > # > then I get the menu just fine anyway. > 2) after selecting the Debian entry from the menu I get: > # > Recalibrate failed. The floppy drive is either missing, improperly > connected, or defective. > error: unable to open /sbus/@1f,0/SUNW,fdtwo@f,140. > # > and then nothing. > Sometimes I get a second error, but mentioning a path to a hard drive > - "/sbus/SUNW,fas@e,880/sd", with the final @0,0 (or @1,0) > missing. I'm not able to reproduce this second error at the moment, > don't know why. I patched the grub.cfg to remove some conditionals and 'echo' every command. As far I can tell, the 'search' command is failing. I did get the 2nd error message: # Invalid SCSI target number fff9afc8 error: unable to open /sbus/SUNW,fas@e,880/sd. # Does it mean that when grub 'search' for the /boot UUID, it gets the wrong device entry ? (missing @sd1,0) Cordially, -- Romain Dolbeau
