Menu

HP 6730B Laptop and BCM5787M

Anonymous
2009-12-12
2013-04-05
  • Anonymous

    Anonymous - 2009-12-12

    I'm having trouble with a HP6730B laptop.  It has a BCM5787M ethernet adapter.  My personal laptop (which I actually have the DRBL server on) has the same card.  I am running clonezilla on a debian unstable drbl server.  The card uses the tg3 driver.  I have run live linux CDs on the client machine and it indeed works with the tg3 driver.

    So, I think that fact is established.  When I boot the client, I get:
    The detected modules for hardware: Not any known PCI device is found!!!.  Try to load them….
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    The driver of the network card is NOt found!
    is this kernel 2.6.31-1-686 too old so it does not support this network card?
    Without network card driver, we can NOT go on!
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Now enter shell to debug. . .

    So for some reason the driver is not found.  The driver works on MY laptop (the DRBL server, in this case), and since the image comes from my  server shouldn't it work also?

    I've read emails online suggesting to add the entry into the modules.pcimap.  That file does not exist under my system.  Isn't that deprecated now?  So I think modules.alias has replaced modules.pcimap?  I added the device ID (gotten from lspci-static) 14e4:1693 into what I believe are the appropriate places in modules.alias file.  This has had no effect.

    I am running kernel 2.6.31-1-686  I set my clients to use same kernel and architecture as DRBL server when I ran drbl setup.

    Can anyone tell me what would cause this.  It is a real pain.

    Thanks for your help

     
  • Steven Shiau

    Steven Shiau - 2009-12-14

    Could you please:

    (1). Run /opt/drbl/bin/drbl-bug-report and post the generated file.

    (2). Share the file /tftpboot/nbi_img/initrd-pxe.img on your DRBL server so we can diagnose it? You can put it somewhere in the http server where we can download it.

    Steven.

     
  • Anonymous

    Anonymous - 2009-12-14

    -----CUT BEGIN HERE-----------------------------
    Description of problem:

    How reproducible:

    Steps to Reproduce:

    Actual results:

    Expected results:

    Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!):

    OS version: Debian Testing-Unstable
    Server arch: i686
    Server CPU:  Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
    Server memory size: 2066200 kB
    Server Kernel version: 2.6.31-1-686
    Installed DRBL-related packages:  drbl-1.9.5-27 clonezilla-2.3.4-34 mkswap-uuid-0.1.1-1 drbl-partimage-0.6.8-1drbl drbl-ntfsprogs-2.0.0-4 partclone-0.1.9-5 drbl-chntpw-0.0.20040818-7 drbl-lzop-1.02-0.8drbl pigz-2.1.5-1drbl pbzip2-1.0.5-1drbl mkpxeinitrd-net-1.3-14 udpcast-20091031-1drbl drbl-etherboot-5.4.3-2 gpxe-0.9.9-1drbl freedos-1.0-11drbl
    Client kernel version:
    Client kernel arch:
    NICs with private IP address in server: eth0 eth2
    Private IP address in server: 192.168.100.101 10.144.0.76
    Total client no: 5
    Client IP address: 192.168.100.200 192.168.100.201 192.168.100.202 192.168.100.203 192.168.100.204
    ===

    /tftpboot/nbi_img/initrd-pxe.img can be found at:

    http://mysite.verizon.net/rfluharty1974/initrd-pxe.img

    Thanks.

     
  • Anonymous

    Anonymous - 2009-12-14

    Sorry, I realize how ugly that debug came out.  You can see it easier at:

    http://mysite.verizon.net/rfluharty1974/DRBL-BUG-RPT-20091214-1301.txt

     
  • Anonymous

    Anonymous - 2009-12-14

    Okay, to give more information..

    After it drops me into a prompt, I can "modprobe tg3" then setup the network interface with "ifconfig eth0 192.168.?.?"   I can then ping my DRBL server.
    So It appears it's DEFINITELY not the driver or the card, but rather the driver is not loading itself.  The "not any known PCI device is found!!!" makes it sound like a PCI detection type problem.  Maybe that message is not accurately describing the problem?  I'm just an netadmin, not a developer.
    Thanks for help

     
  • Steven Shiau

    Steven Shiau - 2009-12-15

    So you are using the unstable DRBL on your Debian squeeze or sid? Actually it's not well tested (since squeeze/sid changes very often) so you might hit other problems :)

    Anyway, I guess the problem is that the system can not identify your card correctly while it is trying to load the kernel modules.

    If  you are sure the driver "tg3" is the one you want, you can use this command on DRBL server to force the PXE client's initrd to load module "tg3":

    /opt/drbl/sbin/mknbi-nic -modules "tg3"

    The initrd created by this command will load module tg3.

    Please let us know the results.

    Steven.

     
  • Anonymous

    Anonymous - 2009-12-15

    You are right.  I pretty much figured out it was a hardware detection problem.  I just didn't know how to specify a driver.  Your solution did work. 

    Thank you VERY much!

     
  • Steven Shiau

    Steven Shiau - 2009-12-17

    Cool! Thanks!
    I have put this on the FAQ/Q&A:

    http://drbl.sourceforge.net/faq/

    Steven.

     
  • Zach  Biles

    Zach Biles - 2010-02-10

    What if you do not know the module?  Is there a way to figure out which one you need?

     
  • Steven Shiau

    Steven Shiau - 2010-02-11

    It's possible you can try to use "lspci" then map the file /lib/modules/$KERNEL_VER/modules.pcimap.
    Or you can try to google that.

    Steven.

     
  • chuck

    chuck - 2010-05-09

    Steve, I think there is an error in your command listed here in Reply 6 and also in the DRBL FAQ. It should be: 

    /opt/drbl/sbin/mknic-nbi -modules "tg3"

    Thanks again for all the good work on DBRL and Clonezilla.

     
  • Steven Shiau

    Steven Shiau - 2010-05-10

    Thanks for pointing that out. I have fixed that in the FAQ.

    Steven.

     
  • Patrick

    Patrick - 2011-06-09

    I know this is quite some time after the last post but I found this faq because we recently were forced to move to the next latest Panasonic Toughbook in line.  Clonezilla worked fine with the T1 on the ethernet boot, but on the C1 when I prepared to make a new master I received the message stating that perhaps the kernel was too old to support it.  I pulled up the vend and dev ID for the new NIC and the old NIC.  Both vends are same (Intel 8086) but neither dev Id was listed in pcitable.  So I figured since the old one was a 1000 that I would use the command you listed above substituting "tg3" with "e1000".  Now when I boot from ethernet on the C1 it does not give me the error message, but it just sits at a portion of the screen with a blinking cursor directly beneath the line Manufacturer: ALPS.  I apologize but I am NOT very proficient with linux based operating systems and I actually inherited the Clonezilla server from a person that used to work here who was.  So any input you can provide would be great.  If anything I would like to know how to reverse what I had done by issuing /opt/drbl/sbin/mknic-nbi -module "e1000" as we still have the T1 Master Image on here that I will need.

    Thanks
    Patrick

     
  • Steven Shiau

    Steven Shiau - 2011-06-15

    If you mean Clonezilla SE, you can try this:
    http://clonezilla.org/use_clonezilla_live_in_drbl.php
    And use Clonezilla live 20110609-natty as client's OS when doing Clonezilla jobs.

    Steven.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.