search for: mhz

...ver 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 gid 0x0 (2000 MHz) powernow-k8: 1 : fid 0x0 gid 0x0 (1700 MHz) powernow-k8: 2 : fid 0x0 gid 0x0 (1400 MHz) powernow-k8: 3 : fid 0x0 gid 0x0 (1200 MHz) powernow-k8: 4 : fid 0x0 gid 0x0 (1000 MHz) powernow-k8: 0 : fid 0x0 gid 0x0 (2000 MHz) powernow-k8: 1 : fid 0x0 gid 0x0 (1700 MHz) powernow-...

I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated.

...he one based on PCMCIA is making problems on FreeBSD. I cannot boot my notebook with the device inserted into the port, or it will render the system unusable (100% load on cbb(4)). And all I can see is the following: Jul 12 14:58:39 link kernel: ath0: ath_chan_set: unable to reset channel 1 (2412 Mhz, flags 0x480 hal flags 0xc0), hal status 0 Jul 12 14:58:40 link kernel: ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x480 hal flags 0xc0), hal status 3233070656 Jul 12 14:58:41 link kernel: ath0: ath_chan_set: unable to reset channel 7 (2442 Mhz, flags 0x480 hal flags 0xc0), hal...

...#39;ll > like that mode better. Using "-r 75" fixes the problem. > Also does 720x480 work better? Yes, 720x480 works without the -r parameter. > Looking at your EDID, you have: > > Established timings supported: > 720x400 at 70Hz 9:5 HorFreq: 31469 Hz Clock: 28.320 MHz > 640x480 at 60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz > 640x480 at 75Hz 4:3 HorFreq: 37500 Hz Clock: 31.500 MHz > 800x600 at 60Hz 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz > 800x600 at 75Hz 4:3 HorFreq: 46900 Hz Clock: 49.500 MHz > 1024x768 at 60Hz 4:3 HorFreq: 48400 Hz C...

...:01:00.0] ZCOMP: 0 tags [ 2.811563] nouveau [ PTHERM][0000:01:00.0] FAN control: PWM [ 2.811588] nouveau [ PTHERM][0000:01:00.0] fan management: automatic [ 2.811634] nouveau [ PTHERM][0000:01:00.0] internal sensor: yes [ 2.811711] nouveau [ CLK][0000:01:00.0] 07: core 324 MHz memory 648 MHz [ 2.811720] nouveau [ CLK][0000:01:00.0] 0a: core 540 MHz memory 1620 MHz [ 2.811727] nouveau [ CLK][0000:01:00.0] 0f: core 1058 MHz memory 5000 MHz [ 2.811872] nouveau [ CLK][0000:01:00.0] --: core 324 MHz memory 648 MHz [ 2.827731] nouveau [ DRM]...

...nel/debug/dri/0/pstate > > AC (or DC) line shows the current state. > > On Mon, Jun 19, 2017 at 1:00 PM, James <bjlockie at lockie.ca> wrote: >> I have a NVE7 (GK107). >> How do I see the current memory/CPU speed? $ sudo cat /sys/kernel/debug/dri/0/pstate 07: core 324 MHz memory 648 MHz 0a: core 540 MHz memory 1620 MHz 0f: core 1058 MHz memory 5000 MHz AC: core 324 MHz memory 648 MHz Wow, it defaults to the lowest. Is there a way to change it?

...on "Ignore" "true" EndSection # Internal LCD does not return DDC information. # Define first channel: Section "Modes" # See also "HP-2133 Known Modes" at file end. Identifier "HP-2133 LCD Modes" # Default mode "1280x768": 80.1 MHz, 47.7 kHz, 60.0 Hz Modeline "1280x768-60.0" 80.14 1280 1344 1480 1680 768 769 772 795 # Default mode "1280x720": 74.6 MHz, 44.2 kHz, 59.2 Hz Modeline "1280x720-59.2" 74.60 1280 1341 1474 1688 720 721 724 746 -hsync +vsync # Default mode "1024x768"...

...ect match for initial modes (II) NOUVEAU(0): Output DVI-0 using initial mode 2048x1536 (--) NOUVEAU(0): VideoRAM: 262144 kBytes (==) NOUVEAU(0): Using gamma correction (1.0, 1.0, 1.0) (--) NOUVEAU(0): Virtual size is 2048x2048 (pitch 2048) (**) NOUVEAU(0): Default mode "2048x1536": 266.9 MHz (scaled from 0.0 MHz), 95.3 kHz, 60.0 Hz (II) NOUVEAU(0): Modeline "2048x1536"x60.0 266.95 2048 2200 2424 2800 1536 1537 1540 1589 -hsync +vsync (95.3 kHz) (**) NOUVEAU(0): Default mode "1920x1440": 234.0 MHz (scaled from 0.0 MHz), 90.0 kHz, 60.0 Hz (II) NOUVEAU(0): Modeline...

...on "Ignore" "true" EndSection # Internal LCD does not return DDC information. # Define first channel: Section "Modes" # See also "HP-2133 Known Modes" at file end. Identifier "HP-2133 LCD Modes" # Default mode "1280x768": 80.1 MHz, 47.7 kHz, 60.0 Hz Modeline "1280x768-60.0" 80.14 1280 1344 1480 1680 768 769 772 795 # Default mode "1280x720": 74.6 MHz, 44.2 kHz, 59.2 Hz Modeline "1280x720-59.2" 74.60 1280 1341 1474 1688 720 721 724 746 -hsync +vsync # Default mode "1024x768"...

Ilia Mirkin <imirkin at alum.mit.edu> writes: > It would be useful to know how the screen is connected. Also please > grab the monitor's EDID from /sys/class/drm/cardN-connector/edid and > attach it here. It would also be interesting to get a boot with > "drm.debug=0x1e nouveau.debug=disp=trace" which has the modeswitch in > question. The screen is connected

...; > > >> Also does 720x480 work better? > > > > Yes, 720x480 works without the -r parameter. > > > >> Looking at your EDID, you have: > >> > >> Established timings supported: > >> 720x400 at 70Hz 9:5 HorFreq: 31469 Hz Clock: 28.320 MHz > >> 640x480 at 60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz > >> 640x480 at 75Hz 4:3 HorFreq: 37500 Hz Clock: 31.500 MHz > >> 800x600 at 60Hz 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz > >> 800x600 at 75Hz 4:3 HorFreq: 46900 Hz Clock: 49.500 MHz > >&g...

...cimal (!) value of the pstate you want to clock to on > boot. The valid pstates are defined by your VBIOS, and are visible in > /sys/kernel/debug/dri/0/pstate (in hex). These are my options. I've tried both 14 (0e) and 15 (0f). Both appear to work. Is there a difference? 07: core 405 MHz memory 648 MHz 0a: core 405-967 MHz memory 1620 MHz 0e: core 405-1241 MHz memory 6008 MHz 0f: core 405-1241 MHz memory 6008 MHz AC DC * AC: core 405 MHz memory 6007 MHz 0f is currently selected in the above. > Based on the little information you provided, I doubt your hangs have > much to d...

...c Start : multiples of 8 (II) NVIDIA(0): Horizontal Sync Width : multiples of 8 (II) NVIDIA(0): Horizontal Total Width : multiples of 8 (II) NVIDIA(0): (--) NVIDIA(0): Connected display device(s) on GeForce 7100 GS at PCI:2:0:0: (--) NVIDIA(0): DFP-0 (--) NVIDIA(0): DFP-0: 155.0 MHz maximum pixel clock (--) NVIDIA(0): DFP-0: Internal Single Link TMDS (--) NVIDIA(0): DFP-0: Native FlatPanel Scaling is not supported (--) NVIDIA(0): DFP-0: DFP modes are not limited to 60 Hz refresh rate (--) NVIDIA(0): DFP-0: DFP is not internal to notebook (--) NVIDIA(0): (--) NVIDIA(0): --- EDI...

...current state. >>> >>> On Mon, Jun 19, 2017 at 1:00 PM, James <bjlockie at lockie.ca> wrote: >>>> I have a NVE7 (GK107). >>>> How do I see the current memory/CPU speed? >> >> $ sudo cat /sys/kernel/debug/dri/0/pstate >> 07: core 324 MHz memory 648 MHz >> 0a: core 540 MHz memory 1620 MHz >> 0f: core 1058 MHz memory 5000 MHz >> AC: core 324 MHz memory 648 MHz >> >> Wow, it defaults to the lowest. > > Defaults to whatever state the VBIOS puts it into. > >> Is there a way to change it? &g...

...nitialized. (II) S3VIRGE(0): I2C device "I2C bus:ddc2" registered at address 0xA0. (II) S3VIRGE(0): I2C device "I2C bus:ddc2" removed. (==) S3VIRGE(0): Using gamma correction (1.0, 1.0, 1.0) (--) S3VIRGE(0): videoram: 2048k (--) S3VIRGE(0): Detected current MCLK value of 45.102 MHz (II) S3VIRGE(0): Monitor0: Using hsync range of 31.50-80.00 kHz (II) S3VIRGE(0): Monitor0: Using vrefresh range of 30.00-100.00 Hz (II) S3VIRGE(0): Clock range: 10.00 to 270.00 MHz (II) S3VIRGE(0): Not using default mode "1024x768" (insufficient memory for mode) (II) S3VIRGE(0): Not usin...

...2-13 18:55:59.203197 +0100 [ 109.093119] nouveau [ PTHERM][0000:01:00.0] fan management: automatic 2014-12-13 18:55:59.206283 +0100 [ 109.096221] nouveau [ PTHERM][0000:01:00.0] internal sensor: yes 2014-12-13 18:55:59.229500 +0100 [ 109.119368] nouveau [ CLK][0000:01:00.0] 20: core 675 MHz shader 1450 MHz memory 1008 MHz 2014-12-13 18:55:59.232628 +0100 [ 109.122527] nouveau [ CLK][0000:01:00.0] --: core 675 MHz shader 1458 MHz memory 900 MHz 2014-12-13 18:55:59.236536 +0100 [ 109.126342] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 FAULT at 0x00fd94 2014-12-13 1...

...ernal Mar 17 23:31:31 MacSam kernel: [ 4.116064] nouveau [ PTHERM][0000:04:00.0] fan management: automatic Mar 17 23:31:31 MacSam kernel: [ 4.116068] nouveau [ PTHERM][0000:04:00.0] internal sensor: yes Mar 17 23:31:31 MacSam kernel: [ 4.116092] nouveau [ CLK][0000:04:00.0] 03: core 405 MHz shader 405 MHz memory 405 MHz Mar 17 23:31:31 MacSam kernel: [ 4.116098] nouveau [ CLK][0000:04:00.0] 07: core 450 MHz shader 810 MHz memory 450 MHz Mar 17 23:31:31 MacSam kernel: [ 4.116101] nouveau [ CLK][0000:04:00.0] 0e: core 450 MHz shader 810 MHz memory 450 MHz Mar 17 23:31:31 MacSam...

Hi, Is there any documentation on enabling hypervisor support for both C and P-state control? On xen-unstable and linux-2.6.18-xen.hg, if I enable cpuidle=1 on the xen command line and then run xenpm, I will get output for C-states (shown below) but it complains that "Xen cpufreq is not enabled!" cpu id : 0 total C-states : 2 idle time(ms) : 73264 C0

...Sam kernel: [ 4.116064] nouveau [ > PTHERM][0000:04:00.0] fan management: automatic > Mar 17 23:31:31 MacSam kernel: [ 4.116068] nouveau [ > PTHERM][0000:04:00.0] internal sensor: yes > Mar 17 23:31:31 MacSam kernel: [ 4.116092] nouveau [ > CLK][0000:04:00.0] 03: core 405 MHz shader 405 MHz memory 405 MHz > Mar 17 23:31:31 MacSam kernel: [ 4.116098] nouveau [ > CLK][0000:04:00.0] 07: core 450 MHz shader 810 MHz memory 450 MHz > Mar 17 23:31:31 MacSam kernel: [ 4.116101] nouveau [ > CLK][0000:04:00.0] 0e: core 450 MHz shader 810 MHz memory 450 MHz &gt...

...0000:01:00.0: fb: 512 MiB GDDR3 The kernel module has options: config=NvClkMode=15 That leads to errors: nouveau 0000:01:00.0: clk: failed to raise voltage: -22 ... nouveau 0000:01:00.0: clk: error setting pstate 3: -22 After that the contents of /sys/kernel/debug/dri/0/pstate are: 03: core 169 MHz shader 338 MHz memory 100 MHz 05: core 275 MHz shader 550 MHz memory 300 MHz 07: core 400 MHz shader 800 MHz memory 300 MHz 0f: core 625 MHz shader 1563 MHz memory 800 MHz AC DC * AC: core 275 MHz shader 550 MHz memory 799 MHz Kernel log and VBIOS will follow. -- You are receiving this mail beca...