On Wed, 5 Jun 2002, Antoine Delvaux wrote:
> Le mercredi 5 juin 2002 vers 8:19, Michel Lanners écrivait :
> > On 4 Jun, this message from Antoine Delvaux echoed through
> > cyberspace:
> >> Since two days I've been in touch with the developper of the eata.c
> >> driver (Ballabio Dario) and he gave me a few debug version of that
> >> driver to play with. Unfortunately we have come to a point where he
> >> can't do more since the problem seems to come from PCI code of the
> >> ppc kernel tree.
> >>
> >> If anyone here have experience in this field, I welcome his advices
> >> as do not know where to start to search. With the latest debugging
> >> enabled eata.c module given by Ballabio, I've got the following
> >> output :
> >
> > I had some similar problems when trying to make a Promise IDE card
> > work in my Mac... but that was a few years ago.
> >
> >> # insmod eata.o io_port=0x1400
> > ^^^^^^
> > Where are you getting this value from? I'm sure it is wrong... Have a
> > look at the boot messages of your kernel, and also send along the
> > output of 'lspci -vv'.
>
> I'm getting this addresse from lspci and from previous tries with
> modprobe eata.o (which gives exactly the same results as insmod BTW)
> Here is the lspci -vv output regarding this card :
>
> 00:0f.0 SCSI storage controller: Distributed Processing Technology
> SmartCache/Raid I-IV Controller (rev 02)
> Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 32 (1000ns min, 2000ns max), cache line size 08
> Interrupt: pin A routed to IRQ 25
> BIST result: 00
> Region 0: I/O ports at 1400 [disabled] [size=32]
> Expansion ROM at 80908000 [disabled] [size=32K]
>
> >> # tail /var/log/syslog Jun 4 13:52:38 brocoli kernel: IN from bad
> >> port 1408 at d005392c
> >
> > This message means you are trying to read from an address where no
> > device is listening. Either the IO port (0x1408) is wrong, or the
> > device isn't configured to reply to IO accesses on the PCI bus.
>
> Why could the device not be configured to reply to IO accesses on the
> PCI bus ?
Because no one enabled it?
Apparently the eata driver doesn't call pci_enable_device().
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
