Thread for problems getting USB hostmode working.

[casper27]

Post all problems with getting USB Hostmost working on different USB peripherals here.
It is Beta software but has been proved to work by numerous people on here so its mostly a case by case problem.
The developers are getting mighty P*ssed with winey posts and duplicate questions on the other thread.

[werebug]

Is it possible to use this on Ubuntu

So I can use keyboard and mouse

[esthreel]

i am having problem with external HDD, flash and mouse worked great. So the drive is 3.5 inch and has power supply, the size is 1TB and it is formatted as NTFS. I know i have to open terminal sudo gainroot and then modprobe ntfs. When I have to do this? after I opn hen? Thanks.

[MohammadAG]

Before you mount, however you might need extra packages (that may/may not be available in maemo) for write support.

[esthreel]

Before you mount, however you might need extra packages (that may/may not be available in maemo) for write support.

I got this error.
http://www.ipix.lt/images/11686382.png

[MohammadAG]

I don't have any NTFS drives, so I can't test, but it should be possible to mount /dev/sda1 /mnt in terminal and open it in filebox

[esthreel]

I don't have any NTFS drives, so I can't test, but it should be possible to mount /dev/sda1 /mnt in terminal and open it in filebox

So the default file manager will not see any drives that are NTFS?

[MohammadAG]

So the default file manager will not see any drives that are NTFS?


[ 8916.612762] usb 1-1: new high speed USB device using musb_hdrc and address 4
[ 8916.791564] usb 1-1: default language 0x0409
[ 8916.842742] usb 1-1: uevent
[ 8916.842864] usb 1-1: usb_probe_device
[ 8916.842895] usb 1-1: configuration #1 chosen from 1 choice
[ 8916.845275] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 8916.845428] usb 1-1:1.0: uevent
[ 8916.845581] libusual 1-1:1.0: usb_probe_interface
[ 8916.845611] libusual 1-1:1.0: usb_probe_interface - got id
[ 8916.845672] usb-storage 1-1:1.0: usb_probe_interface
[ 8916.845703] usb-storage 1-1:1.0: usb_probe_interface - got id
[ 8916.851623] scsi2 : SCSI emulation for USB Mass Storage devices
[ 8916.857360] usb-storage: device found at 4
[ 8916.857391] usb-storage: waiting for device to settle before scanning
[ 8916.858276] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '004'
[ 8916.858581] usb 1-1: New USB device found, idVendor=059f, idProduct=1013
[ 8916.858612] usb 1-1: New USB device strings: Mfr=10, Product=11, SerialNumber=12
[ 8916.858612] usb 1-1: Product: LaCie Hard Disk
[ 8916.858642] usb 1-1: Manufacturer: LaCie
[ 8916.858642] usb 1-1: SerialNumber: 2007102500100BB3
[ 8916.858673] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[ 8916.858703] hub 1-0:1.0: port 1 enable change, status 00000503
[ 8920.256958] twl4030_keypad twl4030_keypad: Spurious key event 4-2
[ 8920.500457] twl4030_keypad twl4030_keypad: Spurious key event 4-2
[ 8921.856048] usb-storage: device scan complete
[ 8921.857299] scsi 2:0:0:0: Direct-Access ST350082 0AS PQ: 0 ANSI: 2 CCS
[ 8921.870544] sd 2:0:0:0: [sda] 1953546336 512-byte hardware sectors: (1.00 TB/931 GiB)
[ 8921.871276] sd 2:0:0:0: [sda] Write Protect is off
[ 8921.871307] sd 2:0:0:0: [sda] Mode Sense: 00 38 00 00
[ 8921.871307] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 8921.872131] sd 2:0:0:0: [sda] 1953546336 512-byte hardware sectors: (1.00 TB/931 GiB)
[ 8921.872863] sd 2:0:0:0: [sda] Write Protect is off
[ 8921.872863] sd 2:0:0:0: [sda] Mode Sense: 00 38 00 00
[ 8921.872894] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 8921.872924] sda: sda1
[ 8921.917846] sd 2:0:0:0: [sda] Attached SCSI disk
/home/user #


If you mount under /media, it should.
mkdir -p /media/ntfs
mount /dev/sda1 /media/ntfs

[esthreel]

If you mount under /media, it should.
mkdir -p /media/ntfs
mount /dev/sda1 /media/ntfs

It worked all like a charm, thanks.

http://www.ipix.lt/images/42508838.png

But the problem is that when I open it from list with default manager i see text (no files), it sees the disk as empty. If i go to filebox I see them all. The bigger problem is that when i try to open a file I get for jpg / pdf - file format not supported, for music / video - file not found. Any ideas?

P.S. http://talk.maemo.org/archive/index.php/t-17811.html Any one looked on this?

[Larswad]

@esthreel: This is basic mounting knowledge for linux. You have to give rights to the user (since you run the filemanager as 'user').
you first need the id of your user and users group:

to find out, enter:


id user

and you will get the user's id. (You will probably get 29999 for both 'user' id and the 'users' group).

now, as root:


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


Replace the 29999 with the id you got, if it was different of course.
Now, you should be able to access your files from the file manager.
Good luck.

[esthreel]

@esthreel: This is basic mounting knowledge for linux. You have to give rights to the user (since you run the filemanager as 'user').
you first need the id of your user and users group:

to find out, enter:


id user

and you will get the user's id. (You will probably get 29999 for both 'user' id and the 'users' group).

now, as root:


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


Replace the 29999 with the id you got, if it was different of course.
Now, you should be able to access your files from the file manager.
Good luck.

Thanks, I will try this later. I am new to Linux :) (My goal if this works would be making this into QBW button.)

Update
It does work! Nice one Larswad.

Update 2
I have a working queen beecon mount button. Thanks again for the script.

P.S This is a killer feature, no, really battery dies faster than it takes to charge :D

[lifenexus]

Thanks, I will try this later. I am new to Linux :) (My goal if this works would be making this into QBW button.)

Update
It does work! Nice one Larswad.

Update 2
I have a working queen beecon mount button. Thanks again for the script.

P.S This is a killer feature, no, really battery dies faster than it takes to charge :D

i mount my ntfs hard drive all the time. mount to any folder then view its contents from filebox by going to that loaction

[IzzehO]

Anyone had any luck with a Microsoft Wireless desktop working? I've still been unable to get it to work beyond being recognized. Its a shame too as my 2 other keyboards and mice including another wireless set work (but this is for my main desktop, whereas the MS one is just sitting around).

Also do these new Keyboard scripts that have popped up bring anything new to the party in that regard? or is it just the same stuff from the BT-HID repackaged?

[Temporal]

May I ask if is it normal that my device doesn't send ANY energy through USB? I tried to see the voltage between pins 1-4 and I got ZERO.

Looks like dead. I had to uninstall the power kernel because it broke the maemo-pc-connectivity through USB, but I don't know if it is incompatibility between power-kernel AND pc-connectivity OR USB-hostmode and PC-Connectivity trying to use it for other purposes...

Just for the heads up, when I did lsusb -v, sometimes I got NOTHING and sometimes it showed the maemo 45 hostmode etc, but without anything, even by plugging two different self powered usb hubs.

[lifenexus]

May I ask if is it normal that my device doesn't send ANY energy through USB? I tried to see the voltage between pins 1-4 and I got ZERO.

Looks like dead. I had to uninstall the power kernel because it broke the maemo-pc-connectivity through USB, but I don't know if it is incompatibility between power-kernel AND pc-connectivity OR USB-hostmode and PC-Connectivity trying to use it for other purposes...

Just for the heads up, when I did lsusb -v, sometimes I got NOTHING and sometimes it showed the maemo 45 hostmode etc, but without anything, even by plugging two different self powered usb hubs.
about the pc connectivity, did u try the connectivity after u closed hen or when it was open?

[aligatro]

Was anyone able to make combined usb devices work (mouse+keyboard, multi slot cardreaders, etc) ? I get the "new usb device found" and correct manufacturer in the log, but can't move the pointer or type. Single devices work without any problems. (including usb mouse)

[lifenexus]

Was anyone able to make combined usb devices work (mouse+keyboard, multi slot cardreaders, etc) ? I get the "new usb device found" and correct manufacturer in the log, but can't move the pointer or type. Single devices work without any problems. (including usb mouse)

mine works. i have a genius wireless keyboard and mouse and it works. ive also tried my hp keyboard and mouse and it works too

[Farooq]

anyone please confirm what are the total requirements for usb houst mode working.
I have stock kernel and hen and m doing all the steps as one did in the youtube for the mouse but my mouse is not working.
if power kernel is required for this then please tell how to do that.

[lifenexus]

anyone please confirm what are the total requirements for usb houst mode working.
I have stock kernel and hen and m doing all the steps as one did in the youtube for the mouse but my mouse is not working.
if power kernel is required for this then please tell how to do that.

go to your app man and install "enhanced kernel for power users"
make sure its from devel repo. it should be version 45

shut down the phone completely and then restart. Remember it should be completely powered down before rebooting

then run host mode

[Farooq]

@lifenexus

If i have a 3G usb internet dongle and its linux drivers and softwate as well. is there any possibilty that i can use that with the hen.

Regards
Farooq

[lifenexus]

@lifenexus

If i have a 3G usb internet dongle and its linux drivers and softwate as well. is there any possibilty that i can use that with the hen.

Regards
Farooq

in theory yes it possible but ull have to give it a go. i have a huwaei one myself but never tried it..

[Farooq]

in theory yes it possible but ull have to give it a go. i have a huwaei one myself but never tried it..

i have the same huwaei one will u ty that ?

[lifenexus]

i have the same huwaei one will u ty that ?

if u pm me the drivers, it will save me alot of time

[Farooq]

if u pm me the drivers, it will save me alot of time

http://ptcl.com.pk/contentb.php?NID=199#drivers

this is the site of the internet provider and the list of drivers is also there. M right now using this dongle on laptop with windows xp installed. the list also contains the drivers for linux

Please if u can port that for N900

[lifenexus]

http://ptcl.com.pk/contentb.php?NID=199#drivers

this is the site of the internet provider and the list of drivers is also there. M right now using this dongle on laptop with windows xp installed. the list also contains the drivers for linux

Please if u can port that for N900

ill have a look but im no expert on linux. if i cant, ill refer some devs here

[samipower]

friends i detect that ps3 sixaxis gamepad driver not compatible with this app, or with power flasher 45,

with flasher 45 and hen my gamepad ps3 not run and without hen and flasher 45 , it run well-

i can see that mouse have energy and light but not move to much people.

and only any persons can move the mouse.

i think that the hen only run mouses of logitech or asus or ....... that only run any types , for example can run logitech mouse but not run genius mouse

[MohammadAG]

We don't really restrict mouse manufacturers, what good would that be...
If it doesn't work, try a different speed, if it doesn't work at all then it's either not following mouse standards or drawing too much power.

[joerg_rw]

POWER:
N900 in hostmode: 200mA
standard PC USB port: 500mA
UMTS 3G stick: comes with Y-cable as it needs 2 times 500mA - guess what's your chances it'll work on N900

jrbme will come with overload detection and notification

some goodies for you, if you still want to do 3G and similar power hogs:
http://www.amazon.com/CyberPower-Mobile-Battery-Powered-CP-H420MP/dp/B0002UQALQ
http://www.societyofrobots.com/robotforum/index.php?topic=5479.0
http://www.newegg.com/Product/Product.aspx?Item=N82E16817804001

[lifenexus]

POWER:
N900 in hostmode: 200mA
standard PC USB port: 500mA
UMTS 3G stick: comes with Y-cable as it needs 2 times 500mA - guess what's your chances it'll work on N900

jrbme will come with overload detection and notification

my 3g dongle runs on a single port so 500mA at the most right..

[lifenexus]

http://ptcl.com.pk/contentb.php?NID=199#drivers

this is the site of the internet provider and the list of drivers is also there. M right now using this dongle on laptop with windows xp installed. the list also contains the drivers for linux

Please if u can port that for N900

those drivers are for x86 and not exactly for armel (the cpu on n900) so it may not work. if the drivers are open source, some one can compile it for the arm cpu and it may work. so far there is nothing i can do

[Armstrong Dicksmasher]

Thanks, I will try this later. I am new to Linux :) (My goal if this works would be making this into QBW button.)

Update 2
I have a working queen beecon mount button. Thanks again for the script.

P.S This is a killer feature, no, really battery dies faster than it takes to charge :D
Can you show me how you did the QBW shortcut?
I've tried osso-xterm-e "mount -t ntfs /dev/sda1 /media/ntfs -o uid=29999,gid=29999,utf8,dmask=027,fmask=137; sudo gainroot" & but it's not working.

[lifenexus]

Can you show me how you did the QBW shortcut?
I've tried osso-xterm-e "mount -t ntfs /dev/sda1 /media/ntfs -o uid=29999,gid=29999,utf8,dmask=027,fmask=137; sudo gainroot" & but it's not working.

download and install filebox. mount the ntfs drive as such

sudo gainroot
mount -t ntfs /dev/sda1 /media/flash
Go to file box. navigate to /media/flash and you will see the files.

[sophocha]

I have a Microsoft notebook optical mouse that I`m trying to make it work.Any commands or drivers that I need to install first to make it work?I can see it`s light when I try to enumerate but that`s it, no cursor on the screen.

[Larswad]

@sophocha: You need to install hid bluetooth scripts. You can do that from the application manager. Beware though that the kinetic scrolling becomes somewhat crippled afterwards, at least in microb.
There's a separate thread for that here, just search.

[sophocha]

@sophocha: You need to install hid bluetooth scripts. You can do that from the application manager. Beware though that the kinetic scrolling becomes somewhat crippled afterwards, at least in microb.
There's a separate thread for that here, just search.

Oh, I just noticed that in microb!Bummer!

What about connecting the keyboard.How do you write numbers?It seems that whenever I type numbers they don`t show up.How do I map these?

[gabby131]

everything works awesome on the h-e-n in my case,

so if i have the audio issue on the v45 kernel-power, i cant play media files (with audio e.i mp3) from an external flash drive right?

[lpdv74]

I have h-e-n working and installed power-kernel V45. My usb stick, 2GB, formatted fat, and my cardreader with 4GD SDHC memory card are working fine. But my other usb stick, 16GB, formatted fat32, is not recognised by h-e-n.

What can I do?

[Temporal]

about the pc connectivity, did u try the connectivity after u closed hen or when it was open?It was closed. In fact, I tried after rebooting just to make sure - thanks!

Good news:
Now I was able to get a SD reader recognized and working AND recognize (but not work with) my modem. I didn't knew that I needed to install h-e-n. I thought that it was installed alongside power kernel, now that they are together, and that was then a command prompt, but I was wrong.

Bad news:
I noticed that after using h-e-n (and closing it), if I go to charge my device (and then shut the screen backlight), it will glow, whenever it needs to glow, but REALLY WEAK and then, from nowhere, goes normal again. And then, randomly, will glow weak again. I just saw that happening RIGHT NOW. I don't know why, maybe some thing is reverse charged and the it needs to wait until discharge, I just see that it does that.

I noticed too that, if I try to copy ONE BIG file(700mb) from the SD to an external SD, it will go really fast in the first 20mb, but will start to slow down up to the maximum of 200mb(in my experiences) when it will "break" - mostly will break before. I'm yet to test with other hub to see if it is a problem with my actual hub, but I'd like to let it registered. I hope someone tried to copy some file from the SD to an USB SD reader to confirm or deny that. I'm yet to test from the internal memory to the USB SD reader too.

And, finally, I guess this is related with the power kernel: It does not like to reboot. Almost always, when I ask it to REBOOT, it will reboot, but not actually boot, it will start to boot and then, turn off. Then I need to turn it on manually. Is anybody else experiencing this?

I'm yet to retry the maemo-pc-connectivity, to see if it is working.

Thanks.

[Temporal]

OBS: Sorry for not editing my last post, but its important: My n900 is not starting now |:/

I'll try to remove the battery and try again.

EDIT: Worked. Before, it was like there was no battery on it. What could have happened? (No, no OC).

[kolos]

I mentioned in "USB hostmode beta release (http://talk.maemo.org/showthread.php?t=65232&page=37)" thread that I unsuccessfully tried to connect Canon camera and Nokia N95 (PC Suite mode). Today I tried again just to get dmesg logs.

[joerg_rw]

I mentioned in "USB hostmode beta release (http://talk.maemo.org/showthread.php?t=65232&page=37)" thread that I unsuccessfully tried to connect Canon camera and Nokia N95 (PC Suite mode). Today I tried again just to get dmesg logs.

N95 looks really weird, from a fast scan it seems N95 is trying to create more than 16 devices, and that fails. ttyACM is coming up (terminal to N95), but no mass storage in first 15 devices

For Canon I see:
[ 9355.010009] usb 1-1: new full speed USB device using musb_hdrc and address 120
[ 9355.164764] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 9355.166290] usb 1-1: New USB device found, idVendor=04a9, idProduct=30b1
[ 9355.166351] usb 1-1: Product: Canon Digital Camera
[ 9355.166351] usb 1-1: Manufacturer: Canon Inc.
Then the log aborts. It seems like Canon needs an awful lot of retries, until it ends up with addr 120. Possibly this device needs some 10s of seconds to initialize after VBUS, prior to starting ENUM.

cheers
jOERG

[firstknight]

mine says unable to connect.. file system unavailable...

what is missing?

[Nightmae]

Thanks all for work on h-e-n, that successfully tested on Flash drive(SanDisk Extreme Contour 16GB), mice and keyboard =)

but how to work on lan adapter? i tested in full speed hostmode, router can detect the lan signal, but can't connect network though wired lan. I don't know how to setup by wired lan, can anyone help me?? thanks!

[lifenexus]

It was closed. In fact, I tried after rebooting just to make sure - thanks!

Good news:
Now I was able to get a SD reader recognized and working AND recognize (but not work with) my modem. I didn't knew that I needed to install h-e-n. I thought that it was installed alongside power kernel, now that they are together, and that was then a command prompt, but I was wrong.

Bad news:
I noticed that after using h-e-n (and closing it), if I go to charge my device (and then shut the screen backlight), it will glow, whenever it needs to glow, but REALLY WEAK and then, from nowhere, goes normal again. And then, randomly, will glow weak again. I just saw that happening RIGHT NOW. I don't know why, maybe some thing is reverse charged and the it needs to wait until discharge, I just see that it does that.


This is a problem which i have to. i just lock the screen and unlock after i close hen.. it works fine after

[quot]


I noticed too that, if I try to copy ONE BIG file(700mb) from the SD to an external SD, it will go really fast in the first 20mb, but will start to slow down up to the maximum of 200mb(in my experiences) when it will "break" - mostly will break before. I'm yet to test with other hub to see if it is a problem with my actual hub, but I'd like to let it registered. I hope someone tried to copy some file from the SD to an USB SD reader to confirm or deny that. I'm yet to test from the internal memory to the USB SD reader too.

And, finally, I guess this is related with the power kernel: It does not like to reboot. Almost always, when I ask it to REBOOT, it will reboot, but not actually boot, it will start to boot and then, turn off. Then I need to turn it on manually. Is anybody else experiencing this?

I'm yet to retry the maemo-pc-connectivity, to see if it is working.

Thanks.[/QUOTE]

yes. i have this problem. i have no clue what it is. i try copying a huge file, it stops at around 250-300mb.

[Nightmae]

Thanks all for work on h-e-n, that successfully tested on Flash drive(SanDisk Extreme Contour 16GB), mice and keyboard :)

but how to work on lan adapter? i tested in full speed hostmode, router can detect the lan signal, but can't connect network though wired lan. I don't know how to setup by wired lan, can anyone help me?? thanks!

[joerg_rw]

yes. i have this problem. i have no clue what it is. i try copying a huge file, it stops at around 250-300mb.
This is a general problem/bug of maemo, to be seen on all copy actions and probably related to mem/swap usage.
It also happens when copying / moving a large file from uSD to eMMC (card to MyDocs) via cmdline in osso-xterm, as well as on trying to directly copy same thing via mass storage under control of your PC.

So while this shows up in your case for USB attached storage, it basically is completely unrelated to hostmode or h-e-n


For the display part: yes, there's something odd with display dimming after restart of bme. Usually a lock&unlock of screen fixes that

/j

[firstknight]

mine says unable to connect no system file available....

also for new power kernel v45 do i still need to instal i2c-tools?

[joerg_rw]

also for new power kernel v45 do i still need to instal i2c-tools?
Yes, i2c-tools are needed to make VBUS boost possible. If Mohammad has packaged
h-e-n GUI pkg correctly, it should install i2c-tools as a dependency
/j

[kolos]

N95 looks really weird, from a fast scan it seems N95 is trying to create more than 16 devices, and that fails. ttyACM is coming up (terminal to N95), but no mass storage in first 15 devices

For Canon I see:
[ 9355.010009] usb 1-1: new full speed USB device using musb_hdrc and address 120
[ 9355.164764] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 9355.166290] usb 1-1: New USB device found, idVendor=04a9, idProduct=30b1
[ 9355.166351] usb 1-1: Product: Canon Digital Camera
[ 9355.166351] usb 1-1: Manufacturer: Canon Inc.
Then the log aborts. It seems like Canon needs an awful lot of retries, until it ends up with addr 120. Possibly this device needs some 10s of seconds to initialize after VBUS, prior to starting ENUM.

cheers
jOERG

Joerg, thanks for explanation.

About camera, I attached it in switched off state, so when I initiate VBUS it actually switch on the camera first. I will do the test also with switched on camera and post the log.

N95 has 2 partitions, phone's internal drive and microsd memory card. I will try to connect the phone in PC suite mode without microsd memory and also post the results.

I don't expect from you guys that you will provide us functionality for any device which come across our minds. I'm already exited and satisfied with current progress. I just hope that infos like this can help you to make some additional improvements.

Thanks again!

[firstknight]

Yes, i2c-tools are needed to make VBUS boost possible. If Mohammad has packaged
h-e-n GUI pkg correctly, it should install i2c-tools as a dependency
/j

hmm i tried.. and this is what i got...as per attachement....

[sygys]

I just fixed to connect my PC keyboard without installing any other programs. Awsome!

[cloud596]

@joerg_rw :

thanx for your advance from my 1st report but unfortunately I don't have any pc linux at all.

Sorry while I edit my imei suddenly i overwrite sda1 to sdb1 on last word. that was a mistake, so actually the problem is with primary hard drive on n86 it self, Icon copy , move file from n900 to 8GB sdhc and delete file inside MC from N900. as far as I know as standard format for mobile usually FAT or FAT32 not NTFS which is microsoft development.
but at part of kernel message from h-e-n it was succesfully scan and set write protected off, but while tried to copy to primary hard drive on n86, cause something I don't know its been set to read only.

I am curious so I plugged again and the reported were ?
below on attachment

[debernardis]

I've also tested two quite recent nokia smartphones, equipped with microsd adjunctive memory: an E51 and an E90.
With sfdisk -l both showed sda1 to 4 after connecting with h-e-n, which is the first weird thing because they should show two partitions only (internal and sdcard); also, the partitions appeared empty.

A cheap Chinese mp3 player with 2 gigs on board didn't get recognized in any way.

I'm not particularly interested in making those work. Anyway, if someone is interested I can attach dmesg output for each device.

All thumb drives I have work well, and this is what counts to me. Also two external hard drives with their external power supply I have, connected to a hub and from the hub to the n900, did get enumerated and could be mounted - for the NTFS one I did like in http://talk.maemo.org/showpost.php?p=872695&postcount=10

[joerg_rw]

@joerg_rw :

thanx for your advance from my 1st report but unfortunately I don't have any pc linux at all.

[...]
but at part of kernel message from h-e-n it was succesfully scan and set write protected off, but while tried to copy to primary hard drive on n86, cause something I don't know its been set to read only.

I am curious so I plugged again and the reported were ?
below on attachment
please check your log. it has several lines suggesting "USB cable defect?"
Also it seems the device is recognized as full-speed, while you're trying to connect high-speed.
In addition to my answer in other thread, I'd suggest trying a better cable/adapter combo, and also try to use different speeds in h-e-n GUI.
Also I don't know if there's such a thing, but if there is then you should select "mass storage mode" on N86, at least for initial testing. Make sure N86 doesn't try to charge from USB, this would cause problems with VBUS overload and switchoff, which also will result in hostmode failing after initial proper ENUM. To rule that out you may want to use a externally powered hub.

Thanks for the log :-)
cheers
jOERG

[stlpaul]

I'm still waiting for my USB adapter to arrive in mail before I can try to attach a real device, however:

- USB/wall charger is not attached to N900
- Start h-e-n
- Wait 5 seconds
- Close h-e-n
- Battery is now detected as having MUCH less life.

For example if I have 90% battery remaining suddenly it will have 50% remaining. If I open h-e-n for 5 seconds and quit again, suddenly N900 says my battery is dead.

(I understand that BME must be stopped for h-e-n to function and that battery monitoring won't work while it is active, I'm talking about after h-e-n has closed)

Is this normal experienced by everyone else or have I got something wrong? I'm using power45 and h-e-n 0.2-8

EDIT/Update: I decided to try "stop bme" followed by "start bme" and after issuing these commands, the battery level appears to be the normal (expeced) value again.

[kolos]

I made new logs as I promised. Now I attached already switched on camera and N95 without memory card. Between camera logs is few seconds delay.

[joerg_rw]

I'm still waiting for my USB adapter to arrive in mail before I can try to attach a real device, however:

- USB/wall charger is not attached to N900
- Start h-e-n
- Wait 5 seconds
- Close h-e-n
- Battery is now detected as having MUCH less life.

For example if I have 90% battery remaining suddenly it will have 50% remaining. If I open h-e-n for 5 seconds and quit again, suddenly N900 says my battery is dead.

(I understand that BME must be stopped for h-e-n to function and that battery monitoring won't work while it is active, I'm talking about after h-e-n has closed)

Is this normal experienced by everyone else or have I got something wrong? I'm using power45 and h-e-n 0.2-8

EDIT/Update: I decided to try "stop bme" followed by "start bme" and after issuing these commands, the battery level appears to be the normal (expeced) value again.
Don't ask me what bme is doing to guesstimate battery capacity. Maybe it gets confused by 'sudden' voltage drop, or it goes mad about somebody "messed with bq24150" - no idea. My suggestion: just ignore it. If battery really would drop at that rate, your device would melt and glow.
BME is known to store things to CAL (a persistent storage partition for all sort of small data), and maybe it decides battery has to be very near to an end when voltage is dropping by 100mV from last probe to next probe (ignoring there were arbitrary off times between). Aslo BME is known to lie about capacity. This seems in accordance with other phones. The icon is all but linear.
/j

[stlpaul]

Don't ask me what bme is doing to guesstimate battery capacity. Maybe it gets confused by 'sudden' voltage drop, or it goes mad about somebody "messed with bq24150" - no idea. My suggestion: just ignore it. If battery really would drop at that rate, your device would melt and glow.
/j

:D I was sure the battery didn't really lose full capacity in a matter of seconds.

In fact, after more repeated "stop bme" and "start bme" I can see that the readings fluctuate quite large amounts each time it is restarted in general.

so in other words "Nothing to see here. Move along."

Thanks. :)

[firstknight]

hmm i tried.. and this is what i got...as per attachement....

anyone can help me??

[kolos]

I'm attaching another log, for Patriot 16GB USB stick. For this one I needed to hit 2 times Mount before it appeared in File Manager.

[keljuk]

Is there a way to get a generic dual-stick-clone gamepad to work with n900 and the emulators... It seems to recognize it, but it has no function what so ever and none of the light light up :(

[sophocha]

I'm attaching another log, for Patriot 16GB USB stick. For this one I needed to hit 2 times Mount before it appeared in File Manager.

yeah, almost all times you need to hit it twice, I`m not sure if it`s a bug or not

[arkonosze]

Usb mouse doesn't work for me :/ I've installed bt-hid-scrpits. I can mount pendrives and card readers but when I connect mouse it doesn't react. Mouse cursor doesn't move, but mouse lights are on. Please help :D btw I have power kernel installed. I just don't know what to do :/

[impeham]

mouse works for me but i cannot see the cursor - anyone had this issue? if i click i can see it reacts but no cursor...

[SubCore]

mouse works for me but i cannot see the cursor - anyone had this issue? if i click i can see it reacts but no cursor...

you need to install bt-hid-scripts (http://maemo.org/packages/view/bt-hid-scripts/) (you don't have to download from there, it's in extras-devel) and call "showmouse" from XTerm.

but beware, it will mess up kinetic scrolling.

[impeham]

ok issue solved - i installed ExtMou and cursor is working and also a wireless mouse that previously didn't work.

[blue_led]

working devices

"Carrefour" class card reader :D
Gembird NIC-U1 ( device id 0b95:772a, ASIX chip )

card reader work fine but xD card dont mount from button . it must mount manually. PNY 32G sd card mount ok from button. other media not tested yet.
ethernet adapter detected but dhcp is useless.
I add ip, route, dns settings mannualy

[impeham]

Is there a way to get a generic dual-stick-clone gamepad to work with n900 and the emulators... It seems to recognize it, but it has no function what so ever and none of the light light up :(

it is working - i was playing with such a joystick - connected my n900 to the TV and played mame games, playstation games with the emulator, and mupen 64 - amazing - the N900 has now become a full game console...

i used mgtech joystick:
http://img.zap.co.il/pics/5/6/1/1/21601165b.gif

[impeham]

just got my order from ebay:
http://cgi.ebay.com/USB-Female-USB-Micro-Male-B-5-Pin-Adapter-/190471639753?pt=LH_DefaultDomain_0&hash=item2c58fe92c9

no extra cables, very easy to carry around.

very small and works great!

[prymus]

Anyone get a usb serial adapter working? Someone in the "[Announce] USB hostmode beta release" thread said that they did, but the one I have does not work. Mine has a Prolific PL2303 chipset in it. I never get the /dev/ttyUSB0 created. This same adapter works fine on the PC running Debian or Ubuntu. If anyone has a usb serial working, what chipset is it using?

[blue_led]

Anyone get a usb serial adapter working? Someone in the "[Announce] USB hostmode beta release" thread said that they did, but the one I have does not work. Mine has a Prolific PL2303 chipset in it. I never get the /dev/ttyUSB0 created. This same adapter works fine on the PC running Debian or Ubuntu. If anyone has a usb serial working, what chipset is it using?

power kernel 46 seems to have usbserial.ko in place but because pl2303.ko is missing ... you get the idea
diablo version of pl2303.ko don't work ( forcing mode ; got some errors revealed in dmesg )
i tried to compile a new version but i have problems with my ironport proxy and dns as usual in scratchbox.

Late edit:
I compiled pl2303.ko against 10power46 kernel.
i will test it after a long sleep ( offtopic : & my regular saturday enduro ride )

Later edit 2
i put the driver here, for convenience but i don't test it yet

[Trestry]

Is there a way to get write support for NTFS? At the moment I can see my NTFS harddisk, but I can't write files towards it. FAT and FAT32 are both working fine.

[blue_led]

in extras thre is kernel-module-ntfs. take a look.

[anapospastos]

Mount button doesnt work all the times so I m mounting manually the connected devices but they are read-only. Can someone tell me the right way to give them write permissions? I tried chmod with all the ways but no light.

[MohammadAG]

Mount button doesnt work all the times so I m mounting manually the connected devices but they are read-only. Can someone tell me the right way to give them write permissions? I tried chmod with all the ways but no light.

mount -o uid=29999,gid=29999,utf8,dmask=027,fmask=137 [dev node] [mount point]
Read the first page of this thread.

[Zas]

anyone can help me??
http://talk.maemo.org/attachment.php?attachmentid=15677&stc=1&d=1290036923

As root:
cd /var/lib/dpkg/info
mv linux-kernel-headers.list linux-kernel-headers.list.bak
mv linux-kernel-headers.md5sums linux-kernel-headers.md5sums.bak
apt-get install i2c-tools
mv linux-kernel-headers.list.bak linux-kernel-headers.list
mv linux-kernel-headers.md5sums.bak linux-kernel-headers.md5sums

[MohammadAG]

As root:
cd /var/lib/dpkg/info
mv linux-kernel-headers.list linux-kernel-headers.list.bak
mv linux-kernel-headers.md5sums linux-kernel-headers.md5sums.bak
apt-get install i2c-tools
mv linux-kernel-headers.list.bak linux-kernel-headers.list
mv linux-kernel-headers.md5sums.bak linux-kernel-headers.md5sums


Don't do that, the new package is fixed, don't mess with dpkg's database!

[bachagabriel]

Same question but did not get answered
Thanks all for work on h-e-n, that successfully tested on Flash drive(SanDisk Extreme Contour 16GB), mice and keyboard =)

but how to work on lan adapter? i tested in full speed hostmode, router can detect the lan signal, but can't connect network though wired lan. I don't know how to setup by wired lan, can anyone help me?? thanks!

I tried connecting a usb network adapter. The connection between the adapter and the N900 worked but the N900 does not connect to the internet.

How can I make this work? What packages must I install?

If nothing is available can someone write a program that allows us to do so?

Thanks

[deny_winarto]

sorry if this has been asked before, but do you have to install the power kernel in order to make this work?
I've heard bad things about the modified kernel so i prefer to keep the original one.. thanks

[NokiaRocks]

Yes you do need the power kernel to get the host mode working.

I just installed h-e-n, but I dont really know here I can find the mounted device.
.Thx for the help.

//edit : Just rebooted again and now every thing's working fine ;)
Great job all people who made the host mode possible.

[didik.wahyono]

Guys, sorry i don't have much knowledge about USB HOST MODE, but is it possible that we use N900 as a host-mode as well as charging it? I know that during this mode, BME is stopped. But who know we can still give a command to Battery management to draw power from the USB port to charge the battery. For sure we can create such cable that provide an external power port to power the N900 and attached device.

[didik.wahyono]

Is there a way to get a generic dual-stick-clone gamepad to work with n900 and the emulators... It seems to recognize it, but it has no function what so ever and none of the light light up :(

you have to remap the joypad event into the keyboard. I have compiled Xjoypad for ubuntu into Maemo. You can download it from 4shared.
http://talk.maemo.org/attachment.php?attachmentid=15978&stc=1&d=1290921841

http://talk.maemo.org/attachment.php?attachmentid=15979&stc=1&d=1290921841

http://www.4shared.com/file/sO2p4sJN/DDKcorp_xjoypad.html

copy to your /usr/bin and put permission for that file.

[joerg_rw]

Guys, sorry i don't have much knowledge about USB HOST MODE, but is it possible that we use N900 as a host-mode as well as charging it? I know that during this mode, BME is stopped. But who know we can still give a command to Battery management to draw power from the USB port to charge the battery. For sure we can create such cable that provide an external power port to power the N900 and attached device.

http://talk.maemo.org/showthread.php?p=866309#post866309


Also the much requested hostmode while charging (N900 works as USB host but does not supply VBUS 5V - this will be done by a modified hub or a Y-cable: http://wiki.openmoko.org/wiki/Specia...aka_Y-Cable.29) is not yet supported.

Wait for a version of jrbme integrating management of VBUS (incl. "charging hostmode") as well as hostmode enabling and notifications to user, to come in a few weeks.


[edit] http://talk.maemo.org/showthread.php?p=921203#post921203
/j

[ed00]

Has anybody tried to connect webcam?
I have tiny 3 MP webcam. And seems that h-e-n recognize it. And obviously its not showing up in File manager. Wondering if possible to retrieve and get access to it.


sb 1-1:1.0: uevent
[122824.725524] uvcvideo 1-1:1.0: usb_probe_interface
[122824.725524] uvcvideo 1-1:1.0: usb_probe_interface - got id
[122824.725585] uvcvideo: Found UVC 1.00 device USB 2.0 PC Cam (174f:5271)
[122824.727874] input: USB 2.0 PC Cam as /class/input/input21
[122824.784606] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
[122824.784790] usb 1-1:1.1: uevent
[122824.784881] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '057'
[122824.785278] usb 1-1: New USB device found, idVendor=174f, idProduct=5271
[122824.785308] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[122824.785308] usb 1-1: Product: USB 2.0 PC Cam
[122824.785339] usb 1-1: Manufacturer: Image Processor
[122824.785369] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[122824.785400] hub 1-0:1.0: port 1 enable change, status 00000503
[122860.465850] Forced hostmode error: no device attached
[122860.465942] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[122860.465972] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
[122860.466003] usb 1-1: USB disconnect, address 57
[122860.466003] usb 1-1: unregistering device
[122860.466033] usb 1-1: usb_disable_device nuking all URBs
[122860.466064] musb_hdrc musb_hdrc: shutdown urb cf3e4780 ep3in-intr
[122860.466064] usb 1-1: unregistering interface 1-1:1.0
[122860.526611] usb 1-1:1.0: uevent
[122860.526672] usb 1-1: unregistering interface 1-1:1.1
[122860.526763] usb 1-1:1.1: uevent
[122860.527191] usb 1-1: uevent
[122860.682464] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[122860.807434] usb 1-1: new high speed USB device using musb_hdrc and address 58
[122860.964843] usb 1-1: skipped 1 descriptor after configuration
[122860.964874] usb 1-1: skipped 5 descriptors after interface
[122860.964904] usb 1-1: skipped 1 descriptor after endpoint
[122860.964904] usb 1-1: skipped 13 descriptors after interface
[122860.965087] usb 1-1: default language 0x0409
[122860.965942] usb 1-1: uevent
[122860.966094] usb 1-1: usb_probe_device
[122860.966094] usb 1-1: configuration #1 chosen from 1 choice
[122860.968353] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[122860.968566] usb 1-1:1.0: uevent
[122860.968719] uvcvideo 1-1:1.0: usb_probe_interface
[122860.968750] uvcvideo 1-1:1.0: usb_probe_interface - got id
[122860.968841] uvcvideo: Found UVC 1.00 device USB 2.0 PC Cam (174f:5271)
[122860.972259] input: USB 2.0 PC Cam as /class/input/input22
[122861.026580] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
[122861.026702] usb 1-1:1.1: uevent
[122861.026763] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '058'
[122861.027008] usb 1-1: New USB device found, idVendor=174f, idProduct=5271
[122861.027008] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[122861.027038] usb 1-1: Product: USB 2.0 PC Cam

[joerg_rw]

Has anybody tried to connect webcam?
I have tiny 3 MP webcam. And seems that h-e-n recognize it. And obviously its not showing up in File manager. Wondering if possible to retrieve and get access to it.


Your dmesg clearly shows it's recognized and enumerated as high speed device. To me it looks like it's drawing too much power or sth, and so resets and starts over again enumerating. Anyway there's even a video driver loaded for it.
Obviously it won't show up in file manager, what would you expect to see? A mpeg video file?

If it works and driver works.... I guess you then could access it similarly to internal cams which are /dev/video0 and /dev/video1

cheers
jOERG

[giannoug]

Has anybody tried to connect webcam?
I have tiny 3 MP webcam. And seems that h-e-n recognize it. And obviously its not showing up in File manager. Wondering if possible to retrieve and get access to it.

You can use it with mplayer. Try something like this.
mplayer tv:// -tv driver=v4l2:device=/dev/video0

Change /dev/video0. To find all the cameras attached (and working), use:
ls /dev/video*

/dev/video0 is the back camera
/dev/video1 is the front camera
and /dev/video2 should be your USB camera.

[WhiteWolf]

You can use it with mplayer. Try something like this.
mplayer tv:// -tv driver=v4l2:device=/dev/video0

Change /dev/video0. To find all the cameras attached (and working), use:
ls /dev/video*

/dev/video0 is the back camera
/dev/video1 is the front camera
and /dev/video2 should be your USB camera.

I have a Logitech Webcam Pro 9000 Webcam, works on my Ubuntu, the N900 is detected but the commands you indicate only shows green screen.

[ed00]

Thanks for respond :)


heres what im getting

ls /dev/video*
/dev/video0 /dev/video1 /dev/video2

but when i run
mplayer tv:// -tv driver=v4l2:device=/dev/video2
its giving me
Playing tv://.
TV file format detected.
No such driver: V412

[joerg_rw]

just a suggestion in which direction to think, about mounting etc:
[excerpt from my PC syslog]

Dec 2 09:01:10 halley kernel: [6102345.471038] usb 1-1: new high speed USB device using ehci_hcd and address 59
Dec 2 09:01:10 halley kernel: [6102345.587521] usb 1-1: New USB device found, idVendor=1307, idProduct=0165
Dec 2 09:01:10 halley kernel: [6102345.587552] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 2 09:01:10 halley kernel: [6102345.587572] usb 1-1: Product: USB Mass Storage Device
Dec 2 09:01:10 halley kernel: [6102345.587588] usb 1-1: Manufacturer: USB007
Dec 2 09:01:10 halley kernel: [6102345.587602] usb 1-1: SerialNumber: 00000000000619
Dec 2 09:01:10 halley kernel: [6102345.587887] usb 1-1: configuration #1 chosen from 1 choice
Dec 2 09:01:10 halley kernel: [6102345.590306] scsi23 : SCSI emulation for USB Mass Storage devices
Dec 2 09:01:10 halley kernel: [6102345.590623] usb-storage: device found at 59
Dec 2 09:01:10 halley kernel: [6102345.590631] usb-storage: waiting for device to settle before scanning
Dec 2 09:01:11 halley kernel: [6102346.591239] scsi 23:0:0:0: Direct-Access USB007 mini-USB2BU 0.00 PQ: 0 ANSI: 2
Dec 2 09:01:11 halley kernel: [6102346.591722] sd 23:0:0:0: Attached scsi generic sg2 type 0
Dec 2 09:01:11 halley kernel: [6102346.595452] sd 23:0:0:0: [sdb] 1974272 512-byte logical blocks: (1.01 GB/964 MiB)
Dec 2 09:01:11 halley kernel: [6102346.596211] sd 23:0:0:0: [sdb] Write Protect is off
Dec 2 09:01:11 halley kernel: [6102346.596230] sd 23:0:0:0: [sdb] Mode Sense: 00 00 00 00
Dec 2 09:01:11 halley kernel: [6102346.596238] sd 23:0:0:0: [sdb] Assuming drive cache: write through
Dec 2 09:01:11 halley kernel: [6102346.598117] usb-storage: device scan complete
Dec 2 09:01:11 halley kernel: [6102346.599687] sd 23:0:0:0: [sdb] Assuming drive cache: write through
Dec 2 09:01:11 halley kernel: [6102346.599725] sdb: sdb1
Dec 2 09:01:11 halley kernel: [6102346.954787] sd 23:0:0:0: [sdb] Assuming drive cache: write through
Dec 2 09:01:11 halley kernel: [6102346.954808] sd 23:0:0:0: [sdb] Attached SCSI removable disk
Dec 2 09:01:12 halley hald: mounted /dev/sdb1 on behalf of uid 1000
Dec 2 09:01:29 halley kernel: [6102364.537195] usb 1-1: USB disconnect, address 59
Dec 2 09:01:29 halley hald[1356]: forcibly attempting to lazy unmount /dev/sdb1 as enclosing drive was disconnected
Dec 2 09:01:29 halley hald: unmounted /dev/sdb1 from '/media/disk-1' on behalf of uid 0



particularly look at the hald-lines

from my ps:
1490 ? S 29:49 hald-addon-storage: polling /dev/sr0 (every 2 sec)
/j

[foosball]

Thanks for respond :)


heres what im getting

ls /dev/video*
/dev/video0 /dev/video1 /dev/video2

but when i run
mplayer tv:// -tv driver=v4l2:device=/dev/video2
its giving me
Playing tv://.
TV file format detected.
No such driver: V412


I've noticed that you didn't type the code correctly... "v4l2" stands for "Video 4 Linux 2" input, so make sure you enter letter "l", not digit "1"

[ed00]

@foosball
yes, i found that right after when i posted.

Well im still trying to make webcam work no luck yet ...

[Hardik]

Hello,

I have installed h-e-n application on my N900 & i am able to connect USB mouse successfully with my device through this software.

But when I try to connect my pendrive with the same procedure i followed for mouse, the pen drive is not detected. I searched some videos in which people has successfully connected their pendrives/USB HDDs to the device by doing some kernal settings through Xterminal.

Can Anyone here tell me how I can enable USB disk detection on my N900??

Thanks a lot for your support..

Best Regards,
Hardik

[blue_led]

try fullspeed not highspeed. some cards don't work in HSmode from start.

[WhiteWolf]

The problem we suffer is to mount USB drives. The script does not work.

Always properly enumerate my devices.

Completely assembled manually.

[sophocha]

I don`t know if this is been asked before but.....is there a way of connecting a USB game controller to the N900 and use it in games through HEN?

Thanks

[obhishap]

Hi guys
First of all, thanks a lot for the good work. Wishing you guys all the very best. Anyway, I am getting some problem with host mode to work. My N900 is on the latest FW which is PR 1.3 and I am using the latest kernel which is Titan's kernel V46 with no over clocking. I have installed extmou for my bluetooth mouse (A4Tech BT-630) and it works perfect. Yesterday I installed h-e-n and I made a female to female usb converter by myself. I have a Verbatim 2GB pendrive. I tried to connect it with N900 but no luck. N900 does recognise it but there is no drive in nither File manager nor Filebox. Today I uninstalled extmou and restart devide and reinstalled extmou also restart and tried my bluetooth mouse. Its working fine but no avail with usb laser mouse. I did collect the kernel message which I am providing below.
http://i1128.photobucket.com/albums/m491/obhishap/Shared%20in%20web/Screenshot-20101222-153239.png

BTW, I saw somewhere that i2c-tools is needed but when I search for it, I just find i2c_tiny_usb. Is this the same one ? Anyway, I tried with the pendrive with fat, fat32 and ntfs format. I also tried to mount manually but get an error says "no such file or directory". Sometimes I get a yellow banner says "unable to connect". I also checked the media/flash in filebox and got an empty mmc1 folder. Now I am very much confused:confused:. I dont know what to do. I tried almost everything I could but returns with no luck. So it would be my humbble pleasure if anybody can lead me to the solution. Thanks:D

[slender]

obhishap,
You made converter yourself? So have you confirmed on some other device that your handmade plug really works?

Also I have huge trouble on understand what is the issue?
- No cursor
- Usb pendrive not working
These?

You can btw. copy that log and copy paste it here or in pastebin.

[obhishap]

Thanks slender for quick reply. Yes, I made the converter. I took a male to female usb extension cable and a female usb point from a ps2 to usb converter. Then I did cut the male point from the cable and soldered the female point into there. I think it is working cause, I can see the pendrive and usb mouse getting power and also recognised by N900. The problem is, I am not getting mouse cursor and not getting any pendrive drive in the file manager. Another problem is, after checking anything in h-e-n, I cannot connect N900 to pc if not restarted. I am using N900 as usb modem and everytime I use h-e-n, I need to restart N900 to get connection to the pc. This is the most annoying part. I will paste the log ASAP. Thanks again for the help.

[obhishap]

[ 4996.560668] usb 1-1: usb_probe_device
[ 4996.560699] usb 1-1: configuration #1 chosen from 1 choice
[ 4996.564453] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 4996.564788] usb 1-1:1.0: uevent
[ 4996.565185] libusual 1-1:1.0: usb_probe_interface
[ 4996.565277] libusual 1-1:1.0: usb_probe_interface - got id
[ 4996.657897] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '006'
[ 4996.658294] usb 1-1: New USB device found, idVendor=0a16, idProduct=1200
[ 4996.658325] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4996.658355] usb 1-1: Product: Store'n'Go Mini
[ 4996.658355] usb 1-1: Manufacturer: Verbatim
[ 4996.658386] usb 1-1: SerialNumber: 4af2aac589831b
[ 4996.658416] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[ 4996.658477] hub 1-0:1.0: port 1 enable change, status 00000503
[ 4996.729919] Initializing USB Mass Storage driver...
[ 4996.730163] usb-storage 1-1:1.0: usb_probe_interface
[ 4996.730194] usb-storage 1-1:1.0: usb_probe_interface - got id
[ 4996.730712] scsi0 : SCSI emulation for USB Mass Storage devices
[ 4996.738922] usbcore: registered new interface driver usb-storage
[ 4996.738983] USB Mass Storage support registered.
[ 4996.744720] usb-storage: device found at 6
[ 4996.744720] usb-storage: waiting for device to settle before scanning
[ 5001.746032] usb-storage: device scan complete
[ 5001.766723] scsi 0:0:0:0: Direct-Access Verbatim Store'n'Go Mini 1.30 PQ: 0 ANSI: 2
[ 5001.784881] sd 0:0:0:0: [sda] 3948544 512-byte hardware sectors: (2.02 GB/1.88 GiB)
[ 5001.785186] sd 0:0:0:0: [sda] Write Protect is off
[ 5001.785217] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
[ 5001.785217] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 5001.789703] sd 0:0:0:0: [sda] 3948544 512-byte hardware sectors: (2.02 GB/1.88 GiB)
[ 5001.789978] sd 0:0:0:0: [sda] Write Protect is off
[ 5001.790008] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
[ 5001.790039] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 5001.790039] sda:
[ 5002.109436] sd 0:0:0:0: [sda] Attached SCSI removable disk


But though I am not getting it working.

[jurop88]

Hi Obhishap,
what does ls /dev/sd* outputs?

[obhishap]

Hi Obhishap,
what does ls /dev/sd* outputs?



Sorry I am not getting it. Did you mean the list in /dev ??? if yes, then there is no sd or sda1 exist in dev directory. Looking ahead to your reply. Thanks.

BTW, I saw a broken symlink in the dev directory which is named "core".

[jurop88]

I am not a kernel developer but the broken symlink shouldn't matter.
It sounds strange you don't have any /dev/sda kind of file, the log says clearly the kernel is going to file your verbatim under /dev/sda...
Just to be sure, did you check the existance of /dev/sda AFTER having enumerated your verbatim usb stick? The device is created on the fly by the kernel, it is not a dir you have to create

[obhishap]

Got it working man thanks a lot. I checked for sda instead of sda1 and I got it right a way....Now I am so happy. Thanks jurop88 and all of you who helped me.

[Temporal]

Hi everybody,

something strange is happening here:
A while ago I asked about a problem that happened when moving files bigger than 200mb (and promptly answered by joerg that is a maemo bug).

And I had another problem of time while working with h-e-n: sometime after started, it said in dmesg something like usb1:suspend, and then the link was lost. I use to use the hub (cp-h420mp) - the only one I have that works, all my other [cheap] self powered hubs just won't - because direct link between mouse-n900 just doesn't work.

And the problem with self suspend was true UNTIL I plugged together another gadget called Gemei x760+, that I planed to use as a SD reader (and that have another memory with 4GB that isn't auto mounted but is easy to mount - it is recognized).

And the problem with the files of more than 200mb was solved too!! Now I can move and copy anything without problems and having to run fdisk to fix things.

Is there any explanation for that?

Thanks.

[Dark_Angel85]

my problem:

Trying to find that darn USB female-female converter....

Darn shops ain't got nothin in em

[deny_winarto]

Hello, i'm getting this error when running male to female cable with USB Visipro 8GB



[31587.611602] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
[31587.674224] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31587.885101] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31588.096008] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31588.096069] hub 1-0:1.0: port_wait_reset: err = -16
[31588.096099] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31588.306884] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31588.517913] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31588.728942] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31588.728973] hub 1-0:1.0: port_wait_reset: err = -16
[31588.729003] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31588.939849] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31589.150878] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31589.361724] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31589.361755] hub 1-0:1.0: port_wait_reset: err = -16
[31589.361785] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31589.572662] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31589.783599] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31589.994476] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31589.994537] hub 1-0:1.0: port_wait_reset: err = -16
[31589.994567] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31590.205474] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31590.416473] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31590.627441] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31590.627471] hub 1-0:1.0: port_wait_reset: err = -16
[31590.627502] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31590.627532] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[31590.627624] hub 1-0:1.0: logical disconnect on port 1
[31590.627716] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[31590.627777] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s
[31590.627807] usb 1-1: USB disconnect, address 24
[31590.627899] usb 1-1: unregistering device
[31590.627929] usb 1-1: usb_disable_device nuking all URBs
[31590.627960] usb 1-1: unregistering interface 1-1:1.0
[31590.663116] scsi 4:0:0:0: rejecting I/O to dead device
[31590.663269] scsi 4:0:0:0: rejecting I/O to dead device
[31590.663391] scsi 4:0:0:0: rejecting I/O to dead device
[31590.663482] scsi 4:0:0:0: rejecting I/O to dead device
[31590.663513] scsi 4:0:0:0: [sda] READ CAPACITY failed
[31590.663543] scsi 4:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
[31590.663604] scsi 4:0:0:0: [sda] Sense not available.
[31590.663665] scsi 4:0:0:0: rejecting I/O to dead device
[31590.663757] scsi 4:0:0:0: [sda] Write Protect is off
[31590.663787] scsi 4:0:0:0: [sda] Mode Sense: 00 00 00 00
[31590.663818] scsi 4:0:0:0: [sda] Assuming drive cache: write through
[31590.663909] scsi 4:0:0:0: rejecting I/O to dead device
[31590.664001] scsi 4:0:0:0: rejecting I/O to dead device
[31590.664093] scsi 4:0:0:0: rejecting I/O to dead device
[31590.664184] scsi 4:0:0:0: rejecting I/O to dead device
[31590.664245] scsi 4:0:0:0: [sda] READ CAPACITY failed
[31590.664276] scsi 4:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
[31590.664306] scsi 4:0:0:0: [sda] Sense not available.
[31590.664367] scsi 4:0:0:0: rejecting I/O to dead device
[31590.664428] scsi 4:0:0:0: [sda] Write Protect is off
[31590.664459] scsi 4:0:0:0: [sda] Mode Sense: 00 00 00 00
[31590.664489] scsi 4:0:0:0: [sda] Assuming drive cache: write through
[31590.667572] usb 1-1:1.0: uevent
[31590.668914] usb 1-1: uevent
[31590.729156] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
[31590.791351] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31591.002227] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31591.214202] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31591.214233] hub 1-0:1.0: port_wait_reset: err = -16
[31591.214263] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31591.424163] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31591.635040] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31591.846008] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31591.846038] hub 1-0:1.0: port_wait_reset: err = -16
[31591.846038] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31592.056945] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31592.268066] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31592.478973] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31592.479003] hub 1-0:1.0: port_wait_reset: err = -16
[31592.479034] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31592.689849] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31592.900787] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31593.111724] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31593.111755] hub 1-0:1.0: port_wait_reset: err = -16
[31593.111785] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31593.322662] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31593.533599] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31593.744598] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31593.744628] hub 1-0:1.0: port_wait_reset: err = -16
[31593.744659] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31593.744689] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[31593.806915] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
[31593.869384] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31594.080474] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31594.291412] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31594.291442] hub 1-0:1.0: port_wait_reset: err = -16
[31594.291473] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31594.502349] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31594.713287] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31594.924285] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31594.924316] hub 1-0:1.0: port_wait_reset: err = -16
[31594.924346] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31595.135162] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31595.346130] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31595.556945] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31595.557006] hub 1-0:1.0: port_wait_reset: err = -16
[31595.557037] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31595.768005] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31595.978912] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31596.189910] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31596.189941] hub 1-0:1.0: port_wait_reset: err = -16
[31596.189971] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31596.400848] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31596.611724] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31596.822540] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31596.822570] hub 1-0:1.0: port_wait_reset: err = -16
[31596.822601] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31596.822631] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[31596.885192] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
[31596.947784] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31597.158599] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31597.369415] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31597.369445] hub 1-0:1.0: port_wait_reset: err = -16
[31597.369476] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31597.580474] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31597.791412] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31598.002410] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31598.002441] hub 1-0:1.0: port_wait_reset: err = -16
[31598.002471] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31598.213348] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31598.424346] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31598.635162] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31598.635192] hub 1-0:1.0: port_wait_reset: err = -16
[31598.635223] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31598.846069] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31599.056945] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31599.268157] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31599.268188] hub 1-0:1.0: port_wait_reset: err = -16
[31599.268218] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31599.479095] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31599.689849] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31599.900787] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31599.900817] hub 1-0:1.0: port_wait_reset: err = -16
[31599.900848] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31599.900878] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[31599.963287] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
[31600.025878] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31600.236724] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31600.447662] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31600.447692] hub 1-0:1.0: port_wait_reset: err = -16
[31600.447723] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31600.658660] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31600.869537] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31601.080352] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31601.080383] hub 1-0:1.0: port_wait_reset: err = -16
[31601.080413] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31601.291412] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31601.502349] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31601.713287] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31601.713317] hub 1-0:1.0: port_wait_reset: err = -16
[31601.713348] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31601.924224] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31602.135162] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31602.346099] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31602.346130] hub 1-0:1.0: port_wait_reset: err = -16
[31602.346160] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31602.557037] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31602.768096] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31602.978912] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[31602.978942] hub 1-0:1.0: port_wait_reset: err = -16
[31602.978973] hub 1-0:1.0: port 1 not enabled, trying reset again...
[31602.979003] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[31602.979095] hub 1-0:1.0: unable to enumerate USB device on port 1
[31604.978973] hub 1-0:1.0: hub_suspend
[31604.979034] usb usb1: bus auto-suspend
[31844.648956] usb usb1: usb resume
[31844.666229] hub 1-0:1.0: hub_resume
[31844.666290] hub 1-0:1.0: port 1: status 0101 change 0001
[31844.775817] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[31844.775909] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[31844.900878] usb 1-1: new high speed USB device using musb_hdrc and address 29
[31845.025787] usb 1-1: device descriptor read/64, error -19
[31845.260162] usb 1-1: device descriptor read/64, error -19
[31845.494537] usb 1-1: new high speed USB device using musb_hdrc and address 30
[31845.619689] usb 1-1: device descriptor read/64, error -19
[31845.854003] usb 1-1: device descriptor read/64, error -19
[31846.088378] usb 1-1: new high speed USB device using musb_hdrc and address 31
[31846.510131] usb 1-1: device not accepting address 31, error -19
[31846.635253] usb 1-1: new high speed USB device using musb_hdrc and address 32
[31847.057006] usb 1-1: device not accepting address 32, error -19
[31847.057098] hub 1-0:1.0: unable to enumerate USB device on port 1
[31847.057159] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31847.057220] hub 1-0:1.0: port 1 enable change, status 00000501
[31849.767883] hub 1-0:1.0: hub_suspend
[31849.767944] usb usb1: bus auto-suspend
[31934.570831] usb usb1: usb resume
[31934.588623] hub 1-0:1.0: hub_resume
[31934.588775] hub 1-0:1.0: port 1: status 0101 change 0001
[31934.697723] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[31934.697814] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[31934.822570] usb 1-1: new high speed USB device using musb_hdrc and address 33
[31934.973297] usb 1-1: default language 0x0409
[31934.975708] usb 1-1: uevent
[31934.975921] usb 1-1: usb_probe_device
[31934.975952] usb 1-1: configuration #1 chosen from 1 choice
[31934.979858] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[31934.980194] usb 1-1:1.0: uevent
[31934.980468] libusual 1-1:1.0: usb_probe_interface
[31934.980529] libusual 1-1:1.0: usb_probe_interface - got id
[31934.980712] usb-storage 1-1:1.0: usb_probe_interface
[31934.980773] usb-storage 1-1:1.0: usb_probe_interface - got id
[31935.075317] scsi5 : SCSI emulation for USB Mass Storage devices
[31935.101623]
/home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c:
creating file '033'
[31935.102325] usb 1-1: New USB device found, idVendor=0951, idProduct=1624
[31935.102386] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[31935.102416] usb 1-1: Product: DataTraveler G2
[31935.102447] usb 1-1: Manufacturer: Kingston
[31935.102478] usb 1-1: SerialNumber: 001372982918A961A62D0044
[31935.102508] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31935.102600] hub 1-0:1.0: port 1 enable change, status 00000503
[31935.109130] usb-storage: device found at 33
[31935.109161] usb-storage: waiting for device to settle before scanning
[31940.105743] usb-storage: device scan complete
[31940.166442] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31940.228912] usb 1-1: reset high speed USB device using musb_hdrc and address 33
[31940.291534] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31940.439910] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31940.502349] usb 1-1: reset high speed USB device using musb_hdrc and address 33
[31940.564788] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31940.713378] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31940.776245] usb 1-1: reset high speed USB device using musb_hdrc and address 33
[31940.838348] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31940.986846] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[31941.049133] usb 1-1: reset high speed USB device using musb_hdrc and address 33
[31941.111755] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002</p>

Could anyone help me?
Any known solution for this?

[peterleinchen]

Hey Dark_Angel.

I do not know , where You are from, but check this out:
http://cgi.ebay.de/USB-2-0-Adapter-A-Buchse-A-Buchse-Kupplung-/320635173280?pt=DE_Technik_Computerzubeh%C3%B6r_Ka bel_Adapter&hash=item4aa75879a0
or
http://cgi.ebay.de/USB-2-0-Adapter-Buchse-A-Buchse-A-Kupplung-Verbinder_W0QQitemZ330427903030QQcategoryZ131871QQ cmdZViewItemQQ_trksidZp3286.m7QQ_trkparmsZalgo%3DL VI%26itu%3DUCI%26otn%3D1%26po%3DLVI%26ps%3D63%26cl kid%3D6039350702583254572#shId

Both send to Germany for free. And both have good reputation (from me ;)).


@all
Wouldn't it be much more convenient for all to put the outputs of dmesg or similar into a small txt file and attach it with the post? Instead of "spamming" the thread with such long listings, making it hard to read?

[blue_led]

The problem we suffer is to mount USB drives. The script does not work.

Always properly enumerate my devices.

Completely assembled manually.


please read post #604 in hostmode thread. the problem is solved

[joerg_rw]

Hi Deny_winarto,
this looks like your cable isn't good for highspeed. Try a better cable, or try connecting with fullspeed.

cheers
jOERG

[deny_winarto]

@peterleinchen : sorry I'll do that next time

@joerg_rw ; thanks, so what cable/adapter combination would you recommend? I bought that cable because someone on the other thread managed to get it working on a HDD.

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

and what actually determines the success rate of hostmode? is it the quality of male pinout or the female pinout?

[Boemien]

my problem:

Trying to find that darn USB female-female converter....

Darn shops ain't got nothin in em

Hi all, I just brought 2 Usb cable (male - female) and cut the 2 female usb and connected themselves, following the colors of the cables. finally i made my female - female usb adaptator and it works pretty well!!! no need to buy an adaptator!

[trx]

In case you have one of these around, its pretty much the fastest way to improvise...

http://img137.imageshack.us/img137/572/20101209001.jpg

TRX.

[didik.wahyono]

hi sami power

most emulators do not support joypad. they are supporting keyboard. this is how xjoypad works. it reads your joypad and send the pressed key to keyboard, so the emulator will thinks that the keyboard is being pressed.

it means, after you are succesfully enumerate your joypad and the joypad is listed in dev/input, you are able to control all applications that supports keyboard. this inlcuding your xterminal.

maybe the problem was, your joypad is not listed as js0. try to findout what is the codename of your joypad. since i have only one joypad, i am unable to find another codename, thats why i assign js0 as default in xjoypad.

try to reboot your N900,
cd /dev/input then type ls
enumerate your joypad,
then do cd /dev/input then type ls again.
any new item will be your joypad.

regard

[samipower]

gamepad codename ?? what numbers/letters in hen , is it?? , can you see my captures,

now i wil try it:

try to reboot your N900,
cd /dev/input then type ls
enumerate your joypad,
then do cd /dev/input then type ls again.
any new item will be your joypad.

edit:

you're very lucky , only 1 gamepad and it are running perfect

but you has been played only a psx and others emulators?

try mame, and others please and tell me . thanks


for example user IMPEHAM say it:

it is working - i was playing with such a joystick - connected my n900 to the TV and played mame games, playstation games with the emulator, and mupen 64 - amazing - the N900 has now become a full game console...

i used mgtech joystick: http://img.zap.co.il/pics/5/6/1/1/21601165b.gif

this gamepad are very compatible with all emulators

i tried 4 gamepads and only 1 ran and only with mame, very rare.

and without xjoypad, with xjoypad identical results.


i tried

enumerate joypad,
then do cd /dev/input then type ls again.
and not new item

i think that it depend compatibility drivers but

my big dude:

play 3 station gamepad original bluettoth have sixaxis driver installed and run very well

why are not running in usb mode? , if n900 have library ??

[didik.wahyono]

gamepad codename ?? what numbers/letters in hen , is it?? , can you see my captures,

now i wil try it:

try to reboot your N900,
cd /dev/input then type ls
enumerate your joypad,
then do cd /dev/input then type ls again.
any new item will be your joypad.

edit:

you're very lucky , only 1 gamepad and it are running perfect

but you has been played only a psx and others emulators?

try mame, and others please and tell me . thanks


for example user IMPEHAM say it:

it is working - i was playing with such a joystick - connected my n900 to the TV and played mame games, playstation games with the emulator, and mupen 64 - amazing - the N900 has now become a full game console...

i used mgtech joystick: http://img.zap.co.il/pics/5/6/1/1/21601165b.gif

this gamepad are very compatible with all emulators

i tried 4 gamepads and only 1 ran and only with mame, very rare.

and without xjoypad, with xjoypad identical results.


i tried

enumerate joypad,
then do cd /dev/input then type ls again.
and not new item

i think that it depend compatibility drivers but

my big dude:

play 3 station gamepad original bluettoth have sixaxis driver installed and run very well

why are not running in usb mode? , if n900 have library ??

greeting,

yes, i have tried it at three different emulator. its PSX4all, drNokSNES, iNES, Master gear, and it works fine. i just need to set up the emulators to read specific key in the joypad.

can you please tell me what was listed in /dev/input after you enumerate ur joypad? what i mean by "codename" is letter and numbers in /dev/input. for example js0.

regard

[samipower]

my steps exactly:

i started nokia n900
open xterminal and in dev/input are this files

event0 event1 event2 event3 keypad ts pwrbutton uinput

now i started hen
full speed vboost
connect usb gamepad ps3 original and enumerate , two times enumerate process
hen log: show name and compant gamepad and usb hid core driver 2.6

in dev/input/ i write ls

and nothing not new file created

but if i put on bluetooth and conect ps3 gamepad bluetoth mode

yes in dev/input magic js0 now

usb mode not js0
bluetoth mode yes js0

same gamepad ps3 original used

i used filebox and compress js0 file into zip file with bluetoth active

and after i tried with js0 file copy/paste in dev/input and try put usb ps3 original gamepad and hen enumerate and xjoypad

and yes xjoypad run ok now , but gamepad not run .

[istota]

Before you mount, however you might need extra packages (that may/may not be available in maemo) for write support.

hello
very please help I want to connect a dvd rom as I have to do it
so to play dvd and if it is possible to have a record
Thank you for hen and greet

I apologize for the language

[jaskin71]

hi all, what im doing wrong? when i switch on h-e-n and i do all what i saw in all forums and youtube videos but i still cant get working any discs. i have nokia card reader and usb sandisk 4GB. mouse working properly, keyboard as well. what i have to do?thx

[hellsing]

Hello,
I've got a little problem:
i plug my usb key, it's enumerate, i can see it in dmesg.
The mount button doesn't work at all.
I can mount it by in root: mount /dev/sda /media/flash -o uid=29999,gid=29999,utf8,dmask=027,fmask=137
and its appear in /media/flash that i created.
Is there a way that the mount button work?
Thx

[cheve]

hi,

I have tried to connect a usb DVD drive and got the following in the logs:

[39971.219238] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '022'
[39971.219604] usb 1-1: New USB device found, idVendor=03f0, idProduct=5e07
[39971.219635] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[39971.219665] usb 1-1: Product: HP USB Mass Storage Device
[39971.219665] usb 1-1: Manufacturer: Hewlett-Packard
[39971.219696] usb 1-1: SerialNumber: 2104752485555557234
[39971.219726] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[39971.219757] hub 1-0:1.0: port 1 enable change, status 00000503
[39971.375396] Initializing USB Mass Storage driver...
[39971.375640] usb-storage 1-1:1.0: usb_probe_interface
[39971.375671] usb-storage 1-1:1.0: usb_probe_interface - got id
[39971.377471] scsi0 : SCSI emulation for USB Mass Storage devices
[39971.378784] usbcore: registered new interface driver usb-storage
[39971.378814] USB Mass Storage support registered.
[39971.381378] usb-storage: device found at 22
[39971.381378] usb-storage: waiting for device to settle before scanning
[39976.381317] usb-storage: device scan complete
[39976.394439] scsi 0:0:0:0: CD-ROM HP DVD-ROM rm475e JH21 PQ: 0 ANSI: 0

My guess is that h.e.n. is working, Is it? Further question is that how do I mount this one?(note: I have also posted http://talk.maemo.org/showthread.php?p=927103#post927103) for help on this.)

Cheers,

[WhiteWolf]

I'm trying to use a USB to RJ45 hostmode mode.

The data provided by the command "lsusb"on my PC are:
ID 0fe6: 8101 Kontron (Industrial Computer Source / ICS Advent) DM9601 Fast Ethernet Adapter

How do I start on my N900?

[mveplus]

I'm trying to use a USB to RJ45 hostmode mode.

The data provided by the command "lsusb"on my PC are:
ID 0fe6: 8101 Kontron (Industrial Computer Source / ICS Advent) DM9601 Fast Ethernet Adapter

How do I start on my N900?

Hi, you may have my problem --missing kernel module for your usb2network adapter. Kernel 10power46, has build in only general usb networking. i.e. does not include all modules needed, for all possible usb devices - some may work and some nay not work.

if that is the case with you then download the module that i'm attached and do like root (you have to have installed pakage rootsh ), open terminal, change directory to the place that you download dm9601.ko, let assume that is in your documents folder:
cd MyDocs/.documents/
tar -zxvf dm.tar.gz
sudo gainroot
modprobe usbnet
insmod dm9601.ko
Assuming that you do not get any errors from the code here, then proceed like normal, start h-e-n, connect your adapter and after activateing hen, go and check do you have eth0 node in:
ls /dev/eth*
if you do then you are good to go

[WhiteWolf]

Thanks I'll try and tell you...

[WhiteWolf]

Do not get it to work.

[cheve]

hi,

I have tried to connect a usb DVD drive and got the following in the logs:

[39971.219238] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '022'
[39971.219604] usb 1-1: New USB device found, idVendor=03f0, idProduct=5e07
[39971.219635] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[39971.219665] usb 1-1: Product: HP USB Mass Storage Device
[39971.219665] usb 1-1: Manufacturer: Hewlett-Packard
[39971.219696] usb 1-1: SerialNumber: 2104752485555557234
[39971.219726] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[39971.219757] hub 1-0:1.0: port 1 enable change, status 00000503
[39971.375396] Initializing USB Mass Storage driver...
[39971.375640] usb-storage 1-1:1.0: usb_probe_interface
[39971.375671] usb-storage 1-1:1.0: usb_probe_interface - got id
[39971.377471] scsi0 : SCSI emulation for USB Mass Storage devices
[39971.378784] usbcore: registered new interface driver usb-storage
[39971.378814] USB Mass Storage support registered.
[39971.381378] usb-storage: device found at 22
[39971.381378] usb-storage: waiting for device to settle before scanning
[39976.381317] usb-storage: device scan complete
[39976.394439] scsi 0:0:0:0: CD-ROM HP DVD-ROM rm475e JH21 PQ: 0 ANSI: 0

My guess is that h.e.n. is working, Is it? Further question is that how do I mount this one?(note: I have also posted http://talk.maemo.org/showthread.php?p=927103#post927103) for help on this.)

Cheers,

pls excuse the bad form in quoting my own post:p. someone mentioned "modprobe isofs", did a search and came up with the following:

"The mount button is currently hardcoded to mount /dev/sda1, default for most USB flash drives and HDDs. For NTFS support, do modprobe ntfs as root. For ISO (CDs/DVDs - most of them), do modprobe isofs (also as root). CDs will have the dev node /dev/sr0, so you'll need to do mount /dev/sr0 /mnt etc"

in this link http://www.my-maemo.com/software/applications.php?name=H-E-N_%28USB_Hostmode_GUI%29&faq=42&fldAuto=1973

Cheers,

[mveplus]

Do not get it to work.

attach the output files from fallowing commands, when the adapter is connected :
dmesg > dmdmesg.log
lsmod > dmmod.log
ifconfig > ifconfig.log
ls /dev/ > dmls.log

from ls /dev/eth* you should get eth0 , if you do not do not proceed with the fallowing, jump on the next section
also did you try: sudo gainroot
ifconfig eth0 up
udhcpc

IF the node eth0 is not created in /dev/ then you need udev rule to do so, download the attached file and copy it to /etc/udev/rules.d/ :
cd # to directory where you saved the file
tar -zxvf z98_usbEth.rules.tar.gz
sudo gainroot
cp z98_usbEth.rules /etc/udev/rules.d/

This script is taken form the package for N800 (http://wiki.maemo.org/USB_to_ethernet_networking), but modified for your specific device ATTRS{idProduct}=="8101" , according to your host-log file. It will work only for devices that that has this idProduct, you can modify z98_usbEth.rules, for other device IDs looking in dmesg log, finding yours product id and modifying this file.

Specail thanks to Mathan, h-e-n Team, the guys form here (http://wiki.maemo.org/USB_to_ethernet_networking) for good work which we can reuse now for N900, and all TMO hackers ;)

By

[mveplus]

Here is more easy solution for the people that struggle with USB <> NET adapters
Usual WARNING apply for that beta package ! If you mess up it's your call!

Working with Matan's kernel-10power46 (http://wiki.maemo.org/Kernel_Power) and with kernel-10power46-wl1 (patched with injection capability (http://david.gnedt.eu/blog/wl1251/)) form lxp.
Not tested with lower versions of Matan's kernel may work?!? (but h-e-n will not - probably)

What contain that package?

1. compiled some of the missing kernel USB2NET modules like external modules rtl8150.ko
mcs7830.ko
dm9601.ko
smsc95xx.ko
kaweth.ko
pegasus.ko
plusb.ko
gl620a.ko
catc.ko


these are not included modules in kernel-power v46, but Matan may add them in future updates.

2. I updated some of the scripts form original package (http://wiki.maemo.org/USB_to_ethernet_networking) for N800 to be able to use them with our kernel 2.6.28.10power46, but they were pretty much almost working.
3. Some settings for adding WIRED to show up in the usual network list - see below screenshot - do not ask for improvements because I'm not familiar with Hildon at all, may be someone who is capable of doing something about can fix/add some features.

For now the script is capable of getting setting form DHCP server (IP,GW, DNS), but you can not add IP address from Hildon (desktop) manually. You can do that form terminal if you connect to network that does not serve DHCP.

Download attached usb2net_n900_v.0.1.8.DEB (http://dl.dropbox.com/u/12258575/N900/usb2net_n900_v.0.1.8.deb) package and install it: <- NEW
cd MyDocs/.documents
sudo gainroot
dpkg -i usb2net_n900_v.0.1.8.deb

if you want to remove the package:
sudo gainroot
dpkg -P usb2net
reboot

IF for any reason not working with your USB2NET adapter then check do you have node (file) created in /dev/eth0, when h-e-n is started Hi-Speed,VBUS, Enumerate is pressed. Try to enumerate again after a few seconds, if still does not show up then you need to make your hands dirty :)
ls /dev/eth*
#output should be:
/dev/eth0
# if not then:
dmesg | grep 'idProduct'
# or
lsusb
to find out the idProduct='8730' usually four digits without quotas.
then you need to edit and add one row in vi /etc/udev/rules.d/z98usbEth.rules
you will need root access, you can use your favorite editor - vi, nano or leafpad.

You need to add that row like in screenshot below

VERY IMPORTANT! - when you disconnect your adapter you need to press 'ENUMERATE' AGAIN in h-e-n, this will give chance to udevd to register that USB2NET device is disconnected and will remove /dev/eth0, ifconfig eth0 down and clean routing table, other wise you may have problems connecting back to Wireless! Only 'VBUS boost off' does not do the job.


Some side effects and known problems:
1. During the installation of the usb2net, your wireless connection will be disconnected for a while
2. This is program is not designed to work with two USB to Ethernet adapters, ONLY with one at a time, do not know what will happed if you do ( not tested)
3.FIXED in version 0.1.8 - load modules on demand! as Joerg_rw suggested - Thanks Joerg_rw

No warranty of any kind! :) this is beta package!

Tested and working with
1. 'noname' RTL8150 based USB 1.1 - drains about 110mA form USB port.
2. 'noname' MCS8730 based USB 2.0 - drains about 186mA from USB port.

If your adapter is consuming equal or higher that 200mA, then it will not work, without external power + hub! wait for h-e-n update.

Cheers

[Boemien]

Please Guys, I own a Sagem Fast 800-E4 USB Modem! Is there a way to connect it to the Phone and have internet access???

[cheve]

@ Boemien, I think if your USB modem(refer to http://wiki.maemo.org/USB_to_ethernet_networking , there is a list of working at the end of that wiki article) uses one of the chipset mentioned in post 127 of this thread, then you have a better chance of get it working with the N900.

Cheers,

[Boemien]

Thanks Cheve, I will try it and post my feedbacks. But before I start, I Own An USB ADSL Modem wich requires Identification and password to get connected to internet. How do I enter the ID and the password? On Windows there is a GUI to do that, Even on Ubuntu (but it's a bit different)

[eefo]

well , i have the worst experience ever related to usb hostmode :(
flashed my emmc just cause of kernel :(
and still i wanted to use this mode but afraid of installed kernel again :(
any tip for me ?

[cheve]

Thanks Cheve, I will try it and post my feedbacks. But before I start, I Own An USB ADSL Modem wich requires Identification and password to get connected to internet. How do I enter the ID and the password? On Windows there is a GUI to do that, Even on Ubuntu (but it's a bit different)

@Boemien, I don't know the answer, but just thinking out loud here....currently, what exactly do you do to key in the ID and password? Do you do it by pointing your web browser to a local address(eg. http://192.x.x.x)? If so, then I think as long as you get your USB-ethernet up; then I see no reason why you wouldn't browser to the same local address to give the ID and password. However, if the interface to supply those info is thru a special application; then i think it is much more difficult. You may have to contact the manufacturer, if possible, for info.

good luck

[cheve]

well , i have the worst experience ever related to usb hostmode :(
flashed my emmc just cause of kernel :(
and still i wanted to use this mode but afraid of installed kernel again :(
any tip for me ?

@eefo, From reading your other posts and threads, I would advice you to slow down somewhat, take a 'breather' so to speak:) and do some reading. For what is worth, I have varies version of power kernels on my N900 and had not experienced issue that forces me to reflash. Now, it does not mean the power kernel is absolute perfect; but so far so good for my use case.

By the way, what do you mean by "the worst experience ever", when you have a chance, please provide detail steps of what you did/or attempted to do. With the details, folks round here may offer you educated suggestion. Please consider this: when you go to see a doctor, do you answer doctor that 'I am sick' to every questions that he ask you. Chances are that you would not.

Good luck,

[istota]

hi,

I have tried to connect a usb DVD drive and got the following in the logs:

[39971.219238] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '022'
[39971.219604] usb 1-1: New USB device found, idVendor=03f0, idProduct=5e07
[39971.219635] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[39971.219665] usb 1-1: Product: HP USB Mass Storage Device
[39971.219665] usb 1-1: Manufacturer: Hewlett-Packard
[39971.219696] usb 1-1: SerialNumber: 2104752485555557234
[39971.219726] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[39971.219757] hub 1-0:1.0: port 1 enable change, status 00000503
[39971.375396] Initializing USB Mass Storage driver...
[39971.375640] usb-storage 1-1:1.0: usb_probe_interface
[39971.375671] usb-storage 1-1:1.0: usb_probe_interface - got id
[39971.377471] scsi0 : SCSI emulation for USB Mass Storage devices
[39971.378784] usbcore: registered new interface driver usb-storage
[39971.378814] USB Mass Storage support registered.
[39971.381378] usb-storage: device found at 22
[39971.381378] usb-storage: waiting for device to settle before scanning
[39976.381317] usb-storage: device scan complete
[39976.394439] scsi 0:0:0:0: CD-ROM HP DVD-ROM rm475e JH21 PQ: 0 ANSI: 0

My guess is that h.e.n. is working, Is it? Further question is that how do I mount this one?(note: I have also posted http://talk.maemo.org/showthread.php?p=927103#post927103) for help on this.)

Cheers,
hi
I have the same problem. There is no dew/sr0, kernel messages ends
[74326.714263] scsi 5:0:0:0: CD-ROM TSSTcorp CDDVDW SE-T084M TD00 PQ: 0 ANSI: 0
and nothing else happens
In WHAT IS THE PROBLEM?

[bastibasti]

Maybe your bridge is not supported by the kernel?

[sygys]

i havent had any updates in some time now... are there still people working on USB host mode?

[hellsing]

Hello,
I've got a little problem:
i plug my usb key, it's enumerate, i can see it in dmesg.
The mount button doesn't work at all.
I can mount it by in root: mount /dev/sda /media/flash -o uid=29999,gid=29999,utf8,dmask=027,fmask=137
and its appear in /media/flash that i created.
Is there a way that the mount button work?
Thx


Nobody?
i guess it's because my flash drive is in /dev/sda instead of /dev/sda1, but how can i solve that?

[hotkolbas]

after a bit of stuffing around and 4 mice and 2 keyboards i found my HP wireless mouse/keyboard set work great. the total mA rating is 100mA and both work very well with no lag/jitters.
i did have a problem with a usb hub, i can get it working BUT nothing off that can be mounted. maybe power issue maybe not.

[pavi.kant]

I am using PowerKernel v46 multibooted with Nitdroid Ginderbread and the omap pr1.3 Kernel i installed the h-e-n software and bought the female to female converter...i am trying to connect a transcend 4gb flash drive with fat32 file system.
I run the device at high speed. nothing happens. some times when i open file manager it says no filesystem found(this is a rarity... most of the times nothing happens at all).
can you suggest what might be going wrong?... any help will be appreciated...

My Kernel messages read:

[26428.858734] WARNING: at /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/musb/musb_host.c:128 musb_h_tx_flush_fifo+0x94/0xcc()
[26428.858795] Could not flush host TX0 fifo: csr: 000a
[26428.858825] Modules linked in: ipv6 pn_pep vfat fat sd_mod scsi_mod iphb rfcomm panic_info_buff sco l2cap ext3 jbd omaplfb pvrsrvkm bridgedriver g_file_storage uinput board_rx51_camera et8ek8 omap_previewer_hack omap34xxcam_mod isp_mod iovmm videobuf_dma_sg videobuf_core omap3_iommu iommu2 iommu dspbridge ssi_mcsaab_imp phonet cmt_speech joydev wl12xx smc91x mii omap_ssi nokia_av hci_h4p mac80211 crc7 tsc2005 bluetooth fmtx_si4713 smia_sensor ad5820 adp1653 rtc_twl4030 tsl2563 leds_twl4030_vibra lis302dl videodev v4l1_compat compat_ioctl32 rtc_core smiaregs v4l2_int_device ntfs nls_utf8 leds_lp5523 led_class mmc_block omap_hsmmc mmc_core twl4030_wdt omap_wdt
[26428.859405] [<c0030470>] (dump_stack+0x0/0x14) from [<c0057444>] (warn_slowpath+0x64/0x80)
[26428.859497] [<c00573e0>] (warn_slowpath+0x0/0x80) from [<c01e9a60>] (musb_h_tx_flush_fifo+0x94/0xcc)
[26428.859558] r3:00000000 r2:c0349b67
[26428.859588] r6:d80ab100 r5:0000000a r4:0000000a
[26428.859649] [<c01e99cc>] (musb_h_tx_flush_fifo+0x0/0xcc) from [<c01ea930>] (musb_cleanup_urb+0xc0/0x10c)
[26428.859710] [<c01ea870>] (musb_cleanup_urb+0x0/0x10c) from [<c01eb134>] (musb_urb_dequeue+0x1dc/0x248)
[26428.859771] [<c01eaf58>] (musb_urb_dequeue+0x0/0x248) from [<c01cec9c>] (unlink1+0x108/0x114)
[26428.859863] [<c01ceb94>] (unlink1+0x0/0x114) from [<c01cfc38>] (usb_hcd_unlink_urb+0x9c/0xf8)
[26428.859924] [<c01cfb9c>] (usb_hcd_unlink_urb+0x0/0xf8) from [<c01d0af4>] (usb_kill_urb+0x84/0x14c)
[26428.860015] r7:c93afa80 r6:c93afa80 r5:cf0a6000 r4:00000000
[26428.860046] [<c01d0a70>] (usb_kill_urb+0x0/0x14c) from [<c01d1d78>] (usb_start_wait_urb+0x80/0x120)
[26428.860137] r6:00001388 r5:cf0a7e50 r4:00000000
[26428.860168] [<c01d1cf8>] (usb_start_wait_urb+0x0/0x120) from [<c01d1ff8>] (usb_control_msg+0xc4/0xe8)
[26428.860260] [<c01d1f34>] (usb_control_msg+0x0/0xe8) from [<c01cacec>] (hub_port_init+0x3d8/0x634)
[26428.860321] [<c01ca914>] (hub_port_init+0x0/0x634) from [<c01cc3e4>] (hub_events+0x86c/0xe64)
[26428.860412] [<c01cbb78>] (hub_events+0x0/0xe64) from [<c01ce034>] (hub_thread+0x30/0x19c)
[26428.860473] [<c01ce004>] (hub_thread+0x0/0x19c) from [<c006da90>] (kthread+0x54/0x80)
[26428.860534] r6:00000000 r5:c01ce004 r4:00000000
[26428.860565] [<c006da3c>] (kthread+0x0/0x80) from [<c005a950>] (do_exit+0x0/0x7bc)
[26428.860656] r5:00000000 r4:00000000
[26428.860687] ---[ end trace adbd6ed65c91e9be ]---
[26428.890655] usb 1-1: khubd timed out on ep0out len=0/0
[26435.101074] ------------[ cut here ]------------
[26435.101135] WARNING: at /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/musb/musb_host.c:128 musb_h_tx_flush_fifo+0x94/0xcc()
[26435.101196] Could not flush host TX0 fifo: csr: 000a
[26435.101226] Modules linked in: ipv6 pn_pep vfat fat sd_mod scsi_mod iphb rfcomm panic_info_buff sco l2cap ext3 jbd omaplfb pvrsrvkm bridgedriver g_file_storage uinput board_rx51_camera et8ek8 omap_previewer_hack omap34xxcam_mod isp_mod iovmm videobuf_dma_sg videobuf_core omap3_iommu iommu2 iommu dspbridge ssi_mcsaab_imp phonet cmt_speech joydev wl12xx smc91x mii omap_ssi nokia_av hci_h4p mac80211 crc7 tsc2005 bluetooth fmtx_si4713 smia_sensor ad5820 adp1653 rtc_twl4030 tsl2563 leds_twl4030_vibra lis302dl videodev v4l1_compat compat_ioctl32 rtc_core smiaregs v4l2_int_device ntfs nls_utf8 leds_lp5523 led_class mmc_block omap_hsmmc mmc_core twl4030_wdt omap_wdt
[26435.101806] [<c0030470>] (dump_stack+0x0/0x14) from [<c0057444>] (warn_slowpath+0x64/0x80)
[26435.101898] [<c00573e0>] (warn_slowpath+0x0/0x80) from [<c01e9a60>] (musb_h_tx_flush_fifo+0x94/0xcc)
[26435.101959] r3:00000000 r2:c0349b67
[26435.102020] r6:d80ab100 r5:0000000a r4:0000000a
[26435.102050] [<c01e99cc>] (musb_h_tx_flush_fifo+0x0/0xcc) from [<c01ea930>] (musb_cleanup_urb+0xc0/0x10c)
[26435.102111] [<c01ea870>] (musb_cleanup_urb+0x0/0x10c) from [<c01eb134>] (musb_urb_dequeue+0x1dc/0x248)
[26435.102203] [<c01eaf58>] (musb_urb_dequeue+0x0/0x248) from [<c01cec9c>] (unlink1+0x108/0x114)
[26435.102264] [<c01ceb94>] (unlink1+0x0/0x114) from [<c01cfc38>] (usb_hcd_unlink_urb+0x9c/0xf8)
[26435.102325] [<c01cfb9c>] (usb_hcd_unlink_urb+0x0/0xf8) from [<c01d0af4>] (usb_kill_urb+0x84/0x14c)
[26435.102416] r7:c93afa80 r6:c93afa80 r5:cf0a6000 r4:00000000
[26435.102478] [<c01d0a70>] (usb_kill_urb+0x0/0x14c) from [<c01d1d78>] (usb_start_wait_urb+0x80/0x120)
[26435.102539] r6:00001388 r5:cf0a7e50 r4:00000000
[26435.102600] [<c01d1cf8>] (usb_start_wait_urb+0x0/0x120) from [<c01d1ff8>] (usb_control_msg+0xc4/0xe8)
[26435.102661] [<c01d1f34>] (usb_control_msg+0x0/0xe8) from [<c01cacec>] (hub_port_init+0x3d8/0x634)
[26435.102752] [<c01ca914>] (hub_port_init+0x0/0x634) from [<c01cc3e4>] (hub_events+0x86c/0xe64)
[26435.102813] [<c01cbb78>] (hub_events+0x0/0xe64) from [<c01ce034>] (hub_thread+0x30/0x19c)
[26435.102874] [<c01ce004>] (hub_thread+0x0/0x19c) from [<c006da90>] (kthread+0x54/0x80)
[26435.102935] r6:00000000 r5:c01ce004 r4:00000000
[26435.102996] [<c006da3c>] (kthread+0x0/0x80) from [<c005a950>] (do_exit+0x0/0x7bc)
[26435.103057] r5:00000000 r4:00000000
[26435.103088] ---[ end trace adbd6ed65c91e9be ]---
[26435.124694] usb 1-1: khubd timed out on ep0out len=0/0
[26435.334686] usb 1-1: device not accepting address 35, error -110
[26435.459838] usb 1-1: new full speed USB device using musb_hdrc and address 36
[26441.458312] ------------[ cut here ]------------
[26441.458374] WARNING: at /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/musb/musb_host.c:128 musb_h_tx_flush_fifo+0x94/0xcc()
[26441.458404] Could not flush host TX0 fifo: csr: 000a
[26441.458404] Modules linked in: ipv6 pn_pep vfat fat sd_mod scsi_mod iphb rfcomm panic_info_buff sco l2cap ext3 jbd omaplfb pvrsrvkm bridgedriver g_file_storage uinput board_rx51_camera et8ek8 omap_previewer_hack omap34xxcam_mod isp_mod iovmm videobuf_dma_sg videobuf_core omap3_iommu iommu2 iommu dspbridge ssi_mcsaab_imp phonet cmt_speech joydev wl12xx smc91x mii omap_ssi nokia_av hci_h4p mac80211 crc7 tsc2005 bluetooth fmtx_si4713 smia_sensor ad5820 adp1653 rtc_twl4030 tsl2563 leds_twl4030_vibra lis302dl videodev v4l1_compat compat_ioctl32 rtc_core smiaregs v4l2_int_device ntfs nls_utf8 leds_lp5523 led_class mmc_block omap_hsmmc mmc_core twl4030_wdt omap_wdt
[26441.458709] [<c0030470>] (dump_stack+0x0/0x14) from [<c0057444>] (warn_slowpath+0x64/0x80)
[26441.458770] [<c00573e0>] (warn_slowpath+0x0/0x80) from [<c01e9a60>] (musb_h_tx_flush_fifo+0x94/0xcc)
[26441.458801] r3:00000000 r2:c0349b67
[26441.458801] r6:d80ab100 r5:0000000a r4:0000000a
[26441.458831] [<c01e99cc>] (musb_h_tx_flush_fifo+0x0/0xcc) from [<c01ea930>] (musb_cleanup_urb+0xc0/0x10c)
[26441.458862] [<c01ea870>] (musb_cleanup_urb+0x0/0x10c) from [<c01eb134>] (musb_urb_dequeue+0x1dc/0x248)
[26441.458923] [<c01eaf58>] (musb_urb_dequeue+0x0/0x248) from [<c01cec9c>] (unlink1+0x108/0x114)
[26441.458953] [<c01ceb94>] (unlink1+0x0/0x114) from [<c01cfc38>] (usb_hcd_unlink_urb+0x9c/0xf8)
[26441.458984] [<c01cfb9c>] (usb_hcd_unlink_urb+0x0/0xf8) from [<c01d0af4>] (usb_kill_urb+0x84/0x14c)
[26441.459014] r7:c93afa80 r6:c93afa80 r5:cf0a6000 r4:00000000
[26441.459045] [<c01d0a70>] (usb_kill_urb+0x0/0x14c) from [<c01d1d78>] (usb_start_wait_urb+0x80/0x120)
[26441.459075] r6:00001388 r5:cf0a7e50 r4:00000000
[26441.459106] [<c01d1cf8>] (usb_start_wait_urb+0x0/0x120) from [<c01d1ff8>] (usb_control_msg+0xc4/0xe8)
[26441.459136] [<c01d1f34>] (usb_control_msg+0x0/0xe8) from [<c01cacec>] (hub_port_init+0x3d8/0x634)
[26441.459197] [<c01ca914>] (hub_port_init+0x0/0x634) from [<c01cc3e4>] (hub_events+0x86c/0xe64)
[26441.459228] [<c01cbb78>] (hub_events+0x0/0xe64) from [<c01ce034>] (hub_thread+0x30/0x19c)
[26441.459259] [<c01ce004>] (hub_thread+0x0/0x19c) from [<c006da90>] (kthread+0x54/0x80)
[26441.459289] r6:00000000 r5:c01ce004 r4:00000000
[26441.459320] [<c006da3c>] (kthread+0x0/0x80) from [<c005a950>] (do_exit+0x0/0x7bc)
[26441.459350] r5:00000000 r4:00000000
[26441.459381] ---[ end trace adbd6ed65c91e9be ]---
[26441.542388] usb 1-1: khubd timed out on ep0out len=0/0
[26447.749176] ------------[ cut here ]------------
[26447.749267] WARNING: at /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/musb/musb_host.c:128 musb_h_tx_flush_fifo+0x94/0xcc()
[26447.749298] Could not flush host TX0 fifo: csr: 000a
[26447.749328] Modules linked in: ipv6 pn_pep vfat fat sd_mod scsi_mod iphb rfcomm panic_info_buff sco l2cap ext3 jbd omaplfb pvrsrvkm bridgedriver g_file_storage uinput board_rx51_camera et8ek8 omap_previewer_hack omap34xxcam_mod isp_mod iovmm videobuf_dma_sg videobuf_core omap3_iommu iommu2 iommu dspbridge ssi_mcsaab_imp phonet cmt_speech joydev wl12xx smc91x mii omap_ssi nokia_av hci_h4p mac80211 crc7 tsc2005 bluetooth fmtx_si4713 smia_sensor ad5820 adp1653 rtc_twl4030 tsl2563 leds_twl4030_vibra lis302dl videodev v4l1_compat compat_ioctl32 rtc_core smiaregs v4l2_int_device ntfs nls_utf8 leds_lp5523 led_class mmc_block omap_hsmmc mmc_core twl4030_wdt omap_wdt
[26447.749908] [<c0030470>] (dump_stack+0x0/0x14) from [<c0057444>] (warn_slowpath+0x64/0x80)
[26447.750000] [<c00573e0>] (warn_slowpath+0x0/0x80) from [<c01e9a60>] (musb_h_tx_flush_fifo+0x94/0xcc)
[26447.750091] r3:00000000 r2:c0349b67
[26447.750122] r6:d80ab100 r5:0000000a r4:0000000a
[26447.750152] [<c01e99cc>] (musb_h_tx_flush_fifo+0x0/0xcc) from [<c01ea930>] (musb_cleanup_urb+0xc0/0x10c)
[26447.750213] [<c01ea870>] (musb_cleanup_urb+0x0/0x10c) from [<c01eb134>] (musb_urb_dequeue+0x1dc/0x248)
[26447.750305] [<c01eaf58>] (musb_urb_dequeue+0x0/0x248) from [<c01cec9c>] (unlink1+0x108/0x114)
[26447.750366] [<c01ceb94>] (unlink1+0x0/0x114) from [<c01cfc38>] (usb_hcd_unlink_urb+0x9c/0xf8)
[26447.750457] [<c01cfb9c>] (usb_hcd_unlink_urb+0x0/0xf8) from [<c01d0af4>] (usb_kill_urb+0x84/0x14c)
[26447.750518] r7:c93afa80 r6:c93afa80 r5:cf0a6000 r4:00000000
[26447.750579] [<c01d0a70>] (usb_kill_urb+0x0/0x14c) from [<c01d1d78>] (usb_start_wait_urb+0x80/0x120)
[26447.750640] r6:00001388 r5:cf0a7e50 r4:00000000
[26447.750701] [<c01d1cf8>] (usb_start_wait_urb+0x0/0x120) from [<c01d1ff8>] (usb_control_msg+0xc4/0xe8)
[26447.750762] [<c01d1f34>] (usb_control_msg+0x0/0xe8) from [<c01cacec>] (hub_port_init+0x3d8/0x634)
[26447.750854] [<c01ca914>] (hub_port_init+0x0/0x634) from [<c01cc3e4>] (hub_events+0x86c/0xe64)
[26447.750915] [<c01cbb78>] (hub_events+0x0/0xe64) from [<c01ce034>] (hub_thread+0x30/0x19c)
[26447.750976] [<c01ce004>] (hub_thread+0x0/0x19c) from [<c006da90>] (kthread+0x54/0x80)
[26447.751037] r6:00000000 r5:c01ce004 r4:00000000
[26447.751098] [<c006da3c>] (kthread+0x0/0x80) from [<c005a950>] (do_exit+0x0/0x7bc)
[26447.751159] r5:00000000 r4:00000000
[26447.751190] ---[ end trace adbd6ed65c91e9be ]---
[26447.824554] usb 1-1: khubd timed out on ep0out len=0/0
[26448.029937] usb 1-1: device not accepting address 36, error -110
[26448.030029] hub 1-0:1.0: unable to enumerate USB device on port 1
[26448.030059] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[26448.030090] hub 1-0:1.0: port 1 enable change, status 00000101
[26450.202667] hub 1-0:1.0: hub_suspend
[26450.202758] usb usb1: bus auto-suspend
[26450.202789] musb_bus_suspend 2266: trying to suspend as a_host is_active=1
[26450.202850] usb usb1: bus suspend fail, err -16
[26450.202880] hub 1-0:1.0: hub_resume
[26450.202941] hub 1-0:1.0: port 1: status 0101 change 0000
[26450.203033] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[26450.203125] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[26450.327026] usb 1-1: new full speed USB device using musb_hdrc and address 37
[26455.326904] usb 1-1: khubd timed out on ep0in len=0/64
[26460.327056] usb 1-1: khubd timed out on ep0in len=0/64
[26465.327239] usb 1-1: khubd timed out on ep0in len=0/64
[26465.451873] usb 1-1: device descriptor read/64, error -110
[26470.561248] usb 1-1: khubd timed out on ep0in len=0/64

[joerg_rw]

please copy/move this post to http://talk.maemo.org/showthread.php?t=65232 [Announce] USB hostmode beta release.

This is clearly h-e-n kernel related, and needs somebody checking & fixing weird stuff e.g. in

http://mxr.maemo.org/fremantle/source/kernel/drivers/usb/musb/musb_regs.h#278
http://mxr.maemo.org/fremantle/source/kernel/drivers/usb/musb/musb_regs.h#480
http://mxr.maemo.org/fremantle/source/kernel/drivers/usb/musb/musb_host.c#111
etc.
Please add as much info as possible, esp *full* syslog as attachment, as well as precise description of the steps taken

thanks
jOERG

[NOMIOMI]

when i connect the wireless 2.4 ghz mouse ((((not bluetooht mouse))) with n900 after few moments its says that unable to connect no file system available any solution ?

[Nnet]

Hello I have problem with one flash drive. I dont know why...
One flash drive with FAT16 work well. External HDD with NTFS work well but This 4GB flash with FAT32 do not.

I dont know why but kernel do not mount this drive like sda1

Here is Kernel export:

[ 9356.581268] usb 1-1: New USB device found, idVendor=058f, idProduct=6387
[ 9356.581329] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9356.581359] usb 1-1: Product: Mass Storage
[ 9356.581390] usb 1-1: Manufacturer: USB
[ 9356.581420] usb 1-1: SerialNumber: 1F62ABCB
[ 9356.581451] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[ 9356.581542] hub 1-0:1.0: port 1 enable change, status 00000503
[ 9356.720764] Initializing USB Mass Storage driver...
[ 9356.721160] usb-storage 1-1:1.0: usb_probe_interface
[ 9356.721252] usb-storage 1-1:1.0: usb_probe_interface - got id
[ 9356.724273] scsi0 : SCSI emulation for USB Mass Storage devices
[ 9356.739410] usbcore: registered new interface driver usb-storage
[ 9356.739532] USB Mass Storage support registered.
[ 9356.751098] usb-storage: device found at 2
[ 9356.751129] usb-storage: waiting for device to settle before scanning
[ 9361.752319] usb-storage: device scan complete
[ 9361.753753] scsi 0:0:0:0: Direct-Access USB USB 2.0 Flash 8.07 PQ: 0 ANSI: 2
[ 9361.766571] sd 0:0:0:0: [sda] 7946240 512-byte hardware sectors: (4.06 GB/3.78 GiB)
[ 9361.766876] sd 0:0:0:0: [sda] Write Protect is off
[ 9361.766876] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 9361.766906] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 9361.771240] sd 0:0:0:0: [sda] 7946240 512-byte hardware sectors: (4.06 GB/3.78 GiB)
[ 9361.771514] sd 0:0:0:0: [sda] Write Protect is off
[ 9361.771545] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 9361.771575] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 9361.771606] sda:
[ 9362.093078] sd 0:0:0:0: [sda] Attached SCSI removable disk

[joerg_rw]

see http://talk.maemo.org/showpost.php?p=925442&postcount=119
it might help

[one1002]

hello...i'm having problem connecting my pendrive..i had no problem before this...but somehow i can't seem to mount the pendrive..the mount button doesn't seem to work..

and also, i kept getting different kernel messages..i've attached the different kernel message output below..

i got "port 1 not reset yet", "Forced hostmode error: a full/low-speed device attached but high-speed mode selected", "rejecting I/O to dead device", "Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2"..

those messages appeared in different logs..everytime i failed to mount, i exit, unplugged the cable, and restart H-E-N, but then i got a different message..this goes on and on..

pls help..

17546

17547

17548

17549

[joerg_rw]

look at ok sequence

[20268.602447] hub 1-0:1.0: port 1 enable change, status 00000101
[20270.602142] hub 1-0:1.0: hub_suspend
[20270.602233] usb usb1: bus auto-suspend
[20339.805114] slide (GPIO 71) is now open
[20360.664581] slide (GPIO 71) is now closed
[20363.013183] twl4030_usb twl4030_usb: HW_CONDITIONS 0x54/84; link 3
[20390.143859] usb usb1: usb resume
[20390.164459] hub 1-0:1.0: hub_resume
[20390.164520] hub 1-0:1.0: port 1: status 0101 change 0001
[20390.274017] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[20390.274078] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[20390.399169] usb 1-1: new high speed USB device using musb_hdrc and address 34
[20390.556976] usb 1-1: default language 0x0409
[20390.566711] usb 1-1: uevent
[20390.566925] usb 1-1: usb_probe_device
[20390.566955] usb 1-1: configuration #1 chosen from 1 choice
[20390.570831] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[20390.571197] usb 1-1:1.0: uevent
[20390.571441] libusual 1-1:1.0: usb_probe_interface
[20390.571533] libusual 1-1:1.0: usb_probe_interface - got id
[20390.571685] usb-storage 1-1:1.0: usb_probe_interface
[20390.571746] usb-storage 1-1:1.0: usb_probe_interface - got id
[20390.667022] scsi2 : SCSI emulation for USB Mass Storage devices
[20390.673095] /home/r00t/MyDocs/kernel-power-2.6.28-power46-wl1/drivers/usb/core/inode.c: creating file '034'
[20390.673797] usb 1-1: New USB device found, idVendor=0951, idProduct=1607
[20390.673858] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

esp the timestamps in there

you need to be patient with hostmode startup. It might take up to 20s (on sluggish devices) after vbus on, until you can enumerate. It may take another while from a successful enumerate until the device file ( /dev/* ) gets created so you can mount it.

[NOMIOMI]

here is the link of that keyboard and mouse which i want to connect with my n900

http://www.vmart.pk/main/labtec-ultra-flat-wireless-desktop-p-703.html

plz help me and guide me that how to connect it with n900

[one1002]

look at ok sequence

[20268.602447] hub 1-0:1.0: port 1 enable change, status 00000101
[20270.602142] hub 1-0:1.0: hub_suspend
[20270.602233] usb usb1: bus auto-suspend
[20339.805114] slide (GPIO 71) is now open
[20360.664581] slide (GPIO 71) is now closed
[20363.013183] twl4030_usb twl4030_usb: HW_CONDITIONS 0x54/84; link 3
[20390.143859] usb usb1: usb resume
[20390.164459] hub 1-0:1.0: hub_resume
[20390.164520] hub 1-0:1.0: port 1: status 0101 change 0001
[20390.274017] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[20390.274078] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[20390.399169] usb 1-1: new high speed USB device using musb_hdrc and address 34
[20390.556976] usb 1-1: default language 0x0409
[20390.566711] usb 1-1: uevent
[20390.566925] usb 1-1: usb_probe_device
[20390.566955] usb 1-1: configuration #1 chosen from 1 choice
[20390.570831] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[20390.571197] usb 1-1:1.0: uevent
[20390.571441] libusual 1-1:1.0: usb_probe_interface
[20390.571533] libusual 1-1:1.0: usb_probe_interface - got id
[20390.571685] usb-storage 1-1:1.0: usb_probe_interface
[20390.571746] usb-storage 1-1:1.0: usb_probe_interface - got id
[20390.667022] scsi2 : SCSI emulation for USB Mass Storage devices
[20390.673095] /home/r00t/MyDocs/kernel-power-2.6.28-power46-wl1/drivers/usb/core/inode.c: creating file '034'
[20390.673797] usb 1-1: New USB device found, idVendor=0951, idProduct=1607
[20390.673858] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

esp the timestamps in there

you need to be patient with hostmode startup. It might take up to 20s (on sluggish devices) after vbus on, until you can enumerate. It may take another while from a successful enumerate until the device file ( /dev/* ) gets created so you can mount it.

thank you sir..however, i still can't get it to detect..i waited like a minute after tapping the vbus boost, another minute after enumerate, and another minute after mount..nothing happens either..

then i got "unable to connect to filesystem"...hmm..reinstalling doesn't seem to work..but i can get mouse to work..

[istota]

GREETS AGAIN.
I have a question for which no one anywhere I can not answer.
As you can see it is possible (http://www.youtube.com/watch?v=zDzUG-bno6Q ) I have the same dvd-rom.
I have a kernel-power in 45, and additions to handle MohammadAG cd-rom.
information to the kernel.

[5162.718414] USB Mass Storage support registered.
[5162.721343] usb-storage: device found at 3
[5162.721374] usb-storage: waiting for device to settle before scanning
[5167.715332] usb-storage: device scan complete
[5167.716674] scsi 0:0:0:0: CD-ROM TSSTcorp CDDVDW SE-T084M TD00 PQ: 0 ANSI: 0
NO dev/sr0
Where should I look for and ask nowhere and interest solution to this issue.
THANK YOU GREETS

[freemangordon]

when i connect the wireless 2.4 ghz mouse ((((not bluetooht mouse))) with n900 after few moments its says that unable to connect no file system available any solution ?

Mice do not have file systems, so message seems reasonable to me. Do you have extmou installed? If not install it and check if mouse cursor appears after you press enumerate. And do not press mount button, mouse cannot be mounted.

[werebug]

I'm getting this error
I have latest firmware
Please tell me what I need to do to get hostmode workin with latest nokia firmware



your kernal has no proper matching version of hostmode api
Version 2010110 required.
Kernel-power v46 is suggested

[cuffy1]

I'm getting this error
I have latest firmware
Please tell me what I need to do to get hostmode workin with latest nokia firmware



your kernal has no proper matching version of hostmode api
Version 2010110 required.
Kernel-power v46 is suggested

i'm having the same problem, someone help??

[joerg_rw]

i'm having the same problem, someone help??
You can't get h-e-n working with "the latest firmware". h-e-n needs a specially patched kernel - kernel-power v46+ includes the h-e-n patches, you need to switch to (install) that kernel, and you should understand what are the implications in doing so, esp regarding incompatibilities with some other pkgs like early fcam drivers, multiboot, and generally SSU updates. You probably want to keep in mind you can NOT uninstall kernel-power, as your system doesn't work without any kernel, rather you need to follow the instructions that come with kernel-power whenever you want to go back to stock kernel as shipped by Nokia.

/j

[cuffy1]

You can't get h-e-n working with "the latest firmware". h-e-n needs a specially patched kernel - kernel-power v46+ includes the h-e-n patches, you need to switch to (install) that kernel, and you should understand what are the implications in doing so, esp regarding incompatibilities with some other pkgs like early fcam drivers, multiboot, and generally SSU updates. You probably want to keep in mind you can NOT uninstall kernel-power, as your system doesn't work without any kernel, rather you need to follow the instructions that come with kernel-power whenever you want to go back to stock kernel as shipped by Nokia.

/j

so it mite not be possible for me to install kernel power since i have nitdroid installed??

[evar]

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 ?

[joerg_rw]

so it mite not be possible for me to install kernel power since i have nitdroid installed??

Well, I never tried nitdroid, so here's what I learned from swearing and moaning users that had to reflash their N900 and sometimes even needed to find an external battery charger:
1) nitdroid needs multiboot
2) multiboot is not compatible with usual ways to install kernels. Instead it is flashing(!!!) kernel on each reboot, a procedure that users frequently like to do with roller shutters closed, doors locked, and every device except PC unplugged ;), so nothing will interrupt the process. Actually multiboot is a brilliant nasty hack.:p
3) installing power-kernel (as well as any arbitrary future kernel update via Nokia SSU) makes multiboot break the system, so you definitely will have to reflash, as long as your battery isn't depleted yet by bootlooping

Blame nitdroid devels why they didn't get round to adopt uBoot for their distro. There's a uBoot+powerkernel package in maemo-devel repo, and it *could* boot nitdroid as well (same way it does with meego), if those droids would care to nitty-gritty config their stuff accordingly.

Anyway, I suggest you stay with maemo :-) - and install kernel-power 46+ AFTER NUKING multiboot (however see IRC quote below)

(disclaimer: the above is all hearsay and might be obsolete info, as far as it concerns nitdroid and multiboot)


cheers
jOERG


<Flyser__> Hey guys, I have a problem. I just *un*installed nitdroid on my n900 and rebooted the device. now I see an empty multiboot menu and the device wont boot. what can I do to fix this? :-/
<Treibholz> Flyser__: I had the same problem just a few days ago :-)
... (hours later)
<Flyser__> flashing rootfs now -.-"

[ioiomi]

how can i use pl2303 on n900
i want to connect arduino
kernel

[blue_led]

"search" is a wonderful thing

driver compiled but never tested
http://talk.maemo.org/attachment.php?attachmentid=15958&d=1290827145

[geneven]

"search" is a wonderful thing

driver compiled but never tested
http://talk.maemo.org/attachment.php?attachmentid=15958&d=1290827145

Telling what message you are responding to is also a wonderful thing. There are several inquiries above your answer.

[joerg_rw]

you might be interested in http://talk.maemo.org/showthread.php?t=56932 "Printing with N900"

/j

[M_Scofield]

Hi, I need a bit of a help over here.
I have running kernel-power v46 and h-e-n: my usb mouse works great.
The problem is that when I connect my ntfs file system formatted usb hard drive, there is no data in the file manager, the blue light is on though ??
I tried as MohammadAG said:

mkdir -p /media/ntfs
mount /dev/sda1 /media/ntfs

but this error appears

Failed: No such a file or directory

What can I do ?

[peterleinchen]

Enabling (read-only) ntfs driver?

sudo modprobe ntfs
or
sudo modprobe -a ntfs

[M_Scofield]

Do I have to install a ntfs driver ? If yes from where can I download it ?
When I try your command It says:

user is not in the sudoers file. This insident will be reported.

Thank you !

[peterleinchen]

@m_scofield
Do not try to sudo as root.
Either as user with sudo or as root
modprobe -a ntfs

This is the ntfs driver, coming with the power kernel (v46), but it is not loaded automatically per default (as normally there is no need for ntfs on a linux device ;))

[M_Scofield]

I did what you said, this time the error didn't appear but I still have no data in File manager :(

I don't know what to do anymore :(:confused:

[peterleinchen]

Hmm, are You using standard Nokia file manager?
I do not think, that that this will work at all.

Did You enaple ntfs module prior to starting h-e-n?
You also need to mount as Mohammad said.

[NiQ]

Hi,
Apparently USB CD-ROM's not working. Here's a dump of the dmesg log:
hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[ 266.855407] usb 1-1: new high speed USB device using musb_hdrc and address 8
[ 267.004730] usb 1-1: default language 0x0409
[ 267.006408] usb 1-1: uevent
[ 267.006622] usb 1-1: usb_probe_device
[ 267.006652] usb 1-1: configuration #1 chosen from 1 choice
[ 267.006805] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 267.007080] usb 1-1:1.0: uevent
[ 267.007324] libusual 1-1:1.0: usb_probe_interface
[ 267.007385] libusual 1-1:1.0: usb_probe_interface - got id
[ 267.028289] /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '008'
[ 267.029022] usb 1-1: New USB device found, idVendor=13fd, idProduct=0842
[ 267.029052] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 267.029083] usb 1-1: Product: USB Mass Storage Device
[ 267.029113] usb 1-1: Manufacturer: TSSTcorp
[ 267.029144] usb 1-1: SerialNumber: SATASLIM00000000000
[ 267.029205] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[ 267.029266] hub 1-0:1.0: port 1 enable change, status 00000503
[ 267.117034] Initializing USB Mass Storage driver...
[ 267.117431] usb-storage 1-1:1.0: usb_probe_interface
[ 267.117523] usb-storage 1-1:1.0: usb_probe_interface - got id
[ 267.120300] scsi0 : SCSI emulation for USB Mass Storage devices
[ 267.122741] usbcore: registered new interface driver usb-storage
[ 267.122802] USB Mass Storage support registered.
[ 267.127136] usb-storage: device found at 8
[ 267.127166] usb-storage: waiting for device to settle before scanning
[ 272.122009] usb-storage: device scan complete
[ 272.123260] scsi 0:0:0:0: CD-ROM TSSTcorp USB Mass Storage 6.17 PQ: 0 ANSI: 0

The device is identified but no /dev/sr0 is created (possibly a kernel issue?)

Here's a dmesg log for comparison taken from a Debian machine when connecting the save drive to it:
[ 39.996064] usb 1-3: new high speed USB device using ehci_hcd and address 4
[ 40.129005] usb 1-3: New USB device found, idVendor=13fd, idProduct=0842
[ 40.129008] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 40.129010] usb 1-3: Product: USB Mass Storage Device
[ 40.129012] usb 1-3: Manufacturer: TSSTcorp
[ 40.129014] usb 1-3: SerialNumber: SATASLIM00000000000
[ 40.129111] usb 1-3: configuration #1 chosen from 1 choice
[ 40.213776] Initializing USB Mass Storage driver...
[ 40.213878] scsi4 : SCSI emulation for USB Mass Storage devices
[ 40.214014] usbcore: registered new interface driver usb-storage
[ 40.214017] USB Mass Storage support registered.
[ 40.214096] usb-storage: device found at 4
[ 40.214097] usb-storage: waiting for device to settle before scanning
[ 45.212158] usb-storage: device scan complete
[ 45.212655] scsi 4:0:0:0: CD-ROM TSSTcorp CDDVDW SE-S084C TS01 PQ: 0 ANSI: 0
[ 45.221146] sr1: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 45.221765] sr 4:0:0:0: Attached scsi CD-ROM sr1
[ 45.223166] sr 4:0:0:0: Attached scsi generic sg2 type 5

Note the last 3 lines (marked as bold) that assign the block device to the drive - They don't exist in the N900 log (even after 5 mins of waiting).
Oh, and yes, the drive is fully powered from an external source.

Thanks!

[M_Scofield]

Hmm, are You using standard Nokia file manager?
I do not think, that that this will work at all.

Did You enaple ntfs module prior to starting h-e-n?
You also need to mount as Mohammad said.

Yes I am sure, I'm using the default Nokia file manager.

I haven't enabled any ntfs module.:confused: I am so newbie. :mad:
All I did is that I installed the power Kernel (v46), installed h-e-n and typed that you have said (modprobe -a ntfs)

[NiQ]

OK, apparently the problem of not being able to mount CD-ROMs is due to the modules cdrom.ko, sr_mod.ko and sg.ko being missing from the kernel-power-modules package. I'll try to compile them from source and ask titan to include them in the official package.

[peterleinchen]

@m_scofield

Okay, let's try one more time.
Power kernel comes with ntfs module, but it needs to be loaded via
modprobe -a ntfs
h-e-n will give You ability to enumerate Your external HDD via USB
start h-e-n, choose speed (most probably full), press VBUS (hopefully Your HDD has external or Y-cable power supply), press enumerate
create a mount point with
mkdir /media/ntfs
now mount the enumerated sda1 manually via
mount -t ntfs /dev/sda1 /media/ntfs -o uid=29999,gid=29999,utf8,dmask=027,fmask=137
You should now be able to browse your ntfs files from within /media/ntfs folder using xterm and ls command
You may also CuteExplorer or FileBox, but not nokia file manager

Hope. this helps and was understandable enough :)

[iscio]

please help me, I am not able to see a key :-(

m [<c01cec9c>] (unlink1+0x108/0x114)
[46999.140167] [<c01ceb94>] (unlink1+0x0/0x114) from [<c01cfc38>] (usb_hcd_unlink_urb+0x9c/0xf8)
[46999.140258] [<c01cfb9c>] (usb_hcd_unlink_urb+0x0/0xf8) from [<c01d0af4>] (usb_kill_urb+0x84/0x14c)
[46999.140319] r7:cfc11d80 r6:cfc11d80 r5:cf0a6000 r4:00000000
[46999.140380] [<c01d0a70>] (usb_kill_urb+0x0/0x14c) from [<c01d1d78>] (usb_start_wait_urb+0x80/0x120)
[46999.140441] r6:00001388 r5:cf0a7e50 r4:00000000
[46999.140502] [<c01d1cf8>] (usb_start_wait_urb+0x0/0x120) from [<c01d1ff8>] (usb_control_msg+0xc4/0xe8)
[46999.140563] [<c01d1f34>] (usb_control_msg+0x0/0xe8) from [<c01cacec>] (hub_port_init+0x3d8/0x634)
[46999.140655] [<c01ca914>] (hub_port_init+0x0/0x634) from [<c01cc3e4>] (hub_events+0x86c/0xe64)
[46999.140716] [<c01cbb78>] (hub_events+0x0/0xe64) from [<c01ce034>] (hub_thread+0x30/0x19c)
[46999.140777] [<c01ce004>] (hub_thread+0x0/0x19c) from [<c006da90>] (kthread+0x54/0x80)
[46999.140838] r6:00000000 r5:c01ce004 r4:00000000
[46999.140899] [<c006da3c>] (kthread+0x0/0x80) from [<c005a950>] (do_exit+0x0/0x7bc)
[46999.140960] r5:00000000 r4:00000000
[46999.140991] ---[ end trace 24f0a7c3bb577e01 ]---
[46999.142608] usb 1-1: khubd timed out on ep0out len=0/0
[46999.349212] usb 1-1: device not accepting address 113, error -110
[46999.349304] hub 1-0:1.0: unable to enumerate USB device on port 1
[46999.349334] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[46999.349365] hub 1-0:1.0: port 1 enable change, status 00000501
[47001.349365] hub 1-0:1.0: hub_suspend
[47001.349456] usb usb1: bus auto-suspend
[47001.349487] musb_bus_suspend 2266: trying to suspend as a_host is_active=1
[47001.349548] usb usb1: bus suspend fail, err -16
[47001.349578] hub 1-0:1.0: hub_resume
[47001.349639] hub 1-0:1.0: port 1: status 0501 change 0000
[47001.349731] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[47001.349792] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s
[47001.474426] usb 1-1: new high speed USB device using musb_hdrc and address 114
[47006.474365] usb 1-1: khubd timed out on ep0in len=0/64
[47011.474304] usb 1-1: khubd timed out on ep0in len=0/64
[47016.474365] usb 1-1: khubd timed out on ep0in len=0/64
[47016.599426] usb 1-1: device descriptor read/64, error -110
[47021.708526] usb 1-1: khubd timed out on ep0in len=0/64
[47025.622589] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[47026.708557] usb 1-1: khubd timed out on ep0in len=0/64
[47026.833557] usb 1-1: device descriptor read/64, error -71
[47027.067962] usb 1-1: new high speed USB device using musb_hdrc and address 115
[47027.157104] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[47027.193359] usb 1-1: device descriptor read/64, error -71
[47027.427581] usb 1-1: device descriptor read/64, error -71
[47027.661651] usb 1-1: new high speed USB device using musb_hdrc and address 116
[47028.015533] Forced hostmode error: no device attached
[47028.083587] usb 1-1: device not accepting address 116, error -71
[47028.146087] hub 1-0:1.0: unable to enumerate USB device on port 1
[47028.146118] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[47028.146148] hub 1-0:1.0: port 1, status 0501, change 0003, 480 Mb/s
[47028.302459] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x501
[47028.427551] usb 1-1: new high speed USB device using musb_hdrc and address 118
[47028.552337] usb 1-1: device descriptor read/64, error -71
[47028.786682] usb 1-1: device descriptor read/64, error -71
[47029.021057] usb 1-1: new high speed USB device using musb_hdrc and address 119
[47029.146057] usb 1-1: device descriptor read/64, error -71
[47029.380706] usb 1-1: device descriptor read/64, error -71
[47029.615051] usb 1-1: new high speed USB device using musb_hdrc and address 120
[47030.036682] usb 1-1: device not accepting address 120, error -71
[47030.161773] usb 1-1: new high speed USB device using musb_hdrc and address 121
[47030.583557] usb 1-1: device not accepting address 121, error -71
[47030.583648] hub 1-0:1.0: unable to enumerate USB device on port 1
[47030.583679] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[47030.583709] hub 1-0:1.0: port 1 enable change, status 00000501
[47033.216430] hub 1-0:1.0: hub_suspend
[47033.216491] usb usb1: bus auto-suspend
[47033.216522] musb_bus_suspend 2266: trying to suspend as a_host is_active=1
[47033.216583] usb usb1: bus suspend fail, err -16
[47033.216613] hub 1-0:1.0: hub_resume
[47033.216674] hub 1-0:1.0: port 1: status 0501 change 0000
[47033.216827] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[47033.216888] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s
[47033.341339] usb 1-1: new high speed USB device using musb_hdrc and address 122
[47033.466430] usb 1-1: device descriptor read/64, error -71
[47033.700714] usb 1-1: device descriptor read/64, error -71
[47033.935089] usb 1-1: new high speed USB device using musb_hdrc and address 123
[47034.060089] usb 1-1: device descriptor read/64, error -71
[47034.294494] usb 1-1: device descriptor read/64, error -71
[47034.528869] usb 1-1: new high speed USB device using musb_hdrc and address 124
[47034.950714] usb 1-1: device not accepting address 124, error -71
[47035.076324] usb 1-1: new high speed USB device using musb_hdrc and address 125
[47035.497558] usb 1-1: device not accepting address 125, error -71
[47035.497650] hub 1-0:1.0: unable to enumerate USB device on port 1
[47035.497680] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[47035.497711] hub 1-0:1.0: port 1 enable change, status 00000501
[47038.216430] hub 1-0:1.0: hub_suspend
[47038.216522] usb usb1: bus auto-suspend
[47038.216552] musb_bus_suspend 2266: trying to suspend as a_host is_active=1
[47038.216583] usb usb1: bus suspend fail, err -16
[47038.216613] hub 1-0:1.0: hub_resume
[47038.216705] hub 1-0:1.0: port 1: status 0501 change 0000
[47038.216796] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[47038.216857] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s
[47038.341552] usb 1-1: new high speed USB device using musb_hdrc and address 126
[47038.466461] usb 1-1: device descriptor read/64, error -71
[47038.701019] usb 1-1: device descriptor read/64, error -71
[47038.935363] usb 1-1: new high speed USB device using musb_hdrc and address 127
[47039.060302] usb 1-1: device descriptor read/64, error -71
[47039.294616] usb 1-1: device descriptor read/64, error -71
[47039.528991] usb 1-1: new high speed USB device using musb_hdrc and address 2
[47039.950775] usb 1-1: device not accepting address 2, error -71
[47040.076232] usb 1-1: new high speed USB device using musb_hdrc and address 3
[47040.497711] usb 1-1: device not accepting address 3, error -71
[47040.497802] hub 1-0:1.0: unable to enumerate USB device on port 1
[47040.497833] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[47040.497863] hub 1-0:1.0: port 1 enable change, status 00000501
[47043.218170] hub 1-0:1.0: hub_suspend
[47043.218200] usb usb1: bus auto-suspend
[47043.218231] musb_bus_suspend 2266: trying to suspend as a_host is_active=1
[47043.218261] usb usb1: bus suspend fail, err -16
[47043.218261] hub 1-0:1.0: hub_resume
[47043.218322] hub 1-0:1.0: port 1: status 0501 change 0000
[47043.218353] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[47043.218414] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s
[47043.341339] usb 1-1: new high speed USB device using musb_hdrc and address 4
[47043.466400] usb 1-1: device descriptor read/64, error -71
[47043.700927] usb 1-1: device descriptor read/64, error -71
[47043.935211] usb 1-1: new high speed USB device using musb_hdrc and address 5
[47044.060211] usb 1-1: device descriptor read/64, error -71
[47044.294616] usb 1-1: device descriptor read/64, error -71
[47044.528961] usb 1-1: new high speed USB device using musb_hdrc and address 6
[47044.950714] usb 1-1: device not accepting address 6, error -71
[47045.075714] usb 1-1: new high speed USB device using musb_hdrc and address 7
[47045.497650] usb 1-1: device not accepting address 7, error -71
[47045.497772] hub 1-0:1.0: unable to enumerate USB device on port 1
[47045.497863] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[47045.497924] hub 1-0:1.0: port 1 enable change, status 00000501
~ $

[M_Scofield]

I did each step precisely as you told me.

1) modprobe -a ntfs
2) Started h-e-n (my hdd doesn't have external power cable)
3) mount -t ntfs /dev/sda1 /media/ntfs -o uid=29999,gid=29999,utf8,dmask=027,fmask=137

and the following error appeared :mad:

Mount: mounting /dev/sda1 on /media/ntfs failed: No such a file or directory

OK I went to /media there was the ntfs and moved to the another directory /dev but there were no "sda1" in it :confused::confused:

[peterleinchen]

OK, so we have to stop here.
The N900 can deliver only 200 mA and this will never be enough for an external HDD. Without additional power supply You will never see files, respectively a /dev/sda1 device (after enumerating) ....

I was successful with a standard Y cable providing the current with the second USB connector from my laptop (or USB charger).
Or You my try with a powered hub.

[NiQ]

OK, apparently the problem of not being able to mount CD-ROMs is due to the modules cdrom.ko, sr_mod.ko and sg.ko being missing from the kernel-power-modules package. I'll try to compile them from source and ask titan to include them in the official package.
Regarding that earlier post I made - confirmed this is due to missing modules. These modules are included in the original h-e-n hostmode kernel (that's how there are a few videos out there showing the N900 play DVD's etc) but they are not included in kernel-power.
The bad news: You cannot transfer the modules from the old hostmode kernel to kernel-power because of symbol differences.
If you try compiling them against kernel-power-headers you will be able to get cdrom.ko and sg.ko to load but not sr_mod.ko, which means that it's as good as nothing.

Only solutions to that problem:
1. Revert back to the original hostmode kernel (and lose all the other unrelated improvements that kernel-power features).
2. Recompile kernel-power and add support for necessary modules (such as CD-ROM). I've written a very thorough guide (http://talk.maemo.org/showthread.php?t=71069) on how to do that.
3. Since I've already done method 2, I now have a kernel image based on kernel-power 46 with support for CD-ROM drives and DVB dongles. I may upload it and post a download link once I've tested it and am more-or-less confident there are no problems or regressions. If you want it earlier, please send me a PM.

[sunny2nisha]

plz help me conntecting usb mouse in N900

HEN Application was successfully installed in my phone but when we connect flash drives and keyboard through USB mouse it works but i cannot use mouse its not working plz suggest..............
i am using logitech cordless desktop mk250

[Asbahl]

Regarding that earlier post I made - confirmed this is due to missing modules. These modules are included in the original h-e-n hostmode kernel (that's how there are a few videos out there showing the N900 play DVD's etc) but they are not included in kernel-power.
The bad news: You cannot transfer the modules from the old hostmode kernel to kernel-power because of symbol differences.
If you try compiling them against kernel-power-headers you will be able to get cdrom.ko and sg.ko to load but not sr_mod.ko, which means that it's as good as nothing.

Only solutions to that problem:
1. Revert back to the original hostmode kernel (and lose all the other unrelated improvements that kernel-power features).
2. Recompile kernel-power and add support for necessary modules (such as CD-ROM). I've written a very thorough guide (http://talk.maemo.org/showthread.php?t=71069) on how to do that.
3. Since I've already done method 2, I now have a kernel image based on kernel-power 46 with support for CD-ROM drives and DVB dongles. I may upload it and post a download link once I've tested it and am more-or-less confident there are no problems or regressions. If you want it earlier, please send me a PM.

Guy,

a) I'm using the kernel-power 46-wl1 that has the bleeding-edge WLAN driver for packet injections. It's important remember the source code is shared;

b) I live in Brazil and the digital tv standard here is ISDB not DVB.

There would be some way to add this drive in a kernel-power 46-wl1?

[joerg_rw]

Regarding that earlier post I made - confirmed this is due to missing modules. These modules are included in the original h-e-n hostmode kernel (that's how there are a few videos out there showing the N900 play DVD's etc) but they are not included in kernel-power.

Thank you so much for straightening that. I'll go to push PK maintainer to fix this extremely annoying flaw. In the meantime we might consider to host the fixed PK on h-e-n garage.

thanks
jOERG

[NiQ]

Guy,

a) I'm using the kernel-power 46-wl1 that has the bleeding-edge WLAN driver for packet injections. It's important remember the source code is shared;

b) I live in Brazil and the digital tv standard here is ISDB not DVB.

There would be some way to add this drive in a kernel-power 46-wl1?
Sure, my custom kernel does not actually include any source changes, only configuration changes (i.e. include the drivers that were missing). It should be possible to recompile kernel-power-wl1 and add these drivers to the configuration as well.

About TV/DVB/ISDB - I have to admit that I've yet to succeed in watching TV through the N900. The driver loads but still doesn't really work with the DVB dongle that I have and there's also the issue of userspace software which may have to be patched and/or recompiled from source. Anyway, the whole watching TV issue is still in its infancy and should not be considered as working by anyone. Adding the kernel drivers for DVB is just a first step in the right direction, therefore I think that your concern is a bit premature. CD/DVD drive / CD writing support is confirmed working, though.
On the second hand, you do have a point here - ISDB support is very new in Linux and AFAIK preliminary support was added to the Linux kernel in version 2.6.32 - which is newer than the version used by N900 (2.6.28). If we want this to happen, we may have to upgrade the N900 to a newer kernel - which is a big project.

Thank you so much for straightening that. I'll go to push PK maintainer to fix this extremely annoying flaw. In the meantime we might consider to host the fixed PK on h-e-n garage.

thanks
jOERG
Would really like to see that happening. I'm gonna send cheve my custom kernel for testing today and if he reports no problems I'll send you the binary (no need for sources as the only changes are configuration).

[Asbahl]

Sure, my custom kernel does not actually include any source changes, only configuration changes (i.e. include the drivers that were missing). It should be possible to recompile kernel-power-wl1 and add these drivers to the configuration as well.

About TV/DVB/ISDB - I have to admit that I've yet to succeed in watching TV through the N900. The driver loads but still doesn't really work with the DVB dongle that I have and there's also the issue of userspace software which may have to be patched and/or recompiled from source. Anyway, the whole watching TV issue is still in its infancy and should not be considered as working by anyone. Adding the kernel drivers for DVB is just a first step in the right direction, therefore I think that your concern is a bit premature. CD/DVD drive / CD writing support is confirmed working, though.
On the second hand, you do have a point here - ISDB support is very new in Linux and AFAIK preliminary support was added to the Linux kernel in version 2.6.32 - which is newer than the version used by N900 (2.6.28). If we want this to happen, we may have to upgrade the N900 to a newer kernel - which is a big project.


Would really like to see that happening. I'm gonna send cheve my custom kernel for testing today and if he reports no problems I'll send you the binary (no need for sources as the only changes are configuration).

NiQ,

Could you PM with your contact, I have PM do not available to me!

[ahbarnasha]

hostmode doesn't work for me,

when I try to connect a usb mouse or flash drive sometimes nothing happens and sometimes it says:
"can't mount filesystem" (or something like that, it's translated)

dmesg shows:
... new full speed USB device using musb_hdrc ...

and after that a couple of lines like these:
usb 1-1: khubd timed out on ep0out len=0/0
usb 1-1: khubd timed out on ep0out len=0/64

I've tried different speeds, does anybody know what's wrong here?

Thanks in advance,
AhBarnasha

[Schturman]

Please Help !
It's my first time for using USB host mode...
After connecting I can see and play files on my SD card by card reader - no problem..
But when I tried to transfer this files to the phone - it's failed all the time... it's procure 10-20% and stops, card reader shuts down.. something like auto unmount.. I tried with another card reader - the same result. Restart the phone did not help...
After that I tried to transfer from SD card to memory card on the phone (it's the first time I put memory card in my phone..), transfer succeeded. Here reveals a new problem..
When I tried to move the file from a memory card in to the phone to one of the folders in MyDocs - I got a message that "you don't have permission, the file system read-only!"..
I was in shock.. I tried to transfer files in MyDocs from one folder to another and I got the same message... and again, restart the phone did not help...
All this stuff I tried with default file manager and with FileBox...
Now I can not do anything with the files - not copy, not move... only running..
What can I do? How I can change this permission ?
Thanks

[stlpaul]

Please Help !
It's my first time for using USB host mode...
After connecting I can see and play files on my SD card by card reader - no problem..
But when I tried to transfer this files to the phone - it's failed all the time... it's procure 10-20% and stops, card reader shuts down.. something like auto unmount.. I tried with another card reader - the same result. Restart the phone did not help...
After that I tried to transfer from SD card to memory card on the phone (it's the first time I put memory card in my phone..), transfer succeeded. Here reveals a new problem..
When I tried to move the file from a memory card in to the phone to one of the folders in MyDocs - I got a message that "you don't have permission, the file system read-only!"..
I was in shock.. I tried to transfer files in MyDocs from one folder to another and I got the same message... and again, restart the phone did not help...
All this stuff I tried with default file manager and with FileBox...
Now I can not do anything with the files - not copy, not move... only running..
What can I do? How I can change this permission ?
Thanks

Unmount MyDocs partition and fsck it. Or remount it read-write like:

mount -o remount,rw /home/user/MyDocs

[Schturman]

Thanks, it's helped..
But when I again tried to transfer file by FileBox, the filebox is stoped and freezed, after restart I got a new look of FileBox (see pic)
After this I tried to transfer with default file manager and it's worked fine. Movie 1.4GB - 3 min, 2.5GB - 4-5 min...
I tried to uninstall and reinstall the FileBox, but it's still with this bad look...
I tried again to transfer by FileBox and again it's stoped work and freezed... I think the problem in FileBox..
Any ideas to fix this ?
Thanks

[Schturman]

ok.. after "big" reboot, the filebox is loaded correctly..
I think about two things why the filebox not worked:
1) The filebox not like and can't work with usb host mode..
2) The filebox work with root access, and this not compatible to work with usb host mode..

Someone, any ideas ? or why filebox crashed when his work with usb host mode..
Thanks

[joerg_rw]

ok.. after "big" reboot, the filebox is loaded correctly..
I think about two things why the filebox not worked:
1) The filebox not like and can't work with usb host mode..
2) The filebox work with root access, and this not compatible to work with usb host mode..

Someone, any ideas ? or why filebox crashed when his work with usb host mode..
Thanks

filebox shouldn't even notice it's USB hostmode. That's some other problem unrelated to hostmode, rather it's maybe the filesystem on your memstick that is confusing filebox, or whatever.

/j

[Schturman]

Thanks..
Today I tried again to transfer the movie from my disk on key to the phone with default file manager and again it's crashed...
Don't know why...

[andyt12]

From reading the last 19 pages it seems hostmode is working rather well, It looks like most of the issues are user error and not understanding how linux works.

[ahbarnasha]

From reading the last 19 pages it seems hostmode is working rather well, It looks like most of the issues are user error and not understanding how linux works.

do you know what error I'm making?

when I try to connect a usb mouse or flash drive sometimes nothing happens and sometimes it says:
"can't mount filesystem" (or something like that, it's translated)

dmesg shows:
... new full speed USB device using musb_hdrc ...

and after that a couple of lines like these:
usb 1-1: khubd timed out on ep0out len=0/0
usb 1-1: khubd timed out on ep0out len=0/64

I've tried different speeds, does anybody know what's wrong here?

ps:
the lights on my flash disk and mouse don't light up

[cheve]

@ahbarnasha: for USB drive, sometime I have to select umount and then mount again to make it work. Also please note that it was said that you may need to wait for sometime(may be upto 1min.; I don't remember the recommended time) for the system to sort out everything.

In any case, did the log report the name of the manufacturer and product for your USB drive or mouse, if it does then the good news is that h.e.n. is most likely working as design; and the bad news is that there are issue with drivers or other thing in play that is causing you the problem.

good luck,
cheers,

[sudarsan_avs]

when I try to connect a usb mouse or flash drive sometimes nothing happens and sometimes it says:
"can't connect, no filesystem"

dmesg shows:
... new full speed USB device using musb_hdrc ...

Kernel Message:
usb 1-1: khubd timed out on ep0out len=0/0

I cannot see the pen drive listed on the file manager, but shown in Xarchiver - however while I try to open the pen drive - error: Failed to execute child process "gnome-mount" (no such file or dir)

pls help..

[ahbarnasha]

@ahbarnasha: for USB drive, sometime I have to select umount and then mount again to make it work. Also please note that it was said that you may need to wait for sometime(may be upto 1min.; I don't remember the recommended time) for the system to sort out everything.

In any case, did the log report the name of the manufacturer and product for your USB drive or mouse, if it does then the good news is that h.e.n. is most likely working as design; and the bad news is that there are issue with drivers or other thing in play that is causing you the problem.

good luck,
cheers,

Hi,

I tried again with my mouse, the manufacurer doesn't show.
when I wait a while it fails to connect and tries again and again.
dmesg shows:
[41385.422760] usb 1-1: device descriptor read/64, error -110

and sometimes a warning with a large trace (I attached one)
then it starts over..

I hope you can help, thanks anyway.

[sunny2nisha]

OMG it works

[biketool]

This is a great thread, my USB key loads and mounts out of the box. I am still working on getting my MP3 player to mount properly and USB Ethernet dongle to show as a /dev/eth* net interface both kernel modules load and it appears they just need one or two more things to work. I just need to work my way up the thread a bit.
It would really help if those with successful fixes were posted or linked on the wiki. http://wiki.maemo.org/N900_Hardware_USB_Host

[bentech4u]

now my problem is with NTFS mounting..

the drive is detected as /dev/sda1.and i mounted with a command

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

also showing in the file manager

IF i try to paste anything to this drive, then i got an error message like " mounted as read-only" something like that..

please help me friends

Thanks

[Bratag]

I just connected my nook to my phone. Nook is recognised as a Nook and can be mounted as storage ... freaking sweet.

[peterleinchen]

Hi bentech4u.
Nothing wrong. You did it right.
This driver is a read-only driver. No chance to get it read-writeable.
Maybe next version of power kernel?

[mehdi.gl]

Hi everybody.
Please I need help !!!!!!
I installed the kernel power
I installed HEN
I installed extmou


I followed the steps described on the net
BUT
Nothing is working
I tested flash drives, mouse, keyboards etc.....


Please Help me, I'm excited to test the USB HOST MODE feature on my n900

:''(((

[mehdi.gl]

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

[mehdi.gl]

Please help me !!

[mehdi.gl]

This is the message error shown when connecting a mouse for example
"Unable to connect, no file system available"

[yorkey]

This is the message error shown when connecting a mouse for example

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

MIce and keyboards do not need mounting.

[yorkey]

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

[biketool]

Please help me !!

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

[woody14619]

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


Did you try using the flag rw?
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.

[mehdi.gl]

Did you try using the flag rw?
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.


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

[mehdi.gl]

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 !!
:(

[mehdi.gl]

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


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

[mehdi.gl]

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

[mehdi.gl]

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

[adi619]

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


If you mount under /media, it should.
mkdir -p /media/ntfs
mount /dev/sda1 /media/ntfs

[mehdi.gl]

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

[mehdi.gl]

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 :)

[jackjohn]

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

[evar]

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=927995&postcount=127


many thanks to MVEPLUS !!!

[jackjohn]

I already try that but still not working .

Can some assists me.

plzzzzzzzzz

[mveplus]

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...
$dmesg
$lsusb

Greetings,
mveplus

P.S. Okey I didi compile your source code against kernel-power-headers, but got some errors during compilation:
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 (http://dl.dropbox.com/u/12258575/N900/sr9600.zip) 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.

[jackjohn]

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...
$dmesg
$lsusb

Greetings,
mveplus

P.S. Okey I didi compile your source code against kernel-power-headers, but got some errors during compilation:
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 (http://dl.dropbox.com/u/12258575/N900/sr9600.zip) 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

[mveplus]

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 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

[joerg_rw]

Warning: __bad_udelay
sounds odd.

/j

@mveplus:

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

http://freeyourphone.de/portal_v1/viewtopic.php?f=20&t=1430&p=14569#p14569

[mveplus]

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:
Warning: __bad_udelay
sounds odd.

/j

@mveplus:

http://freeyourphone.de/portal_v1/viewtopic.php?f=20&t=1430&p=14569#p14569

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

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 (http://dl.dropbox.com/u/12258575/N900/usb2net_n900_v.0.1.8.deb) so I compiled today hope it will work this time! usbnet.ko (http://dl.dropbox.com/u/12258575/N900/usbnet.zip)

[jackjohn]

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 #

[mveplus]

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"



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

[sudarsan_avs]

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...

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

[biketool]

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.

[jackjohn]

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
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"
~

[jackjohn]

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 #

[jackjohn]

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.

[NiQ]

To set static IP address root yourself then type:
ifconfig eth0 <ip-address> netmask <subnet-mask>
ifconfig eth0 up


Also add default gateway if you want Internet access:
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:
ifup eth0

Cheers.

[jackjohn]

Dear NiQ,

Noted and thanks

[cheve]

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

[cheve]

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=921203&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

[ubnefio]

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

[Estel]

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=921203&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

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...

[joerg_rw]

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

cheers
jOERG

[cheve]

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.

[cheve]

@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,

[Estel]

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.

[shadowjk]

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.

[singpolyma]

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:


[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

[singpolyma]

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:


[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 :)

[Estel]

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...

[benitoh]

Hi I cant install h-e-n when I click to install I get a message:
Unable to install 'h-e-n (USB Hostmode GUI)' conflicting application packages.

when I click on details I got:
kernel-modules-maemo

[singpolyma]

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.

Hmmm... I tried this with a new powered USB hub with my keyboard+mouse, but no luck. What's strange is that the keyboard and mouse work fine by themselves when not through a hub.

Here is dmesg output after a failed attempt and also a success with just the mouse:

[115066.722564] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[115071.094238] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[115071.361694] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[115081.727203] Forced hostmode error: no device attached
[115081.727264] usb usb1: usb resume
[115081.750335] hub 1-0:1.0: hub_resume
[115081.750396] hub 1-0:1.0: port 1: status 0301 change 0001
[115081.860473] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[115081.860534] hub 1-0:1.0: port 1, status 0301, change 0000, 1.5 Mb/s
[115081.984863] usb 1-1: new low speed USB device using musb_hdrc and address 96
[115086.984893] usb 1-1: khubd timed out on ep0in len=0/64
[115088.747558] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[115088.748199] regulator_disable: not in use by this consumer
[115088.748229] regulator_disable: not in use by this consumer
[115091.985260] usb 1-1: khubd timed out on ep0in len=0/64
[115092.110046] usb 1-1: device descriptor read/64, error -19
[115092.344238] usb 1-1: device descriptor read/64, error -19
[115092.516143] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
[115092.578582] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115092.789581] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115093.000518] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115093.000549] hub 1-0:1.0: port_wait_reset: err = -16
[115093.000579] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115093.212341] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115093.422424] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115093.633483] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115093.633514] hub 1-0:1.0: port_wait_reset: err = -16
[115093.633544] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115093.844177] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115094.055572] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115094.266296] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115094.266326] hub 1-0:1.0: port_wait_reset: err = -16
[115094.266357] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115094.477264] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115094.688171] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115094.899078] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115094.899139] hub 1-0:1.0: port_wait_reset: err = -16
[115094.899169] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115095.110046] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115095.320892] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115095.537231] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115095.537292] hub 1-0:1.0: port_wait_reset: err = -16
[115095.537322] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115095.537353] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[115095.594207] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
[115095.656707] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115095.867584] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115096.078552] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115096.078582] hub 1-0:1.0: port_wait_reset: err = -16
[115096.078582] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115096.289428] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115096.500579] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115096.711334] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115096.711364] hub 1-0:1.0: port_wait_reset: err = -16
[115096.711395] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115096.922393] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115097.133239] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115097.344146] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115097.344177] hub 1-0:1.0: port_wait_reset: err = -16
[115097.344207] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115097.555175] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115097.766082] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115097.977264] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115097.977325] hub 1-0:1.0: port_wait_reset: err = -16
[115097.977355] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115098.187988] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115098.399108] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115098.609924] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115098.609954] hub 1-0:1.0: port_wait_reset: err = -16
[115098.609985] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115098.610015] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[115098.672424] hub 1-0:1.0: port 1 not reset yet, waiting 50ms
[115098.735046] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115098.945770] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115099.156860] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115099.156890] hub 1-0:1.0: port_wait_reset: err = -16
[115099.156921] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115099.367675] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115099.578765] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115099.789581] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115099.789611] hub 1-0:1.0: port_wait_reset: err = -16
[115099.789642] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115100.000427] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115100.211669] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115100.422668] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115100.422698] hub 1-0:1.0: port_wait_reset: err = -16
[115100.422729] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115100.633514] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115100.844360] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115101.055145] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115101.055206] hub 1-0:1.0: port_wait_reset: err = -16
[115101.055236] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115101.266143] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115101.477325] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115101.688232] hub 1-0:1.0: port 1 not reset yet, waiting 200ms
[115101.688262] hub 1-0:1.0: port_wait_reset: err = -16
[115101.688293] hub 1-0:1.0: port 1 not enabled, trying reset again...
[115101.688323] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[115101.688415] hub 1-0:1.0: unable to enumerate USB device on port 1
[115101.688476] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[115101.688537] hub 1-0:1.0: port 1 enable change, status 00000301
[115104.289550] hub 1-0:1.0: hub_suspend
[115104.289642] usb usb1: bus auto-suspend
[115105.623199] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[115110.182006] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[115121.703704] slide (GPIO 71) is now open
[115172.261596] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[115173.784454] usb usb1: usb resume
[115173.805023] hub 1-0:1.0: hub_resume
[115173.805084] hub 1-0:1.0: port 1: status 0301 change 0001
[115173.914672] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[115173.914794] hub 1-0:1.0: port 1, status 0301, change 0000, 1.5 Mb/s
[115174.039611] usb 1-1: new low speed USB device using musb_hdrc and address 100
[115174.190979] usb 1-1: skipped 1 descriptor after interface
[115174.191497] usb 1-1: default language 0x0409
[115174.193450] usb 1-1: uevent
[115174.193634] usb 1-1: usb_probe_device
[115174.193695] usb 1-1: configuration #1 chosen from 1 choice
[115174.195739] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[115174.196075] usb 1-1:1.0: uevent
[115174.196350] usbhid 1-1:1.0: usb_probe_interface
[115174.196380] usbhid 1-1:1.0: usb_probe_interface - got id
[115174.213684] input: PS/2+USB Mouse as /class/input/input6
[115174.273864] generic-usb 0003:04F3:0212.0003: input: USB HID v1.11 Mouse [PS/2+USB Mouse] on usb-musb_hdrc-1/input0
[115174.274810] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '100'
[115174.275512] usb 1-1: New USB device found, idVendor=04f3, idProduct=0212
[115174.275543] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[115174.275573] usb 1-1: Product: PS/2+USB Mouse
[115174.275573] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[115174.275634] hub 1-0:1.0: port 1 enable change, status 00000303
[115179.323333] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[115224.234832] slide (GPIO 71) is now closed

[singpolyma]

Woah! I switched to "full speed" instead of "low speed" with the hub and keyboard+mouse combo and now it works! Also, switching to "full speed" instead of "high speed" seems to have fixed my sd card reader (I had been sure it was USB 2.0... guess not)

[singpolyma]

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 %

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.

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.

By "active hub" do you just mean a powered hub? Will any powered hub work for this? Even if I don't charge while in hostmode a powered hub should reduce the drain on my n900 battery, right?

I tried this with my powered hub earlier. Got my mouse/keyboard/sd reader all working ("full speed") and then ran boostoff. Instantly the devices stopped working. Ran the charge script, the devices still were not working. Am I doing something wrong?

[Estel]

Yea, active hub SHOULD mean powered HUB - I use "should" because with so much designs and sometimes, pseudo-designs, You can never be sure. anyway, in 99% powered hubs, You will also get power on line connected to N900 - not so much possibility for manufacturers to limit that, would require very complicated circuit and probably conflict with device power-on-port discovery - so N900 should charge.

It's indeed strange that Your devices stop working when You try to use charger script. Maybe Your power supply can't provide enough current to power both keyboard/mouse and N900? Its strange a little, because mouse and keyboard don't need much power.

[vivek4ever]

hi techs...first of let me thank all d developers and ppl on this thread who r helping us to make h-e-n working on our charming n900...
jus becoz of this thread i was able to make use of such a grt feature hidden in n900...thanks ppl :):)
now i ve also got some issues wid h-e-n on my device...
it reads my keyboard,mouse and my 4gb pendrive but it fails to read my 1 TB.:mad:i cant figure it out.though the light gets light up when connect to n900 but it says unable to connect no file system found....plz plz help me make it work...my hard drive(1tb) is working perfectly in my lappy...
ps. my hard drive does not require an external power..

[Estel]

ps. my hard drive does not require an external power..

First of all, are You sure that in this specific case, You don't need external power supply? As it was mentioned in HEN wiki and many posts, N900 can provide only 200 mA of current, where Your laptop (or any "regular" computer" port) is capable of putting 500 mA.

Thats the case, why many power-hungry peripherals that work fine on desktop/laptop need powered hub or Y-cable on N900.

also, You may want to read cheve feedback few posts before - he succeed getting his HD to work by just slowing down mounting process (that's probably unrelated, but worth try)

---

Side note - and thats only my personal opinion - if You consider using less "luser like" shortcuts in Your posts, it would be much easy to read them.

[joerg_rw]

Yea, active hub SHOULD mean powered HUB - I use "should" because with so much designs and sometimes, pseudo-designs, You can never be sure. anyway, in 99% powered hubs, You will also get power on line connected to N900 - not so much possibility for manufacturers to limit that, would require very complicated circuit and probably conflict with device power-on-port discovery - so N900 should charge.

It's indeed strange that Your devices stop working when You try to use charger script. Maybe Your power supply can't provide enough current to power both keyboard/mouse and N900? Its strange a little, because mouse and keyboard don't need much power.

Sorry to have to tell you this isn't correct - most hubs separate external power from upstream port, if only by a very cheap single-diode-design (see http://freeyourphone.de/portal_v1/viewtopic.php?f=3&t=590&p=6266&hilit=diode&sid=535d135f60a019573b017155ed1805c3#p6266 and http://people.openmoko.org/joerg/Y-Cable/USB-HUB.jpg , http://people.openmoko.org/joerg/Y-Cable/USB-HUB.txt ).
Some hubs (obviously the one in post above that estel answered is one of them) even *sense* if there's power from upstream and accordingly power up the downstream ports, even though external power to hub is applied.

Generally speaking you'll need the Y-cable between N900 and hub, not usually though between hub and peripheral.

There's a very simple test if *your* hub supplies power to upstream port: power the hub, connect *switched off* N900 to upstream port with adapter. If N900 shows any reaction (startup, LED flashing etc) then the hub delivers power to N900. Otherwise not.

cheers
jOERG

[Estel]

Again no need to sorry - it's very useful info, that you provided. I'm sorry that i provided wrong info -strange thing, that all USB 2.0 HUBS i used doesn't separate power from upstream port, i was really sure that it's common habit.

If they tend to separate it, they do it with some rationale, do they? What is the danger of using non-separating USB hub?

I encountered only one strange - amusing, but not dangerous - thing when using such a hub. It was powered by ATX power supply, that i use also to power my other things around computer, like WC (water cooling, not toilet) fan controller - using 5V to operate and 12V to power up ventilators. One time, my ATX was turned off, while HUB still connected to it and to my notebook. What was my surprise, when on notebook power-on, Fan controller also waked up - fans we're not turning, but controller itself worked. It turned out that power from my notebook flow by the upstream port of HUB and its power plug to the (powered down) ATX power supply, then, by its lines, to fan controller. I just wonder if this single-diode design can also separate-to-powerplug power, not only powerplug-to-separate - will check that.

[vivek4ever]

First of all, are You sure that in this specific case, You don't need external power supply? As it was mentioned in HEN wiki and many posts, N900 can provide only 200 mA of current, where Your laptop (or any "regular" computer" port) is capable of putting 500 mA.


Thats the case, why many power-hungry peripherals that work fine on desktop/laptop need powered hub or Y-cable on N900.

also, You may want to read cheve feedback few posts before - he succeed getting his HD to work by just slowing down mounting process (that's probably unrelated, but worth try)




---

Side note - and thats only my personal opinion - if You consider using less "luser like" shortcuts in Your posts, it would be much easy to read them



i m preety sure it does not require external power source.i ve also tried cheve method of slow mounting but it didnt solve my problem.
what do i do now? plz go through my attachment.
do i need to use a usb hub/y connector and a usb charger to supply d deficient charge??