[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Installing Debian/Hurd



>> From: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>
>> 
>> On Sat, Mar 04, 2000 at 02:57:53AM -0600, Ali Hamisheh-Bahar wrote:
>> >  |
>> >  | Will a Linux scsi driver module work with the hurd kernel somehow ?
>> > 
>> > Not being intimately knowledgable about hurd, I'd still venture to
>> > say, 'no'. A driver is tightly bound to a kernel.
>> 
>> The scsi and all other block device drivers in gnumach are taken straight
>> from linux, with very little changes in some cases.
>> 
>> In most cases you can just plug the linux source file in the appropriate
>> directory and do some changes to the source and expect it to work.

 Well, in that case, I expect I need a source package so I can do some
 playing around meself !

 Latest, is my own chicken scratches of the sequence of error...

 Sometime after probing parallel ports, and such, after the failed WD-7000,
 I get...

scsi: AdvanSys SCSI 3.1E PCI Ultra 16 CDB: IO FCC0/F, IRQ 9
scsi: 1 host
scsi: aborting command due to timeout: pid 0, scsi 0, channel 0, id 0, LUN 0, 0x 00 00 00 00 00 00
SCSI host 0 abort ( pid 1 ) timed out - Resetting
SCSI bus is being reset for host 0 channel 0
scsi: aborting command due to timeout: pid 0, scsi 0, channel 0, id 0, LUN 0, 0x 00 00 00 00 00 00
SCSI host 0 abort ( pid 1 ) timed out - Resetting
SCSI bus is being reset for host 0 channel 0
scsi: aborting command due to timeout: pid 1, scsi 0, channel 0, id 1, LUN 0, 0x 00 00 00 00 00 00
SCSI host 0 abort ( pid 2 ) timed out - Resetting
SCSI bus is being reset for host 0 channel 0
scsi: aborting command due to timeout: pid 1, scsi 0, channel 0, id 1, LUN 0, 0x 00 00 00 00 00 00
SCSI host 0 abort ( pid 2 ) timed out - Resetting
SCSI bus is being reset for host 0 channel 0

 This entire aborting command sequence is repeated 14 times or so, as the pid and id 
 repeat once, and increment by one, thru the second pid 6 and id 6.
 finally ending with

scsi : detected total

 and then the boot process continues up to...

Root device `sd0s1' does not exist !
Root device name ? [sd0s1]

 At that point, nothing I feed it will cause it to access the scsi drive again.

 Oh, bother ! ( as winnie would say )

 Also having some problems accessing partitions on other drives while
 running under VMWare, but that's probably my own fumble-fingers, or
 perhaps VMWare itself.

 Maybe I'll buy one of those removable IDE trays over the next few weeks....

--
Cowboy

To lead people, you must follow behind.
		-- Lao Tsu




Reply to: