Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 5 hrs, 23 mins ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 6 hrs, 37 mins ago -
Maemo repository (3)
to Community by torsen - 22 hrs, 6 mins ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 1 day, 19 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 2 hrs ago - more...
| The Following User Says Thank You to Alex Atkin UK For This Useful Post: | ||
 |
|
2009-11-12
, 06:11
|
|
Posts: 319 |
Thanked: 289 times |
Joined on Sep 2009
@ Lisboa, Portugal
|
#12
|
So, I bought a spare 16gb microSD card and I think that would be enough for me.
How could I increase the amount of space for /opt then? Lets say by 10gb?
How could I increase the amount of space for /opt then? Lets say by 10gb?
|
|
2009-11-12
, 06:21
|
|
Posts: 176 |
Thanked: 56 times |
Joined on Oct 2009
|
#13
|
Originally Posted by HangLoose
In theory you could create a RAID 0 array between the built in storage for /opt and the microSD card. To do so you would have to compile or use already compiled raid drivers as a module or built into the kernel. I am not sure if the default kernel supports RAID but I assume it is removed to reduce size. You would need to format the RAID partition destroying any data in /opt or on the SD card. I feel this is a bad idea. If you removed the SD card /opt would be unusable. Also the SD card and built in /opt storage are likely to read and write at different speeds.
So, I bought a spare 16gb microSD card and I think that would be enough for me.
How could I increase the amount of space for /opt then? Lets say by 10gb?
A better solution might be to link the SD card to a folder under /opt for example make it /opt/sd and store some files in there.
My intention is to remove the /opt partition and add that space to the root partition. Then use a partition on a never to be removed SD card as /opt.
It will much easier to figure this out once we have phones to try it.
|
|
2009-11-12
, 08:55
|
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#14
|
Originally Posted by Bruce
Yes, doesn't look like good solution.
In theory you could create a RAID 0 array between the built in storage for /opt and the microSD card
....
I feel this is a bad idea. If you removed the SD card /opt would be unusable.
Also the SD card and built in /opt storage are likely to read and write at different speeds.
Originally Posted by Bruce
32GB internal eMMC is made of
A better solution might be to link the SD card to a folder under /opt for example make it /opt/sd and store some files in there.
My intention is to remove the /opt partition and add that space to the root partition. Then use a partition on a never to be removed SD card as /opt.
~768MB of swap (to make total virtual memory 1GB)
2GB ext3 for /opt
rest is FAT32 for MyDocuments
/opt shoud stay as unix filesystem and cannot be removed, due to small 256MB root filesystem (ubifs in internal NAND) current official workaround is to put almost everything to /opt automatically. Almost all installable packages will use /opt for most of its stuff. That means if /opt is on removable card it really cannot be removed or system may not boot or interesting things will happen.
IMO if one needs bigger /opt then repartitioning internal eMMC card can be solution. Either make it significantly larger or remove FAT completely and leave only external card to be FAT for easy data exchange.
Or another solution is the old 'boot from mmc' one i.e. have one big partition on internal mmc or microsd, copy whole root fs to it and keep /opt there too (i.e. do not mount it anywhere). Personally this will be the first thing I'll do when I get the device - move whole root to internal eMMC, if it is slow (there are such reports that it might be, also 32GB is likely to be class 2 and quite slow to keep the price of device down) then move at least swap to microSD to put frequent writes away (eMMC may be fast for reads but poor for frequent writes), if it is still slow then move whole system to (class 6) microSD.
__________________
Newbies click here before posting. Thanks.
If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.
Newbies click here before posting. Thanks.
If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.
Last edited by fanoush; 2009-11-12 at 09:11.
|
|
2009-11-12
, 11:33
|
|
Posts: 3,841 |
Thanked: 1,079 times |
Joined on Nov 2006
|
#15
|
I still feel that the biggest downside of the N900 will be the microSD solution. I'll probably be doing my boot-from-card stuff and all the fancy things with my old N800 and the Pandora, and basically leave the N900 as-is, I suspect.
EDIT: Oh, and I think I might have to get one of those Scott E-vests to be able to actually carry all these gadgets and phones.
EDIT: Oh, and I think I might have to get one of those Scott E-vests to be able to actually carry all these gadgets and phones.
__________________
N800/OS2007|N900/Maemo5
-- Metalayer-crawler delenda est.
-- Current state: Fed up with everything MeeGo.
N800/OS2007|N900/Maemo5
-- Metalayer-crawler delenda est.
-- Current state: Fed up with everything MeeGo.
|
|
2009-11-12
, 12:33
|
|
Posts: 1,255 |
Thanked: 393 times |
Joined on Oct 2009
@ US
|
#16
|
Originally Posted by fanoush
I hope they did not use class 2 for two obvious reasons:
Yes, doesn't look like good solution.
32GB internal eMMC is made of
~768MB of swap (to make total virtual memory 1GB)
2GB ext3 for /opt
rest is FAT32 for MyDocuments
/opt shoud stay as unix filesystem and cannot be removed, due to small 256MB root filesystem (ubifs in internal NAND) current official workaround is to put almost everything to /opt automatically. Almost all installable packages will use /opt for most of its stuff. That means if /opt is on removable card it really cannot be removed or system may not boot or interesting things will happen.
IMO if one needs bigger /opt then repartitioning internal eMMC card can be solution. Either make it significantly larger or remove FAT completely and leave only external card to be FAT for easy data exchange.
Or another solution is the old 'boot from mmc' one i.e. have one big partition on internal mmc or microsd, copy whole root fs to it and keep /opt there too (i.e. do not mount it anywhere). Personally this will be the first thing I'll do when I get the device - move whole root to internal eMMC, if it is slow (there are such reports that it might be, also 32GB is likely to be class 2 and quite slow to keep the price of device down) then move at least swap to microSD to put frequent writes away (eMMC may be fast for reads but poor for frequent writes), if it is still slow then move whole system to (class 6) microSD.
1. Greater data latency
2. Read write failure curve is shorter (does not last as long as class 6)
Given the reliance of the 32gb resources for apps, this would seem very foolish.
|
|
2009-11-12
, 13:10
|
|
Posts: 226 |
Thanked: 63 times |
Joined on Sep 2009
@ Maldives
|
#17
|
Hehe... I like the idea of a RAID using the eMMC & µSD, but I doubt that it would have much of a benefit, But I am glad the internal storage is big for a change, much like a real computer, coming from the E90, I constantly fill up the 128MB internal storage and if installing application/messages on card makes it useless for mass storage support over USB. I personally find the partition allocation for Linux on the N900 some what limited. Glad to know that we can change that.
|
|
2009-11-12
, 13:35
|
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#18
|
Originally Posted by Rushmore
Well, strictly speaking, there is no class rating for MMC cards so by class 2 I meant the slowest and cheapest solution available. But anyway, when looking at Samsung eMMC pages now, it looks like there is only one choice for 32GB. It is marked as 2bit MLC flash, 8x32gbit which does not say much about speed. Also I'm not sure this one is used it just seems most likely, at least N810 uses eMMC by Samsung.
I hope they did not use class 2
I wonder if anyone with N900 could make some speed test via dd command.
__________________
Newbies click here before posting. Thanks.
If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.
Newbies click here before posting. Thanks.
If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.
 |
|
2009-11-12
, 13:52
|
|
Posts: 850 |
Thanked: 626 times |
Joined on Sep 2009
@ Vienna, Austria
|
#19
|
Originally Posted by fanoush
it's "high speed" (whatever that means)
I wonder if anyone with N900 could make some speed test via dd command.
[ 6.618591] mmc1: new high speed MMC card at address 0001
[ 6.622467] mmcblk0: mmc1:0001 MMC32G 29.8 GiB
[ 6.622772] mmcblk0: p1 p2 p3
from the dmesg output of a summit device.
maybe we're lucky and "high speed" means MMC Plus? that's the only faster MMC standard i know of.
|
|
2009-11-12
, 14:03
|
|
Posts: 176 |
Thanked: 56 times |
Joined on Oct 2009
|
#20
|
Could someone run
hdparm -t -T /dev/whatevertheinternalstorageis
and
hdparm -t -T /dev/thesdcard
for comparison?
hdparm -t -T /dev/whatevertheinternalstorageis
and
hdparm -t -T /dev/thesdcard
for comparison?
I personally am thinking I might delete the /opt partition and make /home the full size as I do not need mass storage device ability. Being able to properly share all that space between /opt and /home/User (whatever its called) is far more convenient. The ONLY reason they are separate partitions is to allow mass storage device ability, which you could still do for the microSD if you needed that ability.
OpenSSH will be one of the first things I install so that I can transfer data over more easily as I hate the messing around mounting/unmounting/permission denied issues you get with the mass storage controller method. That and how it cannot be accessed from the phone at the same time.