Nokia Phone: Plugged as Storage Media: Slack Cannot Mount Memory Card: Help
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Nokia Phone: Plugged as Storage Media: Slack Cannot Mount Memory Card: Help
DKU/USB cabled nokia to slack; chose option phone card treated as a Data Storage.
Used to have this automated or manually mounted before with newer models N6230i N70 N82 N96, but since I felt comfortable with the previous I downgraded back to my old N6230i, there was no issue, but I wonder cannot sync anymore today. I need help.
blah@blah--$: cat /proc/scsi/usb-storage/6
returned: Host scsi6: usb-storage
Vendor: Nokia
Product: Nokia 6230i
Serial Number: ###############
Protocol: Transparent SCSI
Transport: Bulk
Quirks:
I see this is good
---------------------------
blah@blah--$: /sbin/lsusb
returned:
Bus 002 Device 003: ID 04d9:1603 Holtek Semiconductor, Inc.
Bus 002 Device 002: ID 04f3:0210 Elan Microelectronics Corp. AM-400 Hama Optical Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 0421:0429 Nokia Mobile Phones 6230i MultiMedia Card
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
Bus 001 Device 006: ID 064e:c108 Suyin Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I see this is good.
---------------------------
blah@blah--$: /sbin/fdisk -l
returned: Device Boot Start End
/dev/sda1 1 2464
/dev/sda2 2465 6473
/dev/sda3 9450 18707
/dev/sda4 6474 9449
/dev/sda5 9451 17000
/dev/sda6 17217 18707
/dev/sda7 17001 17108
/dev/sda8
ONLY MY HARD DRIVE IS SEEN!
-----------------------------
I DID:
1.)
mount /dev/sdc /mnt/temp [no such device]
mount /dev/sdc1-2 /mnt/temp [no such device]
2.)
User blah, became member to Groups daemon, hald, messagebus, plugdev, cdrom, adm
blah@blah--$: /etc/rc.d/rc.messagebus restart reload (good)
blah@blah--$: /etc/rc.d/rc.hald restart (good)
STILL THE SAME, PHONE'S MEM CARD DID NOT MOUNT AUTOMATICALLY, AND HAS NO LEGITIMATE DEV NODE WHICH COULD BE MOUNTED TO A GOOD MOUNTING POINT.
HELP an old man.
Thanks.
BY THE WAY, The phone continues reporting on screen the following:
-- "Transferring Data....." (ad infinitum also..)
Could this be in the phone? But I have had good connections with this before in the same slack...
thanks ahead.
Last edited by malekmustaq; 08-07-2009 at 12:38 AM.
Reason: follow up data
I don't know what's wrong with your phone, but you won't be fixing *any* problems by being a member of the daemon, hald, or messagebus groups -- go back and revert those changes.
I have tested my Nokia 6300 cell phone with Ubuntu 9.04 Jaunty, via USB cable.
The three modes the phone supports and the corresponding results are:
(every mode works out of the box, no tweaks required)
1. Data Storage mode
Works as a regular flash drive. Rhythmbox captures the phone as a Media Player, can transfer music files to the phone within Rhythmbox, transparently converting music files to the MP4 format.
2. Printing And Media
The system recognises the phone as a digital camera, can import pictures to F-Spot.
3. Nokia mode
The system recognises the phone, and you can set up a broadband mobile internet connection through a wizard very easily. You just select your country and your provider, no advanced settings are required.
In the case of Nokia 6300 and Slackware 12.2 data storage mode doesn't work. The computer recognizes the mobile phone as sdb device...
Code:
usb 4-1: new full speed USB device using uhci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb 4-1: New USB device found, idVendor=0421, idProduct=04fa
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-1: Product: Nokia 6300
usb 4-1: Manufacturer: Nokia
usb 4-1: SerialNumber: 123451234512345
scsi 9:0:0:0: Direct-Access Nokia Nokia 6300 0000 PQ: 0
ANSI: 4
sd 9:0:0:0: [sdb] 3854337 512-byte hardware sectors (1973 MB)
sd 9:0:0:0: [sdb] Write Protect is off
sd 9:0:0:0: [sdb] 3854337 512-byte hardware sectors (1973 MB)
sd 9:0:0:0: [sdb] Write Protect is off
sdb:
sd 9:0:0:0: [sdb] Attached SCSI removable disk
sd 9:0:0:0: Attached scsi generic sg1 type 0
...but the mobile phone displays endlessly the message...
Code:
Transfering data
...the computer displays endlessly these messages...
...and there is no /dev/sdb* device in the system...
$ ls /dev/sd*
Code:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4
In that old thread: http://www.linuxquestions.org/questi...n-12.2-720287/ I reported that it's possible to mount device displaying similar messages. It works with USB flash drive but it doesn't work with the mobile phone, probably because it tries to send some data to the computer.
Connect both devices via a USB cable, it is the kind of cables furnished with digital cameras. A menu automatically pops up on the Nokia 6300, saying "USB data cable connected. Select mode.". Press "OK", a menu appears, proposing 3 USB cable modes. Choose "Data Storage". The phone will show a "USB mode: Data storage" screen, then a "Transferring data" progress bar, then again the "USB mode: Data storage" screen, which will stay until the end.
Unfortunately in the case of Slackware the phone stops at the ``Transfering data'' message.
***
In result I use to read and store data external card reader and adapter for micro SD card. Of course it's also possible to connect the mobile phone to the computer using Windows.
Yes you are correct: something is wrong, not with my phone, but with the Memory Card in it. I remember now that I have "formatted the memory card" within the phone command. I don't understand how Nokia could have implemented a different "formatting" effect. It was around this time that Slack and Mint can no longer auto sync with the "data storage mode" via usb. I gave up working under linux and plugged it to an old machine with an xp, Nokia PC Suite went well. Now probably I suspect Nokia "Format Mem" command had something to do that the mem card is no longer synced with linuxes: a vintage of proprietary stupidity within the product.
Yes it was silly messing with daemon groups, I only wanted to indulge my self momentarily the belief that DBus had nothing to do with the trouble. they are reverted promptly though.
----------------
w1k0:
Yes, it looks similar to my issue. Actually, until evidence proves otherwise, I am personally convinced that it is the post factory "Formatting" of the memory card that renders it unreadable to linuxes but Windows alone. But this is only an inference based on what a day's wasted time has shown me in fixing mine. I hope our free coders can come up a better solution someday.
----------------
Thank you very much my friend.
Last edited by malekmustaq; 08-08-2009 at 02:21 AM.
You just jogged my memory a *little* bit. It won't be enough to help you probably, but I seem to recall a discussion on LKML about some vendor's braindead "extension" or "modification" or "bastardization" of some filesystem format (probably vfat), and the result was memory cards that would not work in linux. Maybe that's enough information to at least point you in the right direction, assuming that's what you're running up against here.
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309
Rep:
I tested the above with 2 GB micro SD card I bought separately as well as with 512 MB micro SD card I bought with Nokia 6300. Both these cards work the same. I'm not sure whether original card has factory format because it could be modified by telephone company offering that model of mobile phone.
Really? that 2GB card you mean was "brand new" (not yet reformatted in your phone)? If that's the case then truly my suspicion is justified then, reading from Robby's post above: how vfat is "modified" to avoid linux detection.
Actually, when I issued "ls -a /dev" I discovered how the memory card created a "hidden node" named as "/dev/.tmp-storage-8:32" I said Voila! that's my card, I can read its Major and Minor numbers, pretty certain: my linux had it, but cannot actually sync any further. So I tried mknod an artificial node in a manner conceivable under linux parlance, bound or moved that hidden ./.tmp-storage-8:32 into my created node. But it did not work: the terminal hanged infinite. I tried renaming that hidden node into scsi or sdc, sdc1-15, still no avail, terminal hangs. I gave up since I noticed the problem is beyond a newbie's tampering.
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309
Rep:
rworkman inspired me to perform some tests...
According to fdisk original micro SD card hadn’t any partition. To mount it in the system I had to use mount /dev/sdd /mnt/tmp command...
$ fdisk -l /dev/sdd
Code:
Disk /dev/sdd: 510 MB, 510132224 bytes
16 heads, 61 sectors/track, 1020 cylinders
Units = cylinders of 976 * 512 = 499712 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
So I copied boot sector of the card to the file, inspected its contents, and found FAT16 flag...
$ dd if=/dev/sdd of=sdd.512.img bs=512 count=1
Code:
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.0259045 s, 19.8 kB/s
Then I wiped the card contents out with dd command...
$ dd if=/dev/zero of=/dev/sdd bs=512
Code:
dd: writing `/dev/sdd': No space left on device
996353+0 records in
996352+0 records out
510132224 bytes (510 MB) copied, 410.947 s, 1.2 MB/s
...made sdd1 partition type 6 (FAT16) on it...
$ fdisk /dev/sdd
Code:
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x355a592e.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1020, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-1020, default 1020):
Using default value 1020
Command (m for help): t
Selected partition 1
Hex code (type L to list codes): 6
Changed system type of partition 1 to 6 (FAT16)
Command (m for help): p
Disk /dev/sdd: 510 MB, 510132224 bytes
16 heads, 61 sectors/track, 1020 cylinders
Units = cylinders of 976 * 512 = 499712 bytes
Disk identifier: 0x355a592e
Device Boot Start End Blocks Id System
/dev/sdd1 1 1020 497729+ 6 FAT16
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.
...made FAT16 file system...
$ mkdosfs -F 16 /dev/sdd1
Code:
mkdosfs 2.11 (12 Mar 2005)
Mounted the partition and copied some files on it...
$ mount /dev/sdd1 /mnt/tmp
Next I put the card into the mobile phone and plugged it to the computer via USB.
The result was exactly the same as described above. It means that responsibility for the problem with the communication with the computer isn’t on the side of the card but on the side of the mobile phone.
ATTENTION: If you intend to perform these tests and restore at the end the original contents of the card prepare the copy of it with the command dd if=/dev/sdd of=sdd.orig.img bs=512. It isn’t enough to copy original files because Linux doesn’t recognize some characters and changes them to ?.
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309
Rep:
Quote:
Originally Posted by malekmustaq
w1k0:
Really? that 2GB card you mean was "brand new" (not yet reformatted in your phone)? If that's the case then truly my suspicion is justified then, reading from Robby's post above: how vfat is "modified" to avoid linux detection.
That card was brand new but after I bought it I inserted it into the mobile phone and formatted it. According to my above post I suspect the problem lies not on the card but on the mobile phone side.
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309
Rep:
Now I did similar test but I made on the card FAT32 partition (type b) and I formatted it with the command mkdosfs -F 32 /dev/sdd1. Surprisingly Nokia 6300 recognizes FAT32 partition as well. Unfortunately the problem with the communication with the computer persists.
Did you try gnokii? How did it respond? I have known that gnokii has compatibility with non-symbian nokia phones. I obtained from slackbuilds, installed, but I don't know why it doesn't succeed in my case. My suspicion remains with the card because I have had positive sessions before with the card same system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Nokia Phone: Plugged as Storage Media: Slack Cannot Mount Memory Card: Help
