rd.blacklist=nouveau
dracut -f --omit-drivers nouveau --xz
doktor5000 wrote:Well, usually you simply run drakx11, select the propr. driver, then do NOT run the test and simply reboot, that's it.
[...]
Usually you only need "nokmsboot" as boot option, can you check whether you have that? If not, please add it and try again with the nvidia driver.
"Minimal BASH-like editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions.
grub> _"
grub>
grub> search -f /boot/vmlinuz-desktop --set=root
grub> probe -u $root --set=abc
grub> linux /boot/vmlinuz-desktop root=UUID=$abc ro
grub> initrd /boot/initrd-desktop.img
grub> boot
Myles wrote:But is that actually the actual letters "abc" or do I have to substitute it for something?
Myles wrote:Also re: nouveau driver. I originally selected to use nVidia driver but after about the 2nd or 3rd boot (maybe more, but not by many) of the newly installed MGA6, if failed to be built and defaulted to nouveau ...
Myles wrote: At the moment it seems I have both drivers that cause problems
grub> search -f /boot/vmlinuz-desktop --set=root
did you mean"/usr/lib/" as I can't find a /lib directly under /root. I am able to use the Mageia DVD to install the Windows boot loader (I have a Windows partition dual boot set-up) and use a pgm to inspect /root.What is the contents of /lib/modules/4.9.50-desktop-1.mga6/dkms/drivers/char/drm ? (assuming you have updated to latest kernel)
Myles wrote:as for:did you mean"/usr/lib/" as I can't find a /lib directly under /root.What is the contents of /lib/modules/4.9.50-desktop-1.mga6/dkms/drivers/char/drm ? (assuming you have updated to latest kernel)
Myles wrote:In /usr/lib/modules/4.9.50-desktop-1.mga6/ there was no sub-folder named /dkms.
Myles wrote:is: "error: no such device: /boot/vmlinuz-desktop." so not much point continuing with the rest of the them.
ls /boot
ls (disk,partition)/boot
"error: file '/boot/vmlinuz-server' not found.
error: you need to load the kernel first.
Press any key to continue..."
Myles wrote:SO, should I just cut my losses and re-install the system from the DVD, again, or poke around a bit on the CLI (using the DVD Rescue or grub) with you good people's help and see if we can rescue my system? Can it be rescued?
Myles wrote:But late last night, (after I had posted my update), I had a brainwave. I had an stock-standard install of Mageia 6 installed (entire system + new /home all in the one install + successfully using the nvidia driver as well!
) on another partition when I still had a beautifully working #5.1 It is still there.
So, I thought, why not try and see if I can re-install the bootloader for that partition and see if that works!
Myles wrote:Well, I just did that and it does! Major breakthrough! So, on the GRUB2 menu I selected to boot my MGA6 install for my broken system and discovered why I'm having so much trouble with it now (not the nouveau problem; just the grub> problem) - When I try and boot my broken system I get:
- Code: Select all
"error: file '/boot/vmlinuz-server' not found.
error: you need to load the kernel first.
Press any key to continue..."
Myles wrote:So at least that explains why I can't boot my system, but doesn't explain what happened to it, (and why it got so screwed up), just by selecting the nvidia driver and doing a hard reset of my computer (which I have done numerous times by the way)!!!! Why would that delete/screw-up my system files??????
I am pretty sure your system can be rescued, but it is your decision based on how interested you are in learning, how much data you would need to secure before re-installing, the delay due to responders being in different time zones, etc. etc.
By this, do you mean you installed the bootloader using the rescue menu on the DVD?
Can you boot the system on that partition?
If yes, that may be the best platform for fixing the broken istallation.
It would still be interesting to know what files are in the /boot directory.
Are there any old kernel versions there, or did you uninstall those after the update to the latest version?
If not uninstalled, those should be available in the advanced option boot menu for the broken system
"error: file '/boot/vmlinuz-server' not found.
error: you need to load the kernel first.
Press any key to continue..."
Myles wrote:BTW, after I posted my update I was mucking around on my Windows system with the original pgm I use to read my Linux partitions, and it is working - I can see what files and folders are present in /root or /boot etc. It appears just the "file preview" portion that, for some reason, is not working suddenly. So I may be able to save the file to my Windows system (which is how the pgm works) to view if I had to view files. I'll test that. (Nope, today that pgm is playing up again and locks up when I try to access the /boot folder; but I have another one - trialware - that I used to get the below screenshot. I have raised a support ticket for my original pgm and hope to get it working ASAP). So we have that option as well as CLI from the Rescue Environment from the DVD.
Myles wrote:Should I update my other MGA6 system to be up-to-date so we can possibly use it to rescue - would that be a wise idea?
This is what I would try first at this point:
Boot into the non-updated MGA6 install and update its boot configuration, for example by clicking through the boot-loader setup in MCC (without making any changes).
If all goes well you should then be able to boot the broken MGA6 install
.1. Create blacklist.nouveau.conf with the entries Peter suggested.
2. Set nvidia driver in xorg.conf (Driver "nVidia")
3.Dracut rebuild (as suggested by Jiml8 and syntax provided by alf):
Code: Select all
dracut -f --omit-drivers nouveau --xz
4. Do I need to specify nvidia driver in MCC after all this before rebooting?
.The ksmserver-logout-greeter crash is a bug (probably related to this one: https://bugs.mageia.org/show_bug.cgi?id=20153)
The workaround is to get to a root prompt and type reboot
The test in MCC fails because a driver change requires a reboot. Just skip it.
Myles wrote:(I don't know how to get the "arnesp wrote:" bit into the quote).
[quote="<id>"]
Myles wrote:Perhaps you could explain why this approach worked so I can learn from this experience.
Myles wrote:1. Create blacklist.nouveau.conf with the entries Peter suggested.
2. Set nvidia driver in xorg.conf (Driver "nVidia")
3.Dracut rebuild (as suggested by Jiml8 and syntax provided by alf):
Code: Select all
dracut -f --omit-drivers nouveau --xz
4. Do I need to specify nvidia driver in MCC after all this before rebooting?
click through the boot-loader setup in MCC to re-create grub.cfg and get the boot-loader back to this system
un-install nvidia packages
reboot
select proprietary driver in MCC
Myles wrote:So, any guidance on how to get rid of nouveau now would be fantastic!
arnesp,
For the record, did this occur after trying my suggestions above?
If yes, did you do it before being aware that I had done an edit?
Myles wrote:Sorry, no I didn't see the edit till after as my email notification said I had a private msg (I've never had one so didn't bother looking at it till after). Anyway as you can see below, I'm not sure that that would really matter.
Myles wrote:Do you or anyone have any idea where Mageia stores the files it downloads as part of the install process??? Would it be in /var? I had problems once before where my printer wouldn't print. I eventually worked out it was because /var was full (I had duplicated 1 large folder twice for other reasons). At the moment at only has 21.8Mb free!!!!!!!
Myles wrote:Would this be the cause of "curl error x" errors? (where x=number)
Myles wrote:I'm copying off the said large folder I want to keep (just in case) as I have a small partition adjacent to /var that I might be able to expand into.
Myles wrote:IAlso, another tactic: would I be able to just copy over the files and folders from the stock installed MGA6 (excluding /home and /var folders - which are separate partitions for my "real" MGA6 system)????? Would that work and let me boot my old system if I re-install the bootloader for MGA6 stock-standard?
"I had to do a hard reset to get another reinstall happening, thus - probably - retaining all of the files Mageia had already downloaded and filling up /var, thus the 2nd reinstall didn't get very far before again failing. I tried a 3rd time and managed to take a shot of where the installer crashed out to a black screen with msgs - one being: "error: db5 error (28) from db->close: No space left on device" (then other msgs then eventually saying reboot.myles wrote:just stopped at the kernel-desktop etc part of the instal
Myles wrote:I also selected the nvidia driver, so I'll leave this open and see how the system goes and if when I reboot, that nouveau doesn't rear it's ugly head again. Otherwise I'll have to seek help and guidance with the exact steps to stop it loading!
Users browsing this forum: No registered users and 1 guest