On Mon, Apr 12, 2004 at 06:26:33PM -0400, Nori Heikkinen wrote: | on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated: | > On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote: | > | on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated: | > [...] | > | > I haven't noticed any changes in networking, but that might be | > | > dependent on the hardware and what modules I already had configured | > | > to be loaded. | > | | > | the network error i get when i try to reconfigure my network | > | interfaces is below: | > | | > | Reconfiguring network interfaces: | > | > | cat: /var/run/dhclient.pid: No such file or directory | > | > This message results from trying to stop dhclient while it isn't | > running. No harm done. | | yeah, looked pretty innocuous ... | | > | Unrecognized kernel version | > | > This I've never seen before. | | :-P | | > | done. | > | | > | i can tell that _something's_ not recognizing my kernel version, but | > | what is it? i probably just need to grab a newer package of | > | something, but what? | > | > What is your network card? | | 02:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast | Etherlink] (rev 78)
Pretty normal. | > What driver did you use with the 2.4 kernel? | | i put in the 3c59x module for it. the same one exists with the 2.6 | kernel ... is this what you mean? never been good with hardware | configuration. Yes, that's what I mean. | > What does 'ifconfig -a' report? (is eth0 listed there?) | | with the 2.4 kernel, yes (clearly -- i'm writing from that :). | with the 2.6, also yes, but not configured: | | eth0 Link encap:Ethernet HWaddr 00:06:5B:5F:A0:30 | BROADCAST MULTICAST MTU:1500 Metric:1 | RX packets:0 errors:0 dropped:0 overruns:0 frame:0 | TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 | collisions:0 txqueuelen:1000 | RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) | Interrupt:18 Base address:0xdc80 This looks good. I thought that perhaps you had some odd NIC with a vendor-supplied binary-only driver. However, a basic 3Com should be fine. The above from 'ifconfig -a' shows that the kernel does recognize the hardware. | > What version of the dhcp-client package do you have installed? | | 2.0pl5-11 That's the one from woody. If you don't mind running a newer system, then I'd try the version from sarge or the 'dhcp3-client' package. I don't remember exactly, but I think I upgraded to dhcp3-client before I upgraded to kernel 2.6. It is conceivable that dhclient is somewhat tied to the kernel version. One way to try and isolate the error message would be to run dhclient directly (not though the ifup wrapper). Another possibility is to run ifup via strace: 'strace -f ifup eth0'. Find that error message in the output, then scroll back and see what generated it and what that program did before printing that message. (note that some familiarity with C and the POSIX APIs is necessary to really make sense of strace's output) | a friend of mine heard i was installing the 2.6 kernel, and he said | "bad idea." i asked why, and he mentioned bad driver support -- maybe | he means my ethernet card :-P I would not be surprised if the vendor-supplied binary-only driver support lags a bit. Kernel 2.6 reorganized the module system (hence the modutils -> module-init-tools change). The drivers in linus' kernel tree changed accordingly, I expect, but commercial vendors may not have caught up yet. Let's see ... yes, one of the machines I adminster has a 3c905B NIC (3c59x module) and it has had no problem with kernel 2.6 and dhcp3-client. Another machine uses the 3c509 module, and it too has worked fine. -D -- Windows, hmmm, does it come with a GUI interface that works or just pretty blue screens? www: http://dman13.dyndns.org/~dman/ jabber: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
