maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   Nokia N900 + Ethernet (via USB-RJ45 adapter) (https://talk.maemo.org/showthread.php?t=65839)

s4br0s0 2010-11-18 15:54

Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I search but not find this (maybe don't look well), anyway.

Here the video.

Nokia N900 + Ethernet (via USB-RJ45 adapter)

Grettings.

hellnick 2010-11-18 18:58

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
This looks handy, almost like having a Fluke of my very own

bakuur 2010-11-18 19:05

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
looks just simply amazing!

casper27 2010-11-18 19:10

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by s4br0s0 (Post 877169)
I search but not find this (maybe don't look well), anyway.

Here the video.

Nokia N900 + Ethernet (via USB-RJ45 adapter)

Grettings.

Looks cool things are really taking off with hostmode. Wonder who will be first to get DVB-T working now that would be cool.

cauliflower 2010-11-19 04:52

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Do you have course? if you have it,could you give me or write down on the website.

NiQ 2011-02-15 03:36

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Excuse me for bumping this but does the kernel include the necessary drivers for USB-RJ45 adapters or do I need to compile my own driver?

Sonny_Jim 2011-02-15 16:02

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Depends on the make/model of the USB Ethernet adapter. Some (like the Belkin Gigabit I have) have the necessary drivers already in the kernel, some don't. I'm not sure of a 'compatibility list' anywhere, unfortunately.

http://talk.maemo.org/showthread.php...941#post883941

blue_led 2011-02-15 17:43

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Report to work ok .
I tried myself but some settings must be done manually ( @ dhcp ) .
http://www.gmb.nl/default.aspx?op=pr...2=item&id=5027
this have ASIX chipset and driver is included in powerkernel46

ZenGuru 2011-03-16 16:47

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Just one more ok! report :)

Working out-of-the-box
http://www.edimax.com/en/support_det...id=5&pl2_id=26

Thank you all for making this possible. I know some of you were working hard...no point in naming you all, list would be too big.

Don't know what else to say other than RESPECT!

hardkorek 2011-03-17 06:42

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I had a problem with USB NIC before.

I have created wiki: http://wiki.maemo.org/N900_Hardware_...tibile_devices

Please submit your USB NIC status there.

teh 2011-03-17 13:07

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I'll tell you something other than that is really cool... loading of webpages is much faster using USB ethernet...

ZenGuru 2011-03-17 15:28

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by hardkorek (Post 969443)
I had a problem with USB NIC before.

I have created wiki: http://wiki.maemo.org/N900_Hardware_...tibile_devices

Please submit your USB NIC status there.

Done it, thx

cheve 2011-03-17 15:32

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
In case someone is interested, here is a post listing some ASIX chipset USB adapter:

http://www.wodejukebox.org/viewtopic...=2633&start=90

Cheers,

teemui 2011-03-17 16:12

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I tested my alink usb-eth adapter heres what i get, could this work?

Code:

Nokia-N900:~# dmesg | grep usb
[71585.875213] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[71642.198913] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[71647.117828] usb 1-1: USB disconnect, address 6
[71647.117828] usb 1-1: unregistering device
[71647.117858] usb 1-1: usb_disable_device nuking all URBs
[71647.117889] musb_hdrc musb_hdrc: shutdown urb c543ce80 ep1in-intr
[71647.117950] musb_hdrc musb_hdrc: shutdown urb cd36c400 ep2in-bulk
[71647.117950] musb_hdrc musb_hdrc: shutdown urb cd36cd80 ep2in-bulk
[71647.117980] musb_hdrc musb_hdrc: shutdown urb cd36cc80 ep2in-bulk
[71647.118011] musb_hdrc musb_hdrc: shutdown urb cd36cb80 ep2in-bulk
[71647.118011] musb_hdrc musb_hdrc: shutdown urb cd36c800 ep2in-bulk
[71647.118041] musb_hdrc musb_hdrc: shutdown urb cd36c480 ep2in-bulk
[71647.118041] musb_hdrc musb_hdrc: shutdown urb cd36c280 ep2in-bulk
[71647.118072] musb_hdrc musb_hdrc: shutdown urb c5609c00 ep2in-bulk
[71647.118103] musb_hdrc musb_hdrc: shutdown urb c93ee880 ep2in-bulk
[71647.118103] musb_hdrc musb_hdrc: shutdown urb c93eef00 ep2in-bulk
[71647.118133] musb_hdrc musb_hdrc: shutdown urb c93ee500 ep2in-bulk
[71647.118133] musb_hdrc musb_hdrc: shutdown urb c93ee900 ep2in-bulk
[71647.118164] musb_hdrc musb_hdrc: shutdown urb c93ee580 ep2in-bulk
[71647.118194] musb_hdrc musb_hdrc: shutdown urb c741e900 ep2in-bulk
[71647.118194] musb_hdrc musb_hdrc: shutdown urb c741ef80 ep2in-bulk
[71647.118225] musb_hdrc musb_hdrc: shutdown urb ce68c280 ep2in-bulk
[71647.118255] musb_hdrc musb_hdrc: shutdown urb c9564f00 ep2in-bulk
[71647.118255] musb_hdrc musb_hdrc: shutdown urb c758b880 ep2in-bulk
[71647.118286] musb_hdrc musb_hdrc: shutdown urb cfc3f880 ep2in-bulk
[71647.118286] musb_hdrc musb_hdrc: shutdown urb cf3e9000 ep2in-bulk
[71647.118316] musb_hdrc musb_hdrc: shutdown urb cf3e9800 ep2in-bulk
[71647.118347] musb_hdrc musb_hdrc: shutdown urb cf3e9700 ep2in-bulk
[71647.118347] musb_hdrc musb_hdrc: shutdown urb cf3e9600 ep2in-bulk
[71647.118377] musb_hdrc musb_hdrc: shutdown urb cf3e9f00 ep2in-bulk
[71647.118377] musb_hdrc musb_hdrc: shutdown urb cf3e9300 ep2in-bulk
[71647.118408] musb_hdrc musb_hdrc: shutdown urb cf3e9d00 ep2in-bulk
[71647.118438] musb_hdrc musb_hdrc: shutdown urb cd190400 ep2in-bulk
[71647.118438] musb_hdrc musb_hdrc: shutdown urb ce4e2580 ep2in-bulk
[71647.118469] musb_hdrc musb_hdrc: shutdown urb ce4e2780 ep2in-bulk
[71647.118469] musb_hdrc musb_hdrc: shutdown urb ce4e2700 ep2in-bulk
[71647.118499] musb_hdrc musb_hdrc: shutdown urb ce4e2a80 ep2in-bulk
[71647.118530] musb_hdrc musb_hdrc: shutdown urb c7560280 ep2in-bulk
[71647.118530] musb_hdrc musb_hdrc: shutdown urb c7560780 ep2in-bulk
[71647.118560] musb_hdrc musb_hdrc: shutdown urb cbcd4380 ep2in-bulk
[71647.118560] musb_hdrc musb_hdrc: shutdown urb cbcd4200 ep2in-bulk
[71647.118591] musb_hdrc musb_hdrc: shutdown urb cbcd4700 ep2in-bulk
[71647.118621] musb_hdrc musb_hdrc: shutdown urb cbcd4f00 ep2in-bulk
[71647.118621] musb_hdrc musb_hdrc: shutdown urb cbcd4600 ep2in-bulk
[71647.118652] musb_hdrc musb_hdrc: shutdown urb cfcd0380 ep2in-bulk
[71647.118682] musb_hdrc musb_hdrc: shutdown urb c7724900 ep2in-bulk
[71647.118682] musb_hdrc musb_hdrc: shutdown urb c7724100 ep2in-bulk
[71647.118713] musb_hdrc musb_hdrc: shutdown urb cfe28180 ep2in-bulk
[71647.118713] musb_hdrc musb_hdrc: shutdown urb c94bad00 ep2in-bulk
[71647.118743] musb_hdrc musb_hdrc: shutdown urb c948e800 ep2in-bulk
[71647.119018] usb 1-1: unregistering interface 1-1:1.0
[71647.119934] eth0: unregister 'asix' usb-musb_hdrc-1, ASIX AX88178 USB 2.0 Ethernet
[71647.212799] usb 1-1:1.0: uevent
[71647.213500] usb 1-1: uevent
[71647.493560] usb 1-1: new high speed USB device using musb_hdrc and address 7
[71647.649169] usb 1-1: default language 0x0409
[71647.656799] usb 1-1: uevent
[71647.657012] usb 1-1: usb_probe_device
[71647.657043] usb 1-1: configuration #1 chosen from 1 choice
[71647.661041] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[71647.661376] usb 1-1:1.0: uevent
[71647.662200] asix 1-1:1.0: usb_probe_interface
[71647.662231] asix 1-1:1.0: usb_probe_interface - got id
[71648.450134] eth0: register 'asix' at usb-musb_hdrc-1, ASIX AX88178 USB 2.0 Ethernet, 00:1a:9f:0b:0e:d5
[71648.450256] /home/r00t/MyDocs/kernel-power-2.6.28-power46-wl1/drivers/usb/core/inode.c: creating file '007'
[71648.451110] usb 1-1: New USB device found, idVendor=0b95, idProduct=1780
[71648.451141] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[71648.451202] usb 1-1: Product: AX88178
[71648.451202] usb 1-1: Manufacturer: ASIX Elec. Corp.
[71648.451232] usb 1-1: SerialNumber: 0B0ED5

when i try udhcpc it says

Code:

Nokia-N900:~# udhcpc
udhcpc (v0.9.9-pre) started
Sending discover...
Sending discover...
Sending discover...
Sending discover...
Lease failed:
zeroconf: address selected is 169.254.27.182
zeroconf: state is Active/Announce, Link-local address 169.254.27.182
bogus packet, option fields too long: Read past the packet length when getting option 0x1 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x2 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x3 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x4 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x5 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x6 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x7 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x8 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x9 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0xc (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0xd (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0xf (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x10 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x11 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x17 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x1a (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x1c (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x28 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x29 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x2a (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x2c (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x32 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x33 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x35 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x36 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x38 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x42 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x43 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0xfc (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x34 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x1 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x2 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x3 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x4 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x5 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x6 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x7 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x8 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x9 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0xc (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0xd (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0xf (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x10 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x11 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x17 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x1a (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x1c (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x28 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x29 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x2a (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x2c (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x32 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x33 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x35 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x36 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x38 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x42 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0x43 (308 >= 308)
bogus packet, option fields too long: Read past the packet length when getting option 0xfc (308 >= 308)
/etc/udhcpc/default.script: exec: line 7: /etc/udhcpc/default.zeroconf: not found


chill 2013-10-07 07:22

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by hardkorek (Post 969443)
I had a problem with USB NIC before.

I have created wiki: http://wiki.maemo.org/N900_Hardware_...tibile_devices

Please submit your USB NIC status there.

Would anybody care to update the list and/or share their experiences? There's a lot of USB-ethernet adapters out there, and beyond the US$30 Belkin one, I wouldn't know where else to go.

chill 2014-07-14 01:48

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I got this one:
http://trendnet.com/products/proddet...=280_TU2-ET100

It works "out of the box" (note my N900 setup in my signature, though). However:

a) on one network, I got the same "bogus packet" messages with udhcpc.

b) on another network, it works fine at first, but it seems that after a while the web browsers (microb and Opera) "forget" that they are connected, and never download the requested page; ping and wget from XTerminal still work. Also, turning on the online accounts in My Availability causes the N900 to connect to the default network (3G); this is even before the web browser problem sets in.

c) power consumption: the dongle runs pretty warm (though it can still be held) and will drain a full N900 battery in roughly an hour. The declared consumption is 178 mA.

chill 2014-07-24 06:43

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
After more usage and seeing a report about current draw here (though that was clearly for Trendnet's previous model), I decided to send it back.

I am instead getting this. Knock on wood.

biketool 2014-07-24 07:02

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I tried to get this working a few years ago, the need has past though though it would be nice to have the capacity when faced with a school or corporate network.
Post your how-to for N900 on the wiki page so others can try to replicate your success.

chill 2014-07-24 07:16

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Ok, issue a) will hopefully be resolved with the new device. Note it has the same chipset as Trendnet's.

Issue b) was caused by the local network not having a DHCP server, so who knows where I was getting the DHCP packets from, and what was in them. I tried on a third LAN then, and it worked, except again I had issues a) and b).

Issue c) remains elusive. It seems here that Maemo applications dislike usb ethernet, so I am thinking of installing a dummy network as suggested there. Indeed, it seems like that would completely convince Maemo that I am connected to a network. Never done that, though. Tips, please?

@biketool, yeah, I don't really need need it, but there is a coolness/nerdiness factor involved. Also, once you do need it, it will be too late to try to make it work.

Quote:

Originally Posted by chill (Post 1432661)
I got this one:
http://trendnet.com/products/proddet...=280_TU2-ET100

It works "out of the box" (note my N900 setup in my signature, though). However:

a) on one network, I got the same "bogus packet" messages with udhcpc.

b) on another network, it works fine at first, but it seems that after a while the web browsers (microb and Opera) "forget" that they are connected, and never download the requested page; ping and wget from XTerminal still work. Also, turning on the online accounts in My Availability causes the N900 to connect to the default network (3G); this is even before the web browser problem sets in.

c) power consumption: the dongle runs pretty warm (though it can still be held) and will drain a full N900 battery in roughly an hour. The declared consumption is 178 mA.


chill 2014-07-28 23:32

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Update: I've received the Plugable USB 2.0 to Ethernet adapter. Note it has the same AX88772 chipset as the Trendnet adapter I had sent back.

The good news is that my N900 was able to recognize it and connect to the LAN. Also good is that it does not feel as hot as the Trendnet; note the Plugable has a larger plastic case.

Unfortunately, the battery again drains in an hour, even if the N900 is left alone. I am considering several options:

a) when not in use, disconnect the adapter from USB mode. However, this does not solve the problem of being unable to use the LAN for an hour at a time.

b) the chipset has a suspend mode. However, I do not know how to utilize it.

c) get a powered USB hub. Since we are connecting to the wall (RJ45) anyway, there is sure to be a wall socket nearby. Also, this has the additional advantage of powering other USB devices (mouse, keyboard). I'm not sure if it would allow for charging of the N900 as well ("USB host mode with charging" in USB mode). The disadvantage is that it's more cost and bulk.

Also good is that I got it to work so that Maemo applications (such as the web browser, HAM, online accounts) now believe they are connected and no longer try to connect to 3G. I installed a dummy/null network (here is the link again). Note that I installed the null (not dummy) network, because only the lib for the dummy is in the repository. Also, the Dummy Network did not show after installing the lib (and rebooting), so I had to use the gconftool command line. The connection manager now shows a Dummy Network. I can connect to Dummy Network before or after connecting to the LAN (with udchpc), as long as it's before any Maemo applications are run.

biketool 2014-07-29 11:05

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Just a thought, I remember having a great 10baseT low power CF ethernet card good for several hours at least for my Linux Zaurus PDA. Since we cant really expect much more than 10Mb/S from our N900s maybe there is a lower power 10baseT USB NIC?

chill 2014-07-30 08:53

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by biketool (Post 1434184)
Just a thought, I remember having a great 10baseT low power CF ethernet card good for several hours at least for my Linux Zaurus PDA. Since we cant really expect much more than 10Mb/S from our N900s maybe there is a lower power 10baseT USB NIC?

Right, but that assumes the culprit is the device or the chipset. So, if it drains the N900 ~1500 mAh battery in an hour, it will probably drain a bigger phone battery in two hours (from full), assuming the non-USB consuption are about the same on both phones. A laptop would likewise be drained quickly. Now, assuming laptops (for sure) and tablets and phones (probably) are target market for these devices; does the maker actually expect the adapters to sell?

Looking around the web, I don't see any reviews mentioning power consumption being a problem, or evaluating it in any depth. So we still don't know what exactly is causing the drain; since that's the case, it's more difficult to begin to solve it.

But yeah, one way to see if it's really the adapter that's to blame is to try a different adapter. Note that's what I did with Plugable vs. Trendent. But ordering and returning can only be done so many times. Ok, I'll see if I can try a third device, this time an older one.

biketool 2014-07-30 09:35

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
RasberryPi owners are surely conscious of power consumption, that might produce some leads.

chill 2014-07-30 09:56

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by biketool (Post 1434290)
RasberryPi owners are surely conscious of power consumption, that might produce some leads.

Right, I have been searching through their discussion forums. Also there is http://elinux.org/RPi_USB_Ethernet_adapters

Note that consumption/drain data is relatively sketchy. It either works with a powered USB hub or it doesn't. E.g. they list my former Trendnet TU2-ET100 as working out of the box, but don't say for how long.

zerox 2014-07-30 13:13

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
@chill

Perhaps you could obtain power from the ethernet cable via a POE device, e.g. this one on Amazon

chill 2014-07-30 21:12

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by zerox (Post 1434298)
@chill

Perhaps you could obtain power from the ethernet cable via a POE device, e.g. this one on Amazon

It doesn't look like that particular cable would work, because it has a barrel connector at the other end, and the N900 doesn't have a socket for it.

But let's think about PoE as an idea. Power would come from the Ethernet (PoE) for the N900 (note that USB-Ethernet adapters cannot be powered, or none that I know can). The N900 would then simultaneously power the USB-Ethernet adapter. The problem is, how do you make it so that both the USB-Ethernet adapter and the power cable (coming from the PoE) are plugged into the N900?

zerox 2014-07-30 22:46

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
One possible solution would be to use the POE device to power a hub, to which both the ethernet adaptor and the N900 would be connected.

chill 2014-07-31 00:04

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I see. That's correct, but then you are looking at buying and maintaining three devices: PoE, USBEthernet adapter and USB hub. Given that the area where the N900 is deployed can be expected to have a wall socket (unlike where PoE is intended), this is probably not the best solution. A powered USB hub and USBEthernet adapter seems more reasonable.

chill 2014-07-31 21:56

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
So if we're looking to reduce the number of devices to just one, we want a USB-Eth adapter that is externally powered. There aren't that many of them out there. There are a few brands carrying this one but the reviews complain about the quality of the plastic. Also, there is this one. Compatibility should be ok, because it is based on the Asix AX88760 chip, which Asix's web site says uses the same driver as the AX88772 (which the N900 with power kernel recognizes, as shown by my usage of the Trendnet and Plugable adapters). However, Syba says it will 1) only operate when the external power is on and 2) it will not charge the host (N900). Ideally we'd have 1) and 2) but I guess we can live without.

An alternative would be to get a powered USB hub and use it with the existing USBEth adapter. This way we'd get 1) and 2) in exchange for operating two devices.

Estel 2014-08-02 00:14

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
if you want to determine what is causing massive power drainage while using usb-rj45 adapter, you may want to perform the same tests that I suggested in other thread:
http://talk.maemo.org/showpost.php?p...6&postcount=35

+ do powertop tests. We should know if it's really the adapter draining too much power, or just device's CPU is active all the time + gods know whatsnot (or both).

Although, from my experience, hostmoding anything - be it just keyboard or mouse - result in device drawing much more current than it "should" (i.e. we're able to give only 200 mA to device connected to USB, so if your full ~1200 mAh battery drains in one hour when using ethernet adapter, it means that adapter itself could eat as much as 200 mAh, and device is eating rest of 1000 mAh on it's own).

Well, our hostmode implementation isn't a "reference one" - damn you Nokia for carrying about some stupid certification, and pulling out official hostmode support on the last moment. As a result, the fact that we have hostmode at all - even with it's speed limited by unknown reasons to under what's our WiFi offers, constant high-speed problems, and such - it's a miracle.

/Estel

Halftux 2014-08-02 06:56

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I found some usblan adapters with 120mA posted from RPI guys who had some problem with a kernel bug. So I dont know if they will work.

biketool 2014-08-02 17:56

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
The blue USB-eth one from that link with 120ma/h has a thread somewhere on TMO, I had one, the driver is not in KP.

peterleinchen 2014-08-02 19:52

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
I never ever got that d*mn blue (but all colors available) DM9601 thing to work ... :mad:

Estel 2014-08-03 04:20

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Once, I've asked Pali to include that driver (IIRC, it works, when compiled as a module). For some reason, Pali wasn't interested, until someone can work in a brain-dead patch for KP that would include it. He said that having it work as a loadable module is one thing, and having it released with KP is another, and would require much work.

Scratch it if I'm writing nonsense, I don't know anything about how integrating module in kernel works from theoretical point of view.

/Estel

chill 2014-08-03 08:36

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by Estel (Post 1434577)
if you want to determine what is causing massive power drainage while using usb-rj45 adapter, ...
Well, our hostmode implementation isn't a "reference one" - damn you Nokia for carrying about some stupid certification, and pulling out official hostmode support on the last moment. As a result, the fact that we have hostmode at all - even with it's speed limited by unknown reasons to under what's our WiFi offers, constant high-speed problems, and such - it's a miracle.

/Estel

I just tried to do a powertop test, and while I was messing around with powertop, learning to fix the segmentation fault etc, the device shut down, undoubtedly due to a drained battery. :( I'll try again later.

So if it's indeed a miracle and it looks like nothing can be done to improve the situation consumption-wise, then I should proceed with the external power idea. To clarify, my plan is to power the USBEth adapter with a USB hub, or get the Syba adapter+hub thing, and put the N900 in "host with charging" mode. The N900 thus won't be putting out (big) current, so the battery won't drain.

Additionally, I'd like to charge the N900 while I'm powering the USBEth adapter, but it's hard to tell if any given USB hub will charge the host that's attached to it. The Syba device will not, according to Syba.

Estel 2014-08-04 01:16

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Syba will not on it own, but everything - no matter if it want it or not - will charge N900 at the time of hostmoding, if you use USB Y-cable. Thanks to it, you connect +5V charging device (aka any_usb_charger) in parallel (with first USB device from N900 side, in this case, a network adapter or hub) to N900, and it is it.

This way, you can charger N900 while using any USB peripherial, even without hub, as long as N900 is able to give enough current to, at least, enumerate that device - because, you need to enumerate first and then, ONLY then, attach external power to Y-cable. Other way, enumeration will fail (no hardware risk, just no working connection).

All things that require more than 200mA current to even enumerate (some external hard drives, for example) require powered hub, as those may have power attached before enumerating client. Hub is required too - obviously - if you want to use more than one device at the same time.

I've got my small, ultra-lightweight powered hub for something like 2USD (charger not included, but hacking it to charge from any other 5V power source is a piece of cake), so it's rather feasible to just use one, and carry it alongside N900.

/Estel

chill 2014-08-04 21:41

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by Estel (Post 1434768)
Syba will not on it own, but everything - no matter if it want it or not - will charge N900 at the time of hostmoding, if you use USB Y-cable. Thanks to it, yoiu connect +5V charging device (aka any_usb_charger) in parallel (with first USB device from N900 side, in this case, a network adapter or hub) to N900, and it is it.

This way, you can charger N900 while using any USB peripherial, even without hub, as long as N900 is able to give enough current to, at least, enumerate that device - because, you need to enumerate first and then, ONLY then, attach external power to Y-cable. Other way, enumeration will fail (no hardware risk, just no working connection).

All things that require more than 200mA current to even enumerate (some external hard drives, for example) require powered hub, as those may have power attached before enumerating client. Hub is required too - obviously - if you want to use more than one device at the same time.

I've got my small, ultra-lightweight powered hub for something like 2USD (charger not included, but hacking it to charge from any other 5V power source is a piece of cake), so it's rather feasible to just use one, and carry it alongside N900.

/Estel

Ok, that's pretty useful info.

But let me get this straight. You recommend using a Y-splitter USB cable and any_charger_cable to power the peripherals and, simultaneously, the N900. However, you are not using a Y-splitter yourself - you use a powered hub to charge the peripherals, which implies that the N900 is not simultaneously charged. Correct?

Also, will the N900 be charged - no matter if it want it or not - even if the selected mode is not USB host+charging?

Also, what do you mean by "it's rather feasible to just use one"?

Estel 2014-08-05 07:16

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by chill (Post 1434867)
Ok, that's pretty useful info.

But let me get this straight. You recommend using a Y-splitter USB cable and any_charger_cable to power the peripherals and, simultaneously, the N900. However, you are not using a Y-splitter yourself - you use a powered hub to charge the peripherals, which implies that the N900 is not simultaneously charged. Correct?

No, sorry for the confusion. Is use Y-splitter cable (to be precise, a femal-to-female USB adaptor, with additional cable soldered to +5V and ground USB pins) for every hostmode use. N900 is on the one end of such cable, as a host.

then, on the other end, I may have either device itself, or a powered or un-powered hub. In all those cases, I can charge N900 simultaneously, by plugging the "3th end" of Y-cable into power source, and selecting hostmode+charging.

Hoever, this way you can't use peripherals, that require more than 200 mA current to even enumerate - because you may connect "3th end" of Y-cable (and select hostmode_charging) only after device got successfully connected, already. No device will enumerate, if +5V from external source is present already, you may connect it only AFTER you have device connected and visible by system (as stated in hostmode "manual").

For such cases (devices that draw more than 200 mA to even enumerate properly), USB hub is a must. It doesn't have anything to do with using Y-cable, you still need one for charging devices. BTW, powered USB hubs should *never* charge host device that they're connected to - if they do (I saw some that do), it is implementation fault. They shouldn't put current "upstream".

Now, if your passive (non-powered) hub (or active one, which doesn't have charger connected, so act as a passive at the moment) follows specification strictly, it *won't* give more than 100 mA to connected peripherals. It is because passive hub is powered by other usb host (normally, up to 500 mA), so it reserver 100 mA for itself, and gives 100 mA for every of fours possible clients. Now, most hubs are internally manufactured to allow connecting of 4 peripherals, no matter, how many ports they have in reality. 7-port hubs have seven ports not incidentally - they're two hubs connected in series, internally.

There are many passive hubs, that doesn't follow specifications strictly - and they will give every peripherals as much current as they need even in passive mode, as far as they got enough power from "upstream". Normally, they're worse choice (as they will flop if, for example, you connected them to PC, and 4x 500mA-requiring USB hard disks). Hoever, for N900, they're better, as they allow you to have the same functionality as powered hub, just by using Y-cable, as described earlier.

In case you don't have such hub, you must use "officially" powered one. There are some, that act as powered when connected to charger, and as passive, otherwise. They're most flexible ones, and I would recommend those.

Quote:

Originally Posted by chill (Post 1434867)
Also, will the N900 be charged - no matter if it want it or not - even if the selected mode is not USB host+charging?

No, see above.

Quote:

Originally Posted by chill (Post 1434867)
Also, what do you mean by "it's rather feasible to just use one"?

With USB hub - passive or active - you may connect peripherals on the fly, without going through the enumerating process on the N900's side. You just enumerate hub once, and it is it, you just connect peripherals to hub, and hub does enumerating, internally, for you.

That is why I've said it is feasible - as in practical, convenient, and not expensive - to carry a small hub with your N900 all the time, when you expect needing to do hostmode.

/Estel

// Edit

To make thins easier to understand, here is the idea schematic:

Code:

                              _________
                          ___| +5V    |___
    _______      ________<USB| USB    |___
  [N900  ]    /            |_Charger_|
  [_______]    / Y-Cable
 --[qwerty_]  /  3th end    __________
|            /            |USB Client|
|  ___  ____|___ ___      |    or    |
 --<USB||ADAP|TOR|USB>------| USB HUB  |
                            |__________|
        (Female
            to
          Female)


chill 2014-08-06 00:57

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Good info again, thanks. I have a few small questions, if you don't mind, esp. after reading the threads about h-e-n and the likes:

Quote:

Originally Posted by Estel (Post 1434898)
No, sorry for the confusion. Is use Y-splitter cable (to be precise, a femal-to-female USB adaptor, with additional cable soldered to +5V and ground USB pins) for every hostmode use. N900 is on the one end of such cable, as a host.

then, on the other end, I may have either device itself, or a powered or un-powered hub. In all those cases, I can charge N900 simultaneously, by plugging the "3th end" of Y-cable into power source, and selecting hostmode+charging.

Hoever, this way you can't use peripherals, that require more than 200 mA current to even enumerate - because you may connect "3th end" of Y-cable (and select hostmode_charging) only after device got successfully connected, already. No device will enumerate, if +5V from external source is present already, you may connect it only AFTER you have device connected and visible by system (as stated in hostmode "manual").

Ok, I guess this is because the N900 can supply no more than 200 mA (this I got from my reading elsewhere).
Not to doubt you, but could you point to the "manual"?

I guess you mean no device will enumerate if external +5V is presented to the N900 while you're trying to enumerate.

Quote:

Originally Posted by Estel (Post 1434898)
For such cases (devices that draw more than 200 mA to even enumerate properly), USB hub is a must. It doesn't have anything to do with using Y-cable, you still need one for charging devices.

Ok, so reading this and the below, you need a powered hub for these >200mA devices. This is because a) they cannot get >200mA from the N900, and b) the >200mA they could get from a +5V external source via the y-cable would not allow for enumeration on the N900. Correct?

Quote:

Originally Posted by Estel (Post 1434898)
BTW, powered USB hubs should *never* charge host device that they're connected to - if they do (I saw some that do), it is implementation fault. They shouldn't put current "upstream".

Now, if your passive (non-powered) hub (or active one, which doesn't have charger connected, so act as a passive at the moment) follows specification strictly, it *won't* give more than 100 mA to connected peripherals. It is because passive hub is powered by other usb host (normally, up to 500 mA), so it reserver 100 mA for itself, and gives 100 mA for every of fours possible clients. Now, most hubs are internally manufactured to allow connecting of 4 peripherals, no matter, how many ports they have in reality. 7-port hubs have seven ports not incidentally - they're two hubs connected in series, internally.

There are many passive hubs, that doesn't follow specifications strictly - and they will give every peripherals as much current as they need even in passive mode, as far as they got enough power from "upstream". Normally, they're worse choice (as they will flop if, for example, you connected them to PC, and 4x 500mA-requiring USB hard disks).

Ok I guess here you mean that you connect a non-compliant passive hub to a PC, and since a PC port only gives up to 500mA (it is assumed compliant) and a USB hard disk wants >500mA, the USB hard disk doesn't work, and then the user is left wondering why.

Quote:

Originally Posted by Estel (Post 1434898)
Hoever, for N900, they're better, as they allow you to have the same functionality as powered hub, just by using Y-cable, as described earlier.

Right, but (from my understanding) they would not solve the problem of >200mA peripherals, due to the above.

So, bottom line, if you want to charge the N900 and be able to use >200mA peripherals, so you need a y-cable and a powered hub. Yes?

Thanks esp. for the schematic. I personally will buy a y-cable because they are $2-5 only; even videos about making them recommend not doing it on your own unless you can't wait for the order to arrive.

EDIT: To test my understanding of the matter, let me pose the following solution to the >200mA peripherals problem:

You connect a y-cable to the N900. You connect a passive non-compliant hub to one of the branches. You start hostmode and enumerate the hub. Then you connect a charger to the other branch. Then you connect a >200mA peripheral to the hub. Logic: the charger gives >200mA to the peripheral via the y-cable and the non-compliant hub. The hub has already been enumerated so there is no more enumerating to be be done on the N900, which means there is no problem with the external +5V preventing enumerating. The hub enumerates the peripheral. The peripheral will enumerate and operate because it has sufficient current. Yes? No?

Estel 2014-08-06 09:51

Re: Nokia N900 + Ethernet (via USB-RJ45 adapter)
 
Quote:

Originally Posted by chill (Post 1434973)
Good info again, thanks. I have a few small questions, if you don't mind, esp. after reading the threads about h-e-n and the likes:

Sure, I'll gladly answer :) The things are easy once you know them, but can be confusing at the start. I remember how many times I had problems with it in the past...

Quote:

Originally Posted by chill (Post 1434973)
Ok, I guess this is because the N900 can supply no more than 200 mA (this I got from my reading elsewhere).
Not to doubt you, but could you point to the "manual"?

That's why I have put quotas there - I meant general instructions from USB Mode or H-E-N (I assume, that you're using USB Mode).

Quote:

Originally Posted by chill (Post 1434973)
I guess you mean no device will enumerate if external +5V is presented to the N900 while you're trying to enumerate.

Yes - even if N900 is *not* charging yet. The sole presence of +5V to N900 from external source prevent enumerating.

Quote:

Originally Posted by chill (Post 1434973)
Ok, so reading this and the below, you need a powered hub for these >200mA devices. This is because a) they cannot get >200mA from the N900, and b) the >200mA they could get from a +5V external source via the y-cable would not allow for enumeration on the N900. Correct?

Yes, entirely correct.

Quote:

Originally Posted by chill (Post 1434973)
Ok I guess here you mean that you connect a non-compliant passive hub to a PC, and since a PC port only gives up to 500mA (it is assumed compliant) and a USB hard disk wants >500mA, the USB hard disk doesn't work, and then the user is left wondering why.

To be completely precise, in such cases, Hard disk's manufacturers add their own Y-cable, to draw current from 2nd PC port. What I meant is that you connect non-compliant passive HUB to PC - HUB gets up to 500 mA, as you correctly guessed. Then, you connect 4x devices to hub, and every one of them want 300 mA, for example. 4*300mA = 1200 mA. Hub have only 500 mA from single port it is connected to, so it silently fails - not only devices conencted to it, but hub too (it require re-enumerating from scratch, to recover).

Now, compliant hub in passive mode would allow client devices to get only 100 mA, so devices wanting more current wouldn't work, but hub itself wouldn't "die" due to low power (and, in case it have some devices connected, that require less than 100 mA - like mouse, keyboard, etc - they would still continue to work).

But, it's all not entirely related to hostmoding on N900. I meant that - in funny twist - those non-compliant hubs are better for N900, as they try to give peripherals connected to them as much current as needed, and can draw those power from N900's side (which can be already "augmented" with power from 3th branch of Y-cable) - which mean that those passive hubs act entirely like active hubs, for all intents and purposes.

But, to not complicate things, you can safely assume, that you need powered (aka active) hub, for everything that require more than 200 mA, for N900 hostmoding.

Quote:

Originally Posted by chill (Post 1434973)
So, bottom line, if you want to charge the N900 and be able to use >200mA peripherals, so you need a y-cable and a powered hub. Yes?

Yes, see above. By the way, if you tinker with it a little, active hub can be powered from the same +5V power source as your N900 is charged from (via 3th branch of Y-cable) - this way, you can carry just one charger with you, instead of two. But for this, you need powerful enough +5V power source. I use a 2A +5V charger, that I have modified to contain two USB ports. I connect 3th branch of Y-cable to it (for charging N900), and another cable for powering active hub, to the 2nd port.

Of course, it doesn't hurt if you want to carry two power sources (one for charging N900, one for powering active hub). It is just less convenient, IMO.

Quote:

Originally Posted by chill (Post 1434973)
Thanks esp. for the schematic. I personally will buy a y-cable because they are $2-5 only; even videos about making them recommend not doing it on your own unless you can't wait for the order to arrive.

True :D I made it myself, as:
a) I wanted to have it less bulky than ones sold
b) I had all required parts and I'm cheap bastard, so paying few bucks wasn't required
c) doing it myself, I was, at least, sure that it's properly shielded - N900's high-speed hostmode is picky enough, I wasn't in need for risk of any additional interferences.

Quote:

Originally Posted by chill (Post 1434973)
EDIT: To test my understanding of the matter, let me pose the following solution to the >200mA peripherals problem:

You connect a y-cable to the N900. You connect a passive non-compliant hub to one of the branches. You start hostmode and enumerate the hub. Then you connect a charger to the other branch.

...then you select "hostmode with charging" on N900, if you want to charge it.

Quote:

Originally Posted by chill (Post 1434973)
Then you connect a >200mA peripheral to the hub. Logic: the charger gives >200mA to the peripheral via the y-cable and the non-compliant hub. The hub has already been enumerated so there is no more enumerating to be be done on the N900, which means there is no problem with the external +5V preventing enumerating. The hub enumerates the peripheral. The peripheral will enumerate and operate because it has sufficient current. Yes? No?

Yes, absolutely correct.

/Estel


All times are GMT. The time now is 20:00.

vBulletin® Version 3.8.8