J4ZZ | # 231 | 2012-05-01, 15:46 | Report

mmcinfo

Device: OMAP SD/MMC
Manufacturer ID: 11
OEM: 100
Name: MMC32
Tran Speed: 25000000
Rd Block Len: 512
MMC version 4.0
High Capacity: Yes
Capacity: 29,8 GiB
Bus Width: 8-bit

mmc dev 1

mmc1 is current device

mmc part 1

shows partition map
1 Type c
2 Type 83
3 swap (Type 82)

fatls mmc 1:1 /

lists 132 file(s), 144 dir(s)
but the file/folder names seem to be totally messed up...

pali | # 232 | 2012-05-01, 15:52 | Report

so this is problem why u-boot cannot load it.

you can try to backup all files, then format partition to vfat (fat32) and copy files back.

scoobydoo | # 233 | 2012-05-01, 16:10 | Report

sorry to sound ******ed but can't seem to do this part


Examples:

This tarball http://atrey.karlin.mff.cuni.cz/~pal...12.04-1.tar.gz contains some kernels (stock PR1.3 and stock PR1.3 with framebuffer) and some item files.

For playing & testing download archive to / and unpack it as root:
$ cd / && tar -xf u-boot-images.tar.gz

probably just bieng a fool

J4ZZ | # 234 | 2012-05-01, 16:10 | Report

but why is this? Filenames are just fine in WinSCP or Putty when doing ls.

Could this be caused by a restored backup optfs?

Estel | # 235 | 2012-05-01, 16:30 | Report

No, it doesn't work that way. Just do as Pali suggested - at best, it will fix Your problem, at worst, it will filter out possible source of issues. U-Boot is just different kind of low-level, when reading required bits - it may work well via filemanager, SCP or whatever, but be too FCKD up for U-Boot. Which seems to be the case - You said already, that for U-Boot directories/filenames are FCKD.

/Estel

drucula | # 236 | 2012-05-01, 19:47 | Report

I found out the reason that causing J4ZZ's problem (and mine). I have (now, had) the same problem too after installing u-boot today for the first time.
The problem is backupmenu. It is creating a .item file in /etc/bootmenu.d/ called backupmenu.item which contains only this line:
u-boot-update-bootmenu can't read this file correctly and then fails while running, throwing some "can't read from /dev/null" error (sorry for not saving the error log ).

I fixed it this way: flashed only the kernel, booted maemo, renamed this /etc/bootmenu.d/backupmenu.item file, reflashed u-boot (run dpkg -i u-boot-flasher...) and finally ran u-boot-update-bootmenu again. Now everything works the way it should have worked.

pali | # 237 | 2012-05-01, 19:54 | Report

This is not valid bootmenu item file. u-boot use same file format as fanoush bootmenu and this is invalid.

drucula | # 238 | 2012-05-01, 20:20 | Report

That's the weird part.. I found no reason for it to be there at all. I looked through backupmenu's .deb and install scripts and found nothing related to /etc/bootmenu.d. I have no idea how it got there. I certainly have not copied it there.

J4ZZ | # 239 | 2012-05-01, 22:10 | Report

It's half way fixed... Proper U-boot menu is now showing omap1-power50 and all the others, but after selecting default entry all I get is "Starting Kernel..."
and then the phone turns off.

fatls mmc 1:1 / is now displaying correct filenames after backup and mkfs.vfat -F32 /dev/MyDocs... and then restoring.

J4ZZ | # 240 | 2012-05-01, 22:15 | Report

sorry, but I cannot confirm that. No such *.item file here. But the problem still exists.