All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 197033] New: system crash after startx - drm radeon hd4200
Date: Mon, 25 Sep 2017 17:35:22 +0000	[thread overview]
Message-ID: <bug-197033-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=197033

            Bug ID: 197033
           Summary: system crash after startx - drm radeon hd4200
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.10.17
          Hardware: i386
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: alertesmails@yahoo.fr
        Regression: No

Created attachment 258591
  --> https://bugzilla.kernel.org/attachment.cgi?id=258591&action=edit
syslog

System crash during startx.

Normal because I don't have the firmware :
radeon 0000:01:05.0: radeon_uvd: Can't load firmware "radeon/RS780_uvd.bin"

Strange : kernel modesetting is usually disabled probably because the driver
run in software mode due to the lack of firmware. But in Xorg.log it is enabled
:
[   101.256] (II) [KMS] Kernel modesetting enabled.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-09-25 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 17:35 bugzilla-daemon [this message]
2017-09-25 17:36 ` [Bug 197033] system crash after startx - drm radeon hd4200 bugzilla-daemon
2017-09-25 17:36 ` bugzilla-daemon
2017-09-25 17:39 ` bugzilla-daemon

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=bug-197033-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.