Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Aug 1997 20:59:20 -0700 (PDT)
From:      Doug White <dwhite@resnet.uoregon.edu>
To:        Zach Heilig <zach@gaffaneys.com>
Cc:        questions@FreeBSD.ORG
Subject:   Re: Question about the sea0 device...
Message-ID:  <Pine.BSF.3.96.970824205814.27361T-100000@resnet.uoregon.edu>
In-Reply-To: <19970819093232.36248@gaffaneys.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Aug 1997, Zach Heilig wrote:

> sea0 at 0x0 irq 5 maddr 0xde000 msize 16384 on isa
> sea0: type Future Domain TMC-885/TMC-950
> sea0 waiting for scsi devices to settle
> (sea0:0:0): "SANYO CRD-254S 1.02" type 5 removable SCSI 2
> cd0(sea0:0:0): CD-ROM cd present [179142 x 2048 byte records]
> 
> The first problem is the whole computer will freeze for the second or three it
> takes the CD-ROM to wake up after sleeping for more than a few minutes.
> Everything stops (even the modem lights quit flashing, if the modem was
> otherwise busy).  Everything seems normal after the disk is up to speed
> though.  Is this an artifact from the sea0 driver, or should I suspect my
> cdrom drive?

This is normal and is probably a by-product of the design of the sea
device.  Not much we can do for ya.

> The other problem is a conflict with sbxvi0... here are the appropriate
> lines from the kernel config file:
> 
> controller sea0 at isa? bio irq 5 iomem 0xde000 iosiz 0x2000 vector seaintr
> controller scbus1 at sea0 bus 0
> device cd0 at scbus1 target 0 unit 0
> 
> controller snd0
> device sb0 at isa? port 0x220 irq 10 drq 1 vector sbintr
> device sbxvi0 at isa? drq 5
> device sbmidi0 at isa? port 0x330
> device opl0 at isa? port 0x388
> 
> and the lines from dmesg:
> 
> sbxvi0 not probed due to I/O address conflict with sea0 at 0x0
> 
> The sea0 driver doesn't use I/O address 0x0, does it?  The sbxvi0 driver
> doesn't advertise using that I/O addr either.  Is this something that can be
> resolved (perhaps with that new sound driver I keep reading about?) or should
> I just get a different SCSI controller [this is a future plan anyway].

Throw a 'conflicts' onto the sbxvi0 device line and it should quiet that.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major
Spam routed to /dev/null by Procmail    | Death to Cyberpromo




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970824205814.27361T-100000>