[gentoo-user] Problem with CPU temperature (Santa Rosa CPU)

public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed

* [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
@ 2007-10-09 17:33 Marco Calviani
  2007-10-09 18:44 ` Volker Armin Hemmann
       [not found] ` <d257c3560710091122j501e0d47oa1553da3b1156ebd@mail.gmail.com>
  0 siblings, 2 replies; 19+ messages in thread
From: Marco Calviani @ 2007-10-09 17:33 UTC (permalink / raw
  To: gentoo-user; +Cc: gentoo-laptop

Hi list,
   i have a Santa Rosa (Core 2 Duo T7300) Acer AS5720 laptop, and i'm
getting problems with the temperature of the CPU. In particular i'm
using the coretemp module for determining the core temperature.
Normally (using cpufreqd and the "ondemand" governor) the CPU stays at
nearly 50C  (which i think is quite high since in windows , using Core
Temp it gives about 30C).
While compiling this increases up to 95-100C (after which it shuts
down). The problem is that the fan is not spinning up at all!
What can be the cause of this behaviour? consider that i'm using an up
to date system with gentoo-sources-2.6.22-r8.

Any help appreciated,
Regards,
Marco
-- 
gentoo-user@gentoo.org mailing list

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-09 17:33 [gentoo-user] Problem with CPU temperature (Santa Rosa CPU) Marco Calviani
@ 2007-10-09 18:44 ` Volker Armin Hemmann
  2007-10-10  7:27   ` Marco Calviani
       [not found] ` <d257c3560710091122j501e0d47oa1553da3b1156ebd@mail.gmail.com>
  1 sibling, 1 reply; 19+ messages in thread
From: Volker Armin Hemmann @ 2007-10-09 18:44 UTC (permalink / raw
  To: gentoo-user

On Dienstag, 9. Oktober 2007, Marco Calviani wrote:
> Hi list,
>    i have a Santa Rosa (Core 2 Duo T7300) Acer AS5720 laptop, and i'm
> getting problems with the temperature of the CPU. In particular i'm
> using the coretemp module for determining the core temperature.
> Normally (using cpufreqd and the "ondemand" governor) the CPU stays at
> nearly 50C  (which i think is quite high since in windows , using Core
> Temp it gives about 30C).
> While compiling this increases up to 95-100C (after which it shuts
> down). The problem is that the fan is not spinning up at all!
> What can be the cause of this behaviour? consider that i'm using an up
> to date system with gentoo-sources-2.6.22-r8.

ACPI. You might be missing some options there. Or something else. Are you 
using fancontrol? If yes, try without, if no, try with it ;)
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-09 18:44 ` Volker Armin Hemmann
@ 2007-10-10  7:27   ` Marco Calviani
  2007-10-10  9:42     ` Volker Armin Hemmann
  0 siblings, 1 reply; 19+ messages in thread
From: Marco Calviani @ 2007-10-10  7:27 UTC (permalink / raw
  To: gentoo-user; +Cc: gentoo-laptop

Hi Volker,
  yes i can imagine there could be something wrong with ACPI, but how
can i recognize it? What is fancontrol?

m

> ACPI. You might be missing some options there. Or something else. Are you
> using fancontrol? If yes, try without, if no, try with it ;)
> --
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-10  7:27   ` Marco Calviani
@ 2007-10-10  9:42     ` Volker Armin Hemmann
  2007-10-10 10:53       ` Marco Calviani
  0 siblings, 1 reply; 19+ messages in thread
From: Volker Armin Hemmann @ 2007-10-10  9:42 UTC (permalink / raw
  To: gentoo-user

On Mittwoch, 10. Oktober 2007, Marco Calviani wrote:
>   yes i can imagine there could be something wrong with ACPI, but how
> can i recognize it?

posting your config? make menuconfig and reading the help-text to all the 
acpi-options?

> What is fancontrol? 

a nice tool, included into lm_sensors. pwmconfig to configure 
it /etc/init.d/fancontrol start, to start it. If everything works, it will 
spin the fans up/down when the temperature rises/goes down.

I have it running on my desktop and it is great - 1000rpm instead of 3000 at 
the moment.

-- 
gentoo-user@gentoo.org mailing list

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-10  9:42     ` Volker Armin Hemmann
@ 2007-10-10 10:53       ` Marco Calviani
  2007-10-10 10:55         ` Marco Calviani
  0 siblings, 1 reply; 19+ messages in thread
From: Marco Calviani @ 2007-10-10 10:53 UTC (permalink / raw
  To: gentoo-user; +Cc: gentoo-laptop

Hi Volker,
  i'm attaching my kernel .config. As you can see all the ACPI related
points are enabled.

> posting your config? make menuconfig and reading the help-text to all the
> acpi-options?
>

Thanks, i've found fancontrol, but since the laptop lacks some chipset
to control the fan itself, the /etc/fancontrol is not created.

I've realized that the temperature given in the
/proc/acpi/thermal_zone/TZ01/temperature is more or less random at a
given machine startup and it does not change while the machine is on.
When it start at a temperature above 60C, the fan starts (and never
switch off) but the cores temperature remains low (~35C). If it's 0C
or 50C or something below this threshold, the fan does not switch on
and the core temp increases up to 100C.....
It would be nice to be able to link the fan control directly with the
coretemp and not with the ACPI thermal zone....

m
-- 
gentoo-user@gentoo.org mailing list

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-10 10:53       ` Marco Calviani
@ 2007-10-10 10:55         ` Marco Calviani
  2007-10-10 14:47           ` Volker Armin Hemmann
       [not found]           ` <d257c3560710100828k5967565cxe07b9b3aa4136351@mail.gmail.com>
  0 siblings, 2 replies; 19+ messages in thread
From: Marco Calviani @ 2007-10-10 10:55 UTC (permalink / raw
  To: gentoo-user; +Cc: gentoo-laptop

[-- Attachment #1: Type: text/plain, Size: 43 bytes --]

Sorry i missed the attachment.

regards,
m

[-- Attachment #2: config.artibeus --]
[-- Type: application/octet-stream, Size: 44835 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.22-gentoo-r8
# Wed Oct 10 09:15:52 2007
#
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ZONE_DMA32=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_DMI=y
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_BUG=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
# CONFIG_TASKSTATS is not set
# CONFIG_UTS_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
# CONFIG_CPUSETS is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y

#
# Block layer
#
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VSMP is not set
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
CONFIG_MCORE2=y
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_X86_HT=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_MTRR=y
CONFIG_SMP=y
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_NUMA=y
CONFIG_K8_NUMA=y
CONFIG_NODES_SHIFT=6
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NUMA_EMU=y
CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
CONFIG_DISCONTIGMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_DISCONTIGMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_NEED_MULTIPLE_NODES=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
CONFIG_OUT_OF_LINE_PFN_TO_PAGE=y
CONFIG_NR_CPUS=32
CONFIG_HOTPLUG_CPU=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_SWIOTLB=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
# CONFIG_KEXEC is not set
CONFIG_CRASH_DUMP=y
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_START=0x200000
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_K8_NB=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_ISA_DMA_API=y
CONFIG_GENERIC_PENDING_IRQ=y

#
# Power management options
#
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
# CONFIG_PM_SYSFS_DEPRECATED is not set
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION=""
CONFIG_SUSPEND_SMP=y

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_SLEEP_PROC_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_DOCK=m
# CONFIG_ACPI_BAY is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_SBS=m

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_DEBUG=y
CONFIG_CPU_FREQ_STAT=y
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=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y

#
# CPUFreq processor drivers
#
# CONFIG_X86_POWERNOW_K8 is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_ACPI_CPUFREQ=y

#
# shared options
#
CONFIG_X86_ACPI_CPUFREQ_PROC_INTF=y
# CONFIG_X86_SPEEDSTEP_LIB is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_HT_IRQ is not set

#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
# CONFIG_YENTA is not set
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_SYSVIPC_COMPAT=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET6_XFRM_MODE_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_IPV6_SIT=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_NETLABEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
CONFIG_NET_SCH_FIFO=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
CONFIG_BT=y
CONFIG_BT_L2CAP=m
CONFIG_BT_SCO=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUSB_SCO=y
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
# CONFIG_BT_HCIDTL1 is not set
# CONFIG_BT_HCIBT3C is not set
# CONFIG_BT_HCIBLUECARD is not set
# CONFIG_BT_HCIBTUART is not set
CONFIG_BT_HCIVHCI=m
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_DEBUG is not set
# CONFIG_RXKAD is not set

#
# Wireless
#
CONFIG_CFG80211=m
CONFIG_WIRELESS_EXT=y
CONFIG_MAC80211=m
# CONFIG_MAC80211_LEDS is not set
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG is not set
CONFIG_IEEE80211=y
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=y
CONFIG_IEEE80211_CRYPT_TKIP=y
# CONFIG_IEEE80211_SOFTMAC is not set
CONFIG_RFKILL=m
# CONFIG_RFKILL_INPUT is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_PNPACPI=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECS is not set
# CONFIG_BLK_DEV_DELKIN is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
CONFIG_BLK_DEV_IDEACPI=y
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_BLK_DEV_ATIIXP=y
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_BLK_DEV_TC86C001 is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
# CONFIG_SCSI_TGT is not set
CONFIG_SCSI_NETLINK=y
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
CONFIG_SCSI_SAS_ATTRS=y
# CONFIG_SCSI_SAS_LIBSAS is not set

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
CONFIG_SCSI_AIC79XX=y
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=4000
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_ARCMSR is not set
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=y
CONFIG_MEGARAID_MAILBOX=y
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_MEGARAID_SAS=y
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set

#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_SVW=y
CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
CONFIG_SATA_NV=y
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
CONFIG_SATA_SIL=y
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
CONFIG_SATA_VIA=y
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_CRYPT is not set
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_MIRROR is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_BLK_DEV_DM_BBR is not set

#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_SPI=y
# CONFIG_FUSION_FC is not set
CONFIG_FUSION_SAS=y
CONFIG_FUSION_MAX_SGE=128
# CONFIG_FUSION_CTL is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
CONFIG_IEEE1394=y

#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set

#
# Controllers
#
# CONFIG_IEEE1394_PCILYNX is not set
CONFIG_IEEE1394_OHCI1394=y

#
# Protocols
#
# CONFIG_IEEE1394_VIDEO1394 is not set
# CONFIG_IEEE1394_SBP2 is not set
# CONFIG_IEEE1394_ETH1394_ROM_ENTRY is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
CONFIG_IEEE1394_RAWIO=y

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=y
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
# CONFIG_TYPHOON is not set

#
# Tulip family network device support
#
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_PCMCIA_XIRCOM is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
CONFIG_B44=y
CONFIG_FORCEDETH=y
# CONFIG_FORCEDETH_NAPI is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
CONFIG_E100=y
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
CONFIG_8139CP=y
CONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
# CONFIG_E1000_NAPI is not set
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_TIGON3=y
CONFIG_BNX2=y
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
CONFIG_NETDEV_10000=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_IXGB is not set
CONFIG_S2IO=m
# CONFIG_S2IO_NAPI is not set
# CONFIG_MYRI10GE is not set
# CONFIG_NETXEN_NIC is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET_MII is not set
# CONFIG_USB_USBNET is not set
# CONFIG_NET_PCMCIA is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
CONFIG_NETCONSOLE=y
CONFIG_NETPOLL=y
# CONFIG_NETPOLL_TRAP is not set
CONFIG_NET_POLL_CONTROLLER=y

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=y
CONFIG_HW_RANDOM_AMD=y
# CONFIG_HW_RANDOM_GEODE is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
CONFIG_RAW_DRIVER=y
CONFIG_MAX_RAW_DEVS=256
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_ISA=m
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
CONFIG_I2C_STUB=m
# CONFIG_I2C_TINY_USB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
CONFIG_SENSORS_EEPROM=m
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y

#
# SPI Master Controller Drivers
#
# CONFIG_SPI_BITBANG is not set

#
# SPI Protocol Masters
#
CONFIG_SPI_AT25=m
CONFIG_SPI_SPIDEV=m

#
# Dallas's 1-wire bus
#
CONFIG_W1=m

#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_MATROX is not set
# CONFIG_W1_MASTER_DS2490 is not set
# CONFIG_W1_MASTER_DS2482 is not set

#
# 1-wire Slaves
#
# CONFIG_W1_SLAVE_THERM is not set
# CONFIG_W1_SLAVE_SMEM is not set
# CONFIG_W1_SLAVE_DS2433 is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
CONFIG_SENSORS_ABITUGURU=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_K8TEMP=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_ATXP1=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_FSCPOS=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_CORETEMP=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM63=m
# CONFIG_SENSORS_LM70 is not set
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
CONFIG_SENSORS_W83793=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
CONFIG_SENSORS_HDAPS=m
# CONFIG_SENSORS_APPLESMC is not set
CONFIG_HWMON_DEBUG_CHIP=y

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
CONFIG_DAB=y
# CONFIG_USB_DABUSB is not set

#
# Graphics support
#
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=m
CONFIG_LCD_CLASS_DEVICE=m
# CONFIG_BACKLIGHT_PROGEAR is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_VGASTATE is not set
CONFIG_FB=m
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=m
CONFIG_FB_CFB_COPYAREA=m
CONFIG_FB_CFB_IMAGEBLIT=m
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_SYS_FOPS is not set
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set

#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_VGA16 is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HECUBA is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_LE80578 is not set
CONFIG_FB_INTEL=m
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_INTEL_I2C=y
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=256
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE is not set
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
# CONFIG_SND_SEQUENCER is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
# CONFIG_SND_RTCTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=m
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_AC97_POWER_SAVE=y

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set

#
# PCMCIA devices
#
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set

#
# System on Chip audio support
#
# CONFIG_SND_SOC is not set

#
# Open Sound System
#
CONFIG_SOUND_PRIME=y
# CONFIG_OSS_OBSOLETE is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_OSS is not set
CONFIG_AC97_BUS=m

#
# HID Devices
#
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_EHCI_BIG_ENDIAN_MMIO is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=y

#
# MMC/SD Host Controller Drivers
#
# CONFIG_MMC_SDHCI is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set

#
# LED devices
#
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y

#
# LED drivers
#

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=y
CONFIG_LEDS_TRIGGER_IDE_DISK=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=y

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
# CONFIG_EDAC is not set

#
# Real Time Clock
#
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set

#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set

#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_V3020 is not set

#
# on-CPU RTC drivers
#

#
# DMA Engine support
#
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y

#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m

#
# Virtualization
#
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
# CONFIG_KVM_AMD is not set

#
# Firmware Drivers
#
CONFIG_EDD=m
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_EXT2_FS_SECURITY is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_EXT4DEV_FS=y
CONFIG_EXT4DEV_FS_XATTR=y
CONFIG_EXT4DEV_FS_POSIX_ACL=y
CONFIG_EXT4DEV_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
# CONFIG_REISERFS_FS_SECURITY is not set
CONFIG_JFS_FS=y
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=y
CONFIG_XFS_QUOTA=y
# CONFIG_XFS_SECURITY is not set
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
CONFIG_GFS2_FS=m
# CONFIG_GFS2_FS_LOCKING_NOLOCK is not set
# CONFIG_GFS2_FS_LOCKING_DLM is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
CONFIG_NTFS_DEBUG=y
CONFIG_NTFS_RW=y

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_BIND34 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
CONFIG_CODA_FS=m
# CONFIG_CODA_FS_OLD_API is not set
CONFIG_AFS_FS=m
# CONFIG_AFS_DEBUG is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y

#
# Distributed Lock Manager
#
# CONFIG_DLM is not set

#
# Instrumentation Support
#
CONFIG_PROFILING=y
CONFIG_OPROFILE=y
CONFIG_KPROBES=y

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_IOMMU_DEBUG is not set
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
# CONFIG_SECURITY_CAPABILITIES is not set
# CONFIG_SECURITY_ROOTPLUG is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_GF128MUL is not set
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
# CONFIG_CRYPTO_SERPENT is not set
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=y
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
CONFIG_CRYPTO_ARC4=y
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
CONFIG_CRYPTO_MICHAEL_MIC=y
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_TEST is not set

#
# Hardware crypto devices
#

#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-10 10:55         ` Marco Calviani
@ 2007-10-10 14:47           ` Volker Armin Hemmann
       [not found]           ` <d257c3560710100828k5967565cxe07b9b3aa4136351@mail.gmail.com>
  1 sibling, 0 replies; 19+ messages in thread
From: Volker Armin Hemmann @ 2007-10-10 14:47 UTC (permalink / raw
  To: gentoo-user

On Mittwoch, 10. Oktober 2007, Marco Calviani wrote:
> Sorry i missed the attachment.
>
> regards,
> m


CONFIG_ACPI_FAN=m

the module is loaded, right? does anything change, when you compile it into 
the kernel? I have to admit - I don't know anything about laptops...
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

[parent not found: <d257c3560710100828k5967565cxe07b9b3aa4136351@mail.gmail.com>]

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
       [not found]           ` <d257c3560710100828k5967565cxe07b9b3aa4136351@mail.gmail.com>
@ 2007-10-10 18:12             ` Marco Calviani
  2007-10-10 18:41               ` Volker Armin Hemmann
       [not found]               ` <d257c3560710101217s14c0207dya59348bffd5deedb@mail.gmail.com>
  0 siblings, 2 replies; 19+ messages in thread
From: Marco Calviani @ 2007-10-10 18:12 UTC (permalink / raw
  To: gentoo-laptop; +Cc: gentoo-user

Hi Beso,
  sorry i misunderstood your suggestion. I did what you suggest and
this is the result of the trip_points:

critical (S5):      100C

which i suppose is the reason why at that temperature the laptop switch off.
So, nothing except for the critical state. Should i have to add there something?

An additional problem is this:
doing a
$ cat /proc/acpi/thermal_zone/TZ01/temperature
it gives only a:

temperature:     0C

My question is:
even if i change the polling frequency, how the fan can start if the
temperature gives 0??
Do you know if it's possible to link the fan start with the core
temperature instead of the ACPI thermal zone?

Regards,
m

>
> thats why i told you to do this commanda:
> > echo "2 seconds" >
> /proc/acpi/thermal_zone/TZ01/polling:frequency
> >
>  this enables the polling of your thermal every 2 seconds. this should be
> enough.
> do you have the other file that i mentioned:
> > /proc/acpi/thermal_zone/TZ01/trip_points ?!
> this sets the trip points for your processor. whitout it you governor cannot
> understand what to do even if it polls right.
>
> as for the kernel thigs, set these options:
> select processor type: intel core2 instead of normal x86
> CONFIG_X86_SPEEDSTEP_CENTRINO=y instead of m
> CONFIG_ACPI_FAN=y instead of m
> CONFIG_MICROCODE=y instead of m (for what i know cpu micocode is needed on
> intels)
> CONFIG_K8_NUMA=n instead of y (this should be the amdk8 numa, that you
> should not need. if it's not then let him be)
> CONFIG_X86_MCE_AMD=n instead of y (you don't need amd mce features since
> they are not included into intel cpus)
> CONFIG_NR_CPUS=32 <-- this leaves me a little dazzled: do you really have 32
> cpus in your core?! for what i know this sets the real number of cpus inside
> the kernel, but i might be wrong. so if this is really what i think it is,
> ie the real nr of cpus (not virtual ones) set this to 2 or 4 based on your
> cpu cores.
> CONFIG_HOTPLUG_CPU=n instead of y (i don't really think that you'll unplug
> your cpu from your laptop when the laptop is still running considering that
> you don't use multi cpus but a single multicore cpu. the same goes for
> memory hotplug: i don't think that your laptop supports it, so just disable
> it.)
> for what i have seen the acpi problems may be due to a failure in loading
> the intel speedstep module. if you look into the modules loaded (lsmod) you
> should not see it. so it's better to insert it directly in the kernel, since
> it is one of the first modules called (if you use it as a module you should
> be loading it with initramdisk before loading acpi to have a full acpi
> configuration).
> try setting these options and recompile and install the new kernel and
> modules and reboot (kexec is not working on my amd turion with 64bit enabled
> and so may also be for your core2duo).
>
>  2007/10/10, Marco Calviani <marco.calviani@gmail.com>:
> > Sorry i missed the attachment.
> >
> > regards,
> > m
> >
> >
>
>
>
> --
> dott. ing. beso
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-10 18:12             ` [gentoo-laptop] " Marco Calviani
@ 2007-10-10 18:41               ` Volker Armin Hemmann
  2007-10-10 18:51                 ` Marco Calviani
       [not found]               ` <d257c3560710101217s14c0207dya59348bffd5deedb@mail.gmail.com>
  1 sibling, 1 reply; 19+ messages in thread
From: Volker Armin Hemmann @ 2007-10-10 18:41 UTC (permalink / raw
  To: gentoo-user

On Mittwoch, 10. Oktober 2007, Marco Calviani wrote:
> Hi Beso,
>   sorry i misunderstood your suggestion. I did what you suggest and
> this is the result of the trip_points:
>
> critical (S5):      100C
>
> which i suppose is the reason why at that temperature the laptop switch
> off. So, nothing except for the critical state. Should i have to add there
> something?
>
> An additional problem is this:
> doing a
> $ cat /proc/acpi/thermal_zone/TZ01/temperature
> it gives only a:
>
> temperature:     0C
>
> My question is:
> even if i change the polling frequency, how the fan can start if the
> temperature gives 0??
> Do you know if it's possible to link the fan start with the core
> temperature instead of the ACPI thermal zone?

AFAIK only if you have lm_sensors installed and sensors working.

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-10 18:41               ` Volker Armin Hemmann
@ 2007-10-10 18:51                 ` Marco Calviani
  2007-10-10 22:57                   ` Volker Armin Hemmann
  0 siblings, 1 reply; 19+ messages in thread
From: Marco Calviani @ 2007-10-10 18:51 UTC (permalink / raw
  To: gentoo-user

>
> AFAIK only if you have lm_sensors installed and sensors working.

Yes there are both installed. But what do you mean?

m
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-10 18:51                 ` Marco Calviani
@ 2007-10-10 22:57                   ` Volker Armin Hemmann
  0 siblings, 0 replies; 19+ messages in thread
From: Volker Armin Hemmann @ 2007-10-10 22:57 UTC (permalink / raw
  To: gentoo-user

On Mittwoch, 10. Oktober 2007, Marco Calviani wrote:
> > AFAIK only if you have lm_sensors installed and sensors working.
>
> Yes there are both installed. But what do you mean?

that controlling the fan speed without acpi needs a) lm_sensors. b) sensors 
being working and c) fancontrol working.


-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

[parent not found: <d257c3560710101217s14c0207dya59348bffd5deedb@mail.gmail.com>]

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
       [not found]               ` <d257c3560710101217s14c0207dya59348bffd5deedb@mail.gmail.com>
@ 2007-10-11 10:14                 ` Marco Calviani
       [not found]                   ` <d257c3560710110358o66e7f061k96c569ba39246f49@mail.gmail.com>
  0 siblings, 1 reply; 19+ messages in thread
From: Marco Calviani @ 2007-10-11 10:14 UTC (permalink / raw
  To: gentoo-laptop; +Cc: gentoo-user

Hi Beso,
   i've tried with your trip_points modification but it gives this error:

bash: echo: write error: Invalid argument

like i'm not able to write on that file.

And of course acpitool gives me a random ACPI temperature:

  Battery #1     : charged
  AC adapter     : on-line
  Thermal zone 1 : ok, 40 C

PS: i followed all your suggestions concerning the microcode and fan
option in the kernel.
Could this be a problem of DSDT?

regards,
m

On 10/10/07, Beso <givemesugarr@gmail.com> wrote:
>
>
> 2007/10/10, Marco Calviani <marco.calviani@gmail.com>:
> > Hi Beso,
> >   sorry i misunderstood your suggestion. I did what you suggest and
> > this is the result of the trip_points:
> >
> > critical (S5):      100C
>
> wow.... you don't have anything that says to the cpu to slow down when it
> reaches some point....
> now, to add some other trip points you have to copy these in a konsole with
> root priviledges:
> echo "passive:                 78 C: tc1=3 tc2=1 tsp=150 devices=CPU0 \
> active[0]:               68 C: devices= FN1 \
> active[1]:               58 C: devices= FN2" >>
> /proc/acpi/thermal_zone/TZ01/trip_points
>
> then do a cat on the thermal_zone/TZ0/trip_points to see if you've added the
> lines for passive and active  lines.
> that means that when your thermal reaches 78 degrees it will slow down the
> processor. from 58 to 68 it will turn on the fan but don't turn down the
> speed of the processor, below 58 it will turn off the fan.
> >
> >
>
> > which i suppose is the reason why at that temperature the laptop switch
> off.
> > So, nothing except for the critical state. Should i have to add there
> something?
>
> if the pc turns down then it can read from somewhere the actual thermal
> point. you try to see after actually setting the things i've just said, if
> your pc is behaving as it should. remember to also turn on the polling
> frequency. without it it will not look for thermal changes. and remember to
> actually compile the mce and speedstep features in the kernel and not as
> module and reboot and then set the things i've mentioned. after that type
> acpitool (it should be installed by default with the acpi package) and see
> what it says. it should give something like this:
>
> >   Battery #1     : charging, 46.00%, 01:17:04
> >   AC adapter     : on-line
> >   Thermal zone 1 : activ, 58 C
>
> it indicates, as you can see not only the battery and ac status but also the
> current processor mode (active) and the current thermal temperature.... if
> you don't have acpitool try acpi -t (you'll surely have either one or the
> other) and it should indicate the thermal state and temperature. if this
> command don't give you these infos then you'll have to be very careful using
> your pc since acpi probably don't support santarosa well. you should then
> unmask newer acpi in portage (adding acpi in /etc/package.keywords) and try
> with the new acpi ( 1.0.6).
> you may need some additional acpi modules, like ibm_acpi for example, but
> that depends on your's pc brand. i'm looking around to see if there were
> someone that had problems with santarosa and linux acpi, but for the moment
> i couldn't find something useful. try what i've said and see if the things
> work. if they work then append the tweak in some script that starts at boot
> like the top of xdm script and you'll have a functional system. let me know
> if you were succesful on that.
>
>
> > An additional problem is this:
> > doing a
> > $ cat /proc/acpi/thermal_zone/TZ01/temperature
> > it gives only a:
> >
> > temperature:     0C
> >
> > My question is:
> > even if i change the polling frequency, how the fan can start if the
> > temperature gives 0??
> > Do you know if it's possible to link the fan start with the core
> > temperature instead of the ACPI thermal zone?
>
> probably the fan don't start since  you have it as a module. i've curently
> had the same problem which solved by compiling it integrated in the kernel.
> the fan in your case should always be on, not always be off....
>
> >
> > Regards,
> > m
> >
> > >
> > > thats why i told you to do this commanda:
> > > > echo "2 seconds" >
> > > /proc/acpi/thermal_zone/TZ01/polling:frequency
> > > >
> > >  this enables the polling of your thermal every 2 seconds. this should
> be
> > > enough.
> > > do you have the other file that i mentioned:
> > > > /proc/acpi/thermal_zone/TZ01/trip_points ?!
> > > this sets the trip points for your processor. whitout it you governor
> cannot
> > > understand what to do even if it polls right.
> > >
> > > as for the kernel thigs, set these options:
> > > select processor type: intel core2 instead of normal x86
> > > CONFIG_X86_SPEEDSTEP_CENTRINO=y instead of m
> > > CONFIG_ACPI_FAN=y instead of m
> > > CONFIG_MICROCODE=y instead of m (for what i know cpu micocode is needed
> on
> > > intels)
> > > CONFIG_K8_NUMA=n instead of y (this should be the amdk8 numa, that you
> > > should not need. if it's not then let him be)
> > > CONFIG_X86_MCE_AMD=n instead of y (you don't need amd mce features since
> > > they are not included into intel cpus)
> > > CONFIG_NR_CPUS=32 <-- this leaves me a little dazzled: do you really
> have 32
> > > cpus in your core?! for what i know this sets the real number of cpus
> inside
> > > the kernel, but i might be wrong. so if this is really what i think it
> is,
> > > ie the real nr of cpus (not virtual ones) set this to 2 or 4 based on
> your
> > > cpu cores.
> > > CONFIG_HOTPLUG_CPU=n instead of y (i don't really think that you'll
> unplug
> > > your cpu from your laptop when the laptop is still running considering
> that
> > > you don't use multi cpus but a single multicore cpu. the same goes for
> > > memory hotplug: i don't think that your laptop supports it, so just
> disable
> > > it.)
> > > for what i have seen the acpi problems may be due to a failure in
> loading
> > > the intel speedstep module. if you look into the modules loaded (lsmod)
> you
> > > should not see it. so it's better to insert it directly in the kernel,
> since
> > > it is one of the first modules called (if you use it as a module you
> should
> > > be loading it with initramdisk before loading acpi to have a full acpi
> > > configuration).
> > > try setting these options and recompile and install the new kernel and
> > > modules and reboot (kexec is not working on my amd turion with 64bit
> enabled
> > > and so may also be for your core2duo).
> > >
> > >  2007/10/10, Marco Calviani < marco.calviani@gmail.com>:
> > > > Sorry i missed the attachment.
> > > >
> > > > regards,
> > > > m
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > dott. ing. beso
> > --
> > gentoo-laptop@gentoo.org mailing list
> >
> >
>
>
>
> --
> dott. ing. beso
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

[parent not found: <d257c3560710110358o66e7f061k96c569ba39246f49@mail.gmail.com>]

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
       [not found]                   ` <d257c3560710110358o66e7f061k96c569ba39246f49@mail.gmail.com>
@ 2007-10-11 11:43                     ` Marco Calviani
       [not found]                       ` <d257c3560710110537u26ad7a1bq3cda3f0b007eb48a@mail.gmail.com>
  0 siblings, 1 reply; 19+ messages in thread
From: Marco Calviani @ 2007-10-11 11:43 UTC (permalink / raw
  To: gentoo-laptop; +Cc: gentoo-user

Hi Beso,
   i have an Acer Aspire 5720. I've tried with the acer_acpi, it
compiles well but when it comes to loading it fails, saying
"No or unsupported WMI interface, unable to load".

However as far as i can understood, this module deals with issues of
buttons and hotkey not with ACPI issues.

Yes, my DSDT failed during recompiling, but i have managed to solve
the issues, and now it compiled well (with warning but i'm not
caring). I'll try to recompile the new DSDT in the kernel, maybe it
could help (but i'm not sure).

Regards,
m

On 10/11/07, Beso <givemesugarr@gmail.com> wrote:
> yep you're right.... i cannot modify my trippoints so this file cannot be
> modified....
> i don't think that it's random, since it is 40 c.... try doing some
> compiling or so and see if it goes up and then stop compiling and do nothing
> and see if it goes down.... this will tell you if thermal is working....
> for dsdt problem you have follow this guide:
> http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
> if it gives you errors when recompiling dsdt then it may be a dsdt problem,
> but if it gives you no problem recompiling it then it may be that you need
> some additional modules like asus_acpi or ibm or toshiba ones based on your
> pc model. i don't know what you're using (i've managed to see some lenovo,
> asus toshiba and acer models around and for what i know every one of then
> needs an additional acpi module to have it work correctly). that was why
> i've asked you for your brand and model name.
>
> 2007/10/11, Marco Calviani <marco.calviani@gmail.com>:
> > Hi Beso,
> >    i've tried with your trip_points modification but it gives this error:
> >
> > bash: echo: write error: Invalid argument
> >
> > like i'm not able to write on that file.
> >
> > And of course acpitool gives me a random ACPI temperature:
> >
> >   Battery #1     : charged
> >   AC adapter     : on-line
> >   Thermal zone 1 : ok, 40 C
> >
> > PS: i followed all your suggestions concerning the microcode and fan
> > option in the kernel.
> > Could this be a problem of DSDT?
> >
> > regards,
> > m
> >
> > On 10/10/07, Beso <givemesugarr@gmail.com> wrote:
> > >
> > >
> > > 2007/10/10, Marco Calviani < marco.calviani@gmail.com>:
> > > > Hi Beso,
> > > >   sorry i misunderstood your suggestion. I did what you suggest and
> > > > this is the result of the trip_points:
> > > >
> > > > critical (S5):      100C
> > >
> > > wow.... you don't have anything that says to the cpu to slow down when
> it
> > > reaches some point....
> > > now, to add some other trip points you have to copy these in a konsole
> with
> > > root priviledges:
> > > echo "passive:                 78 C: tc1=3 tc2=1 tsp=150 devices=CPU0 \
> > > active[0]:               68 C: devices= FN1 \
> > > active[1]:               58 C: devices= FN2" >>
> > > /proc/acpi/thermal_zone/TZ01/trip_points
> > >
> > > then do a cat on the thermal_zone/TZ0/trip_points to see if you've added
> the
> > > lines for passive and active  lines.
> > > that means that when your thermal reaches 78 degrees it will slow down
> the
> > > processor. from 58 to 68 it will turn on the fan but don't turn down the
> > > speed of the processor, below 58 it will turn off the fan.
> > > >
> > > >
> > >
> > > > which i suppose is the reason why at that temperature the laptop
> switch
> > > off.
> > > > So, nothing except for the critical state. Should i have to add there
> > > something?
> > >
> > > if the pc turns down then it can read from somewhere the actual thermal
> > > point. you try to see after actually setting the things i've just said,
> if
> > > your pc is behaving as it should. remember to also turn on the polling
> > > frequency. without it it will not look for thermal changes. and remember
> to
> > > actually compile the mce and speedstep features in the kernel and not as
> > > module and reboot and then set the things i've mentioned. after that
> type
> > > acpitool (it should be installed by default with the acpi package) and
> see
> > > what it says. it should give something like this:
> > >
> > > >   Battery #1     : charging, 46.00%, 01:17:04
> > > >   AC adapter     : on-line
> > > >   Thermal zone 1 : activ, 58 C
> > >
> > > it indicates, as you can see not only the battery and ac status but also
> the
> > > current processor mode (active) and the current thermal temperature....
> if
> > > you don't have acpitool try acpi -t (you'll surely have either one or
> the
> > > other) and it should indicate the thermal state and temperature. if this
> > > command don't give you these infos then you'll have to be very careful
> using
> > > your pc since acpi probably don't support santarosa well. you should
> then
> > > unmask newer acpi in portage (adding acpi in /etc/package.keywords) and
> try
> > > with the new acpi ( 1.0.6).
> > > you may need some additional acpi modules, like ibm_acpi for example,
> but
> > > that depends on your's pc brand. i'm looking around to see if there were
> > > someone that had problems with santarosa and linux acpi, but for the
> moment
> > > i couldn't find something useful. try what i've said and see if the
> things
> > > work. if they work then append the tweak in some script that starts at
> boot
> > > like the top of xdm script and you'll have a functional system. let me
> know
> > > if you were succesful on that.
> > >
> > >
> > > > An additional problem is this:
> > > > doing a
> > > > $ cat /proc/acpi/thermal_zone/TZ01/temperature
> > > > it gives only a:
> > > >
> > > > temperature:     0C
> > > >
> > > > My question is:
> > > > even if i change the polling frequency, how the fan can start if the
> > > > temperature gives 0??
> > > > Do you know if it's possible to link the fan start with the core
> > > > temperature instead of the ACPI thermal zone?
> > >
> > > probably the fan don't start since  you have it as a module. i've
> curently
> > > had the same problem which solved by compiling it integrated in the
> kernel.
> > > the fan in your case should always be on, not always be off....
> > >
> > > >
> > > > Regards,
> > > > m
> > > >
> > > > >
> > > > > thats why i told you to do this commanda:
> > > > > > echo "2 seconds" >
> > > > > /proc/acpi/thermal_zone/TZ01/polling:frequency
> > > > > >
> > > > >  this enables the polling of your thermal every 2 seconds. this
> should
> > > be
> > > > > enough.
> > > > > do you have the other file that i mentioned:
> > > > > > /proc/acpi/thermal_zone/TZ01/trip_points ?!
> > > > > this sets the trip points for your processor. whitout it you
> governor
> > > cannot
> > > > > understand what to do even if it polls right.
> > > > >
> > > > > as for the kernel thigs, set these options:
> > > > > select processor type: intel core2 instead of normal x86
> > > > > CONFIG_X86_SPEEDSTEP_CENTRINO=y instead of m
> > > > > CONFIG_ACPI_FAN=y instead of m
> > > > > CONFIG_MICROCODE=y instead of m (for what i know cpu micocode is
> needed
> > > on
> > > > > intels)
> > > > > CONFIG_K8_NUMA=n instead of y (this should be the amdk8 numa, that
> you
> > > > > should not need. if it's not then let him be)
> > > > > CONFIG_X86_MCE_AMD=n instead of y (you don't need amd mce features
> since
> > > > > they are not included into intel cpus)
> > > > > CONFIG_NR_CPUS=32 <-- this leaves me a little dazzled: do you really
> > > have 32
> > > > > cpus in your core?! for what i know this sets the real number of
> cpus
> > > inside
> > > > > the kernel, but i might be wrong. so if this is really what i think
> it
> > > is,
> > > > > ie the real nr of cpus (not virtual ones) set this to 2 or 4 based
> on
> > > your
> > > > > cpu cores.
> > > > > CONFIG_HOTPLUG_CPU=n instead of y (i don't really think that you'll
> > > unplug
> > > > > your cpu from your laptop when the laptop is still running
> considering
> > > that
> > > > > you don't use multi cpus but a single multicore cpu. the same goes
> for
> > > > > memory hotplug: i don't think that your laptop supports it, so just
> > > disable
> > > > > it.)
> > > > > for what i have seen the acpi problems may be due to a failure in
> > > loading
> > > > > the intel speedstep module. if you look into the modules loaded
> (lsmod)
> > > you
> > > > > should not see it. so it's better to insert it directly in the
> kernel,
> > > since
> > > > > it is one of the first modules called (if you use it as a module you
> > > should
> > > > > be loading it with initramdisk before loading acpi to have a full
> acpi
> > > > > configuration).
> > > > > try setting these options and recompile and install the new kernel
> and
> > > > > modules and reboot (kexec is not working on my amd turion with 64bit
> > > enabled
> > > > > and so may also be for your core2duo).
> > > > >
> > > > >  2007/10/10, Marco Calviani < marco.calviani@gmail.com>:
> > > > > > Sorry i missed the attachment.
> > > > > >
> > > > > > regards,
> > > > > > m
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > dott. ing. beso
> > > > --
> > > > gentoo-laptop@gentoo.org mailing list
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > dott. ing. beso
> > --
> > gentoo-laptop@gentoo.org mailing list
> >
> >
>
>
>
> --
> dott. ing. beso
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

[parent not found: <d257c3560710110537u26ad7a1bq3cda3f0b007eb48a@mail.gmail.com>]

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
       [not found]                       ` <d257c3560710110537u26ad7a1bq3cda3f0b007eb48a@mail.gmail.com>
@ 2007-10-11 13:33                         ` Marco Calviani
  2007-10-13 16:49                         ` Marco Calviani
  1 sibling, 0 replies; 19+ messages in thread
From: Marco Calviani @ 2007-10-11 13:33 UTC (permalink / raw
  To: gentoo-laptop; +Cc: gentoo-user

As far as i know unfortunately the Travelmate 5720 exists, together
with the entry level Aspire 5720... I've tried also the new version
and the load error appears at the same level.
I've mailed Carlos of acer-acpi, let's see what comes out.

Thanks again for your help,
i'll let you know about the improvement of this situation,
m


On 10/11/07, Beso <givemesugarr@gmail.com> wrote:
> normally all acer have dsdt problems and don't work unless you load
> acer_acpi.
> now, in the portage tree there's only the 0.8.2 version, so you have to go
> here:
>
>  http://code.google.com/p/aceracpi/
>
> download the latest version and install it. there's a 5720 product listed
> (under travelmate and not aspire, but it may have been an error). simply
> search for acer_acpi in the /lib/modules/2.6.22-gentoo-r8 and delete it then
> do a depmod -a and update the modules installed and retry loading the newly
> compiled driver. if you manage to get it working in this way ok, if not try
> contacting the guy maintaing the aceracpi module and tell him about you
> problems. he may be of help.
>
>
> 2007/10/11, Marco Calviani <marco.calviani@gmail.com>:
> > Hi Beso,
> >    i have an Acer Aspire 5720. I've tried with the acer_acpi, it
> > compiles well but when it comes to loading it fails, saying
> > "No or unsupported WMI interface, unable to load".
> >
> > However as far as i can understood, this module deals with issues of
> > buttons and hotkey not with ACPI issues.
> >
> > Yes, my DSDT failed during recompiling, but i have managed to solve
> > the issues, and now it compiled well (with warning but i'm not
> > caring). I'll try to recompile the new DSDT in the kernel, maybe it
> > could help (but i'm not sure).
> >
> > Regards,
> > m
> >
> > On 10/11/07, Beso <givemesugarr@gmail.com> wrote:
> > > yep you're right.... i cannot modify my trippoints so this file cannot
> be
> > > modified....
> > > i don't think that it's random, since it is 40 c.... try doing some
> > > compiling or so and see if it goes up and then stop compiling and do
> nothing
> > > and see if it goes down.... this will tell you if thermal is working....
> > > for dsdt problem you have follow this guide:
> > > http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
> > > if it gives you errors when recompiling dsdt then it may be a dsdt
> problem,
> > > but if it gives you no problem recompiling it then it may be that you
> need
> > > some additional modules like asus_acpi or ibm or toshiba ones based on
> your
> > > pc model. i don't know what you're using (i've managed to see some
> lenovo,
> > > asus toshiba and acer models around and for what i know every one of
> then
> > > needs an additional acpi module to have it work correctly). that was why
> > > i've asked you for your brand and model name.
> > >
> > > 2007/10/11, Marco Calviani <marco.calviani@gmail.com>:
> > > > Hi Beso,
> > > >    i've tried with your trip_points modification but it gives this
> error:
> > > >
> > > > bash: echo: write error: Invalid argument
> > > >
> > > > like i'm not able to write on that file.
> > > >
> > > > And of course acpitool gives me a random ACPI temperature:
> > > >
> > > >   Battery #1     : charged
> > > >   AC adapter     : on-line
> > > >   Thermal zone 1 : ok, 40 C
> > > >
> > > > PS: i followed all your suggestions concerning the microcode and fan
> > > > option in the kernel.
> > > > Could this be a problem of DSDT?
> > > >
> > > > regards,
> > > > m
> > > >
> > > > On 10/10/07, Beso <givemesugarr@gmail.com > wrote:
> > > > >
> > > > >
> > > > > 2007/10/10, Marco Calviani < marco.calviani@gmail.com>:
> > > > > > Hi Beso,
> > > > > >   sorry i misunderstood your suggestion. I did what you suggest
> and
> > > > > > this is the result of the trip_points:
> > > > > >
> > > > > > critical (S5):      100C
> > > > >
> > > > > wow.... you don't have anything that says to the cpu to slow down
> when
> > > it
> > > > > reaches some point....
> > > > > now, to add some other trip points you have to copy these in a
> konsole
> > > with
> > > > > root priviledges:
> > > > > echo "passive:                 78 C: tc1=3 tc2=1 tsp=150
> devices=CPU0 \
> > > > > active[0]:               68 C: devices= FN1 \
> > > > > active[1]:               58 C: devices= FN2" >>
> > > > > /proc/acpi/thermal_zone/TZ01/trip_points
> > > > >
> > > > > then do a cat on the thermal_zone/TZ0/trip_points to see if you've
> added
> > > the
> > > > > lines for passive and active  lines.
> > > > > that means that when your thermal reaches 78 degrees it will slow
> down
> > > the
> > > > > processor. from 58 to 68 it will turn on the fan but don't turn down
> the
> > > > > speed of the processor, below 58 it will turn off the fan.
> > > > > >
> > > > > >
> > > > >
> > > > > > which i suppose is the reason why at that temperature the laptop
> > > switch
> > > > > off.
> > > > > > So, nothing except for the critical state. Should i have to add
> there
> > > > > something?
> > > > >
> > > > > if the pc turns down then it can read from somewhere the actual
> thermal
> > > > > point. you try to see after actually setting the things i've just
> said,
> > > if
> > > > > your pc is behaving as it should. remember to also turn on the
> polling
> > > > > frequency. without it it will not look for thermal changes. and
> remember
> > > to
> > > > > actually compile the mce and speedstep features in the kernel and
> not as
> > > > > module and reboot and then set the things i've mentioned. after that
> > > type
> > > > > acpitool (it should be installed by default with the acpi package)
> and
> > > see
> > > > > what it says. it should give something like this:
> > > > >
> > > > > >   Battery #1     : charging, 46.00%, 01:17:04
> > > > > >   AC adapter     : on-line
> > > > > >   Thermal zone 1 : activ, 58 C
> > > > >
> > > > > it indicates, as you can see not only the battery and ac status but
> also
> > > the
> > > > > current processor mode (active) and the current thermal
> temperature....
> > > if
> > > > > you don't have acpitool try acpi -t (you'll surely have either one
> or
> > > the
> > > > > other) and it should indicate the thermal state and temperature. if
> this
> > > > > command don't give you these infos then you'll have to be very
> careful
> > > using
> > > > > your pc since acpi probably don't support santarosa well. you should
> > > then
> > > > > unmask newer acpi in portage (adding acpi in /etc/package.keywords)
> and
> > > try
> > > > > with the new acpi ( 1.0.6).
> > > > > you may need some additional acpi modules, like ibm_acpi for
> example,
> > > but
> > > > > that depends on your's pc brand. i'm looking around to see if there
> were
> > > > > someone that had problems with santarosa and linux acpi, but for the
> > > moment
> > > > > i couldn't find something useful. try what i've said and see if the
> > > things
> > > > > work. if they work then append the tweak in some script that starts
> at
> > > boot
> > > > > like the top of xdm script and you'll have a functional system. let
> me
> > > know
> > > > > if you were succesful on that.
> > > > >
> > > > >
> > > > > > An additional problem is this:
> > > > > > doing a
> > > > > > $ cat /proc/acpi/thermal_zone/TZ01/temperature
> > > > > > it gives only a:
> > > > > >
> > > > > > temperature:     0C
> > > > > >
> > > > > > My question is:
> > > > > > even if i change the polling frequency, how the fan can start if
> the
> > > > > > temperature gives 0??
> > > > > > Do you know if it's possible to link the fan start with the core
> > > > > > temperature instead of the ACPI thermal zone?
> > > > >
> > > > > probably the fan don't start since  you have it as a module. i've
> > > curently
> > > > > had the same problem which solved by compiling it integrated in the
> > > kernel.
> > > > > the fan in your case should always be on, not always be off....
> > > > >
> > > > > >
> > > > > > Regards,
> > > > > > m
> > > > > >
> > > > > > >
> > > > > > > thats why i told you to do this commanda:
> > > > > > > > echo "2 seconds" >
> > > > > > > /proc/acpi/thermal_zone/TZ01/polling:frequency
> > > > > > > >
> > > > > > >  this enables the polling of your thermal every 2 seconds. this
> > > should
> > > > > be
> > > > > > > enough.
> > > > > > > do you have the other file that i mentioned:
> > > > > > > > /proc/acpi/thermal_zone/TZ01/trip_points ?!
> > > > > > > this sets the trip points for your processor. whitout it you
> > > governor
> > > > > cannot
> > > > > > > understand what to do even if it polls right.
> > > > > > >
> > > > > > > as for the kernel thigs, set these options:
> > > > > > > select processor type: intel core2 instead of normal x86
> > > > > > > CONFIG_X86_SPEEDSTEP_CENTRINO=y instead of m
> > > > > > > CONFIG_ACPI_FAN=y instead of m
> > > > > > > CONFIG_MICROCODE=y instead of m (for what i know cpu micocode is
> > > needed
> > > > > on
> > > > > > > intels)
> > > > > > > CONFIG_K8_NUMA=n instead of y (this should be the amdk8 numa,
> that
> > > you
> > > > > > > should not need. if it's not then let him be)
> > > > > > > CONFIG_X86_MCE_AMD=n instead of y (you don't need amd mce
> features
> > > since
> > > > > > > they are not included into intel cpus)
> > > > > > > CONFIG_NR_CPUS=32 <-- this leaves me a little dazzled: do you
> really
> > > > > have 32
> > > > > > > cpus in your core?! for what i know this sets the real number of
> > > cpus
> > > > > inside
> > > > > > > the kernel, but i might be wrong. so if this is really what i
> think
> > > it
> > > > > is,
> > > > > > > ie the real nr of cpus (not virtual ones) set this to 2 or 4
> based
> > > on
> > > > > your
> > > > > > > cpu cores.
> > > > > > > CONFIG_HOTPLUG_CPU=n instead of y (i don't really think that
> you'll
> > > > > unplug
> > > > > > > your cpu from your laptop when the laptop is still running
> > > considering
> > > > > that
> > > > > > > you don't use multi cpus but a single multicore cpu. the same
> goes
> > > for
> > > > > > > memory hotplug: i don't think that your laptop supports it, so
> just
> > > > > disable
> > > > > > > it.)
> > > > > > > for what i have seen the acpi problems may be due to a failure
> in
> > > > > loading
> > > > > > > the intel speedstep module. if you look into the modules loaded
> > > (lsmod)
> > > > > you
> > > > > > > should not see it. so it's better to insert it directly in the
> > > kernel,
> > > > > since
> > > > > > > it is one of the first modules called (if you use it as a module
> you
> > > > > should
> > > > > > > be loading it with initramdisk before loading acpi to have a
> full
> > > acpi
> > > > > > > configuration).
> > > > > > > try setting these options and recompile and install the new
> kernel
> > > and
> > > > > > > modules and reboot (kexec is not working on my amd turion with
> 64bit
> > > > > enabled
> > > > > > > and so may also be for your core2duo).
> > > > > > >
> > > > > > >  2007/10/10, Marco Calviani < marco.calviani@gmail.com>:
> > > > > > > > Sorry i missed the attachment.
> > > > > > > >
> > > > > > > > regards,
> > > > > > > > m
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > dott. ing. beso
> > > > > > --
> > > > > > gentoo-laptop@gentoo.org mailing list
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > dott. ing. beso
> > > > --
> > > > gentoo-laptop@gentoo.org mailing list
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > dott. ing. beso
> > --
> > gentoo-laptop@gentoo.org mailing list
> >
> >
>
>
>
> --
> dott. ing. beso
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
       [not found]                       ` <d257c3560710110537u26ad7a1bq3cda3f0b007eb48a@mail.gmail.com>
  2007-10-11 13:33                         ` Marco Calviani
@ 2007-10-13 16:49                         ` Marco Calviani
       [not found]                           ` <d257c3560710131008m6b8e370ala1b5af2416b4f294@mail.gmail.com>
  1 sibling, 1 reply; 19+ messages in thread
From: Marco Calviani @ 2007-10-13 16:49 UTC (permalink / raw
  To: gentoo-laptop; +Cc: gentoo-user

Just to give a short update:
1) no luck with the acer_acpi module: it does not load in the system,
as the developer is having a look at it. However he told me that the
module can do practically nothing on the thermal zone since this last
point is controlled fully by ACPI
2) i've tried to modify the DSDT table: it had errors, but also after
correction the system behave in practically the same way. I've mailed
to the acpi-linux mailing list, hoping that the acpi gurus can try to
solve the issue.
As far as i understand now it is just a matter of ACPI implementation.

Regards,
m

On 10/11/07, Beso <givemesugarr@gmail.com> wrote:
> normally all acer have dsdt problems and don't work unless you load
> acer_acpi.
> now, in the portage tree there's only the 0.8.2 version, so you have to go
> here:
>
>  http://code.google.com/p/aceracpi/
>
> download the latest version and install it. there's a 5720 product listed
> (under travelmate and not aspire, but it may have been an error). simply
> search for acer_acpi in the /lib/modules/2.6.22-gentoo-r8 and delete it then
> do a depmod -a and update the modules installed and retry loading the newly
> compiled driver. if you manage to get it working in this way ok, if not try
> contacting the guy maintaing the aceracpi module and tell him about you
> problems. he may be of help.
>
>
> 2007/10/11, Marco Calviani <marco.calviani@gmail.com>:
> > Hi Beso,
> >    i have an Acer Aspire 5720. I've tried with the acer_acpi, it
> > compiles well but when it comes to loading it fails, saying
> > "No or unsupported WMI interface, unable to load".
> >
> > However as far as i can understood, this module deals with issues of
> > buttons and hotkey not with ACPI issues.
> >
> > Yes, my DSDT failed during recompiling, but i have managed to solve
> > the issues, and now it compiled well (with warning but i'm not
> > caring). I'll try to recompile the new DSDT in the kernel, maybe it
> > could help (but i'm not sure).
> >
> > Regards,
> > m
> >
> > On 10/11/07, Beso <givemesugarr@gmail.com> wrote:
> > > yep you're right.... i cannot modify my trippoints so this file cannot
> be
> > > modified....
> > > i don't think that it's random, since it is 40 c.... try doing some
> > > compiling or so and see if it goes up and then stop compiling and do
> nothing
> > > and see if it goes down.... this will tell you if thermal is working....
> > > for dsdt problem you have follow this guide:
> > > http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
> > > if it gives you errors when recompiling dsdt then it may be a dsdt
> problem,
> > > but if it gives you no problem recompiling it then it may be that you
> need
> > > some additional modules like asus_acpi or ibm or toshiba ones based on
> your
> > > pc model. i don't know what you're using (i've managed to see some
> lenovo,
> > > asus toshiba and acer models around and for what i know every one of
> then
> > > needs an additional acpi module to have it work correctly). that was why
> > > i've asked you for your brand and model name.
> > >
> > > 2007/10/11, Marco Calviani <marco.calviani@gmail.com>:
> > > > Hi Beso,
> > > >    i've tried with your trip_points modification but it gives this
> error:
> > > >
> > > > bash: echo: write error: Invalid argument
> > > >
> > > > like i'm not able to write on that file.
> > > >
> > > > And of course acpitool gives me a random ACPI temperature:
> > > >
> > > >   Battery #1     : charged
> > > >   AC adapter     : on-line
> > > >   Thermal zone 1 : ok, 40 C
> > > >
> > > > PS: i followed all your suggestions concerning the microcode and fan
> > > > option in the kernel.
> > > > Could this be a problem of DSDT?
> > > >
> > > > regards,
> > > > m
> > > >
> > > > On 10/10/07, Beso <givemesugarr@gmail.com > wrote:
> > > > >
> > > > >
> > > > > 2007/10/10, Marco Calviani < marco.calviani@gmail.com>:
> > > > > > Hi Beso,
> > > > > >   sorry i misunderstood your suggestion. I did what you suggest
> and
> > > > > > this is the result of the trip_points:
> > > > > >
> > > > > > critical (S5):      100C
> > > > >
> > > > > wow.... you don't have anything that says to the cpu to slow down
> when
> > > it
> > > > > reaches some point....
> > > > > now, to add some other trip points you have to copy these in a
> konsole
> > > with
> > > > > root priviledges:
> > > > > echo "passive:                 78 C: tc1=3 tc2=1 tsp=150
> devices=CPU0 \
> > > > > active[0]:               68 C: devices= FN1 \
> > > > > active[1]:               58 C: devices= FN2" >>
> > > > > /proc/acpi/thermal_zone/TZ01/trip_points
> > > > >
> > > > > then do a cat on the thermal_zone/TZ0/trip_points to see if you've
> added
> > > the
> > > > > lines for passive and active  lines.
> > > > > that means that when your thermal reaches 78 degrees it will slow
> down
> > > the
> > > > > processor. from 58 to 68 it will turn on the fan but don't turn down
> the
> > > > > speed of the processor, below 58 it will turn off the fan.
> > > > > >
> > > > > >
> > > > >
> > > > > > which i suppose is the reason why at that temperature the laptop
> > > switch
> > > > > off.
> > > > > > So, nothing except for the critical state. Should i have to add
> there
> > > > > something?
> > > > >
> > > > > if the pc turns down then it can read from somewhere the actual
> thermal
> > > > > point. you try to see after actually setting the things i've just
> said,
> > > if
> > > > > your pc is behaving as it should. remember to also turn on the
> polling
> > > > > frequency. without it it will not look for thermal changes. and
> remember
> > > to
> > > > > actually compile the mce and speedstep features in the kernel and
> not as
> > > > > module and reboot and then set the things i've mentioned. after that
> > > type
> > > > > acpitool (it should be installed by default with the acpi package)
> and
> > > see
> > > > > what it says. it should give something like this:
> > > > >
> > > > > >   Battery #1     : charging, 46.00%, 01:17:04
> > > > > >   AC adapter     : on-line
> > > > > >   Thermal zone 1 : activ, 58 C
> > > > >
> > > > > it indicates, as you can see not only the battery and ac status but
> also
> > > the
> > > > > current processor mode (active) and the current thermal
> temperature....
> > > if
> > > > > you don't have acpitool try acpi -t (you'll surely have either one
> or
> > > the
> > > > > other) and it should indicate the thermal state and temperature. if
> this
> > > > > command don't give you these infos then you'll have to be very
> careful
> > > using
> > > > > your pc since acpi probably don't support santarosa well. you should
> > > then
> > > > > unmask newer acpi in portage (adding acpi in /etc/package.keywords)
> and
> > > try
> > > > > with the new acpi ( 1.0.6).
> > > > > you may need some additional acpi modules, like ibm_acpi for
> example,
> > > but
> > > > > that depends on your's pc brand. i'm looking around to see if there
> were
> > > > > someone that had problems with santarosa and linux acpi, but for the
> > > moment
> > > > > i couldn't find something useful. try what i've said and see if the
> > > things
> > > > > work. if they work then append the tweak in some script that starts
> at
> > > boot
> > > > > like the top of xdm script and you'll have a functional system. let
> me
> > > know
> > > > > if you were succesful on that.
> > > > >
> > > > >
> > > > > > An additional problem is this:
> > > > > > doing a
> > > > > > $ cat /proc/acpi/thermal_zone/TZ01/temperature
> > > > > > it gives only a:
> > > > > >
> > > > > > temperature:     0C
> > > > > >
> > > > > > My question is:
> > > > > > even if i change the polling frequency, how the fan can start if
> the
> > > > > > temperature gives 0??
> > > > > > Do you know if it's possible to link the fan start with the core
> > > > > > temperature instead of the ACPI thermal zone?
> > > > >
> > > > > probably the fan don't start since  you have it as a module. i've
> > > curently
> > > > > had the same problem which solved by compiling it integrated in the
> > > kernel.
> > > > > the fan in your case should always be on, not always be off....
> > > > >
> > > > > >
> > > > > > Regards,
> > > > > > m
> > > > > >
> > > > > > >
> > > > > > > thats why i told you to do this commanda:
> > > > > > > > echo "2 seconds" >
> > > > > > > /proc/acpi/thermal_zone/TZ01/polling:frequency
> > > > > > > >
> > > > > > >  this enables the polling of your thermal every 2 seconds. this
> > > should
> > > > > be
> > > > > > > enough.
> > > > > > > do you have the other file that i mentioned:
> > > > > > > > /proc/acpi/thermal_zone/TZ01/trip_points ?!
> > > > > > > this sets the trip points for your processor. whitout it you
> > > governor
> > > > > cannot
> > > > > > > understand what to do even if it polls right.
> > > > > > >
> > > > > > > as for the kernel thigs, set these options:
> > > > > > > select processor type: intel core2 instead of normal x86
> > > > > > > CONFIG_X86_SPEEDSTEP_CENTRINO=y instead of m
> > > > > > > CONFIG_ACPI_FAN=y instead of m
> > > > > > > CONFIG_MICROCODE=y instead of m (for what i know cpu micocode is
> > > needed
> > > > > on
> > > > > > > intels)
> > > > > > > CONFIG_K8_NUMA=n instead of y (this should be the amdk8 numa,
> that
> > > you
> > > > > > > should not need. if it's not then let him be)
> > > > > > > CONFIG_X86_MCE_AMD=n instead of y (you don't need amd mce
> features
> > > since
> > > > > > > they are not included into intel cpus)
> > > > > > > CONFIG_NR_CPUS=32 <-- this leaves me a little dazzled: do you
> really
> > > > > have 32
> > > > > > > cpus in your core?! for what i know this sets the real number of
> > > cpus
> > > > > inside
> > > > > > > the kernel, but i might be wrong. so if this is really what i
> think
> > > it
> > > > > is,
> > > > > > > ie the real nr of cpus (not virtual ones) set this to 2 or 4
> based
> > > on
> > > > > your
> > > > > > > cpu cores.
> > > > > > > CONFIG_HOTPLUG_CPU=n instead of y (i don't really think that
> you'll
> > > > > unplug
> > > > > > > your cpu from your laptop when the laptop is still running
> > > considering
> > > > > that
> > > > > > > you don't use multi cpus but a single multicore cpu. the same
> goes
> > > for
> > > > > > > memory hotplug: i don't think that your laptop supports it, so
> just
> > > > > disable
> > > > > > > it.)
> > > > > > > for what i have seen the acpi problems may be due to a failure
> in
> > > > > loading
> > > > > > > the intel speedstep module. if you look into the modules loaded
> > > (lsmod)
> > > > > you
> > > > > > > should not see it. so it's better to insert it directly in the
> > > kernel,
> > > > > since
> > > > > > > it is one of the first modules called (if you use it as a module
> you
> > > > > should
> > > > > > > be loading it with initramdisk before loading acpi to have a
> full
> > > acpi
> > > > > > > configuration).
> > > > > > > try setting these options and recompile and install the new
> kernel
> > > and
> > > > > > > modules and reboot (kexec is not working on my amd turion with
> 64bit
> > > > > enabled
> > > > > > > and so may also be for your core2duo).
> > > > > > >
> > > > > > >  2007/10/10, Marco Calviani < marco.calviani@gmail.com>:
> > > > > > > > Sorry i missed the attachment.
> > > > > > > >
> > > > > > > > regards,
> > > > > > > > m
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > dott. ing. beso
> > > > > > --
> > > > > > gentoo-laptop@gentoo.org mailing list
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > dott. ing. beso
> > > > --
> > > > gentoo-laptop@gentoo.org mailing list
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > dott. ing. beso
> > --
> > gentoo-laptop@gentoo.org mailing list
> >
> >
>
>
>
> --
> dott. ing. beso
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

[parent not found: <d257c3560710131008m6b8e370ala1b5af2416b4f294@mail.gmail.com>]

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
       [not found]                           ` <d257c3560710131008m6b8e370ala1b5af2416b4f294@mail.gmail.com>
@ 2007-10-13 21:46                             ` Marco Calviani
  2007-10-16 19:56                               ` Marco Calviani
  0 siblings, 1 reply; 19+ messages in thread
From: Marco Calviani @ 2007-10-13 21:46 UTC (permalink / raw
  To: gentoo-laptop; +Cc: gentoo-user

Beso,
   yes i'm always staying in powersave mode...... but in any case the
CPU temperature tends to increase. I hope that the ACPI guys will work
on this (hoping i'm not the only one experiencing these problems). The
fans unfortunately are masked to the user in most Acer laptops, and
they are controlled fully by ACPI.

Thanks again,
m

On 10/13/07, Beso <givemesugarr@gmail.com> wrote:
> i think that you'll have to wait a little more and always stay aware when
> using the pc till acpi supports it.
> i'd recommend to stay on powersave when using the processor extensively so
> that you'd not incur in hardware errors and failures. and it the fan is not
> starting try to modify it by command prompt via echo "on" >
> /proc/acpi/fan/..
> this will work at least the thermal doesn't reach the state when it would
> stop the fan, but since you don't have that point and that you cannot read
> temperature starting it via echo "on" should always stay on. you'd have some
> noise maybe, but you'd be sure that the processor would not run overheat.
> and hope that the acpi people would fix that in the near future.
> i'm sorry for not being able to help you more.
> and as an advice for the future: before getting a notebook in the future
> have some surf on the web to see if it's fully supported by linux (acer
> sells linux only notebooks actually but only from taiwan). i had my linux
> notebook not working with linux for 5-6 months and yet i had to change the
> wireless since it wasn't supported after almost 2 years. for what i know
> dell, hp and compaq are quite well supported.
>
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-13 21:46                             ` Marco Calviani
@ 2007-10-16 19:56                               ` Marco Calviani
  0 siblings, 0 replies; 19+ messages in thread
From: Marco Calviani @ 2007-10-16 19:56 UTC (permalink / raw
  To: gentoo-laptop; +Cc: gentoo-user

Hi,
  just for information, i report that i've filed a bug on bugzilla:

http://bugzilla.kernel.org/show_bug.cgi?id=9167

regards,
m

On 10/13/07, Marco Calviani <marco.calviani@gmail.com> wrote:
> Beso,
>    yes i'm always staying in powersave mode...... but in any case the
> CPU temperature tends to increase. I hope that the ACPI guys will work
> on this (hoping i'm not the only one experiencing these problems). The
> fans unfortunately are masked to the user in most Acer laptops, and
> they are controlled fully by ACPI.
>
> Thanks again,
> m
>
> On 10/13/07, Beso <givemesugarr@gmail.com> wrote:
> > i think that you'll have to wait a little more and always stay aware when
> > using the pc till acpi supports it.
> > i'd recommend to stay on powersave when using the processor extensively so
> > that you'd not incur in hardware errors and failures. and it the fan is not
> > starting try to modify it by command prompt via echo "on" >
> > /proc/acpi/fan/..
> > this will work at least the thermal doesn't reach the state when it would
> > stop the fan, but since you don't have that point and that you cannot read
> > temperature starting it via echo "on" should always stay on. you'd have some
> > noise maybe, but you'd be sure that the processor would not run overheat.
> > and hope that the acpi people would fix that in the near future.
> > i'm sorry for not being able to help you more.
> > and as an advice for the future: before getting a notebook in the future
> > have some surf on the web to see if it's fully supported by linux (acer
> > sells linux only notebooks actually but only from taiwan). i had my linux
> > notebook not working with linux for 5-6 months and yet i had to change the
> > wireless since it wasn't supported after almost 2 years. for what i know
> > dell, hp and compaq are quite well supported.
> >
>
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

[parent not found: <d257c3560710091122j501e0d47oa1553da3b1156ebd@mail.gmail.com>]

* [gentoo-user] Re: [gentoo-laptop] Problem with CPU temperature (Santa Rosa CPU)
       [not found] ` <d257c3560710091122j501e0d47oa1553da3b1156ebd@mail.gmail.com>
@ 2007-10-10  7:26   ` Marco Calviani
  2007-10-10  9:43     ` Volker Armin Hemmann
  0 siblings, 1 reply; 19+ messages in thread
From: Marco Calviani @ 2007-10-10  7:26 UTC (permalink / raw
  To: gentoo-laptop; +Cc: gentoo-user

Hi Beso,
    actually i'm getting this error:

cat /proc/acpi/thermal_zone/TZ01/polling_frequency
<polling disabled>

cat /proc/acpi/thermal_zone/TZ01/cooling_mode
<setting not supported>

m

On 10/9/07, Beso <givemesugarr@gmail.com> wrote:
> your thermal doesn't poll.... make it poll like this:
> echo "2 seconds" >
> /proc/acpi/thermal_zone/THRM/polling_frequency
> or wichever thermal zone is in /proc/acpi/thermal_zone. then verify your
> trip points in the same THRM directory but in the file trip_points. you
> should see something like this:
> critical (S5):           105 C
> passive:                 76 C: tc1=3 tc2=1 tsp=150 devices=CPU0
> active[0]:               67 C: devices= FN1
> active[1]:               57 C: devices= FN2
>
> in the eg passive means that your cpu is downclocked since it has passed 76
> degrees C
> active [0] means that your fan is triggered to on
> active[1] means that the fan is not triggered and it is shut down.
> the critical point is when the system shuts down.
> if the polling_frequency tweak doesn't work then you have another problem
> (eg i had to compile the fan and thermal module included in kernel since
> modprobing them would not start the fan). if it works copy the tweak command
> and put it in some init script (i put it at the start of /etc/init.d/xdm so
> that i'm sure it loads after acpi, since that file doesn't exists without
> acpi loaded).
> then try installing kima if you're using kde and add the kima kmenu applet
> to monitor some things. you should be able to see that the processor hardly
> passes 60 degrees while thermal goes high till the passive point and over;
> if you monitor also the cpu load and freq you should be able to see how your
> processors reacts to programs. remember to also install the klaptopdaemon
> since is quite useful in controlling the cpufreq_utils governors and acpi
> settings. try also the laptop_mode-tools and see if they can help you have a
> better use for your disk. the last thing that you can also install is the
> hddtemp for monitoring your disk temperature.
>
> 2007/10/9, Marco Calviani <marco.calviani@gmail.com>:
> >
> > Hi list,
> >    i have a Santa Rosa (Core 2 Duo T7300) Acer AS5720 laptop, and i'm
> > getting problems with the temperature of the CPU. In particular i'm
> > using the coretemp module for determining the core temperature.
> > Normally (using cpufreqd and the "ondemand" governor) the CPU stays at
> > nearly 50C  (which i think is quite high since in windows , using Core
> > Temp it gives about 30C).
> > While compiling this increases up to 95-100C (after which it shuts
> > down). The problem is that the fan is not spinning up at all!
> > What can be the cause of this behaviour? consider that i'm using an up
> > to date system with gentoo-sources-2.6.22-r8.
> >
> > Any help appreciated,
> > Regards,
> > Marco
> > --
> > gentoo-laptop@gentoo.org mailing list
> >
> >
>
>
>
> --
> dott. ing. beso
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

* Re: [gentoo-user] Re: [gentoo-laptop] Problem with CPU temperature (Santa Rosa CPU)
  2007-10-10  7:26   ` [gentoo-user] Re: [gentoo-laptop] " Marco Calviani
@ 2007-10-10  9:43     ` Volker Armin Hemmann
  0 siblings, 0 replies; 19+ messages in thread
From: Volker Armin Hemmann @ 2007-10-10  9:43 UTC (permalink / raw
  To: gentoo-user

On Mittwoch, 10. Oktober 2007, Marco Calviani wrote:
> Hi Beso,
>     actually i'm getting this error:
>
> cat /proc/acpi/thermal_zone/TZ01/polling_frequency
> <polling disabled>
>
> cat /proc/acpi/thermal_zone/TZ01/cooling_mode
> <setting not supported>

hm, you might want to google ;) I really don't know anything about laptops ;)

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 19+ messages in thread

end of thread, other threads:[~2007-10-16 20:13 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-09 17:33 [gentoo-user] Problem with CPU temperature (Santa Rosa CPU) Marco Calviani
2007-10-09 18:44 ` Volker Armin Hemmann
2007-10-10  7:27   ` Marco Calviani
2007-10-10  9:42     ` Volker Armin Hemmann
2007-10-10 10:53       ` Marco Calviani
2007-10-10 10:55         ` Marco Calviani
2007-10-10 14:47           ` Volker Armin Hemmann
     [not found]           ` <d257c3560710100828k5967565cxe07b9b3aa4136351@mail.gmail.com>
2007-10-10 18:12             ` [gentoo-laptop] " Marco Calviani
2007-10-10 18:41               ` Volker Armin Hemmann
2007-10-10 18:51                 ` Marco Calviani
2007-10-10 22:57                   ` Volker Armin Hemmann
     [not found]               ` <d257c3560710101217s14c0207dya59348bffd5deedb@mail.gmail.com>
2007-10-11 10:14                 ` Marco Calviani
     [not found]                   ` <d257c3560710110358o66e7f061k96c569ba39246f49@mail.gmail.com>
2007-10-11 11:43                     ` Marco Calviani
     [not found]                       ` <d257c3560710110537u26ad7a1bq3cda3f0b007eb48a@mail.gmail.com>
2007-10-11 13:33                         ` Marco Calviani
2007-10-13 16:49                         ` Marco Calviani
     [not found]                           ` <d257c3560710131008m6b8e370ala1b5af2416b4f294@mail.gmail.com>
2007-10-13 21:46                             ` Marco Calviani
2007-10-16 19:56                               ` Marco Calviani
     [not found] ` <d257c3560710091122j501e0d47oa1553da3b1156ebd@mail.gmail.com>
2007-10-10  7:26   ` [gentoo-user] Re: [gentoo-laptop] " Marco Calviani
2007-10-10  9:43     ` Volker Armin Hemmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox