1 |
On 27/06/2021 11:36, Michael wrote: |
2 |
> On Sunday, 27 June 2021 10:05:59 BST Wols Lists wrote: |
3 |
>> On 21/06/21 16:17, Michael wrote: |
4 |
>>> Have you tried using a Display Manager? Some of my systems won't work |
5 |
>>> with |
6 |
>>> Wayland, but I haven't spent time to find out why all I get with them is a |
7 |
>>> black screen. |
8 |
>>> |
9 |
>>> Anyway, from a VT you'd run something like: |
10 |
>>> |
11 |
>>> XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland |
12 |
>> |
13 |
>> Okay, we're slowly moving forward ... |
14 |
>> |
15 |
>> My first attempt got the error "kwin-plasma won't run as root" or |
16 |
>> somesuch. Created a new user for me, and promptly got a black screen! |
17 |
> |
18 |
> You're meant to be running X11 as a non-root user. |
19 |
> |
20 |
And if the only user on the system is root, which I'm logged in as :-) |
21 |
> |
22 |
>> As I said earlier, X currently won't run. I've got a Asus EAH4350, and |
23 |
>> am loading the Radeon driver. |
24 |
> |
25 |
> I am not familiar with the model and any APU/graphics options it may be |
26 |
> furnished with. You have not shared what the video card might be. |
27 |
|
28 |
Well, "Asus EAH4350" is what it says on the box. |
29 |
|
30 |
> A quick |
31 |
> search on the interwebs mention an AMD R700 family, HD4350 card. According |
32 |
> to: |
33 |
|
34 |
So I guess Asus have rebadged the 4350 chipset, and those drivers should |
35 |
work. |
36 |
> |
37 |
> https://wiki.gentoo.org/wiki/Radeon |
38 |
> |
39 |
> such a card requires in your make.conf: |
40 |
> |
41 |
> VIDEO_CARDS="radeon r600" |
42 |
> |
43 |
> emerge 'sys-kernel/linux-firmware' and in your kernel specify the following |
44 |
> firmware: |
45 |
> |
46 |
> radeon/R600_rlc.bin radeon/RS780_uvd.bin radeon/RS780_pfp.bin radeon/ |
47 |
> RS780_me.bin |
48 |
> |
49 |
Thanks. I'll add all that stuff ... |
50 |
> |
51 |
>> When I looked at the X log it was clearly |
52 |
>> loading the driver, which failed with something like "cannot find |
53 |
>> /dev/card1". If that gives anyone any clues where to point me that's |
54 |
>> great, or I'll transfer the logs to this machine and post them. |
55 |
>> |
56 |
>> Cheers, |
57 |
>> Wol |
58 |
> |
59 |
> dmesg will show if there is any problem with the kernel missing modules, or |
60 |
> having problems loading firmware; |
61 |
> |
62 |
> /var/log/Xorg.0.log will show what problems X11 comes up with when it tries to |
63 |
> launch. |
64 |
> |
65 |
> Normally /dev/dri/card0 is the first card being loaded: |
66 |
> |
67 |
> $ grep -i card /var/log/Xorg.0.log |
68 |
> [ 37.111] (II) xfree86: Adding drm device (/dev/dri/card0) |
69 |
> [ 37.148] (II) xfree86: Adding drm device (/dev/dri/card1) |
70 |
> [ 38.366] (II) Applying OutputClass "Radeon" to /dev/dri/card0 |
71 |
> [ 38.367] (II) Applying OutputClass "Radeon" to /dev/dri/card1 |
72 |
> |
73 |
Thank you very much. Let's see whether that fixes the problem with |
74 |
Wayland, too. I found an interesting blog by ?Michael Graesslin on |
75 |
fixing the "black screen in Wayland" problem, but a lot of it dates from |
76 |
2016. If Wayland doesn't fix itself, I'll work my way through that, but |
77 |
it looks like there's a LOT of things that can go wrong and cause |
78 |
problems... |
79 |
|
80 |
Cheers, |
81 |
Wol |