Networking Forums

Networking Forums > Computer Networking > Linux Networking > Swapped hardware like the motherboard, but can't seem to get the onboard Marvell network to work.

Reply
Thread Tools Display Modes

Swapped hardware like the motherboard, but can't seem to get the onboard Marvell network to work.

 
 
ANTant@zimage.com
Guest
Posts: n/a

 
      12-26-2006, 07:24 AM
Yesterday, I upgraded my Debian/Linux box from a MSI KT4AV-L motherboard
(http://www.msi.com.tw/program/produc...il.php?UID=456
; disabled its onboard VIA network since I didn't trust it -- used an
Intel InBusiness 10/100 (82559) NIC) to an ASUS K8V SE Deluxe
(http://www.asus.com/products4.aspx?m...1=3&l2=14&l3=0
; onboard Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet
Controller enabled). I removed the Intel NIC to use the onboard network.

After the hardware swap and powering up, everything seems to work except
for the network. I didn't see the ethernet listed in ifocnfig. According
to dmesg, Yukon was detected: skge 1.6 addr 0xfdb00000 irq 193 chip
Yukon-Lite rev 7 and skge eth1: addr 00:11:2f:28:63:60 ... lspci showed
00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001
Gigabit Ethernet Controller (rev 13). And yes, I enabled onboard network
in my CMOS. So, I assumed this worked.

I am using Kernel v2.6.18-2 (Linux fool 2.6.18-3-k7 #1 SMP Sun Dec 10
20:17:39 UTC 2006 i686 GNU/Linux). I know the onboard network works
because I had Windos earlier for this motherboard.

Was I supposed to do something to tell Debian/Linux that the network
interface was changed? Or is it supposed to pick it up automatcially? I
put the Intel NIC back and I have network connection without any
problems. I'd like to see if I can use onboard network.

Thank you in advance.
--
"When you need a helpline for breakfast cereals, it's time to start thinking about tearing down civilization and giving the ants a go." --Chris King in A.S.R.
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 
Reply With Quote
 
 
 
 
Anton Ertl
Guest
Posts: n/a

 
      12-26-2006, 08:49 AM
(E-Mail Removed) writes:
>According
>to dmesg, Yukon was detected: skge 1.6 addr 0xfdb00000 irq 193 chip
>Yukon-Lite rev 7 and skge eth1: addr 00:11:2f:28:63:60 ...


My guess is that your networking is configured to work with eth0, not
eth1. Take a look into /etc/network/interfaces and adjust it
appropriately.

Followups set to comp.os.linux.hardware (the other groups are probably
more appropriate, but I don't read them at the moment).

- anton
--
M. Anton Ertl Some things have to be seen to be believed
(E-Mail Removed) Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html
 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Motherboard Network Interface? Pete Linux Networking 5 09-25-2007 04:44 AM
marvell yukon network 88 Nachiket Gokhale Linux Networking 2 02-28-2006 09:31 PM
Wlan with Broadcom onboard chip does not work (using ndiswrapper) Jan Krumsiek Linux Networking 1 12-11-2005 03:37 PM
Network won't work with onboard adapter!! Kees Windows Networking 0 03-29-2005 05:50 PM
Problems with OnBoard LAN driver and Acer Motherboard Christian Schmidbauer Windows Networking 1 03-26-2005 07:34 AM



1 2 3 4 5 6 7 8 9 10 11