Keyboard, mouse, and cd drive freezes completely (Happens randomly but inevitable)

[Christopher Denter]

Hi.
This is a Feisty, Gutsy, Hardy, Intrepid, and Jaunty bug.
The keyboard randomly stops working. (It freezes. I can't even toggle Num Lock)

It seems it does not depend on what i do, nor is it a matter of time. Sometimes it happens after an hour of use and sometimes it happens as soon as you log in (or you are not even able to log in!).
Last time it happened I clicked the evolution icon in the GNOME panel. I have to do one or two reboots to make everything work again. I already re-installed feisty-final and updated it. This does only happen on my desktop pc. Laptop works fine. (Thanks for that one!)

I did never have any similar issue in the past. I did not change any hardware components. It happens only in Feisty. Not in Breezy, Dapper or Edgy.

You see that this is quite annoying since all my work is to be lost as soon as this happens and i have to reboot.
Nevertheless I do want to use Feisty since it is such a great release.
Therefore I am eager to help you fixing this issue as best as I can.
So: If you need any further information or logs, just let me know and I will immediately add them to this bugreport.

regards

[Johnathon (kirrus)]

Hello, thanks for your bug report. Can you check in your /var/crash/ folder for a bug report, as well as checking in your system logs (System > Administration > System Logs) immediatly after you have recovered from a crash, to see if there is any references to the crash. If there is, can you attach the log file?

[Christopher Denter (dennda)]

Hello,
there is no file or directory in /var/crash.
"Unfortunately" I did not have another crash up to now.
I will be at home until Sunday evening so I cannot check my machine's state or logs.

I hope it is possible to figure the problem out without these logs.
If I find any bug-report occurence in the logs I will immediately attach it.

regards.

[Johnathon (kirrus)]

Hi,

Unless someone else has the same problem, we can't progress without something more to go on, I'm afraid. I'm hoping that the System Logs will show where the problem is, and once we know that we can start targeting that package for debugging programs. Still, no rush, work on it when you get round to it. I'll set the bug status to rejected if theres' not activity after a month, but we can always re-open it again.

Regards,

Johnathon

[Jorge García (jorgegarciar)]

Hi,

    I have exactly the same problem. I'm reviewing the logs in /var/log and I don't find any significant error. The mouse works but the keyboard is totally frozen. I'll try to find any aditional clue.
    Regards and thanks in advance for your help.

Jorge.

[Johnathon (kirrus)]

Try running "dmesg" in a terminal. Or better still, have a script on your desktop which runs the line "dmesg > dmesg.log" and then run that once the issue has showed itself (by double clicking on it.) then, reboot, and attach the dmesg.log file here. If you need me to write you a shell script to do it, just ask.

[Jorge García (jorgegarciar)]

I have just detected a little difference between the problem of the related bug and mine: My mouse works but I can't interact with any window. I think the difference comes from the fact that I have "Desktop Effects" on. So I will wait till the moment the problem happens again (it happens randomly and not very often) and send you dmesg.log just after the first reboot.
I'll switch the effects off in order to check if I the error is the same or not. If it is, I'll send you the result of the script you told me.
Thanks for your help.

[Christopher Denter (dennda)]

Hi,
again it happened. I do not see anything unnormal in dmesg.log that might be related to this issue.
I attach the complete output from dmesg.log after I ran "dmesg > dmesg.log" after reboot.

I hope you can figure it out.
Thanks in advance.

regards

[Johnathon (kirrus)]

Can you attach the "dmesg" file from your "/var/log/" dirrectory? Also, "messages" may be useful, whilst you're at it.

Thanks,

Johnathon

[Ali Najand (ali-najand)]

This is the log of the messages I get during the error. On my laptop the USB mouse stops working and the touchpad stops working after a few minutes too, or you cannot just select or right-click anything on the screen. On a random intervals, the keyboard stops working too. The log is attached for the reference.

[Johnathon (kirrus)]

Ok, that's a kernel problem. Dennda, do you see similar lines in your report? Also, what make are your laptops, please?

[Christopher Denter (dennda)]

Hi,
I do not have any problems with my laptop. It is a HP nx6125.

I attach the log file.

regards

[Ali Najand (ali-najand)]

My computer is a NEC Lavie G, however after a quick research at ubuntu forums I realized that many people have similar problems.
Well, I guess it is a bug with APIC (or the old 8259). I am going to boot with noapic option and see if it is because of that or not.

[kudiehl (klaus-diehl)]

I had exactly the same problems in the past with the 64bit versions of Dapper and Edgy. I am using an Athlon 64 3200+.
With still the same hardware and now Feisty 32bit, i have absolutly no problems with it!!
Could it be a problem of the 64bit Version in conection with some hardware?
regards
kudiehl

[Johnathon (kirrus)]

Do you still have this problem with the latest kernel version?

[Jorge García (jorgegarciar)]

Hi, I don't have the problem with the new version or at least by the moment. If it happens again, I'll tell you as fast as possible. Thanks.

[Johnathon (kirrus)]

OK, closing it. Thanks for the report...

[Jorge García (jorgegarciar)]

:( Unlikely, it has happened again. I was just listening to some music and browsing the network and sudenly the image on the screen got frozen and keyboard stopped responding (even Caps Lock and bloq num. lights). The mouse moves perfectly, but it doesn't do any thing on the screen . No answer to Ctrl+Atl+Del. When I press de poweoff button of my portable PC in order to do a "tidy" shutdown, I see that there are still activity with the hardisk (because of the LED lights), but the computer doesn't stop, so I have to keep the button pressed down until it stops.
I tried to unplug all USB staff conected, but no answer.
Nothing is written in system logs.

Thanks,

Jorge+

[Johnathon (kirrus)]

Can you replicate the problem?

Unless it is repeatable, we can't track down the cause of the problem.

[Johnathon (kirrus)]

Sorry, I should have asked you to check in /var/crash/ for a crash report about this...

Also, you may want to wait a couple of minutes after a freeze, and then reboot, in order to give the system time to write a crash report.

Re-opening ticket...

[Jorge García (jorgegarciar)]

The error happens randomly (or I've not been able to guess the reason or secuence of movements that let me there). The only common fact I've seen always is that Beryl or Compiz were working. Once the error happens again, I'll post the file /var/crash after a couple of minutes. Thanks in advance.

[Jorge García (jorgegarciar)]

Hi. It has happened again, and no crash report has been created in /var/crash. Any other idea? Thanks

[Johnathon (kirrus)]

Can you try attaching the files /var/log/dmesg, /var/log/daemon.log, /var/log/user.log and /var/log/kern.log to this report, straight after it has happened again? (If you are busy at the time, can you take a copy of the files, and then upload them when you get round to it?)

I'm hoping that something will be logged by the system as it fails.
Thanks, Johnathon

[Jorge García (jorgegarciar)]

Here they are (zipped). Thanks again

[Johnathon (kirrus)]

Just out of curiosity, can you list attach ifconfig.txt, made through the following command?
"ifconfig > ifconfig.txt"

I'm still reading through your logs, but there appeared to be an error message in your daemon.log that *may* cause you some other issues.

[Johnathon (kirrus)]

Also, if it's not too much trouble, can you translate these two messages into english for me?
Jun 20 23:30:25 portatil gconfd (jorge-5362): Se resolvió la dirección «xml:readonly:/var/lib/gconf/defaults» a una fuente de configuración de sólo lectura en la posición 4
Jun 20 23:30:34 portatil gconfd (jorge-5362): Se resolvió la dirección «xml:readwrite:/home/jorge/.gconf» a una fuente de configuración escribible en la posición 0

[Jorge García (jorgegarciar)]

Of course,
The Spanish on the log is not very good, so this is my best with English:
Jun 20 23:30:25 portatil gconfd (jorge-5362): The address «xml:readonly:/var/lib/gconf/defaults» was solved to a read only setup source at position 4
Jun 20 23:30:34 portatil gconfd (jorge-5362): The address «xml:readwrite:/home/jorge/.gconf» was solved to a writable setup source at position 0

In the attached file (ifconfig.txt) you'll see vmnet1 and 8 interfaces. This is due to the fact that I have just installed VMWare Server.

Moreover I don't stop searching on the Internet for the solution, but ...¡nothing!. I've just found more and more people with the same problem, but not solution.

Thanks again and again,

Jorge.

[Johnathon (kirrus)]

Do you have an active wireless network?

[Johnathon (kirrus)]

Reason for me asking, is that your logs & ifconfig indicate that you may be being affected by bug #78078, but I'm not sure if that is a completely separate issue to the one you are suffering from now.

[Jorge García (jorgegarciar)]

Yes, I do have an active wireless network working properly. I don't have a wired one.

[Conn (conrad-aerolente)]

Hello,
I have already the same problem.

(K)Ubuntu 6.10

My kernel:
Linux conrad-laptop 2.6.17-11-generic #2 SMP Fri May 18 23:39:08 UTC 2007 i686 GNU/Linux

My keyboard stops working randomly. A reset ist the only way to shut down the system. I have this problem, scince 6 to 8 weeks I think. I had never such an error before. There are different posts in several forums, which are also describing the same problem, but nowhere seems to be a solution.

The "dmesg" and "messages" file is attached in one *.txt file.
In couldn't find a file, which is named /var/crash.

I have the feeling, that it could be a problem with the KNetworkManager. The problem is more often, if connect the system to a WPA2 network. But it is only an impression.

[Johnathon (kirrus)]

Can you translate these messages into English for me please?
I keep meaning to learn German but haven't quite got round to it yet ;)

 Die Adresse »xml:readonly:/etc/gconf/gconf.xml.defaults« wurde an der Position 2 zu einer nur lesbaren Konfigurationsquelle aufgelöst
 Die Adresse »xml:readonly:/var/lib/gconf/debian.defaults« wurde an der Position 3 zu einer nur lesbaren Konfigurationsquelle aufgelöst
 Die Adresse »xml:readonly:/var/lib/gconf/defaults« wurde an der Position 4 zu einer nur lesbaren Konfigurationsquelle aufgelöst

[Conn (conrad-aerolente)]

Hi thank you for your answer.
I will try it, my English isn't the best.

the address »xml:readonly:/etc/gconf/gconf.xml.defaults« was decomposed to an only readable configuration source at position 2
the address »xml:readonly:/var/lib/gconf/debian.defaults« was decomposed to an only readable configuration source at position 3
the address »xml:readonly:/var/lib/gconf/defaults« was decomposed to an only readable configuration source at position 4

[Johnathon (kirrus)]

Ok, thanks.. thats just a standard message.

I must admit, I'm stumped. I don't believe that there is enough information here to progress this bug further, so I'm releasing the bug back into the general awaiting triage queue, so hopefully someone else will be able to help.

Sorry I couldn't be more use!

[Jorge García (jorgegarciar)]

Thanks anyway, Johnanthon ;). Good job

[Joe Daverin (joe-daverin)]

I have to throw my hat into this ring as well, as I have been having a similar problem.

I have Ubuntu Feisty installed on a Compaq Presario S6900NX Desktop, dual boot with Windows XP, and I get the keyboard freeze inevitably after running for a couple hours. The mouse will work and I can interact with windows etc. Copy/paste works so I've been able to leave windows open with commands and returns in them and copy/paste to run commands in a terminal when the keyboard is frozen, but haven't found anything useful yet. Right now I'm just saving very regularly and using Windows when I really need to stay up for a while, which seems really wierd to say.

Mouse interactions seems to work completely normally, but trying to send the computer to a clean shutdown hangs somewhere, requiring a manual power cycle.

I don't have logs to attach right now, but next time it happens I'll try to capture all the information mentioned in this discussion and post it, if I'm lucky both while the problem is manifesting and after restart.

[Fernando Muñoz (fmunozs)]

I'm experiencing the same behavior as described by Joe Daverin , I'm using a Wireless Connection, this problem didn't appear with my previous Ethernet connection. I'm guessing this bug could be related to several kernel modules problems. My usb wireless adaptor uses at76_usb module, lsusb identifies it as 'Bus 001 Device 002: ID 03eb:7603 Atmel Corp. at76c503a D-Link DWL-120 802.11b Adapter'

[Joe Daverin (joe-daverin)]

So the freeze-up just happened when I was trying to apt-get install some mysql/php related nonsense. Attached are the logs captured after re-booting. I didn't see anything particularly telling in them but maybe someone else would see something suspicious.

Thanks!
Joe D

[Fernando Muñoz (fmunozs)]

I can see some bluetooth module problems on Joe Daverin logs, by the way, when my keyboard freezes, if I unplug the usb wireless adapter, the keyboard works again, and I can reboot / shutdown normally, however if I reconnect the wireless adapter, it doesn't work normally, after a reboot, it works again.

[Johnathon (kirrus)]

Fernando: It sounds like your problem is something going wrong with the USB stuff in the kernel. I'd reccomend opening a new bug report about it.

Regards,

Johnathon

[Jorge García (jorgegarciar)]

I have discovered something interesting. If I remove the service "powernowd" from the services list, everthing works good. The problem is that I need powernow in order to control the speed of my processor (to not get my computer very hot and use scalable speeds for my intel chip).

I hope it helps

[Johnathon (kirrus)]

Definitely still a problem.

[stephen84s (stephen84s)]

Same situation with me here as with Killeroid.
I have disabled "powerond" and ever since then no keyboard freezes.

I use Gnome and I almost never hit the "Window + B" key combination, even nothing much happened even when I tried it.

I will re-enable my powerond and give my feed back soon.

[stephen84s (stephen84s)]

Sorry for the typo its not "powerond" its "powernowd"

[Ed (edyesed)]

i updated to hardy.. two days without a freeze. I couldn't take my work machine freezing up anymore.

I only have the one 64bit machine... if I end up with another one, I'll revisit this bug..

However, I am 99.99% certain that in my situation powernowd was not the offender.

[stephen84s (stephen84s)]

I restarted my powernowd service as I had told earlier . . . . . Two days and no keyboard freezes as yet.
So I am completely blank as to what is happening on this machine ......!!!!!

[Killeroid (killeroid)]

I uninstalled powernowd and I keep getting the keyboard freezes. Not as frequently as when powernowd was installed though.

[stephen84s (stephen84s)]

I actually had never uninstalled powernowd just switched it of from the services menu, and the keyboard freezes stopped, However now its already been 3 days and no freezes as yet, earlier I used to have at least 3-4 keyboard freezes a day !!!

[stephen84s (stephen84s)]

My Keyboard freezes are back now, even though I dint do anything with the system !!
In fact I noticed an important feature of the keyboard freezes, if you have a key pressed when the dreaded freeze strikes, . . . the key remains pressed for the system(even after you have physically released the key on the keyboard ) !!!!

[Killeroid (killeroid)]

@stephen84s
Yeah, as I said earlier, the keyboard freezes returned after I uninstalled powernowd. The freezes are not as frequent though. And yes, if the keyboard freezes whilst you have a key pressed. the OS assumes the key is still pressed even after you take your hand of the key. (made me wreck my laptop keyboard since i was thinking the key had gotten stuck and so I to reseat the key and unfortunately broke something)

[GG (giorgio-gilestro)]

Very same thing here, using Hardy on a dell optiplex desktop. The thing is really annoying. It happens only after long sleep times: usually I come back in the morning and find my pc responsive to everything but the keyboard. If I try restart sometimes it hangs and all I am left to do is a cold poweroff. Other times it starts the restart process but then it hangs with a segfault: no trace of it in the logs. Shutdown usually works ok.

my kernel is 2.6.24-15-generic but this thing was present also with the older kernels.

Glad I finally found this thread after days of research. My guess is that the fact that no specific error message is given makes difficult to people even complaint about it so this bug seems relatively infrequent but it might well be a common one.

[GG (giorgio-gilestro)]

FYI, my bug wasn't related to powernowd. removing powernowd didn't help.

[misi (misi-aaaa)]

I have the same problem.

at first glance I was convinced that it has either to do with Xwindow or maybe, probably, who knows, can happen :) with the gpl breakers NVIDIA driver...

But I eliminated the first one as if log in remotely I cannot kill Kdm, xorg etc, so it is clear that there is some bug in the kernel.

what I propose is to kill linux (yes the project) and port everything to mikrokernel based solution and terrorize NVIDIA to release graphic card bulshit.

In that case one we will have a stable FREE DESKTOP :)

why is maKintoSSHH stable... because they use mikrokernel. And all the idiots do not have access to restricted OS spaces. But in that case lot of people would not be busy writing so much nonsense about nonsense bugs...

I will try to remove the NVIDIA driver... does any of you have this bug in the context of NVIDIA driver loaded??

If not nvidida is the problem, something is for sure messing up the kernel, as for sure not the KB driver that is probably 3 lines of code :)

good luck

[Killeroid (killeroid)]

Has nothing to do with nvidia. I don't have a nvidia card(never had one) and I use to experience this problem. After upgrading to hardy, i kept expereincing the same problem. Soon afterwards it disappeared. The problem seems fixed on my laptop. Personally, I think it has something to do with heat. I beleive when the internal heat gets high, some pcs/laptop shut down some components.

[misi (misi-aaaa)]

nvidida was o presumption (you always think about the bad guy :). Definitively the kernel behaves very bad in this situation. Anything happens the system did not crash, just the KERNEL gets crazy!! I will try to activate some trace in the kernel to see waTZ happennin'.

but let's see if it is related to some processor type I have a Intel(R) Pentium(R) D CPU 3.40GHz (without virtualization feature)

[misi (misi-aaaa)]

I upgraded to Ubuntu 8, and problem still occours.

[Alistair Wibberley (alistair-wibberley)]

I'm getting this bug using the amd64 version of 8.04. The problem is erratic, but seems to occur every one to two hours. Since it's pretty frequent if anyone wants I can probably get some logs, etc on what's failing.

I'm using:

Ubuntu version: 8.04
Kernel: 2.6.24-19-generic
Proc: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Wireless: RT61 802.11g PCI (using XP 64-bit driver and ndiswrapper, due to a nasty bug in the standard driver that causes kernel panics)
Video: Radeon HD 3870 (using the ati proprietary drivers)

I have just disabled powernow to see if that fixes anything, and will update with the results.

[hansel (h-p-elbers)]

Same problem here (kleyboard freeze once in a while) - both keyboards (internal and external) frozen

- Ubuntu 8.04.1, kernel 2.6.24-19-generic
- laptop lenovo T61
- CPU0: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz stepping 0b

The problem seems kdm or X11 or video driver related: after a killall kdm (via ssh) the keyboard works for a while. Startx works after that... keyboard froze again after 10 min... rebooting now...

Happy hunting, Hans.

[misi (misi-aaaa)]

switched window manager from enlightment to dark ages xfce :) and the problem does not occur anymore.. for centuries already

[TechShep (tech-shep)]

I've been having this problem for a while also. Has anyone else been messing with the compositing manager with metacity? I had it on, then after I turned it off, I began having the problems. I just turned it back on (took 3 tries logging on to get it working) and so far, no crashes. I will post in a few days if it remains fixed or not.

[michael (mike-rockatronic)]

It's powernowd.
Battling this too; Asus A8V amd64x2, random total lock-ups, no logs produced. Thought it might be nvidia and/or compiz. No. In the end I disabled powernowd and that solved problem. System stable for 3+ days now with everything possible running on it.

[TechShep (tech-shep)]

ok, pwernowd didn't make a difference for me, but I have found that opening a shell with ctrl + F1 (might have to do it twice), logging in, then exiting fixes the problem without loosing anything, although that doesn't stop it from happening again later.

[bh1nd3r (preet-bhinder)]

I don't think the problem is in powernowd because the bug still occurs for me in Jaunty and AFAIK there is no powernowd process running on Jaunty.

My laptop specs are:
Sony Vaio CR220E
Intel X3100
3gb RAM
Intel Core 2 duo

I have experienced this bug on Ubuntu versions from Dapper right up to Jaunty. I wish something could be done about this. Please let me know if you need further information.

[safiur (i-safiur)]

safiur
I updated my ubuntu 8.1 to kernel 2.6.27-14. However several times my mouse got freezed and needed restart.Also several times mouse gets uncontrolled and executes several programs, usually with icons at corner. My system details are: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz
Ubuntu 8.10 (intrepid)
Gnome: 2.24.1
kernel: 2.6.27-14 genericIntel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz
CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHzIntel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz
Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz

[christos pontikis (pontikis)]

Hello

I have the same problem to a fresh installed Jaunty with Gnome and 2.6.28-13-server kernel.
(Fujitsu Siemens Amilo 3650 - 4GB RAM - NVIDIA 9600m GT - Intel Audio HD - 2 SATA HDD 300 GB)
I have read all posts. Seems to be a strange bug...

[christos pontikis (pontikis)]

Hello again

in Jaunty there is not powernowd installed, so I set additional kernel parameters "noapic nolapic irqpoll ht=on" and I hope...!
I will report what will happen.

Regards

[christos pontikis (pontikis)]

Hello
unfortunately, keyboard got freezed again after two days.

[christos pontikis (pontikis)]

Plaease, FORGIVE my previous post: actually I had never set additional boot parameters "noapic nolapic irqpoll ht=on", as I did not modify correctly GRUB.

So, after apply these boot parameters (using GRUB correctly), I have serious problems with my multiprocessing laptop, so I gave up.

Now, I am testing computer behavior, disabling Advanced Power Management (suggesting that APM can cause the keyboard freeze problem). I 'll post my results.

[Trustmaster (trustmaster)]

I have encountered the same problem after I moved from Jaunty 32-bit to Jaunty 64-bit on a newly bought computer. I have tried different kernels, disabling ACPI/APIC, disabling cpufreq, different drivers for my ATI graphics card (including radeonhd and frglx), different keyboard/mouse drivers (evdev/kbd/mouse)... But it still kept freezing.

What has actually stopped my computer from freezing anymore is move from Gnome to XFCE. And as I can see no KDE/XFCE users posting in this thread I can suppose that this bug is Gnome-specific.

[bh1nd3r (preet-bhinder)]

I observed the same pattern. I only saw this bug with Gnome and moving
to XFCE made it disappear.

On Fri, Aug 28, 2009 at 6:30 AM, Trustmaster<email address hidden> wrote:
> I have encountered the same problem after I moved from Jaunty 32-bit to
> Jaunty 64-bit on a newly bought computer. I have tried different
> kernels, disabling ACPI/APIC, disabling cpufreq, different drivers for
> my ATI graphics card (including radeonhd and frglx), different
> keyboard/mouse drivers (evdev/kbd/mouse)... But it still kept freezing.
>
> What has actually stopped my computer from freezing anymore is move from
> Gnome to XFCE. And as I can see no KDE/XFCE users posting in this thread
> I can suppose that this bug is Gnome-specific.
>
> --
> Keyboard freezes completely and mouse interaction doesn't work for some tasks (Happens randomly but inevitable)
> https://bugs.launchpad.net/bugs/110394
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[piggy (konradbox)]

Could anyone check if this is related to https://bugs.launchpad.net/bugs/397004 ?

To check that, try pressing »LEFT«+»Ctrl« (in this sequence: press&hold »LEFT« then press »Ctrl«).

Thanks!

[chadnash (chad-nash)]

I have the same symptoms in Ubuntu 9.10 karmic k
that is: random key board hang with mouse still working and mouse actions gradually degrading.

[PCGuyIV (pcguyiv)]

Similar problem still around in 10.04 LTS Lucid.
My keyboard and/or mouse hang up at random intervals, and once they hang up, the only "cure" is to reboot the machine.
My system has no PS/2 connections, just USB. There are no "legacy" settings in the BIOS.
This is the only system on which I have this problem, but it is the one that most desperately needs to be running a version of Linux.
I've also tried other distributions, and the same problem occurs. It isn't unique to Ubuntu, or Debian-based distros.
Likewise, no useful information in the log files.

[Phillip Susi (psusi)]

The powernowd package is obsolete, please do not use it. CPU frequency scaling is now handled by the kernel, so if you still have issues on a modern release, file a bug against the linux package.

[Steve Langasek (vorlon)]

This is not an appropriate way to declare a package "obsolete". If you think a package should not be used, file a bug to get it removed from the archive and *then* invalidate the bugs.

[chadnash (chad-nash)]

I get the same behavior without powernowd on ubuntu 10.04 lts
So it might not be related to powernowd

[hahahafr (ullrich-999)]

what is your configuration (mainboard, socket, os, processor)

[chadnash (chad-nash)]

toshiba PORTEGE M600
socket??
10.04 LTS - the Lucid Lynx
core 2duo = 2xT7500 @2.2GHz
firmware
          description: BIOS
          vendor: TOSHIBA
          physical id: 0
          version: V2.50 (08/30/2007)

[hahahafr (ullrich-999)]

You might test it with 10.10 to see if something has changed.

[hahahafr (ullrich-999)]

Using the bootable live-cd may be preferable.

[Phillip Susi (psusi)]

This package is obsolete and has been removed from the archive. Closing associated bugs.