I use Fedora 21 ...
really I would upgrading to the last version ... but I fear to lost data
(this is not a simple work).
I'll do the upgrading (but not now).
Ok, thank you for your advice ! :-).
Only if you know it, and if you are interested to this subject, I say that
I investigate about the
On Mon, 2017-08-07 at 14:05 -0700, Jonathan Ryshpan wrote:
> [ ... ]
>
> The modesetting driver appears to be installed since it's part of the
> xorg-x11-server-Xorg package, which is installed on my system. But
> possibly not active. Where are instructions on how to find out whether
> it's active
On 08/07/2017 02:30 PM, Stephen Morris wrote:
> On 8/5/17 5:36 PM, Tim wrote:
>> Hi,
>>
>> Have we got to the stage where the default install options for Fedora
>> 26 work fine with a SSD, or should I be tweaking something?
>>
>> At the moment I've let it install with whatever parameters it does by
I prefer not watching the blank screen with the egg turning into an F
and normally remove rhgb from /etc/default/grub.
That is not having the desired effect on this Fedora-26 system.
[root@Box10 bobg]# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux ima
On Tue, 8 Aug 2017 13:03:46 -0400
Bob Goodwin wrote:
> Obviously this is wrong? Whay should I be doing or is this something I
> can no longer change?
Nothing ever looks at /etc/default/grub or runs grub2-mkconfig unless
you manually run it.
I just edit the grub.cfg file itself. It works perfect
On 08/08/17 13:10, Tom Horsley wrote:
(The main problem being finding
the grub.cfg file if you have a uefi system - it is hidden
pretty well :-).
+
Then that must be my problem?
I see two boot partitions:
dev/sda2 976M 167M 742M 19% /boot
/dev/sda1 200M 9.5M 191M 5
On 08/08/2017 10:24 AM, Bob Goodwin wrote:
> On 08/08/17 13:10, Tom Horsley wrote:
>> (The main problem being finding
>> the grub.cfg file if you have a uefi system - it is hidden
>> pretty well :-).
>
> +
>
> Then that must be my problem?
>
> I see two boot partitions:
>
> dev/sda2
On 08/08/17 14:02, Rick Stevens wrote:
I see two boot partitions:
/dev/sda2 976M 167M 742M 19% /boot
/dev/sda1 200M 9.5M 191M 5% /boot/efi
But it says "efi" not "uefi" and I dunno what the difference is.
There really isn't. "efi" and "uefi" are synonymous in this conte
On 08/08/2017 11:24 AM, Bob Goodwin wrote:
> On 08/08/17 14:02, Rick Stevens wrote:
>>> I see two boot partitions:
>>>
>>> /dev/sda2 976M 167M 742M 19% /boot
>>> /dev/sda1 200M 9.5M 191M 5% /boot/efi
>>>
>>> But it says "efi" not "uefi" and I dunno what the difference is.
>
On Tue, 8 Aug 2017 11:50:54 -0700
Rick Stevens wrote:
> Note that on your next kernel upgrade, however, the "rhgb quiet" will
> reappear unless you edit the /etc/default/grub file and those bits from
> the "GRUB_CMDLINE_LINUX" variable in there as well.
That hasn't been my experience. The "grubby
On 08/08/2017 11:59 AM, Tom Horsley wrote:
> On Tue, 8 Aug 2017 11:50:54 -0700
> Rick Stevens wrote:
>
>> Note that on your next kernel upgrade, however, the "rhgb quiet" will
>> reappear unless you edit the /etc/default/grub file and those bits from
>> the "GRUB_CMDLINE_LINUX" variable in there a
On 08/08/17 14:50, Rick Stevens wrote:
So, yes, you're using UEFI to boot. All you need to do is edit the
/boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
reboot. You should be fine.
Note that on your next kernel upgrade, however, the "rhgb quiet" will
reappear unless you e
On 08/08/2017 12:26 PM, Bob Goodwin wrote:
> On 08/08/17 14:50, Rick Stevens wrote:
>> So, yes, you're using UEFI to boot. All you need to do is edit the
>> /boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
>> reboot. You should be fine.
>>
>> Note that on your next kernel upgr
On 8 August 2017 at 20:59, Tom Horsley wrote:
> On Tue, 8 Aug 2017 11:50:54 -0700
> Rick Stevens wrote:
>
>> Note that on your next kernel upgrade, however, the "rhgb quiet" will
>> reappear unless you edit the /etc/default/grub file and those bits from
>> the "GRUB_CMDLINE_LINUX" variable in ther
Hi!
I run GNOME on a 2560x1440 resolution display where I disabled the
"double scaling" (not sure how it's called). So one pixel is one dot.
Unfortunately when running Qt applications such as VLC for example they
autoscale to 1 dot for 4 pixels making those huge and taking most of my
display area.
On 08/09/2017 11:03 AM, Frederic Muller wrote:
> Hi!
>
> I run GNOME on a 2560x1440 resolution display where I disabled the "double
> scaling"
> (not sure how it's called). So one pixel is one dot. Unfortunately when
> running Qt
> applications such as VLC for example they autoscale to 1 dot for
On 08/09/2017 10:18 AM, Ed Greshko wrote:
> On 08/09/2017 11:03 AM, Frederic Muller wrote:
>> Hi!
>>
>> I run GNOME on a 2560x1440 resolution display where I disabled the "double
>> scaling"
>> (not sure how it's called). So one pixel is one dot. Unfortunately when
>> running Qt
>> applications s
17 matches
Mail list logo
