Debian Eabi With Installer

[tux]

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.

[tux]

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.

[cortez]

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.

[tux]

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.

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

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.

[tux]

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.

[dlj0]

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.

[tux]

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?

[tux]

 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.  

[dlj0]

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.

[mscdex]

I'm interested in trying this on my C1000 when you are able to get the necessary files for it in order

[dlj0]

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.

[tux]

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?

[tux]

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.

[tux]

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.

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