Hi ,

I have install Centos 5.2 on my dell laptop.But unable to detect the ethernet.

Below are the reuire details.

$>uname -rmi
output - 2.6.18-92.e15PAE i686 i386

$>for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done

output -
09:00:0 "Ethernet controller" marvell Technology Group Ltd." "88E8040 PCI-E FastEthernet controller" -13 "dell" "unknown device 02aa"
09:00.0 0200: llab:4354 (rev 13)
0c:00:0 "network controller" "broadcom corporation" "BCM4310 USB controller" -r01 "dell" "unknown device 000c"
0c:00.0 0280: 14e4:4315 (rev 01)

Please help..

Quote:
CentOS 5.4 is the current release point level. You have installed an out-of-date release.

However all is not lost, as you should be able to get Internet connectivity via the wired card and then be able to perform an on-line update to CentOS 5.4.

The first step is to use another system and download the kABI tracking kmod-sk98lin package that is available from ELRepo.

As you are running a 32-bit system with a PAE kernel, the package you require is kmod-sk98lin-PAE-10.70.7.3-2.el5.elrepo.i686.rpm which can be found here.

Transfer that package to your laptop via some form of removable medium (USB memory stick, CD-RW, floppy disk, etc) and, as root, install it by --


Now edit your /etc/modprobe.conf file so that there is one alias line that references the eth0 device --


At this point I would recommend that you re-boot your laptop after connecting it to a wired Internet source. You should now be able to configure the system (if necessary) by running system-config-network.

Once you have a working Internet connection, please read the CentOS 5.4 Release Notes and then update your system.

Hello All,

I have been struggling with an onboard Marvell nic as well. It will never give me an IP-adress at all. I started off with the default sky2 driver, then I tried the driver from the Marvell web site for 2.6 and above kernels (driver is in this post). Then I tried the suggestions Alan gave in this topic as well as in previous topics on this subject, but to no avail... When trying the kmod-sk98lin-driver the system freezes. I can confirm the nic is working, because it ran out of the box with 32 bit Windows Vista, just yesterday.


Here are my details (using the driver from the Marvel website that was included as an attachment):
[root@localhost disk]# uname -rmi
2.6.18-164.el5 x86_64 x86_64
[root@localhost disk]# grep eth0 /etc/modprobe.conf
alias eth0 sk98lin
[root@localhost disk]# /sbin/ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:0A:48:1F:DB:11
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:225 Memory:fddfc000-0

[root@localhost disk]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:0A:48:1F:DB:11
IPV6INIT=yes
IPV6_AUTOCONF=yes
ONBOOT=yes
[root@localhost disk]# /sbin/lspci -m | grep net
02:00.0 "Ethernet controller" "Marvell Technology Group Ltd." "88E8056 PCI-E Gigabit Ethernet Controller" -r12 "Albatron Corp." "Unknown device 5621"
[root@localhost disk]# /sbin/lspci -n | grep "$(/sbin/lspci | awk '/net/ { print $1 }')"
02:00.0 0200: 11ab:4364 (rev 12)
[root@localhost disk]#
[root@localhost disk]#

Unfortunately, the casing is too small to even host an alternative nic...

Help is much appreciated

Update, I have found the system now also freezes when trying the driver from the Marvell web site.

tice17,

Have you tested the sky2 driver of the 2.6.18-164.6.1.el5 kernel?

In theory, that NIC should just work.


Looking at the kernel change log, I see the following --


If it fails, it looks as if an upstream bug report will be necessary.

Hello Alan,

No I have just finished testing it. Unfortunately using this kernel, I get the same results ...


[root@localhost ~]# uname -rmi
2.6.18-164.6.1.el5.centos.plus x86_64 x86_64

[root@localhost ~]# grep eth0 /etc/modprobe.conf
alias eth0 sky2

[root@localhost ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:0A:48:1F:DB:11
inet6 addr: fe80::20a:48ff:fe1f:db11/64 Scope:Link
UP BROADCAST RUNNING 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:209

[root@localhost ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:0A:48:1F:DB:11
IPV6INIT=yes
IPV6_AUTOCONF=yes
ONBOOT=yes

[root@localhost ~]# lspci -m | grep net
02:00.0 "Ethernet controller" "Marvell Technology Group Ltd." "88E8056 PCI-E Gigabit Ethernet Controller" -r12 "Albatron Corp." "Unknown device 5621"

[root@localhost ~]# lspci -n | grep "$(lspci | awk '/net/ { print $1 }')"
02:00.0 0200: 11ab:4364 (rev 12)

[root@localhost ~]# dmesg | grep sky2
sky2 driver version 1.22
sky2 0000:02:00.0: v1.22 addr 0xfddfc000 irq 209 Yukon-2 EC Ultra rev 2
sky2 eth0: addr ffff81012249c9a8M
sky2 eth0: enabling interface
sky2 eth0: ram buffer 0K
sky2 0000:02:00.0: error interrupt status=0x80000000
sky2 0000:02:00.0: PCI hardware error (0x2010)
sky2 0000:02:00.0: error interrupt status=0x80000000
sky2 0000:02:00.0: PCI hardware error (0x2010)
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both

Assuming that you can show that the NIC hardware is operating correctly (standalone diagnostics; boot another OS live CD; etc) then it does seem as if a bug report for the sky2 driver in kernel-2.6.18-164.6.1.el5 is necessary.

I know you have downloaded and compiled the manufacturer's supplied driver but have you tested the kABI tracking kmod-sk98lin package, as referenced, above?

Quote:
Yes, it seems like i have to file a bug. I am posting this message from the same server, now booted up with Knoppix. It ran out of the box, using the same version of the sky2 driver...( :S).

knoppix@Microknoppix:~$ dmesg | grep sky2
[ 12.996926] sky2 driver version 1.22
[ 12.996967] sky2 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 12.996975] sky2 0000:02:00.0: setting latency timer to 64
[ 12.997016] sky2 0000:02:00.0: Yukon-2 EC Ultra chip revision 2
[ 13.029122] sky2 0000:02:00.0: Marvell Yukon 88E8056 Gigabit Ethernet Controller
[ 13.029167] sky2 0000:02:00.0: irq 510 for MSI/MSI-X
[ 13.029450] sky2 eth0: addr 00:0a:48:1f:db:11
[ 38.550027] sky2 eth0: enabling interface
[ 40.236428] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
knoppix@Microknoppix:~$
Quote: