Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
09-19-2005, 12:11 PM
|
#1
|
Member
Registered: Jul 2004
Distribution: Custom Linux, Buildroot, Busybox, Fedora, Raspberry Pi
Posts: 151
Rep:
|
eth0: TX timeout errors
I have a small embedded system with a PCMCIA Wireless Ethernet card. The plan is to get this embedded system connected to the rest of a network via an access point.
The current situation is …
1) the PCMCIA card is registered with the cardmgr, and the drivers are loaded, and an i/p address of 10.1.10.15 gets allocated to the embedded system.
2) the access point can see the PCMCIA card and gets the MAC address
3) If I try to ping the network from the embedded system I think it’s half working, in that I can see traffic on the routers and the pinged PC responds, but nothing is received back on the embedded system. Instead I get stuff like this in the log…
Sep 19 10:56:46 rhobert user.info kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 19 10:56:46 rhobert user.warn kernel: eth0: Tx timeout! ALLOCFID=0129, TXCOMPLFID=0128, EVSTAT=800b
Sep 19 10:56:46 rhobert user.debug kernel: orinoco_lock() called with hw_unavailable (dev=c1ae4800)
Sep 19 10:56:47 rhobert user.info kernel: eth0: New link status: Connected (0001)
I’ve tried looking for solutions on WWW but there is talk of devices like wlan0. I don’t have a wlan0. I think I read somewhere that it was obsolete. Should I have a wlan0 ? Because I’m building a small embedded systems I’m not using a distribution, so have had to create all the devices manually.
What I have got is…
Kernel is 2.4.31.
pcmcia-cs-2.3.7
wireless_tools.28
Any help appreciated.
Mike
|
|
|
09-19-2005, 12:34 PM
|
#2
|
Member
Registered: Jul 2004
Distribution: Custom Linux, Buildroot, Busybox, Fedora, Raspberry Pi
Posts: 151
Original Poster
Rep:
|
I think I should clarify that the Access Point is part of the main network, and not physically part of the embedded system. The embedded system just has one PCMCIA wireless card.
|
|
|
All times are GMT -5. The time now is 12:32 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|