Skip to contentSkip to conversation

Compaq Presario and 2.5.72

DISCUSSION Thomas Molina 2 participants 2 messages Jun 25, 2003 – Jun 29, 2003 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 11 lines · Russell King
Quoted 9 lines · Thomas Molina

The other problem was getting my pcmcia ethernet card up and operational. The change in the yenta module for the latest bk version of 72 allows it to be autoloaded by my RedHat 8.0 system as previously done. However, there is another problem. Although all the required modules get loaded -- pcmcia core, yenta socket, ds, crc32, tulip -- for some reason the dhcp client doesn't get brought up to acquire an address for the interface. It may be a problem with the RedHat scripts since running the dhclient software manually does its magic. It is a change in behaviour so I am reporting it here also.

Quoted 2 lines

Can you check whether 2.5.73 fixes it for you? If not, please re-report the problem.

The problem persisits in the latest bk pull of 2.5.73. All the modules get autoloaded, but, for some reason, the dhcp client doesn't get called. I apologize for not having a better report. I will look into it as I have time.

#2 lore raw
Quoted 13 lines · Russell King
Quoted 12 lines · Thomas Molina
Quoted 9 lines

The other problem was getting my pcmcia ethernet card up and operational. The change in the yenta module for the latest bk version of 72 allows it to be autoloaded by my RedHat 8.0 system as previously done. However, there is another problem. Although all the required modules get loaded -- pcmcia core, yenta socket, ds, crc32, tulip -- for some reason the dhcp client doesn't get brought up to acquire an address for the interface. It may be a problem with the RedHat scripts since running the dhclient software manually does its magic. It is a change in behaviour so I am reporting it here also.

Quoted 2 lines
Quoted 2 lines

Can you check whether 2.5.73 fixes it for you? If not, please re-report the problem.

Here is some additional info. I am including /var/log/messages output from the 0607 version of the kernel which works, and the 0629 (today) version of the kernel which doesn't. Note the differences in the output from /etc/hotplug/net.agent. I will attempt to look into why this is happening.

First, the working version from June 7:

Jun 29 12:16:02 lap /etc/hotplug/pci.agent: Setup tulip for PCI slot 
02:00.0
Jun 29 12:16:02 lap kernel: Linux Tulip driver version 1.1.13 (May 11, 
2002)
Jun 29 12:16:02 lap kernel: PCI: Enabling device 02:00.0 (0000 -> 0003)
Jun 29 12:16:02 lap kernel: eth0: ADMtek Comet rev 17 at 0x1800, 
00:E0:98:8E:C0:94, IRQ 9.
Jun 29 12:16:02 lap /etc/hotplug/net.agent: Bad NET invocation: $INTERFACE 
is not set
Jun 29 12:16:02 lap /etc/hotplug/net.agent: invoke ifup eth0
Jun 29 12:16:11 lap dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 
67
Jun 29 12:16:11 lap dhclient: DHCPACK from 24.35.32.1
Jun 29 12:16:11 lap dhclient: bound to 24.35.32.166 -- renewal in 494444 

seconds.

Now, the non-working version from June 29:

Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Enabling device 0000:02:00.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth0: ADMtek Comet rev 17 at 0x1800, 00:E0:98:8E:C0:94, IRQ 9.

Jun 29 12:25:00 lap /etc/hotplug/pci.agent: Setup tulip for PCI slot 
0000:02:00.0
Jun 29 12:25:00 lap kernel: Linux Tulip driver version 1.1.13 (May 11, 
2002)
Jun 29 12:25:00 lap kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 
0003)
Jun 29 12:25:00 lap kernel: eth0: ADMtek Comet rev 17 at 0x1800, 
00:E0:98:8E:C0:94, IRQ 9.
Jun 29 12:25:00 lap /etc/hotplug/net.agent: NET add event not supported