https://bugzilla.novell.com/show_bug.cgi?id=338188#c1 --- Comment #1 from Jan Engelhardt 2007-10-31 10:08:10 MST --- Actually, depmod -a puts most modules into /lib/modules/*/Modules.unsupported.blacklist. This is annoying. 17:07 ichi:/lib/modules/2.6.23.1-900.ccj58-regular > grep TCPMSS modules.unsupported.blacklist blacklist xt_TCPMSS unsupported Because it still leaves me with the question why xt_TCPMSS can be modprobed, while ipt_TCPMSS can not. -- 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=338188#c4 Jan Engelhardt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jengelh@gmx.de | --- Comment #4 from Jan Engelhardt 2007-11-01 01:59:54 MST --- It is not commented out: # # Every kernel module has a flag 'supported'. If this flag is not set loading # this module will taint your kernel. You will not get much help with a kernel # problem if your kernel is marked as tainted. In this case you firstly have # to avoid loading of unsupported modules. # # Enabling this entry makes sure that autoloading of modules via module aliases # will skip unsupported modules. Commenting this out enables autoloading of # these modules. include modules.unsupported.blacklist This is how the file is stored in the module-init-tools-3.2.99.pre11-23.i586.rpm, so everyone using opensuse got that. -- 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=338188#c6 Jan Engelhardt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jengelh@gmx.de | --- Comment #6 from Jan Engelhardt 2007-11-01 02:18:38 MST --- Upgrade from previous 10.2 -- which did not have /etc/modprobe.d/unsupported.blacklist in its RPM package. Adding set -x to the %post script makes clear why it went bonkers: 09:14 ichi:/home/lbuild-jengelh/output-10.3 # rpm -Uhv module-init-tools-3.2.9pre11-23.ccj1.test0.i586.rpm Preparing... ########################################### [100%] 1:module-init-tools ########################################### [100%] ++ uname -r + uname_r=2.6.23.1-900.ccj58-pae + test -e /lib/modules/2.6.23.1-900.ccj58-pae/modules.dep -a '!' -e /lib/modules/2.6.23.1-900.ccj58-pae/modules.unsupported.blacklist + unblacklist= + test -e /etc/sysconfig/hardware/config + test 2 = 1 + test x = xyes So, upgrading 10.2's module-init-tools RPM to the one in 10.3 added /etc/modprobe.d/unsupported.blacklist to my filesystem, but it did not get around to unblacklist: # if this is _new install_ and we are not SLES, unblacklist if test "$1" = 1; then -- 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=338188#c8 Jan Engelhardt changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Minor Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #8 from Jan Engelhardt 2007-11-01 02:31:51 MST --- Is there any specfile around which *also* deletes /etc/sysconfig/hardware/config? -- 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=338188 User tilman.vogel@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=338188#c10 Tilman Vogel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tilman.vogel@web.de --- Comment #10 from Tilman Vogel 2008-02-29 17:26:51 MST --- I was bitten by the same issue when upgrading from SuSE Linux 10.0. -- 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=338188 User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=338188#c12 --- Comment #12 from Michal Marek 2008-06-12 06:32:10 MDT --- (In reply to comment #10 from Tilman Vogel)

I was bitten by the same issue when upgrading from SuSE Linux 10.0.

Hmm yes, when updating from 10.0, it'll break, because 10.0 didn't have the LOAD_UNSUPPORTED_MODULES_AUTOMATICALLY sysconfig variable at all. But then, if you skip *two* versions during an update, you can expect some glitches... -- 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=338188 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=338188#c14 --- Comment #14 from Lars Müller 2008-06-13 03:23:23 MDT --- This issue is a generic rpm issue. One approach would be to use the epoch feature of rpm. But this would cause several other issues the package management guys of YaST, yum, smart, and zypper know better about. Bug #399274 comment #18 has some arguments why not trying to work around the known rpm update issue. In particular why to keep all kind of %pre and %post scripts as simple as possible as they might cause more harm than benefit for the majority of users. You might know the Keep It Simple Stupid (KISS) design goal. But in the particular case of the module-init-tools %post script it isn't even a rpm issue as the chosen approach is very straight and must work even in the case of an update from 10.0 as it only depends on the existence of /etc/sysconfig/hardware/config and the value of LOAD_UNSUPPORTED_MODULES_AUTOMATICALLY=yes Therefore in this case no reason to hit any at SUSE with a clue stick. :) -- 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.