From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205661] Upgrade to 5.4 from K5.3.13 fails x2 attempts
Date: Thu, 28 Nov 2019 18:50:49 +0000 [thread overview]
Message-ID: <bug-205661-2300-CKtCyGlMoJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205661-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205661
--- Comment #2 from Ivan Ratoyevsky (ivan@cyteck.co.uk) ---
Hi Jani, Thanks for your response but I don't really understand what you mean?
a) I have resolved the 1st firmware error. Managed to source a current copy of
the missing firmware file for a realtek NIC. I copied the file to the required
folder and the error is now gone.
b) The Nvidia driver error is still a major problem. This error only showed up
with K5.4. I downgraded back to K5.3.13 and I have no driver issues now.
So its definitely something within K5.4 that's a problem with Nvidia graphics
drivers. Its related to DKMS but more than that is beyond my knowledge or
experience with Linux & the kernel.
--
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
next prev parent reply other threads:[~2019-11-28 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 14:14 [Bug 205661] New: Upgrade to 5.4 from K5.3.13 fails x2 attempts bugzilla-daemon
2019-11-28 15:12 ` [Bug 205661] " bugzilla-daemon
2019-11-28 18:50 ` bugzilla-daemon [this message]
2019-12-02 12:17 ` bugzilla-daemon
2019-12-06 11:35 ` 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-205661-2300-CKtCyGlMoJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox