maemo.org - Talk - Thread for problems getting USB hostmode working.

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)

- - Thread for problems getting USB hostmode working. (https://talk.maemo.org/showthread.php?t=65570)

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by mehdi.gl (Post 986345)

When I connect a mouse it lights but no cursor
When I connect a keyboard it's as it is not connected
When I connect a flash drive it's as it is not connected

I think for mice you need extmou http://talk.maemo.org/showthread.php?t=66141
I think for keyboards you need extkdb http://talk.maemo.org/showthread.php?t=65577
For the flash drive I think you will need to post the log

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by mehdi.gl (Post 986509)

Please help me !!

Do you get anything in kernel messages?
You might just have a bad cable.

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by bentech4u (Post 981214)

Code:

mount -t ntfs /dev/sda1 /media/ntfs -o uid=29999,gid=29999,utf8,dmask=027,fmask=137

Did you try using the flag rw?

Code:

mount -t ntfs /dev/sda1 /media/ntfs -o uid=29999,gid=29999,utf8,dmask=027,fmask=137,rw

The kernel module in power kernel should be able to write, but it's not the default since it's still experimental. If you're not specifying rw in the flags it's probably defaulting to ro. If the fs module truly is the read-only one as someone suggested here, using rw will fail to mount, and dmesg should show a kernel message to that affect.

If this is something you can use vfat on (a storage drive, etc) then you should really use that instead. NTFS is great and all, but it's proprietary and thus not well documented or supported in open source code. There are simple command-line drive format tools out there that can format very large drives with vfat without an issue.

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by woody14619 (Post 986776)

Did you try using the flag rw?

Code:

mount -t ntfs /dev/sda1 /media/ntfs -o uid=29999,gid=29999,utf8,dmask=027,fmask=137,rw

Result:
mount:mounting /dev/sda1 on media/ntfs failed : No such file or directory :(

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by biketool (Post 986761)

Do you get anything in kernel messages?
You might just have a bad cable.

I don't have error messages
My cable is working because if I connect a mouse I see the red light of the mouse as it is connected on the pc !!
:(

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by yorkey (Post 986758)

extkb and extmou are installed but usb host mode for mouse and keyboard is not working
Where can I find the log ??

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by yorkey (Post 986753)

Why would a mouse have a filesystem? You cant store files on your mouse!

MIce and keyboards do not need mounting.

I don't know !!
This is why I'm posting here
I'm not using mount but I have the message

"Unable to connect, no file system available"
Please help me

Re: Thread for problems getting USB hostmode working.

After multiple attempts I wrote

mount /dev/sda1 /media/my_flash

and it worked

I don't know why the mount of the gui h-e-n does not work

------------------------------

But the problem is persisting for mice and keyboards

Re: Thread for problems getting USB hostmode working.

Awesome software and good people...Dude your post made my day...
U guys Rock!!!!!

Quote:

Originally Posted by MohammadAG (Post 872630)

If you mount under /media, it should.

Code:

mkdir -p /media/ntfs

mount /dev/sda1 /media/ntfs

Re: Thread for problems getting USB hostmode working.

Problem is persisting for mice and keyboards
Please Help Me
Where can I find the log to recognize the problem ??

Re: Thread for problems getting USB hostmode working.

It's perfect adi619 !!!!
Thanks a lot, the problem was in the mode
I selected high speed mode, that was the problem.
For mice and keyboards we should select low speed mode.
Now everything is ok
These are the steps to connect a mouse or a keyboard to the n900

Instalaltions
1- Install power kernel
2- Install h-e-n
--------------------------------------------------------------------
To Execute

1.. Start h-e-n

2. Connect the data cable to the n900

3. Connect the mouse to the Cable

4. In h-e-n select low speed hostmode

5. Click v boost on

6. Click enumarate

7.wait a minute and u'll get a message "connected to OM"

Thanks to adi619 for his help by Private Message :)
And thanks to the community :)

Re: Thread for problems getting USB hostmode working.

Dear guys,

Need your assistance. I had bought usb network adapter sr9600 but getting error SIOCGIFINDEX failed and under ifconfig no such ethernet 0.

Kindly do refer to attachment of screenshot and also the network card driver

Re: Thread for problems getting USB hostmode working.

Hi guys,
i have bought a LogiLink USB 2.0 RJ45 Fast Ethernet Adapter
and when I try to connect my N900 to LAN I got - after the command UDHCPC - the following message :

SIOCGIFINDEX failed! : No such device

Reading all your posts I think that the LogiLink drive is missing . I have the Linux drive for this device provided from the maker but I do not know how to compile and load on N900.

Anyone can help me ?

================================================== =====

Hi guys in the mean time I have found the solution!
It works perfect ! Follow this:

http://talk.maemo.org/showpost.php?p...&postcount=127

many thanks to MVEPLUS !!!

Re: Thread for problems getting USB hostmode working.

I already try that but still not working .

Can some assists me.

plzzzzzzzzz

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by jackjohn (Post 993497)

I already try that but still not working .

Can some assists me.

plzzzzzzzzz

The pack that I put together is not perfect and will not work for all USB 2 Net dingle's out there...

It really depends on what is the chip inside. If it's cheap you can open and see.( if there is no warranty )

You can connect your dongle to Linux (Ubuntu. Mint, or else) and check if it's working, whiteout installing any drivers. if does not work there is big chance to not be able to use that with N900.

If it works under Linux you can post output of dmesg and lsusb command, to see what is going on...

Code:

$dmesg

$lsusb

Greetings,
mveplus

P.S. Okey I didi compile your source code against kernel-power-headers, but got some errors during compilation:

Code:

make

Building SR9600 USB2NET chip driver...

make[1]: Entering directory `/targets/FREMANTLE_ARMEL/usr/src/kernel-power-headers'

  CC [M]  /home/mven/sr9600.o

  Building modules, stage 2.

  MODPOST 1 modules

WARNING: "__bad_udelay" [/home/mven/sr9600.ko] undefined!

  CC      /home/mven/sr9600.mod.o

  LD [M]  /home/mven/sr9600.ko

make[1]: Leaving directory `/targets/FREMANTLE_ARMEL/usr/src/kernel-power-headers'

Here is your compiled sr9600.ko file

If it's working then enjoy, if not then - Hmmm, do not give up go and buy other dongle :)

Do not have much time to do more now.

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by mveplus (Post 993576)

Code:

$dmesg

$lsusb

Greetings,
mveplus

P.S. Okey I didi compile your source code against kernel-power-headers, but got some errors during compilation:

Code:

make

Building SR9600 USB2NET chip driver...

make[1]: Entering directory `/targets/FREMANTLE_ARMEL/usr/src/kernel-power-headers'

  CC [M]  /home/mven/sr9600.o

  Building modules, stage 2.

  MODPOST 1 modules

WARNING: "__bad_udelay" [/home/mven/sr9600.ko] undefined!

  CC      /home/mven/sr9600.mod.o

  LD [M]  /home/mven/sr9600.ko

make[1]: Leaving directory `/targets/FREMANTLE_ARMEL/usr/src/kernel-power-headers'

Here is your compiled sr9600.ko file

If it's working then enjoy, if not then - Hmmm, do not give up go and buy other dongle :)

Do not have much time to do more now.

Dear mveplus

First of thanks for the assistance. Anyway still not managed to add it.

the chip is supereal sr9600.

after i run insmod sr9600.ko get error inserting sr9600.ko:-1 unknown symbol in module

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by jackjohn (Post 993628)

Usually this means that this module depends on some other modules.You need to load that/these/ module first, then sr9600.ko last.

dmesg can reveal more details when you get this error what is the module that is missing/need to be load before this/

You can try with my package load first all modules that I have in my package and then last one sr9600.ko, hope it depend on some of them....

Greetings

Re: Thread for problems getting USB hostmode working.

Warning: __bad_udelay
sounds odd.

/j

@mveplus:

Quote:

Nokia N900 - H-E-N is here, NEXT STEP - Spacecraft control

http://freeyourphone.de/portal_v1/vi...p=14569#p14569

Re: Thread for problems getting USB hostmode working.

I sow later that this is only warning, but I'm not 'C' programmer, clud not raelly say if it's a issue or not :confused:

Quote:

Originally Posted by joerg_rw (Post 994100)

Warning: __bad_udelay
sounds odd.

/j

@mveplus:

http://freeyourphone.de/portal_v1/vi...p=14569#p14569

Yes that's what I'm talking about! Great Joerg_rw,but it needs N900 beside OpenMoko :) Wil become Supercomputer then!

Quote:

jackjohn

Today , 07:09 AM
Posts: 12 | Thanked: 2 times | Joined on Nov 2010

Originally Posted by mveplus

Originally Posted by jackjohn

Dear mveplus

First of thanks for the assistance. Anyway still not managed to add it.

the chip is supereal sr9600.

after i run insmod sr9600.ko get error inserting sr9600.ko:-1 unknown symbol in module

Usually this means that this module depends on some other that need to be loaded first, the this second.
dmesg can reveal mode details when you get this error.

dear mveplus,

iam getting this.

[81459.418823] sr9600: Unknown symbol usbnet_set_msglevel
[81459.421020] sr9600: Unknown symbol usbnet_get_msglevel
[81459.421966] sr9600: Unknown symbol __bad_udelay
[81459.423065] sr9600: Unknown symbol usbnet_get_settings
[81459.424102] sr9600: Unknown symbol usbnet_suspend
[81459.424804] sr9600: Unknown symbol usbnet_get_drvinfo
[81459.425628] sr9600: Unknown symbol usbnet_get_endpoints
[81459.426910] sr9600: Unknown symbol usbnet_nway_reset
[81459.427917] sr9600: Unknown symbol usbnet_defer_kevent
[81459.428833] sr9600: Unknown symbol usbnet_disconnect
[81459.429534] sr9600: Unknown symbol usbnet_set_settings
[81459.430023] sr9600: Unknown symbol usbnet_probe
[81459.430480] sr9600: Unknown symbol usbnet_resume

Jackson you can sent me PM, but write here to benefit all Maemo geeks!

sr9600 is looking for something in usbnet module.
I do not have that one in my pack so I compiled today hope it will work this time! usbnet.ko

Re: Thread for problems getting USB hostmode working.

Dear Guys,,

Its still not working. Really need your assistance since this the only type that been sell. Really need to get this adapter work.

FYI. i had copy the usbnet.ko to /lib/modules/2.6.28.10power46 and copy the file sr9600.ko to /home/opt/usb2net/module and opt/usb2net/module and after i run insmode sr9600;ko at both location i get same error "inserting sr9600.ko:-1 unknown symbol in module" and under dmesg it just show 1 error [81459.421966] sr9600: Unknown symbol __bad_udelay"

Try to run h-e-n still not working getting below messages.

[117868.085937] sr9600: Unknown symbol __bad_udelay
[117900.744262] slide (GPIO 71) is now closed
[117916.822479] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[117943.400512] slide (GPIO 71) is now open
[117966.525451] slide (GPIO 71) is now closed
[117977.695343] usb usb1: usb resume
[117977.712890] hub 1-0:1.0: hub_resume
[117977.713012] hub 1-0:1.0: port 1: status 0101 change 0001
[117977.822540] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[117977.822631] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[117977.947418] usb 1-1: new full speed USB device using musb_hdrc and address 99
[117978.095764] usb 1-1: ep0 maxpacket = 8
[117978.096832] usb 1-1: default language 0x0409
[117978.098602] usb 1-1: uevent
[117978.098815] usb 1-1: usb_probe_device
[117978.098846] usb 1-1: configuration #1 chosen from 1 choice
[117978.102233] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[117978.102569] usb 1-1:1.0: uevent
[117978.105194] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '099'
[117978.105895] usb 1-1: New USB device found, idVendor=0fe6, idProduct=8101
[117978.105957] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=3
[117978.105987] usb 1-1: Product: USB Network Controller
[117978.106018] usb 1-1: SerialNumber:
[117978.106048] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[117978.106140] hub 1-0:1.0: port 1 enable change, status 00000103
[117994.048889] slide (GPIO 71) is now open
/home/user # ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:10360 errors:0 dropped:0 overruns:0 frame:0
TX packets:10360 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:616991 (602.5 KiB) TX bytes:616991 (602.5 KiB)

phonet0 Link encap:UNSPEC HWaddr 15-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP POINTOPOINT RUNNING NOARP MTU:4000 Metric:1
RX packets:38208 errors:0 dropped:0 overruns:0 frame:0
TX packets:7490 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:17187936 (16.3 MiB) TX bytes:367854 (359.2 KiB)

/home/user # usbEthUp.sh
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/rtl8150.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/mcs7830.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/dm9601.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/smsc95xx.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/kaweth.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/pegasus.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/plusb.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/gl620a.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.28.10power46/usb2net/catc.ko': -1 File exists
udhcpc (v0.9.9-pre) started
SIOCGIFINDEX failed!: No such device
/home/user # lsusb
Bus 001 Device 099: ID 0fe6:8101
Bus 001 Device 001: ID 1d6b:0002
/home/user # udhcpc
udhcpc (v0.9.9-pre) started
SIOCGIFINDEX failed!: No such device
/home/user # ifconfig eth0 up
ifconfig: SIOCGIFFLAGS: No such device
/home/user # ls /dev/eth*
ls: /dev/eth*: No such file or directory
/home/user #

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by jackjohn (Post 994463)

Hi Jackjohn, I fas so in a hurry that I compiled something that is already there usbnet.ko, is included by default, so the only thin you need to do is to modprobe usbnet, however this will not make your adapter to work. It's based on
* Davicom DM9601 USB 1.1 10/100Mbps Ethernet devices, but is using chip sr9600 which is the "'same copy" but I do not really know why is not working, may be different registry addressing or similar. Look your source code sr9600.c, second row is the email of the guy that wrote this driver, your best bet is to contact him.
Quick search in google - revile that it has something to do with kernel and architecture AMR ? I look trough the code but as I said before I do not write "C" code so I can not help further...

Greetings, mveplus

Re: Thread for problems getting USB hostmode working.

Hi Guys,

Need your help, i am unable to connect to USB mouse or Pen drive. I have installed the HEN, extmou and tried opening the cursor and the run the HEN but my mouse is not detected. Attached the log file for your reference, awaiting for your response.. Thanks in advance...

Code:

 7 ports 1 chg 0002 evt 0000



[ 4986.916290] usb 1-1: new high speed USB device using musb_hdrc and address 75

[ 4987.041229] usb 1-1: device descriptor read/64, error -71

[ 4987.275665] usb 1-1: device descriptor read/64, error -71

[ 4987.510009] usb 1-1: new high speed USB device using musb_hdrc and address 76

[ 4987.931945] usb 1-1: device not accepting address 76, error -71

[ 4988.057067] usb 1-1: new high speed USB device using musb_hdrc and address 77

[ 4988.478820] usb 1-1: device not accepting address 77, error -71

[ 4988.478942] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 4988.479003] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 4988.479034] hub 1-0:1.0: port 1 enable change, status 00000501

[ 4991.197448] hub 1-0:1.0: hub_suspend

[ 4991.197509] usb usb1: bus auto-suspend

[ 4991.197509] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[ 4991.197540] usb usb1: bus suspend fail, err -16

[ 4991.197570] hub 1-0:1.0: hub_resume

[ 4991.197631] hub 1-0:1.0: port 1: status 0501 change 0000

[ 4991.197692] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[ 4991.197723] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[ 4991.322479] usb 1-1: new high speed USB device using musb_hdrc and address 78

[ 4991.447509] usb 1-1: device descriptor read/64, error -71

[ 4991.681915] usb 1-1: device descriptor read/64, error -71

[ 4991.916290] usb 1-1: new high speed USB device using musb_hdrc and address 79

[ 4992.041290] usb 1-1: device descriptor read/64, error -71

[ 4992.276489] usb 1-1: device descriptor read/64, error -71

[ 4992.510040] usb 1-1: new high speed USB device using musb_hdrc and address 80

[ 4992.931915] usb 1-1: device not accepting address 80, error -71

[ 4993.056884] usb 1-1: new high speed USB device using musb_hdrc and address 81

[ 4993.478698] usb 1-1: device not accepting address 81, error -71

[ 4993.478790] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 4993.478820] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 4993.478851] hub 1-0:1.0: port 1 enable change, status 00000501

[ 4996.197387] hub 1-0:1.0: hub_suspend

[ 4996.197448] usb usb1: bus auto-suspend

[ 4996.197448] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[ 4996.197479] usb usb1: bus suspend fail, err -16

[ 4996.197509] hub 1-0:1.0: hub_resume

[ 4996.197540] hub 1-0:1.0: port 1: status 0501 change 0000

[ 4996.197601] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[ 4996.197631] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[ 4996.322540] usb 1-1: new high speed USB device using musb_hdrc and address 82

[ 4996.447540] usb 1-1: device descriptor read/64, error -71

[ 4996.681915] usb 1-1: device descriptor read/64, error -71

[ 4996.916290] usb 1-1: new high speed USB device using musb_hdrc and address 83

[ 4997.041290] usb 1-1: device descriptor read/64, error -71

[ 4997.275726] usb 1-1: device descriptor read/64, error -71

[ 4997.510101] usb 1-1: new high speed USB device using musb_hdrc and address 84

[ 4997.931823] usb 1-1: device not accepting address 84, error -71

[ 4998.057586] usb 1-1: new high speed USB device using musb_hdrc and address 85

[ 4998.478790] usb 1-1: device not accepting address 85, error -71

[ 4998.478912] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 4998.478973] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 4998.479034] hub 1-0:1.0: port 1 enable change, status 00000501

[ 5001.197479] hub 1-0:1.0: hub_suspend

[ 5001.197540] usb usb1: bus auto-suspend

[ 5001.197570] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[ 5001.197631] usb usb1: bus suspend fail, err -16

[ 5001.197662] hub 1-0:1.0: hub_resume

[ 5001.197723] hub 1-0:1.0: port 1: status 0501 change 0000

[ 5001.197814] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[ 5001.197906] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[ 5001.322540] usb 1-1: new high speed USB device using musb_hdrc and address 86

[ 5001.447540] usb 1-1: device descriptor read/64, error -71

[ 5001.681915] usb 1-1: device descriptor read/64, error -71

[ 5001.916259] usb 1-1: new high speed USB device using musb_hdrc and address 87

[ 5002.041473] usb 1-1: device descriptor read/64, error -71

[ 5002.275817] usb 1-1: device descriptor read/64, error -71

[ 5002.510101] usb 1-1: new high speed USB device using musb_hdrc and address 88

[ 5002.932678] usb 1-1: device not accepting address 88, error -71

[ 5003.056945] usb 1-1: new high speed USB device using musb_hdrc and address 89

[ 5003.478759] usb 1-1: device not accepting address 89, error -71

[ 5003.478881] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 5003.478942] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 5003.479003] hub 1-0:1.0: port 1 enable change, status 00000501

[ 5006.197448] hub 1-0:1.0: hub_suspend

[ 5006.197509] usb usb1: bus auto-suspend

[ 5006.197540] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[ 5006.197570] usb usb1: bus suspend fail, err -16

[ 5006.197570] hub 1-0:1.0: hub_resume

[ 5006.197631] hub 1-0:1.0: port 1: status 0501 change 0000

[ 5006.197692] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[ 5006.197723] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[ 5006.322570] usb 1-1: new high speed USB device using musb_hdrc and address 90

[ 5006.447540] usb 1-1: device descriptor read/64, error -71

[ 5006.681884] usb 1-1: device descriptor read/64, error -71

[ 5006.916229] usb 1-1: new high speed USB device using musb_hdrc and address 91

[ 5007.041229] usb 1-1: device descriptor read/64, error -71

[ 5007.275604] usb 1-1: device descriptor read/64, error -71

[ 5007.510040] usb 1-1: new high speed USB device using musb_hdrc and address 92

[ 5007.931884] usb 1-1: device not accepting address 92, error -71

[ 5008.056915] usb 1-1: new high speed USB device using musb_hdrc and address 93

[ 5008.478729] usb 1-1: device not accepting address 93, error -71

[ 5008.478851] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 5008.478912] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 5008.478973] hub 1-0:1.0: port 1 enable change, status 00000501

[ 5011.197509] hub 1-0:1.0: hub_suspend

[ 5011.197601] usb usb1: bus auto-suspend

[ 5011.197631] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[ 5011.197692] usb usb1: bus suspend fail, err -16

[ 5011.197692] hub 1-0:1.0: hub_resume

[ 5011.197784] hub 1-0:1.0: port 1: status 0501 change 0000

[ 5011.197875] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[ 5011.197937] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[ 5011.322601] usb 1-1: new high speed USB device using musb_hdrc and address 94

[ 5011.447601] usb 1-1: device descriptor read/64, error -71

[ 5011.681976] usb 1-1: device descriptor read/64, error -71

[ 5011.916229] usb 1-1: new high speed USB device using musb_hdrc and address 95

[ 5012.041442] usb 1-1: device descriptor read/64, error -71

[ 5012.275726] usb 1-1: device descriptor read/64, error -71

[ 5012.510101] usb 1-1: new high speed USB device using musb_hdrc and address 96

[ 5012.931945] usb 1-1: device not accepting address 96, error -71

[ 5013.056945] usb 1-1: new high speed USB device using musb_hdrc and address 97

[ 5013.478881] usb 1-1: device not accepting address 97, error -71

[ 5013.479034] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 5013.479064] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 5013.479125] hub 1-0:1.0: port 1 enable change, status 00000501

[ 5016.197509] hub 1-0:1.0: hub_suspend

[ 5016.197601] usb usb1: bus auto-suspend

[ 5016.197631] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[ 5016.197662] usb usb1: bus suspend fail, err -16

[ 5016.197692] hub 1-0:1.0: hub_resume

[ 5016.197784] hub 1-0:1.0: port 1: status 0501 change 0000

[ 5016.197875] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[ 5016.197937] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[ 5016.322662] usb 1-1: new high speed USB device using musb_hdrc and address 98

[ 5016.447601] usb 1-1: device descriptor read/64, error -71

[ 5016.681854] usb 1-1: device descriptor read/64, error -71

[ 5016.916259] usb 1-1: new high speed USB device using musb_hdrc and address 99

[ 5016.978881] Forced hostmode error: a full/low-speed device attached but high-speed mode selected

[ 5017.041290] usb 1-1: device descriptor read/64, error -71

[ 5022.150909] usb 1-1: khubd timed out on ep0in len=0/64

[ 5027.150756] usb 1-1: khubd timed out on ep0in len=0/64

[ 5027.213226] Forced hostmode error: a full/low-speed device attached but high-speed mode selected

[ 5027.275726] usb 1-1: device descriptor read/64, error -19

[ 5027.447509] Forced hostmode error: a full/low-speed device attached but high-speed mode selected

[ 5027.510101] usb 1-1: new high speed USB device using musb_hdrc and address 100

[ 5027.931884] usb 1-1: device not accepting address 100, error -19

[ 5027.994445] Forced hostmode error: a full/low-speed device attached but high-speed mode selected

[ 5028.056976] usb 1-1: new high speed USB device using musb_hdrc and address 101

[ 5028.478851] usb 1-1: device not accepting address 101, error -19

[ 5028.478942] hub 1-0:1.0: unable to enumerate USB device on port 1

[ 5028.479003] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 5028.479064] hub 1-0:1.0: port 1 enable change, status 00000501

[ 5031.197570] hub 1-0:1.0: hub_suspend

[ 5031.197631] usb usb1: bus auto-suspend

[ 5035.071289] usb usb1: usb resume

[ 5035.088043] hub 1-0:1.0: hub_resume

[ 5035.088104] hub 1-0:1.0: port 1: status 0101 change 0001

[ 5035.197418] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[ 5035.197448] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s

[ 5035.260192] musb_h_ep0_irq 1083: no URB for end 0

[ 5035.322631] usb 1-1: new high speed USB device using musb_hdrc and address 102

[ 5035.471832] usb 1-1: default language 0x0409

[ 5035.474060] usb 1-1: uevent

[ 5035.474273] usb 1-1: usb_probe_device

[ 5035.474304] usb 1-1: configuration #1 chosen from 1 choice

[ 5035.474456] usb 1-1: adding 1-1:1.0 (config #1, interface 0)

[ 5035.474700] usb 1-1:1.0: uevent

[ 5035.474945] libusual 1-1:1.0: usb_probe_interface

[ 5035.475006] libusual 1-1:1.0: usb_probe_interface - got id

[ 5035.475189] usb-storage 1-1:1.0: usb_probe_interface

[ 5035.475250] usb-storage 1-1:1.0: usb_probe_interface - got id

[ 5035.575561] scsi7 : SCSI emulation for USB Mass Storage devices

[ 5035.581970] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '102'

[ 5035.582672] usb 1-1: New USB device found, idVendor=0a16, idProduct=1200

[ 5035.582733] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 5035.582763] usb 1-1: Product: TDZAPG4

[ 5035.582794] usb 1-1: Manufacturer: TREK

[ 5035.582794] usb 1-1: SerialNumber: f9d7ac053455f6

[ 5035.582855] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 5035.582946] hub 1-0:1.0: port 1 enable change, status 00000503

[ 5035.614562] usb-storage: device found at 102

[ 5035.614624] usb-storage: waiting for device to settle before scanning

[ 5040.613159] usb-storage: device scan complete

[ 5040.615081] scsi 7:0:0:0: Direct-Access     TREK     TDZAPG4          1.00 PQ: 0 ANSI: 2

[ 5040.636291] sd 7:0:0:0: [sda] 1974271 512-byte hardware sectors: (1.01 GB/963 MiB)

[ 5040.636840] sd 7:0:0:0: [sda] Write Protect is off

[ 5040.636901] sd 7:0:0:0: [sda] Mode Sense: 00 00 00 00

[ 5040.636932] sd 7:0:0:0: [sda] Assuming drive cache: write through

[ 5040.644287] sd 7:0:0:0: [sda] 1974271 512-byte hardware sectors: (1.01 GB/963 MiB)

[ 5040.644805] sd 7:0:0:0: [sda] Write Protect is off

[ 5040.644836] sd 7:0:0:0: [sda] Mode Sense: 00 00 00 00

[ 5040.644866] sd 7:0:0:0: [sda] Assuming drive cache: write through

[ 5040.644897]  sda: sda1

[ 5040.769805] sd 7:0:0:0: [sda] Attached SCSI removable disk

[ 5078.587493] Forced hostmode error: no device attached

[ 5078.587615] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 5078.587677] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s

[ 5078.587677] usb 1-1: USB disconnect, address 102

[ 5078.587707] usb 1-1: unregistering device

[ 5078.587707] usb 1-1: usb_disable_device nuking all URBs

[ 5078.587738] usb 1-1: unregistering interface 1-1:1.0

[ 5078.610717] usb 1-1:1.0: uevent

[ 5078.611541] usb 1-1: uevent

[ 5078.767822] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101

[ 5078.892761] usb 1-1: new high speed USB device using musb_hdrc and address 103

[ 5079.042022] usb 1-1: default language 0x0409

[ 5079.043243] usb 1-1: uevent

[ 5079.043365] usb 1-1: usb_probe_device

[ 5079.043395] usb 1-1: configuration #1 chosen from 1 choice

[ 5079.043487] usb 1-1: adding 1-1:1.0 (config #1, interface 0)

[ 5079.043609] usb 1-1:1.0: uevent

[ 5079.043731] libusual 1-1:1.0: usb_probe_interface

[ 5079.043762] libusual 1-1:1.0: usb_probe_interface - got id

[ 5079.048248] usb-storage 1-1:1.0: usb_probe_interface

[ 5079.048339] usb-storage 1-1:1.0: usb_probe_interface - got id

[ 5079.051635] scsi8 : SCSI emulation for USB Mass Storage devices

[ 5079.058898] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '103'

[ 5079.059265] usb 1-1: New USB device found, idVendor=0a16, idProduct=1200

[ 5079.059295] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 5079.059326] usb 1-1: Product: TDZAPG4

[ 5079.059326] usb 1-1: Manufacturer: TREK

[ 5079.059356] usb 1-1: SerialNumber: f9d7ac053455f6

[ 5079.059356] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 5079.059417] hub 1-0:1.0: port 1 enable change, status 00000503

[ 5079.065979] usb-storage: device found at 103

[ 5079.065979] usb-storage: waiting for device to settle before scanning

[ 5081.891723] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1

[ 5085.066223] usb-storage: device scan complete

[ 5091.260192] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[ 5091.322631] usb 1-1: reset high speed USB device using musb_hdrc and address 103

[ 5096.322418] usb 1-1: usb-storage timed out on ep0in len=0/64

Re: Thread for problems getting USB hostmode working.

I had H-E-N working and could mount some flash drives or a keyboard. After I broke off my USB port and re-soldered it I can connect to a Linux box in slave mode and browse my N900 but I cant attach devices in h-e-n anymore. I even tried reinstalling kernel-power and h-e-n. I cant imagine this is a hardware issue but am not sure what the issue is or even if it is connected to the broken USB port since it has been a while since I have used h-e-n.
I actually get some response from the kernel messages screen saying a forced hostmode error high speed selected but full/low speed device attached. I also don't get any LED's on the flash drive or my still not working USB-RJ-45 wired ethernet adapter when I switch v-boost on.
since I have every expectation of fixing the problem I am also curious if there will be an upgrade to the kernel module to allow rw from flash drives.

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by mveplus (Post 995023)

Dear Mveplus,

Thanks a lot for your assistance. Really appreciated that.

Anyway can you confirm is there any wrong config in the z98_usbEth.rules.

And can you provide the step by step before and until i run the h-e-n. Maybe i had miss some step.

BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
#Installed as part of the usbLAN package

#UDEV rules to bring up and shutdown Eth0 interface when USB network adapter is
SUBSYSTEMS=="usb", ATTRS{idProduct}=="8150", ACTION=="add", RUN+="/usr/sbin/usb

SUBSYSTEMS=="usb", ATTRS{idProduct}=="7830", ACTION=="add", RUN+="/usr/sbin/usb

SUBSYSTEMS=="usb", ATTRS{idProduct}=="8101", ACTION=="add", RUN+="/usr/sbin/usb

SUBSYSTEMS=="usb", ACTION=="remove", RUN+="/usr/sbin/usbEthDown.sh"
~

Re: Thread for problems getting USB hostmode working.

Dear Mveplus,

I had purchased new usb adapter managed to get ip when connected to linux dhcp server but when i connected to normal cisco router iam not managed to get the IP with dmesg eth0: no IPv6 routers present and /etc/udhcpc/default.script: exec: line 7: /etc/udhcpc/default.zeroconf: not found.

How to disable the IPV6? and also regarding the missing file default.zeroconf: not found

2.6.28/drivers/usb/core/inode.c: creating file '003'
[ 852.006439] usb 1-1: New USB device found, idVendor=9710, idProduct=7830
[ 852.006469] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 852.006500] usb 1-1: Product: USB-MAC Controller
[ 852.006500] usb 1-1: Manufacturer: Moschip Semiconductor
[ 852.006530] usb 1-1: SerialNumber: 6e0002c5

ome/user # udhcpc
udhcpc (v0.9.9-pre) started
Sending discover...
Sending discover...
Sending discover...
Sending discover...
Lease failed:
zeroconf: address selected is 169.254.59.32
zeroconf: state is Active/Announce, Link-local address 169.254.59.32
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)
/etc/udhcpc/default.script: exec: line 7: /etc/udhcpc/default.zeroconf: not found

1704.260009] eth0: no IPv6 routers present
[ 1934.111663] slide (GPIO 71) is now closed
[ 1943.283477] proximity (GPIO 89) is now closed
[ 1944.722686] proximity (GPIO 89) is now open
[ 1996.363342] proximity (GPIO 89) is now closed
[ 2000.596069] proximity (GPIO 89) is now open
[ 2039.041351] slide (GPIO 71) is now open
/home/user #

Re: Thread for problems getting USB hostmode working.

Dear Mveplus,

Its because of the MAC address filtering at Router. No issue. work like charm,

Anyway need to know how to configure static IP and DNS.

Re: Thread for problems getting USB hostmode working.

To set static IP address root yourself then type:

Code:

ifconfig eth0 <ip-address> netmask <subnet-mask>

ifconfig eth0 up

Also add default gateway if you want Internet access:

Code:

route add default gw <default-gateway>

To specify DNS servers edit /etc/resolv.conf

Or, if you want the settings to persist reboots, just edit /etc/network/interfaces then type:

Code:

ifup eth0

Cheers.

Re: Thread for problems getting USB hostmode working.

Dear NiQ,

Noted and thanks

Re: Thread for problems getting USB hostmode working.

i am happy to report that h.e.n work my N900 with the following:
1. a SSD(Intel X25-M 120GB 2.5") without using additional power supply. I got about 1.5hr of play time from playing mp3 off the SSD from full charge and speaker on.:)

2. a powered hub where it is connected to a Seagate 750GB 2.5" SATA drive and a cheap multi-format memory card reader(ie. CF, SDHC etc) at the same time; thus allowing transfers of content from the memory cards to the drive directly.

cheers

ps: both drives are in 2.5" h/d enclosure, with JMicron USB to ATA/ATAPI Bridge

Re: Thread for problems getting USB hostmode working.

All,

I have a few questions about charging while USB host is enabled. I have read the post http://talk.maemo.org/showpost.php?p...&postcount=647. I have a few things that I do not understanding..

1. jOERG mentioned about booston and boostoff script, are they provided?

2. jOERG's post point to the http://enivax.net/jk/n900/charge.sh.txt. My guess is that I need to download the charge.sh.txt to N900, then rename it as charge.sh and then run it. The question is where should this script reside in the N900.

3. What is the exact command at the x-term to run the charge.sh?
should it be "charge"
or
"charge &"

4. If the device that I want to use requires power itself(ie. usb harddrive); how does one setup charging under this scenario?

thanks

Re: Thread for problems getting USB hostmode working.

m unnable to mount my flash drive...
it says no system file...
cn ny1 help???????:(

Re: Thread for problems getting USB hostmode working.

Quote:

Originally Posted by cheve (Post 1002480)

1. boostoff and booston are provided with HEN. If You have latest HEN installed, you just have that 2 commands "aboard". The'yre executed just by:

booston
boostoff

in console (not 2 at once, use only one that You want in the moment) - don't need to put anything before or after that command, but be sure that You're root. Overall, executing this commands act exact same way as enabling, for example, leafpad - You don't need to provide path to the file, just call it out from the console.

2. Good guessing - you need to download it, and put whenever You want in Your phone, except MyDocs, that by default is nk-exec. BUT, to execute THAT script, You need to provide full path to it, so putting it into root ("/") directory can be good idea. Personally, i would recommend to rename it to something like "charger", without .sh or .txt. - faster executing.

If You put it into root, You type in terminal:

/charger

(or whatever name You renamed it to). Notice the "/" - that because you must provide full path to the file. So, if you place it under "/home", to execute charger you need:

/home/charger

also, If you download it on Your desktop computer with windows/mac/whatever system that doesn't keep file permissions, You need to:

chmod 775 /charger

to make it executable - other way You get "permission denied" reply, what was the case for me.

Remember, that in my examples charge.sh.txt was renamed to "charger" (without any extensions).

Also, about executing whole thing - this is very straightforward, if You know that joerg_rw was executing many other commands to just "show" that battery is charging. you don't need to do that. to achieve charging during hostmode, You need literally 2-3 commands (depending on situation), and to have charging script downloaded and put somewhere on Your phone with executable rights.

Then, You just:

1. start hostmode as normal, select speed, vbus, enumerate, mount if You connected storage media...

2. without disabling HEN, open xterm and use:

boostoff

3. Next, do (in case that Your charging script is renamed to "charger" and put into root directory):

/charger

script will start its job... From my experience, if second output is like:

Status: 0x10 Mode: CHARGING Full: 0 WallCharger: 0 Battery Voltage: 4150 NAC: 1987 Battery level: 97 %

.. then you're all done. You can minimize xterm (DON'T close it - charging will stop after 10 seconds, if you close Xterm, because that terminates script going inside it). If You want to do something inside xterm, just click "xterminal" on upper part of the screen, then choose "new" (Yea, i know its basic thing, but i was searching for few hours how can i do something in terminal while charging during hostmode... 0_o... shadowjk kindly and mercifully brightened me up...).

But, if Your second line in output after executing "/charger" is like:

Status: 0x20 Mode: STANDBY Full: 0 WallCharger: 0 Battery Voltage: 3967 NAC: 1999 Battery level: 97 %

...then you need to press ctrl+c (that will stop script and allow You to type in same terminal window again) and execute:

/charger

...again. This time You're done for sure.

---

Side note: I don't know why in joerg_rw example we must use "/charger" twice. For me, 99% times it work just after first try - i double checked, if charging really goes on. But, literally one time, i get STANDBY - so, i just followed joerg_rw advice, ctrl-c'ing. I don't know why this work like that - i think joerg_rw know, so we can ask him ;)

Last but not least, Your question about externally-powered things, like hard disc. I suppose that you know about "y-cable" thing to charge while hostmode, OR - method that i prefer - USB 2.0 active HUB (this way You DON'T need "y-cable"). Then, if your HDD or CD/DVd is powered externally by own power supply - that doesn't matter for charging while hostmode at all. HDD use own power, and Your N900 use Y-cable power or active HUB power.

IF HDD need to draw much power from USB line, Y-cable or powered HUB should provide it - again, you don't care about that. Sometimes, HDD's got own Y-cable, that you literally plug into 2 ports, to draw 1A instead of 500 mA (500mA is current limit for 1 port) - in that case, active HUB is a must (or You just use additional 5V charger with USB port - this way, You need to use additional wall plug, and you plug powering part of HDD's y-cable to that charger).

Another side note - sometimes, externally powered things like HDD's and USB printers also provide 5V at their USB PLUG (not port... don't ask about design). This way You can charge during hostmode by just connecting that peripheral to Your N900, without Y-cable or active HUB ;) It's funny to see how Your N900 print using printer, and the same time it is CHARGED by that printer... But, i encountered literally ONE printer like that. Normally, externally powered printers doesn't need current on USB plug, neither doesn't provide it.

If You got any additional question, just feel free to ask. And, don't be scarred by length of that post - i tried to cover every aspect of charging during USB. In most cases it is as easy as executing 2 commands in xTerm...

Re: Thread for problems getting USB hostmode working.

Estel,
many thanks for this excellent explanation. :-D

cheers
jOERG

Re: Thread for problems getting USB hostmode working.

Hi,

I tried hostmode again today and for some reasons my N900 no longer 'see' my drives. I was able to attached them and worked with them before with N900. I checked the hostmode file, it seems that h.e.n. sees the drive, but N900 could not mount it.

I have power kernel 47. Would appreciate some help.

thank you for your time,

cheers,

Attached is the hostmode file.

Re: Thread for problems getting USB hostmode working.

@Estel, thank for giving me the helping hand.

I am able to connect(to both of my drives) again. The solution: one really needs to SLOW DOWN. For my case, I select the speed, then set the VBUS boost on, then select "enumerate" and then wait for at least 5 seconds(I went to check the log to ensure that no newer entries are written to it), and then select the 'mount'.

As for charging, I got
sleep 1 status 0x00
status: 0x00 mode: STANDBY FULL

so, I don't know whether it is working for me or not; but my guess is that it is not working. The 'status:0x00 mode: STANDBY FULL' message repeat itself at the xterm with the value of Battery Voltage dropping at each successive message.

What is the difference between status 0x00 and 0x02?

I have tried the CTRL-C and then re-executed the charger script; but I got the same result(ie. status 0x00 and STANDBY FULL)

One more observation, there is about 3 to 5 seconds wait time between the 1st and then the showing of the 2nd messages.

As a recap, I connect the stuffs as follows:
1. 4-port usb hub connects to the wall A/C.
2. n900 connects to the hub with a straight usb cable
3. usb drive connects to the hub with a Y-cable

Cheers,

Re: Thread for problems getting USB hostmode working.

Are You sure that Your battery isn't full or almost full, when You try to charge it while hostmode? I'll try to replicate this after my next charging cycle, but message seems quite self-explanatory. Can You post here Your voltage readings, when You got that message? Also, could You try hostmode charging with battery ~50% (or lower, just to be sure)?

I'm glad that You succeed with mounting. Hope that charging will go as well.

Re: Thread for problems getting USB hostmode working.

You're reading it wrong for starters,

it's not "STANDBY FULL", it's:

Status: 0x00
Mode: Standby
Full: 0
Wall: 0

Status code is directly from the hw chip:
0 - Standby
1 - Charge in progress
2 - Charge done

Mode and Full are just flags tracked by the charge script for its own use. Wall is whether wall charger has been detected.

Things to note:
The charger chip is programmed on script start. There's no error recovery. Chip resets to defaults on some error conditions.

This means in some circumstanced the charger chip can go back to its defaults, which are to charge the battery to 20-40% at a slow rate.

The logs written in /home/user/MyDocs/ can provide some hints to whether there has been a fault condition.

Re: Thread for problems getting USB hostmode working.

USB sticks, mouse, and keyboard are working for me, but not my SD card reader (it does not show up as /dev/sd* and mount does not work). I get the following from dmesg:

Code:

[15168.828552] hub 1-0:1.0: hub_suspend

[15168.828643] usb usb1: bus auto-suspend

[15168.828674] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15168.828735] usb usb1: bus suspend fail, err -16

[15168.828765] hub 1-0:1.0: hub_resume

[15168.828857] hub 1-0:1.0: port 1: status 0501 change 0000

[15168.828948] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15168.829010] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15168.953704] usb 1-1: new high speed USB device using musb_hdrc and address 36

[15169.078674] usb 1-1: device descriptor read/64, error -71

[15169.313018] usb 1-1: device descriptor read/64, error -71

[15169.547271] usb 1-1: new high speed USB device using musb_hdrc and address 37

[15169.672210] usb 1-1: device descriptor read/64, error -71

[15169.906768] usb 1-1: device descriptor read/64, error -71

[15170.141174] usb 1-1: new high speed USB device using musb_hdrc and address 38

[15170.562866] usb 1-1: device not accepting address 38, error -71

[15170.688079] usb 1-1: new high speed USB device using musb_hdrc and address 39

[15171.109710] usb 1-1: device not accepting address 39, error -71

[15171.109802] hub 1-0:1.0: unable to enumerate USB device on port 1

[15171.109832] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15171.109893] hub 1-0:1.0: port 1 enable change, status 00000501

[15173.262542] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1

[15173.828399] hub 1-0:1.0: hub_suspend

[15173.828460] usb usb1: bus auto-suspend

[15183.461425] slide (GPIO 71) is now closed

[15199.992675] slide (GPIO 71) is now open

[15257.087585] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2

[15259.161956] Forced hostmode error: no device attached

[15259.162048] usb usb1: usb resume

[15259.179992] hub 1-0:1.0: hub_resume

[15259.180053] hub 1-0:1.0: port 1: status 0101 change 0001

[15259.289581] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15259.289642] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s

[15259.414672] usb 1-1: new high speed USB device using musb_hdrc and address 40

[15259.539550] usb 1-1: device descriptor read/64, error -71

[15259.773956] usb 1-1: device descriptor read/64, error -71

[15260.008361] usb 1-1: new high speed USB device using musb_hdrc and address 41

[15260.133361] usb 1-1: device descriptor read/64, error -71

[15260.367706] usb 1-1: device descriptor read/64, error -71

[15260.602233] usb 1-1: new high speed USB device using musb_hdrc and address 42

[15261.023956] usb 1-1: device not accepting address 42, error -71

[15261.148925] usb 1-1: new high speed USB device using musb_hdrc and address 43

[15261.570648] usb 1-1: device not accepting address 43, error -71

[15261.570770] hub 1-0:1.0: unable to enumerate USB device on port 1

[15261.570800] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15261.570831] hub 1-0:1.0: port 1 enable change, status 00000501

[15263.828552] hub 1-0:1.0: hub_suspend

[15263.828613] usb usb1: bus auto-suspend

[15263.828643] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15263.828704] usb usb1: bus suspend fail, err -16

[15263.828735] hub 1-0:1.0: hub_resume

[15263.828796] hub 1-0:1.0: port 1: status 0501 change 0000

[15263.828948] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15263.829010] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15263.953582] usb 1-1: new high speed USB device using musb_hdrc and address 44

[15264.078491] usb 1-1: device descriptor read/64, error -71

[15264.312957] usb 1-1: device descriptor read/64, error -71

[15264.547332] usb 1-1: new high speed USB device using musb_hdrc and address 45

[15264.672271] usb 1-1: device descriptor read/64, error -71

[15264.906860] usb 1-1: device descriptor read/64, error -71

[15265.141082] usb 1-1: new high speed USB device using musb_hdrc and address 46

[15265.562988] usb 1-1: device not accepting address 46, error -71

[15265.687896] usb 1-1: new high speed USB device using musb_hdrc and address 47

[15266.110015] usb 1-1: device not accepting address 47, error -71

[15266.110168] hub 1-0:1.0: unable to enumerate USB device on port 1

[15266.110229] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15266.110290] hub 1-0:1.0: port 1 enable change, status 00000501

[15268.828674] hub 1-0:1.0: hub_suspend

[15268.828735] usb usb1: bus auto-suspend

[15268.828796] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15268.828826] usb usb1: bus suspend fail, err -16

[15268.828857] hub 1-0:1.0: hub_resume

[15268.828948] hub 1-0:1.0: port 1: status 0501 change 0000

[15268.829040] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15268.829101] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15268.953643] usb 1-1: new high speed USB device using musb_hdrc and address 48

[15269.079284] usb 1-1: device descriptor read/64, error -71

[15269.313049] usb 1-1: device descriptor read/64, error -71

[15269.547424] usb 1-1: new high speed USB device using musb_hdrc and address 49

[15269.672363] usb 1-1: device descriptor read/64, error -71

[15269.906799] usb 1-1: device descriptor read/64, error -71

[15270.141082] usb 1-1: new high speed USB device using musb_hdrc and address 50

[15270.562988] usb 1-1: device not accepting address 50, error -71

[15270.687927] usb 1-1: new high speed USB device using musb_hdrc and address 51

[15271.109924] usb 1-1: device not accepting address 51, error -71

[15271.110076] hub 1-0:1.0: unable to enumerate USB device on port 1

[15271.110137] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15271.110198] hub 1-0:1.0: port 1 enable change, status 00000501

[15273.828552] hub 1-0:1.0: hub_suspend

[15273.828643] usb usb1: bus auto-suspend

[15273.828674] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15273.828704] usb usb1: bus suspend fail, err -16

[15273.828735] hub 1-0:1.0: hub_resume

[15273.828826] hub 1-0:1.0: port 1: status 0501 change 0000

[15273.828918] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15273.828979] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15273.953552] usb 1-1: new high speed USB device using musb_hdrc and address 52

[15274.078704] usb 1-1: device descriptor read/64, error -71

[15274.312988] usb 1-1: device descriptor read/64, error -71

[15274.547332] usb 1-1: new high speed USB device using musb_hdrc and address 53

[15274.672302] usb 1-1: device descriptor read/64, error -71

[15274.906799] usb 1-1: device descriptor read/64, error -71

[15275.141052] usb 1-1: new high speed USB device using musb_hdrc and address 54

[15275.562957] usb 1-1: device not accepting address 54, error -71

[15275.688049] usb 1-1: new high speed USB device using musb_hdrc and address 55

[15276.110015] usb 1-1: device not accepting address 55, error -71

[15276.110168] hub 1-0:1.0: unable to enumerate USB device on port 1

[15276.110229] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15276.110290] hub 1-0:1.0: port 1 enable change, status 00000501

[15278.828735] hub 1-0:1.0: hub_suspend

[15278.828826] usb usb1: bus auto-suspend

[15278.828857] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15278.828887] usb usb1: bus suspend fail, err -16

[15278.828918] hub 1-0:1.0: hub_resume

[15278.829010] hub 1-0:1.0: port 1: status 0501 change 0000

[15278.829101] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15278.829162] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15278.953674] usb 1-1: new high speed USB device using musb_hdrc and address 56

[15279.078704] usb 1-1: device descriptor read/64, error -71

[15279.312988] usb 1-1: device descriptor read/64, error -71

[15279.547393] usb 1-1: new high speed USB device using musb_hdrc and address 57

[15279.672485] usb 1-1: device descriptor read/64, error -71

[15279.906860] usb 1-1: device descriptor read/64, error -71

[15280.141082] usb 1-1: new high speed USB device using musb_hdrc and address 58

[15280.562957] usb 1-1: device not accepting address 58, error -71

[15280.688568] usb 1-1: new high speed USB device using musb_hdrc and address 59

[15281.109954] usb 1-1: device not accepting address 59, error -71

[15281.110046] hub 1-0:1.0: unable to enumerate USB device on port 1

[15281.110076] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15281.110107] hub 1-0:1.0: port 1 enable change, status 00000501

[15283.828643] hub 1-0:1.0: hub_suspend

[15283.828704] usb usb1: bus auto-suspend

[15283.828735] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15283.828796] usb usb1: bus suspend fail, err -16

[15283.828826] hub 1-0:1.0: hub_resume

[15283.828887] hub 1-0:1.0: port 1: status 0501 change 0000

[15283.828979] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15283.829040] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15283.953735] usb 1-1: new high speed USB device using musb_hdrc and address 60

[15284.078735] usb 1-1: device descriptor read/64, error -71

[15284.313079] usb 1-1: device descriptor read/64, error -71

[15284.547363] usb 1-1: new high speed USB device using musb_hdrc and address 61

[15284.672546] usb 1-1: device descriptor read/64, error -71

[15284.911956] usb 1-1: device descriptor read/64, error -71

[15285.143707] usb 1-1: new high speed USB device using musb_hdrc and address 62

[15285.562988] usb 1-1: device not accepting address 62, error -71

[15285.688232] usb 1-1: new high speed USB device using musb_hdrc and address 63

[15286.109802] usb 1-1: device not accepting address 63, error -71

[15286.109893] hub 1-0:1.0: unable to enumerate USB device on port 1

[15286.109924] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15286.109954] hub 1-0:1.0: port 1 enable change, status 00000501

[15288.828430] hub 1-0:1.0: hub_suspend

[15288.828491] usb usb1: bus auto-suspend

[15288.828491] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15288.828521] usb usb1: bus suspend fail, err -16

[15288.828521] hub 1-0:1.0: hub_resume

[15288.828582] hub 1-0:1.0: port 1: status 0501 change 0000

[15288.828613] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15288.828643] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15288.953643] usb 1-1: new high speed USB device using musb_hdrc and address 64

[15289.078582] usb 1-1: device descriptor read/64, error -71

[15289.312957] usb 1-1: device descriptor read/64, error -71

[15289.547271] usb 1-1: new high speed USB device using musb_hdrc and address 65

[15289.672454] usb 1-1: device descriptor read/64, error -71

[15289.906860] usb 1-1: device descriptor read/64, error -71

[15290.141143] usb 1-1: new high speed USB device using musb_hdrc and address 66

[15290.562957] usb 1-1: device not accepting address 66, error -71

[15290.687866] usb 1-1: new high speed USB device using musb_hdrc and address 67

[15291.109710] usb 1-1: device not accepting address 67, error -71

[15291.109802] hub 1-0:1.0: unable to enumerate USB device on port 1

[15291.109832] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15291.109832] hub 1-0:1.0: port 1 enable change, status 00000501

[15293.828491] hub 1-0:1.0: hub_suspend

[15293.828552] usb usb1: bus auto-suspend

[15293.828552] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15293.828582] usb usb1: bus suspend fail, err -16

[15293.828582] hub 1-0:1.0: hub_resume

[15293.828643] hub 1-0:1.0: port 1: status 0501 change 0000

[15293.828674] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15293.828704] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15293.953491] usb 1-1: new high speed USB device using musb_hdrc and address 68

[15294.078582] usb 1-1: device descriptor read/64, error -71

[15294.312927] usb 1-1: device descriptor read/64, error -71

[15294.547637] usb 1-1: new high speed USB device using musb_hdrc and address 69

[15294.672546] usb 1-1: device descriptor read/64, error -71

[15294.906646] usb 1-1: device descriptor read/64, error -71

[15295.141113] usb 1-1: new high speed USB device using musb_hdrc and address 70

[15295.562988] usb 1-1: device not accepting address 70, error -71

[15295.687927] usb 1-1: new high speed USB device using musb_hdrc and address 71

[15296.109832] usb 1-1: device not accepting address 71, error -71

[15296.109924] hub 1-0:1.0: unable to enumerate USB device on port 1

[15296.109954] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15296.109985] hub 1-0:1.0: port 1 enable change, status 00000501

[15298.828521] hub 1-0:1.0: hub_suspend

[15298.828582] usb usb1: bus auto-suspend

[15298.828582] musb_bus_suspend 2266: trying to suspend as a_host is_active=1

[15298.828613] usb usb1: bus suspend fail, err -16

[15298.828613] hub 1-0:1.0: hub_resume

[15298.828674] hub 1-0:1.0: port 1: status 0501 change 0000

[15298.828704] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15298.828735] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s

[15298.954345] usb 1-1: new high speed USB device using musb_hdrc and address 72

[15299.078643] usb 1-1: device descriptor read/64, error -71

[15299.312988] usb 1-1: device descriptor read/64, error -71

[15299.547363] usb 1-1: new high speed USB device using musb_hdrc and address 73

[15299.672485] usb 1-1: device descriptor read/64, error -71

[15299.906921] usb 1-1: device descriptor read/64, error -71

[15300.141265] usb 1-1: new high speed USB device using musb_hdrc and address 74

[15300.563018] usb 1-1: device not accepting address 74, error -71

[15300.688140] usb 1-1: new high speed USB device using musb_hdrc and address 75

[15301.109802] usb 1-1: device not accepting address 75, error -71

[15301.109954] hub 1-0:1.0: unable to enumerate USB device on port 1

[15301.110015] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15301.110076] hub 1-0:1.0: port 1 enable change, status 00000501

[15302.943969] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1

[15303.828643] hub 1-0:1.0: hub_suspend

[15303.828704] usb usb1: bus auto-suspend

Re: Thread for problems getting USB hostmode working.

Also I tried to use an (unpowered) hub to use mouse and keyboard both with it and that did not work, I get the following from dmesg:

Code:

[15680.245086] wlan0: roaming signal from driver, sending LOWSIGNAL

[15687.106628] wlan0: roaming signal from driver, sending HIGHSIGNAL

[15738.547912] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2

[15739.313018] Forced hostmode error: no device attached

[15739.313110] usb usb1: usb resume

[15739.336486] hub 1-0:1.0: hub_resume

[15739.336578] hub 1-0:1.0: port 1: status 0101 change 0001

[15739.445831] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000

[15739.445892] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s

[15739.571563] usb 1-1: new high speed USB device using musb_hdrc and address 80

[15739.695953] usb 1-1: device descriptor read/64, error -71

[15739.930297] usb 1-1: device descriptor read/64, error -71

[15740.164733] usb 1-1: new high speed USB device using musb_hdrc and address 81

[15740.289581] usb 1-1: device descriptor read/64, error -71

[15740.523986] usb 1-1: device descriptor read/64, error -71

[15740.758239] usb 1-1: new high speed USB device using musb_hdrc and address 82

[15741.180267] usb 1-1: device not accepting address 82, error -71

[15741.305206] usb 1-1: new high speed USB device using musb_hdrc and address 83

[15741.727111] usb 1-1: device not accepting address 83, error -71

[15741.727233] hub 1-0:1.0: unable to enumerate USB device on port 1

[15741.727294] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002

[15741.727355] hub 1-0:1.0: port 1 enable change, status 00000501

[15742.515472] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1

[15743.828521] hub 1-0:1.0: hub_suspend

[15743.828582] usb usb1: bus auto-suspend

Any help would be appreciated. Thanks :)

Re: Thread for problems getting USB hostmode working.

It MAY be the same problem cheve had with mounting - being too hasty. until i learned to click "VBUST ON" 2-3 seconds after plugging cable, and "Enumerate" after another 6-7 seconds, many times i get same errors.

Also, remember to always unplug device (be it HUB, stick, mouse, whatever) from N900 before trying to start from scratch. Cable and adapter can sit on N900, but nothing can be connected to them. You can connect anything only after setting speed (then, do not exceed 3-4 seconds before You click VBUS ON, but also don't do it 0.1 second after plugging device - not too late, not too early), otherwise you get exact same errors. At least, that is in my case, always, 100% reproduceable.

On side note, i would NOT recommend plugging and unplugging again cable direct from N900 when You want start "hostmod(d)ing" from scratch - it's better to unplug device/adapter from end of the cable. We don't want to stress too much our N900 USB port...