> Did you inject RPI UEFI firmware into the BOOT partition?
Are you talking about some third-party bootloader software? No, I'm
using the default U-Boot that comes with the miniroot. No modification
required.
I've upgraded from 7.4 to 7.5 and had no issues with the Raspberry Pi 4 model
B. Ethernet works for me - during the installation and afterwards. I use it as
a home server.
To connect to it, I use the serial console. The root storage device is a USB
(v3.X) stick, and it's encrypted with a
On Tue, Apr 16, 2024 at 06:08:13PM +0200, Peter J. Philipp wrote:
> On Tue, Apr 16, 2024 at 04:35:23PM +0100, Polarian wrote:
>
> > Does anyone have any suggestions on what I could try?
> OpenBSD 7.5-current (GENERIC.MP) #11: Thu Apr 11 17:03:03 MDT 2024
>
On Tue, Apr 16, 2024 at 04:35:23PM +0100, Polarian wrote:
> Does anyone have any suggestions on what I could try?
Hi, I too have a RPI 4b that is currently my workstation. Near the time of
release I was building my own base and packages, which was right near the
times of the ld.so changes,
Here is my blog post on how I got this working -
https://blog.adamretter.org.uk/running-openbsd-74-under-utm/
On Sat, 13 Jan 2024 at 19:55, Adam Retter wrote:
>
> I've had some success with this on Intel Mac, although it requires some
> workarounds. I'm in the process of writing a blog, I'll
> On Jan 12, 2024, at 21:31, Implausibility wrote:
>
> Hi.
>
> Since there's some uncertainty around the future of VMware Fusion on the Mac,
> I've decided to switch to UTM (with QEMU under the covers) -- but I can't
> seem to get OpenBSD .isos (7.3 or 7.4) to boot -- instead, I get dumped
Sorry if I pop up in the thread with my argument:
before all, anyone know the shortcut to boot a Mac Pro from a usb stick
to install OpenBSD?
> N0\/\/@r€Z
> --
> /\/\@rk€T
I've had some success with this on Intel Mac, although it requires some
workarounds. I'm in the process of writing a blog, I'll post it here in the
next few days if I can...
On Fri, 12 Jan 2024, 22:32 Implausibility, wrote:
> Hi.
>
> Since there's some uncertainty around the future of VMware
Hi.
Since there's some uncertainty around the future of VMware Fusion on the Mac,
I've decided to switch to UTM (with QEMU under the covers) -- but I can't seem
to get OpenBSD .isos (7.3 or 7.4) to boot -- instead, I get dumped into the
UEFI shell, which is a dead end.
I've done a number of
Aug 4, 2023, 08:19 by jfsimon1...@gmail.com:
> Further multi-boot is absolutely not a good idea from experience. Some OS
> just don't care about your boot, they claim they own the platform and will
> occasionally quite mess with it.
>
> That's not just Windows.
>
Some OSs including OpenBSD
Further multi-boot is absolutely not a good idea from experience. Some OS
just don't care about your boot, they claim they own the platform and will
occasionally quite mess with it.
That's not just Windows.
Best option is multi drive and select bootable drive on bios short-key
but each
one is
Always the right one
On 7/31/23 17:37, Theo de Raadt wrote:
Omar Polo wrote:
On 2023/07/31 17:19:59 +0200, Karel Lucas wrote:
Hi,
But fdisk also has an option to edit the existing partition table.
only if you want to do stuff manually, which from the thread I assume
you don't need.
On 8/3/23 16:48, Karel Lucas wrote:
Hi,
My openBSD installation was successful! I first removed all partitions
except for the EFI partition, which I left. Second I created one openBSD
partition(type A6) on the freed space, after which I partitioned that
partition with auto layout. Then I
On Thu, 2023-08-03 at 22:48 +0200, Karel Lucas wrote:
>
> Hi,
>
> My openBSD installation was successful!
Have fun on OpenBSD.
> I first removed all partitions
> except for the EFI partition, which I left.
Sure, the EFI partition isn't supposed to be formatted/recreated but
shared among
Hi,
My openBSD installation was successful! I first removed all partitions
except for the EFI partition, which I left. Second I created one openBSD
partition(type A6) on the freed space, after which I partitioned that
partition with auto layout. Then I continued with the regular
On Wed, Aug 2, 2023 at 7:31 AM David Demelier wrote:
> On Tue, 2023-08-01 at 01:00 +0800, ykla wrote:
> > Actually, I think it's a bug that OpenBSD cannot create EFI
> > partitions manually.
>
> I've installed OpenBSD many times in dualboot with linux (for some
> things we can't do right now on
On Tue, 2023-08-01 at 01:00 +0800, ykla wrote:
> Actually, I think it's a bug that OpenBSD cannot create EFI
> partitions manually.
I've installed OpenBSD many times in dualboot with linux (for some
things we can't do right now on OpenBSD such as ESP32 development). And
my take is to install
On Mon, Jul 31, 2023 at 04:08:49PM +0200, Karel Lucas wrote:
>
> Hi,
>
> Multi-boot is not an option here. The intention is to replace the entire
> PfSense installation with openBSD. Eventually this computer becomes a
> firewall with PF, so the current installation is unnecessary. But my
>
Karel Lucas said on Mon, 31 Jul 2023 16:08:49 +0200
>Hi,
>
>Multi-boot is not an option here. The intention is to replace the
>entire PfSense installation with openBSD. Eventually this computer
>becomes a firewall with PF, so the current installation is
>unnecessary. But my question remains
On Mon, Jul 31, 2023, at 12:00 PM, ykla wrote:
> Any manually created efi
> partition system will not be recognized.
I can assure you, it will (when done correctly). I have done so
manually/scripted with EFI+GPT and EFI+MBR many times. An example of the less
common EFI+MBR approach for the
Multiboot support will never be a priority in OpenBSD.
None of the developers are using multiboot scenarios. We develop and
test OpenBSD to support what we use, that is why it is so good at what
it does, and that is also also why it sucks ass for multiboot.
I suggest you get over it. If that
Actually, I think it's a bug that OpenBSD cannot create EFI partitions
manually. File systems that write MSDOS, mount points that write /boot/efi,
or none at all are not recognized by the system, and the installer will
indicate that it can't install the boot and fail to boot the system. If you
On Mon, Jul 31, 2023 at 09:37:13AM -0600, Theo de Raadt wrote:
> Omar Polo wrote:
>
> > On 2023/07/31 17:19:59 +0200, Karel Lucas wrote:
> > >
> > > Hi,
> > >
> > > But fdisk also has an option to edit the existing partition table.
> >
> > only if you want to do stuff manually, which from
On Sun, Jul 30, 2023 at 07:30:27PM +0200, Karel Lucas said:
Should I keep the (U)EFI partition? And if so, how do I mount the
future openBSD root partition to this (U)EFI installation? Are there
any other things I should watch out for? I look forward to receiving
responses from this community.
Omar Polo wrote:
> On 2023/07/31 17:19:59 +0200, Karel Lucas wrote:
> >
> > Hi,
> >
> > But fdisk also has an option to edit the existing partition table.
>
> only if you want to do stuff manually, which from the thread I assume
> you don't need.
>
> > This
> > allows me to delete only the
On 2023/07/31 17:19:59 +0200, Karel Lucas wrote:
>
> Hi,
>
> But fdisk also has an option to edit the existing partition table.
only if you want to do stuff manually, which from the thread I assume
you don't need.
> This
> allows me to delete only the partitions related to PfSense without
>
Hi,
But fdisk also has an option to edit the existing partition table. This
allows me to delete only the partitions related to PfSense without
deleting the (U)EFI partition. The question here is whether I will need
it to boot openBSD's root partition.
Op 31-07-2023 om 16:10 schreef Theo
Karel Lucas wrote:
> Multi-boot is not an option here. The intention is to replace the entire
> PfSense installation with openBSD. Eventually this computer becomes a
> firewall with PF, so the current installation is unnecessary. But my
> question remains whether I need the (U)EFI partition
Hi,
Multi-boot is not an option here. The intention is to replace the entire
PfSense installation with openBSD. Eventually this computer becomes a
firewall with PF, so the current installation is unnecessary. But my
question remains whether I need the (U)EFI partition for that or not.
Can
00:06 schreef Saïd AARAB:
Hi,
It depends if you want to keep the existing psfsens install or if you
want dual boot.
If looking to install beside pfsens, I would beleive that installing
OpenBSD along any existing OS should be no different than installing
linux or windows along another OS
On Mon, Jul 31, 2023 at 07:52:02AM -0400, Nick Holland wrote:
>
> IF you want to multiboot, just don't until you can answer questions like
> this yourself. Multibooting is very complicated, and requires a mastery
> of the boot process of ALL the OSs installed. People often consider it
> a way
On 7/30/23 13:30, Karel Lucas wrote:
Hi all,
I'm going to install openBSD on a small PC that currently has PfSense on
it. This PC boots this OS via (U)EFI, and therefore has an EFI partition
on the existing SSD. The current partition table looks like, as shown by
openBSD fdisk:
0: efiboot0
On Sun, Jul 30, 2023 at 07:30:27PM +0200, Karel Lucas wrote:
>
> Hi all,
>
> I'm going to install openBSD on a small PC that currently has PfSense on it.
> This PC boots this OS via (U)EFI, and therefore has an EFI partition on the
> existing SSD. The current partition table looks like, as shown
Good morning,
I'll preface this with: I'm a new OpenBSD user.
Yes you should keep the EFI partition...but the OpenBSD installer is
pretty thorough and easy to use if you don't have any special
circumstances.
I too started with pfsense and swapped to OpenBSD as a learning
exercise. But I did that
Hi,
It depends if you want to keep the existing psfsens install or if you
want dual boot.
If looking to install beside pfsens, I would beleive that installing
OpenBSD along any existing OS should be no different than installing
linux or windows along another OS, as you would need to prepare
Hi all,
I'm going to install openBSD on a small PC that currently has PfSense on
it. This PC boots this OS via (U)EFI, and therefore has an EFI partition
on the existing SSD. The current partition table looks like, as shown by
openBSD fdisk:
0: efiboot0
1: gptboot0
2: swap0
3: zfs0.
On Thu, May 18, 2023 at 10:05 AM Daniele B. wrote:
>
> Don't think your platform is supported:
> https://www.openbsd.org/plat.html
> https://www.openbsd.org/macppc.html
>
> otherwise let us know, I will install it on mine too ;d)
Top-posting is messy but I'll try it this way!
OPs states that
Don't think your platform is supported:
https://www.openbsd.org/plat.html
https://www.openbsd.org/macppc.html
otherwise let us know, I will install it on mine too ;d)
-- Daniele Bonini
May 18, 2023 08:39:07 yellowcutterpillow :
> Hello!
>
> I wanted to install OpenBSD on my Macbook Pro 8,1
Hello!
I wanted to install OpenBSD on my Macbook Pro 8,1 (Early/Late 2011)
but seem to fail. When I boot up install73.img or miniroot73.img, they
boot up, but when I actually boot up the ramdisk, bsd or bsd.rd, they
stuck up at a message about aicp0 being remapped or something. I would
try to
Il Sab 29 Ott 2022, 01:02 Jeff Ross ha scritto:
> Hi all,
>
> I got a nice new laptop at Costco for under $200. I did the developer
> mode to get to a linux shell and installed a bunch of programs but I'd
> rather just wipe the whole disk and install OpenBSD.
>
> All of places I'm finding with
You can't just boot any old USB from a Chromebook. It has a locked down
BIOS. More information here:
https://mrchromebox.tech/
On 10/28/22 17:59, Jeff Ross wrote:
Hi all,
I got a nice new laptop at Costco for under $200. I did the developer
mode to get to a linux shell and installed a
On 10/29/22 8:50 AM, Nick Holland wrote:
On 10/29/22 10:11, Jeff Ross wrote:
On 10/29/22 1:29 AM, Stuart Henderson wrote:
On 2022-10-28, Gabriel Busch de Brito wrote:
All of places I'm finding with directions on how to do this are
from circa
2015 and do not work now.
Anybody have a
On 10/29/22 10:11, Jeff Ross wrote:
On 10/29/22 1:29 AM, Stuart Henderson wrote:
On 2022-10-28, Gabriel Busch de Brito wrote:
All of places I'm finding with directions on how to do this are from circa
2015 and do not work now.
Anybody have a pointer to a more updated set of directions I
As it seems to be an x86_64 machine why not try a fresh OpenBSD
Live system via USB or DVD and and see what happens?
https://fuguita.org/
Wolfgang
On Sat, Oct 29, 2022 at 08:11:15AM -0600, Jeff Ross wrote:
On 10/29/22 1:29 AM, Stuart Henderson wrote:
On 2022-10-28, Gabriel Busch de Brito
On 10/29/22 1:29 AM, Stuart Henderson wrote:
On 2022-10-28, Gabriel Busch de Brito wrote:
All of places I'm finding with directions on how to do this are from circa
2015 and do not work now.
Anybody have a pointer to a more updated set of directions I can try?
I suggest that you follow
On 2022-10-28, Gabriel Busch de Brito wrote:
>
>> All of places I'm finding with directions on how to do this are from circa
>> 2015 and do not work now.
>>
>> Anybody have a pointer to a more updated set of directions I can try?
> I suggest that you follow the installation guide at the FAQ
> All of places I'm finding with directions on how to do this are from circa
> 2015 and do not work now.
>
> Anybody have a pointer to a more updated set of directions I can try?
I suggest that you follow the installation guide at the FAQ section of
the website.
Best,
G
Hi all,
I got a nice new laptop at Costco for under $200. I did the developer
mode to get to a linux shell and installed a bunch of programs but I'd
rather just wipe the whole disk and install OpenBSD.
All of places I'm finding with directions on how to do this are from
circa 2015 and do
Hi all,
I got a nice new laptop at Costco for under $200. I did the developer
mode to get to a linux shell and installed a bunch of programs but I'd
rather just wipe the whole disk and install OpenBSD.
All of places I'm finding with directions on how to do this are from
circa 2015 and do
Hello,
I'm not Sure but shouldn't it be
cd: /mnt/usr/share/zoneinfo
instead of:
cd: /mnt/user/share/zoneinfo
?
regards
Am 13. September 2021 15:48:02 MESZ schrieb Sandeep Gupta
:
>Hello,
>
> I am stuck on installing openbsd 6.8 (or 6.9) on rpi 4. I am able to
>boot the openbsd i
Hello,
I am stuck on installing openbsd 6.8 (or 6.9) on rpi 4. I am able to
boot the openbsd installer off of USB
drive using UEFI boot loader (on sd card). However the installer
fails at the step "What timezone are you in?".
It doesn't like any timezone I input. Just before this
Hi,
I tried installing OpenBSD on an Oracle Cloud arm64 VM. Here's what I
did:
1. Download the arm64/install69.img
2. dd if=install69.img of=/dev/sda conv=fsdatasync bs=4096
3. echo b > /proc/sysrq-trigger
During step 2, I downloaded the install69.img into /run, which is a
ramd
You can also install Windows after and boot OpenBSD quite easily by following
the faq. This is not easy on grub/Linux as grub is greedy. Atleast the guides
that I found for grub/Linux, failed to work. I have no interest in running Linux
these days though and little interest then. I had the notion
On Monday, April 13, 2020, Никита Степанов
wrote:
>
Yes
On Fri, 29 Nov 2019, Clay Daniels wrote:
Date: Fri, 29 Nov 2019 12:55:43 -0600
From: Clay Daniels
To: "misc@openbsd.org"
Subject: Re: Installing OpenBSD -current snapshots
Thanks to everyone who responded. If I knew all the answers I would not
have asked. And I should have r
Thanks to everyone who responded. If I knew all the answers I would not
have asked. And I should have read deeper into the documentation before
asking, and am in the process of doing so now.
What I decided was to stick with the release install66.fs boot image. It
works to completely install
On 2019-11-29 02:26, Clay Daniels wrote:
> Nick, thanks for straightening me out about what is actually going on here
> with the install. I see that there is now a fresh snapshot with today's
> date, not the one I downloaded and ran yesterday. This might tend to keep
> one busy. I'm not sure I
> BTW, why do you want to run -current?
> There are only 2 real reasons to do that
> [ ... ]
Total nonsense ...
On Fri, Nov 29, 2019, at 2:26 AM, Clay Daniels wrote:
> Nick, thanks for straightening me out about what is actually going on here
> with the install. I see that there is now a fresh snapshot with today's
> date, not the one I downloaded and ran yesterday. This might tend to keep
> one busy. I'm
On 29.11.2019 08:45, Clay Daniels wrote:
Another question. I know I need to write the boot file to the usb drive
thus:
# dd if=install66.fs of=/dev/da0 bs=1M conv=sync
But can I just use plain old "cp base66.tgz /mnt" etc for the other
files?
Sounds like you are rushing too quickly and
On Fri, Nov 29, 2019 at 01:45:37AM -0600, Clay Daniels wrote:
> Another question. I know I need to write the boot file to the usb drive
> thus:
> # dd if=install66.fs of=/dev/da0 bs=1M conv=sync
> But can I just use plain old "cp base66.tgz /mnt" etc for the other files?
the installnn.fs image
Another question. I know I need to write the boot file to the usb drive
thus:
# dd if=install66.fs of=/dev/da0 bs=1M conv=sync
But can I just use plain old "cp base66.tgz /mnt" etc for the other files?
On Fri, Nov 29, 2019 at 1:26 AM Clay Daniels
wrote:
> Nick, thanks for straightening me out
Nick, thanks for straightening me out about what is actually going on here
with the install. I see that there is now a fresh snapshot with today's
date, not the one I downloaded and ran yesterday. This might tend to keep
one busy. I'm not sure I would not be better off doing what Bruno & Marc
On 2019-11-27 21:29, Edgar Pettijohn wrote:
> On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> I have successfully installed OpenBSD 6.6 release and would like to give
>> the Current Snapshots a try. I went to a mirror, and to:
>>
>> Index of /pub/OpenBSD/snapshots/amd64/
>>
>> I
On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
Just run sysupgrade -s
Done.
On Nov 28, 2019 2:15 AM, Bruno Flueckiger wrote:
>
> On 27.11., Clay Daniels wrote:
> > I have successfully installed OpenBSD 6.6 release and would like to give
> > the Current Snapshots a try. I went to a mirror, and to:
> >
> > Index of /pub/OpenBSD/snapshots/amd64/
> >
> > I saw install66.fs
On 27.11., Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
>
> Index of /pub/OpenBSD/snapshots/amd64/
>
> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> for a
On Wed, 27 Nov 2019 20:29:27 -0600
Edgar Pettijohn wrote:
> On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> > I have successfully installed OpenBSD 6.6 release and would like to
> > give the Current Snapshots a try. I went to a mirror, and to:
> >
> > Index of
On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
>
> Index of /pub/OpenBSD/snapshots/amd64/
>
> I saw install66.fs (probably for usb memstick) and
Never mind, I found the instructions the the same mirror directory,in a
plain text file called "INSTALL.amd64".
Forgive the dummy here,
Clay
On Wed, Nov 27, 2019 at 8:05 PM Clay Daniels
wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a
I have successfully installed OpenBSD 6.6 release and would like to give
the Current Snapshots a try. I went to a mirror, and to:
Index of /pub/OpenBSD/snapshots/amd64/
I saw install66.fs (probably for usb memstick) and install66.iso (surely
for a cd/dvd) at ~450Mb. I picked the install66.fs,
f: Re: Blank screen after installing OpenBSD 6.5
>
> On Wed, Jul 17, 2019 at 01:15:26PM +0200, oxst...@gmx.net wrote:
> > Hello,
> >
> > I recently installed OpenBSD 6.5 on an i386 router.
> > The intallation process went fine. However, I got a black screen after
On Wed, Jul 17, 2019 at 01:32:37PM +0200, Stefan Sperling wrote:
> On Wed, Jul 17, 2019 at 01:15:26PM +0200, oxst...@gmx.net wrote:
> > Hello,
> >
> > I recently installed OpenBSD 6.5 on an i386 router.
> > The intallation process went fine. However, I got a black screen after
> > rebooting.
> >
On Wed, Jul 17, 2019 at 01:15:26PM +0200, oxst...@gmx.net wrote:
> Hello,
>
> I recently installed OpenBSD 6.5 on an i386 router.
> The intallation process went fine. However, I got a black screen after
> rebooting.
>
> I tried opening a SSH session, but the computer doesn't reply.
>
> The
have a look at man boot ...
you need to set tty to the correct serial port com0 com1 etc...
and you need to set the Baud rate... spec .. depending rotuer baud settings
115200 and N 8 1 ...
On Wed, 17 Jul 2019 at 12:22, wrote:
> Hello,
>
> I recently installed OpenBSD 6.5 on an i386 router.
>
Hello,
I recently installed OpenBSD 6.5 on an i386 router.
The intallation process went fine. However, I got a black screen after
rebooting.
I tried opening a SSH session, but the computer doesn't reply.
The screen is attached using a VGA cable. The computer send a signal over that
cable. If
apparently the F-35 project sources motherboards for key instrumentation
from China.
This is a new economic cold war. Do what you feel best but a big part of
this is politics.
Maybe the list should qualify when a mail thread is verging on personal
politics and out of strictly technical
Sun, 16 Jun 2019 05:23:36 +0200 ms
> "It looks like at least the reengineering of the firmware
>
> and the analysis of the code could increase the security, to avoid
> security wholes"
> ^^
Your clock is off. Wrong time is a serious reliability & security flaw.
Before you look
On 2019-06-15, ms wrote:
> https://www.golem.de/news/supermicro-diskussion-um-ueberwachungschips-1810-136965.html
>
> https://www.heise.de/security/meldung/Bericht-Winzige-Chips-spionierten-in-Cloud-Servern-von-Apple-und-Amazon-4181461.html
Those are based on the discredited Bloomberg piece I
And I think I read that Supermicro is moving production
out of China because of the perceptions of risk (and/or actual
risks) of sensitive electronics manufacturing there.
Forgive/ignore if this question is excessive here, but I
wonder if anyone has knowledge or educated perspective to share
On 16/6/19 1:23 pm, ms wrote:
>>> Now a day backdors are already on the silicon level (inside chips). They
>>> are declared as debugging interfaces..
>> Must have happened around the time when school dropouts went to business.
>
> What do you want to say? Do you have experience in chip design?
I am sorry for NOT reading my content again before posting it, my fault.
On 16.06.19 06:35, li...@wrant.com wrote:
Sat, 15 Jun 2019 23:52:18 +0200 ms
Now a day backdors are already on the silicon level (inside chips). They
are declared as debugging interfaces..
Must have happened around the
Sat, 15 Jun 2019 23:52:18 +0200 ms
> Now a day backdors are already on the silicon level (inside chips). They
> are declared as debugging interfaces..
Must have happened around the time when school dropouts went to business.
> It looks like at least the reengineering of the frimware an it is
https://www.golem.de/news/supermicro-diskussion-um-ueberwachungschips-1810-136965.html
https://www.heise.de/security/meldung/Bericht-Winzige-Chips-spionierten-in-Cloud-Servern-von-Apple-und-Amazon-4181461.html
Now a day backdors are already on the silicon level (inside chips). They
are
My understanding is that a well known linux vendor was disabling kernel ACPI
APEI & EINJ parameter support by default.
"ACPI provides an error injection mechanism, EINJ, for debugging and testing
the ACPI Platform Error Interface (APEI) and other RAS features. If
supported by the firmware, ACPI
On 2019-06-15, ms wrote:
> There were some serious security issues with hardware and software from
> Supermicro (espionage chips, firmware)
Assuming you mean the allegations in that Bloomberg piece, there was no
evidence found supporting them.
There were some serious security issues with hardware and software from
Supermicro (espionage chips, firmware)
For me a NoGo!
On 15.06.19 12:52, Andrew Luke Nesbit wrote:
On 15/06/2019 10:36, Jonathan Gray wrote:
On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
Hello,
I
On Sat, 15 Jun 2019 19:36:23 +1000
Jonathan Gray wrote:
> On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
> >
> > Hello,
> >
> > I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an
> > Intel Atom CPU (Denverton). The board boots but most devices are
> > not
On 15/06/2019 10:36, Jonathan Gray wrote:
> On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
>>
>> Hello,
>>
>> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
>> Atom CPU (Denverton). The board boots but most devices are not
>> detected because ACPI can't
On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
>
> Hello,
>
> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
> Atom CPU (Denverton). The board boots but most devices are not
> detected because ACPI can't be enabled.
>
> Does anyone know if this is
Hello,
I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
Atom CPU (Denverton). The board boots but most devices are not
detected because ACPI can't be enabled.
Does anyone know if this is likely to be supported at some point?
Full dmesg is below
OpenBSD 6.5
hello,
I upgraded VirtualBox from 5.1 to 5.2 and ... it works !
as the solution was so easy, i feel confused...
thanks for your help.
Le mar. 13 nov. 2018 à 22:07, jean-yves boisiaud <
jean-yves.boisi...@alcor-consulting.fr> a écrit :
> hello Dumitru,
>
> thanks for your answer.
>
> Le mar.
hello Dumitru,
thanks for your answer.
Le mar. 13 nov. 2018 à 21:50, Dumitru Moldovan a écrit :
> On Tue, 13 Nov 2018 20:51:09 +0100, jean-yves boisiaud <
> jean-yves.boisi...@alcor-consulting.fr> wrote:
>
> > I 'm trying to install OpenBSD 6.4 on VirtualBox 5.1.38 on a LinuxMint
> host.
> >
On Tue, 13 Nov 2018 20:51:09 +0100, jean-yves boisiaud
wrote:
> I 'm trying to install OpenBSD 6.4 on VirtualBox 5.1.38 on a LinuxMint host.
> Please note that 6.0, ... 6.3 worked fine, only 6.4 failed.
I've been running 6.4 with no issues on VirtualBox 5.0.x (initially) and now
5.2.x. But
hello,
I 'm trying to install OpenBSD 6.4 on VirtualBox 5.1.38 on a LinuxMint host.
Please note that 6.0, ... 6.3 worked fine, only 6.4 failed.
The boot sequence starts, and restarts forever.
I recorded the console of the VM, the last message displayed before reboot
is :
isa0 at mainbus0
> On 17. May 2017, at 13:51, flipchan wrote:
>
> Yeah the amd64 works to install and it boots but it disabled all port
> includeing the keyboard:
>
> I have tried both 6.1 6.0 and 5.9 all same
> error: [drm:pid0:intel_uncore_check_errors] eERROR Unclaimed register before
Yeah the amd64 works to install and it boots but it disabled all port
includeing the keyboard:
I have tried both 6.1 6.0 and 5.9 all same
error: [drm:pid0:intel_uncore_check_errors] eERROR Unclaimed register before
interupt
nvram invalid checksum
uhub0: device problem, disabling port 1,3,5,12
On Tue, May 16, 2017 at 12:22:18PM +, flipchan wrote:
> Here is the output:
>
>
> first boot didnt work so i searched around and found this blog post
> http://www.sacrideo.us/openbsd-on-macbook/ and i tried typing in the mkdir
> commands i it booted
>
> >>OpenBSD/i386 BOOT 3.31
> boot>
>
Here is the output:
first boot didnt work so i searched around and found this blog post
http://www.sacrideo.us/openbsd-on-macbook/ and i tried typing in the mkdir
commands i it booted
>>OpenBSD/i386 BOOT 3.31
boot>
boot>mkdir cd-dir
boot>cd cd-dir
boot>mkdir -p 4.2/i386
boot>mkdir -p etc
1 - 100 of 312 matches
Mail list logo