1
Ubuntu / Size Mismatch On Packages
« on: June 21, 2008, 01:55:02 am »
Hmmm... well at least I'm not losing my mind and someone else is having the same issue.
Select language:
News:
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Ubuntu / Size Mismatch On Packages
« on: June 04, 2008, 04:44:30 pm »
All of a sudden I'm getting size mismatches from the handhelds.org repository when I'm using apt-get. I gave aptitude a shot and it was able to install properly some things that apt-get couldn't but I'm still getting problems. Anyone have any ideas as to what might be wrong?
3
Ubuntu / My Zaurus Ubuntu Install Log
« on: May 31, 2008, 03:04:16 pm »
I started messing around with getting my Ambicom wireless card working. It seemed to load the drivers fine. However, for some reason when I ran ifup wlan0, the dhcp client was not working properly. I kept getting a "execve (/lib/dhcp3-client/call-dhclient-script, …): Permission denied" error.
After a quick google search someone else with the same issue just ran "apt-get install --reinstall dhcp3-client" to fix the issue. That seemed to work for me just fine as well.
After a quick google search someone else with the same issue just ran "apt-get install --reinstall dhcp3-client" to fix the issue. That seemed to work for me just fine as well.
4
Ubuntu / My Zaurus Ubuntu Install Log
« on: May 29, 2008, 06:40:13 pm »
So I've been playing around a little bit more. I've made a whole mess of little scripts to handle creating the virtual qemu drive and untar the rootfs back into it. I also created a script to generate a new tarball when I want. This has made my horrible mistakes... er I mean my testing go much smoother.
Here is what my general install procedure is like.
makezubuntudisk script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
echo Creating zubuntu-qemu image with dd...
dd if=/dev/zero of=zubuntu-qemu bs=1MB count=4096
echo Formatting zubuntu-qemu
sudo mke2fs -F -m 0 -b 1024 zubuntu-qemu[/div]
createrootfs script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
echo Creating qemu directory
mkdir qemu
echo Mounting zubuntu-qemu image at ./qemu
sudo mount -t ext2 -o loop zubuntu-qemu qemu
cd qemu
echo Untarring rootfs to ./qemu. Please wait...
sudo tar -zxpf ../sdinstall/android-root.tar.gz
echo Untar completed.
cd ..
sudo umount qemu[/div]
You will notice that I have an sdinstall directory. This is where I keep the files to put on the SD card for installs. So naturally the android-root.tar.gz file is located there.
startzaurus script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
qemu-system-arm \
-M versatilepb -kernel zImage-versatile-2.6.24-rc7.armv5tel \
-append "root=/dev/sda ip=bootp" \
-hda zubuntu-qemu -localtime -startdate now \
-usbdevice tablet \
-net nic -net user,script=/etc/qemu-ifup[/div]
I've made a few minor changes to Cortez suggestions. I added the -localtime and the -startdate now settings. This sets the date and time for me immediately and I don't have to worry about remembering the set anything with the date command after I startup.
Once I boot into the qemu session I run the follow commands
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']apt-get install less ntpdate enlightenment xinit xdm sylpheed dillo xterm abiword gnumeric thunar menu console-data wireless-config gtkeyboard[/div]
Then I run
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']dpkg-reconfigure tzdata[/div]
and set my timezone appropriately
When I'm working on my PC, the /etc/init.d/keymap file sets the keyboard to use the zaurus keymap. That drives me nuts so I disable that by moving the file out of /etc/init.d. This is temporary and before I create a new rootfs I put it back so the Zaurus has the right keyboard layout.
You can use [div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']dpkg-reconfigure console-data[/div] to reconfigure your keyboard to your PC's setup.
I then setup a user ID and passwords
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']passwd #set the root password
useradd -d /home/suttonca suttonca #create a normal user id
usermod suttonca -G users dialout voice cdrom sudo audio video games suttonca[/div]
When I've got things configured they way on want from qemu I run the following script to create a new rootfs.
makerootfs script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
echo Mounting image to qemu
sudo mount -t ext2 -o loop zubuntu-qemu qemu
cd qemu
echo Creating tarball...
sudo tar -czpf ../zubuntu-custom-rootfs.tar.gz .
cd ..
sudo umount qemu
echo Removing previous tarball
rm sdinstall/android-root.tar.gz
echo Moving new tarball to sdinstall directory
mv zubuntu-custom-rootfs.tar.gz sdinstall/android-root.tar.gz
echo Completed.[/div]
Well that's my update for now. I'm going to create a new rootfs with all that in it and try it out!
Here is what my general install procedure is like.
makezubuntudisk script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
echo Creating zubuntu-qemu image with dd...
dd if=/dev/zero of=zubuntu-qemu bs=1MB count=4096
echo Formatting zubuntu-qemu
sudo mke2fs -F -m 0 -b 1024 zubuntu-qemu[/div]
createrootfs script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
echo Creating qemu directory
mkdir qemu
echo Mounting zubuntu-qemu image at ./qemu
sudo mount -t ext2 -o loop zubuntu-qemu qemu
cd qemu
echo Untarring rootfs to ./qemu. Please wait...
sudo tar -zxpf ../sdinstall/android-root.tar.gz
echo Untar completed.
cd ..
sudo umount qemu[/div]
You will notice that I have an sdinstall directory. This is where I keep the files to put on the SD card for installs. So naturally the android-root.tar.gz file is located there.
startzaurus script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
qemu-system-arm \
-M versatilepb -kernel zImage-versatile-2.6.24-rc7.armv5tel \
-append "root=/dev/sda ip=bootp" \
-hda zubuntu-qemu -localtime -startdate now \
-usbdevice tablet \
-net nic -net user,script=/etc/qemu-ifup[/div]
I've made a few minor changes to Cortez suggestions. I added the -localtime and the -startdate now settings. This sets the date and time for me immediately and I don't have to worry about remembering the set anything with the date command after I startup.
Once I boot into the qemu session I run the follow commands
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']apt-get install less ntpdate enlightenment xinit xdm sylpheed dillo xterm abiword gnumeric thunar menu console-data wireless-config gtkeyboard[/div]
Then I run
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']dpkg-reconfigure tzdata[/div]
and set my timezone appropriately
When I'm working on my PC, the /etc/init.d/keymap file sets the keyboard to use the zaurus keymap. That drives me nuts so I disable that by moving the file out of /etc/init.d. This is temporary and before I create a new rootfs I put it back so the Zaurus has the right keyboard layout.
You can use [div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']dpkg-reconfigure console-data[/div] to reconfigure your keyboard to your PC's setup.
I then setup a user ID and passwords
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']passwd #set the root password
useradd -d /home/suttonca suttonca #create a normal user id
usermod suttonca -G users dialout voice cdrom sudo audio video games suttonca[/div]
When I've got things configured they way on want from qemu I run the following script to create a new rootfs.
makerootfs script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
echo Mounting image to qemu
sudo mount -t ext2 -o loop zubuntu-qemu qemu
cd qemu
echo Creating tarball...
sudo tar -czpf ../zubuntu-custom-rootfs.tar.gz .
cd ..
sudo umount qemu
echo Removing previous tarball
rm sdinstall/android-root.tar.gz
echo Moving new tarball to sdinstall directory
mv zubuntu-custom-rootfs.tar.gz sdinstall/android-root.tar.gz
echo Completed.[/div]
Well that's my update for now. I'm going to create a new rootfs with all that in it and try it out!
5
Debian / Working Sip Client?
« on: May 13, 2008, 11:07:55 pm »
I'm pretty sure that people have successfully run Kphone on the Zaurus. See this section on the wiki. https://www.oesf.org/index.php?title=Distri...ns#Applications.
6
Ubuntu / My Zaurus Ubuntu Install Log
« on: May 13, 2008, 10:58:31 pm »
I have to restart 3 times before I get a console that I can log into. I get a fsck run right away that is rather annoying with a reboot. Then I get a kernel panic so I restart. Then it works all of a sudden. I'm pretty sure this has to do the the date being set to 1970. I tried adding -localtime to the qemu command line parameters but that didn't seem to fix it really. I imagine this won't happen on the real hardware.
Once I login I run the following:
icewm - pretty ugly at the moment, but it launches just fine.
Firefox - doesn't launch. It nails the cpu for a while and then nothing happens. I think maybe there isn't enough memory perhaps? Seems to me that I need to set qemu to 64mb RAM and setup a swap file to make things more similar to my c3000.
xterm - it works fine.
What is everyone else running? What's working? What's not? I'm so stoked about this! I hope I can find more time tomorrow to mess around and get a few more things working. I think I'm going to setup a bzr repository of my tarball so I can recover from the massively huge mistakes I'll be making over the next few weeks .
Later,
Chad
Once I login I run the following:
- date -s "05/13/2008" #set to the current date
- apt-get install ntpdate #need to check if this adds it into cron
- tzselect #follow the prompts
- apt-get update
- apt-get upgrade
- apt-get install less #I can't get along with out it
- apt-get install icewm
- apt-get install firefox
- apt-get xterm
icewm - pretty ugly at the moment, but it launches just fine.
Firefox - doesn't launch. It nails the cpu for a while and then nothing happens. I think maybe there isn't enough memory perhaps? Seems to me that I need to set qemu to 64mb RAM and setup a swap file to make things more similar to my c3000.
xterm - it works fine.
What is everyone else running? What's working? What's not? I'm so stoked about this! I hope I can find more time tomorrow to mess around and get a few more things working. I think I'm going to setup a bzr repository of my tarball so I can recover from the massively huge mistakes I'll be making over the next few weeks .
Later,
Chad
7
Debian / U-boot Bricking My C3000
« on: November 14, 2007, 07:24:59 pm »
I'm following the 2.6.23.1 yonggun with uboot guide on the wiki.
The process for installing uboot always results in a bricking my c3000. After the uboot procedure, the orange charging light does not even go on. I have to restore the Sharp nand at that point. It does seem to boot on the local disk to a text prompt before I attempt to flash to the uboot update. I can login as root there, so the previous steps in that doc seem to be working.
I've reformatted the SD card to just a 128mb fat16 partition and used that for the uboot procedure. I had read that it was best to do that for the Sharp ROM to be able to read it properly.
Anyone else having issues with uboot like this? If so, what can I do to get around it?
The process for installing uboot always results in a bricking my c3000. After the uboot procedure, the orange charging light does not even go on. I have to restore the Sharp nand at that point. It does seem to boot on the local disk to a text prompt before I attempt to flash to the uboot update. I can login as root there, so the previous steps in that doc seem to be working.
I've reformatted the SD card to just a 128mb fat16 partition and used that for the uboot procedure. I had read that it was best to do that for the Sharp ROM to be able to read it properly.
Anyone else having issues with uboot like this? If so, what can I do to get around it?
8
C1000/3x00 Hardware / Vnc
« on: February 14, 2005, 10:57:28 pm »
I ran into the same problem with vnc. I used the fbvncserver-sl5500_0.9.4_arm.ipk. I get all kinds of strange things happening. My screen stopped responding to the stylus. I couldn't launch programs either.
I'm not sure what's wrong but if I figure something out I'll post it here.
Later
I'm not sure what's wrong but if I figure something out I'll post it here.
Later
Pages: [1]