Re: Boot problem custom Kernel 5.7
> entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304] > == At this point the system reboots. No further messages. Your kernel is probably too large. A limitation in the bootblocks.
Re: Boot problem custom Kernel 5.7
On Tue, 09 Jun 2015, Theo de Raadt wrote: > > entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304] > > == At this point the system reboots. No further messages. > > Your kernel is probably too large. A limitation in the bootblocks. Do you mean the kernel with the ramdisk or without? What would be the best way to workaround this limit? Decrease ramdisk size? Remove driver/options from the kernel?
Re: Boot problem custom Kernel 5.7
> > > entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304] > > > == At this point the system reboots. No further messages. > > > > Your kernel is probably too large. A limitation in the bootblocks. > Do you mean the kernel with the ramdisk or without? What would be the > best way to workaround this limit? Decrease ramdisk size? > Remove driver/options from the kernel? Those are your changes, outside the OpenBSD tree. You are on your own.
Re: Boot problem custom Kernel 5.7
On 2015-06-09 13:34, Oliver wrote: On Tue, 09 Jun 2015, Theo de Raadt wrote: > entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304] > == At this point the system reboots. No further messages. Your kernel is probably too large. A limitation in the bootblocks. Do you mean the kernel with the ramdisk or without? What would be the best way to workaround this limit? Decrease ramdisk size? Remove driver/options from the kernel? Back when I was building live CDs/DVDs, I used GENERIC or GENERIC.MP kernels with cd0a as the root filesystem, and MFS mounted /etc, /var, /root, /tmp, /home, and /dev. Read-only filesystems on media were all CD9660. I ran into cdboot(8) issues with very large /usr/local filesystems (e.g. KDE and Gnome). My simple circumvention was to vnconfig(8) /usr/local from an .iso image file after boot completed.
Re: Boot problem custom Kernel 5.7
Hello, On Tue, 09 Jun 2015, Theo de Raadt wrote: > > > > entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304] > > > > == At this point the system reboots. No further messages. > > > > > > Your kernel is probably too large. A limitation in the bootblocks. > > Do you mean the kernel with the ramdisk or without? What would be the > > best way to workaround this limit? Decrease ramdisk size? > > Remove driver/options from the kernel? > > Those are your changes, outside the OpenBSD tree. You are on your own. I just want to say that this problem is fixed in OpenBSD 5.8-beta. The problem is not the bootloader. Can someone point me to the right direction to backport the changes to 5.7? Thanks, Oliver
Re: Boot problem custom Kernel 5.7
2015/07/10 22:12 "Oliver" : > > Hello, > > On Tue, 09 Jun 2015, Theo de Raadt wrote: > > > > > entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304] > > > > > == At this point the system reboots. No further messages. > > > > > > > > Your kernel is probably too large. A limitation in the bootblocks. > > > Do you mean the kernel with the ramdisk or without? What would be the > > > best way to workaround this limit? Decrease ramdisk size? > > > Remove driver/options from the kernel? > > > > Those are your changes, outside the OpenBSD tree. You are on your own. > I just want to say that this problem is fixed in OpenBSD 5.8-beta. The > problem is not the bootloader. Can someone point me to the right direction to > backport the changes to 5.7? > > Thanks, > > Oliver Is it fixed, or is it just randomly working?
Re: Boot problem custom Kernel 5.7
On Sat, 11 Jul 2015, Joel Rees wrote: > 2015/07/10 22:12 "Oliver" : > > > > Hello, > > > > On Tue, 09 Jun 2015, Theo de Raadt wrote: > > > > > > entry point at 0x1000160 [7205c766, 3404, 24448b12, 1080a304] > > > > > > == At this point the system reboots. No further messages. > > > > > > > > > > Your kernel is probably too large. A limitation in the bootblocks. > > > > Do you mean the kernel with the ramdisk or without? What would be the > > > > best way to workaround this limit? Decrease ramdisk size? > > > > Remove driver/options from the kernel? > > > > > > Those are your changes, outside the OpenBSD tree. You are on your own. > > I just want to say that this problem is fixed in OpenBSD 5.8-beta. The > > problem is not the bootloader. Can someone point me to the right > direction to > > backport the changes to 5.7? > > > > Thanks, > > > > Oliver > > Is it fixed, or is it just randomly working? It now works all the time. So something was fixed in current. With 5.7 it never worked. Even with a very small ramdisk. I always run into the boot loop.
