Re: Xircom_cb missing (Fedora Core 2.4.22-1.2115nptf)

From: Jim Anderson (ezjab_at_ieee.org)
Date: 06/22/04 

Date: Tue, 22 Jun 2004 05:00:45 GMT

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
be adding:

GATEWAY=192.168.1.100

where the IP address is the internal LAN address of my router.

Jim

Lenard wrote:
> On Mon, 21 Jun 2004 12:54:25 +0000, Jim Anderson wrote:
>
>
>
>>Hi,
>>
>>In April I post regarding this problem, and I had a follow up in May,
>>but still no success getting the ethernet interface working on my
>>laptop. I'm reposting the April post which has most of the relevant
>>information in it. Unfortunately, my other laptop is out for repairs and
>>I don't have the post from May available.
>>
>>Lenard, if you replay to this, can you please also send a reply to my
>>e-mail address and include your e-mail address. If it is ok with you I
>>would like to send any follow up questions to you. I respect that you
>>probably don't want your e-mail address posted and I will make sure it
>>does not get included on posts to the news group.
>>
>
> [ Pulling (and merging) the original thread information from Google Groups
> (to refresh both our memories about this) ];
>
>
>>>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 the 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 of the box and I assume it is ok.
>
> (and from your second posting to my reply on this....)
>
> 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
>
> [End of Google Groups pull]
>
> 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 to 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
>
>
>
>