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

[tux]

Finally I have cortez-debian with X! But the Wiki pages and the linked threads are so fragmented!!! Thanks anyway guys.. I finally blundered my way through.

Particular thanks to cortez for his install files being smooth working. Thanks for the thousands of words from ZDevil..

I would never have got there if it hadn't been for the fact that I used ssh to cut and paste the steps from ZDevil's afterinstall scripts, one after the other, into the terminal on BigZ!

The X system gave me the biggest struggle and jpmatrix's page of tips at the Wiki got me through. But I didn't have the luck to be able to use his preferred steps. I had to take the alternatives he suggested.

Points to note:
1. I used cortez's files to install. This means I used his kernel and modules.
2. When it came to X it had no touchscreen calibration nor use of mouse.
3 So I left the first module_raw uncommented.
4. I could not get calibration to work with the use of a script, I had to use this command at the terminal :export TSLIB_TSDEVICE=/dev/input/event1
5. finally ts_calibrate worked....
6. I used rmmod mousedev to get the pointer to behave itself after X started.

I think I'm going to have to suspend BigZ to keep X working or I'll have to manually do export TSLIB_TSDEVICE=/dev/input/event1 and rmmod mousedev after each boot. I will eventually get this automated but the tips don't seem to work as advertised so far...

One other thing jpmatrix, so far I've not managed to get your tips about running X as a non-root user working. But tomorrow is another day.

[dlj0]

Finally I have cortez-debian with X! But the Wiki pages and the linked threads are so fragmented!!! Thanks anyway guys.. I finally blundered my way through.

That makes two of us.

I would never have got there if it hadn't been for the fact that I used ssh to cut and paste the steps from ZDevil's afterinstall scripts, one after the other, into the terminal on BigZ!

That makes two of us!

The X system gave me the biggest struggle and jpmatrix's page of tips at the Wiki got me through. But I didn't have the luck to be able to use his preferred steps. I had to take the alternatives he suggested.

Points to note:
1. I used cortez's files to install. This means I used his kernel and modules.
2. When it came to X it had no touchscreen calibration nor use of mouse.
3 So I left the first module_raw uncommented.
4. I could not get calibration to work with the use of a script, I had to use this command at the terminal :export TSLIB_TSDEVICE=/dev/input/event1
5. finally ts_calibrate worked....
6. I used rmmod mousedev to get the pointer to behave itself after X started.

I think I'm going to have to suspend BigZ to keep X working or I'll have to manually do export TSLIB_TSDEVICE=/dev/input/event1 and rmmod mousedev after each boot. I will eventually get this automated but the tips don't seem to work as advertised so far...

For the fouchscreen, to calibrate I had to comment out the line in /etc/ts.conf that installed a config file for a corgi or some such. Then it worked.

For the user-X, and to consistently get the TSLIB device set up, replace /usr/bin/X with the following script:

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

chmod 4755 this file and it will work.

I think cortez himself has gone back to the drawing board on this, so you and I may be the only ones using it. But I have gotten to the point that this thing is better than it ever was. The only major hassle now is the browser issue, and I have workarounds for that, along with minor hassles.

[tux]

That makes two of us!

For the user-X, and to consistently get the TSLIB device set up, replace /usr/bin/X with the following script:

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

chmod 4755 this file and it will work.

I think cortez himself has gone back to the drawing board on this, so you and I may be the only ones using it. But I have gotten to the point that this thing is better than it ever was. The only major hassle now is the browser issue, and I have workarounds for that, along with minor hassles.

Just tried it! Login screen is rotated!!

It won't be difficult to fix. Login works and mouse behaves itself and so does the rotated desktop. Funnily enough, I didn't include rmmod mousedev in the script (thanks for that suggestion scottlfa ) but the mouse isn't jumping.

Can't say I'm in love with icewm though.

Cheers.. breakfast calls...

This post has been edited by tux: Nov 21 2007, 01:29 AM

[jpmatrix]

Just tried it! Login screen is rotated!!

It won't be difficult to fix. Login works and mouse behaves itself and so does the rotated desktop. Funnily enough, I didn't include rmmod mousedev in the script (thanks for that suggestion scottlfa ) but the mouse isn't jumping.

Can't say I'm in love with icewm though.

Cheers.. breakfast calls...

just add this line somewhere in your scripts :

xrandr -o right

and yes, icewm rocks!

perhaps we should put all config files that works on a web server. i've yet started with some files in matrixmen.free.fr/zaurus/debian