Help - Search - Members - Calendar
Full Version: Cf Card / Microdrive Switched...
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
Alfinfrance
Hi,

I've got this strange problem on my SL-C3100 :

In PdaXrom v 1.1.0beta4 and 1.1.0r121, when I click on the Card utility, I see my Hitachi Microdrive and the SD Card. Can't see the CF Card.

I read that it was due to some error in flashing with a CF card inserted.

So I tried to flash back to Trisoft Sharp Rom.

In this rom, no problem, SD and CF are detected well.

I tried PdaXrom 1.1.0beta3 : also no problem.

But each time I go back to a beta4 or r121, the problem occures ( and I only flash with an SD Card ).

Could someone please help?
Capn_Fish
It's a bug. sad.gif
Alfinfrance
Ok.

And no way to correct it?
Capn_Fish
If it's unmounting /dev/hda, you may be able to do a pccardclt eject 1 and a pccardctl eject 0, then reinsert the CF card (pccardctl insert 0/1, whichever is CF. You can check with pccardctl ident 0/1 to see what either card is) first (so it becomes /dev/hdax), then the microdrive.

This is completely untested, but let me know how it goes.
speculatrix
tried rebooting with the card not inserted?
Alfinfrance
speculatrix : of course I did all the next flash without any CF Card inserted. And, to test, I also tried with a CF Card inserted, that doesn't change anything.

QUOTE
If it's unmounting /dev/hda, you may be able to do a pccardclt eject 1 and a pccardctl eject 0, then reinsert the CF card (pccardctl insert 0/1, whichever is CF. You can check with pccardctl ident 0/1 to see what either card is) first (so it becomes /dev/hdax), then the microdrive.

This is completely untested, but let me know how it goes.


when I do pccardctl eject 0, Microdrive disappeare. Then, I do pccardctl insert 1 but CF is still not mounting in the control applet. And, when I do pccardctl insert 0, Microdrive is back in the applet.

Any way to switch 0 and 1 when both ejected?

Just forgot to say, I have this problem for months now ( still 1.1.0beta4 ) and I went back to 1.10beta3, but I'd like to have a 2.6 kernel fine working ( graphics are so much faster ).
Capn_Fish
I was hoping that the applet would be unmounting a device, and by switching the order in which you "inserted" the drives, you would also switch their device and so the other would be unmounted by the applet.

As a workaround, you could make a script to unmount the CF card and make a .desktop file for the script. From there you could put it in the system tray and have basically the same thing.
speculatrix
if this only happens with the new OS installed, try changing the order of loading kernel modules?

can either mangle by hand the modules config files, or manually - unmount the file systems manually (check that it works), kill the card manager process, lsmod to find the list of kernel modules, rmmod the appropriate kernel modules, then modprobe the modules in a different order before starting card manager and "cardctl insert" to load the cards!
Alfinfrance
So, I see where the problem comes from :

My Microdrive is /dev/hda and /dev/hda1 is mounted in /mnt/cf.

I tried to change it in fstab but it doesn't change anything ( I was sure of it before testing, but I give a try to any solution right now ).

Perhaps is there something to change in init files ( I clearly see the Microdrive is created as hda).
Alfinfrance
QUOTE
if this only happens with the new OS installed, try changing the order of loading kernel modules?

can either mangle by hand the modules config files, or manually - unmount the file systems manually (check that it works), kill the card manager process, lsmod to find the list of kernel modules, rmmod the appropriate kernel modules, then modprobe the modules in a different order before starting card manager and "cardctl insert" to load the cards!


Ok, but... where is the module that manage my drive? I did an lsmod and :

CODE
mousedev
rfcomm
l2cap
bluetooth
joydev
ipv6
lots of snd
pxaficp_ir
irda


Nothing seems to be a module for microdrive. ( sorry, I'm just some kind of user, perhaps it is stupid and there is another way to fond it ).
Meanie
QUOTE(Alfinfrance @ Mar 7 2007, 08:55 AM)
QUOTE
if this only happens with the new OS installed, try changing the order of loading kernel modules?

can either mangle by hand the modules config files, or manually - unmount the file systems manually (check that it works), kill the card manager process, lsmod to find the list of kernel modules, rmmod the appropriate kernel modules, then modprobe the modules in a different order before starting card manager and "cardctl insert" to load the cards!


Ok, but... where is the module that manage my drive? I did an lsmod and :

CODE
mousedev
rfcomm
l2cap
bluetooth
joydev
ipv6
lots of snd
pxaficp_ir
irda


Nothing seems to be a module for microdrive. ( sorry, I'm just some kind of user, perhaps it is stupid and there is another way to fond it ).
*



it's probably a bug in udev config...
Alfinfrance
Could somone please post what is the result when typing ./ide-devfs.sh in /etc/udev/scripts ?

I have :

CODE
ide/host-1/bus1/target/lun0/part discs/disc-1/part


if it works as I think, lun must be 2, like in a SCSI chain...
radiochickenwax
QUOTE(Alfinfrance @ Mar 6 2007, 11:23 PM)
Could somone please post what is the result when typing ./ide-devfs.sh in /etc/udev/scripts ?

I have :

CODE
ide/host-1/bus1/target/lun0/part discs/disc-1/part


if it works as I think, lun must be 2, like in a SCSI chain...
*



Same as you, This gives me:

ide/host-1/bus1/targe/lun0/part discs/disc-1/part





QUOTE(Alfinfrance @ Mar 6 2007, 09:11 PM)
Hi,

I've got this strange problem on my SL-C3100 :

In PdaXrom v 1.1.0beta4 and 1.1.0r121, when I click on the Card utility, I see my Hitachi Microdrive and the SD Card. Can't see the CF Card.

I read that it was due to some error in flashing with a CF card inserted.

So I tried to flash back to Trisoft Sharp Rom.

In this rom, no problem, SD and CF are detected well.

I tried PdaXrom 1.1.0beta3 : also no problem.

But each time I go back to a beta4 or r121, the problem occures ( and I only flash with an SD Card ).

Could someone please help?
*



QUOTE(Alfinfrance @ Mar 6 2007, 10:49 PM)
So, I see where the problem comes from :

My Microdrive is /dev/hda and /dev/hda1 is mounted in /mnt/cf.

I tried to change it in fstab but it doesn't change anything ( I was sure of it before testing, but I give a try to any solution right now ).

Perhaps is there something to change in init files ( I clearly see the Microdrive is created as hda).
*



If I'm understanding this correctly, you're not able to mount the external CF cards at all? I don't have this problem on the 3200 in pdax >= r121.

If booting with an external CF in the slot, the external CF consistently is recognized for me as /dev/hdc. whereas the internal CF is /dev/hda.

I only have one partition on my external CF card, so fstab just mounts /dev/hdc1 to /mnt/cf.

I have three partitions on the internal CF:

1. swap : /dev/hda1
2. vfat : /dev/hda2
3. ext2 : /dev/hda3




which are set as follows in /etc/fstab.


CODE
/dev/hdc1   /mnt/cf   auto   noauto,ownder   0  0
/dev/hda2   /data   auto   noauto,ownder   0  0
/dev/hda3   /share   auto   noauto,ownder   0  0




Prior to the altered fstab file, I had the same problems that I think you're speaking of. But you did try this and it didn't work? Is this the same for all 3100s? Does "dmesg" show anything upon the insert of the card?
Alfinfrance
And when I do a pccardctl, my microdrive is recognized as device 0 and CF as device 1. I think you should have CF as device 0 and microdrive has device 1, don't you?

And I don't have the slightest idea how to switch it.
radiochickenwax
QUOTE(Alfinfrance @ Mar 6 2007, 11:42 PM)
And when I do a pccardctl, my microdrive is recognized as device 0 and CF as device 1. I think you should have CF as device 0 and microdrive has device 1, don't you?

And I don't have the slightest idea how to switch it.
*



I'm sorry, I don't quite understand the question. My understanding is that the devices are recognized differently as /dev/hdc and /dev/hda. I haven't really used the 'pccardctl'.

I just use 'dmesg' to tell me when the bus has changed. Perhaps it's not as elegant, but it's worked for me thus far.
Meanie
QUOTE(Alfinfrance @ Mar 7 2007, 09:42 AM)
And when I do a pccardctl, my microdrive is recognized as device 0 and CF as device 1. I think you should have CF as device 0 and microdrive has device 1, don't you?

And I don't have the slightest idea how to switch it.
*


recompile the kernel with those values in the correct order smile.gif
Alfinfrance
Not sure it will work anyway... And it's a long way. Don't forget that even if I flash back to Sharp Rom and after go back to beta4 or r121 the problem is still there...

Is there a part of the memory which isn't reset when installing U-boot?

If so, how could I reset it? I expect not to erase base datas of my zaurus...

I tried all reset options in the D+M menu and haven't found anything making it work after...
desertrat
QUOTE(Alfinfrance @ Mar 6 2007, 11:42 PM)
And when I do a pccardctl, my microdrive is recognized as device 0 and CF as device 1. I think you should have CF as device 0 and microdrive has device 1, don't you?

This is for beta3 and older (not sure whether it any different for beta4 etc) -> when you boot with a CF inserted then CF becomes device 0 and microdrive is device 1.

a) do you observe any difference in the device numbers when you boot with and without CF?

b) what does "fdisk -l" show when you boot with and without CF?

c) are you able to mount the CF manually?
Alfinfrance
For pdaxrom beta4 and r121

a ) no. That's why I tried to reflash with and without CF Card

b )

/dev/hda1 1 20 10048+ 83 Linux
/dev/hda2 21 40 10080 83 Linux
/dev/hda3 41 7936 3979584 c W95 FAT32 (LBA)

and, with a CF inserted at boot, just add :

/dev/hdc1 1 992 49936+ 6 FAT16

pccardctl status (without CF inserted)

Socket 0:
3.3V 16-bit PC-Card
Subdevice 0 (function 0) bound to driver "ide-cs"
Socket 1:
no card

c ) I can mount the CF Card manually

For beta3

b )

/dev/hda1 1 20 10048+ 83 Linux
/dev/hda2 21 40 10080 83 Linux
/dev/hda3 41 7936 3979584 c W95 FAT32 (LBA)

and, with a CF inserted at boot:

/dev/hdc1 1 20 10048+ 83 Linux
/dev/hdc2 21 40 10080 83 Linux
/dev/hdc3 41 7936 3979584 c W95 FAT32 (LBA)

/dev/hda1 1 992 499936+ 6 FAT16

cardctl status (without CF inserted)

Socket 0:
no card
Socket 1:
3.3V 16-bit PC-Card
function 0: [ready], [bat dead], [bat low]

For Sharp Rom :


So, as I thought, there is a problem between cardctl and pccardctl. Even if microdrive is detected as hda also in beta3 when I boot without CF...

Sharp Rom : CF inserted or not :

b )

/dev/hda1 1 20 10048+ 83 Linux
/dev/hda2 21 40 10080 83 Linux
/dev/hda3 41 7936 3979584 c W95 FAT32 (LBA)

cardctl status (without CF inserted)

Socket 0:
no card
Socket 1:
3.3V 16-bit PC-Card
function 0: [ready], [bat dead], [bat low]
desertrat
QUOTE(Alfinfrance @ Mar 8 2007, 06:15 PM)
So, as I thought, there is a problem between cardctl and pccardctl. Even if microdrive is detected as hda also in beta3 when I boot without CF...

NB I haven't used anything later beta3, is pccardctl the equivalent of cardctl? If so, it is not directly responsible for mounting your partitions. I think the only conclusion that can be drawn is what Capn_Fish pointed out right at the beginning, ie the "Card utility" is broken - but you knew that already didn't you wink.gif Doesn't any other beta4 (or later) users have this problem?
Alfinfrance
Ok, but what I can't understand is why this happened ONLY if you try to flash beta4 or r121 with a CF card ( I did this at the very first time beta4 was downloadable and before this error was described on pdaxrom web site ).

And where are these data written, because I thought that if you came back to original Sharp Rom, problem will be solved.

Is there any other data than NAND you can save/restore in the SL-C3100? ( I saw a HDD Backup / Restore tool in the D+M Menu for example ).

If so, could anyone place here a save from his own data to test ( and how to restore it ).

Another thing : has anyone a sharp rom backup ( original, not the trisoft one ) just to test if it can solve something?

And last : is there anywhere a translation of the buttons of the emergency boot from Sharp? ( I can't read japanese, only french english and german wink.gif )

If anyone need more information about this issue, I'm ready to post any other information you need and to do any test also.

I think I've got a solution, but I'm not quite equiped yet : flash the Sharp Rom without the Microdrive, then flash to r121 and only after all that done, put back the Microdrive ( I need to buy some very small screwdriver to open my Zaurus ). Will send the results here smile.gif
Capn_Fish
Tyrannozaurus has a translatipn of the buttons:

http://www.tyrannozaurus.com/?q=cacko
Alfinfrance
QUOTE(Capn_Fish @ Mar 9 2007, 01:56 PM)
Tyrannozaurus has a translatipn of the buttons:

http://www.tyrannozaurus.com/?q=cacko
*


Thanks.

But it's not a full translation of the menu. I saw for example that some "things" could be solve by the third item of the menu ( harddrive problems for example ) on another part of this forum ( a story of harddrive locked on boot if I remember well ).

Does anyone here speaks japanese?
Capn_Fish
I'm fairly sure Meanie does.
Alfinfrance
For those who will be interestede, I found original Sharp Rom Backups here :

http://downloads.conics.net/pda/zaurus-sl-...iginal-backups/
Antikx
Thanks Conics. You rock!
Alfinfrance
Hum, tried to start the Zaurus without Microdrive and...

Battery light blinking...

Ok, so I reassembled it...

Battery light still blinking sad.gif((((((((((((((

No way to make it start again.

Anyone have a clue of what's going on?
speculatrix
QUOTE(Alfinfrance @ Mar 26 2007, 09:50 PM)
Hum, tried to start the Zaurus without Microdrive and...

Battery light blinking...

Ok, so I reassembled it...

Battery light still blinking sad.gif((((((((((((((

No way to make it start again.

Anyone have a clue of what's going on?
*


the startup scripts specifically look for the hdd, search the forum for "microdrive partition" and you'll find out where the scripts live and how to bypass.

if you're running cacko or OZ, simply install the SL-C1000 variants which don't expect to find a microdrive.
Alfinfrance
QUOTE(speculatrix @ Mar 26 2007, 11:46 PM)
QUOTE(Alfinfrance @ Mar 26 2007, 09:50 PM)
Hum, tried to start the Zaurus without Microdrive and...

Battery light blinking...

Ok, so I reassembled it...

Battery light still blinking sad.gif((((((((((((((

No way to make it start again.

Anyone have a clue of what's going on?
*


the startup scripts specifically look for the hdd, search the forum for "microdrive partition" and you'll find out where the scripts live and how to bypass.

if you're running cacko or OZ, simply install the SL-C1000 variants which don't expect to find a microdrive.
*



I put back the microdrive, and my Zaurus is still in "Blinking Light" Mode. As it couldn't find the battery... Very strange, no?
Meanie
QUOTE(Alfinfrance @ Mar 28 2007, 12:26 AM)
QUOTE(speculatrix @ Mar 26 2007, 11:46 PM)
QUOTE(Alfinfrance @ Mar 26 2007, 09:50 PM)
Hum, tried to start the Zaurus without Microdrive and...

Battery light blinking...

Ok, so I reassembled it...

Battery light still blinking sad.gif((((((((((((((

No way to make it start again.

Anyone have a clue of what's going on?
*


the startup scripts specifically look for the hdd, search the forum for "microdrive partition" and you'll find out where the scripts live and how to bypass.

if you're running cacko or OZ, simply install the SL-C1000 variants which don't expect to find a microdrive.
*



I put back the microdrive, and my Zaurus is still in "Blinking Light" Mode. As it couldn't find the battery... Very strange, no?
*



comment out the code in rc.rofilesys which tries to mount the partitions and make the light blink when it fails to...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.