Adam Williamson wrote:
> In this case it worked out, and in fact was correct
as the issue turns
> out to be in some ways Fedora-specific, but
generally speaking I
> usually recommend filing graphics issues upstream
these days, as there
> are a lot more devs following upstream trackers than
RHB
Chris Murphy wrote:
> Have you had a chance to file a bug about this yet?
I did, immediately. I should have posted the link here,
so others concerned could follow.
https://bugzilla.redhat.com/show_bug.cgi?id=1334075
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.
Chris Murphy wrote:
> Boot the non-PAE kernel, then dnf remove the PAE
kernel packages,
> there will be three, kernel, kernel-core, kernel-
modules. At least in
> my case with Cinnamon on i686, I got both PAE and
non-PAE and dnf is
> just keeping both up to date.
Thanks Chris. I was hoping I co
P. Gueckel wrote:
> Felix Miata wrote:
>
>> There probably isn't a motherboard in existence
with
> a BIOS that old that
>> does not require a genuine DOS boot to update its
> BIOS. That should be no
>> impediment to any Linux user, as DOS boot media to
&
Felix Miata wrote:
> There probably isn't a motherboard in existence with
a BIOS that old that
> does not require a genuine DOS boot to update its
BIOS. That should be no
> impediment to any Linux user, as DOS boot media to
facilitate flashing are
> readily available. e.g. from
http://www.boot
On my laptop, I notice that the kernel that got
installed from the Workstation live disc is kernel. I
did an update and now I see that the very same
numbered kernel, but the pae version, has now been
installed.
I just checked and, unlike previous releases, F24 ha
no /etc/sysconfig/kernel file
Chris Murphy wrote:
> You might check if
> the firmware is current.
The firmware is ancient. I haven't had windows (XP)
since about 2000.
I haven't ever managed to figure out how to do BIOS
updates in Linux. Is it possible?
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http
Chris Murphy wrote:
> On Sat, May 7, 2016 at 7:48 PM, P. Gueckel
wrote:
>> Mike Chambers wrote:
>>
>>> Maybe you need to boot up into rescue mode and
>> reinstall grub? I've had
>>> to do that a few times during fresh installs
lately.
>>
&
Mike Chambers wrote:
> Maybe you need to boot up into rescue mode and
reinstall grub? I've had
> to do that a few times during fresh installs lately.
That had already occurred to me. How do I select
rescue mode, when I cannot even get the grub menu? I
the tried, from grub rescue, typing set r
I installed the latest version, which is pretty likely
what will become F24ß.
On my desktop computer, everything appears to have
gone smoothly, although I have had little time to
experiment. Getting back into my old system, F23, gave
me some problems, since osprober (?) generated menu
items f
Rex already fixed it, he says :-)
Maybe I'll remember some of this next time ;-)
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
I forgot to add the output of:
rpm -q --scripts appstream
postinstall program: /sbin/ldconfig
postuninstall program: /sbin/ldconfig
posttrans scriptlet (using /bin/sh):
/usr/bin/appstreamcli refresh-index --force >&
/dev/null ||:
I'm afraid that doesn't tell me a whole lot ;-)
I guess it's sup
Adam Williamson wrote:
> On Fri, 2015-10-02 at 20:42 -0600, P. Gueckel
wrote:
>> Adam Williamson wrote:
>>
>> > In practice, the best thing to do about scriptlet
>> fails is to file a
>> > bug any time you see one, and try to figure out
what
>> spe
Adam Williamson wrote:
> In practice, the best thing to do about scriptlet
fails is to file a
> bug any time you see one, and try to figure out what
specifically the
> scriptlet that failed *was*, and what it was meant
to do. If it
> actually needed to do something in your particular
context,
I read somewhere that, when a scriptlet fails during
upgrade, one need only turn off selinux, run the
upgrade, and then turn selinux back on.
Fine, but I won't know in advance that a scriptlet is
going to fail and I'm not disabling selinux every time
I upgrade some packages, just in case there
I messed something up by manually installing the
kernel-PAE package (my kernel supports pae and nx).
Then, I read that PAE is only useful with more than
4Gb of memory, which my laptop does not have, so I
went back to the default kernel. This is easier,
anyway, as it requires no extra work for
16 matches
Mail list logo
