Putting back the old router completely solves the problem. I've performed some tests and it seems it just happens with the Alix. More, on the first ethernet port of the router, the Alix doesn't even respond to pings, even if the light shows it's "up and running at 100 Mbits". The only (big) difference between the old router (Linksys WRT54GL with dd-wrt) and the new one (with dd-wrt, tomato or the stock firmware) is the 1 Gbit ethernet capability. Is it possible that there are some problems between NetBSD, the Alix network chipset and the 1 Gbit integrated switch of the Cisco?
Here's my dmesg:
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 5.1_STABLE (GEODE_DRAGAS) #1: Mon Apr 4 18:13:21 UTC 2011
ro...@netbsd.dragas.org:/usr/obj/sys/arch/i386/compile/GEODE_DRAGAS
total memory = 255 MB
avail memory = 245 MB
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
Generic PC
mainbus0 (root)
cpu0 at mainbus0: AMD 586-class, 498MHz, id 0x5a2
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 1 function 0
pchb0: vendor 0x1022 product 0x2080 (rev. 0x33)
glxsb0 at pci0 dev 1 function 2: RNG AES
vr0 at pci0 dev 9 function 0: VIA VT6105M (Rhine III) 10/100 Ethernet
vr0: interrupting at irq 10
vr0: Ethernet address: 00:0d:b9:1e:4a:c4
OUI 0x0002c6 model 0x0034 rev 3 at vr0 phy 1 not configured
vr1 at pci0 dev 10 function 0: VIA VT6105M (Rhine III) 10/100 Ethernet
vr1: interrupting at irq 11
vr1: Ethernet address: 00:0d:b9:1e:4a:c5
OUI 0x0002c6 model 0x0034 rev 3 at vr1 phy 1 not configured
vr2 at pci0 dev 11 function 0: VIA VT6105M (Rhine III) 10/100 Ethernet
vr2: interrupting at irq 15
vr2: Ethernet address: 00:0d:b9:1e:4a:c6
OUI 0x0002c6 model 0x0034 rev 3 at vr2 phy 1 not configured
gcscpcib0 at pci0 dev 15 function 0
gcscpcib0: vendor 0x1022 product 0x2090 (rev. 0x03)
timecounter: Timecounter "gcscpcib0" frequency 3579545 Hz quality 1000
gcscpcib0: Watchdog Timer via MFGPT0, GPIO
gpio0 at gcscpcib0: 32 pins
viaide0 at pci0 dev 15 function 2
viaide0: Advanced Micro Devices CS5536 IDE Controller (rev. 0x01)
viaide0: bus-master DMA support present
viaide0: primary channel wired to compatibility mode
viaide0: primary channel interrupting at irq 14
atabus0 at viaide0 channel 0
viaide0: secondary channel wired to compatibility mode
viaide0: secondary channel ignored (disabled)
ohci0 at pci0 dev 15 function 4: vendor 0x1022 product 0x2094 (rev. 0x02)
ohci0: interrupting at irq 12
ohci0: OHCI version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
gcscehci0 at pci0 dev 15 function 5: vendor 0x1022 product 0x2095 (rev. 0x02)
gcscehci0: interrupting at irq 12
gcscehci0: EHCI version 1.0
gcscehci0: companion controller, 4 ports each: ohci0
usb1 at gcscehci0: USB revision 2.0
isa0 at gcscpcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com0: console
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
attimer0 at isa0 port 0x40-0x43: AT Timer
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff
npx0: reported by CPUID; using exception 16
attimer0: attached to pcppi0
isapnp0: no ISA Plug 'n Play devices found
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
uhub0 at usb0: vendor 0x1022 OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
uhub1 at usb1: vendor 0x1022 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub1: 4 ports with 4 removable, self powered
[...]
No interesting messages can be seen, like timeouts or so.
Any idea?
Stefano
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
that does sound like auto-negotiate wierdness ... I don't know whether
it's related, however I have a Cisco for which my Asus 1000H ale0
doesn't come up properly and I have to manually set it to 10MB/s (!!)
before I get anything to work. My wife's netbook is the same model and
she has no problems with it at all - she is running Windows though, so
it may be a NetBSD driver issue ...
but try manually setting the link speed on your alix, then try
explicitly setting something on the Cisco and see if that helps ...
--
Malcolm Herbert This brain intentionally
mj...@mjch.net left blank
Actually, it might me as you say. Look at my ifconfig:
vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:0d:b9:1e:4a:c4
media: Ethernet none (none)
inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
inet6 fe80::20d:b9ff:fe1e:4ac4%vr0 prefixlen 64 scopeid 0x1
"media: Ethernet none (none)" ?
I will try to force other values. Let's see.
Stefano
Solved. I had forgotten (months ago) to compile the ukphy support. With a 100Mbit switch I had no problems but it seems that with a faster one, it was confused.
Now it seems to be ok.
Thank you for pointing me in the right direction.
Stefano
That usually means there is no cable connected.
What PHY does NetBSD detect for this interface? Please look for lines
like this in "dmesg":
brgphy0 at bge0 phy 1: BCM5750 1000BASE-T media interface, rev. 0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
It will of course mention "vr0" in your case.
Kind regards
--
Matthias Scheler http://zhadum.org.uk/
Thank you. As I posted some minutes ago, I didn't compile the phy support. It was working without problems when connected to a 100Mbit switch, but got "confused" with the new router, even if the Alix has a 100Mbit interface.
Anyway, after compiling the phy support, everything is working perfectly.
Stefano
You said you compiled in ukphy(4) now. But ukphy(4) is only the last resort.
I would try a GENERIC to check whether there is a better PHY driver for
your hardware.
Kind regards
--
Matthias Scheler http://zhadum.org.uk/
--
> You said you compiled in ukphy(4) now. But ukphy(4) is only the last resort.
> I would try a GENERIC to check whether there is a better PHY driver for
> your hardware.
Yes, I've compiled ukphy(4) because the GENERIC kernel says it's the one it can use. So I don't think there's a more specific one for my hardware (Via Rhine III)
Stefano
I don't know what's up with Cisco lately, but apparently they've decided it's
an OK idea to dilute their own brand by slapping the Cisco-name on products
that are barely worthy of being called Linksys.
I have an Cisco EPC3925 cable modem with built-in router and 4-point switch,
and from the looks of it there is some shared platform hiding underneath.
I recognise your problems, along with a few others (like ipv6 neighbourhood
discovery being broken). The EPC3925 has a known issue with autonegotiation,
if a device negotiates at 100 mbit that port becomes unreliable. Since I
can't easily replace the cable modem, I ended up installing a second switch
behind the Cisco modem. This fixed some (but not all!) of my problems with
this router.
Martijn
--
Martijn van Buul - pi...@dohd.org
Yes, ukphy(4) was the best I found to use when I was experimenting with
the same PC Engines ALIX board.
FYI to anyone else looking at this, the PHY in my tests identified as:
OUI 0x0002c6, model 0x0034, erv. 3
--
Greg A. Woods
Planix, Inc.