Search Discussions:
Advanced Search...
Welcome to Nokia Support Discussions! Here you can share advice and tips with thousands of other Nokia users around the world in English. Many Nokia employees also follow and participate in the discussions, see our guidelines for more information. Everyone can search and read the discussions, but to post your own question or reply to others, simply sign in with your Nokia account. If this is your first time here, you can choose an alias to represent you. And if you don't have a Nokia account yet, please register.
Reply

Re: No WLAN without SIM on N900

Contributor
Posts: 8
Accepted Solution

No WLAN without SIM on N900

I can't get the WLAN to work without a SIM-card in the phone. I have the same problem if there is a SIM in the phone but I choose not to enter then pin when starting the phone. I have set up a WLAN that works fine with the SIM enabled so it seems as the settings are fine. Is there something special I have to do to enable the WLAN when there is no SIM in the phone?'

Cheers! 

Please use plain text.
Professor
Posts: 429

Re: No WLAN without SIM on N900

which pin?  sim or device?
Please use plain text.
Contributor
Posts: 8

Re: No WLAN without SIM on N900

The sim pin. 

  

Please use plain text.
Professor
Posts: 429

Re: No WLAN without SIM on N900

The SIM PIN controls many functions...  No PIN...the phone is as good as a brick.  SIM pins are more powerful then the standard lock code since it actively disables/prevents functions from being used ( Cell radios, WiFi, keyboard...etc).  If you have a SIM PIN and you do not enter it your device will not function as a phone ( device that has a cellular radio/wifi) and on most phones the device would not even boot.  Since N900 not really a phone the SIM Pin does not prevent it from starting - but it cripples certain parts of the device.

 

Having inserted a "protected" SIM the N900 is now coded to that SIM- and needs that SIM to enable the radio functions. 

 

Your N900 is functioning "normally" for a device where the SIM PIN has not been entered.

 

Call your carrier

1) Ask what functions the SIM PIN disables.

2) Ask if you can get a PIN free SIM.

Please use plain text.
Mobile Guru
Posts: 3,500

Re: No WLAN without SIM on N900

I took my Orange UK sim out of my phone and powered it up. It didn't ask for my PIN code (as expected) and the device booted and I was able to use wifi normally..

 

If I put the SIM back in the phone, and powered up it asked me for my PIN number.. If I skipped this the device would continue to boot and wifi would work but the phone wouldn't.. If I tried to make a call, it asked me for the PIN again.. 

 

Maybe this is a regional issue.. I've not heard of a phone being tied to a specific pin. Some phones refuse to boot without a SIM inserted (usually stating insert pin, emergency calls only). My E90 handset will boot in offline mode if there is no sim inserted.. to use wireless you have to switch it specifically out of offline mode (it prompts 'are you sure you want to use wifi/bluetooth in offline mode?') I thought the N900 was the same and could be used as a wifi tablet without the sim.. I didn't think it had any persistent sim data

 

My device works without problem when no SIM was inserted.. I can confirm that the N900s in the Nokia store in London were the same :smileyhappy:

 

 

Please use plain text.
Contributor
Posts: 8

Re: No WLAN without SIM on N900

"Having inserted a "protected" SIM the N900 is now coded to that SIM- and needs that SIM to enable the radio functions."

 

Is it possible to "uncode" the N900 again?  

 

 

Please use plain text.
Mobile Guru
Posts: 3,500

Re: No WLAN without SIM on N900

Can you let me know the version of software you're using on your device?

 

Open settings, scroll to the end and select about product.. 

 

Version: 1.2009.42-11????

 

 

Please use plain text.
Professor
Posts: 429

Re: No WLAN without SIM on N900

Call your carrier

1) Ask what functions the SIM PIN disables.

2) Ask if you can get a PIN free SIM.

 

 

Can you try it with an non-pin protected sim?  You really need to talk to your carrier.

Please use plain text.
Contributor
Posts: 8

Re: No WLAN without SIM on N900

"Can you let me know the version of software you're using on your device?"

1.2009.42-11 

 

"Call your carrier

 

1) Ask what functions the SIM PIN disables."

 No, they claim that the SIM should not have any thing to do with the WLAN. On the other hand, I'm not sure the guy I talked to really understod what I was talking about. 

 

I tried with a SIM from another carrier, hoping that the N900 would use the settings from this SIM instead. The same result as earlier, WLAN OK with sim, no WLAN without SIM.

 

To me it seems a bit odd that the WLAN is not working just because I inserted the "wrong" SIM once. It must be possible to erase this information some how? 

Please use plain text.
Mobile Guru
Posts: 3,500

Re: No WLAN without SIM on N900

that does seem very strange and I've peronally never seen that behavior on any other phone. It is drastic but you could reflash your phone completely.. restore back t factory settings.. search this forum, it has been posted a few times. I'd be very interested to see the kernel logs on your phone though..

 

if you feel up to it, open an xterminal and type

 

dmesg > MyDocs/dmesg.txt

 

it is case sensative, the > can be entered using the blue button then the ctrl button..

 

try that without a sim in your phone then using pc suite or mass storage mode, pull dmesg.txt off your phone and post it here..

 

 

Please use plain text.
Professor
Posts: 429

Re: No WLAN without SIM on N900

I tried with a SIM from another carrier, hoping that the N900 would use the settings from this SIM instead. The same result as earlier, WLAN OK with sim, no WLAN without SIM."

 

I'm going to ask a really stupid question....  we are talking about wireless lan from a router and not your 3G GPRS wireless internet connection.

 

BTW what is your country /carrier?

Please use plain text.
Mobile Guru
Posts: 3,500

Re: No WLAN without SIM on N900


DrEJV wrote:

I tried with a SIM from another carrier, hoping that the N900 would use the settings from this SIM instead. The same result as earlier, WLAN OK with sim, no WLAN without SIM."

 

I'm going to ask a really stupid question....  we are talking about wireless lan from a router and not your 3G GPRS wireless internet connection.

 

BTW what is your country /carrier?


 

Ha! I both see and like were you're going with that! :smileyhappy: 

 

Please use plain text.
Contributor
Posts: 8

Re: No WLAN without SIM on N900

Yes, we're talking about WLAN as in IEEE 802.11.

 

I'm in Sweden and is using Telenor as a carrier

Please use plain text.
Professor
Posts: 429

Re: No WLAN without SIM on N900

did your sim come from another phone or is it a new sim that you got and registered with the N900
Please use plain text.
Mobile Guru
Posts: 3,500

Re: No WLAN without SIM on N900

I don't believe this problem is directly related to the sim or the function on the sim..

 

I wonder if there is a hardware fault starting the wireless device unless the GSM radio is also initialised.. 

 

Tieing the phone to the sim makes no sense.. what if the sim was lost.. it would render the device useless.. I've never heard or see that happen on a euro GSM/3G network/carrier..

 

The dmesg command will give some indication as to whether the radio (3G/BT/Wifi) has been initialised.. without that we're stabbing in the dark.. and not really getting far

 

Please use plain text.
Professor
Posts: 429

Re: No WLAN without SIM on N900

Did you know that on AT&T you could not use wifi an a BB unless you had a AT&T data plan?  Buddy of mine trickled down a BB to his daughter who was on AT&T as well- she popped in her sim...BB did not work, needed to call AT&T to give them IMIE.  BB worked...she went to connect to home WiFi - zip, nothing. Removed SIM - zip, nothing.  AT&T's response was... No wifi if no sim installed and no wifi if user did not have a BB data plan.  My mates response got daughter E-71

 

Never underestimate the power of a carrier to stick it to its customers.

Please use plain text.
Mobile Guru
Posts: 3,500

Re: No WLAN without SIM on N900

/hi five

 

carriers suck.. and I have stated before they cause serious headaches.. but the BB is a curious device and very heavily carrier tied device.. and for the love of **** I hope the N900 is not that seriously haven't gone down that root.. (that being said we do have access to a lot of the source code for Maemo, and theres not much in there to suggest it so far.. 

 

 

Please use plain text.
Contributor
Posts: 8

Re: No WLAN without SIM on N900

Attachements didn't work... dmesg without a SIM
It is an old SIM that I have used for a few years in other phones without any problems. 
 
0211: Regulatory domain changed to country: US
[    2.436492] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    2.436523] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    2.436584] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    2.436614] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    2.436645] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    2.436706] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    2.436737] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[    2.438049] NET: Registered protocol family 2
[    2.443786] Switched to high resolution mode on CPU 0
[    2.506439] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    2.506805] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    2.507110] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    2.507324] TCP: Hash tables configured (established 8192 bind 8192)
[    2.507354] TCP reno registered
[    2.529907] NET: Registered protocol family 1
[    2.550811] VFS: Disk quotas dquot_6.5.1
[    2.550964] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    2.552459] msgmni has been set to 479
[    2.553009] lowmem: Module initialized.
[    2.561523] alg: No test for stdrng (krng)
[    2.561676] io scheduler noop registered
[    2.562072] io scheduler cfq registered (default)
[    2.562469] OMAP DSS rev 2.0
[    2.562591] OMAP DISPC rev 3.0
[    2.562683] OMAP VENC rev 2
[    2.570526] OMAP3 ROM RNG: initializing
[    2.572723] Serial: 8250/16550 driver4 ports, IRQ sharing disabled
[    2.579345] brd: module loaded
[    2.581634] loop: module loaded
[    2.581726] i2c /dev entries driver
[    2.582885] input: triton2-pwrbutton as /class/input/input0
[    2.607910] triton2 power button driver initialized
[    2.608489] OneNAND driver initializing
[    2.609710] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base d0880000
[    2.609802] OneNAND Manufacturer: Samsung (0xec)
[    2.609832] Muxed OneNAND 256MB 1.8V 16-bit (0x40)
[    2.609863] OneNAND version = 0x0121
[    2.609893] Chip support all block unlock
[    2.609893] Chip has 2 plane
[    2.611511] Scanning device for bad blocks
[    2.673828] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[    2.673858] Bad eraseblock 1094 at 0x088c0000
[    2.728057] Creating 6 MTD partitions on "omap2-onenand":
[    2.728088] 0x00000000-0x00020000 : "bootloader"
[    2.728485] 0x00020000-0x00080000 : "config"
[    2.728729] 0x00080000-0x000c0000 : "log"
[    2.731231] mtdoops: Attached to MTD device 2
[    2.731262] 0x000c0000-0x002c0000 : "kernel"
[    2.731536] 0x002c0000-0x004c0000 : "initfs"
[    2.731811] 0x004c0000-0x10000000 : "rootfs"
[    2.734008] UBI: attaching mtd5 to ubi0
[    2.734069] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    2.734100] UBI: logical eraseblock size:    129024 bytes
[    2.734130] UBI: smallest flash I/O unit:    2048
[    2.734161] UBI: sub-page size:              512
[    2.734191] UBI: VID header offset:          512 (aligned 512)
[    2.734252] UBI: data offset:                2048
[    2.868682] UBI: attached mtd5 to ubi0
[    2.868743] UBI: MTD device name:            "rootfs"
[    2.868804] UBI: MTD device size:            251 MiB
[    2.868835] UBI: number of good PEBs:        2009
[    2.868865] UBI: number of bad PEBs:         1
[    2.868896] UBI: max. allowed volumes:       128
[    2.868927] UBI: wear-leveling threshold:    4096
[    2.868927] UBI: number of internal volumes: 1
[    2.868957] UBI: number of user volumes:     1
[    2.868988] UBI: available PEBs:             0
[    2.869018] UBI: total number of reserved PEBs: 2009
[    2.869049] UBI: number of PEBs reserved for bad PEB handling: 20
[    2.869079] UBI: max/mean erase counter: 10/1
[    2.869110] UBI: image sequence number: 1
[    2.869659] usbcore: registered new interface driver libusual
[    2.869750] mtdoops: Ready 0, 1 
[    2.869781] UBI: background thread "ubi_bgt0d" started, PID 25
[    2.889709] input: omap_twl4030keypad as /class/input/input1
[    2.938293] cpuidle: using governor ladder
[    2.938323] cpuidle: using governor menu
[    2.938507] Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
[    2.938781] ASoC version 0.13.2
[    2.952362] AIC3X Audio Codec 0.2
[    2.954925] asoc: tlv320aic3x <-> omap-mcbsp-dai-0 mapping ok
[    2.956420] asoc: Bluetooth codec <-> omap-mcbsp-dai-1 mapping ok
[    3.008117] input: RX51 (tlv320aic3x) Jack as /class/input/input2
[    3.032348] ALSA device list:
[    3.032409]   #0: RX51 (tlv320aic3x)
[    3.032897] TCP cubic registered
[    3.032958] NET: Registered protocol family 17
[    3.033020] NET: Registered protocol family 15
[    3.033081] Power Management for TI OMAP3.
[    3.036468] pm_dbg_init()
[    3.037231] SmartReflex driver initialized
[    3.043914] Disabling unused clock "gpt2_ick"
[    3.044006] Disabling unused clock "gpt3_ick"
[    3.044036] Disabling unused clock "gpt4_ick"
[    3.044097] Disabling unused clock "gpt5_ick"
[    3.044128] Disabling unused clock "gpt6_ick"
[    3.044158] Disabling unused clock "gpt7_ick"
[    3.044189] Disabling unused clock "gpt8_ick"
[    3.044219] Disabling unused clock "gpt9_ick"
[    3.044250] Disabling unused clock "uart3_ick"
[    3.044311] Disabling unused clock "gpio2_dbck"
[    3.044342] Disabling unused clock "gpio3_dbck"
[    3.044372] Disabling unused clock "gpio4_dbck"
[    3.044403] Disabling unused clock "gpio5_dbck"
[    3.044433] Disabling unused clock "gpio6_dbck"
[    3.044494] Disabling unused clock "gpt9_fck"
[    3.044525] Disabling unused clock "gpt8_fck"
[    3.044555] Disabling unused clock "gpt7_fck"
[    3.044586] Disabling unused clock "gpt6_fck"
[    3.044616] Disabling unused clock "gpt5_fck"
[    3.044647] Disabling unused clock "gpt4_fck"
[    3.044677] Disabling unused clock "gpt3_fck"
[    3.044708] Disabling unused clock "gpt2_fck"
[    3.044769] Disabling unused clock "uart3_fck"
[    3.044799] Disabling unused clock "wdt2_ick"
[    3.044830] Disabling unused clock "wdt2_fck"
[    3.044860] Disabling unused clock "gpio1_dbck"
[    3.044921] Disabling unused clock "rng_ick"
[    3.044952] Disabling unused clock "ssi_ick"
[    3.044982] Disabling unused clock "gpt10_ick"
[    3.045043] Disabling unused clock "gpt11_ick"
[    3.045074] Disabling unused clock "uart1_ick"
[    3.045104] Disabling unused clock "uart2_ick"
[    3.045135] Disabling unused clock "usbtll_ick"
[    3.045196] Disabling unused clock "ssi_ssr_fck"
[    3.045227] Disabling unused clock "uart1_fck"
[    3.045257] Disabling unused clock "uart2_fck"
[    3.045318] Disabling unused clock "usbtll_fck"
[    3.045440] Disabling unused clock "ts_fck"
[    3.045471] Disabling unused clock "cpefuse_fck"
[    3.045532] Disabling unused clock "gpt11_fck"
[    3.045562] Disabling unused clock "gpt10_fck"
[    3.045593] Disabling unused clock "dpll5_ck"
[    3.045684] Disabling unused clock "dpll4_m6x2_ck"
[    3.045715] Disabling unused clock "dpll4_m5x2_ck"
[    3.045745] Disabling unused clock "dpll3_m3x2_ck"
[    3.045776] Disabling unused clock "sys_clkout1"

Please use plain text.
Contributor
Posts: 8

Re: No WLAN without SIM on N900

[    3.046173] Bootup reason: pwr_key
[    3.046264] OMAP GPIO switch handler initializing
[    3.048767] slide (GPIO 71) is now closed
[    3.048828] proximity (GPIO 89) is now open
[    3.048858] kb_lock (GPIO 113) is now open
[    3.048889] headphone (GPIO 177) is now disconnected
[    3.048919] cam_shutter (GPIO 110) is now closed
[    3.048950] cam_launch (GPIO 69) is now inactive
[    3.048980] cam_focus (GPIO 68) is now inactive
[    3.049011] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
[    3.061279] omapfb: acx565akm rev 8b LCD detected
[    3.068267] tpa6130a2 2-0060: Headphone amplifier initialized successfully
[    3.088958] UBIFS: recovery needed
[    3.111724] UBIFS: recovery completed
[    3.111816] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.111846] UBIFS: file system size:   254693376 bytes (248724 KiB, 242 MiB, 1974 LEBs)
[    3.111907] UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[    3.111968] UBIFS: media format:       4 (latest is 4)
[    3.111999] UBIFS: default compressor: lzo
[    3.112030] UBIFS: reserved for root:  4384586 bytes (4281 KiB)
[    3.112396] VFS: Mounted root (ubifs filesystem).
[    3.112609] Freeing init memory: 144K
[    4.599700] Registered led device: twl4030:vibrator
[    4.662658] cam_shutter (GPIO 110) is now open
[    4.693328] twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
[    4.826751] cam_shutter (GPIO 110) is now closed
[    4.827392] tsl2563 2-0029: model 7, rev. 0
[    4.897613] lp5523 2-0032: LP5523 Programmable led chip found
[    4.990875] Linux video capture interface: v2.00
[    5.053344] I2C driver for Si4713 FM Radio Transmitter
[    5.842529] Bluetooth: Core ver 2.15
[    5.858184] NET: Registered protocol family 31
[    5.858245] Bluetooth: HCI device and connection manager initialized
[    5.858306] Bluetooth: HCI socket layer initialized
[    5.897033] i2c_omap i2c_omap.2: controller timed out
[    5.936218] hci_h4p hci_h4p: Registering HCI H4P device
[    5.953918] lp5523 2-0032: got interrupt from led chip
[    5.954498] lp5523 2-0032: interrupt from led chip 4f
[    5.954528] lp5523 2-0032: all engines configured
[    5.954559] lp5523 2-0032: disabling engines
[    5.955169] Registered led device: lp5523:kb1
[    5.955322] Registered led device: lp5523:kb2
[    5.955474] Registered led device: lp5523:kb3
[    5.955596] Registered led device: lp5523:kb4
[    5.955749] Registered led device: lp5523:b
[    5.955902] Registered led device: lp5523:g
[    5.956024] Registered led device: lp5523:r
[    5.956176] Registered led device: lp5523:kb5
[    5.956298] Registered led device: lp5523:kb6
[    6.020538] nokia-av nokia-av: accessory detect module initialized
[    6.038970] radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00:00 Component: 3.0 Chip Rev.: unknown
[    6.137634] TSC2005 driver initializing
[    6.140747] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
[    6.140899] mmc0: cover is open, card is now inaccessible
[    6.143524] input: TSC2005 touchscreen as /class/input/input3
[    6.249572] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
[    6.407867] omap_wdt omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec, nowayout is on
[    6.410339] SSI DRIVER Version 1.1-rc2
[    6.410827] omap_ssi omap_ssi: SSI Hardware REVISION 1.0
[    6.524047] phy0: Selected rate control algorithm 'minstrel'
[    6.556182] wl1251: loaded
[    6.556915] wl1251: initialized
[    6.575134] smc91x: not found (-19).
[    6.686187] mmc1: new high speed MMC card at address 0001
[    6.691162] mmcblk0: mmc1:0001 MMC32G 29.8 GiB 
[    6.691497]  mmcblk0: p1 p2 p3
[    6.935852] CMT speech driver v0.2.0
[    6.948913] NET: Registered protocol family 35
[    6.975830] SSI McSAAB PROTOCOL Version: 2.0-rc1
[    7.204162] dspbridge_init: 412800 bytes @ 80600000
[    7.290100] omap-iommu omap-iommu.1: isp registered
[    7.452148] omap-iommu omap-iommu.1: isp: version 1.1
[    7.602935] smia-sensor 2-0010: firmware: requesting smia-sensor-01-022b-04.bin
[    7.627716] smia_reglist_import: meta_reglist version 2009-07-27
[    7.627777] smia_reglist_import: type 10 w 648 h 488 fmt 30314142 ival 100/1502 ptr d0c392a0
[    7.627807] smia_reglist_import: type 10 w 648 h 488 fmt 30314142 ival 100/3003 ptr d0c39228
[    7.627838] smia_reglist_import: type 1 w 0 h 0 fmt 30314142 ival 100/0 ptr d0c39090
[    7.627838] smia_reglist_import: type 0 w 0 h 0 fmt 30314142 ival 100/0 ptr d0c39038
[    7.640594] et8ek8 3-003e: firmware: requesting et8ek8-0002.bin
[    7.664611] smia_reglist_import: meta_reglist version V14 03-June-2008
[    7.664703] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314442 ival 100/1292 ptr d0c3c1f4
[    7.664733] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314142 ival 100/399 ptr d0c3c454
[    7.664733] smia_reglist_import: type 10 w 1296 h 984 fmt 30314142 ival 100/501 ptr d0c3c57c
[    7.664764] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/2500 ptr d0c3c614
[    7.664794] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/3000 ptr d0c3c28c
[    7.664794] smia_reglist_import: type 10 w 864 h 656 fmt 30314142 ival 100/2988 ptr d0c3c324
[    7.664825] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/499 ptr d0c3c4e4
[    7.664825] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/2993 ptr d0c3c3bc
[    7.664855] smia_reglist_import: type 1 w 2592 h 1968 fmt 30314142 ival 100/1207 ptr d0c3c04c
[    8.282836] g_file_storage gadget: File-backed Storage Gadget, version: 7 August 2007
[    8.282928] g_file_storage gadget: Number of LUNs=2 Number of buffers=16
[    8.282989] musb_hdrc musb_hdrc: MUSB HDRC host driver
[    8.283569] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[    8.284027] usb usb1: configuration #1 chosen from 1 choice
[    8.284240] hub 1-0:1.0: USB hub found
[    8.284362] hub 1-0:1.0: 1 port detected
[   11.506439] cam_shutter (GPIO 110) is now open
[   11.672912] McSAAB: ACWAKE DOWN
[   11.672973] McSAAB: ACWAKE UP
[   11.673004] McSAAB: WAKELINES TEST OK
[   18.029876] kjournald starting.  Commit interval 1 seconds
[   18.033935] EXT3 FS on mmcblk0p2, internal journal
[   18.033966] EXT3-fs: recovery complete.
[   18.038177] EXT3-fs: mounted filesystem with writeback data mode.
[   18.289062] Adding 786424k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 across:786424k
[   18.681274] Bluetooth: L2CAP ver 2.13
[   18.681304] Bluetooth: L2CAP socket layer initialized
[   18.791046] Bluetooth: SCO (Voice Link) ver 0.6
[   18.791076] Bluetooth: SCO socket layer initialized
[   18.795135] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
[   19.278747] Bluetooth: RFCOMM socket layer initialized
[   19.278839] Bluetooth: RFCOMM TTY layer initialized
[   19.278839] Bluetooth: RFCOMM ver 1.11
[   23.467864] misc iphb: Module registered in 2.6.28-omap1, built Oct 28 2009 15:33:55
[   24.272094] cam_shutter (GPIO 110) is now closed
[   28.835754] cam_shutter (GPIO 110) is now open
[   30.053375] slide (GPIO 71) is now open
[   30.358337] cam_shutter (GPIO 110) is now closed
[   41.336791] warning: `dnsmasq' uses 32-bit capabilities (legacy support in use)
[   49.227874] cfg80211: Regulatory domain changed to country: US
[   49.227905]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   49.227935]  (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   49.227966]  (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[   49.227966]  (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[   49.227996]  (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[   49.227996]  (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[   49.228027]  (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[   51.022369] wl12xx spi4.0: firmware: requesting wl1251-fw.bin
[   52.592498] wl1251: 154 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[   52.608123] wl1251: firmware booted (Rev 6.0.4.156)
[   53.928649] wl1251: down
[   54.926940] SCSI subsystem initialized
[   55.147033] Driver 'sd' needs updating - please use bus_type methods
[  115.319183] cam_shutter (GPIO 110) is now open
[  119.123931] cam_shutter (GPIO 110) is now closed

Please use plain text.
Registered Member
Posts: 1

HOW CAN I USE N900

PLEASE CAN THE N 900 BE USED TO MAKE A CALL WITHOUT SLIDING IT OPEN?

replies to daviiis01@yahoo.com 

Please use plain text.