Re: [gentoo-user] New install - Wayland and graphical login

[antlists <antlists@youngman.org.uk>]

On 27/06/2021 11:36, Michael wrote:
> On Sunday, 27 June 2021 10:05:59 BST Wols Lists wrote:
>> On 21/06/21 16:17, Michael wrote:
>>> Have you tried using a Display Manager?  Some of my systems won't work
>>> with
>>> Wayland, but I haven't spent time to find out why all I get with them is a
>>> black screen.
>>>
>>> Anyway, from a VT you'd run something like:
>>>
>>> XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
>>
>> Okay, we're slowly moving forward ...
>>
>> My first attempt got the error "kwin-plasma won't run as root" or
>> somesuch. Created a new user for me, and promptly got a black screen!
> 
> You're meant to be running X11 as a non-root user.
> 
And if the only user on the system is root, which I'm logged in as :-)
> 
>> As I said earlier, X currently won't run. I've got a Asus EAH4350, and
>> am loading the Radeon driver.
> 
> I am not familiar with the model and any APU/graphics options it may be
> furnished with.  You have not shared what the video card might be.

Well, "Asus EAH4350" is what it says on the box.

>  A quick
> search on the interwebs mention an AMD R700 family, HD4350 card.  According
> to:

So I guess Asus have rebadged the 4350 chipset, and those drivers should 
work.
> 
> https://wiki.gentoo.org/wiki/Radeon
> 
> such a card requires in your make.conf:
> 
> VIDEO_CARDS="radeon r600"
> 
> emerge 'sys-kernel/linux-firmware' and in your kernel specify the following
> firmware:
> 
> radeon/R600_rlc.bin radeon/RS780_uvd.bin radeon/RS780_pfp.bin radeon/
> RS780_me.bin
> 
Thanks. I'll add all that stuff ...
> 
>> When I looked at the X log it was clearly
>> loading the driver, which failed with something like "cannot find
>> /dev/card1". If that gives anyone any clues where to point me that's
>> great, or I'll transfer the logs to this machine and post them.
>>
>> Cheers,
>> Wol
> 
> dmesg will show if there is any problem with the kernel missing modules, or
> having problems loading firmware;
> 
> /var/log/Xorg.0.log will show what problems X11 comes up with when it tries to
> launch.
> 
> Normally /dev/dri/card0 is the first card being loaded:
> 
> $ grep -i card /var/log/Xorg.0.log
> [    37.111] (II) xfree86: Adding drm device (/dev/dri/card0)
> [    37.148] (II) xfree86: Adding drm device (/dev/dri/card1)
> [    38.366] (II) Applying OutputClass "Radeon" to /dev/dri/card0
> [    38.367] (II) Applying OutputClass "Radeon" to /dev/dri/card1
> 
Thank you very much. Let's see whether that fixes the problem with 
Wayland, too. I found an interesting blog by ?Michael Graesslin on 
fixing the "black screen in Wayland" problem, but a lot of it dates from 
2016. If Wayland doesn't fix itself, I'll work my way through that, but 
it looks like there's a LOT of things that can go wrong and cause 
problems...

Cheers,
Wol