From: hjb@pro-linux.de
To: chromi@cyberspace.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: d-link dfe-530 tx (bug-report)
Date: Sun, 4 Feb 2001 12:40:41 +0100 [thread overview]
Message-ID: <200102041140.f14BefR18479@mandel.hjb.de> (raw)
In-Reply-To: <l03130328b6a2de0ec77b@[192.168.239.105]>
In-Reply-To: <l03130328b6a2de0ec77b@[192.168.239.105]>
Hi,
>This sounds every much like it's related to the problems we're having with
>the card not initialising on reboot from Windows.
>
>What's the bets we're looking at a new revision of the chip which VIA
>haven't (publically) released documentation for yet? I'd say they're
>pretty high...
I had the same problem yesterday. I don't have any Windows crap in my
network, the affected machine hasn't rebooted in a week, and my card is
not new. There may be another problem.
via-rhine.c:v1.08b-LK1.1.6 8/9/2000 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
PCI: Found IRQ 10 for device 00:0a.0
eth0: VIA VT3043 Rhine at 0xd800, 00:40:05:a4:3d:84, IRQ 10.
eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 0000.
Kernel 2.4.1-pre9. I loaded the module like this:
insmod via-rhine options=28
00:0a.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine 10/100] (rev 06)
Subsystem: Elecom Co Ltd: Unknown device 1420
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (29500ns min, 38000ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at d800 [size=128]
Region 1: Memory at de000000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at <unassigned> [disabled] [size=64K]
I wonder about the subsystem: Unknown device. It's the first time I see
this (lspci 2.1.8).
BTW why do I have to "strings /sbin/lspci" to find out its version?
Regards,
hjb
--
Pro-Linux - Germany's largest volunteer Linux support site
http://www.pro-linux.de/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 10:23 Jonathan Morton
2001-02-04 11:40 ` hjb [this message]
2001-02-04 12:14 ` Urban Widmark
2001-02-04 12:35 ` Manfred Spraul
2001-02-04 12:40 ` Urban Widmark
2001-02-04 15:39 ` Manfred
[not found] ` <Pine.LNX.4.30.0102042130100.26061-300000@cola.teststation.com>
2001-02-05 0:07 ` Thomas Stewart
2001-02-05 8:38 ` Manfred Spraul
2001-02-05 9:26 ` Urban Widmark
2001-02-05 10:41 ` Thomas Stewart
2001-02-05 10:58 ` Manfred Spraul
2001-02-05 19:41 ` Thomas Stewart
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 14:51 ksa1
2001-02-06 21:15 ` Jonathan Morton
2001-02-04 9:26 ksa1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200102041140.f14BefR18479@mandel.hjb.de \
--to=hjb@pro-linux.de \
--cc=chromi@cyberspace.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®