similar to: compaq v2000 working with correct boot options and compaq r4000 still SLOWWW

Jerry Geis <geisj at pagestation.com <http://lists.centos.org/mailman/listinfo/centos>> wrote: >/ So I thought I would try those same options on my r4000 />/ laptop. they had no effect.... This AMD turion 64 4000+ />/ rating laptop is still running SLOWWW... />/ /proc/cpuinfo has the cpu Mhz running at 2393 / Yes, the 4000+ is 2.4GHz. >/ below is my dmesg output for

After a couple hours last night.... doing a "killall -SIGUSR1 cpuspeed" bumps up the /proc/cpuinfo information for cpu mhz to 2393 Mhz. I did notice a little increase after that. However, the machine is still sluggish. I did a "hdparm -c 1 /dev/hda" but really did not notice any difference. I tried to download fglrx64_6_8_0_8.16.20-1.x86_64.rpm from ati (also 8.20.8) and get

Hi I have a compaq R4000 with the 2.4GIG AMD 64 bit. 4000+ rated. proc cpuinfo reports cpu Mhz as 997.481 Do I have to run the 64 bit version to have things run correctly? I just have the normal 4.2 loaded at this time. The laptop seems slow for 4000+ as reflected by the cpu Mhz also. Any thoughts on running the 32 bit version of 4.2 vs the 64 bit version of 4.2? Jerry

Hello, Using kernel: 2.6.18-92.1.13.el5.centos.plus the cpu throttling works as desired (see 2 traces below) ------------- trace snips -------------- dmesg | grep -i pow ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0x3fff9b40 powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ processors ( 2 cpu cores) (version 2.20.00) powernow-k8: 0 :

Sorry to have so many questions but I seem to have quite a few mini problems with my first Xen setup. My xen server works fine with Powernow on the standard Kernel but with the Xen kernel it fails. Does anyone know why? Details below. With Standard Kernel powernow-k8: Found 2 Quad-Core AMD Opteron(tm) Processor 8350 processors (8 cpu cores) (version 2.20.00) powernow-k8: 0 : fid 0x0

I have a single VM (of 11) that has a recurring problem. This image has moved from machine to machine, with the problem following it. This image has been rebuilt from scratch, and the problem recurred. It would appear that there is something in the behaviour of this VM which causes it to crash and causes Xend to become unhappy. The problem presents as: Domain crashes, becomes zombie. xm

Gents, I first installed the 32 bit version (as you might have read) of centos 4.2, after downloading x86_64 the install process/progress is about the same. going VERY slow... The screen for formatting the partitions took a LONG time (3 partitions 10 GIG, 2 GIG swap and 50 GIG). While on that screen and moving the mouse it lagged big time and could not keep up. Anyway just reporting that so far

I had my eye on the Tyan dual-Opteron mobos for awhile. I tried to find a posting *anywhere* sharing experiences with these boards under Linux. No such luck. So placing myself under the heading "Where Angles Fear to Tread," I went ahead and built a system anyway. Here's what I've learned. The specs: Tyan Thunder K8SE S2892, BIOS 1.01 2x Opteron 270, 2Ghz Dual-Core, retail

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3-3 Severity: normal Forwarded: http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789 Dear Debian Xen Team, after an upgrade from Squeeze to Wheezy I see about ten of these per second filling my system log (about 8 MB/h): Nov 23 00:15:37 acromantula kernel: [ 462.544193] powernow-k8: fid trans failed, fid 0x2, curr 0x0 Nov 23 00:15:37 acromantula

Hi! I would like to know the status of the frequency scaling in XEN. I found a web site saying that XEN doesn’t work with frequency scaling, at the other hand I found some fixes for powernow-k8 to get rid of some messages. I have an AMD64. powerno-k8 works find with non-XEN kernels, but with XEN-kernels I get the error: powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3400+ processors

Hello, every few hours I get the following message in /var/log/message: Jul 5 20:23:28 hXXX kernel: Machine check events logged Jul 5 20:53:28 hXXX kernel: Machine check events logged Jul 5 22:13:28 hXXX kernel: Machine check events logged Jul 5 23:53:28 hXXX kernel: Machine check events logged Jul 5 23:58:27 hXXX kernel: Machine check events logged Jul 6 01:38:27 hXXX kernel: Machine

I have an IBM System x 3250 that successfully boots using the standard kernel (2.6.18-8.1.10.el5) but fails to boot with the xen kernel. The kernel appears to fail when it attempts to initialize the driver for the onboard SAS controller (LSI Logic / Symbios Logic SAS1064E PCI-Express Fusion-MPT SAS). Can anyone provide any advice? Here's the relevant info. Please let me know if any other

Hello, yesterday night I had a problem with my server located at a hoster (strato.de). I couldn't ssh to it and over the remote serial console I saw "out of memory" errors (sorry, don't have the text). Then I had reinstall CentOS 5.5/64 bit + all my setup (2h work), because I have a contract with a social network and they will shut down my little card game if it is not

I finally got the time to try the new kernel. recompiled it and now the compaq r4000 seems like an amd 64 4000+. THe issues of sloowww ness seemed to have gone away. Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20051228/e8f151a7/attachment-0001.html>

All. I am running Xen on an ES7000 system with 4 procs and 4 GB memory. I am running Suse Sles-9 (32-bit) on the machine. I have compiled Xen (the tip on the unstable tree : 6552) with PAE enabled (XEN_TARGET_X86_PAE=y). The system boots fine. I started xend and when I tried to bring up a virtual machine, the system gave me the following error on the command line. On the serial port, I saw an

During boot of dom0, I get the following. Box is remote, so I''m now waiting for proxy power button pusher ;-) tg3 init fails doing dma_alloc_coherent (I assume this is from tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with the amount of memory in dom0. Is this known? thanks, -chris root (hd0,0) Filesystem type is ext2fs,

Jerry Geis wrote: >/ I finally got the time to try the new kernel. />/ recompiled it and now the compaq r4000 seems like an amd 64 4000+. />/ />/ THe issues of sloowww ness seemed to have gone away. / >Which kernel did you end up with? >Cheers, Chris, The subject line mentioned 2.6.14.5, I downloaded it from kernel.org today. Jerry -------------- next part --------------

Hello, I recently tried Xen 3.0.3-testing on my 2x Opteron-244 SMP machine. Everything works well exept one detail, which is not unimportant to me: the powernow-k8 driver fails to switch frequencies. A closer look on the powernow-k8 source reveals, that some MSR write operations seem to be without any effect. A rdmsr() before and after the wrmsr() call reveals that no real change on the register

Could anyone summarize what the support status of cpu frequency changes is at present. I don''t seem to recall generic changes to the hpyervisor in that respect, but the linux tree has fairly extensive changes to the powernow-k8 driver (which would make sense to me only if all other cpufreq drivers are fully supported now, too). Thanks, Jan

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro