Re: monitoring hardware temperatures
On 06.12.2010 18:19, Andriy Gapon wrote: Another possibility is that a driver that should be able to handle your hardwre just doesn't know the particular IDs. pciconf -lv output could shed some light. Attached -- it is a "vanilla" PowerEdge 2900 with just one add-on card -- audio... Thanks! Yours, -mi hos...@pci0:0:0:0: class=0x06 card=0x80868086 chip=0x25c08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000X Chipset Memory Controller Hub' class = bridge subclass = HOST-PCI pc...@pci0:0:2:0: class=0x060400 card=0x chip=0x25e28086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 2' class = bridge subclass = PCI-PCI pc...@pci0:0:3:0: class=0x060400 card=0x chip=0x25e38086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 3' class = bridge subclass = PCI-PCI pc...@pci0:0:4:0: class=0x060400 card=0x chip=0x25e48086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 4' class = bridge subclass = PCI-PCI pci...@pci0:0:5:0: class=0x060400 card=0x chip=0x25e58086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 5' class = bridge subclass = PCI-PCI pci...@pci0:0:6:0: class=0x060400 card=0x chip=0x25f98086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x8 Port 6-7' class = bridge subclass = PCI-PCI pci...@pci0:0:7:0: class=0x060400 card=0x chip=0x25e78086 rev=0x12 hdr=0x01 vendor = 'Intel Corporation' device = '5000 Series Chipset PCIe x4 Port 7' class = bridge subclass = PCI-PCI no...@pci0:0:8:0: class=0x088000 card=0x80868086 chip=0x1a388086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset DMA Engine (5000P)' class = base peripheral hos...@pci0:0:16:0: class=0x06 card=0x01b11028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI hos...@pci0:0:16:1: class=0x06 card=0x01b11028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI hos...@pci0:0:16:2: class=0x06 card=0x01b11028 chip=0x25f08086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Error Reporting Registers' class = bridge subclass = HOST-PCI hos...@pci0:0:17:0: class=0x06 card=0x80868086 chip=0x25f18086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Reserved Registers' class = bridge subclass = HOST-PCI hos...@pci0:0:19:0: class=0x06 card=0x80868086 chip=0x25f38086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset Reserved Registers' class = bridge subclass = HOST-PCI hos...@pci0:0:21:0: class=0x06 card=0x80868086 chip=0x25f58086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset FBD Registers' class = bridge subclass = HOST-PCI hos...@pci0:0:22:0: class=0x06 card=0x80868086 chip=0x25f68086 rev=0x12 hdr=0x00 vendor = 'Intel Corporation' device = '5000 Series Chipset FBD Registers' class = bridge subclass = HOST-PCI pci...@pci0:0:28:0: class=0x060400 card=0x01b11028 chip=0x26908086 rev=0x09 hdr=0x01 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 PCIe Root Port 1' class = bridge subclass = PCI-PCI uh...@pci0:0:29:0: class=0x0c0300 card=0x01b11028 chip=0x26888086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller *1' class = serial bus subclass = USB uh...@pci0:0:29:1: class=0x0c0300 card=0x01b11028 chip=0x26898086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller *2' class = serial bus subclass = USB uh...@pci0:0:29:2: class=0x0c0300 card=0x01b11028 chip=0x268a8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host Controller *3' class = serial bus subclass = USB uh...@pci0:0:29:3: class=0x0c0300 card=0x01b11028 chip=0x268b8086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '631xESB/632xESB/3100 Chipset USB Universal Host
Re: monitoring hardware temperatures
On 06.12.2010 18:02, Andriy Gapon wrote: BTW, you could probably write a simple script employing smbmsg(1) to query the DIMMs based on logic in the sdtemp driver. From OpenBSD's sdtemp man-page, it would seem, the driver uses the iic framework (if that's the right word, khmm...) And on this server I can't get /dev/iic* (nor smb*) to appear despite loading everything I could think of (even the viapm): 31 0x80c23000 d22 iic.ko 44 0x80c24000 10e7 iicbus.ko 51 0x80c26000 f16 iicsmb.ko 65 0x80c27000 819 smbus.ko 71 0x80c28000 c02 smb.ko 83 0x80c29000 114f iicbb.ko 91 0x80c2b000 1df3 ichsmb.ko 101 0x80c2d000 1aed intpm.ko 111 0x80c2f000 e38 pcf.ko 121 0x80c3 b83 lpbb.ko 131 0x80c31000 368b ppbus.ko 141 0x80c35000 262a viapm.ko Could it be, that the motherboard simply does not have the iic-circuitry and that some other method has to be used? Thanks! Yours, -mi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: monitoring hardware temperatures
On 06.12.2010 14:51, Michael Fuckner wrote: did you try to read the data via IPMI? kldload ipmi;ipmitool sdr Interestingly, I was doing just that, when your e-mail arrived... ipmitool was impressive enough and I'm building openipmi to take a look at that too. I don't see information on each DIMM (yet?), but other information is quite useful... One of the fans, for example, was listed as "cr" (rather than "ok") -- which was, apparently, causing all other fans to run at maximum speed (*very* noisy fans in poweredge 2900). I reset it (by pulling it out and back again), and now the box is quieting back down... The sensors-patches did not add any new entries under hw.sensors hierarchy :( The coretemp(4) stopped functioning, unfortunately... Whereas before, when I simply kldload-ed it, it was reporting reasonable temperatures, now that I have the sensors-patch merged in, I see nonsense like: hw.sensors.cpu0.temp0: -1282,97 degC hw.sensors.cpu1.temp0: -1272,97 degC hw.sensors.cpu2.temp0: -1282,97 degC hw.sensors.cpu3.temp0: -1262,97 degC Seems like some kind of calibration issue -- the numbers differ from each other and change with time... I think, I'll back the patch out as it did not give me any new information -- the it- and lm-devices aren't found on this box :-( Anyway, sdtemp(4) -- or equivalent -- is something, I'd like to have... Thanks! Yours, -mi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
monitoring hardware temperatures
Hello! I have a server (Dell Poweredge 2900), that's loaded with sensors. While it was in Windows-mode, a utility was able to tell me not only the temperature of each CPU-core, but also that of every DIMM!.. One of them was running far hotter than others, and I'd like to continue keeping an eye on it now that the box run FreeBSD. In FreeBSD there is coretemp(4), which is nice, but nothing else... There is no hw.acpi.thermal hierarchy either on this box... Yet, the box has 6 fans, two power-supplies, plus DIMMs -- all of them with sensors, that I can't read... It seems, in 2007, there was an attempt to introduce OpenBSD's sensor-framework: http://kerneltrap.org/OpenBSD/BSDCan_2008_Hardware_Sensors_Framework but it was backed-out after being declared a "pile of crap" and "festering junkpile" by our most mirthful contributor: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=193129+0+archive/2007/cvs-all/20071021.cvs-all "until a proper architectural solution has been found". Has that happened in the three years, that passed since that lovely discussion? Or are we still waiting for someone to design and implement it not merely "adequately", but "perfectly"? If the three other BSD-cousins have had this for a while (NetBSD -- for 10 years, apparently), continuing to insist on some future perfection seems wrong -- we should have this "adequate but imperfect" method if only for cross-BSD compatibility. Is there, perhaps, a set of patches still secretly maintained by some die-hard? I'd love to try it here, and will be very thankful, if it gives me the monitoring, that I can not obtain otherwise... Thanks! Yours, -mi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
passwordless login not working in KDM
Hello! The instructions at: http://freebsd.kde.org/faq.php#HowdoIenablepasswordlessconvenienceloginsinKDMIcheckedthecheckboxintheLoginManagerControlbutKDMwontlogmein seem perfectly clear and, I believe, I followed them correctly: m...@corbulon:~ (1004) ls -l /etc/pam.d/kde* -rw-r--r-- 1 root wheel 458 Dec 2 2007 /etc/pam.d/kde -rw-r--r-- 2 root wheel 459 Dec 29 2007 /etc/pam.d/kde-np m...@corbulon:~ (1005) diff -U2 /etc/pam.d/kde* --- /etc/pam.d/kde 2007-12-02 12:12:44.0 -0500 +++ /etc/pam.d/kde-np 2007-12-29 17:51:31.0 -0500 @@ -8,5 +8,5 @@ #auth sufficient pam_krb5.so no_warn try_first_pass #auth sufficient pam_ssh.so no_warn try_first_pass -auth requiredpam_unix.so no_warn try_first_pass +#auth requiredpam_unix.so no_warn try_first_pass # account Unfortunately, the password-less logins are still rejected for the two users, who are listed: m...@corbulon:~ (1006) grep NoPass /opt/share/config/kdm/kdmrc NoPassEnable=true NoPassUsers=mi,tulik Please, advise... Thanks! -mi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
how to suspend/wake-up a FreeBSD machine?
Hello! I managed to suspend some of my computers a few times (using either ``zzz'' or ``acpiconf -s 1''), but I could never successfully wake the system up after this, requiring a full reboot. What's the proper procedure? I tried the power-button (no effect) and hitting random keyboard keys (no effect). How is it supposed to work? Thanks! -mi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
tail does not exit
Why does not the script below actually ever exit?
#!/bin/sh
if tail -f /var/log/messages | awk '{print "Exiting"; exit 0}'
then
echo Exited
else
echo Failed
fi
exit 0
Awk exits as advertised, but tail stays around -- even though its
stdout is closed... Why?
Thanks!
-mi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
xfontsel would not start, xterm crashes
Hello! I upgraded X-server to xorg-6.9.0 a month ago. Since then, xfontsel would not start and xterm crashes when I try to bring up any of its three menus by pressing any of the mouse buttons while holding Ctrl. The messages are always the same: Warning: Unable to load any usable ISO8859 font Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Error: Aborting: no font found What is it missing? Thanks! -mi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to print in duplex mode?
неділя 05 березень 2006 02:55, Malcolm Kay, Ви написали: > Duplex mode is usually controlled by some printer/manufacturer > specific job control wrapper around the postscript such as HP's > JPL. Is it? I thought, it can be controlled by the PostScript being printed itself... pstops(1) even has an example for duplex printing, but I can't make sense of it. :-( = > Would someone have a ready example: = > = > pstops 'MagickSpell' input.ps duplex.ps = = How is this mystical command line constructed? input.ps is, what I want printed. duplex.ps is the desired output -- the equivalent of input.ps in duplex mode. Thanks! -mi P.S. You are right -- pstops is, from the psutils suit, nor from enscript. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: read vs. mmap (or io vs. page faults)
вівторок 22 червень 2004 23:27, Peter Wemm, Ви написали: = On Monday 21 June 2004 10:08 pm, Mikhail Teterin wrote: = The amount of "work" for the kernel to do a read() and a high-speed = memory copy is much less than the cost of taking a page fault, running = a whole bunch of really really nasty code in the vm system, repairing = the damage from the page fault, updating the process paging state and = restarting the instruction. Does the code _have_ to be "really really nasty", or it just _happened_ to be that way for historical reasons -- like this being a very complex issue, and, once it worked, no one really wanted to mess with it? = The numbers you're posting are a simple reflection of the fact that = the read syscall path has fewer (and less expensive) instructions to = execute compared to the mmap fault paths. Why, then, is the total number of CPU seconds (kernel+user) favorable towards mmap on CPU bound machines and about the same on IO bound? May be, because all that CPU work, you are describing, is also much faster on the modern CPUs? = Some operating systems implemented read(2) as an internal in-kernel = mmap/fault/copy/unmap. Naturally, that made mmap look fast compared to = read, at the time. But that isn't how it is implemented in FreeBSD. = mmap is more valuable as a programmer convenience these days. I figured :-( It is very convenient. As such, it should be wider used (because it leads to cleaner code), but that wouldn't come until it also offers the performance comparable to the less clean method(s)... Yours, -mi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
