Easy Debian Fremantle Beta Testing - Page 256 - maemo.org

Active Topics

The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 2 days, 14 hrs ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 3 days, 9 hrs ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 5 days, 18 hrs ago
more...

Page 256 of 333

256

Thread Tools

	eight	2012-01-27 , 23:41
	Posts: 106 \| Thanked: 81 times \| Joined on Dec 2011 @ /	#2551

Hello Estel, thanks a lot for making your ED image available and all the work you did. Same goes out to qole and the other ED contributors.

I fail at extracting the lzma archive directly on the n900 through lzma. I think it's not a problem related to your image, but I thought I'd post it here.

When trying to extract the archive the following error shows up: lzma: SetDecoderProperties() error.

Code:

Nokia-N900:/home/user/MyDocs/1Files/OS+img# lzma -d ed-squeeze-final.ext3.lzma
lzma: SetDecoderProperties() error

Nokia-N900:/home/user/MyDocs/1Files/OS+img# unlzma ed-squeeze-final.ext3.lzma
unlzma: SetDecoderProperties() error

Nokia-N900:/home/user/MyDocs/1Files/OS+img# tar xf ed-squeeze-final.ext3.lzma
lzma: SetDecoderProperties() error
tar: Child returned status 1
tar: Beende mit Fehlerstatus aufgrund vorheriger Fehler

Nokia-N900:/home/user/MyDocs/1Files/OS+img# tar xzf ed-squeeze-final.ext3.lzma
gzip: invalid magic
tar: Child returned status 1
tar: Beende mit Fehlerstatus aufgrund vorheriger Fehler
Nokia-N900:/home/user/MyDocs/1Files/OS+img#

The command "xzf" forces tar to use gzip, but it should work with "xf". Lzma seems to be broken or wrong configured on my n900.
Though it works with p7zip to extract the archive after renaming to .7z.

Code:

Nokia-N900:/home/user/MyDocs/1Files/OS+img# p7zip -d ed-squeeze-final.ext3.lzma
/usr/bin/p7zip: ed-squeeze-final.ext3.lzma: unknown suffix -- ignored
Nokia-N900:/home/user/MyDocs/1Files/OS+img# mv ed-squeeze-final.ext3.lzma ed-squeeze-final.ext3.7z
Nokia-N900:/home/user/MyDocs/1Files/OS+img# p7zip -d ed-squeeze-final.ext3.7z

7-Zip (A) 9.04 beta  Copyright (c) 1999-2009 Igor Pavlov  2009-05-30
p7zip Version 9.04 (locale=de_DE,Utf16=on,HugeFiles=on,1 CPU)

Processing archive: ed-squeeze-final.ext3.7z

Extracting  ed-squeeze-final.ext3

I'm running CSSU kernel-power49 and have testing and devel repositorys activated.

Code:

Nokia-N900:/home/user/MyDocs/1Files/OS+img# lzma -V
LZMA command line tool 4.32.0beta3
LZMA SDK 4.43

Last edited by eight; 2012-01-28 at 00:00.

Quote & Reply |

The Following User Says Thank You to eight For This Useful Post:
Estel

droll	2012-01-28 , 01:04
Posts: 958 \| Thanked: 483 times \| Joined on May 2010	#2552

a tip for people who aren't so technically inclined with linux (i am one of them

).

download the file manually, copy it to a laptop and extract it there. it is soooooooooo much faster. then copy it back and edit the easy debian config (/home/user/.chroot) file and you're done in a jiffy.

Last edited by droll; 2012-01-28 at 01:10.

Quote & Reply |

The Following 2 Users Say Thank You to droll For This Useful Post:
eight, Estel

	Estel	2012-01-28 , 05:29
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#2553

@eight
Thanks for pointing that out, of course my tar noobines was showing - I've corrected command to not include -z. I wonder why You have this error at all - image was created via aptosid's tar, so maybe it's some version mismatch. If that is the case, I'm probably doomed to PITA lzma'ing on device. Which will probably take a two days or so

In any case, I'm glad that You've found a way to decompress it on device.

By the way - I've used --lzma, as it creates ~450 MB image, vs 650 MB image of gzip - yet, the latter is *much*, much faster, for both compressing, and decompressing, especially on device. What do You think people - it's the 1/3 size save worth the effort?

@Everyone who tested it already - does it work for You as it should? Also, remember, that if You do not like "hiding" panels (again, the easiest way to pop-up them, is to tap (a little harder than usual) just *outside* the screen, at corresponding edge - it's just like having more hardware buttons on N900

), this feature can be disabled via right-click (or long-press) on panel, then, in last tab, unchecking "hide panel". Their sizes can be also easily adjusted - I use relatively big panels, as they're hiding when unneeded anyway, and big ones are easy to click, even with fingers. Yet, everything is customizable.

/Estel

__________________
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!

Quote & Reply |

The Following 2 Users Say Thank You to Estel For This Useful Post:
eight, vetsin

michaelxy	2012-01-28 , 06:10
Posts: 64 \| Thanked: 24 times \| Joined on Aug 2007 @ Germany ...	#2554

I get the error:

Code:

Mount failure!

/media/mmc1/ed-squeeze-final.ext3 failed to mount on loop0

mount: mounting /dev/loop0 on /.debian failed: Invalid argument

my old ED image runs normal. I unzip it with 7zip on w7.

Quote & Reply |

	Estel	2012-01-28 , 14:23
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#2555

You're trying to mount it via /home/user/.chroot, or via hand? If first option is true, have You modified .chroot to mount as ext3, not ext2? If both true, Could You post here Your .chroot file?

Anyone else having this problem?

/Estel

Quote & Reply |

The Following User Says Thank You to Estel For This Useful Post:
maartenmk

maartenmk	2012-01-28 , 16:01
Posts: 182 \| Thanked: 69 times \| Joined on Nov 2009 @ Netherlands	#2556

I have exactly the same problem, mounting by hand also failed. Here's my .chroot

Code:

# Sample config for chroot 

# Device or image containing Debian filesystem.
# Default: first in /home/user/MyDocs/debian*.img*, /media/mmc1/debian*.img*
# Some examples:
IMGFILE=/home/user/MyDocs/ed-squeeze-final.ext3
#IMGFILE=/media/mmc1/debian-squeeze-m5.img.ext2
#IMGFILE=/dev/mmcblk1p2
#IMGFILE=/dev/mmcblk0p4

# Filesystem used; must always be set when using a partition.
# Default: from extension of IMGFILE, or ext2.
IMGFS=ext3

# Mount point for Debian.
# Default: /debian
CHROOT=/.debian

# New /tmp dir size for printing / PDF creation
# Default: 6M
#TMPSIZE=6M

# Debian user to drop privileges
# Default: user
#DEBUSER=user

Quote & Reply |

	eight	2012-01-28 , 16:15
	Posts: 106 \| Thanked: 81 times \| Joined on Dec 2011 @ /	#2557

Got stuck at the same point.

Code:

Nokia-N900:/home/user# mount -o loop -t ext3 /home/user/MyDocs/1Files/OS\+img/ed-squeeze-final.ext3 /mnt/ed-img/
mount: mounting /dev/loop0 on /mnt/ed-img/ failed: Invalid argument

And I did some research on the lzma error. Tested a lzma archive from qole.org which extracts without the error.

Code:

Nokia-N900:/home/user/MyDocs/1Files# lzma -d maemo-sdk-v1_2.img.ext2.lzma
...

Edit:
Well, this reboot problem below was caused by setting smartrefex (vdd1 sr) enabled in qcpufreq.
Disabled VDD1 and now works well, even overclocked.

*-----------------------------------------------------------------------------------------------------------------------------------------------------*

But then the N900 reboots after a few seconds till minutes after starting lzma extraction.
If this happens /dev/mmcblk0p1 (MyDocs) gets read-only. Mount looks normal but dmesg shows it and you'll get an error like this:.

Code:

Nokia-N900:/home/user/MyDocs/1Files# lzma -d maemo-sdk-v1_2.img.ext2.lzma
lzma: Cannot open output file maemo-sdk-v1_2.img.ext2


Nokia-N900:/home/user# mount
...
/dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir)


Nokia-N900:/home/user# dmesg
...
[31237.416351] FAT: Filesystem error (dev mmcblk0p1)
[31237.416381]     fat_free_clusters: deleting FAT entry beyond EOF
[31237.416412]     File system has been set read-only

If this happens at your N900 you can fix it this way:
- umount /dev/mmcblk0p1
- fsck and repair /dev/mmcblk0p1
- remount it to MyDocs

Code:

Nokia-N900:/home/user/MyDocs/1Files# cd ../..
Nokia-N900:/home/user# umount /dev/mmcblk0p1
Nokia-N900:/home/user# fsck -r /dev/mmcblk0p1
fsck 1.41.3.maemo0 (12-Oct-2008)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 1
Reclaimed 1024 unused clusters (16777216 bytes).
Perform changes ? (y/n) y
/dev/mmcblk0p1: 5812 files, 903148/1277519 clusters
Nokia-N900:/home/user# mount -o rw,noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir /dev/mmcblk0p1 /home/user/MyDocs/

This reboot even happens with nice -n 19 [command]. First I thought it could be due to overclocking, but happens also at 600 Mhz.

Last edited by eight; 2012-02-10 at 10:46.

Quote & Reply |

The Following User Says Thank You to eight For This Useful Post:
Estel

	Estel	2012-01-29 , 10:26
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#2558

It seems, that archive get somehow corrupted during upload - my local copy works, but when I downloaded it, I'm also unable to unpack. Doing so like eight described result in false-positive unpacking, but image is unmountable.

Sorry for inconvenience - will upload again, yet, this time, I'm going to download it myself and check, before dropping link here

/Estel

Quote & Reply |

The Following 2 Users Say Thank You to Estel For This Useful Post:
eight, maartenmk

maartenmk	2012-01-29 , 13:52
Posts: 182 \| Thanked: 69 times \| Joined on Nov 2009 @ Netherlands	#2559

I repeated the tests I did in posts 2324&2329 (opening a file in OOCalc directly from Maemo, editing a minimal amount, and closing OOCalc again), now concentrating on the locations of both swap & ED partitions. The setup is as similar as possible, but can't be fully compared of course.
Each test was run 3 times. The numbers behind each line are the times in seconds:

- Swap on emmc, ED on sd: 95,105,90
- swap on emmc, ED on emmc: 95,75,75
- swap on sd, ED on sd:95,80,75
- swap on sd, ED on emmc: 80,70,65

I then overclocked to 900mhz, and ran the last test twice more:80,60

So as expected 'swap on sd & ED on emmc' is the fastest, and overclocking helps, but not a lot.
I can't really explain the second place for both on emmc though. I am also surprised about the bad performance of the first setup. But the conclusion is clear enough for me.

When Estel's image is back up, I can try the same sequence again, so we will have some idea on the performance of Libre-office.

Quote & Reply |

The Following 4 Users Say Thank You to maartenmk For This Useful Post:
eight, Estel, mscion, reinob

	Estel	2012-01-29 , 14:07
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#2560

I got pissed a little by incompatibilities between aptosid tar --lzma and Maemo tar --lzma implementations, so I decided to do everything on device. I'm already during cp -a everything to image file. Then, I'm going to --lzma it, so it will probably take a week or so :P (seriously though, I expect it to be finished tomorrow). After that, I'll upload it again, then download, unpack, and test. If correct, will drop info here.

/Estel