Sorry for the delay in reply, spent the weekend, well, it involved not a lot hanging out in my stomach for long.

Anyway,

Let's try this from the ground up. ZERO out all the info in the GUI config so it doesn't try to do anything insane. After regular boot check out these commands:

/sbin/lsmod

To see if yenta_socket is loaded.

ps aux | grep cardmgr

To see if cardmgr is actually running and listening to that sucker. If the "ps" command above brings back nothing, or only the grep itself, then pcmcia services isn't starting right and we can debug that.

It it is running... should return something like:
root@sidearm:~# ps aux | grep cardmgr
root 83 0.0 0.2 1500 536 ? Ss Jul11 0:01 /sbin/cardmgr
root 11875 0.0 0.2 1672 580 pts/0 R+ 10:40 0:00 grep cardmgr

Take a look at lsmod again and see if it loaded 3c59x, if its loaded... then lets see what ethX name it got assigned:

dmesg | grep eth

If its eth0 then I am at a loss as to why a good solid: dhclient eth0 won't snag it an IP...

Something along the way there is horking, its just a matter of figuring out which one.

Cheers,

Finegan

Finegan,

I got it working! I found my identical problem on linuxforum. Apparently the 3c589 ethernet card not working at bootup is a known bug in fedora core 2, and there is a temporary workaround. Here's what I learned:

http://www.linuxforum.com/forums/ind...0&#entry371048

Thanks for all of your help, man. Taking what I learned from our discussion, it was a lot easier to implement their solution.

Now, if I could only get the sound working on this laptop, I'll be set...

Hi, I got all things okey down until the 'ps' command. I got the yenta_socket row in lsmod, I have the cardmgr process running etc...

What don't is correct are that lsmod do not say "3c59..." on any row? What must I do to make it end up there?
I have the lamps on my PCMCIA litten up now but can still not activate it, gives "eth0 does not seem to be preset"

/Thanx for any tips!
fLa

The lights just show a completed circuit. What's the output of:

/sbin/cardctl ident

Also:

dmesg | grep eth

That'll tell us what's there exactly, basically if cardmgr is seeing anything present.

Cheers,

Finegan

Hi, I've been busy lately. Back on track and problem solving:

Here is my data:

/sbin/lsmod out has one line saying
pcmcia_core 46792 2 yenta_socket, ds
and another one saying
yenta_socket 15104 1

ps aux lists the /sbin/cardmgr process

But then I dont find any 3c59x using lsmod

The command "/sbin/cardctl ident" gives this:
Socket 0:
product info: "3Com Corporation", "3C589", "TP/BNC LAN Card Ver. 2a", "000002"
manfid: 0x0101, 0x0589
finction: 6 (network)
Socket 1:
no product info available

And the "dmesg | grep eth" gives:
divert: not allocating divert_blk for non-ethernet device lo
divert: not allocating divert_blk for non-ethernet device sit0

I hope this helps me out, what could be wrong?

/fLa

The 3c589, which you have, is not supported by the 3c59x module. The latter supports Cyclone and Vortex-based cards (to name the most common ones). These are quite different to the 3c589, which use the 3c589_cs module. Try modprobe 3c589_cs, and if no errors occur, check the last few lines of your dmesg output. It should contain information about the initialization of your card.


Håkan

Okey, here is the printout of "modprobe 3c589_cs"

FATAL: Error inserting 3c589_cs (/lib/modules/2.6.5-1.358/kernel/drivers/net/pcmcia/3c589_cs.ko): Unknown symbol in module, or unknown parameter (see dmesg)


dmesg gives some lines with this:

Yenta: CardBus bridge found at 0000:00:03.1 [1028:00aa]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:03.1. mfunc 0x01261222, devctl 0x66
yenta: ISA IRQ mask 0x0698, PCI irq 11
Socket status: 30000006

further down it says:

3c589_cs: Unknown parameter 'irq'

And the "dmesg | grep eth" gives:
divert: not allocating divert_blk for non-ethernet device lo
divert: not allocating divert_blk for non-ethernet device sit0

Also a couple of lines about cs: IO probe and also PCI: Sharing IRQ 11 with ......

Seams to be a problem with the parameter IRQ or??

/fLa

3c589_cs is a card services module, old pcmcia, so you can't modprobe it by hand. There must be some odd reason why pcmcia-cs's cardmgr isn't binding the module correctly. Also, don't sweat the IRQ thing, if this were 1999 that would be a likely culprit. Most likely its a version of the 3c589 that isn't in the file /etc/pcmcia/config so cardmgr doesn't recognize it as a proper 3c589. Check through that file and see if the config entry has the right manfid entry:

card "3Com 589 Ethernet"
manfid 0x0101, 0x0589
bind "3c589_cs"

Cheers,

Finegan

The config entry seams to be right, exactly as you wrote.

I'm getting irritated now, strange things might soon happen....

:-/

/fLa

Okay, let's tackle this one straightforware then... cardmgr and pcmcia are running, and running fine. Cardmgr can see the card in the socket, so let's assume that there's nothing wrong with the drivers from the pcmcia end of things...

Open up 2 terms, in one:

tail -f /var/log/messages

In the other:

/etc/init.d/pcmcia restart

And take a look at what gets logged in the other term. Post back with it if you can.

Cheers,

Finegan

Okey here is the summurized printout, each row is shorten down. Let me know if you need the exact printout of any line:

cardmgr exiting
cardmgr watching 2 sockets
kernel cs IO port probe 0x0c00-0x0cff clean.
kernel cs IO port probe 0x0100-0x04ff excluding 0c4d0-0x4d7
kernel cs IO port probe 0x0a00-0x0aff clean.
cardmgr socket 0 3Com 589 Ethernet
unknown parameter irq
executing 'modprobe 3c589_cs 2>&1'
+ FATAL: Error inserting 3c589_cs (/lib/modules/2.6.5-1.358/kernel/drivers/net/pcmcia/3c589_cs.ko): Unknown symbol in module, or unknown parameter (see dmesg)
modprobe exited with status 1
module /lib/modules/2.6.5-1.358/pcmcia/3c589_cs.o not available
bind '3c589_cs' to socket 0 failed: Invalid argument