Mailinglist Archive: opensuse-bugs (3171 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=756085

https://bugzilla.novell.com/show_bug.cgi?id=756085#c18


Thomas Renninger <trenn@xxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEEDINFO
       InfoProvider|                            |tittiatcoke@xxxxxxxxx

--- Comment #18 from Thomas Renninger <trenn@xxxxxxxx> 2012-05-10 22:16:46 UTC 
---
Raymond, no problem. I am familiar with the Linux boot process.

Install (booted via DVD/network/whereever) and installed kernel (after first
installation stage completed) are totally different.

acpi-cpufreq is included in the install initrd and a separate mechanism, on
SUSE linuxrc (the init process on first installation stage), probes specific
modules.

The installed kernel is what we are talking about I expect. This does not
happen at installation time, right?
There you have 2 stages of probing modules. Both done via udev for some time.

The first stage in initrd. The only purpose is to provide and load drivers so
that the kernel is able to access the root fs on a block device (disk, network
storage, whatever). There have been laptop which need the thermal and fan
driver for fan control. The first depends on the processor driver (look at
/etc/sysconfig/kernel INITRD_MODULES="", the drivers are all about being able
to access the rootfs (probably disk) on your system and fan/thermal/processor.

The second stage is the ordinary udev module loading when the root fs and all
kernel modules installed on disk are available.

The acpi-cpufreq driver never has been added to the initrd (only to the
installation one, because you do not want to run a whole installation at
highest freq, but as said that is a totally other mechanism). Specific services
have been tried to find the right cpufreq driver (formerly hal), now things
have been cleaned up and there is a X86 CPU feature/driver autoloading
mechanism (since 3.4). This one should be used.

Hope that explains some bits.
I won't go into more details, hope you are willing to give this kernel a try:
ftp://ftp.suse.com/pub/people/trenn/acpi-cpufreq_autoload_via_est_feature

Of course it would be possible to add acpi-cpufreq driver to the initrd, but
I'd like to get rid of the "request_module()" call which is (obviously) evil
and IMO not needed.

-- 
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.