linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Lane <jingai@shell.faradic.net>
To: debian-powerpc@lists.debian.org, jingai@shell.faradic.net,
	nicoya@apia.dhs.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 3COM 3c905c again
Date: Mon, 4 Dec 2000 10:11:06 -0500	[thread overview]
Message-ID: <200012041511.eB4FB6P19204@shell.faradic.net> (raw)


> >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.
>
>
> Check your DHCP server configuration and logfiles. It would appear your
> server doesn't want to give your client an IP address.

Actually, I think it had something to do with the date not being set, as
this went away just after I reset the clock.

> >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...
>
> I think there's some PCI bogosity in the standard 2.2 kernels when it comes
> to PCI-PCI bridges. I've had fairly good luck with 2.2 with a PCI patchset

This was the problem.  I moved the NIC to slot 2, and moved my video board
to slot 4.  Everything works fine now.  The actual problem with packets
not making it to the other machine had to do with my homemade cable (works
over 10BT, but not 100BT... probably either due to length and/or quality).

Also, if you or anyone else can ever recall the source for the PCI patch,
I'd appreciate it.  Wonder why it hasn't been rolled into the 2.2 kernels
yet, though...?

Thanks for everyone's help.  Also, just to summarize, here are the cards
I tried, just in case anyone else here attempts to add a second NIC and
runs into the same problems I did:

Netgear FA311 -- not recognized at all; link light didn't even light up.

Linksys NC100 & LNE100TX -- both seemed to function, as I was able to
   send a couple packets out, but seemed flaky; however, this was
   most likely due to my crummy cable, so I'd say give these cards a
   shot since they're significantly cheaper than the 3com...

3COM 3c905c-tx-m -- works beautifully, if you're cables don't suck :)

Regards,
Jonathan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-12-04 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-04 15:11 Jonathan Lane [this message]
2000-12-05 21:29 ` 3COM 3c905c again Michel Lanners
  -- strict thread matches above, loose matches on Subject: below --
2000-12-04  0:49 Jonathan Lane
2000-12-04  4:11 ` Tony Mantler
2000-12-04  4:54 ` Eric Reischer
2000-12-06 22:00   ` Benjamin Herrenschmidt

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=200012041511.eB4FB6P19204@shell.faradic.net \
    --to=jingai@shell.faradic.net \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=nicoya@apia.dhs.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).