OT>" prompt, but my USB keyboard does not appear to be recognised at
> this point in boot, so I cannot interrupt and set tty to fb0. The boot
> then proceeds to the serial console (i.e. blank screen).
>
> The thought occurred that it may be possible to change boot.conf in the
> mi
be recognised at
this point in boot, so I cannot interrupt and set tty to fb0. The boot
then proceeds to the serial console (i.e. blank screen).
The thought occurred that it may be possible to change boot.conf in the
miniroot69 image to set tty to fb0 but so far my attempts have been
unsuccessful.
I guess this would explain it.
/usr/src/sys/arch/amd64/stand/efiboot/efiboot.c:
efi_cons_getshifts(dev_t dev)
{
/* XXX */
return (0);
}
Any reason for this?
-alfred
boot(8) man page says:
"boot.conf processing can be skipped, and the automatic boot cancelled, by
holding down either Control key as boot starts."
I hold the ctrl key and boot still runs my boot.conf.
Is anyone else also having this issue?
# uname -a
OpenBSD upgrade.lan 6.7 GENERIC.MP
Theo wrote:
> Interesting. Wonder how common this is.
It could possibly come back in some future bios update bug/change as well
but very very rarely I would expect. This problem showed up for me in a
different way as well; My clock would always drift and ntpd would report
that it was always
> On Jul 13, 2020, at 6:58 AM, Alfred Morgan wrote:
>
>
> Brian wrote:
> > (echo boot /bsd.upgrade; echo boot) > /etc/boot.conf
>
> Brian, that doesn't work. I tried that already before. It seems to stop at
> the error not finding bsd.upgrade and won't
Alfred Morgan wrote:
> Theo wrote:
> > Figure out how to build and install. It is not hard to test.
>
> Thank you, I did as you suggested and I was able to narrow down the issue
> to this line of code in /usr/src/sys/arch/amd64/stand/efiboot/efiboot.c:
>
>
Theo wrote:
> Figure out how to build and install. It is not hard to test.
Thank you, I did as you suggested and I was able to narrow down the issue
to this line of code in /usr/src/sys/arch/amd64/stand/efiboot/efiboot.c:
EFI_CALL(ST->RuntimeServices->GetTime, , NULL);
The GetTime call would
I wrote:
> I attempted over the weekend and I'm trying but my new code is not taking.
> when I reboot I see "OpenBSD/amd64" not "HelloBoot/amd64"
I figured out the issue. I need to compile efiboot separately.
# cd /usr/src/sys/arch/amd64/stand/efiboot/
# make
# make install
...
This did the
Brian wrote:
> (echo boot /bsd.upgrade; echo boot) > /etc/boot.conf
Brian, that doesn't work. I tried that already before. It seems to stop at
the error not finding bsd.upgrade and won't continue.
-alfred
> Figure out how to build and install. It is not hard to test.
I attempted over the weekend and I'm trying but my new code is not taking.
I am using 6.6 release source code and it looks like I'm doing the right
steps but when I reboot UEFI I still see the old boot not my new HelloBoot
that I
> On Jul 10, 2020, at 7:31 PM, Alfred Morgan wrote:
>
>
>>
>> You claimed sysupgrade does this.
>> sysupgrade does nothing like that. It placed a /bsd.upgrade file, and
> that is the end of the story.
>> You told boot (via commands in boot.conf)
On 2020-07-10 15:37, Alfred Morgan wrote:
Please, I have had this problem for several versions now and it still isn't
working right.
I have this on all three of my servers:
echo boot > /etc/boot.conf
I have this boot.conf because openbsd fails to boot (on all three servers)
because it ha
Alfred Morgan wrote:
> > You claimed sysupgrade does this.
> > sysupgrade does nothing like that. It placed a /bsd.upgrade file, and
> that is the end of the story.
> > You told boot (via commands in boot.conf) to do something, so it did,
> before discovering the f
> You claimed sysupgrade does this.
> sysupgrade does nothing like that. It placed a /bsd.upgrade file, and
that is the end of the story.
> You told boot (via commands in boot.conf) to do something, so it did,
before discovering the file.
Theo,
When I mentioned sysupgrade I was
ade"
>
> I'm either missing something or one of these statements doesn't seem to be
> entirely
> true. I feel stuck with no options.
You claimed sysupgrade does this.
sysupgrade does nothing like that. It placed a /bsd.upgrade file, and that
is the end of the story.
You told boot (via commands in boot.conf) to do something, so it did, before
discovering the file.
020 at 3:43 PM Theo de Raadt wrote:
> Alfred Morgan wrote:
>
> > Please, I have had this problem for several versions now and it still
> isn't
> > working right.
> > I have this on all three of my servers:
> > echo boot > /etc/boot.conf
> >
> > I have th
Alfred Morgan wrote:
> Please, I have had this problem for several versions now and it still isn't
> working right.
> I have this on all three of my servers:
> echo boot > /etc/boot.conf
>
> I have this boot.conf because openbsd fails to boot (on all three server
Please, I have had this problem for several versions now and it still isn't
working right.
I have this on all three of my servers:
echo boot > /etc/boot.conf
I have this boot.conf because openbsd fails to boot (on all three servers)
because it hangs on the boot> prompt because of some ghost
On 2014-06-13, Jiri B ji...@devio.us wrote:
+.Pa /etc/boot.conf.OpenBSD-mm.nn-arch
The version info parts (and probably also arch) aren't very useful and are
a source of possible confusion as boot loader version isn't tightly coupled
to the OS version. Probably better just start with the MAC
Hi,
is there a plan to make pxeboot load additional config
like installer does it while prefixing path with MAC address?
- installer:
MAC address-install.conf
install.conf
- pxeboot:
/etc/boot.conf
There's old diff[1] which adds support for pxeboot loading
additional config which could
I have exactly the same problem.
When i redirect default console to com0
(set tty com0 in /etc/boot.conf) serial console on tty00 then is working.
But when i don't want to have default console there, then serial access is
not working, but
/usr/lib/getty std.9600 tty00 is running
Only if i edit
,
The /etc/boot.conf deals with loading the kernel - adding set tty
com0 tells the kernel to use com0 as the default console.
Using boot.conf won't solve your serial console issue man 4 cua might help...
Fred
showing getty was running on
/dev/tty00), so I ran fstat /dev/tty00 and
nothing showed up. Then I rebooted and checked again. Still nothing in
fstat, nothing on the serial port, and getty
was still running on /dev/tty00.
I added 'set tty com0' to /etc/boot.conf, rebooted, and then logged in and
ran
Hi folks,
Short question: Is there some magic in /etc/boot.conf I could
use to reset the terminal before booting?
Here is the problem:
AFAICS the BIOS in my Supermicro board switches to black chars
on a black background before disabling console redirection and
handing off control to the OpenBSD
I use a amd64 MP server, default boot into GENERIC, not GENERIC.MP.
I can use boot.conf boot into GENERIC.MP, but this remove the 5
second pause at boot-time.
How can I default boot into GENERIC.MP, and not remove the 5 second
pause at boot-time?
Thanks for some help,
Dongsheng Song
On Mon, Jun 16, 2008 at 05:19:16PM +0800, Dongsheng Song wrote:
| I use a amd64 MP server, default boot into GENERIC, not GENERIC.MP.
|
| I can use boot.conf boot into GENERIC.MP, but this remove the 5
| second pause at boot-time.
Then you probably have the following boot.conf :
boot
On Mon, Jun 16, 2008 at 05:19:16PM +0800, Dongsheng Song wrote:
I use a amd64 MP server, default boot into GENERIC, not GENERIC.MP.
I can use boot.conf boot into GENERIC.MP, but this remove the 5
second pause at boot-time.
How can I default boot into GENERIC.MP, and not remove the 5 second
On Mon, Jun 16, 2008 at 05:19:16PM +0800, Dongsheng Song wrote:
How can I default boot into GENERIC.MP, and not remove the 5 second
pause at boot-time?
Use the following in your boot.conf:
set image bsd.mp
man boot.conf for more details...
On Mon, Jun 16, 2008 at 05:19:16PM +0800, Dongsheng Song wrote:
I use a amd64 MP server, default boot into GENERIC, not GENERIC.MP.
I can use boot.conf boot into GENERIC.MP, but this remove the 5
second pause at boot-time.
How can I default boot into GENERIC.MP, and not remove the 5 second
On Mon, Jun 16, 2008 at 11:28:36AM +0200, Michiel van Baak wrote:
How can I default boot into GENERIC.MP, and not remove the 5 second
pause at boot-time?
cd / mv bsd bsd.up mv bsd.mp bsd reboot
This is not really good advice, because it breaks next time you
accidentally copy the wrong
Hello!
Do you know why bootloader ignores option
set device cd0a
on etc/boot.conf while booting from cd?
It's always asking me about root device.
I'm trying to build livecd from snapshot and I'usinf GENERIC kernel,
all works fine, except what I must specify boot device each time
On Mon, Mar 31, 2008 at 06:21:30PM +0400, B A wrote:
Hello!
Do you know why bootloader ignores option
set device cd0a
on etc/boot.conf while booting from cd?
It's always asking me about root device.
because root on cd is not supported.
there are diffs that were sent about 2-3y ago
Hello!
Do you know why bootloader ignores option
set device cd0a
on etc/boot.conf while booting from cd?
It's always asking me about root device.
I'm trying to build livecd from snapshot and I'usinf GENERIC kernel,
all works fine, except what I must specify boot device each time
the LookXP source
packages from http://lxp.sourceforge.net. I have not knowingly touched
the boot.conf file at all so I'm at a loss as to how the above error is
showing.
I have read the biosboot(8) man page but it didn't help. I am new to
OpenBSD having come from a brief linux background
except bsd.mp and
game41.tgz) and it was working fine. The only thing I did after re-install
was add a few packages and ports and compile the LookXP source packages from
http://lxp.sourceforge.net. I have not knowingly touched the boot.conf file
at all so I'm at a loss as to how the above error
-installed the whole OS yesterday (everything except bsd.mp and
game41.tgz) and it was working fine. The only thing I did after re-install
was add a few packages and ports and compile the LookXP source packages from
http://lxp.sourceforge.net. I have not knowingly touched the boot.conf file
at all
Hello,
I would like to run an OpenBSD machine where I want that the boot prompt
disappears, reason is that I do not want others having access to the
boot prompt.
In case you put a boot into boot.conf or set timeout to zero then you
do not have the opportunity to boot in single user when
On Fri, Feb 24, 2006 at 02:53:06PM +0100, Michael Schmidt wrote:
Hello,
I would like to run an OpenBSD machine where I want that the boot prompt
disappears, reason is that I do not want others having access to the
boot prompt.
In case you put a boot into boot.conf or set timeout to zero
On 2/24/06, Michael Schmidt [EMAIL PROTECTED] wrote:
Hello,
I would like to run an OpenBSD machine where I want that the boot prompt
disappears, reason is that I do not want others having access to the
boot prompt.
In case you put a boot into boot.conf or set timeout to zero then you
do
Boot off of the cd38.iso, mount your / partition and remove
your /etc/boot.conf is the first way that comes to mind.
You could also work some magic with the boot prompt that you get from booting
off the CD. Something like boot -s hd0a:/bsd should do it and I'm sure I
could find a half
On Friday, February 24, Michael Schmidt wrote:
In case you put a boot into boot.conf or set timeout to zero then you
do not have the opportunity to boot in single user when it may be
necessary. Are there ways to circumvent the latter?
With physical access to the machine, yes
Hi,
I'm working on an amd64 box (Opteron 146) with a soft raid with
autoconfig in place. The soft raid works fine, but boot.conf is
somewhat weird. Some experimenting revealed that I have three
partitions which are recognized as boot partitions:
/dev/wd0a, /dev/wd1a, and /dev/raid0a.
On /dev
On Fri, Jan 27, 2006 at 06:05:16PM +0100, Toni Mueller wrote:
- /etc/boot.conf ---
set timeout 30
boot /bsd.mpr
- /etc/boot.conf ---
The boot commands instructs it to boot there and then.
On 2006/01/27 17:30, John Wright wrote:
On Fri, Jan 27, 2006 at 06:05:16PM +0100, Toni Mueller wrote:
- /etc/boot.conf ---
set timeout 30
boot /bsd.mpr
- /etc/boot.conf ---
The boot commands instructs it to boot there and then.
'set image
On Friday, January 27, Toni Mueller wrote:
- /etc/boot.conf ---
set timeout 30
boot /bsd.mpr
- /etc/boot.conf ---
This should give me a 30 second pause before the machine boots the
named kernel, but instead, it boots _immediately_, so I have
[EMAIL PROTECTED]
Cc: misc@openbsd.org
Subject: Re: Sad boot problem (boot.conf: invalid argument)
Hello, Stuart. Thanks for sending me a copy of your reply. I
don't know if anyone else has added anything to this thread
because I subscribe in digest mode. So here is all the info you
told me
--On 09 June 2005 00:42 -0300, Luciano ES wrote:
First off, the boot error message:
Loading...
probing: pc0 com0 com1 apm mem [508K 254M a20=on]
disk: fd0 hd0+* hd1+* hd2*
OpenBSD/i386 BOOT 2.06
open(hd0a:/etc/boot.conf): Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid
Hello, Stuart. The answers to your latest questions:
On 09/06/05 at 12:11, Stuart Henderson wrote in 7K:
How does 'fdisk wd0' look?
- The second slice (offset 63) was marked as unknown. Then I fixed it with
OpenBSD's fdisk. Now it is marked as OpenBSD. The problem is that I have
done that many
On Thursday, June 9, Luciano ES wrote:
Hello, Stuart. The answers to your latest questions:
On 09/06/05 at 12:11, Stuart Henderson wrote in 7K:
How does 'fdisk wd0' look?
- The second slice (offset 63) was marked as unknown. Then I fixed it with
OpenBSD's fdisk. Now it is marked as
On 6/9/05, Luciano ES [EMAIL PROTECTED] wrote:
Hello, Stuart. The answers to your latest questions:
On 09/06/05 at 12:11, Stuart Henderson wrote in 7K:
How does 'fdisk wd0' look?
- The second slice (offset 63) was marked as unknown. Then I fixed it with
OpenBSD's fdisk. Now it is marked
with the very good experience I had in my
tests, I have already installed it three times because of a problem that
beats the heck out of me. You certainly have heard about it before:
disk: fd0 hd0+
OpenBSD/i386 BOOT 2.02
open(hd0a:/etc/boot.conf: Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd
I am sorry, I forgot to say that my motherboard is an Asus A7N 266 VM. I am
sure that someone will want to know.
--
Luciano Espirito Santo
Santos, SP - Brasil
BOOT 2.02
open(hd0a:/etc/boot.conf: Invalid argument
boot
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
failed(22). will try /obsd
boot
booting hd0a:/obsd: open hd0a:/obsd: Invalid argument
failed(22). will try /bsd.old
My first line is different from disk: fd0 hd0+ because I have three
54 matches
Mail list logo
