Re: [osol-discuss] Oracle Solaris 11 install trouble, NVIDIA
On 01/10/12 15:38, Blai Bonet wrote: I'm also having trouble with the nvidia driver. I installed Solaris 11 11/11 in a Sun Ultra 20. Everything went fine until installing the desktop. Afterwards, I get kernel panics (and crash dumps) when using the supplied nividia driver. Please provide the panic message and stack trace, at a minimum. The kernel core file would also be really helpful if it is not too much trouble to find a host. The contents of /var/log/Xorg.0.log using the nv driver will also help identify the specific NVIDIA graphics hardware. However, the nv driver doesn't cause panics. Unfortunately, the desktop won't run ok with the nv driver because it doesn't support the glx extension. I downloaded the driver from nvidia but cannot install it. The driver is packed with the old format of packages and the installation script gets confused. Instructions for manual installation of drivers from nvidia.com: http://hub.opensolaris.org/bin/view/Community+Group+x_win/NvidiaInstallation ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle Solaris 11 install trouble, NVIDIA
On 11/10/11 21:09, Paul Gress wrote: /kernel/drv/amd64/nvidia: undefined symbol 'pm_destroy_components' warning: mod_load: cannot load module 'nvidia' You are using an old NVIDIA driver without the fix for IR 842949. Either use the bundled driver for Solaris 11 or any driver from nvidia.com posted after late summer. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Intel Kernel Mode-setting (KMS) in snv173
On 10/17/11 13:38, Bruno Damour wrote:
I has tried with console=text but not the correct option as it seems ;-)
console=text still uses bitmapped graphics. From the heads up message:
Solaris now has support for high resolution and color depth consoles.
By default, your machine will boot using a 1024x768x16-bit console, unless
your video card doesn't support it in which case it will fall back to
800x600 and finally 640x480.
The type of console (and also the old VGA TEXT 640x480 console) can be
controlled through both kernel parameters and GRUB directives:
-B console={text|graphics|force-text}
selects the type of booting console. 'text' and 'graphics' both select a
high resolution console, while force-text selects the old VGA TEXT
console. ...
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] libc thread failure: _thread_setschedparam_main() fails
struct queue *chunk_que; chunk_que = spm_normal_malloc(sizeof(struct queue) * nqueues); pthread_mutex_init(que-mutex, NULL); pthread_mutex_lock(que-mutex); //The error occurs here! Go check your test program. It is not doing what you think it is. Check the return code from your call to pthread_mutex_init(). Also verify pthread_mutex_init() isn't being called more than once. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] sort options
On 03/18/11 08:18 AM, Richard L. Hamilton wrote: I think sort(1) needs a couple of new (as of the last time I looked at an OpenSolaris man page) options: -C (upper case letter C): same as -c but explicitly silent. This should comply with the latest SUS/XPG, and reconcile the difference between /usr/bin/sort and /usr/xpg4/bin/sort. -h (as a comparison type, thus also usages like -k1h): from recent GNU sort, to compare human-readable numeric values with or without a suffix like K M G etc. (Thus solving the problem of how to sort the output of e.g. du -hs * ) The first of those looks quite easy; the second would require a well-defined format and comparison for human-readable numeric values to be researched and specified, before writing the comparison code. /usr/gnu/bin/sort has both options. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] What pkg is my command in.
On 03/10/11 10:26 AM, Mike DeMarco wrote: How do you go about finding which package the command you want to add is in. pkg search /usr/bin/resize ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Another [OT] Hardware Post
On 02/25/11 04:23 AM, Orvar Korvar wrote: I dont have a cluster or specialized hardware at home, to do heavy calculations. I can buy Nvidia card to do calculations, but Solaris does not support OpenCL nor CUDA nor anything similar - as far as I know. To use graphic cards to do heavy calculation I need to switch OS to Linux with OpenCL, which is not an option. A question: If I buy Nvidia graphic card, and install Windows in VirtualBox together with 3D support - could I use OpenCL / CUDA / whatever in the Windows VM? Not in a Windows guest. Parallels Workstation Extreme supports a GPU dedicated to a guest, but the software alone is expensive. Submit an enhancement request for VirtualBox. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Another [OT] Hardware Post
On 02/24/11 06:50 AM, Orvar Korvar wrote: If I can replace all computers at home, with SunRays I have saved power. Say each PC uses 100 watt at idle, that could be 300Watt at idle. If I replace them with a SunRay server that idles at 50watt, I have saved lots of power. I want the server to be powerful, but excellent graphics performance is not important, but I want rudimentary graphics ability: 1080p, Compiz, etc. Sandybridge is powerful CPU, so I can do some heavy compilations and development, and also SunRay will benefit from powerful CPU. While I'm a big fan of deploying SunRays, there are lower power alternatives to 100W PCs for running compiz. My Atom N330 + ION brick (ASRock ION 330) runs Solaris 11 Express + compiz just fine and rarely every budges above 25W with an active desktop. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Another [OT] Hardware Post
On 02/24/11 03:14 PM, Orvar Korvar wrote: Thanks for the tips, but I also need to do heavy development and run heavy calculations. So I need a beefy CPU above all. But I prefer if it has low power requirements. That is the reason Sandybridge is what I prefer. I have to wait and see how the 3D graphics driver turns out What's the objective definition of beefy? Intel Arrandale CULV + ION might offers a bit more CPU + memory for a bit more power above Atom (18W for the CPU package). The HTPC market is making many low power configs available. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Another [OT] Hardware Post
On 02/23/11 12:46 PM, Alan Coopersmith wrote: On 02/23/11 02:56 AM, Orvar Korvar wrote: I thought 3D driver for Sandbybridge was on it's way? Unlike the nvidia driver, which is available for download separate from the OS, Minor nit. The driver available for download from nvidia.com currently lacks some enhancements/fixes available in the bundled driver (MSI, fastreboot, ...). For example, the GT 220, et. al., fix went into the bundled 260.19.29 driver in build 156 but was not available from nvidia.com until the 270.26 beta driver release this week. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Another [OT] Hardware Post
On 02/21/11 09:56 AM, Orvar Korvar wrote: Eric, Intel Sandybridge, does it support ECC? I heard that Intel does not allow hardware targeted to home users support ECC. Only server stuff supports ECC. http://www.evga.com/support/motherboard/ The eVGA X58 motherboards allow Xeon CPUs with ECC memory. I believe the Mac Pro also uses Xeon with ECC. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fan speed control in OpenSolaris/OpenIndiana
On 01/18/11 08:10 AM, Robin Axelsson wrote: I have noticed that when booting my system in Windows the fans are rotating at a much lower speed than in OSOL/OI. I even tested running some heavy applications for the duration of a couple of hours and still the fans were lower. The conclusion I draw from this is that there is no fan speed control in my OSOL/OI configuration, instead the system/cpu fans are just running continuously at full speed. So my question is; how do I set up fan control in OSOL/OI so that they provide the amount of cooling needed instead of running at full speed all the time? It is more likely a thread is keeping the system busy. Can you provide a snapshot of the output of /usr/bin/powertop? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fan speed control in OpenSolaris/OpenIndiana
On 01/18/11 09:03 AM, Robin Axelsson wrote: Copying the text of PowerTOP destroys the formatting so I supply a png of it instead. At present I'm running a virtual machine (with Windows) and Gnome but I get the same fan speed even when there is nothing running. rge#1 is producing a lot of interrupts. Is there anything connected to this port. (You have two ethernet ports. rge#0 looks normal). ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fan speed control in OpenSolaris/OpenIndiana
Also have you been able to tell which fan is spinning fast? If there is a fan on the graphics card, which model? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Need coaching about used equipment
On 01/12/11 08:58 PM, Erik Trimble wrote: If you care about video/audio, I'd look at the used workstation stuff. It has less hard drive bays, but better audio and video capacity. FWIW, some (most?) newer NVIDIA cards come with an audio device that works with the Solaris audio plumbing. The audio stream is fed over the DisplayPort or HDMI cable so you need a monitor that supports DP/HDMI audio playback. Also, some cards are available in a x1, LP form factor (e.g., NVS 300) which can be used in motherboards without a x16 mechanical slot. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris 11 Express: xterm very slow
On 12/15/10 09:38 AM, Claus Assmann wrote: Oh well, maybe I put an nVidia graphics card into the box again and see how that works (it caused some problems with X and the selection of a graphics card before). Details? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X11 With Multi thread
On 12/15/10 12:55 PM, Debabrata Debroy wrote: Hi I want to use X11 in a multi threaded Application . I have attached a code that I have written to achieve it .Basically From main function I am calling a callback function fun() which will create a thread add(). From the thread I am again creating a callback function AddCB. My doubt is If I dont call XtAppProcessEvent from thread function add() its not calling the callback function AddCB.It giving output as After Creating Threads add Add:Before Timeout add end add After unlock So is it like that If we need to process some event in a thread ,that event should be raised in the thread itself .That is my add thread cannot process any event from the main function . On which build? On build 154 I see: $ g++ test_multi.cpp -lXt -lX11 $ ./a.out After Creating Threads add Add:Before Timeout add end add After unlock Called from Add Called from Add Called from Add ^C $ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
On 12/12/10 01:29 PM, Alan Coopersmith wrote: The mouse being reported as going online and offline several times a second seems like the much bigger problem. On 12/10/10 01:13 PM, user124 wrote: My G9 work in 2009.06 from snv_111b to snv_117 normally, but from snv_118 till nowadays builds it has very strange problem. I looked at the changes in b118 and the one change that stands out: 6769365 USB should power down during suspend A WAG is while it isn't a suspend, the code executed in DDI_DETACH now powers down the device. The interface sub-device may get detached which may have an undesired side effect on the mouse and input sub-devices. Backing out this change in a b118 BE might be an interesting experiment. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
On 12/13/10 09:26 AM, user124 wrote: I think i guessed how to solve this problem. Find the same problem with another mouse and the solution was is to connect mouse through USB hub. Active or passive hub? (Possible power issue) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
On 12/ 9/10 03:37 PM, user124 wrote: Maybe someone would answer to my question after viewing this listing? Your last questions were: Should i have root for viewing /var/adm/messages when i boot from live CD? What is the root password when i boot from live CD? The last one was answered yesterday -- solaris. What's in /var/adm/messages? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
On 12/ 9/10 04:04 PM, user124 wrote: Dec 9 22:55:38 solaris usba: [ID 349649 kern.info] Logitech G9 Laser Mouse 0719BBECD10029 Dec 9 22:55:38 solaris genunix: [ID 936769 kern.info] hid0 is /p...@0,0/pci1043,8...@13/dev...@1/keybo...@0 Dec 9 22:55:38 solaris genunix: [ID 936769 kern.info] hid2 is /p...@0,0/pci1043,8...@13/dev...@2/mo...@0 Dec 9 22:55:38 solaris genunix: [ID 408114 kern.info] /p...@0,0/pci1043,8...@13/dev...@1/keybo...@0 (hid0) online Dec 9 22:55:38 solaris genunix: [ID 408114 kern.info] /p...@0,0/pci1043,8...@13/dev...@2/mo...@0 (hid2) online I think we need our USB experts to look at this but your G9 appears to be advertised as separate keyboard and mouse devices. However, I don't see a discrete keyboard being detected. Do you happen to have something like an Apple keyboard which has an internal USB port? If not, how about switching the USB keyboard and G9 mouse connections to reverse the scan order. After seeing this, I think I will ask Santa for the G9x mouse. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] songbird bug
On 12/ 8/10 04:26 PM, Paul Gress wrote: I also just tried my Songbird, and get the same repeating of the second song with Sol Ex 11 b151a. Reported on other platforms also: http://getsatisfaction.com/songbird/topics/songbird_repeats_every_second_song_endless ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
On 12/ 7/10 01:41 PM, user124 wrote: Anybody? Any ideas? I looked for a G9 in local stores but only the G9x is now available. The web page you sent points to a link that implies the G9 is EOL, replaced by the G9x. When you boot LiveCD are there any interesting USB messages in /var/adm/messages? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
On 12/ 6/10 07:45 AM, user124 wrote: 8 usb_mid 1 device 046d.c048 G9 Laser Mouse I looked in local computer stores and all I could find was a Logitech G9x: http://www.microcenter.com/single_product_results.phtml?product_id=0317173 Does this look the same or can you provide part number details from the mouse or its packaging? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
On 11/26/10 10:22 AM, user124 wrote: Need some time to show you listing of this command because, sometimes, it's hard to work in user interface without mouse. What does the output on b111b show? That will help identify the correct model. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem with Logitech G9 mouse
On 11/25/10 02:34 PM, user124 wrote: Hi all, I've found myself having problems with my Logitech G9 laser mouse on Solaris Express 11. The cursor won't move, and the lights on the mouse keep flashing (rather than lighting solidly as they should). Mouse worked perfect on Solaris 2009.06 (111b), but after system updating the same were happened. I decided to wait for solaris 11 but, unfortunately, were disappointed. If somebody knows how to solve, please help. What does this report: $ sudo bash -c 'echo ::prtusb | mdb -k' ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X11 XtAppAddTimeOut is not working properly.
On 11/22/10 12:25 AM, Alan Coopersmith wrote: I believe Linux defaults to a higher resolution timer, something you can enable system-wide on Solaris, ... Just as an experiment to verify, in /etc/system add: set hires_tick = 1 and reboot. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X11 XtAppAddTimeOut is not working properly.
On 11/22/10 07:13 AM, Debabrata Debroy wrote: Hi John it is working fine with the changes .Can you please tell what will be the performance impact of this The system clock tick rate gets bumped from 100Hz (10mS) to 1000Hz (1mS), so the system load handling the clock interrupt will go up. Objective measurements would depend on the platform. I would run powertop to verify the extra wakeups aren't pushing the system in a higher power state. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] No network/Internet
On 10/16/10 01:13 PM, Jürgen Keil wrote: j...@opensolaris:~$ ifconfig nge0 ifconfig: status: SIOCGLIFFLAGS: nge0: no such interface nVidia MCP61 should work in build 73 or newer: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6497473 Is the nge driver matter here? The original message said: Foxconn M61PMV M.B.; AMD Phenom X3 CPU @ 2.1GHz GeForce 6150SE 128MB; nForce 430 Chipset. -- And finally, this is my network adapter: BroadCom AC131 (MCP61 nForce 4 LAN). According to the Foxconn web page the NIC is Broadcom AC131: http://www.foxconnchannel.com/product/Motherboards/detail_overview.aspx?id=en-us412 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] No network/Internet
On 10/17/10 08:50 AM, Jürgen Keil wrote: As far as I understand it, the Broadcom AC131 is the PHY chip attached at the nVidia MCP61 network controller. The nVidia MCP61 ethernet controller should be handled by the Solaris nge driver. The device driver utility is reporting that the nge driver will be used with the nVidia MCP61 device: http://www.opensolaris.org/jive/thread.jspa?messageID=502914#502914 Maybe the nge driver needs some special code to handle the Broadcom AC131 PHY ? I can't find anything on the Broadcom site about AC131, but if it is just a PHY connected to the nForce MAC then the nge code is pretty generic. On one motherboard I've seen an issue with nge driver is bringing the PHY out of low power mode after warm booted from another OS. Since there isn't device specific code to handle this, sometimes a cold boot is needed to put the PHY in a state where it works with the nForce MAC. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] C programming, invalid argc value
On 10/ 5/10 02:04 PM, Jürgen Keil wrote: Which compiler, compiler version, gdb version did you use? What compilation flags? What does the test program look like? Using Opensolaris b134, gcc 3.4.3, gdb 6.8, a simple hello, world type test program, and compilation options -g -O it works for me. Per private email, this was on b111 and compiling the cfgadm utility source. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] dtcalc grabs mouse and won't let go
On 09/29/10 12:07 PM, Mike DeMarco wrote: Can't find a way to set the number of decimal places in galculator Calculator - Preferences - Show N decimal places ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] NetApp and Oracle settle patent dispute over ZFS
On 09/13/10 08:22 AM, joerg.schill...@fokus.fraunhofer.de wrote: But in any case, patents are anachronistic. Patents have been created to protect inventions made by single personss against big companies 200 years ago. Patents are now perverted by the big companies against the original intention. Single persons like Paul Allen? http://www.theregister.co.uk/2010/08/27/paul_allen_patent_offensive/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] -Graphiccard Support- avaible soon?
On 08/16/10 05:26 AM, Matthias Pfützner wrote: John, it's build 134 he's using, and that has that bug... Not on all machines, but on most... Understood, but I got the impression the need to disable graphics boot mode happened after loading the NVIDIA driver, implying on this system there was no need to do this when the vgatext kernel driver was being used. Matthias You (John Martin) wrote: On 08/15/10 01:22 PM, MOKE wrote: Yes it works great. Thank you very much ;-). this step by step tutorial very clearly and easy. While booting I have to edit the Bootloader and change from graphic loader to text loader. I would consider needing to disable graphics mode a bug, unless this is just a preference. What happens if you leave the boot in graphics mode? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] -Graphiccard Support- avaible soon?
On 08/15/10 01:22 PM, MOKE wrote: Yes it works great. Thank you very much ;-). this step by step tutorial very clearly and easy. While booting I have to edit the Bootloader and change from graphic loader to text loader. I would consider needing to disable graphics mode a bug, unless this is just a preference. What happens if you leave the boot in graphics mode? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] -Graphiccard Support- avaible soon?
On 08/14/10 05:22 PM, MOKE wrote: Hellö My Question is: Are there any projects for NVIDIA Graphic Cards? I am using my Leptop Lenovo W510 with Nvidia FX880M but O-Sol doesent support this GraphicCard now.With Vesa drivers it works but it was not nice ;-( As long as Lenovo uses device id 0xa3c for the Quadro FX 880M, you need driver 195.36.24 or greater (delivered in b139). I recommend downloading driver 256.44 from nvidia.com and follow the installation instructions in comments 5,6,10 of: http://defect.opensolaris.org/bz/show_bug.cgi?id=12196 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
On 08/ 4/10 05:27 AM, Matthias Pfützner wrote: John Martin, any ideas? As this also would work for the standard Solaris, because at least, nVIDIA already does provide the drivers for Solaris... I don't see how Illumos provides added incentive (ignoring potential open versus closed friction). NVIDIA owns CUDA. Let them know how many Quadro boards you will buy. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
On 08/ 4/10 09:40 AM, Matthias Pfützner wrote: But, like Adrian Cockcroft did twitter last night: Mr. Ellison is backing Solaris. Pick your horse. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
On 08/ 4/10 11:24 AM, Paul Gress wrote: Yes I believe that would be true if the OS was developed for Workstations. The only commitment I see from Oracle is Servers and Databases. Would CUDA help there? Large scale GPGPU deployment is being done on servers. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
On 08/ 4/10 12:04 PM, Paul Gress wrote: When I read the Hardware Compatability notes for PTC Pro-Engineer WF5, it states there are no current plans for its next generation WF6 MCAD product to be developed on Solaris 10. This means to me, ... Careful asserting cause to effect. Linux support for Wildfire was dropped a long time ago when there were still plenty of workstation choices from Linux vendors. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] unable to break out of X
On 08/ 2/10 03:40 PM, Allen Jasewicz wrote: It is really weird, I am in single user mode, I have imported rpool to /a as read/write and I am unable to find an xorg.conf file on the /a mount. It was working and I wanted to make adjustments to the display and typed in kdmconfig while windows was running. I exited out without saving anything, then rebooted and that is what lead to where I am, unable to get windows to work or get a prompt when in multi user mode. What does cat /a/etc/release report? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] unable to break out of X
On 08/ 2/10 03:40 PM, Allen Jasewicz wrote: It is really weird, I am in single user mode, I have imported rpool to /a as read/write and I am unable to find an xorg.conf file on the /a mount. It was working and I wanted to make adjustments to the display and typed in kdmconfig while windows was running. I exited out without saving anything, then rebooted and that is what lead to where I am, unable to get windows to work or get a prompt when in multi user mode. You're on Solaris 10 Update 8: Solaris 10 10/09 s10x_u8wos_08a X86 Copyright ... Use is ... Assembled 16 September 2009 Look for /a/etc/openwin/server/etc/OWconfig. There may be a backup file in that directory. The template file should be /a/usr/openwin/server/etc/OWconfig. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] network card driver issue with hp-z400 workstation
On 08/ 1/10 11:55 AM, john george wrote: hi i have installed opensolaris 2009.06 in hp-z400... You need to download the bcme 57xx driver from Broadcom. http://www.broadcom.com/support/ethernet_nic/netxtreme_server.php ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Dell and HP to Certify and Resell all Three Oracle Operating Systems on their x86 Server Computers
On 07/30/10 04:27 PM, Norbert P. Copones wrote: now... where is mr. morgan of theregister? he just said oracle spikes hp oem contract. hope the contract spiking fud ends here. To be fair to TPM, he did a follow-up story referencing his original spikes story: http://www.theregister.co.uk/2010/07/29/oracle_hp_dell_solaris/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] mplayer + VDPAU + opensolaris = ?
On 07/21/10 06:45 PM, Aleksey Cheusov wrote: I'm certain VDPAU is supported and works. It is part of the performance and regression testing done for each driver release. Hm, it is interesting to know how QA is organized in OpenSolaris. Is this information available online anywhere or entire process is made intirely inside Oracle? The NVIDA graphics driver goes through a QA cycle at NVIDIA and then I run a full set of performance/regression and front-of-screen tests before it gets bundled. I have not publicly documented all the tests run. How much memory do you have? My Atom N330 + ION has 4GB. 2Gb of RAM in total, from which 256Mb is marked as iGPU frame buffer size (in BIOS). top says Memory: 1791M phys mem. My SBIOS reserved 512MB. Are you using the 256.35 driver or the 190.53 driver bundled with b134? There have been quite a few VDPAU fixes in the subsequent driver releases. 190.53 We really want to concentrate on the current release driver. There won't be any more updates or investigation of problems on the R190 branch that can't be reproduced in R256. Ok. Lets talk about one video available for both of us. While playing nature_704x576_25Hz_1500kbits.h264 Your original query was for a BDAV file (hd-video.m2ts) which is why I was concentrating on that format. Grab this file from http://www.sendspace.com/file/p3lasn. Play it with: mplayer -vo vdpau -vc ffh264vdpau,ffmpeg12vdpau,ffvc1vdpau,ffwmv3vdpau, test1.m2ts On b134 + 190.53 the playback will be choppy. Update the driver to 256.35 in a new BE (changing only the NVIDIA driver) and the playback will be smooth. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] mplayer + VDPAU + opensolaris = ?
On 07/21/10 04:03 PM, Aleksey Cheusov wrote: It is good to know that OpenSolaris supports VDPAU in theory and works for someone. But unfortunately it still doesn't work for me :-(. I'm certain VDPAU is supported and works. It is part of the performance and regression testing done for each driver release. Last time I strictly followed your instructions with one exception, I added svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libavcore whithout which mplayer just didn't compile. I don't know how to resolve the discrepancy. libavcore is not in the mplayer-vdpau instructions posted by NVIDIA. It did build and run on my non-work Atom N330 system. I also apply your patches. It works the same way -- output is very jerky. As previously -nosound doesn't change anything. So, what to check/do now? What software/subsystems can affect this? SunOS sunos 5.11 snv_134 i86pc i386 i86pc Solaris How much memory do you have? My Atom N330 + ION has 4GB. Are you running the default compiz setting? (Mine is set to Normal). Does it get any better with compiz disabled? Are you using the 256.35 driver or the 190.53 driver bundled with b134? There have been quite a few VDPAU fixes in the subsequent driver releases. Load averages: 2.07, 1.96, 2.61; up 0+22:34:0422:47:47 97 processes: 95 sleeping, 2 on cpu CPU states: 45.8% idle, 27.0% user, 27.3% kernel, 0.0% iowait, 0.0% swap Kernel: 4126 ctxsw, 3428 trap, 6310 intr, 72469 syscall, 3 fork, 2832 flt, 524 Memory: 1791M phys mem, 50M free mem, 512M total swap, 511M free swap PID USERNAME NLWP PRI NICE SIZE RES STATETIMECPU COMMAND 525 root3 200 109M 76M sleep 155:37 13.50% Xorg 4535 cheusov 1 410 146M 48M sleep0:19 6.14% mplayer load averages: 0.30, 0.17, 0.09; up 0+04:17:01 17:00:20 89 processes: 88 sleeping, 1 on cpu CPU states: 89.3% idle, 5.7% user, 5.1% kernel, 0.0% iowait, 0.0% swap Kernel: 1314 ctxsw, 12 trap, 1089 intr, 25691 syscall Memory: 3327M phys mem, 414M free mem, 1663M total swap, 1663M free swap PID USERNAME NLWP PRI NICE SIZE RES STATETIMECPU COMMAND 1849 rugrat 3 530 81M 49M sleep0:59 4.48% Xorg 2263 rugrat 2 590 151M 57M sleep0:02 2.31% mplayer 2051 rugrat 1 590 47M 41M sleep0:21 1.23% compiz-bin Your Xorg process is showing a high cumulative CPU time. Any chance it is constantly handling other tasks, such as a over active mouse/keyboard or firefox client? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] mplayer + VDPAU + opensolaris = ?
On 07/20/10 03:09 AM, Aleksey Cheusov wrote: then no. Results are the same. The same jerks and the same CPU Idle time over 80%. In additional while playing nature_704x576_25Hz_1500kbits.h264 mplayer said No pts value from demuxer to use for frame! pts after filters MISSING No pts value from demuxer to use for frame!,?% 0 0 pts after filters MISSING No pts value from demuxer to use for frame!,?% 0 0 pts after filters MISSING ... On an Atom N330 + ION I see the same messages, except with -nosound the video is very quick and without jerkiness. while playing Grey.ts ... Your system is too SLOW to play this! ... TS_PARSE: COULDN'T SYNC2% 0.0% 0 0 I also tried latest svn snapshot, results are the same. I see the same message, but again the video is not jerky. The complete output: $ mplayer -nosound -vo vdpau -vc ffh264vdpau Grey.ts MPlayer SVN-r31758-4.3.3 (C) 2000-2010 MPlayer Team Cannot test OS support for SSE, leaving disabled. Playing Grey.ts. TS file format detected. VIDEO H264(pid=255) NO AUDIO! NO SUBS (yet)! PROGRAM N. 1000 FPS seems to be: 25.00 == Forced video codec: ffh264vdpau Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family Selected video codec: [ffh264vdpau] vfm: ffmpeg (FFmpeg H.264 (VDPAU)) == Audio: no sound Starting playback... [VD_FFMPEG] Trying pixfmt=0. Movie-Aspect is 1.76:1 - prescaling to correct movie aspect. VO: [vdpau] 1920x1088 = 1920x1088 H.264 VDPAU acceleration [VD_FFMPEG] XVMC-accelerated MPEG-2. V:40348.8 903/903 1% 1% 0.0% 0 0 TS_PARSE: COULDN'T SYNC V:40348.8 903/903 1% 1% 0.0% 0 0 Exiting... (End of file) When I get some time I will look into the SSE message. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] mplayer + VDPAU + opensolaris = ?
For media players I always recommend Fluendo before trying to roll your own. Cannot test OS support for SSE, leaving disabled. . When I get some time I will look into the SSE message. See the fix for SSE/SSE2 below in cpudetect.c. Maybe someone could request pushing this to the upstream code. SSE and SSE2 are enabled on my Atom N330 so hopefully this will help speedup the CPU bound portions of the playback. (I'm not certain the __sun is the correct macro going forward, but it is the only thing that seemed to work with all the compilers I tested). On a Atom N330 + ION 4GB system not on the Oracle network I loaded b134 and added the gcc-43, svn, gettext, and x11/header packages from the /dev repository. Downloaded mplayer following the VDPAU instructions: $ mkdir mplayer $ cd mplayer $ svn co --ignore-externals svn://svn.mplayerhq.hu/mplayer/trunk . $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libavcodec $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libavformat $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libavutil $ svn co svn://svn.mplayerhq.hu/ffmpeg/trunk/libpostproc $ svn co svn://svn.mplayerhq.hu/dvdnav/trunk/libdvdread/src libdvdread4 $ svn co svn://svn.mplayerhq.hu/dvdnav/trunk/libdvdnav/src libdvdnav Made the following changes: +++ configure 2010-07-20 09:27:25.178089569 -0400 @@ -1,4 +1,4 @@ -#! /bin/sh +#! /bin/bash # # Original version (C) 2000 Pontscho/fresh!mindworkz # ponts...@makacs.poliod.hu @@ -1503,6 +1503,10 @@ extra_cflags=$extra_cflags -I/usr/pkg/include fi +if sunos ; then +extra_cflags=$extra_cflags -Wa,--divide +fi + if darwin; then extra_cflags=-mdynamic-no-pic -falign-loops=16 -shared-libgcc $extra_cflags _timer=timer-darwin.c +++ version.sh 2010-07-20 09:28:42.220664374 -0400 @@ -1,4 +1,4 @@ -#!/bin/sh +#!/bin/bash test $1 extra=-$1 +++ cpudetect.c 2010-07-20 13:47:06.382713016 -0400 @@ -45,6 +45,8 @@ #include os2.h #elif defined(__AMIGAOS4__) #include proto/exec.h +#elif defined(__sun) +#include sys/auxv.h #endif /* Thanks to the FreeBSD project for some of this cpuid code, and @@ -416,6 +418,11 @@ mp_msg(MSGT_CPUDETECT,MSGL_WARN, Cannot test OS support for SSE, disabling to be safe.\n ); gCpuCaps.hasSSE=0; #endif /* _POSIX_SOURCE */ +#elif defined(__sun) +uint32_t ui = 0; +(void)getisax(ui, 1); +gCpuCaps.hasSSE = (ui AV_386_SSE) ? 1 : 0; +gCpuCaps.hasSSE2 = (ui AV_386_SSE2) ? 1 : 0; #else /* Do nothing on other platforms for now. */ Built with: $ export PATH=/usr/gcc/4.3/bin:$PATH $ export CC=/usr/gcc/4.3/bin/gcc $ export CXX=/usr/gcc/4.3/bin/g++ $ ./configure --disable-xvr100 --enable-gui --disable-x264-lavc --disable-x264 --enable-vdpau $ gmake ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] mplayer + VDPAU + opensolaris = ?
On 07/19/10 07:40 PM, Aleksey Cheusov wrote: mplayer -vo vdpau \ -vc ffmpeg12vdpau,ffwmv3vdpau,ffvc1vdpau,ffh264vdpau hd-video.m2ts I found a BDAV sample file (test1.m2ts - Cars trailer) and it plays smoothly with the combination of mplayer built with earlier instructions and NVIDIA driver 256.35 on Atom N330 + ION. $ $HOME/bin/mplayer -vo vdpau -vc ffh264vdpau,ffmpeg12vdpau,ffvc1vdpau,ffwmv3vdpau, test1.m2ts MPlayer SVN-r31758-4.3.3 (C) 2000-2010 MPlayer Team Playing test1.m2ts. TS file format detected. VIDEO H264(pid=4113) AUDIO A52(pid=4353) SUB Teletext(pid=4609) PROGRAM N. 1 FPS seems to be: 23.976025 == Forced video codec: ffh264vdpau Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family Selected video codec: [ffh264vdpau] vfm: ffmpeg (FFmpeg H.264 (VDPAU)) == == Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 48000 Hz, 2 ch, s16le, 640.0 kbit/41.67% (ratio: 8-192000) Selected audio codec: [ffac3] afm: ffmpeg (FFmpeg AC-3) == [AO ESD] esd_open_sound failed: Broken pipe [AO SDL] Samplerate: 48000Hz Channels: Stereo Format s16le AO: [sdl] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... [VD_FFMPEG] Trying pixfmt=0. Movie-Aspect is 1.78:1 - prescaling to correct movie aspect. VO: [vdpau] 1920x1080 = 1920x1080 H.264 VDPAU acceleration [VD_FFMPEG] XVMC-accelerated MPEG-2. A: 141.7 V: 142.4 A-V: -0.729 ct: -1.484 1444/1444 2% 1% 8.2% 2 0 Exiting... (End of file) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] NVIDIA GeForce 9500 GS on build 134
On 07/19/10 02:44 PM, Doug Poland wrote: Hello, I'm very new to OpenSolaris but am quite familiar with FreeBSD. I have a box with an NVIDIA G96 GeForce 9500 GS. I installed 2009.06 and the installer choose the Xorg vesa driver. I have a working X desktop but colors and performance are unappealing. I ran pkg image-update and am now running svn_134. Xorg still uses the vesa driver and performance is worse than 2009.06. I did some googling and came across a thread (http://opensolaris.org/jive/thread.jspa?threadID=120352) in which someone suggested that one needs the R190 driver or better. Build 129 has this driver. If I'm not mistaken, build 134 should include this driver, but I have no success getting Xorg to start using the nvidia driver. I can supply exact error messages if necessary. The file created by /usr/bin/nvidia-SunOS-bug-report.sh is the best starting point. You can send it to me privately and I will summarize for the group. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] NVIDIA GeForce 9500 GS on build 134
On 07/19/10 02:44 PM, Doug Poland wrote: I ran pkg image-update and am now running svn_134. Xorg still uses the vesa driver and performance is worse than 2009.06. I did some googling and came across a thread (http://opensolaris.org/jive/thread.jspa?threadID=120352) in which someone suggested that one needs the R190 driver or better. Build 129 has this driver. According to the log file, you have device id 0x645 (different from the card in the above thread). This id was not in the 190.53 driver (Solaris or Linux) delivered to build 132 (no update through 134). The first driver release officially listing this id was 195.36.24 (build 139). You should install the current release driver in a new BE following the instructions in comments #5,6,10 of: http://defect.opensolaris.org/bz/show_bug.cgi?id=12196 FWIW, you were using the nv X driver, not VESA. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] mplayer + VDPAU + opensolaris = ?
On 07/19/10 07:40 PM, Aleksey Cheusov wrote: Hi all. I'm trying to setup mplayer with VDPAU on OpenSolaris v_134 on Atom/ION-based Acer Aspire Revo 3600. I've compiled it successfully from source and run the following command mplayer -vo vdpau \ -vc ffmpeg12vdpau,ffwmv3vdpau,ffvc1vdpau,ffh264vdpau hd-video.m2ts Do the H.264 samples in the VDPAU readme file play correctly? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] NVIDIA GeForce 9500 GS on build 134
On 07/19/10 10:25 PM, Doug Poland wrote: Thanks for the info. I checked out the instructions in the URL you supplied and have a follow-up question. How do I get the OS up to build 139? If I only need the new driver 195.36.24, how do I make pkg fetch that particular version? You don't need to update from b134. Download the current driver from nvidia.com. Follow the instructions in the previous message on how to unpack the driver and install it in a new BE. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] setting proper screen resolution
On 07/16/10 12:20 PM, adidas wrote: here is Xorg.0.log Please help in setting up the proper resolution. You are using build 108 with an ATI Radeon HD 4200. It is falling back to the VESA driver which has restrictions on what resolutions are offered. What happens with build 134? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] gcc + tgmath (Paul Floyd)
On 07/13/10 09:53 AM, Stathis Kamperis wrote: Hi tgmath.h is C99, and you're compiling as C89 (-ansi). Try -std=c99 instead of -ansi, or stick to C89 features. Your code might compile on Linux, since on that platform C89, C99, C++ and in fact most standards are all rather a blur. Yes, you are right. But it doesn't make any difference: Not for the bundled gcc 3.4.3 (package name gcc-3) but it does work for gcc 4.3.3 (package name gcc-43): $ /usr/bin/gcc tgmath.c -lm -Wall -W -ansi -pedantic tgmath.c: In function `main': tgmath.c:6: warning: implicit declaration of function `__tgmath_cos' Undefined first referenced symbol in file __tgmath_cos/var/tmp//cccxaqop.o ld: fatal: symbol referencing errors. No output written to a.out collect2: ld returned 1 exit status $ $ /usr/gcc/4.3/bin/gcc tgmath.c -lm -Wall -W -ansi -pedantic tgmath.c: In function ‘main’: tgmath.c:6: warning: implicit declaration of function ‘cosl’ tgmath.c:6: warning: implicit declaration of function ‘cosf’ $ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Multithreading X
On 07/ 6/10 10:48 PM, Alan Coopersmith wrote: But retrofitting a 25-year old multi-million line code base to be completely thread-safe, much less thread-hot, is not a small task. And since we already have GPU's that run 128 or 256 operations in parallel without adding any threads to the core server, it's not clear what the effects would be. Instead of concentrating just on X, perhaps we should expand this to multithreading (really multiprocessing) the desktop. Some possibilities: Direct rendering by compiz. We currently force indirect rendering by compiz even if the graphics pipeline is capable of direct rendering. Indirect rendering sends all work through the X server which just adds to the single threaded overload. hwc. Hardware cursor movement on Xsun was handled inside the kernel driver, offloading some of the work from the X process. hwc did improve the interactive feel of the desktop, even if part of it was only aesthetic. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] I think Oracle needs a new name for [Open]Solaris ..
On 07/ 7/10 01:43 PM, Gary wrote: And Oracle is really paying you to scour IBM sites to refute an opinion? http://www.goodreads.com/quotes/show/79229 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] setting proper screen resolution
On 06/22/10 02:50 PM, Thommy M. Malmström wrote: I am unable to set the proper screen resolution for osol 2009.06. Desktop's screen resolutions are 1024X768, 800X600, etc. But, monitor's actual resolution is 1600X900. monitor make and model is AOC 2036sa monitor's current resolution is 1024X768 More interesting is your type of graphics card. The contents of /var/log/Xorg.0.log will tell us the graphics card and give clues to why the proper resolution wasn't selected/validated. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X58 and i7?
On 06/15/10 03:29 PM, Stefan Parvu wrote: thx. I was asking if anyone else is running this mobo with OSOL. Does close count? I run my daily operations on a eVGA X58 SLI with i7 980X (previously i7 920) using AHCI for disk access. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] X58 and i7?
On 06/15/10 05:46 PM, Chavdar Ivanov wrote: You will not be able to install if the DVD is SATA in AHCI mode. Is this specific to the P6T or do you believe it is necessary for all X58/ICH10 motherboards? On my eVGA X58 SLI, the hard drive and DVD are connected to the ICH10 SATA ports and set to AHCI. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 8 bit PseudoColor visual ?
On 05/27/10 05:06 PM, Alan Coopersmith wrote: Dennis Clarke wrote: On most graphics cards you will have to choose to either have everything 8-bit or everything 24-bit, not mix both in the same session like some of the old SPARC graphics cards allowed. NVIDIA Quadro cards with Xorg allow turning on color index transparent overlay (off by default). This advertises a 255 PseudoColor X visual in addition to 24 bit. However, when someone says old old software it typically wants the 8 bit visual to be the default, which causes lots of problems with recent desktop managers. Also, composite and XRandR are usually incompatible with transparent overlay. If you are lucky and the old old software searches for an 8 bit visual and can live with only 255 colors (and no composite or XRandR), transparent overlay may work. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using Xinerama with 2 out of 3 monitors?
On 05/20/10 10:23 PM, Ian Collins wrote: [sorry if this appears twice, I sent from the wrong account] Does anyone know if it is possible to combine 2 monitors (on same nVidia card) with Xinerama, while keeping a third as a separate X screen? Twinview isn't an option because one monitor is rotated. The current driver only supports rotating the entire X screen. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using Xinerama with 2 out of 3 monitors?
On 05/21/10 01:37 AM, Ian Collins wrote: With the older GPU I have (a 7900 GTX) Xinerama only works up to 4096 pixels, I have two (rotated) 20 panels flanking a 30 panel. That's 4960 pixels wide. G80 and above supports 8K. GF100 and above supports 16K. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Dual monitors --- where is xorg.conf?
On 04/12/10 06:49 PM, Ian Collins wrote: On 04/13/10 10:26 AM, bsd wrote: You want something like: Section ServerLayout Identifier Layout0 Screen 0 Screen0 0 0 Screen 1 Screen1 leftOf Screen0 InputDevice Keyboard0 CoreKeyboard InputDevice Mouse0 CorePointer Option Xinerama 0 EndSection along with Screen and Monitor sections to identify you displays in your xorg.conf. The above is for multiple X screens. I believe a single X screen is desired. In this case, the single Screen section needs: Virtual 3286 1080 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Adobe Flash Player version 10.0.45.2 seen working ?
On 04/ 9/10 03:45 PM, Guy Woolley wrote: I installed flashplayer from the extra repo, and it didn't work fully (video OK, no audio). I have SUNWmlib installed. What does /usr/bin/audiotest and /usr/bin/audioctl show-device -v report? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any news about 2010.3?
On 04/ 7/10 07:58 PM, bsd wrote: Peace pipe accepted. :-) I set 'console=text' but it still loops. I have also set 'acpi-user-options=2' because otherwise I get a kernel panic. Anything after b129 is problematic for some reason. It's a Toshiba L505D-S5983. Upgrading from b129 on several of my systems required applying these two fixes documented in: http://opensolaris.org/jive/thread.jspa?threadID=125446tstart=0 The first one fixed the panic reboot loop. 6914346 upgrade from OpenSolaris 2009.06 (111b2) to 130 fails with stale http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6914346 After updating to build 130 or beyond, the system may panic with messages of the form /kernel/misc/amd64/pci_autoconfig: undefined symbol 'pcie_get_rc_dip' WARNING: mod_load: cannot load module 'pci_autoconfig' panic[cpu0]/thread=fbc2e3a0: failed to load misc/pci_autoconfig Work-around: Boot the original boot environment (BE) instead and correct the boot archive as follows reboot into the earlier BE u...@host$ pfexec beadm mount name of new BE /mnt u...@host$ pfexec bootadm update-archive -F -R /mnt u...@host$ pfexec beadm unmount name of new BE At this point, the new BE can be booted into. 12380 image-update loses /dev/ptmx from /etc/minor_perm http://defect.opensolaris.org/bz/show_bug.cgi?id=12380 When using image-update or the Package Manager to update to build 125 or greater, remote access to the system via ssh(1) or rlogin(1) may become unavailable. Alternatively, using terminal programs such as gnome-terminal(1) or xterm(1) may result in characters not being echoed or commands unable to be typed. Work-around: Boot the original boot environment (BE) instead and correct the /etc/minor_perm file contained within as follows reboot into the earlier BE u...@host$ pfexec beadm mount name of new BE /mnt u...@host$ pfexec sh -c \ grep ^clone: /etc/minor_perm /mnt/etc/minor_perm u...@host$ pfexec touch /mnt/reconfigure u...@host$ pfexec bootadm update-archive -R /mnt u...@host$ pfexec beadm unmount name of new BE At this point, the new BE can be booted into. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Mapping physmem in a kernel module
On 04/ 4/10 10:37 PM, Maule Mark wrote: Hi all: Sorry for the newbie question. I’m working on a kernel module which is meant to manage a chunk of physical memory. My intent is to boot the kernel with ‘physmem=somevalue’ to limit the physical memory available to the OS, and then use this kernel module to manage the rest of physical memory to support some code that we are porting from another OS. This approach assumes physical memory is contiguous and any space above physmem is reserved for your driver's exclusive use. I believe you will have issues implementing this approach. Does the physical memory get accessed by a hardware device? One of the things the module needs to do is map this reserved physical memory into the kernel virtual address space so that we can write data management structs etc. into it. The module will then service ioctl's from user space, as well as calls from other kernel modules to manipulate the memory. The DMA allocation routines return a KVA. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Codeina popup
On 04/ 1/10 08:53 AM, Gary Gendel wrote: Whenever I log in, I get a message that there are Codeina updates available for the free mp3 decoder. So I installed the upgrade, but it still still happens every time I log in. If I tell it to install again, it tells me that it's already installed. Anyone know what the process is to find out whether it's really upgraded, or if this is a bogus popup? Then, if it is the latter, how do I convince the upgrade process that it's got the upgrade? System - Preferences - Startup Applications Uncheck Codeina update notifier ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SUNWgmake download
On 03/27/10 06:18 AM, lcd_user wrote: hi, I run the pkgrm SUNWgmake command , now I'd like to reinstall that package , can I find it on the net , I'searched on the open solaris but it doesn't contain that package. I've even have a Solaris 10 dvd , If you are using development builds, starting with 133 the IPS package name changed from SUNWgmake to developer/build/gnu-make. pkg install developer/build/gnu-make ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] MythTV
On 03/18/10 10:20 AM, homerun wrote: Greetings Just asking , is there interest to port MythTV to OpenSolaris. http://www.mythtv.org/ How long will the supported list of video capture cards be useful? The notices I've been receiving from Comcast sound like they are moving to most programming being delivered as encrypted digital. If this an indication of where the industry is moving, how useful will the boards be that only support over the air (ATSC) or unencrypted cable (clear QAM)? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Three heads on GeForce 8600 Video Card
On 03/18/10 05:17 PM, robs wrote: I've got two monitors hooked-up to the DVI ports of a GeForce 8600 video card. Recently moved the computer into the living-room, and want to run my TV off of the s-video port. I've tried numerous different settings, but can only get two heads to work at the same time. Not possible. Only two outputs per GPU can be active at the same time. You need to add a second card. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 127 to 134 upgrade woes (gdm)
On 03/11/10 06:27 AM, robs wrote: Well, I tried to upgrade from OpenSolaris 127 to 134, and gdm doesn't start. If I remove the xorg.conf file, my dual monitor setup gets pointers on each monitor, but that's it. There is no mention of any problem relating to this in the 134 notes. I did see that /usr/lib/xorg/modules/extensions/GL was pointing to somewhere non-existent, but the instructions in the 130 release notes no longer apply: u...@host$ pfexec rm /usr/lib/xorg/modules/extensions/GL u...@host$ pfexec ln -s ../../../../../var/run/opengl/server \ /usr/lib/xorg/modules/extensions/GL That is, there ain't an opengl/server directory in 134. From looking through an Xorg.0.log file,I also found that libglx.so symbolic links in these directories were broken: /usr/lib/xorg/modules/extensions /usr/lib/xorg/modules/extensions/amd64 so, I took a swag and redirected them to: /usr/lib/mesa/modules/extensions /usr/lib/mesa/modules/extensions/amd64 as appropriate. No joy. You appear to have manually loaded the NVIDIA driver, which as you found out the X and GLX modules were removed during the upgrade when IPS thought the directories were empty. For the GeForce 8600 GTS, the bundled build 134 driver should work fine. What happens if you do: $ pfexec pkg install driver/graphcis/nvidia $ pfexec reboot -p ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [desktop] NVIDIA driver install
On 03/ 9/10 04:13 AM, Jens Richter wrote: os b133 Hello I'm a bit in a catch22 situation. For my card - FX 5700LE - I need the 173.14.25 driver. I downloaded the driver from NVIDIA. # shdriver.run givs me the error, that the NVDAgraphics package can't be uninstalled. Okay, # pfexec pkg uninstall NVDAgraphics tells me that the package isn't installed. So it seems I have to uninstall the package nvidia. Right, when I try that, the error message is, that the package can't be uninstalled and I should try it in a different boot env. Fair enough, so I left X and switched to init 1. Same problem here. Hum. How to solve the prob? Thank's in advance jens57 Starting with b133, the IPS package name changed. See comment #10 of: http://defect.opensolaris.org/bz/show_bug.cgi?id=12196 Use the instructions in comments #5 and #6 with the new IPS package name to uninstall the bundled driver and install the legacy driver. I have IPS packages of the R173 and R96 legacy drivers but it turns out there are complications hosting these driver in a way where the bundled and two legacy driver exclude each other so that only one driver can be installed at a time. We are still trying to come up with a solution. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [desktop] NVIDIA driver install
On 03/ 9/10 10:23 AM, Jens Richter wrote: j...@opensolaris:~$ pfexec pkg -R /mnt uninstall NVDAgraphics Creating Plan pkg: 'NVDAgraphics' matches no installed packages My previous message mentioned the package name change. The command for b133 and higher is: $ pfexec pkg -R /mnt uninstall -r driver/graphics/nvidia ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] gcc 4.3 and b134
I upgraded from b133 to b134 using the internal /dev repository. There was a notice it was removing the gcc 4.3.2 packages gcc-432 and gcc-runtime-432. After the upgrade, package manager shows gcc-432 and gcc-runtime-432 as empty packages with a new package gcc-43 which appears to be gcc 4.3.3. However, I don't see anything that looks like a gcc 4.3.3 runtime package. Should there be a runtime? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] gcc 4.3 and b134
On 03/ 8/10 02:20 PM, Dennis Clarke wrote: Per LSARC/2009/575, the gcc-runtime-432 package is now obsolete and was refactored into the following new packages: developer/gcc/gcc-libgcc developer/gcc/gcc-libgfortran developer/gcc/gcc-libgomp developer/gcc/gcc-libobjc developer/gcc/gcc-libssp developer/gcc/gcc-libstdc So there is no ADA functionality in these at all is there ? No, but there wasn't ADA runtime in the gcc-runtime-432 package either so it isn't a regression in functionality. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Bordeaux 2.0.2 for Solaris and OpenSolaris Released
On 03/ 1/10 06:19 PM, valrh...@gmail.com wrote: ... A quick question on flash player: can you get the beta 10.1b3 release working? The reason that I ask is about GPU acceleration. There is much better GPU acceleration in the Windows version that doesn't appear in Linux (at least) because the video acceleration isn't standard (there's a bunch of posts on that at Adobe Labs). I don't know enough of the details to understand how Bordeaux/Wine talks to the GPU in OpenSolaris, but if you could get the Windows flash player with full GPU acceleration to give you the same (or similar) performance on OpenSolaris, that would be a stunning technical achievement. FlashPlayer 10 is (thankfully) working properly on OpenSolaris, but its GPU acceleration is limited, and video performance is certainly less than that on Windows (when I reboot and use FlashPlayer 10.1beta. I'm not sure if Adobe plans to spend much time on full GPU acceleration on OpenSolaris, since I think their perception is that the market is small, so if we could use Bordeaux to circumvent this with Windows versions (as opposed to using VirtualBox or something else, which isn't that fast), that would be spectacular! Let's dispel some myths: 1. Flash Player on Solaris (and Linux) will use GPU acceleration via OpenGL for certain operations like scaling. Verify under Settings that Enable hardware acceleration is checked. On a A/C power miserly Atom+ION nettop, flash videos such as: http://www.youtube.com/watch?v=0kNEo8OxrT8 use only a small amount of CPU even in full screen mode. 2. The video acceleration isn't standard issue was primarily for H.264. Some background info from Adobe: http://blogs.adobe.com/penguin.swf/2010/01/welcome_to_the_thicket.html http://blogs.adobe.com/penguin.swf/2010/01/solving_different_problems.html There have been many private communications to Adobe on how to use the standard X and OpenGL APIs to resolve the generic UI issues in addition to using VDPAU for full acceleration of H.264. A specific post from NVIDIA: http://blogs.adobe.com/penguin.swf/2010/01/solving_different_problems.html#comment-2133401 Bordeaux on Solaris is a wonderful thing for running Windows clients that provide unique functionality, but we shouldn't rely on this as the solution for operations where Solaris clients already have the functionality or only need minor tweaks. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Bordeaux 2.0.2 for Solaris and OpenSolaris Released
On 02/28/10 07:16 PM, valrh...@gmail.com wrote: This will make a subdirectory ./temp/, and you have to edit the ./temp/bordeaux-installer file and change tar to gtar. Then the installer works. The default user environment should have /usr/gnu/bin at the front of PATH. /usr/gnu/bin/tar should be a symlink to /usr/bin/gtar. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] NVIDIA driver: multiple monitor configuration retention
On 02/27/10 06:54 PM, valrh...@gmail.com wrote: I am running a multiple monitor configuration on my b133 workstation. Using the nvidia-settings control panel, I can set the second monitor up properly (it's detected and set with the proper resolution automatically). However, after reboot, Osol always activates only the first (primary) monitor, and I have to manually switch the second one on. I can run nvidia-settings as su from a terminal, but that doesn't help; the configuration never persists through a reboot. Does anyone else have this problem? You will need to save /etc/X11/xorg.conf with the Save to X Configuration File button. Tutorials at: http://www.opensolaris.com/toshibanotebook/m10-multiscreen.html ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OS b132: Sun C++ cannot compile C++ source due to linker segfault.
On 02/25/10 12:13 AM, William Kucharski wrote: What I see in b133 is this: $ CC test.cc CC: Fatal error in ld: Segmentation Fault (core dumped) ld: fatal: file /opt/sunstudio12.1/prod/lib/crti.o: section [9].rela.annotate has invalid type [ SHT_RELA ] When previously reported, the two workarounds suggested were to set the environment variable LD_NOEXEC_64=1 or to add -xannotate=no to the compile options. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OS b132: Sun C++ cannot compile C++ source due to linker segfault.
On 02/16/10 07:49 AM, Karel Gardas wrote: $ CC test.cc CC: Fatal error in ld: Segmentation Fault (core dumped) ld: fatal: file /opt/sunstudio12.1/prod/lib/crti.o: section [9].rela.annotate has invalid type [ SHT_RELA ] is this a known bug or should it be reported somewhere? CR 6823945. Apply the latest SS12U1 patch 141858. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Point-of-View ION+Atom 330
On 02/16/10 11:35 AM, Patrick wrote: I tried to install a more recent build on that M/B (b131) and the graphics seems to workok, but I get serious problems with the onboard NIC the assigned gani driver could not attach dmesg... [ID 217474 kern.info] gani0: ilr 0x010a [ID 825931 kern.info] gani0: ddiregsmap_setup failed (ret:-1) is that issue solvable? Can you post the output of prtconf -pv? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b132 is out!
For some reason Firefox 3.6 (tar.gz version) won't start in b132 (it worked in b131). Looks like the nightly build was built only against S10? Please this not be the case; so many people have worked so hard on OpenSolaris! The NVIDIA graphics driver is only built on S10. Binary compatibility allows the same binaries to run on S10, SXCE and OpenSolaris. Why do you believe separate builds are required for Solaris? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [laptop-discuss] Toshiba M10 - 111 to 131 upgrade issues - GDM fails, blank screen
I'm happily running on my Tecra M10. I don't know what the circumstances are exactly, but I am definitely not experiencing panics. One model has NVIDIA graphics, the other Intel. This issue is particular to the Intel models. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Atom based board, and experiences?
On 01/29/10 07:04 AM, Matthias Pfützner - Principal Field Technologist - Systems Infrastructure Ambassador - Solution Architect wrote: Intel is offering some very low power Atoms, that also have virtualization in them (VT-x), anyone already seen board for/with them, and knows, if OpenSolaris will work? Atom is a CPU only, not SOC, so OpenSolaris support will depend on the southbridge chipset used. Atom+ION has worked flawlessly since b126 on this platform: http://www.asrock.com/nettop/spec/ion%20330.asp with the disk interface set to AHCI before installation. A power meter at the wall outlet shows 24W at an idle compiz desktop. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Toshiba M10 - 111 to 131 upgrade issues - GDM fails, blank screen
On 01/25/10 08:04 AM, Bruce Porter wrote: I have booted the system into single user and disabled GDM so I can get at any logs that may be needed to help resolve. /var/log/Xorg.0.log[.old] from the b131 BE would be a good start. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_131 and Intel GM945 - Compiz not working
On 01/23/10 04:26 AM, Chavdar Ivanov wrote: Hi, On snv_131 I get: ... (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/GL/64/libglx.so dlopen: ld.so.1: Xorg: fatal: /usr/lib/xorg/modules/extensions/GL/64/libglx.so: wrong ELF class: ELFCLASS64 (EE) Failed to load /usr/lib/xorg/modules/extensions/GL/64/libglx.so (II) UnloadModule: glx (EE) Failed to load module glx (loader failed, 7) ... Do you have a 32-bit libglx.so? Sun Microsystems Inc. SunOS 5.11 snv_131 January 2010 rug...@tecram10:~$ file /usr/lib/xorg/modules/extensions/GL/libglx.so /usr/lib/xorg/modules/extensions/GL/libglx.so: ELF 32-bit LSB dynamic lib 80386 Version 1, dynamically linked, stripped rug...@tecram10:~$ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [xwin-discuss] Bug 13540 - what are conditions to hit it?
On 01/23/10 11:31 AM, Alexander wrote: Hello. For two builds (130,131) I hit 13540 bug (Xorg dies on gnome-session startup). I couldn't make more sophisticated diagnostics, but all other main gnome processes (gnome-settings-daemon, metacity, nautilus, gnome-panel) may be launched by hand from xterm and work successfully. However, I see that people work with these builds successfully. What can be a reason for such a strange behavior? Can I help in any way in diagnosing this problem? Can you enable core files for Xorg? I believe all we have are X logs and AFAIK no one in engineering has been able to reproduce it yet. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 128a was the latest fairly stable build
On 01/22/10 08:36 AM, Bruce wrote: Does anyone know if there is a bug for this already or do I have to speend time searching ? For VTx enabled on M10, there are at least two bugs: // S/R http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6870290 // power-off http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6913815 There's some hope both of these will be solved by fixing: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6889221 There's also the IDE problem: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6842573 The SBIOS default is AHCI so this should only happen if the setting was changed. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 128a was the latest fairly stable build
On 01/21/10 05:20 AM, Bruce wrote: Is the M10 going to be the continued supported/sold platform (ok US only I know, but I chose it because of the fact it could be obtained with openSol and is a pretty good box). The Tecra M10 is a supported platform. Your list of problems is puzzling since the M10 (NVIDIA version) is my workhorse portable system and I don't see any of the five problems [*] you mention on b130. (I've also run every build on this unit since 111b). [*] I do see a S/R problem if virtualization hardware support is enabled in the SBIOS, but this is not the default setting. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 128a was the latest fairly stable build
On 01/21/10 10:03 AM, Brian Ruthven - Sun UK wrote: Bruce wrote: 1) Progressivly longer boot times snv_111b 2.5 mins to login snv_128 4.5 mins to login A cold boot test on my M10 running b130: 10:20:40 power on 10:20:52 grub menu first appears 10:21:23 OSOL boot begins 10:22:24 login screen appears ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 128a was the latest fairly stable build
On 01/21/10 12:14 PM, Anon Y Mous wrote: [*] I do see a S/R problem if virtualization hardware support is enabled in the SBIOS, but this is not the default setting. Yes, but I would think that one of the main reasons for buying a Toshiba laptop with OpenSolaris pre-installed is to run a software stack that draws heavily from Sun's F.O.S.S. offerings, and probably the fourth most widely used piece of multi-platform Sun free open source software (after Java, MySQL, and OpenOffice) is VirtualBox, and I think it's safe to assume that most users are going to enable virtualization in the BIOS so that they can get better performance from their VirtualBox virtual machines. The bugs are being worked on so this isn't a permanent state of affairs. While not an ideal environment, 32 bit guest OSes work fine under VirtualBox without hardware virtualization enabled. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 128a was the latest fairly stable build
On 01/21/10 03:12 PM, Bruce wrote: Bruce wrote: 1) Progressivly longer boot times snv_111b 2.5 mins to login snv_128 4.5 mins to login A cold boot test on my M10 running b130: 10:20:40 power on 10:20:52 grub menu first appears 10:21:23 OSOL boot begins 10:22:24 login screen appears Fresh install, or updates ? Upgrades. Due to the need to redo the partition on the drive, I reloaded at b124. My grub menu: OpenSolaris 2009.06 opensolaris-b124 osol-125-nvidia osol-127 osol-128-195.22 osol-129 osol-129-195.22 osol-130-195.30 Each upgrade was done against the previous BE. As for the aforementioned DVD firmware upgrade, cdrecord -scanbus reports: scsibus7: 7,0,0 700) 'ATA ' 'Hitachi HTS72201' 'C74A' Disk 7,1,1 701) 'MATSHITA' 'DVD-RAM UJ870BJ ' '1.01' Removable CD-ROM FWIW, smbios -t SMB_TYPE_BIOS reports 3.00. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 128a was the latest fairly stable build
On 01/21/10 05:01 PM, Bruce wrote: I have a different DVD. hmmm, votes for I pull the DVD from the chassis and watch the results ? :-) I would also check the SBIOS settings for hardware virtualization (Virtualization Technology on page 1 - disabled on my M10) and Device Config on page 2 - Setup by OS on mine, plus any other setting you may have changed from the default. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 128a was the latest fairly stable build
On 01/13/10 07:40 AM, Mauro Mozzarelli wrote: 130: could not even see the screen as it was all dark white Which graphics? If NVIDIA and you had previously manually enabled compiz, try the workaround in: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6912450 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] nvidia driver not working
On 01/11/10 07:54 AM, Arun Tomar wrote: Hi! I got a new Nvidia card GeForce 9400 GT for my desktop. I installed the driver that i got from the nvidia site and create the xorg.conf file by running the command nvidia-xconfig. Now when i reboot the machine, it shows the progress bar and then the monitor just goes to the power saving mode. i'm not able to figure out the issue. kindly help me out. The output of /usr/bin/nvidia-SunOS-bug-report.sh is the best start. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Here's some more info for bugster CR 6913752
On 01/ 4/10 01:04 PM, andrew wrote: Is your Tecra M10 an OpenSolaris model with the nVidia graphics or the more common variant with Intel graphics? Mine has nVidia graphics and a build 130 install which was image-updated from build 125 doesn't come back up properly from suspend with VT disabled. Keyboard appears non-functional as is the graphics but I've not checked the network. NVIDIA graphics upgraded from b129 to b130. S3 S/R works fine on both 129 and 130 if VT is disabled in the SBIOS. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Here's some more info for bugster CR 6913752
On 01/ 4/10 02:59 PM, andrew wrote: Hmm that's odd. I wonder if it is because I'm booting it off an eSATA hard drive powered from the USB ports. What does powered mean? The Tecra M10 has an eSATA port on the left side. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Here's some more info for bugster CR 6913752
On 01/ 4/10 03:50 PM, andrew wrote: OK, I've installed OpenSolaris build 130 on the internal hard drive and suspend to RAM and resume both work absolutely fine with VT extensions disabled. Cool! If your external drive has an option to use a dedicated power supply, it would be useful to know if the issue is a problem with eSATA or power being shut off on the USB port. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] build 130 nonsense
On 12/30/09 08:01 AM, andrew wrote: My problem is that the print manager entry on the administration menu is now dead - nothing ever appears after clicking on it and there is no obvious way to get access to the GUI administration for printing. The novice user is therefore stuck with no obvious way to get printing going. See http://defect.opensolaris.org/bz/show_bug.cgi?id=13626 The CUPS GUI worked for me on b130 when setting up my HP printer: http://localhost:631/admin ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
