Re: Further on P4R800-VM and 3c59x
Andrej Prsa <[email protected]> Wed, 7 Jan 2004 19:52:50 +0100
| Newsgroups | gmane.linux.drivers.vortex.devel |
|---|---|
| Organization | Faculty of Mathematics and Physics |
| Message-ID | <[email protected]> |
Hi! > [ sorry for the late reply, yesterday was holiday in Germany... ] Good for you! I wish we had holidays as well, being only couple of hundreds of kilometers away in Slovenia! ;) > > options 3c59x debug=6 > > If you use the Scyld driver, you have to set "debug" to 31 to get all > messages... Sorry about that; the homepage says it should be set to 6 for most wordy output, but now I checked the source and I saw it should be 31. However, even after setting debug=31, I'm still getting nothing more than what I already posted. Any clue why? Could you perhaps suggest any action that should definitely produce some output to the log? While I was looking through the source, I noticed there were two entries for 3c920 card, on lines 321 and 323. Is that normal? I feel I should add here the info that comes from the motherboard booklet, just in case: Integrated 3Com 10/100 Mbps LAN MAC: Onboard is a Realtek 8201BL/CL LAN PHY that works with the integrated 3Com MAC in the IXP 200 southbridge to fully support 10BASE-T/100BASE-TX Ethernet networking. Could it be that this Realtek is causing problems? > > Thus I suspect receiving is ok, but sending doesn't work, right? > > Yes, all the data that you have sent suggest this. I have to go through > the documentation and the Tx initialization code in the driver to try to > > see what could go wrong for these cards. Given that one of the previous > posters indicated trying to use the driver distributed with the kernel > with the same results, I can concur that the problem is not related to > Tx descriptor polling. But that's about it :-( So, what can I do to help? I really want to help you help me! O:-) > > Any certain way to make sure? > > Well, "cat /proc/interrupts" :-) Sorry about that, it's so obvious! %-) Irq 3 isn't shared, it's only for eth0. > > 16:03:36 eth0: Setting promiscuous mode. > > 16:03:36 device eth0 entered promiscous mode > > 16:03:52 device eth0 left promiscous mode > > It's the result of running "tcpdump" which puts the interface into > promiscuous mode to be able to read all packets that arrive on the > cable, not only those destined to this computer. Absolutely normal. So my sweet little card should work once we get her to transmit, right? ;) Thanks, Andrej _______________________________________________ vortex mailing list [email protected] http://www.scyld.com/mailman/listinfo/vortex