Re: Multiport serial card Exsys EX-44388, where are the devices ?
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 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 debug this ?
>>
>
> You need to look to get the register width right.
>
Hit send too quick... I was going to say you needed to make sure that the
register width and strides were right, but they look to be because NetBSD
has
/* SystemBase SB16C1058 UARTs */
{ "SystemBase SB16C1058",
{ PCI_VENDOR_SYSTEMBASE, PCI_PRODUCT_SYSTEMBASE_SB16C1058, 0,
0 },
{ 0x, 0x, 0,
0 },
{
{ PUC_PORT_TYPE_COM, PCI_BAR0, 0x00, COM_FREQ },
{ PUC_PORT_TYPE_COM, PCI_BAR0, 0x08, COM_FREQ },
{ PUC_PORT_TYPE_COM, PCI_BAR0, 0x10, COM_FREQ },
{ PUC_PORT_TYPE_COM, PCI_BAR0, 0x18, COM_FREQ },
{ PUC_PORT_TYPE_COM, PCI_BAR0, 0x20, COM_FREQ },
{ PUC_PORT_TYPE_COM, PCI_BAR0, 0x28, COM_FREQ },
{ PUC_PORT_TYPE_COM, PCI_BAR0, 0x30, COM_FREQ },
{ PUC_PORT_TYPE_COM, PCI_BAR0, 0x38, COM_FREQ },
},
},
for this card. so there's 4 UARTs per bar, like you are seeing. You have
DEFAULT_RCLK * 8. COM_FREQ in NetBSD is defined:
sys/dev/ic/comreg.h:#define COM_FREQ 1843200 /* 16-bit baud rate divisor */
and FreeBSD's DEFAULT_RCLK is
sys/dev/puc/puc_cfg.h:#define DEFAULT_RCLK 1843200
so at a guess you need to remove the *8 to make things work. Otherwise you
are sending data 8 times too slow.
Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Multiport serial card Exsys EX-44388, where are the devices ?
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 (tested using kermit), either 8-( > > Any hints on how to debug this ? > You need to look to get the register width right. -- > p...@freebsd.org +49 171 3101372 One year to go ! > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Multiport serial card Exsys EX-44388, where are the devices ?
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 debug this ? -- p...@freebsd.org +49 171 3101372 One year to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Multiport serial card Exsys EX-44388, where are the devices ?
> 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, heading in the right direction, try > > pciconf -lB > > that should show the hierarchy with the simple comms connected > > behind the pci-pci bridge. More readable without the -v your > > using above. > > Here we go: 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. Anyway, your fixed, so enjoy your serial bits :-) > - > hostb0@pci0:0:0:0:class=0x06 card=0x87611043 chip=0x14501022 rev=0x00 > hdr=0x00 > none0@pci0:0:0:2: class=0x080600 card=0x14511022 chip=0x14511022 rev=0x00 > hdr=0x00 > hostb1@pci0:0:1:0:class=0x06 card=0x chip=0x14521022 rev=0x00 > hdr=0x00 > pcib1@pci0:0:1:1: class=0x060400 card=0x87611043 chip=0x14531022 rev=0x00 > hdr=0x01 > bus range = 1-9 > window[1c] = type I/O Port, range 32, addr 0x1000-0x2fff, enabled > window[20] = type Memory, range 32, addr 0xba30-0xba5f, enabled > window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, > disabled > pcib10@pci0:0:1:2:class=0x060400 card=0x87611043 chip=0x14531022 rev=0x00 > hdr=0x01 > bus range = 10-10 > window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled > window[20] = type Memory, range 32, addr 0xba70-0xba7f, enabled > window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, > disabled > hostb2@pci0:0:2:0:class=0x06 card=0x chip=0x14521022 rev=0x00 > hdr=0x00 > hostb3@pci0:0:3:0:class=0x06 card=0x chip=0x14521022 rev=0x00 > hdr=0x00 > hostb4@pci0:0:4:0:class=0x06 card=0x chip=0x14521022 rev=0x00 > hdr=0x00 > hostb5@pci0:0:7:0:class=0x06 card=0x chip=0x14521022 rev=0x00 > hdr=0x00 > pcib11@pci0:0:7:1:class=0x060400 card=0x14541022 chip=0x14541022 rev=0x00 > hdr=0x01 > bus range = 11-11 > window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled > window[20] = type Memory, range 32, addr 0xba00-0xba2f, enabled > window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, > disabled > hostb6@pci0:0:8:0:class=0x06 card=0x chip=0x14521022 rev=0x00 > hdr=0x00 > pcib12@pci0:0:8:1:class=0x060400 card=0x14541022 chip=0x14541022 rev=0x00 > hdr=0x01 > bus range = 12-12 > window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled > window[20] = type Memory, range 32, addr 0xba60-0xba6f, enabled > window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, > disabled > intsmb0@pci0:0:20:0: class=0x0c0500 card=0x87611043 chip=0x790b1022 rev=0x59 > hdr=0x00 > isab0@pci0:0:20:3:class=0x060100 card=0x87611043 chip=0x790e1022 rev=0x51 > hdr=0x00 > hostb7@pci0:0:24:0: class=0x06 card=0x chip=0x14601022 rev=0x00 > hdr=0x00 > hostb8@pci0:0:24:1: class=0x06 card=0x chip=0x14611022 rev=0x00 > hdr=0x00 > hostb9@pci0:0:24:2: class=0x06 card=0x chip=0x14621022 rev=0x00 > hdr=0x00 > hostb10@pci0:0:24:3: class=0x06 card=0x chip=0x14631022 rev=0x00 > hdr=0x00 > hostb11@pci0:0:24:4: class=0x06 card=0x chip=0x14641022 rev=0x00 > hdr=0x00 > hostb12@pci0:0:24:5: class=0x06 card=0x chip=0x14651022 rev=0x00 > hdr=0x00 > hostb13@pci0:0:24:6: class=0x06 card=0x chip=0x14661022 rev=0x00 > hdr=0x00 > hostb14@pci0:0:24:7: class=0x06 card=0x chip=0x14671022 rev=0x00 > hdr=0x00 > hostb15@pci0:0:25:0: class=0x06 card=0x chip=0x14601022 rev=0x00 > hdr=0x00 > hostb16@pci0:0:25:1: class=0x06 card=0x chip=0x14611022 rev=0x00 > hdr=0x00 > hostb17@pci0:0:25:2: class=0x06 card=0x chip=0x14621022 rev=0x00 > hdr=0x00 > hostb18@pci0:0:25:3: class=0x06 card=0x chip=0x14631022 rev=0x00 > hdr=0x00 > hostb19@pci0:0:25:4: class=0x06 card=0x chip=0x14641022 rev=0x00 > hdr=0x00 > hostb20@pci0:0:25:5: class=0x06 card=0x chip=0x14651022 rev=0x00 > hdr=0x00 > hostb21@pci0:0:25:6: class=0x06 card=0x chip=0x14661022 rev=0x00 > hdr=0x00 > hostb22@pci0:0:25:7: class=0x06 card=0x chip=0x14671022 rev=0x00 > hdr=0x00 > xhci0@pci0:1:0:0: class=0x0c0330 card=0x11421b21 chip=0x43ba1022 rev=0x02 > hdr=0x00 > ahci0@pci0:1:0:1: class=0x010601 card=0x10621b21 chip=0x43b61022 rev=0x02 > hdr=0x00 > pcib2@pci0:1:0:2: class=0x060400 card=0x02011b21 chip=0x43b11022 rev=0x02 > hdr=0x01 > bus range = 2-9 > window[1c] = type I/O Port, range 32, addr 0x1000-0x2fff, enabled > window[20] = type Memory, rang
Re: Multiport serial card Exsys EX-44388, where are the devices ?
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] = type I/O Port, range 32, base 0x1000, size 64, enabled > > > > This is the one you want. You'll need to add vendor 14a1 device 8 to the > puc tables. Do you need help with this? Yes, see my other post. The card is now detected, but the result is still strange (uart2-9 is detected as 16750, why?) and the additional uarts 10 to 13 are also detected, but by some other mechanism I don't understand. And all of them do not work with kermit 8-} > It will be a bit tricky because > each of these defines several ports, I think. > > and: > > > > pcib7@pci0:6:0:0: class=0x060400 card=0x chip=0x10801b21 > > rev=0x04 hdr=0x01 > > vendor = 'ASMedia Technology Inc.' > > device = 'ASM1083/1085 PCIe to PCI Bridge' > > class = bridge > > subclass = PCI-PCI > > > > This is something else. It's the PCIe to PCI bridge on the card itself. -- p...@opsec.eu+49 171 3101372One year to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Multiport serial card Exsys EX-44388, where are the devices ?
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 showing up in the PCI
> listings. Can you post the output from
Sorry for my late answer, I was traveling for a day.
On that box, it was not detected at all. I moved it to a different box,
added the patch below, rebuild the kernel and rebooted.
Effect:
l cuau?
crw-rw 1 uucp dialer 0x8a Jan 19 12:10 cuau0
crw-rw 1 uucp dialer 0x37 Jan 19 12:17 cuau2
crw-rw 1 uucp dialer 0x3d Jan 19 12:10 cuau3
crw-rw 1 uucp dialer 0x43 Jan 19 12:10 cuau4
crw-rw 1 uucp dialer 0x49 Jan 19 13:09 cuau5
crw-rw 1 uucp dialer 0x4f Jan 19 12:14 cuau6
crw-rw 1 uucp dialer 0x55 Jan 19 12:10 cuau7
crw-rw 1 uucp dialer 0x5b Jan 19 12:10 cuau8
crw-rw 1 uucp dialer 0x61 Jan 19 12:10 cuau9
crw-rw 1 uucp dialer 0x6f Jan 19 13:58 cuaua
crw-rw 1 uucp dialer 0x75 Jan 19 13:58 cuaub
crw-rw 1 uucp dialer 0x7b Jan 19 13:58 cuauc
crw-rw 1 uucp dialer 0x81 Jan 19 13:58 cuaud
[...]
pcib7@pci0:6:0:0: class=0x060400 card=0x chip=0x10801b21 rev=0x04
hdr=0x01
vendor = 'ASMedia Technology Inc.'
device = 'ASM1083/1085 PCIe to PCI Bridge'
class = bridge
subclass = PCI-PCI
puc0@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] = type I/O Port, range 32, base 0x1000, size 64, enabled
dmesg:
dmesg | grep uart
uart2: <16750 or compatible> at port 1 on puc0
uart3: <16750 or compatible> at port 2 on puc0
uart4: <16750 or compatible> at port 3 on puc0
uart5: <16750 or compatible> at port 4 on puc0
uart6: <16750 or compatible> at port 5 on puc0
uart7: <16750 or compatible> at port 6 on puc0
uart8: <16750 or compatible> at port 7 on puc0
uart9: <16750 or compatible> at port 8 on puc0
uart10: <16x50 with 256 byte FIFO> iomem
0xfedc9000-0xfedc9fff,0xfedc7000-0xfedc7fff irq 3 on acpi0
uart11: <16x50 with 256 byte FIFO> iomem
0xfedca000-0xfedcafff,0xfedc8000-0xfedc8fff irq 4 on acpi0
uart12: <16x50 with 256 byte FIFO> iomem
0xfedce000-0xfedcefff,0xfedcc000-0xfedccfff irq 3 on acpi0
uart13: <16x50 with 256 byte FIFO> iomem
0xfedcf000-0xfedc,0xfedcd000-0xfedcdfff irq 4 on acpi0
uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
-
Index: pucdata.c
===
--- pucdata.c (revision 343188)
+++ pucdata.c (working copy)
@@ -870,6 +870,16 @@
},
/*
+* Systembase SB16C1058
+ */
+
+ { 0x14a1, 0x0008, 0x14a1, 0x0008,
+ "ExSys EX-44388",
+ DEFAULT_RCLK * 8,
+ PUC_PORT_8S, 0x10, 0, 8,
+ },
+
+ /*
* Perle boards use Oxford Semiconductor chips, but they store the
* Oxford Semiconductor device ID as a subvendor device ID and use
* their own device IDs.
--
p...@opsec.eu+49 171 3101372One year to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Multiport serial card Exsys EX-44388, where are the devices ?
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, heading in the right direction, try > pciconf -lB > that should show the hierarchy with the simple comms connected > behind the pci-pci bridge. More readable without the -v your > using above. Here we go: - hostb0@pci0:0:0:0: class=0x06 card=0x87611043 chip=0x14501022 rev=0x00 hdr=0x00 none0@pci0:0:0:2: class=0x080600 card=0x14511022 chip=0x14511022 rev=0x00 hdr=0x00 hostb1@pci0:0:1:0: class=0x06 card=0x chip=0x14521022 rev=0x00 hdr=0x00 pcib1@pci0:0:1:1: class=0x060400 card=0x87611043 chip=0x14531022 rev=0x00 hdr=0x01 bus range = 1-9 window[1c] = type I/O Port, range 32, addr 0x1000-0x2fff, enabled window[20] = type Memory, range 32, addr 0xba30-0xba5f, enabled window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, disabled pcib10@pci0:0:1:2: class=0x060400 card=0x87611043 chip=0x14531022 rev=0x00 hdr=0x01 bus range = 10-10 window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled window[20] = type Memory, range 32, addr 0xba70-0xba7f, enabled window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, disabled hostb2@pci0:0:2:0: class=0x06 card=0x chip=0x14521022 rev=0x00 hdr=0x00 hostb3@pci0:0:3:0: class=0x06 card=0x chip=0x14521022 rev=0x00 hdr=0x00 hostb4@pci0:0:4:0: class=0x06 card=0x chip=0x14521022 rev=0x00 hdr=0x00 hostb5@pci0:0:7:0: class=0x06 card=0x chip=0x14521022 rev=0x00 hdr=0x00 pcib11@pci0:0:7:1: class=0x060400 card=0x14541022 chip=0x14541022 rev=0x00 hdr=0x01 bus range = 11-11 window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled window[20] = type Memory, range 32, addr 0xba00-0xba2f, enabled window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, disabled hostb6@pci0:0:8:0: class=0x06 card=0x chip=0x14521022 rev=0x00 hdr=0x00 pcib12@pci0:0:8:1: class=0x060400 card=0x14541022 chip=0x14541022 rev=0x00 hdr=0x01 bus range = 12-12 window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled window[20] = type Memory, range 32, addr 0xba60-0xba6f, enabled window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, disabled intsmb0@pci0:0:20:0:class=0x0c0500 card=0x87611043 chip=0x790b1022 rev=0x59 hdr=0x00 isab0@pci0:0:20:3: class=0x060100 card=0x87611043 chip=0x790e1022 rev=0x51 hdr=0x00 hostb7@pci0:0:24:0: class=0x06 card=0x chip=0x14601022 rev=0x00 hdr=0x00 hostb8@pci0:0:24:1: class=0x06 card=0x chip=0x14611022 rev=0x00 hdr=0x00 hostb9@pci0:0:24:2: class=0x06 card=0x chip=0x14621022 rev=0x00 hdr=0x00 hostb10@pci0:0:24:3:class=0x06 card=0x chip=0x14631022 rev=0x00 hdr=0x00 hostb11@pci0:0:24:4:class=0x06 card=0x chip=0x14641022 rev=0x00 hdr=0x00 hostb12@pci0:0:24:5:class=0x06 card=0x chip=0x14651022 rev=0x00 hdr=0x00 hostb13@pci0:0:24:6:class=0x06 card=0x chip=0x14661022 rev=0x00 hdr=0x00 hostb14@pci0:0:24:7:class=0x06 card=0x chip=0x14671022 rev=0x00 hdr=0x00 hostb15@pci0:0:25:0:class=0x06 card=0x chip=0x14601022 rev=0x00 hdr=0x00 hostb16@pci0:0:25:1:class=0x06 card=0x chip=0x14611022 rev=0x00 hdr=0x00 hostb17@pci0:0:25:2:class=0x06 card=0x chip=0x14621022 rev=0x00 hdr=0x00 hostb18@pci0:0:25:3:class=0x06 card=0x chip=0x14631022 rev=0x00 hdr=0x00 hostb19@pci0:0:25:4:class=0x06 card=0x chip=0x14641022 rev=0x00 hdr=0x00 hostb20@pci0:0:25:5:class=0x06 card=0x chip=0x14651022 rev=0x00 hdr=0x00 hostb21@pci0:0:25:6:class=0x06 card=0x chip=0x14661022 rev=0x00 hdr=0x00 hostb22@pci0:0:25:7:class=0x06 card=0x chip=0x14671022 rev=0x00 hdr=0x00 xhci0@pci0:1:0:0: class=0x0c0330 card=0x11421b21 chip=0x43ba1022 rev=0x02 hdr=0x00 ahci0@pci0:1:0:1: class=0x010601 card=0x10621b21 chip=0x43b61022 rev=0x02 hdr=0x00 pcib2@pci0:1:0:2: class=0x060400 card=0x02011b21 chip=0x43b11022 rev=0x02 hdr=0x01 bus range = 2-9 window[1c] = type I/O Port, range 32, addr 0x1000-0x2fff, enabled window[20] = type Memory, range 32, addr 0xba30-0xba4f, enabled window[24] = type Prefetchable Memory, range 64, addr 0xfff0-0xf, disabled pcib3@pci0:2:0:0: class=0x060400 card=0x33061b21 chip=0x43b41022 rev=0x02 hdr=0x01 bus range = 3-3 window[1c] = type I/O Port, range 32, addr 0xfff000-0xfff, disabled window[20] = type Memory, r
Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)
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. For now, that means /EFI/BOOT/BOOT{x64,i386,aa64,arm}.efi,
> the
> > Microsoft boot loader in /EFI/Microsoft and GRUB/shim in /EFI/fedora,
> /EFI/
> > opensuse etc.
> Problem is (for me), our code we put in ESP partition doesn't care about
> several FreeBSD partitions and ability to continue boot from any of them in
> simple way.
set currdev=diskXpY:
boot
Is too complicated? Boot1.efi doesn't allow that, but loader.efi does.
I have been said, that code in ESP partition looks and some EFI
> variables (BootNext & Co), and I could "Set them in BIOS", but all this
> thread doesn't have any clues HOW could I set them in BIOS. Need I EFI
> shell
> (which, according to this message must be installed separately!), or
> something?
>
The EFI shell let's you select which .efi to run in a generic way. Most
BIOSes have the ability to boot to this. There are multiple ways to do
this. There are other things that could also be done, true, and it would be
cool if we had it in the menu...
So many things you'd want to be able to do you can. There are gaps we can
fill in, but booting the FreeBSD on a different partition is easy today
from the loader prompt...
And I repeat for 4th or 5th time: subject is about GPT. GPT/Legacy has same
> problem :-)
>
I don't care about that as much :). Others might, and I'd integrate
reasonable changes here. I care a lot UEFI, and have put a ton of work into
making it more than the most minimal thing to boot.
Warner
--
> Best regards,
> Levmailto:l...@freebsd.org
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
13.0-CURRENT drops to debugger on shutdown with IPNAT enabled
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 the root of this problem. I have included screenshots of the debug output and a backtrace. Thanks. David Boyd. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
PAE on i386
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) time. This together with earlier 4/4 work gives much more life into i386 kernels for whoever still needs them. Please review/test, see the differential review text for more explanation. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)
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, the
> Microsoft boot loader in /EFI/Microsoft and GRUB/shim in /EFI/fedora, /EFI/
> opensuse etc.
Problem is (for me), our code we put in ESP partition doesn't care about
several FreeBSD partitions and ability to continue boot from any of them in
simple way. I have been said, that code in ESP partition looks and some EFI
variables (BootNext & Co), and I could "Set them in BIOS", but all this
thread doesn't have any clues HOW could I set them in BIOS. Need I EFI shell
(which, according to this message must be installed separately!), or something?
And I repeat for 4th or 5th time: subject is about GPT. GPT/Legacy has same
problem :-)
--
Best regards,
Levmailto:l...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)
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 ASUS systems you normally press F8 during POST to bring up the boot > > menu, and F11 on Supermicro systems. > 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 > Shell" which is not documented anywhere, and it doesn't work always. > > When I google "ASUS EFI Shell", for example, all results says about > preparing USB stick with EFI shell and such, not about commands and > variables of EFI shell. > > I don't say, that it is impossible, I only could not find good (or any) > documentation. The specification for EFI Shell is available together with other UEFI specifications, at http://www.uefi.org/specifications. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)
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
> Shell" which is not documented anywhere, and it doesn't work always.
>
> When I google "ASUS EFI Shell", for example, all results says about
> preparing USB stick with EFI shell and such, not about commands and
> variables of EFI shell.
>
> I don't say, that it is impossible, I only could not find good (or any)
> documentation.
Yeah, the documentation is definitely lacking.
If you want to specifically run the EFI Shell, then you'll need to either
install Shell_Full.efi from https://github.com/tianocore/edk2/tree/UDK2014.SP1/
EdkShellBinPkg/FullShell/X64 as Shellx64.efi on a USB stick formatted as FAT16
or FAT32 - or, install the shell as EFI/BOOT/BOOTx64.efi on an ESP.
For booting FreeBSD, you might want to consider installing rEFInd (http://
www.rodsbooks.com/refind/), since it can find the loader in EFI/freebsd/
loader.efi and displays the FreeBSD logo - see https://bluestop.org/files/
rEFInd_FreeBSD.jpeg . For comparison, my ASUS UEFI firmware doesn't find
FreeBSD
at all in /EFI/freebsd, and when installed as /EFI/boot/BOOTx64.efi just
displays a "UEFI OS" entry.
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, the
Microsoft boot loader in /EFI/Microsoft and GRUB/shim in /EFI/fedora, /EFI/
opensuse etc.
--
Rebecca Cran
signature.asc
Description: This is a digitally signed message part.
