Re: Easy Debian Fremantle Beta Testing
 

PLease I need install easy debian, can you say the best version for N900?

Re: Easy Debian Fremantle Beta Testing
 

Define best. Squeeze is most tested and everything(tm) seems to be working as advertised. Unless it's too outdated to work for your needs, that is. Wheezy is most up-to-date with some irritating (albeit, limited to only few programs, namely GIMP, chromium, and gparted, as discovered to date) problems.

While I really, really appreciate sulu's heroic attempts to get Jessie working, even via his own words it sounds like "avoid touching with a long stick" - it doesn't fix any of Wheezy problems, and have probability of creating new ones, not to mention being royal pita to update. Sounds like an option only, if you're really desperate for some Jessie-dependant version/program.

/Estel

Re: Easy Debian Fremantle Beta Testing
 

I think he means which image to download. I suggest Estel's. It contains a lot of stuff I don't use (on the N900, that is - e.g. GIMP), but it is nicely polished and removing stuff is easy.

Re: Easy Debian Fremantle Beta Testing
 

Thanks!! I'll install Estel Version. :) I remember I installed this version with good experience last year.

Re: Easy Debian Fremantle Beta Testing
 

Well, I guess one man's desperation is another man's heroism. ;)

I was able to track down the performance issues I had in Jessie. For some reason xbindkeys, although having no configuration, caused periodic CPU usage spikes that were that short that they rarely even showed up in top. Since I don't ned xbindkeys in the image I just uninstalled it and everything was back to normal.
I didn't check if a non-empty configuration has the same effect.

Re: Easy Debian Fremantle Beta Testing
 

Easy Debian's xbindkeys "always" had habit of waking CPU unnecessary, even with proper config file. I discovered it hard way, long time ago, while "hunting" with Maemo's powertop for a elusive beast that was consuming my battery power.

Maemo's xbindkeys doesn't have such issues. No idea what's the reason for oddity in ED's, but I just switched to using one from Maemo's repos.

/Estel

Re: Easy Debian Fremantle Beta Testing
 

I tried to set up a new Wheezy/armhf image from scratch and I have good and bad news.

the good:
Gimp works without crashing when using the text tool.

the bad:
For some reason I'm unable to get keyboard support in lxde (via debbie it works fine in roxterm and gimp).
Just for reference, I also created an armel image and I have the same problems there, so I'm pretty sure it's not architecture-specific, but I'm missing some "magic".

what I did in detail:
1. I created a 1GB image on my Cubieboard2, formatted it with ext2 and installed Wheezy via debootstrap.
2. Once chrooted into the image I told apt not to install recommended and suggested packages by default. Maybe that's part of the problem, but if it is i'd like to know what I'm missing.
3. I installed these packages:4. I copied these scripts and binaries from my working Wheezy/armel image to the corresponding location in the new image:5. I copied the image to my N900.
6. /var/lock and /var/run/dbus were regular files, not a directory. I tried both leaving them this way as well as replacing them with directories for bind-mountpoints.
7. I ran debian-lxde, the gui came up and the mouse cursor works fine. However, the HW keyboard doesn't work at all.

In addition to the packages I installed right from the start I also tried with these packages installed, but without any change:
Input via xvkbd (onscreen keyboard) works partially. Letters work, digits and most special characters (/-) don't, just like during the jessie dist-upgrade in my working image [1]. libc6 and libc-bin are installed and after seeing this behavior I installed locales and locales-all.
I also tried the following which came from an early post of qole [2] in this thread, but I have the feeling (not more) that my problem is not actually/not only the keyboard focus:
When I start debian-lxde from xterm I get the messages in the textfile attached to this post.
For reference I also attached the output of my working armel image.

In the not_working output there is this line:If the latter is a directory in the image it really isn't there once the chroot is running when it is a directory. But when it's a file it doesn't make any difference, except that the line wil read like this instead:
A 2nd difference is this line in the not_working output:However, the file is there:But if I call it from within the lxde-desktop I get this error:Now, I know this isn't supposed to work, but I would have expected some other error message.
I guess this is the most likely candidate for the problem's reason, but I don't know how to fix it.


Then there's the last line which is only in the not_working output:Where is that variable supposed to come from, and is it essential for the keyboard to work?

I'm running out of ideas. Can somebody give me a hint please?


btw: a halfway recent kernel power (>v49) will be necessary for armhf to run stable, I guess due to the Thumb errata fixes missing in previous versions.

[1] http://talk.maemo.org/showpost.php?p...postcount=3030
[2] http://talk.maemo.org/showpost.php?p...3&postcount=75

Re: Easy Debian Fremantle Beta Testing
 

About mount errors: just create the directories in the chrooted filesystem.
Chroot into debian, mkdir the directory, exit chroot, chroot again.
Maybe it'll be a fix...

Re: Easy Debian Fremantle Beta Testing
 

I already tried that.

Re: Easy Debian Fremantle Beta Testing
 

You should recompile qobi-wmhint-fix for armhf or eventually try to symlink: ln -s /lib/ld-linux-armhf.so.3 /lib/ld-linux.so.3