[osol-discuss] Blastwave
p...@opensolaris:~/Документы# pkgadd -d pkgutil_i386.pkg The following packages are available: 1 CSWpkgutil pkgutil - Installs Solaris packages easily (i386) 1.5,REV=2009.04.09 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: all Processing package instance from pkgutil - Installs Solaris packages easily(i386) 1.5,REV=2009.04.09 cpio: Unexpected end-of-archive encountered. 1 errors pkgadd: ERROR: attempt to process datastream failed - process failed, exit code 1 pkgadd: ERROR: unable to unpack datastream Installation of failed (internal error). No changes were made to the system. p...@opensolaris:~/Документы# I wanted to install Blastwave? but there is failure. Can you explain me step by step what to do? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] upgrading Ultra 20 to snv_111
Bill Shannon wrote: In the announcement of snv_111 it says: 6811922 PCIE init err info failed BDF 0x0 on snv_109 (Ultra 20 M2) Ultra 20 M2 systems may not boot after being upgraded or installed with build 109. Work-around: Upgrade the system's firmware to at least revision 1.52. Updated firmware can be obtained from http://www.sun.com/desktop/workstation/ultra20/downloads.jsp I have an Ultra 20, not an Ultra 20 M2, does that mean this doesn't apply? If it does apply, can someone tell me how to determine what my firmware version is, and how to upgrade it if it's too old? I found the download referenced above, but it comes with no instructions at all, and a web search didn't turn up anything. you can use smbios, or just at power-on, press F2 to enter the bios's setup (not sure if it is F2, look carefully at the messages at power-on) then burn a cd with the iso you downloaded from the website, and follow the instructions. i also own an ultra20, and i can't upgrade the bios because it makes the machine noisier. Are you happy with your's? is it quiet? gerard ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Packages installation
Hello guys..I m a newbie to OpenSolaris.. I was working on installing packages from Package Manager. I added Blastwave Repository.. Then i installed mplayer , ffmpeg codecs and GStreamer Plugins.. But the GStreamer codecs are not recognised by Rhythm Box Music player.. It still says "GStreamer plugin not found".. Please help me in this regard.Is this because, packages installed via Blastwave are installed in /opt/csw .. Is there any way to make Rhythm Box Music Player recognise the plugins.. Please help me out.. But if i install any package via opensolaris.org repos it is added to applications menu.. whereas mplayer that was installed via blastwave was not added to applications menu.. It is present in /opt/csw/bin and not in /opt/bin. .. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Setup VNC on OpenSolaris
Thanks, I just tried on OpenSolaris nv112, but somehow, does not work sigh. We do not use OpenSolaris 2008.11. Tom -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Setup VNC on OpenSolaris
Hi, I used similar ways before and just tried yours, it should work on earlier version but doesn't work on nv112 unfortunately. Sigh. Tom -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Reboots of nv111
[i]Has this system experienced other odd failures?[/i] None aside of http://www.opensolaris.org/jive/thread.jspa?threadID=100180&tstart=15 Could this explain those reboots? According to the explanation in that thread, not. On the other hand, since I clear-ed and scrub-ed it; and upgraded to 112, those reboots have not happened again. Thanks for your efforts, Uwe -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Analysis: Why Linux prospers, Solaris dies?
In my opinion OpenSolaris is to difficult OS for average computer user . Lot of thing must be configurated in shell or configuration files . To faster progression in market of desktops osol should have more graphical configurators , more user friendly shell esier instaling/packaging system like *.PBI from PCBSD and more programs :) But I belive on Opensolaris becouste development rate of this system is very fast and Osol become multioperational system Like Debian Or NetBsd :) I'im waitng impatiently for 2009.06 release :) Ps. Is possible install Polaris on PS3 console withouth Emulation ? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 680i Chipset Support?
The Big T wrote: Just wanted to check if the 680i SLI Chipset is supported by OpenSolaris... Specifically for the Asus P5N32-E SLI. Having a hard time digging anything up on this chipset in reguards to Solaris, so any light anyone can shed on it would be great before i bother putting this machine together... or if i need to find another motherboard. My EVGA nForce 680i SLI motherboard works fine, so you shouldn't have any issues with the core chipset. The normal concerns are the PHY and audio chips. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] 680i Chipset Support?
Just wanted to check if the 680i SLI Chipset is supported by OpenSolaris... Specifically for the Asus P5N32-E SLI. Having a hard time digging anything up on this chipset in reguards to Solaris, so any light anyone can shed on it would be great before i bother putting this machine together... or if i need to find another motherboard. Thanks. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Reboots of nv111
John Martin wrote: I would like access to this core file. The core file reveals an odd failure during device interrupt service. > ::status debugging crash dump vmcore.4 (64-bit) from solu operating system: 5.11 snv_111 (i86pc) panic message: BAD TRAP: type=e (#pf Page fault) rp=ff0007899a30 addr=5ea228138 occurred in module "nvidia" due to an illegal access to a user address dump content: kernel pages only > ::regs %rax = 0xbe42ead0 %r9 = 0x %rbx = 0x %r10 = 0xff0007899a60 %rcx = 0x %r11 = 0xfb827e60 dispatch_hardint %rdx = 0x %r12 = 0x0006 %rsi = 0x0006 %r13 = 0x %rdi = 0xff01be42ead0 %r14 = 0xff01bafd5000 %r8 = 0xff01be42ead0 %r15 = 0xff0007899bb0 %rip = 0xf7f39b7f _nv004189rm+0x1b %rbp = 0xff01bafd8000 %rsp = 0xff0007899b20 %rflags = 0x00010297 id=0 vip=0 vif=0 ac=0 vm=0 rf=1 nt=0 iopl=0x0 status= %cs = 0x0030%ds = 0x004b%es = 0x004b %trapno = 0xe %fs = 0x%gs = 0x01c3 %err = 0x0 > f7f39b7f::dis _nv004189rm:pushq %r13 _nv004189rm+2: pushq %r12 _nv004189rm+4: pushq %rbx _nv004189rm+5: movq %rdi,%r8 _nv004189rm+8: movl %esi,%r12d _nv004189rm+0xb:movl %edx,%ebx _nv004189rm+0xd:movl %ecx,%r13d _nv004189rm+0x10: cmpl $0x5a,%esi _nv004189rm+0x13: ja +0x111 <_nv004189rm+0x12a> _nv004189rm+0x19: movl %esi,%eax _nv004189rm+0x1b: jmp*0xf80b2ab8(,%rax,8) 0xf80b2ab8+(0xbe42ead0*8) does calculate to the fault address (truncated to 64 bits) 0x10005EA228138. However, the register %eax should have a value of 0x6, not 0xbe42ead0 due to the instruction that immediately preceded the faulting jump instruction (movl %esi,%eax). Possible causes: 1. Faulty hardware. Has this system experienced other odd failures? 2. Hardware trap handler not saving/restoring the rax register properly. This interrupt delivery is at IPL 9. When I get some time, I will scan the code for higher priority handlers to see if anything obvious jumps out at me. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] migrando a opensolaris 2008.11
Alejandro Sánchez Martínez wrote: Instale la virtual box, pero lo más seguro es que me haya equivocado al seleccionar el SO base, por lo que me marca un error. Para volver a empezar, desinstalé la virtual box y después la volví a instalar; sin embargo aparecen las anteriores máquinas virtuales que había instalado, con sus respectivos errores. ¿Cómo se podrá corregir esto? http://www.opensolaris.org/jive/thread.jspa?threadID=87892&tstart=0 -- Shawn Walker ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] migrando a opensolaris 2008.11
Instale la virtual box, pero lo más seguro es que me haya equivocado al seleccionar el SO base, por lo que me marca un error. Para volver a empezar, desinstalé la virtual box y después la volví a instalar; sin embargo aparecen las anteriores máquinas virtuales que había instalado, con sus respectivos errores. ¿Cómo se podrá corregir esto? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Kingston USB does not show/automount
> There is no detail in that bugid 6809241, can you > submit a bugid, and refernce the bug id as so this > can have a better chance of getting addressed also > make a note to get a hold of your for more info as > well. and include the fstyp command from above. > # Rem, For usb try include this for the Kingstop 8g > sub thumb drive: > echo " REM Unplug all USB devices, else you get busy > error, clear log:." > sleep 10 > echo "::usba_clear_debug_buf" |mdb -wk > echo " Plug in your usb device you are having issues > with." > sleep 10 > echo "::usba_debug_buf" |mdb -k > echo "::usba_device -v"|mdb -k > echo "::interrupts" | mdb -k > echo "::prtusb" | mdb -k > echo "::status" | mdb -k I don't think this is a usb / hardware / driver problem. It's a problem with the Solaris pcfs filesystem support. Seems as if pcfs filesystems don't automount when they contain spaces in the pcfs partition boot sector and no volume label entry in the pcfs root directory. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Kingston USB does not show/automount
There is no detail in that bugid 6809241, can you submit a bugid, and refernce the bug id as so this can have a better chance of getting addressed also make a note to get a hold of your for more info as well. and include the fstyp command from above. # Rem, For usb try include this for the Kingstop 8g sub thumb drive: echo " REM Unplug all USB devices, else you get busy error, clear log:." sleep 10 echo "::usba_clear_debug_buf" |mdb -wk echo " Plug in your usb device you are having issues with." sleep 10 echo "::usba_debug_buf" |mdb -k echo "::usba_device -v"|mdb -k echo "::interrupts" | mdb -k echo "::prtusb" | mdb -k echo "::status" | mdb -k -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
