| 1   2   | Next
maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   16GB miniSD issue!!! HELP! (https://talk.maemo.org/showthread.php?t=57048)

HeavyComponent 2010-06-24 23:01

16GB miniSD issue!!! HELP!
 
Ok guys, I've looked everywhere for a solution for this and I can't find ONE SOLID solution that will tell me step by step how to fix this. Some solutions tell you steps, but in the middle they assume you know how to get this or do this and I'm clueless! :(

For some reason IN my N900 my 16GB miniSD card isn't working the way it should. Everytime I try to add something ERROR, CORRUPTED anything in that matter. Formatting it in the N900 doesn't work! Formatting it via PC while in the N900 doesn't work! I also formatted it in the adapter and a different phone (EVO) then put it back in my N900, doesn't work! When I put it in an adapter so the PC could read it or another phone to read it, it works GREAT! It's just that when it comes to my phone to use it it's a no go.

Anyone have a SOLID solution? I'm new to Nokia, but I'm def. getting the hang. I'm coming from a Windows phone (HD2) and I know about flashing and stuff. Just that the flashing for this phone is more difficult. I tried reading, but I can't seem to understand it yet. Flashing for Windows phone is much easier!

Thanks in advance! Somebody sent me to this site so I hope I get great results. :D

BTW: I have Version 10.2010.19-1.002

wmarone 2010-06-24 23:21

Re: 16GB miniSD issue!!! HELP!
 
The initial questions I have are:
- Where did you get the SD card
- Where was the seller based
- Have you tried to write data to it beyond formatting from either the EVO or the PC?

HeavyComponent 2010-06-24 23:42

Re: 16GB miniSD issue!!! HELP!
 
- The SD card came from my brand NEW never been used HD2.
- Phone came directly from T-Mobile
- With the adapter or EVO no, but when it was on my N900 I tried and it kept telling me to insert it because it wouldn't open folders, create folders or add any files.

The thing is a few times I added files via N900/USB and I thought it was working then out the blue I would get errors. Happens everytime so I don't even try to add any files anymore.

I will try adding data to the card while on the EVO and adapter to see what happens. I already have a great feeling it will work fine, but when I add it to my phone to access those files. It will not work!

Thanks for the reply!

HeavyComponent 2010-06-25 22:23

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by wmarone (Post 728266)
- Have you tried to write data to it beyond formatting from either the EVO or the PC?

Ok the card seems to be working fine when it comes to adding data via Evo and adapter.

Any suggestions?

There was a thread that I found off google that the person rereflashed with EMMC or whatever it is. I went through the wiki and I don't understand the instructions because it's not a simple step by step. I'm use to flashing because I'm coming from a windows mobile phone (HD2). Pretty easy flashing custom ROMs for WM based phones.

HeavyComponent 2010-06-26 15:51

Re: 16GB miniSD issue!!! HELP!
 
I can't be the only one with this issue!

choubbi 2010-06-27 13:29

Re: 16GB miniSD issue!!! HELP!
 
Maybe a defective connector or something like that... I'd send it back to Nokia if this happened to me.

crail 2010-06-27 13:37

Re: 16GB miniSD issue!!! HELP!
 
try scan and fix option with pc, and tick bad sectors box. if youre using windows. if that dont fix it then its a gonna

HeavyComponent 2010-06-27 13:40

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by choubbi (Post 731329)
Maybe a defective connector or something like that... I'd send it back to Nokia if this happened to me.

I have a feeling it has nothing to do with a bad device. Like I said I read somewhere how somebody did a reflash of EMMC or MMC and got it to work. Where I found it I didn't get basic instructions on how to do it so I left it alone.

I will try and look for it.

HeavyComponent 2010-06-27 14:03

Re: 16GB miniSD issue!!! HELP!
 
I've read somewhere to do the command "dmesg" in X Terminal to look for errors. I don't know what I'm looking for so can someone look through the list. I will most a list with the SD card inserted and when it's not.

With the SD card inserted...

Code:

[95963.578399] slide (GPIO 71) is now open
[95975.125457] slide (GPIO 71) is now closed
[95985.500610] slide (GPIO 71) is now open
[96003.679992] slide (GPIO 71) is now closed
[96021.883148] slide (GPIO 71) is now open
[96190.891113] slide (GPIO 71) is now closed
[96237.820709] slide (GPIO 71) is now open
[96261.023773] slide (GPIO 71) is now closed
[96271.569580] gprs0: detached
[96275.703765] gprs0: attached
[96281.297210] slide (GPIO 71) is now open
[96295.500457] slide (GPIO 71) is now closed
[96313.750457] slide (GPIO 71) is now open
[96376.000610] slide (GPIO 71) is now closed
[96417.203704] slide (GPIO 71) is now open
[96515.000610] slide (GPIO 71) is now closed
[96558.125427] slide (GPIO 71) is now open
[96689.719238] slide (GPIO 71) is now closed
[96722.185333] gprs0: detached
[96726.313629] gprs0: attached
[96756.867614] cam_focus (GPIO 68) is now active
[96756.930053] cam_focus (GPIO 68) is now inactive
[96759.656646] kb_lock (GPIO 113) is now closed
[96759.859710] kb_lock (GPIO 113) is now open
[96782.727233] kb_lock (GPIO 113) is now closed
[96782.906707] kb_lock (GPIO 113) is now open
[96786.891296] slide (GPIO 71) is now open
[96802.711425] slide (GPIO 71) is now closed
[96804.133209] kb_lock (GPIO 113) is now closed
[96804.305114] kb_lock (GPIO 113) is now open
[96815.469268] kb_lock (GPIO 113) is now closed
[96815.625518] kb_lock (GPIO 113) is now open
[96819.484741] slide (GPIO 71) is now open
[96880.673187] gprs0: detached
[96884.821105] gprs0: attached
[96888.101959] slide (GPIO 71) is now closed
[96935.375488] slide (GPIO 71) is now open
[96973.412872] gprs0: detached
[96977.538543] gprs0: attached
[97002.680023] slide (GPIO 71) is now closed
[97008.516174] kb_lock (GPIO 113) is now closed
[97008.664428] kb_lock (GPIO 113) is now open
[97013.485046] kb_lock (GPIO 113) is now closed
[97013.625488] kb_lock (GPIO 113) is now open
[97024.000488] slide (GPIO 71) is now open
[97037.687988] slide (GPIO 71) is now closed
[97039.805175] slide (GPIO 71) is now open
[97058.953552] slide (GPIO 71) is now closed
[97137.359832] slide (GPIO 71) is now open
[97152.500335] slide (GPIO 71) is now closed
[97181.016082] slide (GPIO 71) is now open
[97196.023956] slide (GPIO 71) is now closed
[97281.914550] slide (GPIO 71) is now open
[97314.133148] slide (GPIO 71) is now closed
[97357.484863] slide (GPIO 71) is now open
[97392.687835] slide (GPIO 71) is now closed
[97550.399047] slide (GPIO 71) is now open
[97561.585815] slide (GPIO 71) is now closed
[97566.813140] slide (GPIO 71) is now open
[97567.664642] slide (GPIO 71) is now closed
[97686.235046] slide (GPIO 71) is now open
[97691.305175] slide (GPIO 71) is now closed
[97692.141113] kb_lock (GPIO 113) is now closed
[97692.359771] kb_lock (GPIO 113) is now open
[97846.687866] kb_lock (GPIO 113) is now closed
[97846.859680] kb_lock (GPIO 113) is now open
[97848.289581] kb_lock (GPIO 113) is now closed
[97848.445709] kb_lock (GPIO 113) is now open
[97881.070831] kb_lock (GPIO 113) is now closed
[97881.250488] kb_lock (GPIO 113) is now open
[97940.281616] kb_lock (GPIO 113) is now closed
[97940.508239] kb_lock (GPIO 113) is now open
[99182.988983] gprs0: detached
[99187.139556] gprs0: attached
[100738.133270] slide (GPIO 71) is now open
[100740.851898] slide (GPIO 71) is now closed
[100819.750457] cam_focus (GPIO 68) is now active
[100819.859832] cam_focus (GPIO 68) is now inactive
[100819.961395] cam_focus (GPIO 68) is now active
[100819.992675] cam_focus (GPIO 68) is now inactive
[100820.773895] cam_focus (GPIO 68) is now active
[100820.844238] cam_focus (GPIO 68) is now inactive
[100821.195831] cam_focus (GPIO 68) is now active
[100821.383270] cam_focus (GPIO 68) is now inactive
[100907.944396] regulator_disable: not in use by this consumer
[100907.944458] regulator_disable: not in use by this consumer
[100929.102020] cam_focus (GPIO 68) is now active
[100929.633361] cam_focus (GPIO 68) is now inactive
[100945.461303] slide (GPIO 71) is now open
[100951.617736] slide (GPIO 71) is now closed
[101101.180206] cam_focus (GPIO 68) is now active
[101101.242645] cam_focus (GPIO 68) is now inactive
[101104.680145] kb_lock (GPIO 113) is now closed
[101104.922790] kb_lock (GPIO 113) is now open
[101300.289337] proximity (GPIO 89) is now open
[101307.039520] proximity (GPIO 89) is now closed
[101313.555145] proximity (GPIO 89) is now open
[101314.508361] proximity (GPIO 89) is now closed
[101315.938140] proximity (GPIO 89) is now open
[101318.719238] proximity (GPIO 89) is now closed
[101318.798431] proximity (GPIO 89) is now open
[101320.383605] proximity (GPIO 89) is now closed
[101320.628356] proximity (GPIO 89) is now open
[101322.133636] proximity (GPIO 89) is now closed
[101323.961334] proximity (GPIO 89) is now open
[101325.328460] slide (GPIO 71) is now open
[101330.407592] kb_lock (GPIO 113) is now closed
[101330.578552] kb_lock (GPIO 113) is now open
[101391.281646] slide (GPIO 71) is now closed
[101394.523895] kb_lock (GPIO 113) is now closed
[101394.773803] kb_lock (GPIO 113) is now open
[101400.586456] slide (GPIO 71) is now open
[101425.555145] slide (GPIO 71) is now closed
[101426.367614] kb_lock (GPIO 113) is now closed
[101426.633178] kb_lock (GPIO 113) is now open
[101558.773956] slide (GPIO 71) is now open
[101666.117645] slide (GPIO 71) is now closed
[101667.281799] kb_lock (GPIO 113) is now closed
[101667.539398] kb_lock (GPIO 113) is now open
[101750.312927] kb_lock (GPIO 113) is now closed
[101750.531616] kb_lock (GPIO 113) is now open
[101756.890991] slide (GPIO 71) is now open
[101771.461273] slide (GPIO 71) is now closed
[101772.695709] kb_lock (GPIO 113) is now closed
[101772.828521] kb_lock (GPIO 113) is now open
[102234.609680] slide (GPIO 71) is now open
[102270.750335] slide (GPIO 71) is now closed
[102295.656646] slide (GPIO 71) is now open
[102321.188659] slide (GPIO 71) is now closed
[102380.625396] proximity (GPIO 89) is now closed
[102393.656707] proximity (GPIO 89) is now open
[102456.655792] slide (GPIO 71) is now open
[102552.617645] slide (GPIO 71) is now closed
[102554.656707] kb_lock (GPIO 113) is now closed
[102554.836303] kb_lock (GPIO 113) is now open
[103181.656707] slide (GPIO 71) is now open
[103224.078521] slide (GPIO 71) is now closed
[103225.398864] kb_lock (GPIO 113) is now closed
[103225.594116] kb_lock (GPIO 113) is now open
[103260.938049] slide (GPIO 71) is now open
[103278.672210] slide (GPIO 71) is now closed
[103280.133270] kb_lock (GPIO 113) is now closed
[103280.375396] kb_lock (GPIO 113) is now open
[103319.203582] slide (GPIO 71) is now open
[103337.281768] slide (GPIO 71) is now closed
[103339.742584] kb_lock (GPIO 113) is now closed
[103339.976867] kb_lock (GPIO 113) is now open
[103362.664489] slide (GPIO 71) is now open
[103443.369964] omapfb omapfb: Unknown ioctl 0x80047210
[103443.371276] omapfb omapfb: Unknown ioctl 0x80047210
[103443.372558] omapfb omapfb: Unknown ioctl 0x80047210
[103444.303802] omap-previewer omap-previewer: previewer_ioctl: Invalid Command Value
[103498.094207] slide (GPIO 71) is now closed
[103499.648864] kb_lock (GPIO 113) is now closed
[103499.836334] kb_lock (GPIO 113) is now open
[103627.851959] slide (GPIO 71) is now open
[103643.759277] slide (GPIO 71) is now closed
[103656.289520] kb_lock (GPIO 113) is now closed
[103656.555145] kb_lock (GPIO 113) is now open
[103735.781646] kb_lock (GPIO 113) is now closed
[103735.945556] kb_lock (GPIO 113) is now open
[103738.469085] slide (GPIO 71) is now open
[103751.531707] slide (GPIO 71) is now closed
[103764.617645] slide (GPIO 71) is now open
[103774.867553] slide (GPIO 71) is now closed
[103775.578582] kb_lock (GPIO 113) is now closed
[103775.820678] kb_lock (GPIO 113) is now open
[104745.328582] slide (GPIO 71) is now open
[104813.258239] slide (GPIO 71) is now closed
[104813.922454] kb_lock (GPIO 113) is now closed
[104814.179992] kb_lock (GPIO 113) is now open
[106272.609832] slide (GPIO 71) is now open
[106304.609924] slide (GPIO 71) is now closed
[106351.336212] slide (GPIO 71) is now open
[106449.156555] slide (GPIO 71) is now closed
[107228.289398] kb_lock (GPIO 113) is now closed
[107228.485290] kb_lock (GPIO 113) is now open
[130531.453247] regulator_disable: not in use by this consumer
[130531.453369] regulator_disable: not in use by this consumer
[130534.086395] slide (GPIO 71) is now open
[130546.875457] slide (GPIO 71) is now closed
[130562.781707] kb_lock (GPIO 113) is now closed
[130562.805145] kb_lock (GPIO 113) is now open
[ 3502.758270] proximity (GPIO 89) is now closed
[ 3515.695770] proximity (GPIO 89) is now open
[ 3522.047363] slide (GPIO 71) is now open
[ 3534.766113] slide (GPIO 71) is now closed
[ 4038.344268] slide (GPIO 71) is now open
[ 4103.797302] slide (GPIO 71) is now closed
[ 4340.773742] kb_lock (GPIO 113) is now closed
[ 4341.000244] kb_lock (GPIO 113) is now open
[ 7252.180145] slide (GPIO 71) is now open

EDIT: Took off the long post! :o

HeavyComponent 2010-06-27 14:15

Re: 16GB miniSD issue!!! HELP!
 
With SD card NOT inserted...

Code:

[ 3.098937] Disabling unused clock "ssi_ick"
[ 3.098968] Disabling unused clock "gpt10_ick"
[ 3.098999] Disabling unused clock "gpt11_ick"
[ 3.099029] Disabling unused clock "uart1_ick"
[ 3.099090] Disabling unused clock "uart2_ick"
[ 3.099121] Disabling unused clock "usbtll_ick"
[ 3.099151] Disabling unused clock "ssi_ssr_fck"
[ 3.099212] Disabling unused clock "uart1_fck"
[ 3.099243] Disabling unused clock "uart2_fck"
[ 3.099273] Disabling unused clock "usbtll_fck"
[ 3.099334] Disabling unused clock "ts_fck"
[ 3.099365] Disabling unused clock "cpefuse_fck"
[ 3.099426] Disabling unused clock "gpt11_fck"
[ 3.099456] Disabling unused clock "gpt10_fck"
[ 3.099487] Disabling unused clock "dpll5_ck"
[ 3.099548] Disabling unused clock "dpll4_m6x2_ck"
[ 3.099609] Disabling unused clock "dpll4_m5x2_ck"
[ 3.099639] Disabling unused clock "dpll3_m3x2_ck"
[ 3.099670] Disabling unused clock "sys_clkout1"
[ 3.100128] Bootup reason: pwr_key
[ 3.100219] OMAP GPIO switch handler initializing
[ 3.102874] slide (GPIO 71) is now closed
[ 3.102935] proximity (GPIO 89) is now open
[ 3.102966] kb_lock (GPIO 113) is now open
[ 3.102996] headphone (GPIO 177) is now disconnected
[ 3.103027] cam_shutter (GPIO 110) is now closed
[ 3.103057] cam_launch (GPIO 69) is now inactive
[ 3.103088] cam_focus (GPIO 68) is now inactive
[ 3.103118] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
[ 3.123504] omapfb: acx565akm rev 8d LCD detected
[ 3.157989] tpa6130a2 2-0060: Headphone amplifier initialized successfully
[ 3.178680] UBIFS: recovery needed
[ 3.666107] UBIFS: recovery completed
[ 3.666168] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.666229] UBIFS: file system size: 254564352 bytes (248598 KiB, 242 MiB, 1973 LEBs)
[ 3.666259] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[ 3.666320] UBIFS: media format: 4 (latest is 4)
[ 3.666351] UBIFS: default compressor: lzo
[ 3.666381] UBIFS: reserved for root: 4384586 bytes (4281 KiB)
[ 3.666778] VFS: Mounted root (ubifs filesystem).
[ 3.666992] Freeing init memory: 144K
[ 5.290100] Registered led device: twl4030:vibrator
[ 5.569091] twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
[ 5.766693] tsl2563 2-0029: model 7, rev. 0
[ 5.891754] lp5523 2-0032: LP5523 Programmable led chip found
[ 6.088317] Linux video capture interface: v2.00
[ 6.119110] I2C driver for Si4713 FM Radio Transmitter
[ 6.880249] Bluetooth: Core ver 2.15
[ 6.888977] i2c_omap i2c_omap.2: controller timed out
[ 6.898986] NET: Registered protocol family 31
[ 6.899017] Bluetooth: HCI device and connection manager initialized
[ 6.899078] Bluetooth: HCI socket layer initialized
[ 6.945739] lp5523 2-0032: got interrupt from led chip
[ 6.946319] lp5523 2-0032: interrupt from led chip 4f
[ 6.946350] lp5523 2-0032: all engines configured
[ 6.946380] lp5523 2-0032: disabling engines
[ 6.946990] Registered led device: lp5523:kb1
[ 6.947143] Registered led device: lp5523:kb2
[ 6.947265] Registered led device: lp5523:kb3
[ 6.947418] Registered led device: lp5523:kb4
[ 6.947540] Registered led device: lp5523:b
[ 6.947662] Registered led device: lp5523:g
[ 6.947784] Registered led device: lp5523:r
[ 6.947937] Registered led device: lp5523:kb5
[ 6.948059] Registered led device: lp5523:kb6
[ 6.990203] hci_h4p hci_h4p: Registering HCI H4P device
[ 7.030883] radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00:00 Component: 3.0 Chip Rev.: unknown
[ 7.149322] nokia-av nokia-av: accessory detect module initialized
[ 7.156707] TSC2005 driver initializing
[ 7.157379] input: TSC2005 touchscreen as /class/input/input3
[ 7.214141] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
[ 7.334747] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
[ 7.664398] omap_wdt omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec, nowayout is on
[ 7.685455] SSI DRIVER Version 1.1-rc2
[ 7.686218] omap_ssi omap_ssi: SSI Hardware REVISION 1.0
[ 7.756164] phy0: Selected rate control algorithm 'minstrel'
[ 7.811004] mmc1: new high speed MMC card at address 0001
[ 7.813018] smc91x: not found (-19).
[ 7.818267] mmcblk0: mmc1:0001 MMC32G 29.8 GiB
[ 7.818695] mmcblk0: p1 p2 p3
[ 7.846923] wl1251: loaded
[ 7.847625] wl1251: initialized
[ 8.227539] CMT speech driver v0.2.0
[ 8.355377] NET: Registered protocol family 35
[ 8.422271] SSI McSAAB PROTOCOL Version: 2.0-rc1
[ 8.687438] dspbridge_init: 412800 bytes @ 80600000
[ 8.809112] omap-iommu omap-iommu.1: isp registered
[ 9.013305] omap-iommu omap-iommu.1: isp: version 1.1
[ 9.188262] smia-sensor 2-0010: firmware: requesting smia-sensor-01-022b-04.bin
[ 9.221282] smia_reglist_import: meta_reglist version 2009-07-27
[ 9.221374] smia_reglist_import: type 10 w 648 h 488fmt 30314142 ival 100/1502 ptr d0ccc2a0
[ 9.221374] smia_reglist_import: type 10 w 648 h 488fmt 30314142 ival 100/3003 ptr d0ccc228
[ 9.221405] smia_reglist_import: type 1 w 0 h 0 fmt 30314142 ival 100/0 ptr d0ccc090
[ 9.221435] smia_reglist_import: type 0 w 0 h 0 fmt 30314142 ival 100/0 ptr d0ccc038
[ 9.234130] et8ek8 3-003e: firmware: requesting et8ek8-0002.bin
[ 9.257568] smia_reglist_import: meta_reglist version V14 03-June-2008
[ 9.257659] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314442 ival 100/1292 ptr d0ccf1f4
[ 9.257690] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314142 ival 100/399 ptr d0ccf454
[ 9.257720] smia_reglist_import: type 10 w 1296 h 984fmt 30314142 ival 100/501 ptr d0ccf57c
[ 9.257720] smia_reglist_import: type 10 w 1296 h 984fmt 30314442 ival 100/2500 ptr d0ccf614
[ 9.257751] smia_reglist_import: type 10 w 1296 h 984fmt 30314442 ival 100/3000 ptr d0ccf28c
[ 9.257781] smia_reglist_import: type 10 w 864 h 656fmt 30314142 ival 100/2988 ptr d0ccf324
[ 9.257781] smia_reglist_import: type 10 w 648 h 492fmt 30314142 ival 100/499 ptr d0ccf4e4
[ 9.257812] smia_reglist_import: type 10 w 648 h 492fmt 30314142 ival 100/2993 ptr d0ccf3bc
[ 9.257812] smia_reglist_import: type 1 w 2592 h 1968 fmt 30314142 ival 100/1207 ptr d0ccf04c
[ 10.215026] NET: Registered protocol family 10
[ 10.215698] lo: Disabled Privacy Extensions
[ 10.216217] ADDRCONF(NETDEV_UP): phonet0: link is not ready
[ 10.248321] g_file_storage gadget: File-backed Storage Gadget, version: 7 August 2007
[ 10.248382] g_file_storage gadget: Number of LUNs=2 Number of buffers=16
[ 10.248443] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 10.249053] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[ 10.249542] usb usb1: configuration #1 chosen from 1 choice
[ 10.249786] hub 1-0:1.0: USB hub found
[ 10.249877] hub 1-0:1.0: 1 port detected
[ 12.729278] Adding 786424k swap on /dev/mmcblk0p3. Priority:-1 extents:1 across:786424k
[ 13.041076] proximity (GPIO 89) is now closed
[ 13.834350] proximity (GPIO 89) is now open
[ 15.932952] kjournald starting. Commit interval 1 seconds
[ 15.948181] EXT3 FS on mmcblk0p2, internal journal
[ 15.948211] EXT3-fs: recovery complete.
[ 15.952392] EXT3-fs: mounted filesystem with writeback data mode.
[ 18.148101] McSAAB: ACWAKE DOWN
[ 18.148162] McSAAB: ACWAKE UP
[ 18.148193] McSAAB: WAKELINES TEST OK
[ 18.148590] ADDRCONF(NETDEV_CHANGE): phonet0: link becomes ready
[ 18.277282] Bluetooth: L2CAP ver 2.13
[ 18.277313] Bluetooth: L2CAP socket layer initialized
[ 18.387237] Bluetooth: SCO (Voice Link) ver 0.6
[ 18.387268] Bluetooth: SCO socket layer initialized
[ 18.395080] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
[ 19.068756] Bluetooth: RFCOMM socket layer initialized
[ 19.068817] Bluetooth: RFCOMM TTY layer initialized
[ 19.068847] Bluetooth: RFCOMM ver 1.11
[ 22.325073] misc iphb: Module registered in 2.6.28.10power37, built May 26 2010 00:25:25
[ 53.101409] cfg80211: Regulatory domain changed to country: US
[ 53.101440] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 53.101440] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 53.101470] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 53.101470] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 53.101501] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 53.101501] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 53.101531] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 55.906250] SCSI subsystem initialized
[ 55.994873] gprs0: attached
[ 56.268035] Driver 'sd' needs updating - please use bus_type methods
[ 74.482788] slide (GPIO 71) is now open

In the list I've seen this at the end...

Driver 'sd' needs updating - please use bus_type methods

How do I get it updated?

Thanks

EDIT: Took off the long post sorry! :o

ToJa92 2010-06-27 14:18

Re: 16GB miniSD issue!!! HELP!
 
@HeavyComponent: Use pastebin.com instead of paste'ing such long text blocks, just a advice :)

HeavyComponent 2010-06-27 14:20

Re: 16GB miniSD issue!!! HELP!
 
Lol oh sorry, I didn't know about that.

HeavyComponent 2010-06-28 00:02

Re: 16GB miniSD issue!!! HELP!
 
If anyone had this issue and ended up solving it please post! I would LOVE to get my 16GB working for a total of 48GB of memory.

crail 2010-06-28 00:04

Re: 16GB miniSD issue!!! HELP!
 
ignore my reply it wasnt helpful at all *faint*

HeavyComponent 2010-06-28 00:09

Re: 16GB miniSD issue!!! HELP!
 
crail,

No no lol, I appreciate your reply thanks for your help.

darguzar 2010-06-28 00:09

Re: 16GB miniSD issue!!! HELP!
 
i don't know if this is gona fix it or not but you can always try....

well i had to same problem but with a 8gb card and some other cell phone...

the thing was that the card format (Like it is basically FAT or FAT 16)

So for that try fromatting it but not on the phone or directly from the card reader by right clicking the drive icon and formatting it

Format it with Panasonic SD Formatter......

it might be available online for to download a very small but very effective software for formatting Memory cards...

I hope it solves the problem....

If you can't find the SD formatter email me...
darguzar@yahoo.com

crail 2010-06-28 00:12

Re: 16GB miniSD issue!!! HELP!
 
HC did you try what i said?

HeavyComponent 2010-06-28 00:23

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by darguzar (Post 732038)
i don't know if this is gona fix it or not but you can always try....

well i had to same problem but with a 8gb card and some other cell phone...

the thing was that the card format (Like it is basically FAT or FAT 16)

So for that try fromatting it but not on the phone or directly from the card reader by right clicking the drive icon and formatting it

Format it with Panasonic SD Formatter......

it might be available online for to download a very small but very effective software for formatting Memory cards...

I hope it solves the problem....

If you can't find the SD formatter email me...
darguzar@yahoo.com

Will give it a try, thanks dude.

Crail,

Yes, no errors. Thanks!

HeavyComponent 2010-06-28 00:35

Re: 16GB miniSD issue!!! HELP!
 
darguzar,

Is it this right here that you're talking about?

http://panasonic.jp/support/global/c...oad/index.html

If so, I'm formatting it with the program while the SD card is in the N900 is that fine or do I need to use the adapter?

damion 2010-06-28 00:47

Re: 16GB miniSD issue!!! HELP!
 
become root (root sh installed and type sudo gainroot).
type:

sfdisk -l /dev/mmcblk1
file -s /dev'mmcblk1
file -s /dev'mmcblk1p1
file -s /dev'mmcblk1p2

paste the output here.

As long as you have partition (dos/doze don't care) mkdosfs should format cleanly.

Check your block device is okay, ie you have the magnet under the stand still.

HeavyComponent 2010-06-28 00:58

Re: 16GB miniSD issue!!! HELP!
 
damion,

Ok I typed exactly what you typed and this is everything.

Code:

~ $ sudo gainroot
Root shell enabled


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # sfdisk -l /dev/mmcblk1

Disk /dev/mmcblk1: 486192 cylinders, 4 heads, 16 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
 /dev/mmcblk1: unrecognized partition table type
No partitions found
/home/user # file -s /dev'mmcblk1 
> file -s /dev'mmcblk1p1
/bin/sh: file: not found
/home/user # file -s /dev'mmcblk1p2
>

Quote:

Originally Posted by damion (Post 732066)
Check your block device is okay, ie you have the magnet under the stand still.

I have no idea what you're talking about when it comes to that. I just got my N900 last week...:confused:

stlpaul 2010-06-28 01:03

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by HeavyComponent (Post 731402)
In the list I've seen this at the end...

Driver 'sd' needs updating - please use bus_type methods

How do I get it updated?

It's a harmless and meaningless (to you) kernel warning, it happens on desktop machines too. It was fixed in newer kernels but N900 still uses old 2.6.28 which was first released in 2008.

HeavyComponent 2010-06-28 01:04

Re: 16GB miniSD issue!!! HELP!
 
stlpaul,

Yeah I googled it and read that off somewhere.

Thanks!

HeavyComponent 2010-06-28 02:30

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by darguzar (Post 732038)
i don't know if this is gona fix it or not but you can always try....

well i had to same problem but with a 8gb card and some other cell phone...

the thing was that the card format (Like it is basically FAT or FAT 16)

So for that try fromatting it but not on the phone or directly from the card reader by right clicking the drive icon and formatting it

Format it with Panasonic SD Formatter......

it might be available online for to download a very small but very effective software for formatting Memory cards...

I hope it solves the problem....

If you can't find the SD formatter email me...
darguzar@yahoo.com

I did what you said, I got the program from http://panasonic.jp/support/global/c...oad/index.html and I hope that's the right one.

After I formatted it using the program while the SD card was inserted in the N900 via PC though. I restarted my phone and made a copy of my videos into the SD card. It was working... THEN I would repeatedly play the videos off the SD card to make sure it would keep playing. That's when it started saying NO FILE FOUND. :(

So I'm back to the beginning with this issue...

I'm getting so tired of this! :mad::(

crail 2010-06-28 02:35

Re: 16GB miniSD issue!!! HELP!
 
scan and fix and check for bad sectors. have you done that??????

HeavyComponent 2010-06-28 07:39

Re: 16GB miniSD issue!!! HELP!
 
crail,

I've already answered your question on the previous page. I said yes and their was no bad sectors.

damion 2010-06-28 15:29

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by HeavyComponent (Post 732071)
damion,

Ok I typed exactly what you typed and this is everything.

Code:

~ $ sudo gainroot
Root shell enabled


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # sfdisk -l /dev/mmcblk1

Disk /dev/mmcblk1: 486192 cylinders, 4 heads, 16 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
 /dev/mmcblk1: unrecognized partition table type
No partitions found
/home/user # file -s /dev'mmcblk1 
> file -s /dev'mmcblk1p1
/bin/sh: file: not found
/home/user # file -s /dev'mmcblk1p2
>



I have no idea what you're talking about when it comes to that. I just got my N900 last week...:confused:

I guess I installed file from somewhere, however as we now see, you don't have any partitions. Try partitioning it in to a single partition and format that as fat32.

crail 2010-06-28 15:43

Re: 16GB miniSD issue!!! HELP!
 
you should have a warranty on the card if you bought it new. you should send it back

HeavyComponent 2010-06-28 19:37

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by damion (Post 732797)
I guess I installed file from somewhere, however as we now see, you don't have any partitions. Try partitioning it in to a single partition and format that as fat32.

I have no idea on how to do that. Like I said I'm new to all this stuff. Please explain...

Quote:

Originally Posted by crail (Post 732808)
you should have a warranty on the card if you bought it new. you should send it back

Like I said before the card is fine because it works on every other device I have with no issues. This is how I know it's the phone, I put a 4GB card in the phone and I got the same problems.That 4GB is in use with another phone with no problems. The phone is perfect just this memory card issue that I'm having.

woody14619 2010-06-28 21:01

Re: 16GB miniSD issue!!! HELP!
 
Try this, in a root terminal (this will format the card!). you should be able to cut/paste it right into a root terminal. (Be sure you're root first, via root or gainroot!)

Code:

sfdisk /dev/mmcblk1 <<EOF
,,c
EOF
sync
mkfs.vfat /dev/mmcblk1p1
sfdisk -d /dev/mmcblk1

That should show you've created a new partition, and formatted it to vfat.

HeavyComponent 2010-06-28 21:34

Re: 16GB miniSD issue!!! HELP!
 
woody14619,

Thanks for the reply, I will try right away and post back on the results.

HeavyComponent 2010-06-28 21:51

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by woody14619 (Post 733186)
Try this, in a root terminal (this will format the card!). you should be able to cut/paste it right into a root terminal. (Be sure you're root first, via root or gainroot!)

Code:

sfdisk /dev/mmcblk1 <<EOF
,,c
EOF
sync
mkfs.vfat /dev/mmcblk1p1
sfdisk -d /dev/mmcblk1

That should show you've created a new partition, and formatted it to vfat.

Before I continue this is what I got so far. I stopped after the 3rd line "EOF". This what showed up and I wanted to know is it safe to continue?

Code:

/home/user # sfdisk /dev/mmcblk1 <<EOF
> ,,c
> EOF
Checking that no-one is using this disk right now ...
BLKRRPART: Device or resource busy

This disk is currently in use - repartitioning is probably a bad idea.
Umount all file systems, and swapoff all swap partitions on this disk.
Use the --no-reread flag to suppress this check.
Use the --force flag to overrule all checks.
/home/user #

Now what?

woody14619 2010-06-28 22:04

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by HeavyComponent (Post 733249)
Before I continue this is what I got so far. I stopped after the 3rd line "EOF". This what showed up and I wanted to know is it safe to continue?

So it's mounted? That's really odd...

Try this (and again, be sure you are root!)

Code:

root
umount /dev/mmcblk1

That should unmount everything. They try this block again:

Code:

sfdisk /dev/mmcblk1 <<EOF
,,c
EOF
sync
mkfs.vfat /dev/mmcblk1p1
sfdisk -d /dev/mmcblk1

Worst case, use the --force flag, just make sure you're saying mmcblk1 and NOT mmcblk0! mmcblk0 is your internal OS!

HeavyComponent 2010-06-28 22:09

Re: 16GB miniSD issue!!! HELP!
 
woody14619,

Ok lets say I have to use the force flag. How do I do that?

EDIT: Tried the umount and this is what I got.

Code:

/home/user # umount /dev/mmcblk1
umount: cannot umount /dev/mmcblk1: Invalid argument
/home/user #


woody14619 2010-06-28 22:19

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by HeavyComponent (Post 733273)
woody14619,

Ok lets say I have to use the force flag. How do I do that?

EDIT: Tried the umount and this is what I got.

Code:

/home/user # umount /dev/mmcblk1
umount: cannot umount /dev/mmcblk1: Invalid argument
/home/user #


Just throw it into the command between sfdisk and the device name. :) I'm more concerned about the fact that it thinks it's in use. As root just try typing mount and see if it's listing anything for /dev/mmcblk1. If it is, try umounting that by name. (For example, it may have /dev/mmcblk1p1 mounted? But the previous command said it had no partitions, so...)

HeavyComponent 2010-06-28 22:26

Re: 16GB miniSD issue!!! HELP!
 
Ok woody14619,

At root just typed "mount".

Code:

/home/user # mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,bulk_read,no_chk_data_crc)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw,noatime,size=1024k)
tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=256k,mode=755)
none on /dev type tmpfs (rw,noatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k)
/dev/mmcblk0p2 on /home type ext3 (rw,noatime,errors=continue,commit=1,data=writeback)
/home/opt on /opt type none (bind)
nodev on /sys/kernel/debug type debugfs (0)
/opt/pymaemo/usr/lib/python2.5 on /usr/lib/python2.5 type bind (bind)
/opt/pymaemo/usr/share/pyshared on /usr/share/pyshared type bind (bind)
/opt/pymaemo/usr/lib/pyshared on /usr/lib/pyshared type bind (bind)
/opt/pymaemo/usr/share/python-support on /usr/share/python-support type bind (bind)
/opt/pymaemo/usr/lib/python-support on /usr/lib/python-support type bind (bind)
/dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir)
/dev/mmcblk1p1 on /media/mmc1 type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir)


fnordianslip 2010-06-28 22:32

Re: 16GB miniSD issue!!! HELP!
 
Isn't it mmcblk1p1 for the FAT32 partition on the uSDHC card on the N900?

If so, "umount /media/mmc1" as root, followed by the other stuff, as appropriate, should (probably) work.

Note that /dev/mmcblk1p1 is the first partition on /dev/mmcblk1 and /media/mmc1 is the directory it gets mounted to.

Edit: beer induced typo corrected for the benefit of humanity..

HeavyComponent 2010-06-28 22:36

Re: 16GB miniSD issue!!! HELP!
 
fnordianslip,

Did the "umount /media mmc1"

Code:

/home/user # umount /media mmc1
umount: cannot umount /media: Invalid argument
umount: cannot umount mmc1: No such file or directory
/home/user #


woody14619 2010-06-28 22:50

Re: 16GB miniSD issue!!! HELP!
 
Quote:

Originally Posted by HeavyComponent (Post 733293)
Ok woody14619,

At root just typed "mount".

Code:

/dev/mmcblk1p1 on /media/mmc1 type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir)

Hmm.. thats odd, since the sfdisk command output you showed bfore said it had no partitions on the device... Yet now it's saying it has a partition mounted. Well, this should do it for you:

Code:

umount /dev/mmcblk1p1
sfdisk /dev/mmcblk1 <<EOF
,,c
EOF
sync
mkfs.vfat /dev/mmcblk1p1
sync
sfdisk -d /dev/mmcblk1

The output the the last command should show you have a partition, formatted properly. Then a quick reboot (or open your back cover and replace it) and you should be all set.

fnordianslip 2010-06-28 22:50

Re: 16GB miniSD issue!!! HELP!
 
Aargh. Sorry. Been drinking :) Not helpfull, I know, but at least I'm trying ...

"umount /media/mmc1" should do it.


| 1   2   | Next
All times are GMT. The time now is 19:53.

vBulletin® Version 3.8.8