Again : Problem with LinkSys 10/100 Etherfast Lan Card

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by Jeremy Lo » Sun, 31 Dec 1899 09:00:00



Hie there

 Really sorry that I am posting it again but you can say that I am really
desparate here and I really am :(

Recently bought a LinkSys Fast Ethernet 10/100 card. Inserted into that
system that runs on Redhat Linux 6.2 and Windows98, complete with 166MMX,
24MB and with Award Modular BIOS v4.51PG

The network card worked out fine in Windows. In Linux, I downloaded the
driver source (tulip.c and kern_compat.h), compiled it with the appropriate
option as specified in tulip.c and copied the object file tulip over to
/lib/modules/2.2.14-5.0/net/. Next changed the permissions to executable.

Next did "depmod -a" followed by "modprobe tulip.o" I was issued a :

tulip.o: init_module: Device or resource busy

I also edited /etc/lilo.conf to look like this

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt

other=/dev/hda1
 label=Windows
image=/boot/vmlinuz-2.2.14-5.0
 label=Linux
 read-only
 root=/dev/hda3
 append="ether=9,0x6000"

I issued "lilo"  and edited my /etc/conf.modules file to look like this :

alias parport_lowlevel parport_pc
alias sound-slot-0 es1370
alias eth0 tulip
options eth0 io=0x6000-0x60FF irq=11
*similar to the settings in Windows and output of "cat /proc/pci"

then restarted the system and did "dmesg | grep eth0 -" and was shown
nothing. Knowing that my LinkSys card is still not being seen by the system,
I checked by doing "lsmod" and was given :

Module                  Size  Used by
nfs                    29152   1  (autoclean)
autofs                  9476   1  (autoclean)
lockd                  31592   1  (autoclean) [nfs]
sunrpc                 53540   1  (autoclean) [nfs lockd]
nls_iso8859-1           2240   4  (autoclean)
nls_cp437               3748   4  (autoclean)
vfat                    9500   4  (autoclean)
fat                    31168   4  (autoclean) [vfat]
es1370                 22484   0
soundcore               2692   4  [es1370]

True enough, the tulip driver was not loaded. I then tried to manually load
it by doing "insmod /lib/modules/2.2.14-5.0/net tulip.o" but was given a :
tulip.o: init_module: Device or resource busy

I then did "cat /proc/pci" and got :

PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Intel 82437 (rev 2).
      Medium devsel.  Master Capable.  Latency=32.
  Bus  0, device   7, function  0:
    ISA bridge: Intel 82371FB PIIX ISA (rev 2).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  No
bursts.
  Bus  0, device   7, function  1:
    IDE interface: Intel 82371FB PIIX IDE (rev 2).
      Medium devsel.  Fast back-to-back capable.  Master Capable.
Latency=32.
      I/O at 0x3000 [0x3001].
  Bus  0, device  17, 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=32.  Min Gnt=255.Max Lat=255.
      I/O at 0x6000 [0x6001].
      Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
  Bus  0, device  19, function  0:
    Multimedia audio controller: Ensoniq AudioPCI (rev 0).
      Slow devsel.  IRQ 10.  Master Capable.  Latency=32.  Min Gnt=12.Max
Lat=128.
      I/O at 0x6100 [0x6101].
  Bus  0, device  20, function  0:
    VGA compatible controller: S3 Inc. ViRGE (rev 6).
      Medium devsel.  IRQ 9.  Master Capable.  Latency=32.  Min Gnt=4.Max
Lat=255.
      Non-prefetchable 32 bit memory at 0xe0000000 [0xe0000000].

Doing "cat /proc/interrupts" returned :

           CPU0
  0:      25561          XT-PIC  timer
  1:        454          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  4:        280          XT-PIC  serial
  8:          1          XT-PIC  rtc
 10:          0          XT-PIC  es1370
 13:          1          XT-PIC  fpu
 14:      78912          XT-PIC  ide0
 15:          5          XT-PIC  ide1
NMI:          0

Still no ethernet card. Looks like it gonna be a long and sad story :( Any
ideas ???

 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by Scott Nold » Sun, 31 Dec 1899 09:00:00



> Hie there

>  Really sorry that I am posting it again but you can say that I am really
> desparate here and I really am :(

> Recently bought a LinkSys Fast Ethernet 10/100 card. Inserted into that
> system that runs on Redhat Linux 6.2 and Windows98, complete with 166MMX,
> 24MB and with Award Modular BIOS v4.51PG

> The network card worked out fine in Windows. In Linux, I downloaded the
> driver source (tulip.c and kern_compat.h), compiled it with the appropriate
> option as specified in tulip.c and copied the object file tulip over to
> /lib/modules/2.2.14-5.0/net/. Next changed the permissions to executable.

> Next did "depmod -a" followed by "modprobe tulip.o" I was issued a :

> tulip.o: init_module: Device or resource busy

> I also edited /etc/lilo.conf to look like this

> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt

> other=/dev/hda1
>  label=Windows
> image=/boot/vmlinuz-2.2.14-5.0
>  label=Linux
>  read-only
>  root=/dev/hda3
>  append="ether=9,0x6000"

> I issued "lilo"  and edited my /etc/conf.modules file to look like this :

> alias parport_lowlevel parport_pc
> alias sound-slot-0 es1370
> alias eth0 tulip
> options eth0 io=0x6000-0x60FF irq=11
> *similar to the settings in Windows and output of "cat /proc/pci"

> then restarted the system and did "dmesg | grep eth0 -" and was shown
> nothing. Knowing that my LinkSys card is still not being seen by the system,
> I checked by doing "lsmod" and was given :

> Module                  Size  Used by
> nfs                    29152   1  (autoclean)
> autofs                  9476   1  (autoclean)
> lockd                  31592   1  (autoclean) [nfs]
> sunrpc                 53540   1  (autoclean) [nfs lockd]
> nls_iso8859-1           2240   4  (autoclean)
> nls_cp437               3748   4  (autoclean)
> vfat                    9500   4  (autoclean)
> fat                    31168   4  (autoclean) [vfat]
> es1370                 22484   0
> soundcore               2692   4  [es1370]

> True enough, the tulip driver was not loaded. I then tried to manually load
> it by doing "insmod /lib/modules/2.2.14-5.0/net tulip.o" but was given a :
> tulip.o: init_module: Device or resource busy

> I then did "cat /proc/pci" and got :

> PCI devices found:
>   Bus  0, device   0, function  0:
>     Host bridge: Intel 82437 (rev 2).
>       Medium devsel.  Master Capable.  Latency=32.
>   Bus  0, device   7, function  0:
>     ISA bridge: Intel 82371FB PIIX ISA (rev 2).
>       Medium devsel.  Fast back-to-back capable.  Master Capable.  No
> bursts.
>   Bus  0, device   7, function  1:
>     IDE interface: Intel 82371FB PIIX IDE (rev 2).
>       Medium devsel.  Fast back-to-back capable.  Master Capable.
> Latency=32.
>       I/O at 0x3000 [0x3001].
>   Bus  0, device  17, 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=32.  Min Gnt=255.Max Lat=255.
>       I/O at 0x6000 [0x6001].
>       Non-prefetchable 32 bit memory at 0xe4000000 [0xe4000000].
>   Bus  0, device  19, function  0:
>     Multimedia audio controller: Ensoniq AudioPCI (rev 0).
>       Slow devsel.  IRQ 10.  Master Capable.  Latency=32.  Min Gnt=12.Max
> Lat=128.
>       I/O at 0x6100 [0x6101].
>   Bus  0, device  20, function  0:
>     VGA compatible controller: S3 Inc. ViRGE (rev 6).
>       Medium devsel.  IRQ 9.  Master Capable.  Latency=32.  Min Gnt=4.Max
> Lat=255.
>       Non-prefetchable 32 bit memory at 0xe0000000 [0xe0000000].

> Doing "cat /proc/interrupts" returned :

>            CPU0
>   0:      25561          XT-PIC  timer
>   1:        454          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   4:        280          XT-PIC  serial
>   8:          1          XT-PIC  rtc
>  10:          0          XT-PIC  es1370
>  13:          1          XT-PIC  fpu
>  14:      78912          XT-PIC  ide0
>  15:          5          XT-PIC  ide1
> NMI:          0

> Still no ethernet card. Looks like it gonna be a long and sad story :( Any
> ideas ???

Boot in single user mode so that eth0 is not defined.  I got mine to
work just fine with the default modules in RH.

1.  Check to see if eth0 is specified before other NICs in
/etc/conf.modules (or modules.conf).
alias eth0 tulip
alias eth1 ne
options ne io=0x280 irq=9

2.  Is your linuxconf configuration conflicting with any manual
configurations you've done?

3.  Check your /etc/sysconfig/network for the following:
NETWORKING=yes
HOSTNAME="whateveryouwant.com"
GATEWAY="gatewayipaddress_here"
GATEWAYDEV="eth0"

4.  After all this... try to "ifup eth0" to see if the NIC comes up.

- Scott
--
Never do Windows again with  |  Scott M. Nolde

glaze!                       |  
12:15pm up 2 days, 17:35, 1 user, load average: 1.11, 1.04, 1.04

 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by HomerWelc » Sun, 31 Dec 1899 09:00:00



> Hie there

>  Really sorry that I am posting it again but you can say that I am really
> desparate here and I really am :(

> Recently bought a LinkSys Fast Ethernet 10/100 card. Inserted into that
> system that runs on Redhat Linux 6.2 and Windows98, complete with 166MMX,
> 24MB and with Award Modular BIOS v4.51PG

> The network card worked out fine in Windows. In Linux, I downloaded the
> driver source (tulip.c and kern_compat.h), compiled it with the appropriate
> option as specified in tulip.c and copied the object file tulip over to
> /lib/modules/2.2.14-5.0/net/. Next changed the permissions to executable.

> Next did "depmod -a" followed by "modprobe tulip.o" I was issued a :

> tulip.o: init_module: Device or resource busy

> I also edited /etc/lilo.conf to look like this

> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt

> other=/dev/hda1
>  label=Windows
> image=/boot/vmlinuz-2.2.14-5.0
>  label=Linux
>  read-only
>  root=/dev/hda3
>  append="ether=9,0x6000"

> I issued "lilo"  and edited my /etc/conf.modules file to look like this :

> alias parport_lowlevel parport_pc
> alias sound-slot-0 es1370
> alias eth0 tulip
> options eth0 io=0x6000-0x60FF irq=11
> *similar to the settings in Windows and output of "cat /proc/pci"

> then restarted the system and did "dmesg | grep eth0 -" and was shown
> nothing. Knowing that my LinkSys card is still not being seen by the system,
> I checked by doing "lsmod" and was given :

> Module                  Size  Used by
> nfs                    29152   1  (autoclean)
> autofs                  9476   1  (autoclean)
> lockd                  31592   1  (autoclean) [nfs]
> sunrpc                 53540   1  (autoclean) [nfs lockd]
> nls_iso8859-1           2240   4  (autoclean)
> nls_cp437               3748   4  (autoclean)
> vfat                    9500   4  (autoclean)
> fat                    31168   4  (autoclean) [vfat]
> es1370                 22484   0
> soundcore               2692   4  [es1370]

> True enough, the tulip driver was not loaded. I then tried to manually load
> it by doing "insmod /lib/modules/2.2.14-5.0/net tulip.o" but was given a :
> tulip.o: init_module: Device or resource busy

> I then did "cat /proc/pci" and got :

> PCI devices found:
>   Bus  0, device   0, function  0:
>     Host bridge: Intel 82437 (rev 2).
>       Medium devsel.  Master Capable.  Latency=32.
>   Bus  0, device   7, function  0:
>     ISA bridge: Intel 82371FB PIIX ISA (rev 2).
>       Medium devsel.  Fast back-to-back capable.  Master Capable.  No
> bursts.
>   Bus  0, device   7, function  1:
>     IDE interface: Intel 82371FB PIIX IDE (rev 2).
>       Medium devsel.  Fast back-to-back capable.  Master Capable.
> Latency=32.
>       I/O at 0x3000 [0x3001].
>   Bus  0, device  17, 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.

                                                    ^^^^^^^

It appears thatt your ethernet device expects IRQ 11.
Search the archives of this newsgroup.  There have been
several posts regarding this card.

--


Troy, Michigan

 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by Bit Twist » Sun, 31 Dec 1899 09:00:00


I have 4 linksys pci cards in three machines. Three cards
hooked to a Linksys Etherfast 100Base TX 4 port hub.

Running RH6.1 and Mandrake 7.0, did not have to recompile.
I did not mess with lilo.conf.

I did have to mess with the PCI settings on Bios. Could not
enter io/irq/adress and get them to work. Finaly removed
io/irqs from linuxconf and /etc/conf.modules contains

alias eth0 tulip
alias eth1 tulip

Yet, snippet from    cat /proc/pci     shows linux found them automagically.

  Bus  0, device  11, function  0:
    Ethernet controller: LiteOn LNE100TX (rev 32).
      Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master Capable.
      I/O at 0xe400 [0xe401].
      Non-prefetchable 32 bit memory at 0xe2001000 [0xe2001000].
  Bus  0, device  12, function  0:
    Ethernet controller: LiteOn LNE100TX (rev 32).
      Medium devsel.  Fast back-to-back capable.  IRQ 10.  Master Capable.
      I/O at 0xe800 [0xe801].
      Non-prefetchable 32 bit memory at 0xe2000000 [0xe2000000].

On Fri, 30 Jun 2000 15:41:03 +0800, Jeremy Low


>Hie there

> Really sorry that I am posting it again but you can say that I am really
>desparate here and I really am :(

>Recently bought a LinkSys Fast Ethernet 10/100 card. Inserted into that
>system that runs on Redhat Linux 6.2 and Windows98, complete with 166MMX,
>24MB and with Award Modular BIOS v4.51PG

--
The warranty and liability expired as you read the message.
If the above breaks your system, it's yours and you keep both pieces.
Practice safe computing. Backup the file before you change it.
Do a,  man every_command_here, before doing anything or running a script.
 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by Kevi » Sun, 31 Dec 1899 09:00:00



FYI, I have a  Linksys LNE100TX card, and until this morning was
having the same difficulty.  I read Don Becker's page on tulip,
downloaded the src.rpm, built it, installed it, and the card was
recognized.  give it a try...

http://www.scyld.com/network/updates.html#rpm

Kevin

 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by dwass.. » Sun, 31 Dec 1899 09:00:00





> FYI, I have a  Linksys LNE100TX card, and until this morning was
> having the same difficulty.  I read Don Becker's page on tulip,
> downloaded the src.rpm, built it, installed it, and the card was
> recognized.  give it a try...

> http://www.scyld.com/network/updates.html#rpm

> Kevin

I have been having problems getting the same to work on my system.  The
problem isn't recognition it is getting the card to send any packets
out.  My routing table is fine (I have checked and rechecked and had
others check it too.)

Building a new driver from source maybe something to try but doesn't
seem that it is the only solution.  Well hopefully not.

--
"Ancient weapons and hokey religions are no match for a good blaster
at your side kid." - Han Solo

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by antigo » Sun, 31 Dec 1899 09:00:00






>> FYI, I have a  Linksys LNE100TX card, and until this morning was
>> having the same difficulty.  I read Don Becker's page on tulip,
>> downloaded the src.rpm, built it, installed it, and the card was
>> recognized.  give it a try...

>> http://www.scyld.com/network/updates.html#rpm

>> Kevin

>I have been having problems getting the same to work on my system.  The
>problem isn't recognition it is getting the card to send any packets
>out.  My routing table is fine (I have checked and rechecked and had
>others check it too.)

>Building a new driver from source maybe something to try but doesn't
>seem that it is the only solution.  Well hopefully not.

I have this card and it works great with a switch but not with a hub.

Plugged into into the hub when it was set at 100TX it would flash a
few times then conk out. To get it to work on the hub
I set tulip options=9

That puts it in 10TX mode.

All the options are on the webpage mentioned in tulip.c

Mike

 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by Lorne Oickl » Sun, 31 Dec 1899 09:00:00


I have the same problem with my Intel 10/100 NIC.  It works great when I
connect it to my 10Mbs hub, although when I connect it to my 10/100 Switch,
it sets itself to 100Mbs and then it won't transfer any data.  It's just
dead, although the switch recognizes that it's working normally.  So I have
to keep it plugged into my 10Mbs hub until I find a solution.

Help...Lorne






> >> FYI, I have a  Linksys LNE100TX card, and until this morning was
> >> having the same difficulty.  I read Don Becker's page on tulip,
> >> downloaded the src.rpm, built it, installed it, and the card was
> >> recognized.  give it a try...

> >> http://www.scyld.com/network/updates.html#rpm

> >> Kevin

> >I have been having problems getting the same to work on my system.  The
> >problem isn't recognition it is getting the card to send any packets
> >out.  My routing table is fine (I have checked and rechecked and had
> >others check it too.)

> >Building a new driver from source maybe something to try but doesn't
> >seem that it is the only solution.  Well hopefully not.

> I have this card and it works great with a switch but not with a hub.

> Plugged into into the hub when it was set at 100TX it would flash a
> few times then conk out. To get it to work on the hub
> I set tulip options=9

> That puts it in 10TX mode.

> All the options are on the webpage mentioned in tulip.c

> Mike

 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by r.. » Sun, 31 Dec 1899 09:00:00


I too am having problems. I have installed the latest RPM and now at
least it recognises the card ( Although it says it is a ADK Comet
under 'dmesg', I assume ( hope ) this is because of similar chip sets ).
When I try to ping anything other then the local host, it can't find
anything and if I use 'ifconfig' it comes up with errors under TX and
RX.

When I do 'cat /proc/ioport' I get a value of
 c2824c00-c2824c7f : eth0

I initially try to set io=0x300 and irq=11. Any suggestions would be
gratefully recieved.

                  Joseph




> FYI, I have a  Linksys LNE100TX card, and until this morning was
> having the same difficulty.  I read Don Becker's page on tulip,
> downloaded the src.rpm, built it, installed it, and the card was
> recognized.  give it a try...

> http://www.scyld.com/network/updates.html#rpm

> Kevin

Sent via Deja.com http://www.deja.com/
Before you buy.
 
 
 

Again : Problem with LinkSys 10/100 Etherfast Lan Card

Post by Kevi » Sun, 31 Dec 1899 09:00:00


For pci cards, you shouldn't have to manually set the irq and io.  Just
insmod/modprobe the module, and check /proc/pci.  It should have an entry
for ethernet controller, and give some information about it, like irq.  

Then you can set the card up with ifconfig (if needed).  

Quote:>I too am having problems. I have installed the latest RPM and now at
>least it recognises the card ( Although it says it is a ADK Comet
>under 'dmesg', I assume ( hope ) this is because of similar chip sets ).
>When I try to ping anything other then the local host, it can't find
>anything and if I use 'ifconfig' it comes up with errors under TX and
>RX.

>When I do 'cat /proc/ioport' I get a value of
> c2824c00-c2824c7f : eth0

>I initially try to set io=0x300 and irq=11. Any suggestions would be
>gratefully recieved.

>                  Joseph

 
 
 

1. any help with LinkSys Etherfast 10/100 LAN Lan Card with SuSE 6.1?

Hey everyone, I've been pulling out my hair trying to get my LinkSys
LNE100TX 10/100 Etherfast Lan Card working for my SuSE 6.1 system. It's
a PCI card that costs around 26 dollars at Fry's, and I"m pretty sure it
works with Linux because it says so on the box. and on the driver disks,
it came with a tulip.c file. how do I use that? or do I use YaST? I've
also heard that I have use a DHCP client, but I'm not sure, do I have to
do a Base Network config or the DHCP client in the Yast Network setup?
thanks

am

2. How to fix Netscape's monopoly (& solve DOJ vs MS)

3. Problem with LinkSys 10/100 Etherfast Lan Card

4. Slackware bootdisk for ASUS SP3G m/b?

5. Linksys 10/100 Etherfast Lan card - problem

6. Problem with Linux 1.1.53: unable to format floppy disks

7. Linksys EtherFast 10/100 LAN Card Trouble

8. STEALTH 64 (S3864) config file NEEDED!

9. Conflict with X-Windows and Linksys EtherFast 10/100 LAN Card

10. Linksys EtherFast 10/100 LAN Card

11. Linksys EtherFast 10/100 LAN Card - Help!

12. Driver for Linksys EtherFast 10/100 LAN Card

13. LinkSys EtherFast 10/100 LAN Card not working