Printable View
Quote:
Originally Posted by si-skyline
Well ive searched around and this is what happens but still no fix:
Ubuntu goes to boot screen and does the first progress bar. Then it loads like 15% on the second one and stops. The lights on the keyboard for the capslock and scroll lock blink. On the Ubuntu forums it said this is an indicator for a kernal panic. Anyone know what the cause is?
Oh and dual boot.
I'm going to go take pictures of whats happening.
Yep big hole in all debian based Linux packages (including Ubuntu) - basically the number of encryption keys that can be generated was reduced from 2^128 to 2^16 or something of that order by a programming glitch which means they are easily crackable by brute force attacks. THERE ARE EVEN LISTS OF THE REDUCED KEYS AVAILABLE FOR DOWNLOAD.
http://wiki.debian.org/SSLkeys
On the main issue, sorry, but IMHO Linux is not ready for the desktop for the average user - and I am writing this on a laptop running Ubuntu.
YES Hardy heron gets your wireless working (as long as you have a wired connection to download the firmware) YES it installs the GPU drivers. Yes it works very nicely out of the box ..... until ....
... you try and do something that it doesn't do easily out of the box yet .... eg installing a TV card. It was a bitch to get my TV card working and I am still not there with the remote control. It does volume up and down, slow playback, speed playback, but I have to get up and change channel manually. I'm a computer expert compared to 99.9% of the population. Until installing my TV card and getting it working is not a total and utter frikkin bitch for me, sorry but the baby is not really walking properly YET.
I would propose that in a year to two years Linux will be a real desktop possibility for the average user. Moreover, wiithin 3 - 4 years Microsoft and Windows will be playing catch-up very fast indeed because the improvements over the last year to eighteen months are impressive. Linux will be the standard personal OS in 5 years time, not anything Micro$oft produce.
Crazy
Quote:
Originally Posted by noopypoop
I suspect you could just try reinstalling Ubuntu which might fix it (has for some folk). It sounds like its crunching up against a hardware/driver issue to me. You can also change boot instructions and there is a safe graphics mode for debugging. Instructions here.Quote:
Causes of kernel panics
General causes of kernel panics
Kernel panics are often caused by one or more of the following issues.
- Defective or incompatible RAM are the most frequent causes of kernel panics. Despite being a highly-reliable product, RAM can fail. Modern operating systems, like Mac OS X, are sensitive to RAM. Purchase additional RAM from either Apple or third parties who guarantee their RAM is compatible with Mac OS X, offer a liberal exchange policy, and provide a lifetime warranty should the RAM become defective or a later version of Mac OS X introduce incompatibilities.
- Incompatible, obsolete, or corrupted kernel extensions. If a third-party kernel extension or one of its dependencies is incompatible or obsolete with respect to the version of Mac OS X you are using, kernel panics may occur when the kernel executes such extensions. Likewise, if a kernel extension or one of its dependencies is corrupted, such as the result of hard disk corruption, kernel panics are likely to occur when the kernel attempts to load or execute such.
- Incompatible, obsolete, or corrupted drivers. Similar to kernel extensions, drivers for third-party hardware which are incompatible with the version of Mac OS X you are using, or which have become corrupted, will cause in kernel panics.
- Hard disk corruption, including bad sectors, directory corruption, and other hard-disk ills.
- Incorrect permissions on System-related files or folders.
- Insufficient RAM and available hard disk space.
- Improperly installed hardware or software.
- Defective hardware or software. Hardware failures, including a defective CPU, or programming errors can result in kernel panics.
- Incompatible hardware. While rare, this is generally the result of a third-party hardware vendor’s product failing to properly respond to the kernel or a kernel extension in an expected way.
Crazy
Well here's the error I get
Code:dmi_save_oem_strings_devices: out of memory
http://lkml.org/lkml/2007/12/18/361 and this is the fix. But how do I apply the fix?
Before we go there:Quote:
Originally Posted by noopypoop
Is yours a HP Desktop? There are other reasons for getting this error.Quote:
People with HP Desktops (including me) encounter couple of DMI errors
during boot - dmi_save_oem_strings_devices: out of memory and dmi_string: out of
memory.[FONT=verdana,geneva,lucida,'lucida grande',arial,helvetica,sans-serif]
Crazy
[/FONT]</pre>
Quote:
Originally Posted by Crazy Buddhist
Yea ='(
HP FTL
Thanks very much for all the info when I finish my present case build/mod I will give Ubuntu a go again, thanks again. :)Quote:
Originally Posted by simon275
This issue has been dealt with, on one of the recent updates after all the updates install a dialog box comes up alerting the user of the issue and then allows the user to generate a new encryption key after the issue has been resolved. Personally I recall flaws this great coming from M$ as well.Quote:
Originally Posted by Crazy Buddhist
Indeed ... Windows Meta File anyone?Quote:
Originally Posted by chaksq
... Some old keys generated on debian run servers are still crackable I understand but could be wrong though yes I understand the hole has been patched.
CB
So can anyone tell me how to apply that fix so I can boot into ubuntu?