Timeline for Why does nvidiafb module hang the entire system?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 13, 2023 at 18:11 | comment | added | user3161924 | I asked a whole new question at: unix.stackexchange.com/questions/764769/… | |
| Dec 13, 2023 at 18:11 | vote | accept | user3161924 | ||
| Dec 13, 2023 at 9:19 | answer | added | Artem S. Tashkinov | timeline score: 2 | |
| Dec 13, 2023 at 9:17 | comment | added | Artem S. Tashkinov | linuxquestions.org/questions/slackware-14/… You really shouldn't be using nvidiafb in 2023 | |
| Dec 12, 2023 at 22:24 | comment | added | user3161924 | How would you tell it to use nouveau for the frame buffer, i see it for drm. It was included in the 6.6.5 kernel build with that option (chipset level items) enabled. | |
| Dec 12, 2023 at 8:44 | comment | added | Artem S. Tashkinov | AFAIK nvidiafb is deprecated and terribly outdated and for FB/KMS you need to use either nouveau or binary nvidia drivers. And, yes, blacklisting this module is the best thing to do. This has nothing to do with "nvidia drivers hang so many systems". | |
| Dec 12, 2023 at 2:28 | history | asked | user3161924 | CC BY-SA 4.0 |