Are you sure you're using i386 and not amd64?
Paul 'WEiRD' de Weerd
On Mon, May 01, 2023 at 12:26:41PM +1000, Damian McGuckin wrote:
|
| What is required please?
|
| I am trying to boot this bsd.rd (which is a file 4Mb big) on an old
| NET5500 which has 512MBytes of RAM. On a running system,
How are you getting to the boot> prompt?
On Mon, May 1, 2023 at 12:28 PM Damian McGuckin wrote:
>
>
> What is required please?
>
> I am trying to boot this bsd.rd (which is a file 4Mb big) on an old
> NET5500 which has 512MBytes of RAM. On a running system,
>
> From the
>
> boot>
>
>
What is required please?
I am trying to boot this bsd.rd (which is a file 4Mb big) on an old
NET5500 which has 512MBytes of RAM. On a running system,
From the
boot>
prompt, doing
boot> boot bsd.rd
it appears to loads bsd.rd, but then drops straight back into the BIOS
On Mon, May 1, 2023 at 10:08 AM Aaron Mason wrote:
>
> I can reproduce it with this in QEMU 8.0 in Winders (thanks Antun who
> sent something like this to the bugs@ list):
>
> qemu-system-x86_64 -accel whpx,kernel-irqchip=off -machine q35 \
>-cpu EPYC-Rome,-monitor -m 8g -smp
I can reproduce it with this in QEMU 8.0 in Winders (thanks Antun who
sent something like this to the bugs@ list):
qemu-system-x86_64 -accel whpx,kernel-irqchip=off -machine q35 \
-cpu EPYC-Rome,-monitor -m 8g -smp 6,sockets=1,cores=6 \
-nic user,model=virtio-net-pci,hostfwd=tcp::10022-:22
Hi,
what qemu version are you using? I cannot reproduce this with qemu 7.2.
Can you try with a newer qemu?
Cheers,
Stefan
Am 25.04.23 um 14:53 schrieb Aaron Mason:
Yeah I'm getting the same thing. Trying a build in QEMU and
transferring in to see if that helps. Will report back.
Ok, good
On Sun, Apr 30, 2023, at 8:14 AM, Why 42? The lists account. wrote:
> After running fsck manually to clean one of the filesystems I did an
> additional reboot, just to be sure the system would/could come up
> cleanly.
>
> I noticed this message on the console, seemingly as the system was
>
Theo de Raadt writes:
> Yoshihiro Kawamata wrote:
>
> > From: Janne Johansson
> > Subject: Re: Minimum install size
> > Date: Fri, 28 Apr 2023 09:09:49 +0200
> >
> > > Do not assume "desireable" and "possible" are always the same.
> >
> > My point was whether the wording "installable on 512MB
Hi All,
Our 7.2 system just paniced again in pmap_page_remove / uvm_fault:
> ddb{1}> show panic
> *cpu1: uvm_fault(0xfd818b0ca560, 0x7f817ca74cb0, 0, 2) -> e
> ddb{1}> trace
> pmap_page_remove(fd8109c56480) at pmap_page_remove+0x21d
> uvm_anfree_list(fd804a0e7e40,800022eab518)
Hi.
Check your PF rules and also confirm you have set
net.inet.ip.forwarding=1 via sysctl.
Regards,
Roman
On 30.04.23 11:23, Gurra wrote:
Hi list,
I’m stuck setting up this configuration - 2 OpenBSD 7.3 boxes
connected via a private network 192.168.2.0/24.
The clients connected to box 1 on
> I’m stuck setting up this configuration - 2 OpenBSD 7.3 boxes
> connected via a private network 192.168.2.0/24.
> The clients connected to box 1 on 192.168.1.0/24 should be able to reach the
> server
> on 192.168.2.0/24 with ip 192.168.2.2 on port 1234 tcp
> The communication between clients
Hi list,
I’m stuck setting up this configuration - 2 OpenBSD 7.3 boxes
connected via a private network 192.168.2.0/24.
The clients connected to box 1 on 192.168.1.0/24 should be able to reach the
server
on 192.168.2.0/24 with ip 192.168.2.2 on port 1234 tcp
The communication between clients
This is current/amd64 on an APU1C (dmesg below).
It runs off a microSD card (sd1 in a SD card adapter in the SD slot)
and has a 60GB mSATA (sd0 in the mSATA slot ) for backups of others.
Filesystem SizeUsed Avail Capacity Mounted on
/dev/sd1a 501M106M370M23%/
13 matches
Mail list logo
