With kernel 2.6.35 I get wrong readings on lm_sensors. They are about 20C off than the real values (e.g. if the CPU is at 50C, lm_sensors will show 70C). If I boot with any other kernel (like 2.6.32) I get the correct values. I'm using the 'coretemp' module on an Acer 7720 laptop. My distro is 64-bit Arch Linux.
View 2 RepliesI noticed that sensors reports some strange numbers regarding my PSU:
[Code]...
I have not change any sensors configuration for 3 years now (from the day that I makde my PC), and I have not seen those numbers before. So, why are the maximum levels so low? Why is the VBat and V5SB readings so messed up? Can I do something to correct it? If not, is it a problem of the PSU?
I have a system running openSUSE 11.2 with Desktop and XEN kernel, as well as Windows 7 (not by choice though...). I have noticed a strange time issue, with Windows 7 and the desktop kernel the time is correct (like for example now: 1:32 PM) but in the XEN kernel it is ahead several hours (6:32 PM). If it was an issue between openSUSE and windows then I would think that it is a problem with the system clock but I don't know what would cause a time issue between kernels like that.
View 6 Replies View RelatedI am using Linux as my OS and using TOP command to measure the system performance. From the readings using the TOP, I have observed the following
(1) The used memory increase significantly from 7% to 99% over sometimes? Is there a sign of memory leak? Does OS play a part in used memory? Will system performance be affected? Will system crash due to 99% used memory?
(2) What is the difference between Memory Buffers and Cached?
(3) From the readings, it was observed that Buffers readings decrease, whereas Cached readings increase over time.
(5) Should TOP be used to take readings for system performance (memory & CPU usage)? What is the recommended method to take readings?
Whereas, my applications only consume a bit of memory and CPU.
When I installed fedora 11 the other day using the live CD it installed the i586 kernel and not the i686, despite the fact that smolt seems to know that that the hardware is i686 (well, actually it's x86, but I'm not going to argue because I forgot to get that one...). Why would it install the i586 one though? (uname -r 2.6.29.6-213.fc11.i586) But more importantly, are there any specific issues which this version can cause that I should be aware of? I can't really be bothered to change it at the moment if there is no real issue with it but I'm not too sure what difference it makes? Is it slower? It seems to know that I have a quad-core processor and seems to use them fine.
View 10 Replies View RelatedJust installed Fedora 12 on my Dell Precision M4400 and I'm trying to install the Broadcom wireless driver. When I try to compile the driver, I get:make: *** /lib/modules/2.6.31.5-127.fc12.i686/build: No such file or
directory. Stop.So I followed the link and /lib/modules/2.6.31.5-127.fc12.i686/build is a soft link:lrwxrwxrwx. 1 root root 47 2009-11-09 14:17 build -> ../../../usr/src/kernels/2.6.31.5-127.fc12.i686But in /usr/src/kernels all I see is:
total 12
drwxr-xr-x. 3 root root 4096 2010-01-09 11:56 .
drwxr-xr-x. 4 root root 4096 2009-11-09 14:10 ..
[code]....
It points to the old Fedora kernel, and needs to be directed to the pre-installed kernel. What will the new menu entry be after it loads?
View 1 Replies View RelatedMy distro is ClearOS, which is RHEL so I assume this is the right place.I moved my sytem from an old PATA-drive to a bigger SATA. ClearOS uses LVM for the root directory and the swap directory, so this VolumeGroup was moved using lv-commands. I left the old hda drive in for the time being and hda also remained the BIOS start up disk. /boot is at hda2.Now, clearly there are 2 VolGroup00/ LogVol00 's: on hda and sda.
Eventually I wanted to unload my hda. I copied /boot from the hda disk to sda, changed (hd0,1) to (hd0,0) as /boot is in different locations, later found out that I needed to do the same for the location of the splash image and did that as well, but I don't get access to my new VolGroup.I did an /sbin/mkinitrd and a grub-install on the new sda but no luck. I have seen various error messages. The latter one is that grub loader 1.5 is active, giving me a grub prompt.
I'm running Scientific Linux 5.5 (equivalent to CentOS 5.5), and over the past two weeks, I have had a problem with my root partition filling up, preventing anyone from logging into the server.After searching for large files, and finding none, I was mystified when du told me that the root partition had only 660 MB of disk space used, whilst df showed it full. The problem was this: the /var/crash directory had been filled up by an 8GB crash file. Now, I'm a 'proper' sysadmin and make sure that /var has its own mount point, so the crash should not have touched the root partition at all. Except it did - instead of writing to /var/crash on /dev/mapper/VolGroup00-LogVol04 which is mounted as /var, it wrote the file to /dev/md0 directly, so when all the file systems were mounted, those files were hidden under the mounted /var.
View 4 Replies View RelatedI have two HP Quard core high end server.
OS : Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Kernel : kernel-2.6.18-92.el5
From last couple of days I found entry in dmesg:
###########################################
Oct 11 15:03:46 kernel: schedule_timeout: wrong timeout value ffefda64 from c05a784e
Oct 11 15:03:46 last message repeated 2 times
[code]...
I just installed Slackware 13.1 x86 on a new laptop (you probably remember me from my audio post). I am having one other issue. My root file system is formatted as EXT4. When my computer boots, it tries to mount it as EXT3 then EXT2, fails both types and then tries EXT4. Here are the messages.
Code:
EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT4-fs (sda2): mounted filesystem with ordered data mode
So, eventually / is mounted correctly, but I think this is slowing down my boot time. Does anyone know how to fix this.
I am having issues trying to compile the alsa-linuxtant module and I am getting errors about not being able to find some files and the source needing to be reconfigured. Anyway the developers told me to try compiling on a pristine source to see if I could compile that way. When I went looking at kernel.org I did not find a 2.6.32-5 version. So I did some checking and to see just what version I have.
$ uname -r
2.6.32-5-amd64
$ dpkg --list | grep linux-image
ii linux-image-2.6-amd 64 2.6.32+27 Linux 2.6 for 64-bit PCs (meta-package)
ii linux-image-2.6.26-2-amd64 2.6.26-24 Linux 2.6.26 image on AMD64
ii linux-image-2.6.32-5-amd64 2.6.32-15 Linux 2.6.32 for 64-bit PCs
So the actual package that is installed is 2.6.32-15 but uname -r reports 2.6.32-5 as the kernel version.
Grub use to open an old kernel I tried to edit /boot/grub/menu.lst to open the one I wanted. The edit gets saved but it still opens in the wrong kernel. i.e when edit menu.lst it has no effect. I have tried running sudo grub-update. I've read piles of forum entries to no avail. I am running Jaunty.
View 7 Replies View RelatedI'm running CentOS 5.4 on an Atom 230-based MSI MS-7418 motherboard. I'd like to monitor this host' CPU temperature as well as the HD's temperature, but can't get lm_sensors to work:Code: # uname -aLinux msi.workgroup 2.6.18-164.9.1.el5 #1 SMP Tue Dec 15 21:04:57 EST 2009 i686 i686 i386 GNU/Linux
# cat /etc/issue
CentOS release 5.4 (Final)
Kernel
[code]....
Trying to find the CPU temperature, I found this lm_sensors is what I need..I do this;
wget http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.2.0.tar.bz2
bzip2 -dv lm_sensors-3.2.0.tar.bz2
tar xvf lm_sensors-3.2.0.tar[code].....
Ok.. when it comes to drivers and kernels...I have a rented server - so I do not have local access to it, and I do not have a KVM or remote console to it.
This is the current kernel that came with it:
Linux version 2.6.26-2-686 (Debian 2.6.26-22lenny1) (dannf@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed May 12 21:56:10 UTC 2010 the network card module according to support is r8169 (when i do lsmod i see r8169 listed), lspci lists it as: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03).
So.. where everything went bad is after I installed grsecurity kernel via apt-get install linux-image-grsec. It installed and rebooted successfully, but without the right network card module. The datacentre support had to reboot it to the original kernel for me.
So - i don't know how to update the network card drivers of the grsecurity kernel? It has to be perfect (I can't do trial and error) because each attempt that fails, I have to engage the datacentre support to reboot the system back into the original kernel. Apparently the new kernel detected it as a gigabit fibre card.
I am an openSuSE user for many years. My current installation is openSuSE 11.2. However, my first was SuSE 6.4 and I have been _constantly_ upgrading since then until reaching the current openSuSE 11.2. The technical issue I have been facing lately is with the kernel version of my current system: although it should be 2.6.31.5-0.1-desktop, as this is the one I have chosen via the online update mechanism and the yast2 system boot-loader procedure, grub shows it as preselected, the boot procedure in the end greets me mentioning this very kernel version, _but_ when I issue the command: uname -a in a command prompt, I am informed of using linux kernel version: 2.6.18.2-34-default #1 SMP PREEMPT
I am really quite puzzled, since I _cannot_ find any such vmlinuz file under /boot/ ! Could it be that my system properly runs with the expected kernel version, but uname mistakes it with a different one? Is there a way to determine the actual version of the linux kernel that my system currently runs with? If it's a problem with uname, have you got any suggestions that could potentially shed some light towards the origin/cause of the reported issue?
I did apply the updates on 11.1 32bit and upgraded the kernel from 2.6.27.45 to 2.6.27.56.
Now:
Code:
> uname -a
Linux myhost 2.6.27.45-0.1-default #1 SMP 2010-12-01 16:57:58 +0100 i686 i686 i386 GNU/Linux
but:
Code:
> cat /proc/version
Linux version 2.6.27.56-0.1-pae (geeko@buildhost) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP 2010-12-01 16:57:58 +0100
I managed to get lm-sensors working it has no initialization at bootime:Quote:Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yCopy prog/init/lm_sensors.init to /etc/init.d/lm_sensorsfor initialization at boot time.You should now start the lm_sensors service to load the requiredkernel modules.I've already copied 'prog/init/lm_sensors.init' to '/etc/init.d/lm_sensors' but it doesn't work. I still have i manutally have to load 'coretemp' to be able to have a temperature output from the command "sensors"
View 5 Replies View Relatedhow should I read below output of lm_sensors ? Im interested ONLY with temp1 and temp2.I suspect that temp1 presents motherboard chipset temp and temp2 CPU temp. I hope this is like this... but I have no 100% assurance.
Code:
~# /usr/local/bin/sensors
w83697hf-isa-0290
[code]....
I have a problem with monitoring CPU temperature on x86_64 OpenSUSE 11.3. It returns the following:
it8720-isa-0290
Adapter: ISA adapter
in0: +1.18 V (min = +0.00 V, max = +4.08 V)
in1: +1.58 V (min = +0.00 V, max = +4.08 V)
[code].....
I use a Core i5 750 on a Gigabyte GA-P55A-UD3 motherboard. I could not find anything useful neither by googling, nor by using the forum search.
I am operating openSUSE 11.2 x86_64 KDE4.3 after installing sensors then adding
Code:
acpi_enforce_resources=no
to my optional kernel parameters and running
[code]....
I cannot install lm_sensors-2.5.5-3.i386.rpm nor lm_sensors-2.5.5-6.i386.rpm on RH 7.1.
The files complained by "failed dependencies" are present on my computer.
Why it fail to install?
Please help to fix the problem. code...
We are trying to implement a firewall as kernel module through netfilter hooking (in C). In the following code we are allowing only TCP traffic. Source port number and destination port number are printed for every TCP packet. On execution, this code prints wrong port numbers. This is the first time we are using skb_transport_header function for accessing tcp headers.
We verified port numbers being printed by firewall through NFS traffic. On the same machine where firewall is running, we hosted an NFS server. An NFS client (from a different system) puts a file in exported mount. Firewall is able to capture packets for this file transfer but port numbers printed are wrong. It prints '69' for source portnumber (whereas ethereal capture shows it as 790) and prints '553231' for destination port (whereas for nfs version 4 it has to be 2049).
[Code]....
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
lm_sensors failed after configuration by sensors-detect.
server3:~ # rclm_sensors start
Starting up sensors: failed
/etc/sysconfig/lm_sensors
[code]....
I recently built a cluster with Centos 5.3 and nodes that used different versions of the w83627ehf sensors chip. On some nodes sensors-detect detected the chip:
Found `Winbond W83627DHG Super IO Sensors' Success!(address 0x290, driver `w83627ehf')
But starting lm_sensors returned the error: Starting lm_sensors: No sensors found!
On other nodes sensors-detect did not detect the chip at all: Found unknown chip with ID 0xb073(logical device B has address 0x290, could be sensors)
[Code]....
Basically, About 50% of the time, the system boots and sets the console resolution to something strange, and the console renders in a small box in the top-left hand corner of my screen. This causes problems not only with the display of the console, but with the display of X as well.
I have an Intel GL40 chipset on this laptop, with an integrated GMA4500 GPU. I am using the latest stable Intel video drivers (2.10.0-1), and have tried using the git drivers. In addition, the problem has been occuring since December, when I install Arch linux on this machine, I have just now had the time to address it. So basically, the issue has persisted with all driver versions since mid-December to the latest releases.
In addition, I have tried using several kernels, including:
But the problem persists with each.
I wish I could give you relevant diagnostic information for this issue, but if I had any idea where to start...
I will gladly post any information necessary. I was going to post a copy of everything.log for a successful and unsuccesful boot, but unfortunately they put me over the posing limit by about 100,000 characters each.
I guess, on second thought, that my Intel video driver really wouldn't have anything to do with my console, now would they?
I'm running CentOS 5.4 on an Atom 230-based MSI MS-7418 motherboard. I'd like to monitor this host' CPU temperature as well as the HD's temperature, but can't get lm_sensors to work:
Code:
# uname -a
Linux msi.workgroup 2.6.18-164.9.1.el5 #1 SMP Tue Dec 15 21:04:57 EST 2009 i686 i686 i386 GNU/Linux
[code]....
I'm booting kernel 2.6.34.7-0.4 (opensuse 11.3), but "uname -r" says version:2.6.34.7-0.3-default. What's wrong?
View 1 Replies View Related