See http://blogs.sun.com/sch/entry/indiana_vesa_if_you_need
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
A developer would know how to change his/her environment to use a shell of
his/her choice, some prefer tcsh, some zsh, some ksh, others bash. I'm all for
having bash as the default shell.
--
This message posted from opensolaris.org
___
indiana-discuss
Writing scripts with the assumption that /bin/sh is ksh93 is in itself a very
bad idea. And you can always do #!/usr/bin/ksh93
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.open
Cheer up, not everyone is negative about it ;) Kudos to everyone involved with
the project Indiana, good job!
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailm
> > > Known issue. In the meantime you can pull up a
> shell then run "pfexec
> > > bash" and do a shutodown, init 5 (to shutdown),
> init 6 (to reboot),
> > > etc.
> >
> > You guys with your init-fu... I find that "halt"
> and "reboot" from
> > the root command line do the trick just fine. :)
>
> Didn't see anyone cheering about that except Mike and
> some die hard
> Linux proponents.
Oh, great, so everyone who doesn't agree with you is either Mike or a die hard
Linux proponent... I prefer bash (and I haven't used a Linux distro in more
than 6-7 years), believe it or not, not everyone
See http://www.opensolaris.org/jive/thread.jspa?threadID=43774&tstart=0
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Or just run /lib/opengl/ogl_select/nvidia_vendor_select
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
You might want to try Gnomebaker (it's not hard to get it compiled under OSOL +
SunStudio 12)
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indi
> And wouldn't it be a better solution to start a discussion on adding
> an option to the installer that allows the user to select his
> favourite userland.
+1
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss
I don't think it's a matter of unwillingness, rather than one of a lack of
resources, I'm sure if you get involved with project caiman, you could add this
option yourself :)
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
> cdrecord is the backend for the cd burning functionality in the file manager.
> It
> might not do all of what you want, but it could be extended relatively easily
> I'd imagine.
nautilus-cd-burn seems to be using growisofs when burning to dvd on my snv60,
is it using a different backend in ne
Yeah, it seems to be the case with the newer ON builds when running SATA drives
in PATA mode...
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/in
Here's the issue, hopefully it'll get solved soon:
http://bugs.opensolaris.org/view_bug.do?bug_id=6622965
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailma
Hmm, hopefully this will be fixed in the final DP2
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
boot into single user mode and then do the chown
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Uhm, this is not GNOME specific.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Hey everyone,
Just for your information, I managed to install DP2 preview on a very old
computer with Athlon 850 processor (doesn't support SSE). The problem was that
the caiman installer was crashing, after some debugging, found out that it
tries to unmount /lib/libc.so.1, which is not mounte
Thanks! Keep up the good work :)
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
I second that, please add a comment, it's a common pitfall.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
I still think it's a wee misleading, one assumes that he/she already has the 75
version.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-d
> How well supported is multimedia (mpeg, avi, wmv etc)
> going to be in project Indiana? I ask this because it
> sucks in Solaris 10 and even Nevada / OpenSolaris
> builds that i have trialled to date.
Since Indiana is freely redistributable, there won't be AFAIK
any support for those formats yo
> - gnome-desktop-devel
> To pull in all the necessary packages for
> developing GNOME apps.
> java-desktop-devel
> Pulls in basic JDK needs.
> java-web-devel
> Pulls in a J2EE stack
+1, it would be great to have that..
> I think an IDE should be separate since most people
> have their own p
Just do: pfexec ./imagine or ipstool
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
You are most probably hitting bug
http://defect.opensolaris.org/bz/show_bug.cgi?id=520
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-dis
+1
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
This is imho a case where there's place for improvement, instead of just
copying what Linux has, so I think it should be net0, net1, ...
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http:/
The LiveCD performance is abyssmal. The cpu usage is skyrocketing.
I imagine this is due to LZMA... But is LZMA worth it ? There is a world of
difference in terms of speed in contrast to DP1 & DP2 and I would think that
some people will be put-off by this initial experience (how would they know
> On Sat, 2008-04-26 at 18:55 -0700, MC wrote:
> > While I'm thinking about it, I want to strongly recommend that the
> > default user and password be changed to something other than jack and
> > jack. It stunningly unprofessional :) There are ample linux livecds
> > to use for inspiration if
> BTW, just installed RC2 on IBM/Lenovo R61i (Core 2 duo, Intel Video, e1000g
> NIC, . . what
> else?) Everything seems to be OK, except with the e1000g (funny, no problem
> when running
> LiveCD, but problem when running the installed system). This problem was
> eventually solved
Hmm, maybe
While the zfs-crypto project will provide encryption [1], the support for that
on the root partition is only planned in Phase 4 [2]. Since Phase 1 is planned
for Q2 2008, I don't imagine Phase 4 hitting us in '08, but that's just my
opinion, zfs-crypto devs know better and will surely give you a
Yep, I have that happening to me as well, highly annoying and probably hurts
the drive as well.
It was even more annoying when I was running my drives in P-ATA as I was
hitting this: http://bugs.opensolaris.org/view_bug.do?bug_id=6622965 . But even
in AHCI I still get the spindowns.
What's more
Dave, if it only were as easy as that, it seems that pkg doesn't even retry (or
doesn't retry enough) failed connections, I got a timeout while in the middle
of downloading the openoffice package (and that's a 5Mbps connection, and I was
able to browse the internet just fine at the time, so it m
I found that it's often easier to just remove everything iim* related than deal
with tons of little nuances (for e.g. it leads to artifacts if you use xfce
instead of gnome, bad defaults - I mean Ctrl-Space ? that's like the de-facto
standard for completion)
--
This message posted from opensola
Nope, desktop
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
> As far as I can remember, Ctrl-space has been the "universal" default for
> activating IM.
> Unless we are Microsoft, I doubt we could unilaterally change this. :-)
That's the first time I hear about this (Ctrl-space being the default). But
Ctrl-space is the default for completion in: IDEA, E
Yes, but if I install Linux, Windows, MacOSX, etc.. with the default
installation (the European or US versions), I have no problem whatsover with
using IDEs and with Ctrl-space, with OpenSolaris on the other hand the default
installation already "surprises" you...
--
This message posted from op
At this point a text-based installation is not present. You should try
OpenSolaris RC2a, it allows you to scroll the install window so that it's
possible to go through the installation even with a 640x480 resolution.
--
This message posted from opensolaris.org
__
Not at this time
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
> Well, it took MORE than 60 minutes to install on my
> desktop computer (see info below).
> According to its progress bar, most of the time (99%)
> it was moving data from the CDROM to disk. I gave it
> a slice of 15GB on a 160GiB disk. And it had 1.2 GB
> of RAM to do the job. So what was it doin
Thanks David!
Maybe it would be a good idea to add this bug to the list of known issues for
2008.05 ? Imagine someone having 4 hdds and more and hear all of them power
down / power up immediately, it won't make a good impression...
--
This message posted from opensolaris.org
__
As Alan suggested, better try installing the gcc-dev package
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Nice experiment!
> (1) Installation was very slow. We used to install
> SXDE onto the same machine before, which took us less than 45 minutes to
> finished. Today, most of the folks spent about the same amount of time
> on installation. We think this is too much to install a CD.
Were you installi
> Is anyone looking at ways to have official mirrors around the world?
> Ideally it would be cool if pkg install could check to see what the nearest
> mirror was and install from that.
Why not distribute the last version of the packages on the dvd, so that you
could
mount it, start a script, an
Yeah, and the problem with such times is that on modern hardware they are
simply unacceptable, I don't know if the problem is with architecture of the
pkg itself, or the choice of the language, but I sure hope this will be fixed.
I suppose the performance/liveliness can be improved by caching th
> As pointed out by Laca the real issue here is that
> there is no GUI feedback to the user as to what
> package manager is doing...synaptic too is not fast
> on package operations where it's hitting the network,
> the only difference between the two there is that
> they let the user know what is g
> So in this analogy, is there any plan to give live
> upgrade like capability to opensolaris? As the
> fortnight update is based on development branch and
> is analogous to SXCE, I would except there will be
> occasions I have to fall back to previous BE (or
> previous version of certain packages)
It's mostly a game of gamble, sometimes it powers off, sometimes it doesn't...
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Maybe this will help you:
http://thnetos.wordpress.com/2007/06/05/not-as-simple-perl-script-for-zfs-snapshot-auditing/
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.
Here's the task in question:
http://defect.opensolaris.org/bz/show_bug.cgi?id=1702
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
http://blogs.sun.com/mhaywood/entry/introducing_speedstep_on_solaris
With the knowledge that Solaris supports CPU power management on your system,
you may be asking yourself, "How do I turn it on?" We've recently added a
couple of new keywords to the power.conf(4) file. The new keywords "cpupm"
Yep, that would totally rock!
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Woah! SUNWgnu-mc is in, awesome! Thanks.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
> 2) Why isn't COMPIZ built with Studio? :)
good quesiton...
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Yep, it's a bug worth voting for:
http://defect.opensolaris.org/bz/show_bug.cgi?id=1702
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-di
> > 2) Why isn't COMPIZ built with Studio? :)
>
> Sun Studio is not open AFAIK; thus not
> redistributable. Building Compiz
> with Studio would render Compiz as
> non-redistributable, thus buggering
> OpenSolaris the distro, which is redistributable.
> ICBWT.
Given that virtually all SUNW* pack
What I don't understand is this: Is it expected that everyone who installed
2008.05 knows about indiana-discuss ? It would seems rather natural to update
your system once an update is available, and if most of the ones who installed
2008.05 don't know about indiana-discuss they will end up with
OSS hasn't been integrated into ON yet
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
+1
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
$ pkg search -r Xlib.h
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Yes, of course, just update the grub by booting from the OpenSolaris livecd
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/3.0/contrib/solaris_pkgadd/
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-di
$ pfexec pkg install gcc-dev
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
> I don't know what kind of display you have, but on my
> LCD it's very
> obvious that Firefox 2 (on the right) has clear and
> readable fonts, and
> Firefox 3 (on the left) has dreadfully muddy ones.
On my screen the one on the left looks way better
> If you have a config option to turn the latt
> > On my screen the one on the left looks way better
>
> What type of screen do you have?
24" MVA panel...
Try creating a ".fonts.conf" in your $HOME dir:
none
true
hintfull
true
You'll have to restart the X session though...
--
This me
http://defect.opensolaris.org/bz/show_bug.cgi?id=2302
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
AFAIK it has been said before that there will be .iso releases based on newer
builds, but there were no dates...
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/ma
See http://www.opensolaris.org/jive/thread.jspa?threadID=64494&tstart=0#252216
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Something related to your hardware I assume, as I have 4GB of RAM, and
everything works just fine
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/
As has been mentioned the timeout issue HAS been fixed already, and you
shouldn't be having it after an upgrade to the latest SUNWpkg
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://ma
It's the same version, but has a newer timestamp
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
> 1. it's nice to not have to install 1gb of updates on
> each test system we install
The actual transferred data is around 420MB.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail
> We haven't been distributing USB images, since it
> requires Solaris Express or OpenSolaris to put them on the drive. I
> suppose we can start placing them on the torrent as well, if people would
> find it useful.
That's a great idea, particularily for those who don't have a dvd-writer
in th
See
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6710496
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6698039
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http:
Prepare to be suprised:
PSARC/2008/290 lofi mount
6384817 Need persistent lofi based mounts and direct mount(1m) support for lofi
this is since build 91...
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@ope
Thanks for the link Shawn, this really belongs to this forum's faq as well, as
a lot of people have been asking about that:
Q:
If you download OpenSolaris, but do not purchase a OpenSolaris Subscription,
what can you receive?
A:
You can download future full OpenSolaris releases and obtain securi
> So I would need to buy a subscription just to get
> security updates?
No, you only need subscription if you need support.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.openso
Re xterm, see: http://www.opensolaris.org/jive/thread.jspa?messageID=240012
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
I'm having a similar issue but with different files:
$ firefox
ld.so.1: firefox-bin: fatal: /usr/lib/firefox/libsqlite3.so: corrupt or
truncated file
ld.so.1: firefox-bin: fatal: libsqlite3.so: open failed: No such file or
directory
ld.so.1: firefox-bin: fatal: relocation error: file /usr/lib/fi
> I hadn't noticed the -f to verify; seems unintuitive
> that it needs
> a flag to do what one would think 'verify' does.
> Looks like verify
> without -f doesn't do much if it fails to detect
> truncated files.
Agreed, -f should probably be the default.. Otherwise pkg verify OKs an
otherwise bro
Thanks, I already had the firefox fixed by extracting the libsqllite3.so from
the firefox 3.0.1 contrib package, as for the SUNWcsl, I'll probably wait for a
new build and will update from b93 again.
I guess the best way to fix it, is for pkg to verify the checksum upon
dowloading/installing.
>From http://opensolaris.org/os/project/indiana/resources/rn3/ :
"
# 2328 Package Manager Currently Unavailable
At the current time, the Package Manager cannot be used to install or update
packages. This issue is being addressed and will be fixed as soon as possible.
Workaround
Use the pkg(1) c
> No problem with the un-updated os0811. Sorry for the
> false alarm.
Works fine in the updated OpenSolaris 2008.11 (b105) as well
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mai
> This system was progressively image-updated all the
> way from build 93, which was installed from an
> interim/makeshift LiveDVD. It has a lot of problems.
> E.g., the NIC stopped working--until I updated to
> b105--after I "entire"-updated from os0811, which
> was image-updated from previous b
Update manager failed to update saying that I need to manually update SUNWipkg
(weird, it used to do that automatically), same for image-update.
So I did:
$ pfexec pkg install SUNWipkg
$ pfexec pkg image-update
and pkg just stays on "Creating Plan..." for over 30 minutes now...
--
This message
4Gb RAM + 2Gb swap
I stopped that process.
Ran it again, after 15 minutes of "creating plan" pkg slowly grows to consuming
417Mb and on average 2% CPU, then the growth is very slow (~1Mb per
minute...)..And it seems that after around 30 minutes it finally went on to
downloading (with a horribl
Yep, probably the connection was slow. BTW, pkg(ips) is a great piece of
engineering, keep up the good work ;)
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailm
Yep, probably the connection was slow. BTW, pkg(ips) is a great piece of
engineering, keep up the good work ;)
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailm
Disable the graphic boot ("e" then delete splash & background/foreground
entries, change console=graphics to console=text). Boot. You'll see a console
login prompt, login as usual with your username, type "pfexec svcadm clear
nwam", this will boot the machine... (or just disable it and enable th
If you disable nwam, you must start "physical", i.e.:
$ pfexec svcadm enable physical:default
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indian
I suppose there are two problems, one with the device not being
removed/updated, and another nwam should NEVER get into maintenance mode as it
blocks pretty much the whole system when you do a graphical boot...
--
This message posted from opensolaris.org
_
You are not supposed to update OpenSolaris with BFU, as it's only a minimal
userland+kernel update anyway. You should use "System-> Administration ->
Update Manager" instead.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
> AFAIK, b107 has some X server problems and was
> skipped.
/dev/ seems to have been updated to b107.
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listin
Just updated myself without any problems, the only thing I noticed that is not
working so far is the packagemanager
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/
> Due to a dependency that is missing from the package
> definition, you
> will need to:
>
> pfexec pkg install SUNWgnome-python-extras
>
> ...to get it working again.
Yep, that fixed it, thanks.
--
This message posted from opensolaris.org
___
indian
Strange, it works fine for me:
$ nm /.zfs/snapshot/2008.11/lib/libc.so | grep defopen_r
$
$ nm /lib/libc.so | grep defopen_r
00047479 T defopen_r
Maybe http://defect.opensolaris.org/bz/show_bug.cgi?id=3562 ?
--
This message posted from opensolaris.org
More on this:
http://pkg.opensolaris.org/dev/en/search.shtml?token=libc_hwcap%2A&action=Search
Doesn't give a result for b107 ?
Yet,
http://pkg.opensolaris.org/dev/manifest/0/SUNWcsl%400.5.11%2C5.11-0.107%3A20090212T172317Z
clearly has libc_hwcap
You can manually download the three libc_hwcap1(2
This has been discussed many times now:
http://defect.opensolaris.org/bz/show_bug.cgi?id=6331
--
This message posted from opensolaris.org
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indian
Lenovo T61 fails to suspend now, it used to work on all builds so far. Could it
be the Xorg update that caused this ? When I click on suspend the system goes
back to text mode and just hangs. Log only has:
genunix: [ID 535284 kern.notice] System is being suspended
--
This message posted from ope
Another issue I noticed, I wonder if it's just on my config:
$ pfexec powertop
OpenSolaris PowerTOP version 1.1 (C) 2008 Intel Corporation
powertop: ../cpufreq.c : cpu-change-speed probe unavailable
Collecting data for 5.00 second(s)
And powertop doesn't display the % for P-states. Used to wor
1 - 100 of 135 matches
Mail list logo
