On 08/06/2018 10:39 PM, Fred wrote:
On 08/06/2018 11:20 AM, Frank Scheiner wrote:
>> [...]
The CDROM drive in my Ultra 10 is attached to IDE channel #2 (the IDE port farer away from the CPU) and configured as Master device.And I just now tested with the ISO in question (from 20180516-18:22) and didn't recognize an issue. Sure, hardware detection takes long on the Ultra 10, but it eventually succeeds and the CDROM drive is correctly detected.
>> [...]
Hi Frank, The MB has only three connectors: floppy, IDE HD and IDE cdrom.
But the two existing IDE ports are not labeled as such on the PCB, there is J14 which is the second IDE channel and J13 which is the first IDE channel (both according to [1]). At least that's the case on the system board PCB of my Ultra 10 and hence I referenced my known good configuration in this way.
[1]: http://www.shrubbery.net/~heas/sun-feh-2_1/Devices/System_Board/SYSBD_Ultra5_10.html#0066
I changed the DVD drive jumper from cable select to master but the installer still could not find it. Whatever loaded the installer program didn't have any problem using the drive.
This is perfectly normal, as soon as the Linux kernel is started it usually uses its own drivers to access devices. And if a specific CDROM drive and the assumed "compatible" driver don't work together, this results in a situation like yours:
Your firmware (OBP) can load and start the boot loader (SILO) from the CDROM, which itself - presumably using the same drivers as the firmware - can load and start the Linux kernel (plus initrd) from CDROM. The kernel then uses its own driver to access or to try to access the CDROM drive and fails for some reason.