Thanks for the reply.
>
>The driver works on Blue&White G3 with TI PCI1410 adapter. So it's not a
>PowerPC problem. It's something more special to your setup.
The machine I'm running on, being nubus architecture, seems to be sufficiently
different to 'normal' pci based macs to cause a lot of problems like this. They
aren't supported by the official kernel, and are ported from the official tree
continuously.
>> The drivers compile fine, but when they are loaded I get in dmesg:
>>
>> cardmgr[9777]: socket 0: Cabletron RoamAbout 802.11 DS
>
>Please make sure that the card works on a PC with the same driver. While
>the card is listed in hermes.conf, "802.11 DS" may indicate that it has
>very old, pre-802.11b hardware, possibly with some quirks.
>
>Please run "cardctl config" and "cardctl status" both on the PC and in the
>nubus adapter. Compare them. Check Vcc voltage and make sure that your
>nubus adapter can actually provide that voltage.
I'll try, but as I have no current access to a pc laptop or a pci cradle, I
don't know how easy it will be. The card does work perfectly in the mac laptop
under mac os with the orinoco drivers, so it's not a hardware problem as such,
more just the drivers.
>
>> kernel: trex: XXX enabling card interrupts
>> last message repeated 3 times
>
>This is not from the driver. I hope you know where it comes from.
Yes, trex is the name of apple's pcmcia chipset that was used in this laptop.
It was only ever used in about 4 different mac laptops I think. It is
non-standard in that it also isn't supported by the kernel or by the official
pcmcia_cs package. The drivers for this chipset have only been written in the
last 6 months or so, so problems are somewhat to be expected.
>
>> kernel: eth1: failed to initialize firmware (err = -19)
>
>It's a failure in hermes_init(). Most likely the HERMES_CMD register
>could not be read. 0xffff was read instead. It's a hardware problem of
>some kind. Either the card firmware is not functioning, or the I/O
>registers are not mapped where they should be, or the data arrives too
>late (i.e. the latency is not set properly by the socket driver).
>
I think this might be what I was looking for thanks, a more detailed
description of the error. I'll follow this up with this info on the
nubus-kernel mailing list, although I don't think the person who actually wrote
the trex driver is very involved with the list.
>
>Please don't worry about firmware versions as long as the card is working
>on a PC with the same driver.
>
>I'm almost sure that the problem is not in the Orinoco driver. PCMCIA
>cards vary in their I/O and memory requirements, voltage and latency.
>Please check the socket driver.
>
>It may be more useful to send further questions to
>linux-pcmcia-IAPFreCvJWM7uuMidbF8XZu6nac5fYnt@xxxxxxxxxxxxxxxx You can refer
>to my opinion that the
>Orinoco driver is not doing anything wrong or unusual.
>
as the trex pcmcia driver isn't part of the official kernel, I'll follow it up
on the nubus kernel list. Thanks for the description of what the error means, I
probably should have asked more directly for that now I realise.
Thanks,
Andrew Leech
____________________________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
|
