On Tue, 2355 September 1993, Matthew Sean Thyer wrote:
> When "device scbus0" changed to "device scbus" in LINT and I applied
> that to my config file I found I could no longer wire down my disks
> to scbus0 unless I changed the base SCSI code line back to "device
> scbus0".
>
> This is what I have:
>
> device scbus0 # Base SCSI code
> device da0 at scbus0 target 0
> device da1 at scbus0 target 1
> device da2 at scbus0 target 2
> device da3 at scbus0 target 3
> device da4 at scbus0 target 4
> device da5 at scbus0 target 5
> device da6 at scbus0 target 6
>
> And it works fine.
Hmmm.
Doesn't work for me. Haven't seen any more comments on this
recently, but then, I haven't cvsup'ed anew for several days.
But before I go further, let me see if I can make my life a little
bit easier -- I have a 3-button mouse that is autodetected as type
microsoft, yet the middle button doesn't work to paste, with -current,
with -stable, I even tried it briefly under 2.2 to see if it would
work there cuz I was sure that I had it working. No go, and I don't
want to have to do something to hack around it if possible.
Where it does work is under Linux, type ms, all three buttons work
as I expect, so it's not a hardware error. It could be operator
error, I haven't exhaustively tried everything, but I did all that
I could think of under -current with all the different types, none
of which gave me clean 3-button mode.
Does anyone out there have a serial three-button mouse working as
type microsoft? Thanks...
Anyway, my -current kernel config file already had evidence that I
had attempted to use scbus0 without success sometime before...
ARGH! I don't have a spare machine here with a SCSI card, nor a
spare SCSI controller to throw into a machine to be able to
transcribe the dmesg and config file off my portable disk... So,
Anyway, I had a comment like `# will this work?' before the
commented `device scbus0', followed by a comment `#No.' I went
ahead and made a new kernel, but it failed to wire target 1 to
da0 as I specified.
What happens if you change the IDs of your drives, and change
your kernel config to match, something like
> device da0 at scbus0 target 0
> device da1 at scbus0 target 2
> device da2 at scbus0 target 1
> device da3 at scbus0 target 3
(swapping the IDs of da1 and da2 above)
Do you still see the desired disk as da1 and da2, or do you
still get target 1 wired to da1?
As far as I can see, your specified configuration works whether
or not the devices are wired, as everything is in order, while
I have to have things out of order, of necessity...
It could also be I'm overlooking something, so I'll keep trying...
brry bouwma, tle dnmark intrnet
--
*** This was posted with the express permission of ***
******************************************************
** HIS HIGHNESS KAAZMANN LORD AND MASTER OF USENET **
******************************************************
********* We are simple servants of his will *********
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
