maemo.org - Talk - New patch for N810 mmc mis identity is now UP, again, anybody interested?

Bug 2747, more prevalent in N810, mis ID mmc1 vs mm2 under various conditions, https://bugs.maemo.org/attachment.cg...26&action=edit. Now has a new patch 10/22/09. This is very important for N810 users, especially mmc boot, have you ever wipe out your hard drive because of mis identity? Now you got the picture.

Well, can one of you gurus apply the patch and post the 'fixed' kernel, pleeeeeeeeeeeeeas? OR, even better, some council member take it up.....hint, hint, hint :) :) :) TIA,

somewhat 'unrelated' issues. I did some experiments today, that may be good for others dont have to repeat them.

Just for the sake of reading, microSD labelled mmcblk1 is considered RIGHT.

N810, with microSD in slot before boot, latest Diablo.
1In) IntFlash boot:
boot message: mtdblock4 jffs2 ... (Right)
cat /proc/partitions microSD is mmcblk0 (Wrong)
df initfs is on mtdblock4 and microSD is mmcblk1 (Right)
No warning message when pulled out microSD and re-inserted microSD "memory card available" all is well

2In) IntSD boot:
boot message: mmcblk1p2 ext2... (Wrong)
cat /proc/partitions microSD is mmcblk0 (Wrong)
df initfs mmcblk0 and microSD is mmcblk1 (Right?)
When open microSD door, warning "Data damage....." when card pull out, system reboot

3In) ExtSD (microSD) boot
bootup message: mmcblk0p2 ext2... (Wrong)
cat /proc/partitions microSD is mmcblk0 (Wrong)
df /initfs is mmcblk1 and microSD is mmcblk1 (Right)
Pull out the microSD, there is NO warning. System hanged for 3 second and screen faded to black!

Re-insert microSD, all is well, thank god! And it also boot too. So.............pull the OS disk while it is ON, did not seem to cause damage to the system file on the disk. NOT recommend to try it, I did it already, so you do not have to try :)

With microSD out before boot and re-insert after boot up completed
1Out) IntFlash boot
boot message: mtdblock4 jffs2... (Right)
cat /proc/partitions microSD is mmcblk1 (Right)
df initfs is mtdblock4 and microSD is mmcblk1 (Right)

2Out) IntSD boot
boot message: mmcblk0p2 ext2... (Right)
cat /proc/partitions microSD is mmcblk1 (Right)
df initfs is mmcblk0 and microSD is mmcblk1 (Right)

Pull out microSD has no problem, all is well.

3Out) extSD (microSD) boot Not possible :(

Apparantly in the above examples, 2In and 3In while swapping microSD will cause data loss, especially for 3In, there is NO warning! :( 2In reboot is absolutely a fluke, the OS is in microSD, it crashed simply because of the system think it is living on intSD. Unnecessary crashing!

Conclusion The absolute sure way to deal with this, is have your microSD card out before bootup and re-insert it after bootup, then you would be sure about mmc1 and mmc2. Of course, that means, boot up on microSD will still be problem. I want the patch............please!!!!!

enjoy,

bun