![]() |
2010-11-08
, 19:43
|
Posts: 12 |
Thanked: 27 times |
Joined on Nov 2010
|
#82
|
![]() |
2010-11-08
, 19:58
|
Posts: 701 |
Thanked: 585 times |
Joined on Sep 2010
@ London, England
|
#83
|
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.
![]() |
2010-11-08
, 20:11
|
|
Posts: 1,391 |
Thanked: 4,272 times |
Joined on Sep 2007
@ Vienna, Austria
|
#84
|
The Following 9 Users Say Thank You to thp For This Useful Post: | ||
![]() |
2010-11-08
, 20:14
|
Posts: 133 |
Thanked: 16 times |
Joined on Sep 2010
@ Balzan Malta
|
#85
|
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
![]() |
2010-11-08
, 20:19
|
Posts: 490 |
Thanked: 191 times |
Joined on May 2010
|
#86
|
![]() |
2010-11-08
, 20:50
|
|
Posts: 164 |
Thanked: 79 times |
Joined on Jul 2010
|
#87
|
![]() |
2010-11-08
, 21:16
|
|
Posts: 2,473 |
Thanked: 12,265 times |
Joined on Oct 2009
@ Jerusalem, PS/IL
|
#88
|
The Following 34 Users Say Thank You to MohammadAG For This Useful Post: | ||
ahmadamaj, amjadk, ammyt, casper27, Chrome, cincibluer6, clasificado, CutterSlade, dave1010, Dave999, debernardis, Deltree, dqm, esthreel, F2thaK, fw190, hardkorek, ILikeMaemo, ivyking, IzzehO, jakiman, kolos, mivoligo, mr id, mveplus, nerfiaux, OVK, RobbieThe1st, S0urcerr0r, Silvarum, smartypants, snakekontrol, woody14619, Zoin |
![]() |
2010-11-08
, 21:28
|
Posts: 490 |
Thanked: 191 times |
Joined on May 2010
|
#90
|
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.
![]() |
Tags |
bada rox, detection, h-e-n, hostmode, speed, usb host |
Thread Tools | |
|
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.
My name was Maemo, then it became Meego and now I'm getting a third one. I am Sailfish.