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.


Messages - Meanie

Pages: [1] 2 3 ... 187
1
Angstrom & OpenZaurus / Zaurus Kexecboot-enabled Kernels
« on: April 23, 2013, 02:08:56 am »
Quote from: InSearchOf
I've moved on to become an Apple Fanboy. I do iOS development now and I'm about 6 months away from putting an app in the AppStore.

Late

I'm waiting for my first macbook and who knows, I might actually like apple products. This is going to be my first so I hope it will be fun, otherwise it will be back to Windoze and Android.

2
C1000/3x00 General discussions / Usbapplet
« on: September 06, 2010, 08:55:54 am »
Quote from: Snappy
Hi folks, how has everyone been?  

Life has been too busy. No time to to develop anything new for the Zaurus, but I am still using it.

3
Zaurus - pdaXrom / Want Compiled Thread?
« on: September 06, 2010, 08:48:48 am »
Quote from: jcabrer
Does anyone know how to deal with this?  When I issue the make command, I'm getting Makefile:16: *** missing separator.  Stop.

The Makefile is peppered with various symbols like KE@ CC@ etc.

I'm sure SOMETHING needs to read these, but what that something is, I don't know.  Anyone?

you probably need to run configure first to generate the Makefile with the correct settings.

4
C1000/3x00 General discussions / Usbapplet
« on: August 13, 2010, 12:05:25 pm »
Quote from: xamindar
Quote from: xamindar
I'm using a powered usb hub. When I plug more than one usb drive into it only the first is mounted and shows in the files tab. I can mount a second one manually so I know they work. Just wondering why this applet and/or the automount package doesn't do more than one.
No one ever responded to this so I decided (2 years later ) to look into it myself. The /etc/hotplug/usb/usb-storage script is what is called when a drive is inserted and it will by default mount up to 4 drives (sda-sdd). If you connect one flash drive it will run through, check for a remove script and if it does not exist will then go ahead and mount the drive by looking for each of the four in turn. Then, once it is done mounting it will create a remove link under /var/run/usb/. If you then connect a second drive afterwards the script will run again and first check for any remove scripts which in this case will exist and therefore it will not try to mount anything else.
On the other hand, if I plug four flash drives into a usb hub and then afterwards plug that hub into the Zaurus the script will run and because there is no remove link yet it will run through and mount all four drives in the first go. Drives can be unmounted individually from the usb tray applet but ALL have to be physically disconnected from the zaurus before it will remove that remove link and allow mounting new drives again.
I'm not sure why whoever made this automounter (meanie?) decided to make it this way but it isn't very robust at all. Of course, I'm not very skilled with hotplug as the zaurus is the only linux I have that still uses it. Oh well, good enough as long as you understand how this usb-storage script is working. Maybe a simple change to the script to check if the drive is already mounted before trying to mount it instead of looking for that remove script would fix it. I'll try it but it may be that way for a reason.

I mainly put this here so in the future when I again try to figure this out I will remember where I left off.

Yeah that was my fault. Back then when I wrote it I was a Linux n00b.

5
C1000/3x00 General discussions / Joysticks And Keyboard *duplicate Post*
« on: August 13, 2010, 11:42:34 am »
Quote from: xamindar
Wow, no one ever replied to this? I was getting a little curious at getting a joystick to work with all the emulators in my zaurus. Anyone know where this joy2key zaurus package is? Anyone else ever use a joystick with their zaurus?

Tried it ages ago and gave up due to weird signal mappings.

6
Zaurus - pdaXrom / Need Help Finding Pdaxii13 For C3100
« on: August 08, 2010, 10:41:37 pm »
I have just been made aware that tyrannozaurus is no more
so the files for pdaXii13 are gone as well. Because of that I have uploaded my backup to the following location:
http://members.iinet.net.au/~wyso/myZaurus/pdaXii13/

7
Zaurus - pdaXrom / Pdaxii13 Install On C3100
« on: December 02, 2007, 09:27:47 pm »
Quote from: DaemonsGR
I know about the tgz.. I have problem with the update/init (boot) files... The page says to use the file from sally?!?

http://www.tyrannozaurus.com/feed/pdaXii13/akita/

8
Zaurus - pdaXrom / Pdaxii13v2
« on: December 02, 2007, 07:46:08 am »
Quote from: ZDevil
Would Meanie consider changing the versioning? pdaXii13v2 build 5.5 alpha 5.... isn't this a little bit bizarre?  

let me explain the versioning here to stop the confusion.

pdaXii13 is the pdaXrom beta1/beta3 compatible edition
pdaXiiv2 (or pdaXii13v2) is the next generation that is compatible with pdaXrom Latest packages, ie r197/r198. it is still backwards compatible with beta1/beta3 packages


the build number of pdaXii has always increased after each release. build 5.4.9 is the last of the pdaXii13(v1), after build 5.5.0, its pdaXii13v2 or pdaXiiv2
the v2 is to signify that the compatability against pdaXrom has changed. so the name would just be pdaXiiv2. build 5.5(.0) is probably the last pdaXii image since updates to the image are going to be via the upgrade feed. once you have gone to pdaXiiv2, updates are all done via the feed, ie by updating the packages rather than running a script to patch the system like in pdaXii13(v1)

the alpha5 only comes into play because that's the version number for the pdaXiiv2 updater. remember that the pdaXii13 flash installer (updater.sh) also has a build number but you don't quote that number when you say what version of pdaXii you have. similarly, the alpha5 or whichever number that follows is the build number for the pdaXiiv2 updater/upgrader.

hope this makes sense.

pdaXiiv2 is updated by running:

ipkg update
ipkg upgrade

the ipkg warning will be removed once the pdaXiiv2 updater is not alpha anymore.

9
Zaurus - pdaXrom / Pdaxrom Activity
« on: November 27, 2007, 01:37:15 am »
Quote from: stupkid
Are the embedded Debian binaries stripped? Just wondering how much space they take up and why they take up as much as they do.

debian takes up more space because all the man pages are included. also the apt-get subsystem is more sophisticated than the ipkg sub-system and thus stores more data for its package management system. You will see that the cache for that is several megs in size compared to several ks. there are lots of other files that the traditional zaurus distros stripped away because they waste space, but debian being 100% GNU/GPL compliant puts all the mandatory license files, readme files, etc... onto the disk when installed.

10
Debian / Problem #2 -- Remote Display With Ssh
« on: November 20, 2007, 01:48:08 am »
xhosts +?

11
Zaurus - pdaXrom / Vncserver For Pdaxii13
« on: November 19, 2007, 01:33:48 am »
Quote from: adf
Clearly not something I use much, but it occurred to me that I might want to run a vncserver on my Z. I thought the tight vnc ipk would do it--but it doesn't. I fugured I must have something that would suit--but it is all for qtopia roms.  The last relevent posts in the forums seem to be very old and unresolved. Is there a decent vnserver available for pdaX (ii13)?

pdaXii13 (full) comes with a vnc server (x11vnc) pre-installed. tightvnc for zaurus is the vnc client only.

12
Zaurus - pdaXrom / Pdaxii13v2
« on: November 15, 2007, 11:12:52 pm »
ok, alpha5 is out
nothing much changed except I enhanced the postinst script to try to guess whether you have base or full installed. at the moment, if you have rox and scim installed, it will assume you have pdaxii13 full and does the full upgrade and add some extra packages as well. if it does not find rox and scim, it will assume you have pdaXii13 base installed and only upgrade installed packages without adding extra packages.

in theory if, you have the pdaxiiv2-upgrade package installed already, you don't need to reinstall it unless you really want to. what this package is as follows:

replace /usr/bin/ipkg with a newer version (has not changed since alpha2 and not likely to change anymore)
replace /etc/ipkg.conf with updated feeds (this one is also unlikely to change and you might want to add your own custom feeds anyway)
replace /etc/issue (this one contains the version number of pdaXiiv2 and would be 5.5.0-alphaX)
add/replace /usr/lib/ipkg/ignored (this is where you put the names of packages you don't want upgraded)

the postinst script will then use ipkg upgrade and/or add packages that are listed in postinst script

as an alternate, you could simply update the above files like ipkg.conf and ignored before running ipkg update; ipkg upgrade

in effect, it will grab the latest packages from the pdaxiiv2 feed and upgrade your current packages with the newer ones from the feed (if it is newer)

13
Zaurus - pdaXrom / Installing Rox To Pdaxii13 Base
« on: November 15, 2007, 10:43:27 pm »
Quote from: liberated
I found that I really don't need everything in pdaXii13 full so i went for base instead. I do like rox however, but I can't get it to run.
After installing rox, rox-session and the missing dependecies gnome-vfs, dbus & dbus-glib I get the following error when I try to run rox:

/usr/apps/ROX-Filer/Linux-armv5tel/ROX-Filer: relocation error: /usr/lib/libgnomevfs-2.so.0: undefined symbol: g_thread_pool_set_sort_function

I guess there has been some version mismatch. Anyone know how to grab the right ones?

you installed libraries from the pdaxiiv2 feed without first upgrading your install to pdaxiiv2

to fix it, simply run ipkg upgrade

this would upgrade you to pdaXii13v2 (build 5.5.0). if you want to remain on build 5.4.9, then you will need to reinstall those packages you added, but from the pdaxii13 custom feed

14
Zaurus - pdaXrom / R198 First Touches And Experiences
« on: November 15, 2007, 10:35:52 pm »
Quote from: ecc_hy
Move 1.1beat3 to r198 on C1000

1. u-boot can be setup by CF, system can be setup by sd only. When system is in SD, the setup prog do not run autoboot.sh and get in SH prompt, and then carsh if you tray to run autoboot.sh manually.
2. Moving window by alt + mose is not working.
3. gtk open file dialog is too large to fit screen.
4. Try pstree after start x-windows. I found some process like bash, .xinitrc, running in a process add a few same name thread. I have meet same problem in pdaxrom 1.1beta3, but only scim-gtk-panel. After google search, it seems a glibc nptl problem. I am sure scim-gtk-panel use nptl.

Need help.

the latest gtk2 libraries combined with latest openbox resize dialog boxes correctly so they will fit onto the screen (these packages are part of pdaXiiv2 but should work with r198)

15
Zaurus - pdaXrom / R198 First Touches And Experiences
« on: November 15, 2007, 10:33:26 pm »
Quote from: walkman
Hi, as it seems to be useful and I am still missing a proper way to report bugs/issues, I am keeping this thread alive and using it as a bug-tracker.

[size=]MPlayer[/size]
- Install of gmplayer worked.
- try to run it, yields nothing...
- try the same from the command line and see that it needs libsdl.
BUG: dependency of mplayer on SDL package is missing
- SDL-sound installed (installed obviously also the core SDL package)
- gmplayer starts and everything is alright

- let's try to use mplayer from command line as I am not that fond of the GUI thingy:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']mplayer http://www.sky.fm/mp3/solopiano.mp3[/div]
BUG: for whatever reason mplayer starting script launches aterm. I do not have aterm installed, so it crashed.
- OK, let's install aterm
- mplayer now launches aterm, opens a new window but still crashes, i.e. does not play anything and aterm also exits...
- so let's take a look at the script and see that it actually tries to launch mplayer3.
- trying to launch mplayer3 yields success and everything plays well... almost...
ISSUE: The volume is too loud by default. Moving the slider on the volume applet in the panel is very sensitive. Below one half, the music is off and above moving the slider a little bit goes from silent to VERY loud.

[size=]CPU usage on blank screen[/size]
- as I would like to use my Z as an mp3 player (and want to wash dishes with Midnight Oil in my ears  ) I want to start mplayer, blank the screen, close the display and enjoy the music. And here some minor problems start...

Closing display
Question: I am not sure whether the display blanks when I close the display. Does it? When I tried to open it a bit and peak in, it was on... Not nice to battery...

Blank screen and CPU
- I started mplayer and everything played well. CPU was high, but the music was smooth and played well...
- blank the screen using PowerCtrl applet works, but somehow the music is not smooth anymore!
BUG: blanking the screen obviously does something with CPU usage. I see two possibilities:
  • blanking the screen leads to higher CPU usage for some reason (doubtful)
  • blanking the screen leads to CPU underclocking (why?)
I am not sure which one is right, but overclocking CPU before blanking the screen worked well and music played quite alright afterwards (still not smooth at times, but probably I overclocked it not enough)[/i]

[size=]PowerCtrl applet[/size]
- mb-applet-powerctrl is started from command line

ISSUE: on clicking on the icon in the panel an error message is issued to the command line:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']mb-applet-powerctrl failed to open /proc/driver/fr/corgi-bl[/div] What's that?
ISSUE: I noticed that volume control is completely missing in powerctrl applet. I remember it used to be there in pdaXii13v2.
BUG: CPU overclocking in powerctrl applet does not work:
- clicking on CPU clock frequency issues an error message: [div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']mb-applet-powerctrl failed to open /proc/ZAURUS/VCORE.[/div]
- CPU speed is set to 104Mhz which is obviously wrong.

you probably installed the mplayer package for pdaXii13 which is not meant for r198
the powectrl applet was intended for beta3/pdaXii13 which have a 2.4 kernel. i sorta ported it to r198 in so much that it could run and not crash, but not all the features have been ported/enabled  yet...

Pages: [1] 2 3 ... 187