maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   [Announce] USB hostmode beta release (https://talk.maemo.org/showthread.php?t=65232)

anapospastos 2010-11-08 19:41

Re: [Announce] USB hostmode beta release
 
Ok, I ve got working that too. Two things I noticed as they mentioned also here:
1. It doesn't auto mount
2. it "sees" memory stick as read-only

Thanks for all your effort and keep doing great things for Maemo and N900.

Zoin 2010-11-08 19:43

Re: [Announce] USB hostmode beta release
 
Quote:

Originally Posted by luketanti (Post 867288)
Yes. I did. And I even restarted the phone. I do not know why. I also tried an mp4 player and a microsd to usb card reader but nothing. In the kernel log it detects them but in file mangers I do not see anything.

They are just not mounted properly - I'm pretty much sure. You can read log to confirm this

retsaw 2010-11-08 19:58

Re: [Announce] USB hostmode beta release
 
Quote:

Originally Posted by Hmoobwarrior (Post 867096)
sorry stupid question but .. 3g dongle via usb will work? now with usb beta? stil on att unfortunately. need to know so i can purchase a dongle, I love n900 hate that att doesnt have the right freq.. stuck on plan for another year or so.

Not likely. 3G dongles draw a LOT of power, whilst (for the moment at least) the N900 can only output 200mA of current, compared to a regular USB port which can output 500mA (and sometimes more). You could try it but I doubt you'd have much luck and I'm not sure the driver for it would be included in the kernel (though that could be easily fixed so long as there is a linux driver for it).

Maybe you should consider getting a MiFi instead, they are also more convenient than connecting a dongle and have their own battery,

thp 2010-11-08 20:11

Re: [Announce] USB hostmode beta release
 
Ok, I did not get my Logitech Rumblepad 2 to be detected, but I was able to get an older Sidewinder Gamepad (Freestyle Pro) to work in low speed mode and be available as normal joystick. Here's a small utility that will use SDL to read joystick input and convert it into keyboard events (the axes map to keyboard arrows, the buttons to different keys). Useful for playing emulator games with USB joysticks/gamepads:

http://thp.io/2010/maemo/jsthingie (Source: http://thp.io/2010/maemo/jsthingie.c)

For now, only digital pads are supported (no analog joysticks due to the primitive logic that is used to determine direction for arrow keys) and you have to have SDL installed, uinput loaded (modprobe uinput) and you either have to give correct permissions to /dev/input/uinput or make sure that you run jsthingie as root.

luketanti 2010-11-08 20:14

Re: [Announce] USB hostmode beta release
 
Code:

wlan0: roaming signal from driver, sending LOWSIGNAL
[16772.927581] wlan0: roaming signal from driver, sending HIGHSIGNAL
[16969.750946] wlan0: roaming signal from driver, sending LOWSIGNAL
[16979.785736] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17082.705627] wlan0: roaming signal from driver, sending LOWSIGNAL
[17092.739532] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17126.125213] wlan0: roaming signal from driver, sending LOWSIGNAL
[17133.891387] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17234.571136] wlan0: roaming signal from driver, sending LOWSIGNAL
[17245.118652] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17289.766784] wlan0: roaming signal from driver, sending LOWSIGNAL
[17294.990051] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17436.821655] wlan0: roaming signal from driver, sending LOWSIGNAL
[17458.736267] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17661.807128] wlan0: roaming signal from driver, sending LOWSIGNAL
[17676.859954] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17720.266906] wlan0: roaming signal from driver, sending LOWSIGNAL
[17814.287078] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17821.149108] wlan0: roaming signal from driver, sending LOWSIGNAL
[17856.888336] wlan0: roaming signal from driver, sending HIGHSIGNAL
[17967.047119] kb_lock (GPIO 113) is now closed
[17967.328094] kb_lock (GPIO 113) is now open
[17972.875122] kb_lock (GPIO 113) is now closed
[17973.335845] kb_lock (GPIO 113) is now open
[18113.418640] wlan0: driver reports beacon loss from AP cfff0ed4 - sending probe request
[18114.754486] wlan0: driver reports beacon loss from AP cfff0ed4 - sending probe request
[18116.766906] wlan0: no probe response from AP cfff0ed4 - disassociating
[18118.383483] wlan0: authenticate with AP 00:1d:0f:ee:61:8a
[18118.405426] wlan0: authenticated
[18118.405487] wlan0: associate with AP 00:1d:0f:ee:61:8a
[18118.413604] wlan0: RX AssocResp from 00:1d:0f:ee:61:8a (capab=0x431 status=0 aid=2)
[18118.413635] wlan0: associated
[18124.073181] wlan0: driver reports beacon loss from AP cfff0ed4 - sending probe request
[18159.095733] wlan0: driver reports beacon loss from AP cfff0ed4 - sending probe request
[18160.934936] wlan0: driver reports beacon loss from AP cfff0ed4 - sending probe request
[18163.601776] wlan0: driver reports beacon loss from AP cfff0ed4 - sending probe request
[18168.313507] wlan0: driver reports beacon loss from AP cfff0ed4 - sending probe request
[18175.686492] wlan0: driver reports beacon loss from AP cfff0ed4 - sending probe request
[18177.688751] wlan0: no probe response from AP cfff0ed4 - disassociating
[18178.501495] wlan0: direct probe to AP 00:1d:0f:ee:61:8a try 1
[18178.695373] wlan0: direct probe to AP 00:1d:0f:ee:61:8a try 2
[18178.749847] wlan0 direct probe responded
[18178.749908] wlan0: authenticate with AP 00:1d:0f:ee:61:8a
[18178.812530] wlan0: authenticated
[18178.812591] wlan0: associate with AP 00:1d:0f:ee:61:8a
[18178.864715] wlan0: RX AssocResp from 00:1d:0f:ee:61:8a (capab=0x431 status=0 aid=2)
[18178.864776] wlan0: associated
[18468.648284] kb_lock (GPIO 113) is now closed
[18468.812377] kb_lock (GPIO 113) is now open
[18500.489532] wlan0: roaming signal from driver, sending LOWSIGNAL
[18505.405334] wlan0: roaming signal from driver, sending HIGHSIGNAL
[18527.921875] usb 1-1: new high speed USB device using musb_hdrc and address 77
[18528.072204] usb 1-1: configuration #1 chosen from 1 choice
[18528.099334] scsi12 : SCSI emulation for USB Mass Storage devices
[18528.109649] drivers/usb/core/inode.c: creating file '077'
[18528.110595] usb 1-1: New USB device found, idVendor=0781, idProduct=5406
[18528.110656] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18528.110717] usb 1-1: Product: U3 Cruzer Micro
[18528.110748] usb 1-1: Manufacturer: SanDisk
[18528.110778] usb 1-1: SerialNumber: 0877631412002F67
[18528.121612] usb-storage: device found at 77
[18528.121673] usb-storage: waiting for device to settle before scanning
[18533.118988] usb-storage: device scan complete
[18533.120727] scsi 12:0:0:0: Direct-Access    SanDisk  Cruzer          8.01 PQ: 0 ANSI: 0 CCS
[18533.143096] sd 12:0:0:0: [sda] 15731711 512-byte hardware sectors: (8.05 GB/7.50 GiB)
[18533.143676] sd 12:0:0:0: [sda] Write Protect is off
[18533.143737] sd 12:0:0:0: [sda] Mode Sense: 45 00 00 08
[18533.143768] sd 12:0:0:0: [sda] Assuming drive cache: write through
[18533.152313] sd 12:0:0:0: [sda] 15731711 512-byte hardware sectors: (8.05 GB/7.50 GiB)
[18533.152893] sd 12:0:0:0: [sda] Write Protect is off
[18533.152954] sd 12:0:0:0: [sda] Mode Sense: 45 00 00 08
[18533.152984] sd 12:0:0:0: [sda] Assuming drive cache: write through
[18533.153045]  sda:
[18533.170257] sd 12:0:0:0: [sda] Attached SCSI removable disk
[18570.337066] wlan0: roaming signal from driver, sending LOWSIGNAL
[18576.383392] wl1251: ERROR Power save entry failed, giving up
[18581.288177] wlan0: roaming signal from driver, sending HIGHSIGNAL
[18588.558807] wlan0: roaming signal from driver, sending LOWSIGNAL
[18602.383422] wlan0: roaming signal from driver, sending HIGHSIGNAL

This is my log of the sandisk (I think). Can some one tell me what am I doing wrong then.

aligatro 2010-11-08 20:19

Re: [Announce] USB hostmode beta release
 
Noticed a wierd problem with fm-module. I tried to activate it but it says that fm failed to start or something like that. Also, bluetooth name change to "BCMXXX (some number) Initialization configuration"
had a powerkernel before flashing to hostmode.

PathFinder@9GS 2010-11-08 20:50

Re: [Announce] USB hostmode beta release
 
I've got a question.. So If I plug in something that is being powered externally.. mm say my dslr.. I power it up and connect it to my phone and follow the steps..

Would there be like a backup current flow from the camera to the phone? and if there would be.. would it harm my phone?

MohammadAG 2010-11-08 21:16

Re: [Announce] USB hostmode beta release
 
kernel-power with hostmode added into it.
http://mohammadag.xceleo.org/hostmod..._2010/power40/
Download all packages there and dpkg -i them, no step by step tuts since it is after all... for power users.

WhiteWolf 2010-11-08 21:24

Re: [Announce] USB hostmode beta release
 
I've tried a 2Gb pendrive Toahiba and it has worked without external power and I played a movie.

"Gran Torino."

Link: video

aligatro 2010-11-08 21:28

Re: [Announce] USB hostmode beta release
 
Quote:

Originally Posted by aligatro (Post 867337)
Noticed a wierd problem with fm-module. I tried to activate it but it says that fm failed to start or something like that. Also, bluetooth name change to "BCMXXX (some number) Initialization configuration"
had a powerkernel before flashing to hostmode.

Don't tell me I am the only person with this problem. oO
Can someone with fm-app plz check if it's still working.


All times are GMT. The time now is 15:12.

vBulletin® Version 3.8.8