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
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
featur
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, a
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:
>>
> 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.
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 resul
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
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 in
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
> anyth
> 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] dem
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, th
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 mes
> 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
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 ne
14 matches
Mail list logo
