Snapshots with kernels above 4.19.01: Monitor out of range
Re: Snapshots with kernels above 4.19.01: Monitor out of range
About the nvidiafb module: as far as I know, the MX/Debian kernels don't build it, but the Liquorix kernels do for sure.
We also have backports of Debian's latest legacy 340xx and 304xx drivers in the main repo.
nvidia-legacy-340xx-kernel-source does fail to build with my 5.0 Liquorix kernel. Maybe I can find a patch for it out there.
We also have backports of Debian's latest legacy 340xx and 304xx drivers in the main repo.
nvidia-legacy-340xx-kernel-source does fail to build with my 5.0 Liquorix kernel. Maybe I can find a patch for it out there.
Re: Snapshots with kernels above 4.19.01: Monitor out of range
The problem is that AFAICT Debian has stopped blacklisting nvidiafb and rivafb by default so when someone uses a kernel that includes these drivers havoc can ensue. The file /lib/modprobe.d/fbdev-blacklist.conf blacklists the other framebuffer drivers. IMO this is currently a bug in our system.
See for example: antiX-17 finally installed on P-III after a year!
Of course I will modify our Safe Video Mode so it automatically blacklists these drivers but this is far from ideal because those drivers should be blacklisted by default. We currently have a belt and suspenders solution without a belt and when a foreign kernel is used, without suspenders as well.
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."
-- Richard Feynman
-- Richard Feynman
Re: Snapshots with kernels above 4.19.01: Monitor out of range
I did adapt a patch for the 340xx legacy Nvidia drivers from the Arch AUR to get it to build up to and including the 5.0 kernel. I tested with the kernel-source deb package build, and now it works. I'll upload to the test repo, and take a look at the other legacy drivers.
Edit: Arch doesn't support the 304xx drivers any longer, and the legacy 390xx drivers in our main repo are supposed to support the 5.0 kernel (testing that right now--yes it builds), so I think I'm done with those now.
Edit: Arch doesn't support the 304xx drivers any longer, and the legacy 390xx drivers in our main repo are supposed to support the 5.0 kernel (testing that right now--yes it builds), so I think I'm done with those now.
Re: Snapshots with kernels above 4.19.01: Monitor out of range
Situation: Snapshots from a fully updated and fresh installation on the target machine (Kernels: 4.9./4.20/5.0.0.6)(No nvidia installed or removed)BitJam wrote: ↑Wed Apr 10, 2019 7:28 pm These ideas are a stab in the dark but they're easy to try. Stevo might have other ideas but, if you are willing, I'd like you to try these 3 ideas next and see if any of them fix the problem. If not, then we can try some other ideas.
1) normal video mode plus "blacklist=nvidiafb"
2) safe video mode plus "blacklist=nvidiafb"
3) normal video mode and run "modprobe nouveau" at bp=b9
Nouveau working flawless with all kernels.
Snapshot with 4.9.; video (default): works
Snapshot with 4.9.; video (safe mode): works
Snapshot with 4.20; video (default): does not work (out-of-range)
Snapshot with 4.20; video (default) + blacklist=nvidiafb: works
Snapshot with 4.20; video (safe mode): does not work (out-of-range)
Snapshot with 4.20; video (safe mode) + blacklist=nvidiafb: works
Snapshot with 4.20; video (default) + bp=b9 + modprobe nouveau: bp reached; modprobe nouveau: ok; exit and boot: works
Snapshot with 5.0.0.7-liquorix; video (default): does not work (out-of-range)
Snapshot with 5.0.0.7-liquorix; video (default) + blacklist=nvidiafb: works
Snapshot with 5.0.0.7-liquorix; video (safe mode): does not work (out-of-range)
Snapshot with 5.0.0.7-liquorix; video (safe mode) + blacklist=nvidiafb: works
Snapshot with 5.0.0.7-liquorix; video (default) + bp=b9 + modprobe nouveau: bp reached; modprobe nouveau: ok; exit and boot: works
Hope that helps, my generals..
Re: Snapshots with kernels above 4.19.01: Monitor out of range
Have you tried the new Nviidia 340xx legacy driver? It does work now with the 5.0 kernels.
Re: Snapshots with kernels above 4.19.01: Monitor out of range
No. It looks like the 340 does not support the 6150LE?
https://www.nvidia.de/Download/driverRe ... /135242/de
Re: Snapshots with kernels above 4.19.01: Monitor out of range
Does nvidia-detect say what driver may support it?Friedrich wrote: ↑Sat Apr 13, 2019 8:03 pmNo. It looks like the 340 does not support the 6150LE?
https://www.nvidia.de/Download/driverRe ... /135242/de
Re: Snapshots with kernels above 4.19.01: Monitor out of range
Brilliant! Thank you!Friedrich wrote: ↑Sat Apr 13, 2019 7:45 pm Snapshot with 4.20; video (default): does not work (out-of-range)
Snapshot with 4.20; video (default) + blacklist=nvidiafb: works
Snapshot with 4.20; video (safe mode): does not work (out-of-range)
Snapshot with 4.20; video (safe mode) + blacklist=nvidiafb: works
Snapshot with 4.20; video (default) + bp=b9 + modprobe nouveau: bp reached; modprobe nouveau: ok; exit and boot: works
[etc]
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."
-- Richard Feynman
-- Richard Feynman
Re: Snapshots with kernels above 4.19.01: Monitor out of range
The nvidia site says the GeForce 6150 cards are supported by 304.137
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Re: Snapshots with kernels above 4.19.01: Monitor out of range
I think the nvidiafb driver was causing most of your problems. By blacklisting it, or by loading nouveau first (at bp=b9) then you get working graphics. If the nouveau driver suffices then you don't need to try to get the nvidia driver to work. We should be blacklisting nvidiafb by default. I'm sorry this omission has caused you so much trouble.
"The first principle is that you must not fool yourself -- and you are the easiest person to fool."
-- Richard Feynman
-- Richard Feynman