Description of problem: When switching to the proprietary AMD driver, the boot option "nokmsboot" is needed to correctly start X. This option is not added automatically to grub2 and thus results in an error message followed by a blank screen which requires a hard reset. This option should be added automatically otherwise less experienced users might be stuck with an unusable system. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
This bug is still present after install using beta 3, 3rd pre-release kde live cd.
CC: (none) => davidwhodginsComponent: RPM Packages => InstallerWhiteboard: (none) => 3beta2
only on grub2 ?
Yes. With grub legacy, the nokmsboot option is added.
Assignee: bugsquad => zen25000Summary: Proprietary AMD driver requires nokmsboot to correctly start X => Proprietary AMD driver requires nokmsboot to correctly start X (grub2)Source RPM: (none) => grub2
This needs to be inserted into: /etc/default/grub by whatever code currently adds it to menu.lst for grub legacy, followed by a call to: grub2-mkconfig -o /boot/grub2/grub.cfg Change required in /etc/default/grub:- GRUB_DISTRIBUTOR="Mageia" GRUB_CMDLINE_LINUX_DEFAULT="nokmsboot" <============================== GRUB_DISABLE_RECOVERY="true" GRUB_GFXMODE="1024x768x32" GRUB_GFXPAYLOAD_LINUX="text" GRUB_THEME="/boot/grub2/themes/maggy/theme.txt" GRUB_TERMINAL_OUTPUT="gfxterm"
CC: (none) => anssi.hannula
*** Bug 8865 has been marked as a duplicate of this bug. ***
CC: (none) => paiiou
bug 8865 reported that it fail at http://svnweb.mageia.org/soft/drakx/trunk/perl-install/bootloader.pm?revision=6812&view=markup#l2023 called from http://svnweb.mageia.org/soft/drakx-kbd-mouse-x11/trunk/tools/display_driver_helper?revision=6517&view=markup and http://svnweb.mageia.org/soft/drakx-kbd-mouse-x11/trunk/lib/Xconfig/various.pm?view=markup big part to review :s
CC: (none) => thierry.vignaud, zen25000Component: Installer => RPM PackagesBlocks: (none) => 416Assignee: zen25000 => bugsquadSource RPM: grub2 => drakxtools-backend
So after a brief stint with mageia 2, I'm back to check on cauldron. Can't seem to boot at all with proprietary drivers even when adding nokmsboot. Did something break while I was gone?
I reinstalled from the mageia 3b2 disk and the proprietary driver seemed to work (although the nokmsboot is still needed to boot X). If I'm not mistaken, 3b2 came with kernel version 3.8.0rc4. I think on my last post, I was using kernel 3.8.0rc5. And as of today, I'm on 3.8.0 final. It appears that since rc5, the system now ignores the nokmsboot directive when added to grub at boot time. I know the driver needs to be patched for it to work with kernels newer than 3.7 so is it possible there is something wrong with the patch?
A new update to dracut seems to have fixed a bug which resulted in no kmsboot being ignored. We're back to the original bug that nokmsboot needs to be added automatically when switching to proprietary graphics driver.
Summary: Proprietary AMD driver requires nokmsboot to correctly start X (grub2) => Proprietary AMD driver requires nokmsboot to correctly start X (bootloader:modify_append needs take grub2 conf)
Priority: Normal => release_blockerWhiteboard: 3beta2 => 3beta3
I'd like for someone else to confirm this, but I think this bug has been resolved. Switching to proprietary driver no longer needs manual intervention. nokmsboot is added to grub.cfg and the system boots normally. Good work!!
It appears this is not quite 100% fixed as it used to work. It looks like nokmsboot is hardcoded and mageia will now boot with this parameter regardless of the driver used.
Barjac, can you have a look at what is currently done? It seems noknsboot is now added all the time.
CC: (none) => pierre-malo.denielou
AFAICT nokmsboot is not being added to grub2 config when it's not needed. I do not use any proprietary drivers and I have not seen any spurious nokmsboot entries. I will test a clean net-install on real hardware to check for this.
(In reply to Malo Deniélou from comment #12) > Barjac, can you have a look at what is currently done? It seems noknsboot is > now added all the time. A net-install on my Intel machine with on-board Intel graphics that does not require nokmsboot went OK. nokmsboot is not present in the grub2 kernel command line configuration.
I'm not sure why, but I think it might be the installation of grub2 itself that adds the parameter. On friday, I went ahead and removed the nokmsboot from grub.cfg to have kms boot capability. But after installing the latest grub update yesterday, nokmsboot was again added automatically. I'm currently using ati free driver.
(In reply to Philippe Leblanc from comment #15) > I'm not sure why, but I think it might be the installation of grub2 itself > that adds the parameter. On friday, I went ahead and removed the nokmsboot > from grub.cfg to have kms boot capability. But after installing the latest > grub update yesterday, nokmsboot was again added automatically. I'm > currently using ati free driver. Changes to /boot/grub2/grub.cfg will be overwritten any time that grub2 is updated. The place to make custom changes is /etc/default/grub, followed by: update-grub Grub2 itself does not add the nokmsboot. This is added to etc/default/grub by something else. What's the output of cat /etc/default/grub
[root@localhost ~]# cat /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT=" splash quiet resume=UUID=f674a5fb-6556-4a4c-a7fe-31ffafd9a0cc" GRUB_DISABLE_OS_PROBER=false GRUB_DISABLE_RECOVERY=true GRUB_TERMINAL_OUTPUT=gfxterm GRUB_DISTRIBUTOR=Mageia GRUB_GFXMODE=1024x768x32 GRUB_GFXPAYLOAD_LINUX=text GRUB_TIMEOUT=10 GRUB_THEME=/boot/grub2/themes/maggy/theme.txt Nokmsboot isn't present in this file yet was added automatically upon the last update of grub2 over the weekend. Is there another place that may be responsible for controlling the addition of nokmsboot to grub.cfg?
I think Thierry will need to answer that. Nothing should alter grub.cfg directly, as any changes will be lost when update-grub is run. I don't understand how you are seeing nokmsboot in grub.cfg if it's not in /etc/default/grub. If you still have the grub.cfg with nokmsboot, can you do: su cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg_nokms update-grub Then please attach grub.cfg and grub.cfg_nokms here.
I apologize. I ran the update-grub2 command to overwrite grub.cfg. It's entirely possible it was a mistake in my part since I've been switching back and forth between the free and closed drivers a lot to test out performance in gnome 3 on my little apu. For the sake of testing this specific bug, I've switched back to the free driver (which is what I was running the first time I noticed nokmsboot being added after grub update this weekend) and removed nokmsboot from /etc/default/grub and ran update-grub2. At this point in time, all my config files are consistent. As grub 2 integration is still ongoing, I'm sure there will be future updates to the grub package. If the update process adds nokmsboot as I thought it did during the last update, I will update you with my config files as suggested above. For now, I've destroyed any evidence I had.
Bootloader.pm write nothing in grub.cfg but it read from here some info like the kernel option. This bug was about adding grub2 support in modify_append which is called indirectly by XFdrake and installer I doubt it's now hard-coded, seems you have forgotten to remove it in the default file, and launch again update-grub.
Here is the full file, just in case this is the next question :-) [marcus@mzlaptop ~]$ cat /etc/default/grub GRUB_DISABLE_OS_PROBER=false GRUB_DISABLE_RECOVERY=true GRUB_TERMINAL_OUTPUT=gfxterm GRUB_DISTRIBUTOR=Mageia GRUB_GFXMODE=1024x768x32 GRUB_GFXPAYLOAD_LINUX=text GRUB_THEME=/boot/grub2/themes/maggy/theme.txt [marcus@mzlaptop ~]$
CC: (none) => marcus.zurhorst
Sorry for the noise, I wanted to comment on bug 9604 instead.
Is it still reproducable? I have no "nokmsboot" in my grub.cfg or /etc/default/grub file on an Intel graphics card. Philippe, did you also checked files under /etc/grub.d/ ? Those are automatically added into grub.cfg by grub2. May be some files became inconsistent between your propierty/free driver switches?
CC: (none) => tarakbumba
Humm, I fixed missing 'type' field in entries read from grub2 config in bug #9563 on April 05 in drakxtools-15.35-1.mga3 so it may just be fixed already. Can anyone try with latest drakxtools? Thanks.
Keywords: (none) => NEEDINFO
Both an install using the latest live dvd, and a network install have it.
Status: NEW => RESOLVEDResolution: (none) => FIXED