Re: [osol-discuss] DomU OS Image trials on Nevada Build 77
John Levon wrote: > On Sat, Dec 08, 2007 at 10:13:51AM +0800, Steven Sim wrote: > > >> CentOS actually gave me the initial linux boot up screen. However, after >> typing "linux text" for the installation, vmlinuz loaded and...the DomU >> then rebooted and went back to the original screen once more. >> > > I think this might be a known problem. The simplest solution is not to > use HVM - both CentOS and Fedora 8 can run para-virtualized. That is, > answer no here: > I have see a problem with Mandriva as well. Trying to boot the Mandriva install DVD in an HVM domU freezes the system at the bootloader screen requiring a poweroff. Regards, Moinak. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] DomU OS Image trials on Nevada Build 77
On Sat, Dec 08, 2007 at 10:13:51AM +0800, Steven Sim wrote: > CentOS actually gave me the initial linux boot up screen. However, after > typing "linux text" for the installation, vmlinuz loaded and...the DomU > then rebooted and went back to the original screen once more. I think this might be a known problem. The simplest solution is not to use HVM - both CentOS and Fedora 8 can run para-virtualized. That is, answer no here: > Would you like a fully virtualized guest (yes or no)? This will allow > you to run unmodified operating systems. yes One wrinkle is that they don't support install from CD-ROM (some Linux problem), so you'll need to do a net-install of some kind. regards john ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] DomU OS Image trials on Nevada Build 77
Hi All; I have receive quite a lot of very valuable assistance in this mailing list and I thought of giving something back. I have setup the Nevada build 77 running on xVM Hypervisor. It works. # uname -a SunOS solaris-devx 5.11 snv_77 i86pc i386 i86xpv The H/W is an Intel Core2 Quad CP (2.4 Ghz) with 4 Gbyte RAM and 4 x 320 Mbyte eSATA hard disks. The motherboard is a Gigabyte DS3 with Intel VT support turned on. # xm info host : solaris-devx release: 5.11 version: snv_77 machine: i86pc nr_cpus: 4 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2400 hw_caps: bfebfbff:20100800::0140:e3bd::0001 total_memory : 4094 free_memory: 784 xen_major : 3 xen_minor : 0 xen_extra : .4-1-xvm xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : Mon Oct 29 23:19:32 2007 -0700 13226:b0c4d9d28fee cc_compiler: gcc version 3.4.3 (csl-sol210-3_4-20050802) cc_compile_by : xen-discuss cc_compile_domain : opensolaris.org cc_compile_date: Mon Oct 29 23:20:11 PDT 2007 xend_config_format : 3 # prtdiag System Configuration: Gigabyte Technology Co., Ltd. P35-DS3 BIOS Configuration: Award Software International, Inc. F5 08/13/2007 Processor Sockets Version Location Tag -- Intel(R) Core(TM)2 Quad CP Socket 775 Memory Device Sockets TypeStatus Set Device Locator Bank Locator --- -- --- --- unknown in use 0 A0 Bank0/1 unknown in use 0 A1 Bank2/3 unknown in use 0 A2 Bank4/5 unknown in use 0 A3 Bank6/7 On-Board Devices = Upgradeable Slots ID StatusType Description --- - 0 available PCI PCI 1 available PCI PCI 2 available PCI PCI 0 available PCI PCI I've tried Windoze and very much thanks to Moinak Ghosh and friends I have now gotten Windoze running as a DomU. Thanks to John Levon for his pointer to use "xm new" instead of "xm create" From John's email, I gather that the xm create / xm new sub commands would be deprecated soon and that the recommended method for creation a DomU would be to use virt-install. But virt-install did not allow me to further customize the DomU configuration so I went back to the Python script. For anybody who is interested, the script is shown below.. # cat winxp2.py kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' name = "winxp1" vcpus = 1 memory = 1056 shadow_memory = 8 kernel = '/usr/lib/xen/boot/hvmloader' builder = 'hvm' vif = [ 'mac=00:16:3e:1b:f1:92,type=ioemu' ] disk = ['file:/export/home/hvm1/windoze-raw,hdc,w', 'file:/export/home/admin/iso-images/xp2/e-xp2ja2k7.iso,hda:cdrom,r'] sdl = 0 vnc = 5900 vncconsole = 1 vnclisten="0.0.0.0" boot = 'd' on_shutdown = "destroy" on_reboot = "restart" on_crash = "restart" device_model = '/usr/lib/xen/bin/qemu-dm' usb=1 usbdevice='tablet' serial='null' soundhw='sb16' XML dump... # virsh dumpxml winxp1 winxp1 90f32adda19bfcc29e350ceb32fff057 hvm /usr/lib/xen/boot/hvmloader 1097728 1081344 1 destroy restart restart /usr/lib/xen/bin/qemu-dm I was wondering whether we could have the <> tag syntax?? The XML DTD perhaps? I've also tested the follow OS but they didn't quite work outnothing on vncviewer, just a blank screen. Fedora8 CentOS CentOS actually gave me the initial linux boot up screen. However, after typing "linux text" for the installation, vmlinuz loaded and...the DomU then rebooted and went back to the original screen once more. The following virt-install syntax was used.. #virt-install --name=fedora8 --ram 768 --cdrom //export/home/admin/iso-images/Fedora8/Fedora-8-i386-DVD.iso --os-type=linux --os-variant=fedora6 --file /dev/zvol/dsk/datahome/fedora8 --vnc Attempt to create with the -nographics option also failed with the following error... #virt-install --name=fedora8 --ram 768 --cdrom //export/home/admin/iso-images/Fedora8/Fedora-8-i386-DVD.iso --os-type=linux --os-variant=fedora6 --file /dev/zvol/dsk/datahome/fedora8 --nographics Would you like a fully virtualized guest (yes or no)? This will allow you
Re: [osol-discuss] [website-discuss] Linking to older SXCE releases on the download page
John Levon wrote: > On Thu, Dec 06, 2007 at 12:54:51PM -0800, Stephen Lau wrote: > >> No it's automatic. I had a script that did it that I handed off to the >> ON GK team. The problem is the ON builds are published before the SXCE >> releases are. You could put the link in pre-emptively, but then they'd >> be dead/broken links for about a week. > > And there'd be plenty of email too. > >> Going back a week later to update them and generate new text is >> possible; but again, someone has to trigger the script. > > Do you know who owns this? Steve wrote the original script at looks for a new release on the SDLC and updates the download page link. I think the SDLC keeps the last 4 builds on the site, but I'll check how far back they go and how we can make it easier to find them. Derek > > cheers > john > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > -- Derek Cicero Program Manager Solaris Kernel Group, Software Division ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Portable UPnP SDK : build success
> Hi > > Just managed to build mediatomb and currently testing > it. > i planned to make full independ installation package > , one pkg. > But currently been too busy and lack of time. Hi, did you manage to make a package out of it finally ? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hotplugging sata drives
Jürgen Keil <[EMAIL PROTECTED]> wrote: > > I just added a sata disk to a running system and the > > kernel messages show: > > > ... > > the sata driver seems to be OK at low level. > > There is however no new device in /devices/. Is this > > a known issue? > > Did you already use cfgadm_sata(1M)? > > To make the hotplugged s-ata disk usable, you would use > something like > ># cfgadm -l ># cfgadm -y -c connect sata1/1 ># cfgadm -y -c configure sata1/1 OK, I was asuming that sata works similar to hotplugged SCSI drives that may just need a call to devfsadm(1) and/or disks(1). Not it is too late and I need to reboot the machine without the disk on Monday to check. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Intel GB NICs (82573 PCI-E) not working
Jürgen Keil wrote: > > Did you try "ifconfig -a plumb" ? > > With Solaris, network interfaces are not shown until > you "plumb" them... Jürgen, Thanks for the reply. Yes, I tried "ifconfig -a plumb". It didn't change anything; I still just see the two lo0 devices (IPv4 & IPv6) > >> prtconf -pv shows two Ethernet controllers: >> >> 'pci8086,108c' >> ... >> vendor-id: 8086 >> device-id: 108c > > Seem to be known, at least with ~ snv_80: > > % grep e1000g /etc/driver_aliases > ... > e1000g "pci8086,108c" > ... > >> 'pci8086,109a' >> ... >> vendor-id: 8086 >> device-id: 109a > > The second one appears to be known, too: > > % grep e1000g /etc/driver_aliases > ... > e1000g "pci8086,109a" > ... Yes, both devices are in there. But the driver is not loaded. I'm at a lost to understand why. I've also got a Supermicro PCI-X 8-port SATA card plugged in (SAT2-AOC-MV8) with 8 drives connected. None of those devices are visible to the O/S either. I don't know if this is related, or just coincidental. Why is nothing ever easy!!! R. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GUI doesn't work
On Dec 7, 2007 2:44 PM, Aubrey Li <[EMAIL PROTECTED]> wrote: > Or please guide me a right mailing list to ask. > Let's make things even cooler and weirder shall we? Yesterday at NLOSUG we all got the SXCE 76 build on DVD (thanks for the cool evening by the way, I know for sure Casper is on this list). So, I installed the DVD on my laptop (HP Pavilion dv8000 series with Nvidia Go 5600. Installation went and directly after this the weirdness started. 1) When I choose option 1 (Solaris Express community edition build 76) the system boots, I see X being loaded, I see the nvidia logo and then the root window, as if I started Xorg by typing /usr/X11/bin/X. 2) When I choose the xVM option from grub, my system works like a charm, I can log in to JDS, the whole lot. In my opinion this means my hardware is fine and functional and that this is really something within this build that doesn't play nice. As always, if I can help debug, let me know, just give me a hint or two of what commands I should try. Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GUI doesn't work
On Dec 7, 2007 8:15 PM, Patrick Ale <[EMAIL PROTECTED]> wrote: > > > On Dec 7, 2007 2:44 PM, Aubrey Li <[EMAIL PROTECTED]> wrote: > > > Or please guide me a right mailing list to ask. > > > > I didn't see it mentioned in this thread so I assume it wasn't done already. I filed a bug five minutes ago regarding my current experience with a clean SXCE76 build. Let's see what comes out ;-) Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Intel GB NICs (82573 PCI-E) not working
> I've just got a couple of Supermicro PDSME boards to > build a couple of Solaris boxes to use as NAS devices. > > These boards have 2 x Intel single-port 82573 PCI-E > Gigabit Ethernet Controllers. > > I've installed SXCE b77 on one of these boards and no > driver seems to be loaded for these NICs. Did you try "ifconfig -a plumb" ? With Solaris, network interfaces are not shown until you "plumb" them... > prtconf -pv shows two Ethernet controllers: > > 'pci8086,108c' > ... > vendor-id: 8086 > device-id: 108c Seem to be known, at least with ~ snv_80: % grep e1000g /etc/driver_aliases ... e1000g "pci8086,108c" ... > 'pci8086,109a' > ... > vendor-id: 8086 > device-id: 109a The second one appears to be known, too: % grep e1000g /etc/driver_aliases ... e1000g "pci8086,109a" ... This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hotplugging sata drives
> I just added a sata disk to a running system and the > kernel messages show: > ... > the sata driver seems to be OK at low level. > There is however no new device in /devices/. Is this > a known issue? Did you already use cfgadm_sata(1M)? To make the hotplugged s-ata disk usable, you would use something like # cfgadm -l # cfgadm -y -c connect sata1/1 # cfgadm -y -c configure sata1/1 # zpool import This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Nevada and VMware Woes
On 30 Nov 2007, at 05:14, Steven Stallion wrote: > > Any ideas if VMware/Sun is aware of the issue and is working to > resolve > it? I have not decided yet whether sacrificing 64bit support is worth > switching over to Nevada from Solaris 10, so well see. Yes, VMware are aware of the issue and I believe they actually had a fix for it prior to the Fusion 1.0 release, but deemed it too risky to include. I guess it was still too risky for 1.1 :/ Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Laptop testing OpenSolaris (Indiana) on ODM laptops
On 29 Nov 2007, at 17:01, W. Wayne Liauh wrote: >> FWIW, I'm not interested :) >> >> Cheeri, >> Calum. >> > > Even if it is Solaris-based and/or Sun-licensed? :-) Well, maybe if the Sun licensing meant I got a free one :) Otherwise, that form factor really isn't my cup of tea at all. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to avoid several "access restricted" files from indexing
I apologize. I must have accidentally cc'ed to the wrong dl. This question pertains to OpenGrok and not OpenSolaris. I apologize again. Thanks, Yeshanth On Dec 7, 2007 6:15 AM, Darren J Moffat <[EMAIL PROTECTED]> wrote: > yeshanth wrote: > > I am trying to index a source code tree and there are several files that > are "access restricted". So as a result, I get the indexing to stop with > Exceptions(Access is Denied). I tried using the -i option and it does work. > But the same option is tedious if I have around 65 files that I need to > omit with -i option. > > > > Is there any option/way that I can use/approach that would help me skip > these "access is denied" from getting indexed?? > > > > Any help is appreciated. > > The -i option to what ? > > What are you indexing with and why is this relevant to OpenSolaris ? > > -- > Darren J Moffat > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OpenSolaris Build Times on "desktop" supercomputers
For someone compiling current OpenSolaris kernels, I was looking at current OpenSolaris build times on several high-end servers. Non-clustered single server instance: 1. 32-core test server (2.93 Ghz, eight X7350 quad-core CPUs, 64GB RAM) 2. 8-core Sun SPARC Enterprise T5220 Server (1 x 1.4 GHz UltraSPARC T2 8-Core, 64 GB RAM, 64 threads) The proposed effort was to keep the FULL OpenSolaris kernel build times <=55 minutes (based on real time scores) for BOTH architectures (x86-64 and SPARC). We can now have 'desktop' supercomputers the size of common household microwave ovens that can fully compile current OpenSolaris kernels in under one hour. ~ Ken Mays Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] newly created DomU entry in xm list disappears after shutdown!
On Fri, Dec 07, 2007 at 09:02:42PM +0530, Moinak Ghosh wrote: > I think Steven already installed it via virt-install. However he wanted to > define the following properties for the Windows domU: > > usb=1 > usbdevice='tablet' > > to work around a mouse lag problem. All docs state to use a python > script. > Is there a way to do that using the xml format ? I'm not sure. Setting parameters in general isn't very pleasant at the moment, sorry about that. regards john ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] newly created DomU entry in xm list disappears after shutdown!
John Levon wrote: > On Fri, Dec 07, 2007 at 10:54:11PM +0800, Steven Sim wrote: > > >> I can get back the previous state by doing >> >> #xm create -c -f /export/home/admin/iso-images/xp2/winxp2.py >> > > Try using: > > xm new -f ...py > > instead. > > BTW, is there a reason you're not using virt-install for creating the > domU? This is the supported way. > I think Steven already installed it via virt-install. However he wanted to define the following properties for the Windows domU: usb=1 usbdevice='tablet' to work around a mouse lag problem. All docs state to use a python script. Is there a way to do that using the xml format ? Regards, Moinak. > regards > john > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] newly created DomU entry in xm list disappears after shutdown!
On Fri, Dec 07, 2007 at 10:54:11PM +0800, Steven Sim wrote: > I can get back the previous state by doing > > #xm create -c -f /export/home/admin/iso-images/xp2/winxp2.py Try using: xm new -f ...py instead. BTW, is there a reason you're not using virt-install for creating the domU? This is the supported way. regards john ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Intel GB NICs (82573 PCI-E) not working
Has nobody got any idea about this? R. Robin Bowes wrote: > Hi, > > I've just got a couple of Supermicro PDSME boards to build a couple of > Solaris boxes to use as NAS devices. > > These boards have 2 x Intel single-port 82573 PCI-E Gigabit Ethernet > Controllers. > > I've installed SXCE b77 on one of these boards and no driver seems to be > loaded for these NICs. > > prtconf -pv shows two Ethernet controllers: > > Node 0x20 > assigned-addresses: > 82050010..ed80..0002.81050018..8000..0020 > reg: > 0005.....02050010....0002.01050018....0020 > compatible: 'pciex8086,108c.15d9.108c.3' + > 'pciex8086,108c.15d9.108c' + 'pciex8086,108c.3' + 'pciex8086,108c' + > 'pciexclass,02' + 'pciexclass,0200' + 'pci8086,108c.15d9.108c.3' + > 'pci8086,108c.15d9.108c' + 'pci15d9,108c' + 'pci8086,108c.3' + > 'pci8086,108c' + 'pciclass,02' + 'pciclass,0200' > model: 'Ethernet controller' > power-consumption: 0001.0001 > devsel-speed: > interrupts: 0001 > subsystem-vendor-id: 15d9 > subsystem-id: 108c > unit-address: '0' > class-code: 0002 > revision-id: 0003 > vendor-id: 8086 > device-id: 108c > pcie-capid-pointer: 00e0 > pcie-capid-reg: 0001 > name: 'pci15d9,108c' > > Node 0x21 > assigned-addresses: > 82060010..ed90..0002.81060018..9000..0020 > reg: > 0006.....02060010....0002.01060018....0020 > compatible: 'pciex8086,109a.15d9.109a.0' + > 'pciex8086,109a.15d9.109a' + 'pciex8086,109a.0' + 'pciex8086,109a' + > 'pciexclass,02' + 'pciexclass,0200' + 'pci8086,109a.15d9.109a.0' + > 'pci8086,109a.15d9.109a' + 'pci15d9,109a' + 'pci8086,109a.0' + > 'pci8086,109a' + 'pciclass,02' + 'pciclass,0200' > model: 'Ethernet controller' > power-consumption: 0001.0001 > devsel-speed: > interrupts: 0001 > subsystem-vendor-id: 15d9 > subsystem-id: 109a > unit-address: '0' > class-code: 0002 > revision-id: > vendor-id: 8086 > device-id: 109a > pcie-capid-pointer: 00e0 > pcie-capid-reg: 0001 > name: 'pci15d9,109a' > > > Now, it is my understanding that these NICs should be supported > "out-of-the-box" by the e1000g driver, but I could be wrong. > > Any idea how to get my NICs working? > > Thanks, > > R. > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] newly created DomU entry in xm list disappears after shutdown!
Hi! I've Nevada build 77 running on xVM Hypervisor with Nevada as Dom0. # xm info host : solaris-devx release: 5.11 version: snv_77 machine: i86pc nr_cpus: 4 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2400 hw_caps: bfebfbff:20100800::0140:e3bd::0001 total_memory : 4094 free_memory: 1 xen_major : 3 xen_minor : 0 xen_extra : .4-1-xvm xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : Mon Oct 29 23:19:32 2007 -0700 13226:b0c4d9d28fee cc_compiler: gcc version 3.4.3 (csl-sol210-3_4-20050802) cc_compile_by : xen-discuss cc_compile_domain : opensolaris.org cc_compile_date: Mon Oct 29 23:20:11 PDT 2007 xend_config_format : 3 With valued assistance from Moinak Ghosh, I manage to create a properly running Windows DomU. # virsh dumpxml winxp1 winxp1 a3011e029cde5c88bb74c6a160dd727e hvm /usr/lib/xen/boot/hvmloader 1097728 1081344 1 destroy restart restart /usr/lib/xen/bin/qemu-dm # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 2948 4 r- 2694.8 winxp1 8 1064 1 -b484.3 I eventually shutdown my computer and when I re-started it hours later, xm list showed no winxp1 DomU! !! Is this normal?? I then re-created the DomU from scratch. And then I noticed something else... Everytime I "shutdown" my Windows DomU I noticed the relevant entry disappears from xm list! I can get back the previous state by doing #xm create -c -f /export/home/admin/iso-images/xp2/winxp2.py But is this the correct way? Should it be #xm start winxp1 Something is wrong here.. I had thought it would be like Solaris Zonesthe zone is reflected even when shutdown using zoneadm... Warmest Regards Steven Sim Fujitsu Asia Pte. Ltd. _ This e-mail is confidential and may also be privileged. If you are not the intended recipient, please notify us immediately. You should not copy or use it for any purpose, nor disclose its contents to any other person. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hotplugging sata drives
Joerg Schilling schrieb: > So the sata driver seems to be OK at low level. > There is however no new device in /devices/. Is this a known issue? I don't know if it is intended that way. But after plugging the SATA disk I searched for a connected but unconfigured port with cfgadm -l then enabled that port with cfgadm -c configure sataX/Y Daniel ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Cisco VPN Client for Solaris x86, anyone?
If you are not aware, Cisco currently doesn't release a version of their VPN client for Solaris on x86 platforms (they do have Sparc). I'm sure probably quite a few of you out there work within companies that use Cisco VPN servers, and would find a client for the Solaris platform to be useful. I'm filing a request for product enhancement with Cisco for this functionality. I was wondering if anybody might like to include themselves with my request? My request will read as follows: Solaris/OpenSolaris has a rapidly growing userbase. Many of its users work within organizations that utilize Cisco VPN servers, and would find the ability to connect within the Solaris platform to be immensely useful. Please consider making a Solaris x86 version of the Cisco VPN client software available. Thank you for your time and consideration of this request- In case any of you haven't used the Cisco VPN client, it's a very smart piece of software and well thought out. They currently have version support for Mac OS X from 10.3 through 10.5, Windows 98 through Vista, Solaris on Sparc (only), and "Linux". Obviously, they've demonstrated a willingness to make broad platform availability of their software. I'm hoping to push them to include Solaris x86 in the fold. The lack of this software is one key item against my total adoption of Solaris for some remote users. Thanks for your time and thoughts- John Tracy This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GUI doesn't work
Or please guide me a right mailing list to ask. Thanks, -Aubrey On Dec 7, 2007 9:22 PM, Aubrey Li <[EMAIL PROTECTED]> wrote: > On Dec 6, 2007 4:48 PM, Aubrey Li <[EMAIL PROTECTED]> wrote: > > The problem is gone after backward to bfu b73(my original installation). > > Should I file a bug? > > > > Thanks, > > -Aubrey > > > > A little more details about this issue. > It seems to have nothing to do with X-windows. > I tried to disable the GUI by > #/usr/dt/bin/dtconfig -d > After reboot, > > the system boot at > "read zfs config done"(something like that, I can't remember exactly) > a few minutes later(10 minutes??) > > I got a chance to enter my username and password. > And another a few minutes later(10 minutes??), > shall comes out. > > I have to wait about 30 minutes every time I reboot the system. > The problem is gone after I downgrade to b73. (BFU) > > Any suggestions are really appreciated! > > Thanks, > -Aubrey > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GUI doesn't work
On Dec 6, 2007 4:48 PM, Aubrey Li <[EMAIL PROTECTED]> wrote: > The problem is gone after backward to bfu b73(my original installation). > Should I file a bug? > > Thanks, > -Aubrey > A little more details about this issue. It seems to have nothing to do with X-windows. I tried to disable the GUI by #/usr/dt/bin/dtconfig -d After reboot, the system boot at "read zfs config done"(something like that, I can't remember exactly) a few minutes later(10 minutes??) I got a chance to enter my username and password. And another a few minutes later(10 minutes??), shall comes out. I have to wait about 30 minutes every time I reboot the system. The problem is gone after I downgrade to b73. (BFU) Any suggestions are really appreciated! Thanks, -Aubrey ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Hotplugging sata drives
Hi, I just added a sata disk to a running system and the kernel messages show: Dec 7 13:53:35 unknown port 1: link established Dec 7 13:53:35 unknown sata: [ID 801593 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1028,[EMAIL PROTECTED],2: Dec 7 13:53:35 unknown SATA device detected at port 1 Dec 7 13:53:35 unknown sata: [ID 663010 kern.info] /[EMAIL PROTECTED],0/pci1028,[EMAIL PROTECTED],2 : Dec 7 13:53:35 unknown sata: [ID 761595 kern.info] SATA disk device at port 1 Dec 7 13:53:35 unknown sata: [ID 846691 kern.info] model WDC WD5000AAKS-75YGA0 Dec 7 13:53:35 unknown sata: [ID 693010 kern.info] firmware 12.01C02 Dec 7 13:53:35 unknown sata: [ID 163988 kern.info] serial number WD-WCAS82941518 Dec 7 13:53:35 unknown sata: [ID 594940 kern.info] supported features: Dec 7 13:53:35 unknown sata: [ID 981177 kern.info] 48-bit LBA, DMA, Native Command Queueing, SMART, SMART self-test Dec 7 13:53:35 unknown sata: [ID 643337 kern.info] SATA Gen2 signaling speed (3.0Gbps) Dec 7 13:53:35 unknown sata: [ID 349649 kern.info] Supported queue depth 32 Dec 7 13:53:35 unknown sata: [ID 349649 kern.info] capacity = 976773168 sectors So the sata driver seems to be OK at low level. There is however no new device in /devices/. Is this a known issue? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to avoid several "access restricted" files from indexing
yeshanth wrote: > I am trying to index a source code tree and there are several files that are > "access restricted". So as a result, I get the indexing to stop with > Exceptions(Access is Denied). I tried using the -i option and it does work. > But the same option is tedious if I have around 65 files that I need to omit > with -i option. > > Is there any option/way that I can use/approach that would help me skip these > "access is denied" from getting indexed?? > > Any help is appreciated. The -i option to what ? What are you indexing with and why is this relevant to OpenSolaris ? -- Darren J Moffat ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Install of nv77x86 onto USB drives gives SCSI transport errors @ newfs time
Hi, Noel Milton Vega wrote: > Hi: > > I gave up attempting to install Solaris10 nv77 on my Dell XPS-720 SATA drives > (see about 6 posts ago for problem there - basically the nv_sata driver > wouldn't > recognize directly connected SATA drives). > > Instead I decided to install Solaris10 nv77 onto 300GB Seagate drives > connected > to my Dell XPS-720 via USB interfaces (plural because I have two of these > drives, > model ST3300631A). I've gone the opposite direction - moving from USB storage (for backup in my case) to eSATA because USB kept giving transport errors. In my case, also using nv_sata now that it is in but previously in non-native mode, my SATA disks have been happily regognised provided I configure them in the Nvidia RAID BIOS option (as JBODs). > I proceed through the installation menus but when suninstall initiates > mkfs/newfs > during the "Creating filesystems" phase, it hangs on the first slice > (c0t0d0s0). > But it gave no indication as to why. > > So I reboot my machine and direct the menu to take me to a SHELL > prompt. From there I can do an fdisk, format, and newfs, but only > intermittantly... Problem? SCSI transport errors "tran_err" or "timeout". > So it wasn't the installer. > > I attempted newfs on both of these drives, which are connected to different > USB ports. Both fail... newfs starts but immediately hangs due to these > SCSI errors. > > I checked the cabling, and they are secure. The length of the cables > themselves > are the typical lengths (about 4 feet). > > I don't get it. > > I know I installed Solaris (nv49 or something) on these same two disks > before, but that was when they were attached to my laptop. > > Any ideas? Again the problem is SCSI transport errors I guess triggered by > I/O access to these USB attached drives. Thanks in Advance. While others have reported success on usb mass storage, I have a litany of failures. I have used two different Seagate products (one USB, one USB/eSATA), a bus-powered Acomdata USB/Firewire device, another bus-powered generic enclosure on a variety of machines (U40 M2, Tyan Thunder K8W whitebox, Acer Ferrari 4005, Acer Aspire, Gigabyte K8NSLI whitebox) and I've found USB to be extremely patchy and to hang as you describe. Dtrace shows usb bulkonly device resets occuring, sometimes managing to get things going again but not always. I am backing up via zfs send | zfs receive to the external device. USB devices do not work reliably, and using firewire on the one device was worse. So I've switched to eSATA and it's perfect. The usual recommendation is to edit /kernel/drv/scsa2usb.conf and add reduced-cmd-support for your device type. You can use echo "::prtusb" | mdb -k to see the vid,pid of your device and add that, or just do attribute-override-list="vid=* reduced-cmd-support=true"; in scsa2usb.conf, and if it works then get more specific for your particular device. I've tried this with all devices and I've got to say that no combination worked reliably. Of course editing this file for install is going to be a challenge - I'm not sure if there is something you can do via kmdb to force reduced command support for all devices. I did log a bug on this way back around build 55. At the time it was thought that the one drive I had then (a Seagate external USB disk) had dodgy electronics at the USB<->IDE interface. That may be so, but then it seems that would apply to the other devices, too. I've tried every few builds since and sometimes get success for a whole backup, but then at the next try it fails again. More often than not it fails, so I threw in the towel and went to eSATA. I did also dig out some old builds around 45'ish and did get successful backups there, but did not repeat often enough to be confident and also did not have all builds in order to try to narrow the behaviour to a build it was introduced in. Gavin ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
