Solaris 8 on Compaq ProLiant 1600

We tried to install Solaris 8 on a Compaq ProLiant 1600/500
with dual processor. The installation failed in the "scanning hardware
configuration" phase entering into debugger mode.
We know that our configuration is NOT on the hardware compatibility list.
On the other hand the Compaq ProLiant 1600 (2 CPUs, PIII-550) can be found
in the HCL.
Any kind of help would be higly appreciated.
Andras

The first thing to do with a Compaq is make sure the latest and greatest rompaq has been applied to the board and all devices. Next, download and use the latest and greatest Solaris DCA diskette and use it for the install boot. I am making the assumption you are using the CD this time around. If that doesnt work, you will have to remove all but the bare minimun of hardware and try the install then add each device one by one. The DCA diskettes are updated regularly so thelatest one may solve the issue.
Lee

Similar Messages

  • Compaq Proliant 1600 Server Install

    Hi!
    I'm working on setting up a Compaq Proliant 1600 server. . .I've made a bit of progress thanks to a few posts on the forum.
    I've bugged everyone on the irc channel so now its time to ask here  :oops:
    Basically, I can't get the Arch install to recognize the scsi drives (2) I've got...
    What I've done:
    1.  Loaded all the modules (cpqarray etc...)
    2.  In '/dev' I did 'mkdir ida'
    3.  Next I 'mknod /dev/ida/c0d0p1 b 72 1' <---this should be my swap
    4.  Then I 'mknod /dev/ida/c0d0p2 b 72 2' <-----this is my /
    Now I'm not sure what to do...
    Since I've been able to partition the drives the next step seems to be to
    set filesystem mountpoints, right?  The Arch install doesn't recognize  the drives at all - It simply says "NONE". 
    So, if anyone has any tips or advice I'd appreciate it 
    I'm setting this server up for my school's website - and thought I'd go with Arch. . .
    Thanks!
    nedson

    It's all about loading the right modules. With < 0.7 ISO's you can modprobe cpqarray. Later ISO's don't have cpqarray anymore, they use cciss.
    Some threads you'll want to read:
    Help no cpqarray modules
    Compaq proliant install help

  • Install solaris 10 on Proliant 1600 - Compaq Smart Array 221

    I'm trying to install solaris 10 06/06 on a Proliant 1600 with smart array 221.
    I boot from the cd and choose the first option (Solaris), then I get this warning:
    WARNING: failed to program IO space [0/20/2] BAR@0x20 length 0x20
    and the system hang up.
    Does anyone know to what it is related to?
    Thank you
    Andrea V

    I have the save problem when installing Solaris 10 on my System.
    my configuration:
    Proliant 1600
    Compaq Smart Array 221
    1 CPU 550mhz
    512M RAM
    It would be nice if somebody could help.
    Edit:
    The system crashes in the same way when I try to boot the "install check CD 1.1."
    Message was edited by:
    darthich

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

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

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

  • I have a Compaq Proliant 1600 PII 450. the installation hangs. any ideas ?

     

    Hi,
    Can you tell me at what stage it hangs? Which version of Solaris ur trying to install? And if u could give more informations that will help to solve ur problem.
    Ramesh ([email protected])

  • No /dev/lp? on COMPAQ Proliant ML370 with Solaris 8 x86 10/00

    Dear Sir,
    I have a problem about the /dev/lp? port in Solaris 8 x86 with COMPAQ Proliant ML370. I have seen in the boot interpreter it has detected a parallel port
    device isa/lp@1...., but after I boot -r to start Solaris 8
    OS it don't make any /dev/lp? or /devices/isa/lp*... and if
    I mknod /dev/lp? myself it cannot print out ( I use cat /etc/hosts >> /dev/lp1, /dev/lp1 major=83 minor=1 ) It say "cannot create". I wonder why this happens, If I install this Solaris 8 x86 on other PC model. It has /dev/lp1 and can print out successfully. I try many ways such as: upgrade latest ROMPAQ BIOS firmware,
    install lp driver patch set, install acpi patch. But still don't work. I found that serial ports (asy) which are ACPI is working because I can redirect console to serial port (asy).
    Do anyone have the idea to solve or track down this problems. Thanks a lot...

    Check out the HP Compaq web site and you shuld be able to find the Solaris drivers that are needed. http://h18023.www1.hp.com/support/files/server/us/download/19340.html

  • Compaq proliant ML370 installation

    we are triyng to install solaris 8 intel on compaq proliant ml370. when we are loading the firt software cd at the point when is loading the package SUNWnamow the system hang without any warning messages.
    we cannot complete the installation.
    we will apreciate all yours helps regarding this matter.
    B4N

    Check out the HP Compaq web site and you shuld be able to find the Solaris drivers that are needed. http://h18023.www1.hp.com/support/files/server/us/download/19340.html

  • Latest kernel crash while installing on a Compaq Proliant ML370G2

    SunOS Release 5.8 Version Generic_108529-13 32-bit
    Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
    panic[cpu0]/thread=fec17660: BAD TRAP: type=0 (Divide Error Exception) rp=fec12b70 addr=0
    Divide Error Exception
    pid=0, pc=0xfea6b5ef, sp=0x1c, eflags=0x10246
    eip(fea6b5ef), eflags(10246), ebp(fec12bc0), uesp(1c), esp(fec12ba0)
    eax(d18a09), ebx(d18a09), ecx(0), edx(0), esi(0), edi(1c)
    cr0(80050033), cr2(0), cr3(1e69000)
    cs(158) ds(160) ss(5868) es(160) fs(1a8) gs(1b0)
    fec12aa4 unix:die+9c (0, fec12b70, 0, 0, 1c)
    fec12b5c unix:trap+2f6 ()
    fec12b70 unix:_cmntrap+94 (fec10160, e1420160, 1c)
    fec12bc0 unix: pcplusmp:apic_clkinit+77 ()
    fec12bdc unix:mach_clkinit+113 (fec09750)
    fec12c1c unix:cbe_init+6b ()
    fec12c2c genunix:main+1e ()
    skipping system dump - no dump device configured
    rebooting...

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

  • 2nd CPU not recognized on Compaq Proliant 1500

    I have x86/2.6 running on a dual CPU Compaq Proliant 1500, but it's not recognizing the 2nd CPU. (verified with mpstat)
    Does anyone know how to convince x86 to initialize the 2nd CPU?
    Thanks in advance!
    David

    Saw your post at http://forum.sun.com/profile.jsp?user=10948. I was having the exact same problem with the EXACT same hardware and I got the solution for you too. No charge! :-)
    I contacted Compaq support and got a REAL sharpy on the phone. Compaq EISA config has an undocumented feature called 'Advanced'. To turn on the second CPU in Compaq ROM, follow these steps.
    Start EISA config.
    To use the 'Advanced' feature, merely hit 'CTRL-A' at the EISA config main menu.
    Run configure system.
    When it is done, go into Edit Details and scroll down until you see a line item called APIC.
    It probably says DISABLED.
    Highlight it and hit the ENTER key.
    At that point, you'll see two options for 'ENABLE'.
    Pick the one that says 'Full Table'. 'Full Table - Mapped' evidently don't mix with Solaris.
    Save and exit, cycle power, and restart EISA config.
    Save, exite, recycle power again.
    At this next power up, the post message should say 'Processors Running at xxx' The next line should say Processor 2 initializing. When Solaris boots up, use the psrinfo command (no options) and it should show both processors up and running. psadm allows you to change the state of the other processor.
    Let me know how this works. Mine is working like a champ!

  • Installing Arch i686 on my Compaq ProLiant 5500. Will it detect the..

    I got a Compaq ProLiant 5500 and going to install Arch on it for a web/email server so will it detect the SCSI's out of box or what?
    Also, how should I partition my drives for it?  It'll be a web/mail/dns/dhcp server.

    The driver for SCSI drives is in the ARch kernel so it shouldn't be a problem.  I have a scsi-drive on one of my computer's and it has no problems.  As how to partition, I'd look at one of the BSD-guides.  Alot of BSD's are used for mail servers and have good advice on how to partition.  If i remember correctly you'll want partitions for /, /tmp, and /var...  Here, I done looked it up for ya :
    http://openbsd.org/faq/faq4.html#Partitioning

  • 9IAS install on Compaq Proliant DL360

    I have been trying to install 9IAS Release 2 (9.0.2.0.1) - on Compaq Proliant DL360 (Win200).After install EM website stops intermittently and unable to run Forms - is there a
    problem with 9IAS and Proliant DL360 and is there any way round it?

    Alec,
    Some ideas:
    1) Do you have .Net running simultaneously?
    See: http://download-west.oracle.com/docs/cd/B10573_02/relnotes.902/addendum/oem.htm#1007067
    2) Do you have a fixed IP address or DHCP?
    See: http://download-west.oracle.com/docs/cd/B10573_02/relnotes.902/addendum/ipchange.htm#1004903
    3) Did you install the infra & the middle tier in separate ORACLE_HOMEs?
    Thanks,
    Ashesh Parekh
    Oracle9iAS Product Manager

  • Compaq proliant install help

    Can someone please give me some tips as i need to install Arch on my Compaq Proliant server.
    I know i need the cpqarray , tlan , sym53c8xx_2 , sd_mod , scsi_mod
    But i still cant see the dev files for ida blah blah so Arch cant see my drive.
    I have the raid setup as mirroring ( Raid 1 ) on 3 * 9Gb scsi drives.
    If you have installed Arch on one of these servers can you help me out. I will be using the 0.7.1 noodle cd.
    Regards,
    Justin Smithies

    /etc/udev/udev.conf
    # udev.conf
    # Where in the filesystem to place the device nodes
    udev_root="/dev"
    # The name and location of the udev database.
    udev_db="/dev/.udevdb"
    # The name and location of the udev rules file(s).
    udev_rules="/etc/udev/rules.d"
    # The syslog(3) priority: "err", "info", or the numerical value.
    udev_log="err"
    /etc/udev/scsi-devfs.sh
    #! /bin/sh
    # scsi-devfs.sh: udev external PROGRAM script
    # Copyright 2004 Richard Gooch <[email protected]>
    # Copyright 2004 Fujitsu Ltd.
    # Distributed under the GNU Copyleft version 2.0.
    # return devfs-names for scsi-devices
    # Usage in udev.rules:
    # BUS="scsi", KERNEL="sd*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh sd %b %n",
    NAME="%c{1}", SYMLINK="%c{2} %k %c{3} %c{4}"
    # BUS="scsi", KERNEL="sr*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh sr %b %n",
    NAME="%c{1}", SYMLINK="%c{2} %k %c{3} %c{4}"
    # BUS="scsi", KERNEL="st*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh st %b %n",
    NAME="%c{1}", SYMLINK="%c{2} %k %c{3} %c{4}"
    # BUS="scsi", KERNEL="sg*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh sg %b %n",
    NAME="%c{1}", SYMLINK="%c{2} %k %c{3} %c{4}"
    # Find out where sysfs is mounted. Exit if not available
    sysfs=`grep -F sysfs /proc/mounts | awk '{print $2}'`
    if [ "$sysfs" = "" ]; then
    echo "sysfs is required"
    exit 1
    fi
    cd $sysfs/bus/scsi/devices
    case "$1" in
    sd)
    # Extract partition component
    if [ "$3" = "" ]; then
    lpart="disc"
    spart=""
    else
    lpart="part$3"
    spart="p$3"
    fi
    sr)
    lpart="cdrom"
    spart=""
    st)
    # Not supported yet
    exit 1
    sg)
    lpart="generic"
    spart=""
    exit 1
    esac
    # Extract SCSI logical address components
    scsi_host=`echo $2 | cut -f 1 -d:`
    scsi_bus=`echo $2 | cut -f 2 -d:`
    scsi_target=`echo $2 | cut -f 3 -d:`
    scsi_lun=`echo $2 | cut -f 4 -d:`
    # Generate long and short common name parts
    l_com="bus$scsi_bus/target$scsi_target/lun$scsi_lun/$lpart"
    s_com="b${scsi_bus}t${scsi_target}u${scsi_lun}$spart"
    # Generate long and short logical names
    l_log="scsi/host$scsi_host/$l_com"
    s_log="$1/c${scsi_host}${s_com}"
    readlink $2 | grep -F -q pci
    if [ "$?" != "0" ]; then
    # Not a PCI controller, show logical locations only
    echo $l_log $s_log
    exit 0
    fi
    # Extract PCI address
    tmp=`readlink $2 | sed -e 's@/host.*/.*@@'`
    pci_addr=`basename "$tmp"`
    pci_domain=`echo $pci_addr | cut -f 1 -d:`
    pci_bus=`echo $pci_addr | cut -f 2 -d:`
    pci_slot=`echo $pci_addr | tr . : | cut -f 3 -d:`
    pci_function=`echo $pci_addr | cut -f 2 -d.`
    # Generate long and short physical names
    l_pci="domain$pci_domain/bus$pci_bus/slot$pci_slot/function$pci_function"
    l_phy="bus/pci/$l_pci/scsi/$l_com"
    s_phy="$1/pci/$pci_addr/$s_com"
    echo $l_phy $s_phy $l_log $s_log
    /etc/udev/rules.d/udev.rules
    # This ruleset should provide a DevFS-compatible device tree.
    # There are a number of modifiers that are allowed to be used in some
    # of the different fields. They provide the following subsitutions:
    # %n the "kernel number" of the device.
    # For example, 'sda3' has a "kernel number" of '3'
    # %e the smallest number for that name which does not matches an existing node
    # %k the kernel name for the device.
    # %M the kernel major number for the device
    # %m the kernel minor number for the device
    # %b the bus id for the device
    # %c the string returned by the PROGRAM
    # %s{filename} the content of a sysfs attribute.
    # %% the '%' char itself.
    # There are a number of modifiers that are allowed to be used in some of the
    # fields. See the udev man page for a full description of them.
    # global stuff
    # default permissions for all block devices
    SUBSYSTEM="block", GROUP="disk"
    # CD/DVD symlinks
    BUS="ide", KERNEL="hd[a-z]", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%c{1
    } %c{2} %c{3} %c{4} %c{5} %c{6}"
    BUS="scsi", KERNEL="sr[0-9]*", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%c
    {1} %c{2} %c{3} %c{4} %c{5} %c{6}"
    BUS="scsi", KERNEL="scd[0-9]*", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%
    c{1} %c{2} %c{3} %c{4} %c{5} %c{6}"
    # ide block devices
    BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-devfs.sh %k %b %n", SYMLINK="%c{
    1} %c{2}"
    # permissions for IDE CD devices
    BUS="ide", KERNEL="hd[a-z]", SYSFS{removable}="1", PROGRAM="/bin/cat /proc/ide/%
    k/media", RESULT="cdrom*", NAME="%k", GROUP="optical"
    # permissions for SCSI CD devices
    BUS="scsi", KERNEL="sr[0-9]*", SYSFS{type}="5", NAME="scd%n", GROUP="optical"
    BUS="scsi", KERNEL="sg[0-9]*", SYSFS{type}="5", NAME="%k", GROUP="optical"
    # permissions for IDE floppy devices
    BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-floppy.sh %k", RESULT="floppy",
    NAME{all_partitions}="%k", GROUP="floppy"
    # permissions for removable devices like cardreaders or sticks
    BUS="usb", KERNEL="sd*", PROGRAM="/etc/udev/usb-storage.sh %k", RESULT="1", NAME
    ="%k", GROUP="storage"
    # permissions for ide storage like pcmcia card readers
    BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-storage.sh %k", RESULT="1", NAME
    ="%k", GROUP="storage"
    # permissions for SCSI scanners
    BUS="scsi", KERNEL="sg[0-9]*", SYSFS{type}="6", NAME="%k", GROUP="scanner"
    # pty and tty legacy devices
    KERNEL="pty[a-z][a-z,0-9]*", NAME="legacy/%k"
    KERNEL="tty[a-z][a-z,0-9]*", NAME="legacy/%k"
    # md block devices
    KERNEL="md[0-9]*", NAME="md/%n"
    # device-mapper
    KERNEL="device-mapper", NAME="mapper/control"
    # floppy devices
    KERNEL="fd[0-9]*", NAME="fd%n", SYMLINK="floppy/%n fd%nu1440 fd%nu720 fd%nh1200
    fd%nu360", GROUP="floppy"
    # tty devices
    SUBSYSTEM="tty", GROUP="tty"
    KERNEL="tty[0-9]*", NAME="vc/%n"
    KERNEL="ttyS[0-9]*", NAME="tts/%n", SYMLINK="ttyS%n"
    KERNEL="ttyUSB[0-9]*", NAME="tts/USB%n"
    # vc devices
    KERNEL="vcs", NAME="vcc/0"
    KERNEL="vcs[0-9]*", NAME="vcc/%n"
    KERNEL="vcsa", NAME="vcc/a0"
    KERNEL="vcsa[0-9]*", NAME="vcc/a%n"
    KERNEL="ptmx", MODE="0666"
    KERNEL="tty", MODE="0666"
    # video devices
    SUBSYSTEM="video4linux", GROUP="video"
    KERNEL="dvb*", PROGRAM="/etc/udev/dvb.sh %k", NAME="%c", GROUP="video"
    KERNEL="nvidia*", GROUP="video"
    KERNEL="card[0-9]*", NAME="dri/%k", GROUP="video"
    KERNEL="3dfx*", NAME="%k", GROUP="video"
    # v4l devices
    KERNEL="video[0-9]*", NAME="v4l/video%n", SYMLINK="%k", GROUP="video"
    KERNEL="radio[0-9]*", NAME="v4l/radio%n", SYMLINK="radio%e", GROUP="video"
    KERNEL="vbi[0-9]*", NAME="v4l/vbi%n", SYMLINK="%k", GROUP="video"
    KERNEL="vtx[0-9]*", NAME="v4l/vtx%n", SYMLINK="%k", GROUP="video"
    # dm devices (ignore them)
    KERNEL="dm-[0-9]*", NAME=""
    # i2c devices
    KERNEL="i2c-[0-9]*", NAME="i2c/%n", SYMLINK="%k"
    # loop devices
    KERNEL="loop[0-9]*", NAME="loop/%n", SYMLINK="%k"
    # ramdisks
    KERNEL="ram[0-9]*", NAME="rd/%n", SYMLINK="%k"
    # framebuffer devices
    KERNEL="fb[0-9]*", NAME="fb/%n", SYMLINK="%k", GROUP="video"
    # misc
    KERNEL="rtc", NAME="misc/%k", SYMLINK="%k", GROUP="audio", MODE="0664"
    KERNEL="nvram", NAME="misc/%k", SYMLINK="%k"
    KERNEL="psaux", NAME="misc/%k", SYMLINK="%k"
    KERNEL="agpgart", NAME="misc/%k", SYMLINK="%k" GROUP="video"
    KERNEL="uinput", NAME="misc/%k", SYMLINK="%k"
    KERNEL="random", MODE="0666"
    KERNEL="urandom", MODE="0444"
    KERNEL="mem", MODE="0640", GROUP="kmem"
    KERNEL="kmem", MODE="0640", GROUP="kmem"
    KERNEL="port", MODE="0640", GROUP="kmem"
    KERNEL="full", MODE="0666"
    KERNEL="null", MODE="0666"
    KERNEL="zero", MODE="0666"
    KERNEL="sgi_fetchop", MODE="0666"
    KERNEL="sonypi", MODE="0666"
    KERNEL="inotify", NAME="misc/%k", SYMLINK="%k", MODE="0666"
    # sound devices
    # alsa devices
    SUBSYSTEM="sound", GROUP="audio"
    KERNEL="controlC[0-9]*", NAME="snd/%k"
    KERNEL="hw[CD0-9]*", NAME="snd/%k"
    KERNEL="pcm[CD0-9cp]*", NAME="snd/%k"
    KERNEL="midi[CD0-9]*", NAME="snd/%k"
    KERNEL="timer", NAME="snd/%k"
    KERNEL="seq", NAME="snd/%k"
    # oss devices
    KERNEL="audio*", NAME="sound/%k", SYMLINK="%k"
    KERNEL="dmmidi*", NAME="sound/%k", SYMLINK="%k"
    KERNEL="admmidi*", NAME="sound/%k", SYMLINK="%k"
    KERNEL="dsp*", NAME="sound/%k", SYMLINK="%k"
    KERNEL="adsp*", NAME="sound/%k", SYMLINK="%k"
    KERNEL="midi*", NAME="sound/%k", SYMLINK="%k"
    KERNEL="amidi*", NAME="sound/%k", SYMLINK="%k"
    KERNEL="mixer*", NAME="sound/%k", SYMLINK="%k"
    KERNEL="sequencer*", NAME="sound/%k", SYMLINK="%k"
    # input devices
    KERNEL="mice", NAME="input/%k", MODE="0644"
    KERNEL="mouse*", NAME="input/%k", MODE="0644"
    KERNEL="event*", NAME="input/%k"
    KERNEL="js*", NAME="input/%k", MODE="0664"
    KERNEL="ts*", NAME="input/%k"
    KERNEL="uinput", NAME="input/%k"
    # USB devices
    KERNEL="hiddev*", NAME="usb/%k"
    KERNEL="auer*", NAME="usb/%k"
    KERNEL="legousbtower*", NAME="usb/%k", MODE="0666"
    KERNEL="dabusb*", NAME="usb/%k"
    BUS="usb", KERNEL="lp[0-9]*", NAME="usb/%k"
    BUS="usb", KERNEL="ttyUSB*", SYSFS{product}="Palm Handheld*", SYMLINK="pilot"
    # printer devices
    SUBSYSTEM="printer", GROUP="lp"
    # netlink devices
    KERNEL="route", NAME="netlink/%k"
    KERNEL="skip", NAME="netlink/%k"
    KERNEL="usersock", NAME="netlink/%k"
    KERNEL="fwmonitor", NAME="netlink/%k"
    KERNEL="tcpdiag", NAME="netlink/%k"
    KERNEL="nflog", NAME="netlink/%k"
    KERNEL="xfrm", NAME="netlink/%k"
    KERNEL="arpd", NAME="netlink/%k"
    KERNEL="route6", NAME="netlink/%k"
    KERNEL="ip6_fw", NAME="netlink/%k"
    KERNEL="dnrtmsg", NAME="netlink/%k"
    KERNEL="tap*", NAME="netlink/%k"
    # CAPI devices
    KERNEL="capi", NAME="capi20", SYMLINK="isdn/capi20"
    KERNEL="capi*", NAME="capi/%n"
    # Network devices
    KERNEL="tun", NAME="net/%k"
    # raw devices
    KERNEL="raw[0-9]*", NAME="raw/%k"
    # kbd devices
    KERNEL="kbd", NAME="%k", MODE="0664"
    # packet devices
    KERNEL="pktcdvd", NAME="pktcdvd/control", GROUP="optical", MODE="0660"
    KERNEL="pktcdvd[0-9]*", NAME="pktcdvd/pktcdvd%n", GROUP="optical", MODE="0660"
    pacman -Qi udev
    Name : udev
    Version : 057-1
    Groups : None
    Packager : maci <[email protected]>
    URL : http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
    License : None
    Architecture : i586
    Size : 301287
    Build Date : Mon Apr 18 03:00:55 2005 UTC
    Install Date : Sat Apr 23 19:59:26 2005 UTC
    Install Script : Yes
    Reason: : explicitly installed
    Provides : None
    Depends On : coreutils hotplug
    Required By : None
    Conflicts With : None
    Description : The userspace dev tools (udev)
    Hope that helps.

  • Problem booting Solaris 10 on ProLiant server after installation.

    Hi all!
    I have a brand new HP ProLiant DL360 G5 server. It contains 6 internal
    hard drives. RAID 5 is configured on these drives using built-in HP
    Smart Array P400i controller. I've just installed Solaris 10 8/07 on this
    server. Solaris requires a driver for P400i controller. I'm using Driver
    Update CD created from HP provided ISO image. Solaris 10 is
    officially supported OS for DL360 G5 server.
    Installation proceeds as expected:
    1) At the begining of Solaris installation, Driver Update is used to
    load HP driver for raid controller. During installation, disk is
    recognized as c1d0t0 (the only disk in system); one partition is
    created on this disk.
    2) Disk is devided to 6 slices:
    c1d0t0s0 - swap, 4GB
    c1d0t0s1 - /, cca 32GB
    c1d0t0s[3,4,5,6] - /zones/[a,b,c,d] - each cca 160GB
    3) At the end of installation, CPQary3 driver is installed to target
    system without any errors reported. No errors are reported during
    installation at all.
    After reboot, GRUB is started. It shows boot menu containing two
    options:
    - Solaris 'normal' boot
    - failsafe boot
    PROBLEM: Selecting 'normal' boot leads to immediate system restart.
    According to documentation, this case occurs when PCQary3
    driver is not installed.
    I'm able to boot using 'failsafe' option in grub. After entering single
    user, I load PCQary3 driver to runtime using 'install-du' command.
    I'm also able to find instaled Solaris using 'install-recovery' and mount
    its root volume to /a directory. Necessary driver IS installed inside
    /a/kernel/drv/ directory. Options 'bootpath' in /a/boot/solaris/bootenv.rc
    file is set up correctly pointing to device associated with /dev/dsk/c1d0t0s1
    device. Also GRUB is able to recognize UFS filesystem for boot partition.
    I've already tried (without success):
    1) Use RAID 1+0 instead of RAID5
    2) Create only 3,5GB partition instead of 700GB large one.
    3) Place / on c1d0t0s0 instead of c1d0t0s1.
    4) Re-create boot archive using 'bootadm update-archive -R /a'
    So, everything seems to be installed correctly, but system cannot boot.
    Do you have any ideas how to fix this problem?
    Jozef

    Sounds like an issue I just had with a brand new X4150, installation and failsafe worked fine, but normal booting led to immediate reboot of the server. This was due to an incompatibility of solaris and intel's newest generation xeon chips.
    You can still boot 'normal' solaris in 32-bit mode:
    hit 'e' at the grub menu, 'e' again to edit the 'normal' boot entry and add 'kernel/unix' after multiboot. This should boot up solaris in 32-bit mode. From there, download and install the latest patch set (125370-06 and 127112-05 are fixing this issue). After that you should be fine.
    Bjoern

  • Kernel panic on Compaq Proliant ML370 G2

    Happens during installation of Solaris 8 (02/2002):
    SunOS Release 5.8 Version Generic_108529-13 32-bit
    Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
    panic[cpu0]/thread=fec17660: BAD TRAP: type=0 (Divide Error Exception) rp=fec12b70 addr=0
    Divide Error Exception
    pid=0, pc=0xfea6b5ef, sp=0x1c, eflags=0x10246
    eip(fea6b5ef), eflags(10246), ebp(fec12bc0), uesp(1c), esp(fec12ba0)
    eax(d18a09), ebx(d18a09), ecx(0), edx(0), esi(0), edi(1c)
    cr0(80050033), cr2(0), cr3(1e69000)
    cs(158) ds(160) ss(5868) es(160) fs(1a8) gs(1b0)
    fec12aa4 unix:die+9c (0, fec12b70, 0, 0, 1c)
    fec12b5c unix:trap+2f6 ()
    fec12b70 unix:_cmntrap+94 (fec10160, e1420160, 1c)
    fec12bc0 unix: pcplusmp:apic_clkinit+77 ()
    fec12bdc unix:mach_clkinit+113 (fec09750)
    fec12c1c unix:cbe_init+6b ()
    fec12c2c genunix:main+1e ()
    skipping system dump - no dump device configured
    rebooting...

    Check out the HP Compaq web site and you shuld be able to find the Solaris drivers that are needed. http://h18023.www1.hp.com/support/files/server/us/download/19340.html

  • CallManager on Compaq Proliant DL580

    Hi Guys,
    I read the post with the same subject, but, the post is old. My Customer have a CUCM 8.6.2 install about VMWare 5.1 EsXi in the hardware DL-580 GL. I would like know if this solution is approved to install CUCM.
    Thank You,
    Wilson

    You have to look at the 3rd-party server / specs-based column (at top) and walk through the requirements and links.  All vendors are now supported; however, a given server must meet specs for various components.  You need to know the details of what is in the HP server and compare to what is required to be supported.  You won't see a list of "Server A" is supported, "Server B" is not.
    Hailey
    Please rate helpful posts!

Maybe you are looking for