On 5/30/2025 4:35 PM, Greg A. Woods wrote:
> At Fri, 30 May 2025 06:29:49 -0400, Chuck Zmudzinski
> wrote:
> Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen
> 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and Xen))
>>
> ...
>> Maybe such simplicity is not possible or so easy with
On 5/29/2025 4:02 PM, Greg A. Woods wrote:
> At Thu, 29 May 2025 15:01:50 -0400, Chuck Zmudzinski
> wrote:
>
>> When I pass bootdev=dk12 in boot.cfg, the bootloader strangely tries dk1 as
>> root
>> (which is wrong) and correctly detects dk11 as the dump device. But it never
>> gives me the cha
On 5/30/2025 4:35 PM, Greg A. Woods wrote:
> At Fri, 30 May 2025 06:29:49 -0400, Chuck Zmudzinski
> wrote:
> Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen
> 4.18.5_20250521nb0 not ELF binary (Was: Re: EFI and Xen))
>>
>> I am not sure I understand why it is even necessary to do th
At Fri, 30 May 2025 06:29:49 -0400, Chuck Zmudzinski wrote:
Subject: Re: Xen boot strangeness (Was: Re: [SOLVED] Re: Xen 4.18.5_20250521nb0
not ELF binary (Was: Re: EFI and Xen))
>
> I am not sure I understand why it is even necessary to do this search for the
> boot device on modern UEFI/GPT par
Sent with Proton Mail secure email.
On Friday, 30 May 2025 at 15:01, Brian Buhrow wrote:
> hello everyone! I'm wondering if anyone on this list is running MS Windows 10
> or 11 on
> their AMD64 NetBSD machine using nvmm and Qemu? Also, if you have it working,
> do you have
> sound workin
On Fri, May 30, 2025 at 10:53:52AM -0400, Chuck Zmudzinski wrote:
[...]
> if (booted_partition & 0xfff0)
> continue;
>
> [...] Of course this also assumes "booted_partition" is
> declared as an uint32_t, or equivalent.
Maybe use
On 5/30/2025 3:36 AM, Manuel Bouyer wrote:
> On Fri, May 30, 2025 at 12:53:08AM -0400, Chuck Zmudzinski wrote:
>> On 5/29/2025 5:20 PM, Chuck Zmudzinski wrote:
>> > On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
>> >> On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
>> >>> [...]
>> >>
On 5/30/2025 6:29 AM, Chuck Zmudzinski wrote:
> On 5/29/2025 4:02 PM, Greg A. Woods wrote:
>> At Thu, 29 May 2025 15:01:50 -0400, Chuck Zmudzinski
>> wrote:
>> ...
>>
>>> When I pass bootdev=dk12 in boot.cfg, the bootloader strangely tries dk1 as
>>> root
>>> (which is wrong) and correctly det
hello everyone! I'm wondering if anyone on this list is running MS
Windows 10 or 11 on
their AMD64 NetBSD machine using nvmm and Qemu? Also, if you have it working,
do you have
sound working from Windows as well? If you do, would you send over a
description of the steps you
used to g
Hello, I think have been able to resume audio working by doing this:
netbsd-raspa4# audiocfg test 0
0: [*] audio1 @ vcaudio0: vchiq auds 3
playback: 2ch, 48000Hz
record: unavailable
(P-) slinear_le 16/16, 2ch, 48000-48000Hz
testing channel 0...audiocfg: write: Resourc
On Fri, May 30, 2025 at 12:02:07PM +0200, Christoph Badura wrote:
> On Thu, May 29, 2025 at 09:23:46PM +0200, Manuel Bouyer wrote:
> > On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
> > > The strange part is that it is necessary to pass -c to the DOM0 in
> > > boot.cfg to
> > >
On 5/29/2025 4:02 PM, Greg A. Woods wrote:
> At Thu, 29 May 2025 15:01:50 -0400, Chuck Zmudzinski
> wrote:
> ...
>
>> When I pass bootdev=dk12 in boot.cfg, the bootloader strangely tries dk1 as
>> root
>> (which is wrong) and correctly detects dk11 as the dump device. But it never
>> gives me
On Thu, May 29, 2025 at 09:23:46PM +0200, Manuel Bouyer wrote:
> On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
> > The strange part is that it is necessary to pass -c to the DOM0 in boot.cfg
> > to
> > actually disable com* and the bootloader does not execute the
> > userconf=
On Fri, May 30, 2025 at 12:53:08AM -0400, Chuck Zmudzinski wrote:
> On 5/29/2025 5:20 PM, Chuck Zmudzinski wrote:
> > On 5/29/2025 3:23 PM, Manuel Bouyer wrote:
> >> On Thu, May 29, 2025 at 03:01:50PM -0400, Chuck Zmudzinski wrote:
> >>> [...]
> >>> When I pass bootdev=dk12 in boot.cfg, the bootlo
14 matches
Mail list logo
