It takes ages to unmount an external disk on F26
by Paul Smith
Dear All,
I have just upgraded from F25 to F26.
I am using XFCE and Thunar as file manager, and when I try to unmount
an external disk (usb connected), it takes ages to unmount. Any ideas?
Thanks in advance,
Paul
6 years, 9 months
Failed update
by antonio montagnani
After proceeding to download updated packages after the usual dnf
system-upgrade download --refresh --releasever=26 --allowerasing I get
this warning. Is it safe to remove fwupdate-libs and related packages??
Errore: Transaction check error:
il file /usr/share/locale/en/libfwup.po entra in conflitto durante il
tentativo d'installazione di fwupdate-libs-8-2.fc26.i686 e
fwupdate-libs-8-2.fc26.x86_64
Tnx for help
--
Antonio M
Skype: amontag52
Linux Fedora F25 (Workstation Edition)
on Fujitsu Lifebook A512
http://lugsaronno.altervista.org
http://campingmonterosa.altervista.org
6 years, 9 months
Re: how to (re-?)construct grub menu?
by William
on Monday, July 10, Rick Stevens wrote:
> I'd suggest booting your system using a live CD (which will use nouveau)
> and see how it behaves. If it's OK, then simply comment out your
> blacklist stuff and rebuild grub to go back to nouveau.
After getting the system to boot from the May failures, I was quick to:
1. back up user data,
2. upgrade from f24 to f25, and
3. make an f25 live USB stick.
A week after recovery from the May problems, I discovered the hard drive
was failing. For a few days, I used the F25 live USB so I could
minimize use of the hard drive until the new drive arrived and I could
get the old one cloned, and get the new one installed. With the live
USB, screen resolution was coarse, and I experienced freeze-ups. So the
test that was suggested has been tried. Nouveau did poorly. That
coupled with Francois Patte's thread tell me to stick with the nVidia
proprietary driver.
thanks,
Bill.
6 years, 9 months
samba nautilus, duplicate file hangs won't cancel
by Chris Murphy
Fedora 26 Workstation and Server
In nautilus, I do a copy then paste to duplicate a file. I get a
status dialog that says duplicating but it gets stuck.
https://drive.google.com/open?id=0B_2Asp8DGjJ9dkxsY1E2RG5UUTg
And then then cancel also is stuck.
https://drive.google.com/open?id=0B_2Asp8DGjJ9a1daaVFGUDRlV3M
Nothing useful is in the journal either server or client side, but
this is smbstatus on the server:
https://paste.fedoraproject.org/paste/tDmSnX9f~NOyolNma0nKig
So I'm not really sure how to go about getting more information why
it's hung before filing a bug.
If I connect using smbclient and use scopy to duplicate the same file, it works.
-rw-r-----. 1 chris chris 1022032 Jul 8 14:49 'wl_apsta (copy).o'
-rw-r-----. 1 chris chris 13231072 Apr 15 19:02 wl_apsta.o
-rw-r-----. 1 chris chris 13231072 Jul 8 15:36 wl_apsta.o.copy2
[chris@f26s scratch]$
copy2 is the scopy one the works, and (copy) is the still hanging nautilus copy.
352 -rw-r-----. 1 chris chris 1022032 Jul 8 14:49 'wl_apsta (copy).o'
273 -rw-r-----. 1 chris chris 13231072 Apr 15 19:02 wl_apsta.o
353 -rw-r-----. 1 chris chris 13231072 Jul 8 15:36 wl_apsta.o.copy2
[chris@f26s scratch]$
Each failure copies exactly the same amount, the partial copy is the
same size in every attempt.
-rw-r-----. 1 chris chris 1022032 Jul 8 16:01 'wl_apsta (another copy).o'
-rw-r-----. 1 chris chris 1022032 Jul 8 15:55 'wl_apsta (copy).o'
If I switch to another file, same problem but a different partial file
size which is consistent for that particular file. And it also happens
when it's duplication from one directory to another, rather than in
the same directory.
Because scopy works, I'm thinking there might be a bug here...
Originally what I was testing was efficient duplicates:
https://wiki.samba.org/index.php/Server-Side_Copy#Btrfs_Enhanced_Server-S...
However, the problem happens whether 'vfs objects = btrfs' is set on
the server or not. If it is set, smbclient scopy does reflink copy the
file instantly.
--
Chris Murphy
6 years, 9 months
Upgrade from Fedora 24 to F25 - does it include firmware installed
directly to hardware devices, mainboard?
by Wolfgang Pfeiffer
Hi All
I have a strange behaviour since upgrading from F24 to F25 a few days
ago: the mini display port on my laptop doesn't connect me anymore to
the external second screen, a TV monitor. This connection worked like a
charm on F24. And the mini display port cable is OK: I can see pre-login
messages on the connected TV monitor while booting the system.
If you're interested in the machine where this happens, software etc:
here's a message to the xorg list from me, a few weeks ago, on how
adding a second display to a computer with F24 worked very well:
https://lists.x.org/archives/xorg/2017-May/058744.html
The reason for this message today is only what you see in the subject
line: I simply want to rule out bugs that have nothing to do with the OS
itself, or software - like drivers, xorg packages etc.
I know that during such upgrade processes firmware is getting updated,
but so far I thought this was a change to a runnning OS, and not one
with persistent changes to hardware.
Details:
xrandr detects the mini display port, and the connection to the monitor,
but the monitor stays black in 99% of cases.
xrandr output:
DisplayPort-1-0 connected (normal left inverted right x axis y axis)
1360x768 60.02 +
Please note the missing asterisk the last lines behind
"1360x768 60.02" that normally seems to indicate an established
connection to some external display.
journalctl often says:
/usr/libexec/gdm-x-session[4386]: (WW) RADEON(G0): drmWaitVBlank failed
for PRIME update: Invalid argument
Funny thing is: I have similar problems on a second OS (Debian 9) on the
same computer, on a separate disk - not necessarily with the same error
messages, but with similar results. Except that Debian even does not
detect the mini display port connection, contrary to Fedora 25. When I
saw that hours ago it made me wonder whether this is really just a
result of wrong settings, software/OS bugs, and not the result of some
new firmware installed to some hardware device.
If I can rule out this mentioned firmware issue I might try upgrade to
F26 and see if it helps.
Thanks a lot for your time
Wolfgang
6 years, 9 months
Re: DWA-192 Driver no Longer Compiles After Maintenance Update in F25
by Stephen Morris
On 7/8/17 4:43 AM, Rick Stevens wrote:
> On 07/07/2017 02:04 AM, Stephen Morris wrote:
>> On 7/6/17 8:50 AM, Rick Stevens wrote:
>>> On 07/05/2017 03:25 PM, Stephen Morris wrote:
>>>> On 6/24/17 4:03 PM, Samuel Sieb wrote:
>>>>> On 06/23/2017 05:56 PM, Stephen Morris wrote:
>>>>>> I am using a DWA-192 usb WiFi adapter in F25 hence I need to get
>>>>>> a driver from github to be compiled on my system so that I can use
>>>>>> the adapter. This driver compiled and worked quite happily with
>>>>>> kernel 4.9.9, not that the kernel version is necessarily an indicator
>>>>>> of compile success. It had been a month or more since I had apply any
>>>>>> system updates, so I did so two days ago, which as part of the update
>>>>>> updated the kernel to 4.11.5, and when dkms went to compile the
>>>>>> driver for the new kernel the compile failed with error messages
>>>>>> about implicit function definitions and messages about warnings
>>>>>> having been converted to errors.
>>>>> That's the problem with using out-of-tree drivers. Someone has to
>>>>> keep them up-to-date with kernel changes.
>>>>>
>>>>>> Does anyone know if there is an updated driver that will compile
>>>>>> with the current level of F25 or whether it has yet to be updated for
>>>>>> compatibility with F25 and hence I will need to continue to use
>>>>>> Ethernet internet access?
>>>>> https://github.com/xxNull-lsk/rtl8812AU has a recent commit that
>>>>> mentions kernel 4.11. I think
>>>>> https://wikidevi.com/wiki/D-Link_DWA-192 is suggesting that you have
>>>>> to modify one of the files to add your device id to it.
>>>> I downloaded the rtl8812AU driver even though its not necessarily the
>>>> right chipset (I believed the chipset in the DWA-192 was the rtl8814AU
>>>> chipset) but when I compiled it, it failed with the same errors.
>>>> It seems to me that the reason the source code is failing to compile
>>>> after the system update is that the compiler has been changed, as this
>>>> is the only reason I can see that source code that compiled fine before
>>>> the update won't compile after the update, unless the functions that the
>>>> compiler is rejecting as being implicitly defined, are functions that
>>>> were defined in the 4.9.9 kernel but have been removed sometime between
>>>> there and the 4.11.5 kernel.
>>> I just built the driver from https://github.com/xxNull-lsk/rtl8812AU on
>>> my machine with kernel 4.11.8-200.fc25.x86_64 with absolutely no
>>> problem. Note that you must have the kernel-devel RPM installed, and
>>> I'd recommend also having the elfutils-libelf-devel RPM installed.
>>>
>>> I didn't build it for DKMS use, just the regular build:
>>>
>>> [rick@prophead rtl8812AU-master]$ uname -r
>>> 4.11.8-200.fc25.x86_64
>>>
>>> [rick@prophead rtl8812AU-master]$ modinfo 8812au.ko
>>> filename: /home/rick/Downloads/Drivers/rtl8812AU-master/8812au.ko
>>> version: v5.1.5_19247.20160830
>>> author: Realtek Semiconductor Corp.
>>> description: Realtek Wireless Lan Driver
>>> license: GPL
>>> srcversion: C550A52D7A7F27740561522
>>> alias: usb:v2604p0012d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v2001p3316d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v2001p3315d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v07B8p8812d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v2019pAB30d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v1740p0100d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v1058p0632d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v2001p3313d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0586p3426d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0E66p0022d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0B05p17D2d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0409p0408d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0789p016Ed*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v04BBp0952d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0DF6p0074d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v7392pA822d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v2001p330Ed*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v050Dp1106d*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0BDAp881Cd*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0BDAp881Bd*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0BDAp881Ad*dc*dsc*dp*ic*isc*ip*in*
>>> alias: usb:v0BDAp8812d*dc*dsc*dp*ic*isc*ip*in*
>>> depends: cfg80211
>>> vermagic: 4.11.8-200.fc25.x86_64 SMP mod_unload
>>>
>>> <other stuff snipped>
>> I have the kernel-devel, kernel-headers and the elfutils package already
>> installed but it makes no difference. One thing of note with this is, I
>> have copied the source code to Ubuntu and the latest update has upgraded
>> their kernel (Ubuntu 16.10) to 4.8.8, I don't know how their kernel
>> numbering relates to Fedora's numbering, and it compile quite happily
>> via dkms. I have also tried a straight make from the source code
>> directory and it fails with the same errors. I have copied a snippet of
>> one of the errors below.
>>
>>
>> In file included from
>> /usr/local/downloads/dwa192/rtl8814AU-driver-4.3.21/include/drv_types.h:32:0,
>>
>> from
>> /usr/local/downloads/dwa192/rtl8814AU-driver-4.3.21/core/rtw_cmd.c:22:
>> /usr/local/downloads/dwa192/rtl8814AU-driver-4.3.21/include/osdep_service.h:
>> In function ‘thread_enter’:
>> /usr/local/downloads/dwa192/rtl8814AU-driver-4.3.21/include/osdep_service.h:343:2:
>> error: implicit declaration of function ‘allow_signal’
>> [-Werror=implicit-function-declaration]
>> allow_signal(SIGTERM);
>> ^~~~~~~~~~~~
>>
>> Just having a look at this error, is this because the makefile has the
>> -Werror parameter specified, or is it something supplied by the compiler
>> itself?
>>
>> In the messages above I am compiling the rtl8814AU driver but the
>> rtl8812AU driver I downloaded is getting exactly the same errors.
> It appears you're using a different driver than the 8812AU driver I
> built from github at:
>
> https://github.com/gnab/rtl8812au
>
> Digging through the source, it appears to be v5.1.5_19247.20160830.
> I included the USB device listings above. Do an "lsusb" with your
> device plugged in and see if the vendor and product match one of the
> entries above, e.g.:
>
> alias: usb:v1058p0632d*dc*dsc*dp*ic*isc*ip*in*
> ^^^^ ^^^^
> |||| ||||
> |||| -------> USB Product ID
> ------------> USB Vendor ID
>
> Perhaps it'll match up.
>
> That all being said, I pulled down your driver (the rtl8814AU) version
> from
>
> https://github.com/diederikdehaas/rtl8814AU
>
> and built it. There is a bug in one of the header files. If you want
> to fix it, go into your
>
> /usr/local/downloads/dwa192/rtl8814AU-driver-4.3.21/include
>
> directory and edit the "osdep_service_linux.h" file. Go down to line
> 59 or so and insert the following lines BELOW the line that reads
> "#include <linux/vmalloc.h>"
>
> #if (LINUX_VERSION_CODE >= KERNEL_VERSION(4, 11, 0))
> #include <linux/sched/signal.h>
> #endif
>
> This adds the definition of the functions that the compiler is bitching
> about. Then try "make" again. Worked for me:
>
> [rick@prophead rtl8814AU-driver-4.3.21]$ modinfo 8814au.ko
> filename:
> /home/rick/Downloads/Drivers/rtl8814AU-driver-4.3.21/8814au.ko
> version: v4.3.21_17997.20160531
> author: Realtek Semiconductor Corp.
> description: Realtek Wireless Lan Driver
> license: GPL
> srcversion: E16A7178CDD95B68C2D2259
> alias: usb:v7392pA834d*dc*dsc*dp*ic*isc*ip*in*
> alias: usb:v056Ep400Dd*dc*dsc*dp*ic*isc*ip*in*
> alias: usb:v056Ep400Bd*dc*dsc*dp*ic*isc*ip*in*
> alias: usb:v0B05p1817d*dc*dsc*dp*ic*isc*ip*in*
> alias: usb:v2001p331Ad*dc*dsc*dp*ic*isc*ip*in*
> alias: usb:v0BDAp8813d*dc*dsc*dp*ic*isc*ip*in*
> depends: cfg80211
> vermagic: 4.11.8-200.fc25.x86_64 SMP mod_unload
I apologise for sending my response directly to you Rick, it appears
that I used reply instead of reply-list.
I did the changes you suggested to my source code and the code did
compile successfully, so I copied that code to the source location for
dkms to pick it up from, and ran the dkms autoinstall process and it was
compiled and built into the kernel successfully, and I now have wireless
access back again.
Thankyou for all your help.
Just one question on this, with all the include files that are in that
source, how did you find that what you have provided the solution for
was the issue and what the needed include was and where it should be placed?
regards,
Steve
> ----------------------------------------------------------------------
> - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
> - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
> - -
> - The trouble with troubleshooting is that trouble sometimes -
> - shoots back. -
> ----------------------------------------------------------------------
6 years, 9 months
Re: how to (re-?)construct grub menu?
by William
On Friday, July 07, Rick Stevens wrote:
> Ye gods! That was a LONG time ago.
It took me a few hours of groping around to find that thread!
> Nouveau has gotten better. It just didn't work well on some
> chipsets way back when dinosaurs walked the earth.
Should I stick with the nVidia proprietary driver or switch back to the
Nouveau driver, or does it not really matter? The only hardware that
has changed on my workstation is the hard drive.
As best as I can determine, the file in which those GRUB_ lines appear
is merely a text file read by "grub2-mkconfig" and/or "grub2-install" to
make scripts used early in the boot process. Thus my suspicion that
order does not matter, except for the two lines that Sam suggested to me
in an earlier message in this thread.
thanks,
Bill.
6 years, 9 months
Pulseaudio: Hardware Routing
by Frank Elsner
Hello,
for reasons I have to send the input from an audio interface to an other.
I can do this with
pactl load-module module-loopback \
source="alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" \
sink="alsa_output.usb-M-AUDIO_M-Track_Hub-00.analog-stereo"
and this works as desired.
Currently I have to issue this command (realized as procedure) after each login.
I want a permanent solution. Where to place this command? Or is there an other
permant solution beside this command?
BTW, rc.local doesnt't work.
Any pointer welcome.
Kind regards, Frank
6 years, 9 months
Lost wired connection
by Lucélio Gomes de Freitas
Hi,
Somebody helps?
Old "Fedora 20-x86_64" installed and working. Due to a problem,
I Changed my motherboard and lost network(Internet) connection.
How to recover connection before install Fedora-Kde-live-25-1-3?
Thanks.
6 years, 9 months