Description of problem: I boot up and choose live mode - either proprietary or not and it fails. I choose "safe mode" and it goes further for regular mode until it ends with xserver fail. If I choose proprietary it builds the driver and then loops out Version-Release number of selected component (if applicable): 6.1 How reproducible: Athlon x23800 with Nvidia 6150 LE Steps to Reproduce: 1. Start ISO (DVD) 2. Select Live Mode (if I choose defaults it just hangs) 3. If I choose Kernel options "safe mode" it goes further. With proprietary it builds Nvidia driver 304 and then loops out on DVD (left for 30 minutes). 4. I was able to choose install when I choose proprietary driver.
CC: (none) => kernel, marja11Whiteboard: (none) => 6.1RCAssignee: bugsquad => isobuild
Keywords: (none) => 6.1Whiteboard: 6.1RC => (none)
If instead of choosing "safe mode", you append "rd.driver.blacklist=nouveau" to the default kernel options, does that get you further when trying to boot Live Mode? If you press the escape key while it is booting, to reveal the scrolling text messages, what are the last few messages displayed when it gets stuck?
CC: (none) => mageia
Hi Martin - I tried this on both standard and proprietary driver options and it hangs up. This locks up almost immediately after it says "loading kernel" It appears to complete that and then attempt to go into a graphics mode that hangs. I placed rd.driver.blacklist=nouveau immediately after the initial LABEL=xxxx_xfce. Right before the nosplash quiet options. It happens so fast I am unable to get any text. It does flash something that starts with "probing" Anything else I should also try? I also tried nomodeset with no luck.
Hi Brian, "safe mode" adds these extra kernel boot options: apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll pci=nommconf Are these carried over to the installed system? (which, if I've read your notes on the pad correctly, boots without any problem). If so, could you try removing them one by one to find which one(s) make the difference. Do you have another, fully updated, Mageia 6 install on that machine that works without these options?
Here are the boot settings: nomodeset nokmsboot splash quiet noiswmd pci=nommconf acpi=off resume=UUID=1fd9f864-7401-43f0-8308-9ac10d55d22b audit=0 I bet it is the acpi=off. I'll try it.
removing acpi=off caused it to freeze.
Here is a fully working legacy build running on same hardware. On the Live-Build 6.1 - the system hangs at shutdown (as predicted by acpi documentation). On the old build, it does fully shutdown. Here is the config: $ uname -a Linux localhost 4.14.56-desktop-1.mga6 #1 SMP Mon Jul 16 20:46:05 UTC 2018 i686 i686 i686 GNU/Linux noapic splash quiet noiswmd resume=UUID=566ab761-91a8-4316-81b0-77d6bebfba1e audit=0 I wonder if the noapic makes a difference?
Give noapic a try. If it works for the old build, it should work for the live system too.
I did, it worked. For another oddity it also fixed my auto-mount issue for USB devices (at least they correlated). Using noapic also resolved the issue of the system not completely shutting down which is what acpi=off is documented to cause.
I guess you must have added the noapic option to the old install, as I can't find anything in the installer that would have done it automatically. And it is known that that option needs to be added to prevent hangs on some old hardware (as described in https://wiki.mageia.org/en/How_to_set_up_kernel_options). Maybe we should have a reference to that in the Errata. Similarly, it is known the nouveau driver doesn't work with all NVIDIA cards (I know Len has at least one machine that only works with the proprietary driver). Again this is mentioned on the Wiki (https://wiki.mageia.org/en/Mageia_6_Errata#Non-working_graphics). Much as I would like it to be otherwise, I don't think there's much more we can do - there's no set of boot options which will work for every bit of hardware out there.
Keywords: (none) => IN_ERRATA6
I'm good with that as I understand the challenge. I think noapic may have been needed after 4.9.5x kernel. I know I had to make several changes to make it work.
Not sure what the proper resolution for this is - there isn't a CANT_FIX option - so WORKSFORME will have to do,
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED