[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-misc
Subject:    Re: boot error: 'entry point at 0xffffffff81001000'
From:       J Dragu <jack.dragu () gmail ! com>
Date:       2021-10-30 21:04:19
Message-ID: ba4acdf4-4f49-4365-3b18-b55c33e689f8 () gmail ! com
[Download RAW message or body]

It turned out to be a problem with the hardware, not the OS. My 
apologies. Thank you very much for your help.

On 10/28/21 10:01 PM, Mike Larkin wrote:
> On Thu, Oct 28, 2021 at 09:26:33PM -0500, J Dragu wrote:
>> Trying with a snapshot returned the same error.
>>
>> Here's what it tells me when I check machine memory:
>>
>>> Low ram: 634KB High ram: 3065328KB
>>> Total free memory: 8179378KB
>> On Thu, Oct 28, 2021 at 20:04 Mike Larkin <mlarkin@nested.page> wrote:
>>
>>> On Thu, Oct 28, 2021 at 06:57:46PM -0500, J Dragu wrote:
>>>> Hello,
>>>>
>>>> I know there was a previous thread here about a perhaps similar issue
>>>> with 6.8 (?), but since from what I can tell it was fixed with 6.9
>>>> I figured I'd ask about my problem. If there's something obvious I'm
>>>> missing I do apologize!
>>>>
>>>> I'm trying to install OpenBSD 7.0 on a Thinkpad T410 from a USB stick.
>>>> Whenever I try to boot in to the installer I get the following messages:
>>>>
>>>>> cannot open hd0a:/etc/random.seed: No such file or directory
>>>>> booting hd0a:/7.0/amd64/bsd.rd: 38030471+1598464+3907256+0+704512
>>>> [109+288+28]=0x995530
>>>>> entry point at 0xffffffff81001000
>>>> ... at which point it becomes unresponsive. I've checked to make sure
>>>> the BIOS are up to date (1.45, going by Lenovo's website), and also
>>>> fiddled with some settings like disabling hyperthreading, to no avail.
>>>> I'm writing this email from my X61s (which is running 7.0 just fine)
>>>> and I tried putting this SSD in the T410 and got the exact same results,
>>>> so I suppose the issue isn't with the installer itself (?). Has anyone
>>>> else encountered this?
>>>>
>>>> Thank you for reading.
>>>> J
>>>>
>>> 2 things to try:
>>>
>>> 1. get a latest snap if you didn't already.
>>>
>>> 2. boot>   machine memory
>>>   ... and show the result here.
>>>
> You'll probably need to bisect builds and find where it started failing.
>
> -ml

[prev in list] [next in list] [prev in thread] [next in thread]