Re: [Announce] USB hostmode beta release
 

usually that's a job for udev. So not even any special daemon needed. See /etc/udev/rules.d and man udev

e.g the automatic start of showmouse on mouse plug in could get handled in 50-udev.rules, around "# input devices", with a RUN+= parameter
/j

Re: [Announce] USB hostmode beta release
 

I connected inexio 46" touchscreen to the N900 and it worked but was not calibrated. Where ever I touch the monitor it seems to get input only from left top. Is it somehow possible to emulat that as mouse? And after playing it for I while N900 built in touchscreen stopped working and I had to disconnect inexio touchscreen to get it working again.

Re: [Announce] USB hostmode beta release
 

@MohammadAG In response to your request to put the pmount source onto extras-devel, I've uploaded it but it fails on the autobuilder, seemingly with problems related to libblkid-dev (see https://garage.maemo.org/builder/fre...log.FAILED.txt) , though that is in the Build-Depends list. I'm a bit of a n00b when it comes to this, but I've tried dpkg-genbuilddeps and can't see anything that looks wrong. I've also attempted to use sbdmock but can't locate configuration files for fremantle (though I can locate complaints by other users regarding lack of said configuration files). So while this may be OT, I'm kinda stuck and out of time to look for more other ideas...

Re: [Announce] USB hostmode beta release
 

Wow, I dropped off the face of the earth and then this ... this is so impressive :) A word of caution: the usb connector broke off my n900 and I had to send it back for warranty service (the n900 is broken for other reasons ATM) so really truly do be careful about putting stress on it.

Re: [Announce] USB hostmode beta release
 

Hello, i have installed h-e-n app and tried it with flashdrive. It worked fine, but i have noticed that everytime i try to use my camera specially when opening the camera slider it wont open the default camera app. Instead shows "Operation Failed". Please help...

Re: [Announce] USB hostmode beta release
 

Please see issues with kernel-power and certain devices, either upgrade fcam-drivers, or uninstall them.
This is NOT related to host mode

Re: [Announce] USB hostmode beta release
 

hello, thanks for d reply.. ive read the previous posts and found out that the fcam driver is having conflicts with h-e-n. i uninstalled fcam ang reboot.. now its working. thanks and good job! :)

Re: [Announce] USB hostmode beta release
 

Well start and stop through gui or system menu, and a status bar icon (or whatever you call those little icons that says if you're on 3G or wlan active and whatnot) to know if it's enabled would be a pretty good option in my opinion.

EDIT: Oops, I thought I was at the end of the thread

Re: [Announce] USB hostmode beta release
 

Dear Mohammed,

Thanks to this wonderful app I was able to offload some of my photos during my sisters wedding onto a usb flash drive and continue with more shooting... nice

I would like to request the following feature if it is possible:
1. Options to mount using NTFS or ISO CD/DVD instead of running the script manually
2. To show a small icon in status bar if something is mounted. It is just for cosmetic sake. The icon could change color when vbus is active and based on speed

Is it possible to attach a usb tv tuner card and watch it on N900 or am just dreaming too much ;-)

Re: [Announce] USB hostmode beta release
 

Haha, amazing...
NOTHING WILL STOP THIS COMMUNITY!

Thanks for the progress :D

Re: [Announce] USB hostmode beta release
 

With a SSH remote terminal, I've installed hostmode-gui with the i2c-tools dependency, and appears the big warning. Nothing happens and installation doesn't end...

After an hour (I thought it was frozen) I've taken the device, and seen the license message on screen. Oh, that was the issue!

fcam-drivers package makes the same (graphic message on device screen), but explains it on terminal:
Could i2c-tools package install with the same verbosity?

Re: [Announce] USB hostmode beta release
 

I so hate those warnings, we were just forced to put them because of the severity of the damage that i2cset could do (h-e-n is perfectly safe to use FYI), I'll do it on the next release.

Re: [Announce] USB hostmode beta release
 

its hard to find the usb coupler where i stay, so can someone tell me if buying these 2 things will work as expected?

http://cgi.ebay.in/Specialised-Cable...item3f05649172

http://cgi.ebay.in/Mini-USB-MicroUSB...item3f0578682d

tia..

Re: [Announce] USB hostmode beta release
 

I personally use the Mini to Micro ones (exactly like those) to charge my N900 from my old Motorola RAZR charger (RAZR used a mini usb port).

They are, to say the least, fragile. A little bit of force up or down when it's attached to another port, and it has a high chance of pushing itself open from the inside. Inside the cords hold together, and if the pins that hold the two plastic pieces together don't break and you don't damage the actual cord bits inside, you can just close it again. Applying tape or maybe glue to where the two plastic parts come together on that adapted would probably solve this. Careful use makes them last for a while too. (I just noticed the pictures are different for that product. The first one shows different ones than the second two... So *Shrug*. My experience is with the one shown in the generic first photo.)

As for the first item, the USB to Mini USB cable, *shrug* should work, with the other one.

Assuming both sellers are legitimate and you get both of them as advertised and working, I would say it should be fine.

Re: [Announce] USB hostmode beta release
 

@MohammadAG OK I've managed to get the pmount source accepted by extras-devel. Problem was an unspecified dependency of libblkid-dev on libuuid1. Unfortunately there is still some debugging code in the 'configure' file in the repository but it doesn't seem worthwhile making another version just to take it out.

Re: [Announce] USB hostmode beta release
 

@MohammadAG, I'm asking for adding this comment on terminal, to say that something is waiting for a response in screen:

Re: [Announce] USB hostmode beta release
 

The iNexio touchscreens behave as standard HID devices so there is no reason for it not to work. On a PC, it works like a mouse with no problems. However I think you might need to calibrate it on your N900, but since there are no Maemo-compatible drivers... yeah.

Re: [Announce] USB hostmode beta release
 

If the TV Card has open sourced linux drivers then it *might* be possible.. As long as it would be possible to send external power somehow. However I'm not associated with this project in any way so I guess someone with more know-how probably have a different opinion.

Re: [Announce] USB hostmode beta release
 

This is my first post on the maemo forum, although I have been using it as a reference for a few months and I have to say it is a fantastic community.

Before I am given the stock reply of "use the search" I would like to ask if host mode can be run alongside overclocking. I've seen that it won't be possible until a power kernel release for pr1.3 but I recieved an update for power kernel a week ago.

If not, is it at least possible to multiboot between a kernel with overclocking and a seperate kernel with usb host mode.

I am developing a game in python and at the moment I require 850mhz to get a decent fps.

Thanks and sorry for the n00bery :D

Re: [Announce] USB hostmode beta release
 

hostmode works with kernel-power (v43(?) onwards), v45+ is recommended.

Re: [Announce] USB hostmode beta release
 

Is v45 the latest version in the extras repo, or will I have to use the devel or testing repos?

Sorry for the ignorance, I looked at the description in package manager but can't find anything about a version number

Re: [Announce] USB hostmode beta release
 

You'll need the devel repos, the latest in testing is v42. The main difference between v45 and v46 is that v45 has uboot, and v46 doesn't. Unless you want uboot, just enable the devel repo and install the latest version.

Also, "apt-cache showpkg <packagename> will give you information about all the versions of packages available in the repos you have selected and which repos they are in.

Re: [Announce] USB hostmode beta release
 

i thought today about connecting a web cam to myN900, i still haven't started experimenting with it, so i was just asking if anyone have already tried that ?
the camera works out of the box under ubuntu, it should be supported by v4l2.
so if the webcam works what software would be used with it on the n900 and can it record video from the webcam ?


My usb connector came out completely, and as the phone got no warranty i fixed it myself, but because it was very hard to connect all the pins back on the board i didn't connect the ID pin,
i know that this pin is used by USB OTG, so how will this affect my device ?

while i was fixing the usb connector i noticed the +5v pin of the usb connector was connected directly to a very small fuse, did anyone else notice that ? , its shown too on the phone schematic
what happens if you would short out the +5V and GND of the n900 USB connector. did anyone blow that fuse or its rated above the 200mA the port can deliver and no one should worry about it ?!

Re: [Announce] USB hostmode beta release
 

Search this and the more appropriate "problems"-thread .
Please see post #9 of this thread, about topic of the thread.
The ID pin isn't needed for h-e-n hostmode.
The fuse is a 2A, and most likely a self-resetting fuse that doesn't blow in the usual sense. I.E. nobody should worry.

/j

Re: [Announce] USB hostmode beta release
 

Is there any way to multiboot between the stable (non host mode) kernel and the devel one? Or is there no serious problems that I may cause by installing the devel?

EDIT:

Just installed v46 and h.e.n and I have to say this community is amazing. I honestly had no idea how easy it is to use this fantastic piece of software. Tested on high performance flash drive with 2 partitions and both were mounted with no problems.

I was also pleasantly surprised that OCing worked as before. Thanks to everyone involved :D

Re: [Announce] USB hostmode beta release
 

For me everything is working just fine :)

I tested several USB sticks / drives and even 500GB HDDs are instantly detected and can be really fast accessed. I'm simply impressed!

I use this Adapter which I bought from a German Ebay shop: http://cgi.ebay.de/ws/eBayISAPI.dll?...=STRK:MEWNX:IT (1,00€)

This one to get additional power for HDDs and stuff: http://cgi.ebay.de/ws/eBayISAPI.dll?...=STRK:MEWNX:IT (3,89€)

I tested afterwards other devices like several Logitech USB mouses and they all worked fine with extmou (Also wireless ones!). I only noticed that I can't click anything inside the default browser and that some applications like Firefox don't show the mouse cursor.

USB keyboards with extkbd didn't worked for me at all, the 3 LEDs blink once and nothing happens. Sometimes extkbd stucks at 100% CPU when I try to configure the keyboard, so far no success.

Keep up the good work :)

Re: [Announce] USB hostmode beta release
 

The fuse is a normal fuse consisting of a thin wire across a ceramic core , the wire thickness as i saw under a microscope is very thin it can never be 2A fuse, i saw its says 2.0A in the schematic but still it may be a mistake , maybe !
so what I'm asking here is did anyone short out the 5V with GND while a USB device was connected and the phone was supplying power to it ?

Re: [Announce] USB hostmode beta release
 

Have you forgotten that it also charges through the USB port, the included wall charger outputs 1.2A, so I'd expect the fuse to take at least 1.5A to give a safety margin (you don't want the fuse to be blown in the course of normal charging). The fuse is likely to be protection against dodgy chargers or a faulty charge circuit.

I doubt the fuse has anything to do with hostmode, in theory if shorted in hostmode it should detect this and cut the power (it does on my netbook), but I certainly won't volunteer my N900 to see what happens.

Re: [Announce] USB hostmode beta release
 

test of today's release of "uboot for powerkernel v46" - in maemo-devel, and most recent h-e-n hostmode GUI as of today, on a pr1.1.1 system (yes!) with a custom kernel:

installation of uboot-pk-v46 went fine and pulled in pk as a dependency as supposed.
Not showing any of the usual warning dialogs though that usually come with pk.
uboot bootmenu showing fine, boot to system OK.

(installed backup-menu after that, and it also worked as expected)

installation of h-e-n GUI listed pk-v46 as a dependency that gets installed, obviously the dependencies of h-e-n aren't satisfied by uboot-pk-v46.
I refused to accept the warning dialog that showed up for pk this time ("click outside gray area...") -> HAM rises error notifier "installation wasn't possible"
Nevertheless h-e-n got installed

Clicking Icon doesn't work, running `update-sudoers` from a rootshell fixed this (why is the file so awkwardly named? ->"/etc/sudoers.d/hostmode.sudoers.dpkg-new")

after that h-e-n works like expected, until mounting.
error:"sh: /opt/h-e-n/mount.sh: Permission denied"
in a rootsh `chmod u+x /opt/h-e-n/mount.sh` fixed this, for the first time I tested. For some weird reason h-e-n wasn't able to call ` /opt/h-e-n/mount.sh --mount` after this initial success, on all my tests. I guess there's some bug in h-e-n regarding the mount button.
A manual call, in a rootshell, of ` /opt/h-e-n/mount.sh --mount` worked just fine
Maybe of interest: the unmount button works like expected. (checked by inserting "set -vx" at top of /opt/h-e-n/mount.sh)
[edit] unchecking the settings->"open fm after mount" seems fixed the mount button[/edit]

settings->default-filemanager: is locked, i.e it's empty and I can't change it. Not even after ticking above checkmark and closing/restarting h-e-n

The help text is using USB1.1 as descriptive term for both fullspeed and lowspeed. I suggest to check if that's not LS=USB1.0, and maybe even change the button labels to the more clear USBx.y terms rather than the HS/FS/LS. Also a sort order left=low, right=high would be more intuitive, I.E.: [USB1.0] [USB1.1] [USB2.0] for the three buttons.
[VBUS boost] should become a checkmark widget above those three buttons, and hitting any of the 3 would do both select speed and - according to VBUS checkmark - enable vboost same moment. The three speed buttons then change to a single [STOP] button.

Sidenote: it seems you need to be patient when hitting the buttons. My pendrive needs some 8s after vboost enable, and then again several seconds after ENUM, until kernel finally created device sda{1}. Prior to that 'mount' won't work I guess

bottom line: some weirdness might have come in by HAM aborting the installation as a result of me refusing to accept installation of pk. This probably resulted in postinstall script never being executed, which might explain the missing permissions and update-sudoers run.
The mount-button breakage I guess is related to inconsistencies between my 1.1.1 filesystem and pathes, and what h-e-n GUI expects to find for HFM. However this shouldn't cause the mount button to become dysfunctional

for the rest of it: nice work Mohammad. Thanks a lot
cheers
jOERG

Re: [Announce] USB hostmode beta release
 

t900:~# udevadm monitor
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent

UEVENT[1292139844.895416] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292139844.898223] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292139844.915222] add /class/scsi_host/host6 (scsi_host)
UDEV [1292139844.920135] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292139844.985168] add /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UEVENT[1292139844.986419] add /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UEVENT[1292139844.987426] add /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292139844.988403] add /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292139845.130371] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292139845.139709] add /class/scsi_host/host6 (scsi_host)
UDEV [1292139845.147888] add /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UDEV [1292139845.156921] add /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292139845.165771] add /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UDEV [1292139845.171905] add /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292139849.999999] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292139850.003967] add /class/scsi_disk/6:0:0:0 (scsi_disk)
UEVENT[1292139850.009216] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292139850.221099] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292139850.222442] add /block/sda/sda1 (block)
UEVENT[1292139850.223907] add /class/bdi/8:0 (bdi)
UEVENT[1292139850.227752] add /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292139850.261840] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292139850.263275] add /class/scsi_disk/6:0:0:0 (scsi_disk)
UDEV [1292139850.272369] add /class/bdi/8:0 (bdi)
UDEV [1292139850.279541] add /block/sda (block)
UDEV [1292139850.283782] add /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292139850.335357] add /block/sda/sda1 (block)


#vboost off, on; enumerate



UEVENT[1292140015.841522] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140015.847076] remove /block/sda/sda1 (block)
UDEV [1292140015.983337] remove /block/sda/sda1 (block)
UDEV [1292140015.992675] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140017.473510] remove /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UEVENT[1292140017.477569] remove /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UEVENT[1292140017.481292] remove /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292140017.485259] remove /class/scsi_device/6:0:0:0 (scsi_device)
UEVENT[1292140017.488861] remove /class/scsi_disk/6:0:0:0 (scsi_disk)
UEVENT[1292140017.492736] remove /class/bdi/8:0 (bdi)
UEVENT[1292140017.496276] remove /block/sda (block)
UEVENT[1292140017.499755] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140017.503326] remove /class/scsi_host/host6 (scsi_host)
UEVENT[1292140017.508026] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292140017.510101] remove /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UEVENT[1292140017.513793] remove /devices/platform/musb_hdrc/usb1/1-1 (usb)
UDEV [1292140017.527557] remove /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292140017.533477] remove /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UDEV [1292140017.538482] remove /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UDEV [1292140017.543518] remove /class/bdi/8:0 (bdi)
UDEV [1292140017.548980] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292140017.550231] remove /class/scsi_disk/6:0:0:0 (scsi_disk)
UDEV [1292140017.554626] remove /class/scsi_host/host6 (scsi_host)
UDEV [1292140017.563079] remove /block/sda (block)
UDEV [1292140017.598205] remove /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292140017.604553] remove /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UDEV [1292140017.690521] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292140017.729675] remove /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140017.949890] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140017.952667] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292140017.969390] add /class/scsi_host/host7 (scsi_host)
UDEV [1292140017.973358] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140018.033996] add /class/usb_endpoint/usbdev1.17_ep01 (usb_endpoint)
UEVENT[1292140018.034545] add /class/usb_endpoint/usbdev1.17_ep82 (usb_endpoint)
UEVENT[1292140018.034820] add /class/usb_endpoint/usbdev1.17_ep83 (usb_endpoint)
UEVENT[1292140018.035095] add /class/usb_endpoint/usbdev1.17_ep00 (usb_endpoint)
UDEV [1292140018.171661] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292140018.193603] add /class/usb_endpoint/usbdev1.17_ep01 (usb_endpoint)
UDEV [1292140018.195465] add /class/usb_endpoint/usbdev1.17_ep82 (usb_endpoint)
UDEV [1292140018.198455] add /class/scsi_host/host7 (scsi_host)
UDEV [1292140018.205047] add /class/usb_endpoint/usbdev1.17_ep83 (usb_endpoint)
UDEV [1292140018.210876] add /class/usb_endpoint/usbdev1.17_ep00 (usb_endpoint)
UEVENT[1292140023.038940] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UEVENT[1292140023.042968] add /class/scsi_disk/7:0:0:0 (scsi_disk)
UEVENT[1292140023.048278] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.238189] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.239624] add /class/bdi/8:0 (bdi)
UEVENT[1292140023.240722] add /class/bdi/8:0 (bdi)
UEVENT[1292140023.242645] add /class/scsi_device/7:0:0:0 (scsi_device)
UDEV [1292140023.258483] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.270721] add /class/scsi_disk/7:0:0:0 (scsi_disk)
UDEV [1292140023.288391] add /block/sda (block)
UDEV [1292140023.291992] add /class/scsi_device/7:0:0:0 (scsi_device)
UDEV [1292140023.327728] add /block/sda/sda1 (block)





HFM (and also hulda?) doesn't like when you hit vboost-stop in h-e-n (well, I also applied external VBUS, and started bme):
Dec 12 08:55:55 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 08:55:55 t900 last message repeated 42 times
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - Failed to create monitor for path file:///media/sda1
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - error accessing 'file:///media/sda1': File not found
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - Failed to create monitor for path file:///media/sda1
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - error accessing 'file:///media/sda1': File not found
...
Dec 12 08:56:36 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 08:57:07 t900 last message repeated 122991 times
Dec 12 08:58:08 t900 last message repeated 252652 times
Dec 12 08:59:09 t900 last message repeated 253458 times
Dec 12 09:00:10 t900 last message repeated 252588 times
Dec 12 09:01:05 t900 last message repeated 231701 times
Dec 12 09:01:05 t900 iphbd: client with socket 9 disappeared
Dec 12 09:01:05 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 11190 times
Dec 12 09:01:09 t900 [2363]: GLIB CRITICAL ** default - free_async_operations_list: assertion `gAttachmentsOperList && g_list_length (gAttachmentsOperList) > 0' failed
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Goodbye! modest-nokiamessaging-plugin is being unloaded
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 30 times
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Unloaded!
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 1188 times
Dec 12 09:01:09 t900 maemo-launcher[966]: child (pid=2363) terminated due to exit()=0
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:40 t900 last message repeated 125470 times
Dec 12 09:02:02 t900 last message repeated 92220 times
Dec 12 09:02:02 t900 kernel: [ 7761.922119] kb_lock (GPIO 113) is now closed
Dec 12 09:02:02 t900 systemui-tklock[974]: Method call received from: :1.12, iface: com.nokia.system_ui.request, method: tklock_close
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 582 times
Dec 12 09:02:02 t900 browser[1786]: GLIB CRITICAL ** default - download_mgr_update_current: assertion `self->cur_item' failed
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 28 times
Dec 12 09:02:02 t900 kernel: [ 7762.258117] kb_lock (GPIO 113) is now open
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:33 t900 last message repeated 116783 times
Dec 12 09:01:05 t900 last message repeated 231701 times
Dec 12 09:01:05 t900 iphbd: client with socket 9 disappeared
Dec 12 09:01:05 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 11190 times
Dec 12 09:01:09 t900 [2363]: GLIB CRITICAL ** default - free_async_operations_list: assertion `gAttachmentsOperList && g_list_length (gAttachmentsOperList) > 0' failed
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Goodbye! modest-nokiamessaging-plugin is being unloaded
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 30 times
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Unloaded!
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 1188 times
Dec 12 09:01:09 t900 maemo-launcher[966]: child (pid=2363) terminated due to exit()=0
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:40 t900 last message repeated 125470 times
Dec 12 09:02:02 t900 last message repeated 92220 times
Dec 12 09:02:02 t900 kernel: [ 7761.922119] kb_lock (GPIO 113) is now closed
Dec 12 09:02:02 t900 systemui-tklock[974]: Method call received from: :1.12, iface: com.nokia.system_ui.request, method: tklock_close
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 582 times
Dec 12 09:02:02 t900 browser[1786]: GLIB CRITICAL ** default - download_mgr_update_current: assertion `self->cur_item' failed
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 28 times
Dec 12 09:02:02 t900 kernel: [ 7762.258117] kb_lock (GPIO 113) is now open
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:33 t900 last message repeated 116783 times


Found no other way to stop that madness, other than reboot
:-o

Re: [Announce] USB hostmode beta release
 

http://www.youtube.com/watch?v=O-19REKPrQc
http://www.youtube.com/watch?v=EM6vB5QD4So
http://www.youtube.com/watch?v=tOVErUmLDyA

Re: [Announce] USB hostmode beta release
 

Works fine for me. Tested with an iPod Video and an old (full-speed!) Fujifilm SM-R2 SmartMedia reader (that's that enormous memory card format they've stopped manufacturing). Both mounted and could be read.

The black cable in the photo is from this eBay UK page (presumably, the eBay pic is actually two of them). It is slightly shorter than the N900 itself, but still flexes enough to prevent it acting as a lever to break the USB socket.

This cable definitely seems like a very portable alternative to a rigid, socket-breaking adaptor, and is available in the UK.
http://ompldr.org/vNmp3Nw
(Sorry for the poorly-lit webcam pic... white cable is just a regular A-B cable).

Initially, the camera didn't work with Titan's kernel (I use FCam).
followed by a reboot fixed things. I haven't checked, but I believe that fix requires extras-devel.

Thanks to everyone who made hostmode work!

P.S. It appears that that international seller sells the same adaptor on ebay.com too.

Edit: Tried a Logitech mouse and an A4Tech KL-5UP keyboard with extkbd - both worked fine (this is a "slim" keyboard with no numpad - I actually wouldn't mind taking this on a train if I had some LaTeX to write on the N900).

Re: [Announce] USB hostmode beta release
 

I tried to connect a externally powered hub to my N900..Belkin 7port hub.. however it failed to identify the device connected to the hub. I tried to put on VBus the same instance theperipheral was connected still no effect. And i think my N900 had little earth when i connected to hub..I need your advice..I have seen a youtube video where HDD is conneted via a 5pin external powered Hub. Is power rating of the Hub a factor affecting this..Should i buy a new Hub..actually my idea was to connect multiple devices via a Hub to N900...

Re: [Announce] USB hostmode beta release
 

Ticket Status: NEEDINFO
please supply the usual dmesg printout, and lsusb printout.
Make sure your hub is powered via external PSU, plug in hub to N900 immediately after hitting [VBUS boost], then hit [Enumerate].
Then plug in peripheral to hub.

/j

Re: [Announce] USB hostmode beta release
 

dmesg output ::

[73303.344604] slide (GPIO 71) is now closed
[73305.493041] slide (GPIO 71) is now open
[73321.257904] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[73322.832946] Forced hostmode error: no device attached
[73322.833068] usb usb1: usb resume
[73322.852264] hub 1-0:1.0: hub_resume
[73322.852325] hub 1-0:1.0: port 1: status 0101 change 0001
[73322.961822] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[73322.961883] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[73323.086914] usb 1-1: new full speed USB device using musb_hdrc and address 33
[73328.086730] usb 1-1: khubd timed out on ep0in len=0/64
[73333.086883] usb 1-1: khubd timed out on ep0in len=0/64
[73338.086791] usb 1-1: khubd timed out on ep0in len=0/64
[73338.215148] usb 1-1: device descriptor read/64, error -110
[73343.321258] usb 1-1: khubd timed out on ep0in len=0/64
[73348.321075] usb 1-1: khubd timed out on ep0in len=0/64
[73353.321075] usb 1-1: khubd timed out on ep0in len=0/64
[73353.446105] usb 1-1: device descriptor read/64, error -110
[73353.680572] usb 1-1: new full speed USB device using musb_hdrc and address 34
[73358.680725] usb 1-1: khubd timed out on ep0in len=0/64
[73363.467712] Forced hostmode error: no device attached
[73363.680450] usb 1-1: khubd timed out on ep0in len=0/64
[73368.680603] usb 1-1: khubd timed out on ep0in len=0/64
[73368.743194] hub 1-0:1.0: unable to enumerate USB device on port 1
[73368.743316] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[73368.743438] hub 1-0:1.0: port 1, status 0101, change 0003, 12 Mb/s
[73368.899291] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[73369.024444] usb 1-1: new full speed USB device using musb_hdrc and address 35
[73374.024261] usb 1-1: khubd timed out on ep0in len=0/64
[73379.024475] usb 1-1: khubd timed out on ep0in len=0/64
[73384.024475] usb 1-1: khubd timed out on ep0in len=0/64
[73384.149353] usb 1-1: device descriptor read/64, error -110
[73389.258728] usb 1-1: khubd timed out on ep0in len=0/64
[73394.258789] usb 1-1: khubd timed out on ep0in len=0/64
[73398.692077] Forced hostmode error: no device attached
[73399.258605] usb 1-1: khubd timed out on ep0in len=0/64
[73399.321136] hub 1-0:1.0: unable to enumerate USB device on port 1
[73399.321228] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[73399.321380] hub 1-0:1.0: port 1, status 0101, change 0003, 12 Mb/s
[73399.477386] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[73399.602294] usb 1-1: new full speed USB device using musb_hdrc and address 36
[73404.602600] usb 1-1: khubd timed out on ep0in len=0/64
[73409.602508] usb 1-1: khubd timed out on ep0in len=0/64
[73414.602355] usb 1-1: khubd timed out on ep0in len=0/64
[73414.727355] usb 1-1: device descriptor read/64, error -110
[73419.836700] usb 1-1: khubd timed out on ep0in len=0/64
[73424.836853] usb 1-1: khubd timed out on ep0in len=0/64
[73428.220733] Forced hostmode error: no device attached
[73429.836791] usb 1-1: khubd timed out on ep0in len=0/64
[73429.899444] hub 1-0:1.0: unable to enumerate USB device on port 1
[73429.899536] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[73429.899688] hub 1-0:1.0: port 1, status 0101, change 0003, 12 Mb/s
[73430.055603] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[73430.180572] usb 1-1: new full speed USB device using musb_hdrc and address 37
[73435.180480] usb 1-1: khubd timed out on ep0in len=0/64
[73440.180541] usb 1-1: khubd timed out on ep0in len=0/64
[73445.180358] usb 1-1: khubd timed out on ep0in len=0/64
[73445.305541] usb 1-1: device descriptor read/64, error -110

lsub output

Bus 001 Device 001: ID 1d6b:0002

My hub is externaly powered
per port max current = 500mA

Re: [Announce] USB hostmode beta release
 

This is probably a stupid question, but have you tested it with a standard USB flashdisk such as kingston, adata etc?

Re: [Announce] USB hostmode beta release
 

The iPod and card reader are both USB MSC devices, meaning they work exactly like a standard USB flash drive.

Re: [Announce] USB hostmode beta release
 

Is there any soundcard working?

(I want an external stereo microphone.)

I think in the actual kernel is no OSS support.

Could that change in future?

Re: [Announce] USB hostmode beta release
 

I know it is possible to mount iPods as external storage devices, but has anyone figured out how to access the iTunes library, for instance using gtkpod in Easy Debian.

I have installed gtkpod but can't seem to find the iPod using Easy Debian.

Re: [Announce] USB hostmode beta release
 

Thanks i got it working...It was actualy the fault of the Hub ..Thanks!!. Now eed to try keyboard and mouse..
N900 is reallly becoming cool.. :))