RE: Installing LinkSys LNE100TX on Compaq Prolinea 590
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A long time ago, in a galaxy far, far way, someone said...
> It is a v4. Here is the output of cat /proc/pci:
>
> PCI devices found:
> Bus 0, device 0, function 0:
> Non-VGA device: Compaq Unknown device (rev 1).
> Vendor id=e11. Device id=1000.
> Medium devsel. IRQ 32. Master Capable. Latency=32. Min Gnt=35.
> Non-prefetchable 32 bit memory at 0x4198f0 [0x4198f0].
> Non-prefetchable 32 bit memory at 0x3127d0 [0x3127d0].
> Non-prefetchable 32 bit memory at 0x4198f0 [0x4198f0].
> Non-prefetchable 32 bit memory at 0x5ff4160 [0x5ff4160].
> I/O at 0x10000e10 [0x10000e11].
> I/O at 0xe3000144 [0xe3000147].
> Bus 0, device 10, function 0:
> VGA compatible controller: Cirrus Logic GD 5434 (rev 142).
> Fast devsel. IRQ 10.
> Non-prefetchable 32 bit memory at 0x40000000 [0x40000000].
> Bus 0, device 14, function 0:
> Ethernet controller: Unknown vendor Unknown device (rev 17).
> Vendor id=1317. Device id=985.
> Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable.
> Latency=66. Min Gnt=255.Max Lat=255.
> I/O at 0x1000 [0x1001].
> Non-pre Non-prefetchable 32 bit memory at 0x41000000 [0x41000000].
> Bus 0, device 15, function 0:
> ISA bridge: Compaq Unknown device (rev 67).
> Vendor id=e11. Device id=2.
> Medium devsel. Master Capable. No bursts.
>
> How does this output look to you? I have no idea what that first 'unknown'
> device is?
No idea. That can be worried about later once Linux installed.
> What are your thoughts?
Two thoughts:
My first thought is: you're stuck, I have to say. Your ethernet card is
new enough to be unsupported by the Debian install procedure. For various
reasons binary-only drivers don't necessarily work too well with Linux,
which is why Linksys distributed them only in source form.
That leads me to my second thought: someone can provide you with the
drivers. I have them compiled for the kernel on the boot disks, and they
work for me in my limited testing. I make no guarantees that they will
work for anyone but me. Hell, I haven't even *tried* this procedure
before - I made the drivers on a system that I already had Debian
installed on, and I don't have any way of trying out this procedure at
the moment.
The drivers are at: http://tux.creighton.edu/~pbrutsch/drivers.zip. The
The archive (in PKZip format) needs to be extracted to a MS-DOS formatted
floppy.
Start the installation procedure like normal. When it comes time to load
the device driver modules, switch to the command prompt. Then:
1) put the floppy with the driver files in the disk drive
2) do "mount -t vfat /dev/fd0 /mnt"
3) do "cp /mnt/pci-scan.o /target/lib/modules/2.2.17/net/"
4) do "cp /mnt/tulip.o /target/lib/modules/2.2.17/net/"
5) do "umount /mnt"
6) pop the floppy out of the drive
Switch back to the installation menu. You should be able to load the
tulip driver without problems.
PS: In case anyone is interested the source files themselves are at:
http://tux.creighton.edu/~pbrutsch/netdrivers.tgz
- --
- ----------------------------------------------------------------------
Phil Brutsche pbrutsch@tux.creighton.edu
GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC
GPG key id: 50DE1CFC
GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE55SlX/ZTSZFDeHPwRAiwSAJ0e0uhQDnO9YC7QZaD3eUw7i3DtxwCgjcSU
51Ev1BXIjz6NMmyobdEPq/s=
=DliD
-----END PGP SIGNATURE-----
Reply to: