How can I get my PCMCIA network card to work at boot time in Fedora C2?

Hi,

The only way I can get my PCMCIA network card to work on Fedora C2 is:
1. Ensure that the PCMCIA service starts at boot.
2. Log in as root.
3. Activate the Network Card, manually.


This also means:

a. That if the Network service starts at boot - the Network Card does
not activate - even with root login.

b. That I do not get an automatic network connection when the system
boots - only manual activation with root login - works.

c. That if the system reboots after a power outage, there is no
network connection - until I login as root.


So the question is -
How can I get my PCMCIA network card to work at boot time?

Thanks.

Op 31 May 2004 04:10:06 -0700 schreef luther:

> Hi,
>
> The only way I can get my PCMCIA network card to work on Fedora C2 is:
> 1. Ensure that the PCMCIA service starts at boot.
> 2. Log in as root.
> 3. Activate the Network Card, manually.
>
> This also means:
>
> a. That if the Network service starts at boot - the Network Card does
> not activate - even with root login.
>
> b. That I do not get an automatic network connection when the system
> boots - only manual activation with root login - works.
>
> c. That if the system reboots after a power outage, there is no
> network connection - until I login as root.
>
> So the question is -
> How can I get my PCMCIA network card to work at boot time?
>
> Thanks.

Try reading:
http://www.bb-zone.com/SLGFG/chapter6.html
or
http://www.redhat.com/docs/manuals/l...down-sysv.html

AND

consider it *NOT DONE* to post in multiple groups.


--
-----=====##### PapaBear #####=====-----
Jesus is alive, I spoke with Him this morning!
----------------------------------------------

luther wrote:
> So the question is -
> How can I get my PCMCIA network card to work at boot time?

Check your /etc/modules.conf file, make sure there is a line
similar to this:

alias eth0 drivername

"drivername" should be the same name you are currently using
with modprobe.

On 31 May 2004 04:10:06 -0700, luther <(E-Mail Removed)> wrote:
> Hi,
>
> The only way I can get my PCMCIA network card to work on Fedora C2 is:
> 1. Ensure that the PCMCIA service starts at boot.
> 2. Log in as root.
> 3. Activate the Network Card, manually.

If you properly configure pcmcia and eth0 (or whichever) settings and
hotplug is working, your network pc card should come up automatically,
whenever the card is inserted, or if already inserted when pcmcia services
are started during boot (even if that happens after network init). But I
can only say that it is possible because it works automatically for me in
SuSE for either eth0 (wired) or wlan0 (wireless) PC cards. But I am not
familiar with Fedora

Perhaps your card does not work automatically because pcmcia does not
recognize it or what module(s) it needs, and needs to added to or
configured in something in /etc/pcmcia. You forgot to mention 2 important
details, what card is it (make/model/version and/or related output from
lspci -v) and what module does work for it?

--
David Efflandt - All spam ignored http://www.de-srv.com/

In comp.os.linux.portable Kevin D. Snodgrass <(E-Mail Removed)> wrote:
> luther wrote:
>> So the question is -
>> How can I get my PCMCIA network card to work at boot time?

> Check your /etc/modules.conf file, make sure there is a line
> similar to this:

> alias eth0 drivername

> "drivername" should be the same name you are currently using
> with modprobe.

You should NOT do this for 16-bit PCMCIA network cards.

-- Dave

Thanks for the responses.

My PCMCIA network card:
3com 3C589D-TP PCMCIA card
with IO address 0x300
with IRQ 3
using module 3c589_cs


"/sbin/lspci -v" gives:

00:00.0 Host bridge: Intel Corp. 430TX - 82439TX MTXC (rev 01)
Flags: bus master, medium devsel, latency 64

00:01.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 01)
Flags: bus master, medium devsel, latency 0

00:01.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
(prog-if 80 [Master])
Flags: bus master, medium devsel, latency 64
I/O ports at 1020 [size=16]

00:01.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
(prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 1000 [size=32]

00:01.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 01)
Flags: medium devsel, IRQ 9

00:02.0 VGA compatible controller: Chips and Technologies F65555
HiQVPro (rev a8) (prog-if 00 [VGA])
Subsystem: Compaq Computer Corporation Armada 1700 Laptop
Display Controller
Flags: stepping, medium devsel
Memory at 40000000 (32-bit, non-prefetchable)

00:0a.0 CardBus bridge: Texas Instruments PCI1220 (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device b047
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at 7fffe000 (32-bit, non-prefetchable)
Bus: primary=00, secondary=01, subordinate=04, sec-latency=176
Memory window 0: 10000000-103ff000 (prefetchable)
Memory window 1: 10400000-107ff000
I/O window 0: 00004000-000040ff
I/O window 1: 00004400-000044ff
16-bit legacy interface ports at 0001

00:0a.1 CardBus bridge: Texas Instruments PCI1220 (rev 02)
Subsystem: Compaq Computer Corporation: Unknown device b047
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at 7ffff000 (32-bit, non-prefetchable)
Bus: primary=00, secondary=05, subordinate=08, sec-latency=176
Memory window 0: 10800000-10bff000 (prefetchable)
Memory window 1: 10c00000-10fff000
I/O window 0: 00004800-000048ff
I/O window 1: 00004c00-00004cff
16-bit legacy interface ports at 0001


Hmm, lspci shows no "3c589" ??


"/etc/modules.conf" contains:
alias eth0 3c589_cs
alias usb-controller usb-uhci



"/etc/sysconfig/hwconf" contains:
....
class: NETWORK
bus: PCMCIA
detached: 120
device: eth0
driver: 3c589_cs
desc: "3Com 589 Ethernet"
network.hwaddr: 00:60:08:EC:21:FB
vendorId: 0101
deviceId: 0589
function: 0
slot: 1
....


"/etc/pcmcia/config" contains the following "3c589" entries:
....
device "3c589_cs"
class "network" module "3c589_cs"
....
card "3Com 589 Ethernet"
manfid 0x0101, 0x0589
bind "3c589_cs"
....
card "Farallon ENet"
version "Farallon", "ENet"
bind "3c589_cs"
....
card "3Com 3c562/3c563 Ethernet/Modem"
manfid 0x0101, 0x0562
bind "3c589_cs" to 0, "serial_cs" to 1

card "3Com/Megahertz 3CXEM556 Ethernet/Modem"
manfid 0x0101, 0x0035
cis "cis/3CXEM556.dat"
bind "3c589_cs" to 0, "serial_cs" to 1

card "3Com/Megahertz 3CXEM556 B-INT Ethernet/Modem"
manfid 0x0101, 0x003d
cis "cis/3CXEM556.dat"
bind "3c589_cs" to 0, "serial_cs" to 1
....
card "Motorola Marquis Ethernet/Modem"
version "Motorola MARQUIS"
bind "3c589_cs" to 0, "serial_cs" to 1
....



Is there anything else I can try?

luther wrote:

> Is there anything else I can try?

Did you say what "cardctl ident" returns?
It must match an entry in /etc/pcmcia/config
(or one of the files that config reads).

--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

At the moment "cardctl ident" gives:
open_sock(): No such device

"/etc/rc.d/init.d/pcmcia restart" gives:
Shutting down PCMCIA services: done
Starting PCMCIA services: cardmgr [2236]: No sockets found!
done



Now, ONLY when I login as root and manually start the network device
then "/sbin/cardctl ident" gives:

Socket 0:
product info: "TDK", "DF2814 DATA-FAX MODEM", "V0", "TDK Systems
Development Center"
manfid: 0x0105, 0x0101
function: 2 (serial)

Socket 1:
product info: "3Com Corporation", "3C589D", "TP/BNC LAN Card Ver.
2a", "000002"
manfid: 0x0101, 0x0589
function: 6 (network)

In comp.os.linux.portable luther <(E-Mail Removed)> wrote:

> Hmm, lspci shows no "3c589" ??

The 3c589 card is a 16-bit PCMCIA device. There's no reason why it
would show up in 'lspci', since it is not a PCI device.

> "/etc/modules.conf" contains:
> alias eth0 3c589_cs
> alias usb-controller usb-uhci

Remove the "alias eth0 3c589_cs" line.

-- Dave

In comp.os.linux.portable luther <(E-Mail Removed)> wrote:

> Now, ONLY when I login as root and manually start the network device
> then "/sbin/cardctl ident" gives:

Please define how you "manually start the network device", precisely.

-- Dave