Re: Program won't start

[Jonathan Ryshpan]

On Fri, 2018-04-13 at 05:47 +0800, Ed Greshko wrote:
> On 04/12/18 21:05, Jonathan Ryshpan wrote:
> > Seagate's SeaTools for Linux won't start on my system. The file is rather 
> > old and
> > in a funky format, but it looks like it ought to run. Nevertheless, it 
> > won't run.
> > Can anyone tell me what's going on? Here's what happens:
> 
> I suppose the larger question is, why use an old tool when most drives these 
> days
> support S.M.A.R.T. ?  I think SMART came into being around 2003.

A very good question.  This drive, a Seagate USB Backup Plus Portable Drive, 
doesn't seem to support SMART:  Here's a try:
   # smartctl --xall -T permissive /dev/sdc  
   smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.15.15-300.fc27.x86_64] (local 
build)
   Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported field in scsi command

=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number:[No Information Found]
Firmware Version: [No Information Found]
Device is:Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:Fri Apr 13 21:56:30 2018 PDT
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if 
SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if 
SMART is enabled.
A mandatory SMART command failed: exiting. To continue, add one or more '-T 
permissive' options.

I'm trying to get SeaTools for DOS, which is a self booting test suite,
intended to boot from a CD-ROM, running on a flash drive, but so far
without success.

The problem that started all this is that the drive, which I use for
backup, has started making an alarming beeping noise.  After not using
it for a while the noise has gone away, and I have made another backup
successfully.  Time to get a replacement; but I'm still curious what's
going on with the drive.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Danny Horne via users]

On 13/04/18 20:34, Bob Goodwin wrote:
> .
>
> I am attempting to set up an NFS server on a new Fedora 27 computer I
> have assembled using instructions I found, "Fedora
> Administration_Guide_Draft/NFS" and I am having a problem accessing it.
>
> $ cat /etc/exports
> /var/ftp/pub  192.168.1.0/255.255.255.0(ro)
> /home/public  192.168.1.0/255.255.255.0(rw)
>
> var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_subtree_check)
>
> /var/ftp/pub
> 192.168.54.0/255.255.255.0(ro,sync,no_wdelay,no_subtree_check,nohide)
>
> Then from the client I get a refusal:
>
> # mount 192.168.1.86:/home/public  /mnt/test/
> mount.nfs: Connection refused
>
> There is an ethernet path between them on my lan, ssh works from each
> computer to the other ...
>
> Perhaps a problem with bind, I don't know how to troubleshoot this,
> would appreciate suggestions.
>
> Bob
>
Not an expert myself, but I can't see anything there that says you've
opened up the NFS ports on the NFS server
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Danny Horne via users]

On 13/04/18 20:34, Bob Goodwin wrote:
> .
>
> I am attempting to set up an NFS server on a new Fedora 27 computer I
> have assembled using instructions I found, "Fedora
> Administration_Guide_Draft/NFS" and I am having a problem accessing it.
>
> $ cat /etc/exports
> /var/ftp/pub  192.168.1.0/255.255.255.0(ro)
> /home/public  192.168.1.0/255.255.255.0(rw)
>
> var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_subtree_check)
>
> /var/ftp/pub
> 192.168.54.0/255.255.255.0(ro,sync,no_wdelay,no_subtree_check,nohide)
>
> Then from the client I get a refusal:
>
> # mount 192.168.1.86:/home/public  /mnt/test/
> mount.nfs: Connection refused
>
> There is an ethernet path between them on my lan, ssh works from each
> computer to the other ...
>
> Perhaps a problem with bind, I don't know how to troubleshoot this,
> would appreciate suggestions.
>
> Bob
>
Sorry, meant to say firewall ports
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: initramfs: kernel update adds unwanted driver?

[Grant Edwards]

On 2018-04-13, Rick Stevens  wrote:
> On 04/13/2018 09:34 AM, Grant Edwards wrote:

>> What's the best way to remove the old, broken driver from the
>> initramfs so that the driver in the root filesystem is used on boot?
>> 
>> Is there a way to prevent the kernel update process from adding the
>> driver back to the initramfs the next time a kernel is updated?
[...]

> Uhm, probably do a "rmmod foo;modprobe foo", THEN rebuild the
> initramfs image. Also check both the /etc/dracut.conf file and
> /etc/dracut.conf.d directory to see if they're specifying some
> ancient version of your module. At worst, add a
> --add-modules=" to the command.

Except the goal is to _not_ have the driver in the initramfs.  There
is absolutely no reason it needs to be there, and eliminating it from
the initramfs avoids a source of confusion.

I've identified a couple options:

First create a file named /etc/dracut.conf.d/foo containing the line
omit_drivers+="foo".  Then either

1. Rebuild the initramfs with the 'dracut' command.  I haven't tested
   this yet. It seems a bit risky, since (AFAICT) I don't have any way
   of knowing what command-line options were used to generate the
   current, working initramfs, and I might end up making unintentional
   changes when I regenerate it.  One presumes that a well-behaved
   admin would edit the dracut config files rather than use
   command-line options, but I one should not assume customers are all
   well-behaved.

or

2. Unpack the current initramfs-*.img file, delete the foo.ko.xz file
   and re-pack the initramfs-*.img file. I've written a bash shell
   script to do that, and its seems to work fine.  This feels a little
   less risky than regenerating the initramfs from scratch.

In either case, the omit_drivers setting should prevent re-breaking
the system with future runs of dracut (either manually by the admin or
as part of a kernel upgrade).

-- 
Grant Edwards   grant.b.edwardsYow! ... or were you
  at   driving the PONTIAC that
  gmail.comHONKED at me in MIAMI last
   Tuesday?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Help debug a network issue

[Robin Laing]

On 26/03/18 11:57, Ulf Volmer wrote:

On 26.03.2018 08:40, Robin Laing wrote:


sudo modprobe -r r8169
sudo modprobe r1869

So, what is my next step in finding out why this won't restart on suspend?


you can place a script for automatically load/unload your network driver.

see

https://blog.christophersmart.com/2016/05/11/running-scripts-before-and-after-suspend-with-systemd/

best regards
Ulf



This works.

Thanks.

This is the scrip I used.


#!/bin/sh
if [ "${1}" == "pre" ]; then
  # Do the thing you want before suspend here, e.g.:
#  echo "we are suspending at $(date)..." > /tmp/systemd_suspend_test
  modprobe -r r8169
elif [ "${1}" == "post" ]; then
  # Do the thing you want after resume here, e.g.:
#   echo "...and we are back from $(date)" >> /tmp/systemd_suspend_test
  modprobe r8169
fi


Robin
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

NFS server setup -

[Bob Goodwin]

.

I am attempting to set up an NFS server on a new Fedora 27 computer I 
have assembled using instructions I found, "Fedora 
Administration_Guide_Draft/NFS" and I am having a problem accessing it.


$ cat /etc/exports
/var/ftp/pub  192.168.1.0/255.255.255.0(ro)
/home/public  192.168.1.0/255.255.255.0(rw)

var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_subtree_check)

/var/ftp/pub 
192.168.54.0/255.255.255.0(ro,sync,no_wdelay,no_subtree_check,nohide)


Then from the client I get a refusal:

# mount 192.168.1.86:/home/public  /mnt/test/
mount.nfs: Connection refused

There is an ethernet path between them on my lan, ssh works from each 
computer to the other ...


Perhaps a problem with bind, I don't know how to troubleshoot this, 
would appreciate suggestions.


Bob

--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Bob Goodwin]

On 04/13/18 15:37, Danny Horne via users wrote:

  I can't see anything there that says you've
opened up the NFS ports on the NFS server
I have another NFS server that's always running and works so I think the 
required ports are open.


Firewall? Probably closed by default.

May be a firewall problem, but if it works with one NFS server? I'll try 
stopping firewalld, although I think I have already done that a few days 
ago, need to be sure.


Bob

--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Bob Goodwin]

On 04/13/18 15:36, Terry Polzin wrote:

Firewall? Probably closed by default.


.

I just tried stopping firewalld and selinux at either computer, client 
and server, one at a time, but it would not connect with any one of them 
stopped.


--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: SD slot errors

[Patrick O'Callaghan]

On Fri, 2018-04-13 at 15:31 -0400, D. Hugh Redelmeier wrote:
> I've just installed F28 beta on my Cube Mix Plus tablet.

This should go to the Fedora Test list, not here.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Windows eats Fedora installation USB stick

[D. Hugh Redelmeier]

Sometimes when I try to install Fedora, Windows eats my installation
USB stick.

Fedora is distributed as a .iso (a CD/DVD image). This image is cleverly 
designed such that if you dump it, byte for byte, onto a USB stick (not 
into a filesystem), you get a stick that can be booted.

I install by booting this disk, usually in UEFI mode.

But sometimes the firmware escapes me and Windows is booted.  For example, 
if I am not quick enough typing ESC / DEL / F12 / whatever to steer the 
firmware to boot the USB stick.

When that happens, Windows always seems to damage the image on the USB
stick.  What the heck is up with that?

When I boot the installation stick, I always choose the option to
check the contents before booting Fedora.  I do this because the
Windows damage is unannounced.

I just had it happen again.  Here's the damage, as found by cmp(1).  I
haven't worked hard at analyzing what it is but every changed byte
started out as zero.  The new bytes don't smell like ASCII (but I'm
not great at recognizing ASCII in decimal).

Any idea why Windows makes this unprovoked attack on installation
sticks?  It sure is inconvenient.

Since Microsoft is unlikely to fix this Windows bug, would it be 
worthwhile for Fedora to take countermeasures?  For example, ignore 
exactly those bytes that Windows damages?

$ sudo cmp -l Fedora-Workstation-Live-x86_64-28_Beta-1.3.iso /dev/sdg
  61462533   0 377
  61462534   0 377
  61471313   0 377
  61471314   0 377
  61471315   0 377
  61471316   0 377
  61472773   0 377
  61472774   0 377
  61481553   0 377
  61481554   0 377
  61481555   0 377
  61481556   0 377
  61483073   0 102
  61483074   0  40
  61483076   0 111
  61483078   0 156
  61483080   0 146
  61483082   0 157
  61483084   0  17
  61483086   0 162
  61483087   0 162
  61483089   0 155
  61483091   0 141
  61483093   0 164
  61483095   0 151
  61483097   0 157
  61483101   0 156
  61483105   0   1
  61483106   0 123
  61483108   0 171
  61483110   0 163
  61483112   0 164
  61483114   0 145
  61483116   0  17
  61483118   0 162
  61483119   0 155
  61483121   0  40
  61483123   0 126
  61483125   0 157
  61483127   0 154
  61483129   0 165
  61483133   0 155
  61483135   0 145
  61483137   0 123
  61483138   0 131
  61483139   0 123
  61483140   0 124
  61483141   0 105
  61483142   0 115
  61483143   0 176
  61483144   0  61
  61483145   0  40
  61483146   0  40
  61483147   0  40
  61483148   0  26
  61483150   0 103
  61483151   0 223
  61483152   0 142
  61483153   0 215
  61483154   0 114
  61483155   0 215
  61483156   0 114
  61483159   0 224
  61483160   0 142
  61483161   0 215
  61483162   0 114
  61483163   0   2
  61499393   0  56
  61499394   0  40
  61499395   0  40
  61499396   0  40
  61499397   0  40
  61499398   0  40
  61499399   0  40
  61499400   0  40
  61499401   0  40
  61499402   0  40
  61499403   0  40
  61499404   0  20
  61499406   0 103
  61499407   0 223
  61499408   0 142
  61499409   0 215
  61499410   0 114
  61499411   0 215
  61499412   0 114
  61499415   0 224
  61499416   0 142
  61499417   0 215
  61499418   0 114
  61499419   0   2
  61499425   0  56
  61499426   0  56
  61499427   0  40
  61499428   0  40
  61499429   0  40
  61499430   0  40
  61499431   0  40
  61499432   0  40
  61499433   0  40
  61499434   0  40
  61499435   0  40
  61499436   0  20
  61499438   0 103
  61499439   0 223
  61499440   0 142
  61499441   0 215
  61499442   0 114
  61499443   0 215
  61499444   0 114
  61499447   0 224
  61499448   0 142
  61499449   0 215
  61499450   0 114
  61499457   0 102
  61499458   0 107
  61499460   0 165
  61499462   0 151
  61499464   0 144
  61499468   0  17
  61499470   0 377
  61499471   0 377
  61499472   0 377
  61499473   0 377
  61499474   0 377
  61499475   0 377
  61499476   0 377
  61499477   0 377
  61499478   0 377
  61499479   0 377
  61499480   0 377
  61499481   0 377
  61499482   0 377
  61499485   0 377
  61499486   0 377
  61499487   0 377
  61499488   0 377
  61499489   0   1
  61499490   0 111
  61499492   0 156
  61499494   0 144
  61499496   0 145
  61499498   0 170
  61499500   0  17
  61499502   0 377
  61499503   0 145
  61499505   0 162
  61499507   0 126
  61499509   0 157
  61499511   0 154
  61499513   0 165
  61499517   0 155
  61499519   0 145
  61499521   0 111
  61499522   0 116
  61499523   0 104
  61499524   0 105
  61499525   0 130
  61499526   0 105
  61499527   0 176
  61499528   0  61
  61499529   0  40
  61499530   0  40
  61499531   0  40
  61499532   0  40
  61499534   0 104
  61499535   0 223
  61499536   0 142
  61499537   0 215
  61499538   0 114
  61499539   0 215
  61499540   0 114
  61499543   0 224
  61499544   0 142
  61499545   0 215
  61499546   0 114
  61499547   0  50
  61499548   0  21
  61499549   0 114
  61499553   0 102
  61499554   0 164
  61499558   0 377
  61499559   0 377
  61499560   0 377
  61499561   0 377
  61499562   0 377
  61499563   0 377
  61499564   0  17
  61499566   0 316
  61499567  

SD slot errors

[D. Hugh Redelmeier]

I've just installed F28 beta on my Cube Mix Plus tablet.  It seems to
work but a sequence of messages keep showing up in the dmesg
outputnevery 10 seconds.

[  537.896013] mmc1: Timeout waiting for hardware cmd interrupt.
[  537.896023] mmc1: sdhci:  SDHCI REGISTER DUMP ===
[  537.896037] mmc1: sdhci: Sys addr:  0x | Version:  0x1002
[  537.896048] mmc1: sdhci: Blk size:  0x | Blk cnt:  0x
[  537.896053] mmc1: sdhci: Argument:  0x | Trn mode: 0x
[  537.896059] mmc1: sdhci: Present:   0x000a0001 | Host ctl: 0x0001
[  537.896065] mmc1: sdhci: Power: 0x000e | Blk gap:  0x0080
[  537.896070] mmc1: sdhci: Wake-up:   0x | Clock:0xe8c7
[  537.896075] mmc1: sdhci: Timeout:   0x | Int stat: 0x
[  537.896081] mmc1: sdhci: Int enab:  0x00ff0043 | Sig enab: 0x00ff0043
[  537.896086] mmc1: sdhci: AC12 err:  0x | Slot int: 0x
[  537.896092] mmc1: sdhci: Caps:  0x7568c881 | Caps_1:   0x0807
[  537.896097] mmc1: sdhci: Cmd:   0x0102 | Max curr: 0x
[  537.896103] mmc1: sdhci: Resp[0]:   0x | Resp[1]:  0x
[  537.896108] mmc1: sdhci: Resp[2]:   0x | Resp[3]:  0x
[  537.896112] mmc1: sdhci: Host ctl2: 0x
[  537.896118] mmc1: sdhci: ADMA Err:  0x | ADMA Ptr: 0x
[  537.896121] mmc1: sdhci: 

This looks to me as if it is trying to open the SD card (but there
is no SD card in the slot).

Here's the part of dmesg output where the slot is recognized:

[2.093265] sdhci: Secure Digital Host Controller Interface driver
[2.093267] sdhci: Copyright(c) Pierre Ossman
[2.111345] sdhci-pci :00:1e.4: SDHCI controller found [8086:9d2b] (rev 
21)
[2.111363] sdhci-pci :00:1e.4: enabling device ( -> 0002)
[2.112328] mmc0: SDHCI controller on PCI [:00:1e.4] using ADMA 64-bit
[2.112348] sdhci-pci :00:1e.6: SDHCI controller found [8086:9d2d] (rev 
21)
[2.112364] sdhci-pci :00:1e.6: enabling device ( -> 0002)


Why would it do this?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Terry Polzin]

On Fri, Apr 13, 2018 at 3:34 PM, Bob Goodwin  wrote:

> .
>
> I am attempting to set up an NFS server on a new Fedora 27 computer I have
> assembled using instructions I found, "Fedora Administration_Guide_Draft/NFS"
> and I am having a problem accessing it.
>
> $ cat /etc/exports
> /var/ftp/pub  192.168.1.0/255.255.255.0(ro)
> /home/public  192.168.1.0/255.255.255.0(rw)
>
> var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_subtree_check)
>
> /var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_wdelay,no_subtree_chec
> k,nohide)
>
> Then from the client I get a refusal:
>
> # mount 192.168.1.86:/home/public  /mnt/test/
> mount.nfs: Connection refused
>
> There is an ethernet path between them on my lan, ssh works from each
> computer to the other ...
>
> Perhaps a problem with bind, I don't know how to troubleshoot this, would
> appreciate suggestions.
>
> Bob
>
> --
> Bob Goodwin - Zuni, Virginia, USA
> http://www.qrz.com/db/W2BOD
> box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>


Firewall? Probably closed by default.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Windows eats Fedora installation USB stick

[ToddAndMargo]

On 04/13/2018 10:10 AM, D. Hugh Redelmeier wrote:

When that happens, Windows always seems to damage the image on the USB
stick.  What the heck is up with that?


Hi Hugh,

I have to work on THAT operating system whose name I shall
not mention A LOT.  Not that I want to.  My customer base
is mostly small businesses and they can not run their
businesses without THAT operating system as THAT operating
system was won the applications wars for small businesses,
the one that is slow, expensive, and riddled with bugs.
And THAT operating system puts a roof over my head and food
on my table.  If I had enough Linux customers, I would dump
THAT operating system in a second.  If I come home from
a days work and am in a crabby mode, it is because I have
been working on THAT operating system, especially the
one where they CAN'T COUNT.  Linux is just plane
fun to work on, especially Fedora (RHEL and clones, on
the other hand, I won't get into).

I use Live USB sticks to rescue computers with THAT operating
system ALL-THE-TIME.  And what you describe happens to me
on a frequent basis.  I have taught myself never to insert
a Linux based flash drive into THAT operating system which is
running.  And when I forget, I have a spare.  It is a total
pain in the ...

When I get back to my Linux based office, I dd the ISO over
the corrupted stick.

When I have a stick with something custom on it, I will dd
the stick to my hard drive for later over writing when it
gets corrupted.

And be careful with THAT operating system, shutdown and
reboot are suspend and not shutdown.  You have to turn
"Fast Boot" off and do a real shutdown to get it to
take.  (I can provide instructions for that, if you need
them.)

-T

--
~~
Computers are like air conditioners.
They malfunction when you open windows
~~
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: initramfs: kernel update adds unwanted driver?

[Rick Stevens]

On 04/13/2018 09:34 AM, Grant Edwards wrote:
> On Fedora 27 with kernel recently updated to 4.15.15-300.fc27.i686, I
> ran into a problem when I installed a new version of a driver (we'll
> call "foo") in /lib/modules/$(uname -r)/kernel/drivers/[...].
> 
> Doing a "rmmod foo; modprobe foo" loads the new driver and everything
> works great.  However, rebooting loads a 15-year old version of the
> driver (which doesn't work great).
> 
> lsinitrd shows that the 15-year old driver is present in the
> initramfs.  On a clean install of Fedora 27 (running an identical
> kernel version) the initramfs does not contain the "foo" driver at
> all.
> 
> Did the kernel upgrade process muck up the initramfs by adding the old
> version of the "foo" driver?  The "old" version is the one that's
> shipped with the kernel package, but I've never seen it included in
> the initramfs before.
> 
> What's the best way to remove the old, broken driver from the
> initramfs so that the driver in the root filesystem is used on boot?
> 
> Is there a way to prevent the kernel update process from adding the
> driver back to the initramfs the next time a kernel is updated?
> 
> Alternatively, I suppose I could add a "service" that runs at boot
> time and does a "rmmod foo; modrobe foo", but that seems like the
> wrong way to fix this...

Uhm, probably do a "rmmod foo;modprobe foo", THEN rebuild the initramfs
image. Also check both the /etc/dracut.conf file and /etc/dracut.conf.d
directory to see if they're specifying some ancient version of your
module. At worst, add a --add-modules=" to the command.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-  Death is nature's way of dropping carrier -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Help debug a network issue

[Robin Laing]

I have been busy and unable to look at this until today.

On 26/03/18 01:05, Samuel Sieb wrote:

On 03/25/2018 07:45 PM, Robin Laing wrote:

Network controller is:

Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0c)


Module is:

Kernel modules: r8169


That's the right driver.  One thing you could try is after removing the 
module, try "modprobe r8169 debug=n" where n is a number up to 16.  That 
will give you more debugging info in the log.  Careful, 16 might really 
spam the log, so maybe start at 8 and work your way up.


Going to 16 didn't make any difference from 10.

Apr 13 14:03:41 tdllap kernel: r8169 :04:00.0: can't disable ASPM; 
OS doesn't have ASPM control
Apr 13 14:03:41 tdllap kernel: r8169 :04:00.0 eth0: RTL8168g/8111g 
at 0xef2b4190, 40:16:7e:10:e0:9a, XID 0c000880 IRQ 34
Apr 13 14:03:41 tdllap kernel: r8169 :04:00.0 eth0: jumbo features 
[frames: 9200 bytes, tx checksumming: ko]

Apr 13 14:03:41 tdllap kernel: r8169 :04:00.0 enp4s0: renamed from eth0
Apr 13 14:03:41 tdllap kernel: r8169 :04:00.0 enp4s0: link down
Apr 13 14:03:44 tdllap kernel: r8169 :04:00.0 enp4s0: link up



not ready


The driver is saying that there is no link detected.  Are the lights on? 
  What does "ethtool enp4s0" tell you?




Link lights on switch come up when lid closed and opened without 
reloading the network driver.


ethtool shows Link detected: no which is interesting.


Looking further into the log files, I don't seen any mention of r1869 
before March 17 when I tried to make a change to the boot parameters 
from something I found on the net which was almost a month after the 
problem started.


pci=nomsi,noaer


I would suggest removing this.

My guess, given that reloading the driver makes it work again, is that 
after resume, the driver is not turning some part of the chipset back 
on.  Maybe the interrupts are getting turned back on.


 > Mar 26 01:07:55 xx kernel: do_IRQ: 7.33 No irq handler for vector

What does "grep r8169 /proc/interrupts" give you when the interface is 
working?  Try it a couple of times and see how the numbers change.  Then 
when it's not working try it again a few times and see if the numbers 
are still changing.


This is from /proc/interupts and doesn't change between suspends or 
disappear.  It is there from boot until I remove the module.


 34:  0  0  0  0125  0 
0175  IR-PCI-MSI 2097152-edge  enp4s0


It used to work until February but I don't know what update affected it 
as I wasn't told until a few kernel updates that there was an issue.


What I found that is when I load the module, lsmod give me this.
r8169  94208  0
mii16384  1 r8169

I am going to look more at the mii-tool and see if that has anything to 
do with it.


I did find another thread about kernel modules being broken in February 
and specifically mentioning r8169 module not reloading on suspend.


https://forum.manjaro.org/t/linux415-r8168-cant-connect-to-the-network-after-suspend-to-ram/39557/4

https://forum.manjaro.org/t/kernel-update-broke-ethernet-driver-realtek-r8168-r8169/39551/4

Robin
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Rick Stevens]

On 04/13/2018 12:39 PM, Danny Horne via users wrote:
> On 13/04/18 20:34, Bob Goodwin wrote:
>> .
>>
>> I am attempting to set up an NFS server on a new Fedora 27 computer I
>> have assembled using instructions I found, "Fedora
>> Administration_Guide_Draft/NFS" and I am having a problem accessing it.
>>
>> $ cat /etc/exports
>> /var/ftp/pub  192.168.1.0/255.255.255.0(ro)
>> /home/public  192.168.1.0/255.255.255.0(rw)
>>
>> var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_subtree_check)
>>
>> /var/ftp/pub
>> 192.168.54.0/255.255.255.0(ro,sync,no_wdelay,no_subtree_check,nohide)
>>
>> Then from the client I get a refusal:
>>
>> # mount 192.168.1.86:/home/public  /mnt/test/
>> mount.nfs: Connection refused
>>
>> There is an ethernet path between them on my lan, ssh works from each
>> computer to the other ...
>>
>> Perhaps a problem with bind, I don't know how to troubleshoot this,
>> would appreciate suggestions.
>>
>> Bob
>>
> Sorry, meant to say firewall ports

By default F27 uses NFSv4. The access is far more restrictive. If you're
NFS mounting a filesystem as a normal user on the client, then you have
to make sure that user has the same UID and GID on the server and has
access to that exported directory.

If you're mounting it as root on the client (as seems to be true by the
"#" in the example command), make sure you add "no_root_squash" to the
export at the server:

/home/public192.168.1.0/24(rw,no_root_squash)

Otherwise the server will try to demote the root user down to the
anonymous user, who probably doesn't have R/W access to /home/public
(or whatever export you've specified).

Make sense?
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-They say when you play a Microsoft CD backwards, you'll hear-
-   Satanic messages, but if you play it forwards, it will install   -
-   Windows...which means Satan is in your system.   -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Windows eats Fedora installation USB stick

[Danny Horne via users]

On 13/04/18 18:10, D. Hugh Redelmeier wrote:
> Sometimes when I try to install Fedora, Windows eats my installation
> USB stick.
>
> Fedora is distributed as a .iso (a CD/DVD image). This image is cleverly 
> designed such that if you dump it, byte for byte, onto a USB stick (not 
> into a filesystem), you get a stick that can be booted.
>
>
Back in my Windows days I always used a program called Rufus to created
bootable USB sticks from ISO's.  Never had any problems with corruption
on them

https://rufus.akeo.ie/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Windows eats Fedora installation USB stick

[Joe Zeff]

On 04/13/2018 10:10 AM, D. Hugh Redelmeier wrote:

But sometimes the firmware escapes me and Windows is booted.  For example,
if I am not quick enough typing ESC / DEL / F12 / whatever to steer the
firmware to boot the USB stick.


Try this: start your computer without the USB drive inserted.  Only put 
it in after you're in the BIOS so that if Windows gets started, it can't 
trash the image.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Windows eats Fedora installation USB stick

[Joerg Lechner via users]

Hi
I use always Fedora Mediawriter, also in the Windows format, when I have no 
Fedora running. For me it's no problem to use Windows 8.1 in parallel to 
Fedora, Fedora on an usb connected external medium. Do You install Fedora on 
the Windows medium?
Kind regards

 

 

 

-Ursprüngliche Mitteilung- 
Von: D. Hugh Redelmeier 
An: users 
Verschickt: Fr, 13. Apr 2018 19:11
Betreff: Windows eats Fedora installation USB stick

Sometimes when I try to install Fedora, Windows eats my installation
USB stick.

Fedora is distributed as a .iso (a CD/DVD image). This image is cleverly 
designed such that if you dump it, byte for byte, onto a USB stick (not 
into a filesystem), you get a stick that can be booted.

I install by booting this disk, usually in UEFI mode.

But sometimes the firmware escapes me and Windows is booted.  For example, 
if I am not quick enough typing ESC / DEL / F12 / whatever to steer the 
firmware to boot the USB stick.

When that happens, Windows always seems to damage the image on the USB
stick.  What the heck is up with that?

When I boot the installation stick, I always choose the option to
check the contents before booting Fedora.  I do this because the
Windows damage is unannounced.

I just had it happen again.  Here's the damage, as found by cmp(1).  I
haven't worked hard at analyzing what it is but every changed byte
started out as zero.  The new bytes don't smell like ASCII (but I'm
not great at recognizing ASCII in decimal).

Any idea why Windows makes this unprovoked attack on installation
sticks?  It sure is inconvenient.

Since Microsoft is unlikely to fix this Windows bug, would it be 
worthwhile for Fedora to take countermeasures?  For example, ignore 
exactly those bytes that Windows damages?

$ sudo cmp -l Fedora-Workstation-Live-x86_64-28_Beta-1.3.iso /dev/sdg
  61462533   0 377
  61462534   0 377
  61471313   0 377
  61471314   0 377
  61471315   0 377
  61471316   0 377
  61472773   0 377
  61472774   0 377
  61481553   0 377
  61481554   0 377
  61481555   0 377
  61481556   0 377
  61483073   0 102
  61483074   0  40
  61483076   0 111
  61483078   0 156
  61483080   0 146
  61483082   0 157
  61483084   0  17
  61483086   0 162
  61483087   0 162
  61483089   0 155
  61483091   0 141
  61483093   0 164
  61483095   0 151
  61483097   0 157
  61483101   0 156
  61483105   0   1
  61483106   0 123
  61483108   0 171
  61483110   0 163
  61483112   0 164
  61483114   0 145
  61483116   0  17
  61483118   0 162
  61483119   0 155
  61483121   0  40
  61483123   0 126
  61483125   0 157
  61483127   0 154
  61483129   0 165
  61483133   0 155
  61483135   0 145
  61483137   0 123
  61483138   0 131
  61483139   0 123
  61483140   0 124
  61483141   0 105
  61483142   0 115
  61483143   0 176
  61483144   0  61
  61483145   0  40
  61483146   0  40
  61483147   0  40
  61483148   0  26
  61483150   0 103
  61483151   0 223
  61483152   0 142
  61483153   0 215
  61483154   0 114
  61483155   0 215
  61483156   0 114
  61483159   0 224
  61483160   0 142
  61483161   0 215
  61483162   0 114
  61483163   0   2
  61499393   0  56
  61499394   0  40
  61499395   0  40
  61499396   0  40
  61499397   0  40
  61499398   0  40
  61499399   0  40
  61499400   0  40
  61499401   0  40
  61499402   0  40
  61499403   0  40
  61499404   0  20
  61499406   0 103
  61499407   0 223
  61499408   0 142
  61499409   0 215
  61499410   0 114
  61499411   0 215
  61499412   0 114
  61499415   0 224
  61499416   0 142
  61499417   0 215
  61499418   0 114
  61499419   0   2
  61499425   0  56
  61499426   0  56
  61499427   0  40
  61499428   0  40
  61499429   0  40
  61499430   0  40
  61499431   0  40
  61499432   0  40
  61499433   0  40
  61499434   0  40
  61499435   0  40
  61499436   0  20
  61499438   0 103
  61499439   0 223
  61499440   0 142
  61499441   0 215
  61499442   0 114
  61499443   0 215
  61499444   0 114
  61499447   0 224
  61499448   0 142
  61499449   0 215
  61499450   0 114
  61499457   0 102
  61499458   0 107
  61499460   0 165
  61499462   0 151
  61499464   0 144
  61499468   0  17
  61499470   0 377
  61499471   0 377
  61499472   0 377
  61499473   0 377
  61499474   0 377
  61499475   0 377
  61499476   0 377
  61499477   0 377
  61499478   0 377
  61499479   0 377
  61499480   0 377
  61499481   0 377
  61499482   0 377
  61499485   0 377
  61499486   0 377
  61499487   0 377
  61499488   0 377
  61499489   0   1
  61499490   0 111
  61499492   0 156
  61499494   0 144
  61499496   0 145
  61499498   0 170
  61499500   0  17
  61499502   0 377
  61499503   0 145
  61499505   0 162
  61499507   0 126
  61499509   0 157
  61499511   0 154
  61499513   0 165
  61499517   0 155
  61499519   0 145
  61499521   0 111
  61499522   0 116
  61499523   0 104
  61499524   0 105
  61499525   0 130
  61499526   0 105
  61499527   0 176
  61499528   0  61
  61499529   0  40
  61499530   0  40
  61499531   0  40
  

initramfs: kernel update adds unwanted driver?

[Grant Edwards]

On Fedora 27 with kernel recently updated to 4.15.15-300.fc27.i686, I
ran into a problem when I installed a new version of a driver (we'll
call "foo") in /lib/modules/$(uname -r)/kernel/drivers/[...].

Doing a "rmmod foo; modprobe foo" loads the new driver and everything
works great.  However, rebooting loads a 15-year old version of the
driver (which doesn't work great).

lsinitrd shows that the 15-year old driver is present in the
initramfs.  On a clean install of Fedora 27 (running an identical
kernel version) the initramfs does not contain the "foo" driver at
all.

Did the kernel upgrade process muck up the initramfs by adding the old
version of the "foo" driver?  The "old" version is the one that's
shipped with the kernel package, but I've never seen it included in
the initramfs before.

What's the best way to remove the old, broken driver from the
initramfs so that the driver in the root filesystem is used on boot?

Is there a way to prevent the kernel update process from adding the
driver back to the initramfs the next time a kernel is updated?

Alternatively, I suppose I could add a "service" that runs at boot
time and does a "rmmod foo; modrobe foo", but that seems like the
wrong way to fix this...

-- 
Grant
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Earl Ramirez]

> 
> Does "192.168.1.0/255.255.255.0" work?!
> 
> The prefix is usually "24" not "255.255.255.0".

Yes, that also works NFS supports both contiguous mask length and
prefix.

- name: Earl Ramirez
  e-mail: earlarami...@gmail.com
  

signature.asc
Description: This is a digitally signed message part
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Earl Ramirez]

On Fri, 2018-04-13 at 15:34 -0400, Bob Goodwin wrote:
> .
> 
> I am attempting to set up an NFS server on a new Fedora 27 computer
> I 
> have assembled using instructions I found, "Fedora 
> Administration_Guide_Draft/NFS" and I am having a problem accessing
> it.
> 
> $ cat /etc/exports
> /var/ftp/pub  192.168.1.0/255.255.255.0(ro)
> /home/public  192.168.1.0/255.255.255.0(rw)
> 
> var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_subtree_check)
> 
> /var/ftp/pub 
> 192.168.54.0/255.255.255.0(ro,sync,no_wdelay,no_subtree_check,nohide)
> 
> Then from the client I get a refusal:
> 
> # mount 192.168.1.86:/home/public  /mnt/test/
> mount.nfs: Connection refused
> 
> There is an ethernet path between them on my lan, ssh works from
> each 
> computer to the other ...
> 
> Perhaps a problem with bind, I don't know how to troubleshoot this, 
> would appreciate suggestions.
> 
> Bob
> 
> 

Are you able to mount the share locally on the server that is hosting
the shares?



-- 



- name: Earl Ramirez
  e-mail: earlarami...@gmail.com
  

signature.asc
Description: This is a digitally signed message part
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

foxit reader

[ToddAndMargo]

Hi All,

Anyone know of an RPM out there for Foxit Reader?

https://www.foxitsoftware.com/downloads/

-T
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Joseph Loo]

On 04/13/2018 07:11 PM, Earl Ramirez wrote:
> On Fri, 2018-04-13 at 15:34 -0400, Bob Goodwin wrote:

>> $ cat /etc/exports
>> /var/ftp/pub  192.168.1.0/255.255.255.0(ro)
>> /home/public  192.168.1.0/255.255.255.0(rw)
>>
>> var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_subtree_check)
>>
>> /var/ftp/pub 
>> 192.168.54.0/255.255.255.0(ro,sync,no_wdelay,no_subtree_check,nohide)
>>
>> Then from the client I get a refusal:
>>
>> # mount 192.168.1.86:/home/public  /mnt/test/
>> mount.nfs: Connection refused
>>
>> There is an ethernet path between them on my lan, ssh works from
>> each 
>> computer to the other ...
>>
>> Perhaps a problem with bind, I don't know how to troubleshoot this, 
>> would appreciate suggestions.
>>
>> Bob
>>
>>
> 
> Are you able to mount the share locally on the server that is hosting
> the shares?
> 
> 
> 
> 
> 
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> 

are you missing a "/" on va/ftp.pub on your 4th line on the cat
/etc/exports?

Try a showmount -e 192.168.1.86

this will help determine if the directories are actually exported.
Don't forget to restart the nfs server whenever you do changes on the
/etc/exports.
-- 
Joseph Loo
j...@acm.org



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Windows eats Fedora installation USB stick

[Robert Nichols]

On 04/13/2018 03:17 PM, ToddAndMargo wrote:

And be careful with THAT operating system, shutdown and
reboot are suspend and not shutdown.  You have to turn
"Fast Boot" off and do a real shutdown to get it to
take.


Actually, "restart" _always_ does a full shutdown and restart regardless of the 
"Fast Boot" setting.

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: HW and SW threats: how to block?

[home user via users]

> ...I think crypto-currency is stupid...
I agree.  That's why some people and organizations use coin mining.  They get 
us to do all that grunt work for them.  They use our cpu, our gpu, our 
electricity, and our money, and wear out our hardware.

> Also, I have always been suspicious...
I agree.  I have my browsers and e-mail clients set to not download/install 
anything without my permission.  But I'm human, and I make mistakes.  I even 
try to shut down automatic updating if/when I can figure out how to do that 
(sometimes very difficult for home users such as me).

> ...ClamAV
I didn't realize that ClamAV is available for Linux.  So I looked it up in 
wikipedia (I know, it's not the most authoritative place to look).  Overall, 
it's effectiveness is so-so.  I'll dig into ClamAV more later.

> ...Chrootkit...
I assume you mean "chkrootkit".  I've been running that at least weekly for 
about five years.  I learned about it from members of this list.

> ...RKhunter...
I've been running that at least weekly for about five years.  I learned about 
it from members of this list.

> ...BleachBit...
I didn't realize that this is available for Linux.  I'll dig into it more later.

> ...There is no magic "cure-all"...
I agree, and I said this in the first sentence of the "question" part of my 
original post.  Everything said in that last paragraph are things I'm already 
doing.  I've been doing patches ("dnf upgrade --refresh") weekly for about 5 
years, and I upgrade to the next Fedora release about every 6 months.

> ...if you don't allow your browser or mail client to install software...
I've been following this advice for years.

> ...top 7...
(1,3,5,7)  I've been following these for years.
(2-sandboxing and vm)  I really need to learn about these.
(4-firewall)  I think I've got this set properly, but I'm not sure.  Firewalls 
seem v-e-r-y complicated, and are over my head.  I'm trusting that the thread I 
started last summer about hundreds of external attempts to remotely log in to 
my work station fixed this.
(6-"ps -aux")  I did this a short while ago, but not as root.  256 processes!  
...most unfamiliar to me.  It would take a real expert to recognize something 
that doesn't belong.

Thank-you for the discussion and suggestions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Windows eats Fedora installation USB stick

[ToddAndMargo]

On 04/13/2018 08:08 PM, Robert Nichols wrote:

On 04/13/2018 03:17 PM, ToddAndMargo wrote:

And be careful with THAT operating system, shutdown and
reboot are suspend and not shutdown.  You have to turn
"Fast Boot" off and do a real shutdown to get it to
take.


Actually, "restart" _always_ does a full shutdown and restart regardless 
of the "Fast Boot" setting.




Indeed it is suppose to.  Problem with Windows "I Can't Count" is that
each "build" is separate release.  Restart has not worked for me to
get into bios or to make disabling "fast boot" stick until I
shutdown from from the command line:

   shutdown /r f/ /t 00

which is the "Windows Universal fix all".
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Bob Goodwin]

On 04/13/18 16:57, Rick Stevens wrote:

By default F27 uses NFSv4. The access is far more restrictive. If you're
NFS mounting a filesystem as a normal user on the client, then you have
to make sure that user has the same UID and GID on the server and has
access to that exported directory.




If you're mounting it as root on the client (as seems to be true by the
"#" in the example command), make sure you add "no_root_squash" to the
export at the server:

/home/public192.168.1.0/24(rw,no_root_squash)

Otherwise the server will try to demote the root user down to the
anonymous user, who probably doesn't have R/W access to /home/public
(or whatever export you've specified).

Make sense?


.

Just adding "no_root_squash" did not help, it still reports refused.

Sometimes it seems nothing is ever easy, at least with NFS.

Thanks,


--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-27/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Joseph Loo]

On 04/13/2018 04:01 PM, Ed Greshko wrote:
> On 04/14/18 06:16, Bob Goodwin wrote:
>> On 04/13/18 16:57, Rick Stevens wrote:
>>> By default F27 uses NFSv4. The access is far more restrictive. If you're
>>> NFS mounting a filesystem as a normal user on the client, then you have
>>> to make sure that user has the same UID and GID on the server and has
>>> access to that exported directory.
>>>
>>
>>> If you're mounting it as root on the client (as seems to be true by the
>>> "#" in the example command), make sure you add "no_root_squash" to the
>>> export at the server:
>>>
>>> /home/public    192.168.1.0/24(rw,no_root_squash)
>>>
>>> Otherwise the server will try to demote the root user down to the
>>> anonymous user, who probably doesn't have R/W access to /home/public
>>> (or whatever export you've specified).
>>>
>>> Make sense?
>>
>> .
>>
>> Just adding "no_root_squash" did not help, it still reports refused.
>>
>> Sometimes it seems nothing is ever easy, at least with NFS.
>>
>>
> 
> I hadn't set up an nfs server in a while so I did the following.
> 
> Server Side:
> 
> Created /etc/exports with the following contents
> 
> /var/ftp  192.168.1.0/24(rw,async,no_wdelay,no_root_squash)
> 
> Checked the nfs box in the firewalld settings
> 
> systemctl enable nfs-service (only need that if you want 
> the
> service started at boot)
> systemctl start nfs-service
> 
> Client side:
> 
> mount 192.168.1.191:/var/ftp /mnt
> 
> Result:
> 
> [root@meimei mnt]# df -T | grep mnt
> 192.168.1.191:/var/ftp nfs4   29098240  17908736    9688320  65% /mnt
> 
> I suppose, that this point,  you should run on the Server side
> 
> systemctl status nfs-server
> 
> 
> 
> 
> 
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> 
Have you tried showmounts -e 192.168.1.x to see if the nfs server is
exporting the directories.

e.g.
I get howmount -e taurus
Export list for taurus:
/export   *
/export/home1 127.0.0.0/8,192.168.21.0/24
/export/home0 127.0.0.0/8,192.168.21.0/24


My exports looks like this:

/export *(fsid=0,crossmnt,rw,root_squash,sync,no_subtree_check)
/export/home0   192.168.21.0/24(rw,root_squash,sync,no_subtree_check)
127.0.0.0/8(rw,root_squash,sync,no_subtree_check)
/export/home1   192.168.21.0/24(rw,root_squash,sync,no_subtree_check)
127.0.0.0/8(rw,root_squash,sync,no_subtree_check)

I believe you need the first line since nfs version 3


-- 
Joseph Loo
j...@acm.org



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Ed Greshko]

On 04/14/18 06:16, Bob Goodwin wrote:
> On 04/13/18 16:57, Rick Stevens wrote:
>> By default F27 uses NFSv4. The access is far more restrictive. If you're
>> NFS mounting a filesystem as a normal user on the client, then you have
>> to make sure that user has the same UID and GID on the server and has
>> access to that exported directory.
>>
>
>> If you're mounting it as root on the client (as seems to be true by the
>> "#" in the example command), make sure you add "no_root_squash" to the
>> export at the server:
>>
>> /home/public    192.168.1.0/24(rw,no_root_squash)
>>
>> Otherwise the server will try to demote the root user down to the
>> anonymous user, who probably doesn't have R/W access to /home/public
>> (or whatever export you've specified).
>>
>> Make sense?
>
> .
>
> Just adding "no_root_squash" did not help, it still reports refused.
>
> Sometimes it seems nothing is ever easy, at least with NFS.
>
>

I hadn't set up an nfs server in a while so I did the following.

Server Side:

Created /etc/exports with the following contents

/var/ftp  192.168.1.0/24(rw,async,no_wdelay,no_root_squash)

Checked the nfs box in the firewalld settings

systemctl enable nfs-service (only need that if you want the
service started at boot)
systemctl start nfs-service

Client side:

mount 192.168.1.191:/var/ftp /mnt

Result:

[root@meimei mnt]# df -T | grep mnt
192.168.1.191:/var/ftp nfs4   29098240  17908736    9688320  65% /mnt

I suppose, that this point,  you should run on the Server side

systemctl status nfs-server



-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Mark C. Allman]

On 04/13/2018 07:01 PM, Ed Greshko wrote:
> On 04/14/18 06:16, Bob Goodwin wrote:
>> On 04/13/18 16:57, Rick Stevens wrote:
>>> By default F27 uses NFSv4. The access is far more restrictive. If you're
>>> NFS mounting a filesystem as a normal user on the client, then you have
>>> to make sure that user has the same UID and GID on the server and has
>>> access to that exported directory.
>>>
>>> If you're mounting it as root on the client (as seems to be true by the
>>> "#" in the example command), make sure you add "no_root_squash" to the
>>> export at the server:
>>>
>>> /home/public    192.168.1.0/24(rw,no_root_squash)
>>>
>>> Otherwise the server will try to demote the root user down to the
>>> anonymous user, who probably doesn't have R/W access to /home/public
>>> (or whatever export you've specified).
>>>
>>> Make sense?
>> .
>>
>> Just adding "no_root_squash" did not help, it still reports refused.
>>
>> Sometimes it seems nothing is ever easy, at least with NFS.
>>
>>
> I hadn't set up an nfs server in a while so I did the following.
>
> Server Side:
>
> Created /etc/exports with the following contents
>
> /var/ftp  192.168.1.0/24(rw,async,no_wdelay,no_root_squash)
>
> Checked the nfs box in the firewalld settings
>
> systemctl enable nfs-service (only need that if you want 
> the
> service started at boot)
> systemctl start nfs-service
>
> Client side:
>
> mount 192.168.1.191:/var/ftp /mnt
>
> Result:
>
> [root@meimei mnt]# df -T | grep mnt
> 192.168.1.191:/var/ftp nfs4   29098240  17908736    9688320  65% /mnt
>
> I suppose, that this point,  you should run on the Server side
>
> systemctl status nfs-server
>
This was probably already suggested, but:
-- on the server side, run "sudo netstat -antp | grep 111" to see if the
nfs server is there & listening.
-- on the client side, try the classic "telnet  111" to see
if you can at least connect.



*Mark C. Allman, PMP, CSM*
Founder, See How You Ski, www.seehowyouski.com 
Sr. Project Manager, Allman Professional Consulting, Inc.,
www.allmanpc.com 
617-947-4263, Twitter: @allmanpc

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: NFS server setup -

[Tom H]

On Fri, Apr 13, 2018 at 3:34 PM, Bob Goodwin  wrote:
>
> I am attempting to set up an NFS server on a new Fedora 27 computer I have
> assembled using instructions I found, "Fedora
> Administration_Guide_Draft/NFS" and I am having a problem accessing it.
>
> $ cat /etc/exports
> /var/ftp/pub  192.168.1.0/255.255.255.0(ro)
> /home/public  192.168.1.0/255.255.255.0(rw)
>
> var/ftp/pub 192.168.54.0/255.255.255.0(ro,sync,no_subtree_check)
>
> /var/ftp/pub
> 192.168.54.0/255.255.255.0(ro,sync,no_wdelay,no_subtree_check,nohide)
>
> Then from the client I get a refusal:
>
> # mount 192.168.1.86:/home/public  /mnt/test/
> mount.nfs: Connection refused
>
> There is an ethernet path between them on my lan, ssh works from each
> computer to the other ...

Does "192.168.1.0/255.255.255.0" work?!

The prefix is usually "24" not "255.255.255.0".
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Problems with ASUS MB and CPU temperature

[GianPiero Puccioni]

Hi,

I have recently installed Linux on my PC and I have some problems with the CPU 
temperature, while everything works fine under Win10.


The MB is an Asus  STRIX B250F - The chipset is reported by hwinfo as
"Intel 200 Series PCH LPC Controller (B250)".

The problem is that it seems that the fans are not controlled and the CPU temp 
get very high, and during some tasks (like a "dnf update" with several packages)

I get a "Temp critical CPU throttled" message.

The sensors command gave little help at start with the default installation.
On line I found some advice and I tried using the grub option 
"acpi_enforce_resources=lax" and loading the "nct6775" module which reports

"Found NCT6793D or compatible chip at 0x2e:0x290" in dmesg.

With this sensors gave more info (Temp and Fans) but some was still missing 
unfortunately the problem remains.


Does anyone knows what is the proper module to load for this chipset?

Or if there is something else to be done.

Thanks,

GianPiero
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: HW and SW threats: how to block?

[Eddie O'Connor]

I don't know if this will top post or not since I'm replying via cellphone.
But I'd like to chime in on a few points.

First off? I think crypto-currency is stupid. There, I said it. Yes it's my
opinion, and I know there are those who will disagree with me and I'm fine
with that. But it still doesn't change the fact that I think it's stupid.
Bear with me for a moment: you basically run your machine night and day,
trying to decipher some code...and THATS supposed to gain you this digital
"coin" that is the equivalent to REAL MONEY? has NO ONE thought this
through? How can money be MADE by the consuming of CPU cycles!? LoL! I'm
sorry, I'm just a sarcastic guy from NY, but to me? it's HILARIOUS.

Also, I have always been suspicious of ANYTHING that tries to install or
run ANYTHING without my explicit consent! This was one of the reasons why I
left Windows to begin with! How many of you remember the times you'd be
working on something important...only to have your system slow to a crawl
while "Windows Installs Important Updates"? and then, not even being able
to do anything until it was done or until it prompted you to restart your
machine? Supposedly those days are over right? LoL! If I open Firefox or
Midori and I notice anything strange happening? like my system becomes
incredibly slow? I'd shut down the browser...and run ClamAVthen
RKhunterthen Chrootkit. That's never happened to me since I don't allow
things to run in FF without prompting me first...(as in some sites
informing me that if I want to see the embedded video on their page I have
to enable Adobe Flash, which I don't do. I prefer to read the content I
came for, and then leave!) I also run BleachBit every month. And if I see
any file I don't recognize? or that I know for a fact doesn't belong on my
hard drive? it gets deleted. I know I might sound like a paranoid tin-foil
hat wearin' conspiracy-theorist, but with the revelations of FBand
other recent exposures of personal data being stolen, hacked, sold,
brokered, or otherwise being out of the control of "We The People", I think
I would prefer to err on the side of caution.

And finally, to try to answer the OP's question: There is no magic
"cure-all" when it comes to protecting your Linux systems, except
determination, and diligence. When you have a Linux machine, whether it's a
serverlaptopor desktop, you have to constantly do administration on
it. And while it might sound tedious, the alternative is loss of control of
your PC. And you can't be "lazy" when it comes to protecting your
machine(s). No leaving updates from last month sitting in your Software
center. No ignoring articles that warn you of upcoming or existing threats,
do your homework, and focus on always being safe while online...no clicking
on anything that you aren't sure is safe. No opening emails that don't come
from sanctioned and verified emails. (For Pete's sake use a
spamblocker!or else create rules for your inbox allowing ONLY those
email addresses. It may sound hard but once you have a system and methods
in place? You'll find it's a lot easier than you think!!

Just my two cents

On Thu, Apr 12, 2018, 7:05 PM Rick Stevens  wrote:

> On 04/12/2018 09:53 AM, Tim via users wrote:
> > Allegedly, on or about 12 April 2018, home user via users sent:
> >> Ad-blockers are not sufficient.  So let's please get back to the
> >> original question.  There are several coin-mining blockers available
> >> for Firefox.  Based on your experience, which is most effective?
> >
> > I would hazard a guess that script and Flash blockers would kill them.
>
> And again, if you don't allow your browser or mail client to install
> software (which is a spectacularly bad idea in the first place) and
> you're careful about which links you click and which packages you
> download and install, it's sort of a moot point.
> --
> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
> - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
> --
> -   UNIX is actually quite user friendly.  The problem is that it's  -
> -  just very picky of who its friends are!   -
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

[389-users] Announcing 389 Directory Server 1.4.0.7

[Mark Reynolds]

389 Directory Server 1.4.0.7

The 389 Directory Server team is proud to announce 389-ds-base
version 1.4.0.7

Fedora packages are available on Fedora 28 and 29(rawhide).

Rawhide(F29)

https://koji.fedoraproject.org/koji/taskinfo?taskID=26347575


F28

https://koji.fedoraproject.org/koji/taskinfo?taskID=26348320


https://bodhi.fedoraproject.org/updates/FEDORA-2018-7082fefd2e


The new packages and versions are:

  * 389-ds-base-1.4.0.7-1

Source tarballs are available for download at Download
389-ds-base Source



  Highlights in 1.4.0.7

  * Bug fixes and merging of srvcore package


  Installation and Upgrade

See Download  for
information about setting up your yum repositories.

To install, use *yum install 389-ds* yum install 389-ds After install
completes, run *setup-ds-admin.pl* if you have 389-admin installed,
otherwise please run *setup-ds.pl* to set up your directory server.

To upgrade, use *yum upgrade* yum upgrade After upgrade completes, run
*setup-ds-admin.pl -u* if you have 389-admin installed, otherwise please
run *setup-ds.pl* to update your directory server/admin
server/console information.

See Install_Guide
 for more
information about the initial installation, setup, and upgrade

See Source 
for information about source tarballs and SCM (git) access.


  Feedback

We are very interested in your feedback!

Please provide feedback and comments to the 389-users mailing list:
https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.org

If you find a bug, or would like to see a new feature, file it in our
Pagure project: https://pagure.io/389-ds-base

  * Bump version to 1.4.0.7
  * Ticket 49477 - Missing pbkdf python
  * Ticket 49552 - Fix the last of the build issues on F28/29
  * Ticket 49522 - Fix build issues on F28
  * Ticket 49631 - same csn generated twice
  * Ticket 49585 - Add py3 support to password test suite : part-3
  * Ticket 49585 - Add py3 support to password test suite : part-2
  * Ticket 48184 - revert previous patch around unuc-stans shutdown crash
  * Ticket 49585 - Add py3 support to password test suite
  * Ticket 46918 - Fix compiler warnings on arm
  * Ticket 49601 - Replace HAVE_SYSTEMD define with WITH_SYSTEMD in svrcore
  * Ticket 49619 - adjustment of csn_generator can fail so next
generated csn can be equal to the most recent one received
  * Ticket 49608 - Add support for gcc/clang sanitizers
  * Ticket 49606 - Improve lib389 documentation
  * Ticket 49552 - Fix build issues on F28
  * Ticket 49603 - 389-ds-base package rebuilt on EPEL can’t be
installed due to missing dependencies
  * Ticket 49593 - NDN cache stats should be under the global stats
  * Ticket 49599 - Revise replication total init status messages
  * Ticket 49596 - repl-monitor.pl fails to find db tombstone/RUV entry
  * Ticket 49589 - merge svrcore into 389-ds-base
  * Ticket 49560 - Add a test case for extract-pemfiles
  * Ticket 49239 - Add a test suite for ds-replcheck tool RFE
  * Ticket 49369 - merge svrcore into 389-ds-base

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org