From: Daiajo Tibdixious <daiajo@gmail.com>
To: gentoo-amd64 <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] Radeon driver not working (solved)
Date: Wed, 31 May 2017 17:40:47 +1000 [thread overview]
Message-ID: <CAC4mkftDCmf5Ln34xsHX9T5niJiHfPL153uvvBWcpm5VE=QOHQ@mail.gmail.com> (raw)
In-Reply-To: <CAC4mkfv1OD8j+gm45DeKsB6Ckncg1qwHcrkO44PmCgFfQafk2g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
It looks like while cleaning up I de-installed linux-firmware, found this
by looking at dmesg. Reinstalled the firmware & all good now.
On 31 May 2017 5:00 PM, "Daiajo Tibdixious" <daiajo@gmail.com> wrote:
I can't actually send from the machine so its hard to include stuff. I'm
not looking for a solution, just things to try.
I'm on kernel 4.9.16-gentoo
GPU is Turks XT (Radeon HD 6500/7670)
Kernel is setup according to the gentoo radeon guide, I compared it to
4.4.6 kernel, which has been working for months. Booting off that older
kernel doesn't change anything, so it can't be the kernel.
These are a manual transcript of selected Xorg.0.log errors
open /dev/dri/card0: No such file or directory
Device (s) detected, but none match those in config file
The /dev/dri directory does not exist. If it's created by udev, maybe I
have a udev problem?
On 31 May 2017 4:29 PM, "Thanasis" <thanasis@asyr.hopto.org> wrote:
On 05/31/2017 07:29 AM, Daiajo Tibdixious wrote:
> For a while now I've been logging into root & doing "modprobe radeon"
> after which the screen will blank, then come back at a much higher
> resolution. (as an aside, where do I put modules to autoload?) Since the
> last reboot nothing happens. SDDM/KDE will not start.
>
> I have checked all the radeon settings in the kernel, & tried booting
> off a previous kernel with no change.
>
> If I login to my user account & do "startx" that also fails.
>
> I took the cover off the machine & the GPU fan is spinning. It's dusty
> but not too bad.
>
> I've run out of ideas. To me it looks like a HW fault but I don't know
> how to check the GPU. It's still visible in lspci & console mode works
> (with tiny # lines & width).
>
> (IDK if this will be text or html, the setting is not visible on phone)
Are you expecting people here to guess your hardware configuration,
kernel configuration, debug messages, etc?
[-- Attachment #2: Type: text/html, Size: 3068 bytes --]
parent reply other threads:[~2017-05-31 7:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAC4mkfv1OD8j+gm45DeKsB6Ckncg1qwHcrkO44PmCgFfQafk2g@mail.gmail.com>]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC4mkftDCmf5Ln34xsHX9T5niJiHfPL153uvvBWcpm5VE=QOHQ@mail.gmail.com' \
--to=daiajo@gmail.com \
--cc=gentoo-amd64@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox