[SOLVED] Slack 14.2 with Intel i211 Gigabit, No networking
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
May 23 08:54:42 hostname kernel: [ 4.942052] igb 0000:04:00.0: added PHC on eth0
May 23 08:54:42 hostname kernel: [ 4.942074] igb 0000:04:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 00:30:18:cb:53:b0
May 23 08:54:42 hostname kernel: [ 4.942084] igb 0000:04:00.0: eth0: PBA No: FFFFFF-0FF
May 23 08:54:43 hostname root: /etc/rc.d/rc.inet1: List of interfaces: 'eth0 eth1 eth2 eth3 eth4 eth5'
May 23 08:54:43 hostname root: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0
May 23 08:54:43 hostname kernel: [ 12.550863] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
The eth0 interface looks like it should be up, but I cant ping out from 192.168.0.1 to the local network, or vice versa.
After failing with the igb.ko from slack 14.2, I downloaded the latest driver from intel, built it, modprobed it, but still no luck.
Any ideas how I can troubleshoot further?
Anyone else have this adapter and has it working with the igb.ko driver? Did you need to pass in any parameters?
I'd really like to get the wired interface working. I use this device to NAT my LAN to a DSL modem/router, and run iptables and a dns server on it, so I'd prefer not to use the wifi.
It is a fresh install. I'll try upgrading the kernel and firmware. I found a newer version of the igb driver too.
I have the same NIC so when I did a fresh install of Slack 14.2 last year a few things did not work out of the box because of a newer motherboard and the stale kernel shipped with with 14.2. A "slackpkg update & slackpkg upgrade-all" fixed most issues and a compile of the latest stable kernel at the time 4.10.x made everything work great. A current kernel has the latest drivers for the NIC btw.
Pixxt: How did you use slackpkg without networking?
I manually downloaded the latest kernel packages for 14.2 from http://slackware.osuosl.org version 4.4.118 on another machine then installed them on the machine with the i211 adapter, but the network was still broken, even using the latest igb driver igb-5.3.5.18 from intel.
Built and installed the latest stable kernel 4.16.11 from kernel.org. Still no networking. Baffling.
Did the newer version of the igb driver that you found help?
Sometimes (if this is what's happening) if the wrong driver is loading first it can cause the device not to work. Running lspci -v will reveal if the igb kernel driver is in use or not.
Not sure where you would look to find all of the drivers. Only thing that comes to mind at the moment is to look under lsmod.
-::-Also recompiling the kernel can sometimes make what isn't working: work. If you feel like doing that.-::-
Ztcoracat:
The newest driver downloaded from the Intel site was 5.3.5.18. It did not help.
I currently have the latest stable kernel from kernel.org running (4.16.11). The igb.ko version built with that release is 5.4.0-k. It also didn't help.
abga:
Quote:
Can you please post the results for the following ethtool commands?
ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: off (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: no
Shouldn't it be detecting a link, as long as the cable is plugged in?
Code:
ip route show
127.0.0.0/8 dev lo scope link
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1 linkdown
Code:
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
loopback * 255.0.0.0 U 0 0 0 lo
localnet * 255.255.255.0 U 0 0 0 eth0
Quote:
Do you have any LEDs on your ethernet port - Link/Activity, are they on/blinking?
Yes there are LED's for each of 4 ports. LED behavior is weird. Sometimes when I first plug a cable in the LED for the port is yellow. But when I boot the system the LED turns off completely at some point early in the boot sequence.
I'm thinking this is bad hardware. I'm probably going to RMA this thing. Maybe I'll try to call their support number, could be a jumper is set wrong or a header is bad/not fully seated. This thing should just work.
Yes there are LED's for each of 4 ports. LED behavior is weird. Sometimes when I first plug a cable in the LED for the port is yellow. But when I boot the system the LED turns off completely at some point early in the boot sequence.
I'm thinking this is bad hardware. I'm probably going to RMA this thing. Maybe I'll try to call their support number, could be a jumper is set wrong or a header is bad/not fully seated. This thing should just work.
Well, it's just now after your reply I realized that you actually have 4 NICs:
I'll make sure that the driver register/defines all 4 ethx interfaces with distinct MACs. You might want to check the driver capabilities, maybe there are some options for multiple interfaces, run:
Code:
/sbin/modinfo igb
I'd also try to make sure which interface is which, using an udev rule to define them based on MAC might be the easiest way. Create the file:
/etc/udev/rules.d/70-persistent-net.rules
with the following content, change the ATTR{address}=="xx:xx:xx:xx:xx:xx" to reflect the real MAC:
If still failing, I'd move to the BIOS and remove any WoL settings and try to tune the NIC(s) to disable/enable autonegotiation and eventually set to work only on 100Mbit:
Code:
#first disable only the autoneg
/usr/sbin/ethtool -s eth0 autoneg off
# then set the NIC to 100Mbit
/usr/sbin/ethtool -s eth0 speed 100 duplex full autoneg off
abga:
Thanks. I should have some time to try your suggestions later today.
allend:
I don't have the device available at the moment, but I just set an ipaddress and netmask using netconfig. 192.168.0.1 and 255.255.255.0. The device is connected to the LAN via a switch. I'm trying to ping to/from a LAN on the same subnet and it fails with "network unreachable".
One other thing I just realized. My Slack 14.2 DVD is mislabeled. The side that says 64 bit is actually the 32 bit version, and vice versa. My device has a 64 bit processor and I installed a 32 bit Slackware. I'm going to install 64 bit on another SSD and see if that makes this work. A 32 bit OS should work, but it's worth a try.
One other thing I just realized. My Slack 14.2 DVD is mislabeled.
Negative.
When you boot from the Slackware DVD, the version is clearly stated. Read the messages.
If you can 64-bit Slackware then run the 64-bit version.
Only use 32-bit on systems that do not support 64-bit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.