Hi all,
@greguu: Thank you for your work!
I have installed ALARM on my C1000 following the installation howto yesterday. Here are some observations:
Installing the 2.6-kexecboot firmware worked like a charm.
I used the most recent rootfs and replaced the kernel with the slightly updated/fixed one provided by greguu (file date of zImage: 20.02.2018 vs. 11.02.2018)
Rootfs: https://github.com/greguu/alarm-zaurus-c3x00/releases (Attention: the release on the top is NOT the most recent one. Scroll down.)
Kernel: https://github.com/greguu/linux-4.14.18-c3x00/releasesI made the following changes to the rootfs.
All paths are absolute paths, so you need to adjust them if you are changing the rootfs on a SD card mounted on your main computer.Create /etc/dropbear/ directoryThis directory is missing in the rootfs which causes dropbear to drop any SSH connection requests.
mkdir /etc/dropbear/
Swap file instead of partition (might have drawbacks).
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']dd if=/dev/zero of=/swapfile bs=1024 count=400000
mkswap /swapfile
swapon /swapfile
[/div]
in /etc/sysctl.d/zaurus:
vm.swappiness=10
in /etc/fstab (i also changed rootfs type to ext3 here):
/swapfile none swap sw 0 0
Upgrading ArchThe following was necessary to upgrade Arch (I used a CF network card to connect to the internet):
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']pacman -Syu
pacman-key --init
pacman-key --populate
pacman-key --refresh
pacman -S vim # etc...[/div]
Backlight problemThe backlight on my Akita can not be controlled by the kernel:
corgi-lcd spi2.1: failed to request GPIO207 for backlight_on
There are two gpiochips available in /sys/class/gpio/:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']root: ~ $ cat /sys/class/gpio/gpiochip0/label
gpio-pxa
root: ~ $ cat /sys/class/gpio/gpiochip0/base
0
root: ~ $ cat /sys/class/gpio/gpiochip0/ngpio
121
root: ~ $ cat /sys/class/gpio/gpiochip192/label
sharp-scoop.0
root: ~ $ cat /sys/class/gpio/gpiochip192/base
192
root: ~ $ cat /sys/class/gpio/gpiochip192/ngpio
12
[/div]
So, no GPIO 207 seems to be available. I'm not sure about the mapping.
As backlight control does not work, the backlight will not switch off on suspend.
I would appreciate any hints on how to fix this issue.
USB device/gadget modeThe Zaurus boots with USB host mode, i.e. one may attach USB devices with a OTG adapter cable.
I would have liked to activate USB device mode but did not get it to work yet.
It is possible to load the pxa27x_udc and g_ether modules. However, these do not automatically switch the USB port to device mode. IIRC, one might need to toggle some GPIO pins?
Power managementThe MAX1111 ADC seems to report battery voltage / temp and charging voltage.
One can read out values via
/sys/class/hwmon/hwmon0/device/in0_input
(etc.).
However, an error message appears in dmesg:
max1111 spi2.2: spi_sync failed with -108
There are no files in
/sys/class/power_supply/
. Thus, it is not possible to directly read battery status.
Drawing on framebufferI do not want to run X11. Therefore, I tried running PyQt apps directly on the framebuffer.
This works (in principle) in this way (after installing python-pyqt5):
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']$ export QT_QPA_PLATFORM=linuxfb
$ python demo.py -qws
[/div]
This shows my demo app directly (and fullscreen) on the display. However, text is not rendered at all, and the widgets do not receive touchscreen or keyboard input. I haven't had time to address these issues yet.
I would greatly appreciate any tips regarding the aforementioned issues.