On 5/7/19 7:43 PM, S. Bob wrote:
Oddly enough the slow boot / shutdowns have dissappeared, the only
remaining issue is the bios setting weirdness, including the fact that
Linux will not boot without legacy OS Boot = on
That's not weird. You don't have an EFI boot partition, so you can only
b
On Wednesday, 8 May 2019 02.58.56 WEST Sam Varshavchik wrote:
> I distinctly remember reading somewhere about boot video mode initialization
> changes that were going into F30. IIRC, something about a "flicker-free"
> effort that tries to switch the video mode only once, permanently, during
> boot,
On Tue, May 7, 2019 at 8:44 PM S. Bob wrote:
>
> Oddly enough the slow boot / shutdowns have dissappeared, the only
> remaining issue is the bios setting weirdness, including the fact that
> Linux will not boot without legacy OS Boot = on
>
>
> Thoughts?
From my first response:
If this is enabl
Oddly enough the slow boot / shutdowns have dissappeared, the only
remaining issue is the bios setting weirdness, including the fact that
Linux will not boot without legacy OS Boot = on
Thoughts?
On 5/7/19 8:08 PM, Chris Murphy wrote:
On Tue, May 7, 2019 at 3:54 PM S. Bob wrote:
root@F3
On 05/07/2019 08:08 PM, Chris Murphy wrote:
You can add '> journal.log' to output to a file and post
it somewhere
Or, you can use | tee journal.log so you can keep a copy and see the
results yourself if you prefer.
___
users mailing list -- users@li
On Tue, May 7, 2019 at 3:54 PM S. Bob wrote:
>
> root@F30-host # cat /etc/fstab
>
> #
> # /etc/fstab
> # Created by anaconda on Wed Dec 31 19:25:43 1997
> #
> # Accessible filesystems, by reference, are maintained under '/dev/disk/'.
> # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8)
I distinctly remember reading somewhere about boot video mode initialization
changes that were going into F30. IIRC, something about a "flicker-free"
effort that tries to switch the video mode only once, permanently, during
boot, and sticking with the same video mode all the way to the deskto
I also endorse using your own equipment although some equipment might
be a little bit of an adventure.
I've posted several times over the past 8 months or so about the
equipment I've been using on Cox and Spectrum, I don't even have to
tell the ISP what equipment I'm using... I just tell them I'm
On 5/5/19 10:45 PM, Chris Murphy wrote:
On Sun, May 5, 2019 at 1:41 PM S. Bob wrote:
Hi All;
I've managed to install Fedora 30 on a new LG Gram 17 laptop.
I had to set acpi=off to get the live cd to boot, then I had to remove
the acpi=off and rebuild the EFI grub file so the trackpad would
On Tue, May 7, 2019 at 11:53 AM Samuel Sieb wrote:
>
> On 5/7/19 10:42 AM, Chris Murphy wrote:
> > If it's missing or zero length, is curious, but after we know that, it
> > must be be fixed so you can run the grub2-mkconfig command now.
>
> It must be empty because otherwise the "cat" command wou
On 5/7/19 12:50 PM, Rex Dieter wrote:
But yeah, kdm is deprecated and sddm or something else is generally better
to use for posterity.
Anyone know if there is a lightweight Qt-based LightDM greeter out there
anywhere? I've switched to LightDM + slick-greeter, but it's Gtk-based.
The only Qt-b
On 5/7/19 10:42 AM, Chris Murphy wrote:
If it's missing or zero length, is curious, but after we know that, it
must be be fixed so you can run the grub2-mkconfig command now.
It must be empty because otherwise the "cat" command would have given an
error. A very surprising situation though.
_
Ed Greshko wrote:
> On 5/7/19 7:08 AM, David Dembrow wrote:
>> I have been using fedora with kde plasma desktop. When I upgraded from
>> fedora 29 to fedora 30 I lost my kde login manager as well as the kde
>> plasma desktop.
>>
>> Is there a way to get my kde plasma desktop (or equivalent) back?
On Tue, May 7, 2019 at 8:11 AM Ranbir wrote:
>
> On Mon, 2019-05-06 at 17:00 -0600, Chris Murphy wrote:
> >
> > I see two minor anomalies:
> >
> > /boot is XFS, should not be a problem.
> > NVRAM contains dup entries, Boot0001 and Boot0008.
> >
> > Boot0001 is pointing to the new naming for shim,
On 5/7/19 7:10 AM, Ranbir wrote:
On Mon, 2019-05-06 at 17:00 -0600, Chris Murphy wrote:
NVRAM contains dup entries, Boot0001 and Boot0008.
Boot0001 is pointing to the new naming for shim, and it's also the
default and current boot. Therefore, Boot0008 can be deleted. It's
not
causing the proble
Il giorno dom, 05/05/2019 alle 11.38 +0200, François Patte ha scritto:
> Today all my add-ons to firefox do not work!
here the fix:
https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/comment-page-6/#comment-226171
without enable studies
--
Dario Lesca
(inviato dal
On Mon, 2019-05-06 at 17:00 -0600, Chris Murphy wrote:
>
> I see two minor anomalies:
>
> /boot is XFS, should not be a problem.
> NVRAM contains dup entries, Boot0001 and Boot0008.
>
> Boot0001 is pointing to the new naming for shim, and it's also the
> default and current boot. Therefore, Boot
François Patte:
Français language pack could not be verified for use in firefox and has
been disabled!
The worst bug is actually this one for all non-English speakers. Your
browser now does not recognize your own language.
But as already mentioned it is a known bug. You can find more info o
Start aMule via command line (amule-2.3.2-17.fc30.x86_64.rpm)
aMule seem to work, but.
Goto on Network (List Server) panel.
After few second aMule crash (core dumped) with this error
2019-05-06 22:26:02: Initialising aMule 2.3.2 compiled with wxGTK2
v3.0.4 2019-05-06 22:26:02: Checking if there i
19 matches
Mail list logo
