He said that the clock on the chip is running in the lowest possible
speed during boot and he added that clock settings won't be added to the
open source driver. Setting a registry somewhere is obviously is a
major IP hurdle to overcome.
Stay away from this thing. I swear I have the fastest possible laptop
to only run at PII speeds when compiling code. Text scrolling is super
slow and consumes the cpu at 100%. I can not code on the box because of
that so I tend to run it either over the network or without X. It is an
awesome laptop when not in X. Can't wait for my motherboard with intel
graphics...
OpenBSD 4.3-current (GENERIC.MP) #0: Fri Apr 25 12:16:15 CDT 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3755974656 (3581MB)
avail mem = 3633864704 (3465MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf68a0 (63 entries)
bios0: vendor Dell Inc. version "A05" date 11/05/2007
bios0: Dell Inc. Latitude D830
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP HPET APIC ASF! MCFG SLIC TCPA SSDT
acpi0: wakeup devices PCI0(S5) PCIE(S4) USB1(S0) USB2(S0) USB3(S0) USB4(S0)
USB5(S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S3) RP02(S4) RP03(S3) RP04(S3)
RP05(S3) RP
06(S5) LID_(S3) PBTN(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU T7800 @ 2.60GHz, 2593.86 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16
,xTPR,NXE,LONG
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: apic clock running at 199MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T7800 @ 2.60GHz, 2593.50 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16
,xTPR,NXE,LONG
cpu1: 4MB 64b/line 16-way L2 cache
On Sun, Apr 27, 2008 at 09:23:16AM -0400, Jason Beaudoin wrote:
> > I talked with the nvidia guy and he assured me that there is no way
> > that they'll fix this in the open source driver.
> >
>
> that's rather horrendous..
> anymore info on this? Was he referring to the nv developers from being
> able to "figure out" the magick? or that his nVidia people were
> unwilling to intervene? both?
>
> so frustrating..
>
> thanks for sharing!
>
> regards,
> ~Jason
