![]() |
Re: Easy Debian Fremantle Beta Testing
Estel: When I ran it, LXDE from your image wasn't configured very well; the theme, panels, fonts, and background were not set correctly. That's what I meant.
|
Re: Easy Debian Fremantle Beta Testing
Quote:
Maybe it's a wrong image? |
Re: Easy Debian Fremantle Beta Testing
@impeham
Nope, in my case Shockwave Flash is also listed - 9.0 r31, provided via /usr/lib/browser/plugins/libdebianflashplayer.so If you wait a little, we can move this discussion to new thread. @qole, ivgalvez Damn, I have no idea why it was looking like that. Thinking about that, it's probably missing configuration from /home/user/.config/lxpanel and similar things. qole, do you remember which files from /home/user/(.config?) exactly are used by ED? I would upload them, as a "hotfix", for separate extraction. As a long-term solution, I would use - as You suggested - "onfirstchroot" scripts, to unmount Maemo /home/user, and it would use own ED content. uploaded in new version of image. Does anyone have idea, how such script should like? Or, maybe better ideas to solve that? /Estel |
Re: Easy Debian Fremantle Beta Testing
The Chromium plugins problem is another example of the missing home directory config files. I've got a few pots on the stove, but I'll try to make a script for you to unmount the /home/user folder in the image...
|
Re: Easy Debian Fremantle Beta Testing
Quote:
|
Re: Easy Debian Fremantle Beta Testing
Quote:
|
Re: Easy Debian Fremantle Beta Testing
sorry for the silly question but how to run from estel img chromium or libre office from terminal with debbie?
thanks |
Re: Easy Debian Fremantle Beta Testing
Quote:
Code:
debbie chromium-browser Code:
debbie lowriter Code:
debbie localc |
Re: Easy Debian Fremantle Beta Testing
Quote:
Code:
nice -n 19 cp -a /media/ed/* /mnt/debian-tmp/ |
Re: Easy Debian Fremantle Beta Testing
If you are having copy / decompression problems when using the MyDocs directory, you probably need to run the following two commands before trying the copy command:
Code:
sudo nr_requests_setup |
Re: Easy Debian Fremantle Beta Testing
Had also problems with reboots while unlzma'ing and found out that on my n900 enabled SmartReflex VDD1 causes this.
Tested it with 900 to 600 Mhz and always reboots with vdd1. After disabling vdd1 these high-load-tasks work on my device flawlessly, even at 900 Mhz. |
Re: Easy Debian Fremantle Beta Testing
So make sure you turn off SmartReflex VDD1 on your N900, although it should be off by default:
Code:
sudo "echo 0 > /sys/power/sr_vdd1_autocomp" |
Re: Easy Debian Fremantle Beta Testing
First I have turned off smartreflex from /etc/pmconfig,though cpu is at 805.
Then entered Code:
sudo nr_requests_setup Though the device is not switched off itself,since 15 minutes x terminal froze .Even the backlight is not turned off.Still waiting to observe what happens.:cool: |
Re: Easy Debian Fremantle Beta Testing
Quote:
The VDD0/1-Settings is to activate SmartReflex, but this runs only reasonable with KernelPower49. With the one in extras-testing you can safely overclock to 805MHz at the most devices and the battery-savings are awesome. Only a hint and sorry for the off-toppic. :D More informations can be found here. HTH and HAND CU Michael |
Re: Easy Debian Fremantle Beta Testing
I'm using power49 withd vdd1 and vdd2 enabled at 900 Mhz for some days now.
Works well expect of unlzma'ing big archives. To be more precise, dd .. or tar -cfz (-xfz) of my 3 Gig debian partition works without issues. Only lzma gives reboots even with nice -n 19. I have tested it with this archive: http://qole.org/files/maemo-sdk-v1_2.img.ext2.lzma Switching SR VDD off for lzma tasks like this is quickly done. And the battery-savings of VDD2 are really good. A big difference, compared to only-vdd1-mode and directly noticeable. :) |
Re: Easy Debian Fremantle Beta Testing
Ok, here's how to disconnect the image's /home/user directory from the Maemo version, allowing for per-image user settings.
Create a script in the image's /var/run directory called "onfirstchroot-ext.rc", or add the following lines to the existing script: Code:
umount -f "$CHROOT/home/user/MyDocs" Now you can copy all of your Debian application settings into the image's /home/user dir, and things will be the same on everybody's N900. ESTEL: Please either do this with your image and re-upload it, or give me the zip file of your home directory settings files, and I'll do it on my qole.org version. |
Re: Easy Debian Fremantle Beta Testing
I have been testing Estel's image installed on my SD card (ext3, non dedicated partition) with no problems.
Now I've tried to gain some performance by enabling swap on SD: Code:
sudo swapon -p 0 /dev/mmcblk1p3 Code:
~ $ cat /proc/swaps Code:
Mount failure! |
Re: Easy Debian Fremantle Beta Testing
Quote:
Code:
tar -xfv ed-squeeze-final.ext3 |
Re: Easy Debian Fremantle Beta Testing
Quote:
|
Re: Easy Debian Fremantle Beta Testing
is it possible to extract all the files from the .ext3 image to a partition (without mounting and copying the files from the mounted folder because this will also copy the /home/user and /home/user/mydocs folders)?
i would like to extract it to an ext4 partition i made for it on the sd. |
Re: Easy Debian Fremantle Beta Testing
Estel: Did you upload your configuration files for your image to anywhere else?
|
Re: Easy Debian Fremantle Beta Testing
Quote:
Code:
~$ debian-lxde |
Re: Easy Debian Fremantle Beta Testing
Ok, I believe I have a bug report:
1)Every time I reboot, the only way to be able to mount by "loop" is first running sudo debian. I don't know why; 2)The only way to run debian-lxde is by first mounting the partition (in my case, mmcblk0p5) to /.debian; Now I just need to mount using event.d files to be able to run lxde (so I don't need to manually mount every time I run lxde), so, at least for now this works for me. |
Re: Easy Debian Fremantle Beta Testing
Sorry for late reply, I've just gone through through 2,5 weeks of posting. I'll filter out and publish /home/user config files ASAP, then, I'll create new image containing required config files and replace old one with it.
/Estel |
Re: Easy Debian Fremantle Beta Testing
I just tested a Debian Wheezy chroot in armhf. In principle it works but there are some odd things that I don't understand.
To check whether there is any performance gain I ran nbench. For reference I first did this in in an armel chroot. The result is as follows: Code:
\h:\w$ ./nbench Code:
\h:\w$ ./nbench Does this make sense to anybody? I'm running KP49 without DSP profile and without CSSU btw. The second thing you'll notice is that the result of the armhf FOURIER test is more than 4 times as high as the one of the armel test which in theory should come in handy in multimedia related tasks. On the other hand the FP EMULATION test dropped by 45%. Does anybody have an idea why the FP EMULATION result changed or does someone know the practical implications of that change? To get more practical results I made a video decoding benchmark with mplayer and youtube's 240p version of the big buck bunny video: armel: Code:
\h:\w$ mplayer -benchmark -nosound -vo null /root/bbb.flv Code:
\h:\w$ mplayer -benchmark -nosound -vo null /root/bbb.flv |
Re: Easy Debian Fremantle Beta Testing
@sulu,
I'm no expert, but the only difference between armhf vs armel (or rather, hardfp vs softfp) is in the use of FP registers as a calling convention (as opposed to using the stack). Both hardfp and softfp will use the floating point unit in exactly the same way. So, if most of the work done by mplayer is done within a single function (perhaps with other functions inlined), you should see no difference. |
Re: Easy Debian Fremantle Beta Testing
Frankly I'm no expert either.
Quote:
If I read [1] correctly then there are ARM devices out there that have no FPU at all and armel works on them. So this either means that armel doesn't use the FPU at all (and instead emulates FP operations using integer functions) or can detect if there is a FPU and make use of it. As I understand it the latter would require quite some overhead during runtime which makes me believe the former is true. Under this assumption my understanding was that armhf requires an FPU which will then run FP operations much faster than armel using its integer emulation. This might also explain armhf's poor FP EMULATION test result since it simply wouldn't need to be optimized for that. Anybody, please correct me if I'm wrong! [1] http://wiki.debian.org/ArmHardFloatPort#Rationale btw: As you can see I ran the armel test under Squeeze and the armhf test under Wheezy. I will repeat the armel test under Wheezy to see if the "illegal instruction" error is architecture or release related. Edit: I'd welcome any suggestion for a real world FP benchmark! I guess some of the (de)compression algorithms of different archive types make heavy use if it. But I don't have the knowledge which one would be suitable. |
Re: Help me please
Quote:
LXDE with the one title "Lament ..." Does anybody know which that song is ?... Please Help me... I really need that Song..:( |
Re: Easy Debian Fremantle Beta Testing
I repeated nbench under Wheezy armel which worked fine.
Then I tried it under armhf again but changed the compiler to build nbench. First I tried with gcc-4.4 which resulted in a segmentation fault after the FP EMULATION test instead of gcc-4.6's Illegal instruction. Then I tried nbench compiled with gcc-4.5 which even completed the IDEA test but then rebooted the phone. So it seems something is terribly unstable here. Either it's the compiler under armhf or some component in the underlying FP hardware/Maemo software. Can somebody who has any other armhf-compatible device please try if nbench completes reliably if compiled with any of Debian Wheezy's armhf gccs? Just for completeness, this is the gcc-4.5 result as far as it worked: Code:
\h:\w$ ./nbench |
Re: Easy Debian Fremantle Beta Testing
Estel, did you already upload your new image with the files from /home/user/ ?
My ED image got corrupted so I am forced to download a new image ;) Then I started wondering if you had fixed your image |
Re: Easy Debian Fremantle Beta Testing
Unfortunately, not yet. Sorry, have been quite occupied lately. BTW, after doing so, I'll "announce" it here for sure.
/Estel |
Re: Easy Debian Fremantle Beta Testing
Hello!
I am trying Easy Debian right now, and I am not able to perform apt-get update. It look good at the begining, but then: Err htp://packages.tspre.org lenny/main Packages 504 Gateway Timeout Err htp://packages.tspre.org lenny/non-free Packages 504 Gateway Timeout Err htp://packages.tspre.org lenny/contrib Packages 504 Gateway Timeout Fetched 808kB in 1min 10s (11.5kB/s) W: Failed to fetch htp://packages.tspre.org/dists/lenny/main/binary-armel/Packages.gz 504 Gateway Timeout W: Failed to fetch htp://packages.tspre.org/dists/lenny/non-free/binary-armel/Packages.gz 504 Gateway Timeout W: Failed to fetch htp://packages.tspre.org/dists/lenny/contrib/binary-armel/Packages.gz 504 Gateway Timeout E: Some index files failed to download, they have been ignored, or old ones used instead. [root@m5v3e: /] Is there something wrong? PS: I have to do s/http/htp/ because of rules of this forum. |
Re: Easy Debian Fremantle Beta Testing
@rhadesan:
You're right, the server is down. Just deactivate that entry in your sources.list by prepending: # It's quite a long time since I checked but afair there are no critical packages coming from this repository. It's safe not to use it. |
Re: Easy Debian Fremantle Beta Testing
Estel and sulu:
Could either of you please send me your LXDE config files from your home directory? I really don't think I should leave your images as part of my installer with the current config problems. |
Re: Easy Debian Fremantle Beta Testing
I just started to make my own image based on estels but is there really something wrong? I mean, what's missing besides LXDE config? I think it's quite stable and not much to edit?
I just wanted these files for completeness sake, without knowing what exactly was missing... |
Re: Easy Debian Fremantle Beta Testing
1 Attachment(s)
Quote:
|
Re: Easy Debian Fremantle Beta Testing
Thanks sulu, it's shame on me, but accidentally, I've unsubscripted from this thread :o Thus, totally forget about leaving image incomplete, without config files.
/Estel |
Re: Easy Debian Fremantle Beta Testing
Hi, is there any way to install ff11 (iceweasel 11) on ED? I tried adding experimental repos but it gave me broken dependencies, something about gtk. I also tried to extract the deb to a folder and run the binary but that didnt work either
|
Re: Easy Debian Fremantle Beta Testing
1. You can try to download missing dependencies one by one, and see, if - at the end - You get something usable, thus, creating another releases mix, that we've just avoided ;)
2. You can wait for new stable release, and try to dist-upgrade it, then - after that - fix all conflicts, just like Sulu di. (and, in very small addition, I). Is Iceweasel 11 with it's great slowness worth that? Answer Yourself ;) /Estel |
Re: Easy Debian Fremantle Beta Testing
I'ts just that I am a web developer and I want to be able to show off my work on my phone, and as firefox is my dev browser, most possibly I can show off work in progress. 3.5 is slowly becoming tooo old. On the other hand I think that after 3.6 they've improved a bit in terms of speed.
|
All times are GMT. The time now is 06:03. |
vBulletin® Version 3.8.8