Problems with Solaris 11 11/11

Hi,
I need your help because I have problems with Solaris 11 11/11 installed in a Dell Latitude E4310.
Here, there are the problems:
1- No it power off with shutdown or init 5 or init 0 only work well the reboot.
2- It can not connect to the wifi with wpa, no receive ip by dhcp, the driver of the card is "iwp"
Thanks.
Jorge
Edited by: jdangelo on Nov 16, 2011 1:49 PM
Edited by: jdangelo on Nov 17, 2011 2:51 PM

Here is the info of my laptop;
Manufacture name:Dell Inc.
Manufacture model:Latitude E4310
64 Bit:True
OS version:SunOS solaris 5.11 11.0 i86pc i386 i86pc
CPU Type:Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
CPU Number:1
Number Of Cores Per Processor:2
Number Of Threads Per Processor:4
Bios/Firmware Maker:Dell Inc. Version:A05 Release Date:11/20/2010
prtconf -pv:
System Configuration: Oracle Corporation i86pc
Memory size: 3958 Megabytes
System Peripherals (PROM Nodes):
Node 0x000001
bios-boot-device: '80'
stdout: 00000000
name: 'i86pc'
Node 0x000002
existing: 00c21000.00000000.02bc6001.00000000
name: 'ramdisk'
Node 0x000003
acpi-namespace: '\_SB_.PCI0'
compatible: 'pciex_root_complex'
device_type: 'pciex'
reg: 00000000.00000000.00000000.00000000.00000000
#size-cells: 00000002
#address-cells: 00000003
name: 'pci'
Node 0x000004
reg: 00000000.00000000.00000000.00000000.00000000
compatible: 'pci8086,44.1028.410.2' + 'pci8086,44.1028.410' + 'pci1028,410' + 'pci8086,44.2' + 'pci8086,44' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '0'
class-code: 00060000
revision-id: 00000002
vendor-id: 00008086
device-id: 00000044
name: 'pci1028,410'
Node 0x000005
acpi-namespace: '\_SB_.PCI0.VID_'
assigned-addresses: 83001010.00000000.f0000000.00000000.00400000.c3001018.00000000.e0000000.00000000.10000000.81001020.00000000.000060b0.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
reg: 00001000.00000000.00000000.00000000.00000000.03001010.00000000.00000000.00000000.00400000.43001018.00000000.00000000.00000000.10000000.01001020.00000000.00000000.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
compatible: 'pci8086,46.1028.410.2' + 'pci8086,46.1028.410' + 'pci1028,410' + 'pci8086,46.2' + 'pci8086,46' + 'pciclass,030000' + 'pciclass,0300'
model: 'VGA compatible controller'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
device_type: 'display'
unit-address: '2'
class-code: 00030000
revision-id: 00000002
vendor-id: 00008086
device-id: 00000046
name: 'display'
Node 0x000006
acpi-namespace: '\_SB_.PCI0.GLAN'
assigned-addresses: 8200c810.00000000.f5400000.00000000.00020000.8200c814.00000000.f5480000.00000000.00001000.8100c818.00000000.00006040.00000000.00000020
reg: 0000c800.00000000.00000000.00000000.00000000.0200c810.00000000.00000000.00000000.00020000.0200c814.00000000.00000000.00000000.00001000.0100c818.00000000.00000000.00000000.00000020
compatible: 'pci8086,10ea.1028.410.5' + 'pci8086,10ea.1028.410' + 'pci1028,410' + 'pci8086,10ea.5' + 'pci8086,10ea' + 'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '19'
class-code: 00020000
revision-id: 00000005
vendor-id: 00008086
device-id: 000010ea
name: 'pci1028,410'
Node 0x000007
acpi-namespace: '\_SB_.PCI0.EHC2'
assigned-addresses: 8200d010.00000000.f5470000.00000000.00000400
reg: 0000d000.00000000.00000000.00000000.00000000.0200d010.00000000.00000000.00000000.00000400
compatible: 'pci8086,3b3c.1028.410.5' + 'pci8086,3b3c.1028.410' + 'pci1028,410' + 'pci8086,3b3c.5' + 'pci8086,3b3c' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1a'
class-code: 000c0320
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b3c
name: 'pci1028,410'
Node 0x000008
acpi-namespace: '\_SB_.PCI0.HDEF'
assigned-addresses: 8300d810.00000000.f5460000.00000000.00004000
reg: 0000d800.00000000.00000000.00000000.00000000.0300d810.00000000.00000000.00000000.00004000
compatible: 'pciex8086,3b57.1028.410.5' + 'pciex8086,3b57.1028.410' + 'pciex8086,3b57.5' + 'pciex8086,3b57' + 'pciexclass,040300' + 'pciexclass,0403' + 'pci8086,3b57.1028.410.5' + 'pci8086,3b57.1028.410' + 'pci1028,410' + 'pci8086,3b57.5' + 'pci8086,3b57' + 'pciclass,040300' + 'pciclass,0403'
model: 'Mixed Mode device'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1b'
class-code: 00040300
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b57
name: 'pci1028,410'
Node 0x000009
acpi-namespace: '\_SB_.PCI0.RP01'
slot-names: 00000001.746f6c53.00003333
reg: 0000e000.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b42.5' + 'pciex8086,3b42' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b42.5' + 'pci8086,3b42' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00005000.81000000.00000000.00005000.00000000.00001000.82000000.00000000.f4000000.82000000.00000000.f4000000.00000000.01400000
bus-range: 00000001.00000001
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000000
devsel-speed: 00000000
interrupts: 00000001
unit-address: '1c'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b42
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b42'
Node 0x00000a
acpi-namespace: '\_SB_.PCI0.RP02'
slot-names: 00000001.746f6c53.00003433
reg: 0000e100.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b44.5' + 'pciex8086,3b44' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b44.5' + 'pci8086,3b44' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00004000.81000000.00000000.00004000.00000000.00001000.82000000.00000000.f2c00000.82000000.00000000.f2c00000.00000000.01400000
bus-range: 00000002.00000002
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000001
devsel-speed: 00000000
interrupts: 00000002
unit-address: '1c,1'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b44
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b44'
Node 0x000013
acpi-namespace: '\_SB_.PCI0.RP02.PXSX'
assigned-addresses: 83020010.00000000.f2c00000.00000000.00002000
reg: 00020000.00000000.00000000.00000000.00000000.03020010.00000000.00000000.00000000.00002000
compatible: 'pciex8086,422c.8086.1321.35' + 'pciex8086,422c.8086.1321' + 'pciex8086,422c.35' + 'pciex8086,422c' + 'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,422c.8086.1321.35' + 'pci8086,422c.8086.1321' + 'pci8086,1321' + 'pci8086,422c.35' + 'pci8086,422c' + 'pciclass,028000' + 'pciclass,0280'
model: 'Network controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00008086
subsystem-id: 00001321
unit-address: '0'
class-code: 00028000
revision-id: 00000035
vendor-id: 00008086
device-id: 0000422c
name: 'pci8086,1321'
Node 0x00000b
acpi-namespace: '\_SB_.PCI0.RP03'
slot-names: 00000001.746f6c53.00000038
reg: 0000e200.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b46.5' + 'pciex8086,3b46' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b46.5' + 'pci8086,3b46' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00003000.81000000.00000000.00003000.00000000.00001000.82000000.00000000.f1800000.82000000.00000000.f1800000.00000000.01400000
bus-range: 00000003.00000003
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000002
devsel-speed: 00000000
interrupts: 00000003
unit-address: '1c,2'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b46
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b46'
Node 0x000014
acpi-namespace: '\_SB_.PCI0.RP03.PXSX'
assigned-addresses: 82030010.00000000.f1830000.00000000.00000100
reg: 00030000.00000000.00000000.00000000.00000000.02030010.00000000.00000000.00000000.00000100
compatible: 'pciex1180,e822.1028.410.1' + 'pciex1180,e822.1028.410' + 'pciex1180,e822.1' + 'pciex1180,e822' + 'pciexclass,080500' + 'pciexclass,0805' + 'pci1180,e822.1028.410.1' + 'pci1180,e822.1028.410' + 'pci1028,410' + 'pci1180,e822.1' + 'pci1180,e822' + 'pciclass,080500' + 'pciclass,0805'
model: 'SD Host controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '0'
class-code: 00080500
revision-id: 00000001
vendor-id: 00001180
device-id: 0000e822
name: 'pci1028,410'
Node 0x00000c
acpi-namespace: '\_SB_.PCI0.RP04'
slot-names: 00000001.746f6c53.00000039
reg: 0000e300.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b48.5' + 'pciex8086,3b48' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b48.5' + 'pci8086,3b48' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00002000.81000000.00000000.00002000.00000000.00001000.82000000.00000000.f0400000.82000000.00000000.f0400000.00000000.01400000
bus-range: 00000004.00000009
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000003
devsel-speed: 00000000
interrupts: 00000004
unit-address: '1c,3'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b48
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b48'
Node 0x00000d
acpi-namespace: '\_SB_.PCI0.EHCI'
assigned-addresses: 8200e810.00000000.f5450000.00000000.00000400
reg: 0000e800.00000000.00000000.00000000.00000000.0200e810.00000000.00000000.00000000.00000400
compatible: 'pci8086,3b34.1028.410.5' + 'pci8086,3b34.1028.410' + 'pci1028,410' + 'pci8086,3b34.5' + 'pci8086,3b34' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1d'
class-code: 000c0320
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b34
name: 'pci1028,410'
Node 0x00000e
acpi-namespace: '\_SB_.PCI0.P0P1'
slot-names: 0000002f.746f6c53.6c530031.0032746f.746f6c53.6c530033.0034746f.746f6c53.00000032
reg: 0000f000.00000000.00000000.00000000.00000000
compatible: 'pci8086,2448.a5' + 'pci8086,2448' + 'pciclass,060401' + 'pciclass,0604'
model: 'Subtractive Decode PCI-PCI bridge'
bus-range: 0000000a.0000000a
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pci'
power-consumption: 00000001.00000001
devsel-speed: 00000000
unit-address: '1e'
class-code: 00060401
revision-id: 000000a5
vendor-id: 00008086
device-id: 00002448
name: 'pci8086,2448'
Node 0x00000f
#size-cells: 00000001
#address-cells: 00000002
ranges: 00000001.00000000.81000000.00000000.00000000.00000022.00000001.00000024.81000000.00000000.00000024.00000002.00000001.00000028.81000000.00000000.00000028.00000002.00000001.0000002c.81000000.00000000.0000002c.00000006.00000001.00000034.81000000.00000000.00000034.00000002.00000001.00000038.81000000.00000000.00000038.00000002.00000001.0000003c.81000000.00000000.0000003c.00000002.00000001.00000040.81000000.00000000.00000040.00000004.00000001.0000004e.81000000.00000000.0000004e.00000006.00000001.00000060.81000000.00000000.00000060.00000002.00000001.00000063.81000000.00000000.00000063.00000003.00000001.00000067.81000000.00000000.00000067.00000001.00000001.00000070.81000000.00000000.00000070.00000008.00000001.00000070.81000000.00000000.00000070.00000001.00000001.00000080.81000000.00000000.00000080.00000022.00000001.000000a4.81000000.00000000.000000a4.00000002.00000001.000000a8.81000000.00000000.000000a8.00000002.00000001.000000ac.81000000.00000000.000000ac.00000002.00000001.000000b0.81000000.00000000.000000b0.00000006.00000001.000000b8.81000000.00000000.000000b8.00000002.00000001.000000bc.81000000.00000000.000000bc.00000002.00000001.000000c0.81000000.00000000.000000c0.00000020.00000001.000000f0.81000000.00000000.000000f0.00000001.00000001.00000400.81000000.00000000.00000400.00000080.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000500.81000000.00000000.00000500.00000080.00000001.00000680.81000000.00000000.00000680.00000020.00000001.00000930.81000000.00000000.00000930.00000001.00000001.00000934.81000000.00000000.00000934.00000001.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00001000.81000000.00000000.00001000.00000014.00000001.0000164e.81000000.00000000.0000164e.00000002.00000001.0000ffff.81000000.00000000.0000ffff.00000001.00000000.f54c0000.82000000.00000000.f54c0000.00001000.00000000.f8000000.82000000.00000000.f8000000.04000000.00000000.fed00000.82000000.00000000.fed00000.00000400.00000000.fed10000.82000000.00000000.fed10000.00004000.00000000.fed18000.82000000.00000000.fed18000.00002000.00000000.fed1c000.82000000.00000000.fed1c000.00024000.00000000.fed45000.82000000.00000000.fed45000.0004b000.00000000.fee00000.82000000.00000000.fee00000.00100000.00000000.ff000000.82000000.00000000.ff000000.01000000.00000000.ff000000.82000000.00000000.ff000000.01000000
acpi-namespace: '\_SB_.PCI0.LPCB'
device_type: 'isa'
reg: 0000f800.00000000.00000000.00000000.00000000
compatible: 'pci8086,3b0f.1028.410.5' + 'pci8086,3b0f.1028.410' + 'pci1028,410' + 'pci8086,3b0f.5' + 'pci8086,3b0f' + 'pciclass,060100' + 'pciclass,0601'
model: 'ISA bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f'
class-code: 00060100
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b0f
name: 'isa'
Node 0x00001c
unit-address: '1,60'
interrupts: 00000001.0000000c
reg: 00000001.00000060.00000001.00000001.00000064.00000001
name: 'i8042'
Node 0x00001d
compatible: 'pnpPNP,303'
device-type: 'keyboard'
interrupts: 00000001.0000000c
reg: 00000000
acpi-namespace: '\_SB_.PCI0.LPCB.PS2K'
model: 'System keyboard'
name: 'keyboard'
Node 0x00001e
compatible: 'pnpPNP,f03'
device-type: 'mouse'
reg: 00000001
interrupts: 0000000c
acpi-namespace: '\_SB_.PCI0.LPCB.PS2M'
model: 'PS/2 Port for PS/2-style Mice'
name: 'mouse'
Node 0x00001f
interrupts: 00000004
reg: 00000001.000003f8.00000008
model: 'Standard serial port'
compatible: 'PNP0500'
name: 'asy'
Node 0x000010
acpi-namespace: '\_SB_.PCI0.SAT0'
assigned-addresses: 8100fa10.00000000.00006090.00000000.00000008.8100fa14.00000000.00006080.00000000.00000004.8100fa18.00000000.00006070.00000000.00000008.8100fa1c.00000000.00006060.00000000.00000004.8100fa20.00000000.00006020.00000000.00000020.8200fa24.00000000.f5440000.00000000.00000800
reg: 0000fa00.00000000.00000000.00000000.00000000.0100fa10.00000000.00000000.00000000.00000008.0100fa14.00000000.00000000.00000000.00000004.0100fa18.00000000.00000000.00000000.00000008.0100fa1c.00000000.00000000.00000000.00000004.0100fa20.00000000.00000000.00000000.00000020.0200fa24.00000000.00000000.00000000.00000800
compatible: 'pci8086,3b2f.1028.410.5' + 'pci8086,3b2f.1028.410' + 'pci1028,410' + 'pci8086,3b2f.5' + 'pci8086,3b2f' + 'pciclass,010601' + 'pciclass,0106'
model: 'SATA AHCI 1.0 Interface'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,2'
class-code: 00010601
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b2f
name: 'pci1028,410'
Node 0x000011
acpi-namespace: '\_SB_.PCI0.SBUS'
assigned-addresses: 8300fb10.00000000.f5430000.00000000.00000100.8100fb20.00000000.00006000.00000000.00000020
reg: 0000fb00.00000000.00000000.00000000.00000000.0300fb10.00000000.00000000.00000000.00000100.0100fb20.00000000.00000000.00000000.00000020
compatible: 'pci8086,3b30.1028.410.5' + 'pci8086,3b30.1028.410' + 'pci1028,410' + 'pci8086,3b30.5' + 'pci8086,3b30' + 'pciclass,0c0500' + 'pciclass,0c05'
model: 'SMBus (System Management Bus)'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,3'
class-code: 000c0500
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b30
name: 'pci1028,410'
Node 0x000012
assigned-addresses: 8300fe10.00000000.f5420000.00000000.00001000
reg: 0000fe00.00000000.00000000.00000000.00000000.0300fe10.00000000.00000000.00000000.00001000
compatible: 'pci8086,3b32.1028.410.5' + 'pci8086,3b32.1028.410' + 'pci1028,410' + 'pci8086,3b32.5' + 'pci8086,3b32' + 'pciclass,118000' + 'pciclass,1180'
model: 'DSP/DAP controllers'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,6'
class-code: 00118000
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b32
name: 'pci1028,410'
Node 0x000015
device_type: 'acpirootnex'
compatible: 'SOLA0001' + 'acpirootnex' + 'SOLA0002' + 'acpivirtnex'
acpi-namespace: '\'
name: 'fw'
Node 0x000016
unit-address: '1'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000000
acpi-processor-id: 00000001
acpi-namespace: '\_PR_.CPU0'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000017
unit-address: '2'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000004
acpi-processor-id: 00000002
acpi-namespace: '\_PR_.CPU1'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000018
unit-address: '3'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000001
acpi-processor-id: 00000003
acpi-namespace: '\_PR_.CPU2'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000019
unit-address: '4'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000005
acpi-processor-id: 00000004
acpi-namespace: '\_PR_.CPU3'
device_type: 'acpicpu'
name: 'cpu'
Node 0x00001a
unit-address: '0'
compatible: 'acpidevice' + 'SOLA0002' + 'acpivirtnex'
acpi-namespace: '\_SB_'
device_type: 'acpidevice'
name: 'sb'
Node 0x00001b
io-space: 00000000.00000020.00000020.00000002.00000024.00000002.00000028.00000002.0000002c.00000002.0000002e.00000002.00000030.00000002.00000034.00000002.00000038.00000002.0000003c.00000002.00000040.00000004.0000004e.00000002.00000050.00000004.00000060.00000001.00000061.00000001.00000063.00000001.00000064.00000001.00000065.00000001.00000067.00000001.00000070.00000008.00000070.00000001.00000080.00000001.00000081.00000011.00000092.00000001.00000093.0000000d.000000a0.00000002.000000a4.00000002.000000a8.00000002.000000ac.00000002.000000b0.00000002.000000b2.00000002.000000b4.00000002.000000b8.00000002.000000bc.00000002.000000c0.00000020.000000f0.00000001.00000400.00000080.000004d0.00000002.00000500.00000080.00000680.00000020.00000930.00000001.00000934.00000001.00000cf8.00000008.00001000.00000004.00001004.00000010.0000164e.00000002.0000ffff.00000001
device-memory: f54c0000.00001000.f8000000.04000000.fed00000.00000400.fed10000.00004000.fed18000.00001000.fed19000.00001000.fed1c000.00004000.fed20000.00020000.fed45000.0004b000.fee00000.00100000.ff000000.01000000.ff000000.01000000
dma-channels: 00000004
interrupts: 00000000.00000001.00000002.00000008.0000000c.0000000d
name: 'used-resources'
prtdiag:
System Configuration: Dell Inc. Latitude E4310
BIOS Configuration: Dell Inc. A05 11/20/2010
==== Processor Sockets ====================================
Version Location Tag
Intel(R) Core(TM) i5 CPU M 560 @ 2.67GH CPU 1
==== Memory Device Sockets ================================
Type Status Set Device Locator Bank Locator
Unknown in use 0 DIMM_A BANK 0
unknown empty 0 DIMM_B BANK 2
==== On-Board Devices =====================================
"Intel GM45 Graphics"
NETWORK_NAME_STRING
==== Upgradeable Slots ====================================
ID Status Type Description
0 available PCI Express x16 J5C1
1 available PCI Express J6C2
2 in use PCI Express J6D2
3 in use PCI Express J7C1
4 available PCI Express J7D2
System Information:
Manufacturer:Dell Inc.
Product:Latitude E4310
BIOS Information:
Vendor:Dell Inc.
Version:A05
Release Date:11/20/2010
BIOS Revision: BIOS Revision:4.6
Firmware Revision:
MotherBoard Information:
Product:0D8H24
Manufacturer:Dell Inc.
Version:A00
Onboard Devices:[Video,Disabled]"Intel GM45 Graphics"
CPU Information:
Processor 0:
Processor Socket Type:CPU 1
Processor Manufacturer:Intel
Current Voltage:0.0V
External Clock:533MHZ
Max Speed:4000MHZ
Current Speed:2666MHZ
Memory Information:
Physical Memory: 4G (4G)
Maximum Memory Support: 4096G
Memory Subsystem 0:
Array Used Function:System memory
Memory Error Correction Supported:None
Maximum Array Capacity:8G
Number of Memory Devices:2
Memory Device 0:
Memory Device Locator:DIMM_A
Total Width:64
Data Width:64
Installed Size:4096M
Memory Device Type:Unknown
Speed:1067MHZ
Memory Device 1:
[Not Installed]

Similar Messages

Installation problems with Solaris 8 on Intel

Howdy,
I am having some problem with my installation of Solaris 8 on Intel. I am installing the system on a P133 (Asus TX97 motherboard). When I first start the installation and perform the system scan I get the following error:
The PnP ISA: IDE Controller programable device was unable to be programmed.
This could be caused by two possible reasons:
- Lack of resouces available
- There is a conflict with the following already-existing device: 8086,7111 - Bus Mastering IDE Controller
When I bring up the View/Edit device settings and I scroll to the IDE controller there is an ! mark beside the PCI IDE controller. The controler is specifying: Bus 0, device: 1, function: 1 port 1F0-1F7, 3F6, 170-177, 376, E000-E00F, 0 IRQ 14, 15
Does anyone have any suggestions on how to resolve this conflict? I tried removing the PCI IDE interface and then installing a ISA IDE interfact (for IRQ: 14, IRQ 15 automatically put a PnP IDE controller there). This seemed to resolve the conflict but then I received a: No Bootable devices have been found.
If anyone can help out with how to resolve the conflict, or what the No Bootable Devices have been found error it would be greatly appreciated.
Currently there is a partition set up with NT on it, but I wish to basically get rid of everything on the HD and install Solaris on it. FYI, when I check the HD's in NT it mentions I/0: 1F0-1F7 IRQ 14 and also I/O 170-177 IRQ 15.
Any help would greatly be appreciated.
Regards,
S.

When I close down Solais in the CDE I am taken back to the logon screen
and I turn the PC off.Don't do that. If you simply turn off the PC, the OS has no chance to
write back cached / modified disk data back to the HDD - this is also the
reason why solaris has to check the filesystems on the next boot and apparently
has to repair filesystem defects.
What you have to do is shutdown the machine, before you can power it off.
Login as user "root" and use the command
init 5
or
halt
"init 5" will shutdown system services, by executing commands from
/etc/rc0.d/K* with argument "stop". Then it'll sync all modified disk blocks to
the HDD, kills all remaining processes and unmounts all filesystems. In this
state it's safe to power off the machine!
"halt" is a quick-and-dirty shutdown. It does not stop system services (the
/etc/rc0.d/K* commands are not run). But, it syncs all modified disk blocks
to the HDD, kills all processes and unmounts all filesystems. "init 5" is preferred,
especially if you have services like a database server running on the machine,
which needs to be cleanly shutdown. On the other hand, with a default solaris
installation and no extra services, a simple "halt" should be OK.
Btw. if multiple users are logged in on the machine, you should also have a look
at the shutdown(1M) command. "shutdown" sends warnings to the logged in
users that the machine is about to be shut down, ...

Several mysterious problems with Solaris 11 x86 install

Hi folks,
I've recently installed Solaris 11 x86 as a replacement for Solaris 9 SPARC on an Ultra 2 machine. I like the operating system, but I've promptly acquired some mysterious problems. The computer is a Fujitsu Siemens Esprimo E2500 with a Pentium 4 HT 3.06 GHz processor, 2 GB RAM, an 80 GB SATA disk and a 147 GB SCSI disk.
I have had a few occasions on which the screen goes totally blank, the monitor claims that there is no signal, and I have to restart the machine. However, with the blank screen, the hard drive activity light is sometimes still flashing. This happens predictably when I try to log off (as opposed to shutting down) and when I use Totem media player and click on anything inside the Totem window. The motherboard has built-in graphics and brief specifications can be found here:
http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRIMO/Datasheets/ds_esprimo_edition_e2500.pdf
Yesterday my PS/2 keyboard started causing the motherboard to beep crazily when I use it. It beeps rapidly 4 times, then prints the expected character. However, the problem doesn't occur at the initial log in screen. The mouse cursor has also gone beserk on one occasion, flying all over the screen (I had this problem with a previous PC, but a different OS, and thought it was a hardware fault, which I why I got this new computer). With the keyboard problem, the machine is basically unusable. However, it is configured as a dual boot machine, and the keyboard problem isn't present with Windows XP.
There are also a few smaller, odd problems. Occasionally all the icons vanish from my Gnome desktop. The command prompt also mysteriously changed from $chris@pluto to $bash-4.1 just before the keyboard problem appeared, although that might have had something to do with me copying my home directory to a different disk and editing the /etc/auto_home file (moving the home directory worked fine). Also, unlike with Solaris 9 SPARC, I find that I have to have external SCSI devices switched on at boot time, should I want to use them later. That's a pain. With Solaris 9, I could run "boot -r" when I first attached the device, then switch on the SCSI devices and mount them whenever I wanted.
After the useful advice I received here about "more" and "less", I thought I'd post these problems and see if anyone can help. I'd really appreciate some advice. Can anyone identify likely causes for these problems? Which problems can I expect to solve and which do I have to live with?
Many thanks,
Chris Tidy
Edited by: Chris Tidy on 23-Mar-2012 03:36

Hi folks,
I've recently installed Solaris 11 x86 as a replacement for Solaris 9 SPARC on an Ultra 2 machine. I like the operating system, but I've promptly acquired some mysterious problems. The computer is a Fujitsu Siemens Esprimo E2500 with a Pentium 4 HT 3.06 GHz processor, 2 GB RAM, an 80 GB SATA disk and a 147 GB SCSI disk.
I have had a few occasions on which the screen goes totally blank, the monitor claims that there is no signal, and I have to restart the machine. However, with the blank screen, the hard drive activity light is sometimes still flashing. This happens predictably when I try to log off (as opposed to shutting down) and when I use Totem media player and click on anything inside the Totem window. The motherboard has built-in graphics and brief specifications can be found here:
http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRIMO/Datasheets/ds_esprimo_edition_e2500.pdf
Yesterday my PS/2 keyboard started causing the motherboard to beep crazily when I use it. It beeps rapidly 4 times, then prints the expected character. However, the problem doesn't occur at the initial log in screen. The mouse cursor has also gone beserk on one occasion, flying all over the screen (I had this problem with a previous PC, but a different OS, and thought it was a hardware fault, which I why I got this new computer). With the keyboard problem, the machine is basically unusable. However, it is configured as a dual boot machine, and the keyboard problem isn't present with Windows XP.
There are also a few smaller, odd problems. Occasionally all the icons vanish from my Gnome desktop. The command prompt also mysteriously changed from $chris@pluto to $bash-4.1 just before the keyboard problem appeared, although that might have had something to do with me copying my home directory to a different disk and editing the /etc/auto_home file (moving the home directory worked fine). Also, unlike with Solaris 9 SPARC, I find that I have to have external SCSI devices switched on at boot time, should I want to use them later. That's a pain. With Solaris 9, I could run "boot -r" when I first attached the device, then switch on the SCSI devices and mount them whenever I wanted.
After the useful advice I received here about "more" and "less", I thought I'd post these problems and see if anyone can help. I'd really appreciate some advice. Can anyone identify likely causes for these problems? Which problems can I expect to solve and which do I have to live with?
Many thanks,
Chris Tidy
Edited by: Chris Tidy on 23-Mar-2012 03:36

Video problems with solaris 10

Has any gotten solaris 10 working with an IBM Net Vista workstation? I am having problems with setting it up in desktop mode.

I have had problems with all versions of Solaris on anything but Sun hardware.
I hate MS but they do manage to get their OS to run on almost anything.
Maybe Sun never made it big because they chase away customers with products that don't work.
I would never sell a Sun product to any of my clients.
I only use it in the classroom because I have to.

Directory server 4.12 and 4.15 problem with Solaris 8

Hi there,
I have been having an ongoing problem with my read/write master
directory server. It
occasionally stops responding to bind attempts and queries. The current
setup as is running
on a Sunfire 280R with Solaris 8. Up until a few days ago I was running
4.12, I upgraded this
to 4.15 to see of the problem would go away. I am running several 4.13
replicas on other
Solaris 8 machines with no problems.
The biggest problem is that this master directory server is needed for
our Iplanet messaging
server 5.1 implementation. Every time the directory fails you cannot log
in to the messaging
server. (there doesn't appear to be anyway of sending authentication to
a read only server).
Anyway I was just wanting to see if anyone else had the same problem or
had fixed it and could
provide some insight into how to fix it. Also any pointers on what to
look for in the directory
server error logs would be useful.
I had an idea that it might have been running out of available
connections so I set it to close idle
connections after 300 seconds. Is there any docs on tuning the resources
for the server or for
identifying if you have a resource problem?
Any help or ideas would be appreciated. Please contact me directly as
well as to the newsgroup
if possible.
Thanks,
Scott.
Scott Lawson
Systems Manager
Department Of Information Services
St. George's Hospital Medical School
Tooting
London SW17 0RE
UK
P: 44 (0)208 725 2896
F: 44 (0)208 725 3583
mailto:[email protected]
http://www.sghms.ac.uk
Your mouse has moved.
Windows must be restarted for the change to take effect.
Reboot now? [OK]
__________________________________________________________________

Scott Lawson <[email protected]> wrote in news:3BCAA419.E322F958
@sghms.ac.uk:
>
I had an idea that it might have been running out of available
connections so I set it to close idle
connections after 300 seconds. Is there any docs on tuning the resources
for the server or for
identifying if you have a resource problem?4.15 hotfix solves a problem with FDs running out (apparently .... we are
still testing0.
/* Christopher Burke - Spam Mail to [email protected]
|*
\* Real mail to cburke(at)craznar(dot)com

Thread Problems with Solaris 2.7 and Java 1.3

Hi,
we are deploying a Java distributed application, based on JAVA 1.3, on a SOLARIS 2.7 system and we are meeting some problems with threads.
This application uses a distribuite computing based on ORBIX 2000 environment and creates more than 40 threads.
Sometimes happens that one or more threads ( consider that all the threads have the same priority) are no more scheduled even tought they have some work to do into the local queue.
We have tested the application on a NT system and the problem does not appears.
Do you have some suggestion ?
PS: Note that all the other threads work well and it seems that the problem is not related to a Orbix method.
Thanks
Roberto

It crashed 3 seconds after it is running. Should be reading some jar file.
Could be a something corrupted a zip file or something. Can you still do a java -version? You may want to try reinstalling 1.4.2_07

Problems with Solaris 10 + mod_wl_20

Hello all,
I've been trying to get apache 2.0.58 that's shipped with Solaris 10 (Sparc) with mod_wl_20 from Weblogic 8.1 SP6 with not much luck.
Every time I try connect to a mapped application via Apache+weblogic_mod I keep getting 404, it seems like the plugin isn't even being invoked, as apaches logs keep saying:
File does not exist: /var/apache2/htdocs/examplesWebApp
I copied over mod_wl_20.so from WEBLOGIC_HOME/server/lib/solaris and put it on the solaris box with apache in the libexec directory.
My httpd.conf is basically a copy of the httpd.conf-example with the following entries:
LoadModule weblogic_module libexec/mod_wl_20.so
<Location /examplesWebApp>
SetHandler weblogic-handler
WebLogicHost 192.168.10.120
WebLogicPort 7001
Debug ON
WLLogFile /tmp/test.log
DebugConfigInfo On
</Location>
Strange thing, the /tmp/test.log file gets created, but no logging dumped there.
If I connect to the Weblogic Server host, via port 7001 the examplesWebApp works just fine.
Have I missed something? - is the version of Apache2 that comes with solaris 10 okay?
Thanks for help in advanced.
_rob

Hi haili,
Thanks for the reply, I've modified my entry in httpd.conf to
<Location /examplesWebApp>
SetHandler weblogic-handler
WebLogicHost 192.168.10.120
WebLogicPort 7001
Debug ALL
WLLogFile /tmp/weblogic.log
WLTempDir /tmp
DebugConfigInfo ON
</Location>
The log file /tmp/weblogic.log is no longer been created.
Has anyone got it to work with the standard apache 2.0.58 shipped with solaris 10?
Thanks,
_rob

Mounting problem with Solaris 10

Hi everybody !
I am new in Solaris admin (come from HP !)
here is my problem :
i have to create a FS (would be only data in it) that would be shared by 2 zones working on a fail-over principe.
So i create this FS directly under the global zone.
But i can't find in the Man pages the options of mount that tell the 2 zones to have their entries alternatively on this new FS
waiting for your advices, thanks in advance.
Titine.

You don;t need to mount the FS by NFS unless your talking about zones on two different machines.
Two zones on the same machine can import the same filesystem with no problems.
But I'm unclear as to what your trying to achieve. Two zones on the same machines provides no real failover because if the machine goes down so do both zones.
Your best option is to have the FS on one machine and NFS export it to 2 other machines.
Theres no real advantage to using zones here of course. But you can if you prefer.
Of course the machine hosting the FS is still a single point of failure unless you use a SAN and HA-NFS.

Problem with solaris install/boot

I recently had to use solaris at work and liked it. So thought of getting it on intel box at home to learn it. I have never worked on a unix based OS before. When I installed the OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem i had to reinstall OS, installation went fine and but when i reboot i get this errror.
cannot find mis/krtld
boot error loading interpreter(misc/krtld)
elf32 read error
load error read of "platform/i86pc/kernel/unix failed.
boot path /pci@0,0/pci-ide@1f,1/ide0/cmdk@0,0:a
i have been trying to reinstall with many option like formatting with windows fdisk, linux installer everything as I saw somehwre that disk needs low level format.
I have googled but could not find any reason.
When I try to format disk using windows this is the information gatherd
Partition1 (solarisboot) 12 MB
partition2 unknown 152610
Hardware
pentium4 2.4 GHZ
1Gb DDR memor
Intel Original mother board.
140 Gb hard disk
Installation
install type 3 (tried all options)
entire disk for boot and solaris
accepted almost all parameters.
downloaded again , burned a DVD still same.
Any help will be highly apreciated, as I have been trying out everything I could find, also I really want to learn to use solaris

Weird; it wouldn't be so hard installing/running Solaris 10 on your hardware.
If you haven't tried Solaris 11 (Solaris Express) yet, I would suggest you to download the latest Solaris Express bits from http://www.sun.com/software/solaris/solaris-express/get.jsp.
Hope the following hints are useful, for a smooth installation:
Choose:
* Solaris Interactive installation in the initial screen.
* Networked in Network Connectivity screen
* Use DHCP
* No to IPv6 & Kerberos, if running Solaris 10 is the only priority
* None to Name Service (assuming the machine is not in corporate network)
* CD/DVD to "Specify Media"
* Default Install to "Select type of install"
* No to "Do you need to override the system's default NFS version 4 domain name?"
Note:
Once the installation from CD1 is complete, system boots up from the hard disk; and it may appear that it is not going to ask for CD2. Just be patient, and wait for it to ask you about CD2.
Relevant resources:<ol><li>http://docs.sun.com/app/docs/doc/817-0544/6mgbagb1b?a=view (instructions)
<li>http://shots.osdir.com/slideshows/slideshow.php?release=279&slide=1 (screen shots)</ol>Good Luck!
http://technopark02.blogspot.com

Problems with Solaris 10 Secure Desktop server and Windows XP Client

Solaris 10 Secure Desktop server - Windows XP Client - I've tried to open the Solaris Machine's desktop using the browser based http://MysolarisServerName/sdg and the windows native client
http://MySolarisServerName/tarantella.
I log in ok to the Solaris Server.
I can open a VT420 session with the solaris machine, and this works OK, but whenever I try anything else e.g. smc, or full screen desktop it doesn't. I get various error messages e.g. can't open display, and Session Failed - X Session timeout.
I've also installed Cgywin X Server on the Win XP machine to see if this makes a difference, but it doesn't.
Any clues anyone?

Being able to run the VT420 session, but not any X-Window sessions is the clue; it's an X-specific problem. Most likely, ssh isn't configured correctly, see: http://docs.sun.com/source/819-4309-10/en-us/base/indepth/ssh.html
Pasting in the (most) relevant bit:
Adding support for X applications
To support X applications through OpenSSH, enable X11 forwarding in the OpenSSH configuration file. On each Secure Global Desktop host:
1. Edit the sshd_config file and include the following:
X11Forwarding yes
2. Edit the ssh_config file and include the following:
ForwardAgent yes
ForwardX11 yes
3. Restart the SSH daemon.
Using SSH and X authorization
If SSH connections fail, when X authorization is enabled, you may have to run the SSH daemon in ipv4-only mode because Secure Global Desktop may not support the xsecurity extension used on your server. You enable ipv4-only mode by editing your system SSH configuration file. For example:
* On SUSE Linux, edit the /etc/sysconfig/ssh file and add a SSHD_OPTS="-4" line.
* On Red Hat Enterprise Linux, edit the /etc/sysconfig/sshd file and add a OPTIONS="-4" line.
Note If the SSH configuration file does not exist on your system, you can create it.
You must restart the SSH daemon after making this change.

Problems with Solaris Web Console on Solaris 10 x86

I recently installed Solaris 10 x86 (10/08 release) on a Sun x4450.
I have installed the Jan 14, 2009 patch cluster.
I was having some problems connecting to the Web Console to do some ZFS administration. That's when I installed the patch cluster.
After the patch cluster install I couldn't connect at all. This problem was resolved here: http://forums.sun.com/thread.jspa?threadID=5249136
Now when I login to the Web Console I get a message that says:
"+No application is registered with this Sun Java(TM) Web Console, or you have no rights to use any applications that are registered. See your system administrator for assistance.+"
I'm logging in as root, so it shouldn't be a rights issue.

Quick Solution to the problem you are facing
How to configure ZFS Webconsole Administration
run this command
wcadmin deploy -a zfs -z zfs /usr/share/webconsole/webapps/zfs
you should be able to see & Manage ZFS in Applications area of webconsole.
Enjoy ! Cheers

Link problem with Solaris 9

hello,
i habe a problem in linking my application under the Solaris 9 os using the forte cc environment. Linking on an older machine under Solaris 8 is ok.
I get this error:
ld: fatal: file fz_df_db_anmelden.o: wrong ELF class: ELFCLASS64
ld: fatal: File processing errors. No output written to FZDFNO
There must be a conflict with 32 and 64 bit libraries. How can i link either in 32 or 64 bit. I need both, because the application shall also run on an 32 bit system.
best regards
Stefan

What about the bios settings ? The sony laptop that I have as an install guinea pig had a host of problems as long as plug and play was turned on in the bios then I turned off IrDa and the box seemed a bit quicker. Once I turned PnP off the USB ports started working as well as an external hp 3button mouse. Still no luck with the PCMCIA NIC's though...

Installation problem with Solaris 2.6 on E220R server

Dear Sir/Madam,
I got the problem to install Solaris 2.6 on the new E220R server and
would appreciate if someone can give me some hint/trick how to fix it.
Firsly I boot the machine using the OPERATING ENVIRONMENT INSTALLATION
CD and then selected Solaris 2.6 and from there I used the Solaris 2.6
CD to install.
The installation went OK however after reboot the OS complained that it
could NOT open the "kernel/unix".
Please send me a copy of your answer to
[email protected]
Thanks in advance,
Trung Nguyen

The response is "/platform/sun4u/kernel/unix".
You will be asked another question, but you can just hit enter in response.
Of course, this solution begs the issue of why it happens in the first place.

Problem with SOLARIS INTEL SOFTWARE 2

I can't install software from the second CD of intel software. When I use WebStart, it says that
/usr/bin/bzcat is not present so pkgadd can't work and if I try to install with Admintool, it cannot find
/usr/bin/bzcat too.
Any suggestion ???

Just to let you know you are not allone: We have a similar problem here. I have no idea what they mean with the file: itmpt-x86-XXX-itu.dd
Its just not there. Did you solve the problem in the meanwhile?
Greetings Andreas

Problem with solaris 10 08/11 installation on x86 workstation (DELL T5500)

Trying to install solaris 10 08/11 installation on x86 workstation (DELL T5500). Following error message was received after selecting the Oracle Solaris interactive Text (Desktop Session) installation method-
SunOS Release 5.10 Version Generic_147441-01 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Configuring devices.
SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: 0x5075a820.0x8f97a90 (0x1693e68979)
PLATFORM: i86pc, CSN: -, HOSTNAME:
SOURCE: SunOS, REV: 5.10 Generic_147441-01
DESC: Errors have been detected that require a reboot to ensure system
integrity. See http://www.sun.com/msg/SUNOS-8000-0G for more information.
AUTO-RESPONSE: Solaris will attempt to save and diagnose the error telemetry
IMPACT: The system will sync files, save a crash dump if needed, and reboot
REC-ACTION: Save the error summary below in case telemetry cannot be saved
panic[cpu0]/thread=fffffe80000b3c60: pcieb-7: PCI(-X) Express Fatal Error. (0x4)
fffffe80000b3bf0 pcieb:pcieb_intr_handler+1ea ()
fffffe80000b3c40 unix:av_dispatch_autovect+78 ()
fffffe80000b3c50 unix:intr_thread+5f ()
syncing file systems... done
ereport.io.pci.fabric ena=1693e6221600001 detector=[ version=0 scheme="dev"
device-path="/pci@19,0/pci8086,3410@9" ] bdf=2048 device_id=3410 vendor_id=
8086 rev_id=22 dev_type=40 pcie_off=90 pcix_off=0 aer_off=100 ecc_ver=0
pci_status=10 pci_command=47 pci_bdg_sec_status=0 pci_bdg_ctrl=3 pcie_status=6
pcie_command=7 pcie_dev_cap=8021 pcie_adv_ctl=5 pcie_ue_status=4020
pcie_ue_mask=100000 pcie_ue_sev=62030 pcie_ue_hdr0=0 pcie_ue_hdr1=0
pcie_ue_hdr2=0 pcie_ue_hdr3=0 pcie_ce_status=0 pcie_ce_mask=0
pcie_ue_tgt_trans=0 pcie_ue_tgt_addr=0 pcie_ue_tgt_bdf=ffff pcie_rp_status=0
pcie_rp_control=0 pcie_adv_rp_status=7c pcie_adv_rp_command=7
pcie_adv_rp_ce_src_id=2048 pcie_adv_rp_ue_src_id=2048 remainder=0 severity=44
skipping system dump - no dump device configured
rebooting...
Any ideas?

Sometimes, it's just easier and faster
to just start all over and re-install,
particularly when you have only a fresh install on your system.
This time, do not choose to include all the optional "documentation"
(that's what is held on CD5).
I have never found a reason to ever read that documentation so I stopped installing it.
... or you could download and burn a copy of CD5 and use it when prompted.

Problems with Solaris 11 11/11

Similar Messages

Maybe you are looking for