On Sat 16 Mar 2013 at 12:08:19 +0100, Casper Langemeijer wrote: [Snip]
> From that moment on eth0 is not working anymore. I get these kernel > messages: > > [ 1796.583881] tg3 0000:01:00.0: eth0: transmit timed out, resetting A search with "tg3 transmit timed out resetting" turns up some possibilities for you to investigate. [Snip] > Then it loads that firmware blob onto the network card, breaking it. > > And now what? > > I have a bricked eth0. I really like to repair before the machine > goes into production. Suggestions anyone? You are suggesting the loading of firmware has permanently damaged the network card but I wonder whether this can be so. My understanding is similar to what is expressed in this post: http://lists.debian.org/debian-user/2013/01/msg00028.html >> 2) What happens with the firmware when card becomes operational? I >> mean by definition it should be written to device non-volatile >> memory(for example flash memory), but I doubt that this is the case >> for Wi-Fi adapters.. Or is it? > No. The image is simply loaded into the adapter's ram. After the > device loses power the memory evaporates. When power is applied again > the device is once again blank or back to the default power on state > and the firmware must be loaded again. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130316181950.GS32477@desktop
