OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Debian => Topic started by: ZDevil on October 27, 2007, 02:56:15 pm
-
[size=]A[/size] Debian/Zaurus installation guide (for all C-series models)
Version 0.3 W.I.P. (071101)
Compiled by a random nameless rogue user joe , Contributed by yet more random nameless rogue users joez .
This guide has been posted on the OESF wiki (https://www.oesf.org/index.php?title=Debian/Zaurus_installation_guide_%28for_all_C-series_models%29) and is no longer be maintained.
[size=]Notes:
-- This guide is still at a draft stage and is not error-proof. DO NOT hesitate to point out any error/mistake/inaccuracy and the guide will be updated as quickly as possible.
-- You only need to refer the first two pages of this thread if you don't have much time. Most issues arising from the disccussion in the ensuing pages have been resolved and the results integrated into these first two pages.[/size][/color]
=============
Changelog (071101):
1. Updated zaurus-debian-eabi-afterinstall to 1.1 (for kernel 2.6.23.1 yonggun ONLY) and uploaded in Post #13 (Q12), including the following fixes:
-- Added apmd and libsdl1.2debian-alsa installation instructions in the 2nd-cfg.sh. (Thanks, jpmatrix!)
-- Fixed inserting loadkeys line in /etc/rc.local in 1st-cfg.sh (Thanks, tux!)
-- Fixed package feed locations in sources.list (Thanks, jpmatrix and zecrazytux!)
-- Moved hardware clock setting from 2nd-cfg.sh to 1st-cfg.sh (Thanks, tux!)
Many many thanks goes to 2or0 (yonggun) for his major contribution to the after installation tarball.
2. Added instruction to resolve opening initial console failure upon the very first boot (Thanks, jpmatrix!)
Changelog (071031):
2. Revised and simplified the EABI after installation processes (Q16-Q20).
3. Added installation method of Debian EABI on SD for C1000. (Q20)
Changelog (071029):
1. Added basic after installation instructions to Debian EABI installation.
2. Added & updated (i think it's better to use the same versioning for both).
3. Cleared up some redundancies and inconsistencies in the instructions.
=============
Q: What is this all about? Why should I read this?
A: This is a kinda "rogue guide" to how to get a full Debian installed on your Zaurus. I assume that you:
1. You have a Zaurus;
2. You fancy playing Debian for real on your Zaurus.
Q: How is this guide organized?
A: This guide will walk you through the methods of installing a real Debian on your Zaurus.
It is a bit long, but actually you are not supposed to read it all.
You will be prompted a few questions (Q8-Q12) and you will then know where to continue.
For fresh beginners, please read from Q1 onwards.
For experienced users who just want to check out and review the installation procedures, simply jump directly to the relevant question.
Q1: What the heck is this Debian game all about? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170040)
Q2: So is there only one way to do that (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170041)?
Q3: What are OABI and EABI? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170042)
Q4: What if I want to know more about OABI and EABI in Debian? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170043)
Q5: How many ways can I enjoy real Debian on my Zaurus? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170044)
Q6: So are there just one OABI kernel, one EABI kernel, one OABI system and one EABI system (for running on the Zaurus)? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170045)
Q7: Tell me more about the choice of the kernels. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170046)
Q8: How do I know which kernel I should use? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170047)
Q9: I want to run an OABI system (Etch or Lenny or Sid). Which kernel should I use? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170048)
Q10: I’ve already got the right kernel. Where can I get the Debian OABI system? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170049)
Q11: I want to install the Debian EABI system. Which kernel should I use? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170050)
Q12: I've already got the right kernel. Where can I get the Debian EABI system? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170051)
Q13: I am using a Cxx0 or C1000. How can I install Debian OABI to my SD card? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170052)
Q14: I am using a C3x00. How can I install Debian OABI on the internal drive using the CD image? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170053)
Q15: I am using a C3x00. How can I install Debian OABI on the internal drive using the rootfs tarball? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170054)
Q16: I am using a Cxx0 or C1000. How can I install Debian EABI to my SD card? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170055)
Q17: I am using a C3x00. How can I install Debian EABI on the internal drive? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170056)
Q18: I am using a C3x00, and I want to use kernel 2.6.23.1 yonggun with uboot. How can I install Debian EABI on the internal drive? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170057)
Q19: I am using a C3x00, and I want to use kernel 2.6.23.1 yonggun with uboot. How can I install Debian EABI on SD? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170058)
Q20: I am using a C1000, and I want to use kernel 2.6.23.1 yonggun with uboot. How can I install Debian EABI on SD? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170059)
Q??: So at the end of the days, which one is the best? (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170060)
-
Q1: What the heck is this Debian game all about?
A1: It’s all about installing a full Debian and getting Debian working on your Zaurus. In the past there was a Debian Pocketworkstation that runs as a system chrooted system in Sharp/Cacko rom. http://www.pocketworkstation.org/ (http://www.pocketworkstation.org/) http://wiki.debian.org/PocketWorkstation (http://wiki.debian.org/PocketWorkstation) (The system it uses is Debian 3.0 codenamed ‘Sarge’)
And now users can run a full native Debian (Etch, Lenny, Sid) on the Zaurus!
(About Debian: http://www.debian.org/index.html (http://www.debian.org/index.html) )
Want to know more? Read on.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q2: So is there only one way to do that?
A2: Not really. Over the last few months the playground has expanded quickly. The many interesting cases are all derived from the combos of two ‘things’:
OABI (kernel/system) + EABI (kernel/system)
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q3: What are OABI and EABI?
A3: They are two kinds of ABI (Application Binary Interface). The ‘O’ stands for ‘Old’, and the ‘E’ means ‘Embedded’, a new approach to API for portable devices like the Zaurus.
According to http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2305 (http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2305)
GNU EABI is a new application binary interface (ABI) for Linux. It is part of a new family of ABI's from ARM® Ltd. known in the arm-linux community as EABI (or sometimes Embedded ABI).
……
According to Debian Wiki the new EABI:
* Allows mixing softfloat and hardfloat code.
* Uses a more efficient syscall convention.
* Will be more compatible with future tools.
Furthermore, the GCC default for EABI will be to use softfloat instructions for floating point arithmetic.
……
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q4: What if I want to know more about OABI and EABI in Debian?
A4: Ok, here is a very informal sketch. The Debian OABI is still the mainstream version. You can choose to run Etch (stable release but a bit dated), Lenny (testing & current) or Sid (unstable but the latest). The Debian EABI system, on the other hand, is the ‘armel’ line only in the ‘Sid’ branch of Debian. Do a simple search in the Debian package brower and you will see it. http://www.debian.org/distrib/packages#search_packages (http://www.debian.org/distrib/packages#search_packages)
An EABI system is built to work with an EABI kernel.
I am no guru or hacker but there are some good places to check out. You can educate yourselves by reading these:
http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2305 (http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2305)
http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2442 (http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2442)
http://en.wikipedia.org/wiki/Application_binary_interface (http://en.wikipedia.org/wiki/Application_binary_interface)
http://linuxdevices.com/articles/AT5920399313.html (http://linuxdevices.com/articles/AT5920399313.html)
http://wiki.emqbit.com/eabi-oabi-benchmark (http://wiki.emqbit.com/eabi-oabi-benchmark)
http://people.debian.org/~terpstra/message...f1eb465.en.html (http://people.debian.org/~terpstra/message/20070319.192931.7f1eb465.en.html)
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q5: Wow. That sounds so complicated. So how many ways can I enjoy real Debian on my Zaurus?
A5: Many. There are four logical possibilities (2x2). But in fact you can’t use an OABI kernel to run an EABI system, so just three combos:
OABI kernel + OABI system
EABI kernel + OABI system
EABI kernel + EABI system
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q6: So are there just one OABI kernel, one EABI kernel, one OABI system and one EABI system (for running on the Zaurus)?
A6: In our case, there are one OABI and one EABI system to install, but there are many kernels to choose from.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q7: Tell me more about the choice of the kernels.
A7: Of course! For the kernels, there are three things to pay attention to:
1. Their versions;
2. whether they are OABI or EABI;
3. which Zaurus models they are for.
They are all the new 2.6.xx kernels. Now what we have are:
(Remember, you must have both the kernel image AND the kernel module tarball (if available), and their version must match.)
[size=]OABI kernel:[/size][/u]
2.6.21 Cortez’s rebuilt Poky kernel: https://www.oesf.org/forum/index.php?showto...st&p=169770 (https://www.oesf.org/forum/index.php?showtopic=24935&view=findpost&p=169770) (For C3x00)
[size=]EABI kernels: [/size]
2.6.17 with fastfpe and cpufreq kernel (from Angstrom): http://www.bigbridgezau.sakura.ne.jp/wiki....Debian%2DTitchy (http://www.bigbridgezau.sakura.ne.jp/wiki.cgi?page=%B8%BC%C8%A2Debian%2DTitchy)
2.6.20 with fastfpe and cpufreq kernel (from Angstrom): http://www.bigbridgezau.sakura.ne.jp/dev/debian/ (http://www.bigbridgezau.sakura.ne.jp/dev/debian/) (for C3x00 only)
2.6.20 ‘titchy’ kernel (from Angstrom): http://wiki.neilandtheresa.co.uk/Titchy_Linux/Installing (http://wiki.neilandtheresa.co.uk/Titchy_Linux/Installing) (for C3x00 only)
2.6.21 Angstrom kernel (For C1000 and Cxx0; also you need the whole Angstrom system to install on NAND first; removed from the Angstrom site; uploads in this forum seem to have expired and gone; will upload again if requested)
2.6.21 Poky kernels http://pokylinux.org/releases/blinky-3.0/ (http://pokylinux.org/releases/blinky-3.0/) (for ALL the C-series models)
2.6.23 Angstrom(latest!) http://www.angstrom-distribution.org/unstable/images/ (http://www.angstrom-distribution.org/unstable/images/) (Check out the folders dated 24-Oct-2007 for Spitz (=C3x00); the one for C7x0 is reported to have issues with Altboot – see Q13)
2.6.23.1 yonggun kernel with fastfpe and cpufreq support (the latest latest!) (2or0’s patched build from Angstrom; requires uboot but works great; free of stylus pointer jumping; built for use with EABI system): http://yonggun.tistory.com/57 (http://yonggun.tistory.com/57) (for C3x00; compatibility with C1000 is to be verified)
autoboot.sh here: https://www.oesf.org/forum/index.php?act=at...ost&id=4969 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4969)
[Special installation method: See Q18-Q20]
(Remember, you must have both the kernel image AND the kernel module tarball (if available), and their version must match.)
For all the kernels (except 2.6.23.1 yonggun), you also have to download the updater.sh script from the same download location.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q8: Waitwaitwaitwaitwait~~! How do I know which kernel I should use?
A8: Good question! Ask yourself:
1. Do I want to run the OABI [Q9 & Q10] or the EABI system [Q11 & Q12]?
2. What machine am I using? (Yes, it’s not all too stupid because you must not confuse the kernels!) [Take note of Q7 again]
3. Is Debian going to run on the internal driver (microdrive/CF) or on SD? [Q13 to Q20]
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q9: I want to run an OABI system (Etch or Lenny or Sid). Which kernel should I use?
A9: In principle, you can use all the available kernels to run the OABI system, but using an OABI kernel should avoid most compatibility issues between EABI kernels and the OABI system.
If you are using Cxx0 and C1000, then you should use the 2.6.21 Angstrom kernel or 2.6.23.1 yonggun kernel. Running the system on the SD and the internal driver involve different installation methods.
Proceed to Q10.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q10: I’ve already got the right kernel. Where can I get the Debian OABI system?
A10: It depends on how you want to install it. There are two ways to install the system.
The first method is to install it in the same way as how Debian is installed on laptops and desktops by using an installer CD image with network connection. For the Zaurus, the smallest businesscard CD image for ARM will suit the purpose. Download it here: http://www.debian.org/releases/etch/debian-installer/ (http://www.debian.org/releases/etch/debian-installer/)
The other way is to install it locally by extracting a rootfs tarball (containting the whole base system ‘Etch’) to the SD card or internal drive. Get the hddrootfs.tar.gz (the system tarball) and gnu-tar (to extract the tarball automatically during installation) here: http://www.bigbridgezau.sakura.ne.jp/dev/debian/ (http://www.bigbridgezau.sakura.ne.jp/dev/debian/).
If you are using Cxx0 or C1000 and want to install Debian OABI on SD, go to Q13 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170052).
If you are using C3x00 if you install Debian OABI on the internal drive using the CD image, go to Q14 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170053).
If you are using C3x00 if you install Debian OABI on the internal drive using the rootfs tarball, go to Q15 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170054).
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q11: I want to install the Debian EABI system. Which kernel should I use?
A11: As of the time of writing, a lot of testing and discussions are still going on. In principle all the EABI kernels will do and work well with the EABI system. Actually if you are using C3x00, you don’t have to worry too much about the choice, because you can always install another kernel later without reinstalling the system.
[One thing remains to be verified though is to switch after installing 2or0’s kernel, which installs via pdaXrom’s uboot, while all the others are installed via the common Flash Menu. More on installation methods later.]
But if you are using Cxx0 or C1000, then you have to install the Angstrom 2.6.21 kernel AND the system (see Q7) in NAND because you will need the Angstrom Altboot to boot Debian of SD.
Go to Q12.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q12: I've already got the right kernel. Where can I get the Debian EABI system?
A12: You will extract the rootfs tarball and install it locally. Get the rootfs tarball here: http://armel.applieddata.net/developers/li...root-fs.tar.bz2 (http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2)
Here is an after installation tarball containing some essential packages and scripts that will greatly simplify the process of configurations and finetuning after installing the kernel and the rootfs system: [ You are not allowed to view attachments ] [See the relevant entry below for how to apply it.]
If you are using Cxx0 or C1000 and want to install Debian EABI on SD, go to Q16 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170055).
If you are using C3x00 and want to install any EABI kernel (except 2.6.23.1 yonggun) and Debian EABI on the internal drive, go to Q17 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170056).
If you are using C3x00 and want to install any EABI kernel (except 2.6.23.1 yonggun) and Debian EABI on SD, go to Q18 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170057).
If you are using C3x00 and want to install kernel 2.6.23.1 yonggun and Debian EABI on the internal drive, go to Q19 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170058).
If you are using C3x00 and want to install kernel 2.6.23.1 yonggun and Debian EABI on SD, go to Q20 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170059).
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q13: I am using a Cxx0 or C1000. How can I install Debian OABI to my SD card?
A13: The installation comes in two parts. I) Install the Angstrom kernel & Angstrom system; II) Install the Debian system
[The method described here is based on Chero’s post]
==========
Preparation
==========
1. Install the Angstrom 2.6.21 kernel & system in NAND flash area.
1a. Remove baterry, wait 5 secs, place battery and attach AC power.
1b. Press "OK" key and keep it pressed, then press "On/Off" button.
1c. In the maintenance menu, choose "4" (Update) in the first screen, "2" (SD) in the second and "Y" in the third
1d. The kernel will be flashed and Zaurus will be rebooted
[Note: if your Zaurus is running the new pdaXrom versions with uboot, then you have to do a NAND Restore to revert to the factory stock rom in order to flash this kernel.]
[The 2.6.22 kernel (2.6.23 yet to be verified) has troubles with altboot, so don't use it for now unless you know how to solve the problems.]
==========
Installation
==========
2. Install the Debian system
2.1 Repartition and reformat the SD :
-- Create a linux partition on the SD (for details see: https://www.oesf.org/index.php?title=Multip..._a_CF_/_SD_card (https://www.oesf.org/index.php?title=Multiple_partitions_on_a_CF_/_SD_card) )
-- Format the partition : mkfs.ext3 /dev/mmcblk0p1
2.2 Put the system to the SD
-- get the rootfs from http://www.bigbridgezau.sakura.ne.jp/dev/debian/ (http://www.bigbridgezau.sakura.ne.jp/dev/debian/)
-- untar it to the root of the SD: Run "tar -xvzpf hddrootfs.tar.gz"
2.3 Put the 2.6.21 kernel modules to the SD
- copy /lib/modules from your NAND to the same location on the SD (/media/card/lib/modules)
2.4 Modify some system setting files in the Debian system
The debian boot process looks for init.sysvinit instead of init, so :
cd /media/card/sbin and "ln -s init init.sysvinit"
You need to change the mounted root from the standard /dev/hda1 (Microdrive) for titchy to /dev/mmcblk0p1 (SD-card)
- cd /media/card/etc and edit fstab to make /dev/mmcblk0p1 mount to / and make it bootable. (Also disable the /dev/hdaX entries because you don't have a microdrive)
2.5 Still in Angstrom : Connect to the net, do an "ipkg update" and then "ipkg install altboot"
[Notes : You'll have to edit network settings before you can reach your network (/etc/network/interfaces; /etc/resolv.conf contains some kuro-specific-things)]
==========
1st boot
==========
3.1 Reboot and hit the "any" key when asked to launch altboot then choose "boot from SD"
(the "any" key is the 35th key counting diagonal from the lower left corner or maybe some other key)
3.2 1st login
Login: root
Root password : kuroadmin
[I didn't know this when I first installed it, so I edited /media/card/etc/shadow while running Angstrom and removed the password for root (remove everything between the first ":" and the second ":" on the line beginning with "root")
3.3 Install udev
I don't think udev is installed by default -> first time fiddle with modprobe to load the correct drivers (modprobe orinoco_cs or modprobe hostap_cs), configure your network and then "apt-get install udev"
3.4 Modify /etc/apt/sources.list
You'd better edit /etc/apt/sources.list as well if you don't want to download everything from a japanese server and affect internet speed everywhere between you and Japan or if you want to upgrade to Lenny.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q14: I am using a C3x00. How can I install Debian OABI on the internal drive using the CD image?
A14: Follow the instructions here: http://wiki.neilandtheresa.co.uk/Titchy_Linux/Installing (http://wiki.neilandtheresa.co.uk/Titchy_Linux/Installing)
And this Flickr slideshow shows the whole process (click on the pictures to see more descriptions): http://www.flickr.com/photos/50659119@N00/...157702606/show/ (http://www.flickr.com/photos/50659119@N00/sets/72157602157702606/show/)
(I will add more details here soon)
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q15: I am using a C3x00. How can I install Debian OABI on the internal drive using the rootfs tarball?
A15: The installation has three parts
1. Prepare the SD installer; 2. Prepare the internal drive; 3. Flash the kernel and install the system
==========
Preparation
==========
1. Prepare the SD installer
Download the following four files from http://www.bigbridgezau.sakura.ne.jp/dev/debian/ (http://www.bigbridgezau.sakura.ne.jp/dev/debian/) and copy them to the root of SD:
i. updater.sh
ii. gnu-tar
iii. zImage-2.6.17-cpufreq-fastfpe.bin OR zImage-2.6.20-cpufreq.bin (This is the kernel; rename it to zImange.bin)
iv. hddrootfs.tar.gz (This is the base system and Etch; rename it to hdimage1.tgz)
2. Prepare the internal drive
2.1 Boot into Linux Emergency Mode (remove power sources, press B and D while putting back the battery & lock the cover switch & power on). Login as root.
2.2 Repartition the internal drive using fdisk /dev/hda (how-to: https://www.oesf.org/index.php?title=Multip..._a_CF_/_SD_card (https://www.oesf.org/index.php?title=Multiple_partitions_on_a_CF_/_SD_card) ). Create two partitions. /dev/hda1 is the root partition (ext3); /dev/hda2 is the swap partition (default ~180.9MB in Debian CD installation, but you can make a bigger swap partition if you want to run very resource-hungry programs, or do onboard compilation).
2.3 Reformat the partitions:
mke2fs -j /dev/hda1
mkswap /dev/hda2
==========
Installation
==========
3. Flash the kernel and install the rootfs
3.1. Remove baterry, wait 5 secs, place battery and attach AC power.
3.2. Press "OK" key and keep it pressed, then press "On/Off" button.
3.3. In the maintenance menu, choose "4" (Update) in the first screen, "2" (SD) in the second and "Y" in the third
3.4. First the kernel will be flashed. Next the system tarball will be extracted to the internal drive. And then Zaurus will be rebooted. Debian is ready to go!
==========
1st boot
==========
4. 1st login
Login: root
Root password: kuroadmin
5. Do some initial system settings
5.1 Edit /etc/fstab to make sure the root filessystem, swap partition and other things are mounted properly.
5.2 From now on you will need network connection to update and upgrade the system.
6. Set up network connection
Set up your network profile in /etc/network/interfaces and /etc/resolv.conf, blacklist hostap if you are using Ambicom WL1100C (for details see this post: https://www.oesf.org/forum/index.php?act=fi...&pid=168621 (https://www.oesf.org/forum/index.php?act=fi...&pid=168621) ).
You can then do the postinstallation steps as descibed in "After installation" in the titchy linux wiki: http://wiki.neilandtheresa.co.uk/Titchy_Linux/Installing (http://wiki.neilandtheresa.co.uk/Titchy_Linux/Installing)
7. System upgrade: to Lenny (recommended) or Sid (for the brave hearts)
7.1 In /etc/apt/sources.list, change "etch" to "lenny" or “sid”
7.2 Run "apt-get update" in the terminal
7.3 Run "apt-get dist-upgrade" in the terminal
==========
Change kernels
==========
If you want to switch to other kernels,
a. first extract and copy the corresponding kernel modules to /lib/modules
b. Prepare the correct kernel image (zImage.bin) and updater.sh and install them in the Flash Menu again.
Note: this method work for all kernel except 2.6.23.1 yonggun, which uses uboot to install, for details see Q18-20.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q16: I am using a Cxx0 or C1000. How can I install Debian EABI to my SD card?
A16: The installation comes in two parts. 1. Install the Angstrom kernel & Angstrom system; 2. Install the Debian EABI system
Note:
-- If your Zaurus is already running with uboot (such as the new pdaXrom versions), then you have to do a NAND Restore to revert to the factory stock rom in order to flash this kernel.
-- If you want to keep using uboot, go to Q20 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170059) now.
-- The 2.6.22 kernel (2.6.23 yet to be verified) has troubles with altboot, so don't use it for now unless you know how to solve the problems.
==============================
Install the Angstrom kernel & Angstrom system
==============================
1. Install the Angstrom 2.6.21 kernel & system in NAND flash area.
1a. Remove baterry, wait 5 secs, place battery and attach AC power.
1b. Press "OK" key and keep it pressed, then press "On/Off" button.
1c. In the maintenance menu, choose "4" (Update) in the first screen, "1" (CF) in the second and "Y" in the third
1d. The kernel will be flashed and Zaurus will be rebooted.
====================
Install the Debian EABI system
====================
2. Install the Debian system
2.1 Repartition and reformat the SD :
a. Create a linux partition on the SD (for details see: https://www.oesf.org/index.php?title=Multip..._a_CF_/_SD_card (https://www.oesf.org/index.php?title=Multip..._a_CF_/_SD_card) )
b. Format the partition:
mkfs.ext3 /dev/mmcblk0p1a. Get the rootfs from http://armel.applieddata.net/developers/li...root-fs.tar.bz2 (http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2)
b. Uncompress it to the root of the SD:
tar -xvzpf hddrootfs.tar.gz2.3 Put the 2.6.21 kernel modules on the SD
Copy /lib/modules from your NAND to the same location on the SD (/media/card/lib/modules)
2.4 Modify some system setting files in the Debian system
The debian boot process looks for init.sysvinit instead of init, so :
cd /media/card/sbin and "ln -s init init.sysvinit"You need to change the mounted root from the standard /dev/hda1 (Microdrive) for titchy to /dev/mmcblk0p1 (= SD card)
Eit /etc/fstab to make /dev/mmcblk0p1 mount to / and make it bootable. (Remember to remove the lines mounting /dev/hdaX to / because you don't have a microdrive)
2.5 Still in Angstrom : Connect to the net, run
ipkg update && ipkg install altboot[Notes : You'll have to edit network settings before you can reach your network (/etc/network/interfaces; /etc/resolv.conf contains some kuro-specific-things)]
====================
1st boot: System configuration
====================
3. Reboot
Reboot and hit the "any" key when asked to launch altboot then choose "boot from SD"
(the "any" key is the 35th key counting diagonal from the lower left corner or maybe some other key)
At this stage, booting may fail and complain about being "unable to open an initial console".
If that is the case, do this:
cd ../dev ## use the [Tab] key to help you find "/"
MAKEDEV consoleAfter that, reboot again.
4. 1st login
Login: root
Root password : (no password)
5. Set up date and time
date MMDDHHMMYYYY ##Example: 102906572007
6. After installation configurations
Please see this thread: https://www.oesf.org/forum/index.php?showtopic=24941 (https://www.oesf.org/forum/index.php?showtopic=24941)
And perhaps you may also be interested to check out this after installation tarball and script (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170109), which may save you some time extracting stuff from the Angstrom and pdaXrom packages.
==========
Change kernels
==========
If you want to switch to other kernels,
a. First extract and copy the corresponding kernel modules to /lib/modules
b. Prepare the correct kernel image (zImage.bin) and updater.sh and install them in the Flash Menu again.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q17: I am using a C3x00. How can I install Debian EABI on the internal drive?
A17: First, you have to use an EABI kernel (See Q7). If you are using kernel 2.6.23.1 yonggun, go to Q18 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170057) now. Otherwise, read on.
The installation has four parts.
1. Prepare the installer files; 2. Prepare the internal drive; 3. Extract the system rootfs tarball to the internal drive; 4. Flash the kernel
==========
Preparation
==========
1. Prepare the SD installer
1.1 The kernel:
Download and copy an EABI kernel, its corresponding updater.sh, and kernel module tarball (if available) to an SD card.
1.2 The EABI rootfs:
a. Download the armel rootfs tarball to another computer
http://armel.applieddata.net/developers/li...root-fs.tar.bz2 (http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2) .
b. Uncompress the bz2 format: tar –zjf armel-root-fs.tar.bz2 to get the armel-root-fs.tar.
c. Copy it to the SD.
2. Prepare the internal drive
2.1 Boot into Linux Emergency Mode
a. Rremove power sources
b. Press B and D while putting back the battery & lock the cover switch & power on).
c. In the command prompt, login as "root".
2.2 Repartition the internal drive using fdisk /dev/hda (how-to: https://www.oesf.org/index.php?title=Multip..._a_CF_/_SD_card (https://www.oesf.org/index.php?title=Multiple_partitions_on_a_CF_/_SD_card) ). Create two partitions. /dev/hda1 is the root partition (ext3); /dev/hda2 is the swap partition (default ~180.9MB in Debian CD installation, but you can make a bigger swap partition if you want to run very resource-hungry programs, or do onboard compilation).
2.3 Reformat the partitions:
mke2fs -j /dev/hda1
mkswap /dev/hda2
==========
System Installation
==========
3. Extract the system rootfs tarball, kernel modules and after installation files to the internal drive
a. mount /dev/hda1 /mnt/cf (mkdir /mnt/cf if necessary)
b. Plug in the SD card with armel-root-fs.tar and modules-xxx.tar.gz.
c. cd /mnt/card
d. cp armel-root-fs.tar modules-xxx.tar.gz /zaurus-debian-eabi-afterinstall_1.0b.tar.gz mnt/cf
e. cd /mnt/cf
f. tar -xvpf armel-root-fs.tar
g. cd armel-root-fs
h. mv ./* ../
i. cd ..
j. tar -xvpzf modules-xxx.tar.gz
k. rm -r armel-root-fs armel-root-fs.tar modules-xxx.tar.gz
l. reboot while pressing the [OK] button.
4. Flash the kernel
Now the Zaurus will boot into the Flash Menu
a. In the Japanese menu, choose "4" (Update) in the first screen, "2" (SD) in the second and "Y" in the third
b. The kernel will be flashed and Zaurus will be rebooted. Debian EABI is ready to go!
====================
1st boot: System configuration
====================
Note: The first booting may fail and complain about being "unable to open an initial console".
If that is the case, boot into the Linux Emergency mode and do this:
mount /dev/hda1 /mnt/cf
cd /mnt/cf/dev
MAKEDEV consoleAfter that, reboot again.
5. 1st login
Login: root
Root password : (no password)
6. Set up date and time
date MMDDHHMMYYYY ##Example: 102906572007
7. After installation configurations
Please see this thread: https://www.oesf.org/forum/index.php?showtopic=24941 (https://www.oesf.org/forum/index.php?showtopic=24941)
And perhaps you may also be interested to check out this after installation tarball and script (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170109), which may save you some time extracting stuff from the Angstrom and pdaXrom packages.
==========
Change kernels
==========
If you want to switch to other kernels,
a. First extract and copy the corresponding kernel modules to /lib/modules
b. Prepare the correct kernel image (zImage.bin) and updater.sh and install them in the Flash Menu again.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q18: I am using a C3x00, and I want to use kernel 2.6.23.1 yonggun with uboot. How can I install Debian EABI on the internal drive?
A18: The installation comes in four parts: 1. Prepare the internal drive; 2. Install the EABI rootfs; 3. Install uboot; 4. Flash the kernel
==========
Preparation
==========
1. Prepare the internal drive
[Note: If you are already using the new pdaXrom versions using uboot, you can simply repartition and reformat the internal drive without using the method below. Go directly to 5.]
2. Boot into Linux Emergency Mode
a. Remove power sources,
b. Press B and D while putting back the battery & lock the cover switch & power on.
c. In the command prompt, login as root.
3. Repartition the internal drive using fdisk /dev/hda (how-to: https://www.oesf.org/index.php?title=Multip..._a_CF_/_SD_card (https://www.oesf.org/index.php?title=Multiple_partitions_on_a_CF_/_SD_card) ). Create two partitions. /dev/hda1 is the root partition (ext3); /dev/hda2 is the swap partition (default ~180.9MB in Debian CD installation, but you can make a bigger swap partition if you want to run very resource-hungry programs, or do onboard compilation).
4. Reformat the two partitions:
mke2fs -j /dev/hda1
mkswap /dev/hda2
============
System Installation
============
5. Install the system rootfs, kernel modules and after installation files to the internal drive
a. mount /dev/hda1 /mnt/cf (mkdir /mnt/cf if necessary)
b. Plug in the SD card with armel-root-fs.tar (http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2) (first uncompress the .bz2 format), modules-2.6.23.1-yonggun.tar.gz (http://yonggun.tistory.com/attachment/ck79.gz), and zaurus-debian-eabi-afterinstall_1.1.tar.gz (https://www.oesf.org/forum/index.php?act=attach&type=post&id=5022)
c. cd /mnt/card
d. cp armel-root-fs.tar modules-2.6.23.1-yonggun.tar.gz zaurus-debian-eabi-afterinstall_1.1.tar.gz /mnt/cf
e. cd /mnt/cf
f. tar -xvpf armel-root-fs.tar
g. cd armel-root-fs
h. mv ./* ../
i. cd ..
j. tar -xvpzf modules-2.6.23.1-yonggun.tar.gz
k. tar -xvzf zaurus-debian-eabi-afterinstall_1.1.tar.gz
l. rm -r armel-root-fs armel-root-fs.tar modules-2.6.23.1-yonggun.tar.gz zaurus-debian-eabi-afterinstall_1.1.tar.gz
===========
Uboot installation
===========
6. Install uboot
(adapted from http://www.pdaxrom.org/?q=node/106 (http://www.pdaxrom.org/?q=node/106) )
[If your Zaurus is already using uboot, go directly to 7]
Fresh installation on Zaurus with Sharp bootloader (applicable to Sharp rom, Cacko rom, pdaXrom 1.1.0 Beta 1/Beta3, pdaXii, Angstrom)
a. Download ( http://distro.ibiblio.org/pub/linux/distri...akita-uboot.zip (http://distro.ibiblio.org/pub/linux/distributions/pdaxrom/download/r198/c1000-c3x00/pdaXrom-1.1.0r198-Kathrin-akita-uboot.zip) ) and unzip u-boot archive to CF or MMC/SD card, you will see FOUR files: emergenc.img, u-boot.bin, updater.pro and updater.sh
b. Remove baterry, wait 5 secs, place battery and attach AC power.
c. Press "OK" key and keep it pressed, then press "On/Off" button.
d. In the maintenance menu, choose "4" (Update) in the first screen, "2" (SD) in the second and "Y" in the third
e. The kernel will be flashed
f. Press and hold [OK] during reboot - emergency system will boot up
============
Kernel installation
============
7. Flash the kernel in the uboot emergency system
7.1 Eject the SD card and remove all the uboot installation files on the SD card.
7.2 Download and copy kernel.img.2.6.23.1.cpufreq-fastfpe.hda1 (rename to kernel.img) from http://yonggun.tistory.com/53 (http://yonggun.tistory.com/53) and autoboot.sh from https://www.oesf.org/forum/index.php?act=at...ost&id=4969 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4969) (simply remove the tar.gz extension; it is just a plain text file) and put them on the SD card.
7.3 Reboot the Zaurus while pressing the [Ok] button.
7.4 In the uboot emergency system, you will be asked "Proceed with debian installation or boot to emergency system? [y/n]". Press [y] and [Enter]. The new kernel flashing process will start and complete very quickly.
After reboot, your Z will be running Debian EABI!
[NOTE: Press "2" when (re)booting]
====================
1st boot: System configuration
====================
Note: The first booting may fail and complain about being "unable to open an initial console".
If that is the case, boot into the Linux Emergency mode and do this:
mount /dev/hda1 /mnt/cf
cd /mnt/cf/dev
MAKEDEV consoleAfter that, reboot again. (Press [2] when boot starts)
8. 1st login
Login: root
Root password : (no password)
9. Set up date and time
date MMDDHHMMYYYY ##Example: 10290657200710. The first part of after installation configurations
The after installation process is divided into two parts. Now let's do the first part.
[Note: The after installation scripts (1st-cfg.sh and 2nd-cfg.sh) are intended to be applied only once to a clean, fresh install before any tweaking. Mixing any other different tweak with the application of these scripts may produce unexpected results.]
Do this and follow the instructions:
cd ../afterinstall ## Use the [Tab] key to help you get "/"
../afterinstall/1st-cfg.shWhen the process completes, you will be reminded to set up a proper network connection before proceeding to the second part.
11. Set up network connection
11.1 nano /etc/network/interfaces.
For example, for my Symbol Spectrum 24 wifi CF with a static IP in a home network:
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback
auto eth2
# iface eth2 inet dhcp
allow-hotplug eth2
iface eth2 inet static
address 192.168.0.199
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1
wireless-essid DON'T_BE_STUPID
wireless-key I_KNOW_YOU_KNOW_THAT
wireless-mode managed
dns-nameservers 192.168.0.1
11.2 nano /etc/resolv.conf
Simply put down your router's IP, e.g.
192.168.0.1
11.3 You can do a very simple test to see if your network connection is working:
For example, if your Zaurus is connecting to a wireless router, then do
ping 192.168.0.1 ##Or the correct IP address of the router
ping www.google.com ##This will make sure that your Zaurus can connect to the internetIf ping doesn't report any package loss, then you are ready to proceed to 12.
12. Now we begin the second part of the after installation process.
Go to the afterinstallation directory again. Then
./2nd-cfg.shWhen asked to confirm whether you want to install anything, just type [y] and [Enter].
After this a fully working EABI system is set up. Time to play!
That's it. Have fun!
==========
Change kernels
==========
If you want to switch to other kernels,
a. First extract and copy the corresponding kernel modules to /lib/modules
b. Prepare the correct kernel image (zImage.bin) and updater.sh and install them in the Uboot Emergency Mode again.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q19: I am using a C3x00, and I want to use kernel 2.6.23.1 yonggun with uboot. How can I install Debian EABI on SD?
A19: The installation comes in four parts: 1. Prepare the SD 2. Install the EABI rootfs; 3. Install uboot; 4. Flash the kernel
==========
Preparation
==========
1. Prepare the SD card
[Note: If you are already using the new pdaXrom versions using uboot, you can simply repartition and reformat the internal drive, without using the method below. Go directly to II)]
2. Boot into Linux Emergency Mode
a. Remove power sources,
b. Press B and D while putting back the battery & lock the cover switch & power on.
c. In the command prompt, login as root.
3. Repartition the internal drive using fdisk /dev/hda
(how-to: https://www.oesf.org/index.php?title=Multip..._a_CF_/_SD_card (https://www.oesf.org/index.php?title=Multiple_partitions_on_a_CF_/_SD_card) ). Create two partitions. /dev/hda1 is the root partition (ext3); /dev/hda2 is the swap partition (default ~180.9MB in Debian CD installation, but you can make a bigger swap partition if you want to run very resource-hungry programs, or do onboard compilation).
4. Reformat the two partitions:
mke2fs -j /dev/mmcblk0p1
mkswap /dev/mmcblk0p2
==========
System Installation
==========
5. Extract the system rootfs tarball, kernel modules and after installation files to the SD card
a. mount /dev/mmcblk0p1 /mnt/card
b. Plug in the CF card with armel-root-fs.tar (http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2) (first uncompress the .bz2 format), modules-2.6.23.1-yonggun.tar.gz (http://yonggun.tistory.com/attachment/ck79.gz), and zaurus-debian-eabi-afterinstall_1.1.tar.gz (https://www.oesf.org/forum/index.php?act=attach&type=post&id=5022)
c. cd /mnt/cf
d. cp armel-root-fs.tar modules-2.6.23.1-yonggun.tar.gz zaurus-debian-eabi-afterinstall_1.1.tar.gz /mnt/card
e. cd /mnt/card
f. tar -xvpf armel-root-fs.tar
g. cd armel-root-fs
h. mv ./* ../
i. cd ..
j. tar -xvpzf modules-2.6.23.1-yonggun.tar.gz
k. tar -xvzf zaurus-debian-eabi-afterinstall_1.1.tar.gz
l. rm -r armel-root-fs armel-root-fs.tar modules-2.6.23.1-yonggun.tar.gz zaurus-debian-eabi-afterinstall_1.1.tar.gz
===========
Uboot installation
===========
6. Install uboot
(adapted from http://www.pdaxrom.org/?q=node/106 (http://www.pdaxrom.org/?q=node/106) )
[If your Zaurus is already using uboot, go directly to 7]
Fresh installation on Zaurus with Sharp bootloader (applicable to Sharp rom, Cacko rom, pdaXrom 1.1.0 Beta 1/Beta3, pdaXii, Angstrom)
a. Download ( http://distro.ibiblio.org/pub/linux/distri...akita-uboot.zip (http://distro.ibiblio.org/pub/linux/distributions/pdaxrom/download/r198/c1000-c3x00/pdaXrom-1.1.0r198-Kathrin-akita-uboot.zip) ) and unzip u-boot archive to CF, you will see FOUR files: emergenc.img, u-boot.bin, updater.pro and updater.sh
b. Remove baterry, wait 5 secs, place battery and attach AC power.
c. Press "OK" key and keep it pressed, then press "On/Off" button.
d. In the maintenance menu, choose "4" (Update) in the first screen, "1" (CF) in the second and "Y" in the third
e. The kernel will be flashed
f. Press and hold [OK] during reboot - emergency system will boot up
============
Kernel installation
============
7. Flash the kernel in the uboot emergency system
7.1 Eject the CF card and remove all the uboot installation files on the CF card.
7.2 Download and copy kernel.img.2.6.23.1.cpufreq-fastfpe.sd (rename to kernel.img) from http://yonggun.tistory.com/53 (http://yonggun.tistory.com/53) and autoboot.sh from https://www.oesf.org/forum/index.php?act=at...ost&id=4969 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4969) (simply remove the tar.gz extension; it is just a plain text file) and put them on the CF card.
7.3 Reboot the Zaurus while pressing the [Ok] button.
7.4 In the uboot emergency system, you will be asked "Proceed with debian installation or boot to emergency system? [y/n]". Press [y] and [Enter]. The new kernel flashing process will start and complete very quickly.
After reboot, your Z will be running Debian EABI!
[NOTE: Press "1" when (re)booting]
====================
1st boot: System configuration
====================
Note: The first booting may fail and complain about being "unable to open an initial console".
If that is the case, boot into the Linux Emergency mode and do this:
mount /dev/hda1 /mnt/cf
cd /mnt/cf/dev
MAKEDEV consoleAfter that, reboot again. (Press [1] when boot starts)
8. 1st login
Login: root
Root password : (no password)
9. Set up date and time
date MMDDHHMMYYYY ##Example: 10290657200710. The first part of after installation configurations
The after installation process is divided into two parts. Now let's do the first part.
[Note: The after installation scripts (1st-cfg.sh and 2nd-cfg.sh) are intended to be applied only once to a clean, fresh install before any tweaking. Mixing any other different tweak with the application of these scripts may produce unexpected results.]
Do this and follow the instructions:
cd ../afterinstall ## Use the [Tab] key to help you get "/"
../afterinstall/1st-cfg.shWhen the process completes, you will be reminded to set up a proper network connection before proceeding to the second part.
11. Set up network connection
11.1 nano /etc/network/interfaces.
For example, for my Symbol Spectrum 24 wifi CF with a static IP in a home network:
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback
auto eth2
# iface eth2 inet dhcp
allow-hotplug eth2
iface eth2 inet static
address 192.168.0.199
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1
wireless-essid DON'T_BE_STUPID
wireless-key I_KNOW_YOU_KNOW_THAT
wireless-mode managed
dns-nameservers 192.168.0.1
11.2 nano /etc/resolv.conf
Simply put down your router's IP, e.g.
192.168.0.1
11.3 You can do a very simple test to see if your network connection is working:
For example, if your Zaurus is connecting to a wireless router, then do
ping 192.168.0.1 ##Or the correct IP address of the router
ping www.google.com ##This will make sure that your Zaurus can connect to the internetIf ping doesn't report any package loss, then you are ready to proceed to 12.
12. Now we begin the second part of the after installation process.
Go to the afterinstallation directory again. Then
./2nd-cfg.shWhen asked to confirm whether you want to install anything, just type [y] and [Enter].
After this, a fully working EABI system is set up. Time to play!
That's it. Have fun!
==========
Change kernels
==========
If you want to switch to other kernels,
a. First extract and copy the corresponding kernel modules to /lib/modules
b. Prepare the correct kernel image (zImage.bin) and updater.sh and install them in the Uboot Emergency Mode again.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q20: I am using a C1x00, and I want to use kernel 2.6.23.1 yonggun with uboot. How can I install Debian EABI on SD?
A20: [The method should be the same as Q19, but this remains to be tested.]
==========
Preparation
==========
1. Prepare the SD card
[Note: If you are already using the new pdaXrom versions using uboot, you can simply repartition and reformat the internal drive, without using the method below. Go directly to II)]
2. Boot into Linux Emergency Mode
a. Remove power sources,
b. Press B and D while putting back the battery & lock the cover switch & power on.
c. In the command prompt, login as root.
3. Repartition the internal drive using fdisk /dev/hda
(how-to: https://www.oesf.org/index.php?title=Multip..._a_CF_/_SD_card (https://www.oesf.org/index.php?title=Multiple_partitions_on_a_CF_/_SD_card) ). Create two partitions. /dev/hda1 is the root partition (ext3); /dev/hda2 is the swap partition (default ~180.9MB in Debian CD installation, but you can make a bigger swap partition if you want to run very resource-hungry programs, or do onboard compilation).
4. Reformat the two partitions:
mke2fs -j /dev/mmcblk0p1
mkswap /dev/mmcblk0p2
==========
System Installation
==========
5. Extract the system rootfs tarball, kernel modules and after installation files to the SD card
a. mount /dev/mmcblk0p1 /mnt/card
b. Plug in the CF card with armel-root-fs.tar (http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2) (first uncompress the .bz2 format), modules-2.6.23.1-yonggun.tar.gz (http://yonggun.tistory.com/attachment/ck79.gz), and zaurus-debian-eabi-afterinstall_1.1.tar.gz (https://www.oesf.org/forum/index.php?act=attach&type=post&id=5022)
c. cd /mnt/cf
d. cp armel-root-fs.tar modules-2.6.23.1-yonggun.tar.gz zaurus-debian-eabi-afterinstall_1.1.tar.gz /mnt/card
e. cd /mnt/card
f. tar -xvpf armel-root-fs.tar
g. cd armel-root-fs
h. mv ./* ../
i. cd ..
j. tar -xvpzf modules-2.6.23.1-yonggun.tar.gz
k. tar -xvzf zaurus-debian-eabi-afterinstall_1.1.tar.gz
l. rm -r armel-root-fs armel-root-fs.tar modules-2.6.23.1-yonggun.tar.gz zaurus-debian-eabi-afterinstall_1.1.tar.gz
===========
Uboot installation
===========
6. Install uboot
(adapted from http://www.pdaxrom.org/?q=node/106 (http://www.pdaxrom.org/?q=node/106) )
[If your Zaurus is already using uboot, go directly to 7]
Fresh installation on Zaurus with Sharp bootloader (applicable to Sharp rom, Cacko rom, pdaXrom 1.1.0 Beta 1/Beta3, pdaXii, Angstrom)
a. Download ( http://distro.ibiblio.org/pub/linux/distri...akita-uboot.zip (http://distro.ibiblio.org/pub/linux/distributions/pdaxrom/download/r198/c1000-c3x00/pdaXrom-1.1.0r198-Kathrin-akita-uboot.zip) ) and unzip u-boot archive to CF, you will see FOUR files: emergenc.img, u-boot.bin, updater.pro and updater.sh
b. Remove baterry, wait 5 secs, place battery and attach AC power.
c. Press "OK" key and keep it pressed, then press "On/Off" button.
d. In the maintenance menu, choose "4" (Update) in the first screen, "1" (CF) in the second and "Y" in the third
e. The kernel will be flashed
f. Press and hold [OK] during reboot - emergency system will boot up
============
Kernel installation
============
7. Flash the kernel in the uboot emergency system
7.1 Eject the CF card and remove all the uboot installation files on the CF card.
7.2 Download and copy kernel.img.2.6.23.1.cpufreq-fastfpe.sd (rename to kernel.img) from http://yonggun.tistory.com/53 (http://yonggun.tistory.com/53) and autoboot.sh from https://www.oesf.org/forum/index.php?act=at...ost&id=4969 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4969) (simply remove the tar.gz extension; it is just a plain text file) and put them on the CF card.
7.3 Reboot the Zaurus while pressing the [Ok] button.
7.4 In the uboot emergency system, you will be asked "Proceed with debian installation or boot to emergency system? [y/n]". Press [y] and [Enter]. The new kernel flashing process will start and complete very quickly.
After reboot, your Z will be running Debian EABI!
[NOTE: Press "1" when (re)booting]
====================
1st boot: System configuration
====================
Note: The first booting may fail and complain about being "unable to open an initial console".
If that is the case, boot into the Linux Emergency mode and do this:
mount /dev/hda1 /mnt/cf
cd /mnt/cf/dev
MAKEDEV consoleAfter that, reboot again. (Press [1] when boot starts)
8. 1st login
Login: root
Root password : (no password)
9. Set up date and time
date MMDDHHMMYYYY ##Example: 10290657200710. The first part of after installation configurations
The after installation process is divided into two parts. Now let's do the first part.
[Note: The after installation scripts (1st-cfg.sh and 2nd-cfg.sh) are intended to be applied only once to a clean, fresh install before any tweaking. Mixing any other different tweak with the application of these scripts may produce unexpected results.]
Do this and follow the instructions:
cd ../afterinstall ## Use the [Tab] key to help you get "/"
../afterinstall/1st-cfg.shWhen the process completes, you will be reminded to set up a proper network connection before proceeding to the second part.
11. Set up network connection
11.1 nano /etc/network/interfaces.
For example, for my Symbol Spectrum 24 wifi CF with a static IP in a home network:
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback
auto eth2
# iface eth2 inet dhcp
allow-hotplug eth2
iface eth2 inet static
address 192.168.0.199
network 192.168.0.0
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1
wireless-essid DON'T_BE_STUPID
wireless-key I_KNOW_YOU_KNOW_THAT
wireless-mode managed
dns-nameservers 192.168.0.1
11.2 nano /etc/resolv.conf
Simply put down your router's IP, e.g.
192.168.0.1
11.3 You can do a very simple test to see if your network connection is working:
For example, if your Zaurus is connecting to a wireless router, then do
ping 192.168.0.1 ##Or the correct IP address of the router
ping www.google.com ##This will make sure that your Zaurus can connect to the internetIf ping doesn't report any package loss, then you are ready to proceed to 12.
12. Now we begin the second part of the after installation process.
Go to the afterinstallation directory again. Then
./2nd-cfg.shWhen asked to confirm whether you want to install anything, just type [y] and [Enter].
After this, a fully working EABI system is set up. Time to play!
That's it. Have fun!
==========
Change kernels
==========
If you want to switch to other kernels,
a. First extract and copy the corresponding kernel modules to /lib/modules
b. Prepare the correct kernel image (zImage.bin) and updater.sh and install them in the Uboot Emergency Mode again.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
Q??: So at the end of the days, which one is the best?
A??: Oh, sorry, sweatheart, it's just for [size=]fun[/size][size=]TM[/size][/b][/color][/font], and so I'm not gonna tell you, "Look, my Richard beats your Jimmy hands down!" This is impolite.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
-
(This post is reserved for general purpose)
Upcoming:
Part II FAQs
No rules to follow, but just one basic principle of KISS (keep it short and simple)
Rough outline:
1. After installation
2. Network connection
3. Basic package management commands (apt-get)
4. Binding mouse buttons to keyboards
5. Brightness adjustment
6. Bluetooth
7. X-windows (including WMs)
8. Sound issues
9. Compilation: onboard and cross
10. Other known issues
**********
Well, I think the FAQs deserve a separate thread, lest we make this one too big and long and hard to read. What do you folks think?
-
Great work. It may be huge, but this post makes it a one-stop place for all the bits of information that is scattering around the place. Thanks a lot!
-
No, no, it's A collective work of many random nameless rogue user joez here...
One joe now keeps himself busy making the notes look better.
Thanks cortez for your notes. Now following your suggested format ...
-
No, no, it's A collective work of many random nameless rogue user joez here...
One joe now keeps himself busy making the notes look better.
Thanks cortez for your notes. Now following your suggested format ...
Cheers ZDevil, a good bit of work. I'm, slowly, going through the printed version you sent and I'll pop any bright ideas i have back to you.
-
Hey, folks, this is certainly not the end!
If you come up with alternative and better installation methods, write me the notes and I will incorporate them here (with your name of course!).
-
Very nice piece of docs.
-
Very nice...
To bad I aint own a C serie... maybe soon hmmm
-
Very well covered thanks.
Q20: I am using a C1x00, and I want to use kernel 2.6.22.9 yonggun with uboot. How can I install Debian EABI on SD?
Sent a PM ZDevil
-
Thanks to scottlfa for explaining to me a cleaner way to extract the EABI rootfs. Will add this bit to the guide.
About the EABI installation method:
I also think it will make life much easier if I include all the necessary files (keymap, hardware clock rules, touchscreen and X), plus one single script to set up all these in the "1st boot" section.
So version 0.2 will be up soon.
-
Very well covered thanks.
Q20: I am using a C1x00, and I want to use kernel 2.6.22.9 yonggun with uboot. How can I install Debian EABI on SD?
Sent a PM ZDevil
Untar to SD (/dev/mmcblk0p1) instead of microdrive, the rest is the same.
To boot : press and hold "1" while booting and it will boot from the SD. (that's the beauty of uboot) (I think it is "1" for the SD, if not try "2" "3" or "4")
Chero.
-
Very well covered thanks.
Q20: I am using a C1x00, and I want to use kernel 2.6.22.9 yonggun with uboot. How can I install Debian EABI on SD?
Sent a PM ZDevil
Untar to SD (/dev/mmcblk0p1) instead of microdrive, the rest is the same.
To boot : press and hold "1" while booting and it will boot from the SD. (that's the beauty of uboot) (I think it is "1" for the SD, if not try "2" "3" or "4")
Chero.
Just remember : once uboot is installed the only way to get back to the Angstrom or poky kernels is by doing a NAND restore first (which is quite a long way).
I'd first setup an SD with EABI and try it with the Angstrom 2.6.21 kernel on a C1000.
-
I have one concern:
The EABI rootfs has got something essential missing, such as touchscreen and X stuff. I am thinking of including some library and binary from some Angstrom packages in one single tarball to be installed in one go.
Would it be ok if i simply copy out the files?
Should I add some notice or reference to Angstrom? (oh yeah, the rules!)
Thanks!
-
I have one concern:
The EABI rootfs has got something essential missing, such as touchscreen and X stuff. I am thinking of including some library and binary from some Angstrom packages in one single tarball to be installed in one go.
Would it be ok if i simply copy out the files?
Should I add some notice or reference to Angstrom? (oh yeah, the rules!)
Thanks!
I wouldn't worry about that. I don't think they want you to update the wiki with a howto on debian eabi ...
(my son wants to see some smilies in this post ...)
-
Thanks!
(Goedemorgen, little Chero!)
-
Ok, so here is the planned one-stop hardware cum X initial setup thingie.
Files to include:
libts-1.0.so.0.0.0 (Angstrom)
ts.conf (Angstrom)
ts_calibrate (Angstrom)
Xfbedev (Angstrom)
setfl (pdaX)
keymap.map (from the googlepage guide)
hwclock.rules (from titchy)
And here is my script. Please comment:
(The script is supposed to run after extracting the tarball containing the above files to the right locations during installation and before 1st boot)
#!/bin/sh
## First set up the hardware on the Zaurus
echo "Now setting up the hardware ..." &&
# keymap
echo "loadkeys /etc/keymap.map" >> /etc/rc.local &&
# localhost
echo "Zaurus" > /etc/hostname &&
echo -ne "127.0.0.1\tlocalhost.localdomain localhost Zaurus\n" >> /etc/hosts &&
# touchscreen
ln -s /usr/local/lib/libts-1.0.so.0.0.0 /usr/local/lib/libts-1.0.so.0 &&
echo "/usr/local/lib" >> /etc/ld.so.conf &&
ldconfig &&
cat /etc/ts.conf | sed 's/^# module_raw corgi/module_raw corgi/' > /etc/ts.conf &&
echo -ne "TSLIB_TSDEVICE=/dev/input/ts0\nTSLIB_CONFFILE=/etc/ts.conf\nexport TELIB_TSDEVICE TSLIB_TSCONFFILE\n" >> $HOME/.profile
echo "Done."
echo ""
## Next set up X
echo "Now setting up X ..." &&
chmod 4755 /usr/local/bin/Xfbdev &&
echo -ne "xrandr -o right\n" >> ~/.xsession &&
touch $HOME/.xserverrc &&
chmod 755 $HOME/.xserverrc &&
echo -ne "#!/bin/sh\nexec /usr/local/bin/Xfbdev -dpi 100 -nolisten tcp -fp /usr/share/fonts/X11/misc" > $HOME/.xserverrc
echo "Done."
echo ""Any error? Anything to add? Does it look good?
-
I have one concern:
The EABI rootfs has got something essential missing, such as touchscreen and X stuff. I am thinking of including some library and binary from some Angstrom packages in one single tarball to be installed in one go.
Would it be ok if i simply copy out the files?
Should I add some notice or reference to Angstrom? (oh yeah, the rules!)
Thanks!
I am making the debian packages from angstrom binary. They include X setting, tslib-related stuff, zaurusd, mplayer, gpe-conf, keymaps, and so on. I think this way is easy and simple.
-
Great. zaurusd and gpe-conf are great additions.
So could you package it up and upload here?
Also do you think it's a good idea to run the script as suggested? I wonder if i should add something to set up zaurusd there.
Thanks!
-
I will upload the packages soon. Also they have their own script for setting up. I think we need the script to finalize set-up after installing all packages.
Thanks for your efforts.
-
Ready for testing ...
I've got an eabi kernel loaded, the rootfs is still in armel-root-fs, I added the correct modules in it.
As soon as the files are up, I'm ready to test ... (boot emergency - move everything to / - and reboot)
(just to make sure I will be able to type the commands I added the titchy keymap but it won't be loaded automatically - only as a kind of a backup)
Chero.
(little Chero (8) likes "Need for Speed" more than this forum ...)
-
Chero, test this if you can't wait (actually because I can't wait to see your result ... ).
There are three little extra steps involved:
1. Add these extra files:
-- Download these essential utilities to the SD:
http://kfreebsd-gnu.debian.net/debian/pool...bs-65_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/c/console-tools/libconsole_0.2.3dbs-65_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...bs-65_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/c/console-tools/console-tools_0.2.3dbs-65_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...2-8.1_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/a/apmd/apmd_3.2.2-8.1_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...9p6-1_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/s/sudo/sudo_1.6.9p6-1_armel.deb)
-- Put these attachments to the SD too:
[ You are not allowed to view attachments ] (Fixed on 071028: 1) Add tslib modules; 2) Fix tslib file)
[ You are not allowed to view attachments ] (Fixed on 071029: 1) Correct two typos; 2) Added USB device module loading script; 3) Fix privilege of .xsession)
2. Follow the steps as described, and after extracting the rootfs and the kernel modules, extract the zaurus-hardware-eabi thingie also.
3. After the first login:
-- First install those few armel packages.
-- Then run the afterinstall.sh (remove the .txt extension).
-
Chero, test this if you can't wait (actually because I can't wait to see your result ... ).
There are three little extra steps involved:
1. Add these extra files:
-- Download these essential utilities to the SD:
http://armel-debs.applieddata.net/debian/p...bs-65_armel.deb (http://armel-debs.applieddata.net/debian/pool/main/c/console-tools/libconsole_0.2.3dbs-65_armel.deb)
http://armel-debs.applieddata.net/debian/p...bs-65_armel.deb (http://armel-debs.applieddata.net/debian/pool/main/c/console-tools/console-tools_0.2.3dbs-65_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...2-8.1_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/a/apmd/apmd_3.2.2-8.1_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...9p6-1_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/s/sudo/sudo_1.6.9p6-1_armel.deb)
-- Put these attachments to the SD too:
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
2. Follow the steps as described, and after extracting the rootfs and the kernel modules, extract the zaurus-hardware-eabi thingie also.
3. After the first login:
-- First install those few armel packages.
-- Then run the afterinstall.sh (remove the .txt extension).
the first two links are down, but they are on kfreebsd as well - first have to eat now - will continue this afternoon
-
Sorry, corrected in Post #42.
Just finished mine.
Eet Smakelijk!
-
All files on the system - untarred the extra tarball - booted into emergency - deleting titchy-system - then will move the armel-root-fs to /mnt/cf and reboot ...
Fingers crossed ...
10 - 9 - 8 - ...
-
Very nice...
To bad I aint own a C serie... maybe soon hmmm
I guess the same trick may do for SL-6000, as long as there is a suitable kernel.
-
booted fine, installed the debs, ran the script - rebooted.
udev working.
Called "zaurus" now.
What should I check ?
Problems :
- need to change sources.list cause it can't find packages
- the debs I downloaded are not fully compatible (need a newer libc6)
Chero.
-
Hmm. Then I guess if you can apt-get update after installation, then simply apt-get install those packages.
For the sources.list, you can only set to unstable, because armel is now available only in Sid.
The main reason why we need the consoletool after the first boot is to get the loadkeys command, which is executed in the "afterinstall.sh".
EABI is cool, sound just works without the Angstrom stuff (perhaps except the zaurusd thing), and no more jumping stylus pointer (at least true of 2or0's yonggun 2.6.30.1 kernel). Of course it is speeeeedy.
-
Hmm. Then I guess if you can apt-get update after installation, then simply apt-get install those packages.
For the sources.list, you can only set to unstable, because armel is now available only in Sid.
The main reason why we need the consoletool after the first boot is to get the loadkeys command, which is executed in the "afterinstall.sh".
EABI is cool, sound just works without the Angstrom stuff (perhaps except the zaurusd thing), and no more jumping stylus pointer (at least true of 2or0's yonggun 2.6.30.1 kernel). Of course it is speeeeedy.
What sources should I add in sources.list ?
The default seems to be down and kfreebsd-gnu has lots of unsolved deps .
-
Hmm. Then I guess if you can apt-get update after installation, then simply apt-get install those packages.
For the sources.list, you can only set to unstable, because armel is now available only in Sid.
The main reason why we need the consoletool after the first boot is to get the loadkeys command, which is executed in the "afterinstall.sh".
EABI is cool, sound just works without the Angstrom stuff (perhaps except the zaurusd thing), and no more jumping stylus pointer (at least true of 2or0's yonggun 2.6.30.1 kernel). Of course it is speeeeedy.
What sources should I add in sources.list ?
The default seems to be down and kfreebsd-gnu has lots of unsolved deps .
just ignore this question - the answer is in the mega-manual ...
Tip : maybe a working sources.list could be added in the addons-tar.gz ?
-
Hmm. Me too. apt-get update also gets stuck... site down?
How about: deb ftp.easynet.be/ftp/gnuab/debian sid main
-
Hmm. Me too. apt-get update also gets stuck... site down?
How about: deb ftp.easynet.be/ftp/gnuab/debian sid main
-
just ignore this question - the answer is in the mega-manual ...
Tip : maybe a working sources.list could be added in the addons-tar.gz ?
True. That's very easy to make.
@2or0: do you think we should spilt the finetuning package into at least two? One is for real after installation configurations, the other for adding useful packages, such as the gpe-confs and mplayer, etc.
BTW the OE forum also loads a bit slow today? Any hiccup?
-
Hmm. Me too. apt-get update also gets stuck... site down?
How about: deb ftp.easynet.be/ftp/gnuab/debian sid main
Oh, ignore my answer as well. apt-get is working now.
-
Hmm. Me too. apt-get update also gets stuck... site down?
How about: deb ftp.easynet.be/ftp/gnuab/debian sid main
Oh, ignore my answer as well. apt-get is working now.
for me too - I guess it was just bad timing
-
What window-manager are you using ? Icewm-experimental ?
- What to do before launching ?
- How do you launch it ?
(asking too many questions, so it can be usefull for the new girls and boys)
Chero.
-
AFAIR it's just two simple steps:
1. apt-get install icewm-experimental
2. In ~/.xsession (should have been created by the afterinstall.sh), add the line "exec icewm-session-experimental"
This icewm setting file may help you get started easier:
[ You are not allowed to view attachments ]
(remove ".txt" and drop it to ~/.icewm -- create the dir first)
Can you verify if the afterinstall.sh and the zaurus-hardware-eabi package work, including ...
-- Set the correct date and time and "hwclock -w"?
-- ts_calibrate?
-- loadkeys?
Thanks for doing the little experiment.
-
AFAIR it's just two simple steps:
1. apt-get install icewm-experimental
2. In ~/.xsession (should have been created by the afterinstall.sh), add the line "exec icewm-session-experimental"
This icewm setting file may help you get started easier:
[ You are not allowed to view attachments ]
(remove ".txt" and drop it to ~/.icewm -- create the dir first)
Can you verify if the afterinstall.sh and the zaurus-hardware-eabi package work, including ...
-- Set the correct date and time and "hwclock -w"?
-- ts_calibrate?
-- loadkeys?
Thanks for doing the little experiment.
hwclock -w works
loadkeys works
.xsession contains "xrandr -o right"
startx :command not found
ts_calibrate : ts_open: no such file or directory
-
startx :command not found
ts_calibrate : ts_open: no such file or directory
startx: what if ...
-- simply ln -s /usr/bin/icewm-session-experimental /usr/bin/startx? OR
-- apt-get install xbase-clients (startx is there)?
ts_calibrate:
Can you show mean what is in your ~/.profile?
Mine has this:
......
TSLIB_TSDEVICE=/dev/input/ts0
TSLIB_CONFFILE=/etc/ts.conf
export TELIB_TSDEVICE TSLIB_TSCONFFILE
and check if these files are present:
/usr/local/lib/libts-1.0.so.0.0.0
/usr/local/lib/libts-1.0.so.0
/etc/ts.conf
/dev/input/ts0
-
Oh, I see my typo (dammit!)
In ~/.profile, it should be "export TSLIB_TSDEVICE TSLIB_TSCONFFILE" instead of "export TELIB_TSDEVICE TSLIB_TSCONFFILE"
-
startx :command not found
ts_calibrate : ts_open: no such file or directory
startx: what if ...
-- simply ln -s /usr/bin/icewm-session-experimental /usr/bin/startx? OR
-- apt-get install xbase-clients (startx is there)?
ts_calibrate:
Can you show mean what is in your ~/.profile?
Mine has this:
......
TSLIB_TSDEVICE=/dev/input/ts0
TSLIB_CONFFILE=/etc/ts.conf
export TELIB_TSDEVICE TSLIB_TSCONFFILE
and check if these files are present:
/usr/local/lib/libts-1.0.so.0.0.0
/usr/local/lib/libts-1.0.so.0
/etc/ts.conf
/dev/input/ts0
startx installed and working by installing xbase-clients
.profile didn't have those entries -> added
libts-1.0.so.0.0.0 missing -> symlinked
/dev/input/ts0 missing -> what now ?
-
startx :command not found
ts_calibrate : ts_open: no such file or directory
startx: what if ...
-- simply ln -s /usr/bin/icewm-session-experimental /usr/bin/startx? OR
-- apt-get install xbase-clients (startx is there)?
ts_calibrate:
Can you show mean what is in your ~/.profile?
Mine has this:
......
TSLIB_TSDEVICE=/dev/input/ts0
TSLIB_CONFFILE=/etc/ts.conf
export TELIB_TSDEVICE TSLIB_TSCONFFILE
and check if these files are present:
/usr/local/lib/libts-1.0.so.0.0.0
/usr/local/lib/libts-1.0.so.0
/etc/ts.conf
/dev/input/ts0
startx installed and working by installing xbase-clients
.profile didn't have those entries -> added
libts-1.0.so.0.0.0 missing -> symlinked
/dev/input/ts0 missing -> what now ?
So obviously the parts setting up touchscreen does not work as expected .... sorry... but....
But the correct sequence should be: extract the zaurus-hardware-eabi.tarball (to /.) first, and then run the afterinstall.sh script; otherwise some commands in the script will fail to operate because of missing the binary/library.
/dev/input/ts0 ....
Do you have /dev/input/event1 or /dev/input/touchscreen0 ?
If nothing's there, can you:
cd /dev/input
MAKEDEV ts0 (the command is in capitals)
PS I think i have missed the xbase-clients package. Will add it to the guide. Actually I did install xorg (which pulls down xbase-clients) before playing with Xfbdev. Thanks.
-
startx :command not found
ts_calibrate : ts_open: no such file or directory
startx: what if ...
-- simply ln -s /usr/bin/icewm-session-experimental /usr/bin/startx? OR
-- apt-get install xbase-clients (startx is there)?
ts_calibrate:
Can you show mean what is in your ~/.profile?
Mine has this:
......
TSLIB_TSDEVICE=/dev/input/ts0
TSLIB_CONFFILE=/etc/ts.conf
export TELIB_TSDEVICE TSLIB_TSCONFFILE
and check if these files are present:
/usr/local/lib/libts-1.0.so.0.0.0
/usr/local/lib/libts-1.0.so.0
/etc/ts.conf
/dev/input/ts0
startx installed and working by installing xbase-clients
.profile didn't have those entries -> added
libts-1.0.so.0.0.0 missing -> symlinked
/dev/input/ts0 missing -> what now ?
So obviously the parts setting up touchscreen does not work as expected .... sorry... but....
But the correct sequence should be: extract the zaurus-hardware-eabi.tarball (to /.) first, and then run the afterinstall.sh script; otherwise some commands in the script will fail to operate because of missing the binary/library.
/dev/input/ts0 ....
Do you have /dev/input/event1 or /dev/input/touchscreen0 ?
If nothing's there, can you:
cd /dev/input
MAKEDEV ts0 (the command is in capitals)
PS I think i have missed the xbase-clients package. Will add it to the guide. Actually I did install xorg (which pulls down xbase-clients) before playing with Xfbdev. Thanks.
MAKEDEV ts0 : I don't know how to make device ts0
(but I have event0 and event1)
ran the script again -> nothing changed.
-
Another shot: what do you have in /etc/ts.conf?
Here is the relevant section in my afterinstall.sh. Let's see if something goes wild:
# touchscreen
ln -s /usr/local/lib/libts-1.0.so.0.0.0 /usr/local/lib/libts-1.0.so.0 &&
echo "/usr/local/lib" >> /etc/ld.so.conf &&
ldconfig &&
cat /etc/ts.conf | sed 's/^# module_raw corgi/module_raw corgi/' > /etc/ts.conf &&
echo -ne "TSLIB_TSDEVICE=/dev/input/ts0\nTSLIB_CONFFILE=/etc/ts.conf\nexport TSLIB_TSDEVICE TSLIB_TSCONFFILE\n" >> $HOME/.profile
-
MAKEDEV ts0 : I don't know how to make device ts0
(but I have event0 and event1)
ran the script again -> nothing changed.
I changed the above line to TSLIB_TSDEVICE=/dev/input/event1
now I get this when running ts_calibrate :
couldn't load module input
no raw modules loaded
ts_config: Succes
Don't know what the succes is cause I could not calibrate ...
-
Ok, now plz check /etc/ts.conf
Look for the line with "module_raw corgi"
Make sure that it is uncommented. The first line too.
One more:
-- depmod && reboot?
-- try event0?
Run ts_calibrate again?
-
Another shot: what do you have in /etc/ts.conf?
Here is the relevant section in my afterinstall.sh. Let's see if something goes wild:
# touchscreen
ln -s /usr/local/lib/libts-1.0.so.0.0.0 /usr/local/lib/libts-1.0.so.0 &&
echo "/usr/local/lib" >> /etc/ld.so.conf &&
ldconfig &&
cat /etc/ts.conf | sed 's/^# module_raw corgi/module_raw corgi/' > /etc/ts.conf &&
echo -ne "TSLIB_TSDEVICE=/dev/input/ts0\nTSLIB_CONFFILE=/etc/ts.conf\nexport TSLIB_TSDEVICE TSLIB_TSCONFFILE\n" >> $HOME/.profile
ts.conf has "module_raw input grab_events=1" and "module_raw corgi" uncommented (and some at the end)
about ln -s for libts : it's the other way around.
/etc/ld.conf only has "include /etc/ld.so.conf.d/*.conf" in it
Looks like we are cross-posting : I'll wait untill I see your next post...
-
sorry, posting anyway :
Where can I find the modules for the touchscreen, I think they are missing ... (I remember I could see them on the titchy install).
the error is :
coudn't load module input
no raw modules loaded (both on event0 an event1)
note the touchscreen does something in X but totally un-callibrated.
-
libts: /usr/local/lib/libts-1.0.so.0.0.0 is the real guy, libts-1.0.so.0 is the link, so the command should be correct?
ldconfig: you are right! It should be /etc/ld.so.conf, NOT /etc/ld.conf.
Should be:
echo "/usr/local/lib" >> /etc/ld.so.conf &&
ldconfig &&
-
libts: /usr/local/lib/libts-1.0.so.0.0.0 is the real guy, libts-1.0.so.0 is the link, so the command should be correct?
libts-1.0.so.0.0.0 is not in the tarball -> libts-1.0.so.0 is and its size is only 6544 (6K)
-
Chero, THANKS!
I will make a new tarball and script and upload again. Please give me a minute.
Don't stop the fun ...
upload ...... done
finger crossed...
-
Chero, the file is here: https://www.oesf.org/forum/index.php?act=at...ost&id=4994 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4994)
And you don't have to run the whole script again. Instead do:
ln -s /usr/local/lib/libts-1.0.so.0.0.0 /usr/local/lib/libts-1.0.so.0
echo "/usr/local/lib" >> /etc/ld.so.conf ##if you haven't done this yet...
ldconfigPlease check if:
-- the tslib is now in place (with the right link)
-- ts_calibrate works
Sorry for the confusion. I think I was feeling a bit excited but dim this morning...
-
Chero, the file is here: https://www.oesf.org/forum/index.php?act=at...ost&id=4994 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4994)
And you don't have to run the whole script again. Instead do:
ln -s /usr/local/lib/libts-1.0.so.0.0.0 /usr/local/lib/libts-1.0.so.0
echo "/usr/local/lib" >> /etc/ld.so.conf ##if you haven't done this yet...
ldconfigPlease check if:
-- the tslib is now in place (with the right link)
-- ts_calibrate works
Sorry for the confusion. I think I was feeling a bit excited but dim this morning...
libts is in place now
ts_calibrate still doesn't want to :
Couldn't load module input
No raw modules loaded
Where can I find these modules ?
-
Also getting a consistent failed to open TSLIB device, tried /dev/input/ts0 etc ...
when I check /dev/input I have the following present ... event0, event1, mice, mouse0 and ts0
X flickers and crashes.
-
Also getting a consistent failed to open TSLIB device, tried /dev/input/ts0 etc ...
when I check /dev/input I have the following present ... event0, event1, mice, mouse0 and ts0
X flickers and crashes.
What does ts_calibrate give you ?
-
tsdev (compaq touchscreen emulation) is scheduled for removal.
See Documentation/feature-removal-schedule.txt for details.
Couldn't load module input
No raw modules loaded.
ts_config: Success
-
tsdev (compaq touchscreen emulation) is scheduled for removal.
See Documentation/feature-removal-schedule.txt for details.
Couldn't load module input
No raw modules loaded.
ts_config: Success
@ZDevil : I think we need those modules ...
-
Off topic - it there a way to test audio? noticed the sound drivers aren't loaded like in titchy.
-
Off topic - it there a way to test audio? noticed the sound drivers aren't loaded like in titchy.
one step at the time - first get X and touchscreen going - then we ask ZDevil ..
-
it's dejavu...
the googlepage forgot to mention the modules for ts.
then I posted in the "OABI vs. EABI" thread saying it is missing and I added the files manually.
But again ... I wrote the script referring to the googlepage guide this morning, but I forgot this bit!
So here they are. Sorry, chero. I bet it should work this time, or I owe you a kratten of trippel ...
https://www.oesf.org/forum/index.php?act=at...ost&id=4996 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4996)
Also I've just updated the afterinstall.sh to include loading usb module. If you fancy getting USB devices working, you can simply do "modprobe ohci-hcd" or try this:
https://www.oesf.org/forum/index.php?act=at...ost&id=4998 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4998)
-
Off topic - it there a way to test audio? noticed the sound drivers aren't loaded like in titchy.
one step at the time - first get X and touchscreen going - then we ask ZDevil ..
Sound works great (i am using 2.6.23.1 yonggun with EABI rootfs). I use the armel packages and they work right away, if my memory doesn't fail me again.
Perhaps writing such a big guy in a short burst is not healthy ...
-
it's dejavu...
the googlepage forgot to mention the modules for ts.
then I posted in the "OABI vs. EABI" thread saying it is missing and I added the files manually.
But again ... I wrote the script referring to the googlepage guide this morning, but I forgot this bit!
So here they are. Sorry, chero. I bet it should work this time, or I owe you a kratten of trippel ...
https://www.oesf.org/forum/index.php?act=at...ost&id=4996 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4996)
Also I've just updated the afterinstall.sh to include loading usb module. If you fancy getting USB devices working, you can simply do "modprobe ohci-hcd" or try this:
https://www.oesf.org/forum/index.php?act=at...ost&id=4998 (https://www.oesf.org/forum/index.php?act=attach&type=post&id=4998)
gonna be drunk someday ...
output of ts_calibrate :
xres = 480 , yres = 640
ts_read : Invalid argument
the screen flickers but I don't get a chance to calibrate ...
-
Dangit ... ts_calibrate works, but X still flickers and dies on me.
complains about;
error opening security policy
-
Dangit ... ts_calibrate works, but X still flickers and dies on me.
complains about;
error opening security policy
what kernel are you using ?
-
kernel.img.2.6.22.9.cpufreq-fastfpe.sd with corisponding modules.
-
kernel.img.2.6.22.9.cpufreq-fastfpe.sd with corisponding modules.
I'm on the 2.6.22 Angstrom kernel => that might explain the calibration problem.
Going to flash a new one ...
-
Dangit ... ts_calibrate works, but X still flickers and dies on me.
complains about;
error opening security policy
Ok, ts_calibrate goes thru, sorry, chero, I am thinking of me having a kratten of duvel ...
Now X....
How do you set it up?
If you have /usr/bin/startx symlinked to /usr/bin/icewm-session-experimental (or any other WM launcher),
AND
the entry "exec icewm-session-experimental" in ~/.xsession,
then
you may get this error.
(because i had this too yesterday.)
solution: remove the line in .xsession
-
Yeah I am on the u-boot. Looking into the startx.
-
YAY ... its an issue with the WM installed ... have unroatted xfce4 running
This is with startxfce4 not the base startx. Got it to rotate by typeing xrandr -o right in the prompt.
-
kernel.img.2.6.22.9.cpufreq-fastfpe.sd with corisponding modules.
I'm on the 2.6.22 Angstrom kernel => that might explain the calibration problem.
Going to flash a new one ...
But yonggun uses uboot...
in fact I really want to see if switching from sharpbootloader to uboot will do nothing to the internal drive.
if that's the case then it's very convenient.
Another holly test is awaiting for you, little chero ...
-
YAY ... its an issue with the WM installed ... have unroatted xfce4 running
This is with startxfce4 not the base startx. Got it to rotate by typeing xrandr -o right in the prompt.
"xrandr -o right" is in the testing afterinstall.sh (~/.xsession). Or you do without it?
(sorry just wanna know if more mistakes are knocking on my door)
-
Brave Chero!
-
The xrandr -o right is in the .profile ... but xfce4 seems to ignore the .profile for some reason.
-
The xrandr -o right is in the .profile ... but xfce4 seems to ignore the .profile for some reason.
But xrandr -o right should do nothing in .profile ...
-
keymap in xfce4 seems to be buggered. Need an xmodmap for the z.
-
hehe ... icewm (-experimental) is more easy-going to me.
-
xrandr -o right in .xsession had no effect
-
How would you add xrandr -o right to some X config file?
(this will be useful for the FAQs -- WMs)
-
installing uboot won't harm my internal drive - done it before.
However : something went wrong - I guess I need my other magical SD-card for flashing the kernel.
I'll do it tomorrow cause that card is at work ....
So far for today's episode - to be continued .
Thanks for all the help;
Goodnight.
BTW : little Chero is already sleeping for 3 hours .
-
xrandr -o right in .xsession had no effect
Add it in "autostarted apps" in xfce-settings.
-
While messing with the files, startxfce now acts just like startx ... yay ...
After running ts_calibrate ... startx fixed itself ... love the wierd
Yeah xrandr -o right works from the autostart app in xfce4, dirty but it will do for now.
-
Found it lol ... manually create in home, .xsession (chmod +x .xsession after you make it)
Should contain this basically;
#!/bin/bash
xrandr -o right
xfce4-session
Hope this helps?
-
Thanks. The afterinstall.sh should have "chmod 4755 ~/.xsession". Upload again.
-
Updated the big guide (071029):
1. Added basic after installation instructions to Debian EABI installation
2. Updated zaurus-hardware-eabi tarball and afterinstall.sh to 0.3 (i think it's better to use the same versioning for both)
Please test, comment, post, have fun.
-
kernel.img.2.6.22.9.cpufreq-fastfpe.sd with corisponding modules.
I'm on the 2.6.22 Angstrom kernel => that might explain the calibration problem.
Going to flash a new one ...
flashed this kernel -> changed .profile to ts0 again -> ts_calibrate works -> startx : icewm loaded.
Now, lets play.
-
Yeah got mine up and running with some apps installed
Abiword, gftp, gnumeric, gqview, xfce4, gps, rox-filer (no rox-wallpaper) etc.
Synaptic, gThumb is broken.
Xfdesktop loads real slow, after the xfwm4 loads.
-
Congrats!
Could you tell me, scottlfa, if network setting and connection just works without adding extra stuff such as the Angtrom packages? I want to keep track of the guide but I forgot what has happened in my case ...
-
I use a NF-2511CF Mercury card;
After udev installed things have been fine.
I did "cat /proc/net/wireless" and eth2 came up (which is a rename of wlan0_rename)
All I had to do was edit the /etc/network/interfaces file and add the following lines;
iface eth2 inet dhpc
wireless essid "wireless"
and off it goes, I manually type ifup eth2 to launch it.
-
Gnome is broken, so too it would seem is kde.
-
scottlfa: try to look at the screen output for the errors.
I also ran into trouble installing some packages and got a mysterious (umount: /mnt/cf not mounted) error. The workaround is to plug in a CF card (suppose the packages are already downloaded to /var/cache/apt/archives) and run apt-get install again.
Would that be the same story?
If that still fails, we can consider building them on our own, and put them in a new custom package feed...
Okay, time to switch to hyperwork mode. Hope I can be back tomorrow night ...
-
running from the sd card ... and the errors I get are related to packages that it won't install.
-
running from the sd card ... and the errors I get are related to packages that it won't install.
Check this page for "sources.list" : http://yonggun.tistory.com/54 (http://yonggun.tistory.com/54)
Do an ap-get update and try installing them again.
(I was using other mirrors before with errors and this one solved it)
Chero.
-
Found two more issues in the guide:
-- Wireless network connection: the prerequisite packages libiw29_29-1_armel.deb and wireless-tools_29-1_armel.deb are missing; install them to get network connection before the first apt-get update. (Thanks, chero)
-- Sound: you need to "modprobe snd-soc-spitz" first to get sound, and "echo snd-soc-spitz >> /etc/modules" to make this run all the time.
The 0.4 version will have this. It will also try to incorporate yonggun's bits. (Bravo, 2or0)
0.4 will be up tonight.
-
scottlfa, since your are using uboot on C1000 (uboot is cool, i begin to love it) would you mind testing kernel 2.6.23.1 yonggun? I asked 2or0 and he said in principle it should work, even though the kernel has "hda1" in the name.
If this works then I will also add this to Q20.
If things go well, after this revision I think the content is reasonably stable to be put to the wiki, and it will be open to all for editing.
Remember this is NOT my work, but is a collaboration of a number of enthusiastic players in the field.
-
scottlfa, since your are using uboot on C1000 (uboot is cool, i begin to love it) would you mind testing kernel 2.6.23.1 yonggun? I asked 2or0 and he said in principle it should work, even though the kernel has "hda1" in the name.
If this works then I will also add this to Q20.
If things go well, after this revision I think the content is reasonably stable to be put to the wiki, and it will be open to all for editing.
Remember this is NOT my work, but is a collaboration of a number of enthusiastic players in the field.
I believe that installing this on C1000 is exactly same as what I did on C3200 on SD. But it sould be confirmed by C1000 users.
-
I am still sitting on the fence with respect to eabi/armel. I am confused about the X server. it seems that 2or0 is using the xserver-xorg-video-fbdev server rather than the kdrive server we use in Titchy. Is that correct? Isn't that going to place a greater burden on the resources? OTOH, this server allows configuration options (like a config file!) not used in the kdrive, so that would be worthwhile.
Sorry to not just jump in and see for myself, but I need to have this machine running for a trip in 2 weeks. Is that feasible?
-
I am still sitting on the fence with respect to eabi/armel. I am confused about the X server. it seems that 2or0 is using the xserver-xorg-video-fbdev server rather than the kdrive server we use in Titchy. Is that correct? Isn't that going to place a greater burden on the resources? OTOH, this server allows configuration options (like a config file!) not used in the kdrive, so that would be worthwhile.
Sorry to not just jump in and see for myself, but I need to have this machine running for a trip in 2 weeks. Is that feasible?
No, debian(armel) is using xserver-kdrive-fbdev. Check here: http://yonggun.tistory.com/54 (http://yonggun.tistory.com/54)
-
I wonder why we have to install xserver-xorg-video-fbdev first is because we need to pull down the dependencies and not xorg itself. The repackaged kdrive xfbdev server also needs these dependencies but it doesn't not chase them. Or am i mistaken here?
Also, 2or0, in your guide you mention to apt-get -f install. Is it the workaround of the glibc dependency error when installing libconsole_0.2.3dbs-65_armel.deb, console-tools_0.2.3dbs-65_armel.deb, libiw29_29-1_armel.deb, wireless-tools_29-1_armel.deb (these are four initial packages to install in order to get other things going)?
-
I wonder why we have to install xserver-xorg-video-fbdev first is because we need to pull down the dependencies and not xorg itself. The repackaged kdrive xfbdev server also needs these dependencies but it doesn't not chase them. Or am i mistaken here?
Also, 2or0, in your guide you mention to apt-get -f install. Is it the workaround of the glibc dependency error when installing libconsole_0.2.3dbs-65_armel.deb, console-tools_0.2.3dbs-65_armel.deb, libiw29_29-1_armel.deb, wireless-tools_29-1_armel.deb (these are four initial packages to install in order to get other things going)?
First two packages are for keymap, and rest are for wireless. If you have errors, it is probably due to libiw29_29-1_armel.deb and wireless-tools_29-1_armel.deb. When I set it up, I used libiw28_28 and wireless-tools_28. I fixed this in my blog.
-
I wonder why we have to install xserver-xorg-video-fbdev first is because we need to pull down the dependencies and not xorg itself. The repackaged kdrive xfbdev server also needs these dependencies but it doesn't not chase them. Or am i mistaken here?
Also, 2or0, in your guide you mention to apt-get -f install. Is it the workaround of the glibc dependency error when installing libconsole_0.2.3dbs-65_armel.deb, console-tools_0.2.3dbs-65_armel.deb, libiw29_29-1_armel.deb, wireless-tools_29-1_armel.deb (these are four initial packages to install in order to get other things going)?
First two packages are for keymap, and rest are for wireless. If you have errors, it is probably due to libiw29_29-1_armel.deb and wireless-tools_29-1_armel.deb. When I set it up, I used libiw28_28 and wireless-tools_28. I fixed this in my blog.
I thought from the installation of xserver-xorg-video-fbdev and similar things that this would be the server we'd use. That explains, I guess, what is going on.
But, when you say "I fixed this in my blog", do we now use the 28 version, or the 29?
-
I wonder why we have to install xserver-xorg-video-fbdev first is because we need to pull down the dependencies and not xorg itself. The repackaged kdrive xfbdev server also needs these dependencies but it doesn't not chase them. Or am i mistaken here?
Also, 2or0, in your guide you mention to apt-get -f install. Is it the workaround of the glibc dependency error when installing libconsole_0.2.3dbs-65_armel.deb, console-tools_0.2.3dbs-65_armel.deb, libiw29_29-1_armel.deb, wireless-tools_29-1_armel.deb (these are four initial packages to install in order to get other things going)?
First two packages are for keymap, and rest are for wireless. If you have errors, it is probably due to libiw29_29-1_armel.deb and wireless-tools_29-1_armel.deb. When I set it up, I used libiw28_28 and wireless-tools_28. I fixed this in my blog.
I thought from the installation of xserver-xorg-video-fbdev and similar things that this would be the server we'd use. That explains, I guess, what is going on.
But, when you say "I fixed this in my blog", do we now use the 28 version, or the 29?
Yes, we don't need xorg-related stuff so that I removed them: apt-get remove xorg*, Everything is fine upto now. And I used version 28. Thanks,
-
A new one-stop after installation tarball with automated scripts are almost done. This is primarily an integration of 2or0's stuff.
This will simplify the after installation process and save time a lot.
Will be up in a couple of hours.
Thanks to 2or0 for the great work.
-
The new mega after installation tarball (including all the necessary packages and scripts) is here:
[EDIT]
I have removed the 1.0a tarball here and uploaded a revised 1.0b to Post #13 (Q12) in this thread.
It integrates all of 2or0's packages and scripts together with my old zaurus-hardware-eabi tarball (on page 3) into one big whole, with two after installation scripts that simplify the finetuning processes.
Have fun!
-
Q12: I've already got the right kernel. Where can I get the Debian EABI system?
A12: You will extract the rootfs tarball and install it locally. Get the rootfs tarball here: http://armel.applieddata.net/developers/li...root-fs.tar.bz2 (http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2)
should not we use this rootfs instead ?
http://www.applieddata.net/developers/linu...mel-2007-08-27/ (http://www.applieddata.net/developers/linux/files/debian/root-armel-2007-08-27/)
it seems more recent than the january one
-
Q12: I've already got the right kernel. Where can I get the Debian EABI system?
A12: You will extract the rootfs tarball and install it locally. Get the rootfs tarball here: http://armel.applieddata.net/developers/li...root-fs.tar.bz2 (http://armel.applieddata.net/developers/linux/eabi/armel-root-fs.tar.bz2)
should not we use this rootfs instead ?
http://www.applieddata.net/developers/linu...mel-2007-08-27/ (http://www.applieddata.net/developers/linux/files/debian/root-armel-2007-08-27/)
it seems more recent than the january one
Oh, i was not aware that there is a newer rootfs tarball. But I suppose it's just the same after apt-get dist-upgrade.
Anyway I will post the questions to the wiki tonight. So feel free to change that.
-
Oh, i was not aware that there is a newer rootfs tarball. But I suppose it's just the same after apt-get dist-upgrade.
i think like you i'll try it and report here
-
Thanks. My question is I am not sure to what extent it is different from the January rootfs regarding after installation matters.
-
In the instructions to go on up to eabi/yonggun, it says to format the internal harddrive with two partitions, one for stuff and one for swap. I am old, and don't like to change my ways. I have always made several partitions, to protect my personal data from a screw-up in the distribution, and to protect both from problems with files that are constantly overwritten, like log files.
So, will I be asking for trouble if I set up separate /home and /var parititions? I will play by the rules if need be, but would rather reserve space for these.
-
In the instructions to go on up to eabi/yonggun, it says to format the internal harddrive with two partitions, one for stuff and one for swap. I am old, and don't like to change my ways. I have always made several partitions, to protect my personal data from a screw-up in the distribution, and to protect both from problems with files that are constantly overwritten, like log files.
So, will I be asking for trouble if I set up separate /home and /var parititions? I will play by the rules if need be, but would rather reserve space for these.
Not at all, it is perfectly ok to have several partitions. Just make sure that /etc/fstab has the correct entries and the mounting lines are in an appropriate order. For example, /dev/hda1 (mounting to /) should always go first, followed by others.
-
Just wondered about this step.
CODE
cd afterinstall
./1st-cfg.sh
To use / doesn't the keymap have to have been set? I presume you could just do afterinstall/1st-cfg.sh, where the / came from using the tab key autocompletion bit?
Does this not apply to the instructions about the 2nd-cfg.sh script?
I'm having a play at using the angstrom 2.6.23 kernel and modules. I got the console login and set up the wireless and the console tools. Couldn't get the key map sorted out and the sources.list had to be fiddled with cut and paste. I did something wrong and the repos wouldn't update. I was following jpmatrix's thread and the 20r0 website.
So I'm now trying to follow the post 17 instructions. hence my query above. I take it you are using jpmatrix's wiki for discussion also?
Cheers
-
I found a small issue in the zaurus-debian-eabi-afterinstall_1.0.tar.gz:
In the 1st-cfg.sh, there is a step cd to /sbin, which should be avoided because at the end of the first part the user will end up there.
Will replace the upload with a 1.0a version shortly.
-
Just wondered about this step.
CODE
cd afterinstall
./1st-cfg.sh
To use / doesn't the keymap have to have been set? I presume you could just do afterinstall/1st-cfg.sh, where the / came from using the tab key autocompletion bit?
Does this not apply to the instructions about the 2nd-cfg.sh script?
I'm having a play at using the angstrom 2.6.23 kernel and modules. I got the console login and set up the wireless and the console tools. Couldn't get the key map sorted out and the sources.list had to be fiddled with cut and paste. I did something wrong and the repos wouldn't update. I was following jpmatrix's thread and the 20r0 website.
So I'm now trying to follow the post 17 instructions. hence my query above. I take it you are using jpmatrix's wiki for discussion also?
Cheers
Thanks!
Just give the absolute path will do (by using [Tab] to get to the subdir).
Will modify the instructions accordingly.
By the time you start 2nd-cfg.sh, the keymap will have been loaded and added to a boot script (done by 1st-cfg.sh).
-
Hi ZDevil, I've just put something on the new page you started over on the OESF Wiki. Feel free to remove it. I put a reason for my edit at the talk/discussion page for the new page. I also put a welbcome note in the ZDevil Talk page.
I'm waiting for the rootfs to copy over on BigZ at the moment. Last night was another 3 am finish for me!
Not tonight though!
-
That's good.
I will just add the stuff here following yours.
Do let me know how the after installation stuff go. Let me hold out for the wiki until I am sure it works.
And the zaurus-debian-eabi-afterinstall tarball is supposed to save you a lot of time and effort fiddling with the configurations....
-
That's good.
I will just add the stuff here following yours.
Do let me know how the after installation stuff go. Let me hold out for the wiki until I am sure it works.
And the zaurus-debian-eabi-afterinstall tarball is supposed to save you a lot of time and effort fiddling with the configurations....
You know you give instructions for getting to the OK menu in your posts? We are in the B+D console. Just do reboot and hold the OK button down when it says it is rebooting. You land in the right place from there. If you mistime it you just follow your instructions.
I forgot to do jpmatrix's tip of populating the consoles. I'm stuck at 'unable to open an initial console'. So I'm going to have to go back in to B+D anyway...
-
Are you talking about the end of Step 3 in Q17?
I would just add a line at the end of the DB mode saying reboot while pressing the [OK] button, because you need to go to the Flash Menu (not DB mode) to flash the kernel.
I'm going to have a look at jpmatrix's note about populating the consoles. I remember in my case I did nothing, but a simple reboot will get over this error.
-
Are you talking about the end of Step 3 in Q17?
I would just add a line at the end of the DB mode saying reboot while pressing the [OK] button, because you need to go to the Flash Menu (not DB mode) to flash the kernel.
I'm going to have a look at jpmatrix's note about populating the consoles. I remember in my case I did nothing, but a simple reboot will get over this error.
Sorry, yes I was. I didn't try just a reboot. I did jpmatrix's tip.
1st script works fine.
I got this message when I tried apt-get update: Malformed line 1 in source list /etc/apt/sources.list (URI parse). And the keymap has gone awol! I actually got this message throughout the running of 2nd script?
Is this because I'm using the 2.6.23 kernel?
Suggestions for easy access to 2.6.20 kernel and modules? Yes I am giving angstrom a chance.
-
It should be my script. I just copy the links from 2or0's page and we both checked and didn't spot the error. But I will look into that. It is not anything critical.
Can you verify that after running 1st-cfg.sh, the keymap is working?
And for now can you manually edit /etc/apt/sources.list and try to proceed with the rest of 2nd-cfg.sh?
Thanks for your brave testing!
-
Are you talking about the end of Step 3 in Q17?
I would just add a line at the end of the DB mode saying reboot while pressing the [OK] button, because you need to go to the Flash Menu (not DB mode) to flash the kernel.
I'm going to have a look at jpmatrix's note about populating the consoles. I remember in my case I did nothing, but a simple reboot will get over this error.
Sorry, yes I was. I didn't try just a reboot. I did jpmatrix's tip.
1st script works fine.
I got this message when I tried apt-get update: Malformed line 1 in source list /etc/apt/sources.list (URI parse). And the keymap has gone awol! I actually got this message throughout the running of 2nd script?
Is this because I'm using the 2.6.23 kernel?
Suggestions for easy access to 2.6.20 kernel and modules? Yes I am giving angstrom a chance.
hi
i'm re-installing from scratch too and i 'm stuck at this stage too : "unable to open initial console"
i tried to reboot with no luck...
i wonder how zdevil succeed in ... perhaps because of uboot i don't use?
-
@jpmatrix: which method (which Q) are you using? can you do the same trick as you did to get around this?
-
@jpmatrix: which method (which Q) are you using? can you do the same trick as you did to get around this?
i'm using Q17,
with rootfs from here http://www.applieddata.net/developers/linu...mel-2007-08-27/ (http://www.applieddata.net/developers/linux/files/debian/root-armel-2007-08-27/)
yeah i did the same MAKEDEV trick and now debian is up and running
uname -a :
Linux adsdebian 2.6.23 #1 ...
i haven't (yet) used the zaurus-debian-eabi-afterinstall_1.0.tar.gz file
-
Thanks. Will add this to the instructions.
(Perhaps I also did this step but i am confused by so many times of reinstallation... that's why your notes are very important )
-
@jpmatrix: which method (which Q) are you using? can you do the same trick as you did to get around this?
Hello each! jpmatrix: I just rebooted into the B+D console and did that MAKEDEV thing! It booted into Debian then. I could not find an updater.sh that would download in the 2.6.23 section and I cannot find earlier kernels and modules for the 3200 on the angstrom site. I used an updater from the Bigbridge site.
ZDevil your 1st script works fine, I have the keymap, I can set up the wifi etc. Just that the 2nd script fails with claims that the first line of sources.list is malformed. The keymap didn't last through rebooting and the hardware clock is not accessed. The only error is the report about the malformed line.
I'm not brave, I'm foolhardy!
I have tried editing the sources.list before I got the keyboard sorted by doing cut and paste. If I delete the first line it doesn't like the second/remaining line.
I have things I can try for the keyboard and the hwclock: from peeking into neil's scripts in his packages. I'll get back to you on that.
The repository thing worries me. I don't normally use ftp repos, so I'm looking very suspiciously at the lines. I will try and destroy the sources.list and recreate from scratch.
See you in a bit.
With my OABI + OABI experiments I did get repositories that worked: just got very little progress on the gui set up.
Back later.
-
@tux:
You are right again. I left out the hwclock rules. Will add it to 1.0b.
The rules file was in the old zaurus-hardware-eabi tarball. But I was too dim last night busy gluing 2or0's stuff together and forgort to put that back in. Thank you!
I will add "hwclock -w" early in the 1st script, so that your clock will be saved even if things go wild in the 2nd.
Actually I also am not using 2or0's feed locations.
See if this fits:
deb http://armel-debs.applieddata.net/debian (http://armel-debs.applieddata.net/debian) sid main
This is the one I am using and it works just fine.
-
i'm using Q17,
with rootfs from here http://www.applieddata.net/developers/linu...mel-2007-08-27/ (http://www.applieddata.net/developers/linux/files/debian/root-armel-2007-08-27/)
yeah i did the same MAKEDEV trick and now debian is up and running
uname -a :
Linux adsdebian 2.6.23 #1 ...
well well
it seems lots of packages are now pre-installed with this 0827 rootfs : console-tools, wireless-tools, tzdata...
and i could launch wifi @ home with few command lines!
apt-get is running now!
-
well well
it seems lots of packages are now pre-installed with this 0827 rootfs : console-tools, wireless-tools, tzdata...
and i could launch wifi @ home with few command lines!
apt-get is running now!
That's good news. That means the after install process can be further simplified.
Yet I suppose the stuff in the 2nd-cfg.sh is still relevant, if there are no working kdrive xfbdev and touchscreen tools in the new rootfs...
-
@tux:
You are right again. I left out the hwclock rules. Will add it to 1.0b.
The rules file was in the old zaurus-hardware-eabi tarball. But I was too dim last night busy gluing 2or0's stuff together and forgort to put that back in. Thank you!
I will add "hwclock -w" early in the 1st script, so that your clock will be saved even if things go wild in the 2nd.
Actually I also am not using 2or0's feed locations.
See if this fits:
deb http://armel-debs.applieddata.net/debian (http://armel-debs.applieddata.net/debian) sid main
This is the one I am using and it works just fine.
I've sorted the keymap. I used 2or0's tip from his site. After twiddling the rc.local file to be sure the instruction was before the exit 0 line. The repo you give me is giving me problems. It says some index files failed to download... I'll keep checking. The hwclock thing is fighting me!!
I should have said: the start-stop-daemon seems to be borked. The tip from 2or0's site won't work because start-stop-daemon.REAL is not present. The rpo does not work for me. apt-get goes and looks, can't find the .gz file and when i ask it to install something it gives me a 404 message. I'm going to try and run your 2nd-cfg again to see what happens.
jpmatrix, can you post your sources.list? But I'm getting further...
-
@tux: Are you sure your network connection is working?
I just did an apt-get update with this feed and it just works...
-
I've sorted the keymap.I used 2or0's tip from his site. After twiddling the rc.local file to be sure the instruction was before the exit 0 line.
That's interesting, because what is in the script is exactly 2or0's thing...
-
@tux: Are you sure your network connection is working?
I just did an apt-get update with this feed and it just works...
No it isn't! I can ping my router quite happily! But when I ping www.oesf.org it says 'unknown host'. It was working shortly after the install because I could ping www.google.com. I'd better check what has happened with the host file etc. Thanks for the wake-up!
I shan't post again tonight. I need sleep!
-
Chero, test this if you can't wait (actually because I can't wait to see your result ... ).
There are three little extra steps involved:
1. Add these extra files:
-- Download these essential utilities to the SD:
http://armel-debs.applieddata.net/debian/p...bs-65_armel.deb (http://armel-debs.applieddata.net/debian/pool/main/c/console-tools/libconsole_0.2.3dbs-65_armel.deb)
http://armel-debs.applieddata.net/debian/p...bs-65_armel.deb (http://armel-debs.applieddata.net/debian/pool/main/c/console-tools/console-tools_0.2.3dbs-65_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...2-8.1_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/a/apmd/apmd_3.2.2-8.1_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...9p6-1_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/s/sudo/sudo_1.6.9p6-1_armel.deb)
-- Put these attachments to the SD too:
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
2. Follow the steps as described, and after extracting the rootfs and the kernel modules, extract the zaurus-hardware-eabi thingie also.
3. After the first login:
-- First install those few armel packages.
-- Then run the afterinstall.sh (remove the .txt extension).
the first two links are down, but they are on kfreebsd as well - first have to eat now - will continue this afternoon
i had problems with this repo two days ago when i installed my debian for my c1000. There is an other repo (duplicate or an other domain name):
http://ftp.gnuab.org/debian (http://ftp.gnuab.org/debian)
-
@tux: Are you sure your network connection is working?
I just did an apt-get update with this feed and it just works...
No it isn't! I can ping my router quite happily! But when I ping www.oesf.org it says 'unknown host'. It was working shortly after the install because I could ping www.google.com. I'd better check what has happened with the host file etc. Thanks for the wake-up!
I shan't post again tonight. I need sleep!
I lied! I looked in the rootfs tar and spied on the host and hosts file. i restored some bits I chucked out when i put my nameserver info in. I can now ping www.google.com etc. I still don't get apt-get update to work...
By the way ZDevil, the keymap fix you have in the directory won't work. it puts the 'fix' after the exit 0 line. There is a problem with this start-stop daemon. I'm going to fiddle with reversing the fix and see what happens.
-
..snip..Yet I suppose the stuff in the 2nd-cfg.sh is still relevant, if there are no working kdrive xfbdev and touchscreen tools in the new rootfs...
oh it seems there's an x server installed in 0827 rootfs with lwm as window manager !!!
however it doesn't want to start with my root user and my usual user get permission problems...
ohhh sleeeeeep time see you tomorrow
-
i had problems with this repo two days ago when i installed my debian for my c1000. There is an other repo (duplicate or an other domain name):
http://ftp.gnuab.org/debian (http://ftp.gnuab.org/debian)
Thanks for this: it is working as I type!!
I am not going to risk running the 2nd script. I'll try doing a dpkg install in the afterinstall directory... The packages from the second script look like they are being fixed by apt-get -f install!!
I think my problems were partly because I used the tips from 2or0 manually before noticing the script tarball and trying to use those. There are a couple of tiny glitches in the scripts, but ZDevil is doing a hefty piece of work there! Thanks again ZDevil.
I'll drink a large rum to zecrazytux, I thought I might need to redo the install.... Saved!
-
By the way ZDevil, the keymap fix you have in the directory won't work. it puts the 'fix' after the exit 0 line. There is a problem with this start-stop daemon. I'm going to fiddle with reversing the fix and see what happens.
Could you be more specific about the keymap case? I still don't quite get what you mean by the "fix" and the "exit 0" (neither in the script nor in the keymap ... )
The keymap was copied directly from my Z, which should work, otherwise my Z won't be doing anything these days. (The scripts and the files were done on my Z)
The start-stop daemon part is from 2or0. Maybe he can answer this.
-
..snip..Yet I suppose the stuff in the 2nd-cfg.sh is still relevant, if there are no working kdrive xfbdev and touchscreen tools in the new rootfs...
oh it seems there's an x server installed in 0827 rootfs with lwm as window manager !!!
however it doesn't want to start with my root user and my usual user get permission problems...
Is the X server xorg or kdrive?
-
By the way ZDevil, the keymap fix you have in the directory won't work. it puts the 'fix' after the exit 0 line. There is a problem with this start-stop daemon. I'm going to fiddle with reversing the fix and see what happens.
Could you be more specific about the keymap case? I still don't quite get what you mean by the "fix" and the "exit 0" (neither in the script nor in the keymap ... )
The keymap was copied directly from my Z, which should work, otherwise my Z won't be doing anything these days. (The scripts and the files were done on my Z)
The start-stop daemon part is from 2or0. Maybe he can answer this.
Hi ZDevil, I'll do my best to explain. In the first script the keymap fix is this:
# keymap
echo "Now let's load the right keymap for your Zaurus..."
cp keymap.map /etc/keymap.map &&
loadkeys /etc/keymap.map &&
echo "loadkeys /etc/keymap.map" >> /etc/rc.local &&
echo "Done."
echo ""
The bit in bold appends the loadkeys command to the end of the rc.local file.
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
<====== here is where the loadkeys bit should go, I think.
exit 0
<============ it actually gets put here.
I know because I've edited the file after running the script, it worked when I moved the line.
When this happens the script doesn't work. It does work if you edit the copied line to come before the exit 0 part. I could of course be talking rubbish from the effects of lack of sleep. It's easy to check this out.
Now the bit about start-stop-daemon is easy to explain. There is nothing wrong with your script. My problem was that I did 2or0's fix for this daemon manually. I then ran your script. This resulted in a non-working daemon. I extracted the two necessary files from the tar and copied them into sbin. I then ran the commands from your script and it did what it was supposed to. So that problem was of my own making.
I have a non-responsive gui screen in front of me. Your second script worked fine with me using zecrazytux's repository suggestion.
I now need to sort out the touch screen aetc. But that will no doubt be explained somewhere in the posts in this thread. I must go to bed!
Cheers
-
Hey, tux,
And this is what I need! I really need to find out exactly whether the issue comes from the scirpt itself or from other external factors.
keymap & /etc/rc.local:
Now I see the problem. Merci beaucoup!
It is funny because I the same line was in the older zaurus-hardware-eabi tarball, but no one seemed to run into/spot this error.
But that is easy to fix, anyway.
[EDIT]
Here is my fix. In 1st-cfg.sh Line 49, replace
echo "loadkeys /etc/keymap.map" >> /etc/rc.local &&
with
sed -i '/exit 0/ i\loadkeys /etc/keymap.map' /etc/rc.local &&
which works in my foo file.
start-stop-daemon:
Both scripts are intended to be used only once with a clean, fresh install without any tweaking. So again mixing and applying different tweaks together may have unexpected results, such as the start-stop-daemon thing. I should state this clearly in the instructions.
But of course before this happens, we expect to see some glitches in the scripts...
Package feeds in sources.list:
I'll put both feed locations of zecrazytux's and mine in the sources.list. apt-get will be smart enough to grab packages from either.
Glad to know that the rest of the scripts run well. Thanks!
This is exactly why rushing to post to the wiki is not the best thing ... :lol
Please don't hesitate to report here if there is any other issue about the scripts. I'll do my best to make things work.
-
..snip..Yet I suppose the stuff in the 2nd-cfg.sh is still relevant, if there are no working kdrive xfbdev and touchscreen tools in the new rootfs...
oh it seems there's an x server installed in 0827 rootfs with lwm as window manager !!!
however it doesn't want to start with my root user and my usual user get permission problems...
Is the X server xorg or kdrive?
i'd say xorg but i'm not sure since i've first tried to instal kdrive before i see that there was yet an x server! and kdrive got conflicts....
-
Hey, tux,
And this is what I need! I really need to find out exactly whether the issue comes from the scirpt itself or from other external factors.
keymap & /etc/rc.local:
Now I see the problem. Merci beaucoup!
It is funny because I the same line was in the older zaurus-hardware-eabi tarball, but no one seemed to run into/spot this error.
But that is easy to fix, anyway.
[EDIT]
Here is my fix. In 1st-cfg.sh Line 49, replace
echo "loadkeys /etc/keymap.map" >> /etc/rc.local &&
with
sed -i '/exit 0/ i\loadkeys /etc/keymap.map' /etc/rc.local &&
which works in my foo file.
start-stop-daemon:
Both scripts are intended to be used only once with a clean, fresh install without any tweaking. So again mixing and applying different tweaks together may have unexpected results, such as the start-stop-daemon thing. I should state this clearly in the instructions.
But of course before this happens, we expect to see some glitches in the scripts...
Package feeds in sources.list:
I'll put both feed locations of zecrazytux's and mine in the sources.list. apt-get will be smart enough to grab packages from either.
Glad to know that the rest of the scripts run well. Thanks!
This is exactly why rushing to post to the wiki is not the best thing ... :lol
Please don't hesitate to report here if there is any other issue about the scripts. I'll do my best to make things work.
Glad to be of help. Just trying cortez files and method. I thought I'd need to start again with the Q17 method anyway. So I can test this and, unless I decide to persevere with the cortaz/popky one, I can try this method later on.
-
i've just run the 2nd-cfg.sh:
it ends with :
libsdl1.2debian-alsa is not installed (required for mplayer)
then
Now installing a few more hardare xxxx
2nd-cfg.sh : line 74 : dkpg : command not found (little typo here
-
Thanks again. Could you edit this manually and see if the 2nd-cfg.sh runs to the end?
-
Thanks again. Could you edit this manually and see if the 2nd-cfg.sh runs to the end?
oh too late :
i run the correct dpkg -i with all packages of line 74
but i'm encoutering some dependencies troubles
now i'm running apt-get -f install and it seems to do the job
EDIT: i had to apt-get install apmd too ; it was not installed
-
Could you let me know which packages and dependencies are missing? I will add them to the tarball too.
-
One more thing see if it helps:
The 2nd-cfg.sh can actually be run again without doing harm to the system (i believe), because it is basically an installation script for a number of packages from the feeds and those prepared by yonggun (2or0).
-
I'll drink a large rum to zecrazytux, I thought I might need to redo the install.... Saved!
huhu, join us now and share the rhuuuum, you'll be freeee, hacker...
Does anybody ever tried to use kazehakase ? i got a segfault :-(
I still have problems with the keymap: i can't get a right click, even when using keylaunch :-(
The ctrl and alt keys are well recognized (as i can do a ctrl alt arrow to switch desktops or alt tab to switch windows)
if it can helps:
- for X:
- i took xserver-kdrive-fbdev from angstrom
- make sure /etc/X11/X is a symbolic link to /usr/bin/Xfbdev (or use the .xserverrc config file to specify wich xserver should be used)
- on SID, remove the file /etc/X11/xorg.conf, it works great without
- i used tslib (and other ts packages like tslib-conf) from angstrom:
add "expor TSLIB_TSDEVICE=/dev/input/event1" to your /etc/rc.local script
- rmmod mousedev (i haven't looked how to disable the loading of this module at boot, yet)
and as explain everywhere, just write a tiny .xsession configuration file to start your graphical session with startx
so i now need to fix the right click and to configure openbox and fbpanel
if somebody is interested i certainly could release a sid quite correctly configured rootfs.
-
Chero, test this if you can't wait (actually because I can't wait to see your result ... ).
There are three little extra steps involved:
1. Add these extra files:
-- Download these essential utilities to the SD:
http://armel-debs.applieddata.net/debian/p...bs-65_armel.deb (http://armel-debs.applieddata.net/debian/pool/main/c/console-tools/libconsole_0.2.3dbs-65_armel.deb)
http://armel-debs.applieddata.net/debian/p...bs-65_armel.deb (http://armel-debs.applieddata.net/debian/pool/main/c/console-tools/console-tools_0.2.3dbs-65_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...2-8.1_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/a/apmd/apmd_3.2.2-8.1_armel.deb)
http://kfreebsd-gnu.debian.net/debian/pool...9p6-1_armel.deb (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/s/sudo/sudo_1.6.9p6-1_armel.deb)
-- Put these attachments to the SD too:
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
2. Follow the steps as described, and after extracting the rootfs and the kernel modules, extract the zaurus-hardware-eabi thingie also.
3. After the first login:
-- First install those few armel packages.
-- Then run the afterinstall.sh (remove the .txt extension).
the first two links are down, but they are on kfreebsd as well - first have to eat now - will continue this afternoon
i had problems with this repo two days ago when i installed my debian for my c1000. There is an other repo (duplicate or an other domain name):
http://ftp.gnuab.org/debian (http://ftp.gnuab.org/debian)
I noticed it is not a good idea to mix repo-s. I was mixing applieddata and kfreebsg-gnu, but it gave me lots of dependency-errors. When switching to ftp.easynet.be for everything (main and unreleased) it all installs smoothly :
- gnumeric
- evolution
- dates - contacts - tasks
- homebank
- wxwidgets
- leafpad
- icewm-experimental - xfce - xfce-goodies
- ...
-
I noticed it is not a good idea to mix repo-s. I was mixing applieddata and kfreebsg-gnu
kfreebsd's binaries works great with a linux kernel ?
well, gnuab.org is the official armel debian repository, and it seems the packages from applieddata and gnuab are exactly the same (look the versions, date and time they where uploaded)
To me, that's only a question of qos
gnuab is always up, whereas i had problems with applied going down
-
I still have problems with the keymap: i can't get a right click, even when using keylaunch :-(
The ctrl and alt keys are well recognized (as i can do a ctrl alt arrow to switch desktops or alt tab to switch windows)
if it can helps:
- for X:
- i took xserver-kdrive-fbdev from angstrom
- make sure /etc/X11/X is a symbolic link to /usr/bin/Xfbdev (or use the .xserverrc config file to specify wich xserver should be used)
- on SID, remove the file /etc/X11/xorg.conf, it works great without
- i used tslib (and other ts packages like tslib-conf) from angstrom:
add "expor TSLIB_TSDEVICE=/dev/input/event1" to your /etc/rc.local script
- rmmod mousedev (i haven't looked how to disable the loading of this module at boot, yet)
and as explain everywhere, just write a tiny .xsession configuration file to start your graphical session with startx
so i now need to fix the right click and to configure openbox and fbpanel
if somebody is interested i certainly could release a sid quite correctly configured rootfs.
That's a very instructive post. Thanks!
1) No right-click: I also discovered this using 2.6.23.1 yonggun (even with keylaunch). 2or0, any hint?
2) X and touchscreen: My original zaurus-hardware-eabi tarball had all these settings (.xsession, .xserverrc, touchscreen settings etc). 2or0 told me his repackaged Angstrom debs can manage all these. Perhaps I need to extract the repackaged Angstrom debs in the new tarball and see if there is anything to add to. What do you think, 2or0?
2or0's xserver package is already using Angstrom's kdrive.
Sidenote: It seems to me that touchscreen pointer can use /dev/input/ts0, /dev/input/event1 or /dev/input/touchscreen0, as long the ts modules are in place (under /usr/lib/ts).
I would export TSLIB_TSDEVICE in ~/.profile, but it's just the same.
3) Things to add to the after installation scripts:
-- rm /usr/bin/X && ln -s xfbdev /usr/bin/X
-- rm /etc/X11/xorg.conf
-- rmmod /dev/mousedev
-
I found an issue with the x-yonggun package:
It's very nice to have the xmodmap from pdaXrom (under /etc/X11/kb).
And the settings use xbindkey to map L/M/R mouse buttons to XF86LaunchA, XF86LaunchB, XF86LaunchC (Calendar, Address, Mail) respectively.
However, these three keys don't seem to work.
In xev, they don't seem to map to any keycode or keysym.
I also noticed that the basic settings in .xsession are handled in the included .xinitrc, which is nice. (I feel home more with this as I used to pdaXrom a lot ).
Interestingly the five silkscreen keys do show something in xev (from top to bottom):
87 = F15
89 = F16
84 = F17
79 = F18
81 = F19
So does that mean we can make use of these mappings also? (If positive then I feel even closer to pdaXrom ... )
-
I still have problems with the keymap: i can't get a right click, even when using keylaunch :-(
The ctrl and alt keys are well recognized (as i can do a ctrl alt arrow to switch desktops or alt tab to switch windows)
if it can helps:
- for X:
- i took xserver-kdrive-fbdev from angstrom
- make sure /etc/X11/X is a symbolic link to /usr/bin/Xfbdev (or use the .xserverrc config file to specify wich xserver should be used)
- on SID, remove the file /etc/X11/xorg.conf, it works great without
- i used tslib (and other ts packages like tslib-conf) from angstrom:
add "expor TSLIB_TSDEVICE=/dev/input/event1" to your /etc/rc.local script
- rmmod mousedev (i haven't looked how to disable the loading of this module at boot, yet)
and as explain everywhere, just write a tiny .xsession configuration file to start your graphical session with startx
so i now need to fix the right click and to configure openbox and fbpanel
if somebody is interested i certainly could release a sid quite correctly configured rootfs.
That's a very instructive post. Thanks!
1) No right-click: I also discovered this using 2.6.23.1 yonggun (even with keylaunch). 2or0, any hint?
2) X and touchscreen: My original zaurus-hardware-eabi tarball had all these settings (.xsession, .xserverrc, touchscreen settings etc). 2or0 told me his repackaged Angstrom debs can manage all these. Perhaps I need to extract the repackaged Angstrom debs in the new tarball and see if there is anything to add to. What do you think, 2or0?
2or0's xserver package is already using Angstrom's kdrive.
Sidenote: It seems to me that touchscreen pointer can use /dev/input/ts0, /dev/input/event1 or /dev/input/touchscreen0, as long the ts modules are in place (under /usr/lib/ts).
I would export TSLIB_TSDEVICE in ~/.profile, but it's just the same.
3) Things to add to the after installation scripts:
-- rm /usr/bin/X && ln -s xfbdev /usr/bin/X
-- rm /etc/X11/xorg.conf
-- rmmod /dev/mousedev
1) First, I should mention that xserver-kdrive-fbdev is not from angstrom. Look at this thread: https://www.oesf.org/forum/index.php?s=&...st&p=163836 (https://www.oesf.org/forum/index.php?s=&showtopic=23773&view=findpost&p=163836)
When I used angstrom fbdev, mouse keys did not work but thanks to svs57 I could use mouse keys.
2) I don't think that my setting will work on angstrom kernel. So when I repackaged angstrom ones, I had to carefully take a look the script and to add settings for my kernel. For example, TSLIB_TSDEVICE = /dev/input/ts0 in mine but /dev/input/touchscreen0 in angstrom.
3) In my package, xserver loads Xfbdev instead of X. You don't need make a link.
-
In xev, they don't seem to map to any keycode or keysym.
Try it again without xbindkeys in the memory or remap the keys using xbindkeys-config.
-
Great. I will play with the keys on train on the way home this evening.
So it seems that the stuff after install tarball actually does not 100% work for the Angstrom kernel, am I right?
If that's true, then perhaps it is a good idea to indicate this explicitly.
Could you give me more details of the (in)compatibility between the after install tarball (which are targeted at the yonggun kernel and EABI rootfs) and the Angstrom kernels?
Then maybe in those cases the users need to use the Angstrom stuff (xfbdev, ts).
And the upcoming Poky kernels (by cortez) may add more variables to this debian game...
Up to now I feel most comfortable with the yonggun kernel. Thanks again!
-
Great. I will play with the keys on train on the way home this evening.
So it seems that the stuff after install tarball actually does not 100% work for the Angstrom kernel, am I right?
If that's true, then perhaps it is a good idea to indicate this explicitly.
Could you give me more details of the (in)compatibility between the after install tarball (which are targeted at the yonggun kernel and EABI rootfs) and the Angstrom kernels?
Then maybe in those cases the users need to use the Angstrom stuff (xfbdev, ts).
And the upcoming Poky kernels (by cortez) may add more variables to this debian game...
Up to now I feel most comfortable with the yonggun kernel. Thanks again!
i'm sayin' shit... i run *poky*'s 2.6.21 kernel ! (not angstrom's one)
can't get a right click, that's boring
-
i've sound working ! .... but only on headphones...... when i plug/unplug it seems something is happening but the zaurus speaker is dead quite ...... any idea.?
-
@jpmatrix: have you tried alsamixer? It is installed if you have run 2nd-cfg.sh. Use the [M] key to mute/unmute, and the arrow Up/Down key to turn values up and down.
I am curious to see how far the scripts can go since you are using the Angstrom kernel (2.6.23).
If they don't do much then I have to edit the instructions again and limit the after install tarball to yonggun's kernel only, leaving the Angstrom settings to jpmatrix's post and perhaps also the older zaurus-hardware-eabi tarball on page 3. I was so naive to assume that things just work in the same way for both the Angstrom and yonggun kernels...
-
@jpmatrix: have you tried alsamixer? It is installed if you have run 2nd-cfg.sh. Use the [M] key to mute/unmute, and the arrow Up/Down key to turn values up and down.
I am curious to see how far the scripts can go since you are using the Angstrom kernel (2.6.23).
If they don't do much then I have to edit the instructions again and limit the after install tarball to yonggun's kernel only, leaving the Angstrom settings to jpmatrix's post and perhaps also the older zaurus-hardware-eabi tarball on page 3. I was so naive to assume that things just work in the same way for both the Angstrom and yonggun kernels...
that's strange because i had to manually apt-get install alsa-utils in order to have alsamixer. but anyway that didn't help xmms to produce sound on the zaurus speaker...
another issue for the 2.6.23 (i think) : my belkin BT CF card no longer works lots of error messages as i hciattach it....
-
Thanks.
Alright, then I will take out the after installation notes from the Angstrom kernel + EABI system, because obviously it seems to bring more confusions than without it. And i will make it clear that the after installation tarball is for yonggun's kernel only.
-
Thanks.
Alright, then I will take out the after installation notes from the Angstrom kernel + EABI system, because obviously it seems to bring more confusions than without it. And i will make it clear that the after installation tarball is for yonggun's kernel only.
perhaps it depends on the 0827 rootfs i used too... by the way i noticed alsa-oss didn't get installed too...
you were right perhaps i should launch 2nd-cfg script again to see if more packages get installed.ok i try !
-
Not only this, I agree with 2or0 that some of the packages and the scripts in the after installation tarball (now 1.1 ) are not suitable for the Angstrom kernels. And his X server is no longer Angstrom's as well. So YMMV.
Sorry for the confusion caused so far, because my 3200 is running the yonggun kernel so there is no way for me to check how the same things may work for the Angstrom kernel. I just started out naively presuming that it's the same, but that seems not to be the case.
If it turns out that the script works somehow or need some modification, please do!
Posting to the OESF wiki now ...
-
Not only this, I agree with 2or0 that some of the packages and the scripts in the after installation tarball (now 1.1 ) are not suitable for the Angstrom kernels. And his X server is no longer Angstrom's as well. So YMMV.
Sorry for the confusion caused so far, because my 3200 is running the yonggun kernel so there is no way for me to check how the same things may work for the Angstrom kernel. I just started out naively presuming that it's the same, but that seems not to be the case.
If it turns out that the script works somehow or need some modification, please do!
Posting to the OESF wiki now ...
After BigZ's flirtation with cortez-debian, we got thrown out by the partitioner refusing to work, I'm back using Q17. I'm using the poky 2.6.21 kernel and modules. The only glitch is, seems to be true for angstrom kernels too, is that I couldn't use the poky updater.sh. It didn't recognise my model (3200). So I used the updater.sh from bigbridge.
I'm into the 2nd script. By the way, with this kernel+module set, the eth2 bit doesn't work. What happens is that wlan0 works in the interfaces file but eth0 gets a mention at boot up! I also had to blacklist hostap before I could get a wifi connection working. So there is a diversion from the normal run there.
When the 2nd script begins to run the applieddata repository comes up with error messages and 404s. I'll comment that line out of sources.list for now. The gnuab repository seems to be very alive!
I'm going to hold off on trying to run a gui until I'm sure that everything else is working as per the advertisements! In particular the touchscreen stuff.
Yesterday, after interfering with your scripts, I did get to a gui. But there was no response to the screen, even though the libs and apps you mention were present. I'm trying to be a very good boy and let your scripts run without my interference. I'll get a drink of tea and go for a walk after the 2nd script stops and I reboot. I'll post later on when I've tried a few experimental uses of the system.
-
Yesterday, after interfering with your scripts, I did get to a gui. But there was no response to the screen, even though the libs and apps you mention were present. I'm trying to be a very good boy and let your scripts run without my interference. I'll get a drink of tea and go for a walk after the 2nd script stops and I reboot. I'll post later on when I've tried a few experimental uses of the system.
i've the same problem
to suceed i have to:
1- edit /root/.profile
and change TSLIB_DEVICE with /dev/input/touchscreen0
(or try /dev/input/event1)
2- edit /etc/ts.conf
and comment the line module_raw corgi
3- if you use the 0827 rootfs :
update-rc.d -f xads.sh remove
this worked for me right now
-
Yesterday, after interfering with your scripts, I did get to a gui. But there was no response to the screen, even though the libs and apps you mention were present. I'm trying to be a very good boy and let your scripts run without my interference. I'll get a drink of tea and go for a walk after the 2nd script stops and I reboot. I'll post later on when I've tried a few experimental uses of the system.
i've the same problem
to suceed i have to:
1- edit /root/.profile
and change TSLIB_DEVICE with /dev/input/touchscreen0
(or try /dev/input/event1)
2- edit /etc/ts.conf
and comment the line module_raw corgi
3- if you use the 0827 rootfs :
update-rc.d -f xads.sh remove
this worked for me right now
Thanks for those tips jpmatrix. I'll probably need them tomorrow. For tonight, what do I do with my empty fstab? Yes, I will look at the fstab on the hitachi I swapped out. But does anyone have some good tweaks for that file? I just stopped myself from doing a dist-upgrade. Does it break things?
By the way apart from the empty fstab, I also get a message about a non-empty exim4 paniclog and I saw some messages about mplayer having problems with its install.
I'll try the fix flag...
-
For tonight, what do I do with my empty fstab? Yes, I will look at the fstab on the hitachi I swapped out. But does anyone have some good tweaks for that file?
here is one:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/mmcblk0p1 /media/card auto defaults,sync,noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
usbfs /proc/bus/usb usbfs defaults 0 0
I just stopped myself from doing a dist-upgrade. Does it break things?
it should not
just do another dist-upgrade next time
-
So my fstab now contains:
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda5 none swap sw 0 0
When I rebooted the swap was activated, the filesystem check jumped in and fsck was run manually. Booting is now completing and the hardware clock appears to be saving time between boots!
I must put the ssh server on before I start messing with the gui...
Why was the fstab empty? because the rootfs is generic?
-
Hi All,
I've tried to install Debian using this manual on my C1000:
Q20: I am using a C1x00, and I want to use kernel 2.6.22.9 yonggun with uboot. How can I install Debian EABI on SD?
and now I can't turn my Z on
First of all, as far as I understand, there are two mispints in the kernel version:
a. "use kernel 2.6.22.9 yonggun".
b. kernel.img.2.6.23.1.cpufreq-fastfpe.sd in the Kernel installation.
I didn't find any of the versions above and used the following one described in the Q7:
kernel.img-2.6.23.1-yonggun-eabi-cpufreq-hda1 (compatibility with C1000 is to be verified)
So, I performed all steps 1-7, when the kernel has been flashed, Z displayed some text indicating that it's going to reboot. I hold '1' button, Z has turned off...
Now I can't turn it on, I can't even get into DM menu (holding D+M when connecting AC). Moreover, the orange led is not highlighted when I attach AC power. Therefore I suspect that I've got hardware troubles
Is there any way to resuscitate my Z?
-
i've sound working ! .... but only on headphones...... when i plug/unplug it seems something is happening but the zaurus speaker is dead quite ...... any idea.?
Got everything working fine except the sound on the speaker.
-
i've sound working ! .... but only on headphones...... when i plug/unplug it seems something is happening but the zaurus speaker is dead quite ...... any idea.?
Got everything working fine except the sound on the speaker.
so i'm not the only one !
which zaurus model do you own ?
-
i've sound working ! .... but only on headphones...... when i plug/unplug it seems something is happening but the zaurus speaker is dead quite ...... any idea.?
Got everything working fine except the sound on the speaker.
so i'm not the only one !
which zaurus model do you own ?
I am using C3200. I follow yonggun instruction on his website. I dunno if he has the same problem with us?
-
By the way, have you guys tried installing altboot after u got your Debian EABI working with uboot? I dun quite like the fact that i always need to press the "2" key while doing a reboot? Or is there anyway that i can edit uboot configuration such that it can show a boot menu instead of booting directly from the Nand flash?
-
I want to ask where I can download the 2.6.21 Angstrom kernel for c760?
I want to give a shot to debian...
thx a lot!
-
Hi All,
I've tried to install Debian using this manual on my C1000:
Q20: I am using a C1x00, and I want to use kernel 2.6.22.9 yonggun with uboot. How can I install Debian EABI on SD?
and now I can't turn my Z on
First of all, as far as I understand, there are two mispints in the kernel version:
a. "use kernel 2.6.22.9 yonggun".
b. kernel.img.2.6.23.1.cpufreq-fastfpe.sd in the Kernel installation.
I didn't find any of the versions above and used the following one described in the Q7:
kernel.img-2.6.23.1-yonggun-eabi-cpufreq-hda1 (compatibility with C1000 is to be verified)
So, I performed all steps 1-7, when the kernel has been flashed, Z displayed some text indicating that it's going to reboot. I hold '1' button, Z has turned off...
Now I can't turn it on, I can't even get into DM menu (holding D+M when connecting AC). Moreover, the orange led is not highlighted when I attach AC power. Therefore I suspect that I've got hardware troubles
Is there any way to resuscitate my Z?
I am sorry that I hear you. For kernel 2.6.22.9, it is verified to work on C1000, but nobody has reported yet whether kernel 2.6.23.1 works or not on C1000.
Did you try to press Fn+D+M to get into Service mode? or OK+Power to uboot?
-
Did you try to press Fn+D+M to get into Service mode? or OK+Power to uboot?
Thanks for your reply. I've tried to hold D+M (but not Fn+D+M) while attaching AC (with the battery ejected) and OK+Power (with the battery inserted). I'll try Fn+D+M this evening.
-
Hi All,
I've tried to install Debian using this manual on my C1000:
Q20: I am using a C1x00, and I want to use kernel 2.6.22.9 yonggun with uboot. How can I install Debian EABI on SD?
and now I can't turn my Z on
First of all, as far as I understand, there are two mispints in the kernel version:
a. "use kernel 2.6.22.9 yonggun".
b. kernel.img.2.6.23.1.cpufreq-fastfpe.sd in the Kernel installation.
I didn't find any of the versions above and used the following one described in the Q7:
kernel.img-2.6.23.1-yonggun-eabi-cpufreq-hda1 (compatibility with C1000 is to be verified)
So, I performed all steps 1-7, when the kernel has been flashed, Z displayed some text indicating that it's going to reboot. I hold '1' button, Z has turned off...
Now I can't turn it on, I can't even get into DM menu (holding D+M when connecting AC). Moreover, the orange led is not highlighted when I attach AC power. Therefore I suspect that I've got hardware troubles
Is there any way to resuscitate my Z?
Very sorry for the confusion. I was concentrating on Q16-19 most of the time and left out Q20 and that's why I sticked "remains to be tested" there.
Can you try the 2.6.22.9 yonggun kernel instead? http://yonggun.tistory.com/53 (http://yonggun.tistory.com/53) (kernel.img.2.6.22.9.cpufreq-fastfpe.sd )
2or0 mentioned that it works on C1000.
-
In xev, they don't seem to map to any keycode or keysym.
Try it again without xbindkeys in the memory or remap the keys using xbindkeys-config.
I killed the running xbindkeys, and then installed x-yonggun and the two x-server packages, and now right click key binding works. Thanks!
-
i've sound working ! .... but only on headphones...... when i plug/unplug it seems something is happening but the zaurus speaker is dead quite ...... any idea.?
Got everything working fine except the sound on the speaker.
so i'm not the only one !
which zaurus model do you own ?
I am using C3200. I follow yonggun instruction on his website. I dunno if he has the same problem with us?
Sound plays very well in my setup (C3200, kernel 2.6.23.1 yonggun, Debian EABI).
Have you tried alsamixer (in the package alsa-utils) to set up the sound?
Run alsamixer, use [M] to mute/unmute, and the Up/Down arrow keys for turning things up and down.
-
Did you try to press Fn+D+M to get into Service mode? or OK+Power to uboot?
Thanks for your reply. I've tried to hold D+M (but not Fn+D+M) while attaching AC (with the battery ejected) and OK+Power (with the battery inserted). I'll try Fn+D+M this evening.
I got the message from Korean guy who had same problem. Fn+D+M works and he recoverd the system.
-
Did you try to press Fn+D+M to get into Service mode? or OK+Power to uboot?
Thanks for your reply. I've tried to hold D+M (but not Fn+D+M) while attaching AC (with the battery ejected) and OK+Power (with the battery inserted). I'll try Fn+D+M this evening.
I got the message from Korean guy who had same problem. Fn+D+M works and he recoverd the system.
Thank you guys, I've restored Z using Fn+D+M keys.
So, I've performed all steps form 1 to 11. Unfortunately, I have no proper Inet connection Will it be OK if I skip update and dist-upgrade and install all packages mentioned in the 2nd-cfg.sh manually? I'm going to use this feed:
http://kfreebsd-gnu.debian.net/debian/pool-armel/main/ (http://kfreebsd-gnu.debian.net/debian/pool-armel/main/)
-
@Vitel
For the inet error, try this:
nano /etc/modporbe.d/aliases
Add the following three lines and comment out the last one like this:
alias net-pf-10 ipv6 off
alias net-pf-10 off
alias ipv6 off
#alias net-pf-10 ipv6
Reboot. If your wifi card is supported and /etc/network/interfaces and /etc/resolv.conf are correct, then your Z should be able to connect to the internet.
-
@Vitel
For the inet error, try this:
...
Reboot. If your wifi card is supported and /etc/network/interfaces and /etc/resolv.conf are correct, then your Z should be able to connect to the internet.
I meant I can't connect Z to the internet due to hardware troubles: I have no WiFi AP. Therefore, It'd be better for me to download all necessary deb packets from my desktop and copy them to CF card. Is it way possible?
-
@Vitel
For the inet error, try this:
...
Reboot. If your wifi card is supported and /etc/network/interfaces and /etc/resolv.conf are correct, then your Z should be able to connect to the internet.
I meant I can't connect Z to the internet due to hardware troubles: I have no WiFi AP. Therefore, It'd be better for me to download all necessary deb packets from my desktop and copy them to CF card. Is it way possible?
Why don't you use USB networking? This is easy and convinient.
-
@Vitel
For the inet error, try this:
...
Reboot. If your wifi card is supported and /etc/network/interfaces and /etc/resolv.conf are correct, then your Z should be able to connect to the internet.
I meant I can't connect Z to the internet due to hardware troubles: I have no WiFi AP. Therefore, It'd be better for me to download all necessary deb packets from my desktop and copy them to CF card. Is it way possible?
Why don't you use USB networking? This is easy and convinient.
Thanks for advice, I'll try it.
-
Q16: I am using a Cxx0 or C1000. How can I install Debian EABI to my SD card?
A16: The installation comes in two parts. 1. Install the Angstrom kernel & Angstrom system; 2. Install the Debian EABI system
Note:
-- If your Zaurus is already running with uboot (such as the new pdaXrom versions), then you have to do a NAND Restore to revert to the factory stock rom in order to flash this kernel.
-- If you want to keep using uboot, go to Q20 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170059) now.
-- The 2.6.22 kernel (2.6.23 yet to be verified) has troubles with altboot, so don't use it for now unless you know how to solve the problems.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
Many thanks for the guide! But still lost ...
Ok, here I am. I want to have Debian EABI on my C860. Q16 is my starting point.
Yes, I am the problem child :-).
Where can I find an angstrom 2.6.21 system to download? Or can I use Poky instead? Or did anybody try the november edition of angstrom?
Thank you all
Detlef
-
Sorry, you are right. Angstrom 2.6.21 is no longer available in the Angstrom feeds.
I don't have the kernel at the moment. Chero once uploaded it in some post but his attachment has been lost like many other recent attachments. Perhaps you can ask him or someone for that.
-
Q16: I am using a Cxx0 or C1000. How can I install Debian EABI to my SD card?
A16: The installation comes in two parts. 1. Install the Angstrom kernel & Angstrom system; 2. Install the Debian EABI system
Note:
-- If your Zaurus is already running with uboot (such as the new pdaXrom versions), then you have to do a NAND Restore to revert to the factory stock rom in order to flash this kernel.
-- If you want to keep using uboot, go to Q20 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170059) now.
-- The 2.6.22 kernel (2.6.23 yet to be verified) has troubles with altboot, so don't use it for now unless you know how to solve the problems.
Go back to the main list. (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170039)
Many thanks for the guide! But still lost ...
Ok, here I am. I want to have Debian EABI on my C860. Q16 is my starting point.
Yes, I am the problem child :-).
Where can I find an angstrom 2.6.21 system to download? Or can I use Poky instead? Or did anybody try the november edition of angstrom?
Thank you all
Detlef
From what I read here the Angstrom kernel and Poky kernel are quite alike, so you should be fine using that one.
Before trying the november edition : check the angstrom bugs / mailing list to see whether the altboot problem has been solved.
As for the 2.6.21 kernel : ZDevil has it somewhere, I only have the one for C1000.
edit : oops, cross-posting-fun.
@ZDevil : I don't have the one for C860.
Chero.
-
BTW thanks to flux's testing, now we found some low-level bugs in the after installation scripts. I am revising the files now and am still thinking of the way to handle the hwclock.rules.
The scenario is this:
The 1st-cfg.sh from the afterinstall tarball instructs to copy a hwclock.rules to /etc/udev/rules.d and then executes "hwclock -w" right after that. But the second step fails due to some /dev/rtc error. After a reboot "hwclock -w" works as expected though. The ideal case is not to have the user reboot after running 1st-cfg.sh, but to ensure the hardware clock setting takes effect on the spot. The hwclock man page and google is of little help here.
Any hint?
-
From what I read here the Angstrom kernel and Poky kernel are quite alike, so you should be fine using that one.
Before trying the november edition : check the angstrom bugs / mailing list to see whether the altboot problem has been solved.
As for the 2.6.21 kernel : ZDevil has it somewhere, I only have the one for C1000.
Chero.
Oh, yes. I have the Cxx0 one. But the file is not around me in the workplace. Perhaps if you don't mind waiting till this evening I will upload it here, together with an updated after installation tarball.
-
BTW thanks to flux's testing, now we found some low-level bugs in the after installation scripts. I am revising the files now and am still thinking of the way to handle the hwclock.rules.
The scenario is this:
The 1st-cfg.sh from the afterinstall tarball instructs to copy a hwclock.rules to /etc/udev/rules.d and then executes "hwclock -w" right after that. But the second step fails due to some /dev/rtc error. After a reboot "hwclock -w" works as expected though. The ideal case is not to have the user reboot after running 1st-cfg.sh, but to ensure the hardware clock setting takes effect on the spot. The hwclock man page and google is of little help here.
Any hint?
I always found that hwclock looked for /dev/rtc, but I can only find rtc0 in my dev tree. After doing ln -s /dev/rtc0 /dev/rtc, hwclock works for me.
-
Thanks. I remember flux did the same trick too. Perhaps I should add the symlinking to the updated script.
-
@Vitel
For the inet error, try this:
...
Reboot. If your wifi card is supported and /etc/network/interfaces and /etc/resolv.conf are correct, then your Z should be able to connect to the internet.
I meant I can't connect Z to the internet due to hardware troubles: I have no WiFi AP. Therefore, It'd be better for me to download all necessary deb packets from my desktop and copy them to CF card. Is it way possible?
Why don't you use USB networking? This is easy and convinient.
Thanks for advice, I'll try it.
I've configured USB networking, it works well, but I'm still having troubles with installation.
Some errors occur during execution of the 2nd-cfg.sh in spite of the fact that script downloads and installs lots of packets (about 60Mb as far as I remember). Please see attached log of the 2nd-cfg execution in the second time (after all packets are already downloaded): [ You are not allowed to view attachments ]
BTW, I've tried to add one more server to the list of apt sources, but it didn't help:
#cat sources.list
deb http://ftp.gnuab.org/debian sid main
deb http://kfreebsd-gnu.debian.net/debian sid main
deb http://armel-debs.applieddata.net/debian sid main
-
From what I read here the Angstrom kernel and Poky kernel are quite alike, so you should be fine using that one.
Before trying the november edition : check the angstrom bugs / mailing list to see whether the altboot problem has been solved.
As for the 2.6.21 kernel : ZDevil has it somewhere, I only have the one for C1000.
Chero.
Oh, yes. I have the Cxx0 one. But the file is not around me in the workplace. Perhaps if you don't mind waiting till this evening I will upload it here, together with an updated after installation tarball.
@dsteuer,
Here it is.... you need to install the 1004 (2.6.22) then replace the kernel and modules attached.
-
citro, in the 2nd-cfg.sh try to remove all the "echo" lines, and keep only one "cd packages" in the beginning of the script. The original script has several "cd packages" and then "cd ..", but somehow that fails to work at some point.
Also, add libmad0 and libxosd2 along with other alsa stuff in that apt-get install line.
And don't use the kfreebsd repo. The packages there may cause some compatibility issues.
Make sure your network connection is working before running the 2nd script again.
If you run the script for more than one time, edit /etc/modules and remove the redundant snd-soc-spitz lines (though they don't do harm) and just keep one.
For the hwclock setting, either do a reboot, or try "ln -s /dev/rtc0 /dev/rtc && hwclock -w" to make the hardware clock setting function.
Let me know how things go.
-
Angstrom 2.6.21 kernel. C1000 Version
-
@dsteuer,
Here it is.... you need to install the 1004 (2.6.22) then replace the kernel and modules attached.
Thx, citro!
-
Ok, here are the two revised scripts in the after installation tarball. I would appreciate it very much if you folks could comment on it and help me spot any low-level mistakes. Will add them to the next version of the after installation tarball if things seem alright. Thanks in advance.
The revisions also allow the user to run the scripts repeatedly without manual fiddling with the system setting files
The file structure of the after installation tarball is this:
1st-cfg.sh
2nd-cfg.sh
settings/ ## Containing all the system setting files being used in the scripts
packages/ ## Containing all the 2or0's packages being installed in the second script.
[size=]1st-cfg.sh[/size]
#!/bin/sh
## This is PART I of the after installation configuration script
echo "Do you want to start debian after installation configuration now? [y/n]"
read ans
if [ "$ans" != "y" -a "$ans" != "Y" ]; then
exit 0
fi
# First set up some basic hardware functionalities on the Zaurus
echo "Now setting up some basic hardware functionalities ..." &&
# Set up console-tools and wireless-tools to get other things working
cd packages &&
echo "Now installing libconsole ..."
dpkg -i libconsole_0.2.3dbs-65_armel.deb &&
echo "Done."
echo "Now installing console-tools ..."
dpkg -i console-tools_0.2.3dbs-65_armel.deb &&
echo "Done."
echo "Now installing libiw28 ..."
dpkg -i libiw28_28-1_armel.deb &&
echo "Done."
echo "Now installing wireless-tools ..."
dpkg -i wireless-tools_28-1_armel.deb &&
cd .. &&
echo "Done."
echo ""
# keymap
echo "Now let's load the right keymap for your Zaurus..."
cp settings/keymap.map /etc/keymap.map &&
loadkeys /etc/keymap.map &&
if ! grep "loadkeys /etc/keymap.map" /etc/rc.local; then
sed -i '/exit 0/ i\loadkeys /etc/keymap.map' /etc/rc.local
fi
echo "Done."
echo ""
# start-stop daemon
echo "Now setting up start-stop-deamon ..."
if ! test -f /sbin/start-stop-daemon.REAL; then
cp settings/start-stop-daemon.REAL /sbin
fi
mv /sbin/start-stop-daemon /sbin/start-stop-daemon.FAKE &&
mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemon &&
echo "Done."
echo ""
# hostname & localhost
echo "Now adding a hostname for your Zaurus ..."
if ! grep "Zaurus" /etc/hostname; then
echo "Zaurus" >> /etc/hostname
fi
echo -ne "127.0.0.1\tlocalhost.localdomain localhost Zaurus\n" >> /etc/hosts &&
echo "Done."
echo ""
# package feed locations
echo "Now setting up a working package feed list for your Zaurus ..."
mv /etc/apt/sources.list /etc/apt/sources.list.bak &&
cp settings/sources.list /etc/apt/ &&
echo "Done."
echo ""
# Write the current time to the hardware clock
echo "Now setting up the hardware clock ..."
cp settings/hwclock.rules /etc/udev/rules.d &&
if ! test -f /dev/rtc; then
ln -s /dev/rtc0 /dev/rtc
fi
hwclock -w &&
echo "Done."
echo ""
# Print this message to remind users to set up network before proceeding to the second part.
echo "This is the end of the first part of the after installation
configurations. Please reboot now to make the hwclock setting to
take effect. Make sure that you have a proper network connection
before proceeding to the second part. See you around!"
echo ""
[size=]2nd-cfg.sh[/size]
#!/bin/sh
## This is PART II of the after installation script
echo ""
echo "Welcome to the second part of the Debian EABI after installation.
This script will help you set up a working environment including:
1) Updating the package lists and the (pre)installed packages;
2) Installing and setting up an X server;
3) Installing and configuring touchscreen pointer utilities;
4) Installing IceWM as the default window manager;
5) Intalling and configurating sound support;
6) Installing mplayer for playing video;
7) Adding a few useful utilities for auto suspend & screen blanking,
speaker/headphone sound output switching, usb support, and
over/under-clocking control;
Please make sure that your Zaurus has a proper network connection.
Do you want to proceed with the process now? [y/n]"
read ans
if [ "$ans" != "y" -a "$ans" != "Y" ]; then
exit 0
fi
# Update the package lists
echo "Now updating the package lists ..."
apt-get update &&
echo "Done."
echo ""
# Upgrade the installed packages
echo "Now upgrading the installed packages ..."
apt-get dist-upgrade &&
echo "Done."
echo ""
# X server
echo "Now setting up X server ..."
apt-get install xfonts-base rxvt xbase-clients libxft2 libfontconfig1 icewm icewm-experimental menu icewm-gnome-support grun apmd sudo &&
cd packages &&
dpkg -i xserver-kdrive_1.3.0.0-r19_armel.deb xserver-kdrive-fbdev_1.3.0.0-r19_armel.deb x-yonggun_0.0_armel.deb &&
cd ../ &&
mkdir ~/.icewm &&
cp settings/icewm_preferences ~/.icewm/preferences &&
echo "Done."
echo ""
# touchscreen
echo "Now setting up touchscreen ..."
cd packages &&
dpkg -i libts-1.0-0_1.0-r17_armel.deb tslib-calibrate_1.0-r17_armel.deb tslib-conf_1.0-r17_armel.deb &&
ldconfig &&
echo "Done."
echo ""
# sound
echo "Now setting up sound and installing some essential packages ..."
modprobe snd-soc-spitz &&
if ! grep "snd-soc-spitz" /etc/modules; then
echo snd-soc-spitz >> /etc/modules
fi
apt-get install alsa-base alsa-utils alsa-oss libsdl1.2debian-alsa libmad0 libxosd2 xmms xmms-mad &&
echo "Done."
echo ""
# video
echo "Now installing mplayer for the Zaurus to play videos ..."
dpkg -i libmp3lame0_3.96.1-r4_armel.deb mplayer-common_0.0.1-r0_armel.deb mplayer_0.0+1.0rc1+svnr24587-r3_armel.deb &&
echo "Done."
echo ""
# More utilities
echo "Now installing a few more nice utilties ..."
dpkg -i ipaq-sleep_0.9-r1_armel.deb usb-gadget-mode_0.0.2-r0_armel.deb zaurusd_0.0+svn20060628-r10_armel.deb cpuoverclock_0.0.3-1_armel.deb &&
update-rc.d -f zaurusd remove &&
modprobe ohci-hcd &&
if ! grep "ohci-hcd" /etc/modules; then
echo "ohci-hcd" >> /etc/modules
fi
cd $HOME &&
echo "Done."
echo ""
# Add a greeting here
echo "Congratulations! Debian EABI is set up on your Zaurus.
Have fun! :-) "
echo ""
echo ""
-
i've just had a strange problem after a reboot : stylus was not working anymore......
i find that although the TSLIB_DEVICE was set in /etc/profile and ~/.profile it seems it was never executed....
i had to put the EXPORT TSLIB line in /etc/X11/xdm/Xsession and now it works again!
perhaps my problem come from flux's tip to enable login with $USER but i'm not sure......
-
Perhaps chmod 755 ~/.profile may do?
-
Well, I'm coming closer to a working EABI on my 860.
I installed Angstrom as of Nov. 4th, replaced the kernel with a 2.6.21 version that can cooperate with altboot.
(first I found out that this version of Angstrom refuses to altboot; added info to the wiki)
Installed altboot after some fiddling with Angstrom's Wifi.
Installed armel-rootfs on sd card. (on a loop device, but shoudn't matter)
reboot.
Everything fine!
Because I had forgotten to cp my modules over, I rebooted into Angstrom once more.
Worked like a charm.
Copied modules over.
reboot
altboot doesn't work anymore :-(
Solved: I did not unmount the loop device before rebooting. If doing so I get to debian 4.0!. Now wading through afterinstallation ...
It hangs forever showing [4] CF Card and doesn't react for pressing the "any key".
No [5] advanced does not show up.
Looks like "go back to start" :-(
Anybody with similar experiences?
I only mounted the loop-device on /mnt and cp -a /lib/modules /mnt/lib/moudules, did not play with anything altboot related.
Detlef
-
perhaps we should modify the wiki for those who (had to) use uboot/altboot and those who can install eabi without that : for example on my c3000 these are not needed and it works perfectly...
-
icewm-gnome-support grun
these two packages in the script are broken when using the source.list from the wiki (https://www.oesf.org/index.php?title=1-For_Debian_EABI)
figured I would try a clean install
-
Ok, here are the two revised scripts in the after installation tarball. I would appreciate it very much if you folks could comment on it and help me spot any low-level mistakes. Will add them to the next version of the after installation tarball if things seem alright. Thanks in advance.
Reporting success installing Angstrom Kernel 2.6.21 + EABI File system on a C700. I did the afterinstall steps manually following the directions on Zdevil scripts. Some of the steps were not needed as follows:
1sf-cfg.sh
- I didn't need to install console-tools or libconsole. The system boot without complain about the console
- I didn't have to do the keymap section as keyboard was working perfectly.
2nd-cfg.sh
- on X server section, 2 of the files were not installed: grun and ice-gnome-support due to dependency issues.
- Touchscreen needed some changes as per afterinstall comments on the wiki (comment lines on /etc/ts.conf and replace usr/bin/X with those 2 lines described on the wiki). Without those changes the touchscreen was not working.
- audio section didn't need modprobe snd-soc-spitz as the module was already loaded (by the way the module loaded on C700 is snd-soc-corgi and it works great !!!!)
Now the bad news .... When trying to apt-get most of the programs (xcfe4, gimp, gnumeric, ice-weasel, nautilus, evolution, etc) i get errors because of the known broken package libgtk2.0 being discussed [a href=\'index.php?showtopic=25015\']here[/a]. Hopefully the repository version mismatch will get fixed soon.
One other thing I noticed is that pccardctl is not found so if I want to swap the wireless card for the microdrive I have to shutdown, turn off and reboot. I tried apt-get install pccardctl but it didn't find any packages with that name. Any idea?
So far has tried dillo, sylpheed-claws and xmms and performance is great. I'm really surprised as barely none of the other distributions works good on the C700 with its limited RAM and FLASH memory. However this debian combination is amazingly fast.
-
I've managed to get kernel 2.6.23 and Debian on SD card to work on my C860. See https://www.oesf.org/forum/index.php?showtopic=25399 (https://www.oesf.org/forum/index.php?showtopic=25399) for details.
Cheers,
Dan