On 08/04/2017 11:56 AM, Jon LaBadie wrote:
> On Fri, Aug 04, 2017 at 03:33:19AM +, Marmorstein, Robert wrote:
>>
>>
>>> though loginctl does). Login sessions via ssh, either
>> >from remote hosts or to localhost are registered.
>>
>> Does "who -a" show them? I have a vague recollection I loo
On 08/04/2017 04:39 PM, Ed Greshko wrote:
> Now, adding KDE resulted in 354 additional packages being installed.
>
> One of them did the trick. I suppose I could try and track down the magic
> package
Or, if anyone is interested this is the list of added packages
http://tinyurl.com/yaq
On Fri, 2017-08-04 at 16:39 +0800, Ed Greshko wrote:
>
>
> I will note that I have 2 test VM's installed. One pure KDE. One
> pure LXQt. Both
> are using and have the same version of sddm installed. Which is
> sddm-0.14.0-10.fc26.
>
> On the KDE system when logged in the who command will sho
Quoting "Dr. Robert Marmorstein" :
I've been working on this too, this week. I think I have it working
from source but haven't finished testing yet. The source install
wasn't really too bad, so I recommend it. The messinet rpms didn't
work for me.
Feel free to contact me offline to let
On Thu, Aug 3, 2017 at 8:42 PM, Sherman Grunewagen
wrote:
> That was the problem! Nice catch. I'm clueless as to how previous
> kmod-nvidia modules have built and run. And I don't understand
> why, when running akmods as root, the "make" process is unable
> to "see" inside /usr/local/include (n
On 08/04/2017 12:05 AM, Frédéric Bron wrote:
I would like to force fsck at boot but I tried touch /forcefsck and it
did not run or I did not see it (however the file /forcefsck
disappeared).
It probably ran and you didn't see it. For ext2/3/4, you can run
tune2fs -l /dev/{whatever} | grep "
On 08/04/2017 05:13 AM, Richard Shaw wrote:
On Thu, Aug 3, 2017 at 8:42 PM, Sherman Grunewagen
wrote:
That was the problem! Nice catch. I'm clueless as to how previous
kmod-nvidia modules have built and run. And I don't understand
why, when running akmods as root, the "make" process is unabl
Frédéric Bron wrote on 08/04/2017 02:05 PM:
I would like to force fsck at boot but I tried touch /forcefsck and it
did not run or I did not see it (however the file /forcefsck
disappeared).
Thanks,
Frédéric
Add the following to the boot parameter:
fsck.mode=force
Touching /forcefsck was for sy
On 08/04/2017 06:18 PM, AV wrote:
> On Fri, 2017-08-04 at 16:39 +0800, Ed Greshko wrote:
>>
>> I will note that I have 2 test VM's installed. One pure KDE. One
>> pure LXQt. Both
>> are using and have the same version of sddm installed. Which is
>> sddm-0.14.0-10.fc26.
>>
>> On the KDE system w
Hi Everybody ,
When starting K3B I get the following message :
System configuration problem.
Unable to find cdrskin executable.
K3B uses cdrskin in place of cdrecord.
Solution : Install the libburn package which contains cdrskin.
Question : How to manage and what is the essence of the problem
Le 04/08/2017 à 18:43, Ger van Dijck a écrit :
> Hi Everybody ,
>
>
> When starting K3B I get the following message :
>
> System configuration problem.
> Unable to find cdrskin executable.
> K3B uses cdrskin in place of cdrecord.
> Solution : Install the libburn package which contains cdrskin.
>
On Thu, 27 Jul 2017 13:32:50 -0400, Tom Horsley wrote:
> Well I've been using my newly installed fedora 26 boot partition for all
> of a half day, and the nouveau driver just completely froze up the
> display (exactly the same thing that happened on fedora 24 with
> nouveau). I guess I'm off to lo
On Fri, 28 Jul 2017 14:18:16 +0800, ChunYu Wang wrote:
> Yes, I AGREE!
>
> But one of the key features upon NV cards is CUDA, which we cannot use
> it on other platforms. Though OpenCL is another solution to achieve
> GPGPU resolutions, but it is hard to learn and hard to use, at least,
> for me.
> It probably ran and you didn't see it. For ext2/3/4, you can run
>tune2fs -l /dev/{whatever} | grep "Last checked"
Apparently, this does not work:
# tune2fs -l /dev/sda
tune2fs 1.43.3 (04-Sep-2016)
tune2fs: Bad magic number in super-block while trying to open /dev/sda
Found a gpt partition t
At boot, I get this message in red:
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
And here is the output of the recommanded command:
# systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Module
>Apparently, this does not work:
># tune2fs -l /dev/sda
>tune2fs 1.43.3 (04-Sep-2016)
>tune2fs: Bad magic number in super-block while trying to open /dev/sda
>Found a gpt partition table in /dev/sda
/dev/sda is usually a drive name, not a partition name. Does it work if you
try /dev/sda1 or /dev
On 08/03/2017 11:05 PM, fred roller wrote:
I believe you could use tune2fs command
sudo tune2fs -c 50 /dev/[your dev]
the -c option set the interval of boots. Change it to 1 and it will
check every boot... 30 I believe is the current default because every
boot is impractical imo. I believe
On 08/04/2017 06:46 AM, Mamoru TASAKA wrote:
Touching /forcefsck was for sysvinit and upstart era. It is no longer valid
for systemd.
This is still valid and has nothing to do with systemd. It's handled by
dracut in the initramfs.
___
users mailing
>>Apparently, this does not work:
>># tune2fs -l /dev/sda
>>tune2fs 1.43.3 (04-Sep-2016)
>>tune2fs: Bad magic number in super-block while trying to open /dev/sda
>>Found a gpt partition table in /dev/sda
>
> /dev/sda is usually a drive name, not a partition name. Does it work if you
> try /dev/sd
>> Touching /forcefsck was for sysvinit and upstart era. It is no longer
>> valid
>> for systemd.
>
> This is still valid and has nothing to do with systemd. It's handled by
> dracut in the initramfs.
Yes, apparently from the last checked date, it seems that /forcefsck
worked but I was expecting
> sudo tune2fs -c 50 /dev/[your dev]
>
> the -c option set the interval of boots. Change it to 1 and it will check
> every boot... 30 I believe is the current default because every boot is
> impractical imo. I believe you can set the priority in the fstab.. last
> column if memory serves. 0 no c
On 08/04/2017 09:59 PM, Frédéric Bron wrote:
Apparently the default value is -1 on my partitions which according to
the manual means "If max-mount-counts is 0 or -1, the number of times
the filesystem is mounted will be disregarded by e2fsck(8) and the
kernel."
So I guess that fsck is then ran o
On 08/04/2017 09:54 PM, Frédéric Bron wrote:
Yes, apparently from the last checked date, it seems that /forcefsck
worked but I was expecting to see something on the screen and it must
be done hidden.
Unless there's a problem, it will run very quickly.
___
23 matches
Mail list logo
