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: Thu, 02 May 2019 18:01:27 +1000 [thread overview]
Message-ID: <877eb9mgiw.fsf@sturm.com.au> (raw)
In-Reply-To: <87y33paa40.fsf@sturm.com.au>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
> 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.
> This is a bit of a stab in the dark, but I have been having issues with
> PostgreSQL and OpenSMTPD changing swapping UID/GIDs after reconfiguring
> or booting back into an old Guix System profile. This has required me to
> manually correct the permissions in /var/lib with `chown`. I'm
> suspicious that the same might be happening to GDM. I'll do some testing
> on this.
I also tried removing /var/lib/gdm and reconfiguring, but that didn't
seem to help, so I guess it's not a permissions issue.
Regards,
Ben
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-05-02 8:02 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 [this message]
2019-05-02 15:20 ` Ludovic Courtès
2019-05-08 2:50 ` Ben Sturmfels
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=877eb9mgiw.fsf@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).