Re: 7.1 on a IBM 43P, 7248-132

The PReP partition was set to use 5MB (as recommended in the 
documentation) and located in the first BIOS partition. Only the kernels 
2MB or less seem to make it to the boot loader for me. The <2MB serial 
console sysinit image will make it to the boot loader if I put it into 
the PReP partition, but will not boot past that point as mentioned in 
this thread:
http://mail-index.netbsd.org/port-prep/2017/06/27/msg000119.html


On 06/29/2017 03:32 AM, Artyom Tarasenko wrote:
> Is it a general issue, or was the PReP partition just too small in your setup?
>
> On Thu, Jun 29, 2017 at 10:15 AM, T <[email protected]> wrote:
>> Found that the kernel size is the issue by using mkbootimage with
>> install_small.fs and dding that into the PreP partition and getting that to
>> boot. Will end up doing the small kernel work around mentioned in the
>> referenced email thread.
>>
>>
>>
>> On 06/24/2017 06:37 PM, t wrote:
>>> Hello,
>>> I'm trying to get NetBSD 7.1 working on a 7248-132 but cannot get the
>>> computer to boot from the SCSI disk after installation. Booting the
>>> install kernel over the network seems to work with BOOTP/TFTP. After
>>> completing the installation process and restarting the machine, I load
>>> into the SMS and change the boot priority to boot from the SCSI disk
>>> instead of the network. Upon restarting and completing the boot screen,
>>> the computer ends up at a black screen and blinking cursor.
>>> I believe this issue may be related to this thread:
>>> https://mail-index.netbsd.org/port-prep/2014/07/thread1.html#000101
>>>
>>> This is my first time installing NetBSD so it could also be something I'm
>>> doing.
>>>
>>> I've tried re-writing the generic kernel to the prep partition with
>>> "mkbootimage" but that did not seem to work.
>>> Any help would be appreciated.
>>>
>>>
>>> One other thing I've noticed with this machine is interactions with the
>>> pcn0 device seem to occasionally lockup the machine. I originally was
>>> going to install the NetBSD binary packages from a NFS mount, but the
>>> system would lockup halfway through the installation of the second
>>> package. I bypassed this issue by using the CDROM instead.
>>>
>
>