thanks for the note, yes this did work. for others' reference, using the 2.4.3-benh kernel, i had to compile my own current pcmcia-cs (the one in unstable didn't work)
i had to modify the file /etc/pcmcia/config.opts to contain include port 0x100-0x4ff, port 0x1000-0x17ff include memory 0x80000000-0x80ffffff instead of the default values and i managed to get a 574-based card to work (marked as x86-only in the supported list but i sent in my success report) the card appears to run hot (the fan turns on -- i thought it was broken) and i can't rsync my whole hard drive or the process hangs and the card gets *really* hot. so i will have to watch this thing but at least it works for simple net tasks. i'll see if my 589-based card runs better. brad > there is some pcmcia config file in /etc and in /etc/pcmcia that > requires a bit of tweaking. Actually I did not succesfully try PCMCIA > on a 2.4.x yet, but on 2.2.x it works pretty well. > > parameters that require tweaking: > - I/O range, is defined in /etc/pcmcia/config (or config.opts ?) > see the doku that came with the pcmcia_cs package, there they say > that for PowerPC machines you need to redefine the I/O range to > something like 0x80000000-0x80ffffff or so > - chipset type: the kernel hangs rather badly if it tries to initialize > a PCMCIA controller using the wrong chipset. > > PS: as a network card, I'm using an Abocom FE1000, being basically > a 10/100Mbps NE2000 clone. It works, but not too perfectly: only > when power cable is attached, and only in the upper PCMCIA slot, > and it eventually requires multiple /etc/init.d/pcmcia restart to get > it up and working. (As seen on my Powerbook 2400c) > > bye > Philipp Kaeser / [EMAIL PROTECTED] > -- [EMAIL PROTECTED] Brad Midgley
