OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Debian => Topic started by: Z3n on February 01, 2008, 02:04:20 pm
-
Hey all, I have gotten Titchy installed on my C3100, just the base mind you right now.
I have gotten networking to work with my Hawking Ethernet card but I am going to eventually be using my phone as a modem. I have a Socket Bluetooth card that I would like to use.
I installed the bluez-utils package before inserting the card.
Here is the output from dmesg:
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
pccard: card ejected from slot 1 (ejected Hawking Card)
pccard: PCMCIA card inserted into slot 1 (Socket Bluetooth Card)
pcmcia: registering new device pcmcia1.0
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial_cs: Unknown symbol serial8250_unregister_port
serial_cs: Unknown symbol serial8250_resume_port
serial_cs: Unknown symbol serial8250_register_port
serial_cs: Unknown symbol serial8250_suspend_port
pccard: card ejected from slot 1
Not sure what I should be doing to get this to come up correctly. Any help would be appreciated.
-
So, reading further into the Bluetooth on Debian EABI I am seeing that some have had success upgrading to the Angstrom's 2.6.23 kernel.
Upon trying that I didn't replace my update.sh script and it flashed the kernel and started formating the microdrive! DOH!
So, once I reinstall Titchy base I will try once again to upgrade the kernel using a different update.sh
I have the kernel and the modules but anyone that can point me in the right direction on finding a suitable update.sh script that will work. I don't want to have to reinstall again if I can help it.
-
No one can give a direction on an update.sh script that will only flash the kernel and not start formating the microdrive?
-
I'm afraid I'm not sure now, too much tryouts and bad memory is a bad combo, I think I used titchy's one but can not be sure, I can anyway upload the one I used to update here for you from the place i have it stored tomorrow or the day after tomorrow when I'm back home
-
Hey all, I have gotten Titchy installed on my C3100, just the base mind you right now.
I have gotten networking to work with my Hawking Ethernet card but I am going to eventually be using my phone as a modem. I have a Socket Bluetooth card that I would like to use.
I installed the bluez-utils package before inserting the card.
Here is the output from dmesg:
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
pccard: card ejected from slot 1 (ejected Hawking Card)
pccard: PCMCIA card inserted into slot 1 (Socket Bluetooth Card)
pcmcia: registering new device pcmcia1.0
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial_cs: Unknown symbol serial8250_unregister_port
serial_cs: Unknown symbol serial8250_resume_port
serial_cs: Unknown symbol serial8250_register_port
serial_cs: Unknown symbol serial8250_suspend_port
pccard: card ejected from slot 1
Not sure what I should be doing to get this to come up correctly. Any help would be appreciated.
your kernel is missing the serial_cs or 8250_cs module, so changing the kernel is indeed the way to go.
There is such a updater script in one of the threads (together with a way to change the updater scripts).
Chero.
-
No one can give a direction on an update.sh script that will only flash the kernel and not start formating the microdrive?
Doesn't Meanie or someone have the source to update.sh? I'd have to search the forums to find it, but I know that it has been posted in the past.
-
Back home, or I messed archiving or this is the one I used with zImage.bin (nothing more) after copying modules on lib
-
Thanks all for the advise and thanks laan for the updater.sh script it worked as advertised.
Only problem is, I flashed and got a kernel panic right off the bat. I am going to assume that there is something else that needs to change in the flash to boot that new kernel. Using the same script supplied by Iaan I flashed back to the Titchy 2.6.20 kernel and I am now booted back up...
Steps I took are loaded onto a 1G SD card the required modules for 2.6.23, the kernel image as zImage.bin and the updater.sh script.
Mounted SD card in currently working Titchy install and expanded the modules so I have /lib/modules/2.6.23
Shutdown and restarted with the OK and power to flash new kernel which was successful.
Rebooting give me a kernel panic.
Same procedure but with the Titchy 2.6.20 zImage.bin on SD and reflashed... booted normally.
So, I am going to assume there is something else that needs to change in flash to make it aware that there is a new/different kernel to boot.
Any ideas or direction to take to make this possible?
I really want to have Debian on my Z. It would make having to haul my laptop around a moot point if I can get to a workable solution.
Thanks everyone.
~Z3n
-
So, I went back to this tread - "Bluetooth Under Debian Eabi, it works!"
Last page I believe Chero has links to the 2.6.23 kernel image and modules that he used to flash.
I re-downloaded both files... removed the modules directory I had on my Titchy Zaurus install, expanded the modules*.tgz file to create the new directory (chown -R root:root /lib/modules/2.6.23/)
Tried to reflash with the 2.6.23 kernel and I am getting the same thing.
I did find the decrypter / encrypter for updater.sh. I looked through this but I don't see anything that I would know how to change if something even needs to be changed there. My guess is that the updater.sh file is OK, it is something to do with my system or something I am/am not doing correctly.
Just to recap, I did a NAND restore to my Z, installed Titchy from the howto on Neil's site all the way to having X up and running. Once I found that my Socket Bluetooth card wasn't working, I hit the forums and found that I needed a new kernel. Tried flashing once and used the Titchy updater.sh file and formated my microdrive. NAND flashed once more, and I have a base Titchy install I am working with at the moment. Want to have bluetooth working before I move forward.
That is where I am at right now, once I flash, screen flickers from reboot, I immediately get the following error:
"kernel panic - not syncing: Attempted to kill init!"
Using the same procedure to flash back to Titchy 2.6.20 kernel and the system boots. What am I missing?
~Z3n
Edit: Sitting here thinking about it, thought maybe I needed to change /boot/grub/menu.lst but there is nothing in boot. Assuming that this is all in flash? If this is the case, is the updater.sh script supposed to change the bootloader to load a newly installed kernel? That is the only thing that is hitting me is that the bootloader hasn't been made aware that there is a new kernel and it is panicing because the original (2.6.20) kernel isn't there... Please educate me if I am wrong or not seeing the big picture.
-
Stupid question, have you tried to download zImage again? copied it again into SD? I'd personally try with another angstrom kernel to be sure it is not a specific bogus kernel issue.
-
Well, we are making progress. I grabbed zImage-2.6.23-spitz-20080106230105.bin from Angstrom (different than what I was trying before, thanks Iaan) and flashed and viola, we have 2.6.23 kernel. Booted, ran depmod, rebooted and I have a snippet from dmesg:
NET: Registered protocol family 10
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
pccard: PCMCIA card inserted into slot 1
pcmcia: registering new device pcmcia1.0
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
pcmcia: request for exclusive IRQ could not be fulfilled.
pcmcia: the driver needs updating to supported shared IRQ lines.
ttyS0: detected caps 00000700 should be 00000100
1.0: ttyS4 at I/O 0xc48403f8 (irq = 169) is a 16C950/954
So, going back to page three of the previous mentioned Bluetooth thread regarding "Socket". "CF+ Personal Network Card Rev 2.5", I ran:
# setserial /dev/ttyS4 baud_base 921600
# hciattach -s 921600 /dev/ttyS4 bscp
BCSP initialization timed out
... and from the previous thread it kind of died off at this point. I have searched and found some information from pdaxrom R198 but it didn't pertain to this install.
I have the bluez-utils ver 3.7-1 installed. Am I missing some other package to make this work?
Getting excited, getting closer...
-
Try just doing an "hciattach /dev/ttyS4 socket" after inserting your card; it worked for me when I tried it yesterday.
-
I had no need of using setserial nor using -s just 'hciattach /dev/ttyS4 bcsp' works.
hope it helps
-
pelrun, thank you for that tidbit, that did it. My RAZR was able to find my Z!!!
All, thanks for all for your help. This was my first experience with bluetooth and Linux so thank you for your patience.
I think I have what I need right now, remote access to my systems through my phone using my Z.
Wow factor would be getting a GUI installed and have some apps to show off so we will have to see.
-
just to let you know that "hciattach /dev/ttyS4 socket" worked for me too using a revision H socket/symbol CF bluetooth card. it's not too quick, so I am wondering whether I can influence the speed somewhat?
--edit--
found this, about kernel bug and socket bluetooth
http://www.adamis.de/linux/bt-socket.html (http://www.adamis.de/linux/bt-socket.html)
I can get the hciattach speed up to 230400, and it's a little bit more responsive, it fails to initialise with 460800.