Left Sd Cerd Slot Isn't Working

[pootle]

I went to use my Pandora this evening and had a weird problem- the left hand SD slot isn't being read and the right hand slot has been re designated as the left one.

To explain, the left slot is normally called mmcblk0p1 and the right one is mmcblk1p1.

As of tonight, the right slot is called mmcblk0p1 and when I load a card into the left slot the led flashes briefly but it can't be accessed, it doesn't show up in Thunar and it's not there when I try to connect by USB to my pc.

I have tried different cards with no luck, they work in the right slot (as if it were the left one) but don't register in the left one itself.

Because of this I can't reflash. There's no SD1 to boot from!

I've tried taking the battery out but no joy.

Does anyone have any ideas?

It seems like the left slot has just broken but I would like to try anything to avoid sending the Pandora back for repair.

Thanks!

 

[WizardStan]

How did you try to reflash? Holding R while booting? And no SD card option there? If that's the case, then this would appear to be an unfortunate hardware issue, first I've heard of. An RMA may be your only hope.

 

[pootle]

And no SD card option there?

That's it exactly.

It just seems strange that the access led flashes when I insert a card.

Something is obviously happening in there, even though it's like the slot isn't assigned a name so it can't be accessed.

That made me hope that there might be a software solution.

Thanks again for the help!

 

[lomaxx]

About the "mmcblk"-confusion: That's nothing weird but totally normal. Despite what many people think (and what i thought for quite some time) mmcblk0 and mmcblk1 do NOT refer to the left and right slot, but to the card which was inserted first and second. Someone who boots from the left slot (as you only can boot from that one) will always see the left slot as mmcblk0. The right slot in that case will always be mmcblk1. But with two working slots, if you boot from NAND and insert a card into the right slot first, then the partitions on that card will be called mmcblk0p1 (...p2,....p3,...). The wiki mentions this somewhere too. You have to be careful while using tools like fdisk. You can easily delete the content of the wrong card if you misunderstand that.

As for your slot-problem: I don't have a really helpful hint. You said you tried to leave the battery out. But for how long? Maybe leave it out for a little longer? Did you try to blow air into the left slot? Maybe some dust is the problem, though unlikely. You could boot from NAND, open a terminal, type "dmesg" and see if something is mentioned there. However even if you find a message regarding the slot there, I don't see how it would help.

 

[pootle]

What is it they say? Every day's a schoolday!

Thanks for the info about card naming, that clears up one mystery.

I still have no idea what happened to the slot though. I left the battery out overnight, and I tried air but no luck.

I will send off an RMA email next week.

If anyone is reading this who doesn't have their Pandora yet, don't be put off by people having some build quality issues! After all, you only hear about it when somebody has a problem. The Pandora is a fantastic device, that's why it's such a wrench for me to send it away for repair.

 

[WizardStan]

It does seem strange. The access LED is software controlled, so the hardware is detecting something and telling the kernel to try and scan it. Something not quite adding up.
With a card in just the left slot, typing "ls -l /dev/mmcblk*" in a terminal, what do you get? What if the card is just in the right slot? And again if you have a card in both slots?
Can you paste the output of "dmesg" here, after inserting a card into the left slot?

 

[relliker]

If anyone is reading this who doesn't have their Pandora yet, don't be put off by people having some build quality issues! After all, you only hear about it when somebody has a problem. The Pandora is a fantastic device, that's why it's such a wrench for me to send it away for repair.

You're absolutely right! My Pandora developed the purple tint'o'death and I preferred ordering the cable and changing it myself than sending back the Pandora. I lived with the tint and a gazillion scrolling coloured lines until I got the cable and then repaired it using ED's video (which was so well explained that I fixed it in around 20 mins). Hehe, the only thing is that now the screen lid has some scratches as it was a devil to get open but at least the Pandora never left my hands and I kept using it everyday. Now, if it was a psp or nds within warranty I'd be bitching for a free repair like crazy but the Pandora is too special for me to complain about. It's the most useful portable computer I ever had more so than my old Clie (which I sometimes still use even after more than 6 years btw!) One last thing. I was never ever a gamer before in my life but with the Pandora I've been transformed into at least a casual gamer and have been romming my daughter's PSX1 games to play on it (and Frogatto, damn, I'm hooked). Wow, Wow, WOW! The Pandora's beauty is in the eyes of the beholder and I'm a beholder. I hope you get it back in working order asap. It's too cool not to have

 

[Chaser]

+1 to those sentiments. I held off PTOD rma for as long as possible, nub death etc. The Pandora just has such a feature rich control set, that you can somehow still not wrest yourself to part with her and the game catalogue and other general PC uses just keeps getting stronger. A lovely machine despite all the issues that have plagued the team so far. Here's to brighter things in the future, an established brand and a freaking powerhouse of a sequel machine that firmly carves a swathe into the big corps markets oneday and shows firmly, that open source and yours to do with as you wish, is the only acceptable future for handhelds.

 

[EvilDragon]

The thing about /dev/mmcblk0 is not surprising. The first SD card inserted into a slot is ALWAYS /dev/mmcblk0, regardless whether this is the left or right slot.

If an SD Card slot stops reading cards properly it might need some cleaning.
I had that issue on my old GP2X, my WIZ and also one time on my Pandora.

I use an old SD Card for that, put some contact cleaner spray onto the contacts, insert and remove it into the slot a few times, and after that, it usually starts working again without any issues.

 

[pootle]

Thanks again for all the help everyone and apologies for the delay in answering, it's been one of those weeks and I haven't had a chance.

I've tried contact cleaner with no luck I'm afraid.

The output of dmesg, with a card in the left slot, is as follows

Spoiler

openpandora:~/Desktop$ dmesg
9.633605] musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine (X), bulk split (X), HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[ 9.633636] musb_hdrc: MHDRC RTL version 1.400
[ 9.633636] musb_hdrc: setup fifo_mode 4
[ 9.633697] musb_hdrc: 29/31 max ep, 15424/16384 memory
[ 9.633728] musb_hdrc: hw_ep 0shared, max 64
[ 9.633728] musb_hdrc: hw_ep 1tx, max 512
[ 9.633758] musb_hdrc: hw_ep 1rx, max 512
[ 9.633758] musb_hdrc: hw_ep 2tx, max 512
[ 9.633758] musb_hdrc: hw_ep 2rx, max 512
[ 9.633789] musb_hdrc: hw_ep 3tx, max 512
[ 9.633789] musb_hdrc: hw_ep 3rx, max 512
[ 9.633819] musb_hdrc: hw_ep 4tx, max 512
[ 9.633819] musb_hdrc: hw_ep 4rx, max 512
[ 9.633850] musb_hdrc: hw_ep 5tx, max 512
[ 9.633850] musb_hdrc: hw_ep 5rx, max 512
[ 9.633850] musb_hdrc: hw_ep 6tx, max 512
[ 9.633880] musb_hdrc: hw_ep 6rx, max 512
[ 9.633880] musb_hdrc: hw_ep 7tx, max 512
[ 9.633911] musb_hdrc: hw_ep 7rx, max 512
[ 9.633911] musb_hdrc: hw_ep 8tx, max 512
[ 9.633941] musb_hdrc: hw_ep 8rx, max 512
[ 9.633941] musb_hdrc: hw_ep 9tx, max 512
[ 9.633972] musb_hdrc: hw_ep 9rx, max 512
[ 9.633972] musb_hdrc: hw_ep 10tx, max 512
[ 9.633972] musb_hdrc: hw_ep 10rx, max 512
[ 9.634002] musb_hdrc: hw_ep 11tx, max 512
[ 9.634002] musb_hdrc: hw_ep 11rx, max 512
[ 9.634033] musb_hdrc: hw_ep 12tx, max 512
[ 9.634033] musb_hdrc: hw_ep 12rx, max 512
[ 9.634063] musb_hdrc: hw_ep 13tx, max 512
[ 9.634063] musb_hdrc: hw_ep 13rx, max 512
[ 9.634063] musb_hdrc: hw_ep 14shared, max 1024
[ 9.634094] musb_hdrc: hw_ep 15shared, max 1024
[ 9.634124] musb_hdrc: USB OTG mode controller at d80ab000 using PIO, IRQ 92
[ 9.653289] Bluetooth: Core ver 2.13
[ 9.653594] NET: Registered protocol family 31
[ 9.653594] Bluetooth: HCI device and connection manager initialized
[ 9.653625] Bluetooth: HCI socket layer initialized
[ 9.655059] NET: Registered protocol family 2
[ 9.660736] Switched to high resolution mode on CPU 0
[ 9.723388] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 9.723968] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 9.724182] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 9.724334] TCP: Hash tables configured (established 8192 bind 8192)
[ 9.724334] TCP reno registered
[ 9.746826] NET: Registered protocol family 1
[ 9.747558] NetWinder Floating Point Emulator V0.97 (double precision)
[ 9.749206] VFS: Disk quotas dquot_6.5.1
[ 9.749298] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 9.749877] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 9.752014] aufs 2-27
[ 9.752075] msgmni has been set to 485
[ 9.752319] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 9.752349] io scheduler noop registered
[ 9.752380] io scheduler anticipatory registered (default)
[ 9.752380] io scheduler deadline registered
[ 9.752532] io scheduler cfq registered
[ 9.762878] Serial: 8250/16550 driver4 ports, IRQ sharing enabled
[ 9.783416] serial8250.0: ttyS0 at MMIO 0x49020000 (irq = 74) is a ST16654
[ 9.783477] console [ttyS0] enabled
[ 10.228332] brd: module loaded
[ 10.233703] loop: module loaded
[ 10.237060] set_opp: OPP 3 set
[ 10.240203] pndctrl loaded.
[ 10.243133] usbcore: registered new interface driver asix
[ 10.248687] usbcore: registered new interface driver cdc_ether
[ 10.254669] usbcore: registered new interface driver rndis_host
[ 10.260681] i2c /dev entries driver
[ 10.265228] input: power-button as /devices/virtual/input/input0
[ 10.293670] triton2 power button driver initialized
[ 10.299774] Driver 'sd' needs updating - please use bus_type methods
[ 10.306365] omap2-nand driver initializing
[ 10.311645] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V 16-bit)
[ 10.320800] cmdlinepart partition parsing not available
[ 10.326110] Creating 5 MTD partitions on "omap2-nand":
[ 10.331268] 0x00000000-0x00080000 : "xloader"
[ 10.336242] 0x00080000-0x00260000 : "uboot"
[ 10.341461] 0x00260000-0x00280000 : "uboot-env"
[ 10.346252] 0x00280000-0x00c80000 : "boot"
[ 10.354675] 0x00c80000-0x20000000 : "rootfs"
[ 10.562744] UBI: attaching mtd4 to ubi0
[ 10.566619] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 10.572937] UBI: logical eraseblock size: 129024 bytes
[ 10.578399] UBI: smallest flash I/O unit: 2048
[ 10.583160] UBI: sub-page size: 512
[ 10.587799] UBI: VID header offset: 512 (aligned 512)
[ 10.593688] UBI: data offset: 2048
[ 11.835266] UBI: attached mtd4 to ubi0
[ 11.839050] UBI: MTD device name: "rootfs"
[ 11.844177] UBI: MTD device size: 499 MiB
[ 11.849212] UBI: number of good PEBs: 3995
[ 11.853942] UBI: number of bad PEBs: 1
[ 11.858428] UBI: max. allowed volumes: 128
[ 11.863067] UBI: wear-leveling threshold: 4096
[ 11.867828] UBI: number of internal volumes: 1
[ 11.872314] UBI: number of user volumes: 1
[ 11.876770] UBI: available PEBs: 0
[ 11.881256] UBI: total number of reserved PEBs: 3995
[ 11.886260] UBI: number of PEBs reserved for bad PEB handling: 39
[ 11.892395] UBI: max/mean erase counter: 2/0
[ 11.896728] UBI: image sequence number: 427648896
[ 11.901489] UBI: attaching mtd3 to ubi1
[ 11.905395] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 11.911712] UBI: logical eraseblock size: 129024 bytes
[ 11.917144] UBI: smallest flash I/O unit: 2048
[ 11.921905] UBI: sub-page size: 512
[ 11.926544] UBI: VID header offset: 512 (aligned 512)
[ 11.932434] UBI: data offset: 2048
[ 11.939270] UBI: background thread "ubi_bgt0d" started, PID 29
[ 11.981475] UBI: attached mtd3 to ubi1
[ 11.985260] UBI: MTD device name: "boot"
[ 11.990203] UBI: MTD device size: 10 MiB
[ 11.995117] UBI: number of good PEBs: 80
[ 11.999694] UBI: number of bad PEBs: 0
[ 12.004150] UBI: max. allowed volumes: 128
[ 12.008819] UBI: wear-leveling threshold: 4096
[ 12.013580] UBI: number of internal volumes: 1
[ 12.018035] UBI: number of user volumes: 1
[ 12.022521] UBI: available PEBs: 0
[ 12.027008] UBI: total number of reserved PEBs: 80
[ 12.031829] UBI: number of PEBs reserved for bad PEB handling: 2
[ 12.037902] UBI: max/mean erase counter: 6/3
[ 12.042205] UBI: image sequence number: 1774125323
[ 12.047058] usbmon: debugfs is not available
[ 12.051757] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[ 12.057708] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
[ 12.065521] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
[ 12.071258] UBI: background thread "ubi_bgt1d" started, PID 30
[ 12.082641] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[ 12.090667] usb usb1: configuration #1 chosen from 1 choice
[ 12.096435] hub 1-0:1.0: USB hub found
[ 12.100341] hub 1-0:1.0: 3 ports detected
[ 12.208251] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 12.215087] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 12.222412] usb usb1: Product: OMAP-EHCI Host Controller
[ 12.227783] usb usb1: Manufacturer: Linux 2.6.27.46-omap1 ehci_hcd
[ 12.234008] usb usb1: SerialNumber: ehci-omap.0
[ 12.238677] Initializing USB Mass Storage driver...
[ 12.243743] usbcore: registered new interface driver usb-storage
[ 12.249816] USB Mass Storage support registered.
[ 12.254577] usbcore: registered new interface driver libusual
[ 12.260620] mice: PS/2 mouse device common for all mice
[ 12.286376] input: gpio-keys as /devices/platform/gpio-keys/input/input1
[ 12.356597] input: keypad as /devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-004a/twl4030_keypad/input/input2
[ 12.412231] input: nub0 as /devices/platform/i2c_omap.3/i2c-adapter/i2c-3/3-0066/input/input3
[ 12.465911] input: nub1 as /devices/platform/i2c_omap.3/i2c-adapter/i2c-3/3-0067/input/input4
[ 12.520599] twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
[ 12.530944] bq27x00-battery 3-0055: support ver. 1.1.0 enabled
[ 12.536926] Bluetooth: HCI UART driver ver 2.2
[ 12.541412] Bluetooth: HCI H4 protocol initialized
[ 12.546234] Bluetooth: HCILL protocol initialized
[ 12.551025] hci_h4p hci_h4p: Registering HCI H4P device
[ 12.708099] mmci-omap mmci-omap.0: Failed to get debounce clock
[ 12.817077] mmci-omap mmci-omap.1: Failed to get debounce clock
[ 12.818206] mmci-omap mmci-omap.2: Failed to get debounce clock
[ 12.818603] Registered led device: pandora::sd1
[ 12.823272] Registered led device: pandora::sd2
[ 12.827972] Registered led device: pandora::bluetooth
[ 12.833190] Registered led device: pandora::wifi
[ 12.838165] Registered led device: pandora::keypad_bl
[ 12.843475] Registered led device: pandora:ower
[ 12.848571] Registered led device: pandora::charger
[ 12.853668] usbcore: registered new interface driver usbhid
[ 12.859344] usbhid: v2.6:USB HID core driver
[ 12.863861] Advanced Linux Sound Architecture Driver Version 1.0.17.
[ 12.870483] ASoC version 0.13.2
[ 12.873809] OMAP3 Pandora SoC init
[ 12.877410] TWL4030 Audio Codec init
[ 12.882690] asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
[ 12.889617] asoc: twl4030 <-> omap-mcbsp-dai-1 mapping ok
[ 12.902648] ALSA device list:
[ 12.905700] #0: omap3pandora (twl4030)
[ 12.909912] TCP cubic registered
[ 12.913208] NET: Registered protocol family 17
[ 12.917724] NET: Registered protocol family 15
[ 12.922241] Bluetooth: L2CAP ver 2.11
[ 12.925933] Bluetooth: L2CAP socket layer initialized
[ 12.931060] Bluetooth: SCO (Voice Link) ver 0.6
[ 12.935638] Bluetooth: SCO socket layer initialized
[ 12.940734] Bluetooth: RFCOMM socket layer initialized
[ 12.945983] Bluetooth: RFCOMM TTY layer initialized
[ 12.950927] Bluetooth: RFCOMM ver 1.10
[ 12.954681] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 12.960052] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 12.966583] RPC: Registered udp transport module.
[ 12.971313] RPC: Registered tcp transport module.
[ 12.976135] ThumbEE CPU extension supported.
[ 12.980438] Disabling unused clock "sr2_fck"
[ 12.980468] Disabling unused clock "sr1_fck"
[ 12.980499] Disabling unused clock "mcbsp_fck"
[ 12.980499] Disabling unused clock "mcbsp_fck"
[ 12.980499] Disabling unused clock "mcbsp_fck"
[ 12.980529] Disabling unused clock "mcbsp_ick"
[ 12.980529] Disabling unused clock "mcbsp_ick"
[ 12.980560] Disabling unused clock "mcbsp_ick"
[ 12.980560] Disabling unused clock "gpt2_ick"
[ 12.980590] Disabling unused clock "gpt3_ick"
[ 12.980590] Disabling unused clock "gpt4_ick"
[ 12.980621] Disabling unused clock "gpt5_ick"
[ 12.980621] Disabling unused clock "gpt6_ick"
[ 12.980651] Disabling unused clock "gpt7_ick"
[ 12.980651] Disabling unused clock "gpt8_ick"
[ 12.980651] Disabling unused clock "gpt9_ick"
[ 12.980682] Disabling unused clock "wdt3_ick"
[ 12.980682] Disabling unused clock "wdt3_fck"
[ 12.980712] Disabling unused clock "gpio2_dbck"
[ 12.980712] Disabling unused clock "gpio3_dbck"
[ 12.980743] Disabling unused clock "gpio5_dbck"
[ 12.980773] Disabling unused clock "gpt9_fck"
[ 12.980773] Disabling unused clock "gpt8_fck"
[ 12.980804] Disabling unused clock "gpt7_fck"
[ 12.980804] Disabling unused clock "gpt6_fck"
[ 12.980834] Disabling unused clock "gpt5_fck"
[ 12.980834] Disabling unused clock "gpt4_fck"
[ 12.980865] Disabling unused clock "gpt3_fck"
[ 12.980865] Disabling unused clock "gpt2_fck"
[ 12.980865] Disabling unused clock "gpt1_ick"
[ 12.980895] Disabling unused clock "wdt1_ick"
[ 12.980895] Disabling unused clock "wdt2_ick"
[ 12.980926] Disabling unused clock "wdt2_fck"
[ 12.980926] Disabling unused clock "gpio1_dbck"
[ 12.980957] Disabling unused clock "gpt1_fck"
[ 12.980957] Disabling unused clock "cam_ick"
[ 12.980987] Disabling unused clock "cam_mclk"
[ 12.980987] Disabling unused clock "des1_ick"
[ 12.980987] Disabling unused clock "sha11_ick"
[ 12.981048] Disabling unused clock "rng_ick"
[ 12.981048] Disabling unused clock "aes1_ick"
[ 12.981079] Disabling unused clock "ssi_ick"
[ 12.981079] Disabling unused clock "mailboxes_ick"
[ 12.981109] Disabling unused clock "mcbsp_ick"
[ 12.981109] Disabling unused clock "mcbsp_ick"
[ 12.981140] Disabling unused clock "gpt10_ick"
[ 12.981140] Disabling unused clock "gpt11_ick"
[ 12.981170] Disabling unused clock "uart2_ick"
[ 12.981170] Disabling unused clock "i2c_ick"
[ 12.981170] Disabling unused clock "hdq_ick"
[ 12.981201] Disabling unused clock "mspro_ick"
[ 12.981201] Disabling unused clock "des2_ick"
[ 12.981231] Disabling unused clock "sha12_ick"
[ 12.981231] Disabling unused clock "aes2_ick"
[ 12.981262] Disabling unused clock "icr_ick"
[ 12.981262] Disabling unused clock "pka_ick"
[ 12.981292] Disabling unused clock "ssi_ssr_fck"
[ 12.981292] Disabling unused clock "hdq_fck"
[ 12.981292] Disabling unused clock "uart2_fck"
[ 12.981323] Disabling unused clock "mcbsp_fck"
[ 12.981323] Disabling unused clock "mcbsp_fck"
[ 12.981353] Disabling unused clock "i2c_fck"
[ 12.981353] Disabling unused clock "mspro_fck"
[ 12.981384] Disabling unused clock "gpt11_fck"
[ 12.981384] Disabling unused clock "gpt10_fck"
[ 12.981414] Disabling unused clock "iva2_ck"
[ 12.981414] Disabling unused clock "dpll4_m6x2_ck"
[ 12.981445] Disabling unused clock "dpll4_m5x2_ck"
[ 12.981445] Disabling unused clock "dpll3_m3x2_ck"
[ 12.981475] Disabling unused clock "sys_clkout1"
[ 12.981506] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
[ 13.020599] Console: switching to colour frame buffer device 100x30
[ 13.209838] twl4030_rtc twl4030_rtc: setting system clock to 2011-09-12 18:16:40 UTC (1315851400)
[ 13.339019] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 13.345153] UBIFS: file system size: 508483584 bytes (496566 KiB, 484 MiB, 3941 LEBs)
[ 13.353240] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[ 13.360595] UBIFS: media format: w4/r0 (latest is w4/r0)
[ 13.366485] UBIFS: default compressor: lzo
[ 13.370605] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 13.377319] VFS: Mounted root (ubifs filesystem).
[ 13.382232] Freeing init memory: 148K
[ 21.453613] ads7846 spi1.0: touchscreen, irq 254
[ 21.459045] input: touchscreen as /devices/platform/omap2_mcspi.1/spi1.0/input/input5
[ 25.117034] NET: Registered protocol family 10
[ 25.353454] UBIFS: mounted UBI device 1, volume 0, name "boot"
[ 25.359405] UBIFS: file system size: 8386560 bytes (8190 KiB, 7 MiB, 65 LEBs)
[ 25.366790] UBIFS: journal size: 1032193 bytes (1008 KiB, 0 MiB, 6 LEBs)
[ 25.374084] UBIFS: media format: w4/r0 (latest is w4/r0)
[ 25.379974] UBIFS: default compressor: lzo
[ 25.384094] UBIFS: reserved for root: 396117 bytes (386 KiB)
[ 26.223236] dpll1_ck rate: 600000000
[ 26.226898] arm_fck rate: 600000000
[ 26.230499] PLL_MPU rate: 600000000
[ 26.294097] input: nub0 as /devices/platform/i2c_omap.3/i2c-adapter/i2c-3/3-0066/input/input6
[ 26.520721] input: nub1 as /devices/platform/i2c_omap.3/i2c-adapter/i2c-3/3-0067/input/input7

And when I try ls-l as above I get "No such file or directory" with either card in. That said, my knowledge of linux is limited at best so there's every chance I've done something wrong.

Any ideas on things I could try so I won't have to give in and send my Pandora back will be gratefully received.

That's 2 weeks I've been avoiding it so far!

 

[lomaxx]

And when I try ls-l as above I get "No such file or directory" with either card in. That said, my knowledge of linux is limited at best so there's every chance I've done something wrong.

The command is not "ls-l" but "ls -l" with a space between "ls" and "-l". To be more precise: "ls" is the command that lists the content of a directory or some information about the specified files. And "-l" is a so called parameter. When you use "-l" you get the "long list output" with more details about each file.

Anyway this all seems to be in vain. The only thing I could think of that might help is EvilDragons hint about the contact cleaner spray.