I'll post the APT error...
(I did read around the issue and tried all the likely obvious first-try fixes) but honestly I don't understand the error. so.. yeah.

Quote:

root@kindle:~# apt-get install valac
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
valac : Depends: valac-0.16 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

After several hours messing around and wiping the entire system once just to be sure I didn't mess up a step I still am none the wiser as to the issues real cause.

I know. I intentionally set up lower DPI in order to not make everything too big. It's quite common on mobile devices to specify lower DPI than it is in reality, as those devices are meant to be used from different distance than regular PC screens.

Quote:

Originally Posted by twobob

another change

/etc/mtab doesn't exist on the touch AFAICT

On PW it's also problematic, I should have removed it - it's just an artifact from some experiments.

Quote:

Originally Posted by twobob

hmm..

dpkg -i /root/libmokoui2-dev_0.3+bzr20080630-0ubuntu4_armel.deb

and

dpkg -i /root/libmokoui2-vala_0.3+bzr20080630-0ubuntu4_armel.deb

refuse to install as their dependencies refuse to install.

I'll post the APT error...
(I did read around the issue and tried all the likely obvious first-try fixes) but honestly I don't understand the error. so.. yeah.

After several hours messing around and wiping the entire system once just to be sure I didn't mess up a step I still am none the wiser as the the issue.

I tried the apt-get -f install etc... Any clues? : )

You don't need to install them, I've just uploaded them as they are results from building the same source package as libmokoui2, which is used by my patched matchbox-desktop.

BTW. There's a neat way to automatically install all needed dependencies:

dpkg --force-depends -i package.deb
apt-get -f install

I'll provide APT repository soon, so it will be all resolved automatically.

I know. I intentionally set up lower DPI in order to not make everything too big. It's quite common on mobile devices to specify lower DPI than it is in reality, as those devices are meant to be used from different distance than regular PC screens.
...
On PW it's also problematic, I should have removed it - it's just an artifact from some experiments.
...
You don't need to install them, I've just uploaded them as they are results from building the same source package as libmokoui2, which is used by my patched matchbox-desktop.
...
BTW. There's a neat way to automatically install all needed dependencies:

dpkg --force-depends -i package.deb
apt-get -f install

I'll provide APT repository soon, so it will be all resolved automatically.

Thanks for your feedback, I'm glad you got it to work!

AH good to know I will play with the dpi myself then.

Right I will stop messing about then and wait until you have something solid for me to latch into.

Quote:

Originally Posted by dos1

That's strange, just checked it here and it works. What does "locale" command say inside that terminal?

Hmm.. I will go check.
WHOOPS!...

Quote:

/dev/loop/debian 1290112 1502216 18014398509204344 123% /mnt/debian

tee hee hee. better start again. Think I fried it with Aptitude install. Ah well I don't need it now anyways. : )

I noticed that mounting image from /mnt/us leads to hangs on heavy IO usage, like aptitude does, so I'm using /mnt/base-us instead, without that additional proxy layer and it seems to be working well here. However, i've never seen anything like that

The program 'matchbox-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 249 error_code 148 request_code 144 minor_code 8)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

I noticed that mounting image from /mnt/us leads to hangs on heavy IO usage, like aptitude does, so I'm using /mnt/base-us instead, without that additional proxy layer and it seems to be working well here. However, i've never seen anything like that

seemingly, the reported capacity is about 25% under what you can actually CRAM in there

but it makes df -h do bad things

NOTE TO SELF: Next time back up the damn ext3 file AFTER you did the initial setup...

Where is that printed? I would guess that DISPLAY variable may be set incorrectly to :0 instead of :1 - it could try to run on Kindle's X server. But when starting it together with whole session I don't know how could that be possible...

Where is that printed? I would guess that DISPLAY variable may be set incorrectly to :0 instead of :1 - it could try to run on Kindle's X server. But when starting it together with whole session I don't know how could that be possible...