http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER?(coolo@novell. | |com) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c2 --- Comment #2 from Vincent Untz 2010-06-07 14:55:47 UTC --- Seems to help, yes :-) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c4 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #4 from Vincent Untz 2010-06-18 09:04:11 UTC --- (In reply to comment #3)

hi guys,could this be closed? Thanks.

I don't know if this was fixed. The kernel people will know if powernow_k8 acpi_cpufreq are still modules or not (see comment #1). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c6 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com, | |jeffm@novell.com AssignedTo|kernel-maintainers@forge.pr |trenn@novell.com |ovo.novell.com | --- Comment #6 from Jeff Mahoney 2010-06-21 14:52:50 UTC --- I don't think this is a kernel issue, short of adding some sort of CPU detection support to the kernel for automatic issuing of uevents for udev to load the driver. That's definitely not in the scope of 11.3 this far along. Coolo - Any suggestions where this should be moved to? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c8 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |ASSIGNED --- Comment #8 from Thomas Renninger 2010-06-21 15:47:22 UTC --- Sound reasonable. But we need a tiny boot param to be able to disable cpufreq: CPUFREQ=[off,no] would be hal compatible. There would be very old machines supported by powernow-k7 or speedstep-xy drivers, people would need to load them manually, hal tried to load: speedstep_centrino powernow_k8 powernow_k7 powernow_k6 longrun speedstep_ich acpi_cpufreq (speedstep-centrino can be removed it's more or less non-functional). I wonder why this found that late. When was hal removed? Waiting a day or so for comments... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c10 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|vuntz@novell.com | --- Comment #10 from Vincent Untz 2010-06-28 19:52:30 UTC --- (In reply to comment #9)

Does hal do any harm to your machine, Vincent?

I don't think it can harm the machine. Or if it does, it'll be with things I won't notice for a while... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c12 --- Comment #12 from Kay Sievers 2010-06-29 10:58:24 UTC --- (In reply to comment #9)

I rather readd hal to the distribution than changing kernel configs at this point.

I guess that stuff just belongs into: /etc/sysconfig/kernel::MODULES_LOADED_ON_BOOT= ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c14 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|SHIP_STOPPER+ |SHIP_STOPPER- --- Comment #14 from Stephan Kulow 2010-06-29 17:36:13 CEST --- with the work around in place, it's no longer ship stopper -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c16 --- Comment #16 from Vincent Untz 2010-08-06 20:45:46 UTC --- (In reply to comment #15)

What is this about now? Does this work for 11.3 and should the bug be against factory?

This only "works" in 11.3 because we've put back in the default install, and the hal init.d script loads the right modules. Anyway, we definitely want to fix that in factory... -- Configure bugmail: http://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=612131 https://bugzilla.novell.com/show_bug.cgi?id=612131#c17 --- Comment #17 from Vincent Untz 2010-09-21 08:56:34 UTC --- (In reply to comment #15)

If I have a lot time, I'd like to do it properly and provide a facility to autoload CPU dependent drivers.

Just wondering: do you have an ETA for this? If it's a long time away, it might make sense to just split the code from the hal init script in another init script for now. -- 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=612131 https://bugzilla.novell.com/show_bug.cgi?id=612131#c19 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |trenn@novell.com InfoProvider| |vuntz@novell.com AssignedTo|kernel-maintainers@forge.pr |trenn@novell.com |ovo.novell.com | --- Comment #19 from Thomas Renninger 2011-02-01 12:28:38 UTC --- So we can close this issue for 11.4? I can take care to remove the stuff again, once proper CPU driver autoloading exists. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=612131 http://bugzilla.novell.com/show_bug.cgi?id=612131#c21 --- Comment #21 from Bernhard Wiedemann --- This is an autogenerated message for OBS integration: This bug (612131) was mentioned in https://build.opensuse.org/request/show/42269 Factory / patterns-openSUSE -- You are receiving this mail because: You are on the CC list for the bug.