Found Reason For "wait 30 Sec" Remaining Forever Options

[selfabuse]

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

[guylhem]

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?

[gab74]

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

[adf]

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.

[selfabuse]

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)

[guylhem]

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

[adf]

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..).

[selfabuse]

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

[adf]

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

[adf]

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

[selfabuse]

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

[adf]

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.

[adf]

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