OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - Arch Linux ARM support => Topic started by: greguu on January 12, 2016, 04:12:03 am
-
Hi all,
(Updated 27/10/2016) : For those that are interested, there is a new kernel release.
https://github.com/greguu/linux-4.4-cxx00/releases/tag/v0.7 (https://github.com/greguu/linux-4.4-cxx00/releases/tag/v0.7)
Kernel 4.4.0 for Sharp Zaurus Cxx00 Series
- enabled seccomp (short for secure computing mode) as required by latest systemd;)
- added Atheros 9k USB drivers on request
- added added CVE-2016-0728 patch
- includes staging drivers for :
RealTek RTL8712U (RTL8192SU) Wireless LAN NIC
Realtek RTL8188EU Wireless LAN NIC driver
Realtek RTL8188EU AP mode
Realtek RTL8723AU Wireless LAN NIC driver
Realtek RTL8723AU AP mode
Realtek RTL8723AU BlueTooth C
- includes cpufreq governors
- includes dirty port of 4.2.3 pxamci.c to fix read only SD card issue with 4.4.0
- includes CF disk LED trigger
- includes CPU heartbeat trigger instead of Battery Charge trigger (broken)
- includes USB 180mA patch
- includes ALARM logo
- known issue : Screen blanks white while in console for first time
- known issue : online charging and battery LED trigger broken, offline charging works
- .config file included in tar.xz
- example boot.cfg file included in tar.xz
- arch-kexecboot based on linux 3.5 included in seperate tar.xz, including instructions
- borzoi console keymap file included
- if you need more firmware install via "pacman -S linux-firmware"
Please post any questions or suggestions within this thread, thanks!
All feedback welcome to improve this kernel.
Cheers!
-
Hello daalnroti,
Thank you for the new kernel.
How to underclock the CPU under this kernel?
I use the following lines to set the cpu to a lower freq.
echo ""userspace" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 312000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
I got an 'write error: invalid argument' error code. What do you suggest?
Thank you,
-
Hello daalnroti,
Thank you for the new kernel.
How to underclock the CPU under this kernel?
I use the following lines to set the cpu to a lower freq.
echo ""userspace" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 312000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
I got an 'write error: invalid argument' error code. What do you suggest?
Thank you,
Hi dmarschal,
as far as I know this was not working with the previous kernels, too.
There are no cpufreq scaling governors included in the kernel, just performance mode.
I have added all scaling governors and tested but got the same error.
Need to investigate the issue further, but I was able to overcock to 624Mhz by hardcoding the value in the kernel.
This could be done for underclocking too I suppose.
Cheers!
-
Thank you!
It did work with the 4.2.3-c3x00 0.4 kernel. I was able to underclock to 104mhz, the lowest possible. The problem was that the screen flickers when the internal CF is accessed. The problem gone when the clock speed was set 312mhz or higher.
-
Thank you!
It did work with the 4.2.3-c3x00 0.4 kernel. I was able to underclock to 104mhz, the lowest possible. The problem was that the screen flickers when the internal CF is accessed. The problem gone when the clock speed was set 312mhz or higher.
Hi dmarschal,
thanks for letting me know. I have changed the 4.4.0 kernel accordingly and released v0.3 including cpufreq governors.
Let me know if that works for you.
https://github.com/greguu/linux-4.4-cxx00/releases/tag/v0.3 (https://github.com/greguu/linux-4.4-cxx00/releases/tag/v0.3)
Cheers!
-
Thank you, daalnroti!
'userspace' with 312 mhz cpu clock works great!
(ondemand is unstable > can't wake up from sleep)
Screen and touch screen works fine as well. The touch screen has troubles on lower frequencies.
Again, thank you!
-
I've still not got round to trying the 4.4.0 kernel yet but I'm happy to hear its working for others.
I did dust off my Z a few days ago to try the USB wifi adapter I bought over xmas for £4. Its marked as a 'BeeWi' but Linux identifies it as a RTL8188SU although it appears the kernel either doesn't have support for this chipset or doesn't autoload the correct module properly as I failed to bring it up although I haven't put much effort in. I do know it is supposed to work with Linux but I think I'm required to build the driver myself as an external module. I'm still running the 4.3 kernel on my Z of course but I expect I'll have similar issues with this device under 4.4. I was also not surprised that it requires being plugged into a powered hub so I'm more interested in seeing the updated libertas code make its way into a usable kernel.
Anyway, I've spent all weekend trying to build a new ALARM armv7 kernel for my BPi to get the onboard audio working so it made me wonder how long it takes daal to build these kernels for the Z? I presume you must use distcc daal but have you ever tried without?
-
[....] it made me wonder how long it takes daal to build these kernels for the Z? I presume you must use distcc daal but have you ever tried without?
Hi danboid, I use the Pre-built crosstool-ng toolchains (x-tools) from the ArchLinux ARM website and compile Z kernels on an X86_64 ArchLinux. It takes about 30 seconds or so.
I have compiled kernels on the Z natively and with distcc, you are looking at several hours for the kernel , and a day or so for building modules, too.
Keep in mind that I am using older x-tools (gcc 4.9) as with newer gcc versions (5+) there are bugs in the Z kernel.
Cheers.
-
Hi all,
bumped kernel to v0.5 https://www.oesf.org/forum/index.php?showto...st&p=282273 (https://www.oesf.org/forum/index.php?showtopic=34420&view=findpost&p=282273)
- added added CVE-2016-0728 patch
This patch is fixes the recent exploit found in the Linux kernel. LTS for the Z
- added linux-fusion module (DirectFB multi application support, linux-one not included)
Linux-Fusion :
This module was added because I hope to find some time to get into compiling a DirectFB/SDL environment to run SDL apps without X in a rotated framebuffer.
I will open a new topic for this once I got the first stage done and released.
Cheers!
-
Linux-Fusion :
This module was added because I hope to find some time to get into compiling a DirectFB/SDL environment to run SDL apps without X in a rotated framebuffer.
I will open a new topic for this once I got the first stage done and released.
Seems you've partly answered a question I just asked in another thread but I don't understand why Fusion would be needed " to run SDL apps without X in a rotated framebuffer". I thought we already had that working for SDL1/DFB apps? Maybe its a requirement to get it working for SDL2?
-
Linux-Fusion :
This module was added because I hope to find some time to get into compiling a DirectFB/SDL environment to run SDL apps without X in a rotated framebuffer.
I will open a new topic for this once I got the first stage done and released.
Seems you've partly answered a question I just asked in another thread but I don't understand why Fusion would be needed " to run SDL apps without X in a rotated framebuffer". I thought we already had that working for SDL1/DFB apps? Maybe its a requirement to get it working for SDL2?
Post : https://www.oesf.org/forum/index.php?showto...st&p=282300 (https://www.oesf.org/forum/index.php?showtopic=34405&view=findpost&p=282300)
-
Hi daalnroti,
Now that OESF is back up, any news or updates to share?
Thanks,
Mark
-
Hi Mark,
currently I have no plans on releasing a new 4.4 series kernel unless there is a need.
..but Kernel 4.8 was released today!
Hopefully I find some spare time and I will work on a possible new release for C3x00 series based on 4.8 and a new rootfs tarball this year.
Cheers!
Hi daalnroti,
Now that OESF is back up, any news or updates to share?
Thanks,
Mark
-
Sounds good, daalnroti....
Glad you are still around!
Mark
-
Hi again,
Where is your new Kernel 4.8 located?
Thanks.
-
Hi Mark,
Linux kernel 4.8 was released on kernel.org on 3rd of October 2016.
I am working on a new kernel veriosn 4.8.1 for Sharp Zaurus C3x00 series at the moment.
There have been quite a few changes since 4.4.0 and as expected there are some issues.
Show stoppers at the moment are :
- fbdev legacy support not working (kernel boots, but blanks white on LCD screen)
Once I got a working release, a new thread will be opened and the release posted on github.
Cheers !
Hi again,
Where is your new Kernel 4.8 located?
Thanks.
-
OK, I get it now, Greg.....
Thanks for clarifying.....
-
Is it safe to do:
# pacman -Syu
and upgrade system?
I didn't actually do an upgrade, but when I started process, I got message:
Replace libdbus with core/dbus?
Don't want to do anything until I have an idea of whether it's safe to do so.
Thanks.
Mark
-
Is it safe to do:
# pacman -Syu
and upgrade system?
I didn't actually do an upgrade, but when I started process, I got message:
Replace libdbus with core/dbus?
Don't want to do anything until I have an idea of whether it's safe to do so.
Thanks.
Mark
Hi Mark,
I have not done a recent pacman -Syu but will check later.
I doubt there are any issues. Keep in mind Arch is a rolling distribution and you will need to stay up to date.
If you are not sure, backup (tar) your rootfs to an SD card first.
Cheers!
-
Is it safe to do:
# pacman -Syu
and upgrade system?
I didn't actually do an upgrade, but when I started process, I got message:
Replace libdbus with core/dbus?
Don't want to do anything until I have an idea of whether it's safe to do so.
Thanks.
Mark
Hi Mark,
I have not done a recent pacman -Syu but will check later.
I doubt there are any issues. Keep in mind Arch is a rolling distribution and you will need to stay up to date.
If you are not sure, backup (tar) your rootfs to an SD card first.
Cheers!
Hi Greg,
To backup rootfs, should I do:
# tar cpjf /rootfs.tar.bz2 -C /mnt/card .
Thanks.
-
Is it safe to do:
# pacman -Syu
and upgrade system?
I didn't actually do an upgrade, but when I started process, I got message:
Replace libdbus with core/dbus?
Don't want to do anything until I have an idea of whether it's safe to do so.
Thanks.
Mark
Hi Mark,
I have not done a recent pacman -Syu but will check later.
I doubt there are any issues. Keep in mind Arch is a rolling distribution and you will need to stay up to date.
If you are not sure, backup (tar) your rootfs to an SD card first.
Cheers!
Hi Greg,
To backup rootfs, should I do:
# tar cpjf /rootfs.tar.bz2 -C /mnt/card .
Thanks.
Looks about right. I would just tar it and not compress with bz2 as this will take ages.
-
Is it safe to do:
# pacman -Syu
and upgrade system?
I didn't actually do an upgrade, but when I started process, I got message:
Replace libdbus with core/dbus?
Don't want to do anything until I have an idea of whether it's safe to do so.
Thanks.
Mark
Hi Mark,
I have not done a recent pacman -Syu but will check later.
I doubt there are any issues. Keep in mind Arch is a rolling distribution and you will need to stay up to date.
If you are not sure, backup (tar) your rootfs to an SD card first.
Cheers!
Hi Greg,
To backup rootfs, should I do:
# tar cpjf /rootfs.tar.bz2 -C /mnt/card .
Thanks.
Looks about right. I would just tar it and not compress with bz2 as this will take ages.
Thanks for the suggestion..........
-
Just as to give some feedback, my ALARM installation upgraded fine doing a pacman -Syu a few days ago and rebooted fine and all things run as they should using kernel 4.4.0.
After a successful pacman -Syu and confirming everything works after a reboot, just tar your root partition, to do a backup. This at least can give you back a working system if a pacman -Syu goes wrong.
I always have a backup system on a SD card and boot to that if needed. Currently 4.4.0 is working still fine under ArchLinuxARM, a new release will take some time as there are several changes in 4.8 that require some work.
-
Hi all,
just to let you know there has been an update for the 4.4.0 kernel release today.
See the opening post or go directly here: https://github.com/greguu/linux-4.4-cxx00/releases/tag/v0.7 (https://github.com/greguu/linux-4.4-cxx00/releases/tag/v0.7)
This release fixed systemd startup errors because of missing seccomp support in the previous 4.4.0 release.
INSTRUCTIONS :
1. download https://github.com/greguu/linux-4.4-cxx00/r...x00-v0.7.tar.xz (https://github.com/greguu/linux-4.4-cxx00/releases/download/v0.7/linux-4.4.0-cxx00-v0.7.tar.xz)
2. extract and replace your current 4.4.0 kernel under /boot and replace all 4.4.0 modules under /lib/modules/
3. reboot
NOTE : the current roofs is outdated and does not contain this update. A new roofs tar ball will be released alongside a new kernel version later this year, hopefully.
If not sure how to upgrade just ask.
Cheers!
-
Thanks, Greg.....
Downloaded new kernel and copied over to my SD card.
Copied the .tar.xz file over to home/marks/Documents/kernel directory on Zaurus.
Extracted files into this directory and see:
$ ls -al
.config
4.4.0-cxx00
boot.cfg
firmware
zImage-4.4.0-cxx00
So, which files do I copy to where?
Thanks.
-
Thanks, Greg.....
Downloaded new kernel and copied over to my SD card.
Copied the .tar.xz file over to home/marks/Documents/kernel directory on Zaurus.
Extracted files into this directory and see:
$ ls -al
.config
4.4.0-cxx00
boot.cfg
firmware
zImage-4.4.0-cxx00
So, which files do I copy to where?
Thanks.
file zImage-4.4.0-cxx00 replaces file /boot/zImage-4.4.0-cxx00
folder 4.4.0-cxx00 replaces folder /lib/modules/4.4.0-cxx00
-
Thanks....
Copied files over as instructed....
Now Zaurus freezes at the kexecboot screen.......
Does not matter which option I select....nothing happens.....
Oh well.................
-
Thanks....
Copied files over as instructed....
Now Zaurus freezes at the kexecboot screen.......
Does not matter which option I select....nothing happens.....
Oh well.................
Hm, something must went wrong.
You still have the SD card you installed ArchLinuxARM from ?
Enter the SD card, turn on the Z, choose the kernel from the SD card in Kexecboot (mmcblk0p1)
Boot up. Mount your CF drive and double check your /boot folder contains the right files.
You can join #alarmz on freenode. Happy to help.
Cheers!
-
Did you alter the boot.cfg file under /boot in any way ?
Do you have any other cards inserted ? SD card or CF card while booting to kexecboot ? Remove all and clean boot.
-
Thanks....
Copied files over as instructed....
Now Zaurus freezes at the kexecboot screen.......
Does not matter which option I select....nothing happens.....
Oh well.................
Hm, something must went wrong.
You still have the SD card you installed ArchLinuxARM from ?
Enter the SD card, turn on the Z, choose the kernel from the SD card in Kexecboot (mmcblk0p1)
Boot up. Mount your CF drive and double check your /boot folder contains the right files.
You can join #alarmz on freenode. Happy to help.
Cheers!
OK, will try.....thanks for the help...
Did you alter the boot.cfg file under /boot in any way ?
Do you have any other cards inserted ? SD card or CF card while booting to kexecboot ? Remove all and clean boot.
No, did not alter boot.cfg file, just copied it over....
Yes, have another SD card in slot....plus ethernet CF card....
Will try without....
-
Just tried booting without any cards in slots.....
Same situation....
Selected Arch and then nothing happens.....
Just realized I left all my other SD cards at office....so, won't be able to see if I have the card I used to install Arch until Monday....
Oh well.........
-
I the boot.cfg file from the tar.xz is configured for archlinux's kexecboot and looks for a kernel on a SD card only.
If you copied the boot.cfg file over the boot.cfg on your CF card it will not boot and may cause the issue you are experiencing.
Are you using kexecboot from archlinux or OE ? You can use the rootfs tar from github to create a boot SD card and fix you boot.cfg on our CF card.
-
I the boot.cfg file from the tar.xz is configured for archlinux's kexecboot and looks for a kernel on a SD card only.
If you copied the boot.cfg file over the boot.cfg on your CF card it will not boot and may cause the issue you are experiencing.
OK, understand....
Are you using kexecboot from archlinux or OE ?
Whatever was included in your instructions.
You can use the rootfs tar from github to create a boot SD card and fix you boot.cfg on our CF card.
Thanks for the suggestion.
-
I the boot.cfg file from the tar.xz is configured for archlinux's kexecboot and looks for a kernel on a SD card only.
If you copied the boot.cfg file over the boot.cfg on your CF card it will not boot and may cause the issue you are experiencing.
OK, understand....
Are you using kexecboot from archlinux or OE ?
Whatever was included in your instructions.
You can use the rootfs tar from github to create a boot SD card and fix you boot.cfg on our CF card.
Thanks for the suggestion.
So to get you going again:
I assume your CF partition is ext4 for sda1 and your alarmz root and you did copy the new kernel to the right location on you CF card, including the kernel modules.
Follow Dan's guide to create an arch SD card : https://github.com/danboid/ZALARM-install (https://github.com/danboid/ZALARM-install)
Insert the SD card and turn on the Zaurus.
Boot from the SD card. Kexecboot should list the kernel.
Once logged on as root mount your CF card and edit boot.cfg
mount /dev/sda1 /mnt
nano /mnt/boot/boot.cfg
Example boot.cfg for single kernel boot from sda1 on ext4:
LABEL=ArchLinux
KERNEL=/boot/zImage-4.4.0-cxx00
APPEND=root=/dev/sda1 rootfstype=ext4 fbcon=rotate:1 noinitrd loglevel=3
Then exit the editor and unmount and reboot.
unmount /mnt
reboot
Then remove the SD card and fingers crossed you can boot back into you arch on the CF card.
Hope this helps.
I recommend before doing an kernel upgrade to do a backup first and more importantly have recovery partition or SD card handy for situations like this.
-
Tried booting up with SD card....
Kexecboot does not list it at the selection screen....
Selected System Tools and then Debug Info....
See the following regarding the SD card:
Found device '/dev/mmcblk0' (179, 0) of size 970Mb
+ creating device node
+ can't identify FS type
Hmmm........I formatted card as EXT4.....
I checked card to see that all the directories were there......
Maybe bad card?
UPDATE
Found the SD card that I used originally to install ALARMZ before....
It is recognized in kexecboot.....yeah!
It's booting up Z now.....
-
Tried booting up with SD card....
Kexecboot does not list it at the selection screen....
Selected System Tools and then Debug Info....
See the following regarding the SD card:
Found device '/dev/mmcblk0' (179, 0) of size 970Mb
+ creating device node
+ can't identify FS type
Hmmm........I formatted card as EXT4.....
I checked card to see that all the directories were there......
Maybe bad card?
Please scroll down a bit in the debug log, as it should contain information regarding the first partition I think (/dev/mmcblk0p1)..
-
Tried booting up with SD card....
Kexecboot does not list it at the selection screen....
Selected System Tools and then Debug Info....
See the following regarding the SD card:
Found device '/dev/mmcblk0' (179, 0) of size 970Mb
+ creating device node
+ can't identify FS type
Hmmm........I formatted card as EXT4.....
I checked card to see that all the directories were there......
Maybe bad card?
Please scroll down a bit in the debug log, as it should contain information regarding the first partition I think (/dev/mmcblk0p1)..
Thank you for your help, p0c.....
And welcome to the club.....
Didn't see your post until after I edited my post above...
So, already booted up with my other SD card.....
Strange thing is that even though I used my SD card to boot up, it booted up into login screen and then into Fluxbox which is all installed on my internal CF card.
Edited boot.cfg and rebooted....
Now it boots up OK and only error message is about swap which makes sense as I now need to redo SD card to be swap again.
Whew!
@Greg
Should I try your new updated kernel?
-
Tried booting up with SD card....
Kexecboot does not list it at the selection screen....
Selected System Tools and then Debug Info....
See the following regarding the SD card:
Found device '/dev/mmcblk0' (179, 0) of size 970Mb
+ creating device node
+ can't identify FS type
Hmmm........I formatted card as EXT4.....
I checked card to see that all the directories were there......
Maybe bad card?
Please scroll down a bit in the debug log, as it should contain information regarding the first partition I think (/dev/mmcblk0p1)..
Thank you for your help, p0c.....
And welcome to the club.....
Didn't see your post until after I edited my post above...
So, already booted up with my other SD card.....
Strange thing is that even though I used my SD card to boot up, it booted up into login screen and then into Fluxbox which is all installed on my internal CF card.
Edited boot.cfg and rebooted....
Now it boots up OK and only error message is about swap which makes sense as I now need to redo SD card to be swap again.
Whew!
@Greg
Should I try your new updated kernel?
Up to you. There may some unknown issues. You can add it as a secondary boot option.