Reconfigure reboot in u9

hi there ..
i needed to perform reconfigure reboot, i also touched /reconfigure and did with -r, removed etc/path_to_inst but result is always this (in case of `{0} ok boot -r` and removed path_to_inst):
WARNING: /etc/path_to_inst empty or not found
NOTICE: using backup instance data in /etc/path_to_inst.old
why ^^ for a god's sake .. did it change in u9 ??
i removed some devices which are just no longer in system and they are still in path_to_inst:
"/virtual-devices@100/channel-devices@200/network@1" 1 "vnet"
`devfsadm -Cv` prints nothing same as dladm is no longer seeing vnet1:
# dladm show-dev
vnet0 link: up speed: 0 Mbps duplex: unknown
^^ it is T5240 LDOM:
# ldm list -l ldom2
NAME             STATE    FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME
ldom2            active   -n---   5002    24    4032M    0.0%  26m
SOFTSTATE
Solaris running
VCPU
    VID    PID    UTIL STRAND
    0      88     0.4%   100%
    1      89     0.3%   100%
    2      90     0.3%   100%
    3      91     0.3%   100%
    4      92     0.3%   100%
    5      93     0.3%   100%
    6      94     0.3%   100%
    7      95     0.3%   100%
    8      96     0.3%   100%
    9      97     0.0%   100%
    10     98     0.0%   100%
    11     99     0.0%   100%
    12     100    0.1%   100%
    13     101    0.0%   100%
    14     102    0.0%   100%
    15     103    0.0%   100%
    16     104    0.0%   100%
    17     105    0.1%   100%
    18     106    0.0%   100%
    19     107    0.0%   100%
    20     108    0.0%   100%
    21     109    0.0%   100%
    22     110    0.0%   100%
    23     111    0.0%   100%
MAU
    ID     CPUSET
    9      (88, 89, 90, 91, 92, 93, 94, 95)
    10     (96, 97, 98, 99, 100, 101, 102, 103)
    11     (104, 105, 106, 107, 108, 109, 110, 111)
MEMORY
    RA               PA               SIZE
    0x4000000        0x304000000      4032M
VARIABLES
    auto-boot?=false
    boot-device=disk0
    keyboard-layout=US-English
    use-nvramrc?=true
NETWORK
    NAME             SERVICE                     DEVICE     MAC
    vnic0            vsw@primary                 network@0  00:14:4f:fb:73:21
DISK
    NAME             VOLUME                      TOUT DEVICE  SERVER
    disk0            disk2@vds0                       disk@0  primary
VCONS
    NAME             SERVICE                     PORT
    ldom2            vcc0@primary                5002thanks and regards, daniel
Edited by: 826387 on Jan 7, 2011 3:33 AM

Hmm, are you certain it did change in u9? I've never removed the path_to_inst myself, and i suspect that booting without it can be troublesome since the system might need information from path_to_inst to find its boot device.
The manpage (which has been unchanged since 2007) states that:
WARNINGS
If the file is removed the system may not be bootable (as it
may rely on information found in this file to find the root,
usr or swap device). If it does successfully boot, it will
regenerate the file, but after rebooting devices may end up
having different minor numbers than they did before, and
special files created via mknod(1M) may refer to different
devices than expected.
For the same reasons, changes should not be made to this
file without careful consideration.
So i'm a bit curious what you gain by removing it?
.7/M.

Similar Messages

  • Reconfigure reboot for Solaris 10 u5 x86 guest in VirtualBox

    Hello,
    I just installed the new kernal patch into a Solaris 10 u5 x86 32-bit guest OS in VirtualBox 2.0.4 on a WinXP 32-bit host. I need to do a reconfigure reboot. I can't seem to get to the ok prompt from which to use boot -r. init 0 does not work, it only offers a "push any key to reboot."
    What is the optimal way to initiate a reconfigure reboot for Solaris 10 in my setup?
    I tried the grub-based technique in which, upon reboot, I get the grub menu and push "e." That gets me to another grub screen with 3 entries. I selected the kernal entry, pushed "c" to add "-r" to the end of the line, and then "b" to reboot. Is that the best way to reconfigure reboot for Sol 10 x86.
    The above method did configure devices on reboot, but I'm not sure that is the best way to boot -r
    Thank you in advance...

    x86 machines (including virtual machines) do not have an OBP or an 'ok' prompt.
    You have to manipulate the GRUB either through interactive commands like you've shown, or by editing the menu.lst file to change boot parameters.
    Of course for reconfiguration, you also have the option of touching '/reconfigure' and doing a normal reboot.
    Darren

  • Urgent help needed in configuring X1151A

    for RAC requirements I have to configure this card to use the interface name of ce1 but I have tried changing slots and puting /etc/hostname.ce1 file out there but it fails .. it always comes up as ce0.
    my question is : How can I cofigure this card to come up as ce1 ? in the other box I had to do nothing .. i just placed the /etc/hostname.ce1 file with hostname and it works perfect.
    can you please email me a copy of your response at [email protected] ?
    thanks
    Sami

    For the discussion in this forum thread, the path-to-inst file
    can be though of as a repository of every device path
    for every lump of hardware that was ever installed to a system.
    It tells Solaris where to find the devices, along their communication interconnect paths.
    Thus a device driver can know where to sends its commands
    and where to listen for any return signalling responses from the device.
    Issues can arise if a device was successfully installed to a path,
    such as when a PCI card is installed to a particular slot,
    and that card gets moved to another slot.
    The path-to-inst file will "remember" the old path, in case you return the card.
    No software structures need to be re-built when it reappears in its old slot position.
    The former functionality is maintained if ever needed again.
    The new position initiates a new entry into the file,
    such as when there are two of the same cards instead of the original solitary card.
    For your circumstances, there's got to be something in the computer's configuration
    that can isolate the data streaming to IP address #1 ( such as for ce0 )
    from whatever data might need to go through the other IP address ( such as for ce1 ).
    My suggestion for you is to use the devfsadm command.
    Review its man pages.
    Decide how you want the computers to be configured -- probably using ce0 on both.
    devfsadm -C will purge out stale entries and rebuild the path-to-inst file.
    A reconfiguration reboot, such as might result from a boot -r,
    only appends new device instances to the file.
    There's no cleanup, or 'housekeeping', done to it.

  • V210 won't output to Monitor

    Had to replace my old v210 with a new one. The new one did not come with a video card or DVD-ROM, so I took them out of the old server. The DVD-ROM works fine, but I either get no output on the monitor, or if I do, it looks like a sync'ing issue (horizintal multicolored lines). The only difference between the old and new server - besides no video and DVD, is the new server is dual-cpu with 8GB RAM, whereas the old one was single CPU with 4GB RAM.
    I cannot locate any information on Oracle's site on how to troubleshoot a video problem. I downloaded all the manuals they have at (http://download.oracle.com/docs/cd/E19088-01/v210.srvr/index.html) but nothing is covered in any of them.
    During boot and diags, the monitor does come on as it polls the bus, but it does not stay on, or has horizontal lines. I'm posting the output of my POST and eeprom settings in hopes someone can help.
    POST results
    Sun Fire[TM] V210/V240,Netra[TM] 210/240 POST 4.30.3.b 2009/07/21 13:27
    /export/delivery/delivery/4.30/4.30.3.b/post4.30.3-micro/Fiesta/enxs/inte
    grated (root)
    0>Copyright 2009 Sun Microsystems, Inc. All rights reserved
    0>OBP->POST Call with %o0=00000800.01012000.
    0>Diag level set to MIN.
    0>Verbosity level set to NORMAL.
    0>Start Selftest.....
    0>CPUs present in system: 0 1
    0>Test CPU(s)....|
    0>Interrupt Crosscall....Done
    0>Init Memory....Done
    0>PLL Reset....Done
    0>Init Memory....Done
    0>Test Memory....Done
    0>IO-Bridge Tests....Done
    0>INFO:
    0> POST Passed all devices.
    0>
    0>POST: Return to OBP.
    Configuring system memory & CPU(s)
    Probing system devices
    Probing memory
    Probing I/O buses
    pci0 not found.
    Probing system devices
    Probing memory
    Probing I/O buses
    Sun Fire V210, Keyboard Present
    Copyright 2009 Sun Microsystems, Inc. All rights reserved.
    OpenBoot 4.30.3.b, 8192 MB memory installed, Serial #66908789.
    Ethernet address 0:3:ba:fc:f2:75, Host ID: 83fcf275.
    Running diagnostic script obdiag/normal
    Testing /pci@1e,600000/ide@d
    Testing /pci@1e,600000/isa@7/rtc@0,70
    Testing /pci@1c,600000/scsi@2
    Testing /pci@1c,600000/scsi@2,1
    Testing /pci@1e,600000/isa@7/serial@0,2e8
    Testing /pci@1e,600000/isa@7/serial@0,3f8
    Probing system devices
    Probing memory
    Probing I/O buses
    pci0 not found.
    Probing system devices
    Probing memory
    Probing I/O buses
    Sun Fire V210, Keyboard Present
    Copyright 2009 Sun Microsystems, Inc. All rights reserved.
    OpenBoot 4.30.3.b, 8192 MB memory installed, Serial #66908789.
    Ethernet address 0:3:ba:fc:f2:75, Host ID: 83fcf275.
    Rebooting with command: boot
    Boot device: /pci@1c,600000/scsi@2/disk@0,0 File and args:
    SunOS Release 5.10 Version Generic_118833-33 64-bit
    Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    Hardware watchdog enabled
    Hostname: NCC
    checking ufs filesystems
    /dev/rdsk/c1t0d0s7: is logging.
    ================================================
    EEPROM
    # eeprom
    asr-policy=normal
    keyboard-layout: data not available.
    test-args: data not available.
    diag-passes=1
    local-mac-address?=true
    fcode-debug?=false
    scsi-initiator-id=7
    oem-logo: data not available.
    oem-logo?=false
    oem-banner: data not available.
    oem-banner?=false
    ansi-terminal?=true
    screen-#columns=80
    screen-#rows=34
    ttyb-rts-dtr-off=false
    ttyb-ignore-cd=true
    ttya-rts-dtr-off=false
    ttya-ignore-cd=true
    ttyb-mode=9600,8,n,1,-
    ttya-mode=9600,8,n,1,-
    output-device=ttya
    input-device=ttya
    auto-boot-on-error?=false
    error-reset-recovery=sync
    load-base=16384
    auto-boot?=true
    network-boot-arguments: data not available.
    boot-command=boot
    diag-file: data not available.
    diag-device=net
    boot-file: data not available.
    boot-device=/pci@1c,600000/scsi@2/disk@0,0
    use-nvramrc?=false
    nvramrc: data not available.
    security-mode=none
    security-password: data not available.
    security-#badlogins=0
    verbosity=normal
    diag-trigger=error-reset power-on-reset
    service-mode?=false
    diag-script=normal
    diag-level=min
    diag-switch?=false
    #

    Why would you expect a monitor to show anything, when the new system is using its factory default configuration?
    output-device=ttya
    input-device=ttyaBy the way, that is the preferred method to administer those 1U systems.
    Connect another system to the serial console port and set that system up as you want.
    Did you even take the opportunity to tell the OS of the existence of that card? There isn't any Plug-n-Play as your personal Microsoft PC might have. You likely will need to do a reconfiguration reboot, then install drivers for the video card then more reboots. Have a Sun USB keyboard/mouse kit connected as well, else you may still never see any monitor output.
    Go get the V210 documentation and use its guidance to set the system as you want it.
    http://download.oracle.com/docs/cd/E19088-01/v210.srvr/index.html

  • Qla2310f not shown in cfgadm/luxadm (san 4.4.11)

    I have a problem, with two qlogic qla2310f HBA�s (not sun branded) that are not detected in luxadm/cfgadm.
    The box is a SUN Fire 280R running solaris 8:
    SunOS [hostname] 5.8 Generic_117350-27 sun4u sparc SUNW,Sun-Fire-280R
    Originally it was connected to an older eva-san(HP) using HP-securepath 3.0d for multipathing.
    When changing to a new EVA8000 san, i did the following:
    1. Unmounted the san-disks, removed them fra Solstice.
    2. deletede them in spmgr (HP Securepath)
    3. unpresented the disks
    4. unistalled Hp Securepath
    5. presented disks from the new san (EVA8000)
    6. installed SAN 4.4.11 and required pathces, using the "install_it" script
    7. modified /kernel/drv/scsi_vhci.conf to enable mpxio globally and add hp specific Symmetric options for the eva8000 san.
    After the reconfiguration reboot, i see the disks - however, i Cant see the two qla2310f in luxadm/cfgadm.
    These utillities only see the internal controller, and the two internal disks:
    Luxadm shows:
    luxadm probe
    No Network Array enclosures found in /dev/es
    Found Fibre Channel device(s):
    Node WWN:20000004cfbff6be Device Type:Disk device
    Logical Path:/dev/rdsk/c1t0d0s2
    Node WWN:2000000c500739e5 Device Type:Disk device
    Logical Path:/dev/rdsk/c1t1d0s2
    luxadm fcode_download -p
    Found Path to 0 FC/S Cards
    Complete
    Found Path to 0 FC100/S Cards
    Complete
    Found Path to 1 FC100/P, ISP2200, ISP23xx Devices
    Opening Device: /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:devctl
    Detected FCode Version: ISP2200 FC-AL Host Adapter Driver: 1.15 04/03/22
    Complete
    Found Path to 0 JNI1560 Devices.
    Complete
    Found Path to 0 Emulex Devices.
    Complete
    cfgadm shows:
    cfgadm -l
    Ap_Id Type Receptacle Occupant Condition
    c0 scsi-bus connected configured unknown
    c1 fc-private connected configured unknown
    c2 scsi-bus connected unconfigured unknown
    c3 scsi-bus connected unconfigured unknown
    c4 scsi-bus connected unconfigured unknown
    cfgadm -al
    Ap_Id Type Receptacle Occupant Condition
    c0 scsi-bus connected configured unknown
    c0::dsk/c0t6d0 CD-ROM connected configured unknown
    c1 fc-private connected configured unknown
    c1::21000004cfbff6be disk connected configured unknown
    c1::2100000c500739e5 disk connected configured unknown
    c2 scsi-bus connected unconfigured unknown
    c3 scsi-bus connected unconfigured unknown
    c4 scsi-bus connected unconfigured unknown
    Qlogics SANSurfer CLI shows all three adapters:
    SANsurfer FC HBA CLI
    v1.06.16 Build 57
    Device List Menu
    HBA Model QLA2300/2310:
    1: Port 1 (OS 0): WWPN: 21-00-00-E0-8B-0D-AE-BF Online
    HBA Model QLA2300/2310:
    2: Port 1 (OS 1): WWPN: 21-00-00-E0-8B-0D-B6-BF Online
    HBA Model qlc:
    3: Port 1 (OS 0): WWPN: 21-00-00-03-BA-2F-AA-EF Online
    4: All HBAs
    cat /etc/path_to_inst |grep qla2300
    "/pci@8,700000/QLGC,qla@3" 0 "qla2300"
    "/pci@8,600000/QLGC,qla@1" 1 "qla2300"
    the adapters are recognized at boot as well (and probe-scsi-all sees them as well as the san disks)
    Oct 22 19:15:43 [hostname] qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v5.01 Instance: 0
    Oct 22 19:15:43 [hostname] qla2300: [ID 572349 kern.notice] hba0: QLogic QLA2300 Fibre Channel Host Adapter fcode version 2.00.05 01/29/03
    Oct 22 19:15:50 [hostname] qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v5.01 Instance: 1
    Oct 22 19:15:50 [hostname] qla2300: [ID 572349 kern.notice] hba1: QLogic QLA2300 Fibre Channel Host Adapter fcode version 2.00.05 01/29/03
    I currently use the disks "directly" without using multipathing:
    ls -la /dev/dsk/c5t7d5s6
    lrwxrwxrwx 1 root root 46 Oct 22 13:04 /dev/dsk/c5t7d5s6 -> ../../devices/pci@8,700000/QLGC,qla@3/sd@7,5:g

    I need luxadm/cfgadm to "see" the two qla2310f adapters, in order to use multipathing, any ideas?

    Same here:
    V240 and X4200, QLF2340, Solaris 9 and 10 plus latest 9 recommended patch cluster connectec to McData and HDS.
    Seems like a problem with luxadm and cfgadm, as on V480 with QLC2340 all works well...
    Any new patches/fixes?
    Cheers.

  • M5000 and Qlogic QLE4062C issues

    I am having a problem getting one M5000 server to recognize the Qlogic iSCSI HBAs in PCI slots 3, 4, and 5. We have 2 M5000 servers and one of them is working fine, but the other does not present to Solaris the HBAs. I have done a reconfiguration reboot many times, shut down the domain, rebooted the xscf. The xscf sees the PCI cards on both systems. Is there something I can do to dig deeper as to why Solaris 10 does not see the adapters? Thanks in advance for any insight.
    XSCF> showhardconf
    SPARC Enterprise M5000;
    + Serial:*************; Operator_Panel_Switch:Locked;
    + Power_Supply_System:Single; SCF-ID:XSCF#0;
    + System_Power:On; System_Phase:Cabinet Power On;
    Domain#0 Domain_Status:Running;
    MBU_B Status:Normal; Ver:0201h; Serial:************ ;
    + FRU-Part-Number:CF00541-0478 05 /541-0478-05 ;
    + Memory_Size:32 GB;
    CPUM#0-CHIP#0 Status:Normal; Ver:0201h; Serial:************;
    + FRU-Part-Number:CA06761-D105 A4 /375-3477-01 ;
    + Freq:2.150 GHz; Type:16;
    + Core:2; Strand:2;
    CPUM#0-CHIP#1 Status:Normal; Ver:0201h; Serial:************;
    + FRU-Part-Number:CA06761-D105 A4 /375-3477-01 ;
    + Freq:2.150 GHz; Type:16;
    + Core:2; Strand:2;
    CPUM#1-CHIP#0 Status:Normal; Ver:0201h; Serial:************;
    + FRU-Part-Number:CA06761-D105 A4 /375-3477-01 ;
    + Freq:2.150 GHz; Type:16;
    + Core:2; Strand:2;
    CPUM#1-CHIP#1 Status:Normal; Ver:0201h; Serial:************;
    + FRU-Part-Number:CA06761-D105 A4 /375-3477-01 ;
    + Freq:2.150 GHz; Type:16;
    + Core:2; Strand:2;
    MEMB#0 Status:Normal; Ver:0101h; Serial:**************;
    + FRU-Part-Number:CF00541-0545 05 /541-0545-05 ;
    MEM#0A Status:Normal;
    + Code:2c000000000000000836HTF25672PY-667D10100-dc17def7;
    + Type:2B; Size:2 GB;
    MEM#0B Status:Normal;
    + Code:2c000000000000000836HTF25672PY-667D10100-dc17dbae;
    + Type:2B; Size:2 GB;
    MEM#1A Status:Normal;
    + Code:2c000000000000000836HTF25672PY-667D10100-dc17def4;
    + Type:2B; Size:2 GB;
    MEM#1B Status:Normal;
    + Code:2c000000000000000836HTF25672PY-667D10100-dc17def5;
    + Type:2B; Size:2 GB;
    MEM#2A Status:Normal;
    + Code:2c000000000000000836HTF25672PY-667D10100-dc17def8;
    + Type:2B; Size:2 GB;
    MEM#2B Status:Normal;
    + Code:2c000000000000000836HTF25672PY-667D10100-dc17defa;
    + Type:2B; Size:2 GB;
    MEM#3A Status:Normal;
    + Code:2c000000000000000836HTF25672PY-667D10100-dc17defc;
    + Type:2B; Size:2 GB;
    MEM#3B Status:Normal;
    + Code:2c000000000000000836HTF25672PY-667D10100-dc17defb;
    + Type:2B; Size:2 GB;
    MEMB#1 Status:Normal; Ver:0101h; Serial:*************;
    + FRU-Part-Number:CF00541-0545 05 /541-0545-05 ;
    MEM#0A Status:Normal;
    + Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526ba16;
    + Type:2B; Size:2 GB;
    MEM#0B Status:Normal;
    + Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526ba14;
    + Type:2B; Size:2 GB;
    MEM#1A Status:Normal;
    + Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526ba10;
    + Type:2B; Size:2 GB;
    MEM#1B Status:Normal;
    + Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526ba17;
    + Type:2B; Size:2 GB;
    MEM#2A Status:Normal;
    + Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526c117;
    + Type:2B; Size:2 GB;
    MEM#2B Status:Normal;
    + Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526c014;
    + Type:2B; Size:2 GB;
    MEM#3A Status:Normal;
    + Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526c016;
    + Type:2B; Size:2 GB;
    MEM#3B Status:Normal;
    + Code:7f7f7f7f7f5100004572T256220HP3SB 258c-1526e820;
    + Type:2B; Size:2 GB;
    DDC_A#0 Status:Normal;
    DDC_A#1 Status:Normal;
    DDC_A#2 Status:Normal;
    DDC_A#3 Status:Normal;
    DDC_B#0 Status:Normal;
    DDC_B#1 Status:Normal;
    IOU#0 Status:Normal; Ver:0101h; Serial:**************;
    + FRU-Part-Number:CF00541-2240 03 /541-2240-03 ;
    DDC_A#0 Status:Normal;
    DDCR Status:Normal;
    DDC_B#0 Status:Normal;
    PCI#0 Name_Property:pci; Card_Type:Other;
    PCI#1 Name_Property:network; Card_Type:Other;
    ****PCI#2 Name_Property:pci; Card_Type:Other;_****        This is the first card
    ****PCI#3 Name_Property:pci; Card_Type:Other;_****        Second
    ****PCI#4 Name_Property:pci; Card_Type:Other;_****        Third
    XSCFU Status:Normal,Active; Ver:0101h; Serial:*************;
    + FRU-Part-Number:CF00541-0481 04 /541-0481-04 ;
    OPNL Status:Normal; Ver:0101h; Serial:****************;
    + FRU-Part-Number:CF00541-0850 06 /541-0850-06 ;
    PSU#0 Status:Normal; Serial:0017527-0803010468;
    + FRU-Part-Number:CF00300-2011 0150 /300-2011-01-50;
    + Power_Status:On; AC:200 V;
    PSU#1 Status:Normal; Serial:0017527-0803010469;
    + FRU-Part-Number:CF00300-2011 0150 /300-2011-01-50;
    + Power_Status:Input fail; AC: - ;
    PSU#2 Status:Normal; Serial:0017527-0803010459;
    + FRU-Part-Number:CF00300-2011 0150 /300-2011-01-50;
    + Power_Status:On; AC:200 V;
    PSU#3 Status:Normal; Serial:0017527-0803010460;
    + FRU-Part-Number:CF00300-2011 0150 /300-2011-01-50;
    + Power_Status:Input fail; AC: - ;
    FANBP_C Status:Normal; Ver:0301h; Serial:**************;
    + FRU-Part-Number:CF00541-0848 05 /541-0848-05 ;
    FAN_A#0 Status:Normal;
    FAN_A#1 Status:Normal;
    FAN_A#2 Status:Normal;
    FAN_A#3 Status:Normal;
    -dcw-

    Here are the command and the responses...I have one box identical to this one with the same setup with the exception of 1 memory board rather than this one that has two. Basically there are 3 Qlogic QLE4062C cards in PCI slot 2, 3, and 4. On the other machine the driver is installed and initialized each port after I did a reboot -- -r like it should. On this one, I cannot get the cards to initialize. I am thinking it is something with the XSCF, but the network cards initialize fine. I did a reset to factory defaults (of the XSCF) this evening, but it did not help (had to spend some time setting things back up). Thanks for an insight.
    # cfgadm -a
    Ap_Id Type Receptacle Occupant Condition
    SB0 System_Brd connected configured ok
    SB0::cpu0 cpu connected configured ok
    SB0::cpu1 cpu connected configured ok
    SB0::cpu2 cpu connected configured ok
    SB0::cpu3 cpu connected configured ok
    SB0::memory memory connected configured ok
    SB0::pci0 io connected configured ok
    SB0::pci1 io connected configured ok
    SB0::pci2 io connected configured ok
    SB0::pci3 io connected configured ok
    SB0::pci8 io connected configured ok
    SB1 disconnected unconfigured unknown
    SB2 disconnected unconfigured unknown
    SB3 disconnected unconfigured unknown
    SB4 disconnected unconfigured unknown
    SB5 disconnected unconfigured unknown
    SB6 disconnected unconfigured unknown
    SB7 disconnected unconfigured unknown
    SB8 disconnected unconfigured unknown
    SB9 disconnected unconfigured unknown
    SB10 disconnected unconfigured unknown
    SB11 disconnected unconfigured unknown
    SB12 disconnected unconfigured unknown
    SB13 disconnected unconfigured unknown
    SB14 disconnected unconfigured unknown
    SB15 disconnected unconfigured unknown
    c0 scsi-bus connected configured unknown
    c0::dsk/c0t0d0 disk connected configured unknown
    c0::dsk/c0t1d0 disk connected configured unknown
    c0::dsk/c0t3d0 CD-ROM connected configured unknown
    iou#0-pci#0 pci-pci/hp connected configured ok
    iou#0-pci#1 etherne/hp connected configured ok
    iou#0-pci#2 pci-pci/hp connected configured ok
    iou#0-pci#3 pci-pci/hp connected configured ok
    iou#0-pci#4 pci-pci/hp connected configured ok
    px_pci3.pci1 ; unknown empty unconfigured unknown
    px_pci5.pci1 ; unknown empty unconfigured unknown
    px_pci7.pci1 ; unknown empty unconfigured unknown
    # prtdiag
    System Configuration: Sun Microsystems sun4u Sun SPARC Enterprise M5000 Server
    System clock frequency: 1012 MHz
    Memory size: 32768 Megabytes
    ==================================== CPUs ====================================
    CPU CPU Run L2$ CPU CPU
    LSB Chip ID MHz MB Impl. Mask
    00 0 0, 1, 2, 3 2150 5.0 ; 6 147
    00 1 8, 9, 10, 11 2150 5.0 ; 6 147
    00 2 16, 17, 18, 19 2150 5.0 ; 6 147
    00 3 24, 25, 26, 27 2150 5.0 ; 6 147
    ============================ Memory Configuration ============================
    Memory Available Memory DIMM # of Mirror Interleave
    LSB Group Size Status Size DIMMs Mode Factor
    00 A 16384MB okay 2048MB 8 no 4-way
    00 B 16384MB okay 2048MB 8 no 4-way
    ========================= IO Cards =========================
    LSB Name Model
    00 scsi LSI,1064
    00 network N/A
    00 network N/A
    00 network SUNW,pci-x-q
    00 network SUNW,pci-x-q
    00 network SUNW,pci-x-q
    00 network SUNW,pci-x-q
    00 network SUNW,pcie-qg
    00 network SUNW,pcie-qg
    00 network SUNW,pcie-qg
    00 network SUNW,pcie-qg
    00 ethernet N/A
    00 pci1014,36e N/A
    00 ethernet N/A
    00 pci1014,36e N/A
    00 ethernet N/A
    00 pci1014,36e N/A
    00 ethernet N/A
    00 pci1014,36e N/A
    00 ethernet N/A
    00 pci1014,36e N/A
    00 ethernet N/A
    00 pci1014,36e N/A
    ==================== Hardware Revisions ====================
    System PROM revisions:
    OBP 4.24.10 2008/08/12 19:52
    =================== Environmental Status ===================

  • Inconsistent entries between driver_aliases and path_to_inst

    Hi,
    I see the following in my solaris intel box.
    bash-2.03# grep iprb /etc/driver_aliases
    iprb "pci8086,1229"
    iprb "pci8086,1029"
    bash-2.03# grep iprb /etc/path_to_inst
    "/pci@0,0/pci8086,100c@6" 0 "iprb"
    bash-2.03#
    100c is the inte pro/1000 gig NIC and 1229/1029 are pro/100 fast ethernet NICs.
    The following are my questions:
    1. How can iprb bind to 100c when the aliases do not exist for it?
    2. The iprb is actually binding to the pro/100 NIC(I know this since I can ssh into the box etc, pro1000 card has no connectivity). Does this mean the what ever is in path_to_inst cannot be trusted?
    3. After solaris boots, how do we know what NIC is bound to which driver(assuming a case when we different NICs managed by different drivers.)
    4. What the contention resolution algorithm for driver binding. In other words what does solaris do when more then one driver says it can manage a particular device.
    any help is greatly appreciated,
    Vijay
    ps: BTW, everytime I reboot I do a reconfiguration reboot so that path_to_inst gets updated.

    Here's the long and short of it...
    entries like this in the lpfc.conf file:
    fcp-bind-WWPN="50060482ccb4bbbb:lpfc3t6",
    "50060482ccb4bccc:lpfc5t7",
    "50060482ccb4bddd:lpfc8t9",
    "5006048accb4beee:lpfc9t10",
    "5006048accb4bfff:lpfc10t25",
    "5006048accb4bggg:lpfc11t24",
    "50060482ccb4bhhh:lpfc15t8",
    "50060482ccb4biii:lpfc16t12",
    "5006048accb4bjjj:lpfc20t38",
    "5006048accb4bkkk:lpfc21t13",
    "5006048accb4bmmm:lpfc22t40",
    [snip]
    "5006048accb4bnnn:lpfc25t23";
    and these in the sd.conf file:
    # Start of SD.CONF Entries for DMX
    name="sd" parent="lpfc" target=6 lun=16;
    name="sd" parent="lpfc" target=6 lun=17;
    name="sd" parent="lpfc" target=6 lun=18;
    name="sd" parent="lpfc" target=6 lun=19;
    name="sd" parent="lpfc" target=6 lun=20;
    name="sd" parent="lpfc" target=7 lun=68;
    name="sd" parent="lpfc" target=7 lun=69;
    name="sd" parent="lpfc" target=7 lun=70;
    name="sd" parent="lpfc" target=7 lun=71;
    name="sd" parent="lpfc" target=7 lun=72;
    [snip]
    name="sd" parent="lpfc" target=9 lun=133;
    name="sd" parent="lpfc" target=9 lun=134;
    name="sd" parent="lpfc" target=9 lun=135;
    name="sd" parent="lpfc" target=9 lun=136;
    will create /etc/path_to_inst entries for each LUN, for each TARGET, for each LPFC instance. Normally it's not a problem. In my case I have 44 Emulex LPFC instances, a TON of targets (an average of 1.5 per FA<->HBA mappings) and a TON of LUNS.
    # of HBA(lpfc) x total # of Lun ((sum of lpfc lun/target) + sum of scsi lun/target)) ~ 32,767
    Anyway, by using the hba="..." format in the sd.conf file, we were able to eliminate all of the extra /etc/path_to_inst entries created. This reduced the "sd" entries in /etc/path_to_inst to just over 3,000. Example
    name="sd" parent="lpfc" target=33 hba="lpfc17" lun=123;
    If the instance numbers on my HBA's ever change, I'm in trouble. Of course, this could have been avoided with the latest lpfc driver, or by using leadvill because they don't require entries in sd.conf.
    Thanks to all who assisted.

  • IPRBconf

    hello there! i have installed solaris 11/06 x86 on mt toshiba satellite laptop and the OS did not found the network card --Intel Pro /100 VE and i do have dual boot of winXP on the same laptop and i explored in the XP to find out the vendor id and product id number and even i found it using #prtconf -pv and the id is
    8086,1092
    and i edited /etc/driver_aliases and
    iprb "pci8086,1092" and add some lines in /boot/solaris/devicedb/master as follows
    pci8086,1092, pci8086,1092 net pci iprb.bef"intel pro/100 VE network card"
    and used the ff commands in their order
    #devlinks
    #touch /reconfigure
    #reboot
    #ifconfig iprb0 plumb
    in this case it said unknown interface ! is there someone who can help me?
    pls forward yoyr comment on my problem
    thank you
    Dawit Assefa {CCIE-written, CCNP}

  • Unable to regenerate /dev/rmt/0 drivers with cfgadm -c configure on Solaris 10 update 11 (1/13).  How does one do this for SAS HBA StorageTek Autoloader?

    How does one regenerate the /dev/rmt/0 when cfgadm -c configure <device> will not rebuild it?  Have attempted reboot -- -r, with modifing /kernel/drv/st.conf as well as /kernel/drv/sgen.conf.  Running on a SPARC T4-1 Solaris 10 updat3 11, (1/13).

    This has been resolved.  Getting the /etc/driver_aliases set correctly: # update_drv -d -i st; update_drv -d -i sgen; add_drv -m '* 0600 root sys' -i '"scsiclass,01" "scsiclass,08" wa' worked.  Making sure the st and sgen entries are in /etc/name_to_major were needed.  For the Simpana/CommVault WA drivers, in opt/simpana/WA/wa.conf with the name="wa" parent="fp" target=16 lun=0 fc-port-wwn="device's World Wide Number> added for each lun 0 to 7.  Then the touch /reconfigure; reboot worked.  First the c1::rmt/0 tape and c1::scsi/changer/<wwn> med-changer were mapped.  After modifying the minor_perm ('* 0600 root sys') and name_to_major entries, the WA CommValt entries , WA drivers showed up in cfgadm -al as c1::wa0  tape and c1::wa1  med-changer, only recognizable from CommVault.  Also had to update the SAS-2 HBA StoregTek Autoloader driver with patch 145648-05. Solaris 10 update 11 (1/13) comes with 145648-03.  In our particular case, we found cfgadm -al mapped SAS-2 HBA to c1 using the single mini-sas 6gb connector cable, where it mapped to c7 with the four tail connector.

  • How can I set ne2000 network adapter in Solaris 8 for x86

    I am a beginner. I can not set a ne2000 compatible network adapter(isa) in Solaris 8 for x86.
    I do follows:
    write the file ' /kernel/drv/nei.conf ' with ' name="nei" parent="isa" reg=0x1,0x0300,0x1f interrupts=10 '
    and use the command: drvconfig -i nei --failed
    use the command: drv_add -i nei; devlinks; --there is no the command drv_add
    use the command: touch /reconfigure; reboot
    after reboot, use the command: ifconfig nei0 plumb --failed
    Did I miss something obvious, or what driver should I use?

    After backing up the suspect hard drive, I ran Disk Repair on it and found no problems. Then ran Disk Warrior again and no problems. It is a Hitachi, btw.
    As for the PrefPane issue: Repairing disk permissions on the main volume and on the partition that holds the system did not make any difference.
    Reinstalled the 10.5.8 upgrade, performed safe start and then repaired permissions again. Still getting a blank PrefPane for network.
    Next step is to try and trash the System Configuration plist and Network Interfaces plist.

  • Solaris 10 x86:detect new hard drive

    hi.
    I'm on solaris 10 X86, and I added a hdd today. I can see it in the bios, but nothing appears in my solaris' files: vfstab, mnttab...etc.
    nevertheless, it's in the /var/adm/messages:
    genunix: [ID 846691 kern.info]   model IBM-DTLA-305020I tried touch /reconfigure;reboot and reboot -- -r, but still nothing.
    How could I make solaris detect my new hdd please?

    That's ok now.
    I saw my hdd with the format command. After:
    - partition option in the format command
    - created new fs (with newfs)
    - modified /etc/vfstab
    - mounted /<new fs>
    bye.

  • Solaris Cluster 3.3 on VMware ESX 4.1

    Hi there,
    I am trying to setup Solaris Cluster 3.3 on Vmware ESX 4.1
    My first question is: Is there anyone out there setted up Solaris Cluster on vmware accross boxes?
    My tools:
    Solaris 10 U9 x64
    Solaris Cluster 3.3
    Vmware ESX 4.1
    HP DL 380 G7
    HP P2000 Fibre Channel Storage
    When I try to setup cluster, just next next next, it completes successfully. It reboots the second node first and then the itself.
    After second node comes up on login screen, ping stops after 5 sec. Same either nodes!
    I am trying to understand why it does that? I did every possibility to complete this job. Setted up quorum as RDM from VMware. Solaris has direct access to quorum disk now.
    I am new to Solaris and I am having the errors below. If someone would like to help me it will be much appreciated!
    Please explain me in more details i am new bee in solaris :) Thanks!
    I need help especially on error: /proc fails to mount periodically during reboots.
    Here is the error messages. Is there any one out there setted up Solaris Cluster on ESX 4.1 ?
    * cluster check (ver 1.0)
    Report Date: 2011.02.28 at 16.04.46 EET
    2011.02.28 at 14.04.46 GMT
    Command run on host:
    39bc6e2d- sun1
    Checks run on nodes:
    sun1
    Unique Checks: 5
    ===========================================================================
    * Summary of Single Node Check Results for sun1
    ===========================================================================
    Checks Considered: 5
    Results by Status
    Violated : 0
    Insufficient Data : 0
    Execution Error : 0
    Unknown Status : 0
    Information Only : 0
    Not Applicable : 2
    Passed : 3
    Violations by Severity
    Critical : 0
    High : 0
    Moderate : 0
    Low : 0
    * Details for 2 Not Applicable Checks on sun1
    * Check ID: S6708606 ***
    * Severity: Moderate
    * Problem Statement: Multiple network interfaces on a single subnet have the same MAC address.
    * Applicability: Scan output of '/usr/sbin/ifconfig -a' for more than one interface with an 'ether' line. Check does not apply if zero or only one ether line.
    * Check ID: S6708496 ***
    * Severity: Moderate
    * Problem Statement: Cluster node (3.1 or later) OpenBoot Prom (OBP) has local-mac-address? variable set to 'false'.
    * Applicability: Applicable to SPARC architecture only.
    * Details for 3 Passed Checks on sun1
    * Check ID: S6708605 ***
    * Severity: Critical
    * Problem Statement: The /dev/rmt directory is missing.
    * Check ID: S6708638 ***
    * Severity: Moderate
    * Problem Statement: Node has insufficient physical memory.
    * Check ID: S6708642 ***
    * Severity: Critical
    * Problem Statement: /proc fails to mount periodically during reboots.
    ===========================================================================
    * End of Report 2011.02.28 at 16.04.46 EET
    ===========================================================================
    Edited by: user13603929 on 28-Feb-2011 22:22
    Edited by: user13603929 on 28-Feb-2011 22:24
    Note: Please ignore memory error I have installed 5GB memory and it says it requires min 1 GB! i think it is a bug!
    Edited by: user13603929 on 28-Feb-2011 22:25

    @TimRead
    Hi, thanks for reply,
    I have already followed the steps also on your links but no joy on this.
    What i noticed here is cluster seems to be buggy. Because i have tried to install cluster 3.3 on physical hardware and it gave me excat same error messages! interesting isnt it?
    Please see errors below that I got from on top of VMware and also on Solaris Physical hardware installation:
    ERROR1:
    Comment: I have installed different memories all the time. It keeps sayying that silly error.
    problem_statement : *Node has insufficient physical memory.
    <analysis>5120 MB of memory is installed on this node.The current release of Solaris Cluster requires a minimum of 1024 MB of physical memory in each node. Additional memory required for various Data Services.</analysis>
    <recommendations>Add enough memory to this node to bring its physical memory up to the minimum required level.
    ERROR2
    Comment: Despite rmt directory is there I gor error below on cluster check
    <problem_statement>The /dev/rmt directory is missing.
    <analysis>The /dev/rmt directory is missing on this Solaris Cluster node. The current implementation of scdidadm(1M) relies on the existence of /dev/rmt to successfully execute 'scdidadm -r'. The /dev/rmt directory is created by Solaris regardless of the existence of the actual nderlying devices. The expectation is that the user will never delete this directory. During a reconfiguration reboot to add new disk devices, if /dev/rmt is missing scdidadm will not create the new devices and will exit with the following error: 'ERR in discover_paths : Cannot walk /dev/rmt' The absence of /dev/rmt might prevent a failover to this node and result in a cluster outage. See BugIDs 4368956 and 4783135 for more details.</analysis>
    ERROR3
    Comment: All Nics have different MAC address though, also I have done what it suggests me. No joy here as well!
    <problem_statement>Cluster node (3.1 or later) OpenBoot Prom (OBP) has local-mac-address? variable set to 'false'.
    <analysis>The local-mac-address? variable must be set to 'true.' Proper operation of the public networks depends on each interface having a different MAC address.</analysis>
    <recommendations>Change the local-mac-address? variable to true: 1) From the OBP (ok> prompt): ok> setenv local-mac-address? true ok> reset 2) Or as root: # /usr/sbin/eeprom local-mac-address?=true # init 0 ok> reset</recommendations>
    ERROR4
    Comment: No comment on this, i have done what it says no joy...
    <problem_statement>/proc fails to mount periodically during reboots.
    <analysis>Something is trying to access /proc before it is normally mounted during the boot process. This can cause /proc not to mount. If /proc isn't mounted, some Solaris Cluster daemons might fail on startup, which can cause the node to panic. The following lines were found:</analysis>
    Thanks!

  • LUN has gone AWOL - Solaris 10 x86, Emulex HBAs, IBM DS8300

    We're setting up a test environment for our backup software, currently running on Windows, but targeted for Solaris. This is also a test of our first Solaris x86 deployment.
    * HP DL580 G5 server.
    * Solaris 10 x86 10/08 w/patch cluster from ~March 18th.
    * One dual port Emulex HBA
    * IBM DS8300 SAN
    When we first set this up, we could see the one LUN in format. After adding in the IBM Multipathing software, the LUN disappeared and the FC devices are shown as unconfigured in `cfgadm -al`. We removed the IBM multipathing software, but still cannot see the LUN. Did a reconfiguration reboot and all that.
    Current state:
    # cfgadm -al c6
    Ap_Id                          Type         Receptacle   Occupant     Condition
    c6                             fc-fabric    connected    unconfigured unknown
    c6::5005076306130287           unknown      connected    unconfigured unknown
    # luxadm -e port
    /devices/pci@0,0/pci8086,3607@4/pci10b5,8533@0/pci10b5,8533@a/pci10df,fe00@0/fp@0,0:devctl  CONNECTED
    /devices/pci@0,0/pci8086,3607@4/pci10b5,8533@0/pci10b5,8533@a/pci10df,fe00@0,1/fp@0,0:devctl  NOT CONNECTED
    # luxadm -e dump_map /devices/pci@0,0/pci8086,3607@4/pci10b5,8533@0/pci10b5,8533@a/pci10df,fe00@0/fp@0,0:devctl
    Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
    0    a0200   0        5005076306130287 5005076306ffc287 0x1f (Unknown Type)
    1    a0100   0        10000000c97a7866 20000000c97a7866 0x1f (Unknown Type,Host Bus Adapter)
    # modinfo|grep FC
    102 ffffffffefc2c000  1aab0 190   1  fp (SunFC Port v20090205-1.79)
    103 ffffffffefc47000  199f0 194   1  fcp (SunFC FCP v20090205-1.132)
    104 ffffffffefc63000   a2a0   -   1  fctl (SunFC Transport v20090205-1.59)
    107 ffffffffefc6c000 377bc0 191   1  emlxs (SunFC emlxs FCA v20081211-2.31p)
    189 ffffffffefb547e0   9620 193   1  fcip (SunFC FCIP v20090205-1.50)
    190 ffffffffefb49dc0   5610 196   1  fcsm (Sun FC SAN Management v20070116)
    #c6 is the first port on the dual port card. c7, not shown, is the second port. Prior to installing the IBM multipathing software, we were seeing the one assigned LUN on c6.
    Trying to `cfgadm -c c6` does nothing. Adding `-f` causes an error:
    # cfgadm -c configure c6
    # cfgadm -al c6
    Ap_Id                          Type         Receptacle   Occupant     Condition
    c6                             fc-fabric    connected    unconfigured unknown
    c6::5005076306130287           unknown      connected    unconfigured unknown
    # cfgadm -f -c configure c6
    cfgadm: Library error: failed to create device node: 5005076306130287: Invalid argument
    failed to configure ANY device on FCA port
    # cfgadm -al c6
    Ap_Id                          Type         Receptacle   Occupant     Condition
    c6                             fc-fabric    connected    unconfigured unknown
    c6::5005076306130287           unknown      connected    unconfigured unknown
    #We're currently at a loss here. Any pointers would be greatly appreciated. I am checking sunsolve and google, with plenty of similar hits, but no resolution as yet.
    Thanks,
    Mark

    Ok, so after that detailed message, my SAN admin just realised he hadn't assigned any LUNs to the server. :D
    The LUN that we had seen previously was an artifact from an earlier configuration.

  • Solaris 10 Patch problems

    I installed patch 119254-35 on the weekend. It went in with no errors. HOWEVER, now when I try to apply any other patch AT ALL (I have 11 more to go), the patchadd program fails with
    global variable zonecfg_open_scratch is not set.
    If I try pkgadd instead, then it fails because of zonecfg_set_root not being set.
    HOW DO I FIX THIS PLEASE?
    Thanks,
    -Richard

    I've read that kernel patch 118833-36 requires a reconfiguration reboot prior to allowing any other patches to be installed within the patch cluster. Hence, you would reboot your server to single user, install the cluster, reboot again using a reconfiguration reboot back into single user mode, and run the install_cluster again.

  • Realtek NIC cannot attach in Solaris 10 with Intel D945GCPE motherboard

    Hope someone can help. I've seen references online to people having installed Solaris 10 on this board.
    I can't get the NIC to work on on Solaris 10. I downloaded the drivers from Realtek's site. Ran the install script which said the drivers were installed but failed to attach.
    prtconf doesn't show the drivers. I did a reconfigure reboot ( touch /reconfigure; reboot) and it didn't work so I get an error if I try and plumb the interface.
    I created a /etc/hostname.rtls0 file and updated /etc/inet/hosts and /etc/inet/netmasks though I don't think that means anything at this point.
    There's no setting to disable plug and play, just an acpi option to change from type 2 or 3 I believe.
    I tried setting the acpi boot env variable using
    eeprom acpi-user-options=0x2
    but that just made the hard drive unreadable.
    I tried setting pcplusmp:apic_forceload = -1 in /etc/system and that caused the system to hang.
    From looking around online I'm wondering if the realtek drivers are 32bit? Can anyone confirm this?
    If true, that might be causing the problems with the driver install since Solaris is installed as 64bit.
    I'm going to try and build the drivers myself from the sources I found at http://homepage2.nifty.com/mrym3/taiyodo/eng/. Hopefully that's the only problem.
    If anyone has any experience with this board please let me know.
    Also, when Solaris hangs when booting up, CTRL-ALT-DEL doesn't reboot the system. I'm connected via IPKVM and can't do a hard reboot. Is there any other way to reboot the system when it hangs? CTRL-C don't do anything either.

    Darren_Dunham wrote:
    Do you see the driver files? Often something like '/kernel/drv/xxx'. 32bit drivers will be in drv/xxx, 64bit drivers will be in drv/amd64/xxx.
    If there's no corresponding driver in the amd64 directory, it's not 64 bit. But since you're getting messages from the driver at all, I doubt that's the issue.
    Darren, thanks for responding.
    I haven't been able to reboot yet to check. I'm just going by another forum posting I read that said the Realtek drivers were 32bit. Stupid question, but amd64 is just an old convention from when Sun first started x86-64 servers with Opterons, and all 64 bit drivers go in that directory even if the underlying processor is Intel right?
    This tech note http://access1.sun.com/technotes/01146.html led me to believe it was the 32bit driver on 64bit OS that was the problem since the install script claimed to install everything fine and I remember checking at least the /kernel/drv directory. At the time, I didn't think to check adm64, actually, I didn't even notice it installed in 64bit mode.
    Darren_Dunham wrote:
    Ouch. You might be able to boot the kernel debugger and force it to reboot. I haven't done that on an x86 system, but here are some instructions:
    http://www.sun.drydog.com/faq/7.html
    So <F1>-<A> should give you a key to pull up the debugger and reboot.
    DarrenAh, F1-A, that's the x86 equivalent to Stop-A. That link was very helpful, unfortunately F1-A does nothing. I'm stuck on "Use is subject to license terms" with a blinking underscore. I tried setting up a keyboard macro in the kvm client for F1-A too and that didn't work either. Looks like I need to add boot-file=kadb into /boot/solaris/bootenv.rc to enable the debugger. ctrl-break, shift-break, ctrl-shift-break, ctrl-\, ctrl-alt-break, ctrl-a, ctrl-q, ctrl-s, ctrl-] as well as slamming both hands repeatedly on the keyboard while screaming profanities also failed to reboot the system. The person I was working with at the data center left for the day, I need to see if I can find someone else to reboot this.
    One thing I read on that link you provided, it said using reboot -- -r is bad on x86 systems. Do you know if that might be what caused the problems and not the eeprom or /etc/system settings? When I get into failsafe mode, do I need to make any changes to /boot/solaris/bootenv.rc to undo the reboot -- -r command? I didn't get the errors the FAQ said I'd be getting if I used that option so I think everything might be ok.

Maybe you are looking for

  • No audio for clips in my event library since upgrading to iLife '09

    After upgrading to iLife '09, I noticed something odd in the new iMovie. All of my clips (recorded with a Sanyo Xacti HD1A and imported into the previous version of iPhoto DO show up in the event library, but DO NOT play any sound in the event librar

  • How to get rid of ._songs when trans to cell phone?

    I use a microSD to play mp3s on my LG chocolate (I know... i'll get an iPhone one day!). The only problem is, if I drag-and-drop 30 songs to the card, when I use it on the phone, I now have 60 items, with 30 of them being duplicate titles with "._" i

  • X230T camera does not work under windows 8

    Hi! Is your camera working under Windows 8? Mine is not. It used to work some time ago, but even then the driver was instable. Now, since a few weeks, it seems not to work at all anymore. Reinstalling the driver does not help. This may ba a hardware

  • Help! Motion won't startup

    When I click on the icon in the Dock... it bounces once, and then nothing! (the worst part is... I can't find the install disk to reinstall!) Here's the crash reporter log: Library not loaded: /System/Library/PrivateFrameworks/LiveType.framework/Vers

  • How to make a region "block" instead of "inline"

    Sorry if this is a facile question, but I'm new to Apex and its UIs, and I haven't been able to find a way around this problem. So, I have a hidden region that is shown when a button is hit. Both the hiding of the region when the page is loaded and t