|
A little more info of a more specific nature would be helpful and makes it more likely that you will get a reply.
If you change your network settings, e.g. using slackware's netconfig, you will have to load your new network settings by running the script /etc/rc.d/rc.inet1. Reboot does the same thing but then this is not windows so you don't need to reboot.
You have an operating setup with the other kernel in you laptop so comparing messages/output after/when booting respective kernels should help you identify the problem.
Run ifconfig or ifconfig eth(number of device here) if you have more than one nic installed, and/or..........
run netstat -r or route -n after booting up with each kernel to see if there is any difference in output to the terminal.
Here's what I get with route -n on my workstation connected to an IPCop firewall/gateway
root@rick:/home/rick# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 1 0 0 eth0
The above should tell you if you have a network configuration problem, but..............
I expect that if you are talking about an ethernet card and internet you are accessing the net via an adsl modem or gateway and you suspect the problem is configuring the network of your nic driver.
Try some diagnostics first
When you boot, what do you get from dmesg? You should be able to see hardware being identified. Compare the dmesg from a 2.4.26 boot and a 2.6.8.1 boot to see if your pro/100 nic is identified the same way and which module is loaded if any.
Also check in files like /var/log/syslog or /var/log/messages to see if there is anything to point you in the right direction. For example to snippet from my /varlog/messages below show that when I booted up this morning at around 05:2something show my system identifying devices at boot and doing what has to be done with them.
Oct 20 05:26:26 rick udev[1282]: creating device node '/dev/nvidia0'
Oct 20 05:26:26 rick udev[1274]: creating device node '/dev/nvidiactl'
Oct 20 05:26:26 rick kernel: uhci_hcd 0000:00:10.2: irq 11, io base 0000e000
Oct 20 05:26:26 rick kernel: uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
Oct 20 05:26:26 rick kernel: hub 4-0:1.0: USB hub found
Oct 20 05:26:26 rick kernel: hub 4-0:1.0: 2 ports detected
Oct 20 05:26:26 rick usb.agent[1397]: ... no modules for USB product 0/0/206
Oct 20 05:26:27 rick usb.agent[1443]: ... no modules for USB product 0/0/206
Oct 20 05:26:27 rick kernel: 8139too Fast Ethernet driver 0.9.27
Oct 20 05:26:27 rick kernel: eth0: RealTek RTL8139 at 0xd400, 00:02:44:84:b0:3d, IRQ 11
Oct 20 05:26:27 rick kernel: usb 2-2: new full speed USB device using address 2
Oct 20 05:26:27 rick kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 20 05:26:27 rick kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1204
If your nic isn't being recognised or the module is wrong or nonexistant there will be a message somewhere saying so
I'm not promising I can help you when you come back with something a little more specific. Maybe someone else can if I can't or maybe you'll have something you can google, but you can't fix it or get advice if you don't know the problem.
|
