> * Rocky ([EMAIL PROTECTED]) wrote:
> > How can 4GB be too much memory?
>
> It isn't.
>
> > I'd like to use as much as I want. If I want to
> use 64GB of RAM, then so be it.
> >
> > I have no problems on Windows using as much RAM as
> I w
> Pure update schedule assumption. For the times that
> I've been anxiously awaiting the next release, the
> schedule has held true. I haven't watched it very
> religiously however so I have no idea how accurate
> the schedule is.
:) Lots of us here wishing and willing Sun to hurry up with their
How can 4GB be too much memory?
I'd like to use as much as I want. If I want to use 64GB of RAM, then so be it.
I have no problems on Windows using as much RAM as I want.
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
> If you look here ->
> http://www.opensolaris.org/os/downloads/
>
> You'll see this -> "It is updated every other
> Friday." Under the "Solaris Express Community
> Edition" section. Assuming that is the release that
> you are looking for, b85 is due next Friday, the 21st
> of March.
>
> Good luc
> 2. Modern graphic cards in idle, uses maybe like 33%
> or so, of max power i believe. For a 9800GT that
> probably uses 100-150W max, it translates to maybe
> 40W in idle? That is a lot in my opinion. The AMD
> chipset uses like 1W in idle.
33% and/or 40W is too high to be honest; but I read on
> Rocky, I patched the Solaris CPU driver to enable bit
> 1 of the _PDC. Are
> you willing to give it a try? If it fixes the problem
> with your system,
> then I'll see about getting the fix integrated into
> Nevada.
>
> I've attached the driver and an install
> Try always booting with kernel debugger enabled (add
> -k as kernel argument in grub). When it gets stuck
> see if F1-A key combo (on console) drops you into
> kernel debugger. If yes, then you can look around and
> get stack dump (among other useful info) for others
> to take a look.
Thanks, I
> > Unfortunately in some cases when "init 5" has
> succeeded in taking the
>
> ^ did you leave out "not"
Yes, sorry!
> > Any chance the CPU could be halted after the failed
> power-off?
> > Ideally the power-off would work though.
>
> It would be possible to make more progress with this
>
Unfortunately the power-off command ("init 5") only works in about 50% of cases
on my snv_82 machine. I found that some of the power-saving features (HDD
spin-down) cause some conflicts.
Unfortunately in some cases when "init 5" has succeeded in taking the computers
power off, the system is le
> In the
> meantime, you might want to take Gavin's advice and
> modify the line in
>
> ssdt_1_CpuPm.dsl to be
>
> If (LEqual (And (PDC1, 0x09), 0x09))
>
> recompile the file and place it under
> /boot/acpi/tables.
Superb, Gavin/Mark many thanks for your help, I will have an experiment.
Th
I've not done any controlled testing, but I'm getting about ~45MB/sec from
Vista x64 to snv_81 using CIFS over Gigabit Ethernet. I dragged a 20GB file
across and rougly timed it.
This test server currently has two 7200.11 750GB 32MB seagate drives in a ZFS
mirror.
This message posted from
> Have you tried to upgrade bios ?
I've tried F5, F6, F7, F8a beta, and F8b beta on the GA-G33M-DS2R :(
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
> No. Bit 1 is not for C1E. C1E is a hardware feature
> that you really
> don't want to disable. It should provide good power
> management savings
> all on its own.
OK, many thanks. Any other ideas on how to progress this? I'm getting the
same syslog messages on a number of systems and SpeedS
> ssdt_1_CpuPm.dsl contains the following ASL for
> \PR.CPU1:
>
> Scope (\_PR.CPU1)
> {
> Name (HI1, 0x00)
> Name (HC1, 0x00)
> Name (TLD1, 0x00)
> Method (_PDC, 1, NotSerialized)
> {
> CreateDWordField (Arg0, 0x08, CAP1)
> Store (CAP1, PDC1)
> If (
OK, work-around disussion forum, it's now allowing me. Attached is the output
from iasl, and also the two outputs from acpidump for the two cases listed
above.
This message posted from opensolaris.org
iasl.tar.gz
Description: GNU Zip compressed data
_
> Interesting. \_PR.CPU1._PSS just returns
> \_PR.CPU0._PSS. I've never seen
> this logic in any of the ACPI tables I've ever looked
> at before. This
> might be another ACPI related bug. Can you tar up
> all the files dumped
> by iasl and send them?
I'm getting "You are not allowed to edit th
Attached is the .dsl files from above
This message posted from opensolaris.org
cpu0ist.dsl
Description: Binary data
cpu1ist.dsl
Description: Binary data
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
> Rocky wrote:
> > I'm getting the same messages, SpeedStep is enabled
> in the BIOS, I'm using an Intel Celeron E1200.
> >
> > Feb 8 22:34:06 unknown cpudrv: [ID 805513
> kern.info] NOTICE: cpu_acpi: _PSS package not found.
> > Feb 8 22:34:06 unknown
> My problem was solved by BFU-ing to a newer build ,
> but since you have b81 it's probably a different
> issue
>
> Try "./iasl -g" first as root and see if you get the
> ssdt_?_CpuPm.dsl file. If it doesn't contain _PSS,
> try the acpidump Aubrey mentioned.
Sorry, where do I find "iasl" ?
T
I'm getting the same messages, SpeedStep is enabled in the BIOS, I'm using an
Intel Celeron E1200.
Feb 8 22:34:06 unknown cpudrv: [ID 805513 kern.info] NOTICE: cpu_acpi: _PSS
package not found.
Feb 8 22:34:06 unknown cpudrv: [ID 978953 kern.warning] WARNING: cpu_acpi:
error parsing _PSS for C
> Derek Cicero <[EMAIL PROTECTED]> wrote:
>
> > This link:
> >
> > http://dlc.sun.com/osol/on/downloads/current/
> >
> > seems to have disappeared since the dlc came back
> up. We're looking into it.
>
> We now have the state from December 4th. Do you know
> where to get the last two
> months f
21 matches
Mail list logo
