Cacko Zaurus Qtopia ROM 1.21 is available!

[ShiroiKuma]

OK, maybe not out of the woods yet. Don\'t know if this is just a setup problem...

Like I said above, restarted, the card got recognized on insertion, its light lit up for a while.

Then I proceeded to setup Bluetooth services, following the Bluetooth howto http://www.zaurususergroup.com/modules.php...ename=Bluetooth

Set up a Bluetooth connection in the Networking tab, just selected Add, didn\'t edit any of the options and saved it with OK.

Then, like it says, I went to a command prompt and did sdptool browse to which I immediately, i.e. no delay, no card\'s light flashing, got the following:
Inquiring ...
Inquiry failed

Also just out of curiosity, I tapped the Globe icon in the tray, that represents the Bluetooth connection. It asked for the pin, I put in the pin, than it says Initializing modem and that\'s it, this doesn\'t disappear, nothing further happens.

What\'s wrong? Am I doing something wrong?

[ShiroiKuma]

Additionally, I have just now looked at the  Socket CF Bluetooth Rev 2.5G thead here http://zaurususergroup.com/index.php?name=...etooth&start=30 where part of the symptoms were the same, i.e. the user, after his card was recognized and did sdptool browse he got the Inquiry failed response, just like me.

In it it was recommended that he do cardctl resume and /etc/pcmcia/bluetooth restart, so I tried.

The results:
cardctl resume
ioctl(): Device or resource busy
/etc/pcmcia/bluetooth restart
Shutting down Bluetooth... hci0:   Type: PCCARD
   BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
   DOWN
   RX bytes:0 acl:0 sco:0 events:0 errors:0
   TX bytes:0 acl:0 sco:0 commands:4 errors:0

Done.
Starting Bluetooth... parse error line 3
Done.

Maybe that\'s why the Inquiry fails?

What\'s wrong?

[ShiroiKuma]

Furthermore, thought this might be of importance. I get the following from hciconfig

hci0:   Type: PCCARD
          BD Address: 00:00:00:00:00:00 ACL MTV: 0:0    SCD MTV: 0:0
          DOWN
          RX bytes:0 acl:0 sco:0 events:0 errors:0
          TX bytes:0 acl:0 sco:0 commands:2 errors:0

[maslovsky]

First of all, you should not have installed any additional bluetooth drivers whn using Cacko ROM 1.2x. Npw if you uninstall them, you\'ll most likely get a non-working bluetooth configuration. Did you make a backup of your Zaurus before installing bluetooth drivers? If you did -restore it. If not, then you\'d better reflash the ROM. Then update config file again and post me the result of hciconfig and dmesg commands after the card is inserted.

[ShiroiKuma]

I didn\'t install any other Bluetooth drivers, just tried following the sequence of commands  

Anyhow, I restored my Zaurus to the Sharp Japese ROM yesterday to copy the origininal Japanese fonts.

Then reflashed with Cacko ROM 1.21, so now have a clean Zaurus with nothing else installed. Updated the /etc/pcmcia/bluetooth.conf file as directed.

Now it recognizes the card upon insertion, followed by the card\'s light being lit up for a couple of secs.

The two commands now give me the following output:

hciconfig
hci0:   Type: PCCARD
   BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU: 0:0
   DOWN
   RX bytes:0 acl:0 sco:0 events:0 errors:0
   TX bytes:0 acl:0 sco:0 commands:1 errors:0

dmesg
Linux version 2.4.18-rmk7-pxa3-embedix-021129 (maslovsky@linux) (gcc version 2.95.2 19991024 (release)) #1 Tue, 06 Apr 2004 00:41:29 +0400
CPU: Intel XScale-PXA255 revision 6
Machine: SHARP Shepherd
Converting old-style param struct to taglist
Memory clock: 99.53MHz (*27)
Run Mode clock: 199.07MHz (*2)
Turbo Mode clock: 398.13MHz (*2.0, active)
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: console=ttyS0 root=/dev/mtdblock2 mtdparts=sharpsl-nand:7168k@0k(smf),27648k@7168k(root),-(home) jffs2_orphaned_inodes=delete LOGO=1 LAUNCH=q
Console: colour dummy device 80x30
Calibrating delay loop... 397.31 BogoMIPS
Memory: 64MB = 64MB total
Memory: 62012KB available (1884K code, 470K data, 100K init)
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
RCSR = 2
apm: BIOS version 1.2 Flags 0x02 (Driver version 1.14)
FCS : CCCR = 161
batok installed
Starting kswapd
Journalled Block Device driver loaded
JFFS2 version 2.1. © 2001, 2002 Red Hat, Inc., designed by Axis Communications AB.
reset resolution unkown => 480x640
Console: switching to colour frame buffer device 80x30
fb0: W100FB frame buffer device
keyboard initilaized.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with no serial options enabled
SharpSL serial driver version 5.05c (2001-07-08) with no serial options enabled
ttyS00 at 0xf8100000x (irq = 14) is a 16550A
ttyS01 at 0xf8700000x (irq = 12) is a 16550A, using IRDA
ttyS02 at 0xf8200000x (irq = 13) is a 16550A
rs_init: IRDA H/W initializaion
sharpled_init: done.
corgi remote controller
Cotulla Real Time Clock driver v1.00
Cotulla Touch Screen driver initialized
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
loop: loaded (max 8 devices)
PPP generic driver version 2.4.1
PPP BSD Compression module registered
ide_cs.c 1.26 1999/11/16 02:10:49 (David Hinds)
Corgi audio driver initialize
Sharp SL series flash device: 1000000 at 0
Using static partision definition
Creating 1 MTD partitions on \"sharpsl-flash\":
0x00120000-0x007f0000 : \"Filesystem\"
NAND device: Manufacture ID: 0xec, Chip ID: 0x79 (Samsung K9D1G08V0M)
Creating 3 MTD partitions on \"Samsung K9D1G08V0M\":
0x00000000-0x00700000 : \"smf\"
0x00700000-0x02200000 : \"root\"
0x02200000-0x08000000 : \"home\"
Linux Kernel Card Services 3.1.22
  options:  [pm]
Intel PXA250/210 PCMCIA (CS release 3.1.22)
pxa_pcmcia_init(0)
pxa_pcmcia_init(1)
Backlight Driver Initialized.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.95 © 1998-1999 Rebel.com
IrCOMM protocol (Dag Brattli)
cramfs: wrong magic
FAT: bogus logical sector size 381
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing init memory: 100K
pxa_sd_wait_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
SD Driver Initialized.
sharp_mmcsd 0.21 27 Sep 2002
VFS: Disk change detected on device mmcd(60,1)
pxa_sd_wait_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
VFS: Disk change detected on device mmcd(60,1)
pxa_sd_wait_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
VFS: Disk change detected on device mmcd(60,1)
pxa_sd_wait_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
VFS: Disk change detected on device mmcd(60,1)
pxa_sd_wait_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
VFS: Disk change detected on device mmcd(60,1)
pxa_sd_wait_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
VFS: Disk change detected on device mmcd(60,1)
pxa_sd_wait_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
pxa_sd_wait_id_response: card removed (cmd=00)
ide_attach()
ide_config(0xc3868880)
Trying to free nonexistent resource <f6000000-f600000f>
hda: IBM-DSCM-11000, ATA DISK drive
ide0 at 0xf6000008-0xf600000f,0xf600000e on irq 39
hda: 2104704 sectors (1078 MB) w/60KiB Cache, CHS=2088/16/63
Partition check:
 hda: [PTBL] [522/64/63] hda1
ide_cs: hda: Vcc = 3.3, Vpp = 0.0
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
EXT3-fs: Unrecognized mount option quiet
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
EXT2-fs: Unrecognized mount option quiet
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
cramfs: wrong magic
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
VFS: Can\'t find a Minix or Minix V2 filesystem on device 03:01.
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
VFS: Disk change detected on device ide0(3,1)
 hda: hda1
MSDOS FS: IO charset utf8
usbdm: usbd_monitor 0.3 035 2002-06-12 20:00
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: 9031
pxa_bi 0.1-alpha 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
pxa_pcmcia_init(0)
ide_release(0xc3868880)
in_interrupt
ide_detach(0xc3868880)
ide_release(0xc3868880)
BlueZ Core ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
bluecard_cs: Unknown HCI packet with type 0x28 received.
bluecard_cs: Unknown HCI packet with type 0x20 received.
bluecard_cs: Unknown HCI packet with type 0xfc received.
BlueZ L2CAP ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ RFCOMM ver 1.1
Copyright © 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Copyright © 2002 Marcel Holtmann <marcel@holtmann.org>

Progress? :x

[maslovsky]

hciconfig  
hci0: Type: PCCARD  
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0  
DOWN  
RX bytes:0 acl:0 sco:0 events:0 errors:0  
TX bytes:0 acl:0 sco:0 commands:1 errors:0

BlueZ Core ver 2.3 Copyright © 2000,2001 Qualcomm Inc  
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>  
bluecard_cs: Unknown HCI packet with type 0x28 received.  
bluecard_cs: Unknown HCI packet with type 0x20 received.  
bluecard_cs: Unknown HCI packet with type 0xfc received.  
BlueZ L2CAP ver 2.3 Copyright © 2000,2001 Qualcomm Inc  
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>  
BlueZ RFCOMM ver 1.1  
Copyright © 2002 Maxim Krasnyansky <maxk@qualcomm.com>  
Copyright © 2002 Marcel Holtmann <marcel@holtmann.org>  

Looks like your card is not supported by the bluecard_cs module. Try to bind it to other bluetooth driver modules. If none of them work - then you\'re definitely out of luck

[ShiroiKuma]

Thank you, I\'ll try right away.

This might be a dumb question, but which directory are all the modules in, so that I can try one after the other. I can\'t find them, so don\'t know which ones to try...

Thanks.

[ShiroiKuma]

OK, am out of luck  :cry:

Never mind the above, I found the location of the modules. Tried every one errors.

So no, what are my options?

Can I use any other ROM? The Zaurus original and Cacko don\'t work. Is there a possibility TKC will work or pdaXrom? Should I try?

Also if not, I\'d try contacting the seller and give the card back to them, they ain\'t gonna refund me the cash, but I could maybe ask if I could change it for an older revision and pay some extra...

For this, how do I check than that the card I want to buy will work?

I specifically bought the Anycom card, because all I read everywhere, it said it works... Booh, boo  :cry:

What can I do?

[maslovsky]

The problem with your card is that it looks like Anycom (like many other manufacturers) started to produce new revisions of their cards, which are not yet supported by any linux bluez drivers. The best option for you would be to replace the card witjh older revision (if possible) or with another supported card, like Ambicom BT2000E (not C) or Socket.

[ShiroiKuma]

Is it possible to tell from the card which revision it is, and if I get an Anycom again which revision I should get?

[maslovsky]

Is it possible to tell from the card which revision it is, and if I get an Anycom again which revision I should get?

I don\'t know about Anycom card. Ambicom card BT2000E is the one without LEDs. Possibly old revision of Anycom card does not have LEDs too.

[pdemilly]

I am a new owner of a C860 from Dynamism. I am trying different ROM to find the one I like the best or maybe have a multiboot option. I am very familiar with Linux on the desktop but newbie in regards to PDA and right now I am confused by all the different ROMS. I flashed pdaxrom on the C860 and like it very much. I would like now to try OZ but can\'t find any instructions on how to either restore Sharp ROM and/or install OZ. Also I am confused about all the different ROM names. For example in this thread is mentioned Cacko (is this pdaXrom?), conics web site, Opie, OZ, maslovky?

How can I go from pdaXrom back to Sharp ROM or directly to OZ? Any help greatly appreciated

TIA

Pascal

[padishah_emperor]

Maslovsky, I\'ve done a reflash of the ROM because I was bored but now when I do a \'modprobe usbnet\' I get:

Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
modprobe: Can\'t locate module usbnet

It worked before I flashed, I don\'t want to flash again and I haven\'t modified modules.conf

Also can anyone send me the original startup screen?

[W.E.Coyote]

I would like say thanks to Maslovsky for the ROM.  Very impressive and I am one happy user.  

I have been trying to set up my bluetooth card without much success.  I have followed a number of threads on the subject all to no effect.  

I would agree that adding bluez files as per the ‘how to page’ does not help with the Cacko 1.21a.  It did nothing other than require yet another re flash.

Sadly I think that Maslovsky may well be right about the drive support for newer cards.

In the off chance that anyone has any good ideas this is the brief out line.

Card : Blue Monkey, FCC ID PANBT010M
Cardctl ident: Socket 0:
                                Product info: “Bluetooth BT0100M”, “”, “”
                         Function : 2 (Serial)
Cardctl status: Scocket 0:
      3.3v 16-bit PC Card
      function 0: [ready]
And I get a funky blue led that flashes.

Machine is a C860 with Cacko 1.21a and no other extras (as yet)

No other commands indicate that the existence of the card has been recognised. It responds to card being stopped and restarted, at least the led stops and starts.  My belief is that the drives have not been picked up for it.  This is most probably due the “product info” description not being in the file containing the bind instructions.   This is also probably due the card not being supported.

Two things I would like answers to are
a)   Is there any significance in the ident being function 2 and the staus being function 0?
   Most cards have at least 2 fields in there product information description were at this card has one full field and 2 nulls.  How should it be described in the /etc/pcmcia/bluetooth.conf ?

For background I am an ancient 6502 assembler programmer, no we have not all died we look that way.  I also spend 5 years as an administrator on a small unix system some 15 years ago, man do I wish had not given my books and notes away!
All of which will probably classify me as dangerous out of date and far too gung ho!

[maslovsky]

Maslovsky, I\'ve done a reflash of the ROM because I was bored but now when I do a \'modprobe usbnet\' I get:

Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
modprobe: Can\'t locate module usbnet

It worked before I flashed, I don\'t want to flash again and I haven\'t modified modules.conf

There is no such modules in the ROM. You\'ve probably installed some packages that contained tha module.