Originally Posted by stlpaul

There is of course the possibility that the dto change itself doesn't get along with your device for some reason. Based on everything I've read I doubt that is the case, but you never know. So far 3 people here had success with it, including me. 2 had the boot loop.

In the past (not with this particular change) I've gotten the boot loop when I flashed a kernel but forgot to install the modules first. So encoiuntering that after messing with a module does seem to point to something gone awry.

I'm using the power47 from extras-devel, I'm also using multiboot and the modified backupmenu in multiboot, I don't know if those things change how the boot process works as far as kernel module loading goes... I don't think it should make a difference, but obviously something is not working the same for you guys.

I downloaded the module I attached here and it is indeed the one I am using:

Code:

user@N900 ~/MyDocs/Downloads $ unzip sdfix-power47.zip 
Archive:  sdfix-power47.zip
  inflating: 2.6.28.10power47/omap_hsmmc.ko  
user@N900 ~/MyDocs/Downloads $ md5sum 2.6.28.10power47/omap_hsmmc.ko 
1db1e654a8daf86687c2247356e1d6fb  2.6.28.10power47/omap_hsmmc.ko
user@N900 ~/MyDocs/Downloads $ md5sum /lib/modules/2.6.28.10-power47/omap_hsmmc.ko
1db1e654a8daf86687c2247356e1d6fb  /lib/modules/2.6.28.10-power47/omap_hsmmc.ko
user@N900 ~/MyDocs/Downloads $ uname -a
Linux N900 2.6.28.10-power47 #1 PREEMPT Tue May 3 20:40:52 EEST 2011 armv7l GNU/Linux

I've also compiled & successfully used the modified module with the PR1.3 stock kernel, power46 and power46-wl1, and possibly-successfully for the nitdroid kernel from e-yes' git repository (nitdroid spazzed because of my previous installation, but did not self-destruct like it does with the unmodified kernel). In all cases I'm leaving the installed kernel and modules unchanged, with the exception of my new omap_hsmmc which I just copy over the old one.

Hope someone else can perhaps detect what might be going on.