unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ben Sturmfels <ben@sturm.com.au>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Diego Nicola Barbato <dnbarbato@posteo.de>, 35408@debbugs.gnu.org
Subject: bug#35408: External monitor not working with GDM
Date: Wed, 8 May 2019 12:50:11 +1000	[thread overview]
Message-ID: <497de6f6-6491-283e-085a-34074f73fed3@sturm.com.au> (raw)
In-Reply-To: <87y33oubmb.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 3538 bytes --]

On 03/05/19 01:20, Ludovic Courtès wrote:
> Ben Sturmfels <ben@sturm.com.au> skribis:
> 
>>> On Fri, 26 Apr 2019, Ludovic Courtès wrote:
>>>> Ben Sturmfels <ben@sturm.com.au> skribis:
>>
>>>>> [   448.627] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
>>
>>>> It looks like you have an AMD Radeon graphics card, is that right?  Did
>>>> you pass “modprobe.blacklist=radeon” on the kernel command line, or
>>>> something similar?
>>>>
>>>> Apparently some of these AMD graphics cards are not quite supported by
>>>> free software, so that might be the issue here.
>>>
>>> Whoops, sorry I'm being unintentionally misleading - I shuttle my hard
>>> drive across from my X200 into an F2A85-M motherboard at work, which has
>>> Radeon HD 8470D. It's always just worked with Slim on Guix and Trisquel
>>> 7/8.
>>>
>>> I'll try the modprobe.blacklist though.
>>
>> I tried the modprobe.blacklist=radeon in the kernel line, but GDM still
>> did it's looping thing.
> 
> What .desktop files to you have under /run/current-system/profile?
> 
> There was a bug whereby GDM would enter an infinite loop when no
> .desktop files were provided: <https://issues.guix.info/issue/35068>.

The outcome if this is that I now have GDM working on my X200 + external
monitor, but not on the F2A85-M motherboard + external. For now I'm just
using Slim on the radeon-based system, so I suppose this can be closed.

I think this was two separate issues:

1. I think GDM stopped working on the X200 due to renumbered uid/gids
that caused permission problems on /var/lib/gdm. Not 100% sure - was a
day or two between when I removed /var/lib/gdm and reconfired and when I
tried the external monitor on X200 again.

2. Starting GDM on the F2A85-M gives the following in
/var/log/debug:

May  2 12:19:12 localhost vmunix: [   24.301185] [drm] radeon: 768M of
VRAM memory ready
May  2 12:19:12 localhost vmunix: [   24.301237] [drm] radeon: 1024M of
GTT memory ready.
May  2 12:19:12 localhost vmunix: [   24.301287] [drm] Loading ARUBA
Microcode
May  2 12:19:12 localhost vmunix: [   24.301325] 0000:00:01.0: Missing
Free firmware (non-Free firmware loading is disabled)
May  2 12:19:12 localhost vmunix: [   24.304342] ni_cp: Failed to load
firmware "/*(DEBLOBBED)*/"
May  2 12:19:12 localhost vmunix: [   24.304420] [drm:cayman_init
[radeon]] *ERROR* Failed to load firmware!
May  2 12:19:12 localhost vmunix: [   24.304467] radeon 0000:00:01.0:
Fatal error during GPU init
May  2 12:19:12 localhost vmunix: [   24.304499] [drm] radeon: finishing
device.

And the following in Xorg.0.log:

[   642.963] (II) Module fbdevhw: vendor="X.Org Foundation"
[   642.963] 	compiled for 1.20.4, module version = 0.0.2
[   642.963] 	ABI class: X.Org Video Driver, version 24.0
[   642.963] (EE) open /dev/fb0: No such file or directory
[   642.963] (EE) Screen 0 deleted because of no matching config section.
[   642.963] (II) UnloadModule: "radeon"
[   642.963] (EE) Screen 0 deleted because of no matching config section.
[   642.963] (II) UnloadModule: "modesetting"
[   642.963] (EE) Screen 0 deleted because of no matching config section.
[   642.963] (II) UnloadModule: "fbdev"
[   642.963] (II) UnloadSubModule: "fbdevhw"

Regarding the .desktop issue - I wasn't quite clear on where these files
are supposed to be. I don't seem to have a /run/current-system/profile.
I suppose it doesn't matter now since I've since done a `pull` and
`system reconfigure`.

Thanks!
Ben





[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2019-05-08  2:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  4:25 bug#35408: External monitor not working with GDM Ben Sturmfels
2019-04-25  9:08 ` Ludovic Courtès
2019-04-25 11:41   ` Ben Sturmfels
2019-04-25 12:16     ` Danny Milosavljevic
2019-04-25 12:53       ` Ben Sturmfels
2019-04-25 16:37       ` Ludovic Courtès
2019-04-26  1:12       ` Ben Sturmfels
2019-04-26  8:12         ` Ludovic Courtès
2019-04-25 22:13     ` Diego Nicola Barbato
2019-04-26  0:42       ` Ben Sturmfels
2019-04-26  8:14         ` Ludovic Courtès
2019-05-02  2:00           ` Ben Sturmfels
2019-05-02  8:01             ` Ben Sturmfels
2019-05-02 15:20               ` Ludovic Courtès
2019-05-08  2:50                 ` Ben Sturmfels [this message]
2020-06-11  4:01 ` Royce Strange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=497de6f6-6491-283e-085a-34074f73fed3@sturm.com.au \
    --to=ben@sturm.com.au \
    --cc=35408@debbugs.gnu.org \
    --cc=dnbarbato@posteo.de \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).