Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 5 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 17 hrs ago - more...
|
2011-08-10
, 13:55
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#2362
|
Not sure if this problem has already been solved since I've not been here for quite some time but after some tinkering during the weekend I finally was able to fully dist-upgrade the m5v3e image to Squeeze.
There were a lot of failed attempts and reboots involved but I finally succeeded by only upgrading small portions of packages (via debbie and aptitude) of 30-50MB download volume at a time including manual fixes for some broken packages and a final dist-upgrade when almost everything was done.
I did that because I noticed that some applications (e.g. nload, audacity) were silently broken in the Lenny/Squeeze mix and because I don't like mixed systems.
However there are 3 (or 4) problems I've noticed so far:
1. Loading LXDE takes much longer now, maybe twice the time. I guess that's due to increased RAM requirements. So far I have no idea what to do about that. Once started the system seems to run as fast as usual.
2. A pcmanfm window gets started automatically when LXDE is loaded. I guess the autostart got messed up somehow.
3. The keyboard is messed up. Most keys work fine but according to xev the left cursor (qwerty layout) produces Super_R and so on. I guess that can easily be fixed via xmodmap. I didn't even check so far if the existing xmodmaprc is loaded or not.
(4.) The LXDE logout dialogue doesn't show shutdown or reboot anymore. I don't consider that to be a real problem since logout is still present and working and fully sufficient in a chroot.
There were a lot of failed attempts and reboots involved but I finally succeeded by only upgrading small portions of packages (via debbie and aptitude) of 30-50MB download volume at a time including manual fixes for some broken packages and a final dist-upgrade when almost everything was done.
I did that because I noticed that some applications (e.g. nload, audacity) were silently broken in the Lenny/Squeeze mix and because I don't like mixed systems.
However there are 3 (or 4) problems I've noticed so far:
1. Loading LXDE takes much longer now, maybe twice the time. I guess that's due to increased RAM requirements. So far I have no idea what to do about that. Once started the system seems to run as fast as usual.
2. A pcmanfm window gets started automatically when LXDE is loaded. I guess the autostart got messed up somehow.
3. The keyboard is messed up. Most keys work fine but according to xev the left cursor (qwerty layout) produces Super_R and so on. I guess that can easily be fixed via xmodmap. I didn't even check so far if the existing xmodmaprc is loaded or not.
(4.) The LXDE logout dialogue doesn't show shutdown or reboot anymore. I don't consider that to be a real problem since logout is still present and working and fully sufficient in a chroot.
|
|
2011-08-15
, 13:32
|
|
Posts: 67 |
Thanked: 34 times |
Joined on Apr 2011
@ Co. Wicklow, Ireland
|
#2363
|
Hi all,
I went to install EasyDebian so I could have a look at and play with some extra packages.
I downloaded the chroot package and then ran it.
downloaded the 300MB file (version e) to my MyDocs all went well (but took 3 hours to download!).
All finished so I went to run the LXDE and get an error message.
EZ-CHROOT ERROR
Mount failure!
/home/user/MyDocs/debian-m5-v3e.img.ext2 failed to mount on loop0
mount: mounting /dev/loop0 on /.debian failed: No such file or directory
Any suggestions as to want went wrong and how to fix it?
I am running CSSU on PR1.3 and also have U-Boot installed.
Mike
I went to install EasyDebian so I could have a look at and play with some extra packages.
I downloaded the chroot package and then ran it.
downloaded the 300MB file (version e) to my MyDocs all went well (but took 3 hours to download!).
All finished so I went to run the LXDE and get an error message.
EZ-CHROOT ERROR
Mount failure!
/home/user/MyDocs/debian-m5-v3e.img.ext2 failed to mount on loop0
mount: mounting /dev/loop0 on /.debian failed: No such file or directory
Any suggestions as to want went wrong and how to fix it?
I am running CSSU on PR1.3 and also have U-Boot installed.
Mike
|
|
2011-08-15
, 14:39
|
|
Posts: 1,873 |
Thanked: 4,529 times |
Joined on Mar 2010
@ North Potomac MD
|
#2364
|
Originally Posted by mmarks
Hi, Did you check the Install instructions on the Easy Debian Wiki?
Hi all,
I went to install EasyDebian so I could have a look at and play with some extra packages.
I downloaded the chroot package and then ran it.
downloaded the 300MB file (version e) to my MyDocs all went well (but took 3 hours to download!).
All finished so I went to run the LXDE and get an error message.
EZ-CHROOT ERROR
Mount failure!
/home/user/MyDocs/debian-m5-v3e.img.ext2 failed to mount on loop0
mount: mounting /dev/loop0 on /.debian failed: No such file or directory
Any suggestions as to want went wrong and how to fix it?
I am running CSSU on PR1.3 and also have U-Boot installed.
Mike
There are some self checks there you can try to make sure things are in order.
http://wiki.maemo.org/Easy_Debian
|
|
2011-08-15
, 16:00
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#2365
|
I'M stuck. 
And I noticed a very annoying thing: Sometimes all keyboard inputs and window manager actions (minimizng, maximizing) cease to work but using menus (LXDE and in windows) and dialogue buttons still work. I think I remember having read about the keyboard fix script that comes with ED, but unfortunately that doesn't solve the problem and I'm not sure if that's the right approach at all since this problem has long been sorted out before I became a N900 user.
Does anybody have any idea on the above problems?
Originally Posted by sulu
I'm pretty sure now that the long start time is due to the superfluous pcmanfm start. While starting ED I watched top which showed "pcmanfm -d" to use a lot of CPU ressources during that time. But I couldn't identify where it was started.
1. Loading LXDE takes much longer now, maybe twice the time. I guess that's due to increased RAM requirements. So far I have no idea what to do about that. Once started the system seems to run as fast as usual.
Originally Posted by sulu
Strangely just creating a default xmodmaprc (with -pke) and loading it almost solved the problem. But this also made it worse. Cursors work fine now but the ISO-Level3 functions (everything in blue) don't work with the loaded xmodmaprc anymore. They did before loading it.
3. The keyboard is messed up. Most keys work fine but according to xev the left cursor (qwerty layout) produces Super_R and so on. I guess that can easily be fixed via xmodmap. I didn't even check so far if the existing xmodmaprc is loaded or not.
And I noticed a very annoying thing: Sometimes all keyboard inputs and window manager actions (minimizng, maximizing) cease to work but using menus (LXDE and in windows) and dialogue buttons still work. I think I remember having read about the keyboard fix script that comes with ED, but unfortunately that doesn't solve the problem and I'm not sure if that's the right approach at all since this problem has long been sorted out before I became a N900 user.
Does anybody have any idea on the above problems?
|
|
2011-08-15
, 16:17
|
|
Posts: 1,873 |
Thanked: 4,529 times |
Joined on Mar 2010
@ North Potomac MD
|
#2366
|
Originally Posted by sulu
Could it be there is a problem with your .xbindkeysrc file?
I'M stuck.
I'm pretty sure now that the long start time is due to the superfluous pcmanfm start. While starting ED I watched top which showed "pcmanfm -d" to use a lot of CPU ressources during that time. But I couldn't identify where it was started.
Strangely just creating a default xmodmaprc (with -pke) and loading it almost solved the problem. But this also made it worse. Cursors work fine now but the ISO-Level3 functions (everything in blue) don't work with the loaded xmodmaprc anymore. They did before loading it.
And I noticed a very annoying thing: Sometimes all keyboard inputs and window manager actions (minimizng, maximizing) cease to work but using menus (LXDE and in windows) and dialogue buttons still work. I think I remember having read about the keyboard fix script that comes with ED, but unfortunately that doesn't solve the problem and I'm not sure if that's the right approach at all since this problem has long been sorted out before I became a N900 user.
Does anybody have any idea on the above problems?
In regards to performance, In some earlier posts by qole and estel it
is recommended to make a dedicated easy debian partition. Try looking here
http://talk.maemo.org<br /> /showth...885#post367885
Others have seen significant improvment to performance. I havn't tried it yet but plan to.
 |
|
2011-08-15
, 18:26
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#2367
|
Just keep in mind, that he (if I recall correctly)did full distro-upgrade to squeeze. IMO it's depreciated on ED, due to huge conflict problems. In fact. it mess so many things, that I don't even know what should I suggest to start, for debugging/narrowing his problems.
Normally, I like to track down source of every single problem, but this time I think most sane think to do is start from scratch and perform more conservative approach to upgrade. And, avoid upgrading gconf2 by all means, cause it *will* screw more things, that we can, probably, list here.
// Edit
"By all means" = turn off considering suggested packages as dependencies (a must-do!), and while trying to update something that require new gconf2, try forcing every single older version, until you find one that doesn't depend on updated gconf2. If every higher version (than one You got installed) require new gconf2, You simply can't update this package, without breaking tons of other things.
Last edited by Estel; 2011-08-15 at 18:29.
Normally, I like to track down source of every single problem, but this time I think most sane think to do is start from scratch and perform more conservative approach to upgrade. And, avoid upgrading gconf2 by all means, cause it *will* screw more things, that we can, probably, list here.
// Edit
"By all means" = turn off considering suggested packages as dependencies (a must-do!), and while trying to update something that require new gconf2, try forcing every single older version, until you find one that doesn't depend on updated gconf2. If every higher version (than one You got installed) require new gconf2, You simply can't update this package, without breaking tons of other things.
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
Last edited by Estel; 2011-08-15 at 18:29.
| The Following User Says Thank You to Estel For This Useful Post: | ||
|
|
2011-08-15
, 21:36
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#2368
|
Originally Posted by mscion
I don't se how, but on the other hand I don't want to exclude it. I included it as an attachment. Except for the keycode24 line where I tried to address the ISO_LEVEL3 issue it's still the way it was when I created it.
Could it be there is a problem with your .xbindkeysrc file?
Originally Posted by mscion
The performance is fine. It's the functionality which isn't. I just mentioned the start performance because it seemed odd that the time increased. Now that I know where this comes from I'm merely interested in finding out how to disable this pcmanfm start. I had a look in the openbox autostart folder but couldn't find any autostart scripts. I also checked the /etc/rc* files but there is nothing as well and /etc/init.d/* also doesn't contain anything that might explain this problem.
In regards to performance, In some earlier posts by qole and estel it
is recommended to make a dedicated easy debian partition. Try looking here
http://talk.maemo.org<br /> /showth...885#post367885
Originally Posted by Estel
Any idea why Squeeze messes the image while the Lenny/Squeeze mix doesn't?
In fact. it mess so many things, that I don't even know what should I suggest to start, for debugging/narrowing his problems.
Originally Posted by Estel
As I said the reason why I did a dist-upgrade was because some software was silently broken. I knew in advance that this most likely will cause some problems, but I hoped that there would have been some progress during the time when I wasn't in these forums.
Normally, I like to track down source of every single problem, but this time I think most sane think to do is start from scratch and perform more conservative approach to upgrade.
I still have my backups so it's not a desaster that the dist-upgrade caused problems. I just would have liked one clean release.
Originally Posted by Estel
Do you have a clue why gconf2 breaks so much stuff?
And, avoid upgrading gconf2 by all means, cause it *will* screw more things, that we can, probably, list here.
Edit:
I just solved the pcmanfm problem. The autostart file I never found was:
Code:
/etc/xdg/lxsession/LXDE/autostart
Code:
setxkbmap #xkbset exp 60 =sticky =twokey =latchlock #xkbset sticky -twokey latchlock @lxde-settings-daemon @lxpanel --profile LXDE @pcmanfm -d
Code:
@pcmanfm -desktop
However the keyboard problem remains. I tried to deactivate the first line in the above script but as I expected that changed nothing. I compared the xev outputs for the "blue arrow button" in Lenny and Squeeze and found the following:
Code:
Lenny : keycode=108 keysym=0xfe03 symname=ISO_Level3_Shift Squeeze: keycode=108 keysym=0xff8d symname=KP_Enter
Last edited by sulu; 2011-08-15 at 22:39.
 |
|
2011-08-15
, 22:29
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#2369
|
The reason I went with a mixed system with some packages held back and some packages hacked to look newer than they actually were is very simple:
Maemo, the host system, uses very old, outdated versions of these packages. In order for the chroot Debian system to properly function with the running Maemo daemons, it needs to be running compatible versions of some systems, including pulseaudio and gconf.
Updating your chroot is, for this reason, entirely a "proceed at your own risk" kind of thing, and I have no idea what negative consequences you'll have for trying it, nor do I have any suggestions for fixing those problems.
Maemo, the host system, uses very old, outdated versions of these packages. In order for the chroot Debian system to properly function with the running Maemo daemons, it needs to be running compatible versions of some systems, including pulseaudio and gconf.
Updating your chroot is, for this reason, entirely a "proceed at your own risk" kind of thing, and I have no idea what negative consequences you'll have for trying it, nor do I have any suggestions for fixing those problems.
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2011-08-15
, 22:58
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#2370
|
I see. Now thet you mentioned it I noticed that jack from Squeeze seems not to be able to communicate with Maemo anymore.
Well, if a pure Squeeze doesn't work properly, what about a pure Lenny? Was one of your earlier images a pure Lenny image?
Well, if a pure Squeeze doesn't work properly, what about a pure Lenny? Was one of your earlier images a pure Lenny image?
 |
| Tags |
| beta, debian, easy debian, extras-devel, fremantle, i <3 qole, squeeze |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 22:42.
But qmount isn't executed if we use "none" option and so closechroot not works
EDIT:
Problems found:
After entering on chroot execute echo "none" > /var/lock/qmount-complete as first command.
Now closechroot will work with only a negligible error (it still tries to umount with qumount the chroot target folder).
Last edited by Fabry; 2011-07-27 at 18:11.