Production Pyra photos/videos/thoughts thread


We have JTAG on the Pyra? What controller are you using? I should probably set this up.
According to EvilDragon, it is possible to set up the pin mux so JTAG is present on the left SD slot, and an adaptor has been made that breaks that out. I don't have this adaptor yet though.

I am using an XDS100v2 clone with the uEVM (around £40) and it seems to work well with CCS.
 
Package xserver-xorg-video-armsoc-omap5 is installed?
dpkg -l | grep xserver-xorg-video-armsoc-omap5

I fired up to command line to check this and ... encountered keyboard mapping errors.
Works: Fn + C = [
Works: Fn + V = ]

Fails to produce anything:
Fn + H should be | but results in nothing.
Fn + F should be { but results in nothing.
Fn + G should be } but results in nothing.

There are several other Fn layer combinations that are not resulting in characters showing up in the command line boot.

So, I'd love to run that dpkg command - but...

Who's keeping track of the list?
 
Sorry about that. Can you type > ? You could try
dpkg -l > out
grep xserver-xorg-video-armsoc-omap5 out
rm out
 
Sorry about that. Can you type > ? You could try
dpkg -l > out
grep xserver-xorg-video-armsoc-omap5 out
rm out
The grep of out returns nothing.

To make sure, I re-ran it then did: nano out

out has 1108 lines

I searched it with nano to see if I could find the string 'omap' in it - search wrapped, nothing.

And thank you for including the rm out to clean up. :)
 
OK, then the answer to jakko is package xserver-xorg-video-armsoc-omap5 is not installed
I don't know if it should (looks like yes, but I don't know how it should be)
To install it it would be
apt install xserver-xorg-video-armsoc-omap5
But maybe that also requires configuring files in ways that I haven't tried on this hardware and you'd be better waiting from help from someone else.
 
Then wait I shall.

I suspect that a lot of the issues I'm encountering may stem from disconnects between the version of the OS available for me to download and the version(s) that the devs are currently using. I'm not sure how to, 'catch up'.
 
btw., another alternative woukld be to simply do
Code:
apt-cache policy xserver-xorg-video-armsoc-omap5
so you won't need pipes or special chars
 
  • Like
Reactions: rSl
If I’m honest, this whole X Server thing is way too high for me^^
Do I also have to speak about X Servers, and other high technology stuff as far as I get my Pyra in September??

Can’t I not just get my Pyra, put an Card in and play Tetris??


Gesendet von iPhone mit Tapatalk Pro
 
If I’m honest, this whole X Server thing is way too high for me^^
Do I also have to speak about X Servers, and other high technology stuff as far as I get my Pyra in September??

Can’t I not just get my Pyra, put an Card in and play Tetris??


Gesendet von iPhone mit Tapatalk Pro

The point of me struggling through the process is so that the devs working 'way too high for me' can know what the rest of us will run into.

I just happen to be in a good position to show them an example of 'stumbling in the dark'.
 
Looks like this part is missing:
Ahh - order of operations error then.
I did OS image - got keyboard error - installed Dave's boot to get past keyboard error - then no graphics - to this troubleshooting.

Daves boot file must require that to already be installed. Going to see if I can get it to now.
 
From the instructions on page 7 of the thread, my next step is glxgears.
#glxgears
bash: glxgears: command not found
apt install glxgears
E: Unable to locate package glxgears

So - hmm.
 
Is the keyboard layout in X11 ok again?

If that's the case, there might be different settings for virtual console and for X11. You could check the following things:

Code:
cat /etc/default/keyboard
This one is used in the virtual console.

Code:
gsettings get org.mate.peripherals-keyboard-xkb.kbd layouts
gsettings get org.mate.peripherals-keyboard-xkb.kbd options
gsettings get org.mate.peripherals-keyboard-xkb.kbd model
Those three commands should give information about keyboard layout in MATE.
 
Slide show of the opening screen closed out. Errors in command line menu.

LibGL error: MESA-LOADER: failed to retrieve device information
LibGL error: unable to load driver: omapdrm_dri.so
LibGL error: driver pointer missing
LibGL error: failed to load driver: omapdrm

Getting there - but still missing something.
 
Is the keyboard layout in X11 ok again?

If that's the case, there might be different settings for virtual console and for X11. You could check the following things:

Code:
cat /etc/default/keyboard
This one is used in the virtual console.

Code:
gsettings get org.mate.peripherals-keyboard-xkb.kbd layouts
gsettings get org.mate.peripherals-keyboard-xkb.kbd options
gsettings get org.mate.peripherals-keyboard-xkb.kbd model
Those three commands should give information about keyboard layout in MATE.
The keyboard errors I was getting above where when booting to full-on command line with no graphics. Now that I have graphics and Mate is alive, the keyboard mapping seems to be fine and I can type | {}[] and all sorts of characters. Apparently a good chunk of the Fn layer mappings are handled by the DE?
Post automatically merged:

Did you run the `export` command before running supertux?
export command? Not seeing it in the other post. Any additional syntax for that?
https://pyra-handheld.com/boards/th...eos-thoughts-thread.99139/page-7#post-1676896
Post automatically merged:

Oh - I see it now. Yes I did run that before I loaded the mesa package - need it run again now that I ahve that installed I take it?
 
Back
Top