Help - Search - Members - Calendar
Full Version: C3100 Microdrive Disappears
OESF Forums > Distros, Development, and Model Specific Forums > Model Specific Forums > C1000/3x00 General discussions
icruise
I just got a socket bluetooth card that I have been trying to set up (only partial success so far) but since I started work on it, I've had a problem where my C3100's internal microdrive "disappears" for no apparent reason. I haven't been able to connect this directly to anything I'm doing with the BT card, but it started right after getting it, and even happened when I restored from a backup.

The symptoms are that the microdrive will no longer show up anywhere on the system and the "home" and "documents" screens will get very sluggish. A reboot solves it temporarily, but it's happened 4 times in the last hour or so (since I started trying to get the BT card to work). The last time it happened without even putting the BT card in the slot -- it happened when I put a microdrive in the CF slot. How can I solve this? I'd appreciate any ideas.

By the way, I also get an error message when trying to restart bluetooth or eject the card.
Cresho
what rom are you running and what files did you install to get the bluetooth running>?

If you do a total restore from nand, and you do not use the bluetooth card at all, do you still expirience the same symptoms?
icruise
I'm using the sharp rom with the special kernel. I also have the special kernel modules installed. I haven't tried a NAND restore yet, since I'm still troubleshooting.

I installed the packages from the Bluetooth howto here (including the serial one, since my rev H socket card seems to need it). What is the difference between the "preemptive" package and the other? I tried them both, though, and there doesn't seem to be a difference in terms of this issue.

When I try to eject the card from the command line, I get:
CODE
ioct1():Device or resource busy

When I try to reset bluetooth, I get:

CODE
Shutting down Bluetooth... Can't release device: Operation not permitted
/etc/rc.d/init.d/bluetooth: kill (468) - Not owner
/etc/rc.d/init.d/bluetooth: kill (1579) - No such pid
/etc/rc.d/init.d/bluetooth: kill (468) - Not owner
/etc/rc.d/init.d/bluetooth: kill (474) - Not owner
/etc/rc.d/init.d/bluetooth: kill (474) - Not owner
rm: unable to remove `/var/lock/subsys/bluetooth`:Permission denined
Done.
lardman
You running those commands as root?

Si
icruise
QUOTE(lardman @ Sep 10 2005, 12:31 PM)
You running those commands as root?

Si
*


Heh heh. Oops. No I was not.

One problem solved. biggrin.gif

But I still don't know about this microdrive problem. It hasn't happened again since I wrote the original message, and I've been playing around with the card.
lardman
Could it be something related to the microdrive powering down - then either there not being enough power to spin it up again, or your Z not telling it to wake up again?

Clutching at straws I'm afraid,


Si
Cresho
here is the list of files i use for bluez to work on my z.

bluez-csr-serial_0.1_arm.ipk
bluez-zaurus_arm.ipk
qtopia-bluetoothnetworkapplet_1.0.1_arm.ipk
qtopia-pannetworkapplet_1.0.1_arm.ipk
sudo_0.1_arm.ipk
susp-resume_0.9-3.1.ipk
susp-resume-bluez_0.9.1_arm.ipk

since you have no problems so far, keep us posted and yeah definetly su yourself before initiating commands.
icruise
QUOTE(lardman @ Sep 10 2005, 01:42 PM)
Could it be something related to the microdrive powering down - then either there not being enough power to spin it up again, or your Z not telling it to wake up again?

Clutching at straws I'm afraid,


Si
*


That occurred to me. I think this started when I had my powerbook connected to the Zaurus with the USB cable while at the same time having the bluetooth card inserted. I was running off of battery at the time. So maybe there was too much power drawn somehow. However, I'm pretty sure I've done the same thing with my w-fi card inserted and had no problems, and bluetooth should be lower power than wi-fi, so I don't get it. I'm going to use it for a while and see what happens.

On the bright side, I was able to finally get on the internet through my RAZR. smile.gif So I guess bluetooth itself is working OK.
chroafjd
I also have this problem of my microdrive, and all other cards, disappearing on the C3100. At first I was puzzled as to what was going on, but the postings here have shed some light to the mystery.

I am using the Cacko 1.23b ROM as son far there doesn't seem to be a way to properly switch off the Zaurus using "Suspend" on the QT Menu/ Merely pressing "Suspend" doesn't work.

Hence, the battery gets depleted and I can only switch on the device again using the power supply.

Who has experienced something similar or has an idea of how to properly suspend the C3100 running on Cacko 1.23b?

Thanks in anticipation,
Ashu


--------------------------
SL-C3100, Cack0 1.23b Rom, 1GB SD Card, 1GB CF Card




QUOTE(icruise @ Sep 10 2005, 12:24 PM)
QUOTE(lardman @ Sep 10 2005, 01:42 PM)
Could it be something related to the microdrive powering down - then either there not being enough power to spin it up again, or your Z not telling it to wake up again?

Clutching at straws I'm afraid,


Si
*


That occurred to me. I think this started when I had my powerbook connected to the Zaurus with the USB cable while at the same time having the bluetooth card inserted. I was running off of battery at the time. So maybe there was too much power drawn somehow. However, I'm pretty sure I've done the same thing with my w-fi card inserted and had no problems, and bluetooth should be lower power than wi-fi, so I don't get it. I'm going to use it for a while and see what happens.

On the bright side, I was able to finally get on the internet through my RAZR. smile.gif So I guess bluetooth itself is working OK.
*

icruise
Well, it happened again, and I definitely didn't have anything but the bluetooth card inserted. However, since other people have this same card and don't seem to have this problem, I have a hard time believe that the card is simply incompatible.

Is there anything I can try in the terminal to help narrow down what is happening? Like trying to manually remount the microdrive? I'm not very experienced in Linux, so I'm not sure what to try. So far, as I said above, the only thing that helps is a complete reboot. Restarting Qtopia doesn't solve the problem. I find it interesting that the whole system doesn't exhibit the slowdown that I talked about -- just the home menu. Is that significant in some way? I can't help but think that I have something installed that might be causing this, but I don't know what.

I don't have time to troubleshoot it right now, but I may have to do a restore and see if it still happens with a fresh system.
icruise
I just noticed that if I suspend the Zaurus, the microdrive sometimes reappears. Could this have something to do with the suspend/resume scripts I installed with the bluetooth packages?

Edit: Hmm. It seems that I may have been accidentally causing this myself when trying to eject the bluetooth card in the terminal, although I didn't make the connection until now. It seems that using "cardctl eject" is ejecting my internal microdrive. That's not normal, is it?
polito
QUOTE(icruise @ Sep 11 2005, 06:10 PM)
I just noticed that if I suspend the Zaurus, the microdrive sometimes reappears. Could this have something to do with the suspend/resume scripts I installed with the bluetooth packages?

Edit: Hmm. It seems that I may have been accidentally causing this myself when trying to eject the bluetooth card in the terminal, although I didn't make the connection until now. It seems that using "cardctl eject" is ejecting my internal microdrive. That's not normal, is it?
*


No it's not normal for eject to dump the microdrive. I never had this problem until tonight. I had gotten my Rev. G card working just fine until (of course....) I decided to try and get my Stowaway Bluetooth Keyboard working (which I did manage to get working by the way) using the latest Tetsu kernel (his site seems to be down right now) which is v18b for the C3100.

I installed the kernel, the modules, and I installed the latest bluez and a modified hidp from:
http://gypsyblue.ddo.jp/cgi-bin/fswiki/wiki.cgi

which did technically work... after I manually did the ol'
CODE
hciattach /dev/ttyS3 bcsp 230400


then I was able to get my card working. Connected to internet via my Nokia 6230 with EDGE and everything. The keyboard worked nice too, though I need to mess around with keyhelper more.

Oh, and you'll want to use http://odn.excite.co.jp/world/url to translate that page into english. Yes, that web page is in Japanese but it works, just type the url you want into the box, select the second radio button and hit the submit button with the japanese writing on it that I can't read and you'll be fine biggrin.gif

BUT... somehow, somewhere... while I was fighting with trying to get the card to resume correctly, (and I never typed cardctl eject 1, EVER) the hard drive disappeared!

dmesg talked about being unable to read the partition on hda which made me feel very sad inside since normally that looks like something wrong with the hard drive.

Well I tried various things and I was able to get the card to show up via cardctl again but the drive wouldn't mount automatically like it should.

I tried
CODE
mount -a -t nonfs


which is what the rc scripts do and nothing happened.

Then I thought... since nothing else is working with any sort of sanity, let me pop in my 4gb microdrive into the external CF slot and see what happens.

I did. And it showed up ok, but cardctl showed 'No card' for socket 1 which is the internal microdrive. That ticked me off. So I cardctl insert'ed it and it was there. Then I suspended and resumed... and how interesting... /dev/hda was back! ARGH I hate it when things don't make sense sad.gif

Just thought I'd add some more stuff to the mix. I hope you're not still having the same problems.
icruise
QUOTE(polito @ Sep 25 2005, 12:34 AM)
No it's not normal for eject to dump the microdrive. I never had this problem until tonight. I had gotten my Rev. G card working just fine until (of course....) I decided to try and get my Stowaway Bluetooth Keyboard working (which I did manage to get working by the way) using the latest Tetsu kernel (his site seems to be down right now) which is v18b for the C3100.

Looks like we have identical setups. I'm using the socket bluetooth card (mine's rev H) and Stowaway Bluetooth Keyboard as well. I posted a thread about it in the Accessories section of the forum.

Have you managed to get the keyboard to automatically connect when opening it? The way I have it set up now, I have to run hidd --connect to connect to the keyboard. I have it set to a keyhelper key combination, so it's not a big deal, but it would be nice to have everything be automatic.
QUOTE
Oh, and you'll want to use http://odn.excite.co.jp/world/url to translate that page into english. Yes, that web page is in Japanese but it works, just type the url you want into the box, select the second radio button and hit the submit button with the japanese writing on it that I can't read and you'll be fine biggrin.gif

Well, I'm a Japanese translator, so I don't have any trouble with reading Japanese. Comes in handy for Zaurus-related sites. wink.gif
QUOTE
BUT... somehow, somewhere... while I was fighting with trying to get the card to resume correctly, (and I never typed cardctl eject 1, EVER) the hard drive disappeared!

(snip)

Then I thought... since nothing else is working with any sort of sanity, let me pop in my 4gb microdrive into the external CF slot and see what happens.

I did. And it showed up ok, but cardctl showed 'No card' for socket 1 which is the internal microdrive. That ticked me off. So I cardctl insert'ed it and it was there. Then I suspended and resumed... and how interesting... /dev/hda was back! ARGH I hate it when things don't make sense  sad.gif
*

So am I understanding you correctly that suspending and resuming brought back your microdrive? That seems to do the trick many times in my case as well, although not always. (Sometimes I have to do it a couple of times.) However, I haven't been having this problem very much recently, and I think it's because I've been keeping the socket card in the CF slot all the time. It seems like the problem happens most often when swapping cards.

I think there's something a little fishy with the socket cards and the 3100.
polito
QUOTE(icruise @ Sep 25 2005, 12:03 AM)
Have you managed to get the keyboard to automatically connect when opening it? The way I have it set up now, I have to run hidd --connect to connect to the keyboard. I have it set to a keyhelper key combination, so it's not a big deal, but it would be nice to have everything be automatic.

Well I was really irked at my bluetooth card not coming back normally as it used to when I had the stock sharp kernel and tumnus' bluez-zaurus package installed so I haven't tried getting the keyboard to work automatically yet.

I had to do a tweak to that even to do the hciattach bit in the resume portion but if I kept the card in the slot, I had no problem suspending and resuming. I could whip the Z out and check something out on the net just by clicking the network globe. Now I have to manually type hciattach AND go to the network settings panel and select the bluetooth dialup item to be able to connect... lame. sad.gif

QUOTE
Well, I'm a Japanese translator, so I don't have any trouble with reading Japanese. Comes in handy for Zaurus-related sites. wink.gif

I envy you... I really envy you. I always seem to run into something where the only reference seems to be to some page in Japanese that I can't read and I just had this gut feeling that my answer was in there...somewhere laugh.gif

QUOTE
So am I understanding you correctly that suspending and resuming brought back your microdrive?
*

Well it did seem to make it come back. But only hda3. hda2 and hda1 didn't come back (those are the ext3 partitions) and I rebooted and everything was back to normal... so far. I think you're right... something fishy is definitely going on and it's eating me up inside that I haven't figured it out.

I'll post back here if I figure anything else out. Nice to see I'm not the only one with this problem, thought I was going bonkers.
icruise
QUOTE(polito @ Sep 25 2005, 02:31 AM)
I had to do a tweak to that even to do the hciattach bit in the resume portion but if I kept the card in the slot, I had no problem suspending and resuming. I could whip the Z out and check something out on the net just by clicking the network globe. Now I have to manually type hciattach AND go to the network settings panel and select the bluetooth dialup item to be able to connect... lame.  sad.gif


Hmm. Luckily, my bluetooth seems to be working perfectly (aside from the microdrive issue that we're talking about). It took a little experimentation to figure out how to get my card to work after a suspend, but now I can dial through my RAZR to access the net, and just yesterday I worked out how to use my Windows machine to share my wireless network to the zaurus through bluetooth. Haven't figured out how to do it on my Mac though. I haven't had the disappearing globe problem, although a lot of people seem to.

QUOTE
I'll post back here if I figure anything else out. Nice to see I'm not the only one with this problem, thought I was going bonkers.


Yes, I know what you mean. I'm interested to hear what you discover.
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.