Bug 388005 - applesmc kernel module not loaded by default
Summary: applesmc kernel module not loaded by default
Status: RESOLVED INVALID
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 2
Hardware: Other Other
: P5 - None : Normal with 5 votes (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-07 21:59 UTC by First Last
Modified: 2008-11-13 16:36 UTC (History)
4 users (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description First Last 2008-05-07 21:59:24 UTC
Platform: MacBook, first generation (core duo)
Product: openSUSE 11.0 Beta 2
Media: openSUSE Beta 2 KDE 4 Live-CD (not installed)

Problem:

The applesmc module is not loaded on my MacBook by default using the live-cd. As far as I understand the module on the macBook for some hardware (including CPU fan speed and accelerometer) to work correctly.
Comment 1 Stephan Kulow 2008-05-08 07:06:15 UTC
Rudi, you have one of those too, no?
Comment 2 Ruediger Oertel 2008-05-08 08:52:59 UTC
well, I have a MacBookPro (2nd gen), but the module is not loaded here
either. I have an entry in boot.local modprobing this one.

looking at  modules.pcimap, there is not a single entry for applesmc, so it can not be loaded automatically.

Comment 3 Lars Vogdt 2008-05-08 10:10:01 UTC
Just FYI: http://en.opensuse.org/MacBook_Pro_Specials contains more details about specific hardware settings for MacBook Pro.
Comment 4 Ruediger Oertel 2008-11-05 15:22:57 UTC
still not being loaded by default (SLE11/oS11.1 beta4)

is this something for the kernel ?
Comment 5 Christian Zoz 2008-11-12 18:09:58 UTC
If the module does not contain modaliases, then it cannot be loaded automatically. --> kernel, upstream
Comment 6 Greg Kroah-Hartman 2008-11-13 16:36:59 UTC
There is no way for the kernel to know to automatically load this module, just add it to your module startup list and it will be loaded then.

Nothing the kernel can do here...