https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c Xiyuan Liu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c2 --- Comment #2 from Nikolai Zhubr 2014-01-17 11:41:20 UTC --- (In reply to comment #1)

Does YaST set the value correct in the config files?

Apparently it does. In fact, after some more experiments, I think this is neither yast problem nor initrd problem. I think it is rather that kernel and/or udev behaviour changed since opensuse 11.3, so that i915 gets loaded automatically anyway (just maybe later in boot sequence if NO_KMS_IN_INITRD is set) by means of standard device discovery and kernel module search (by vendor_id/device_id etc) and i915 in turn pulls in kms and everything. Now, my original reason for using NO_KMS_IN_INITRD was actually this: "Do not load any graphics drivers until _really_ required by some graphics subsystem (like X)". In 11.3 NO_KMS_IN_INITRD did the trick perfectly fine. In 13.1, it is essentially useless, although formally it does work. I'm now going to study udev a little bit more to try to make it skip autoloading graphics card module(s) if NO_KMS_IN_INITRD is set. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c Xiyuan Liu changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c5 --- Comment #5 from Nikolai Zhubr 2014-01-18 19:40:17 UTC --- (In reply to comment #4)

Disable plymouth(8) ... from manual page

DESCRIPTION plymouth is a graphical boot system for Linux which takes advantage of the kernel-based mode setting (KMS) available for modern graphic cards to provide a seamless, flickerfree and attractive boot screen.

beside this you should also disable the graphical mode in grub2 that is to set

GRUB_GFXPAYLOAD_LINUX=text

in /etc/default/grub and run

grub2-mkconfig -o /boot/grub2/grub.cfg

afterwards. This bug does not belong to systemd nor udev.

No plymouth installed here, and graphics in Grub was disabled of course, I should have mentioned this, sorry. Now, I have finally "solved" the problem by adding blacklist i915 into /etc/modprobe.d/99-local.conf This still allows automatic loading of i915 by X and manual loading by modprobe i915, but initially after boot text mode is retained (and this is all I want). Obviously this is not a generic solution, but I'd suggest that some reminder in the description of NO_KMS_IN_INITRD (or elsewhere) mentioning grub, plymouth and autoloading by pci_id would not hurt at least. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c7 --- Comment #7 from Nikolai Zhubr 2014-01-19 15:40:27 UTC --- (In reply to comment #6)

I'd like to know what the advantage is not using graphical mode if available? Speed can not be a reason to switch off graphical mode but use text mode only. In my experience the graphical mode systems do boot faster ... therefore I'd like to know what advantage do you have by switching off graphical mode.

Reasons are various, although admittedly, not all of them are critical, but still: * In case this box is (kind of) a server, not loading additional unnecessary (and quite complicated and possibly somewhat buggy) kernel-space code is good practice; * Unless I use some huge 28' monitor, modern graphics resolution is too high for my eyes to comfortably read default console font characters as they become tiny (Yes this can be adjusted, but no friendly fool-proof dialog is provided for that anyway); * Text-mode output is guaranteed to be usable (enough for urgent administration/repair) on ANY random monitor having vga connector, be it shiny new lcd from a shop today or 20 y.o. dusty crt dinosaur, and moreover, it does not matter if you have it connected at boot time or plug at some point later, it will unconditionally "just work"; * You can test/debug/update/tune i915.ko (or whatever appropriate) with comfort and no risk of suddenly being unable to even login; (This can also be achieved by using e.g. some backup kernel in bootloader, but that means more burden and implies some more expertise); * Linux distributions are still about freedom: if you don't want something, you probably prefer to remove/disable it (well, unless absolutely technically pointless). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c9 --- Comment #9 from Dr. Werner Fink 2014-01-20 12:58:47 UTC --- (In reply to comment #8) I'm aware ;) The trick is to use the same resolution for grub and text console as used later on with kms/drm. The problem is that most user arn't aware that this might happen. Nevertless I'd like to know which before X11 is loding the kms/drm module if not done in initrd (mkinitrd or dracut). Please show me the result of sudo lsinitrd /boot/initrd | grep i915.ko also sudo journalctl --all | grep 'Inserted module' clearly without the blacklist line -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c11 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmilasan@suse.com --- Comment #11 from Dr. Werner Fink 2014-01-20 16:22:00 UTC --- Taking former udev maintainer into CC .. maybe Robert knows more about this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c13 --- Comment #13 from Dr. Werner Fink 2014-01-21 08:27:41 UTC --- (In reply to comment #12) The question is which rule or similar triggers the load of KMS/DMR modules -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c15 --- Comment #15 from Dr. Werner Fink 2014-01-21 09:47:24 UTC --- OK ... maybe a stupid question: could it be that loading console fonts may cause a resize which then trigger loading the KMS/DMR modules for modeset? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c17 --- Comment #17 from Dr. Werner Fink 2014-01-21 10:26:40 UTC --- @ Nikolai ... this bug becomes more and more invalid. You may try to set nomodeset modeset=0 or only nomodeset on the kernels command line[1] but disabling kernel events by default due NO_KMS_IN_INITRD looks like no nogo for me. To be able to boot a system in save mode grub already has normally a kernel line which includes nomodeset and x11failsafe. [1] /usr/src/linux/drivers/video/console/vgacon.c ... /* force text mode - used by kernel modesetting */ __setup("nomodeset", text_mode); -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c19 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com, | |mmarek@suse.com, | |trenn@suse.com Component|Basesystem |Documentation AssignedTo|bnc-team-screening@forge.pr |ke@suse.com |ovo.novell.com | QAContact|qa-bugs@suse.de |ke@suse.com --- Comment #19 from Dr. Werner Fink 2014-01-21 11:22:26 UTC --- (In reply to comment #18) Please give the kernel command line parameters from comment #17 a try ... which of them are working (without blacklisting the i915 module) In the meanwhile I'm reassigning this to the documentation people ... also the YaST2 or mkinitrd/dracut people may add a comment to the description of /var/adm/fillup-templates/sysconfig.kernel-mkinitrd to mention then the kernels parameter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c21 --- Comment #21 from Dr. Werner Fink 2014-01-21 16:22:23 UTC --- OK then nomodeset nor modeset=0 should not be mentioned but really the last resort for getting a not bootable system due DRM/KMS up and running without X11. Nevertheless the trick/workaround of using a blacklist for a specific video kernel module in the file /etc/modprobe.d/99-local.conf could be mentioned. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c23 --- Comment #23 from Nikolai Zhubr 2014-05-06 15:42:44 UTC --- (In reply to comment #22)

I'm wondering what this bug is about... Is it about a misleading yast help text?

Essentially yes, I suppose... Adding more up-to-date hints to the description text would be good. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c25 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Basesystem AssignedTo|yast2-maintainers@suse.de |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsrain@suse.com |qa-bugs@suse.de --- Comment #25 from Arvin Schnell 2014-05-08 10:18:03 UTC --- Yes, YaST uses the description from the sysconfig file. So the documentation must be changed there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c26 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com, | |sfalken@opensuse.org --- Comment #26 from Dr. Werner Fink 2014-05-26 06:52:17 UTC --- This bug does *not* belong to systemd. For systemd it does not matter nor does it use NO_KMS_IN_INITRD ... it simply uses /dev/console. The NO_KMS_IN_INITRD has to used by mkinitrd or dracut and nothing else. Beside this: the documentation says that no KMS is loaded into the initrd ... it does not say that no KMS is loaded after initrd has finished. IMHO it is up on YAST or any other configuration module to blacklist the i915 module ... but as already said: it is not specified with NO_KMS_IN_INITRD ... this would require soemthing NO_KMS_WITHOUT_X11, nevertheless this does not belong systemd nor udev. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=859042 https://bugzilla.novell.com/show_bug.cgi?id=859042#c Michal Filka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfilka@suse.com AssignedTo|yast2-maintainers@suse.de |lslezak@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.