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

Similar Messages

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]

HP 250 G3 - problems with Windows 10 boot

I have problems with Windows 10 boot on my HP 250 G3. It often shutdown during boot. But boot is ok with Windows 8.1. Please release upgrade that solve this problem.

SomeoneWithAnHP wrote:
Guys this might be solution: Turn off your laptop. Disconnect all devices connected to the PC. Remove battery and disconnect from wall. Press the power button at least 20 seconds. Connect back battery and turn on your PC. It should be fixed by now, I did with my Pavilion 14, and both sleep and turning off problems were fixed.re: Black Screen and Dead keyboard after locking computer. I tried this with my Envy 17t-3200 3D CTO. Didn't help. for this computer this means removing the back cover and unplugging the battery wiring harness form the Motherboard. I currently have sleep mode disabled when on AC and am still getting the black screen, dead keyboard lockup. I really know I'm hosed since even the caps-lock is non-functional. I see this problem more when I'm at work were I tend to Win-L lock the screen when I walk away from my desk. Seems like locking the computer then letting the screen blank is doing something evil. After I force a reboot, by keyboard backlight forgets it's setitngs and returns to full brightness. If I lock the screen then bring back the computer before the screen is blanked, it seems fine. I don't think there's any way to adjust the screen blanking when the lock screen is up (even my desktop power-saves the monitors after a few minutes on the Lock screen). I'm not sure it's HP or MS that should be looking into this. My computer is about 3 years old so I can't pester HP with warranty requests. I'm not sure how prevelant this problem is. Are all Pavellions and Envy's having the problem? Mine has Radeon graphics which was a bit unusual at the time. I have to install the HP Display driver before any AMD updates or the screen dimming doesn't work (at least with win 7 and 8). Dave.

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

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, ...

Problem with Jumpstart install

Hi,
I'm having a serious problem installing an x86 Solaris 10 with Jumpstart. I have a server with the profiles and rules, everything is ok I think. The server has a DCHP service running, and I start the target machine from the net. When switched on, it connects to server, get IP address and paramenters, and the Grub menu appears with the correct option to select. I select it and the process begin. First, the language selection page asks for the language, then, the process make the partitions, and start the copy of files (graphic mode). After some hours (the files are the Solaris 10 operative system itself and a flash image from other machine), the file copy process finishes, and, after some other tasks, the machine reboots. And here is where the problem appears.
At booting, I select to boot from the first hard disk drive (where the files have been copied, where the OS resides), and the following message appears: Bad PBR sig. Searching in forums, I have read that message means there is no active partition or it's impossible to find the master boot record.
Booting with a CD, I see there is an active partition, and it is the correct partition. So the problem is that there is no master boot record. Again, searching the net, I read that there are two ways of write a MBR: the command Installboot and the command Installgrub.
I boot from solaris 10 CD and enter the command Installboot, and it says that it's obsolete, so I try with Install grub this way: (note: when booting with Solaris CD, it detects a Solaris installed in /dev/rdsk/c0t0d0s0, and ask me if I want to mount it in /a, I answer yes because I think that I need to use the information of grub at /boot/grub of the hard disk)
installgrub -m /a/boot/grub/stage1 /a/boot/grub/stage2 /dev/rdsk/c0t0d0s0
After that, I rebooted the machine and when it starts (from hard disk), the only thing that occurs is that the word GRUB appears.. and nothing else. A flashing cursor at the end of the word GRUB. Nothing to do. The only way to get out of there, is switching off and then on again.
The first time I tried to install, I did the same but without mounting the disk, and with the command installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c0t0d0s0
Here is the profile at Jumpstart:
install_type flash_install
archive_location nfs 10.95.8.7:/export/backup/platform/alba-ucm/ALBA-UCM-HostID_
2b72c461_4x80GbMirror-Prepared_09042008.flar
partitioning explicit
#DISK-0 MIRROR PREPARED
filesys c0t0d0s0 1:2650 /
filesys c0t0d0s1 2651:1600 /var
filesys c0t0d0s2 4251:400 swap
filesys c0t0d0s3 4651:100 /tmp
filesys c0t0d0s4 4751:1000 /opt/app
filesys c0t0d0s5 5751:3143 /repositoryCC
#SVM+Boot
filesys c0t0d0s7 8894:26
#DISK-1 MIRROR PREPARED
filesys c0t1d0s0 1:2650
filesys c0t1d0s1 2651:1600
filesys c0t1d0s2 4251:400
filesys c0t1d0s3 4651:100
filesys c0t1d0s4 4751:1000
filesys c0t1d0s5 5751:3143
#SVM+Boot
filesys c0t1d0s7 8894:26
#DISK-2 MIRROR PREPARED
filesys c0t2d0s0 1:8093 /datos
filesys c0t2d0s1 8094:800 /DBoracle
#SVM+Boot
filesys c0t2d0s7 8894:26
Please, need some urgent help to solve this problem. What am I doing wrong?
Thanks.

Paco,
Quizas deberias de tratar de instalar tus file systems, y sincronizarlos durante el jumpstart. In other words, you should try to mirror your drives during jumpstart. I see you are using cylinders instead of MB sizes, and unless there is a particular reason why you're doing it that way, I suggest you mirror like this:
filesys mirror:d10 c0t0d0s0 c0t1d0s0 /
filesys mirror:d20 c0t0d0s1 c0t1d0s1 /swap
de este modo, una vez el sistema operativo instale, los cambios necesarios al bootenv.rc seran implementados por el sistema operativo.
You should also make sure if you have a live system, that the secondary drive (DRIVE-1) you are trying to boot has been setup with the master boot record:
fdisk -B /dev/rdsk/c0t1d0p0
And make sure your /boot/solaris/bootenv.rc file shows an "alternateboot" property.
Saludos,
--xancatal

Problems with Tiger Install

Previously having OS 10.2, I tried to install 10.4 from an installation disc over 10.2, and it failed to install. After failing to install, the computer made me restart, and now it goes to a screen giving an error about a Mac OS 10.4 and 10.5 Driver. The Computer can't find drivers for 10.4 and 10.5. I cannot boot from an Apple I-care disc, the machine tries to boot into an OS, but there is a question mark, instead of an OS Icon in the middle of the screen, and then shortly after comes the error message. The machine locks up.
I thought maybee the problem was intalling OS10.4 as an update, because there was a gap between version previously installed and the new one, but the installation guide says OS 10.2 or later is updatable.
Please Help.

Hi Brandon,
If you are not able to start up from your installation DVD there might be a problem with your DVD drive.
If this is the case then there are two things you might do:
1- (and most obvious) take your Mac in for repair.
2- Fire Wire Target Disk Mode... (For this option you will need a second Mac)
- Target Disk Mode will basically turn your iMac into an external HD, by doing this you will be able to use a second Mac with a working disc drive to start up from the Tiger DVD and then install it on your iMac.
If you are going to do this it is important that no other FireWire devices are connected to either of the computers.
How to start your iMac in Target Disk Mode: Start up the computer and immediately press and hold down the T key until the FireWire icon appears.
Once you have done this connect it to the second Mac (with FireWire)
Now insert the Tiger DVD in the second Mac, when the disk appears on the Desktop open it and double click on "install"
A window with a restart button will appear... click and restart (there will be no need to hold the "c" key.
Once the computer has started up from the Tiger DVD you need to find UTILITIES or TOOLS (i can remember the exact name) on the top bar
Click on it and open Disk Utility then follow the steps of my previous post.
Make sure that you have selected the correct HD to erase and install (it will not be the first one on the list)
Good Luck.
S

Problems with re-installing OS X

Hi,
I have recently had some problems with my iBook G4, it ran very slow and I could hear the Hard Drive constantly spinning. So I think about doing a fresh install of OSX to see if that would solve the problem, so I went to the apple support and saw that it would work if I followed the installation. Everything was working well. in the installation, I erased everything on the hard drive (I did have everything backed up...) and started the installation. (Just let me say here that I have 4 CDs that came with my iBook to install panther and it also came with a dvd to upgrade to tiger [I bought the day they relesed tiger]) on both installation disks once I satrted installing it said "there were errors installing this software please try again" I had tried many times again. and nothing has happened since.
Does anybody think they could give me a hand? it would be greatly appreciated. Thanks in advance!

Try this:
1. Boot from your Panther Installer Disk. After the installer loads select Disk Utility from the Installer menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled, if supported.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled, if supported.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process will take 30 minutes to an hour or more depending upon the drive size.
7. Once the formatting has completed quit DU to return to the installer. Proceed with the installation of Panther.

[SOLVED] Problem with net install cd

Trying to install Arch on an old Asus P4BGL-MX board which is proprietary, probably something HP. I have had no problems using the net install CD on 3 other Asus boards. What happens is the install process starts (booting the kernel) and then halts with the screen black and the computer hung.
The last line before black screen is: [13.34178412] ACPI: Invalid PBLK length [5]
==>> I think problem solved, but I don't understand it. The board has on board Intel graphics, but I had an ATI PCI card installed with bios set for it. Took it out and now the install goes as it should. I'm marking this post as solved, but if anyone could shed some light on this, it would be appreciated.
Last edited by Ron74 (2012-01-02 19:46:25)

This says:
Colin King wrote:The warning is because of a problem with the Processor declaration in the _PR root namespace of your ACPI DSDT:
Scope (\_PR)
Processor (\_PR.CPU0, 0x00, 0x0000E410, 0x05) {}
Processor (\_PR.CPU1, 0x01, 0x00000000, 0x00) {}
The syntax of the Processor declaration is as follows:
Processor (ProcessorName, ProcessorID, PBlockAddress, PblockLength)
Section 18.5.93 of the ACPI specification states that the PBlockLength is the length of the processor register block, in bytes and is either 0 (for no P_BLK) or 6. In your case, the it's been set to 0x05 in the first Processor declaration which is definetly not compliant with the specification, hence the kernel warning message. The ACPI specification can be downloaded from http://www.acpi.info/DOWNLOADS/ACPIspec40.pdf if your are interested in the details.
As it is, this is not a kernel bug, but a warning from the kernel that your BIOS is buggy and needs fixing. I suggest informing the manufacturer so that they can fix the BIOS.

Problems with graphics after Boot Camp upgrade (from 3.1 to 3.2)

Right, today I upgraded Boot Camp (the first time I used iTunes on Windows so thats way I never did the upgrade before) from 3.1 to 3.2 and after the installation my screen went blank/black. After restarting iMac it the screen appeared but in 1024x768 resolution and without working graphic drivers.
I tried many different options to update the ATI HD 4850 driver, but none of them worked. It always says that there is some problem with it, but it also is up to date every time I try to update it manually for the drivers which comes with 10.12 Catalyst.
I spend several hours trying to solve it, but I just can't and I really don't know what to do next.

Right, I managed to fix it by updating the software manually, but selecting to choose from the list and I had to install the mobility drivers.

Problems with bluetooth in Boot Camp

I recently installed windows xp with bootcamp on my macbook and the bluetooth is acting weird while in windows. It will pair with my devices (Phone: Samsung D-407, Headset: Plantronics Explorer 220) but in the bluetooth connections window it will only show them as connected for a second or two and my devices won't work. I did install Service Pack 3 for windows and I don't know if that affected it or not because I didn't try the bluetooth before updating. Would that cause any problems or is it something else?

Ric - wrote:
I'm having problems with my MacBook Pro's bluetooth support in Vista under Boot Camp so I thought I'd try to re-install the Boot Camp 2.1 drivers. However, whenever I run the setup program, it just gives me a useless error message saying it encountered an error before it could start the install, and to please try again later. Rebooting doesn't help.
So I thought maybe I could uninstall all the Apple stuff then start again. But when I try to uninstall "Boot Camp services" from the programs and features control panel, it starts to uninstall, but then gives up silently as it nears the completion of the "gathering information" dialog.
So I can't uninstall or re-install this thing. Anyone know how I can fix this?
Thanks!
It may be too late, but have you tried going into the drivers using Vista's control panel and either removing the drivers or reverting to precious drivers?

MSI Z87m problems with Realtek install

I cannot install Realtek drivers with this motherboard. Brand-new system with Windows 7. Intel I5 CPU, gigabyte gtx 780, 8 GB ram. All drivers updated, win 7 updated.
I have tried the drivers from the included disc and also direct from Realtek site. They will install but they will not work. Red Cross shows up on the volume icon anytime I try to open audio.
I have even tried reinstalling the OS twice. Makes no difference.
I tried installing the Realtek drivers from SafeBoot. I just get an error message.
Creative Sound Blaster cinema will also not work because the RealTek drivers don't work.
I have read a few other posts of people having this exact same problem with this motherboard and Realtek drivers.
The windows HD audio will work.
Right clicking on Realtek properties in device manager shows everything is working fine, even though it isn't.
I have also had problems when booting into the bios. If I try to change anything, like a fan setting, and then try to save and exit, the system freezes. I had to CMOS once already. Pc also freezes in the bios when trying to access the hardware Monitor option, requiring a reboot. The other options work fine.
I've written to MSI about this problem but I was hoping somebody might have an idea of what I could try before I take the system back to the store for them to check it and replace the motherboard, as I will then be without the PC for a week.

What xmad is trying to get as information is the 'complete' name of the mainboard. Z87m is not good enough. Also, more information about the other systems components including specifics of the RAM, brand, rated speed, and the PSU brand and description. For now, test with just a single RAM stick.

Any problems with a 1TB boot drive?

My Mac Pro finally got here and I added ram & a 1 TB WD Caviar Black HD as a boot drive. The boot drive as shipped was a 640GB WD Caviar Blue but after a lot of reading, I decided to make the 1TB black the Boot 'cause it's faster & roomier. Really don't want to have to change it out in a few years due to space constraints & go through the setup process all over again.
I also have another 1 TB WD Caviar Black coming (should be here today) that I intend to use as a capture scratch disc. I still have the 640GB blue in the machine for use probably as a boot drive for windows XP Pro & all the programs I run on it in my PC at this time.
The question I have is this: is there any problem with using the 1TB black as a boot drive?
I think I recall that in the past some folks advocated a smaller boot drive, but that was before the days of dual processor, 64 MB cache, and dual heads that make the 1TB quite speedy.
I think I'll setup a PCIe external raid in the not too distant future as the archive & backup resovoir. Any difficulties with that?
Ken

Thanks for the replies, they are all helpful.
@ Jim C, glad to hear confirmation on your setup success w/ WD Blacks. My thinking was exactly the same as yours, a drive with lots of room is faster.
@David, I've always had good luck with Seagate, but only had one older WD. I'm aware WD went through some reliability problems earlier. The reviews I found on the recent WD Cav blacks all said they were better all around drives than Seagate now a days. Sorry to hear about your drive failure, time will tell for me. I'm definitely going to go with enterprise class drives on the raid and will also have an installed spare in case on goes.
Some days it's peanuts & other days it's shells. Despite marketing claims on MTBF, there will always be "premature" failures as Jim Kells points out in his reply.
Ultimately when manufacturers get a better handle on SSD's, they will be the longest lived if for no other reason than no moving parts. Performance droop on many of them now also colors the current scene, IMO. Until then it's somewhat of a crap shoot.
Ken

I'm having problems with the install of iTunes 10.7 it seems to be going well and then at the very end of the blue bar it doesnt seem to complete? All of my software is up to date and plenty of space on the mini?

I'm having problems installing iTunes 10.7. It seems to be going well and then at the last part of the blue bar it just doesn't complete. All software is up to date and there is plen of room on the mini? I have tried like 4 times and am ready to throw it out the window.

I noticed some problems with the Apple Support sites here the last day or so.
Try again using > Apple - iTunes - Download iTunes Now

Metalink SR category for problem with CRS install

HI
Can You please tell me , where I find in SR category to create request on metaling about problem with install/start crs :
I wont to create RAC env where host is ORACLE VM and clusterware is OCFS2 and wit Oracle Enterprise linux 5 , but after istal ai have problem with start crs (root.sh) and I don't know to find relevant category
[root@lin1 bin]# ./crsctl start cluster
CRS-2672: Attempting to start 'ora.gipcd' on 'lin1'
CRS-2672: Attempting to start 'ora.mdnsd' on 'lin1'
CRS-2676: Start of 'ora.mdnsd' on 'lin1' succeeded
CRS-2676: Start of 'ora.gipcd' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'lin1'
CRS-2676: Start of 'ora.gpnpd' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'lin1'
CRS-2676: Start of 'ora.cssdmonitor' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'lin1'
CRS-2672: Attempting to start 'ora.diskmon' on 'lin1'
CRS-2676: Start of 'ora.diskmon' on 'lin1' succeeded
CRS-2674: Start of 'ora.cssd' on 'lin1' failed
CRS-679: Attempting to clean 'ora.cssd' on 'lin1'
CRS-2681: Clean of 'ora.cssd' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'lin1'
CRS-2676: Start of 'ora.cssdmonitor' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'lin1'
CRS-2674: Start of 'ora.cssd' on 'lin1' failed
CRS-2679: Attempting to clean 'ora.cssd' on 'lin1'
CRS-2681: Clean of 'ora.cssd' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.diskmon' on 'lin1'
CRS-2676: Start of 'ora.diskmon' on 'lin1' succeeded
CRS-2673: Attempting to stop 'ora.cssdmonitor' on 'lin1'
CRS-2677: Stop of 'ora.cssdmonitor' on 'lin1' succeeded
CRS-4000: Command Start failed, or completed with errors.
[root@lin1 bin]# ./crsctl check cluster
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
CRS-4534: Cannot communicate with Event Manager
[root@lin1 bin]# ./crsctl check cluster -all
lin1:
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
CRS-4534: Cannot communicate with Event Manager
Thank You Brano

HI
Can You please tell me , where I find in SR category to create request on metaling about problem with install/start crs :
I wont to create RAC env where host is ORACLE VM and clusterware is OCFS2 and wit Oracle Enterprise linux 5 , but after istal ai have problem with start crs (root.sh) and I don't know to find relevant category
[root@lin1 bin]# ./crsctl start cluster
CRS-2672: Attempting to start 'ora.gipcd' on 'lin1'
CRS-2672: Attempting to start 'ora.mdnsd' on 'lin1'
CRS-2676: Start of 'ora.mdnsd' on 'lin1' succeeded
CRS-2676: Start of 'ora.gipcd' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.gpnpd' on 'lin1'
CRS-2676: Start of 'ora.gpnpd' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'lin1'
CRS-2676: Start of 'ora.cssdmonitor' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'lin1'
CRS-2672: Attempting to start 'ora.diskmon' on 'lin1'
CRS-2676: Start of 'ora.diskmon' on 'lin1' succeeded
CRS-2674: Start of 'ora.cssd' on 'lin1' failed
CRS-679: Attempting to clean 'ora.cssd' on 'lin1'
CRS-2681: Clean of 'ora.cssd' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.cssdmonitor' on 'lin1'
CRS-2676: Start of 'ora.cssdmonitor' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.cssd' on 'lin1'
CRS-2674: Start of 'ora.cssd' on 'lin1' failed
CRS-2679: Attempting to clean 'ora.cssd' on 'lin1'
CRS-2681: Clean of 'ora.cssd' on 'lin1' succeeded
CRS-2672: Attempting to start 'ora.diskmon' on 'lin1'
CRS-2676: Start of 'ora.diskmon' on 'lin1' succeeded
CRS-2673: Attempting to stop 'ora.cssdmonitor' on 'lin1'
CRS-2677: Stop of 'ora.cssdmonitor' on 'lin1' succeeded
CRS-4000: Command Start failed, or completed with errors.
[root@lin1 bin]# ./crsctl check cluster
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
CRS-4534: Cannot communicate with Event Manager
[root@lin1 bin]# ./crsctl check cluster -all
lin1:
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
CRS-4534: Cannot communicate with Event Manager
Thank You Brano

Problem with solaris install/boot

Similar Messages

Maybe you are looking for