Post-install Steps For Debian Eabi With Installer, What to do after installing debian the cortez way! Options

[tux]

What needs doing after a successful installation of cortez-debian. I'm talking about the version of debian and the installer provided by cortez in this thread Debian Eabi With Installer.

Please re-read the first post in that thread because it has been updated. Follow the steps carefully to ensure fewer problems during and post-install.

It is worth remembering that the kernel and modules used in this method, 2.6.23 at the moment, have been produced by cortez using the build system and source tree used by the Poky linux developers. I believe this is based on bitbake and the angstrom work. I think it is worth considering that there may be incompatabilities between this system and the angstrom kernel, modules and packages.

I have successfully installed this system. However I did make an error in allowing the partitioner to format the new / partition. This meant that I had to copy the modules for the kernel across to the microdrive by using the method shown on the TitchyLinux site. I mean I had to mount the SD card and use this command: dpkg-deb -x (pathtofileon SDcard)zaurus_specific.deb . while being in the / directory of the microdrive.


Does it matter if I use keymap.map as in ZDevil's Monster thread or the spitz.gz file from the TitchyLinux files in order to set up the keyboard? Would it be automatically set upif I hadn't let the partitioner format /?

What about the gui/X system? Where do I start looking? cortez says get kdrive from PokyLinux and install it. Then install the window maager of your choice.

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. I have to do this post-install with all methods and varieties of debian, because all my wifi cards work with orinoco and fail with hostap loaded.

The dhcp in the installer works well!

It is much easier to work from the console if you install the openssh-server and login from a terminal on your desktop or use putty. It is vital to work this way when trying to get X to work. It is possible to have a Zaurus which loads X, but a non-working variety, and the only way to mend things is from a remote console.

Hope this thread is of use, especially to me , to people who are testing this convenient way of installing an EABI + EABI debian system on their Z.

This post has been edited by tux: Nov 4 2007, 12:47 AM

[dlj0]

I finally got X running under eabi/cortez!!!

My steps were different from most. In order to not have the server rotated, I used titchy's script, modified, instead of just linking X to Xfbdev. I also had ts problems.

Very importantly, I had to edit /etc/ts.conf . As installed, it had

module_raw corgi

Then, I needed to arrange the device for the ts. I could manually set TSLIB_TSDEVICE=/dev/input/event1 and that would work (thanks jpmatrix!!), but re-starting would overwrite that to TSLIB_TSDEVICE=/dev/input/ts0, which does not exist on my machine. I could make a link, but this being udev, that link dissolves on each boot.

So, I replaced /usr/bin/X with

#!/bin/sh
export TSLIB_TSDEVICE=/dev/input/event1
exec /usr/bin/Xfbdev -screen 480x640@270 "$@"

and wolla! (That is, voil\`{a}, but I donno how to do accents on this).

Now I have to try to get the gnomish stuff working, which it is not at present. Difficulty there is that libgtk-2.0.0 won't install, because the available version of the libgtk-common is a bit too old.

But, I am up and running.

[jpmatrix]

I finally got X running under eabi/cortez!!!

My steps were different from most. In order to not have the server rotated, I used titchy's script, modified, instead of just linking X to Xfbdev. I also had ts problems.

Very importantly, I had to edit /etc/ts.conf . As installed, it had

module_raw corgi

Then, I needed to arrange the device for the ts. I could manually set TSLIB_TSDEVICE=/dev/input/event1 and that would work (thanks jpmatrix!!), but re-starting would overwrite that to TSLIB_TSDEVICE=/dev/input/ts0, which does not exist on my machine. I could make a link, but this being udev, that link dissolves on each boot.

So, I replaced /usr/bin/X with

#!/bin/sh
export TSLIB_TSDEVICE=/dev/input/event1
exec /usr/bin/Xfbdev -screen 480x640@270 "$@"

and wolla! (That is, voil\`{a}, but I donno how to do accents on this).

Now I have to try to get the gnomish stuff working, which it is not at present. Difficulty there is that libgtk-2.0.0 won't install, because the available version of the libgtk-common is a bit too old.

But, I am up and running.

oh yeah i forgot that ts.conf stuff i put it into the wiki post install page right now !
i had the same reboot problem so i put my TSLIB line into my /etc/X11/xdm/Xsession ...
et voila !!