Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12
HP recently started supporting Debian, but only at version 5 and up. I tried to install Debian 4r8 on a DL360 g6 and none of the dvd or nic drivers ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Sep 2009
    Posts
    8

    Debian Etch on Proliant DL360 G6


    HP recently started supporting Debian, but only at version 5 and up. I tried to install Debian 4r8 on a DL360 g6 and none of the dvd or nic drivers are available. Has anyone had any luck with this?

  2. #2
    Just Joined!
    Join Date
    Aug 2005
    Location
    Houston, Texas.
    Posts
    57
    Pray tell, why are you using Debian 4 when 5 is available? Even better, use the next to be release, Squeeze.

    I know this doesn't help at all but move up to a newer version. You'll be happer. Promise.

  3. #3
    Just Joined!
    Join Date
    Sep 2009
    Posts
    8
    Believe me, if I had a say, I would toss Etch in a second. I have been learning Linux since last August and when my company told me they wanted me to learn Debian, I figured,"they must be using the latest version right?" Of course not. I am in the middle of planning a disaster recovery test for our production servers and after several months of building a very nice PXE auto install program to deploy any server in our inventory, I get handed a DL380 G6 and the damn thing won't get past the NIC detection. I had to throw an old nic into the box in order to complete the build. Of course I can't leave it like that. I at least want to get the damn drivers to install post build and I can't even alien the damn rpms from redhat. I'm about to throw in the towel. Any help would be greatly appreciated.

  4. #4
    Just Joined!
    Join Date
    Aug 2005
    Location
    Houston, Texas.
    Posts
    57
    Just did a Google on the DL380 G6. It's an HP server. HP has been very Linux friendly. I can't see it not accepting Debian 5.

    Surprise your bosses and take the bull by the horns - install Debian 5. You'd probably have the drivers needed for your project. Besides, if not, you can look for a way to install Debian 4 later on. Don't be bull headed. Try Debian Lenny (5).

  5. #5
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,755
    You have provided *no* relevant info.

    You need to look at the results of lspci, find the ethernet chip ID, and search Google and/or the manufacturer of the chip.

    My guess would be it's an Intel or Broadcom chip - both of which are well-supported and typically have very good install directions.

    Code:
    lspci -v | grep -i ethernet
    06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

  6. #6
    Just Joined!
    Join Date
    Sep 2009
    Posts
    8
    Well, just a follow up to this thread, I know debian 5 works. The card is a broadcom nextreme II x not a nextreme II which is common. The reason for the Debian 4 push was because this is a disaster recovery test. That means you have to reproduce the equipment that you have in production exactly as they are. If you don't reproduce the production machines exactly as they are, the test is a failure. We already canceled the upcoming DR test because we can't meet the deadline. I've given up attempting to install Debian 4 because there are just too many unsupported components on the DL360 G6 right now. I still would love to get it up and running but I'm forced to go the Debian 5 route for the time being. The only solution at this point is to slowly rebuild and test all the production servers with Debian 5 and replace the active systems. Then we can reschedule the test.
    if anyone has functional driver modules for the HP NC382i (Broadcom Nextreme IIx) for debian 4 I would be extremely appreciative. Of course that's only scratching the surface. Who knows what else won't work on that machine once I do get the NICs working.

  7. #7
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,755
    So let me see...

    A) You still haven't looked at lspci to identify the chipset.
    B) If you have to install a driver, they are "unsupported components?" So Windows 2003 has a lot of unsupported components out there - I have to install drivers far more often in Windows than "other" OS'es.
    C) You're going to reinstall all of the "production" systems because you can't install a NIC driver successfully on a DR test machine?

    Google: NC382i chipset

    Code:
    14E4.1639: Broadcom NetXtreme II Gigabit Ethernet BCM5709C
    	103C.7055: HP NC382i DualPort Multifunction Gigabit Server Adapter
    	103C.7059: HP NC382T PCIe DualPort Multifunction Gigabit Server Adapter
    So the chip is a Broadcom 5709. Visit Broadcom's site.

    Download the Linux driver. Unzip it. Driver is in two formats - RPM and .tgz source. Since this is Debian, review the INSTALL directions for the .tgz. And the directions say the standard "make, make install" and that's it.

    * Common sense items. From the INSTALL, I can see that this is the bnx2.ko module. The directions recommend ensuring that the cnic or any older bnx2 modules are not loaded. The files can be renamed to ensure they're not loaded. Compiling the driver will require some standard tools and the kernel header files. They can be installed with:

    Code:
    apt-get install build-essential
    apt-get install linux-headers-`uname -r`

  8. #8
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,755
    Just out of curiosity (and because I use Debian so often), I checked the modinfo for the "stock" Debian 4 R3 bnx2.ko module:

    Code:
    modinfo bnx2
    filename:       /lib/modules/2.6.18-6-686/kernel/drivers/net/bnx2.ko
    author:         Michael Chan <mchan@broadcom.com>
    description:    Broadcom NetXtreme II BCM5706/5708 Driver
    license:        GPL
    version:        1.4.44
    vermagic:       2.6.18-6-686 SMP mod_unload 686 REGPARM gcc-4.1
    depends:        
    alias:          pci:v000014E4d0000164Asv0000103Csd00003101bc*sc*i*
    alias:          pci:v000014E4d0000164Asv0000103Csd00003106bc*sc*i*
    alias:          pci:v000014E4d0000164Asv*sd*bc*sc*i*
    alias:          pci:v000014E4d0000164Csv*sd*bc*sc*i*
    alias:          pci:v000014E4d000016AAsv0000103Csd00003102bc*sc*i*
    alias:          pci:v000014E4d000016AAsv*sd*bc*sc*i*
    alias:          pci:v000014E4d000016ACsv*sd*bc*sc*i*
    srcversion:     2AE4E6CC6B4C08FD7809E3A
    parm:           disable_msi:Disable Message Signaled Interrupt (MSI) (int)
    I then grabbed the latest download from Broadcom and compiled it:

    Code:
    filename:       /lib/modules/2.6.18-6-686/kernel/drivers/net/bnx2.ko
    author:         Michael Chan <mchan@broadcom.com>
    description:    Broadcom NetXtreme II BCM5706/5708/5709/5716 Driver
    license:        GPL
    version:        2.0.8e
    vermagic:       2.6.18-6-686 SMP mod_unload 686 REGPARM gcc-4.1
    depends:        
    alias:          pci:v000014E4d0000164Asv0000103Csd00003101bc*sc*i*
    alias:          pci:v000014E4d0000164Asv0000103Csd00003106bc*sc*i*
    alias:          pci:v000014E4d0000164Asv*sd*bc*sc*i*
    alias:          pci:v000014E4d0000164Csv*sd*bc*sc*i*
    alias:          pci:v000014E4d000016AAsv0000103Csd00003102bc*sc*i*
    alias:          pci:v000014E4d000016AAsv*sd*bc*sc*i*
    alias:          pci:v000014E4d000016ACsv*sd*bc*sc*i*
    alias:          pci:v000014E4d00001639sv*sd*bc*sc*i*
    alias:          pci:v000014E4d0000163Asv*sd*bc*sc*i*
    alias:          pci:v000014E4d0000163Bsv*sd*bc*sc*i*
    alias:          pci:v000014E4d0000163Csv*sd*bc*sc*i*
    srcversion:     A8E4A40F80F0AB491150CB2
    parm:           stop_on_tx_timeout:For debugging purposes, prevent a chip  reset when a tx timeout occurs (int)
    parm:           disable_msi:Disable Message Signaled Interrupt (MSI) (int)
    I have attached the bnx2.ko and cnic.ko modules (the cnic.ko was just compiled with it, I don't think it's actually needed.)

    This was compiled against the latest kernel I could get via apt-get upgrade:

    Code:
    uname -a
    Linux XXXX 2.6.18-6-686 #1 SMP Fri Feb 19 23:40:03 UTC 2010 i686 GNU/Linux
    Attached Files Attached Files

  9. #9
    Just Joined!
    Join Date
    Sep 2009
    Posts
    8
    thank you HROAdmin26!
    That worked beautifully. Now if I could only figure out how to include that in an initrd.gz file so I can run the build from PXE or USB.

    I appreciate all your help. You sure got me out of a jam.

  10. #10
    Just Joined!
    Join Date
    Sep 2009
    Posts
    8
    Hey HROAdmin26,

    I know how to repack an initrd.gz file to slipstream preseed files into it, but would you happen to know what specific file or files that Debian is looking for and where to place them in the initrd.gz file in order for the install to detect and use the nic cards?

    Thanks again for your help

    I thought I was doing pretty good working with Debian until I ran into this. It sure is nice to talk to someone who know what they're doing on this platform.

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •