Messages

1

Gemini PDA - Hardware / Gemini screen line and not boot

« on: October 12, 2019, 02:00:43 pm »

I'm in a similar boat with a Gemini PDA that I rarely use. Went to try out a new distro and I get the same scrolling display as you have.

Did you have any luck resolving this issue?

I have the exact same issue, I contacted Planet Computers about the issue, and this was their response.

Thanks for your message. While the issue you’re facing might seem concerning at first, this is a known result of software corruption and is relatively easy to resolve.

1. Please begin by flashing your device with the Android-only setup as instructed at http://support.planetcom.co.uk/index.php/A..._Flashing_Guide. You can get the device to flash mode by holding Esc + the silver side button even if you’re seeing the screen in question. The device will then flash as normal.

2. Once flashed, you will still see the lines. Please wait until the device’s battery dies on the lines screen.

3. Once the battery is entirely empty, connect the original power plug included in the Gemini’s box to the Gemini for around 30 seconds. After 30 seconds, you will be able to power the device on as normal.

Please let me know how this goes.

I have tried to fix the issue using these steps, but haven't had any success. At a guess, despite leaving the device to run flat, there is still some residual charge left causing the issue to persist.
I've contacted Planet again to ask if there is another method of draining the battery or disconnecting it to reset the device, so I will let you know what the outcome of that is.

2

Gemini PDA - Hardware / Hot to touch when charging

« on: October 11, 2018, 11:58:51 am »

When charging with the provided charger, the Gemini gets very warm. Is this normal for others? I know the charger negotiates a higher current / voltage (beyond 5V / .5A), but I would figure the heat will damage the battery and reduce its life over time.

3

Gemini PDA - Linux / Automatic Headphone Audio Switching?

« on: September 28, 2018, 07:59:54 am »

Thanks for the information!

I was able to load the module using pacmd, confirmed with pactl list, but no luck. I also rebooted and added it to the default pulseaudio configuration and had the same result; sound comes out of both the headphones and the speaker, and listing the sink / source info after plugging in headphones shows no change.

My next step is to confirm that the headphone jack actually sends an event to the pulseaudio server. I'm guessing that would be some sort of ACPI event, but I'm not sure. (Further research necessary!)

I don't have Debs on my Gemini, but if it is PulseAudio switching outputs on connect you can try on the command line (as your session user):

pacmd load-module module-switch-on-connect

If that works then to make it load on boot hunt down the default.pa, normally at:

/etc/pulse/default.pa

and add:

load-module module-switch-on-connect

Also check if you have a user specific one:

~/.config/pulse/default.pa

4

Gemini PDA - Linux / Automatic Headphone Audio Switching?

« on: September 26, 2018, 07:57:30 am »

Yo! Long time no see! Yeah, I've been lurking for a while after getting the Gemini. How are you doing?

So far the Gemini is pretty nice; I'm waiting for a keymat replacement to come in the mail (I have the dreaded floppy keys issue).

5

Gemini PDA - Linux / Automatic Headphone Audio Switching?

« on: September 25, 2018, 11:51:14 pm »

Does anybody have automatic headphone audio switching working under the Planet Computers provided Debian TP2 environment?

I can switch audio manually using the 'PulseAudio Volume Control' application (pavucontrol?), but I've yet to find a way to set PulseAudio to automatically switch output from the built in speakers to headphones when I plug into the 3.5mm audio jack.

Thanks!

6

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: November 01, 2015, 08:33:02 pm »

Started working on this today and of course show stopper before I even got started.

For some reason recovery flash can't see my SD card, but it mounts in BSD just fine on the Z (and also on the linux machine I copied files from), so I can't get kexecboot going *sigh*

Been long enough I don't remember but was there some size limit with the Z?  It's only 2gb sandisk ... its a micro in a SD adapter, maybe that is the problem?

I had the same issue with mine. I used a 1gb standard SD and a 2gb micro SD card. Neither worked. Had to flash recovery from CF instead. OBSD and ALARM have no problem with the card. *shrug*

7

Zaurus - Arch Linux ARM support / Archlinuxarm On C3x00

« on: November 01, 2015, 08:23:53 pm »

Hey gang. I gave this a go today.

I ran into some issues with the KEXECBOOT updater not working on my Zaurus. I wound up having to do a complete NAND restore to factory settings to be able to install KEXECBOOT. The SD / CF updater would always fail.

After doing that, I was able to at least install KEXECBOOT and boot into ALARM on my CF card.

I then attempted to replace the internal 4GB microdrive with a 64GB microSD card housed in a Type 2 CF to MicroSD card adapter. I had planned on setting up the internal drive from the CF install of ALARM but to my surprise ALARM would not boot properly after putting in the new internal drive. I suspect that KEXECBOOT (or the NAND app) writes some data to the partitions on the Microdrive normally.

So I took out the internal CF / MicroSD card and partitioned it so that the two Sharp original partitions and files (.SYS directory) were on the new card.

I had planned on reinstalling from scratch (reinstall KEXECBOOT, etc) but even after the new partitioning of the SD / CF adapter, the KEXECBOOT install script tells me the microdrive is not found. Suxxor.

I'll continue with it some time next week. I don't know much about Arch Linux (avid OpenBSD user) so I'll have to learn the ecosystem. It's different enough for me to not know how to do a majority of the stuff I'd like to.

8

Zaurus - Arch Linux ARM support / Welcome To Arch Linux Arm On Zaurus Forum

« on: October 28, 2015, 10:06:33 am »

Hey everyone! I'll give this a try in the near future when I get some weekend free time.

How hard would it be to get a sticky thread with a list of what is working and what is not? It might help to get people looking at the effort.

9

OpenBSD / Openbsd 5.5/zaurus : X Does Not Work With Default Config

« on: May 05, 2014, 10:39:07 am »

TronDD and I have noticed an issue running X on 5.5 release. From my experience before, Zaurus' X server 'just worked' without any necessary configuration.
Running startx results in black screen for a few seconds, and then a return to the console. Anyone else noticing the same behavior?

Xorg.0.log:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\'][   872.326] (--) Using wscons driver on /dev/ttyC1 in pcvt compatibility mode (version 3.32)
[   872.811]
X.Org X Server 1.14.5
Release Date: 2013-12-12
[   872.953] X Protocol Version 11, Revision 0
[   873.025] Build Operating System: OpenBSD 5.5 zaurus
[   873.099] Current Operating System: OpenBSD zaurus.questforless.com 5.5 GENERIC#4 zaurus
[   873.179] Build Date: 12 March 2014  04:22:05AM
[   873.250]  
[   873.323] Current version of pixman: 0.32.4
[   873.394]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[   873.394] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   873.728] (==) Log file: "/var/log/Xorg.0.log", Time: Sun May  4 21:52:41 2014
[   873.888] (==) Using config file: "/etc/X11/xorg.conf"
[   873.916] (==) No Layout section.  Using the first Screen section.
[   873.917] (==) No screen section available. Using defaults.
[   873.918] (**) |-->Screen "Default Screen Section" (0)
[   873.919] (**) |   |-->Monitor "<default monitor>"
[   874.001] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
[   874.002] (**) |   |-->Device "Wsdisplay0"
[   874.003] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[   874.005] (==) Disabling SIGIO handlers for input devices
[   874.006] (==) Automatically adding devices
[   874.007] (==) Automatically enabling devices
[   874.007] (==) Not automatically adding GPU devices
[   874.584] (==) FontPath set to:
   /usr/X11R6/lib/X11/fonts/misc/,
   /usr/X11R6/lib/X11/fonts/TTF/,
   /usr/X11R6/lib/X11/fonts/OTF/,
   /usr/X11R6/lib/X11/fonts/Type1/,
   /usr/X11R6/lib/X11/fonts/100dpi/,
   /usr/X11R6/lib/X11/fonts/75dpi/
[   874.584] (==) ModulePath set to "/usr/X11R6/lib/modules"
[   874.584] (II) The server relies on wscons to provide the list of input devices.
   If no devices become available, reconfigure wscons or disable AutoAddDevices.
[   874.585] (II) Loader magic: 0x1ebc74
[   874.586] (II) Module ABI versions:
[   874.586]    X.Org ANSI C Emulation: 0.4
[   874.586]    X.Org Video Driver: 14.1
[   874.587]    X.Org XInput driver : 19.1
[   874.587]    X.Org Server Extension : 7.0
[   874.715] Initializing built-in extension Generic Event Extension
[   874.787] Initializing built-in extension SHAPE
[   874.859] Initializing built-in extension MIT-SHM
[   874.931] Initializing built-in extension XInputExtension
[   875.003] Initializing built-in extension XTEST
[   875.075] Initializing built-in extension BIG-REQUESTS
[   875.147] Initializing built-in extension SYNC
[   875.219] Initializing built-in extension XKEYBOARD
[   875.291] Initializing built-in extension XC-MISC
[   875.363] Initializing built-in extension SECURITY
[   875.436] Initializing built-in extension XINERAMA
[   875.508] Initializing built-in extension XFIXES
[   875.580] Initializing built-in extension RENDER
[   875.652] Initializing built-in extension RANDR
[   875.724] Initializing built-in extension COMPOSITE
[   875.796] Initializing built-in extension DAMAGE
[   875.868] Initializing built-in extension MIT-SCREEN-SAVER
[   875.941] Initializing built-in extension DOUBLE-BUFFER
[   876.013] Initializing built-in extension RECORD
[   876.085] Initializing built-in extension DPMS
[   876.158] Initializing built-in extension X-Resource
[   876.230] Initializing built-in extension XVideo
[   876.303] Initializing built-in extension XVideo-MotionCompensation
[   876.375] Initializing built-in extension XFree86-VidModeExtension
[   876.447] Initializing built-in extension XFree86-DGA
[   876.520] Initializing built-in extension XFree86-DRI
[   876.592] Initializing built-in extension DRI2
[   876.593] (II) LoadModule: "glx"
[   876.680] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[   876.829] (II) Module glx: vendor="X.Org Foundation"
[   876.830]    compiled for 1.14.5, module version = 1.0.0
[   876.830]    ABI class: X.Org Server Extension, version 7.0
[   876.831] (==) AIGLX enabled
[   876.920] Loading extension GLX
[   876.921] (II) LoadModule: "wsfb"
[   876.926] (II) Loading /usr/X11R6/lib/modules/drivers/wsfb_drv.so
[   876.961] (II) Module wsfb: vendor="X.Org Foundation"
[   876.962]    compiled for 1.14.5, module version = 0.4.1
[   876.962]    ABI class: X.Org Video Driver, version 14.1
[   876.964] (II) wsfb: driver for wsdisplay framebuffer: wsfb
[   876.965] (WW) Falling back to old probe method for wsfb
[size=][   877.000] (II) wsfb(0): using /dev/ttyC1
[   877.004] (EE) Segmentation fault at address 0x10
[   877.078] (EE)
Fatal server error:
[   877.148] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   877.221] (EE)
[   877.293] (EE) [/size]
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[   877.361] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   877.432] (EE)
[   877.582] (EE) Server terminated with error (1). Closing log file.[/div]

/etc/xorg.conf:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']# $OpenBSD: xorg.conf,v 1.5 2012/01/29 11:20:33 matthieu Exp $

Section "Device"
   Identifier   "Wsdisplay0"
   Driver      "wsfb"
   Option      "device" "/dev/ttyC1"
   # Comment out to use the screen in vertical mode
   Option      "rotate" "CW"
EndSection
[/div]

dmesg:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']OpenBSD 5.5 (GENERIC) #4: Thu Mar  6 04:13:47 MST 2014
    deraadt@zaurus.openbsd.org:/usr/src/sys/arch/zaurus/compile/GENERIC
real mem  = 67108864 (64MB)
avail mem = 58281984 (55MB)
warning: no entropy supplied by boot loader
mainbus0 at root
cpu0 at mainbus0: PXA27x step C-5 (XScale core)
cpu0: DC enabled IC enabled WB enabled LABT branch prediction enabled
cpu0: 32KB(32b/l,32way) I-cache, 32KB(32b/l,32way) wr-back-lock D-cache
pxaip0 at mainbus0: CPU clock = 416.000 MHz
pxaintc0 at pxaip0 addr 0x40d00000: Interrupt Controller
pxagpio0 at pxaip0 addr 0x40e00000: GPIO Controller
pxadmac0 at pxaip0 addr 0x40000000 intr 25: DMA Controller
pxaost0 at pxaip0 addr 0x40a00000
com0 at pxaip0 addr 0x40100000 intr 22: pxa2x0, 32 byte fifo
com1 at pxaip0 addr 0x40200000 intr 21: pxa2x0, 32 byte fifo
com2 at pxaip0 addr 0x40700000 intr 20: pxa2x0, 32 byte fifo (SIR)
ohci0 at pxaip0, version 1.0
usb0 at ohci0: USB revision 1.0
uhub0 at usb0 "PXA27x OHCI root hub" rev 1.00/1.00 addr 1
lcd0 at pxaip0
wsdisplay0 at lcd0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1 added (std, vt100 emulation)
zkbd0 at pxaip0
wskbd0 at zkbd0: console keyboard, using wsdisplay0
scoop0 at pxaip0: PCMCIA/GPIO controller
scoop1 at pxaip0: PCMCIA/GPIO controller
pxapcic0 at pxaip0: 2 slots
pcmcia0 at pxapcic0
pcmcia1 at pxapcic0
pxammc0 at pxaip0: MMC/SD/SDIO controller
sdmmc0 at pxammc0
zssp0 at pxaip0
apm0 at pxaip0
zts0 at pxaip0
wsmouse0 at zts0 mux 0
zaudio0 at pxaip0: I2C, I2S, WM8750 Audio
audio0 at zaudio0
zrc0 at pxaip0: CE-RH2 remote control
wskbd1 at zrc0 mux 1
wskbd1: connecting to wsdisplay0
flash0 at pxaip0: Samsung K9F1G08U0A 128Mx8 3.3V
pxaudc0 at pxaip0: USB Device Controller
usbf0 at pxaudc0: USB revision 1.1
cdcef0 at usbf0: address 2a:cb:00:00:00:00
wdc0 at pcmcia0 function 0 "HITACHI, microdrive" port 0x0/16: irq 138
wd0 at wdc0 channel 0 drive 0: <HMS360604D5CF00>
wd0: 32-sector PIO, LBA, 3906MB, 7999488 sectors
wd0(wdc0:0:0): using BIOS timings
scsibus0 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed
sd0: 982MB, 512 bytes/sector, 2012160 sectors
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
boot device: wd0
root on wd0a (22a8adc198419c00.a) swap on wd0b dump on wd0b
WARNING: using filesystem date -- CHECK AND RESET THE DATE![/div]

10

OpenBSD / Openbsd 5.4/zaurus Issues

« on: May 01, 2014, 08:00:56 pm »

Alright, I loaded OpenBSD 5.5 today and here's what I've found:

• The Good:
  • Audio playback works without issue
• The Bad:
  • None of the apm suspend / hibernate / standby modes work properly as far as I can tell
• The Ugly:
  • Using machdep.lidsuspend=1 seems to work, putting the Z into standby, but powering back up results in a black screen. I have a workaround below.

I had hoped that the sound performance would be better; as is, decoding 112kHz streaming OGG is just barely outside of the reach of the Zaurus. Even with the processor max speed set to 520, CPU utilization is pegged at 100% while running ogg123. Playing around with the sndiod audio rate didn't seem to help, though I know little to nothing about sound in UNIX-likes.



In the default OpenBSD shell, ksh, keys combinations can be bound to commands. Check the link here:StackExchange : Adding Ctrl-L as “clear” hotkey in OpenBSD's ksh

The suspend backlight screen fix I used has a few steps:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']
echo wsconsctl display.backlight=100 > /home/screenfix.sh
chmod 0755 /home/screenfix.sh
echo bind -m '^H'=/home/screenfix.sh'^J' >>~/.profile
[/div]
Log out of the shell and log back in, close the lid, open and hit CTRL+H. Seems to work for me. If you want to see what binds are already set, just enter 'bind' at the shell for a list.

If you're in X when you suspend, I feel bad for you son. . . . I got 99 problems but this glitch ain't one.

11

OpenBSD / Openbsd 5.4/zaurus Issues

« on: April 25, 2014, 12:25:17 pm »

Funny, I was trying to get sound going and noticed the devices weren't there.  I swore I had seen them before.

I'm just going to wait for 5.5 before putting too much more time into fiddling with things.

Found this in the release notes:

http://www.openbsd.org/plus55.html[/url] ']

• Re-added audio devices to the zaurus.
• Fixed ztsscale(8/zaurus) after struct wscons_event size change.
• Lock the audio mutex before invoking the audio(4) call-back. Fixes panics on zaurus.

Looks like some fixes for sound issues. Rockin!

12

OpenBSD / Openbsd 5.4/zaurus Issues

« on: April 25, 2014, 12:08:26 pm »

Thanks for the clarification about arm packages....so, while it's great that the libs, etc, are usable, we still have to build packages for the programs we want to use such as browsers, office type programs, etc....which takes time.....

Sorry, I may have caused confusion. If the application package (not just libraries) already exists in the ftp repository, you can install it. For example, there's a dillo package in the repo: dillo-3.0.3.tgz

IMO, the only time you'd want to build a package from source would be

• If a package does not exist
• If the package source version is old, and there are newer features available
• You want to pass in some compiler arguments for optimization
• The package source is . . . . questionable.

13

OpenBSD / Openbsd 5.4

« on: April 25, 2014, 12:15:28 am »

Plan to Build: taskwarrior, libreoffice (or other similar programs such as abiword, gnumeric, etc...), wget, dillo....

Woah, libreoffice will take FOREVER to build. I noticed in your sig you have two SLCs. If you wanted, you could probably have one on a laptop cooler just building packages all day and the other one in 'normal use'.

14

OpenBSD / Openbsd 5.4

« on: April 25, 2014, 12:11:20 am »

SL-C3200 is still supported on OpenBSD. I'm currently running version 5.4 on my Zaurus with zero issues.

What's your use case for the Z? Is it always on, chillin' on a desk? My experience so far has been a little different, but I suspect we're trying different things.

15

OpenBSD / Openbsd 5.4/zaurus Issues

« on: April 25, 2014, 12:08:20 am »

Didn't know that the 'generic arm packages' will run on the z....by generic do you mean all the libs, etc? or including the programs such as browsers, etc?......

Hey Mark! Long time no see.

To answer your question, Yes; the generic arm packages, including libraries should work with the Z. So if you attempt to install dillo for example, any of the packages it needs as a prerequisite SHOULD work from the same 'armish' package tree.

From the OpenBSD site:

http://www.openbsd.org/zaurus.html[/url] ']Since the Zaurus is a fully capable machine, we no longer cross compile. All builds of Zaurus are done on the Zaurus directly. (The shared "arm" packages are nowadays built on the armish platform, because it is faster.)

And from the installation notes:

http://ftp.openbsd.org/pub/OpenBSD/snapsho.../INSTALL.zaurus[/url] ']Installing applications from the ftp.OpenBSD.org package collection:

   All available packages for your architecture have been placed on
   ftp.OpenBSD.org in the directory pub/OpenBSD/5.5/packages/arm/
   You may want to peruse this to see what packages are available.  The
   packages are also on the OpenBSD FTP mirror sites.

Hah, apparently the site is slowly making its way from 5.4 to 5.5!