Upgraded my old Debian box to Kernel 2.6.32, but missing sensors datas and can't compile the latest stable NVIDIA driver.
in [Linux Hardware]
|
Prev: Upgraded my old Debian box to Kernel 2.6.32, but missing sensors datas and can't compile the latest stable NVIDIA driver.
Next: HDD problems causing Kernel panics in Linux/Debian?
From: Ant on 5 Mar 2010 11:20 On 3/5/2010 7:57 AM PT, Anton Ertl typed: >> I just rebooted my old Debian box to start using its new Kernel 2.6.32 >> from 2.6.30, but I noticed two broken issues so far: >> >> 1. Sensors no longer show other kinds of information/data like voltages: > > In my experience lm-sensors stuff usually breaks when switching to a > new kernel. I then have to check and change various sensor-related > configuration files. Right, hence why I reran sensors-detect command but it only gave me only one line to put in /etc/modules. However, where are the other ones it used to tell me? I wonder if it is related to my Kernel compilation issue. >> 2. I can't seem to compile the latest stable NVIDIA driver after >> upgrading to Kernel 2.6.32 in my old Debian box with a GeForce 8800 GT >> video card (512 MB of RAM). What am I missing? > > Isn't that the expected behaviour from proprietary drivers? Isn't > there a Debian package for the proprietary Nvidia driver? Have you > tried that? I want to use the latest one from NVIDIA. :( -- "Thanks for giving me the courage to eat all those ants." --unknown /\___/\ / /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| | Ant's Quality Foraged Links: http://aqfl.net \ _ / Nuke ANT from e-mail address: philpi(a)earthlink.netANT ( ) or ANTant(a)zimage.com Ant is currently not listening to any songs on his home computer.
From: Darren Salt on 5 Mar 2010 15:08 I demand that Ant may or may not have written... > I just rebooted my old Debian box to start using its new Kernel 2.6.32 > from 2.6.30, but I noticed two broken issues so far: > 1. Sensors no longer show other kinds of information/data like voltages: > # sensors > acpitz-virtual-0 > Adapter: Virtual device > temp1: +21.8°C (crit = +96.8°C) (Hmm. Not using UTF-8?) > k8temp-pci-00c3 > Adapter: PCI adapter > Core0 Temp: +32.0°C > Core1 Temp: +18.0°C Booting with acpi_enforce_resources=lax should help. This may cause problems if the BIOS also accesses the "missing" hardware. (I'm currently using this option without problems.) > 2. I can't seem to compile the latest stable NVIDIA driver after upgrading > to Kernel 2.6.32 in my old Debian box with a GeForce 8800 GT video card > (512 MB of RAM). What am I missing? It used to work in earlier Kernels like > 2.6.30. I noticed Debian changed stuff around with its 2.6.32. Here are the > logs: [snip] This looks significant: > The compiler used to compile the kernel (gcc 4.3) does not exactly > match the current compiler (gcc 4.4). The Linux 2.6 kernel module > loader rejects kernel modules built with a version of gcc that does not > exactly match that of the compiler used to build the running kernel. [snip] -- | Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon | using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army | + This comment has been censored. The luck that is ordained for you will be coveted by others.
From: ANTant on 5 Mar 2010 16:27 >> I just rebooted my old Debian box to start using its new Kernel 2.6.32 >> from 2.6.30, but I noticed two broken issues so far: > >> 1. Sensors no longer show other kinds of information/data like voltages: >> # sensors >> acpitz-virtual-0 >> Adapter: Virtual device >> temp1: +21.8°C (crit = +96.8°C) > > (Hmm. Not using UTF-8?) Yeah via PuTTY. :( >> k8temp-pci-00c3 >> Adapter: PCI adapter >> Core0 Temp: +32.0°C >> Core1 Temp: +18.0°C > > Booting with acpi_enforce_resources=lax should help. This may cause problems > if the BIOS also accesses the "missing" hardware. (I'm currently using this > option without problems.) Where do I add/set this? >> 2. I can't seem to compile the latest stable NVIDIA driver after upgrading >> to Kernel 2.6.32 in my old Debian box with a GeForce 8800 GT video card >> (512 MB of RAM). What am I missing? It used to work in earlier Kernels like >> 2.6.30. I noticed Debian changed stuff around with its 2.6.32. Here are the >> logs: > [snip] > > This looks significant: > >> The compiler used to compile the kernel (gcc 4.3) does not exactly >> match the current compiler (gcc 4.4). The Linux 2.6 kernel module >> loader rejects kernel modules built with a version of gcc that does not >> exactly match that of the compiler used to build the running kernel. > > [snip] Actually, I got it resolved. I was missing linux-headers-2.6.32-trunk-common package. I thought I followed up on this earlier. I guess it didn't go through, but then I was a in a hurry to work. :( -- "We are anthill men upon an anthill world." --Ray Bradbury /\___/\ / /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site) | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Please remove ANT if replying by e-mail. ( )
From: ANTant on 5 Mar 2010 17:28 More details: I am using a MSI K8N NEO4-F (MS-7125) motherboard. You can see http://alpha.zimage.com/~ant/antfarm/about/computers.txt for the detailed hardware setup. Kernel 2.6.30 and earlier used to say something like this: $ sensors -f k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: +80.6???F .... Adapter: ISA adapter VCore: +1.12 V (min = +2.11 V, max = +2.48 V) +3.3V: +3.28 V (min = +1.46 V, max = +0.21 V) +5V: +4.97 V (min = +0.89 V, max = +0.22 V) +12V: +11.43 V (min = +0.24 V, max = +9.67 V) -12V: +0.72 V (min = -5.37 V, max = +0.63 V) -5V: +5.10 V (min = +1.18 V, max = -7.66 V) V5SB: +5.59 V (min = +0.13 V, max = +0.48 V) VBat: +1.55 V (min = +2.24 V, max = +3.46 V) fan1: 2360 RPM (min = 1622 RPM, div = 4) fan2: 2376 RPM (min = 1985 RPM, div = 4) temp1: +82.4???F (high = +201.2�F, hyst = +221.0�F) sensor = thermistor temp2: +86.0???F (high = +176.0�F, hyst = +167.0�F) sensor = thermistor beep_enable:enabled I think this issue is normal after looking at the FAQ and saw http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 which look like my issue and matches dmesg: http://pastie.org/856424 ... I am scared to use the lax method since it is not recommended. Is there another way to show the datas safely? Or do I have to use this trick, live without them, or downgrade back to 2.6.30 Kernel? Thank you in advance. :) In alt.os.linux.debian Ant <ant(a)zimage.comant> wrote: > > I just rebooted my old Debian box to start using its new Kernel 2.6.32 > from 2.6.30, but I noticed two broken issues so far: > > 1. Sensors no longer show other kinds of information/data like voltages: > # sensors > acpitz-virtual-0 > Adapter: Virtual device > temp1: +21.8°C (crit = +96.8°C) > > k8temp-pci-00c3 > Adapter: PCI adapter > Core0 Temp: +32.0°C > Core1 Temp: +18.0°C > > # cat /etc/modules > # /etc/modules: kernel modules to load at boot time. > # > # This file contains the names of kernel modules that should be loaded > # at boot time, one per line. Lines beginning with "#" are ignored. > > loop > > #Generated by sensors-detect for MSI K8N NEO4-F (MS-7125; v1.0) > motherboard (NVIDIA nForce4) > w83627ehf > k8temp > usbhid > > #FUSE for TrueCrypt > fuse > > # Generated by sensors-detect on Sat Dec 5 00:43:06 2009 > # Chip drivers for ASUS K8V SE mobo. > #w83627hf > > > I tried rerunning sensors-detect: > # sensors-detect > # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100) > # System: MICRO-STAR INTERNATIONAL CO., LTD MS-7125 > > This program will help you determine which kernel modules you need > to load to use lm_sensors most effectively. It is generally safe > and recommended to accept the default answers to all questions, > unless you know what you're doing. > > Some south bridges, CPUs or memory controllers contain embedded sensors. > Do you want to scan for them? This is totally safe. (YES/no): > Silicon Integrated Systems SIS5595... No > VIA VT82C686 Integrated Sensors... No > VIA VT8231 Integrated Sensors... No > AMD K8 thermal sensors... Success! > (driver `k8temp') > AMD Family 10h thermal sensors... No > AMD Family 11h thermal sensors... No > Intel Core family thermal sensor... No > Intel Atom thermal sensor... No > Intel AMB FB-DIMM thermal sensor... No > VIA C7 thermal sensor... No > VIA Nano thermal sensor... No > > Some Super I/O chips contain embedded sensors. We have to write to > standard I/O ports to probe them. This is usually safe. > Do you want to scan for Super I/O sensors? (YES/no): > Probing for Super-I/O at 0x2e/0x2f > Trying family `National Semiconductor'... No > Trying family `SMSC'... No > Trying family `VIA/Winbond/Nuvoton/Fintek'... No > Trying family `ITE'... No > Probing for Super-I/O at 0x4e/0x4f > Trying family `National Semiconductor'... No > Trying family `SMSC'... No > Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes > Found `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' Success! > (address 0x290, driver `w83627ehf') > > Some systems (mainly servers) implement IPMI, a set of common interfaces > through which system health data may be retrieved, amongst other things. > We first try to get the information from SMBIOS. If we don't find it > there, we have to read from arbitrary I/O ports to probe for such > interfaces. This is normally safe. Do you want to scan for IPMI > interfaces? (YES/no): > Probing for `IPMI BMC KCS' at 0xca0... No > Probing for `IPMI BMC SMIC' at 0xca8... No > > Some hardware monitoring chips are accessible through the ISA I/O ports. > We have to write to arbitrary I/O ports to probe them. This is usually > safe though. Yes, you do have ISA I/O ports even if you do not have any > ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): > > Lastly, we can probe the I2C/SMBus adapters for connected hardware > monitoring devices. This is the most risky part, and while it works > reasonably well on most systems, it has been reported to cause trouble > on some systems. > Do you want to probe the I2C/SMBus adapters now? (YES/no): > Using driver `i2c-nforce2' for device 0000:00:01.1: nVidia Corporation > nForce4 SMBus (MCP) > WARNING: All config files need .conf: > /etc/modprobe.d/blacklist-bluetooth, it will be ignored in a future release. > Module i2c-dev loaded successfully. > > Next adapter: SMBus nForce2 adapter at 4c00 (i2c-0) > Do you want to scan it? (yes/NO/selectively): > > Next adapter: SMBus nForce2 adapter at 4c40 (i2c-1) > Do you want to scan it? (yes/NO/selectively): > > Now follows a summary of the probes I have just done. > Just press ENTER to continue: > > Driver `w83627ehf': > * ISA bus, address 0x290 > Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9) > > Driver `k8temp' (autoloaded): > * Chip `AMD K8 thermal sensors' (confidence: 9) > > To load everything that is needed, add this to /etc/modules: > #----cut here---- > # Chip drivers > w83627ehf > #----cut here---- > If you have some drivers built into your kernel, the list above will > contain too many modules. Skip the appropriate ones! > > Do you want to add these lines automatically to /etc/modules? (yes/NO)n > > Unloading i2c-dev... OK > > > I checked sensors results and same thing. What happened? Did I miss > something? -- "We are anthill men upon an anthill world." --Ray Bradbury /\___/\ / /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site) | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Please remove ANT if replying by e-mail. ( )
From: Darren Salt on 7 Mar 2010 09:56
I demand that ANTant(a)zimage.com may or may not have written... >>> I just rebooted my old Debian box to start using its new Kernel 2.6.32 >>> from 2.6.30, but I noticed two broken issues so far: >>> 1. Sensors no longer show other kinds of information/data like voltages: [snip] >> Booting with acpi_enforce_resources=lax should help. This may cause >> problems if the BIOS also accesses the "missing" hardware. (I'm currently >> using this option without problems.) > Where do I add/set this? Kernel command line; so at boot, or in your boot loader configuration. [snip] -- | Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon | using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army | + http://www.xine-project.org/ Never let facts enter an argument. |