On Mon, 28 Apr 2003, Jay Estabrook wrote: > > The SCSI hd and cdrom are detected, but it tries to spin it up > > immediately afterwards ... and seems to stop then. > > My symptoms were a stream of SCSI error messages related to the CDROM > (unit 6), but not the HD. When I disconnected the CDROM, the HD was > recognized and MILO was usable to boot from, which I proceeded to do. > > I believe that the problem is in the QLogic driver used in the MILO; > if possible, work around it by isolating the CDROM on it's own SCSI > bus, using another SCSI controller, say QLogic or NCR.
I'm using the XLT MILO and finally can report success: the problem with MILO unable to spin up the disk was solved by setting a jumper on the hard drive (PARITY DISABLE). So booting using MILO works mostly, except that it doesn't do it automatically. E.G. I can boot the installed Debian/Linux on the harddrive with: MILO> boot scda1:/boot/vmlinuz root=/dev/sda1 I also figured out that there is a boot image on the CD at sr0:boot/linux, however I didn't figure out what the exact command line is for booting the debian installer from CDROM. At least something like 'boot sr0:boot/linux root=/dev/scd0 load_ramdisk=1' doesn't work, since no ramdisk is found, and I don't find any that I could specify on the command line with 'initrd='. > Finally, I had the following success running X from the XLT MILO: > > 1. Voodoo Banshee > 2. ATI Rage 128 > 3. ATI Radeon 7500 I can now run X from the XLT MILO, 3d works aswell (if I use 16bpp, Voodoos hardware limitation). However I have to boot from CDROM, start the XLT MILO, enter the boot command until I finally can use my machine. So now I try to create a FAT partition, put MILO on it so I can use my Linux on the harddisk (which was installed using SRM, but luckily MILO understands BSD disklabels). Thanks, Max
