Notices


Reply
Thread Tools
Posts: 3,230 | Thanked: 4,116 times | Joined on May 2011 @ Poland
#721
I'm getting an error now that the Nemo platformfs can't be opened

Code:
VFS: CAnnot open root device "mmcblk0p5" or unknown-block(0,0)
When trying to mount the partition (ext4) in Maemo with kp52 I'm getting:

Code:
Unable to mount /dev/mmcblk0p5: Invalid argument.
What am I doing wrong?

Last edited by marmistrz; 2013-07-09 at 19:11.
 
Posts: 2,136 | Thanked: 8,353 times | Joined on May 2010
#722
Originally Posted by marmistrz View Post
Thanks.
and should I run u-boot-update-bootmenu as root or as user?
If you want kernel string of attached kernel visible in u-boot menu, run update script as root. Otherwise as normal user :-)

Originally Posted by marmistrz View Post
I'm getting an error now that the Nemo platformfs can't be opened

Code:
VFS: CAnnot open root device "mmcblk0p5" or unknown-block(0,0)
This means that kernel did not initialized or did not loaded driver for "mmcblk0p5". Make sure your kernel has mmc driver static linked into zImage or you have initramfs with external modules. You can try to add "rootwait" to cmdline, then kernel will wait some time before mounting rootfs.

Originally Posted by marmistrz View Post
When trying to mount the partition (ext4) in Maemo with kp52 I'm getting:

Code:
Unable to mount /dev/mmcblk0p5: Invalid argument.
What am I doing wrong?
Make sure that ext4 driver is loaded (or static linked into kernel). Use modprobe and lsmod for verifing. Specify also filesystem param via "-t ext4" in mount command. When kernel refuse to mount something it will print error message to dmesg.
 

The Following 3 Users Say Thank You to pali For This Useful Post:
peterleinchen's Avatar
Posts: 3,188 | Thanked: 5,756 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#723
Hi pali,

I am updating my device a bit and also installed latest u-boot (bootimg and tools). On bootimg everything went smooth, but after tools I got some weird error.
Originally Posted by pali View Post
This looks like your first eMMC partition (MyDocs) is not valid fat, ext2 or ext4.
Weird, as I never repartitioned my p1 and it is still stock partitioned vfat.

So I investigated a bit and it seems there is a small glitch in update enu script. It will only be noticed when you have easy debian mounted and/or another loop device pointing to a file on MyDocs.
I have both

Easy to solve:
just change line
Code:
type=$(mount | grep "$BOOTMENU_EMMC_DIR" | sed 's/.*type //;s/ .*//')
to
Code:
type=$(mount | grep " $BOOTMENU_EMMC_DIR " | sed 's/.*type //;s/ .*//')
Thought I let you know.

--
reason is that "mount" will give two/three outputs for "/home/user/MyDocs":
/home/user/MyDocs
.debian/home/user/MyDocs
/home/user/MyDocs/myLoopDevice
so type ends in "vfat vfat vfat"
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature

Last edited by peterleinchen; 2013-07-23 at 22:41. Reason: forgot reason/explanation
 

The Following 6 Users Say Thank You to peterleinchen For This Useful Post:
Estel's Avatar
Posts: 5,029 | Thanked: 8,587 times | Joined on Mar 2011
#724
Nice catch. If we're at it, while fixing it, maybe we would finally merge kerio's patch, allowing to make u-boot menu without "attached kernel" boot option?

Sure it's not big deal, but having non-working u-boot entry is still a little irritating for people, that doesn't attach kernels to u-boot (as there is no real reason to do so - after loading, kernel sits in memory, anyway).

BTW, I wonder, if u-boot without kernel attached shouldn't become default method. After all, multiboot was railed for NAND-saving reasons... Having only u-boot flashed to NAND saves it from wear too, as there is no need to reflash it with your favorite kernel-attached- everytime new version of kernel appears (you only need to flash if/when new version of u-boot appears, which happen much less frequently than new version of kernel[s]).

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

The Following 2 Users Say Thank You to Estel For This Useful Post:
Posts: 2,136 | Thanked: 8,353 times | Joined on May 2010
#725
Originally Posted by peterleinchen View Post
Hi pali,

I am updating my device a bit and also installed latest u-boot (bootimg and tools). On bootimg everything went smooth, but after tools I got some weird error.

Weird, as I never repartitioned my p1 and it is still stock partitioned vfat.

So I investigated a bit and it seems there is a small glitch in update enu script. It will only be noticed when you have easy debian mounted and/or another loop device pointing to a file on MyDocs.
I have both

Easy to solve:
just change line
Code:
type=$(mount | grep "$BOOTMENU_EMMC_DIR" | sed 's/.*type //;s/ .*//')
to
Code:
type=$(mount | grep " $BOOTMENU_EMMC_DIR " | sed 's/.*type //;s/ .*//')
Thought I let you know.

--
reason is that "mount" will give two/three outputs for "/home/user/MyDocs":
/home/user/MyDocs
.debian/home/user/MyDocs
/home/user/MyDocs/myLoopDevice
so type ends in "vfat vfat vfat"
Fixed in git: https://gitorious.org/u-boot-shr/u-b...4ad7caaaa62d33
 

The Following 5 Users Say Thank You to pali For This Useful Post:
peterleinchen's Avatar
Posts: 3,188 | Thanked: 5,756 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#726
Originally Posted by Estel View Post
... allowing to make u-boot menu without "attached kernel" boot option?

Sure it's not big deal, but having non-working u-boot entry is still a little irritating for people, that doesn't attach kernels to u-boot (as there is no real reason to do so - after loading, kernel sits in memory, anyway).
Estel, what is your reason to request that?
Afaik the u-boot-flasher has attached the stock kernel, so there is no change of kernel at all.
Of course people who have attached their own kernel (like me, who not installed the u-boot flasher package) may need to change that on a kernel change. But I am thinking of going pali's way now and use the /etc/default symlink way...
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 
Alecsandru's Avatar
Posts: 440 | Thanked: 280 times | Joined on Oct 2012
#727
the cssu3 kernel as default entry would be nice
__________________
N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version

Last edited by Alecsandru; 2013-07-24 at 19:37.
 

The Following 2 Users Say Thank You to Alecsandru For This Useful Post:
Posts: 1,776 | Thanked: 4,132 times | Joined on Feb 2011 @ Germany
#728
Originally Posted by Estel View Post
...as there is no need to reflash it with your favorite kernel-attached- everytime new version of kernel appears
Come on. It's not that frequent that the kernel gets updated. I submit that the mtd partition holding the kernel can be flashed about 10000 times, give or take a 0.1 or 10 factor.
 
Estel's Avatar
Posts: 5,029 | Thanked: 8,587 times | Joined on Mar 2011
#729
Sure, but if we already depreciated multiboot due to NAND wear reasons (despite fact, that NAND wasn't worn so much, until you shuffle kernels on every reboot, and reboot twice a day), I don't see, why we should propagate flashing u-boot with kernels attached.

There is *no* valid reason to attach kernel to u-boot - having u-boot only in kernel area, and loading kernels from regular space is both technically and practically better.
---

Anyway, I don't request moving into u-boot only in NAND area for everyone - I just suggested it as side note (because it's logical, see all of the above).

Main thing I've requested, is to merge already existing (i.e. someone did it months ago) patch to update menu script, that detects lack of attached kernel, thus *in* creating useless menu entry.

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

The Following 2 Users Say Thank You to Estel For This Useful Post:
Alecsandru's Avatar
Posts: 440 | Thanked: 280 times | Joined on Oct 2012
#730
estel i wish you to get a corrupted MyDocs and see how your theory works in that case
__________________
N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version

Last edited by Alecsandru; 2013-07-24 at 20:49.
 

The Following User Says Thank You to Alecsandru For This Useful Post:
Reply

Tags
bootmenu, u-boot

Thread Tools

 
Forum Jump


All times are GMT. The time now is 15:27.