Re: [Bugme-new] [Bug 11734] New: Ramdonly linux don't boot, it hangs at the very first stage of booting with some error related with uvesafb
From: Diego Ocampo <hidden>
Date: 2008-10-10 21:07:47
You mean the firmware of the graphic card? In any case windows vista boots always without any problem... and also ubuntu hardy (kernel 2.6.24) boot always without problems On Fri, Oct 10, 2008 at 10:50 PM, Andrew Morton [off-list ref]wrote:
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Fri, 10 Oct 2008 13:37:41 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:quoted
http://bugzilla.kernel.org/show_bug.cgi?id=11734 Summary: Ramdonly linux don't boot, it hangs at the very first stage of booting with some error related with uvesafb Product: Drivers Version: 2.5 KernelVersion: 2.6.27-6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(Other) AssignedTo: drivers_video-other@kernel-bugs.osdl.org ReportedBy: diegoocampo8@gmail.com Latest working kernel version: 2.6.24-xx Earliest failing kernel version: ---- Distribution: Ubuntu Intrepid Ibex Hardware Environment: Samsung R70 / A009 Software Environment: Ubuntu Intrepid Ibex Beta. Problem Description: First of all: I am not a linux expert so pleasedon't askquoted
me too much technical questions about the problem, but i will try to helpasquoted
much as i can... I am not sure if it is related with Ubuntu or with the kernel but theproblemsquoted
take place in the very first stage of booting (maybe with the loading ofthequoted
kernel??) and I get the following error messages: "606627 uvesafb: failed to execute /sbin/v86d" "606719 uvesafb: make sure that the v86d helper is installed andexecutable"quoted
"606814 uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)" "606905 uvesafb: vbe_init() failed with -22 Then the loading goes on a little bit until reaching the message: "Loading hardware drivers ....... " and the laptop freezers at thispoint.quoted
Like i said this is a ramdonly problem,if i restart the computer mostprobablyquoted
ubuntu starts, but i think it is very annoying anyway!.hm. firmware loader problems, perhaps?