I fully dont understand the approach that may be taken as workaround to
USFI Secure Boot for Fedora:
The last option wasn't hugely attractive, but is probably the least
worst. Microsoft will be offering signing services through their sysdev
It's not entirely free (there's a one-off $99 fee to gain access),
but it's cheaper than any realistic alternative would have been. It
with as wide a range of hardware as possible and it avoids Fedora
having any special privileges over other Linux distributions.
If there are better options then we haven't found them. So, in all
probability, this is the approach we'll take. Our first stage bootloader
will be signed with a Microsoft key.
will I need to pay $99 to use linux,etc. what about other distros?
I know will be speculating at this point but wondering what could be the
reprecussions if this method is taken?
From: users-bounces(a)lists.fedoraproject.org [mailto:email@example.com] On Behalf Of Javier Perez
Sent: Friday, June 01, 2012 9:54 AM
To: Community support for Fedora users
Subject: Re: Red Hat Will Pay Microsoft To Get Past UEFI Restrictions
Tommy, you are exactly right on all of your points.
The Fedora people say that they would rather not go back to the times of compatibility lists to find out what hardware worked with the system.
I'd rather go back to compatibility lists and give my gold to whichever hardware manufacturer caters to my needs than give MS the kind of veto power they would have with secure boot as currently defined.
Perhaps an other option: replacing the UEFI-BIOS by an opensource bios that doesn't hold those ridiculous restrictions?
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
I have a machine with two monitors, using Intel Q35
driver with DRI. Gnome 3
works in fallback mode still in FC17 - I was expecting that would not
happen. Did I hope for
Bill Murray ---- ATLAS
STFC RAL at: Bat 161 1-08, CERN,1211 Meyrin, Geneve 23, Switzerland
Tel:- CERN +41 22 7670631 or RAL +44 (0)1235 446256
First, preupgrade-cli does not work, stops in some .py stuff. Can't get
info, b'cause another comp. No problem, pure preupgrade went smoothly
trough, new 17 all ok, so far. When closing comp kernel panic, again
can't produce message here, but remember, that can't find shutdown.sh
script was one of messages... So, my lap lenovo t61 works, but shutdown
has problems... Doomed to be alive for ever? Heh... So have to wait
other comps upgrading, probably near to 18 rc2 or something. One
question, where you guys, who know something about code and so, have
hurry... If you do distro for people, make sure u understand, that
persons like me, 60 old want to use it. KISS, KISS, u make more crowns
just waiting, not with rush. World IS IS and IS, people aren't.
/* Horror, When There is no Electricity */
I've got a fresh, F17 install, running Gnome desktop. Unsurprisingly
gnome-shell crashed at some point. What is surprising though, is that
remote retrace server is no longer available for choosing in abrtd applet.
Has anything changed recently, or am I just missing some package that is
not in the default install?
I have an hp dv9000 laptop. With proprietary nvidia driver, it works correctly.
xdpyinfo says monitor is 371x232mm, which is correct.
using nouveau, xdpyinfo says it's 447x277mm.
Where do I report this bug?
Here is what I tried to workaround:
I made xorg.conf that contains only this:
# HorizSync source: edid, VertRefresh source: edid
HorizSync 30.0 - 75.0
DisplaySize 371 232
This seems to work. I'm hoping nouveau will use automatic settings for
everything else (AFAICT, it is).
Is this the easiest way to do the 1 thing I need done, which is:
DisplaySize 371 232
To understand what happened see my email regarding the JBoss failure. It all started there.
Basically because of that failure I tried to force the JBoss-as package install under f16 kernel boot 3/4 ways through the f17 install. After successfully installing all the rest of the packages using f17 installer process, the install failed due to the rpmdb changing underneath. That was me forcing the JBoss-as installation I guess. So after the installed exited. Reboot shows no beefy miracle in the grub list.
So now it's no longer the offending JBoss-as package it's more a how do I recover from this failure at this point. Or if I can't should I just install f17 from scratch and hope my /home backup will recover nicely into f17.