Re: 3com905c vs Rage128: In this corner, wearing the white trunks....

1999-08-31 Thread Kent West
Kent West wrote:
 
 Joachim Trinkwitz wrote:
 
  Kent West [EMAIL PROTECTED] writes:
 
   But! Apparently the 3com905c requires a 2.0.x kernel, and won't
   work with the 2.2.x version. The Rage128 video card, not being
   supported yet by Xfree86, can only work with the frame buffer
   method, which apparently requires a 2.2.x kernel.
 
  I have many 3com905 cards working perfectly well here with 2.2.x
  kernels (with versions all the way up). Did you really try the kernel
  driver option CONFIG_VORTEX (Vortex/Boomerang support)?
 
  (Maybe I'm missing something here, I didn't see the whole thread.)
 
  Greetings,
  joachim
 
 
 It's the 3com905c that's unsupported. The '905, '905a, and '905b
 are supported. However, last night I learned that the c is
 supported in the driver available on the driver maintainer's
 page. Tomorrow when I get back in the office I'll download the
 source and recompile it and see if it works.


It worked. The 3c905.c driver available from
http://cesdis.gsfc.nasa.gov/linux/drivers/, worked with the
3c905c card. I do get a CHECKSUM ERROR when booting, but
networking still works. I'll get around to posting a question
about the error in a day or two after I've worked out a couple of
other issues.


Re: 3com905c vs Rage128: In this corner, wearing the white trunks....

1999-08-30 Thread Kent West
Joachim Trinkwitz wrote:
 
 Kent West [EMAIL PROTECTED] writes:
 
  But! Apparently the 3com905c requires a 2.0.x kernel, and won't
  work with the 2.2.x version. The Rage128 video card, not being
  supported yet by Xfree86, can only work with the frame buffer
  method, which apparently requires a 2.2.x kernel.
 
 I have many 3com905 cards working perfectly well here with 2.2.x
 kernels (with versions all the way up). Did you really try the kernel
 driver option CONFIG_VORTEX (Vortex/Boomerang support)?
 
 (Maybe I'm missing something here, I didn't see the whole thread.)
 
 Greetings,
 joachim
 

It's the 3com905c that's unsupported. The '905, '905a, and '905b
are supported. However, last night I learned that the c is
supported in the driver available on the driver maintainer's
page. Tomorrow when I get back in the office I'll download the
source and recompile it and see if it works.


Re: 3com905c vs Rage128: In this corner, wearing the white trunks....

1999-08-29 Thread Joachim Trinkwitz
Kent West [EMAIL PROTECTED] writes:

 But! Apparently the 3com905c requires a 2.0.x kernel, and won't
 work with the 2.2.x version. The Rage128 video card, not being
 supported yet by Xfree86, can only work with the frame buffer
 method, which apparently requires a 2.2.x kernel.

I have many 3com905 cards working perfectly well here with 2.2.x
kernels (with versions all the way up). Did you really try the kernel
driver option CONFIG_VORTEX (Vortex/Boomerang support)?

(Maybe I'm missing something here, I didn't see the whole thread.)

Greetings,
joachim


3com905c vs Rage128: In this corner, wearing the white trunks....

1999-08-28 Thread Kent West
Just dandy.

With the help of Heikki Vatiainen I was able to get my 3com905c
NIC working. Yea!

With the help of others on the web (names not in front of me at
the moment) I was able to get my Rage128-based video card
working. Yea!

But! Apparently the 3com905c requires a 2.0.x kernel, and won't
work with the 2.2.x version. The Rage128 video card, not being
supported yet by Xfree86, can only work with the frame buffer
method, which apparently requires a 2.2.x kernel.

You see the problem?

I can boot into a 2.0.36 system and use the network.

Or I can boot into a 2.2.9 system and use the X Window System.

But I can't use both the NIC anc X at the same time.

Bummer.

Any suggestions? (Besides swapping out hardware or waiting till
one or the other is properly supported.) I thought I could just
reapply the patched 3c905 driver code to the 2.2 kernel, but
nope. Apparently the driver has undergone quite a bit of change,
and I can't make heads or tails out of the new driver code; I
didn't understand the 2.0 code either, but Heikki gave me enough
info to muddle through and get it patched; but that info doesn't
apply to the new code.

TIA!