Messages

1

Ubuntu / Hp's "glassy-bleu" Theme

« on: February 12, 2009, 09:02:45 am »

All,

Just ran across this: http://arstechnica.com/open-source/news/20...rce=microbloggi

Might be old news but thinking this would look really nice on a Z

I will try it out on my Z running Omegamoon's Ubuntu install (thanks for that, it is AWESOME!!)

~Z3n

2

Debian / Andromeda Installation

« on: November 14, 2008, 12:30:50 pm »

So I got this installed and I am very pleased with it.  Congratulations Younggun, very nice work.

I have run into a few snags and wanted to see if anyone had a solution

1. Hawking CF Network card (dmesg - NE2000 (DL10022 rev 05) io 0xc4840300, irq 169, hw_addr ...) isn't working.  I have it plugged and and all I am seeing is the RX light flash repeatedly.  Not sure what is going on.  I have assigned and address but it won't transmit.  Never seen this before...

EDIT: Bad network cable, took the 4 one I guess...

2. Socket Bluetooth doesn't work but I don't have network connectivity at the moment (above) to install the bluez packages.

EDIT: So I got sshd installed but it keeps asking me to change my password on login.  How does one stop this behavior?

Any assistance would be appreciated.

3

Ubuntu / Ubuntu/debian Ported To Arm

« on: April 25, 2008, 11:56:58 am »

All,

Just read this, probably old news:

http://linuxdevices.com/news/NS2097004728.html

With this group going through and natively compiling the packages, do we have a ready repository for ubuntu/debian packages for the Zaurus?

~Z3n

4

Debian / Titchy Socket Bluetooth

« on: February 20, 2008, 12:04:52 pm »

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.

5

Debian / Titchy Socket Bluetooth

« on: February 15, 2008, 09:14:00 am »

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...

6

Debian / Titchy Socket Bluetooth

« on: February 14, 2008, 10:38:46 am »

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.

7

Debian / Titchy Socket Bluetooth

« on: February 14, 2008, 09:41:18 am »

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

8

Debian / Titchy Socket Bluetooth

« on: February 06, 2008, 08:26:50 am »

No one can give a direction on an update.sh script that will only flash the kernel and not start formating the microdrive?

9

Debian / Titchy Socket Bluetooth

« on: February 01, 2008, 02:37:25 pm »

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.

10

Debian / Titchy Socket Bluetooth

« 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.

11

Debian / Bricked Z? Please Help - Update Success!

« on: December 21, 2007, 09:39:54 am »

All,

I would like to report SUCCESS!  I have Debian booting on my Z.

Got it hooked up to the network, apt-get upgrade and all that so it is good to go.

Only thing that I am seeming to have difficult with is the suspend/resume function.  Once booted and running and I power off by hitting the power button, I can't get the Z to boot back up without removing the battery and putting it back in.  Z starts booting even before I have the battery cover back in place and locked.

Any suggestions?

12

Debian / Bricked Z? Please Help - Update Success!

« on: December 19, 2007, 05:06:47 pm »

Alright all.  I need some help.  I am following this howto:

https://www.oesf.org/index.php?title=Q19:_I...n_EABI_on_SD%3F

I am at the point of trying to get U-Boot installed and I am not having any luck.  Following these directions and my Z won't respond after flashing u-boot to the system.  I held down the OK key and got booted into the Emergency Linux System.  I poked around and all was good.

The next step is to flash the kernel.  Turn off my Z and perform the reset procedure (after the files are on the CF card and inserted into the Z) and nothing happens.

Frustrating...

Any thoughts or ideas I could try differently?  I know people have had success with this and all I want to do is see the EABI Debian boot.  I had Titchy installed but wanted to try the latest to see it.

13

Debian / Bricked Z? Please Help - Update Success!

« on: December 17, 2007, 09:55:06 am »

All,

Thanks for the advise and encouragement.  Native Debian has been something I have wanted on my Z for some time so I won't be giving up anytime soon.

Good news I can access the emergency menu with the Fn+D+M plug in the power combo so I will be continuing my efforts with the suggestions in this post.

Thanks again everyone.

~Z3n

14

Debian / Bricked Z? Please Help - Update Success!

« on: December 12, 2007, 04:12:55 pm »

All,

Looking for some help here.  I was following the instructions for getting Debian EABI installed on my 3100 from https://www.oesf.org/index.php?title=Q19:_I...n_EABI_on_SD%3F

I got to the point of installing uboot.  I saw the flash happen, held down OK during reboot and was presented a BASH prompt.  Looked around and say that it wasn't my extracted root_fs on /dev/hda1.  So, I rebooted thinking that would help... I am seeing that was hopefully a corrective big mistake.  Now, I have nothing.

What I mean by nothing, I plug in the power cable and I don't get a light...  I am thinking that is bad.  I have tried doing the D + B while installing the battery, that gets me nothing.  Tried D + M while putting in the battery, that gets me nothing.

Someone, please tell me there is a trick that I don't know of to resurrect my Z!!

Thanks in advance.

15

C1000/3x00 General discussions / Ah! Help... Nand Restore Now What...

« on: January 19, 2007, 10:49:23 am »

Ok, I went ahead and removed the battery to get it rebooted... Sharp screen came up and it appeared to be booting...

Rebooted again and flashed to OZ... and I am now looking at Opie 1.2