OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Debian => Topic started by: tux on November 03, 2007, 07:26:47 pm
-
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 (https://www.oesf.org/forum/index.php?showtopic=24979).
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.
-
Make sure to check the original thread for any updates on the installation process, I'll try to keep it updated to prevent all this useful info scattering all over the forum. Any post-installation steps can easily be integrated into the Installer by extending the preseed.cfg file located in the root directory. Look for instructions on how to do this here (http://d-i.alioth.debian.org/manual/en.i386/apb.html).
The file currently contains:
# Preseed file to make d-i download udebs from unstable, useful for daily
# builds and development builds.
d-i mirror/udeb/suite string unstable
d-i mirror/udeb/suite seen false
# armel repo
d-i mirror/country string enter information manually
d-i mirror/country seen false
d-i mirror/http/hostname string ftp.gnuab.org
d-i mirror/http/hostname seen false
d-i mirror/http/directory string /debian
d-i mirror/http/directory seen false
d-i mirror/suite string unstable
d-i mirror/suite seen false
d-i debian-installer/allow_unauthenticated string true
d-i apt-setup/local0/repository string http://ftp.gnuab.org/debian/ unreleased main
d-i apt-setup/local0/source boolean true
d-i apt-setup/local0/key string http://archive.gnuab.org/gnuab_key_2007.asc
-
Fixing the keyboard.
I got keymap.map from ZDevil's afterinstall tar and copid it to /etc.Then loadkeys /etc/kemap.mapworked to load the correct key table. It has to be repeated at each reboot but I can fix that later. I am going to check keymap.spitz.gz from the TitchyLinux setup file. If that works I'lldo the pernaent cute with that file.
Bear in mind that cortez has set the keymap file he uses to copy into /etc at install and that I didn't tell the partitioner not to format /, so this fix may not be necessary for you.
I suppose I should try a reinstall to check that out?
-
Fixing the keyboard.
I got keymap.map from ZDevil's afterinstall tar and copied it to /etc.Then loadkeys /etc/kemap.mapworked to load the correct key table. It has to be repeated at each reboot but I can fix that later. I am going to check keymap.spitz.gz from the TitchyLinux setup file. If that works I'll do the permanent cure with that file.
Bear in mind that cortez has set the keymap file he uses to copy into /etc at install and that I didn't tell the partitioner not to format /, so this fix may not be necessary for you.
I suppose I should try a reinstall to check that out?
I did try and reinstall and ran into many problems. Is there some sort of limit on the usable size of SD card for flashing purposes? I seem to be getting a success with my 128 MB card and my failures were with a 1GB card.
If this re-install works I'll check if the keymap.map file is present.
Is there an enthusiastic and dozy amateur's guide to getting the kdrive packages and installing them? (And I do mean dozy!) I have gone wandering around the poky site and the angstrom site and Google is not being very friendly at the moment! Has someone got a 'smart' question for me use?
Cheers
-
Fixing the keyboard.
I got keymap.map from ZDevil's afterinstall tar and copid it to /etc.Then loadkeys /etc/kemap.mapworked to load the correct key table. It has to be repeated at each reboot but I can fix that later. I am going to check keymap.spitz.gz from the TitchyLinux setup file. If that works I'lldo the pernaent cute with that file.
Bear in mind that cortez has set the keymap file he uses to copy into /etc at install and that I didn't tell the partitioner not to format /, so this fix may not be necessary for you.
I suppose I should try a reinstall to check that out?
Hey, I could not find keymap.map from Zdevil's tarball. Where is it? I may have a bad version of it, since the untar ended abnormally. Anyway, to get me started, can you send keymap.map to me? I can't get much running without a / !
-
I have re-installed: but BigZ insists on my choosing to let the partition be formatted. hence I have to dpkg-deb -x on the zaurus-specific.deb to get the modules across. I also had to blacklist hostap and hostap_cs.
As usual, once these debian thingies are installed they are rock solid in the wifi department.
Right dlj0 here is my attempt at uploading the keymap file from ZDevil's Monster method tar.
I'm hoping some clever fellow will give me some hints about the X business. I suppose I could try to use the afterinstall tar ball and scripts from ZDevil? But I'd have to watch out for incompatibilitiies with yongun?
-
I have re-installed: but BigZ insists on my choosing to let the partition be formatted. hence I have to dpkg-deb -x on the zaurus-specific.deb to get the modules across. I also had to blacklist hostap and hostap_cs.
As usual, once these debian thingies are installed they are rock solid in the wifi department.
Right dlj0 here is my attempt at uploading the keymap file from ZDevil's Monster method tar.
I'm hoping some clever fellow will give me some hints about the X business. I suppose I could try to use the afterinstall tar ball and scripts from ZDevil? But I'd have to watch out for incompatibilitiies with yongun?
Thanks. Keys work now. As soon as I can figure out how to configure either of my wifi cards and get on the net, I will get back to you on the X stuff.
I can get the hostap modules blacklisted, as I did with titchy, but unlike titchy, it didn't automatically work after than. I have to configure the wifi settings somehow, and haven't done that before. I also have to worry about my new card, but that is another day.
How did you configure your wifi settings?
-
Replying to dlj0's post above.
That sounds strange! Obviously it must have worked during install as it did for me. It didn't work for me after install even after I did the dpkg-deb -x trick on the zaurus-specific.deb that cortez provides.
I did depmod and rebooted. The wifi got errors at boot-up because of the hostap v Orinoco conflict. So I edited etc/modprobe.d/blacklist and did the usual. Then I booted again and this time the wifi started up OK.
The interfaces file is the one that the install set up. I just had to do the blacklisting.
Well here it is anyway:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
# wireless-* options are implemented by the wireless-tools package
wireless-mode managed
wireless-essid any (I will replace this with my routers essid)
wireless-key1 I put this in during install
This is not quite as fancy as I usually use. I use this example that ZDevil posted and edit it to match my router's configuration.
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.111 ## Or any static IP address of your Z
netmask 255.255.255.0
network 192.168.0.0 ## Or your router's IP but change the last number to "0"
broadcast 192.168.0.255
gateway 192.168.0.1 ## Or your router's IP
# wireless-* options are implemented by the wireless-tools package
wireless-mode managed
wireless-essid YouKnowYouAreNotThatStupid
wireless-key1 ComeOnYourKnowIt
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.0.1 ## Or your router's IP, plus any other nameservers addresses found on your router's interface if you like
Here is the reply from ifconfig -a :-
eth0 Link encap:Ethernet HWaddr 00:02:6F:34:4D:6B
inet addr:192.168.1.107 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5989 errors:0 dropped:0 overruns:0 frame:0
TX packets:2537 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6924887 (6.6 MiB) TX bytes:326917 (319.2 KiB)
Interrupt:169
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 TX bytes:560 (560.0
Here is the response to iwconfig :-
lo no wireless extensions.
eth0 IEEE 802.11b ESSID:"*****" Nickname:"Prism I"
Mode:Managed Frequency:2.437 GHz Access Point: 00:12:17:BD:4B:29
Bit Rate:11 Mb/s Sensitivity:1/3
Retry short limit:8 RTS thr:off Fragment thr:off
Encryption key:************************** Security mode:open
Power Management:off
Link Quality=82/92 Signal level=5/153 Noise level=130/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:0 Missed beacon:0
Actually the ***** is just me obscuring the router essid and wep key
I suppose I should emphasise that the wifi is eth0 and not the eth2 that appears to have to be used in ZDevil's monster thread and in jpmatrix's threads on this stuff...
The cards I am using are all Zonet CF1100s under their skin. Working fine.
-
Replying to dlj0's post above.
That sounds strange! Obviously it must have worked during install as it did for me. It didn't work for me after install even after I did the dpkg-deb -x trick on the zaurus-specific.deb that cortez provides.
Oddly, when I booted it up today with the wifi card in it worked. But when I hotplugged the card in yesterday, it did not work.
I have an odder problem now. I am adding a package, texlive. It is taking a long, long time. I thought I would do something on the side, but cannot log in to another terminal. My password is not accepted. I think this had something to do with the keymap --- basically, what was typed before the keymap change. But I don't know what that was....
Progress occurs. I will try to re-install cortez' zaurus-specific stuff, which I have not yet done since succeeding in getting a system.
-
eth0 IEEE 802.11b ESSID:"*****" Nickname:"Prism I"
Encryption key:668C-1CA8-EF5C-533F-0B35-E9CD-F5 Security mode:open
Actually the ***** is just me obscuring the router essid.
...and you forgot to hide yout key
I suppose I should emphasise that the wifi is eth0 and not the eth2 that appears to have to be used in ZDevil's monster thread and in jpmatrix's threads on this stuff...
mine was eth2 on initial start but after some reboots (or another miracle!) it has become eth0
-
[quote name='jpmatrix' date='Nov 6 2007, 06:05 AM' post='170841']
...and you forgot to hide your key
I've done it now but there isn't much likelihood of some lurker here turning up on my street to hack my router is there?
-
....
Progress occurs. I will try to re-install cortez' zaurus-specific stuff, which I have not yet done since succeeding in getting a system.
I suppose I ought to try a dpkg -i on that package too. I may have unpacked the contents to the microdrive but it may very well need the configuring from the package manager,
About the problem with logging in: I presume you are sshing in from your desktop? If this install is a big package you might have done better to ssh in first and do the install from the terminal session. The processing of the package might be taking most of the resources of the system and having no time for trivialities like logging in ssh sessions!
Cheers
-
Adieu for now folks.
I need to have my system working. Unfortunately, that is not going to happen with debian/eabi, at least not for me, not now. I am going to re-install my oabi titchy from my backups, and get back to work.
My frustrations, for the moment, have involved:
1) the x server, which I can't seem to get going except as root. Both xdm and gdm exit without explanation. I can't get the touchscreen stuff to work at all, and nothing is actually any better than with 'ol titchy. I still can't get the mouse working correctly, and with in addition the touchscreen not working, ...
2) the fact that iceweasel and icedove, though they technically exist on the archive, don't work. Those two apps are critical for me, and without them my machine is not that usable.
I just hope this re-install works.... I will leave in cortez' kernel and modules. That will probably get my sparklan card working. Wish me luck!!
I will check back with this in a bit, since I do believe that eabi is really the way to go.
-
Adieu for now folks.
I need to have my system working. Unfortunately, that is not going to happen with debian/eabi, at least not for me, not now. I am going to re-install my oabi titchy from my backups, and get back to work.
SNIPPED ..
I just hope this re-install works.... I will leave in cortez' kernel and modules. That will probably get my sparklan card working. Wish me luck!!
I will check back with this in a bit, since I do believe that eabi is really the way to go.
I'm going to persist with this. As you can see from my sig, I'm in the happy position of not needing to use BigZ for my working Z. In fact the 6000L is my workaday machine. As regards Debian on the Z, you are absolutely correct. The TitchyLinux system is the most complete: you can have a stable working system with X in a fairly short time and with the minimum of command line tinkering. The only thing that does not 'just work' is multimedia, in particular the sound. If BigZ was my only Z, then TitchyLinux would be my Debian choice until someone sorted out the setting up of the EABI system and some packages, important to me, got built.
I know that some people are working hard to make EABI Debian on the Z much easier to install and make into the stable, working system we all want.
Hope to see you back soon in this neighbourhood.
-
Adieu for now folks.
you should say "au revoir", not "adieu"
adieu means you'll never come back
I need to have my system working. Unfortunately, that is not going to happen with debian/eabi, at least not for me, not now. I am going to re-install my oabi titchy from my backups, and get back to work.
My frustrations, for the moment, have involved:
1) the x server, which I can't seem to get going except as root. Both xdm and gdm exit without explanation. I can't get the touchscreen stuff to work at all, and nothing is actually any better than with 'ol titchy. I still can't get the mouse working correctly, and with in addition the touchscreen not working, ...
2) the fact that iceweasel and icedove, though they technically exist on the archive, don't work. Those two apps are critical for me, and without them my machine is not that usable.
1- flux just gave a trick which enables to run X as $USER and it works perfect
2- with gnuab sources.list, people have reported iceweasel is working. however i didn't succeed but i think that's because i mixed applieddata and gnuab libraries..i'd to remove & try again.
-
Adieu for now folks.
I need to have my system working. Unfortunately, that is not going to happen with debian/eabi, at least not for me, not now. I am going to re-install my oabi titchy from my backups, and get back to work.
SNIPPED ..
I just hope this re-install works.... I will leave in cortez' kernel and modules. That will probably get my sparklan card working. Wish me luck!!
I will check back with this in a bit, since I do believe that eabi is really the way to go.
I'm going to persist with this. As you can see from my sig, I'm in the happy position of not needing to use BigZ for my working Z. In fact the 6000L is my workaday machine. As regards Debian on the Z, you are absolutely correct. The TitchyLinux system is the most complete: you can have a stable working system with X in a fairly short time and with the minimum of command line tinkering. The only thing that does not 'just work' is multimedia, in particular the sound. If BigZ was my only Z, then TitchyLinux would be my Debian choice until someone sorted out the setting up of the EABI system and some packages, important to me, got built.
I know that some people are working hard to make EABI Debian on the Z much easier to install and make into the stable, working system we all want.
Hope to see you back soon in this neighbourhood.
Sooner than I thought. It wouldn't boot after the restore. It complains about not being able to open an initial console, something someone else had trouble with, IIRC. So, when I have time, I will try again the cortez way (I like the fact that his kernel does not need to be run in uboot, and has libertas). I need a way to do that that gets me X running, though.
Clearly eabi is the way to go, if I can do it.
-
Adieu for now folks.
you should say "au revoir", not "adieu"
adieu means you'll never come back
1- flux just gave a trick which enables to run X as $USER and it works perfect
2- with gnuab sources.list, people have reported iceweasel is working. however i didn't succeed but i think that's because i mixed applieddata and gnuab libraries..i'd to remove & try again.
What trick? what window manager? What about touchsceen?
I reported iceweasel working, once, on a remote display. Once I got the x server up I could not repeat that success. What sometimes happens, though, is that remote instances of iceweasel are not really run on the remote machine, if the local machine is running it. I thought it was not, but may have been.
-
Adieu for now folks.
you should say "au revoir", not "adieu"
adieu means you'll never come back
1- flux just gave a trick which enables to run X as $USER and it works perfect
2- with gnuab sources.list, people have reported iceweasel is working. however i didn't succeed but i think that's because i mixed applieddata and gnuab libraries..i'd to remove & try again.
What trick? what window manager? What about touchsceen?
I reported iceweasel working, once, on a remote display. Once I got the x server up I could not repeat that success. What sometimes happens, though, is that remote instances of iceweasel are not really run on the remote machine, if the local machine is running it. I thought it was not, but may have been.
look this thread :
https://www.oesf.org/forum/index.php?showto...st&p=170700 (https://www.oesf.org/forum/index.php?showtopic=24992&view=findpost&p=170700)
a working firefox-like browser : epiphany
-
Looking for ts_open
I am trying to work with cortez to get a new installation package. The first version, based on Zdevil's but working with his kernel, has a few (well, quite a few) broken packages. One of them seems to be the ts stuff. ts_calibrate won't start, and (I'm guessing because of that) xdm won't start. I can run X, at least as root, but only with the mouse. I want to use the touchscreen, and I want to get xdm running.
So, where the fsck is ts_open, and what is it? I installed tslib-calibrate_1.0-r17_armel.deb tslib-conf_1.0-r17_armel.deb libts-1.0-0_1.0-r17_armel.deb and most of the packages in cortez's collection. What am I/is he missing? I couldn't find it on my titchy installation, currently backed up onto my desktop.
-
Looking for ts_open
I am trying to work with cortez to get a new installation package. The first version, based on Zdevil's but working with his kernel, has a few (well, quite a few) broken packages. One of them seems to be the ts stuff. ts_calibrate won't start, and (I'm guessing because of that) xdm won't start. I can run X, at least as root, but only with the mouse. I want to use the touchscreen, and I want to get xdm running.
So, where the fsck is ts_open, and what is it? I installed tslib-calibrate_1.0-r17_armel.deb tslib-conf_1.0-r17_armel.deb libts-1.0-0_1.0-r17_armel.deb and most of the packages in cortez's collection. What am I/is he missing? I couldn't find it on my titchy installation, currently backed up onto my desktop.
I don't know what ts_open is, but for me the error message disappeared after changing the kernel to the yonggun one.
check this thread from here on : https://www.oesf.org/forum/index.php?s=&...st&p=170131 (https://www.oesf.org/forum/index.php?s=&showtopic=24960&view=findpost&p=170131)
Chero
-
Looking for ts_open
I am trying to work with cortez to get a new installation package. The first version, based on Zdevil's but working with his kernel, has a few (well, quite a few) broken packages. One of them seems to be the ts stuff. ts_calibrate won't start, and (I'm guessing because of that) xdm won't start. I can run X, at least as root, but only with the mouse. I want to use the touchscreen, and I want to get xdm running.
So, where the fsck is ts_open, and what is it? I installed tslib-calibrate_1.0-r17_armel.deb tslib-conf_1.0-r17_armel.deb libts-1.0-0_1.0-r17_armel.deb and most of the packages in cortez's collection. What am I/is he missing? I couldn't find it on my titchy installation, currently backed up onto my desktop.
it is not that ts_open is missing but ts_calibrate wants to open a device that does not exist.
ensure that your TSLIB_DEVICE is set
then to log as $USER, try this fluck's tip listed here : https://www.oesf.org/forum/index.php?showto...mp;#entry170700 (https://www.oesf.org/forum/index.php?showtopic=24992&st=0&p=170700&#entry170700)
apt-get install xdm
cd /usr/bin
mv X X.OLD
ln -s Xfbdev X
chmod 2755 Xfbdev
then, you can launch xdm, and log into X as $USER : /etc/init.d/xdm start
that worked for flux and me!
look here too:
https://www.oesf.org/forum/index.php?showto...st&p=170918 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170918)
i had to set TSLIB to /dev/input/touchscreen0 for stylus to work under X
perhaps we should put all these post-install tips in the wiki, i'll try to do this this weekend
-
it is not that ts_open is missing but ts_calibrate wants to open a device that does not exist.
ensure that your TSLIB_DEVICE is set
then to log as $USER, try this fluck's tip listed here : https://www.oesf.org/forum/index.php?showto...mp;#entry170700 (https://www.oesf.org/forum/index.php?showtopic=24992&st=0&p=170700&#entry170700)
apt-get install xdm
cd /usr/bin
mv X X.OLD
ln -s Xfbdev X
chmod 2755 Xfbdev
then, you can launch xdm, and log into X as $USER : /etc/init.d/xdm start
that worked for flux and me!
look here too:
https://www.oesf.org/forum/index.php?showto...st&p=170918 (https://www.oesf.org/forum/index.php?showtopic=24960&view=findpost&p=170918)
i had to set TSLIB to /dev/input/touchscreen0 for stylus to work under X
perhaps we should put all these post-install tips in the wiki, i'll try to do this this weekend
OK:
With Cortez' kernel, there is no such thing as either /dev/input/touchscreen0 or the one in the .profile assignment, /dev/input/ts0
Changing the X to be a link to Xfbdev worked, sort of, in that xdm ran, but the screen is rotated. Still no useful stylus action, though. I put in my old ts.conf from titchy in hopes that it would have useful information, but it still does not work.
So, can I make these devices? Since udev such a question becomes more important, since the devices are harder to deal with than in the old days.
-
it is not that ts_open is missing but ts_calibrate wants to open a device that does not exist.
ensure that your TSLIB_DEVICE is set
I think that once I can figure out which device TSLIB_DEVICE needs to be set to, this might work. In fact, I got somewhere by setting TSLIB_TSDEVICE="/dev/input/mice" and others. I have:
Zaurus:/afterinstall# ls -la /dev/input
total 0
drwxr-xr-x 4 root root 220 Nov 9 15:44 .
drwxr-xr-x 13 root root 2980 Nov 9 16:07 ..
drwxr-xr-x 2 root root 80 Nov 9 15:44 by-id
drwxr-xr-x 2 root root 140 Nov 9 15:44 by-path
crw-rw---- 1 root root 13, 64 Nov 9 15:37 event0
crw-rw---- 1 root root 13, 65 Nov 9 15:37 event1
crw-rw---- 1 root root 13, 66 Nov 9 15:44 event2
crw-rw---- 1 root root 13, 63 Nov 9 15:37 mice
crw-rw---- 1 root root 13, 32 Nov 9 15:37 mouse0
crw-rw---- 1 root root 13, 33 Nov 9 15:44 mouse1
crw-rw---- 1 root root 10, 223 Nov 9 15:38 uinput
and, with some of them, I get a touchscreen calibration screen. But, it always says that the calibration failed.
-
it is not that ts_open is missing but ts_calibrate wants to open a device that does not exist.
ensure that your TSLIB_DEVICE is set
I think that once I can figure out which device TSLIB_DEVICE needs to be set to, this might work. In fact, I got somewhere by setting TSLIB_TSDEVICE="/dev/input/mice" and others. I have:
Zaurus:/afterinstall# ls -la /dev/input
total 0
drwxr-xr-x 4 root root 220 Nov 9 15:44 .
drwxr-xr-x 13 root root 2980 Nov 9 16:07 ..
drwxr-xr-x 2 root root 80 Nov 9 15:44 by-id
drwxr-xr-x 2 root root 140 Nov 9 15:44 by-path
crw-rw---- 1 root root 13, 64 Nov 9 15:37 event0
crw-rw---- 1 root root 13, 65 Nov 9 15:37 event1
crw-rw---- 1 root root 13, 66 Nov 9 15:44 event2
crw-rw---- 1 root root 13, 63 Nov 9 15:37 mice
crw-rw---- 1 root root 13, 32 Nov 9 15:37 mouse0
crw-rw---- 1 root root 13, 33 Nov 9 15:44 mouse1
crw-rw---- 1 root root 10, 223 Nov 9 15:38 uinput
and, with some of them, I get a touchscreen calibration screen. But, it always says that the calibration failed.
it should be /dev/input/event1
in fact my /dev/input/touchscreen0 is a link to /dev/input/event1
for your rotated screen, try to type :
xrandr -o right
try to use this /etc/pointercal too :
-49 -9011 34395792 12146 19 -1999532 65536
-
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.
-
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 !!
-
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.
-
You could make it part of your .profile so it loads every time you login.
# ~/.profile: executed by Bourne-compatible login shells.
export TSLIB_TSDEVICE="/dev/input/event1"
rmmod mousedev
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
mesg n
-
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.
-
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...
-
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.
Yep, although I haven't updated this thread for some time, I'm still working on it . I created a root filesystem from scratch with all basic stuff installed. Some of the installed packages are apt, hal, NetworkManager, Midnight Commander, X11, iceWM. Everything is working fine until now, and best of all is that I didn't need any of the "pre install" and "post install" steps described in all the threads and wiki. All seems to work out of the box until now.
But... It takes so much time to set things up correctly, much more than I expected. Anyhow, I hope that I will succeed in building a fresh root filesystem so each of you will be able to install Debian hassle-free without the need of a rocket scientist
Currently I'm having trouble setting up IceWM. Somehow the desktop is in portrait mode all the time. Any ideas are welcome!
cortez
-
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
-
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...
Really? My login screen is not rotated. Huh. Be sure to include the rotation part of the screen definition. I once tried rmmod'ing (or blacklisting) mousedev, and then the mouse did not work at all, nor did the touchscreen. What I have is stable enough to use (fairly well, anyway) xournal. There is still some jitter, but not much. Maybe I will try rmmoding mousedev again...
Icewm works OK. It's a bit more minimalistic than even xfce4, but has a nicer (IMO) look than xfce4, and is certainly less bloated than gnome.
-
Currently I'm having trouble setting up IceWM. Somehow the desktop is in portrait mode all the time. Any ideas are welcome!
cortez
Try my X script instead of the small executable that the debian packages install. I posted it earlier on this thread. For me both the login screen and the desktop show up in landscape mode.
I would like to know more about the mousedev module. Why do those who remove it have to remove it? How do you do that, since it is being used while X is running? I got bad results when I just blacklisted it.
-
Currently I'm having trouble setting up IceWM. Somehow the desktop is in portrait mode all the time. Any ideas are welcome!
cortez
Try my X script instead of the small executable that the debian packages install. I posted it earlier on this thread. For me both the login screen and the desktop show up in landscape mode.
I would like to know more about the mousedev module. Why do those who remove it have to remove it? How do you do that, since it is being used while X is running? I got bad results when I just blacklisted it.
Hi dlj0,
I am using your script now.
I have also installed xfce and much prefer it to icewm. As regards rmmod mousedev: YMMV, I found that the mouse pointer went shooting off away from the stylus position and this made using the 'mouse' difficult. When I did rmmod mousedev the pointer started to behave itself. As regards doing the rmmod: before I used your script xdm ran and could be stopped to allow me to rmmod mousedev. With your script, xdm doesn't appear to be running. So I'm going to put rmmod mousedev in your script and see what happens!!
jpmatrix's tip about xrandr was used before I used your script and I commented it out to cure the rotated screen. All is ok now apart from some jittering with the mouse. I'm going to investigate the state of my scripts and just what tips are being used now.
By the way, my wifi only works with hostap blacklisted and with the interface called wlan0. I had a real battle to get it working...
-
I am using your script now.
I have also installed xfce and much prefer it to icewm. As regards rmmod mousedev: YMMV, I found that the mouse pointer went shooting off away from the stylus position and this made using the 'mouse' difficult. When I did rmmod mousedev the pointer started to behave itself. As regards doing the rmmod: before I used your script xdm ran and could be stopped to allow me to rmmod mousedev. With your script, xdm doesn't appear to be running. So I'm going to put rmmod mousedev in your script and see what happens!!
jpmatrix's tip about xrandr was used before I used your script and I commented it out to cure the rotated screen. All is ok now apart from some jittering with the mouse. I'm going to investigate the state of my scripts and just what tips are being used now.
By the way, my wifi only works with hostap blacklisted and with the interface called wlan0. I had a real battle to get it working...
Check your /etc/ts.conf file for an uncommented machine definition. I found one, and the mouse started to behave once I commented that line out.
You probably had/have both the xrandr command and the rotation from my script, so it may be 180-degrees rotated.
As-far as the wifi goes, I am doing exactly the same. But, up to now I haven't even configured the wifi, dhclient just seems to find it.
-
I've just spent two nights reinstalling! I installed an application and just accepted the options. Unfortunately the install removed some components that allowed X to work. I should have paid more attention. The app was wifi-radar.
I found the reinstall very tedious. The really annoying thing is running the scripts and then going through the steps manually to check which bits worked and which bits need to be done manually. The 2nd-cfg script needs debugging.... But I suppose if cortez's new scheme for a tarball of a working system with X works out this isn't likely to be needed.
Again setting up the wifi seemed very problematical. I know now to use wlan0 and set it up as per the interfaces file from my install of Titchy. (By the way, Titchy is still the easiest to set up and have a working X system. The only drawback is the lack of multimedia!)
Again X was a pain to get going. dlj0's script works well and I add rmmod mousedev to it. jpmatrix's page at the wiki is also useful, though his tips for getting X to work for the normal user don't work for me. This is the biggest issue about working with eabi debian for me. I don't like using root as my working user.
I noticed, this time, that using this install, you should partition the drive using fdisk before install and say no to cortez's installer, when it offers to format the drive for you. You end up with one partition and no swap partition, if you just accept everything. This means that you need to set up a swapfile after the install.
I installed xfce because I don't like having to make my own menu entries for installed apps, as you seem to have to in icewm.
I still haven't got very far with multimedia. I did get mplayer to play some flv files. Rather slow motion though. I still haven't got any sound out, but that is just a matter of playing with mixer settings I believe. An avi file that used to play under cacko showed no signs of life.
This locales hitch annoys me too.
Under Titchy I was able to use my usb lan dongle with very little trouble. I've not managed to get it going under EABI yet. Probably forgotten how I set it up!!!
I'm using dillo as my browser and sylpheed as my mail client. I've installed abiword and I think I've installed gnumeric as compiled by ZDevil.
Lots of playing about to do yet. Roll on cortex's tarball.
(sorry about the lack of commas!)
-
1. This locales hitch annoys me too.
2. I'm using dillo as my browser and sylpheed as my mail client.
(1)The problem with locales above seems to have been dealt with by updated packages at the gnuab repositories. I have just installed locales and generated the gb utf locale. I'll find out if it worked, the next time I install an app which tries to use locales.
(2) I managed to install iceweasel. It started to load and almost every time asked me to close it, because an instance was running already. I did close and both instances vanished. I monitored this by running top, in a ssh terminal on the desktop. On the rare occasions I didn't get the close message the app didn't load up as a working one. Still, dillo works. Epiphany as suggested elsewhere appears to install but doesn't run!
Still no progress to report on sound/video and I still can't use X as a non-root user.
-
Been trying to get xdm to work right with XFCE4...but having problems....
Maybe someone can please advise....
I had XFCE4 working fine and rotated correctly when using 3200 in 'laptop mode'...
Then I decided to try and install Xdm per this thread and wiki....
Now I have following problems..
1) I do see xdm login screen, however, when I click enter key after typing in password, screen goes black for a second or two and then login window comes back, instead of going to XFCE4
2) If do try to start XFCE4 from console, it opens but it's rotated for slate mode, not laptop mode. Also, screen does not respond now to stylus taps at all.
Any suggestions how to fix this mess???
Thanks!
-
@Archimark:
Try the trick here (https://www.oesf.org/forum/index.php?showtopic=25701)