Active Topics
 |
|
2008-10-04
, 11:15
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#82
|
Originally Posted by SKarp
Thnx skarp for the reply.. no it isn't the suggested one but in the forum somewhere someone claimed that it worked and the driver cd that came with the adapter has both pegasus and mcs7830 so i lsmod both and ya i do the echo host and usbEthUp.sh and here's the output of those:
OK, is the adapter one of the ones known to work?
If it is, but it's not an RTL8150-based adapter, did you manually run usbEthUp.sh ?
For that matter, are you using a USB adapter to put the tablet in USB Host mode, or software to set the mode manually?
Also, what do you see if you run ifconfig?
/usr/sbin # ./usbEthUp.sh
udhcpc (v0.9.9-pre) started
Sending discover...
Sending select for 192.168.0.103...
Lease of 192.168.0.103 obtained, lease time 604800
/etc/udhcpc/default.script: exec: line 7: /etc/udhcpc/default.zeroconf.dhcpup: not found
Resetting default routes
adding dns 192.168.0.1
/usr/sbin # ifconfig
eth0 Link encap:Ethernet HWaddr 00:60:6E:00:02:33
inet addr:192.168.0.103 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:107 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:14 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11257 (10.9 KiB) TX bytes:2506 (2.4 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3831 errors:0 dropped:0 overruns:0 frame:0
TX packets:3831 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:197736 (193.1 KiB) TX bytes:197736 (193.1 KiB)
/usr/sbin #
thnx again.....
|
|
2008-10-04
, 16:26
|
|
Posts: 10 |
Thanked: 4 times |
Joined on Mar 2008
|
#83
|
Starting to reach the point where I just randomly reboot things to see if it helps... <grin>
But before that, two other things to try, mostly as additional data points:
1) What does dmesg show as the chipset? Let's try just loading whichever driver is actually necessary instead of relying on what's on the CD; I've seen too many cases where driver CDs have a lot of random stuff that doesn't actually work.
2) Can you ping the tablet from one of your other machines?
But before that, two other things to try, mostly as additional data points:
1) What does dmesg show as the chipset? Let's try just loading whichever driver is actually necessary instead of relying on what's on the CD; I've seen too many cases where driver CDs have a lot of random stuff that doesn't actually work.
2) Can you ping the tablet from one of your other machines?
|
|
2008-10-05
, 15:17
|
|
Posts: 664 |
Thanked: 160 times |
Joined on Jul 2008
@ Australia
|
#84
|
Originally Posted by SKarp
Thanks SKarp for the reply, I don't know which one is actually necessary driver for the adapter I have I couldn't figure out the name model or chipset it's using by any means.. with dmesg I got huge messages so don't know what to look in that (sorry I forgot to mention that I'm linux newbie). Good thing was that after a failure, trying again after the restart kinda made my another computer able to ping my IT and vice versa so I quickly opened up the winSCP in my laptop to try if i can transfer files with it (I usually use it to transfer files between my IT and computer when I'm wireless and I don't know how else to do). It could find the host but failed to log in and trying again was a complete failure and my computer couldn't ping no more either. Everything stopped and retrying kinda brought it back but again for some moment or sometimes not even at all.. But the main thing, accessing internet, was never the part of this story.
Starting to reach the point where I just randomly reboot things to see if it helps... <grin>
But before that, two other things to try, mostly as additional data points:
1) What does dmesg show as the chipset? Let's try just loading whichever driver is actually necessary instead of relying on what's on the CD; I've seen too many cases where driver CDs have a lot of random stuff that doesn't actually work.
2) Can you ping the tablet from one of your other machines?
|
|
2008-10-05
, 18:34
|
|
Posts: 10 |
Thanked: 4 times |
Joined on Mar 2008
|
#85
|
with dmesg I got huge messages so don't know what to look in that (sorry I forgot to mention that I'm linux newbie).
1) Reboot the tablet to start with a simple configuration.
2) Do *not* modprobe anything.
3) Open your root terminal and put the tablet into USB Host mode as usual.
4) Plug in the network adapter
5) Run dmesg and look through the output for information. In my case, the relevant lines are (ignoring the numbers at the beginning of the lines):
Code:
usb 1-1: Manufacturer: ADMtek usb 1-1: device v07a6 p8511 is not supported
6) Now (again, without modprobing anything) run usbEthUp.sh and see if the network comes up.
Good thing was that after a failure, trying again after the restart kinda made my another computer able to ping my IT and vice versa so I quickly opened up the winSCP in my laptop to try if i can transfer files with it (I usually use it to transfer files between my IT and computer when I'm wireless and I don't know how else to do). It could find the host but failed to log in and trying again was a complete failure and my computer couldn't ping no more either. Everything stopped and retrying kinda brought it back but again for some moment or sometimes not even at all.. But the main thing, accessing internet, was never the part of this story.
| The Following User Says Thank You to SKarp For This Useful Post: | ||
 |
|
2008-10-05
, 18:49
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#86
|
jaeezzy, can you post photos of your adapter? Top and back would be helpful.
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
|
|
2008-10-09
, 16:25
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#87
|
Note: it looks like one of my 2 good Crystal Blue adapters may be experiencing trouble. The tablet was recognizing it earlier today, and now does not. Another possible reason to avoid them... and a clue to me to next time pack one of the reliable devices. 
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
|
|
2008-11-14
, 20:17
|
|
Posts: 12 |
Thanked: 3 times |
Joined on Oct 2008
|
#88
|
Guys,
I have bought two adapters already - one of them is the infamous blue cheap one, DM9601 based, the other one is ADMtek ADM8515 "Pegasus II".
The Pegasus II eats too much current (more than N810's 192 mA limit) so I bought a powered hub but it still does not want to work with N810 (it does work very well with a desktop computer, though - it's very fast and stable).
The blue DM9601 thingy is doing even weirder: it requires about 136 mA so N810 can bring it up alone. It is detected, DHCP assigns an IP address, I can ping back and forth, I can even ssh into N810 and play there in Midnight Commader, for example. So far so good. But as soon as the browser tries to load any webpage the whole thing gets stuck. Similarly, if I don't stop the SIP automatic connection at startup it gets stuck as well.
I don't think this is about unreliability. It actually works and gets stuck very reliably. As long as I am only pinging it works for hours... As soon as I try something else it freezes immediately.
I tried lowering the MTU from 1500 to 512 (just an idea) - didn't help.
Please would someone have a better idea? I have spent so much money on the adapters and hub already that I'd really like to get it working now. I run the most up-to-date OS on the N810 (36-5) if it matters and have the latest usblan (0.4.6) installed.
Thanks in advance!
I have bought two adapters already - one of them is the infamous blue cheap one, DM9601 based, the other one is ADMtek ADM8515 "Pegasus II".
The Pegasus II eats too much current (more than N810's 192 mA limit) so I bought a powered hub but it still does not want to work with N810 (it does work very well with a desktop computer, though - it's very fast and stable).
The blue DM9601 thingy is doing even weirder: it requires about 136 mA so N810 can bring it up alone. It is detected, DHCP assigns an IP address, I can ping back and forth, I can even ssh into N810 and play there in Midnight Commader, for example. So far so good. But as soon as the browser tries to load any webpage the whole thing gets stuck. Similarly, if I don't stop the SIP automatic connection at startup it gets stuck as well.
I don't think this is about unreliability. It actually works and gets stuck very reliably. As long as I am only pinging it works for hours... As soon as I try something else it freezes immediately.
I tried lowering the MTU from 1500 to 512 (just an idea) - didn't help.
Please would someone have a better idea? I have spent so much money on the adapters and hub already that I'd really like to get it working now. I run the most up-to-date OS on the N810 (36-5) if it matters and have the latest usblan (0.4.6) installed.
Thanks in advance!
| The Following User Says Thank You to petr For This Useful Post: | ||
|
|
2008-11-14
, 20:27
|
|
Posts: 226 |
Thanked: 47 times |
Joined on Jan 2008
@ Poland / Bialystok
|
#89
|
Petr, I've got exactly the same.
Maybe all this is due to dm9601's driver.
Everything is OK until I try to load browser.
I thought It's because of my (maybe messy) config
but then I had to flash my n810 and usb ethernet
was the first thing that I tried - unfortunately with exactly the same result.
I gave up.
Maybe all this is due to dm9601's driver.
Everything is OK until I try to load browser.
I thought It's because of my (maybe messy) config
but then I had to flash my n810 and usb ethernet
was the first thing that I tried - unfortunately with exactly the same result.
I gave up.
|
|
2008-11-14
, 21:09
|
|
Posts: 12 |
Thanked: 3 times |
Joined on Oct 2008
|
#90
|
XTC, it's not your config.
I have just googled around and happened to find a fix for a recent linux kernel where they fixed the MTU. They said that a packet larger than 1486 bytes didn't go through earlier because it overwrote the header or something. So this is one thing that is most probably wrong.
The other thing I googled up is that another guy reported that as long as the device autoconfigured to 100 Mbps it didn't work. He said he had to patch the driver to set it to 10 Mbps only and then it worked. Interesting.
Is there a source code for the usblan package somewhere? I'd like to compare the dm9601 driver source and possibly build a modified one.
I have just googled around and happened to find a fix for a recent linux kernel where they fixed the MTU. They said that a packet larger than 1486 bytes didn't go through earlier because it overwrote the header or something. So this is one thing that is most probably wrong.
The other thing I googled up is that another guy reported that as long as the device autoconfigured to 100 Mbps it didn't work. He said he had to patch the driver to set it to 10 Mbps only and then it worked. Interesting.
Is there a source code for the usblan package somewhere? I'd like to compare the dm9601 driver source and possibly build a modified one.
I can bring up my card, I get proper network settings via DHCP.
I can ping my gateway as well as webservers (like www.google.pl by their names ie. ping www.google.pl), but the browser can't connect to anything.
Funny that MyTube can search files but with no effect when trying to download them.
Skype can connect without any glitches.
E-mail nor browser - can't.
First I wondered if it's because of my possible messy config but then I've flashed (IFR after 2ssu upgrade), upgraded and installed dbus-scripts as well as usblan on completely fresh system.
All the same.
I admit - I have only one network to test my lan connection but I doubt that's the source of the problem (computers work normally in this network using dhcp).