Re: The support for AMD graphics and how freebsd hardware support
On Tue, Sep 24, 2019 at 8:56 PM wrote: > developed > Reply-To: > X-Priority: 1 > Importance: high > Disposition-Notification-To: > X-Confirm-Reading-To: > Return-Receipt-To: > Hello, > 1. Does freebsd current and freebsd stable 12 fully support all features > of AMD Radeon RX 5700, Vega and RX 500 series including the hardware video > decoding features? > AMD Radeon support is probably the weakest of the three main GPU providers, but someone else may be able to confirm the status of those particular units. You would be far more likely to get information on X related issues by sending to the x...@freebsd.org mailing list. > > 2. From website, https://wiki.freebsd.org/Graphics#AMD_Graphics, it says > "Update drm-stable to Linux 4.16 for FreeBSD 12.0". Does it mean freebsd > hardware support or drivers are copied or translated from linux kernel > codes? > They are derived with minimal changes from the Linux code. FreeBSD has kernel modules that provide kernel support. These modules are not part of FreeBSD. They are GPL licensed, so are built as a port, drm-kmod and a group of slave ports that are for specific kernel versions. > > 3. How are freebsd hardware support really developed? In linux kernel > mailing list, there are over 2,000 emails per day from hardware vendors > such as Intel, AMD, Huawei, Samsung, Sony submitting patches or hardware > drivers. What about BSD? I did not find any such equivalence in freebsd > after googling. > Only Nvidia provides any significant support for its products on FreeBSD and, as a result, almost all other X code is identical or very nearly identical to the Linux code. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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"
The support for AMD graphics and how freebsd hardware support
developed Reply-To: X-Priority: 1 Importance: high Disposition-Notification-To: X-Confirm-Reading-To: Return-Receipt-To: Hello, 1. Does freebsd current and freebsd stable 12 fully support all features of AMD Radeon RX 5700, Vega and RX 500 series including the hardware video decoding features? 2. From website, https://wiki.freebsd.org/Graphics#AMD_Graphics, it says "Update drm-stable to Linux 4.16 for FreeBSD 12.0". Does it mean freebsd hardware support or drivers are copied or translated from linux kernel codes? 3. How are freebsd hardware support really developed? In linux kernel mailing list, there are over 2,000 emails per day from hardware vendors such as Intel, AMD, Huawei, Samsung, Sony submitting patches or hardware drivers. What about BSD? I did not find any such equivalence in freebsd after googling. Mark ___ 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: Can't boot current on Minnowboard
Renato Botelho writes: > On 24/09/19 17:46, D Scott Phillips wrote: >> Renato Botelho writes: >> >>> On 24/09/19 15:36, Toomas Soome wrote: > On 24 Sep 2019, at 21:12, Renato Botelho wrote: > > On 24/09/19 15:10, Toomas Soome wrote: >> >> >>> On 24 Sep 2019, at 20:50, Renato Botelho wrote: >>> >>> As reported at pfSense ticket [1], we can't see console after booting >>> FreeBSD installer iso on Minnowboard. This video [2] demonstrates the >>> problem. >>> >>> Basically I can see all kernel messages but nothing from userland after >>> kernel finishes to load. >>> >>> I would be glad to collect any kind of data you need to help tracking it >>> down. >>> >>> Thanks! >>> >>> [1] https://redmine.pfsense.org/issues/9488 >>> [2] https://imgur.com/a/V4IrQWo >>> -- >>> Renato Botelho >> >> Hi! >> >> does it have bios emulation and does it behave there? > > No, this board is EFI only. > Is it atom board? UEFI32 or UEFI64? >>> >>> It's Atom and is UEFI64. >>> >>> I figured out this board has HDMI and serial console and output is going >>> only to serial. If LiveCD option is selected on serial it shows up on >>> HDMI as well. >>> >>> I've downloaded latest firmware version and updated the board. After >>> that I noted serial console is configurable on setup and disabled by >>> default. >>> >>> Even with Input/Output serial items disabled it's sending output to >>> serial console and I can see UArt item listed on EFI variables on loader >>> prompt. >> >> The logic in stand/efi/loader/main.c:parse_uefi_con_out() seems to be >> that RB_SERIAL is set when the serial device appears before the video >> device in the ConOut efi variable, which is the case on a minnowboard >> that I looked at. You can override this by setting boot_serial="NO" in >> loader.conf or running `set boot_serial=NO` at the loader prompt. > > Adding boot_serial=NO works. I just wonder why the firmware setup > option to disable serial port is not being respected. I'm not 100% sure, but the uart settings in the config screen on the minnowboard might not actually be wired up: https://github.com/tianocore/edk2/blob/UDK2018/Vlv2TbltDevicePkg/PlatformInitPei/PchInitPeim.c#L441 > Thanks! > -- > Renato Botelho ___ 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: Can't boot current on Minnowboard
On 24/09/19 17:46, D Scott Phillips wrote: > Renato Botelho writes: > >> On 24/09/19 15:36, Toomas Soome wrote: >>> >>> On 24 Sep 2019, at 21:12, Renato Botelho wrote: On 24/09/19 15:10, Toomas Soome wrote: > > >> On 24 Sep 2019, at 20:50, Renato Botelho wrote: >> >> As reported at pfSense ticket [1], we can't see console after booting >> FreeBSD installer iso on Minnowboard. This video [2] demonstrates the >> problem. >> >> Basically I can see all kernel messages but nothing from userland after >> kernel finishes to load. >> >> I would be glad to collect any kind of data you need to help tracking it >> down. >> >> Thanks! >> >> [1] https://redmine.pfsense.org/issues/9488 >> [2] https://imgur.com/a/V4IrQWo >> -- >> Renato Botelho > > Hi! > > does it have bios emulation and does it behave there? No, this board is EFI only. >>> >>> Is it atom board? UEFI32 or UEFI64? >> >> It's Atom and is UEFI64. >> >> I figured out this board has HDMI and serial console and output is going >> only to serial. If LiveCD option is selected on serial it shows up on >> HDMI as well. >> >> I've downloaded latest firmware version and updated the board. After >> that I noted serial console is configurable on setup and disabled by >> default. >> >> Even with Input/Output serial items disabled it's sending output to >> serial console and I can see UArt item listed on EFI variables on loader >> prompt. > > The logic in stand/efi/loader/main.c:parse_uefi_con_out() seems to be > that RB_SERIAL is set when the serial device appears before the video > device in the ConOut efi variable, which is the case on a minnowboard > that I looked at. You can override this by setting boot_serial="NO" in > loader.conf or running `set boot_serial=NO` at the loader prompt. Adding boot_serial=NO works. I just wonder why the firmware setup option to disable serial port is not being respected. Thanks! -- Renato Botelho ___ 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: Booting anything after r352057 kills console
> Ian Lepore [i...@freebsd.org] wrote: > > > > On my system, a whole lotta stuff happens between ntpd and syscons (the > > thing that configures blanktime). Try setting rc_debug=YES in rc.conf, > > that should write more info to syslog about what's happening between > > ntpd and the lockup point. > > > The results were not very informative. The 'bad' release did not show any > additional log entries with the rc_debug turned on. The working release > was very chatty. Maybe this will get closer to finding the root cause? > I just realized that the rc.conf file is part of the BEADM boot environment and when I switch releases, rc.conf comes with it. I will need to grab my ZFS admin book and find out how to mount a zfs filesystem from the loader prompt and remove the 'read only' attribute so that I can edit the rc.conf that will be used to load the 'bad' release. Maybe then I will have something useful to report Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ 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: Booting anything after r352057 kills console
Ian Lepore [i...@freebsd.org] wrote: > > On my system, a whole lotta stuff happens between ntpd and syscons (the > thing that configures blanktime). Try setting rc_debug=YES in rc.conf, > that should write more info to syslog about what's happening between > ntpd and the lockup point. > The results were not very informative. The 'bad' release did not show any additional log entries with the rc_debug turned on. The working release was very chatty. Maybe this will get closer to finding the root cause? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ 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: Can't boot current on Minnowboard
Renato Botelho writes: > On 24/09/19 15:36, Toomas Soome wrote: >> >> >>> On 24 Sep 2019, at 21:12, Renato Botelho wrote: >>> >>> On 24/09/19 15:10, Toomas Soome wrote: > On 24 Sep 2019, at 20:50, Renato Botelho wrote: > > As reported at pfSense ticket [1], we can't see console after booting > FreeBSD installer iso on Minnowboard. This video [2] demonstrates the > problem. > > Basically I can see all kernel messages but nothing from userland after > kernel finishes to load. > > I would be glad to collect any kind of data you need to help tracking it > down. > > Thanks! > > [1] https://redmine.pfsense.org/issues/9488 > [2] https://imgur.com/a/V4IrQWo > -- > Renato Botelho Hi! does it have bios emulation and does it behave there? >>> >>> No, this board is EFI only. >>> >> >> Is it atom board? UEFI32 or UEFI64? > > It's Atom and is UEFI64. > > I figured out this board has HDMI and serial console and output is going > only to serial. If LiveCD option is selected on serial it shows up on > HDMI as well. > > I've downloaded latest firmware version and updated the board. After > that I noted serial console is configurable on setup and disabled by > default. > > Even with Input/Output serial items disabled it's sending output to > serial console and I can see UArt item listed on EFI variables on loader > prompt. The logic in stand/efi/loader/main.c:parse_uefi_con_out() seems to be that RB_SERIAL is set when the serial device appears before the video device in the ConOut efi variable, which is the case on a minnowboard that I looked at. You can override this by setting boot_serial="NO" in loader.conf or running `set boot_serial=NO` at the loader prompt. ___ 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: Can't boot current on Minnowboard
On 24/09/19 15:36, Toomas Soome wrote: > > >> On 24 Sep 2019, at 21:12, Renato Botelho wrote: >> >> On 24/09/19 15:10, Toomas Soome wrote: >>> >>> On 24 Sep 2019, at 20:50, Renato Botelho wrote: As reported at pfSense ticket [1], we can't see console after booting FreeBSD installer iso on Minnowboard. This video [2] demonstrates the problem. Basically I can see all kernel messages but nothing from userland after kernel finishes to load. I would be glad to collect any kind of data you need to help tracking it down. Thanks! [1] https://redmine.pfsense.org/issues/9488 [2] https://imgur.com/a/V4IrQWo -- Renato Botelho >>> >>> Hi! >>> >>> does it have bios emulation and does it behave there? >> >> No, this board is EFI only. >> > > Is it atom board? UEFI32 or UEFI64? It's Atom and is UEFI64. I figured out this board has HDMI and serial console and output is going only to serial. If LiveCD option is selected on serial it shows up on HDMI as well. I've downloaded latest firmware version and updated the board. After that I noted serial console is configurable on setup and disabled by default. Even with Input/Output serial items disabled it's sending output to serial console and I can see UArt item listed on EFI variables on loader prompt. -- Renato Botelho ___ 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: Booting anything after r352057 kills console
On Tue, 2019-09-24 at 14:32 -0400, Thomas Laus wrote: > On 2019-09-24 11:58, Pete Wright wrote: > > > > darn, and they didn't give you any additional information in the > > messages buffer, or generate a core file? > > > > There were no messages in the syslog and no other log that showed > anything after killing the console. On my working BEADM boot > environment, the next message after starting ntp is: > > configuring vt: blanktime > > This message never showed in the syslog on any of the 'black screens'. > I looked over the changes made between r352057 and r352064 and nothing > 'vt' related popped up. I have not built anything between these 2 > releases and probably should in order to help narrow the problem. I > originally updated to r352304 and killed my system and was reverting > back toward r352057 by splitting the difference by half. The problem > was still there in r352064, so I stopped and asked for help. > > This problem did not generate a core and building GENERIC with the DEBUG > symbols did not add any more information. > > Tom On my system, a whole lotta stuff happens between ntpd and syscons (the thing that configures blanktime). Try setting rc_debug=YES in rc.conf, that should write more info to syslog about what's happening between ntpd and the lockup point. -- Ian ___ 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: Can't boot current on Minnowboard
> On 24 Sep 2019, at 21:12, Renato Botelho wrote: > > On 24/09/19 15:10, Toomas Soome wrote: >> >> >>> On 24 Sep 2019, at 20:50, Renato Botelho wrote: >>> >>> As reported at pfSense ticket [1], we can't see console after booting >>> FreeBSD installer iso on Minnowboard. This video [2] demonstrates the >>> problem. >>> >>> Basically I can see all kernel messages but nothing from userland after >>> kernel finishes to load. >>> >>> I would be glad to collect any kind of data you need to help tracking it >>> down. >>> >>> Thanks! >>> >>> [1] https://redmine.pfsense.org/issues/9488 >>> [2] https://imgur.com/a/V4IrQWo >>> -- >>> Renato Botelho >> >> Hi! >> >> does it have bios emulation and does it behave there? > > No, this board is EFI only. > Is it atom board? UEFI32 or UEFI64? rgds, toomas ___ 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: Booting anything after r352057 kills console
On 2019-09-24 11:58, Pete Wright wrote: > > darn, and they didn't give you any additional information in the > messages buffer, or generate a core file? > There were no messages in the syslog and no other log that showed anything after killing the console. On my working BEADM boot environment, the next message after starting ntp is: configuring vt: blanktime This message never showed in the syslog on any of the 'black screens'. I looked over the changes made between r352057 and r352064 and nothing 'vt' related popped up. I have not built anything between these 2 releases and probably should in order to help narrow the problem. I originally updated to r352304 and killed my system and was reverting back toward r352057 by splitting the difference by half. The problem was still there in r352064, so I stopped and asked for help. This problem did not generate a core and building GENERIC with the DEBUG symbols did not add any more information. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF ___ 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: Can't boot current on Minnowboard
On 24/09/19 15:10, Toomas Soome wrote: > > >> On 24 Sep 2019, at 20:50, Renato Botelho wrote: >> >> As reported at pfSense ticket [1], we can't see console after booting >> FreeBSD installer iso on Minnowboard. This video [2] demonstrates the >> problem. >> >> Basically I can see all kernel messages but nothing from userland after >> kernel finishes to load. >> >> I would be glad to collect any kind of data you need to help tracking it >> down. >> >> Thanks! >> >> [1] https://redmine.pfsense.org/issues/9488 >> [2] https://imgur.com/a/V4IrQWo >> -- >> Renato Botelho > > Hi! > > does it have bios emulation and does it behave there? No, this board is EFI only. -- Renato Botelho ___ 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: Can't boot current on Minnowboard
> On 24 Sep 2019, at 20:50, Renato Botelho wrote: > > As reported at pfSense ticket [1], we can't see console after booting > FreeBSD installer iso on Minnowboard. This video [2] demonstrates the > problem. > > Basically I can see all kernel messages but nothing from userland after > kernel finishes to load. > > I would be glad to collect any kind of data you need to help tracking it > down. > > Thanks! > > [1] https://redmine.pfsense.org/issues/9488 > [2] https://imgur.com/a/V4IrQWo > -- > Renato Botelho Hi! does it have bios emulation and does it behave there? rgds, toomas ___ 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"
Can't boot current on Minnowboard
As reported at pfSense ticket [1], we can't see console after booting FreeBSD installer iso on Minnowboard. This video [2] demonstrates the problem. Basically I can see all kernel messages but nothing from userland after kernel finishes to load. I would be glad to collect any kind of data you need to help tracking it down. Thanks! [1] https://redmine.pfsense.org/issues/9488 [2] https://imgur.com/a/V4IrQWo -- Renato Botelho ___ 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"
