From: Jonathan Lane <jingai@shell.faradic.net>
To: debian-powerpc@lists.debian.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: 3COM 3c905c again
Date: Sun, 3 Dec 2000 19:49:39 -0500 [thread overview]
Message-ID: <200012040049.eB40ndh24760@shell.faradic.net> (raw)
Okay, I swapped cards around, and it turns out that *anything* in
PCI slots 3-6 are not correctly configured (this is on a UMAX S900).
I moved the USB card and NIC to slots 1 and 2, and my video card
to slot 4, which appears to be working (although I've not tried
using X yet, as XF86 4.0.1 is currently broken...).
However, now I am having another problem: When I ping the machine,
I see the RX light on the NIC flash, but the source machine doesn't
get any responses.
A few things to note: Every once in a while, I see the following
message:
eth1: Setting promiscuous mode.
Also, in my syslog, dhcpd complains with:
Aug 27 16:42:20 colour dhcpd-2.2.x: DHCPDISCOVER from 08:00:46:05:9c:c8 via eth1
Aug 27 16:42:20 colour dhcpd-2.2.x: no free leases on subnet 192.168.1.0
(Ignore the date, my clock had yet to be set). But this indicates that
packets *are* getting thru, as the MAC address shown above is correct.
If anyone can shed some light on this matter, I'd greatly appreciate it.
I'd also like to know why the last four PCI slots don't work properly,
although it appears it's not incredibly important now, unless X doesn't
work...
TIA,
Jonathan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-12-04 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 0:49 Jonathan Lane [this message]
2000-12-04 4:11 ` 3COM 3c905c again Tony Mantler
2000-12-04 4:54 ` Eric Reischer
2000-12-06 22:00 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2000-12-04 15:11 Jonathan Lane
2000-12-05 21:29 ` Michel Lanners
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=200012040049.eB40ndh24760@shell.faradic.net \
--to=jingai@shell.faradic.net \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).