Comment 236 for bug 422536

I just ran into this bug which appears patched. However, it came up for me today 2010-01-25, and I thought this kind of problem auto-updated with the system package managers. I am running Ubuntu 9.10 Live. My systems including nine motherboards were attacked by a bios32/eeprom/LKM rootkit some time ago. I've only recently been able to somewhat bypass the original fully crippled state using recent Linux/Unix distros. This machine is based on a DFI Infinity socket 939 mb, AMD Opteron 170, MSI 6600GT graphics, 1GB Corsair 3200 2-3-3-6. The problems began when I first installed one of my legal OEM copies of Winders and used win up(&down)date. The bios was replaced/supplemented with the usual binary blobs created with Busybox and while trying to appear as unix, are basically embedded smbios with efi and monkeyboy fingerprints(aka ntfs) everywhere. Oh, it also has embedded a debian based kernel (I believe when I first installed openSUSE about a year ago) which has a dual root. Translated, my attempts at hard drive install always are fused into a crippled configuration with enough loops, devices, and processes to imitate HAL. The end result is basically always the same, no hardware control, and a preset network interface that appears to be part of some industry initiative in anticipation of passage of the new trade bill being fought by the EFF and others. I guess they're experimenting on people like me who have been reported by an m$ tech (falsely) as having commercially pirated a copy of WindersXP, Anyone want to tackle a core dump?? MC sorry if I've caused any problems posting this here, but I'm kind of desperate as I have a BS in Architecture, not Computer Science, and all I've written comes from what I've been able to teach myself the past year or so! Also, at 55 I'm not getting any younger and this is getting old!