OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Debian => Topic started by: cortez on October 31, 2007, 06:24:17 pm
-
Hi,
I tried to setup the Debian Installer in a way we can do a fully customized install of Debian without the use of the prefab root file system. See attached all files needed. The kernel used is a brand new 2.6.23 Poky kernel. The zaurus-specific package is just a beginning. I'm sure there's stuff missing here and there. The zaurus-specific package includes the corresponding kernel modules and firmware drivers with which you should be able to perform the (wireless) network installation (DHCP is included). The ramdisk.gz file contains the actual Debian Installer. More info on that can be found here (http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2442).
This version does not require the use of uboot. As said before, although the idea of uboot is great, it can be a real pain to install. More important, if not installed succesfully, it's an even greater pain to get your (seemingly bricked) device back to a working state. It took me quite a while to restore my 3100 after trying the yonggum kernel with uboot.
You can put any additional Debian package files on the SD if you want to use them. After flashing the kernel the updater script will extract any .deb file from the SD to the root of the microdrive. This makes it possible for instance to use a different kernel. Just add the corresponding kernel modules (in a deb package format!) to the SD and it should work.
This version currently only works with the C3x00 models. If this works out to be succesfull and if time permits, I will build a C1000 kernel+package and maybe (depending on the help I get from ZDevil ) even a Cxx0 version to test this procedure.
==========
1. Preparation
==========
a. Extract all files from the attached AllInOne.tar archive and put them on SD. Flashing from CF is currently not supported.
b. You can put any optional debian packages (.deb) on the SD. After flashing the kernel all available .deb files on SD will be extracted to the root of the microdrive.
==========
2. Flashing
==========
a. Remove battery, wait 5 secs, place battery and attach AC power.
b. Press "OK" key and keep it pressed, then press "On/Off" button.
c. In the maintenance menu, choose "4" (Update) in the first screen, "2" (SD) in the second and "Y" in the third
d. The kernel will be flashed, the microdrive formatted and the Installer will be setup.
Your Zaurus will reboot and the Installer is started.
==========
3. The installer
==========
a. Choose your language and location
b. Network configuration. Choose the driver of your network card (yes, you need one). DHCP is included in the installer, so hopefully your network settings are automatically configured.
c. Choose the hostname and domain name. It's fine to accept the defaults, since you can always change them later.
d. Partitioning the disk. This is the most tricky bit, since the installer is currently unable to mount the swap partition. Choose for manual partitioning, and create two partitions, the first a big one and the second a smaller one. Make the smaller one about 200/250Mb and assign the rest of the diskspace to the first partition. Make the first partition primary, bootable, set the mount point to / (root) and choose the ext3 filesystem. I choose the option to not format the partition this partition and leave the current filesystem alone. Make the second partition a swap partition, primary, not bootable and don't give it a mount point. Choose the option to not use it (we deal with that later on). The Installer will complain about not having a swap partition, but you can ignore that and continue the installation.
e. The downloading and installation of the base Debian system begins. Be patient, and keep your finger crossed!
f. Ignore the message about not being able to find the right kernel. Just continue
g. At the "software installation" screen choose only to install the base system.
==========
4. Post-Installation
==========
This is work in progress, we need to setup a few extra's. At the time of writing, this still has to be done. Here's were I need your help, since I don't have the time to do this all on my own.
Good luck!
cortez
-
Nice. I would really love to try this if you can make a kernel for C860 (or Cxx0).
I wonder if: 1) stylus pointer works without jumping; 2) sound works; 3) it is possible to dualboot with this setup?
-
I couldn't see right off the bat, so thought I'd ask. I gather this kernel installs by flashing; without the need to go to uboot. So, what modules are available with this, and how does one go about the rest of the install. In particular, I am interested in the libertas module, which rumor has will support my new Sparklan wifi card with the marvell chip.
-
I keep answering my own questions. No, the libertas module is not there, so I guess I will try with yonggum's kernel.
-
I tried this on my 3100 - and I get the following error;
/tmp/update/updater.sh: 1: Syntax error: ")" expected
error (1)
Rebooting
My Z is currently running Debian OABI - as per ZDevil's guide Q15, and I have updated the kernel to the Pokylinux 2.6.21 kernel. My microdrive (6 gig) is partitioned with ~ 5.5 gig root, 512 swap. Used a 1 gig SD to flash - have used it many times for PDAXii13 flashing with no problems.
-
I tried this on my 3100 - and I get the following error;
/tmp/update/updater.sh: 1: Syntax error: ")" expected
error (1)
Rebooting
My Z is currently running Debian OABI - as per ZDevil's guide Q15, and I have updated the kernel to the Pokylinux 2.6.21 kernel. My microdrive (6 gig) is partitioned with ~ 5.5 gig root, 512 swap. Used a 1 gig SD to flash - have used it many times for PDAXii13 flashing with no problems.
Syntax error?!? That's really strange. I suppose you just renamed the updater.sh.gz file to updater.sh?
I just checked on my 3100, and it works as expected. Anyone having the same problems?
-
Nice. I would really love to try this if you can make a kernel for C860 (or Cxx0).
I wonder if: 1) stylus pointer works without jumping; 2) sound works; 3) it is possible to dualboot with this setup?
I'll update the info in the first post. When time permits I will build a C1000 kernel. This version works without uboot. Although the idea of uboot is great, it can be a real pain to install it. More important, if not installed succesfully, it's an even greater pain to get your (seemingly bricked) device back to a working state. It took my quite a while to restore my 3100 after trying the yonggum kernel with uboot.
Regarding the jumping stylus, sound etc I really don't know. I've not been able to find the time to finish the installation process.
cortez
-
That's cool. Keep up the good work!
And ...... I want a kernel for Cxx0 , not C1000 ...
-
That's cool. Keep up the good work!
And ...... I want a kernel for Cxx0 , not C1000 ...
If you help me test this one first and if it works I promise I'll try to make you a Cxx0 version. Do we have a deal?
-
Zeker!
-
And if you don't mind, once yours is working, I want to add it to the mega guide for easy reference, instead of having the (new) users digging into the many posts and got confused.
And it would be super nice if you can provide the instructions as well.
-
First post updated with some additional info:
You can put any additional Debian package files on the SD if you want to use them. After flashing the kernel the updater script will extract any .deb file from the SD to the root of the microdrive. This makes it possible for instance to use a different kernel. Just add the corresponding kernel modules (in a deb package format!) to the SD and it should work.
-
First post updated with some additional info:
You can put any additional Debian package files on the SD if you want to use them. After flashing the kernel the updater script will extract any .deb file from the SD to the root of the microdrive. This makes it possible for instance to use a different kernel. Just add the corresponding kernel modules (in a deb package format!) to the SD and it should work.
I haven't tried yet, but I wonder if adding extra packages on top of the rootfs would cause dependency issue (such as libc6, etc).
-
First post updated with some additional info:
You can put any additional Debian package files on the SD if you want to use them. After flashing the kernel the updater script will extract any .deb file from the SD to the root of the microdrive. This makes it possible for instance to use a different kernel. Just add the corresponding kernel modules (in a deb package format!) to the SD and it should work.
Hi cortez,
I'm giving it a try now!
-
First post updated with some additional info:
You can put any additional Debian package files on the SD if you want to use them. After flashing the kernel the updater script will extract any .deb file from the SD to the root of the microdrive. This makes it possible for instance to use a different kernel. Just add the corresponding kernel modules (in a deb package format!) to the SD and it should work.
I haven't tried yet, but I wonder if adding extra packages on top of the rootfs would cause dependency issue (such as libc6, etc).
Providing additional packages is meant to be a way of influencing the installer, for instance by adding the libertas driver
-
I tried this on my 3100 - and I get the following error;
/tmp/update/updater.sh: 1: Syntax error: ")" expected
error (1)
Rebooting
My Z is currently running Debian OABI - as per ZDevil's guide Q15, and I have updated the kernel to the Pokylinux 2.6.21 kernel. My microdrive (6 gig) is partitioned with ~ 5.5 gig root, 512 swap. Used a 1 gig SD to flash - have used it many times for PDAXii13 flashing with no problems.
Syntax error?!? That's really strange. I suppose you just renamed the updater.sh.gz file to updater.sh?
I just checked on my 3100, and it works as expected. Anyone having the same problems?
Ummm - your instructions say to rename the files - but I hat to extract the updater.sh.qz - not just simply rename it, that allowed the updater to work, but still errors. So I extracted both the zaurus_specific.deb.gz and zImage.bin.gz - and got further - but still get an error mounting some tmp dir near the end of the flashing, and after reboot I get a kernel panic.
did I miss something in the instructions? what files need to be extracted, and which ones renamed?
-
Hi cortez,
everything appeared to be going very smoothly: exactly as per your instructions. I'm impressed that you got dhcp put in, love the choose the network card bit.
I've got stuck. When the partitioner tries to format it bottles out with the swap partition. I'm not sure whether it is the format stage or the 'mount' the swap stage. I've used B+D and fdisk to clear the old partitions from my other installs. It still stuck at that point.
I'm trying again with a clean SD card and your files again. I'll get back to you. It may well be something about my previous set up. If it fails again at this stage I'll use Meanie's pdxaIII utilities and clean everything up, might even use the diagnostic utilities..
This is looking so smooth I'd hate not to be able to use it! Oh and it seems to be happy on a 1GB SD.
The error message is attempt to mount ... at none ... failed. I have double checked and this is definitely the case here on my system.
But I bet that clearing out my system and returning to a naked state for BigZ will cure this! Coupled with new downloads of your file.
-
I tried this on my 3100 - and I get the following error;
/tmp/update/updater.sh: 1: Syntax error: ")" expected
error (1)
Rebooting
My Z is currently running Debian OABI - as per ZDevil's guide Q15, and I have updated the kernel to the Pokylinux 2.6.21 kernel. My microdrive (6 gig) is partitioned with ~ 5.5 gig root, 512 swap. Used a 1 gig SD to flash - have used it many times for PDAXii13 flashing with no problems.
Syntax error?!? That's really strange. I suppose you just renamed the updater.sh.gz file to updater.sh?
I just checked on my 3100, and it works as expected. Anyone having the same problems?
Ummm - your instructions say to rename the files - but I hat to extract the updater.sh.qz - not just simply rename it, that allowed the updater to work, but still errors. So I extracted both the zaurus_specific.deb.gz and zImage.bin.gz - and got further - but still get an error mounting some tmp dir near the end of the flashing, and after reboot I get a kernel panic.
did I miss something in the instructions? what files need to be extracted, and which ones renamed?
Extraction of individual files should really not be needed!! I don't know why, but maybe your browser is doing something stupid with the files. I've attached an all-in-one archive for you to try. This time only extract the .tar file, after that transfer the files to SD and try again. Please let me know if this works.
-
That might be an explanation for my problem: corrupted download? So I'm downloading the tar now and will report back on what happens. Of course it might also be a glitch with BigZ. I have shoved a lot of installs through the system in the last week or so!
This looks such a good job cortez!
-
Hi cortez,
everything appeared to be going very smoothly: exactly as per your instructions. I'm impressed that you got dhcp put in, love the choose the network card bit.
I've got stuck. When the partitioner tries to format it bottles out with the swap partition. I'm not sure whether it is th format stage or the 'mount' the swap stage. I've used B+D and fdisk to clear the old partitions from my other installs. It still stuck at that point.
I'm trying again with a clean SD card and your files again. I'll get back to you. It may well be something about my previous set uop. If it fails again at this stage I'll use the pdxa utilities and clean everything up, moght evewn use the diagnostic utilities..
This is looking so smooth I'd hate not to be able to use it! Oh and it seems to be happy on a 1GB SD.
Thanks for your feedback. I'm glad the updater script seems to works for you. Too bad you're running into problems, although I'm glad you made it this far. When I stopped late last night I had trouble setting up my network. I will try again later tonight. What Debian archive mirror did you choose, the default ftp.gnuab.org?
If this works and a few of us have a working installation I will try to setup the Installer using preseeding (for info look here (http://d-i.alioth.debian.org/manual/en.i386/apbs02.html)). This way we could automate or finetune the installation process. It also makes it possible to run after-installation scripts or do additional package installations. It would make the installation of Debian a lot more user friendly than it is now. But... first we have to get it to work
I hope you have more success later. Keep trying, I won't be able to do this on my own!
cortez
-
I tried this on my 3100 - and I get the following error;
/tmp/update/updater.sh: 1: Syntax error: ")" expected
error (1)
Rebooting
My Z is currently running Debian OABI - as per ZDevil's guide Q15, and I have updated the kernel to the Pokylinux 2.6.21 kernel. My microdrive (6 gig) is partitioned with ~ 5.5 gig root, 512 swap. Used a 1 gig SD to flash - have used it many times for PDAXii13 flashing with no problems.
Syntax error?!? That's really strange. I suppose you just renamed the updater.sh.gz file to updater.sh?
I just checked on my 3100, and it works as expected. Anyone having the same problems?
Ummm - your instructions say to rename the files - but I hat to extract the updater.sh.qz - not just simply rename it, that allowed the updater to work, but still errors. So I extracted both the zaurus_specific.deb.gz and zImage.bin.gz - and got further - but still get an error mounting some tmp dir near the end of the flashing, and after reboot I get a kernel panic.
did I miss something in the instructions? what files need to be extracted, and which ones renamed?
Extraction of individual files should really not be needed!! I don't know why, but maybe your browser is doing something stupid with the files. I've attached an all-in-one archive for you to try. This time only extract the .tar file, after that transfer the files to SD and try again. Please let me know if this works.
It works now! Thanks - must have been a corrupted file. I am going through the installer now - will report back later.
-
It works now! Thanks - must have been a corrupted file. I am going through the installer now - will report back later.
I'm glad the flashing works! I'll change the instructions in the first post for all to use the AllInOne.tar archive instead of doing the renaming trick on the individual files.
-
First post updated with some additional info:
You can put any additional Debian package files on the SD if you want to use them. After flashing the kernel the updater script will extract any .deb file from the SD to the root of the microdrive. This makes it possible for instance to use a different kernel. Just add the corresponding kernel modules (in a deb package format!) to the SD and it should work.
I haven't tried yet, but I wonder if adding extra packages on top of the rootfs would cause dependency issue (such as libc6, etc).
Providing additional packages is meant to be a way of influencing the installer, for instance by adding the libertas driver
That's tempting. So, have you tried to insmod the libertas module from yonggum's version, and if so, did it load?
-
That's tempting. So, have you tried to insmod the libertas module from yonggum's version, and if so, did it load?
The good news is that I'm building a new kernel right now. Apart from the libertas module I'll include the fast FPE floating point emulation and the CPU frequency scaling.
-
The good news is that I'm building a new kernel right now. Apart from the libertas module I'll include the fast FPE floating point emulation and the CPU frequency scaling.
I've just tried again with the files from your big tar. I'd used meanie's pdaxIII utilities to put a blank label/dos thingy on it. I get stuck in a loop with the partitioner. It keps saying that it can't mount the swap partition at none.
The annoying thing, I mean the most annoying thing , is that the partitions appear to be set up! Is there any significnce in the fact that the partitioner progress bar sits at 33% for ages? Is there any hope of going out to a shell and mounting the partitions by hand? Then go back into the installer and carry on?
Is there any way you could make partitioning an optional step in the install process? I could then partition manually and get this system up.
I'll have one last go at a shell fdisk. If I can't get any further I'll leave this until some good news comes in.
-
That's tempting. So, have you tried to insmod the libertas module from yonggum's version, and if so, did it load?
The good news is that I'm building a new kernel right now. Apart from the libertas module I'll include the fast FPE floating point emulation and the CPU frequency scaling.
Argh, unfortunately the build aborts with "FATAL: This kernel is too big for your PXA Zaurus and will destroy data if you flash it. Please reduce the size of the kernel by making more of it modular.". Sorry dlj0, the rebuild will be without the libertas
-
That's tempting. So, have you tried to insmod the libertas module from yonggum's version, and if so, did it load?
The good news is that I'm building a new kernel right now. Apart from the libertas module I'll include the fast FPE floating point emulation and the CPU frequency scaling.
Argh, unfortunately the build aborts with "FATAL: This kernel is too big for your PXA Zaurus and will destroy data if you flash it. Please reduce the size of the kernel by making more of it modular.". Sorry dlj0, the rebuild will be without the libertas
Huh? But if the libertas stuff is a module, how can it make the kernel too big? And is should be a module, of course. Heck, I should be able to use 2or0's libertas module -- that was my plan before your announcement of a new build.
I do want to second the idea of cutting partitioning out of the script, so that we can roll our own in advance -- just set it up to install on /dev/hda1 or whatever you might prefer.
-
That's tempting. So, have you tried to insmod the libertas module from yonggum's version, and if so, did it load?
The good news is that I'm building a new kernel right now. Apart from the libertas module I'll include the fast FPE floating point emulation and the CPU frequency scaling.
Argh, unfortunately the build aborts with "FATAL: This kernel is too big for your PXA Zaurus and will destroy data if you flash it. Please reduce the size of the kernel by making more of it modular.". Sorry dlj0, the rebuild will be without the libertas
Huh? But if the libertas stuff is a module, how can it make the kernel too big? And is should be a module, of course. Heck, I should be able to use 2or0's libertas module -- that was my plan before your announcement of a new build.
I do want to second the idea of cutting partitioning out of the script, so that we can roll our own in advance -- just set it up to install on /dev/hda1 or whatever you might prefer.
Yeah, I know it sounds strange, but leaving the module out builds the kernel successfully. I will try to continue without it first. I would have to look into it later.
-
Oh my, the instructions are so positively simple !
I'm willing to try that on my C760, if you need me.
In what country do you live ? If you want to conduct some IRC/real time debuging, I think I can find some time.
-
I am also getting an error trying to mount the swap partition, but there is another error earlier that may be the cause - on first boot after flashing I get the following;
Setting up filesystem, please wait ...
modprobe: FATAL: Could not load /lib/modules/2.6.23/modules.dep: No such file or directory
Mount: Mounting none on /dev failed: No such device
modprobe: FATAL: Could not load /lib/modules/2.6.23/modules.dep: No such file or directory
Mount: Mounting devfs on /dev failed: No such device
modprobe: FATAL: Could not load /lib/modules/2.6.23/modules.dep: No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.23/modules.dep: No such file or directory
I don't know – maybe this is normal on first boot? I only have the 4 files on my SD
Also – during the 'Choose mirror of the Debian archive' part it asks to enter info manually – if I change the location it gives me an error, if I go with the defaults of ftp.gnuab.org and /debian I get an error during the 'Download Installer Components' part – “No kernel modules were found.”? If I choose to ignore that and continue without installing the kernel modules I get to the partitioning and get stuck in the loop!
Otherwise – this installer really looks great! Can't wait for an update – keep up the great work cortez!
-
I am also getting an error trying to mount the swap partition, but there is another error earlier that may be the cause - on first boot after flashing I get the following;
Setting up filesystem, please wait ...
modprobe: FATAL: Could not load /lib/modules/2.6.23/modules.dep: No such file or directory
Mount: Mounting none on /dev failed: No such device
modprobe: FATAL: Could not load /lib/modules/2.6.23/modules.dep: No such file or directory
Mount: Mounting devfs on /dev failed: No such device
modprobe: FATAL: Could not load /lib/modules/2.6.23/modules.dep: No such file or directory
modprobe: FATAL: Could not load /lib/modules/2.6.23/modules.dep: No such file or directory
I don't know – maybe this is normal on first boot? I only have the 4 files on my SD
Also – during the 'Choose mirror of the Debian archive' part it asks to enter info manually – if I change the location it gives me an error, if I go with the defaults of ftp.gnuab.org and /debian I get an error during the 'Download Installer Components' part – “No kernel modules were found.”? If I choose to ignore that and continue without installing the kernel modules I get to the partitioning and get stuck in the loop!
Otherwise – this installer really looks great! Can't wait for an update – keep up the great work cortez!
Cortez, I think I know what's going on. bdbell has jogged my memory. I was using 2.6.23 also. What modules does the installer expect? Is it 2.6.20 like on the Titchy one? If so, I think we need to use a 2.6.20 kernel to install. What do you think?
If true, the newer kernels and modules would have to be installed at a later stage, by copying the modules in and then flashing to the matching kernel. Am I right or suffering hallucinations from another late night? There is also your comment about the files being copied to the microdrive, surely not if partitioning is to take place?
Another possibility is, what if the install fstab doesn't have the correct entries for the partitions? Cheers
-
I don't know about the missing modules.dep on first boot. It's strange since the file exists if I look after booting.
I just got past the partitioning screen by selecting a manual partition scheme and setting the mount point to / (root).
-
I don't know about the missing modules.dep on first boot. It's strange since the file exists if I look after booting.
I just got past the partitioning screen by selecting a manual partition scheme and setting the mount point to / (root).
I'm trying again with the manual partitioning. Wish me luck!
I tried a / and a swap partition. The partition progress bar stayed at 33% and the led kept flashing for some time. Then it came back and said the swap failed to mount at none. I noticed at boot time that the same message about swap and none came up.
I'll repeat the manual partitioning with just / for the entire disk.
I seem to have got through to installing the base system! I used all the disk for /. Would it have been wiser to just use 16 GB and leave the rest for putting up a swap partition later on? If I get a working system I should be able to resize the root partition and set up a swap anyway - I hope!
It does seem to be working now. Am I the only one who has had trouble with the partitioning? I did download your big tar again before trying this evening. I sometimes wonder about firefox and downloading attachments from OESF.
I really hope this method works cortez. The big advantage of Titchy was the fairly straightforward install, even for Debian virgins! This version of yours, once any glitches in the install are sorted out looks like a more convenient install method than that, but for EABI. I have to admit EABI is the way we should expect to go!
Cups of tea and a large rum and ginger while I wait for this to proceed. The progress bar was sticking at 6% but various file names are popping up as I type and it now says 32%.
Terminator!
-
I don't know about the missing modules.dep on first boot. It's strange since the file exists if I look after booting.
I just got past the partitioning screen by selecting a manual partition scheme and setting the mount point to / (root).
I'm trying again with the manual partitioning. Wish me luck!
I tried a / and a swap partition. The partition progress bar stayed at 33% and the led kept flashing for some time. Then it came back and said the swap failed to mount at none. i noticed at boot time that the same message came up.
I'll repeat the manual partitioning with just / for the entire disk.
I manually partitioned the disk and split it up in two partitions one sized 3.9Gb and the other about 280Mb. Mark the big partition as root and bootable. Mark the smaller partition (for the time being) as unused. That should get you through the partitioner.
-
I don't know about the missing modules.dep on first boot. It's strange since the file exists if I look after booting.
I just got past the partitioning screen by selecting a manual partition scheme and setting the mount point to / (root).
I'm trying again with the manual partitioning. Wish me luck!
I tried a / and a swap partition. The partition progress bar stayed at 33% and the led kept flashing for some time. Then it came back and said the swap failed to mount at none. i noticed at boot time that the same message came up.
I'll repeat the manual partitioning with just / for the entire disk.
I manually partitioned the disk and split it up in two partitions one sized 3.9Gb and the other about 280Mb. Mark the big partition as root and bootable. Mark the smaller partition (for the time being) as unused. That should get you through the partitioner.
RATS! I didn't specify bootable! Oh well at least this method is mostly automatic and I don't need to keep tarring and untarring and fiddling with command line extras. I may be able to go back and redo the partitioning without going through the whole process again!
-
I don't know about the missing modules.dep on first boot. It's strange since the file exists if I look after booting.
I just got past the partitioning screen by selecting a manual partition scheme and setting the mount point to / (root).
I'm trying again with the manual partitioning. Wish me luck!
I tried a / and a swap partition. The partition progress bar stayed at 33% and the led kept flashing for some time. Then it came back and said the swap failed to mount at none. i noticed at boot time that the same message came up.
I'll repeat the manual partitioning with just / for the entire disk.
I manually partitioned the disk and split it up in two partitions one sized 3.9Gb and the other about 280Mb. Mark the big partition as root and bootable. Mark the smaller partition (for the time being) as unused. That should get you through the partitioner.
RATS! I didn't specify bootable! Oh well at least this method is mostly automatic and I don't need to keep tarring and untarring and fiddling with command line extras. I may be able to go back and redo the partitioning without going through the whole process again!
One last thing I forgot to mention. I choose the option NOT to format the main (root) partition and to leave the current files alone. I have to see how that works out. Installation is almost finished here. Maybe this is finally going to work...
-
Installation succesfully completed
Now selecting the packages to install
-
Installation succesfully completed
Now selecting the packages to install
Setting up users. Should I go back to the partitioner and try to set the boot flag? Yes I think so, if it can't be done easily I can always carry on and see if I get a bootable system. If not I can use meanies pdaxIII utilities and make the partition bootable and do a reboot!
Good luck with your install... looks like another late night!!!!
-
I don't know about the missing modules.dep on first boot. It's strange since the file exists if I look after booting.
I just got past the partitioning screen by selecting a manual partition scheme and setting the mount point to / (root).
I'm trying again with the manual partitioning. Wish me luck!
I tried a / and a swap partition. The partition progress bar stayed at 33% and the led kept flashing for some time. Then it came back and said the swap failed to mount at none. i noticed at boot time that the same message came up.
I'll repeat the manual partitioning with just / for the entire disk.
I manually partitioned the disk and split it up in two partitions one sized 3.9Gb and the other about 280Mb. Mark the big partition as root and bootable. Mark the smaller partition (for the time being) as unused. That should get you through the partitioner.
I'm having the same problem. It won't make the other partitions. I wanted / 2.2 gig, /home 1g, /var 500M, and 400+m swap. But it will not let me do that, so I am just partitioning / with 2.2 gig. The one visible problem is that there is insufficient room for the mount point labels, but that should not affect partitioning.
Aack, now it wants me to add swap space, and prints dire warnings if I don't do it. But then that failed, too.
-
Quote from cortez....
I manually partitioned the disk and split it up in two partitions one sized 3.9Gb and the other about 280Mb. Mark the big partition as root and bootable. Mark the smaller partition (for the time being) as unused. That should get you through the partitioner.
I did what he says but I used all the disk as / and I didn't put the bootable flag on. But it is in the middle of installing software now.
Don't use any 'help' or 'guided' options in the partitioner.
I expect to have problems because I didn't set the bootable flag. i'll probably have to do some playing about with the partitioning facility under Meanie's pdaxIII utilities.
But cortez's tip about doing a manual partition and leaving free space for a later swap should be OK. It is working for me at the moment. It is taking a vast amount of time because I forgot to de-select the desktop option in software selection.
-
Installation succesfully completed
Now selecting the packages to install
I'm jealous. I am again at the point of retrieving packages to complete the installation, I think, and it hangs here, "Retrieving packages" 0% --- I used the default site. The defaults had no special directories to look in or anything. Why is it hanging?
-
Installation succesfully completed
Now selecting the packages to install
I'm jealous. I am again at the point of retrieving packages to complete the installation, I think, and it hangs here, "Retrieving packages" 0% --- I used the default site. The defaults had no special directories to look in or anything. Why is it hanging?
6% now, with a new try using Cortez' new build with my libertas module available. Still installing, using my old wifi card.
Now, once this gets installed, I guess I look at zdevil's postinstall tarball. But, to update, are there any better (faster, from the US) archives than the default for armel? Can I put most any archive in, or will they not have armel at all? 'Cause I am still at 6%. This thing is no "broadband" connection right now. New things get retrieved, which is good. But, sheesh.
-
Installation succesfully completed
Now selecting the packages to install
I'm jealous. I am again at the point of retrieving packages to complete the installation, I think, and it hangs here, "Retrieving packages" 0% --- I used the default site. The defaults had no special directories to look in or anything. Why is it hanging?
6% now, with a new try using Cortez' new build with my libertas module available. Still installing, using my old wifi card.
Now, once this gets installed, I guess I look at zdevil's postinstall tarball. But, to update, are there any better (faster, from the US) archives than the default for armel? Can I put most any archive in, or will they not have armel at all? 'Cause I am still at 6%. This thing is no "broadband" connection right now. New things get retrieved, which is good. But, sheesh.
Well, it has gotten further, but now seems to be stuck at 3% in the "select and install software" step, in "preparing to configure pcmciautils". I wish I could find out what is happening, but that does not seem possible without stopping the process.
It's getting late, so I will let it continue as it is. I guess everyone else is asleep already...
-
Just retrying my install. I left the software business running over night. It was stuck in the middle of the gimp. Anyhow, I've restarted the process, this time I set a bootable / partition of 16 GB and left the other 0.4 GB free. It told me that a swap was useful and asked if I really wanted to carry on. I did!
All proceeded smoothly, by the time I get out of the bath I should be at the choose what to install stage. This time I'll just pick 'standard' system. I expect I'll leave it to do that and go out. I hope to be at the final stages when I come back from town.
TERMINATOR!
-
Just retrying my install. I left the software business running over night. It was stuck in the middle of the gimp. Anyhow, I've restarted the process, this time I set a bootable / partition of 16 GB and left the other 0.4 GB free. It told me that a swap was useful and asked if I really wanted to carry on. I did!
All proceeded smoothly, by the time i get out of the bath I should be at the choose waht to install stage. This time I'll just pick 'standard' sytem. I expect I#ll leave it to do that and go out. I hope to be at the final stages when I come back from towm.
TERMINATOR!
Nice change in your signature. "cortez-debian" I hope it stays there
My installation got stuck at 3% in the "select and install software" step in "preparing to configure pcmciautils". I'll try again with a different kernel setup.
-
Just retrying my install. I left the software business running over night. It was stuck in the middle of the gimp. Anyhow, I've restarted the process, this time I set a bootable / partition of 16 GB and left the other 0.4 GB free. It told me that a swap was useful and asked if I really wanted to carry on. I did!
All proceeded smoothly, by the time i get out of the bath I should be at the choose waht to install stage. This time I'll just pick 'standard' sytem. I expect I#ll leave it to do that and go out. I hope to be at the final stages when I come back from towm.
TERMINATOR!
Nice change in your signature. "cortez-debian" I hope it stays there
My installation got stuck at 3% in the "select and install software" step in "preparing to configure pcmciautils". I'll try again with a different kernel setup.
I think the sig will stay!!!!!
The install finished, reboot is going through and the / partition is undergoing fsck!
The signature will be updated when I find out if it is sid/unstable and precisely which kernel is in there.
Houston BigZ has landed!
I'm at the login. I suspect there will be much to play with, but I have to go out!
TERMINATOR!
There are no modules. So where can I get them? Never mind I expect they are in the tar I downloaded... Is it because I couldn't find the don't format option? Cheers.
-
Houston BigZ has landed!
I used the same step as on the TitchyLinux site: the one that uses dpkg-deb -x. The tab command completion is very useful. This got me the modules over, depmod and a reboot got me to the point of being able to edit the blacklist to stop hostap and hostap_cs loading. I have to do this because all my Wifi cards refuse to work with hostap and orinoco loaded.
So I have the module, and a working wifi link. I have just done apt-get update. The keyboard will need doing some way or another.
cortez, do you think I should do a dpkg -i on the zaurus-specific.deb?
I've got to go out until late tonight, so I must quit for now.
This works for me. cortez, I think you need to edit your instructions, or make a new post, to explain the partitioning solution and how to make sure that the modules don't get zapped in install. Then people won't need to do my dpkg-deb -x trick.
By the way cortez, I left that free space for putting a swap in later on. The boot messages claim that a swap is being set up. I've not had time to check what is going on there.
I really must go to the dance lessons.
-
Great work tux!
I've updated the instructions in the first post.
It's now time to finish it up and do the post-installation stuff.
-
Great work tux!
I've updated the instructions in the first post.
It's now time to finish it up and do the post-installation stuff.
Hi cortez,
I think you should emphasise that the kernel and modules are produced by you using the poky build system and source tree. I have no idea about any possible conflicts if angstrom packages and related tips might cause problems, but I think we should make people aware of the possibility.
I suppose my missing the don't format bit off caused me to have to do the dpkg-deb -x trick to get the modules and would have prevented the unpacking of the deb packages to the microdrive?
Post-Install: I'm going to start a new thread?
About the keyboard, is it supposed to be set up automatically by the install? If not does it matter if I use keymap.map as in ZDevil's Monster thread or the spitz.gz file from the TitchyLinux files?
What about the gui/X system? Where do I start looking?
One definite plus for this install, the hardware clock is sorted out without needing any clever tricks. The wifi only had the post-install problem of blacklisting the hostap modules. The dhcp in the installer works well!
Pending any answers, tips from you and other testers I'll use the ssh server I've just installed to do some investigating.
-
I think you should emphasise that the kernel and modules are produced by you using the poky build system and source tree. I have no idea about any possible conflicts if angstrom packages and related tips might cause problems, but I think we should make people aware of the possibility.
As far as I know Angstrom and Poky share most of their packages, so impact on installed package is probably be minimal (no guarantees).
I suppose my missing the don't format bit off caused me to have to do the dpkg-deb -x trick to get the modules and would have prevented the unpacking of the deb packages to the microdrive?
Did you choose to leave the first partition as it was, or did you had it formatted by the installer. The modules where copied before the Installer started, so they should have been there.
About the keyboard, is it supposed to be set up automatically by the install? If not does it matter if I use keymap.map as in ZDevil's Monster thread or the spitz.gz file from the TitchyLinux files?
I included the files needed to set the keymap and tried to start a script on startup automatically. I have to look into it, since it doesn't work. A simple loadkeys /etc/keymap-2.6.map does the job.
What about the gui/X system? Where do I start looking?
Just install the kdrive xserver from the poky feed. then install the wm of your liking.
-
cortez said: "I included the files needed to set the keymap and tried to start a script on startup automatically. I have to look into it, since it doesn't work. A simple loadkeys /etc/keymap-2.6.map does the job."
So I tried that. No joy! I looked in /etc no keymap-2.6.map. I did extract the contents of zaurus-specific.deb across. It worked, udev and the modules do their job.
I looked inside zaurus-specific.deb. The keymap is not there. This is in the version from the tar file.
So i'll try keymap.map from ZDevils postinstallation tar.
I have started a post installation thread for this system. I'll post anything else in there.
-
I can't see anything here about my problem. I wonder what happened.
Here is what I did: flashed cortez' kernel with the libertas module, and included the other files in his AllInone packgage.
Eventually, it installed everything. I had problems with the partitioning, but so have others. It then installed a base system, as requested. This had several false starts, but eventually finished.
But then when it said to re-boot, no joy. It hung up on asking for a runlevel. I then, using the emergency system, changed /etc/init to boot into runlevel 2 (from my desktop). Then it says Entering runlevel 2 --- and hangs.
Fuck. All I can do is start from the beginning again. I ain't happy. Maybe I will manage to shell out and re-partition and reformat, who knows, that may help. If not this, then it is on to yonggum unless someone can come to my rescue. But cortez is probably asleep. Shit.
-
I can't see anything here about my problem. I wonder what happened.
Here is what I did: flashed cortez' kernel with the libertas module, and included the other files in his AllInone packgage.
Eventually, it installed everything. I had problems with the partitioning, but so have others. It then installed a base system, as requested. This had several false starts, but eventually finished.
But then when it said to re-boot, no joy. It hung up on asking for a runlevel. I then, using the emergency system, changed /etc/init to boot into runlevel 2 (from my desktop). Then it says Entering runlevel 2 --- and hangs.
Fuck. All I can do is start from the beginning again. I ain't happy. Maybe I will manage to shell out and re-partition and reformat, who knows, that may help. If not this, then it is on to yonggum unless someone can come to my rescue. But cortez is probably asleep. Shit.
I don't suppose this is likely, but did you set the / partition as bootable in the partitioner?
-
I am trying for the third or fourth time today to re-install using this method. I have no idea what is going wrong. I installed successfully, as I said previously, with the 'mistake' in partitioning that reformatted the disk. This lost the modules etc that the method copies over. I then copied them manually and got a working command line system.
I tried to reinstall using the tips about setting the bootable flag, preventing the partitioner from formatting the / partition. Each time I have tried this the install hangs at the stage of downloading the standard system.
I've tried this time with a 128 MB card and freshly untarred files. I have now reached the message about installing to an unclean target: this means that the / partition was not formatted over. I'll persevere: but if this time I'm unsuccessful, I'm going to retry with manual partitioning and formatting the partitions. Whatever happens this method has some unfortunate bugs in it.
Don't give in cortez, I'm sure this is the way to go.
-
I can't see anything here about my problem. I wonder what happened.
Here is what I did: flashed cortez' kernel with the libertas module, and included the other files in his AllInone packgage.
Eventually, it installed everything. I had problems with the partitioning, but so have others. It then installed a base system, as requested. This had several false starts, but eventually finished.
But then when it said to re-boot, no joy. It hung up on asking for a runlevel. I then, using the emergency system, changed /etc/init to boot into runlevel 2 (from my desktop). Then it says Entering runlevel 2 --- and hangs.
Fuck. All I can do is start from the beginning again. I ain't happy. Maybe I will manage to shell out and re-partition and reformat, who knows, that may help. If not this, then it is on to yonggum unless someone can come to my rescue. But cortez is probably asleep. Shit.
I don't suppose this is likely, but did you set the / partition as bootable in the partitioner?
Yes, I did.
-
I'm interested in trying this on my C1000 when you are able to get the necessary files for it in order
-
I can't see anything here about my problem. I wonder what happened.
Here is what I did: flashed cortez' kernel with the libertas module, and included the other files in his AllInone packgage.
Eventually, it installed everything. I had problems with the partitioning, but so have others. It then installed a base system, as requested. This had several false starts, but eventually finished.
But then when it said to re-boot, no joy. It hung up on asking for a runlevel. I then, using the emergency system, changed /etc/init to boot into runlevel 2 (from my desktop). Then it says Entering runlevel 2 --- and hangs.
Fuck. All I can do is start from the beginning again. I ain't happy. Maybe I will manage to shell out and re-partition and reformat, who knows, that may help. If not this, then it is on to yonggum unless someone can come to my rescue. But cortez is probably asleep. Shit.
I don't suppose this is likely, but did you set the / partition as bootable in the partitioner?
Yes, I did.
SUCCESS!!!! I got it to install, and boot. I have no modules.dep, but I think that is fixed elsewhere, and I will look it up. I need to fix a whole lot of stuff, like keymap, X, blah, blah, blah. But it is running, so half the battle is over.
the key, for me, was to RE-FORMAT /dev/hda1. Then the installation went through.
-
I can't see anything here about my problem. I wonder what happened.
Here is what I did: flashed cortez' kernel with the libertas module, and included the other files in his AllInone packgage.
Eventually, it installed everything. I had problems with the partitioning, but so have others. It then installed a base system, as requested. This had several false starts, but eventually finished.
But then when it said to re-boot, no joy. It hung up on asking for a runlevel. I then, using the emergency system, changed /etc/init to boot into runlevel 2 (from my desktop). Then it says Entering runlevel 2 --- and hangs.
Fuck. All I can do is start from the beginning again. I ain't happy. Maybe I will manage to shell out and re-partition and reformat, who knows, that may help. If not this, then it is on to yonggum unless someone can come to my rescue. But cortez is probably asleep. Shit.
I don't suppose this is likely, but did you set the / partition as bootable in the partitioner?
Yes, I did.
SUCCESS!!!! I got it to install, and boot. I have no modules.dep, but I think that is fixed elsewhere, and I will look it up. I need to fix a whole lot of stuff, like keymap, X, blah, blah, blah. But it is running, so half the battle is over.
the key, for me, was to RE-FORMAT /dev/hda1. Then the installation went through.
I have uploaded the keymap.map file in the post-install thread. I wonder if keympa.spitz.gz from the TitchyLinux deb would be easier to use to do a 'permanent' fix? I don't want to play with startup scripts to make loadkeys keymap.map work at every reboot!
I think X is meant to be installed after the basic install, like all the other methods, I'm hoping that an easier way will be produced as this cortez-debian is debugged and polished up?
-
the key, for me, was to RE-FORMAT /dev/hda1. Then the installation went through.
The above quote from dlj0 is also true for me. Unless I choose to let the installer reformat the drive, installation fails.
YMMV.
cortez does say that he had success preventing reformat and hence didn't need to unpack zaurus-specific.deb after the install of the base system.
-
Hi,
I tried to setup the Debian Installer in a way we can do a fully customized install of Debian without the use of the prefab root file system. See attached all files needed. The kernel used is a brand new 2.6.23 Poky kernel. The zaurus-specific package is just a beginning. I'm sure there's stuff missing here and there. The zaurus-specific package includes the corresponding kernel modules and firmware drivers with which you should be able to perform the (wireless) network installation (DHCP is included). The ramdisk.gz file contains the actual Debian Installer. More info on that can be found here (http://www.applieddata.net/forums/topic.asp?TOPIC_ID=2442).
This version does not require the use of uboot. As said before, although the idea of uboot is great, it can be a real pain to install. More important, if not installed succesfully, it's an even greater pain to get your (seemingly bricked) device back to a working state. It took me quite a while to restore my 3100 after trying the yonggum kernel with uboot.
You can put any additional Debian package files on the SD if you want to use them. After flashing the kernel the updater script will extract any .deb file from the SD to the root of the microdrive. This makes it possible for instance to use a different kernel. Just add the corresponding kernel modules (in a deb package format!) to the SD and it should work.
This version currently only works with the C3x00 models. If this works out to be successfull and if time permits, I will build a C1000 kernel+package and maybe (depending on the help I get from ZDevil ) even a Cxx0 version to test this procedure.
==========
1. Preparation
==========
a. Extract all files from the attached AllInOne.tar archive and put them on SD. Flashing from CF is currently not supported.
b. You can put any optional debian packages (.deb) on the SD. After flashing the kernel all available .deb files on SD will be extracted to the root of the microdrive.
==========
2. Flashing
==========
a. Remove battery, wait 5 secs, place battery and attach AC power.
b. Press "OK" key and keep it pressed, then press "On/Off" button.
c. In the maintenance menu, choose "4" (Update) in the first screen, "2" (SD) in the second and "Y" in the third
d. The kernel will be flashed, the microdrive formatted and the Installer will be setup.
Your Zaurus will reboot and the Installer is started.
==========
3. The installer
==========
a. Choose your language and location
b. Network configuration. Choose the driver of your network card (yes, you need one). DHCP is included in the installer, so hopefully your network settings are automatically configured.
c. Choose the hostname and domain name. It's fine to accept the defaults, since you can always change them later.
d. Partitioning the disk. This is the most tricky bit, since the installer is currently unable to mount the swap partition. Choose for manual partitioning, and create two partitions, the first a big one and the second a smaller one. Make the smaller one about 200/250Mb and assign the rest of the diskspace to the first partition. Make the first partition primary, bootable, set the mount point to / (root) and choose the ext3 filesystem. I choose the option to not format the partition this partition and leave the current filesystem alone. Make the second partition a swap partition, primary, not bootable and don't give it a mount point. Choose the option to not use it (we deal with that later on). The Installer will complain about not having a swap partition, but you can ignore that and continue the installation.
e. The downloading and installation of the base Debian system begins. Be patient, and keep your finger crossed!
f. Ignore the message about not being able to find the right kernel. Just continue
g. At the "software installation" screen choose only to install the base system.
==========
4. Post-Installation
==========
This is work in progress, we need to setup a few extra's. At the time of writing, this still has to be done. Here's were I need your help, since I don't have the time to do this all on my own.
Good luck!
cortez
I have posted on this elsewhere but thought it worth saying again. The highlighted section in the quote from cortez has worked for him. It did not work for me and I tried it a few times. I have been successful only when I allow the partitions to be formatted. If you are in the same boat this gives you some extra steps to install the base system.
Below are modified instructions from the TitchyLinux site. Before you do the install, copy the attached keymap.map file to the SD card, remove the .txt from the filename. .
cd ..
mkdir media/card
mount dev/mmcblk0p1 media/card
dpkg-deb -x media/card/zaurus-specific.deb .
loadkeys media/card/keymap.map
depmod
You may then need to do: nano /etc/modprobe.d/blacklist and put these two lines in:
blacklist hostap_cs
blacklist hostap
You will need to do the loadkeys bit after every reboot, so it is worth copying the file from the SD card to /etc. (There are other ways to deal with the keyboard issue.)
-
I tried to install several times - was successful, but when I rebooted each time I got a Kernel Panic? So I decided to give the U-Boot - 2.6.23.1 - EABI method a try. I was successful in getting that up and running, but too many little bugs compared to the TichyLinux system. Debating what to do next. I did notice that if I do not press 2 on reboot with U-boot I get a similar Kernel Panic error - is that the mistake I made with Cortez-Debian? Do you need to press 2 on boot?
-
I tried to install several times - was successful, but when I rebooted each time I got a Kernel Panic? So I decided to give the U-Boot - 2.6.23.1 - EABI method a try. I was successful in getting that up and running, but too many little bugs compared to the TichyLinux system. Debating what to do next. I did notice that if I do not press 2 on reboot with U-boot I get a similar Kernel Panic error - is that the mistake I made with Cortez-Debian? Do you need to press 2 on boot?
Uboot is a multiple boot system :
- pressing nothing : boot from flash
- pressing 1 : boot from SD
- pressing 2 : boot from microdrive
- pressing 3 : boot from CF
- pressing OK : install new kernel and/or system on flash
So,
Pressing "2" boots from microdrive, pressing "1" boots from SD which can contain Titchy. You don't have to choose, you can have both !
Chero.
-
I tried to install several times - was successful, but when I rebooted each time I got a Kernel Panic? So I decided to give the U-Boot - 2.6.23.1 - EABI method a try. I was successful in getting that up and running, but too many little bugs compared to the TichyLinux system. Debating what to do next. I did notice that if I do not press 2 on reboot with U-boot I get a similar Kernel Panic error - is that the mistake I made with Cortez-Debian? Do you need to press 2 on boot?
Uboot is a multiple boot system :
- pressing nothing : boot from flash
- pressing 1 : boot from SD
- pressing 2 : boot from microdrive
- pressing 3 : boot from CF
- pressing OK : install new kernel and/or system on flash
So,
Pressing "2" boots from microdrive, pressing "1" boots from SD which can contain Titchy. You don't have to choose, you can have both !
Chero.
Thanks Chero
But I guess I was not clear - I do understand how U-boot works, but what I was asking was is it also necessary to Press 2 to boot from hard drive with Cortez-Debian? I ask this because I got the same error trying to boot Cortez-Debian as I did when I forgot to press 2 booting with Uboot. I know cortez's version did not use uboot - so it is unlikely, but....
-
I tried to install several times - was successful, but when I rebooted each time I got a Kernel Panic? So I decided to give the U-Boot - 2.6.23.1 - EABI method a try. I was successful in getting that up and running, but too many little bugs compared to the TichyLinux system. Debating what to do next. I did notice that if I do not press 2 on reboot with U-boot I get a similar Kernel Panic error - is that the mistake I made with Cortez-Debian? Do you need to press 2 on boot?
Uboot is a multiple boot system :
- pressing nothing : boot from flash
- pressing 1 : boot from SD
- pressing 2 : boot from microdrive
- pressing 3 : boot from CF
- pressing OK : install new kernel and/or system on flash
So,
Pressing "2" boots from microdrive, pressing "1" boots from SD which can contain Titchy. You don't have to choose, you can have both !
Chero.
Thanks Chero
But I guess I was not clear - I do understand how U-boot works, but what I was asking was is it also necessary to Press 2 to boot from hard drive with Cortez-Debian? I ask this because I got the same error trying to boot Cortez-Debian as I did when I forgot to press 2 booting with Uboot. I know cortez's version did not use uboot - so it is unlikely, but....
Since you've been using uboot and don't any longer :did you do a nand-restore before installing "cortez-debian" ?
If not, it's not likely that it will work ...