Messages

1

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: April 27, 2005, 09:31:35 pm »

Whaaaaaaaaaaaaaaaaat ? atd is in our Opie image?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=77097\"][{POST_SNAPBACK}][/a][/div]

Ah, perhaps not then... Maybe I should actually try this image before advising on it

2

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: April 27, 2005, 07:10:53 am »

Has anyone figured out the permanent fix to this problem?

I removed the line that was suggested from the /etc/device_table file.  However, I tried setting an alarm in the qpe-alarmclock package and the Zaurus didn't wake up at the time specified.  When I turned on the Zaurus manually with the On/Off button 20 minutes after the alarm was scheduled to go off, the alarm sounded.

Also, now the thing doesn't suspend unless I actually press the On/Off button.

Any thoughts?

I'm using OZ 3.5.3 64-0 on my SL-5500.

Thanks,

--db
[div align=\"right\"][a href=\"index.php?act=findpost&pid=76316\"][{POST_SNAPBACK}][/a][/div]

A better fix, for opie users (gpe users need not apply, obviously):

- Restore the apm_bios line in device_table
- From a console, run 'killall -9 atd'

That should make things better and alarms should still work (I think). If they don't, replace 'atd' with 'apmd'. If someone could test this and report back, that'd be nice.

3

Angstrom & OpenZaurus / Dgen

« on: April 27, 2005, 07:06:59 am »

Argh, I've just realised you must be using a dgen from a non-OZ feed... If it isn't in the OZ feed already, please request it be built in the upgrades thread.

4

Angstrom & OpenZaurus / Dgen

« on: April 27, 2005, 07:05:18 am »

dgen 1.18 and 1.23 are already in OE, I included them myself. Your setup must be incorrect in some way, because I have tested both and they both load and run (but 1.23 segfaults loading roms (on both PC and Zaurus), and 1.18 seems to sit there doing nothing on loading a rom (on Zaurus, works fine on PC)).

I recommend you do something along the lines of:
ipkg-link umount <path>
ipkg remove libstdc++6 --force-depends
ipkg update
ipkg install -d <dest> libstdc++6 --force-overwrite
ipkg-link mount <path>

Replacing dest and path with the correct destination/path, assuming you didn't install to root.

Also, a tip to people wanting to add things to OE: Check that they aren't already there!

5

Angstrom & OpenZaurus / X Apps On Opie, Or Opie Apps On X

« on: April 27, 2005, 07:00:54 am »

Right, here's where I still don't get it, but in case I'm wrong above I'll save the long version till the next post. Here's the short version (or part of it)...

Why aren't [Qt/E] and [Qt running on X] the same thing as far as a program which uses Qt widgets is concerned?

Thankyou all for the very helpful replies
Simon
[div align=\"right\"][a href=\"index.php?act=findpost&pid=76983\"][{POST_SNAPBACK}][/a][/div]

Qt is currently at version 3.x (with 4.x in beta, I think) - If you're running Qt on X, you're more than likely running version 3, which isn't compatible with applications written for previous major versions (2.x, 1.x). Currently, Opie uses a heavily patched qt/e 2.x - In theory, Opie applications could be compiled for Qt on X, version 2.x, but due to all the patching that's happened on qt/e, as well as other changes in the way things are done with embedded Qt (I think), I don't think this is the case anymore.

When you run GPE, Qt is not involved at all - As far as I know, there isn't any Qt for X11 in any of the OZ feeds, so unless you go about compiling your own software, or some other clever solution, there is no way to run Opie or Qt applications under GPE/X11 using OZ.

Think of it like this:
GPE -> Gtk2 -> X11 -> fb (framebuffer)
Opie -> qt/e -> fb

If you run Xqt, an X-server that uses qt to display, you get:
X11 -> qt/e -> fb

6

Angstrom & OpenZaurus / 3.5.3 Upgrades

« on: April 27, 2005, 06:39:47 am »

I'd love to try a working package for gpe-nmf...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75731\"][{POST_SNAPBACK}][/a][/div]

Will do this as soon as I have time - in the mean time, there's gxine in the upgrades feed, which does a much better job, last I checked.

7

Angstrom & OpenZaurus / Ridiculous Bug on GPE

« on: April 24, 2005, 10:09:33 pm »

Alternatively, upgrade to OZ3.5.3, where this bug has been fixed

8

Angstrom & OpenZaurus / Dgen

« on: April 24, 2005, 09:09:37 pm »

libstdc++6 is indeed what you want, installing packages intended for other distributions/roms/versions will *not* work - Uninstall the file you got from killefiz and install the file lardman indicated... Unfortunately, dgen doesn't seem to work though  (I was the one that added it to OE) If you find differently, do please say.

9

Angstrom & OpenZaurus / Gpe Packages

« on: April 24, 2005, 09:03:46 pm »

OK, I'll have to take this up again because I got no real answers here.  Telling me to use ipkg is really no answer at all and defeats what a forum is for. The answer I would expect from all you experienced, over a thousand post people would be somewhat along these lines:

"If you flash your SL6000 with gpe and the latest 3.5.3 version you will be left with an almost unusable Zaurus.  To get it up to par with Opie or the Sharp ROM or Zynergy, you need to install the following packages:

- the following lib ipks...
- package such and such
- package bla bla bla....
...etc.

Do so using ipkg from a terminal issuing:

ipkg <options (and say what options!)> <.ipk file>

After doing this you may have a decent enough Zaurus."

Now THAT IS A FRIGGIN ANSWER!!!

So if  you guys don't  know the answer please be so kind as to point me to a section of this forum where I can get a real answer.  I see no NEWBIE section either.  The installation instructions at the OZ site don't even go past the instructions on how to flash the software, and I know that.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=76626\"][{POST_SNAPBACK}][/a][/div]

The answer is written quite plainly in the release notes for OZ 3.5.3. If you don't like it, help us work on the solution - complaining that the help people provide in their spare time isn't to your liking, doesn't help. Surprisingly enough.

10

Angstrom & OpenZaurus / Oz 3.5.3 Gpe-image

« on: April 19, 2005, 07:49:46 pm »

hi, just want to say im a relitively new oz user, but have had some time to use 3.5.2, and upgraded to 3.5.3 aparently days before the official release, so i thought id mention some issues that i have found...

im using 3.5.3 on a sl-5500

first: a flat out bug..

1: press and hold the "home" button on your zaurus..
2: press and hold the "space" button (inset button in the joystick like controller thingie..),

tada, the system crashes. or at the very least seems to, restarting requires flipping the battery switch and rebooting the device..

now this style of crash is important to note, since its been happing a lot in other places, scrolling through the text editor with a large text file, or even scrolling around in the k-browser..


another issue i noticed is sending a jpeg file from a cell phone over infared to the zaurus, the zaurus tries to display a thumbnail of the image, it fails miserably only displaying a grey box..


time, setting the time throught the launchers "get toime from network" feature, only seems to set the time for about a minute, then the clock updates to the previous incorrect time + 1 minute..


the usual package manager stuff, but you seem to know the issues with that already..

sorry for the extensive rant, and dont take it as an indictment in any way, ive tried the most recent zaurus rom, and while more stable.. its really not what i wanted, oz really is, or rather will be once i can rely on it.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75964\"][{POST_SNAPBACK}][/a][/div]

These don't sound like problems with GPE to me.

11

Angstrom & OpenZaurus / How To Sync With Gpe?

« on: April 19, 2005, 04:31:44 am »

I'm afraid GPE syncing is in a very immature state at the moment - There's a gpe plugin in multisync cvs, and feel free to give it a try, but last time I inquired it loses data going back and forth

12

Angstrom & OpenZaurus / Oz 3.5.3 Gpe-image

« on: April 17, 2005, 07:47:27 pm »

~Screen blanked as I was typing into the GPE text editor. Pressing a few keys restored it.

It's a known bug that if you hold down the right arrow key on collie it suspends - did you do this by any chance?

~Panel clock is pretty much unusable when the screen is rotated. May we have an option to have the bar either on the bottom or on the side? I can how having it on the side would be very handy, but an option would be great.

Have a look at the matchbox documentation at http://projects.o-hand.com/matchbox - Any contributions of patches or applications are welcome

~Audio Mixer - How do you close it? Takes up almost 1/2 the screen. Had to logout/in to get rid of it.

Don't use the MBOpus theme

~Autologin logs in as root. Can we select which user gets auto logged in?

Known bug - Will probably be fixed in the next release, possibly in the upgrades feed in the future

~Closing a root shell opend from a standard user resulted in the following error: urxvt: can't get colour '#969696' continue without. Selecting OK prompts for the root password.

I may fix this at some point, easy to fix bug

~Screen Setup - The default brightness level of 10 does not accurately reflect the true bright ness. Adjusting the brightness and then setting it back to 10 does not yeild the same level of brighness as before the change.
That said, the brighness does not stay at the requested value. It snaps back almost immediately back to 10 which is now kind of dark. The brighness applet does allow the setting to be changed.

Due to unreadable brightness status on collie - Needs to be fixed at kernel level

~Sokoban - Looks good, but the control pad does not follow the screen rotated state.

Missing keymaps, as said before - contributions welcome

~Feeds - None of them were listed in the package manager.

As said in the release notes, gpe-packagemanager is mostly unusable for collie and still in a very early state.

~SSh - Worked perfectly once I setup the USB0 interface on the Z. X forwarding worked well in most cases also.

Maybe you could post how you did this in the making connections/synchronisation threads?

I'll post a followup once I retest everything should the upgrade go well.

Good luck, and thanks for the feedback

13

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: April 16, 2005, 08:49:58 pm »

Donate a Zaurus serial cable to me and I'll fix it for the next release (collie only I'm afraid, unless I get given a poodle too..)

14

Angstrom & OpenZaurus / Collie 3.5.3

« on: April 16, 2005, 08:46:54 pm »

Afraid I don't know anything about bluetooth cards, but make sure the kernel flashed properly - If you stick the kernel on its own on a CF card (without an image), you can flash the kernel seperate without touching your rootfs - Make sure you've named it 'zImage' (quite possibly case-sensitive) and before you flash, make sure you've checked the md5sum to see that it matches those listed.

Hope that helps.

15

Angstrom & OpenZaurus / Oz 3.5.3 Gpe-image

« on: April 16, 2005, 08:42:49 pm »

The RAM usage in the systems information settings is a little misleading, you may have more free than is reported (it is always like that on my collie too, yet it seems to find enough memory to run minimo, prismstumbler, gpe-edit and rxvt, simultaneously, ok )