Re: Booting OpenBSD on a HP Compaq Desktop

[Israel Brewster]

On Feb 26, 2018, at 8:10 AM, Stuart Henderson  wrote:
> 
> On 2018/02/26 07:50, Israel Brewster wrote:
>>On Feb 24, 2018, at 3:06 AM, Stuart Henderson  
>> wrote:
>> 
>>On 2018-02-24, Israel Brewster  wrote:
>> 
>>I have an HP Compaq Pro 6300 machine on which I am trying to run
>>OpenBSD. The installer boots and runs fine, but after rebooting into 
>> the
>>newly installed OS, I start getting the boot sequence (the white text 
>> on
>>blue background stuff - don't know what that is officially called), 
>> but
>>after a second or so the screen goes blank and that's all she wrote.
>> 
>>My first thought was that it was just a display issue, and that I
>>should be able to ssh in and tweak stuff, but as it turns out, the
>>machine never shows up on the network, either, so apparently it never
>>gets far enough in the boot process to enable the network (networking
>>*does* work while I am running through the installer, so I don't think
>>it's just a missing network driver there).
>> 
>> 
>>It sounds like it's crashing after the video mode is changed. The
>>machine probably has inteldrm so at the boot loader prompt, try
>>"boot -c", then at UKC "disable inteldrm" and "quit".
>> 
>> 
>> Bingo! that did the trick - got a good clean boot after running that 
>> command. The only issue
>> appears to be that I'm going to have to do that every time I boot. Given 
>> that, how do I make it
>> stick? Or, now that we know that is the issue, is there some other, more 
>> permanent "fix" I can
>> try? Do I need that inteldrm for any reason?
> 
> You'll want it if the machine will be running X.

It won't be. It's role in life is to be a FTP/SFTP server, so no need for X.

> 
> It's possible to modify an on-disk kernel with config(8)'s -e flag, but
> that has other problems (not least, syspatch won't be able to update the
> kernel).

Gotcha. It did work to allow ongoing booting, but I'll keep trying other 
solutions.

> 
>>That may let it boot, if not then you're at least more likely to see
>>a hidden error message of some sort.
>> 
>>If this is 6.2, try -current instead. If it's OpenBSD/i386, try amd64
>>instead.
>> 
>> 
>> Since disabling inteldrm seemed to bypass the issue, if only temporarily, 
>> would these still be
>> worth trying, or were they just additional suggestions if the inteldrm thing 
>> didn't work?
> 
> Definitely worth trying, it would be better to have a fix than a workaround,
> and without trying -current you won't know if it's already been fixed. With
> the information you've given so far we have very little idea about what you're
> running or what hardware.

My apologies, I mean't to mention that, but it slipped my mind (kind of like 
remembering to remove the stupid image signature my boss insists upon). This is 
a brand-new install of OpenBSD 6.2, running on a HP Compaq Pro 6300, stock 
hardware (no add-in cards or the like). 

> 
> Please send a bug report with the files generated from sendbug (run as root).
> It's often easiest to do "sendbug -P > /tmp/template.txt" then copy that to
> another machine, edit to add a description etc, and send the whole thing
> to b...@openbsd.org .

Will do. Thanks!

---
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
---

Re: Booting OpenBSD on a HP Compaq Desktop

[Stuart Henderson]

On 2018/02/26 07:50, Israel Brewster wrote:
> On Feb 24, 2018, at 3:06 AM, Stuart Henderson  
> wrote:
> 
> On 2018-02-24, Israel Brewster  wrote:
> 
> I have an HP Compaq Pro 6300 machine on which I am trying to run
> OpenBSD. The installer boots and runs fine, but after rebooting into 
> the
> newly installed OS, I start getting the boot sequence (the white text 
> on
> blue background stuff - don't know what that is officially called), 
> but
> after a second or so the screen goes blank and that's all she wrote.
> 
> My first thought was that it was just a display issue, and that I
> should be able to ssh in and tweak stuff, but as it turns out, the
> machine never shows up on the network, either, so apparently it never
> gets far enough in the boot process to enable the network (networking
> *does* work while I am running through the installer, so I don't think
> it's just a missing network driver there).
> 
> 
> It sounds like it's crashing after the video mode is changed. The
> machine probably has inteldrm so at the boot loader prompt, try
> "boot -c", then at UKC "disable inteldrm" and "quit".
> 
> 
> Bingo! that did the trick - got a good clean boot after running that command. 
> The only issue
> appears to be that I'm going to have to do that every time I boot. Given 
> that, how do I make it
> stick? Or, now that we know that is the issue, is there some other, more 
> permanent "fix" I can
> try? Do I need that inteldrm for any reason?

You'll want it if the machine will be running X.

It's possible to modify an on-disk kernel with config(8)'s -e flag, but
that has other problems (not least, syspatch won't be able to update the
kernel).

> That may let it boot, if not then you're at least more likely to see
> a hidden error message of some sort.
> 
> If this is 6.2, try -current instead. If it's OpenBSD/i386, try amd64
> instead.
> 
> 
> Since disabling inteldrm seemed to bypass the issue, if only temporarily, 
> would these still be
> worth trying, or were they just additional suggestions if the inteldrm thing 
> didn't work?

Definitely worth trying, it would be better to have a fix than a workaround,
and without trying -current you won't know if it's already been fixed. With
the information you've given so far we have very little idea about what you're
running or what hardware.

Please send a bug report with the files generated from sendbug (run as root).
It's often easiest to do "sendbug -P > /tmp/template.txt" then copy that to
another machine, edit to add a description etc, and send the whole thing
to b...@openbsd.org.

Re: Booting OpenBSD on a HP Compaq Desktop

[Israel Brewster]

> On Feb 24, 2018, at 3:06 AM, Stuart Henderson  wrote:
> 
> On 2018-02-24, Israel Brewster  wrote:
>> I have an HP Compaq Pro 6300 machine on which I am trying to run
>> OpenBSD. The installer boots and runs fine, but after rebooting into the
>> newly installed OS, I start getting the boot sequence (the white text on
>> blue background stuff - don't know what that is officially called), but
>> after a second or so the screen goes blank and that's all she wrote.
>> 
>> My first thought was that it was just a display issue, and that I
>> should be able to ssh in and tweak stuff, but as it turns out, the
>> machine never shows up on the network, either, so apparently it never
>> gets far enough in the boot process to enable the network (networking
>> *does* work while I am running through the installer, so I don't think
>> it's just a missing network driver there).
> 
> It sounds like it's crashing after the video mode is changed. The
> machine probably has inteldrm so at the boot loader prompt, try
> "boot -c", then at UKC "disable inteldrm" and "quit".

Bingo! that did the trick - got a good clean boot after running that command. 
The only issue appears to be that I'm going to have to do that every time I 
boot. Given that, how do I make it stick? Or, now that we know that is the 
issue, is there some other, more permanent "fix" I can try? Do I need that 
inteldrm for any reason?

> 
> That may let it boot, if not then you're at least more likely to see
> a hidden error message of some sort.
> 
> If this is 6.2, try -current instead. If it's OpenBSD/i386, try amd64
> instead.

Since disabling inteldrm seemed to bypass the issue, if only temporarily, would 
these still be worth trying, or were they just additional suggestions if the 
inteldrm thing didn't work?

---
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
---
> 
> 

Re: Booting OpenBSD on a HP Compaq Desktop

[Stuart Henderson]

On 2018-02-24, Israel Brewster  wrote:
> I have an HP Compaq Pro 6300 machine on which I am trying to run
> OpenBSD. The installer boots and runs fine, but after rebooting into the
> newly installed OS, I start getting the boot sequence (the white text on
> blue background stuff - don't know what that is officially called), but
> after a second or so the screen goes blank and that's all she wrote.
>
> My first thought was that it was just a display issue, and that I
> should be able to ssh in and tweak stuff, but as it turns out, the
> machine never shows up on the network, either, so apparently it never
> gets far enough in the boot process to enable the network (networking
> *does* work while I am running through the installer, so I don't think
> it's just a missing network driver there).

It sounds like it's crashing after the video mode is changed. The
machine probably has inteldrm so at the boot loader prompt, try
"boot -c", then at UKC "disable inteldrm" and "quit".

That may let it boot, if not then you're at least more likely to see
a hidden error message of some sort.

If this is 6.2, try -current instead. If it's OpenBSD/i386, try amd64
instead.

Re: Booting OpenBSD on a HP Compaq Desktop

[Tom Smyth]

Howdy Israel,
Try Ctrl-Alt- F1 or Ctrl -ALT-F2and so on and so fourth... until
you get a Cli login screen

 it sounds like

it boots command line fine and then it tries to load an X Session
(X  login Prompt) and there may be an issue with the
X config for your particular graphics hardware,
verify that it booted ok apart from the Graphic User interface,
by logging in on the command line on a different virtual terminal

once you have the command line access to the box

run
dmesg to get details on the hardware and exact version of
OpenBSD you are running (the blue writing output on boot)
and copy this detail to the list  to help others in the community
help you ...
you could also have a look at /var/log/messages for obvious errors
that might get you further along to having a fully working system
Hope this helps

On 24 February 2018 at 00:43, Israel Brewster  wrote:
> I have an HP Compaq Pro 6300 machine on which I am trying to run OpenBSD. The 
> installer boots and runs fine, but after rebooting into the newly installed 
> OS, I start getting the boot sequence (the white text on blue background 
> stuff - don't know what that is officially called), but after a second or so 
> the screen goes blank and that's all she wrote.
>
> My first thought was that it was just a display issue, and that I should be 
> able to ssh in and tweak stuff, but as it turns out, the machine never shows 
> up on the network, either, so apparently it never gets far enough in the boot 
> process to enable the network (networking *does* work while I am running 
> through the installer, so I don't think it's just a missing network driver 
> there).
>
> What can I do to fix this?
>
>
>



-- 
Kindest regards,
Tom Smyth

Mobile: +353 87 6193172
The information contained in this E-mail is intended only for the
confidential use of the named recipient. If the reader of this message
is not the intended recipient or the person responsible for
delivering it to the recipient, you are hereby notified that you have
received this communication in error and that any review,
dissemination or copying of this communication is strictly prohibited.
If you have received this in error, please notify the sender
immediately by telephone at the number above and erase the message
You are requested to carry out your own virus check before
opening any attachment.