[prev in list] [next in list] [prev in thread] [next in thread]
List: netbsd-port-alpha
Subject: Re: DEC PWS500au (MiataGL) EIDE Issues
From: Alexander Jacocks <jjacocks () gmail ! com>
Date: 2022-01-04 9:24:12
Message-ID: CAF-r0Y1BnMEz219rpKCxP8jdaB4DZbnZtbJPDS6YJoba__3VKw () mail ! gmail ! com
[Download RAW message or body]
DId you have any further thoughts on this?
Thanks!
- Alex
On Sat, May 29, 2021 at 11:06 AM Jason Thorpe <thorpej@me.com> wrote:
>
>
> > On May 28, 2021, at 8:29 AM, Alexander Jacocks <jjacocks@gmail.com>
> wrote:
> >
> > Sorry for the delay!
> >
> > So, I booted the no-cypide kernel, and it cleared the "stray isa irq"
> messages. However, I don't seem to be able to do anything with the CD-ROM
> (stock Toshiba XM-6302b) attached as the secondary slave device.
>
> Yup, ok, so we're definitely seeing a more fundamental problem. I know
> this used to work, but obviously something went haywire at some point.
>
> I'm going to need to stare at the data sheet for a bit. Stay tuned.
>
> >
> > Here are the boot logs:
> >
> > <snip>
> > [ 1.0000000] pciide0 at pci0 dev 7 function 1: Contaq Microsystems
> 82C693 PCI-ISA Bridge (rev. 0x00)
> > [ 1.0000000] pciide0: primary channel ignored (not responding;
> disabled or no drives?)
> > [ 1.0000000] pciide0: secondary channel ignored (other hardware
> responding at addresses)
> > [ 1.0000000] pciide1 at pci0 dev 7 function 2: Contaq Microsystems
> 82C693 PCI-ISA Bridge (rev. 0x00)
> > [ 1.0000000] pciide1: primary channel ignored (not responding;
> disabled or no drives?)
> > [ 1.0000000] pciide1: secondary channel interrupting at isa irq 15
> > [ 1.0000000] atabus0 at pciide1 channel 1
> > <snip>
> > [ 1.2316134] sd0 at atapibus0 drive 0:
> <\007\007x\003xx\000x\000\000\004\000\000\0\000 7O BHD MR-X23, 0\000 7O BHD
> MR-X23, \002> disk removable
> > [ 1.3839553] uhub0 at usb0: NetBSD (0000) OHCI root hub (0000), class
> 9/0, rev 1.00/1.00, addr 1
> > [ 1.4974007] sd0(pciide1:1:0): Sense Error Code 0x60
> > [ 1.5538064] sd0: drive offline
> > <snip>
> >
> > And, of course, the drive isn't available:
> >
> > -bash-5.1$ sudo fdisk sd0
> > fdisk: cannot opendisk /dev/rsd0: Device not configured
> >
> > Any suggestions?
> >
> > Thanks!
> > - Alex
> >
> > On Sat, May 22, 2021 at 10:34 AM Jason Thorpe <thorpej@me.com> wrote:
> >
> >
> > > On May 18, 2021, at 9:15 PM, Alexander Jacocks <jjacocks@gmail.com>
> wrote:
> > >
> > > I finally managed to get the system up, having found a different LSI
> 53c875 SCSI controller, that seems to work.
> > >
> > > Is there anything that I can do to test, easier, now that the system
> is working?
> >
> > Hey Alex, sorry I wasn't able to work on this for a couple of days.
> >
> > So, I think the first experiment to try is: build a kernel without
> "cypide" … just use the fall-back "pciide" driver that will only do PIO,
> and see if that does any better.
> >
> > I built one for you:
> >
> > http://www.netbsd.org/~thorpej/netbsd-alpha-9-2-GENERIC-no-cypide.gz
> >
> > Give that a whirl… if it results in a working drive (using the slower
> PIO modes), then that narrows down where we need to look.
> >
> > Thanks!
> >
> > -- thorpej
> >
>
> -- thorpej
>
>
[Attachment #3 (text/html)]
<div dir="ltr">DId you have any further thoughts on \
this?<div><br></div><div>Thanks!</div><div>- Alex</div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 29, 2021 at 11:06 \
AM Jason Thorpe <<a href="mailto:thorpej@me.com">thorpej@me.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><br>
<br>
> On May 28, 2021, at 8:29 AM, Alexander Jacocks <<a \
href="mailto:jjacocks@gmail.com" target="_blank">jjacocks@gmail.com</a>> \
wrote:<br> > <br>
> Sorry for the delay!<br>
> <br>
> So, I booted the no-cypide kernel, and it cleared the "stray isa irq" \
messages. However, I don't seem to be able to do anything with the CD-ROM (stock \
Toshiba XM-6302b) attached as the secondary slave device.<br> <br>
Yup, ok, so we're definitely seeing a more fundamental problem. I know this used to \
work, but obviously something went haywire at some point.<br> <br>
I'm going to need to stare at the data sheet for a bit. Stay tuned.<br>
<br>
> <br>
> Here are the boot logs:<br>
> <br>
> <snip><br>
> [ 1.0000000] pciide0 at pci0 dev 7 function 1: Contaq Microsystems 82C693 \
PCI-ISA Bridge (rev. 0x00)<br> > [ 1.0000000] pciide0: primary channel ignored \
(not responding; disabled or no drives?)<br> > [ 1.0000000] pciide0: secondary \
channel ignored (other hardware responding at addresses)<br> > [ 1.0000000] \
pciide1 at pci0 dev 7 function 2: Contaq Microsystems 82C693 PCI-ISA Bridge (rev. \
0x00)<br> > [ 1.0000000] pciide1: primary channel ignored (not responding; \
disabled or no drives?)<br> > [ 1.0000000] pciide1: secondary channel \
interrupting at isa irq 15<br> > [ 1.0000000] atabus0 at pciide1 channel 1<br>
> <snip><br>
> [ 1.2316134] sd0 at atapibus0 drive 0: \
<\007\007x\003xx\000x\000\000\004\000\000\0\000 7O BHD MR-X23, 0\000 7O BHD \
MR-X23, \002> disk removable<br> > [ 1.3839553] uhub0 at usb0: NetBSD \
(0000) OHCI root hub (0000), class 9/0, rev 1.00/1.00, addr 1<br> > [ \
1.4974007] sd0(pciide1:1:0): Sense Error Code 0x60<br> > [ 1.5538064] sd0: \
drive offline<br> > <snip><br>
> <br>
> And, of course, the drive isn't available:<br>
> <br>
> -bash-5.1$ sudo fdisk sd0<br>
> fdisk: cannot opendisk /dev/rsd0: Device not configured<br>
> <br>
> Any suggestions?<br>
> <br>
> Thanks!<br>
> - Alex<br>
> <br>
> On Sat, May 22, 2021 at 10:34 AM Jason Thorpe <<a \
href="mailto:thorpej@me.com" target="_blank">thorpej@me.com</a>> wrote:<br> > \
<br> > <br>
> > On May 18, 2021, at 9:15 PM, Alexander Jacocks <<a \
href="mailto:jjacocks@gmail.com" target="_blank">jjacocks@gmail.com</a>> \
wrote:<br> > > <br>
> > I finally managed to get the system up, having found a different LSI 53c875 \
SCSI controller, that seems to work.<br> > > <br>
> > Is there anything that I can do to test, easier, now that the system is \
working?<br> > <br>
> Hey Alex, sorry I wasn't able to work on this for a couple of days.<br>
> <br>
> So, I think the first experiment to try is: build a kernel without "cypide" … \
just use the fall-back "pciide" driver that will only do PIO, and see if that does \
any better.<br> > <br>
> I built one for you:<br>
> <br>
> <a href="http://www.netbsd.org/~thorpej/netbsd-alpha-9-2-GENERIC-no-cypide.gz" \
rel="noreferrer" target="_blank">http://www.netbsd.org/~thorpej/netbsd-alpha-9-2-GENERIC-no-cypide.gz</a><br>
> <br>
> Give that a whirl… if it results in a working drive (using the slower PIO \
modes), then that narrows down where we need to look.<br> > <br>
> Thanks!<br>
> <br>
> -- thorpej<br>
> <br>
<br>
-- thorpej<br>
<br>
</blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic