Juan Pablo Ramirez wrote: > [...] > What I tried to do and failed was to boot an unstable image made with > Narcissus, using Angstrom-boot-2.6.21-hh20-r6-h3900.exe first. It > froze on pslash. [...] > > 2010/3/25 Jon Foster <[email protected]>: > >> Anyhow this may be part of the issue. The freeze during during the >> splash screen symptom I have seen most commonly caused by a kernel and >> module set mismatch. On the hx4700 you flash the kernel separately. So >> on occasion I've gone to the package browser, found the kernel package >> that matches the modules in the image, used "ar" to extract the kernel >> image and then flashed that onto my device. This has allowed me to get >> booting. >> > > That is an interesting idea. Maybe the best way would be to preserve > the working bits from 2007.12 and to update just the userland part; I > doubt sound and battery drivers would be developed for the 2.6.x h3900 > kernel, so there's not much gained from updating it. > > I'll keep researching alternatives. Hope this new info provides > additional insight. > I've not used that method of booting before but looking at the EXE you were using (Angstrom-boot-2.6.21-hh20-r6-h3900.exe) you would need kernel modules for the r6 kernel. Either you need a newer version of that EXE that matches the modules in the unstable file system or you might downgrade the modules in your image to the ones that were in the 2007.12 (r6). If your file system is ext2 instead of jffs2 its a simple affair.
I used this technique to work around other upgrades on my hx4700. Anyhow you could be running into some other issue but it sure sounds like your running an older kernel with newer modules and its dieing loading the modules. I'm not familiar with HaReT perhaps it has a way of specifying a kernel to load? In which case you can probably find the kernel version in the package repository. But I think I found the kernel package for my device was just a place holder. It was empty, which is why I'm still running 2008. :-D Maybe you will have better luck. Beware of future opkg / ipkg upgrades because if they upgrade the kernel modules it will break your system again. :-( I keep my last known working modules in a tar ball for easy loading. I've also started using the ROM monitor to make backups of my flash file system before I do wholesale upgrades. But with your arrangement recovery should be much simpler. I hope this helps, Jon -- Jon Foster JF Possibilities, Inc. [email protected] 541-410-2760 Making computers work for you! -- Jon Foster JF Possibilities, Inc. [email protected] 541-410-2760 Making computers work for you! _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
