OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - Arch Linux ARM support => Topic started by: ArchiMark on October 26, 2015, 09:34:20 am
-
X and Window Manager
Just got X running and twm....
But like Dan, twm is opening up sideways.....need to rotate display 90 degrees....
Assumed I need to put something like:
xrandr -o right
in xinitrc file, but it still opens up sideways....
So, either there's more too it or need to put in different location or ........
Just tried fluxbox and it opens up sideways too.....
-
Ok started to mess with this and learned 2 things.
1) You can get the screen to rotate by adding the following file and content as follows:
/usr/share/X11/xorg.conf.d/90-rotate.conf
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']Section "Device"
Identifier "PXA FB"
Driver "fbdev"
Option "Rotate" "CW"
EndSection[/div]
2) It took 22 minutes for XFCE4 to load up, so don't try that
The screen refresh is dog slow as predicted, so work still to be done. Oh, also the touch screen doesn't match up, you can't get to any edges.
-
U 'da Man, Walt!!!!
This is a great step towards getting X and WM working...
XFCE4 is nice....but given our lil' Z's think something lighter like fluxbox, etc, will perform much better...
I'll give X another try later...
What X related files did you install? (ie, Xorg, xinit, xf86-.....)
Thanks!
-
Ok started to mess with this and learned 2 things.
1) You can get the screen to rotate by adding the following file and content as follows:
/usr/share/X11/xorg.conf.d/90-rotate.conf
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']Section "Device"
Identifier "PXA FB"
Driver "fbdev"
Option "Rotate" "CW"
EndSection[/div]
2) It took 22 minutes for XFCE4 to load up, so don't try that
The screen refresh is dog slow as predicted, so work still to be done. Oh, also the touch screen doesn't match up, you can't get to any edges.
Hi TheWalt,
Thanks for testing Arch on your Zaurus.
I would suggest to use a minimal window manager, like dwm or maybe fluxbox. Xfce is overkill on the Z.
Cheers!
-
Got TWM running.....needs a little work on the keymap....but works......
Also, will be great if we can get touchscreen calibration....
Have tried opening some programs from terminal running in TWM, but no go so far....
Tried fluxbox and got it to open....but right now just has bar at the bottom and didn't get it to open with terminal. So, couldn't do anything. Touchscreen calibration was not too bad, off by about 1/4" or 1cm roughly....
-
Got TWM running.....needs a little work on the keymap....but works......
Also, will be great if we can get touchscreen calibration....
Have tried opening some programs from terminal running in TWM, but no go so far....
Tried fluxbox and got it to open....but right now just has bar at the bottom and didn't get it to open with terminal. So, couldn't do anything. Touchscreen calibration was not too bad, off by about 1/4" or 1cm roughly....
I have not looked into calibration of the touchscreen. It may be possible. A look into some OE rootfs that includes Xorg may give some hints.. but this is just a guess.
The most lightweight WM I would consider is dwm, it is really small, simple to use with the keyboard only and does a good job. Used it under Debian on the Z.
At the moment there is no intention to focus on getting X to run proper on the Z under ALARM.
Apps that run in pure console or under FBDEV with SDL, pure Frambuffer or with DirectFB would be less memory hungry, less dependencies and probably "faster" .
Getting Chrome, Firefox or LibreOffice running on your Z is just not going to work
-
Understand your points and Z limitations, daalnroti....
Had no thoughts of running LibreOffice, Firefox, etc.....
But some lightweight browser (relatively speaking...) like midori and being able to run a few light X apps would be nice too....
It would be great to be able to calibrate touchscreen too as it can be very helpful to navigate and click buttons.
So, not thinking grandiose, but would be very helpful to have a simple X apps running properly....
But again, understand that this is not your or danboid's focus....
-
Messing around some today I installed the MATE desktop which although slow works pretty well. Keymap is all wrong and touchscreen is still off of course but it looks nice.
https://wiki.archlinux.org/index.php/MATE (https://wiki.archlinux.org/index.php/MATE)
I tried following these steps to calibrate the touch screen with no luck. In fact I ended up calculating the exact same settings as what comes default.
https://wiki.archlinux.org/index.php/Calibrating_Touchscreen (https://wiki.archlinux.org/index.php/Calibrating_Touchscreen)
UPDATE: I obviously do not have the right numbers for the formula but after some random trial and error this gets REAL close. If maybe we can get the right info this can be corrected properly. Just run this in terminal after X is open to test.
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
My hope was to find the settings in a working debain or bsd install but debian seems to use a TSLIB that is not available in arch for its calibrations.
-
Very cool, Walt!.....
Keep up the good work.....
Will do more testing if I get some time......
-
Messing around some today I installed the MATE desktop which although slow works pretty well. Keymap is all wrong and touchscreen is still off of course but it looks nice.
https://wiki.archlinux.org/index.php/MATE (https://wiki.archlinux.org/index.php/MATE)
I tried following these steps to calibrate the touch screen with no luck. In fact I ended up calculating the exact same settings as what comes default.
https://wiki.archlinux.org/index.php/Calibrating_Touchscreen (https://wiki.archlinux.org/index.php/Calibrating_Touchscreen)
UPDATE: I obviously do not have the right numbers for the formula but after some random trial and error this gets REAL close. If maybe we can get the right info this can be corrected properly. Just run this in terminal after X is open to test.
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
My hope was to find the settings in a working debain or bsd install but debian seems to use a TSLIB that is not available in arch for its calibrations.
Keymap : Have a look at this borzoi xmodmap_us file that I copied of pdaxrom. Not sure it does work with Xorg but it may be a start.
! 'Fn' key setup for c700
!
clear Mod1
clear Mod2
clear Mod3
clear Mod4
clear Mod5
keycode 10 = 1 exclam F1 F1
keycode 11 = 2 quotedbl F2 F2
keycode 12 = 3 numbersign F3 F3
keycode 13 = 4 dollar F4 F4
keycode 14 = 5 percent F5 F5
keycode 15 = 6 ampersand F6 F6
keycode 16 = 7 apostrophe F7 F7
keycode 17 = 8 parenleft F8 F8
keycode 18 = 9 parenright F9 F9
keycode 19 = 0 asciitilde F10 F10
keycode 24 = q Q aring Aring
keycode 25 = w W asciicircum asciicircum
keycode 26 = e E equal equal
keycode 27 = r R plus plus
keycode 28 = t T bracketleft bracketleft
keycode 29 = y Y bracketright bracketright
keycode 30 = u U braceleft braceleft
keycode 31 = i I braceright braceright
keycode 32 = o O oslash Ooblique
keycode 33 = p P sterling
keycode 38 = a A ae AE
keycode 39 = s S EuroSign
keycode 40 = d D grave grave
keycode 41 = f F backslash backslash
keycode 42 = g G semicolon semicolon
keycode 43 = h H colon colon
keycode 44 = j J asterisk asterisk
keycode 45 = k K yen
keycode 46 = l L bar bar
keycode 50 = Shift_L
keycode 52 = z Z
keycode 53 = x X
keycode 54 = c C
keycode 55 = v V
keycode 56 = b B underscore underscore
keycode 57 = n N
keycode 58 = m M
!keycode 105 = grave grave
keycode 20 = minus underscore at at
keycode 59 = slash comma less less
keycode 60 = period question greater greater
keycode 69 = Mode_switch
! Cursor
keycode 198 = Up Up Prior Prior
keycode 111 = Up Up Prior Prior
keycode 116 = Down Down Next Next
keycode 204 = Down Down Next Next
keycode 113 = Left Left Home Home
keycode 200 = Left Left Home Home
keycode 114 = Right Right End End
keycode 201 = Right Right End End
keycode 22 = BackSpace BackSpace Delete Delete
! pdaXrom silkscreen
keycode 87 = XF86Launch0
!House
keycode 89 = XF86Launch1
!Mail
keycode 84 = XF86Launch2
!People
keycode 79 = XF86Launch3
!List
keycode 81 = XF86Launch4
!Book
! R-Shift
keycode 62 = Shift_R
! Menu
!keycode 96 = XF86Start
!keycode 67 = XF86LaunchA
!keycode 68 = XF86LaunchB
!keycode 76 = XF86LaunchC
!keycode 107 = XF86LaunchD
! side buttons
!keycode 117 = XF86PowerDown
keycode 71 = Return
keycode 95 = Return
keycode 72 = Escape
keycode 70 = Escape
! CE-RH1 Remote
!keycode 104 = XF86AudioRaiseVolume
!keycode 105 = XF86AudioLowerVolume
!keycode 106 = XF86AudioNext
!keycode 107 = XF86AudioPrev
!keycode 108 = XF86AudioStop
!keycode 109 = XF86AudioPlay
! This is the screen swivel sensor
! keycode 110 = XF86RotateWindows
clear Lock
! remove Lock = Tab
keycode 23 = Tab Tab Caps_Lock Caps_Lock
! add Lock = Caps_Lock
add mod1 = Alt_L Alt_L Alt_L
add mod2 = Mode_switch
tslib could be compiled but then you may need to compile X against it. If we find a way to get the touchscreen calibrated without tslib, that would be awesome.
I think I still have some tslib calibration files for VGA and QVGA somewhere, maybe these coordinates are similar to what the xinput parameters are, this might help.
pointercal-qvga :
-149 -4388 16921896 5942 -14 -957028 65536 6 536 36
pointercal-vga:
30 -8875 33714080 12031 -32 -2007552 65536
Cheers!
-
Have you not had chance to try out daal's suggestions yet Archimark?
Let us know how you get on please!
-
Not yet, danboid.....
Was very busy at work the past week or so....
but should have some time this week....with holiday time here later this week....
Maybe Walt can give it a try too.....
-
Tried installing Mate....
Getting error:
( 3/35) installing caja
Killed
UPDATE
Managed to get caja installed.....
So, moving forward with Mate install now....
-
Some progress.....
Got Mate installed and after about 10 minutes it was fully opened and running.....Yeah!.....
Bad thing like you say is that calibration is off, so, I can't quite get the cursor arrow to reach the top of screen to open the menus......
Haven't been able to find a way to use keyboard to open menu either, have tried various keys and key combos....so, can't open terminal to use and quit Mate......
Is there a way to access menus using keys?
Tried using Fn + Left & Right Arrow to get back to console, but no go.......
Maybe we need to think about lighter display manager like fluxbox or ?
UPDATE
Finally, found a key combo that got me back to a login in console......
Ctl + Alt + Fn + 1
-
After getting back to console with new login (tty3).....
Tried to xinput set-prop as noted in Walt's post above....
Got message something like : Cannot connect to X server.....
-
Just tried to have Mate open with terminal open....by doing the following in .xinitrc file.
For mate-terminal, I changed the line for xterm to mate-terminal that was already there for when using twm.
exec mate-session &
mate-terminal -geometry 80x66+0+0 -name login
But after I do startx, screen goes light color and then soon comes back to console....
I get error message:
Failed to parse arguments: Unknown option -geometry
Any suggestions?
-
Decided to give LXDE a go.....
Had it running OK on my little Nokia N900 with ALARM on it a few years ago...
Good news is that LXDE opens up OK in about 7 minutes.....so, faster than MATE and XFCE.....
Touchscreen works OK and calibration is pretty close...off by about 1/8".....
Bad news right now is that it didn't auto open LXTerminal as I'd wanted....
I did the following in ~/.config/lxsession/LXDE/autostart after the existing lines of text in file:
@lxterminal
But it didn't open up.....
So, just have a nice looking LXDE background image on display with a little black cursor arrow......
No other menu bars, panels, etc, visible......
Hmmmm............
But hopefully, this one has promise with a bit of work.....
UPDATE
Tried various keys.....
When I press the Home button on the keyboard, I get a little window open up on the display....
Openbox at heading of window....
Error message about can't open screenshot.....something like that...
Fortunately, can close the window since stylus calibration is not that far off....
But still no panel bar at bottom of screen nor able to open terminal.....
-
Progress in some respects......
Got lxdm working....instead of opening LXDE with startx.......
Got the login screen......was able to select which user and login with password OK.....
Now, when it opened up to desktop I have the bottom panel with the little applets (start menu button, file manager icon, desktops, network, RAM usage visual (all green....), time, monitor?, in it showing......
So that's the good news....
Bad news is that since I don't have terminal open, I can't really do anything as I can't quite get cursor on top of the start menu button in panel at lower left of display...
Took some pics....when I get time, I'll post them here.
Not sure what's going on with LXDE as I the wiki page nor the forum page seems to be working.....so, have found it hard to find info regarding setting up configuration using console and working directly with files. Most LXDE related pages I've found assume you have it running such that you can open up the preferences window and make your selections that way....
Will keep trying......but if anyone has any tips or suggestions, that would be great...
-
Sorry been busy with holiday and being a little under the weather.
I have a terminal start with MATE by changing the end of /etc/X11/xinit/xinitrc
# twm &
# xclock -geometry 50x50-1+1 &
# xterm -geometry 80x50+494+51 &
# xterm -geometry 80x20+494-0 &
# exec xterm -geometry 80x66+0+0 -name login
exec mate-session &
exec xterm -name login
Then after it all loads (it does take some time) run the following in that terminal
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
You are right though, really need something lighter ... fluxbox is on my 'to look at' list.
-
Ok, fluxbox runs pretty quick and getting a terminal open is easy as adding "xterm &" to the list of programs in ~/.fluxbox/startup
Can't get the right click to bring up a menu so will have to look into that, but the calibration seems close like before. Might try a few other lightweights tomorrow.
-
Sorry been busy with holiday and being a little under the weather.
Hope you're starting to feel better now.....
I have a terminal start with MATE by changing the end of /etc/X11/xinit/xinitrc
# twm &
# xclock -geometry 50x50-1+1 &
# xterm -geometry 80x50+494+51 &
# xterm -geometry 80x20+494-0 &
# exec xterm -geometry 80x66+0+0 -name login
exec mate-session &
exec xterm -name login
Then after it all loads (it does take some time) run the following in that terminal
Thanks for the info....
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
Thanks....
You are right though, really need something lighter ... fluxbox is on my 'to look at' list.
Ok, fluxbox runs pretty quick and getting a terminal open is easy as adding "xterm &" to the list of programs in ~/.fluxbox/startup
Can't get the right click to bring up a menu so will have to look into that, but the calibration seems close like before. Might try a few other lightweights tomorrow.
Sounds good!.....
-
Got fluxbox opening with xterm now......
Besides touchscreen calibration and mouse click recognition issues, the keyboard map needs work.
I count 6 keys that are in the numbers row that are accessed with Shift key that are off.
Then the 2 keys to the right of the space bar are off when Shift key used.
Last, the characters usually accessed by pressing the Fn + other keys do not work at all.
From reading Arch wiki and fluxbox pages, I'm not sure which is right way to go about fixing keymap issues; XKB or xmodmap (as daalnroti mentions in his post #10 above...) or ?
Since I can't seem to access the quote marks " character, not sure how to enter the 'xinput set-prop.....' command suggested....
Think fluxbox would be pretty good wm if we get the issues above sorted out.....
opens pretty quickly, runs pretty well, and looks OK on display....at least I think so....
-
Ya I had to make a executable shell script to run with that command while SSH into the Z so I could type the " forgot to mention that
-
Ya I had to make a executable shell script to run with that command while SSH into the Z so I could type the " forgot to mention that
I see.......thanks for letting me know....
-
Ya I had to make a executable shell script to run with that command while SSH into the Z so I could type the " forgot to mention that
Sorry to be not much of help but you should try to get the keymap working first. This might be trivial but I have not looked into it so far.
Fluxbox may be ok, I would suggest to use dwm or awesome to be lightweight as possible so apps have still a bit of mem to work with.
-
Using the keymap I posted before and following this guide linked below, you guys may have some luck getting Xorg keyboard going.
If you do, please post a guide here, so others can follow. Thanks.
https://wiki.archlinux.org/index.php/Keyboa...uration_in_Xorg (https://wiki.archlinux.org/index.php/Keyboard_configuration_in_Xorg)
Cheers!
-
Agree with your points about getting keymap working, daalnroti......
And when I am able to have a block of time to focus on this for a while, I will see if I can make any progress with it.
Problem lately is been lack of time, due to stresses at work and at home.....
But maybe will be some more time in the next week or so....
-
Agree with your points about getting keymap working, daalnroti......
And when I am able to have a block of time to focus on this for a while, I will see if I can make any progress with it.
Problem lately is been lack of time, due to stresses at work and at home.....
But maybe will be some more time in the next week or so....
No worries mate, Stress at home at work.. well I know how that is
Keymap :
- make sure you install xmodmap (xorg-xmodmap)
- then create a file called .Xmodmap in your ~ (home) folder. (attached to this post, ungzip before use)
- modify your .xinitrc in your home folder to look like this (example)
~/.xinitrc
if [ -s ~/.Xmodmap ]; then
xmodmap ~/.Xmodmap
fi
exec xterm
- start Xorg via startx and you will get a xterm with working keymap.
Please do some testing etc, I just got it going until here. Touchscreen, I may look into at a later stage.
Cheers!
-
Thanks for the headstart on this, daalnroti.....
Will give it a go as soon as I can....
-
Thanks for the headstart on this, daalnroti.....
Will give it a go as soon as I can....
No worries ArchiMark.
As expected it is slow. Even just running xterm takes almost 50% of memory and scrolling is slow too, but I guess it has always been like that.
Well, pdaXrom used a minimal X11, not Xorg, if I remember correctly, that was a bit more lightweight. The bottleneck is the software rotation to
portrait mode...
-
Agree with your points about getting keymap working, daalnroti......
And when I am able to have a block of time to focus on this for a while, I will see if I can make any progress with it.
Problem lately is been lack of time, due to stresses at work and at home.....
But maybe will be some more time in the next week or so....
No worries mate, Stress at home at work.. well I know how that is
Keymap :
- make sure you install xmodmap (xorg-xmodmap)
- then create a file called .Xmodmap in your ~ (home) folder. (attached to this post, ungzip before use)
- modify your .xinitrc in your home folder to look like this (example)
~/.xinitrc
if [ -s ~/.Xmodmap ]; then
xmodmap ~/.Xmodmap
fi
exec xterm
- start Xorg via startx and you will get a xterm with working keymap.
Please do some testing etc, I just got it going until here. Touchscreen, I may look into at a later stage.
Cheers!
Hi,
Finally getting around to try what you suggested....I know, a long time......
Would like to minimize chances of screwing things up....so, would appreciate input.....
Copied .Xmodmap to my home directory.
Now, opened .xinitrc file to edit as you suggest. Here's what I see:
#!/bin/sh
userresources=$HOME//Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
#merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f "$userresources" ]; then
xrdb -merge "$userresources"
fi
if [ -f "usermodmap" ]; then
xmodmap "$usermodmap"
fi
#start some nice programs
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/?*.sh; do
[ -x "$f" ] && . "$f"
done
unset f
fi
Should I just add your text in to the section about keymaps or do I delete any of the existing text and then add your text?
Thanks.
-
OK, decided to be brave and did the following:
- Inserted your text
- Commented out the section in .xinitrc:
if [ -f "usermodmap" ]; then
xmodmap "$usermodmap"
fi
So far, works great now!
-
More good news.....
Was able to get Fluxbox Root Menu to work by modifying the 'keys' file in ~/.fluxbox.....
Makes Fluxbox much more usable.....
As you can see from pics below, I was also able to easily access Fluxbox menus items and changed theme for fun....
Next thing that would make things better is to get screen calibrated for stylus use.
Any input on calibrating?
-
More good news.....
Was able to get Fluxbox Root Menu to work by modifying the 'keys' file in ~/.fluxbox.....
Makes Fluxbox much more usable.....
As you can see from pics below, I was also able to easily access Fluxbox menus items and changed theme for fun....
Next thing that would make things better is to get screen calibrated for stylus use.
Any input on calibrating?
Hi Mark,
you did the right thing. Keymap works fine ?
In regards to touchscreen, you will need tslib installed with Zaurus support.
There is conf file that needs to be adjusted and there used to be a calibration tool.
Look for ts_calibrate after installing.
I have not played with trouchscreen in X using ALARM yet.
Cheers!
-
More good news.....
Was able to get Fluxbox Root Menu to work by modifying the 'keys' file in ~/.fluxbox.....
Makes Fluxbox much more usable.....
As you can see from pics below, I was also able to easily access Fluxbox menus items and changed theme for fun....
Next thing that would make things better is to get screen calibrated for stylus use.
Any input on calibrating?
Hi Mark,
you did the right thing. Keymap works fine ?
In regards to touchscreen, you will need tslib installed with Zaurus support.
There is conf file that needs to be adjusted and there used to be a calibration tool.
Look for ts_calibrate after installing.
I have not played with trouchscreen in X using ALARM yet.
Cheers!
So far, keymap works fine......
Just installed tslib.....
Need to locate conf file and then calibration tool....
Thanks.
-
Until we figure out ts_calibrate.....
I copied Walt's suggestion from an earlier post on this thread
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
That works pretty well....at least close enough that I can reach things at top or bottom of display now.
-
Until we figure out ts_calibrate.....
I copied Walt's suggestion from an earlier post on this thread
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
That works pretty well....at least close enough that I can reach things at top or bottom of display now.
You may be able to tweak the xinput command to fit your touchscreen perfectly (calibrate) by adjusting the matrix values. Tslib calibration may be outdated.
-
Until we figure out ts_calibrate.....
I copied Walt's suggestion from an earlier post on this thread
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
That works pretty well....at least close enough that I can reach things at top or bottom of display now.
You may be able to tweak the xinput command to fit your touchscreen perfectly (calibrate) by adjusting the matrix values. Tslib calibration may be outdated.
Thanks.......
Other thing is to be able to put this command in a config file such that it 'sticks' with each boot up...as opposed to entering this each time one starts the Zaurus.
-
Until we figure out ts_calibrate.....
I copied Walt's suggestion from an earlier post on this thread
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
That works pretty well....at least close enough that I can reach things at top or bottom of display now.
You may be able to tweak the xinput command to fit your touchscreen perfectly (calibrate) by adjusting the matrix values. Tslib calibration may be outdated.
Thanks.......
Other thing is to be able to put this command in a config file such that it 'sticks' with each boot up...as opposed to entering this each time one starts the Zaurus.
Yes, you can add
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
to your ~/.xinitrc
-
Until we figure out ts_calibrate.....
I copied Walt's suggestion from an earlier post on this thread
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
That works pretty well....at least close enough that I can reach things at top or bottom of display now.
You may be able to tweak the xinput command to fit your touchscreen perfectly (calibrate) by adjusting the matrix values. Tslib calibration may be outdated.
Thanks.......
Other thing is to be able to put this command in a config file such that it 'sticks' with each boot up...as opposed to entering this each time one starts the Zaurus.
Yes, you can add
xinput set-prop "ADS7846 Touchscreen" --type=float "Coordinate Transformation Matrix" 1.2 0 -.0625 0 1.18 -.0834 0 0 1
to your ~/.xinitrc
Thanks, will do.....
-
Ok started to mess with this and learned 2 things.
1) You can get the screen to rotate by adding the following file and content as follows:
/usr/share/X11/xorg.conf.d/90-rotate.conf
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']Section "Device"
Identifier "PXA FB"
Driver "fbdev"
Option "Rotate" "CW"
EndSection[/div]
2) It took 22 minutes for XFCE4 to load up, so don't try that
The screen refresh is dog slow as predicted, so work still to be done. Oh, also the touch screen doesn't match up, you can't get to any edges.
It's not working on my SL-C3200 for some reason. X never starts, only black screen
An I have this in log file:
[ 591.417] (II) LoadModule: "fbdev"
[ 591.476] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 591.508] (II) Module fbdev: vendor="X.Org Foundation"
[ 591.509] compiled for 1.20.0, module version = 0.4.4
[ 591.509] Module class: X.Org Video Driver
[ 591.509] ABI class: X.Org Video Driver, version 24.0
[ 591.510] (II) FBDEV: driver for framebuffer: fbdev
[ 591.512] (WW) Falling back to old probe method for fbdev
[ 591.513] (II) Loading sub module "fbdevhw"
[ 591.513] (II) LoadModule: "fbdevhw"
[ 591.516] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 591.535] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 591.535] compiled for 1.20.0, module version = 0.0.2
[ 591.536] ABI class: X.Org Video Driver, version 24.0
[ 591.537] (II) FBDEV(0): using default device
[ 591.538] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 591.539] (II) FBDEV(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 16/16
[ 591.540] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
[ 591.541] (==) FBDEV(0): RGB weight 565
[ 591.542] (==) FBDEV(0): Default visual is TrueColor
[ 591.542] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 591.543] (II) FBDEV(0): hardware: PXA (video memory: 600kB)
[ 591.544] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 591.544] (**) FBDEV(0): Option "Rotate" "CW"
[ 591.545] (**) FBDEV(0): rotating screen clockwise
[ 591.546] (II) FBDEV(0): checking modes against framebuffer device...
[ 591.546] (II) FBDEV(0): checking modes against monitor...
[ 591.547] (II) FBDEV(0): Virtual size is 480x640 (pitch 480)
[ 591.548] (**) FBDEV(0): Built-in mode "current": 52.0 MHz, 75.3 kHz, 116.9 Hz
[ 591.548] (II) FBDEV(0): Modeline "current"x0.0 52.00 480 605 645 691 640 640 643 644 -hsync -vsync -csync (75.3 kHz b)
[ 591.549] (==) FBDEV(0): DPI set to (96, 96)
[ 591.550] (II) Loading sub module "fb"
[ 591.551] (II) LoadModule: "fb"
[ 591.553] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 591.573] (II) Module fb: vendor="X.Org Foundation"
[ 591.573] compiled for 1.20.0, module version = 1.0.0
[ 591.576] ABI class: X.Org ANSI C Emulation, version 0.4
[ 591.576] (**) FBDEV(0): using shadow framebuffer
[ 591.576] (II) Loading sub module "shadow"
[ 591.577] (II) LoadModule: "shadow"
[ 591.581] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 591.618] (II) Module shadow: vendor="X.Org Foundation"
[ 591.619] compiled for 1.20.0, module version = 1.1.0
[ 591.619] ABI class: X.Org ANSI C Emulation, version 0.4
[ 591.627] (II) FBDEV(0): display rotated; disabling DGA
[ 591.628] (II) FBDEV(0): using driver rotation; disabling XRandRAnd I can't kill X because there is no X processes running. This is odd.
-
Hi Marzanna,
what window-manager or desktop-environment did you install ?
Keep in mind the Zaurus is very limited on RAM and current full Xorg is painfully slow, almost unusable.
I would recommend to look into "dwm", "i3wm" and maybe "fluxbox".
Check also the ArchLinux Wiki on how to install these. Some tweaking in the xorg.conf may be needed.
https://wiki.archlinux.org/index.php/I3wm (https://wiki.archlinux.org/index.php/I3wm)
Alternatively, look into tmux, links and other console programs. Mutt for email etc.
This way you get full keyboard controllable applications that run smooth.
Cheers,
Greguu
Ok started to mess with this and learned 2 things.
1) You can get the screen to rotate by adding the following file and content as follows:
/usr/share/X11/xorg.conf.d/90-rotate.conf
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']Section "Device"
Identifier "PXA FB"
Driver "fbdev"
Option "Rotate" "CW"
EndSection[/div]
2) It took 22 minutes for XFCE4 to load up, so don't try that
The screen refresh is dog slow as predicted, so work still to be done. Oh, also the touch screen doesn't match up, you can't get to any edges.
It's not working on my SL-C3200 for some reason. X never starts, only black screen
An I have this in log file:
[ 591.417] (II) LoadModule: "fbdev"
[ 591.476] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 591.508] (II) Module fbdev: vendor="X.Org Foundation"
[ 591.509] compiled for 1.20.0, module version = 0.4.4
[ 591.509] Module class: X.Org Video Driver
[ 591.509] ABI class: X.Org Video Driver, version 24.0
[ 591.510] (II) FBDEV: driver for framebuffer: fbdev
[ 591.512] (WW) Falling back to old probe method for fbdev
[ 591.513] (II) Loading sub module "fbdevhw"
[ 591.513] (II) LoadModule: "fbdevhw"
[ 591.516] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 591.535] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 591.535] compiled for 1.20.0, module version = 0.0.2
[ 591.536] ABI class: X.Org Video Driver, version 24.0
[ 591.537] (II) FBDEV(0): using default device
[ 591.538] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 591.539] (II) FBDEV(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 16/16
[ 591.540] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
[ 591.541] (==) FBDEV(0): RGB weight 565
[ 591.542] (==) FBDEV(0): Default visual is TrueColor
[ 591.542] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 591.543] (II) FBDEV(0): hardware: PXA (video memory: 600kB)
[ 591.544] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 591.544] (**) FBDEV(0): Option "Rotate" "CW"
[ 591.545] (**) FBDEV(0): rotating screen clockwise
[ 591.546] (II) FBDEV(0): checking modes against framebuffer device...
[ 591.546] (II) FBDEV(0): checking modes against monitor...
[ 591.547] (II) FBDEV(0): Virtual size is 480x640 (pitch 480)
[ 591.548] (**) FBDEV(0): Built-in mode "current": 52.0 MHz, 75.3 kHz, 116.9 Hz
[ 591.548] (II) FBDEV(0): Modeline "current"x0.0 52.00 480 605 645 691 640 640 643 644 -hsync -vsync -csync (75.3 kHz b)
[ 591.549] (==) FBDEV(0): DPI set to (96, 96)
[ 591.550] (II) Loading sub module "fb"
[ 591.551] (II) LoadModule: "fb"
[ 591.553] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 591.573] (II) Module fb: vendor="X.Org Foundation"
[ 591.573] compiled for 1.20.0, module version = 1.0.0
[ 591.576] ABI class: X.Org ANSI C Emulation, version 0.4
[ 591.576] (**) FBDEV(0): using shadow framebuffer
[ 591.576] (II) Loading sub module "shadow"
[ 591.577] (II) LoadModule: "shadow"
[ 591.581] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 591.618] (II) Module shadow: vendor="X.Org Foundation"
[ 591.619] compiled for 1.20.0, module version = 1.1.0
[ 591.619] ABI class: X.Org ANSI C Emulation, version 0.4
[ 591.627] (II) FBDEV(0): display rotated; disabling DGA
[ 591.628] (II) FBDEV(0): using driver rotation; disabling XRandRAnd I can't kill X because there is no X processes running. This is odd.
-
Someone on #zaurus has reported that the latest version of ratpoison runs well too, although under pdaxrom.
Varti
-
what window-manager or desktop-environment did you install ?
xfce4, but I quickly realized that it was a mistake.
Alternatively, look into tmux, links and other console programs. Mutt for email etc.
This way you get full keyboard controllable applications that run smooth.
Is there a way to show battery level and network status in console? Maybe in some overlay or shell prompt?
-
what window-manager or desktop-environment did you install ?
xfce4, but I quickly realized that it was a mistake.
Alternatively, look into tmux, links and other console programs. Mutt for email etc.
This way you get full keyboard controllable applications that run smooth.
Is there a way to show battery level and network status in console? Maybe in some overlay or shell prompt?
There are "battery" and "network status" plug-ins for tmux, but I have not tried them on the Zaurus yet.
https://github.com/tmux-plugins (https://github.com/tmux-plugins)
-
Hi there,
hope some people are still reading this section.
Per accident I discovered the section about Arch Linux on the zaurus. In the past I had been through nearly all available ROMs for the zaurus like, Cacko, pdaxrom and so on.
Because I really loved this little device (I have an CL3100) I fetched the zaurus from my box with long not used gadgets and I followed the instructions to install zalarm. So far had success. The basic system is working. Thanks to all involved.
I really like to try X11 on the device. But I am stuck.
What I did:
I installed the following packages:
xorg-server
xorg-apps
xorg-init
xorg-xmodmap
xf86-video-fbdev
lxde
I added the user to the group video
and took the Xmodmap-File from this thread and modified .xinitrc like described above including the start of lxde.
When I type startx the screen seems to get in graphical mode for a short while, the machine is working on the harddisk for a little while, the screen stays black and then finally the command line comes back, saying XServer shut down normally. No errors in Xorg.0.log shown.
Any ideas what is missing or has to be changed?
Any hint would be great.
Thanks in advance
Detlev
-
Hi there,
hope some people are still reading this section.
Per accident I discovered the section about Arch Linux on the zaurus. In the past I had been through nearly all available ROMs for the zaurus like, Cacko, pdaxrom and so on.
Because I really loved this little device (I have an CL3100) I fetched the zaurus from my box with long not used gadgets and I followed the instructions to install zalarm. So far had success. The basic system is working. Thanks to all involved.
I really like to try X11 on the device. But I am stuck.
What I did:
I installed the following packages:
xorg-server
xorg-apps
xorg-init
xorg-xmodmap
xf86-video-fbdev
lxde
I added the user to the group video
and took the Xmodmap-File from this thread and modified .xinitrc like described above including the start of lxde.
When I type startx the screen seems to get in graphical mode for a short while, the machine is working on the harddisk for a little while, the screen stays black and then finally the command line comes back, saying XServer shut down normally. No errors in Xorg.0.log shown.
Any ideas what is missing or has to be changed?
Any hint would be great.
Thanks in advance
Detlev
Hi,
went through the whole installation. It was my fault - lxde was not fully installed.
I now have the LXDE-Desktop. Great!
Will keep on playing with the system ...
Detlev
-
hope some people are still reading this section.
Hi DReymann and welcome back on OESF. Yes, there are still some of us following the Zaurus scene
I'm glad you have solved the issues with LXDE. I have never tried to run X11 on my Z, though it has been reported to be running slowly. If it will run slowly on your system too, you might give Void Linux a try, it reportedly runs faster and uses less memory than Arch:
https://www.oesf.org/forum/index.php?showforum=205 (https://www.oesf.org/forum/index.php?showforum=205)
Varti
-
Note: Void for Zaurus (voidz) currently has no X11 support. This is still WIP. Arch however runs LXDE, Fluxbox or i3wm.
DReymann: What Arch rootfs did you use ? I am curious if the current rootfs from Feb 2018 still allows a seamless upgrade via pacman or if you experienced any issues. I have not updated it in a while.
-
It's been over 2 years since my posts on the prior page.
However, as I recall, even though (as you can read) I got things working, the Zaurus was painfully slow with the setup as there is not enough RAM in the Zaurus for this to run effectively.
It's too bad, as I would have kept the Zaurus otherwise.
-
It's been over 2 years since my posts on the prior page.
However, as I recall, even though (as you can read) I got things working, the Zaurus was painfully slow with the setup as there is not enough RAM in the Zaurus for this to run effectively.
It's too bad, as I would have kept the Zaurus otherwise.
Yes, ArchiMark you are right. There is not enough free RAM on the Zaurus to run any major Xorg apps on Arch nowadays. However, if you trim Archs RAM usage down and run i3wm instead of LXDE, you may be able to get some stuff going. Chromium or Firefox are out of the question and so are most large Xorg applications, but some stuff may actually work ok, such as links2, netsurf, abiword, etc..
I hope to get voidz going using an optimized kdrive server (instead of full Xorg) and maybe also by resorting to use zram, in the near future.
The Zaurus is still very usable in console mode only - once you get tmux going and get familiar with the keyboard shortcuts of the various console applications.
-
Note: Void for Zaurus (voidz) currently has no X11 support. This is still WIP. Arch however runs LXDE, Fluxbox or i3wm.
Sorry, I forgot about this, thanks for clearing it out.
Varti