Topics

1

Angstrom & OpenZaurus / Where Are The Sd Mount Options?

« on: September 14, 2006, 01:35:48 am »

Hi,

OZ 3.5.4, collie

The /etc/fstab options for mounting the SD card only get used when i run the mount command explicitly.  Where does it get its options when mount occurs due to resuming from a suspend or popping in the card?  Are these options editable?

Thanks,

Bekind

2

Angstrom & OpenZaurus / What To Do When Z Freezes

« on: September 05, 2006, 02:09:32 am »

Hi,

Collie, OZ 3.5.4

I use altboot to pivot the root to SD.  The problem is when a freeze happens and I have to do a reset, often the libraries that were in use at the time of the freeze get corrupted.  The only thing I can think of to do then is reinstall the loop file which takes some time.  Is there a better way to handle this, or is pivoting root doomed because of how common file corruption is with the SD?

thanks

3

Angstrom & OpenZaurus / Unsupported Card Needs To Be Bound

« on: August 13, 2006, 10:37:47 pm »

OZ 3.5.4 , collie

I just barely ran ipkg upgrade and now my network card that used to work is labeled as "unsupported" and when I 'configure' it, it says "Caution:  This card is not yet recognized.. valid binding," and no matter what driver I select from the drop down menu, the value always goes back to "none" the next time I go into the dialog, and the card remains "unsupported."

4

Angstrom & OpenZaurus / Mount Options

« on: August 13, 2006, 07:53:07 pm »

oz 3.5.4 , collie

In the /etc/fstab file that comes with OZ 3.5.4, both the cf and sd card mount options include 'user' which will give an error.  So I took it out.

but... it doesnt really matter because those options are hardly ever used.  It looks elsewhere for options, and I'm not sure where, because usually the sd card is mount with just 'rw'.  Only if I run mount -a from the command line do I get my noatime,sync options.

Is there somewhere I can specify mount options that will get used for a case like lets say I umount and then pop the card back in (which automatically mounts it), or for if I reset the Z?

5

Angstrom & OpenZaurus / Why No More Ctrl Keys In 3.5.4?

« on: August 13, 2006, 08:01:25 am »

OZ 3.5.4 collie

I upgraded to 3.5.4, and now from the non graphical run level I can't get ctrl-c or ctrl-z to work anymore.  I used to be able to press fn-z for ctrl-z and fn-shift-c (i think it was) for ctrl-c.  If I run console from inside of opie, fn-z and fn-c work, but in a console in gpe they don't.

What am I supposed to do if I do something like type 'ping' and accidentally leave off the -c?  I've been flipping the reset switch in the back, but there must be a better way.

[edit] there is no -c in busybox ping, so that really screws that.  btw ping is just an example of something i'm used to using ctrl-c with ...  theres also 'top' and many more.  also, if i type something in and i change my mind, i like to press ctrl-c to get a fresh line quickly.

6

Angstrom & OpenZaurus / Ipkg Upgrade, No Options

« on: August 13, 2006, 07:54:46 am »

OZ 3.5.4 collie

Hi,

In the help document for ipkg, it says that if you run ipkg upgrade it will upgrade your installed packages.  I ran it and it started installing packages that I had removed.

7

Angstrom & OpenZaurus / Ipkg Upgrade From The Package Manager

« on: August 13, 2006, 07:41:04 am »

3.5.4, collie

I tried to "upgrade" only dropbear using opie's package manager, and the package manager showed a list with just dropbear in it and said it would upgrade the following items.  I clicked proceed.  Instead it went through and upgraded everything, and when it reached libqte2 opie froze and I had to reboot.  It left  libqte.so.2 truncated, so opie would no longer run.

I have two suggestions:

1.  upgrade should do what it says its going to do

2.  there shouldnt be the option to run upgrade from package manager because it is possibly going to freeze opie and leave some files truncated.

8

Angstrom & OpenZaurus / E2fsck With Altboot

« on: August 13, 2006, 04:58:36 am »

Hi,

I have OZ 3.5.4 on collie.

I'm using altboot to boot a root file system from my SD card.  Is there any way to have it run e2fsck before mounting the SD card (on the ROM i have installed e2fsck for when the SD card messes up), or is that asking too much from altboot?

9

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.

10

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

11

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!

12

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

13

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,

14

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

15

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