On Sun, Jan 20, 2019 at 5:09 PM Warner Losh wrote:
>
>
> On Sun, Jan 20, 2019, 4:41 PM Kurt Jaeger
>> Hi!
>>
>> > Well no longer needed as puc0 has found and allocated the
>> > device(s) which would of shown up had you done this before
>> > you fixed puc0 to find them.
>>
>> The problem is that
On Sun, Jan 20, 2019, 4:41 PM Kurt Jaeger Hi!
>
> > Well no longer needed as puc0 has found and allocated the
> > device(s) which would of shown up had you done this before
> > you fixed puc0 to find them.
>
> The problem is that the found 4 uarts are not 8 uarts, and they do not
> seem to work (t
Hi!
> Well no longer needed as puc0 has found and allocated the
> device(s) which would of shown up had you done this before
> you fixed puc0 to find them.
The problem is that the found 4 uarts are not 8 uarts, and they do not
seem to work (tested using kermit), either 8-(
Any hints on how to de
> Hi!
>
> > > It only detects four (or six?) serials...
> > Are perhaps 2 of them being consumed by sio?
>
> See my other post, the system found 13 uarts 8-}
>
> > > So I think I found a 'somehow' working setup and have to add stuff to
> > > sys/dev/puc/pucdata.c to match it. Thanks for the poi
Hi!
> > none1@pci0:7:4:0: class=0x070002 card=0x000814a1 chip=0x000814a1
> > rev=0xb0 hdr=0x00
> > vendor = 'Systembase Co Ltd'
> > class = simple comms
> > subclass = UART
> > bar [10] = type I/O Port, range 32, base 0x1040, size 64, enabled
> > bar [14] =
Hi!
> > > uart2: <16550 or compatible> port 0x3e8-0x3ef irq 10 on acpi0
[...]
> > I compared it to a second, similar hardware and there I found the same
> > uart2,
> > even if no card was installed 8-(
> >
> > So it seems the card is not detected at all 8-(
>
> Need to find out why it is not sh
Hi!
> > It only detects four (or six?) serials...
> Are perhaps 2 of them being consumed by sio?
See my other post, the system found 13 uarts 8-}
> > So I think I found a 'somehow' working setup and have to add stuff to
> > sys/dev/puc/pucdata.c to match it. Thanks for the pointer!
>
> Ok, hea
On Sun, Jan 20, 2019, 9:29 AM Lev Serebryakov Hello Rebecca,
>
> Sunday, January 20, 2019, 7:27:56 AM, you wrote:
>
> > Ultimately, UEFI doesn't care about disks and partitions: it only really
> knows
> > about ESPs -- FAT12/16/32 formatted partitions that contain the EFI
> directory
> > structure
13.0-CURRENT drops to debugger on shutdown with IPNAT enabled.
Running in VirtualBox 6.0.2.
The identical configuration running 12.0-RELEASE-p2, 12.0-STABLE, 11.2-
RELEASE-p8 and 11.2-STABLE do not exhibit this behavior.
This (VM) is a test machine and I can do anything that will help
identify t
Hello,
at https://reviews.freebsd.org/D18894 I put a review which main goal is
to allow i386 kernels to use NX bits on capable hardware. In essence,
single kernel now can operate using either PAE or non-PAE pagetables,
the selection is done at the cold (very early boot, before paging is
turned on)
Hello Rebecca,
Sunday, January 20, 2019, 7:27:56 AM, you wrote:
> Ultimately, UEFI doesn't care about disks and partitions: it only really knows
> about ESPs -- FAT12/16/32 formatted partitions that contain the EFI directory
> structure. For now, that means /EFI/BOOT/BOOT{x64,i386,aa64,arm}.efi,
On Sat, Jan 19, 2019 at 11:54:25PM +0300, Lev Serebryakov wrote:
> Hello Rebecca,
>
> Saturday, January 19, 2019, 6:06:52 PM, you wrote:
>
> > Ok, I've checked my desktop Asus Z170-A, but it is graphical and I could
> > not find or understand anything in this home-rown UI with crazy-fast mouse.
On Saturday, 19 January 2019 13:54:25 MST Lev Serebryakov wrote:
> Yes, I know. But what should I do next? There is no "Set UEFI Boot Var"
> item in it. You could select different physical drives (but not partitions
> of the drives) and network cards (if PXE is enabled), and, sometimes, "EFI
> S
13 matches
Mail list logo
