Bug 31319 - Sony AIT-1 drive not accessible
Summary: Sony AIT-1 drive not accessible
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 4.4-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-16 21:20 UTC by Dylan Carlson
Modified: 2001-10-16 23:42 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dylan Carlson 2001-10-16 21:20:00 UTC
Kernel detects Sony AIT tape changer correctly at boot-time, but 'mt' and 'tapetype' (amanda) do not work with it.  I have confirmed the device to work in Solaris and NT.

I think I'm just missing something obvious.

See various outputs below.

-----------------------------------
Oct  9 21:10:20 galileo /kernel: Waiting 15 seconds for SCSI devices to settle
Oct  9 21:10:20 galileo /kernel: sa0 at sym1 bus 0 target 12 lun 0
Oct  9 21:10:20 galileo /kernel: sa0: <SONY TSL-A300C L202> Removable Sequential Access SCSI-2 device
Oct  9 21:10:20 galileo /kernel: sa0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit)
Oct  9 21:10:20 galileo /kernel: pass1 at sym1 bus 0 target 12 lun 1
Oct  9 21:10:20 galileo /kernel: pass1: <SONY TSL-A300C L202> Removable Changer SCSI-2 device
Oct  9 21:10:20 galileo /kernel: pass1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit)
-----------------------------------
crw-rw----   4 root      operator   14,   0 Oct 16 14:58 sa0
crw-rw----   4 root      operator   14,   0 Oct 16 14:58 sa0.0
crw-rw----   2 root      operator   14,   4 Oct 16 14:58 sa0.1
crw-rw----   2 root      operator   14,   8 Oct 16 14:58 sa0.2
crw-rw----   2 root      operator   14,  12 Oct 16 14:58 sa0.3
crw-rw----   2 root      wheel      14, 0x20000000 Oct 16 14:58 sa0.ctl
-----------------------------------
galileo# mt -f /dev/sa0 status
mt: /dev/sa0: Device not configured
-----------------------------------
galileo# camcontrol devlist -v
scbus0 on sym0 bus 0:
<  >                               at scbus0 target -1 lun -1 ()
scbus1 on sym1 bus 0:
<SONY TSL-A300C L202>              at scbus1 target 12 lun 0 (pass0,sa0)
<SONY TSL-A300C L202>              at scbus1 target 12 lun 1 (pass1)
<  >                               at scbus1 target -1 lun -1 ()
scbus-1 on xpt0 bus 0:
<  >                               at scbus-1 target -1 lun -1 (xpt0)

How-To-Repeat: 1. Install a basic full distribution of 4.4-RELEASE on a Compaq 1600R 6/500 system with the integrated SCSI2 adapter, with the Sony A300C AIT1 changer attached.

2. mt -f /dev/sa0 status
Comment 1 Kenneth D. Merry freebsd_committer freebsd_triage 2001-10-16 21:27:09 UTC
State Changed
From-To: open->feedback

Looks like you're missing the ch device in your kernel config file. 

Put: 

device		ch 

in your config file, re-run config, recompile, reinstall and reboot.  You 
should then be able to access the changer with chio(1) to move tapes around. 

Let me know if that fixes it (CC your reply to 
FreeBSD-gnats-submit@FreeBSD.org) so this PR can be closed.
Comment 2 Dylan Carlson 2001-10-16 23:33:57 UTC
Fixed


--- ken@FreeBSD.org wrote:
> Synopsis: Sony AIT-1 drive not accessible
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: ken
> State-Changed-When: Tue Oct 16 13:27:09 PDT 2001
> State-Changed-Why: 
> Looks like you're missing the ch device in your kernel config file.
> 
> Put:
> 
> device		ch
> 
> in your config file, re-run config, recompile, reinstall and reboot.  You
> should then be able to access the changer with chio(1) to move tapes around.
> 
> Let me know if that fixes it (CC your reply to
> FreeBSD-gnats-submit@FreeBSD.org) so this PR can be closed.
> 
> 
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31319


__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
Comment 3 Kenneth D. Merry freebsd_committer freebsd_triage 2001-10-16 23:41:47 UTC
State Changed
From-To: feedback->closed

Submitter says his problem is fixed by adding the ch driver to his kernel 
config.