Networking Forums

Networking Forums > Computer Networking > Linux Networking > Xircom_cb missing (Fedora Core 2.4.22-1.2115nptf)

Reply
Thread Tools Display Modes

Xircom_cb missing (Fedora Core 2.4.22-1.2115nptf)

 
 
Jim Anderson
Guest
Posts: n/a

 
      06-23-2004, 06:22 PM

I've been trying in 'comp.os.linux.setup' to resolve this
problem since April and have not succeeded yet. I would
appreciate any help since my laptop is running well except
there is no networking. The problem and steps taken so far
follow.

Jim Anderson


| On Mon, 21 Jun 2004 12:54:25 +0000, Jim Anderson wrote:
|
|
|
| >>I have installed Red Hat Fedora (Fedora Core 2.4.22-1.2115.nptl)
| >>on an IBM Thinkpad 600E that has a Xircom PCMCIA ethernet card
| >>(Xircom Ethernet card: CBE2-10/100BTX). The laptop does not
| >>work with the ethernet after booting.
| >>
| >>When I boot up I get the following message in the
| >>boot window messages:
| >>Bringing up interface eth0: xircom_cb device eth0 does not
| >>seem to be present, delaying initialization. [FAILED]
| >>
| >>
|
| > This normal for the default configuration which attempts
| > to start the network service before the pcmcia service.
| >
| >
|
| >>and in the /var/log/boot.log file the PCMCIA
| >>except is: ... localhost
| >>pcmcia: Starting PCMCIA serices localhost
| >>pcmcia: cardmgr. localhost rc:
| >>Starting pcmcia: succeeded ...
| >>
| >>
|
| > See, the pcmcia service has succeeded in starting, if your pcmcia
| > ethernet card is recognized then you should be able to use it for


| > networking.
| >
| >
|
| >>If I run '/sbin/cardctl ident', I get the following:
| >>
| >>Socket 0:
| >>no product info available
| >>Socket 1:
| >>product info:
| >> "Xircom", "CardBus Ethernet II 10/100", "CBEII-10/100",
| >>"1.03" manfid: 0x0105, 0x0103
| >>function: 6(network)
| >>
| >>
|
| > The card seems to be recognized correctly, no problem here.
| >
| >
|
| >>It looks like the PCMCIA card is alive and well, but Fedora is not
| >>finding 'xircom_cb'. Can anyone help me? Do I have to make a
| >>configuration change? Or does the driver have to be installed.
| >>
| >>
|
| > Check 'cat /proc/modules.conf' without the quotes, is the xircom_cb
| > module loaded or not? If not what happens when as root you type
| > something like '/sbin/modprobe xircom_cb' without the quotes?
|
|
| The file looks like it is /proc/modules. It has the line:
|
| xircom_cb
| 9000
| 1
|
| so this part looks ok.
|
|
|
| > What does 'ifconfig eth0' show?
|
|
|
| eth0 Link encap:Ethernet HWaddr 00:10:A4:03:12:8C
| inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
| UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2
| errors:0 dropped:0 overruns:0 frame:0 TX packets:169 errors:0
| dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX
| bytes:650 (650.0 b) TX bytes:7398 (7.2 Kb) Interrupt:11 Base
| address:0x4800
|
| I compared this to the output of 'ifconfig eth0' on my desktop and it
| looks normal to this newbie eye.
|
|
|
| > What does /etc/sysconfig/network-scripts/ifcfg-eth0 look like?
|
|
| % cat ifcfg-eth0
| DEVICE=eth0
| BOOTPROTO=dhcp
| ONBOOT=yes
| TYPE=Ethernet
|
| This is right out of the box and I assume it is ok.
|
|
| Second, I tried using the document you pointed me to and I brought
| up the tool. In the tool, it looks to me like the s/w thinks the
| ethernet interface is working. I tried to ping my desktop on
| my LAN and got the following:
|
|
| PING 192.168.1.101 (192.168.1.101) 56(84) bytes of data.
| From 192.168.1.105 icmp_seq=0 Destination Host Unreachable
|
|
| You might want to review/edit the /etc/resolv.conf file and
| manually add the DNS IP address information, sample below;
|
| $ cat /etc/resolv.conf
| ; generated by /sbin/dhclient-script
| nameserver XXX.XXX.XXX.XXX
| nameserver XXX.XXX.XXX.XXX
|
| Sometimes depending on the gateway device (some NAT
| routers for example) this information is not passed to Linux
| correctly and is missing. You can get the namesever information
| from your gateway device or your desktop system.
|
| In addition you might modify
| /etc/sysconfig/network-scripts/ifcfg-eth0
| and add a line suppling the gateway's infomation (the gateway's IP
| address), sample below (based on what you have already posted);
|
| % cat ifcfg-eth0
| DEVICE=eth0
| BOOTPROTO=dhcp
| ONBOOT=yes
| TYPE=Ethernet
| GATEWAY=XXX.XXX.XXX.XXX



|| Lenard, I tried both the changes that you suggested, but they
|| don't seem to help.
||
|| First change was to /etc/resolv.conf where I added the lines:
||
|| nameserver 151.198.0.39
|| nameserver 151.197.0.39
||
|| These lines were taken from the status page of my router
|| under WAN DNS.
||
|| I also changed /etc/sysconfig/network-scripts/ifcfg-eth0
|| by adding:
||
|| GATEWAY=192.168.1.100
||
|| where the IP address is the internal LAN address of my router.
||
||
|| Jim




 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora Core 9 and atm Mathias Koerber Linux Networking 0 07-16-2008 08:39 AM
NIST Net & Fedora Core 4 J. B. Wood Linux Networking 3 03-24-2006 11:29 AM
Fedora Core 4 setup as nat Ming-Ching Tiew Linux Networking 6 03-14-2006 09:00 PM
Strange SSH halting problem between Fedora Core 2/Fedora Core 3 Jonathan Abbey Linux Networking 4 12-03-2004 05:00 PM
fedora core 2 freeze Jemy Linux Networking 2 11-12-2004 08:40 AM



1 2 3 4 5 6 7 8 9 10 11