OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: amcclimo on October 29, 2004, 09:01:12 pm
-
I've just downloaded the 3.5.1 release of Opie, and was dissappointed that -no- Compact Flash devices are detected. I've tried 5 different brands of CF Memory Cards, and also my Linksys CF WiFi card.
I'm not sure where to start testing to identify the problem, however when i tried the GPE version, the CF cards were detected again.
Has anyone else noticed this with the Opie 3.5.1 release?
Previously i've been using the Opie 3.3.5 with no issues.
Can someone help guide me to find out what is wrong and how to fix it?
Cheers.
-
I flashed to 3.5.1 Opie (SL5500) last weekend and had no problems installing packages from my CF card, and my dlink 660w wifi was detected without having to change anything.
Unfortunately I also have no suggestions where to begin troubleshooting. Perhaps a bad flash or initialization? It's certainly an odd problem.... OHH!!! I saw in another thread that someone discovered their CF card wouldn't read when formatted as FAT, and they had to reformat as FAT16 (or maybe it was the other way around?). You might take a look at that? However it doesn't explain why your wifi card wouldn't read. Hmmm.
-
I also have no problems whatsoever with a PQI memory card and a D-Link Bluetooth card. Try "cardctl status", "cardctl ident" and "cardctl info" for some diagnostics. Also, check /etc/fstab, /etc/mtab and /etc/ide.opts. Various other cardctl commands, as well as mount/umount, may help you debug the rest.
z.
-
Check that you really flashed the proper zImage. If the kernel doesn't match the root file system, it may look like everything works, but you will experience strange effects. Not mounting any cards could be one of those.
After I released 3.3.5, I received a lot of posts from angry people telling me that OZ 3.3.5 works like shit, then after some inquiry we found out that they didn't rename their kernel and they were working with kernel 2.4.6 from OZ 3.2 still....
-
Check that you really flashed the proper zImage. If the kernel doesn't match the root file system, it may look like everything works, but you will experience strange effects. Not mounting any cards could be one of those.
Just to make sure i had the right files, i downloaded them again.
On my CF card i have only the following two files:
initrd.bin
MD5 Sum: 4D86DF5295936A9A194120AEF1698AD4
zImage.bin (64-0)
MD5 Sum: 411DD36727AF0C654C910B0BA8993044
A start i guess would be to confirm if these are correct... I'll post a bit more info in a moment...
Aaron.
-
Ok, seems the cardctl program can actually see the card, i guess there's another start.
cardctl info:
PRODID_1="SanDisk"
PRODID_2="SDP"
PRODID_3="5/3 0.6"
PRODID_4=""
MANFID=0045,0401
FUNCID=4
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
cardctl ident:
Socket 0:
product info: "SanDisk", "SDP", "5/3 0.6"
manfid: 0x0045, 0x0401
function: 4 (fixed disk)
Socket 1:
no product info available
cardctl status:
Socket 0:
3.3V 16-bit PC Card
function 0: [ready]
Socket 1:
no card
cat /etc/fstab:
/dev/mtdblock4 / jffs2 defaults 1 1
proc /proc proc defaults 0 0
/dev/hda1 /mnt/cf auto defaults,sync,noauto,noatime,user,exec,suid,gid=100,umask=0002 0 0
/dev/mmcda1 /mnt/card auto defaults,sync,noauto,noatime,user,exec,suid 0 0
tmpfs /var tmpfs defaults 0 0
cat /etc/mtab:
/dev/root / jffs2 rw 0 0
ramfs /dev ramfs rw 0 0
proc /proc proc rw 0 0
tmpfs /var tmpfs rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/mmcda1 /mnt/card ext2 rw,noatime 0 0
There is no file /etc/ide.opts
When i try and mount /mnt/cf i get the following:
mount: Mounting /dev/hda1 on /mnt/cf failed: No such device or address
So it seems the Zaurus can see the CF Card, but it's still not working... the cardmon util still only shows the SD Card as being inserted.
Hope this helps somewhat, as i still have no clue as what's wrong...
Aaron.
-
Sorry, it's /etc/pcmcia/ide.opts. It has to do with auto-mounting.
-
Sorry, it's /etc/pcmcia/ide.opts. It has to do with auto-mounting.
Ok, here's some more info:
cat /etc/pcmcia/ide.opts:
# ATA/IDE drive adapter configuration
#
# The address format is "scheme,socket,serial_no[,part]".
#
# For multi-partition devices, first return list of partitions in
# $PARTS. Then, we'll get called for each partition.
#
CASE "$ADDRESS" in
*,*,*,1)
#INFO="Sample IDE setup"
DO_FSTAB="y";
#DO_FSCK="y";
DO_MOUNT="y"
#FSTYPE="msdos"
#FSTYPE="auto"
#OPTS=""
#MOUNTPD="/mnt/ide"
;;
*,*,*)
#PARTS="1"
# Card eject policy options
NO_CHECK=n
NO_FUSER=y
;
esac
Also, i noticed the first time i turned it on after flashing, there were a -lot- of unresolved symbols shown. Is there a log somewhere for all this initial unpacking/setup/configuration/??
It still beats me why others have it working with a fresh install Opie 3.5.1, yet mine doesn't, but everything works with an older version or GPE 3.5.1 =/
... perhaps the unresolved symbols mentioned above are just a start to my problems? can someone confirm the MD5 sums i posted above?
Aaron.
-
Is there a log somewhere for all this initial unpacking/setup/configuration/??
Try "dmesg".
-
I've attached my dmesg output. Of interest is this section:
Internal error: Oops: 0
CPU: 0
pc : [<c010b5fc>] lr : [<c0033e68>] Tainted: P
sp : c3b11c70 ip : c01d4678 fp : c3b11c94
r10: 00000000 r9 : 00037d50 r8 : 00000100
r7 : 00000d00 r6 : 00000c00 r5 : c3f6f280
r4 : 00000c00
r3 : 00000000 r2 : 00000000 r1 : c3b11c3c
r0 : 00000001
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment user
Control: C3AB717F Table: C3AB717F DAC: 00000015
Process cardmgr (pid: 463, stackpage=c3b11000)
Stack: (0xc3b11c60 to 0xc3b12000)
Is this saying the cardmgr is having problems? which could explain my issue?
Aaron.
-
It would seem so but I'm at a loss as to why that might be. Still, you can at least try getting cardmgr to run from the command line and see what happens.
-
I don't know if this helps, but I have the same thing with my 5600. My workaround so far has been that if you turn off automounting of the cf card you can terminate opie, mount a card manually, restart opie and it will work just fine. Be sure to unmount before you pull the card though.
Looking forward to a better solution,
ADF
-
Can you do a 'uname -a' for me?
Cardmgr oopsing can have two problems:
1.) wrong kernel
2.) there is a batch of Zaurii which apparantly have slightly different hardware timing. The 2.4.18-embedix kernel is flakey enough that this could make a difference.
That said, anyone want to help finishing 2.6 ?
-
Mickeyl,
uname -a returns:
Linux collie 2.4.18-rmk7-pxa3-embedix #1 Fri, 28 Nov 2003 17:16:21 +0100 armv41 unknown
Is there any way i can identify if my Zaurus is from the batch with the different hardware timing?
Count me in for 2.6 kernel testing ... i'm ready to start immediately if it'll help fix this problem
Aaron.
-
Linux collie 2.4.18-rmk7-pxa3-embedix #1 Fri, 28 Nov 2003 17:16:21 +0100 armv41 unknown
Aha. That's what I suspected. This is _NOT_ the kernel from OpenZaurus 3.5.1, but the kernel from OpenZaurus 3.3.5 (or 3.3.6-pre1). Look at the date of compilation.
Like I told you, if kernel and root file system don't match, all kinds of things happen. It's very disappointing that the reputation of OpenZaurus always gets thrashed because of user errors
-
Mickeyl,
Don't get me wrong, i'm not trying to thrash the reputation of OpenZaurus, infact i'm all for the progress and effort that people are making and putting in to it.
I just confirmed again that the images i used were the correct ones for Opie 3.5.1 . I downloaded from this location:
http://www.openzaurus.org/official/unstabl.../sl5000,sl5500/ (http://www.openzaurus.org/official/unstable/3.5.1/sl5000,sl5500/)
These are defintely the files that are on my CF Card when i'm flashing it... which now leads me to believe that it's not being flashed properly...
I'll take a step back and double check i'm flashing things right... all going well i'll make a final post with a thankyou for your time and an apology for wasting your time =/
Cheers,
Aaron.
-
Well, don't i feel like the idiot... the zImage file i had appended .bin to the filename... and nobody picked that up from one of my early posts =/
All is working now, such a simple thing too...
Thankyou to all who posted, and yes, my appologies for making an issue of my own user error.
Aaron.
-
Ha! I thought with zImage.bin you'd never get the impression that flashing went OK, so I considered it a typo
-
My kernel, however, is sept '04. the right one. I think the issue is a package (one of many I've installed) doing some caching thing or other.
I'd be happy to help w/ 2.6, but I doubt I have any qualifications beyond the ability to break my z and describe how I did. I certainly can do compiling and stuff like that if it would help?
adf
-
Ha! I thought with zImage.bin you'd never get the impression that flashing went OK, so I considered it a typo
Unfortunately not, the flash updater also features individual flashing of the initrd.bin and the zImage.