Re: [ipw3945-devel] iwl3945 in 2.6.24-rc1 dies under load
On 10/31/07, Pavel Machek <[EMAIL PROTECTED]> wrote: > > Hi! > > ...does not seem to work too well :-(. It connects with the AP > (good!), and survives some "normal" use, but it died at first big > tcpspray (bd!). > > Oct 31 01:05:07 amd kernel: phy4: Selected rate control algorithm > 'simple' [..] > Oct 31 01:23:53 amd kernel: iwl3945: iwl-3945-rs not selected as rate > control algo! [...] the iwl driver do not work well with the simple rate scale algo. make sure that its not built into the kernel and not loaded before iwl3945 is loaded. You can also try the patches from Johannes which fixes this by letting the driver choose which one to use as default. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: allow non root users to set io priority "idle" ?
Jens Axboe wrote: On Wed, Aug 08 2007, dragoran wrote: so there is no real reason not to allow it for non root users? removing the check is easy (3 lines) or are there any other issues/problems? Andi already explained to you why it can't be enabled for non-root users. I merely talked about why idle priority works. ok, I missunderstood you. shouldn't read mails at 0:18 am ;) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: allow non root users to set io priority "idle" ?
so there is no real reason not to allow it for non root users? removing the check is easy (3 lines) or are there any other issues/problems? (resend sorry for the top post stupid gmail ;) ) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: allow non root users to set io priority "idle" ?
so there is no real reason not to allow it for non root users? removing the check is easy (3 lines) or are there any other issues/problems? On 8/7/07, Jens Axboe <[EMAIL PROTECTED]> wrote: > On Mon, Aug 06 2007, Andi Kleen wrote: > > > couldn't this be fixed by bumping idle tasks to middle while they hold a > > > > Usually to high. > > > > But it's all complicated and hasn't been done consistently > > (there are real time mutexes in the -rt kernel for example, > > but there are lots of other locks and they have higher overhead too) > > and it's unclear we really want to do all this complexity anyways. > > > > Also as I said the problem could then still happen in user space > > which then would all need to be fixed to handle PI too. > > > > In some cases the relationship is also not as simple as a single > > lock. And for IO handling it would be likely quite hard. > > > > I personally always found idle priorities quite dubious because > > even if they worked reliable for the CPU they will clear your cache/ > > load your memory controller and impact all other programs because > > of this. And for the disk they will cause additional seeks which are > > also very costly. > > But that is why the idle priority implementation in CFQ adds a grace > period before idle prio tasks are run. So that concern should not be an > issue, if so the grace period needs to be enlarged. That at least covers > the seek side of things. If idle io tasks run, then the IO load on the > system must be very low to zero. Hence other IO relevant resource > contention isn't an iissue. > > -- > Jens Axboe > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: allow non root users to set io priority "idle" ?
Andi Kleen wrote: couldn't this be fixed by bumping idle tasks to middle while they hold a Usually to high. But it's all complicated and hasn't been done consistently (there are real time mutexes in the -rt kernel for example, but there are lots of other locks and they have higher overhead too) and it's unclear we really want to do all this complexity anyways. Also as I said the problem could then still happen in user space which then would all need to be fixed to handle PI too. In some cases the relationship is also not as simple as a single lock. And for IO handling it would be likely quite hard. I personally always found idle priorities quite dubious because even if they worked reliable for the CPU they will clear your cache/ load your memory controller and impact all other programs because of this. And for the disk they will cause additional seeks which are also very costly. ok, thx so that means that the best that can be done for now is to run beagle as best effort with prio 7 (like its done now). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: allow non root users to set io priority "idle" ?
Andi Kleen wrote: dragoran <[EMAIL PROTECTED]> writes: Its possible to set the io priority using tools like ionice and syscalls. But this works only as root. Why can't a non root user change the priority of his processes to idle? I understand that realtime priority requires root but why idle? For instance the beagle trys to set its priority to idle but fails because it does not run as root. Any reason for this that I have missed? I can't think of a case where setting the io priority to idle would have a negative impact for other users or the whole system. Very low priority can starve others when it holds some kernel resource needed by another task. Consider three tasks: one very low priority, one high priority: Low priority task holds some kernel resource, middle task eats as much CPU as it gets; high priority task wants to get the resource. High priority will need to wait for low running, which could take a long time. With true SCHED_IDLE (i believe the current implementation is not true) this could be never or at least a very long time. There are ways to defend against this problem (known as priority inheritance), but the kernel doesn't do them consistently. The same issue could also happen for user space managed resources. For IO I suppose the same could happen too. e.g. low priority task wants to write out a page and keeps it locked until the IO is finished. High priority task wants to access the page and has to wait until it is unlocked. Middle task generates an endless stream of IO that makes the idle priority writeout never finish. couldn't this be fixed by bumping idle tasks to middle while they hold a pagelock? ex: task A - hp task B - mp task C - lp (idle) task C locks a page -> becomes a mp (middle prio) task until its finished task C unlocks the page -> back to idle In general idle priorities are quite risky, even for root. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
allow non root users to set io priority "idle" ?
Its possible to set the io priority using tools like ionice and syscalls. But this works only as root. Why can't a non root user change the priority of his processes to idle? I understand that realtime priority requires root but why idle? For instance the beagle trys to set its priority to idle but fails because it does not run as root. Any reason for this that I have missed? I can't think of a case where setting the io priority to idle would have a negative impact for other users or the whole system. P.S: Please CC me when replying. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
cfs v11 tests
Hello, I tested cfs v11 on 2.6.20.10 and here are my results: I started 6 md5sum /dev/urandom and 3 glxgears with 2 glxgears X was still very responsive...but after starting the third one there where noticeable lags when using X... so I reniced it to -10 and its very smooth again. I am now writing this mail with this task in the background... one more thing: opening a new tab in gnome-terminal has a noticeable delay same for typing su I am using compiz with the nvidia 100.14.03 beta drivers on a core 2 duo T7400 x86_64 with a nvidia 7600 Go... after starting an other md5sum /dev/urandom there are some notice able delays when typing (resending) p.s: please CC me - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ipw3945-devel] [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG
Hesse, Christian wrote: On Saturday 10 February 2007 14:23, Hesse, Christian wrote: On Friday 09 February 2007 22:12, James Ketrenos wrote: We are pleased to announce the availability of a new driver for the Intel PRO/Wireless 3945ABG Network Connection adapter. Wow, great news on this rainy saturday! ;-) The driver works perfectly, I'm writing this mail via wireless link. However there are two things to note: The driver generates two network devices. The second one is for promicious mode? Is there any chance to disable the interface? ifrename renamed the wrong one to wlan0 and I had to tell my system to use eth1 for the wireless connection. Second problem is that I can't unload the module. I get the message "FATAL: Module iwlwifi is in use." even if both interfaces are down. Oh, I forgot one note: "make patch_kernel" is terribly broken. Any chance to get this fixed soon? confirmed on my box it resulted in deleting all kernel modules. (had to reinstall the kernel) (make modules in /lib/modules/`uname -r`/build after make patch_kernel) this was on fc6 x86_64 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: snd-emu10k1 broken in 2.6.13
James Courtier-Dutton wrote:
dragoran wrote:
Niko Nitsche wrote:
dragoran wrote:
Hello.
I am running FC4 and compiled a vanilla linux 2.6.13.
After booting the kernel I see an error messages that says that it was
unable to load snd-emu10k1 (see dmesg).
In dmesg I got this:
Sep 4 10:09:47 chello062178124144 kernel: snd_emu10k1: Unknown
parameter `'
Sep 4 10:09:47 chello062178124144 last message repeated 2 times
the same modprobe.conf works in 2.6.12.
I tryed to load it by hand (modprobe snd-emu10k1) => same result
modprobe snd-emu10k1 index=0 => same result.
I will attach my .config file
(please CC me as I am not subscribed to the list)
Hi,
I had the same problem with FC4/vanilla 2.6.13 and snd-intel8x0
and I had two lines in modprobe.conf like this:
options snd-card-0 index=0
options snd-intel8x0 index=0
I removed them and now everything works just fine. Accutally I had the
Unknown parameter `' messages before but the module loaded.
sorry but this isn't solution (it works thought) but this happens for
all modules that have a options line in /etc/modprobe.conf
Is this a bug or has the syntax of modprobe.conf changed in 2.6.13?
Well, those options lines are just wrong so I am not at all surprised
that it failed.
It should be:
options snd-card-0 snd-intel8x0
options snd-intel8x0 index=0
So, dragoran, what options lines do you have?
James
this is my modprobe.conf:
alias eth0 forcedeth
alias eth1 r8169
alias scsi_hostadapter sata_nv
alias snd-card-0 snd-emu10k1
options snd-card-0 index=0
options snd-emu10k1 index=0
remove snd-emu10k1 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-emu10k1
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
alias ieee1394-controller ohci1394
alias char-major-81 saa7134
options nvidia NVreg_EnableAGPFW=1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: snd-emu10k1 broken in 2.6.13
Niko Nitsche wrote: dragoran wrote: Hello. I am running FC4 and compiled a vanilla linux 2.6.13. After booting the kernel I see an error messages that says that it was unable to load snd-emu10k1 (see dmesg). In dmesg I got this: Sep 4 10:09:47 chello062178124144 kernel: snd_emu10k1: Unknown parameter `' Sep 4 10:09:47 chello062178124144 last message repeated 2 times the same modprobe.conf works in 2.6.12. I tryed to load it by hand (modprobe snd-emu10k1) => same result modprobe snd-emu10k1 index=0 => same result. I will attach my .config file (please CC me as I am not subscribed to the list) # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13 # Sun Sep 4 09:51:58 2005 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_MMU=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y # # Processor type and features # CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_MICROCODE=m CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y # CONFIG_SMP is not set # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set # CONFIG_NUMA is not set CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y CONFIG_HPET_TIMER=y CONFIG_X86_PM_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_GART_IOMMU=y CONFIG_SWIOTLB=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_PHYSICAL_START=0x10 # CONFIG_KEXEC is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y # # Power management options # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y # CONFIG_ACPI_SLEEP_PROC_SLEEP is not set CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m # CONFIG_ACPI_HOTKEY is not set CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y CONFIG_ACPI_ASUS=m CONFIG_ACPI_IBM=m CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_BLACKLIST_YEAR=2001 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_ACPI_CONTAINER is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y CONFIG_CPU_FREQ_DEBUG=y CONFIG_CPU_FREQ_STAT=m CONFIG_CPU_FREQ_STAT_DETAILS=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=m CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m # # CPUFreq processor drivers # CONFIG_X86_POWERNOW_K8=y CONFIG_X86_POWERNOW_K8_ACPI=y CONFIG_X86_SPEEDSTEP_CENTRINO=y CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y CONFIG_X86_ACPI_CPUFREQ=m # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set # CONFIG_X86_SPEEDSTEP_LIB is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_UNORDERED_IO is not set CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=m # CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set CONFIG_PCI_MSI=y CONFIG_PCI_LEGACY_PROC=y # CONFIG_PCI_NAMES is not set # CONFIG_PCI_DEBUG is not set # # PCCARD (PCMCIA/CardBus) support # CONFIG_PCCARD=m # CONFIG_PCMCIA_DEBUG is not set CONFIG_PCMCIA=m # CONFIG_PCMCIA_LOAD_CIS is not set # CONF
snd-emu10k1 broken in 2.6.13
Hello. I am running FC4 and compiled a vanilla linux 2.6.13. After booting the kernel I see an error messages that says that it was unable to load snd-emu10k1 (see dmesg). In dmesg I got this: Sep 4 10:09:47 chello062178124144 kernel: snd_emu10k1: Unknown parameter `' Sep 4 10:09:47 chello062178124144 last message repeated 2 times the same modprobe.conf works in 2.6.12. I tryed to load it by hand (modprobe snd-emu10k1) => same result modprobe snd-emu10k1 index=0 => same result. I will attach my .config file (please CC me as I am not subscribed to the list) # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13 # Sun Sep 4 09:51:58 2005 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_MMU=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y # # Processor type and features # CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_MICROCODE=m CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y # CONFIG_SMP is not set # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set # CONFIG_NUMA is not set CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y CONFIG_HPET_TIMER=y CONFIG_X86_PM_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_GART_IOMMU=y CONFIG_SWIOTLB=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_PHYSICAL_START=0x10 # CONFIG_KEXEC is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_ISA_DMA_API=y # # Power management options # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y # CONFIG_ACPI_SLEEP_PROC_SLEEP is not set CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m # CONFIG_ACPI_HOTKEY is not set CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y CONFIG_ACPI_ASUS=m CONFIG_ACPI_IBM=m CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_BLACKLIST_YEAR=2001 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_ACPI_CONTAINER is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y CONFIG_CPU_FREQ_DEBUG=y CONFIG_CPU_FREQ_STAT=m CONFIG_CPU_FREQ_STAT_DETAILS=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=m CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m # # CPUFreq processor drivers # CONFIG_X86_POWERNOW_K8=y CONFIG_X86_POWERNOW_K8_ACPI=y CONFIG_X86_SPEEDSTEP_CENTRINO=y CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y CONFIG_X86_ACPI_CPUFREQ=m # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set # CONFIG_X86_SPEEDSTEP_LIB is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_UNORDERED_IO is not set CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=m # CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set CONFIG_PCI_MSI=y CONFIG_PCI_LEGACY_PROC=y # CONFIG_PCI_NAMES is not set # CONFIG_PCI_DEBUG is not set # # PCCARD (PCMCIA/CardBus) support # CONFIG_PCCARD=m # CONFIG_PCMCIA_DEBUG is not set CONFIG_PCMCIA=m # CONFIG_PCMCIA_LOAD_CIS is not set # CONFIG_PCMCIA_IOCTL is not set CONFIG_CARDBUS=y # # PC-card bridges # CONFIG_YENTA=m CONFIG_PD6729=m CONFIG_I82092=m CONFIG_TCIC=m CONFIG_PCCARD_NONSTA
