On 2015-10-27 18:15, Stéphane Glondu wrote:
> Le 27/10/2015 17:07, Stéphane Glondu a écrit :
>> It seems that I am experiencing the same bug. I have upgraded to
>> 304.128-6, and the bug is still present.
No, whatever you experienced is clearly a differnent problem, there is
nothing about "busid"
Le 27/10/2015 17:07, Stéphane Glondu a écrit :
> It seems that I am experiencing the same bug. I have upgraded to
> 304.128-6, and the bug is still present.
I tried using the vesa driver. It worked for a few hours, then froze the
graphical display (I could still SSH in). Then, it never worked
Package: nvidia-legacy-304xx-driver
Version: 304.125-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
since my last dist-upgrade, X fails to start when installing this package. When
system boots, the screen starts to flicker, and X doesn't come up.
The error lines in
On 2015-10-20 11:10, Luis Carvalheiro wrote:
> Package: nvidia-legacy-304xx-driver
> Version: 304.125-2
This is not a recent (legacy) driver version. Or you didn't report the
bug on the system where it happened.
Please run
reportbug -N 802452
in the failing system to collect system
On 2015-10-20 13:32, Luis Carvalheiro wrote:
> Dear Maintainer,
>
> I had to apt-get remove --purge nvidia* to get a working graphical
> environment. I used reportbug in a GUI to report it after that. When i run
> reportbug -N 802452 i can't add nothing more. I reported the bug in the
> failing
On 2015-10-20 11:10, Luis Carvalheiro wrote:
> Oct 19 10:03:09 munch kernel: [177312.799746] No drm_driver.set_busid()
> implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to
> set the unique name explicitly.
Yes, same error as in #801193, now that I looked for it
6 matches
Mail list logo
