ANTant@zimage.com 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
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html

In comp.os.linux.hardware Anton Ertl wrote:
> ANTant@zimage.com 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.

Are you saying to copy and paste the eth0 section as eth1? If Intel NIC
is not installed, wouldn't Debian/Linux use eth0 as the one? Is that why
it didn't work?
--
"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.
( )

ANTant@zimage.com writes:
>In comp.os.linux.hardware Anton Ertl wrote:
>> ANTant@zimage.com 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.
>
>Are you saying to copy and paste the eth0 section as eth1?

Worth a try. Alternatively, don't copy, just edit.

> If Intel NIC
>is not installed, wouldn't Debian/Linux use eth0 as the one?

Possibly. There might also be other things getting the eth0, e.g.,
FireWire.

> Is that why
>it didn't work?

If you only have eth0 in your interfaces file, and the port gets eth1,
then it certainly will not work.

- anton
--
M. Anton Ertl Some things have to be seen to be believed
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html

On Tue, 26 Dec 2006 04:19:43 -0600, ANTant wrote:


> Are you saying to copy and paste the eth0 section as eth1? If Intel NIC
> is not installed, wouldn't Debian/Linux use eth0 as the one? Is that why
> it didn't work?

What shows up in /etc/udev/rules.d/z25_persistent-net.rules? I'm guessing
your problem might be udev related.

Anton Ertl wrote:
> ANTant@zimage.com writes:
> >In comp.os.linux.hardware Anton Ertl wrote:
> >> ANTant@zimage.com 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.
> >
> >Are you saying to copy and paste the eth0 section as eth1?

> Worth a try. Alternatively, don't copy, just edit.

OK edit the existing one. I have never done this change in this file,
so I will just make a backup of this file in case I screw up.


> > If Intel NIC
> >is not installed, wouldn't Debian/Linux use eth0 as the one?

> Possibly. There might also be other things getting the eth0, e.g.,
> FireWire.

Even if I don't use Firewire. It is enabled, but not used. USB used
though like my UPS monitoring and USB Flash drives.


> > Is that why
> >it didn't work?

> If you only have eth0 in your interfaces file, and the port gets eth1,
> then it certainly will not work.

Yeah, I have no idea if onboard network took eth1. I didn't see it in
ifconfig when I last checked. I will have to mess around with this.
--
"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.
( )

> > Are you saying to copy and paste the eth0 section as eth1? If Intel NIC
> > is not installed, wouldn't Debian/Linux use eth0 as the one? Is that why
> > it didn't work?

> What shows up in /etc/udev/rules.d/z25_persistent-net.rules? I'm guessing
> your problem might be udev related.

This is assuming that I have and using Intel NIC for networking right
now:

$ more /etc/udev/rules.d/z25_persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules
file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 8086:1030 (e100)
SUBSYSTEM=="net", DRIVERS=="?*", SYSFS{address}=="00:d0:b7:85:0a:3f",
NAME="eth0"

# Firewire device 00e0180000827d4e (ohci1394)
SUBSYSTEM=="net", DRIVERS=="?*",
ATTRS{address}=="00:e0:18:00:00:82:7d:4e", NAME="eth1"

# PCI device 0x11ab:0x4320 (skge)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:2f:28:63:60",
NAME="eth2"


Not sure if this changes if I took the network card out. The date and
time of the file was before the hardware migration:

$ ls -all /etc/udev/rules.d/z25_persistent-net.rules
-rw-r--r-- 1 root root 583 Dec 24 08:50 /etc/udev/rules.d/z25_persistent-net.rules
--
"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.
( )

ANTant@zimage.com writes:
>Anton Ertl wrote:
>> ANTant@zimage.com writes:
>> >In comp.os.linux.hardware Anton Ertl wrote:
>> >> ANTant@zimage.com 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 ...
^^^^
>Yeah, I have no idea if onboard network took eth1.

It showed up in your dmesg output as eth1.

> I didn't see it in
>ifconfig when I last checked.

You won't see it in eth1 before you have the correct setup. What I
usually do to find out what chip got what eth number is

dmesg|grep eth

- anton
--
M. Anton Ertl Some things have to be seen to be believed
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html

On Tue, 26 Dec 2006 12:47:19 -0600, ANTant wrote:


> # PCI device 0x11ab:0x4320 (skge)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:2f:28:63:60",
> NAME="eth2"

Isn't this the nic that you are looking for? It's at eth2.


> Not sure if this changes if I took the network card out. The date and
> time of the file was before the hardware migration:

The rules are persistent. There are readmes at /usr/share/doc/udev.
If you define what you want from eth2 in /etc/network/interfaces, I'm
guessing you'll be alright.

> >> >> >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 ...
> ^^^^
> >Yeah, I have no idea if onboard network took eth1.

> It showed up in your dmesg output as eth1.

Ooh, good catch.


> > I didn't see it in
> >ifconfig when I last checked.

> You won't see it in eth1 before you have the correct setup. What I
> usually do to find out what chip got what eth number is

> dmesg|grep eth

$ dmesg |grep eth
e100: eth0: e100_probe: addr 0xfdf00000, irq 177, MAC addr
000:B7:85:0A:3F
skge eth1: addr 00:11:2f:28:63:60
eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
e100: eth0: e100_watchdog: link up, 100Mbps, half-duplex
eth0: no IPv6 routers present
bridge-eth0: enabling the bridge
bridge-eth0: up
bridge-eth0: already up
bridge-eth0: attached
e100: eth0: e100_watchdog: link down
e100: eth0: e100_watchdog: link up, 100Mbps, half-duplex

Good idea. I never done this before and usually Debian/Linux autodetects
my network easily.
--
"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.
( )

> > # PCI device 0x11ab:0x4320 (skge)
> > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:2f:28:63:60",
> > NAME="eth2"

> Isn't this the nic that you are looking for? It's at eth2.

I am more confused. Why does dmesg say eth1?

$ dmesg |grep eth
e100: eth0: e100_probe: addr 0xfdf00000, irq 177, MAC addr
000:B7:85:0A:3F
skge eth1: addr 00:11:2f:28:63:60
eth1394: eth2: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
e100: eth0: e100_watchdog: link up, 100Mbps, half-duplex
eth0: no IPv6 routers present
bridge-eth0: enabling the bridge
bridge-eth0: up
bridge-eth0: already up
bridge-eth0: attached
e100: eth0: e100_watchdog: link down
e100: eth0: e100_watchdog: link up, 100Mbps, half-duplex

It looks eth2 is the Firewire one?


> > Not sure if this changes if I took the network card out. The date and
> > time of the file was before the hardware migration:

> The rules are persistent. There are readmes at /usr/share/doc/udev.
> If you define what you want from eth2 in /etc/network/interfaces, I'm
> guessing you'll be alright.

Ah, I could change eth0 to eth1 if onboard network uses eth1. Hmm. I
will have to play with this later when I have time.

Maybe I should stick with Intel NIC since it is more reliable than
Marvell from what I heard.
--
"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.
( )