https://bugzilla.novell.com/show_bug.cgi?id=427045 Matt Sealey <matt@genesi-usa.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Booting |Booting Product|openSUSE 11.0 |openSUSE 11.1 Target Milestone|--- |Beta 1 Version|Final |Factory -- 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=427045 User zoz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=427045#c1 Christian Zoz <zoz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmacht@novell.com, seife@novell.com, | |dkukawka@novell.com Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Christian Zoz <zoz@novell.com> 2008-09-19 07:22:04 MDT --- If you want to avoid that a kernel module is loaded, then please go for /etc/modprobe.conf.local: install <module> /bin/true see 'man modprobe.conf' Since most modern cpus use multiple frequencies, we will not add such an rarely used switch to sysconfig to keep config as simple as possible. I hope you can understand our POV. -- 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=427045 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=427045#c3 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #3 from Stefan Seyfried <seife@novell.com> 2008-09-19 09:41:39 MDT --- And as this is PowerPC (a fact that was possibly simply overlooked until now), it does not make sense to check for modules that are not available there at all. So there are two things to check / fix: - find out _if_ there are any cpufreq modules on ppc at all - if there are some, adjust the module list for ppc. While doing this, it should not be too hard to have cpufreq switched off completetly from a configuration file, but that's nothing for me (only an interested bystander :) to decide. -- 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=427045 User matt@genesi-usa.com added comment https://bugzilla.novell.com/show_bug.cgi?id=427045#c5 --- Comment #5 from Matt Sealey <matt@genesi-usa.com> 2008-09-19 15:00:44 MDT --- (In reply to comment #3 from Stefan Seyfried)

And as this is PowerPC (a fact that was possibly simply overlooked until now), it does not make sense to check for modules that are not available there at all.

So there are two things to check / fix: - find out _if_ there are any cpufreq modules on ppc at all

There are CPUFreq modules for PPC; for 750FX which are used on very late model iBook G3, and for 7447A-based G4 iBook and PowerBook (also late model). This is both implemented in-chip and with the help of some ASIC. All PowerMac G5 models should support it too (64-bit). The e300 (G2) core we use in the Efika, and the 7447 we use on the Pegasos, did not have any CPUfreq functionality. There are a lot of relevant G3 and G4 Mac hardware which it does not make sense to even attempt to load the modules.

While doing this, it should not be too hard to have cpufreq switched off completetly from a configuration file, but that's nothing for me (only an interested bystander :) to decide.

Indeed, some 750FX processors (see above) do not work properly with cpufreq; maybe the driver doesn't work or maybe it checks and does just do nothing. But, it should be possible to turn it off without using a kernel argument (the modules are not in the kernel anyway so it makes little sense to pass them as a kernel argument in my opinion). I also see regular forum posts and bugreports about cpufreq on x86 (where it is also modular) when new processors break, or old buggy processors cause some strange functionality. Just a note to say that, this is not urgent, nor is it a requirement, nor will I be particularly disappointed to see nothing happen. I just thought it was odd that such a functionality (which can be turned off seperately on Fedora for example with "service cpufreq off" and similar, as an example) is hardcoded into the haldaemon script with no configuration variable, when everything else is so configurable through /etc/sysconfig. I guess the suggestion is, can we turn CPUFreq into a service, and if not, just turn it off in haldaemon with /etc/sysconfig/something so it is not something we have to reconfigure GRUB for? :) Thanks for your interest :) -- 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=427045 User hmacht@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=427045#c7 Holger Macht <hmacht@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@novell.com Status|NEW |ASSIGNED --- Comment #7 from Holger Macht <hmacht@novell.com> 2008-10-08 04:56:10 MDT --- I think we will add something like this to a pm-profiler profile we are going to have in 11.1. -- 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.