04-26-2019, 04:32 AM
A follow-up to my previous message:
The pulseaudio issue is reproducible on my system (all pine components including emmc, pcie-sata, wfif/bt board, nas box, and an HDMI monitor without sound => using headphone jack). After apt remove pulseaudio as root, and login to desktop as rock, I can then sudo apt install pulseaudio, and hey presto it works, I even have sound -e.g. youtube (first time for this rockpro)!
However if I then logout and then try to login again as rock, it crashes again. I can restart, login as root, apt remove pulseaudio, and now again can login as rock … So the crash is related to the process just after login, probably solvable.
A bigger issue is that I still can’t get wifi and BT to work usefully - they can see other devices, and vice-versa, and attempt connecting / pairing, but never succeed to establish a useable connection.
So I went back to ayufan’s latest mate-desktop build (0.8.0rc10) and there the same wifi does connect well - so I know the hardware works and is setup OK. However on that build trying to mount the sata drives crashes everything (same drives working ok on this build), and there are other stability issues (will write in other thread).
Two easily-fixable issues that make MrFixIt build inconvenient for experimenting (that are good in Ayufan’s build) :
- ssh should be easy to use on startup with a documented login name (I can connect by searching for the IP number on the router, but this varies and is a hassle).
- a wide range of screen resolutions should be supported and work on startup, for example for a 1280x1024 monitor (yes it’s old, but don’t expect all users to dedicate a new monitor costing more than the board). I can make this resolution work by using xrandr in terminal, but the option vanishes on each reboot.
I wish that you guys could somehow join forces and implement everything together, this must be possible since each feature has worked, just never in one system. Meanwhile swapping is tedious as I have only one emmc, have to keep re-flashing. For long term application, we need to build on a stable system that can be updated without re-flashing the whole image. So in general, while mate is nice, I also wonder about the wisdom of relying on 32-bit armhf - isn’t this likely to become a dead-end route for future updates?
The pulseaudio issue is reproducible on my system (all pine components including emmc, pcie-sata, wfif/bt board, nas box, and an HDMI monitor without sound => using headphone jack). After apt remove pulseaudio as root, and login to desktop as rock, I can then sudo apt install pulseaudio, and hey presto it works, I even have sound -e.g. youtube (first time for this rockpro)!
However if I then logout and then try to login again as rock, it crashes again. I can restart, login as root, apt remove pulseaudio, and now again can login as rock … So the crash is related to the process just after login, probably solvable.
A bigger issue is that I still can’t get wifi and BT to work usefully - they can see other devices, and vice-versa, and attempt connecting / pairing, but never succeed to establish a useable connection.
So I went back to ayufan’s latest mate-desktop build (0.8.0rc10) and there the same wifi does connect well - so I know the hardware works and is setup OK. However on that build trying to mount the sata drives crashes everything (same drives working ok on this build), and there are other stability issues (will write in other thread).
Two easily-fixable issues that make MrFixIt build inconvenient for experimenting (that are good in Ayufan’s build) :
- ssh should be easy to use on startup with a documented login name (I can connect by searching for the IP number on the router, but this varies and is a hassle).
- a wide range of screen resolutions should be supported and work on startup, for example for a 1280x1024 monitor (yes it’s old, but don’t expect all users to dedicate a new monitor costing more than the board). I can make this resolution work by using xrandr in terminal, but the option vanishes on each reboot.
I wish that you guys could somehow join forces and implement everything together, this must be possible since each feature has worked, just never in one system. Meanwhile swapping is tedious as I have only one emmc, have to keep re-flashing. For long term application, we need to build on a stable system that can be updated without re-flashing the whole image. So in general, while mate is nice, I also wonder about the wisdom of relying on 32-bit armhf - isn’t this likely to become a dead-end route for future updates?
