[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2011-07-14 Thread Brad Figg
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu)

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-09-11 Thread marcobra (Marco Braida)
@Brad Figg can you copy and paste here the result of the lspci (lower of LSPCI) terminal command here... I use this network interface with karmic the updated alpha5 without any issue (not installed from alpha5 cd) Linux ubuntu 2.6.31-10-generic 32 bits Thank you -- 3Com Corporation 3c905C-TX/

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-09-11 Thread Brad Figg
I have this problem after installing Karmic Alpha 5. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid. https://bugs.launchpad.net/bugs/356148 You received this bug notification because you are a member

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-08-27 Thread marcobra (Marco Braida)
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Released => Incomplete -- 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-08-27 Thread marcobra (Marco Braida)
Description:Ubuntu karmic (development branch) Release:9.10 The 00:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 30) is working now with kernel: Linux ubuntu 2.6.31-7-generic #27-Ubuntu SMP Mon Aug 24 17:33:49 UTC 2009 i686 GNU/Linux Thank you -- 3Com Cor

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-08-11 Thread Leann Ogasawara
Thanks for the feedback marcobra. Let's see if Martyn will be able to test since it seems he had the same issue and hardware. @Martyn, can you comment if this issue remains with the latest Karmic 9.10 Alpha development release? Images are available at http://cdimage.ubuntu.com/releases/karmic/ .

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-07-22 Thread marcobra (Marco Braida)
I always upgrade my kernel from the standard Ubuntu repository kernel but now i'm on Karmik and i can only test the 3com nic on it BTW now i'm not using the 00:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 30) with karmik i still use: 00:07.0 Ethernet controller: R

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-05-25 Thread Leann Ogasawara
Hi marcobra, Can you comment which version of the kernel you had updated from where this wasn't an issue? It will help narrow down the scope of patches to examine which may have introduced this regression. I do see some much older bugs reported against other distros and upstream having a similar

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-04-29 Thread Martyn Young
I'm having the same issue. dmesg: [ 9542.571630] :04:00.0: 3Com PCI 3CCFE575CT Tornado CardBus at c207a000. [ 9542.571646] 3c59x :04:00.0: setting latency timer to 64 [ 9542.686126] *** EEPROM MAC address is invalid. [ 9542.686139] 3c59x: vortex_probe1 fails. Returns -22 [ 9542.

[Bug 356148] Re: 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

2009-04-10 Thread Mathieu Marquer
Confirming as a user on ubuntu-fr.org forum encounters the same problem. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid. https://bugs.launchpad.net/bugs/356148 You received this bug notification because you