Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - jerrybme

Pages: 1 [2] 3
X/Qt / X/qt & Debian With Cacko 1.22
« on: January 20, 2005, 03:11:23 pm »
Well, I've been futzing around for the last several days with this combo and have gotten it  to work very well, so I thought I'd share my experience.

First, while I'm a pdaXrom fan; I want to see if this was the best of both worlds. In many ways it is. The down side is that on a CLXXX machine you're forced to use the slow SD memory for the debian file system so it is slow. Second, if you want to use Wifi, that means using a swapfile on the SD, which raises concerns for what it might do to the memory long term. Since I've got a microdrive, when not surfing the web I use it for swap space. Therefore, this setup makes more sense for the 6000 (assuming a microcard in the CF slot) or 3000 users in that they can keep the debian file system and the swapfile on the faster microdrive.

I found that using the default wm, icewm was not as good as fvwm. It is faster and lighter (important when forced to use the SD). But I am biased as I like the configurability of fvwm, but that means it needs more tweaking and doesn't work "out of the box" as icewm does.

The only adaptations I had to do from the excellent wiki guide was to change the xmodmaprc file.
And alter the startd script that goes in the debian root directory. That solved all of my locales errors that were making some installations fail.

Attached are some screenshots of my setup


 [ Invalid Attachment ]

X/Qt / Debian/x-qt & Cacko
« on: January 18, 2005, 01:01:23 pm »
The pinned thread is getting a bit lengthy so thought I'd make this a seperate one.

I was getting Locale error messages even after installing & configuring Locales. After some googling I found that adding the following to my startd script has fixed this problem->
Code: [Select]
unset LANG
unset LC_ALL
export LC_TYPE=en_US
I'm running as root so you may need to add su or sudo if you're running as the zaurus user.

I tried putting these in my .xinitrc but it didn't work, I quess they need to be made inside the chroot enivironment. I've removed the
Code: [Select]
export LANG=en_US
export LC_ALL=en_US
from my .xinitrc and installations seem to be working fine.

X/Qt / X/qt With Debian
« on: January 13, 2005, 02:54:39 pm »
Ok, I give up  
I've been trying to get my .Xresource file used in my X/QT session, I've but it in my /home/zaurus directory (which is where it seems to me it'd be read during X init), my /mnt/card/debroot/root, /mnt/card/home/zaurus and none of the locations seem to invoke the settings. I know I'm missing something but I'm tried of copying the damn file around.
Doh, I meant to type .Xdefaults when creating this thread, I'd been searching the forum and had been reading about .Xresource    So my question is really about using .Xdefaults....

Zaurus - pdaXrom / Favorite Pdaxrom Tweaks
« on: December 28, 2004, 09:59:57 am »
I though it might be fun/useful to share your favorite tweaks.

Here's a couple of mine that I've copied over from my gentoo setup:
I have been using .Xdefaults in my home directory to set default aterm settings. This allows me to have the same aterm settings as I use different wm with having to hack different scripts in each.

Code: [Select]
# ~/.Xdefaults
# Aterm Terminal Settings

# 786 lines = 500 KB of memory

# Aterm Font Settings, selected using 'xfontsel'

# Aterm Color Settings

aterm*background:  black
aterm*foreground:  green
aterm*cursorColor: green

# I got these colors from using gnome-terminal's color
# dialogue. under Palette, i selected 'linux console'
# and just middle-mouse copied the values over--a swell hack

aterm*color0:      #000000
aterm*color1:      #AA0000
aterm*color2:      #00AA00
aterm*color3:      #AA5500
aterm*color4:      #0000AA
aterm*color5:      #AA00AA
aterm*color6:      #00AAAA
aterm*color7:      #AAAAAA
aterm*color8:      #555555
aterm*color9:      #FF5555
aterm*color10:     #55FF55
aterm*color11:     #FFFF55
aterm*color12:     #5555FF
aterm*color13:     #FF55FF
aterm*color14:     #55FFFF
aterm*color15:     #FFFFFF

Then to customize the bash prompt I've added .bash_profile and .bashrc to my home directory as well. The settings display the path at the prompt so you always know where you are. Also it allows you to create aliases or shortcuts, I've set it so that "d" = ls and "nano" = nano -w.
.bash_profile ->
Code: [Select]
# /etc/skel/.bash_profile:
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/skel/.bash_profile,v 1.10 2002/11/18 19:39:22 azarah Exp $

#This file is sourced by bash when you log in interactively.
[ -f ~/.bashrc ] && . ~/.bashrc

.bashrc ->
Code: [Select]
# /etc/skel/.bashrc:
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/skel/.bashrc,v 1.8 2003/02/28
 #15:45:35 azarah Exp $

# This file is sourced by all *interactive* bash shells on startup.  This
# file *should generate no output* or it will break the scp and rcp commands.

alias d="ls"
alias nano="nano -w"

PS1="\$(pwd) # "

And lastly, I've added a message that is displayed with each new prompt by adding a last line to /etc/profle
Code: [Select]
echo "Zaurus = Penguin Power"

Zaurus - pdaXrom / Gimp On Sd
« on: December 28, 2004, 09:34:39 am »
Anyone else had this problem? I've installed gimp on SD and it runs fine until next reboot. Then some, but not all, of the gimp libraries /usr/shar/lib symlinks -> /mnt/card/usr/share/lib are lost. Once I re-link them it works fine. I don't have this issue with other apps installed to SD (yet)

I'm not sure if this is a bug or a problem with my SD. I had this same problem on RC5 too. If others have seen this then it's not my card.



Zaurus - pdaXrom / Fwvm + Mplayer Fullscreen Problem
« on: December 27, 2004, 08:37:54 pm »
I had this problem with RC5 when I installed the newer version of mplayer. mplayer works fine with the default matchbox wm, but with fvwm when I use a script that sets the resolution to 320X480 mplayer seems to want to place the fullscreen image as if it was still 640X480. See attached screenshot.

The script I'm using is:

Code: [Select]
xrandr -s 1
sleep 1
mplayer -fstype fullscreen -fs -ac mad  -really-quiet $1
sleep 1
xrandr -s 0
sleep 3

Anyone have an idea why the wm would display so differently?

For Sale / Wanted / For Sale: 5600- New With Wifi Card
« on: December 01, 2004, 08:25:59 am »
Hi, I've got a a new, still in shrink-wrapped box 5600. I'm including a slightly used SMC2642W Cf card. Selling on ->
Click here to see Amazon page

I'm in the US, but will ship overseas if buyer pays shipping & insurance. I'll use paypal for any sale that doesn't go through amazon. PM me through the forum if you're interested.


Zaurus - pdaXrom / Kismet & Socket CF
« on: October 20, 2004, 01:21:23 pm »
My problem with the Socket card is that although I can run the kismet GUI fine; it doesn't show any activity most of the time.  This occurs even though I'm standing next to an access point. Occassionally, it shows a few packets then seems to stop. Dmesg doesn't offer any relevant info. My SMC 2642w card works fine with my configuration. In RC-3 I had similar problem but it worked 30-50% of the time, seems to have gotten worse. Any ideas would be appreciated.


Zaurus - pdaXrom / Starting Kismet with Script
« on: September 07, 2004, 03:43:55 pm »
I don't understand shell operations well enough to figure out why I can't use a script to first set TERM=xterm-color and then launch Kismet  
Code: [Select]
# Kismet startup script
export TERM=xterm-color
xterm -e kismet monitor

This will launch Kismet fine, but not in the color mode.

The export command seems to only work within the current instance of xterm or aterm. There must be a way to set this globally or am I just missing something simple?  



Zaurus - pdaXrom / A plea for KO/PI compile
« on: August 25, 2004, 05:31:19 pm »
Can someone take pity on those of us that need their pdaXrom for PIM and can't get the compiler to work? The latest KO/PI (now called KDE PIM/PI) has an intergrated address book and many other refinements. I tried compiling the lastest source code but I couldn't get the pdaXrom SDK to even work on the example. I'm using the 1.63 version that sash compiled, but I really need my contacts too.

The source code is here

I'm sure there are others that would be thankful too.


Zaurus - pdaXrom / Puzzled by Network problem
« on: August 23, 2004, 11:52:22 am »
OK, I'm out of ideas.    I can't get my work PC to connect to my Z. I've never had any problems before with the other ROMs I've used.

I used the USB utility to setup the default IP address. Hotplug works after I plug in the cable ifconfig shows the correct IP address, and the icon for the network connection shows up in the sys tray of W2K. But I can't ping in either direction.

Anyone have any ideas of what I might try?  



Zaurus - pdaXrom / SSH & RC2
« on: August 19, 2004, 04:31:01 pm »
Hmm, can't seem to get ssh to work     Anyone else having trouble besides me?
I've got the usb set to network and there is a key in /ect/ssh.

Linux Issues / SSH Weirdness
« on: July 28, 2004, 06:18:42 pm »
OK, I just moved from Mandrake to Slackware 10 on my laptop. I'm able to ping my Z after
Code: [Select]
#ifconfig usb0 I try to
Code: [Select]
#ssh root@ it asks for a password. Well, I haven't set a password for root (yes, I know not good practice). So, I set a password, tried it again and same problem
Code: [Select]
root@'s password:
Permission denied, please try again

This used to work on Mandrake 10, not clear what I'm doing wrong  

Any suggestions? (other than going back to Mandrake 10)

I haven't messed with the sshd_config file yet, because since it used to work I don't want to mess it up further.


General Discussion / New wrinkle in PDA
« on: July 12, 2004, 10:46:38 pm »
Check this out multiple cpus in a PDA. Too bad it's not using linux


Sharp ROMs / SSH File transfer problem
« on: June 23, 2004, 10:03:47 am »
I'm using Winscp to move files back and forth from my work W2K pc to my Z (Cacko 1.21B). Transfers from the Z to the pc work fine, but large files going from my pc to the Z periodically error out "connection reset by peer" or "host has not responded in 15 seconds - Abort or Retry".  The error is inconsistant, sometimes 50 mg files will transfer fine, other times it will choke on 12 mg files. File less than 1 mg so far have never failed.

I've fiddled with the sshd-config file and set the ClientAlive setting up to 120 and the ClientAliveMaxcount to 10. On the Winscp side; file resume is disabled, I've tried the various Keepalive settings - send dummy protocol commands and send null ssh packets, neither setting has helped.

Anyone else had this problem?


Pages: 1 [2] 3