Something unclearly for me in dmesg

[svs]

Who can explain me messages I underlined.
I havn\'t \"noatimei\" in /etc/fstab
/dev/mmca1 is Linux (83) partition and ext2 fs.
What\'s mean: \"cramfs: wrong magic\"
Last 2 messages more important for me.
Something wrong with Socket BT CF?
What\'s wrong with  battery?
A lot of thanks in advance.

...
SD Driver Initialized.
sharp_mmcsd 0.21 27 Sep 2002
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
EXT2-fs: Unrecognized mount option noatimei
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
cramfs: wrong magic
~~~~~~~~~~~~~~

VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Can\'t find a Minix or Minix V2 filesystem on device 3c:01.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
MSDOS FS: IO charset utf8
FAT: bogus logical sector size 0
VFS: Can\'t find a valid FAT filesystem on dev 3c:01.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

FAT: freeing iocharset=utf8
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
 mmcda: mmcda1
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BlueZ Core ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
dtl1_cs: Nokia control data = 07 00
usbdm: usbd_monitor 0.3 035 2002-06-12 20:00
monitor_request_irq: 23 44
monitor_request_irq: failed: -16
usbdm: request irq failed
monitor_connected: 1
monitor_load:
monitor_hotplug: agent: usbd interface: monitor action: load
usbdcore: usbdcore 0.1 035 2002-06-12 20:00 (dbg=\"\")
net_fd 0.1 035 2002-06-12 20:00 (dbg=\"\",alwaysup=0,OUT=64,IN=64)
vendorID: 4dd productID: 8004
sa1100_bi 0.2 035 2002-06-12 20:00 (dbg=\"\")
bi_modinit: call udc_startup_events
bi_device_event: call udc_enable
bi_device_event: call udc_all_interrupts
monitor_modinit: finished
BlueZ L2CAP ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ RFCOMM ver 1.0
Copyright © 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Copyright © 2002 Marcel Holtmann <marcel@holtmann.org>
This function is not support     411c
~~~~~~~~~~~~~~~~~~~~~~~~~~
check backup battery !
~~~~~~~~~~~~~~~~~~~~~~~~~~

[tumnus]

I don\'t see anything wrong. Mount options for SD cards are specified in /etc/sdcontrol, not /etc/fstab. Besides which the message about noatimei is just a warning and doesn\'t affect anything. The messages about cramfs, Minix and FAT are also just routine messages as it tries to automount the SD card and guesses the format simply by trying a filesytem until it finds one that works.

Possibly the only thing to be concened about is the message about the backup battery. Have you charged your Zaurus for at least 24 hours since you got it or let the main battery go flat? It has a backup NiCd battery inside that it uses to keep the RAM alive for 24 hours if the main battery goes flat. I think this backup battery is trickle charged to make it last longer, hence the 24 hour charge.

[svs]

Thanks for quick reply. I worry because my Zaurus hang
from time to time without any reason. I bought used Z (5500). How can I check backup battery?
I didn\'t find backup battery test in internal tests
(Fn - d - p - <hard reset> buttons)
I\'ll try charge Z 24 hours next weekend.

What do you think about message:
This function is not support     411c
Is it about bluetooth?

[maslovsky]

How can I check backup battery?

You don\'t. I looked in the kernel source code - it\'s just a dummy message indicating that it\'s checking battery status. It should be something like \"Checking battery...\"

[Anonymous]

Ok. Next times when Z will hang I try find backup battery
test in hardware tests.

[bluey]

It is a typo on the script /etc/sdcontrol, it should be noatime, you can change it.

atime stands for \"access time\". When you access a file on the sd card, in this case, there\'d be a change in the access time for that file, causing writes being made in the sd. With noatime, there won\'t be writes to the sd, so the access speed to the card should be faster.

Are you using tkcrom?

c ya.

[Anonymous]

No. I\'m using Sharp ROM 3.10