Did this progress any further, by any chance ?
Sorry, that box is having issues (maybe some bad memory), haven't straightened
it out yet. :-(
Will let you know ASAP.
On Tue, Oct 14, 2003 at 10:28:11PM +0200, Geert Uytterhoeven wrote:
> On Wed, 1 Oct 2003, Nathan Ingersoll wrote:
> > I'll test it out tonight and get back to you on it.
>
> And?
On Wed, 1 Oct 2003, Nathan Ingersoll wrote:
> I'll test it out tonight and get back to you on it.
And? Any success?
> Thanks,
> Nathan
>
> On Wed, Oct 01, 2003 at 04:43:20PM +0200, Geert Uytterhoeven wrote:
> > On Wed, 1 Oct 2003, Nathan Ingersoll wrote:
> > > Not at one of those machines presen
I'll test it out tonight and get back to you on it.
Thanks,
Nathan
On Wed, Oct 01, 2003 at 04:43:20PM +0200, Geert Uytterhoeven wrote:
> On Wed, 1 Oct 2003, Nathan Ingersoll wrote:
> > Not at one of those machines presently, and I don't recall the specific
> > model
> > atm, but it uses the de4x
Not at one of those machines presently, and I don't recall the specific model
atm, but it uses the de4x5 or tulip drivers.
The fix I've seen in the past was to buffer the descriptors to 32 bytes
(cache line size?). I've had to do the same for the epic100 driver when
using it in that machine.
On W
On Wed, 1 Oct 2003, Nathan Ingersoll wrote:
> Not at one of those machines presently, and I don't recall the specific model
> atm, but it uses the de4x5 or tulip drivers.
Does this patch help?
--- linux-ppc-2.4.21/drivers/net/tulip/tulip_core.c.origFri Jun 13
18:05:48 2003
+++ linux-ppc-
On Tue, 30 Sep 2003, Zach Archer wrote:
> >Also, what ethernet card are you using? the onboard one?
>
> Yep, it's the onboard one.
What type is the onboard?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [E
Did you build your own kernel? If so, which version? You might need a
small patch for that driver to work correctly.
On Tue, Sep 30, 2003 at 11:12:32PM -0700, Zach Archer wrote:
> >The 6500 has some quirks, I've got a couple of the 250 MHz model, and
> >have had plenty of annoyance dealing with th
The 6500 has some quirks, I've got a couple of the 250 MHz model, and
have had plenty of annoyance dealing with these issues. Just to be sure,
if you do "ifdown eth0" then "ifup eth0", does it re-enable the
ethernet?
Thanks, in fact if the computer's network has hung, then the command
"ifdown e
On Tue, Sep 30, 2003 at 09:17:14PM -0700, Zach Archer wrote:
> Hi. I just installed Debian Woody on my PowerPC 6500/225. After the
> initial shock, everything seems to be working and I've even set up
> SSH accounts for my friends, and am hosting a webserver... Just like
> a real system admin!!!
At 9:33 PM -0700 9/30/03, Chris Tillman wrote:
But it's quite likely
there could be some oxidation on the 6500's connector pins. This
might be helped by simply plugging and unplugging the cable, say
100 times, to rub through the oxidation layer.
Hmm well I'll give it a shot.
Related question:
On Tue, Sep 30, 2003 at 09:17:14PM -0700, Zach Archer wrote:
> Hi. I just installed Debian Woody on my PowerPC 6500/225. After the
> initial shock, everything seems to be working and I've even set up
> SSH accounts for my friends, and am hosting a webserver... Just like
> a real system admin!!!
Hi. I just installed Debian Woody on my PowerPC 6500/225. After the
initial shock, everything seems to be working and I've even set up
SSH accounts for my friends, and am hosting a webserver... Just like
a real system admin!!! Woo, Yay for me
A little about the setup: I have DSL, connected to
13 matches
Mail list logo