tg3: doesn't recognize the network device on Fujitsu Esprimo E5915

Need to backport this patch. May be a good idea to just backport tg3 from latest kernel, since there's ~4 other chipsets added since 2.6.15.

commit af36e6b6d7f4ad7a5ccfd14dfa71ec941255f93d
Author: Michael Chan <email address hidden>
Date: Thu Mar 23 01:28:06 2006 -0800

    [TG3]: Add 5755 support

    Add support for new chip 5755 which is very similar to 5787.

    Signed-off-by: Michael Chan <email address hidden>
    Signed-off-by: David S. Miller <email address hidden>

That sounds great, I'll look forward to it.

Have taken the ids from patch and have it my git tree.

will this be merged to ubuntu-dapper.git -tree before next release? Just pulled the current version and it doesn't seem to have this in yet.

a colleague tested my custom-built d-i (with kernel 2.6.15-50.61) and it got to the phase where it was trying to fetch udeb's from the network. So, while I haven't personally verified this, it seems that the backport works!

Seems that this has already been backported successfully in a test kernel, so it would make a good target for the dapper point release.

The dapper-proposed approach with ABI 50 never really took off, readjusting tags and status for standard SRU workflow.

linux-source-2.6.15 (2.6.15-51.63) dapper-proposed; urgency=low

  * Fix kernel-versions for ABI bump
  * Fix for kernel crash on lvremove
    - LP: #103729
  * e1000: Disable MSI by default. Allow it to be enabled with module param.
    Some chip implementations seem to not work well with MSI.
    - LP: #56885
  * tg3: Backport from 2.6.16.y
    - LP: #72696
  * Add r1000 to nic-modules
    - LP: #81782
  * Add bnx2 to nic-modules
    - LP: #73647
  * usb-serial: Fix oops with pilot-link
    - LP: #39518
  * megaraid: Move AMI/Megaraid3 IDs from megaraid_mbox.ko to megaraid.ko
    - LP: #57233

 -- Ben Collins <email address hidden> Tue, 23 Oct 2007 16:57:09 -0400

Please test and give feedback here.

  * tg3: Backport from 2.6.16.y
    - LP: #72696

This commit e69ba3b0afb86cc326f26ef5182e3fac6b346451 actually removes the 5575 support that was added in commit c91d48dd784f9f142bef5a84a66df618c4a64152 and would fix LP #72696.

Could not be verified, and Adrian's comment seems to indicate that this needs another patch.

Now there's a new LTS version which does support these devices.. should this bug be marked as wontfix?

let's not pretend this will get in dapper.