Hello

I found why sometimes it failed: missing ldconfig

So when you use a new gui, do :
1) untar it and properly link it
2) log it as root
3) run ldconfig

Then either reset or log out. qtopia will start only if you are not logged in. (think about this feature a safe way to hack) . If your console crashes (or an app hangs) a long press on "record" will open a new one.

I strongly suggest to start up a network connection manually and monitor /var/log/qtopia.log for applications log files. If they crash they'll tell you why in this file. do tail -f /var/log/qtopia.log to monitor it.

Regarding external keyboard, it's mostly working. Today I tested my bluetooth mouse and keyboard.

I only have the following problems:
- redraw of the mouse pointer confuses some apps like freenoteqt
- a/fn confusion (I really need C3000/c1000 files ! I hope someone will provide them)
- the blue Fn button on the stowaway bt keyboard turns light off (my fault - mapped 0x1052 )
- the arrows are rotated

They can be fixed.

On the Gui problems, the only serious remaining bug is the date/clock app. I simply don't understand why it fails. Maybe it must be run as root?

Could testers please concentrate on the console mode bugs? The gui problems will hopefully be fixed with the next release, which will ship with a minimal qtopia 1.5. It will also include a development environment module based on the devimage 1.6 put in the proper places instead of symlinked all over.

PS: I would be interested in any "size reduction" proposal for the base system. 12 Mb is still too much - it should be even more minimal

on the size issue (you've probably already thought of this) maybe cut down the number of modules and provide a means for a second modules location on external flash? same w/ library files in lib vs a possible extyernal /usr/lib or usr/share lib..or something along those lines? what about UCLX (undertow.net, I think) compression of the executables? a little trimming and some compression or even just compression, should help.

On the requested-not-to-be-concentrated-on gui stuff. it looks like the cacko setup doesn't redraw the desktop. I'll ldconfig and look at the path... ideas would be appre ciated

hello

yes the modules are big. yet if the setup is too minimal, ppl complain they miss some. maybe we could provide them separately as you suggest, so ppl would download what they need.

I'm not sure compression is the way to go. it may be too slow. There may be unneeded stuff, like the fbvnc I forgot.

hmmm. I was thinking maybe monolithic kernels for the different models based on hardware.... the zImage-L not having bluetooth built in for example... that way only the sd module would need to be on internal flash..and everything will work. would allow offloading of a bigger tree of modules, and less local space required..maybe? a fat basic monolithic kernel runs about 1.2-1.3 megs. 4-500k bigger than a basic modular one. worth it?

re-thinking my uclx idea... isn't stuff on the internal memory already compressed anyway?

could be done. I like modules to recompile them separately and test stuff in a working kernel, but it could be good. Now the question is which modules will make it

Please add at least the BT modules for the CF cards! :-)

Adalberto

If they (excpt the sd/mmc) are going on sd as many as yyou like... all of 'em
if you mean in the monolithic kernel?

pretty much everything you compile as a module plus maybe ipv6 minus z specific stuff.. no bluetooth for the l no wifi nor bleutooth for the n (does anyone have an n?)ext2 support has to be in the kernel if you do things this way might as well do vfat too.

I got qtopia 1.5 running.

gui issue: the gui crashes on zoomed apps.

console issue. how do I get wireless going? I managed to turn on the prism2 usb via usbctl.. but couldn't get networking going.

Of course, I haven't messed w/ iwconfig much lately. maybe ifup/down should be included?

I got qtopia 1.5 running too !
infos : yes gui crashes on zoomed apps
Time ad date hung up when i try to change time from a city to another....
try to set-up network using gui but it fails......

gab74, adf - I hadn't experienced the zoom bug - thanks a lot for the bug report!

Actually I'm working on the date problem. No idea why it happens- maybe it's due to my half vanilla sharp rom/half cacko mixed bred :-) Will start from scratch with a vanilla 1.5

Today I got A/FN key working thanks to an ugly hack in the kernel. My axim external keyboard (bluetooth) now works like a charm, and USB keyboard is fine too, so I guess keyboard problems are gone (besides arrows rotation stuff - will fix that in 5 minutes)

I would like to fix the qtopia 1.5 problems before the next release. I'll see if I have sometime to do that today.

I'm also trying to set up a softfloat toolchain to work on the post 1.5 release which hopefully will include lots of opie/oz goodies and speed while remaining compatible with sharp apps thanks to ugly LD_PRELOAD hacks.

guylhem, how can i configure wlan working ? Is your network qtopia gui working ?

Mine does, but I fixed may bugs since the release.

Try the safe way - the following script:

#!/bin/sh

/sbin/modprobe p80211
/sbin/modprobe prism2_usb

/sbin/usbctl on 1

/bin/sleep 1

/sbin/wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
/sbin/wlanctl-ng wlan0 lnxreq_autojoin ssid=externe.net authtype=opensystem
/sbin/ifconfig wlan0 10.3.0.76 netmask 255.255.255.0
/sbin/route add default gw 10.3.0.1

# replace externe.net by your wifi SSID, 10.3.0.76 by your IP,10.3.0.1 by your server


Besides that, anything else you miss or you would like to see fixed in the next version?

well.. i kinda like an icon for this---

I assume "ANY" will work for SSID?

what about the default gateway? if I don't know its ip, (It happens) how do I set that to auto?

ifconfig wlan0 dhcp work?

Proxy settings?



aside from this, maybe a good look at what would make up the essential 57 meg rom? a good enough selection that it might be "good" without sd or cf? Off the top of my head, here is stuff I think most of us use:


pim
kismet or wellenreiter
browser, or room left for one (though included opera 7.55 would be cool.and the devices come with an opera license...right?)
calculator
spreadsheet?
word processor/or good gui text editor (tinykate?).
tree explorer
media player. (mplayer based?)
maybe a good playlist player as well?
email client
nano (I'll put it on anyway-- I really don't like vi, but that is a different discussion)
handwriting?
Xqt? or room for it? (would make the pocket workstation guys really happy)
Java
good sytem settings guis (the sharp stuff seems ok to me)


What is the indispensible stuff? might as well try to make the package selection really handy. the repartitioning makes it seem that possibly everything needed could go internally... and given your approach those who want their system on flash can do it easily.

any clue as to how to use a usbmouse in xqt without the bottom bar from Qtopia staying on top would probably be appreciated (certainly by the pocketworkstation and x-forwarding fans). I have no idea if that can even be done, though.

the softfloated stuff is definitley something to look forward to. As is Qtopia 2.1

Here's my proposed roadmap :
- I will release a embedix like + sharp qtopia 1.5 rom hopefully with everything working this time.
If it works this will be the last release

- Then I'll work on porting 3.5.3 to have everything at least as good (ie make sure hancom opera etc work, no function is failing etc.) that's when softfloat will be added

- Then qtopia 2.1, which will require the compatibility (hancom opera etc.) to be further improved

adf, would you like to help? If you're ok, you could be the official "packager" ie who does the tests and the nandbackup.

guylhem - I read that you were going to be adding Qtopia to the rom in the future. Do you also plan on releasing future versions in a Qtopia-free flavor? I've been using your rom as a base to try and get a native X server and some other stuff running on the Zaurus, and have no real desire to run Qtopia if I don't have to. If you have your source for this rom available somewhere, I suppose I could just use that and go off in my own direction if it doesn't quite jive with your roadmap, but I don't have too much free time to hack on zaurus stuff, and it seems to make more sense to not duplicate work.

thanks!

-r

hello

Of course 2 versions can be maintained in parallel. Removing /opt/QtPalmtop is no big deal :-)

In fact I'd be very interested in a common base with multiple frontend. How successful have you been with X so far? Is it something one may test?

Guylhem if you want a tester here i am ! let me know...

I agree. an xserver or x-server plus basic windowmanager/browser/etc would make a nice rom.

Of course I still think that it should be setup so that the rom can be installed to the internal flash and be functional.

has anyone tried getting debtools &tc from woody on here? that would give 2.95 gcc compatability and a huge package base..all that would remain woud be confiureing debian's x-server. (I know, I keep saying this)

pdaxrom is supposedly being brought to the 6k. would it be easiest to take that, or OZ X stuff and treat it the way Qtopia is being treated? Since OZ has all the necessary packages already sitting in a feed, this might be handy--if the kernel will run the x-server, or can be patched or given modules to do so.
This approach would dovetail nicely with the projected soft-float system.

I only just installed the rom last night (work keeps me *very* busy). I happened to have a spare 512mb SD card that I had been using for pocketworkstation before I got my 1gb card, so I installed the rom, got the network up, chrooted to /mnt/card/debroot and did apt-get install x-window-system. A startx fails at 'cannot open virtual console n (no such file or directory)' That's about as far as I got before something at the office blew up that needed my attention. I'm about to sit down and take another stab at it right now, though. I think that error should be pretty trivial to fix, I just suspect that a worse error is lurking behind it. I'll start hacking, and report back with what I find


(PS - pocketworkstation uses packages from debian testing, so I don't know if I'm going to run in to some GCC issues down the line, but a SD card with testing is what I have, so I figure I'll work with this, and worry about that problem if/when it comes up)

Virtual console problem? Check the device in /dev. convention changes...
Also feel free to use "rec" to open a couple of console and chvt between them. For some reason qtopia is confused if I start it from another vc. I have to chvt 1

I have seen that before too.
I had thought it was an error consequent to the chroot thing... I have gotten the same error on sharp rom (I think it was sharprom) doing the same thing.

If you are right (and man do I hope you are) and it is trivial..and you get debian's x configured in the chrrot environment, then please post. I have been interested in getting exactly this working for a while.

of course, my attempts in that direction have only gone so far as "whatta ya mean chvt unknown command...?"

On the other hand kmeaw posted an alternate kdrive in gpe bugs (there is a link on the oz 3.5.3 bug thread on zug) that might be compiled to suit this project if the deb thing doesn't work.

edit: If you find gcc probs, you can just change your sources list to stable from testing. stable is still woody. no big thing at all,I think (though on reflection I have never "downgraded" that way before... maybe it willl be a mess..).

I'm pretty sure there was some reason that pocketworkstation had to use testing. I don't remember why right now, but I'm sure if I switch down to woody, I'll probally remember real quick, right after it trashes all my stuff . I got past the virtual console issue (A couple makedevs fixed that right up) now it's saying it can't find a valid screen. That's probally just an error in my XF86Config-4. For some reason I can get the zaurus to connect to my AP at my office with no problem via the command line, but it absolutley won't connect to the one at my house. They even use the same WEP key and everything. Makes it much more difficult to work on the thing at home, because I can't telnet in to it, and I"m stuck with that tiny keyboard. Anyway, I'm back at the office, where I can telnet in to it and use a full size keyboard, so hopefully I can get this XF86Config-4 thing ironed out.

-ross

Excellent!
I agree, the screen shouldn't pose too much of a problem.
Keep us posted

er..... what about the touchscreen? Will that pose much of a problem in your XF86config?

sure might. I'm just trying to get it started in the first place right now. I'm not quite sure what video driver to use in X. I figured I'd start with VESA and work from there, but i'm not having any luck yet. I hadn't used the SD card that i'm testing with in a few months, so as it turns out my apt-cache was old. I did an update, and there's a newer xfree package available, so I set it to do an apt-get upgrade, but it took from about 10am yesterday until I left work at 4. I forgot the damn thing at home today, so it looks like I don't do too much more until Wednesday. I'm fairly certain I'll be able to get it running. When debian gives me problems, it just makes me that much more determined to solve them.

-ross

fbdev. use the fbdev x server. 60 hx refresh

modelines for 480x640 60 and 640x480 60 and probably 240x320 and 320x240 too

I'm working with the vnc setup. having a hell of a time with keymapping (klaus set the keymaps up to handle the screwy sharp setup) it is pretty snappy--- supposedly the shared mem vnc will go at 190 fps at 1:1 on a z. this also leaves a nice vncviewer to talk to to other boxes.

any ideas on the keymap thing? pop in guylhems tosa keymap into the xkeymap (where is that btw?)
suggestions.

btw... had some probs setting the PW vnc on qtopia 2.1. It was handy though, because it showed me that the touchscreen tty is read as a (gpm, I think) mouse. that might be of use to you.

I'll be happy to do what I can on the packaging

atm I'm trying to remeber how to make your new kernel suspend.... LMAO