[OpenIndiana-discuss] Quadro 600 No Joy - Updated
Greetings All: I explored this a bit more. Got rid of the glx complaints by bumping /usr/X11 to top listing in "Files" section. Also installed xtsol, just to eliminate as even remote possibility. Only WW remaining in Xorg.0.log is now: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support EE's output is now limited to following: (EE) Feb 27 06:32:01 NVIDIA(0): Failed to initialize the NVIDIA graphics device! (EE) Screen(s) found, but none have a usable configuration. Trying to increment logging via startx -logverbose n doesn't provide any additional verbiage. Console output does generate following warning: gfx_private:WARNING:gfxp_vgatext: can't find reg entry for registers. Minimal xorg.conf consists of: Section "Files" ModulePath "/usr/X11/lib/modules/" ModulePath "/usr/lib/xorg/modules/amd64" FontPath "catalogue:/etc/X11/fontpath.d" EndSection Section "Device" Identifier "Card0" Driver "nvidia" EndSection Full text of Xorg.0.log follows: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: SunOS 5.11 i86pc Current Operating System: SunOS io 5.11 oi_148 i86pc Build Date: 06 September 2010 07:48:44PM Solaris ABI: 64-bit Current version of pixman: 0.18.4 Before reporting problems, check http://openindiana.org/consolidation/xnv to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 27 06:31:56 2011 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |-->Screen "Default Screen Section" (0) (**) | |-->Monitor "" (==) No device specified for screen "Default Screen Section". Using the first device section listed. (**) | |-->Device "Card0" (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. (==) Disabling SIGIO handlers for input devices (==) Automatically adding devices (==) Automatically enabling devices (**) FontPath set to: catalogue:/etc/X11/fontpath.d, catalogue:/etc/X11/fontpath.d (**) ModulePath set to "/usr/X11/lib/modules/,/usr/lib/xorg/modules/amd64" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. (II) Loader magic: 628150 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 2 (--) PCI: (0:1:5:0) 1002:4752:: ATI Technologies Inc Rage XL rev 39, Mem @ 0xfc00/16777216, 0xfdfff000/4096, I/O @ 0xac00/256, BIOS @ 0x/65536 (--) PCI:*(0:5:0:0) 10de:0df8:10de:0835 nVidia Corporation rev 161, Mem @ 0xfa00/16777216, 0xc800/134217728, 0xd600/33554432, I/O @ 0x6c00/128, BIOS @ 0x/65536 (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/X11/lib/modules/extensions/NVIDIA/amd64/libglx.so (II) Module glx: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Server Extension (II) NVIDIA GLX Module 256.44 Thu Jul 29 02:25:12 PDT 2010 (II) Loading extension GLX (II) LoadModule: "dri" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: "dri2" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.1.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading e
Re: [OpenIndiana-discuss] Explain the Goal of oi
On Sat, 2011-02-26 at 19:35 -0600, Harry Putnam wrote: > I'm getting a little confused about what OI is trying to do exactly. > > I changed to oi with Opensolaris looked untenable due to oracle > maneuvers, expecting to see a basic continuation of what was happing > from b 101 up to 134. > > I've been seeing little snippets of subjects and the like that seem to > indicate that oi is merging with Illumini (no sure what that is called > by full name). > > If that is the case what, in general, will that mean? I noticed my > subscription to illuminos-discuss has produced 6 msgs since the end of Jan. > > So can someone fill me in, just in general, what the plan is over > the next yr or so? OpenSolaris, despite it's name, to the contrary still contained non free bits that Sun _still_ hadn't gotten around to replacing when Oracle took over and nuked OpenSolaris. Illumos is more akin to the Linux kernel - an open core around which "distributions" may be constructed. OI aims to be one such distribution but hasn't quite gotten there yet because Illumos hasn't quite gotten there yet... But they're getting closer. Hence the discussion. Recently a developer spun an IllumsOS based OpenIndiana Live Cd, dubbed oi-dev-148a. Sans the "as" it's still Sun ON based . Clear as mud? -- Ken Gunderson ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Explain the Goal of oi
I'm getting a little confused about what OI is trying to do exactly. I changed to oi with Opensolaris looked untenable due to oracle maneuvers, expecting to see a basic continuation of what was happing from b 101 up to 134. I've been seeing little snippets of subjects and the like that seem to indicate that oi is merging with Illumini (no sure what that is called by full name). If that is the case what, in general, will that mean? I noticed my subscription to illuminos-discuss has produced 6 msgs since the end of Jan. So can someone fill me in, just in general, what the plan is over the next yr or so? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] quadro 600 on oi-dev-148a - no joy - Xoeg.log output
Damn, guess I that Xorg.log was just too massive for Mailman and I need to include inline. Sorry about that X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: SunOS 5.11 i86pc Current Operating System: SunOS oi-illumos 5.11 oi_148a i86pc Build Date: 06 September 2010 07:48:44PM Solaris ABI: 64-bit Current version of pixman: 0.18.4 Before reporting problems, check http://openindiana.org/consolidation/xnv to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 26 18:02:41 2011 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |-->Screen "Default Screen Section" (0) (**) | |-->Monitor "" (==) No device specified for screen "Default Screen Section". Using the first device section listed. (**) | |-->Device "Card0" (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. (==) Disabling SIGIO handlers for input devices (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: catalogue:/etc/X11/fontpath.d (==) ModulePath set to "/usr/lib/xorg/modules/amd64,/usr/X11/lib/modules/" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. (II) Loader magic: 628150 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 2 (--) PCI: (0:1:5:0) 1002:4752:: ATI Technologies Inc Rage XL rev 39, Mem @ 0xfc00/16777216, 0xfdfff000/4096, I/O @ 0xac00/256, BIOS @ 0x/65536 (--) PCI:*(0:5:0:0) 10de:0df8:10de:0835 nVidia Corporation rev 161, Mem @ 0xfa00/16777216, 0xc800/134217728, 0xd600/33554432, I/O @ 0x6c00/128, BIOS @ 0x/65536 (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "dri" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: "dri2" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.1.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) LoadModule: "ia" (II) Loading /usr/lib/xorg/modules/extensions/amd64/libia.so (II) Module IANAME: vendor="X.Org Foundation" compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SolarisIA (II) LoadModule: "xtsol" (WW) Warning, couldn't open module xtsol (II) UnloadModule: "xtsol" (EE) Failed to load module "xtsol" (module does not exist, 0) (II) LoadModule: "nvidia" (II) Loading /usr/X11/lib/modules/drivers/amd64/nvidia_drv.so (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Video Driver (II) NVIDIA dlloader X Driver 256.44 Thu Jul 29 02:06:07 PDT 2010 (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs (II) Primary Device is: PCI 05@00:00:0 (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib/xorg/modules/amd64/libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.7.
[OpenIndiana-discuss] quadro 600 on oi-dev-148a - no joy :(
Apparently Mailman trimmed xorg.log. Sending again, sans the xorg.conf's. Hello All You Happy People:) Well, I finally tracked down a #00 Phillips screw driver so I could swap out the factory low profile mount for a standard height on my new Quadro 600. Unfortunately, oi loads only with vesa driver. Boo Hiss!! Booting to console and forcing nvidia drivers in xorg.conf pukes up glx initialization failures. I uninstalled and reinstalled the nvidia drivers, glx extensions, etc., but results were the same with both simple xorg.conf specifying nvidia driver and Xorg -configure generated xorg.conf. See attached log and xorg.conf's. nvidia's website and marketing stuff conveniently omits anything about supported cpu's, but the actual packaging stipulates processor requirements: *Intel Core i5, i7 or Xeon processor or later * AMD Phenom or Opteron class processor or later The system is Tyan S2865 based, sporting any Opteron 180, & 4GB ECC, fwiw. Ideas? Thanks in advance. -- Ken Gunderson ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] quadro 600 on oi-dev-148a - no joy :(
Hello All You Happy People:) Well, I finally tracked down a #00 Phillips screw driver so I could swap out the factory low profile mount for a standard height on my new Quadro 600. Unfortunately, oi loads only with vesa driver. Boo Hiss!! Booting to console and forcing nvidia drivers in xorg.conf pukes up glx initialization failures. I uninstalled and reinstalled the nvidia drivers, glx extensions, etc., but results were the same with both simple xorg.conf specifying nvidia driver and Xorg -configure generated xorg.conf. See attached log and xorg.conf's. nvidia's website and marketing stuff conveniently omits anything about supported cpu's, but the actual packaging stipulates processor requirements: *Intel Core i5, i7 or Xeon processor or later * AMD Phenom or Opteron class processor or later The system is Tyan S2865 based, sporting any Opteron 180, & 4GB ECC, fwiw. Ideas? Thanks in advance. -- Ken Gunderson Section "Device" Identifier "Card0" Driver "nvidia" EndSection Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules/amd64" ModulePath "/usr/X11/lib/modules/" FontPath "catalogue:/etc/X11/fontpath.d" EndSection Section "Module" Load "dri2" Load "dri" Load "ia" Load "dbe" Load "extmod" Load "glx" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" EndSection Section "Device" Identifier "Card0" Driver "nvidia" VendorName "ATI Technologies Inc" BoardName "Rage XL" BusID "PCI:5:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [zfs-discuss] iSCSI initiator question
> > Now, the question is simple, where would you think the source of > > these errors belong? > > Based on the log supplied, it would appear that the iSCSI Target from > SANRAD is failing on the SCSI command 0x8a, being a SCSI Write(16) > command. > > A SCSI Write(16) command is required to read and write to SCSI LUNs > that are equal to, or greater than 2TBs in size. The Check Conditions > and resulting information give indications that I/Os to LBAs above the > 2TB size are those that are failing. > > To validate this, performing I/Os at the 2TB boundary, or higher will > trigger the use of Read(16) and/or Write(16) SCSI CDBs, and thus iSCSI > I/Os between initiator and target. The can be done with dd(1m) as > follows: Thanks a bunch. Now, it really shouldn't be a 2TB boundary problem. We've been using this Sanrad thing for far larger volumes, and we have larger volumes in production too, which work, so I'm starting to think maybe the Sanrad is indeed the problem. The storage units (NexSAN stuff) don't show any bad drives, so I somewhat doubt that's the problem. Vennlige hilsener / Best regards roy (who can't wait till he gets this proprietary shite kicked out) -- Roy Sigurd Karlsbakk (+47) 97542685 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] iSCSI initiator question
Hei all Sorry for crossposting, but I'm not really sure where this question belongs. I'm trying to troubleshoot a connection from an s10 box to a SANRAD iSCSI concentrator. After some network issues on the switch, the s10 box seems to lose iSCSI connection to the SANRAD box. The error messages I get in the logs are pasted here http://pastebin.com/hyuuRvNt - we get tons of these and the error block number seems to vary to the extremes, so I somewhat doubt that's the issue. Now, the question is simple, where would you think the source of these errors belong? On the initiator or the target? I tried to setup a new server (initiator) to eliminate that part, exported the two pools, and tried zpool import to look for them again, but could only find one of them, even though I specified the taret statically. So, again, sorry if this is slightly off-topic, I haven't tried with OI, only S10u9, but still, I think it might be relevant, and right now, I'm a little desperate... Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
