no internet, eth1 no receive buffer allocated

Forum: Networking
Topic: no internet, eth1 no receive buffer allocated
started by: wirechief

Posted by wirechief on Aug. 05 2007,00:14

I have tried DSL 4 and 4.2 both connect briefly to the internet then the connection is lost, both report in Dmesg that eth1 or eth0
no receive buffer allocated.
I have checked the md5sum both of download and burnt media md5sum is ok.
During bootup modprobe cannot locate block major 2 is a bootup error.
I have tried both CD's in ram on both computers same results.
my network card is RTL-8169 gigabyte Ethernet (rev 10) and
DSL 4.2 is 2.4.34.1 #2
The DSL 4.0 CD was tested and installed on a neighbors pc and it connects to the internet fine however they have a different NIC
card.
I am wondering if this might be a router/firewall conflict, I am using IPcop on a seperate linux box but it has never presented
any problems with any of my other distros unless their is a firewall on DSL that is blocking things.

Posted by wirechief on Aug. 06 2007,00:49

Quote (wirechief @ Aug. 04 2007,20:14)

I am not able to paste a lspci however it reports the card as a unknown device.

Posted by wirechief on Aug. 06 2007,01:28

Quote (wirechief @ Aug. 05 2007,20:49)

Quote (wirechief @ Aug. 04 2007,20:14)

I am not able to paste a lspci however it reports the card as a unknown device.

I found a Ethernet controller from 3com 3c905 and installed it and now I have internet access.
Apparently the RTL-8169 with the error of Unknown device 311a will not work unless someone here knows of a way to make it play. but for connecting I am good with this other Nic card now.

Posted by lucky13 on Aug. 06 2007,12:08

DSL 4.0 is NOT an official release yet. DSL is still officially at 3.4 and there is no 4.2. You're using alpha 2, not 4.2. Please post issues related to 4.0 in the existing release candidate threads per specific release candidate.

Edit: I'll address your issue when you post it here:
< http://damnsmalllinux.org/cgi-bin....6;st=10 >

Posted by wirechief on Aug. 06 2007,22:44

Quote (lucky13 @ Aug. 06 2007,08:08)

I am unable to post to the location you requested. I get a warning that I am not authorized to post there. now, what ? I have resolved the issue myself
however other users with that particular Network card will face the same thing.
Replacement of the network card was the work around.
I am still testing both the advertised 4.0 and 4.0 rc2, I can see by the kernel they are actually something else and will address any further bugs with that it might, sorry but I tried to repost it.

Posted by lucky13 on Aug. 06 2007,23:24

Quote

however other users with that particular Network card will face the same thing.

I disagree. RealTek NICs are very common (mine works using every version of DSL) and "replacement" isn't a work around.

Edit: unless there's actually something wrong with the NIC itself. BTW, there's no need to further test 4.0rc1 now that the second one is out and changes have been made -- that's why alpha2 is out.

Posted by tinker on Aug. 07 2007,18:01

wirechief,

Quote (lucky13 @ Aug. 06 2007,08:08)

[quote wirechief] I am unable to post to the location you requested. I get a warning that I am not authorized to post there. now, what ?

I think what lucky13 meant was for you to add a reply to that thread for RC4alpha2 , not try to add a new topic to that section of the forum. My guess would be that only Robert and John would be authorised to add a "new" topic there. It's the place where RC's and any problem people are having with them are discussed and the thread is specific to the RC. It's the best place to make sure Robert sees it, so he can change code if necessary for the next RC or, often, he just gives a solution if it is a mistake the poster is making. Putting your question there means those familiar with the specific RC see it and can offer specific help.

You've probably already figured this all out for yourself by now, I'll just mention it in case anyone else new to the way the forum is organised needs the hint.

As lucky13 suggests, your workaround might not even be necessary if the hardware is working, since he has one that he knows works on DSL, he can probably help you to get it working.

Posted by wirechief on Aug. 08 2007,01:07

Im still confused with the proper spot to describe the original problem.
The card in question has been used by several distros with no problem so iit seemed likely that DSL failed to successfully cofigure it. I have the very same model card on a second Desktop and it fails in the same manner with the same error and installing a older
network allows it to work too.

Posted by lucky13 on Aug. 08 2007,15:24

Quote

Im still confused with the proper spot to describe the original problem.

In the thread I linked: use the existing thread for alpha2. That's where issues related to release candidates go. In the threads that pertain to them. The developers need to know about those kinds of issues without going through every bleeping thread in the forums.

Quote

The card in question has been used by several distros with no problem

Do they use the same kernel with the same modules? Do they use the same (Knoppix) detection script?

My RealTek card is the nearly ubiquitous 8139, and it's fully supported. I haven't checked to see if there's a difference between its driver and the 8169's. I suggested the topic move to the relevant thread so it can be addressed more appropriately with respect to the development of DSL 4 -- the version you're having trouble with is a development release, not official release yet -- so any appropriate module, if it's NOT already in the kernel, may need to be added to it or made available as an extension.

Either of those can be done. THAT is the appropriate "work around," not telling people to change hardware to run DSL unless there's an actual problem with the hardware itself.

Posted by wirechief on Aug. 08 2007,21:57

I tried to report only the things that I had tried. I realize now that the thread was in the wrong place and I apoligize for that.
I just wanted it known that there was a issue with both what I thought was 4.0 and 4.2 both were unable to connect to the internet with that card.
I have used Knoppix 5.1 and even installed it to a test HD using that network card, it was in place because some distro's I had been testing would not detect or use the Nvidia network card. I should not have suggested that replacement of the card is a work around but it worked, I will have to try it again, I hate it when such a
neat program with so many nice features stumbles with my computers and it is with two different cards and two different computers. If there were some other test you would like for me to perform on it I will, I am just as curious as you on this issue.
The kernels and distros vary from knoppix, ubuntu, debian, linux mint, mepis, sidux, victorLinux, puppy, mepis x, and some others that i have not menetioned.

Posted by lucky13 on Aug. 09 2007,01:07

Quote

what I thought was 4.0 and 4.2

There is no 4.2 (yet); the current release is 3.4. Issues related to release candidates need to go in the threads reserved for them so they can be addressed.

Quote

The kernels and distros vary

Exactly. That's why it's beside the point to say something works on one but not another. Why are some things troublesome on some but not on all? Because they're different.

BTW, have you searched here yet to see if anyone else has experienced a problem with that particular NIC? Forcedeth/nforce? If so, you might try searching to see what others have done to get it working. But please make your next post related to alpha2 to the appropriate thread in "release candidates" if you want the issue handled by the time 4.0 is officially released.