[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Status update on 1.0
From: |
Maxim Cournoyer |
Subject: |
Re: Status update on 1.0 |
Date: |
Wed, 13 Mar 2019 22:26:29 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Danny Milosavljevic <address@hidden> writes:
> On Wed, 13 Mar 2019 17:00:55 +0100
> Pierre Neidhardt <address@hidden> wrote:
>
>> > The last time I tried the installer it didn't work on AMD(GPU) cards.
>> > I'll give
>> > it another go.
>>
>> I've experienced the same issue and I'm quite sure this is because the
>> installer
>> uses KMSCON which only works with the proprietary amdgpu kernel module.
>> During
>> FOSDEM, Mathieu mentioned that KMSCON was chosen because it works better with
>> text/input encoding, if I recall correctly.
>
> Or find out why on earth KMSCON needs the prorietary amdgpu kernel module.
>
> It's not exactly 3D graphics, so what is going on? Furthermore, vesafb should
> always work regardless (if slowly, but who cares).
As Pierre hinted, your question should rather be as "Why on Earth does
the AMDGPU drivers needs a binary blob to provide basic features such as KMS
at all". I'm still appalled that this mammoth, 125 K lines of codes
driver got merged in the Linux kernel and is barely useful [0] when
the proprietary binary blobs are not installed.
Maxim
[0] Booting an AMD R9 285 GPU without the binary blobs installed would
leave me to a black screen last time I tried, using Debian 9.
- Status update on 1.0, Ludovic Courtès, 2019/03/13
- Re: Status update on 1.0, Tobias Geerinckx-Rice, 2019/03/13
- Re: Status update on 1.0, Pierre Neidhardt, 2019/03/13
- Re: Status update on 1.0, Danny Milosavljevic, 2019/03/13
- Re: Status update on 1.0, Pierre Neidhardt, 2019/03/13
- Re: Status update on 1.0, Ludovic Courtès, 2019/03/15
- Re: Status update on 1.0, Pierre Neidhardt, 2019/03/15
- Re: Status update on 1.0, Mathieu Othacehe, 2019/03/15
- Re: Status update on 1.0,
Maxim Cournoyer <=
Re: Status update on 1.0, Ludovic Courtès, 2019/03/15
Re: Status update on 1.0, mikadoZero, 2019/03/13
- Re: Status update on 1.0, Ricardo Wurmus, 2019/03/13
- Re: Status update on 1.0, pelzflorian (Florian Pelz), 2019/03/13
- Re: Status update on 1.0, L p R n d n, 2019/03/13
- Re: Status update on 1.0, L p R n d n, 2019/03/14
- Re: Status update on 1.0, Ludovic Courtès, 2019/03/15
- Re: Status update on 1.0, pelzflorian (Florian Pelz), 2019/03/15
Re: Status update on 1.0, mikadoZero, 2019/03/13
Re: Status update on 1.0, Timothy Sample, 2019/03/14