Re: Is i686 dead and gone??
x86 is an alternative architecture now. You'll need to download the proper ISO file to install the OS on 32 bit hardware. Here's a mirror which contains the proper ISO files. http://mirror.math.princeton.edu/pub/fedora-secondary/releases/ On 01/01/2018 02:12 PM, Beartooth wrote: > I have a Thinkpad T42 which I haven't used for so long I don't > remember what's on it. When I try to boot it, it complains that it can't, > and asks me to use a "kernel appropriate for your CPU." > > > My main purpose is to get it usable again, preferably with Fedora > 27, if that's possible. (I run F27 on all our other machines.) > > I'd prefer to examine it first, if there's a way. If I run a USB > cable between it and a F27 PC, can I then mount it as if it were a > storage medium and display the contents?? > > Fwiw, it mounted and opened UBCD; but when I chose "CPU Info" > from UBCD's menu, it flashed up something about "stress" -- and then went > black. > 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: Device or resource busy when trying to do a software update
On Tue, 02 Jan 2018 20:06:24 +0100 Martin Wagner wrote: > Since some time back I can no longer do a software update using Gnome > Software (version 3.24.3) on my Fedora 26 desktop. Using 'yum update' > works fine. What happens is that when I hit the 'Restart & Update' > button I'm not sure I understand: Do you use the command line update system (yum/dnf) back to back with the Gnome Software upgrade routine? IINM Gnome software has its own update system independently from tools like dnf ... > the system is going down and there are some log messages that > flicker by really quickly. Then at bootup after unlocking the disk > there are again some log messages that flicker by quickly. What I > managed to see from the messages is the the phrase 'Device or resource > busy'. After that the system reboots and comes up normally but without > any software updates applied. > > I'll attach the end of journald when the system is going down first > time. There are some error, but I don't know what to make of them... > > My biggest concern is not really about software update, as yum update > works fine, but about doing a fedup to Fedora 27 at some point. That > would probably not work? > > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 > msg='unit=systemd-fsck@dev-disk-by\x2duuid-d1a72941\x2deb0a\x2d4d82\x2d96ae\x2df837c572b875 > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > systemd[1]: Stopped File System Check on > /dev/disk/by-uuid/d1a72941-eb0a-4d82-96ae-f837c572b875. > systemd[1]: Removed slice system-systemd\x2dfsck.slice. > systemd[1]: Stopped target Local File Systems (Pre). > systemd[1]: Stopped Create Static Device Nodes in /dev. > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using > dmeventd or progress polling... > systemd[1]: Stopped Remount Root and Kernel File Systems. > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > lvm[1124]: 3 logical volume(s) in volume group "fedora" unmonitored > systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd > or progress polling. > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > juno systemd[1]: Stopping LVM2 metadata daemon... > juno lvmetad[839]: Failed to accept connection errno 11. > systemd[1]: Stopped LVM2 metadata daemon. > audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=lvm2-lvmetad comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > juno systemd-cryptsetup[1099]: Failed to deactivate: Device or resource busy > systemd[1]: > systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: > Control process exited, code=exited status=1 > systemd[1]: Stopped Cryptography Setup for > luks-862c1862-0497-442f-9442-a7cd6a73b46c. > audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 > msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=failed' > systemd[1]: > systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: > Unit entered failed state. > systemd[1]: > systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c.service: > Failed with result 'exit-code'. Looks like cryptsetup cannot close an encrypted partition. Did you try to log out from your X (Gnome?) before the upgrade? Then switch to a tty (can be reached via CTRL-ALT-Fx). From there, as root, two commands: # dnf check-update # dnf upgrade (Sorry, I have no idea about how yum works ... ) Or https://www.happyassassin.net/2016/10/04/x-crash-during-fedora-update-when-system-has-hybrid-graphics-and-systemd-udev-is-in-update/ maybe starting with this line: "If you don’t use GNOME, you can use the offline update system via pkcon, like this:" HTH Wolfgang > systemd[1]: Reached target Unmount All Filesystems. > systemd[1]: Removed slice system-systemd\x2dcryptsetup.slice. > kernel: kauditd_printk_skb: 102 callbacks suppressed > kernel: audit: type=1130 audit(1514917562.780:129): pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=systemd-cryptsetup@luks\x2d862c1862\x2d0497\x2d442f\x2d9442\x2da7cd6a73b46c
Re: USB Broadband mobile
On 2 January 2018 at 13:18, Patrick Dupre wrote: > Hello, > > When I try to add a connection, I get > > No plugin supported adding this connection (by using Network Manager) > > > nmcli dev > DEVICE TYPE STATE CONNECTION > virbr0 bridgeconnected virbr0 > ttyUSB4 gsm disconnected -- > > [...] > mmcli -m 0 --simple-connect="pin=6837,apn=3G" > error: couldn't connect the modem: 'GDBus.Error:org.freedesktop. > ModemManager1.Error.MobileEquipment.NetworkPuk: Device is locked: > 'ph-net-puk'' > > > > Any idea? > https://en.wikipedia.org/wiki/Personal_unblocking_code -- George N. White III Head of St. Margarets Bay, Nova Scotia ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Can't create volatile files... -- What is "gluster"?
On Tue, 2018-01-02 at 22:26 -0800, Samuel Sieb wrote: > On 01/02/2018 10:19 PM, Jonathan Ryshpan wrote: > > Can someone tell me what this is about? A message in the journal > > shortly after a boot reads: > > Failed to start Create Volatile Files and Directories > > which leads me to the following systemd status query. > > > > Jan 02 21:34:31 amito.localdomain systemd-tmpfiles[860]: > > [/usr/lib/tmpfiles.d/gluster.conf:2] Unknown user 'gluster'. > > gluster is a distributed file system. I wouldn't expect it to be > installed by default and somehow there's a config file installed > without > the user being created. > > What is the output of the following two commands? > > rpm -qf /usr/lib/tmpfiles.d/gluster.conf > > rpm -qa | grep gluster I don't remember installing it. I've checked the installation on another machine on which I recently installed Fedora-27 on bare hardware; $ rpm -qa | grep gluster doesn't show anything, so I must have done something to cause the gluster filesystem to be installed. Is there any reason not to remove it? On the other hand, is gluster useful for some particular purpose? For example, can it be configured as a backup system to protect a computer against ransomware, etc? Here are the results of the commands you asked about: $ rpm -qf /usr/lib/tmpfiles.d/gluster.confglusterfs-3.12.4- 1.fc27.x86_64 $ rpm -qa | grep gluster glusterfs-cli-3.12.4-1.fc27.x86_64 glusterfs-libs-3.12.4-1.fc27.x86_64 qemu-block-gluster-2.10.1-2.fc27.x86_64 glusterfs-api-3.12.4-1.fc27.x86_64 glusterfs-fuse-3.12.4-1.fc27.x86_64 glusterfs-client-xlators-3.12.4-1.fc27.x86_64 glusterfs-3.12.4-1.fc27.x86_64 libvirt-daemon-driver-storage-gluster-3.7.0-3.fc27.x86_64 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Can't create volatile files... -- What is "gluster"?
On Wed, 03 Jan 2018 10:17:24 -0800 Jonathan Ryshpan wrote: > Is there any reason not to remove it? If you do an "dnf erase gluster" you'll probably see if there is a reason to not remove it when it tries to take stuff you do you with it :-). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Device or resource busy when trying to do a software update
On Wed, 2018-01-03 at 18:45 +0100, Wolfgang Pfeiffer wrote: > On Tue, 02 Jan 2018 20:06:24 +0100 > Martin Wagner wrote: > > > Since some time back I can no longer do a software update using > > Gnome > > Software (version 3.24.3) on my Fedora 26 desktop. Using 'yum > > update' > > works fine. What happens is that when I hit the 'Restart & Update' > > button > > I'm not sure I understand: Do you use the command line update > system (yum/dnf) back to back with the Gnome Software upgrade > routine? > IINM Gnome software has its own update system independently from > tools > like dnf ... > I've used 'yum update' to update the system because the Gnome Software update routine didn't work any more > Looks like cryptsetup cannot close an encrypted partition. > > Did you try to log out from your X (Gnome?) before the upgrade? Then > switch to a tty (can be reached via CTRL-ALT-Fx). From there, as > root, > two commands: > > # dnf check-update > # dnf upgrade Yes, that works fine, but that didn't involve any kind of restart like the Gnome Software update routine does. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Fedora27: Firefox freezes
On 01/01/18 20:53, Ed Greshko wrote: On 01/02/18 04:42, Terry Barnaby wrote: On 01/01/18 20:38, Joe Zeff wrote: On 01/01/2018 12:15 PM, Terry Barnaby wrote: I don't think it is that one. The display is fine all other applications run fine. Its just that the Firefox tab does not load any content for a while. I can still operate Firefox clicking on things etc, but no tab will update its contents. Have you tried the Firefox Help Site? This may not be Linux related, and it doesn't hurt to ask. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Will do so, just trying to find out if it is well known on Fedora/KDE/Plasma or if it could be a one off due to something in my setup/config somewhere. FWIW, I do not use FF extensively. It is configured to use a proxy and I only use it to access US based media sites. When I do use it I've not noticed any problems. You mention your home directory is NFS mounted. You may want to consider moving and creating a symbolic link to ~/.cache/mozilla to local storage. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Hi I tried symbolically linking ~/.cache/mozilla to local storage. This had no effect. I have also seen some strange freezing on a separate F27 server. The SDDM login GUI was frozen. A ssh to the system would freeze. a web access to port 80 would timeout. NFS was still working, although the remote systems had NFS server UP/Down messages in the logs. Accessing a Mariadb MySql server on the system was fine though. A hard reset was needed. Very strange ... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: NetworkManager-wait-online is still utterly, and completely, broken
On 01/01/2018 03:09 AM, Roberto Ragusa wrote: > On 12/24/2017 10:00 PM, Chris Adams wrote: >> Once upon a time, Sam Varshavchik said: >>> I defy anyone to identify a tangible benefit that comes from >>> removing a static IP address from a port when it loses carrier, and >>> installing one only once a carrier is present. >> >> It is useful for systems with multiple interfaces, for example a desktop >> with wired and wifi, and different preference default routes out both >> (so if the wired goes down, traffic can still go out over the wifi). >> Anything acting like a router also needs this behavior, typically in >> conjuction with dynamic routing protocols. >> > > Routing fail over is not a good reason to totally unconfigure an interface, > especially on machines where there is nowhere else to send packets. > You should just change the default gw, maybe. As a network admin, I can see no reason to remove a fixed IP address from a NIC based on whether or not there's a carrier present. Even in the case of DHCP, unless the address lease expires between a disconnect and reconnect or there's pressure on the DHCP pool, most DHCP servers will try to give a client NIC the same IP address it had when it disconnected. Thus, even in those cases, the address "sticks". Route failover is a common thing to do. We have multiple uplinks on our routers, a primary and at least one backup with each uplink on a different ISP. If the primary goes down the router fails over to (one of) the secondary uplink(s) based on cost factors. However the primary is NOT deconfigured and its IP address remains assigned. If the primary uplink comes back up, then the routes fail back to it. This is standard practice. There's no need to remove its fixed IP address while it's down (and, in fact, would be a "bad idea"). Now, if we want one of the uplinks to remain unavailable, it is marked "administratively down" (in Cisco IOS-speak). For Linux, this would essentially be "ip link dev down". This takes the link down, but doesn't change the IP address for it. To remove the address, you'd "ip addr del dev ". Utterly unnecessary (and sort of stupid) if you do the "ip link" command. That's my stubborn, curmudgeon-y opinion. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - Never put off 'til tommorrow what you can forget altogether! - -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: NetworkManager-wait-online is still utterly, and completely, broken
Once upon a time, Rick Stevens said: > Now, if we want one of the uplinks to remain unavailable, it is marked > "administratively down" (in Cisco IOS-speak). For Linux, this would > essentially be "ip link dev down". This takes the link down, > but doesn't change the IP address for it. The difference is that Cisco can leave an interface configured but inactive, while Linux doesn't really support that. On a Cisco, the IP will still show up configured on the interface, but things like "show ip route " will not show it (it is not actually active when the interface is down). If you configure a Cisco interface for 10.0.0.1/24 and the link drops, the route for 10.0.0.0/24 is removed from the routing table. The interface shows down, but it is still watching for link to come back. When that happens, 10.0.0.0/24 is re-added to the routing table. On Linux, with static config, the route would still point out the down interface. If you shut the link down, the route will be removed, but then the interface will not come back automatically when link returns. You have to have some type of user-space active network management to get basic router-like behavior (functionally, that's how Cisco actually works, it's just all under the hood). -- Chris Adams ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Can't create volatile files... -- What is "gluster"?
On 01/03/2018 10:17 AM, Jonathan Ryshpan wrote: I don't remember installing it. I've checked the installation on another machine on which I recently installed Fedora-27 on bare hardware; $ rpm -qa | grep gluster doesn't show anything, so I must have done something to cause the gluster filesystem to be installed. Right, it's not part of the default install. Is there any reason not to remove it? On the other hand, is gluster useful for some particular purpose? For example, can it be configured as a backup system to protect a computer against ransomware, etc? It's a distributed network file system. It's kind of like nfs but with multiple servers and each file has multiple copies on different servers. Here are the results of the commands you asked about: $ rpm -qf /usr/lib/tmpfiles.d/gluster.conf glusterfs-3.12.4-1.fc27.x86_64 I suspect that it was brought in by qemu. Did you install virtualization packages? The strange part is that the user wasn't created. If that had happened, you would never have noticed that it was installed. I suggest filing a bug at https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=glusterfs with the info from your original message. It seems like a bug to me that it's expecting a user that it didn't create. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
