Hi All, On popular request here are some updated diffs with bugfixes and cleanups, the ro/rw-scripts are committed and blink got scraped. Please test and comment. Rickard. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: README.diff Url: http://lists.mindrot.org/pipermail/flashboot/attachments/20060901/21b4b6df/attachment.ksh -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: extension.diff Url: http://lists.mindrot.org/pipermail/flashboot/attachments/20060901/21b4b6df/attachment-0001.ksh -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: largekernel.diff Url: http://lists.mindrot.org/pipermail/flashboot/attachments/20060901/21b4b6df/attachment-0002.ksh
On Fri, 2006-09-01 at 11:48 +0200, Rickard Dahlstrand wrote:> Hi All, > > On popular request here are some updated diffs with bugfixes and > cleanups, the ro/rw-scripts are committed and blink got scraped. Please > test and comment. >./build-largekernel.sh GENRIC-RD produce a kernel which doesn''t boot, it stops loading the ''second stage'' during the boot phase even before starting to outputting the result of the boot process (dmesg). The result is the box continuisly rebooting while uncompressing/loading the kernel. Regards -- Massimo.run();
Massimo Lusetti wrote:> On Fri, 2006-09-01 at 11:48 +0200, Rickard Dahlstrand wrote: > > >> Hi All, >> >> On popular request here are some updated diffs with bugfixes and >> cleanups, the ro/rw-scripts are committed and blink got scraped. Please >> test and comment. >> >> > > ./build-largekernel.sh GENRIC-RD produce a kernel which doesn''t boot, it > stops loading the ''second stage'' during the boot phase even before > starting to outputting the result of the boot process (dmesg). > The result is the box continuisly rebooting while uncompressing/loading > the kernel. >That was what we suspected. What factors that are involved when booting large kernels are a bit of a mystery to us. The 25 mb WRAP12 kernel boots fine on my 128 MB WRAP-box. But the generic is a bit larger and could possibly cause problems. This is what Damien wrote on the subject: /A couple of caveats regarding kernel customisation: First, if your kernel+ramdisk blob is larger than 16Mb, then you will need to increase NKPTP in the kernel config (just uncomment the entry in the file, it''s good for 32Mb kernels). The symptom of a kernel with a too-small NKPTP is an immediate crash or reboot after the kernel is loaded. Another caveat is that kernels larger than about 14Mb in size will use up all the ISA DMA memory and the kernel will panic at boot unless isadma is disabled in the config or via UKC. This leads to the final problem: if isadma is disabled, then things that attempt to use it (e.g. floppy disk access) will panic the kernel. The best solution is to try to keep your kernels small./ As far as I can tell both of these are done for all kernels: http://cvsweb.mindrot.org/index.cgi/flashboot/GENERIC-RD.diff?r1=1.7;r2=1.8 And then we have this where Damien had some kind of idea on what could be done: http://cvsweb.mindrot.org/index.cgi/flashboot/TODO?rev=1.6 I''m afraid that I understand to little on this, we need an expert. Until we get some facts here people should only use the large-kernel option if tested properly and on systems with console access and a backup obsd-kernel. Rickard. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20060904/45a6b881/attachment.html
Massimo Lusetti wrote:> On Fri, 2006-09-01 at 11:48 +0200, Rickard Dahlstrand wrote: > > >> Hi All, >> >> On popular request here are some updated diffs with bugfixes and >> cleanups, the ro/rw-scripts are committed and blink got scraped. Please >> test and comment. >> >> > > ./build-largekernel.sh GENRIC-RD produce a kernel which doesn''t boot, it > stops loading the ''second stage'' during the boot phase even before > starting to outputting the result of the boot process (dmesg). > The result is the box continuisly rebooting while uncompressing/loading > the kernel. >A uncompressed generic kernel on 3.9 seems to be over the 32 mb limit, try moving down to the 20 mb ramdisk. Have a look in the build.largekernel file on how to modify it and give us a report on what your progress are. Rickard. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20060905/72d24bf9/attachment.html
Massimo Lusetti wrote:> On Fri, 2006-09-01 at 11:48 +0200, Rickard Dahlstrand wrote: > > >> Hi All, >> >> On popular request here are some updated diffs with bugfixes and >> cleanups, the ro/rw-scripts are committed and blink got scraped. Please >> test and comment. >> >> > > ./build-largekernel.sh GENRIC-RD produce a kernel which doesn''t boot, it > stops loading the ''second stage'' during the boot phase even before > starting to outputting the result of the boot process (dmesg). > The result is the box continuisly rebooting while uncompressing/loading > the kernel. >The latest patch that was committed this morning hopefully fixed this issue. I have set down the largekernel from 25 to 20 MB and that should produce a kernel that is smaller than the 32 MB limit. Please give it a try and report your progress. Regards, Rickard. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20061019/7fef8aea/attachment.html
On Thu, 2006-10-19 at 09:12 +0200, Rickard Dahlstrand wrote:> The latest patch that was committed this morning hopefully fixed this > issue. I have set down the largekernel from 25 to 20 MB and that > should produce a kernel that is smaller than the 32 MB limit. Please > give it a try and report your progress.Thanks, i will try as soon as possible, I''m in the middle of a big deploy and I''m missing time slot. -- Massimo.run();