From: Oliver R. <ol...@fu...> - 2003-06-07 11:17:29
|
Hi Christoph, On 06-Jun-03 18:22:33, Christoph Gutjahr wrote: >> I think you need to add "nobats" (minus quotes) to the bootstrap >> command-line, IIRC, to allow the BlizzPPC SCSI support to work. At >> least, that's what I use here, and everything is fine (my root partition >> is on a SCSI drive). I'm sure I remember reading that nobats was >> required, but can't remember where. > Thanks for the hint. I'm one step further now (it *does* recognise my > drives), but a new problem appeared. > > The kernel recognises the drive(s), but it gets stuck in an endless loop > as soon as it tries to "identify" the first drive in the chain. Lots of > error messages > (quote: "Duh? Bad things happening in the NCR driver"). It's not a > problem with a specific HD, I tried both. Hmmm... Can't say I've ever had that problem :( > Could you tell me how you configured the node that your SCSI drive is > connected to is configured in the BPPC early startup menu? I've got no I'm not sure if these have any effect on LinuxAPUS, but I have both the SCSI and NCR SCSI patches disabled (in the system section). For the SCSI section I have everything set to auto. However, for the SCSI IDs that I'm not using, I have manually set those all to NO LUN, so those IDs aren't scanned - figured it might speed things up. > idea about all those settings. What kernel parameters are you using? > Thanks in advance. I've absolutely no idea, sorry :( I'm using one of the older kernels - IIRC, it's the same one that was supplied on an Amiga Active CD-ROM some time ago (possibly 2.2.10). I've had nothing but problems with the 2.4 kernels, so I just stick with the old one :) I don't use Linux much anyway - just occassional testing with Mozilla and Opera. -- Oliver Roberts - http://www.oliver-roberts.co.uk/ - ICQ: 34640231 Pace 56 Solo mailing list ==> http://groups.yahoo.com/group/56solo/ |