| Summary: | Can't get nvidia proprietary working on MGA6D1 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Rolf Pedersen <rolfpedersen> |
| Component: | Release (media or process) | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | andrewsfarm, laidlaws, lovaren, mageia, marja11, ouaurelien, sysadmin-bugs, thierry.vignaud, tmb |
| Version: | Cauldron | Keywords: | 6dev1, NEEDINFO, PATCH |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
xorg.conf
Xorg.0.log mga6d1 x86_64 report.bug.gz report.bug.xz |
||
|
Description
Rolf Pedersen
2016-03-28 16:51:27 CEST
Created attachment 7598 [details]
xorg.conf
The attached xorg.conf looks like what I told XFdrake to do.
Could you please attach Xorg log, as explained here https://wiki.mageia.org/en/Triage_guide#X_server_crashes_at_startup Keywords:
(none) =>
6dev1, NEEDINFO there is a missing "nokmsboot" on kernel command line can you list all nvidia packages that are installed: rpm -qa |grep -i nvidia CC:
(none) =>
tmb Created attachment 7606 [details]
Xorg.0.log
(In reply to Thomas Backlund from comment #3) > there is a missing "nokmsboot" on kernel command line > Added from working MGA5. I'll try another boot later this evening. > can you list all nvidia packages that are installed: > > rpm -qa |grep -i nvidia From chroot [root@p8z68 /]# rpm -qa |grep -i nvidia nvidia-current-doc-html-352.79-2.mga6.nonfree nvidia-current-kernel-desktop-latest-352.79-12.mga6.nonfree nvidia-current-kernel-4.4.5-desktop-1.mga6-352.79-11.mga6.nonfree dkms-nvidia-current-352.79-2.mga6.nonfree nvidia-current-kernel-4.4.6-desktop-1.mga6-352.79-12.mga6.nonfree x11-driver-video-nvidia-current-352.79-2.mga6.nonfree Thanks. (In reply to Thomas Backlund from comment #3) > there is a missing "nokmsboot" on kernel command line Yes, nokmsboot got it booting into X. Seems like the installer dropped the ball on that one but hard to say. Thanks. Please attach /root/drakx/report.bug.xz Created attachment 7608 [details]
mga6d1 x86_64 report.bug.gz
Assigning to tmb, since he already took an interest in this bug, and the information he requested was supplied. @ tmb Please reassign if needed. Keywords:
NEEDINFO =>
(none) Still valid after installing 64-bit Plasma from the Jan 11 sta2 Classical isos. If running under nouveau and the 340 driver is installed via MCC/Hardware, "nokmsboot" is NOT added to the grub2 kernel options, resulting in a failed boot. Adding it results in a successful boot using the 340 driver. Installing the 340 driver with the Classical installer DOES add "nokmsboot" but still results in a failed boot due, I believe, to a different bug. CC:
(none) =>
andrewsfarm Please attach /root/drakx/report.bug.xz Created attachment 8852 [details]
report.bug.xz
Be aware as you read this report that the BIOS erroneously reports that ECC memory is installed, resulting in the Classical installer installing the server kernel. The server kernel has always worked fine, so I leave it alone.
(In reply to Thomas Andrews from comment #10) > Still valid after installing 64-bit Plasma from the Jan 11 sta2 Classical > isos. If running under nouveau and the 340 driver is installed via > MCC/Hardware, "nokmsboot" is NOT added to the grub2 kernel options, > resulting in a failed boot. Adding it results in a successful boot using the > 340 driver. > > Installing the 340 driver with the Classical installer DOES add "nokmsboot" > but still results in a failed boot due, I believe, to a different bug. Dö you get the same problem if you add modprobe.blacklist=nouveau on the kernel boot command line? I use that to boot successfully. CC:
(none) =>
hamnisdude I haven't tried that. When I install the nvidia 340 driver via MCC/Hardware and then try to boot, I see a box with a message telling me that "nokmsboot" is required and the boot will probably fail because it isn't there. Pressing "Enter" clears the box and the boot continues, but fails. Simply adding "nokmsboot" to the kernel options gets me a successful boot, so I assume the MCC installer is supposed to add the option but doesn't, and that's what needs to be fixed for this bug.
Marja Van Waes
2017-01-13 23:55:17 CET
CC:
(none) =>
laidlaws Thanks for adding me to this bug, Marja. It may be related to my problem. I have the attachments for my report, but having trouble describing it. Got there! Created bug 20130. (In reply to Thomas Andrews from comment #10) > Still valid after installing 64-bit Plasma from the Jan 11 sta2 Classical > isos. If running under nouveau and the 340 driver is installed via > MCC/Hardware, "nokmsboot" is NOT added to the grub2 kernel options, > resulting in a failed boot. Adding it results in a successful boot using the > 340 driver. This particular issue is a unwanted side effect of the fix for bug 18783. As that postdates the original report here, it wasn't the cause of the original bug. CC:
(none) =>
mageia OK, so I chose the wrong bug. Sorry about that. Comments 3-6 seemed to imply that it would fit. So what should I do to help get my issue fixed? Start a new bug? Sit back and wait? I'm OK with either one. Patches were proposed on bug #18783 (to be applied in /usr/lib/libDrakX) CC:
(none) =>
thierry.vignaud So nobody tested the suggested patches? Keywords:
(none) =>
NEEDINFO, PATCH Sorry. I'm not using the nvidia card, now. Marja added me to this bug. My report is bug 20130, closed as a duplicate of bug 17400. I have been checking for "nokmsboot" in /etc/default/grub. It always seems to be present. Since installing nvidia340 from the Classical isos has been working, I have not tried installing the nvidia driver from MCC. I will see what I can do about trying it after installing from the latest RC test iso this evening. Using the April 27 RC test isos on my MBR nvidia340 system, if the proprietary driver is installed from an iso, "nokmsboot" is added to the kernel boot options, and the nvidia340 driver boots without incident. When I used the Classical iso to install Plasma on the same hardware without the proprietary driver, the nouveau driver is used. After getting all updates, including tainted, drakxtools, and a new kernel, and rebooting, I installed the proprietary nvidia340 driver from MCC. At the reboot, using "e" in grub 2 to check the kernel options, I saw that "nokmsboot" was NOT added to them. I added it manually, and proceeded with a successful boot that used the nvidia driver. So if the patches have been applied, they don't work. My experience has been different. I have gone back to 5.1 for other reasons. On installing Cauldron sta 2, I would initially set vesa graphics to avoid the "good luck" bug. Then, after all updates, etc (same stage as Thomas,) I could switch to the nvidia driver, and nokmsboot would be present. I am not a beta tester, so I don't have access to the RC isos. Currently on Mageia 8 Beta 1, Selecting NVIDIA proprietary Drivers correctly write nokmsboot to kernel command line. See on systems with 390-series and 450-series. Time to close this, seems a patch was already proposed. Resolution:
(none) =>
FIXED I am on the CC list only, but I agree that everything now works. |