From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Gabriel C <nix.or.die@gmail.com>
Cc: LKML Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 5.6-rc3 nouveau failure, 5.6-rc2 OK
Date: Thu, 27 Feb 2020 13:07:24 +0000 [thread overview]
Message-ID: <1fa89e07-79e4-4e1e-abc1-ab5563ca00e0@blueyonder.co.uk> (raw)
In-Reply-To: <CAEJqkgiXE-ye_P99FGcFM8j7Qqd3npKM9kY44MEnxGZF2_Hntw@mail.gmail.com>
Thanks Gabriel.
The new firmware didn't fix it.
Regards
Sid.
On 27/02/2020 03:14, Gabriel C wrote:
> Am Do., 27. Feb. 2020 um 01:24 Uhr schrieb Sid Boyce <sboyce@blueyonder.co.uk>:
>
> Hello,
>
>> [94.455712] [T411] nouveau 0000:07:00.0 disp ctor failed, -12
>>
>> Welcome to openSUSE Tumbleweed 20200224 - Kernel 5.6.0-rc3 (tty1)
>>
>> ens3s0: 192.168.10.214 .......
>>
>> login:
>>
>>
>> I can login here but X does not start -- lspci
>>
>> 07:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX
>> 1650] (rev a1)
>>
>> from dmesg:-
>>
>> [Wed Feb 26 22:42:39 2020] nouveau 0000:07:00.0: NVIDIA TU117 (167000a1)
>> [Wed Feb 26 22:42:39 2020] nouveau 0000:07:00.0: bios: version
>> 90.17.2a.00.39
>> [Wed Feb 26 22:44:12 2020] nouveau 0000:07:00.0: disp ctor failed, -12
>> [Wed Feb 26 22:44:12 2020] nouveau: probe of 0000:07:00.0 failed with
>> error -12
>>
> *Warning* I have no idea bout Nvidia GPU HW :-). I saw this commit in
> linux-firmware git added 8 days ago:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2277987a593d54c1e922a9f25445802071015f42
>
> Maybe you just need to update your firmware package.
>
> BR,
>
> Gabriel C.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
prev parent reply other threads:[~2020-02-27 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 0:18 Sid Boyce
2020-02-27 3:14 ` Gabriel C
2020-02-27 11:34 ` Sid Boyce
2020-02-27 13:07 ` Sid Boyce [this message]
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=1fa89e07-79e4-4e1e-abc1-ab5563ca00e0@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@gmail.com \
/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
all inboxes | Powered by JetHome®