Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Apr 2007 21:39:42 -0400
From:      "Dave" <dmehler26@woh.rr.com>
To:        "Robert Marella" <rmarella@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: locking down scsi device id's in 6.2
Message-ID:  <000701c77e35$c6d6f090$0200a8c0@satellite>
References:  <000501c778a1$769989b0$0200a8c0@satellite> <20070407124555.3243bbcb@p4> <000501c7797b$961a9010$0200a8c0@satellite> <20070409072701.0687c6cd@p4> <001701c77d69$360a20e0$0200a8c0@satellite> <20070412153231.6cdc124e@p4> <000501c77df4$1f0ee2f0$0200a8c0@satellite> <20070413150600.77fca4eb@p4>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello,
    Thanks for your reply. Please see below for responses.

----- Original Message ----- 
From: "Robert Marella" <rmarella@gmail.com>
To: "Dave" <dmehler26@woh.rr.com>; <freebsd-questions@freebsd.org>
Sent: Friday, April 13, 2007 9:06 PM
Subject: Re: locking down scsi device id's in 6.2


> On Fri, 13 Apr 2007 13:49:43 -0400
> "Dave" <dmehler26@woh.rr.com> wrote:
>
>> Hi,
>>     Either i've got a syntax error or my devices aren't wiring
>> obeying /boot/device.hints. I've added:
>>
>> hint.scbus.0.at="ahc0"
>>
>> to my config. The tape drive is consistent on scbus0, target5, lun0,
>> if i change it's target to say 3 it still shows up as scbus0,
>> target5, lun0, but the sa driver is now at sa1 vs. sa0 and pass2 i
>> think instead of pass0 not sure if this is important. The burner and
>> the rom device never moved, they're still on scbus 2 and 3.
>> Thanks.
>> Dave.
>>
>
> Please keep freebsd-questions included in your responses by replying
> to "all". I have added the list back in to this message.
>
> Please copy and paste what you now have edited in "/boot/device.hints"
> to your next reply.
Here is my add-ons to /boot/device.hints:

# custom devices
hint.scbus.0.at="ahc0"   #find this with dmesg
hint.sa.0.at="scbus0"
hint.sa.0.target="5"
hint.sa.0.unit="0"
hint.cd.0.at="scbus0"
hint.cd.0.target="0"
hint.cd.0.unit="0"
hint.cd.1.at="scbus0"
hint.cd.1.target="1"
int.cd.1.unit="0"

>
> Also, the "ahc0" id for an adaptec scsi controller. Is that what you
> have. What I mean is, does ahc0 show up in dmesg or did you just
> include it from my previous email?
I do have an adaptec scsi controller. Here's the dmesg output:

ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0xd000-0xd0ff mem 
0xe8116000-0xe8116fff irq 16 at device 5.0 on pci0
ahc0: [GIANT-LOCKED]
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs
sa0 at ahc0 bus 0 target 5 lun 0
sa0: <Quantum DLT4000 D996> Removable Sequential Access SCSI-2 device
sa0: 10.000MB/s transfers (10.000MHz, offset 15)
cd1 at ata1 bus 0 target 0 lun 0
cd1: <LITE-ON LTR-48246S SS06> Removable CD-ROM SCSI-0 device
cd1: 33.000MB/s transfers
cd1: Attempt to query device size failed: NOT READY, Medium not present
cd2 at ata1 bus 0 target 1 lun 0
cd2: <LITE-ON DVDRW SOHW-1633S BS0K> Removable CD-ROM SCSI-0 device
cd2: 33.000MB/s transfers
cd2: cd present [2295104 x 2048 byte records]



>
> Oh yeah, show me again what you have in "camcontrol devlist"
>
This is what the devices are now, whenever i alter /boot/device.hints and 
reboot this box the cd's go all over the place, sometimes they're cd2 and 3, 
other times 0 and 3 this is what camcontrol devlist shows now:

<Quantum DLT4000 D996>             at scbus0 target 5 lun 0 (sa0,pass0)
<LITE-ON LTR-48246S SS06>          at scbus3 target 0 lun 0 (cd1,pass1)
<LITE-ON DVDRW SOHW-1633S BS0K>    at scbus3 target 1 lun 0 (cd2,pass2)


> Thanks
>
> Robert
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe@freebsd.org"

Thanks.
Dave.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000701c77e35$c6d6f090$0200a8c0>