1
C1000/3x00 General discussions / Re: C1000 As A Ir Remote
« Last post by DiTBho on April 28, 2025, 08:10:34 am »interesting 
Select language:
News:
Recent Posts
2
Zaurus - Arch Linux ARM support / kexecboot-size, max-size?
« Last post by DiTBho on April 28, 2025, 07:47:23 am »I'm a bit confused by what I read online.
I wonder:
1) what is the maximum size of the kexecboot executable? < 2Mbyte? or <1.2 Mbyte? Different things are read online.
2) isn't it possible to repartition the flash and use the entire flash to contain kexecboot or something similar?
3) why is there no interest in u-boot?
I wonder:
1) what is the maximum size of the kexecboot executable? < 2Mbyte? or <1.2 Mbyte? Different things are read online.
2) isn't it possible to repartition the flash and use the entire flash to contain kexecboot or something similar?
3) why is there no interest in u-boot?
3
Zaurus - Arch Linux ARM support / Re: Update: C1000 / Akita support
« Last post by DiTBho on April 28, 2025, 07:36:26 am »as you may know, current 3.10.y and previous 3.x kexecboot kernels fail to boot on C1000 / Akita.
why did it fail?
what was/is the problem?
4
Zaurus - Void Linux support / Re: kernel patches? to Vanilla
« Last post by DiTBho on April 28, 2025, 07:10:20 am »as far as I observe, the patches are only about GPIO.
Right?
Right?
Code: [Select]
1. 7 Kbyte patch_from_void/01-fix-pxa27x-udc.patch
3. 8 Kbyte patch_from_void/01_revert_mmc_slot-gpio.patch
2. 8 Kbyte patch_from_void/02_revert_mmc_spitz_pxamci.patch
1. 6 Kbyte patch_from_void/03_revert_mmc_pxamci_platform.patch
295. 0 byte patch_from_void/04_revert_mmc_pxa_platform.patch
2. 3 Kbyte patch_from_void/05_revert_mmc_pxa_gpio_desc.patch
759. 0 byte patch_from_void/06_revert_mmc_pxa_gpio_desc.patch
3. 7 Kbyte patch_from_void/07_revert_mmc_spi_gpio_desc.patch
3. 8 Kbyte patch_from_void/08_revert_pcmcia_cpufreq.patch
342. 0 byte patch_from_void/09_usb_power.patch
1. 1 Kbyte patch_from_void/10_sandisk-cf.patch
249. 0 byte patch_from_void/11-revert-mmc-slot-gpio.patch
(only these? to Vanilla from kernel dot org)5
Zaurus - Void Linux support / Re: kernel patches? to Vanilla
« Last post by greguu on April 28, 2025, 02:01:51 am »Yes, the latest voidz package is 5.4.229. I can upload a build if needed, still working on a new voidz rootfs with new kernel.
There is binary package for 5.3.221 here https://github.com/greguu/voidz-packages/releases/download/build-008/zaurus-5.4.221_1.tar.gz
There is binary package for 5.3.221 here https://github.com/greguu/voidz-packages/releases/download/build-008/zaurus-5.4.221_1.tar.gz
6
Zaurus - Arch Linux ARM support / kernel from 2.6.23 to kernel 5.4.229: suspend/resume?
« Last post by DiTBho on April 27, 2025, 06:06:18 pm »hi
I usually take my C1000 out of the house, as I use it daily, usually on the train(2h/day)/tube(40min/day)/coffee breaks/etc, so I desperately need the suspend/resume feature offered by the power management system, as well as desperately need the battery charging feature to get up to 4/5 hours.
Unfortunately *everything* I've tested after kernel version 2.6.23 doesn't work.
I haven't tested kernels 3.* and 4.*
Kernel 5.* ... ummm, not working.
I don't quite understand: have these two features been fixed, and I simply missing something? Are there any specific patches?
Also kernel 4.* is ok
Please let me know.
I usually take my C1000 out of the house, as I use it daily, usually on the train(2h/day)/tube(40min/day)/coffee breaks/etc, so I desperately need the suspend/resume feature offered by the power management system, as well as desperately need the battery charging feature to get up to 4/5 hours.
Unfortunately *everything* I've tested after kernel version 2.6.23 doesn't work.
I haven't tested kernels 3.* and 4.*
Kernel 5.* ... ummm, not working.
I don't quite understand: have these two features been fixed, and I simply missing something? Are there any specific patches?
Also kernel 4.* is ok
Please let me know.
7
Zaurus - Arch Linux ARM support / Re: Update: C1000 / Akita support
« Last post by DiTBho on April 27, 2025, 01:21:30 pm »hi
I applied all the patches found in Void, to vanilla kernel { 5.0-rc3, 5.4.229 }.
Tested on my c1k, both k5 kernels boot find, but the suspend does not work at all.
When I press the suspend button, the screen makes a bright flash.
Sometimes the screen even goes white, and I can't see the text console anymore.
I applied all the patches found in Void, to vanilla kernel { 5.0-rc3, 5.4.229 }.
Code: [Select]
~ arch/arm/mach-pxa/spitz.c
~ drivers/mmc/core/slot-gpio.c
~ drivers/mmc/host/pxamci.c
~ drivers/mmc/host/mmc_spi.c
~ drivers/mmc/host/of_mmc_spi.c
~ drivers/ata/pata_pcmcia.c
~ drivers/pcmcia/soc_common.c
~ drivers/pcmcia/soc_common.h
~ include/linux/mmc/slot-gpio.h
~ include/linux/platform_data/mmc-pxamci.h
~ include/linux/spi/mmc_spi.h
(patches, modified these files)Tested on my c1k, both k5 kernels boot find, but the suspend does not work at all.
When I press the suspend button, the screen makes a bright flash.
Sometimes the screen even goes white, and I can't see the text console anymore.
8
Zaurus - Void Linux support / Re: kernel patches? to Vanilla
« Last post by DiTBho on April 26, 2025, 03:32:54 pm »5.4.229?
9
Zaurus - Void Linux support / Re: kernel patches? to Vanilla
« Last post by DiTBho on April 26, 2025, 03:26:27 pm »to exactly which kernel 5.4.? version?
10
Gemini PDA - Linux / Working UBports (Ubuntu Touch) Focal for the Gemini PDA by NotKit
« Last post by AnotherLinuxUser on April 17, 2025, 02:13:19 pm »I recently gave NotKit's UBports (Ubuntu Touch) port for the Gemini PDA and it works pretty well. It is Halium 9-based. For those who are looking for a newer Linux-based distribution to run on the Gemini PDA and/or helpful sources that could lead to something like Droidian being ported, here's the link:
https://gitlab.com/ubports/porting/community-ports/android9/planet-geminipda/planet-geminipda
The instructions on the Gitlab repo assumes that the installation is being done from Linux (such as Gemian) from the Gemini PDA. The actual vendor image with the UBports root filesystem doesn't need to be directly written to any partition; only the boot image file.
The 'ubuntu.img' file has to be placed at the root of the Gemian partition, so, the path to the file should look like: '/ubuntu.img'
Do note that the 'ubuntu.img.zstd' from the 'artifacts.zip' file has to be decompressed to in order to get the 'ubuntu.img' file.
As mentioned in the instructions, to boot UBports from "Boot 3" does the following command need to be executed:
cat boot.img > /dev/disk/by-partlabel/boot3
Note: The port requires the Android 8.1 firmware to be installed already. Elevated permissions are required to write the 'boot.img' file and to move the 'ubuntu.img' to '/ubuntu.img'
After testing, I can confirm that the Gemini PDA runs UBports quite well.
https://gitlab.com/ubports/porting/community-ports/android9/planet-geminipda/planet-geminipda
The instructions on the Gitlab repo assumes that the installation is being done from Linux (such as Gemian) from the Gemini PDA. The actual vendor image with the UBports root filesystem doesn't need to be directly written to any partition; only the boot image file.
The 'ubuntu.img' file has to be placed at the root of the Gemian partition, so, the path to the file should look like: '/ubuntu.img'
Do note that the 'ubuntu.img.zstd' from the 'artifacts.zip' file has to be decompressed to in order to get the 'ubuntu.img' file.
As mentioned in the instructions, to boot UBports from "Boot 3" does the following command need to be executed:
cat boot.img > /dev/disk/by-partlabel/boot3
Note: The port requires the Android 8.1 firmware to be installed already. Elevated permissions are required to write the 'boot.img' file and to move the 'ubuntu.img' to '/ubuntu.img'
After testing, I can confirm that the Gemini PDA runs UBports quite well.