Messages

16

Angstrom & OpenZaurus / Keymap

« on: July 24, 2006, 01:52:23 am »

Why aren't fn-z fn-x fn-c and fn-v by default mapped to anything useful in gpe?

In opie fn-shift-c is ctrl-c and fn-z is ctrl-z.

I think those 2 are very useful to have.  I'm pretty sure fn-shift was equal to ctrl most of the time so you got a lot of ctrl sequences.

17

Angstrom & OpenZaurus / Keymap

« on: July 21, 2006, 02:36:12 pm »

You'll need to edit the keymap-2.4.map file.

Try a google search for xmodmap to tell you how to change the contents of the .map file,


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

On Collie w/ 2.4 kernel, Fn+SPACE produces "|", Fn+C = Ctrl-C.
Fn+Z may or may not produce Ctrl-Z
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136007\"][{POST_SNAPBACK}][/a][/div]

you were right about fn+space making "|" , but i can't get Ctrl-C or Ctrl-Z or Ctrl-G to work in the terminal.  They print out "~" when i use fn+C or fn+Z.

on opie it worked.  i had to use shift+fn+c for ctrl-c though, but fn+z was ctrl-z

how about for you? (on gpe)

18

Angstrom & OpenZaurus / Stty Error At Boot

« on: July 21, 2006, 08:48:12 am »

I get a few of these messages on boot since I upgraded to 3.5.4 (collie.)  It is the very first thing that shows up when I boot.  I think it might be coming from AltBoot, but I'm not sure.

Code: [Select]

stty: standard input: bad file descriptor
AltBoot seems to work ok, and i'm not sure what it's trying to do that gives this error, but I thought I'd bring it up just in case.

19

Angstrom & OpenZaurus / Can I Switch To Console View?

« on: July 21, 2006, 08:13:33 am »

There's a key sequence you do in opie to switch to the console (and then another one to return to opie.)  I think it's calendar+left or fn+left or something like that (anyone remember?)

Does GPE have a similar ability?

Thanks!

P.S.  I am running 3.5.4 / gpe 2.7 on a collie

20

Angstrom & OpenZaurus / Keymap

« on: July 21, 2006, 08:09:37 am »

Hi, I'm running OZ 3.5.4 and GPE 2.7 for Collie.  I can't find a good keymap file for this build.  I would like to have a mapping for the vertical pipe and Ctrl-C and Ctrl-Z would be nice.  Maybe something like the mapping for opie.

I found "keymap-2.4.map" and "keymap-2.6.map" in /etc  and i ran the 2.4 one with loadkeys and it had no errors, but I still can't get the keys I want.  Then  I found this topic  which has an attached file and I ran that (with xmodmap.)  That aborted because of lot of errors.

I'm obviously very inexperienced with key mapping, so any help would be appreciated.

thank you!

21

Angstrom & OpenZaurus / Syncing The Sd Card Properly

« on: July 03, 2006, 02:54:42 am »

What if I'm using altboot to boot off of SD, will the SD card always be "busy" or is there a way to umount before you reboot?

Another similar topic is what are you supposed to do if your Z freezes up?  Before, I would reboot by setting the switch the "replace battery" and pressing the button inside briefly.  Then I bypass opie and run chkfs.ext2 on the SD card (which isn't in any installation I know of, so I put it in my custom ROM, because you have to run it from ROM i think.)

I'm probably going to make a very simple rootfs with just altboot, no windows manager, and some other basics, including chkfs.ext2 (because usually if im there it's because the SD is corrupted because of a freeze up.)  Then I will have two root installations on the SD one for GPE and one for OPIE.

So what do you do to get back to the altboot menu while properly syncing the SD (or CF) card, and do you know of a better way to fix a corrupt FS if the Zaurus froze than with chkfs.ext2?

I would like it to flag the FS on the SD as possibly bad if it didnt get shutdown properly and then the next startup run a check/fix on the FS.  Can someone tell me how to set that up?

Thank you so much,

BeKind

PS I have a collie with OZ 3.5.4 on it

22

Angstrom & OpenZaurus / Altboot: "loop Image" Vs. "direct Install"

« on: June 06, 2006, 12:27:54 am »

Hi, everyone,

I'm about to upgrade to 3.5.4 with Opie on my Collie.  I want to use altboot for the main reason that I don't like ipkg-link.

I read that FAQ and I think I get that a "direct install" means that the entire SD card is looked at as the root filesystem, and the "loop image" means that the rootfs is in the image file it creates on your card, and then the leftover space is found in /mnt/card.

They suggest: "If you go for a loop-image you should choose a size greater than 100Mb."  A boot image is usually 14 MB.  Do they suggest a bigger size so that you can install more things directly into the image?

I want to install everything "to root" instead of "to SD" from now on.  Let's say I use a loop image and then I start uninstalling and installing packages, changing the rootfs around.  Does that change the image file?  If I make the file 100Mb is that my size limit for installing packages on "root?"

Thanks,

23

Angstrom & OpenZaurus / Altboot Or Ipkg-link? (the 3 Hassles Of Ipkg)

« on: June 01, 2006, 03:30:21 am »

Ok, so what I get from that, is that once you have AltBoot installed and booting from your SD card, then the flash doesn't get used any more (unless you change the option in AltBoot to boot from the flash again.)

That sounds fine to me.  Then all you need on the ROM(flash)(16MB) is AltBoot itself and enough of an O/S that you can fall back on it if the SD card gets messed up.  So I'm taking up 16 (14) more MB by using AltBoot because all the stuff I had on the flash I need on the SD now, too.  That isn't a problem for me, the SD i have is .5 GB, so I'm not worried about that space.

Does that sounds right?

24

Angstrom & OpenZaurus / Altboot Or Ipkg-link? (the 3 Hassles Of Ipkg)

« on: June 01, 2006, 12:00:18 am »

Quick question about AltBoot.

Let's say you flash a rootfs onto your Z, and then you tell AltBoot to boot from the SD.  Does that mean you have to copy what was on the 16 MB of ROM (the rootfs) onto the SD and that the 16 MB of ROM never gets used any more?

--BeKind

25

Angstrom & OpenZaurus / Altboot Or Ipkg-link? (the 3 Hassles Of Ipkg)

« on: May 31, 2006, 07:00:11 pm »

I've been reading a little about Altboot, and it seems pretty cool.

I have used ipkg to install everything on SD, so i'm able to use all 64 MB on my collie for system memory.

One problem I have with ipkg-link is sometimes it does stupid things, and you have to go back and make or fix some links by hand.  One example is I tried to install some glossaries for QPSword and it can't do it automatically because the data directory is already a link, and it's trying to make links inside of links, so I have to do it by hand.

Also, I get the problem that sometimes if my Z freezes and I have to flip the switch on the back, some of the links will disappear and I have to run ipkg-link again on some of the packages.  I've always wondered why that is, and what we can do to fix it?  Does anyone else experience this problem?  Those links are on the ROM they shouldn't go away just because you do a soft reboot, but they do.  Why?

Another nuisance is that if you try to run the graphical package manager (which I don't because of this) when you install a new package it goes back and redoes the links for EVERYTHING which takes way too long.

So because of the 3 hassles I just mentioned, I am open to another option, and Altboot might be pretty good.

OR

Has anyone found good solutions to any of those hassles, and decided to keep with ipkg-link?


Obviously if you are using multiple-boot options, you need Altboot, but what about someone like me who is just trying to avoid those hassles with ipkg-link, is it worth it to use Altboot instead?  (Will it even help?)

26

Angstrom & OpenZaurus / Upgrade To 3.5.4, Sticking To My Custom Initrd.bin

« on: May 31, 2006, 06:40:18 pm »

Hi,

I am running 3.5.3 with the r21 kernel on SL-5500.  I am considering upgrading to 3.5.4.  My extra consideration is that I have selected my own programs that I want on my rootfs, and so I have my custom initrd.bin that I keep.

So, what is my best option?  Can I just change the feed to 3.5.4 and then run ipkg update/ ipkg upgrade, or do I actually have to flash something?  Is the kernel the same as r21, and if not, can I flash the kernel only and then run ipkg upgrade to 3.5.4?  Or is the quickest way, to reflash everything and then reorganize the rootfs and remake my custom initrd.bin with the new upgraded packages?

Thank you,

Adam

27

Angstrom & OpenZaurus / Exiting Opie Using Keys/buttons Only

« on: October 30, 2005, 07:52:52 pm »

Well.  I turned off the Z and went to bed.  When I woke up in the morning I turned it on and it was booting up again, and the filsystem checked out ok.

Still, I know how to get back into opie from the terminal, but is there a key combo to get out to the terminal, or does this not exist?

 

28

Angstrom & OpenZaurus / Exiting Opie Using Keys/buttons Only

« on: October 29, 2005, 08:33:28 pm »

Hi,

I have this friend who accidently sent a -9 signal to qpe and the screen froze.  Now he would like to restart opie, without doing a hard reset, because he has a card he would like to sync before doing that.

Do you have any advice on how to achieve the same effect as going to the terminal from opie by using only keystrokes or buttons?  (I tried calendar+left and calendar+right to no avail)  or does my friend just have to tap the reset button in the battery area?

 

29

Angstrom & OpenZaurus / Ipkg-link Mount Overwrites Links To Runcompat

« on: July 05, 2005, 10:28:45 pm »

Whenever I run packagemanager and install a new package, and consequently run ipkg-link mount, it changes all of my links in opt/qtpalmtop/bin that were linking to runcompat.

Is there something I can do to stop this from happening every time I run ipkg-link mount, so that I don't have to run makecompat again on all my software that uses the alternate libs?

30

Angstrom & OpenZaurus / collie and kernel from 3.5.3 upgrades

« on: July 05, 2005, 02:19:10 am »

To remove the warning, you need to remove/rename a script in /etc/init.d/ (checkver something like that - no Z to hand atm I'm afraid).

OK but how would you do that when the Z will not go passed the sleep message.

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

works fine for me, after a minute or two it continues booting.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86118\"][{POST_SNAPBACK}][/a][/div]

I want to upgrade the 3.5.3 kernel to the june 30 update (collie 64-0) by hrw, but I am afraid my Z will lock up on boot like this and not continue.  What do I need to do to insure this doesn't happen?