installing fedora on HEWLETT PACKARD pavilion 500

[Angelo Moreschini]

Hi Chris,

I followed your suggestion:
I tried efibootmgr -v
and  I got this output:

*"efibootmgr: EFI variables are not supported on this system."*

thinking that the installation is not good, I found this link:

http://unix.stackexchange.com/questions/91620/arch-linux-grub-install-efi-variables-are-not-supported-on-this-system

where is wrote :  The problem was simply that the efivars kernel module was
not loaded.


I have not so much experience so I would ask you what to do..

perhaps it is enough to install the efivars kernel module. ?

Thank you

On Fri, Mar 13, 2015 at 3:43 PM, Chris Murphy <lists at colorremedies.com>
wrote:

> On Fri, Mar 13, 2015 at 11:56 AM, Angelo Moreschini
> <mrangelo.fedora at gmail.com> wrote:
> > I already had some problem to install fedora on HP pavilion 500, but at
> last
> > I was able to finish the installation.
> >
> > I got the message: "installation complete" and so I did the shutdown.
> >
> > The computer closed regular,
> > (the system is going down for power out at ...)
> > but when I try to open it again, I find this message on the screen:
> > -------------------------
> > boot device not found
> >
> > please install an operating system on your hard disk
> >
> > Hard DISK - (3F0)
> > F2 - System Diagnostics
> >
> > for more information visit the site
> > http://h18021.www1.hp.com/helpandsupport/hp-self-support.html
> > ----------------------------
> >
> > The site don't explain nothing about a problem connected with linux
> >
> > and after running diagnostic I get the message :
> > ERROR: no boot disk has been detected
>
> Curious. This is the 3rd such report in just a couple months,
> including myself. In my case it was intermittent though and Dell
> support concluded either logic board or SSD flakiness; and also mine
> was a dual boot scenario and sometimes happened even with Windows only
> installed on the system (and all Fedora NVRAM entries cleared).
>
> The fact that your on-board diagnostic doesn't see a drive suggests a
> hardware problem. But I wonder if there's something (efbootmgr +
> kernel tickling the firmware's NVRAM?) about Fedora that's instigating
> this? Or if it's just coincidence. I guess the sample size isn't big
> enough to know.
>
> What happens if you boot from install media, and capture both
> dmesg
> efiboomgr -v
> ?
>
> In my case, dmesg clearly showed the lack of proper ACPI
> initialization, no drive was found at all.
>
> --
> Chris Murphy
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20150314/54f1f3d6/attachment.html>