PCI Bursting on Solaris 10

We recently ported our Xserver to Solaris 10 from Solaris 8. The code used for both OS's is the same, just built using different compilers on different OS's.
When we run our Xserver on Solaris 8, the graphics card will do PCI bursting when doing memory writes. However, the newly compiled Xserver when running on the same hardware, but with Solaris 10, no longer does PCI bursts.
We actually tried running the Solaris 8 build of our Xserver on Solaris 10 and found the same problem, which leads me to believe that it's not necessarily a problem with our code or the way we compiled the code. Is there a configuration setting that Solaris 10 needs that Solaris 8 did not need in order to enable PCI bursting? Is this a change in the way the driver should be written?
I've scoured SunSolve for an answer to this, but haven't had much luck. Any help would be appreciated.
Thanks,
Kent

Thanks for your answer.
Now work. But before I need to change two times, because I don't know after the first time I change, stranously the network doesn't worked. The machine couldn't ping any machine :-!!!!!!
After to put , cut and put again the entries in the files hosts, work !!!
Many thanks again,
Luz

Similar Messages

Porting PCI board from Solaris Intel to Sparc

Our own PCI board which has been working on Solaris(8) Intel for years does not seem to be recognized by Solaris(8) for Sparc. At the prom level a show-devs shows the device ie: pci1234,5678 but booting with 'boot -rswv' does not. Two questions:
1. Is the process of scanning hardward and making entries in the /devices directory documented anywhere that I might access?
2. What might be different between Solaris-Intel and Solaris-Sparc when dealing with PCI devices?
The platform for our testing is an AXE-300 3 slot PCI Ultra Sparc.
Thanks in advance
[email protected]
(781)-482-1215

The 'prtconf -pv' command does show the presence of our board
pretty much matching what is displayed when running prtconf on
the Intel system with the exception that the Intel results under the
'compatible:' header shows a series of 32 bit hex values while the
Sparc output for 'compatible:' shows "'pci1234,5678' +
'pciclass,ff0000'".
Furthermore running:
truss -f -a add_drv -v -m '* 0666 root bin' -i '"pci1234,5678"' pixgen
seems to show the point of failure occurring in 'devfsadm -v -i pixgen'
as follows: (note I've cleaned up the output a bit for readability).
open("/devices/pseudo/devinfo@0:devinfo", O_RDONLY) = 5
ioctl(5, 0xDF81, 0xFFBEF8F8) Err#6 ENXIO
close(5)
devfsadm then returns an exit code=11 and reports that the driver
was 'successfully added ... but failed to attach'.
I added a number of trace statements to each entry point in the
driver using the cmn_err function and compiled for Intel and Sparc
and verified that the driver continued to work on Intel and indeed
showed each routine being entered but I never got even one line
of output on the Sparc. That presents a couple of questions.
1. I'm using an old compiler: Sun's CC workshop Compiler 4.2 30
Oct 1996 on both platforms. The Sparc platform is a sun4m (ss-10).
Is it possible that this old compiler is not generating proper code for
the sun4u platform? The compiler and linker switches are:
cc -xstrconst -DKERNEL -DDEBUG -DPIXGENDEBUG=255 -c driver.c
ld -r -m -o pixgen driver.o
pkgadd installs the driver as /usr/kernel/drv/pixgen
2. The driver installation using pkgadd places the following line in
/etc/devlink.tab: 'type=io;minor=pixgen0 pixgen'. Is this
possibly an issue?
Any help/insight would be much appreciated.
Thanks
Charlie Jack [email protected]
(781)-482-1215 (East Coast)

Vantec PCIe SATA controller, Solaris x86

I've searched all the online resources I can find, and don't see an answer to this. Is there a driver for this SATA controller for Sol. x86, and if so, where would I find it?
Output of uname -X:
System = SunOS
Node = p810
Release = 5.10
KernelID = Generic_139556-08
Machine = i86pc
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 4
Card is a Vantec UGT-IS100R, you can see more about it here:
http://www.tigerdirect.com/applications/SearchTools/item-details.asp?Sku=V13-2602
PC is not COTS but homebuilt from various components. Motherboard is Asus M2N68-AM SE2. The card has one hard drive attached, a Western Digital Caviar, 1 TB. The card's a RAID controller, but with one disk it's obviously not doing any RAID stuff, and it recognizes the drive as a non-RAID device.
Boot drive is a 320 GB SATA connected directly to the motherboard (not to the Vantec). Windows 7, Slackware 12.2, and Solaris all installed just fine; Win7 and Slack recognize the Vantec and attached drive with no problems. Solaris seems to be working well in all other respects.
Thanks!
Phil

A little progress, and some more information.
1) I had downloaded Solaris 10 longer ago than I thought; I now have the latest-n-greatest (10/09). Output of uname -v is Generic_141445-09. This upgrade eliminated a message I was getting during boot with the older version:
ahci_port_reset port 1 the device hardware has been initialized and the power-up diagnostics failed
2) The Vantec card uses the JMicron 363 chip. After doing more web surfing, I found this thread relating to JMicron and OpenSolaris:
http://opensolaris.org/jive/thread.jspa?messageID=376370
Essentially I'm getting the same results as the OP in that thread, except that prtconf already shows my card in AHCI mode. cfgadm -la shows the controller there; cfgadm -c configure results in "failed" status for the controller; and no matter what I can't get it to recognize the attached hard drive.
I don't want to upgrade the card's firmware; having that drive available under Solaris isn't as important as having the card and drive work under Win7 and Slackware, so if I just have to live without it I will. So ... any other ideas? Thanks!
Phil

Gigabit PCI card on Solaris 8

I'm just trying to install a Gigabit card into an E450 with Solaris 8. I've just stuck the driver CD in but it only seems to have drivers for 2.7 and below... anyone know where I can find drivers for 8?
TIA
Rob

In the same way you install any other card. Plug the card in
the slot., and install the appropriate solaris driver for that
network card. May be you want to detail the problem, if this
is not you are looking for.
Thx
Tushar Patel.

I want to know VendorID of pci devices in system.

Hi.
I have a question.
I want to display vendor ID & device ID of My pci devices in solaris system.
in windows driver...
#define VENDORID          0x1234
#define DEVICEID          0x5678
for( bus = 0 ; bus < 256 ; bus ++ )
for( slot = 0 ; slot < 32 ; slot ++ )
dwRet = HalGetBusData(PCIConfiguration, bus, slot, &Buffer, sizeof(PCI_COMMON_CONFIG));
if(dwRet == 0)
continue;
if(Buffer.VendorID != VENDORID)
continue;
if(Buffer.DeviceID != DEVICEID)
continue;
DbgPrint("Bus:%d Slot:%d\n", Buffer.VendorID, Buffer.DeviceID);
but i don't know how search "My" pci devices in solaris system.
is there some command?
please show me the way. (by simple code)
bye..

The information is available in the output from the "prtconf -pv" command. Each PCI device is listed
with it's "vendor-id:" and "device-id:" property, as well as the "subsystem-vendor-id:" and "subsystem-id:".
Note also the value of the "compatible:" property, which is used by the solaris kernel to select a device
driver for the PCI device.
Node 0x1b4d10
assigned-addresses: 81005020.00000000.00001060.00000000.00000020
class-code: 000c0300
compatible: 'pci925,1234' + 'pci925,1234' + 'pci1106,3038' + 'pciclass,0c0300'
device-id: 00003038
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
model: 'PCI: 925,1234 - class: Universal Serial Bus'
name: 'pci925,1234'
power-consumption: 00000001.00000001
reg: 00005000.00000000.00000000.00000000.00000000.01005020.00000000.00000000.00000000.00000020
revision-id: 00000004
slot: 00000003
subsystem-id: 00001234
subsystem-vendor-id: 00000925
unit-address: 'a'
vendor-id: 00001106
You can also use my "prtpci" awk script to reformat the "prtconf -pv" output
wget http://www.tools.de/solaris/prtpci.bz2
bunzip2 prtpci.bz2
chmod +x prtpci
./prtpci -u -p pcidev.csv (optional, fetches PCI device database from http://www.pcidatabase.com)
./prtpci
the output from that script for a PCI device looks like this:
Bus,Device,Function: 0,12,0
Vendor,Device ID: 1106,3038 Rev 50 (VIA Technologies Inc, VT83C572)
Subsys. Vendor,Device: 925,1234
Class code: 0c0300 (Serial Bus, Universal Serial Bus, UHCI)
Interrupt pin: 1
assigned-addresses:
I/O 0000000000001080 0000000000000020 (@20)
Model: 'PCI: 925,1234 - class: Universal Serial Bus'
Name: 'pci925,1234'
compatible: 'pci925,1234' + 'pci925,1234' + 'pci1106,3038' + 'pciclass,0c0300'

X (Fatal Error)

Im having a little bit of trouble getting X to start on a HP OmniBook XE2 laptop. First and foremost, here is the Xorg log:
[ 35.602]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 35.603]
X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
[ 35.604] X Protocol Version 11, Revision 0
[ 35.604] Build Operating System: Linux 2.6.34-ARCH i686
[ 35.604] Current Operating System: Linux myhost 2.6.33-ARCH #1 SMP PREEMPT Thu May 13 12:06:25 CEST 2010 i686
[ 35.604] Kernel command line: root=/dev/sda1 ro
[ 35.604] Build Date: 21 June 2010 11:54:27AM
[ 35.605]
[ 35.623] Current version of pixman: 0.18.2
[ 35.624] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 35.624] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 35.625] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 7 07:15:31 2011
[ 35.670] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 35.687] (==) No Layout section. Using the first Screen section.
[ 35.687] (==) No screen section available. Using defaults.
[ 35.687] (**) |-->Screen "Default Screen Section" (0)
[ 35.688] (**) | |-->Monitor "<default monitor>"
[ 35.688] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 35.689] (==) Automatically adding devices
[ 35.689] (==) Automatically enabling devices
[ 35.728] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 35.728] Entry deleted from font path.
[ 35.728] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 35.728] Entry deleted from font path.
[ 35.728] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 35.728] Entry deleted from font path.
[ 35.729] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 35.729] Entry deleted from font path.
[ 35.729] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 35.729] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 35.729] Entry deleted from font path.
[ 35.729] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 35.729] (==) FontPath set to:
/usr/share/fonts/misc/
[ 35.730] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 35.730] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 35.730] (II) Loader magic: 0x81e9d00
[ 35.730] (II) Module ABI versions:
[ 35.730] X.Org ANSI C Emulation: 0.4
[ 35.730] X.Org Video Driver: 7.0
[ 35.730] X.Org XInput driver : 9.0
[ 35.730] X.Org Server Extension : 3.0
[ 35.778] (--) PCI:*(0:1:0:0) 126f:0710:103c:000e Silicon Motion, Inc. SM710 LynxEM rev 163, Mem @ 0xfd000000/16777216
[ 35.779] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 35.779] (II) LoadModule: "extmod"
[ 35.782] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 35.792] (II) Module extmod: vendor="X.Org Foundation"
[ 35.792] compiled for 1.8.1.902, module version = 1.0.0
[ 35.792] Module class: X.Org Server Extension
[ 35.792] ABI class: X.Org Server Extension, version 3.0
[ 35.792] (II) Loading extension MIT-SCREEN-SAVER
[ 35.792] (II) Loading extension XFree86-VidModeExtension
[ 35.792] (II) Loading extension XFree86-DGA
[ 35.792] (II) Loading extension DPMS
[ 35.792] (II) Loading extension XVideo
[ 35.792] (II) Loading extension XVideo-MotionCompensation
[ 35.792] (II) Loading extension X-Resource
[ 35.792] (II) LoadModule: "dbe"
[ 35.793] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 35.802] (II) Module dbe: vendor="X.Org Foundation"
[ 35.803] compiled for 1.8.1.902, module version = 1.0.0
[ 35.803] Module class: X.Org Server Extension
[ 35.803] ABI class: X.Org Server Extension, version 3.0
[ 35.803] (II) Loading extension DOUBLE-BUFFER
[ 35.803] (II) LoadModule: "glx"
[ 35.803] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 35.812] (II) Module glx: vendor="X.Org Foundation"
[ 35.812] compiled for 1.8.1.902, module version = 1.0.0
[ 35.812] ABI class: X.Org Server Extension, version 3.0
[ 35.819] (==) AIGLX enabled
[ 35.819] (II) Loading extension GLX
[ 35.819] (II) LoadModule: "record"
[ 35.819] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 35.821] (II) Module record: vendor="X.Org Foundation"
[ 35.821] compiled for 1.8.1.902, module version = 1.13.0
[ 35.821] Module class: X.Org Server Extension
[ 35.821] ABI class: X.Org Server Extension, version 3.0
[ 35.821] (II) Loading extension RECORD
[ 35.822] (II) LoadModule: "dri"
[ 35.822] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 35.840] (II) Module dri: vendor="X.Org Foundation"
[ 35.840] compiled for 1.8.1.902, module version = 1.0.0
[ 35.840] ABI class: X.Org Server Extension, version 3.0
[ 35.840] (II) Loading extension XFree86-DRI
[ 35.840] (II) LoadModule: "dri2"
[ 35.841] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 35.842] (II) Module dri2: vendor="X.Org Foundation"
[ 35.842] compiled for 1.8.1.902, module version = 1.2.0
[ 35.842] ABI class: X.Org Server Extension, version 3.0
[ 35.843] (II) Loading extension DRI2
[ 35.843] (==) Matched siliconmotion as autoconfigured driver 0
[ 35.843] (==) Matched vesa as autoconfigured driver 1
[ 35.843] (==) Matched fbdev as autoconfigured driver 2
[ 35.843] (==) Assigned the driver to the xf86ConfigLayout
[ 35.843] (II) LoadModule: "siliconmotion"
[ 35.873] (II) Loading /usr/lib/xorg/modules/drivers/siliconmotion_drv.so
[ 35.877] (II) Module siliconmotion: vendor="X.Org Foundation"
[ 35.878] compiled for 1.8.0.902, module version = 1.7.4
[ 35.878] Module class: X.Org Video Driver
[ 35.878] ABI class: X.Org Video Driver, version 7.0
[ 35.878] (II) LoadModule: "vesa"
[ 35.879] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 35.893] (II) Module vesa: vendor="X.Org Foundation"
[ 35.893] compiled for 1.8.0, module version = 2.3.0
[ 35.893] Module class: X.Org Video Driver
[ 35.893] ABI class: X.Org Video Driver, version 7.0
[ 35.893] (II) LoadModule: "fbdev"
[ 35.895] (WW) Warning, couldn't open module fbdev
[ 35.895] (II) UnloadModule: "fbdev"
[ 35.895] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 35.895] (II) SMI: driver (version 1.7.4) for Silicon Motion Lynx chipsets: Lynx,
LynxE, Lynx3D, LynxEM, LynxEM+, Lynx3DM, Cougar3DR, MSOC
[ 35.895] (II) VESA: driver for VESA chipsets: vesa
[ 35.896] (--) using VT number 7
[ 35.898] (II) Primary Device is: PCI 01@00:00:0
[ 35.898] (WW) Falling back to old probe method for siliconmotion
[ 35.898] (--) Assigning device section with no busID to primary device
[ 35.899] (--) Chipset LynxEM found
[ 35.899] (WW) Falling back to old probe method for vesa
[ 35.899] (II) Loading sub module "vgahw"
[ 35.899] (II) LoadModule: "vgahw"
[ 35.900] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 35.902] (II) Module vgahw: vendor="X.Org Foundation"
[ 35.902] compiled for 1.8.1.902, module version = 0.1.0
[ 35.902] ABI class: X.Org Video Driver, version 7.0
[ 35.902] (II) SMI(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 35.902] (==) SMI(0): Depth 24, (--) framebuffer bpp 32
[ 35.902] (==) SMI(0): RGB weight 888
[ 35.902] (==) SMI(0): Default visual is TrueColor
[ 35.902] (==) SMI(0): PCI Burst enabled
[ 35.902] (==) SMI(0): PCI Retry enabled
[ 35.902] (==) SMI(0): Using Hardware Cursor
[ 35.902] (II) Loading sub module "int10"
[ 35.903] (II) LoadModule: "int10"
[ 35.904] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 35.908] (II) Module int10: vendor="X.Org Foundation"
[ 35.908] compiled for 1.8.1.902, module version = 1.0.0
[ 35.908] ABI class: X.Org Video Driver, version 7.0
[ 35.913] (II) SMI(0): Primary V_BIOS segment is: 0xc000
[ 35.914] (II) Loading sub module "vbe"
[ 35.914] (II) LoadModule: "vbe"
[ 35.914] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 35.922] (II) Module vbe: vendor="X.Org Foundation"
[ 35.922] compiled for 1.8.1.902, module version = 1.1.0
[ 35.922] ABI class: X.Org Video Driver, version 7.0
[ 35.922] (II) SMI(0): VESA BIOS detected
[ 35.922] (II) SMI(0): VESA VBE Version 2.0
[ 35.923] (II) SMI(0): VESA VBE Total Mem: 4096 kB
[ 35.923] (II) SMI(0): VESA VBE OEM: Silicon Motion SM710 VGA BIOS
[ 35.923] (II) SMI(0): VESA VBE OEM Software Rev: 2.0
[ 35.923] (II) SMI(0): VESA VBE OEM Vendor: SM710
[ 35.923] (II) SMI(0): VESA VBE OEM Product: SM710
[ 35.923] (II) SMI(0): VESA VBE OEM Product Rev:
[ 35.923] (--) SMI(0): Chipset: "LynxEM"
[ 35.923] (==) SMI(0): Dual head disabled
[ 35.923] (==) SMI(0): Using XAA acceleration architecture
[ 35.924] (--) SMI(0): videoram: 4096kB
[ 35.925] (II) SMI(0): Cursor Offset: 003FFC00
[ 35.925] (II) SMI(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
[ 35.925] (II) SMI(0): Reserved: 003FF800
[ 35.925] (II) SMI(0): TFT Panel Size = 1024x768
[ 35.925] (II) Loading sub module "i2c"
[ 35.925] (II) LoadModule: "i2c"
[ 35.925] (II) Module "i2c" already built-in
[ 35.925] (II) SMI(0): I2C bus "I2C bus" initialized.
[ 35.926] (II) Loading sub module "ddc"
[ 35.926] (II) LoadModule: "ddc"
[ 35.926] (II) Module "ddc" already built-in
[ 35.926] (==) SMI(0): Using gamma correction (1.0, 1.0, 1.0)
[ 35.926] (II) SMI(0): MCLK = 85.909
[ 35.926] (II) SMI(0): Output LVDS has no monitor section
[ 35.927] (II) SMI(0): Not using default mode "640x350" (vrefresh out of range)
[ 35.927] (II) SMI(0): Not using default mode "320x175" (doublescan mode not supported)
[ 35.927] (II) SMI(0): Not using default mode "640x400" (vrefresh out of range)
[ 35.927] (II) SMI(0): Not using default mode "320x200" (doublescan mode not supported)
[ 35.927] (II) SMI(0): Not using default mode "720x400" (vrefresh out of range)
[ 35.927] (II) SMI(0): Not using default mode "360x200" (doublescan mode not supported)
[ 35.927] (II) SMI(0): Not using default mode "640x480" (exceeds panel dimensions)
[ 35.927] (II) SMI(0): Not using default mode "320x240" (doublescan mode not supported)
[ 35.927] (II) SMI(0): Not using default mode "640x480" (vrefresh out of range)
[ 35.927] (II) SMI(0): Not using default mode "320x240" (doublescan mode not supported)
[ 35.927] (II) SMI(0): Not using default mode "640x480" (vrefresh out of range)
[ 35.928] (II) SMI(0): Not using default mode "320x240" (doublescan mode not supported)
[ 35.928] (II) SMI(0): Not using default mode "640x480" (vrefresh out of range)
[ 35.928] (II) SMI(0): Not using default mode "320x240" (doublescan mode not supported)
[ 35.928] (II) SMI(0): Not using default mode "800x600" (vrefresh out of range)
[ 35.928] (II) SMI(0): Not using default mode "400x300" (doublescan mode not supported)
[ 35.928] (II) SMI(0): Not using default mode "800x600" (exceeds panel dimensions)
[ 35.928] (II) SMI(0): Not using default mode "400x300" (doublescan mode not supported)
[ 35.928] (II) SMI(0): Not using default mode "800x600" (vrefresh out of range)
[ 35.928] (II) SMI(0): Not using default mode "400x300" (doublescan mode not supported)
[ 35.928] (II) SMI(0): Not using default mode "800x600" (vrefresh out of range)
[ 35.928] (II) SMI(0): Not using default mode "400x300" (doublescan mode not supported)
[ 35.928] (II) SMI(0): Not using default mode "800x600" (vrefresh out of range)
[ 35.928] (II) SMI(0): Not using default mode "400x300" (doublescan mode not supported)
[ 35.928] (II) SMI(0): Not using default mode "1024x768i" (interlace mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "512x384i" (doublescan mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "1024x768" (hsync out of range)
[ 35.929] (II) SMI(0): Not using default mode "512x384" (doublescan mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "1024x768" (vrefresh out of range)
[ 35.929] (II) SMI(0): Not using default mode "512x384" (doublescan mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "1024x768" (vrefresh out of range)
[ 35.929] (II) SMI(0): Not using default mode "512x384" (doublescan mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "1024x768" (vrefresh out of range)
[ 35.929] (II) SMI(0): Not using default mode "512x384" (doublescan mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "1152x864" (vrefresh out of range)
[ 35.929] (II) SMI(0): Not using default mode "576x432" (doublescan mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "1280x960" (hsync out of range)
[ 35.929] (II) SMI(0): Not using default mode "640x480" (doublescan mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "1280x960" (vrefresh out of range)
[ 35.929] (II) SMI(0): Not using default mode "640x480" (doublescan mode not supported)
[ 35.929] (II) SMI(0): Not using default mode "1280x1024" (hsync out of range)
[ 35.930] (II) SMI(0): Not using default mode "640x512" (doublescan mode not supported)
[ 35.930] (II) SMI(0): Not using default mode "1280x1024" (vrefresh out of range)
[ 35.930] (II) SMI(0): Not using default mode "640x512" (doublescan mode not supported)
[ 35.930] (II) SMI(0): Not using default mode "1280x1024" (vrefresh out of range)
[ 35.930] (II) SMI(0): Not using default mode "640x512" (doublescan mode not supported)
[ 35.930] (II) SMI(0): Not using default mode "1600x1200" (hsync out of range)
[ 35.930] (II) SMI(0): Not using default mode "800x600" (doublescan mode not supported)
[ 35.930] (II) SMI(0): Not using default mode "1600x1200" (vrefresh out of range)
[ 35.930] (II) SMI(0): Not using default mode "800x600" (doublescan mode not supported)
[ 35.930] (II) SMI(0): Not using default mode "1600x1200" (vrefresh out of range)
[ 35.930] (II) SMI(0): Not using default mode "800x600" (doublescan mode not supported)
[ 35.930] (II) SMI(0): Not using default mode "1600x1200" (vrefresh out of range)
[ 35.930] (II) SMI(0): Not using default mode "800x600" (doublescan mode not supported)
[ 35.930] (II) SMI(0): Not using default mode "1600x1200" (vrefresh out of range)
[ 35.930] (II) SMI(0): Not using default mode "800x600" (doublescan mode not supported)
[ 35.931] (II) SMI(0): Not using default mode "1792x1344" (hsync out of range)
[ 35.931] (II) SMI(0): Not using default mode "896x672" (doublescan mode not supported)
[ 35.931] (II) SMI(0): Not using default mode "1792x1344" (vrefresh out of range)
[ 35.931] (II) SMI(0): Not using default mode "896x672" (doublescan mode not supported)
[ 35.931] (II) SMI(0): Not using default mode "1856x1392" (hsync out of range)
[ 35.931] (II) SMI(0): Not using default mode "928x696" (doublescan mode not supported)
[ 35.931] (II) SMI(0): Not using default mode "1856x1392" (vrefresh out of range)
[ 35.931] (II) SMI(0): Not using default mode "928x696" (doublescan mode not supported)
[ 35.931] (II) SMI(0): Not using default mode "1920x1440" (hsync out of range)
[ 35.931] (II) SMI(0): Not using default mode "960x720" (doublescan mode not supported)
[ 35.931] (II) SMI(0): Not using default mode "1920x1440" (vrefresh out of range)
[ 35.931] (II) SMI(0): Not using default mode "960x720" (doublescan mode not supported)
[ 35.931] (II) SMI(0): Not using default mode "832x624" (vrefresh out of range)
[ 35.931] (II) SMI(0): Not using default mode "416x312" (doublescan mode not supported)
[ 35.931] (II) SMI(0): Not using default mode "1400x1050" (hsync out of range)
[ 35.932] (II) SMI(0): Not using default mode "700x525" (doublescan mode not supported)
[ 35.932] (II) SMI(0): Not using default mode "1400x1050" (vrefresh out of range)
[ 35.932] (II) SMI(0): Not using default mode "700x525" (doublescan mode not supported)
[ 35.932] (II) SMI(0): Not using default mode "1920x1440" (vrefresh out of range)
[ 35.932] (II) SMI(0): Not using default mode "960x720" (doublescan mode not supported)
[ 35.932] (II) SMI(0): Not using default mode "2048x1536" (hsync out of range)
[ 35.932] (II) SMI(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 35.932] (II) SMI(0): Not using default mode "2048x1536" (vrefresh out of range)
[ 35.932] (II) SMI(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 35.932] (II) SMI(0): Not using default mode "2048x1536" (vrefresh out of range)
[ 35.932] (II) SMI(0): Not using default mode "1024x768" (doublescan mode not supported)
[ 35.932] (II) SMI(0): Printing probed modes for output LVDS
[ 35.932] (II) SMI(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz)
[ 35.932] (II) SMI(0): Output LVDS connected
[ 35.933] (II) SMI(0): Using fuzzy aspect match for initial modes
[ 35.933] (II) SMI(0): Output LVDS using initial mode 1024x768
[ 35.933] (II) SMI(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 35.933] (EE) SMI(0): Not enough video memory for the configured screen size (1024x1024) and color depth.
[ 35.934] (II) UnloadModule: "siliconmotion"
[ 35.934] (II) UnloadModule: "vbe"
[ 35.934] (II) Unloading /usr/lib/xorg/modules/libvbe.so
[ 35.934] (II) UnloadModule: "int10"
[ 35.934] (II) Unloading /usr/lib/xorg/modules/libint10.so
[ 35.934] (II) UnloadModule: "vgahw"
[ 35.934] (II) Unloading /usr/lib/xorg/modules/libvgahw.so
[ 35.935] (EE) Screen(s) found, but none have a usable configuration.
[ 35.935]
Fatal server error:
[ 35.935] no screens found
[ 35.935]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 35.935] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 35.935]
I'm not exactly sure what is going on and searching google more or less turned up nothing which is why I am here. The VGA controller shows up as a "Silicon Motion SM710 LynxEM" So I loaded the xf86-video-siliconmotion driver. This may or may not be the correct one. I also downloaded the generic Vesa driver but I am not sure how to actually remove the SiliconMotion and load the Vesa. Thank you so much!!!

Don't forget to use the code tag. It will make your post a lot more readable.
As for a video driver, you might want to read the man page for siliconmotion driver and see if you can't get it to work by manipulating some of its options:
http://www.xfree86.org/4.4.0/siliconmotion.4.html

Very random freezes... This is driving me nuts!

This problem is just absurd!
Every once and a while my computer just freezes for 5 or 6 seconds and then unfreezes just to continue on like nothing happened. No error logs, no BSOD's, no warnings, no nothing! I don't know if it's a coincidence or not, but the freezes have occurred after doing the following... but never happen again if I try to recreate the situation.
-Unplugged the USB cable from my PSP
-In the middle of a World of Warcraft Game
-Started Trillian
-Started Windows
-Closed Firefox
-During use and startup of iTunes.
-And as soon as I dock my Dell PocketPC
Now since this problem is sooooo random it's extremely hard for me to pinpoint the problem.
This problem although irritating it doesn't happen that often. Sometimes it happens 5 times a day, other times it only happens once or twice a week.
I've reinstalled windows numerous times trying to see if it is a software issue or not but it's still hard to tell.
The only real tie in I've been able to find is every time I've reinstalled windows and plugged in my ipod the freezes start happening after that point.
Otherwise it seems to be freezeless before that point.
My computer specs are in my sig...
Here is a list of programs that are running in the background when in idle.
Trillian
Webshots
MS AntiSpyware
Dantz Retrospect
AVG Antivirus
Picasa2
ActiveSync
Outlook 2000
Ipodservice
I still think it's a software issue as the computer runs flawlessly (without freezes) with a fresh copy of windows on it without any software installed, but I am open to suggestions.
Do you think this is a hardware issue or software?
HELP ME!

I just got this e-mail from BFG...
Anything you would add to or remove??
Thank you for contacting the BFG E-Mail Technical Support Group. I understand your having some difficulty with your BFG Asylum GeForce card. The problem you specified seems as if it's originating in the BIOS. Your BIOS is the basic "input/output" system setup for your computer and must be entered while the computer is booting, during or shortly after POST. To enter your BIOS you normally have to press a key specific to your system. This is normally something like F1, F10 or Delete keys, but varies from computer to computer. Below I've listed all of the BIOS settings that may pertain to all of our cards. Please make sure these settings are concurrent in your setup. Please keep in mind these settings may not apply for some cards that are pci and some settings may not apply to the agp cards. If you're not familiar with your BIOS we recommend contacting your computer or motherboard manufacturer to make any changes.
Assign IRQ for VGA: Enable
AGP Turbo Read Mode: Disable
AGP Turbo Write Mode: Disable
AGP Fast Writes: Disable (Change this setting while troubleshooting)
AGP WS Write: Highest Possible Value
AGP WS Read: Highest Possible Value
AGP Transfer Mode: 4X ~or~ 8X ~or~ AUTO
AGP Clock: 2/3 ~or~ AUTO ~or~ 66mHz
AGP/Graphics Aperture Size: Half the installed RAM (Example: 256 RAM; Set Aperture to 128. Can change lower in some computers to troubleshoot lockup/rebooting issues)
C8000-xxxxx-Cacheable: Disabled
Delayed Transaction: Enable
PCI Bursting: Disable
PCI 2.1 Compliancy: Enable
PCI Latency Timer: 128
Pipeline Cache Write: Disable
Passive Release: Enable
PnP O/S Installed: Enable (Can set to Disabled in some computers with NT, 2K or XP)
Peer Concurrency: Enabled
USWC Options: Disable (or set to UC)
VGA Boot Sequence: AGP or PCI (Based on the installed card)
VGA Pallet Snooping: Disable
Video BIOS Shadow: Disabled (Change this setting while troubleshooting)
Video BIOS Cacheable: Disabled (Change this setting while troubleshooting)
Video RAM Cacheable: Disabled
Video RAM Shadowing: Disable
Corey H @ BFG Technical Support

Device not supported

Despite my server running fine on a fresh Solaris U1 install, I get a ton of warning messages during bootup that I thought the developers would like to know about.
Here is the relevant info from my messages file:
Apr 21 21:43:33 ailvfs02 symhisl: [ID 291704 kern.info] Symbios SDMS (TM) V4.0 PCI High-Performance Solaris Driver
Apr 21 21:43:33 ailvfs02 Copyright 1995-2000 LSI Logic Corporation
Apr 21 21:43:33 ailvfs02 SYMHISL-4.07.01
Apr 21 21:43:33 ailvfs02 pcplusmp: [ID 637496 kern.info] pcplusmp: pci1000,20 (symhisl) instance 0 vector 0x18 ioapic 0x2 inti
n 0x8 is bound to cpu 0
Apr 21 21:43:33 ailvfs02 pci: [ID 370704 kern.info] PCI-device: pci103c,60b0@5, symhisl0
Apr 21 21:43:33 ailvfs02 genunix: [ID 936769 kern.info] symhisl0 is /pci@1,0/pci103c,60b0@5
Apr 21 21:43:33 ailvfs02 symhisl: [ID 982002 kern.warning] WARNING: SYMHISL0: Device (ID=16, LUN=0) not supported
Apr 21 21:43:33 ailvfs02 symhisl: [ID 982002 kern.warning] WARNING: SYMHISL0: Device (ID=17, LUN=0) not supported
It then repeats all the way to ID 128 and then does the same for SYMHISL1.
PS - Thanks for amazing product. Love my new Solaris webserver.

No, haven't found a solution yet only because it isn't a priority as my Solaris server fully functions perfectly so far.
I don't think it is related to the NIC though as you suggest. You might just not have a supported NIC hence why you even see it?

Problem with network interfaces

I have installed Solaris 8 on intel. The two network adapters I have were properly
recognised during the installation by the configuration assistant. However, after the installation none of them has the interface installed (no /etc/hostname files).
Both network adapters are SMC PCI cards from solaris 8 hardware compatibility list.
Any ideas? Or where to put the card's driver manually and how to set it up?

By accessing. I mean accessing them through thier network ip address through ssh or an xterm or any other network service the zone is running.
say I have all 3 zone running each in a xterm.
I click on zone 1 or global zone and both this 2 xterm windown respond and I can run commands.
If I swich to the zone 2 zterm, zone 1 and global zone freeze, and zone 2 takes 30 sec - 1 min to start responding.
If I am in a ssh session instead of a xterm the ssh session will stop responding and session will get disconnected.

Skipping sound on 648 Max

I just installed the 648 max board with a 2.4ghz cpu. When I play mp3's or CD's, using the onboard sound, the songs sound like they skip or stutter at random places. Usually happens if I might be moving the mouse, or minimizing, maximizing, opening or closing windows... stuff like that. Then I noticed it would "skip or stutter" even if I was not even making any mouse movements. So I disabled the onboard sound and installed a Sound Blaster Live. Still has the problem but only once in awhile, not as bad as with the onboard. I thought it was the PC Alert that was causing this, but it is not.
Anyone had this problem before? Or any suggestions?
Thanks!

While you're at it also try lower PCI latency timer settings (to keep bus hogs like RAID/IDE controllers in check). The reason for sound skips is that the audio controller has a very limited amout of on-board buffer RAM and therefore relies on constant audio data transfers over the PCI bus - and if something has a very long transfer in progress the bus will not free up in time. (The PCI latency timer defines, in PCI clock cycles, how long a device may lock the bus before giving it up)
Most often this has been a PCI VGA driver issue (where they make use of PCI bursting with very long transfer cycles - this gives them a bit of a performance boost, sacrificing all other users of the bus) - but nothing I've seen with AGP VGA cards...
/WernerJ

X4270 system not booting after installing a new SAS card

Hello
we have Sun Fire x4270 server , with Solaris 10 .
we installed a new SAS PCI card to connect it to tape drive. after installing the PCI card , the Solaris is not booting , seems like there is conflict between the onboard sas controller and one oncard controller.
your support is appreciated
HEBA

Hello ,
I've checked the BIOS for boot order , and the issue is not with the order.
the system boots normally , then I poweroff , install the SAS card , and poweron and it never boots, the output on screen as follows:
Intel(R) Boot Agent GE v1.3.31
Copyright (C) 1997-2009, Intel Corporation
PXE-E61: Media test failure, check cable
PXE-M0F: Exiting Intel Boot Agent.
Intel(R) Boot Agent GE v1.3.31
Copyright (C) 1997-2009, Intel Corporation
PXE-E61: Media test failure, check cable
PXE-M0F: Exiting Intel Boot Agent.
Intel(R) Boot Agent GE v1.2.42P1
Copyright (C) 1997-2006, Intel Corporation
CLIENT MAC ADDR: 00 1B 21 94 A5 9D GUID: FF200008 FFFF FFFF FFFF A62AB2282100
PXE-E51: No DHCP or proxyDHCP offers were received.
PXE-M0F: Exiting Intel Boot Agent.
Reboot and Select proper Boot device
or Insert Boot Media in selected Boot device and press a key
Edited by: HEBA2008 on May 6, 2013 4:08 PM

Pl. help me install a PCI card in a solaris 2.6 system

Hello,
I am working on a cpci chassis with Sun CP1400 processor card running Solaris 2.6. I am trying to install a voip card from AudioCodes. After installing the driver, and the card, the software doesn't seem to recognize the board.
I ran "show-devs" from the ok prompt. It doesn't list the card. Also, there is no entry for the driver in /etc/driver_aliases. I am not sure if the board is faulty, or the driver is not properly installed.
The driver.conf indicates its a pseudo driver (I dont know if this makes any difference). When I run pci_scan that came with the driver it listed a device on the bus with vendor id = 0x10b5. I think this is the plx chip on the card. But I don't see any AudioCodes vendor, and device ids in the list.
Thanks for your time.
Sridhar
[email protected]

It is possible that this card may not be compatible with this Solaris
system.
You may want to check these sites out for driver related information:
http://soldc.sun.com/developer/support/driver/
http://soldc.sun.com/developer/support/driver/IO_kit/PCI.html
Thx
Tushar Patel.

PCI id problem under Solaris-8,9,10

In attempting to qualify a SuperMicro X5DA8 dual CPU dual channel SCSI card I have found a problem with the PCI id's for the Adaptec 7902 (Ultra-320) chipset. My question is whether the problem is SuperMicro's, Sun's or Adaptec's.
The DCA->Device Tasks->View/Edit Devices displays the PCI id of the two SCSI controllers as follows:
[ ] PCI: 9005,801f.9005.5f.3 Adaptec AIC-7902 - Ultra 320 SCSI
The /etc/driver_aliases file has the entries:
cadp "pci9005,5f"
adpu320 "pci9005,801f"
The file: /boot/system/driverdb/master has the entries:
pci9005,801f pci9005,801f msd pci adpu320.bef "Adaptec AIC-7902 - Ultra320 SCSI"
pci9005,5f pci9005,5f msd pci cadp.bef "Adaptec AIC-7896 SCSI"
Checking in www.pcidatabase.com shows that the two above identifiers map to:
9005,801f Vendor Adaptec: Ultra320 SCSI Controller
9005,5f Vencor Adaptec: Ultra2 SCSI Controller !!!!!
The presence of the 9005.5f is confusing Solaris to the point that it is loading the incorrect driver and crashing. It is my belief the the 9005.5f device identifier is incorrect, or is it? Is this identifier put in firmware by SuperMicro or is it possibly embedded in the AIC-7902 chips?
As I am not an OEM to SuperMicro or Adaptec I can't ask them directly. If anyone has any insight as to whose problem this is I can hopefully report it as a bug to the appropriate party and perhaps get it fixed.
Kudos to j.keil for helping me sort this out. I am able to get Solaris-10 running on this board but only after hacking the aforementioned files. It would be nice to have it work out of the box.
Charlie Jack

Hello Phil,
<i>Cjack, did you get a resolution for this?</i>
if you review his profile you will see that his last login to this forums was on April 21st 2005 and if you read the last sentence of his post...
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
Kudos to j.keil for helping me sort this out. I am able to get Solaris-10 running on this board but only after hacking the aforementioned files. It would be nice to have it work out of the box.
</td></tr></table>
Unfortunately notification (answers to watched topics) still <b>doesn't</b> work, besides the bug (blank screen after post) that is responsible for double-posting .
I would suggest that you post on the SolarisX86 yahoogroup. This is the place besides Opensolaris.org where you can find more Sun engineers or other knowledgeable SolarisX86 people.
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
Please check the Links page before posting:
http://groups.yahoo.com/group/solarisx86/links
Post message: solarisx86@yahoogroups.com
UNSUBSCRIBE: solarisx86-unsubscribe@yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/solarisx86/
<*> To unsubscribe from this group, send an email to:
solarisx86-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
</td></tr></table>
Michael

Installing Solaris 10 on Compaq Proliant 1600 with Smart 2DH PCI controller

I'm trying to put Solaris 10 on a fairly old 350 Mhz Compaq Proliant.
Compaq SMART-2DH Array controller Ver C rev 3.08
This is a PCI card
I have tried downloading HP's drivers for the Smart II controller and renaming the DU/ folders to 210 instead of 28, and the installation program will process the drivers
When it continues on to the part where you select the type of installation, it gives these errors:
/platform/i86pc/kernel/drv/smartii: undefined symbol 'eisa_nvm'
WARNING: mod_load: cannot load module 'msartii'
WARNING: forceload of drv/smartii failed
WARNING: forceload of drv/smartii failed
Then it will continue on to the GUI portion of the install and give the error about not having any available disks to install on to (check cables)
Is there any way to make Solaris 10 load these drivers? I know it doesn't support EISA, but this card is PCI. Not sure why it tries to load EISA drivers for it.
This thing also has SCSI built into the motherboard, does anyone know if Solaris 10 will support that particular controller? No idea what it's called. If it will, I'm just going to plug the hard disk cable in to that and go with it.

Has any body found a way to get Solaris 10 to install with the Smart-2DH controller? I've got a Compaq Proliant 1850R that also has that raid controller and the Solaris 10 install rejected the Solaris 8 driver.

Solaris 10 x86 goes to reboot mode after installing Sun x4 PCIe Quad card

I have an x4200 server installed with solaris 10 x86 11/06 OS. After installing the OS it comes up fine.
Now, When I install an SUN x4 PCIe Quad Gigabit Ethernet card on PCI slot 0 and on the power up server does not comes up. It gpes into the reboot mode.
bash-3.00# uname -a
SunOS server1-1 5.10 Generic_118855-33 i86pc i386 i86pc
Does any one has face this issue..

Solution found:
First tried to login using "console login" when solaris booted up, before the desktop login window appeared. Then, run command "kdmconfig", changed the video device to X86 VESA compatible device, which is from the x86 driver and porting kit for solaris, then test/save and exit. After that, reboot the system. Now it is working, not perfect though (due to my old monitor) :)-

PCI Bursting on Solaris 10

Similar Messages

Maybe you are looking for