lkml.org 
[lkml]   [1999]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: problems with SCSI cdrom
Date
> for the state of the art computer and perphrials that are all exciting 
> to use with linux that developers like. When booting up a 2.2.3 kernel I

I must have been imagining things when I spent most of this week working
on obsolescent technology - MCA bus, the NCR5380 and the AHA152x

> Future Domain 16-bit SCSI Driver Version 5.50 scsi0: <fdomain> BIOS
> version 3.4 at 0xca000 using scsi id 7
> scsi0: <fdomain> TMC-18C30 chip at 0x140 irq 5
> arbitration (2), target = 1 cmnd = 0x00 pieces = 0 size = 256
> sent_command = 0, have_data_in = 0, timeout = 0
> in_interrupt_flag = 0
> IMR = 0x9ed8, IRR = 0x0000, ISR = 0x0000
> SCSI Status = 0x01
> TMC Status = 0x43
> Interrupt Status = 0x28 (enabled)
> FIFO Status = 0x08
> Int. Condition = 0x10
> Configuration 1 = 0x82
> Configuration 2 = 0x07scsi : aborting command due to timeout : pid 2,
> scsi0, channel 0, id 2, lun 0 Test Unit Ready 00 00 00 00 00scsi:
> <fdomain> abort

Does a 2.0 kernel find the CDROM correctly ? In truth you may well be the
almost the first person to use the 16bit FD driver in 2.2...

Alan



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:51    [W:0.037 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site