Dummy audio and no Wifi after upgrading to f25
by Tomas Repik
Hi,
I've been struggling with both audio and wifi since i upgraded from F24 to F25. I went through many advices and suggestions (different kernels, restarting, reinstalling both alsa and pulseaudio) to solve the issues with no result.
I don't have any audio feedback from my device (in audio settings only dummy output is shown). I filed a bug against pulseaudio [1]. I also provide output from lshw command [2].
It shows that both wifi and audio devices are UNCLAIMED (don't know what that mean).
thanks for any help
Tomas
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1416291
[2] https://trepik.fedorapeople.org/tmp/lshw
7 years, 2 months
- 3
- 5
iPhone photos -
by Bob Goodwin
Gphoto2 worked normally until yesterday
when I began getting errors. Both Fedora
25 and the iPhone have had updates since
I last used it, a day or two ago. This
is what I am seeing:
[bobg@box10 photosnew]$ gphoto2
--auto-detect
Model Port
----------------------------------------------------------
Apple iPhone 5 (PTP mode) usb:003,005
[bobg@box10 photosnew]$ gphoto2
--get-all-files --force-overwrite
[bobg@box10 photosnew]$ gphoto2
--get-all-files --force-overwrite
*** Error ***
PTP Invalid Storage ID
*** Error (-1: 'Unspecified error') ***
For debugging messages, please use the
--debug option.
Debugging messages may help finding a
solution to your problem.
If you intend to send any error or debug
messages to the gphoto
developer mailing list
<gphoto-devel(a)lists.sourceforge.net>,
please run
gphoto2 as follows:
env LANG=C gphoto2 --debug
--debug-logfile=my-logfile.txt
--get-all-files --force-overwrite
Please make sure there is sufficient
quoting around the arguments.
[bobg@box10 photosnew]$ env LANG=C
gphoto2 --debug
--debug-logfile=my-logfile.txt
--get-all-files --force-overwrite
*** Error ***
PTP Invalid Storage ID
*** Error (-1: 'Unspecified error') ***
Any thoughts on what has happened will
be appreciated ...
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-25/64bit LINUX XFCE Fastmail POP3
7 years, 2 months
- 2
- 2
KVM and 3D?
by Tom Horsley
I saw a blog post that claimed virt-manager 1.4 has the
support for 3D video acceleration in virtual machines,
then I saw lots of comments in the blog saying that
it won't work without libvirt support. Since I always
thought virt-manager just called libvirt to do everything
that confused the heck out of me :-).
Are there instructions of dummies anywhere about how
to get 3D working in a virtual machine?
Is there any chance it will ever work in a Windows
virtual machine (the only reason I have a Windows hardware
box is because I need to run an app that insists on 3D
support).
7 years, 2 months
- 4
- 8
Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
by Stephen Morris
On 31/01/2017 02:58, poma wrote:
> On 29.01.2017 22:42, Stephen Morris wrote:
>> On 27/01/2017 21:20, poma wrote:
>>> On 26.01.2017 22:12, Stephen Morris wrote:
>>>> On 24/01/2017 15:12, poma wrote:
>>>>> On 23.01.2017 21:14, Stephen Morris wrote:
>>>>>> On 23/01/2017 08:27, poma wrote:
>>>>>>> On 22.01.2017 21:49, Stephen Morris wrote:
>>>>>>>> On 23/01/2017 00:43, poma wrote:
>>>>>>>>> On 21.01.2017 21:00, poma wrote:
>>>>>>>>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>>>>>>>>> [...]
>>>>>>>>>>> The lsusb output for that device is also below.
>>>>>>>>>>>
>>>>>>>>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>>>>>>>>>
>>>>>>>>>> [...]
>>>>>>>>>>
>>>>>>>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>>>>>>>
>>>>>>>>>> https://wikidevi.com/wiki/D-Link_DWA-192
>>>>>>>>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>>>>>>>>>> ftp://files.dlink.com.au/products/DWA-192
>>>>>>>>>> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>>>>>>>>>
>>>>>>>>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>>>>>>>>> http://www.edimax.com/edimax/download/download/data/edimax/global/downloa...
>>>>>>>>>> http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-...
>>>>>>>>>>
>>>>>>>>>> https://github.com/pld-linux/rtl8812au
>>>>>>>>>> https://github.com/diederikdehaas/rtl8812AU
>>>>>>>>>>
>>>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>>>>
>>>>>>>>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>>>>>>>> $ cd EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>>>>>>>>
>>>>>>>>>> $ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debu... | patch -p1
>>>>>>>>>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | patch -p1
>>>>>>>>>> $ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | patch -p1
>>>>>>>>>> $ curl -s https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | patch -p1
>>>>>>>>>>
>>>>>>>>>> $ make -j3
>>>>>>>>>> $ su
>>>>>>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>>>>>>> # depmod
>>>>>>>>>> # modinfo 8814au | grep 2001
>>>>>>>>>>
>>>>>>>>>> # modprobe -v 8814au
>>>>>>>>>> # dmesg:
>>>>>>>>>> ...
>>>>>>>>>> RTL871X: module init start
>>>>>>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>>>>>>> RTL871X: build time: Jan 21 2017 20:04:38
>>>>>>>>>> usbcore: registered new interface driver rtl8814au
>>>>>>>>>> RTL871X: module init ret=0
>>>>>>>>>> ...
>>>>>>>>>> # modprobe -rv 8814au
>>>>>>>>>> # dmesg:
>>>>>>>>>> ...
>>>>>>>>>> RTL871X: module exit start
>>>>>>>>>> usbcore: deregistering interface driver rtl8814au
>>>>>>>>>> RTL871X: module exit success
>>>>>>>>>> ...
>>>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>>>>
>>>>>>>>>> Wifi ball works now?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> HW add.
>>>>>>>>>> https://wikidevi.com/wiki/ASUS_USB-AC68
>>>>>>>>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>>>>>>>>>
>>>>>>>>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>>>>>>>>>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>>>>>>>>>
>>>>>>>>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>>>>>>>>>> https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>>>>>>>>>>
>>>>>>>>>> SW add.
>>>>>>>>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>>>>>>>>> https://github.com/austinmarton/rtl8812au_linux
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> OR
>>>>>>>>> according to "rtl8814au? #10"
>>>>>>>>> https://github.com/diederikdehaas/rtl8812AU/issues/10
>>>>>>>>>
>>>>>>>>> $ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git RTL8814AU-uminokoe
>>>>>>>>> $ cd RTL8814AU-uminokoe/
>>>>>>>>> $ git revert -n 9260f77 8d33100
>>>>>>>>> // "Disabled debugging code."
>>>>>>>>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | patch -p1
>>>>>>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>>>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>>>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>>>>>>
>>>>>>>>> OR
>>>>>>>>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git RTL8814AU-diederikdehaas
>>>>>>>>> $ cd RTL8814AU-diederikdehaas/
>>>>>>>>> // Adds missing Vendor/Product ID
>>>>>>>>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A}, /* Edimax - Edimax */' os_dep/linux/usb_intf.c
>>>>>>>>> // "Added VHT capabilities."
>>>>>>>>> $ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch -p1
>>>>>>>>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>>>>>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>>>>>>>>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> $ make -j3
>>>>>>>>> $ su
>>>>>>>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>>>>>>>> # depmod
>>>>>>>>> # modinfo 8814au
>>>>>>>>>
>>>>>>>>> # modprobe -v 8814au
>>>>>>>>> # dmesg:
>>>>>>>>> ...
>>>>>>>>> RTL871X: module init start
>>>>>>>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>>>>>>>> usbcore: registered new interface driver rtl8814au
>>>>>>>>> RTL871X: module init ret=0
>>>>>>>>> ...
>>>>>>>>> # modprobe -rv 8814au
>>>>>>>>> # dmesg:
>>>>>>>>> ...
>>>>>>>>> RTL871X: module exit start
>>>>>>>>> usbcore: deregistering interface driver rtl8814au
>>>>>>>>> RTL871X: module exit success
>>>>>>>>> ...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello Diederik,
>>>>>>>>> it seems there are only two Linux RTL8814AU users, so far.
>>>>>>>>>
>>>>>>>>> Morris, when you catch some time, would you mind to run a couple iperf tests with DWA-192,
>>>>>>>>> to see real network throughput results.
>>>>>>>> I can't run any at the moment because Fedora is refusing to actually use
>>>>>>>> the device at all.
>>>>>>>>
>>>>>>>> I have also just upgraded to F25 and nothing has changed.
>>>>>>>>
>>>>>>>> The last time I used this device was on 08/10/2016 and it was using the
>>>>>>>> ATH9K driver. The main reason I upgraded to this USB device was that I
>>>>>>>> upgraded my router to a faster version, and I found that unlike the
>>>>>>>> DWA182 I didn't have to compile my own driver, the kernel had inbuilt
>>>>>>>> support for the DWA192.
>>>>>>>>
>>>>>>>> It is possible that I have managed to Blacklist the device in some way,
>>>>>>>> not by the conventional Blacklist.conf, and I have forgotten how so I
>>>>>>>> can't find where I've done it to reverse it.
>>>>>>>>
>>>>>>>> Also, having never done it before, I also don't know how to run iperf tests.
>>>>>>>>
>>>>>>>> regards,
>>>>>>>> Steve
>>>>>>>>
>>>>>>> Did I understand you correctly, what you're saying here is that:
>>>>>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>>>>> therefore the USB based device, was driven by:
>>>>>>> $ modinfo --description ath9k
>>>>>>> Support for Atheros 802.11n wireless LAN cards.
>>>>>>> https://wireless.wiki.kernel.org/en/users/drivers/ath9k
>>>>>>> "ath9k is a completely FOSS wireless driver for all Atheros IEEE 802.11n PCI/PCI-Express and AHB WLAN based chipsets."
>>>>>>> https://wiki.debian.org/ath9k
>>>>>>> "Atheros 802.11n PCI/PCI-E devices (ath9k)"
>>>>>> Yes, when the device was working iwconfig reported the driver as being
>>>>>> ATH9K, but if refused to use the 5GHz channel. Following a suggestion on
>>>>>> this list I tried compiling my own kernel and setting a recommended
>>>>>> flag, but that had no effect on its ability to use the 5GHz channel. It
>>>>>> was from compiling my own kernel I found that it looked like the ATH10K
>>>>>> driver would support the 5GHz channel, which Winfried de Heiden is
>>>>>> confirming, so at the time I couldn't work out why the system wasn't
>>>>>> assigning the ATH10K driver instead of the ATH9K driver.
>>>>>> From what you are saying it sounds like that various updates to F24
>>>>>> (and in F25 which I am using now) have changed the functionality of
>>>>>> ATH9K to not support USB devices, which would potentially go a long way
>>>>>> towards explaining why my adapter is no longer recognized any more.
>>>>>> Also it seems to me that you are suggesting that I need to go back to
>>>>>> compiling a driver for this card again (if I have to do this will the
>>>>>> driver support the 5GHz channel), if this is so given that from when I
>>>>>> first started using this adapter up until 08/10/2016 there was native
>>>>>> support in the kernel for the device, why has this support been dropped?
>>>>>> I first started using this adapter in F23.
>>>>>>
>>>>>> regards,
>>>>>> Steve
>>>>> This should show the WiFi devices that are connected to the machine:
>>>>> $ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
>>>>>
>>>>> Would you mind copy and paste the output here.
>>>> I have input the commands and the output is listed below.
>>>>
>>>> echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
>>>>
>>>>
>>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 005 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
>>>> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 004 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
>>>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>> Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>> Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>>> Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>>
>>>> /: Bus 11.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
>>>> /: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
>>>> |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
>>>> /: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
>>>> /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
>>>> /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M
>>>> /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M
>>>> /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
>>>> |__ Port 2: Dev 2, If 0, Class=Human Interface Device,
>>>> Driver=usbhid, 12M
>>>> |__ Port 2: Dev 2, If 1, Class=Human Interface Device,
>>>> Driver=usbhid, 12M
>>>> |__ Port 2: Dev 2, If 2, Class=Human Interface Device,
>>>> Driver=usbhid, 12M
>>>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M
>>>> |__ Port 1: Dev 2, If 0, Class=Human Interface Device,
>>>> Driver=usbhid, 1.5M
>>>> |__ Port 1: Dev 2, If 1, Class=Human Interface Device,
>>>> Driver=usbhid, 1.5M
>>>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M
>>>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
>>>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M
>>>>
>>>> Bus 010 Device 002 is the usb wifi adapter that is not recognized anymore.
>>> Bus 10 Device 2
>>>
>>> lsusb:
>>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>>
>>> lsusb -t:
>>> /: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
>>> |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
>>>
>>>
>>> 8814au.ko when built, installed and loaded,
>>> should show up as assigned to the device:
>>>
>>> /: Bus 10 [...]
>>> |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=8814au, 480M
>> I can rebuild that driver like I was with the DWA-182 usb device when I
>> had it, but when I purchased the DWA-192, under Fedora 23 there was
>> native support for DWA-192 in the kernel, hence I did not have to
>> compile a driver anymore. At the time I also raised a Bugzilla around
>> the fact that the ATH9K driver (which is the driver the commands I
>> issued at the time, that I was advised to on this list, told me was the
>> one being used) did not provide access to the 5 GHz channel. That driver
>> was being used through F23 and F24, or at least native kernel support,
>> was provided up until 08/10/2016 at which time I switched over to an
>> Ethernet Home Plug interface to networking (this was because the device
>> became problematic in retaining connection to the network).
>> Now that I have switched back to the wifi device, because even on the
>> 2.4 GHz channel this wifi device is faster than the Ethernet device, I
>> have found that the DWA-192 device appears to no longer be supported
>> natively by the kernel.
>> Why has support for this device been removed from the kernel? As a side
>> issue to this, I have also noticed that this device has exactly the same
>> non-support issue under Ubuntu 16.10.
>>
>
> "Dlink DWA-192 not Properly Supported"
> https://bugzilla.redhat.com/show_bug.cgi?id=1346465
> Apparently Fedora Kernel Team know less than you there ;)
>
> Morris, would you mind try to read the following lines with care and understanding;
>
> = DWA-192 win driver location:
> http://support.dlink.com/ProductInfo.aspx?m=DWA-192#Download
> ftp://ftp2.dlink.com/PRODUCTS/DWA-192/REVA/DWA-192_REVA_DRIVERS_1.03.B04_...
>
> = A brief review of the aforementioned driver,
> part of the installation via Wine - https://winehq.org
>
> $ unzip DWA-192_REVA_DRIVERS_1.03.B04_WIN.ZIP
> $ wine DWA-192_V1.03b04/Setup.exe
> ...
> See "Wine installation RTL8814AU D-Link DWA-192.png" (attachment)
> ...
> $ dos2unix < ~/.wine/dosdevices/c\:/Program\ Files/D-Link/DWA-192/Drivers/Win7x86/D_netrtwlanu.inf | grep '8814AU\|2001\|331A'
> %DWA-192_331A.DeviceDesc% = RTL8814auDLink.ndi, USB\VID_2001&PID_331A
> ;; Dlink 8814AU installation
> DWA-192_331A.DeviceDesc = "D-Link DWA-192 AC1900 Wi-Fi USB 3.0 Adapter"
> DWA-192_331A.DeviceDesc.DispName = "D-Link DWA-192 AC1900 Wi-Fi USB 3.0 Adapter"
>
> = Conclusion:
> D-Link DWA-192 AC1900 Wi-Fi USB 3.0 Adapter -is- related to Realtek RTL8814AU 4T4R 802.11ac, USB 3.0 Chipset,
> which again correlates with the Linux kernel case - 8814au.ko.
>
> ~~~~~
>
> "Dlink DWA192 Partially Supported in Kernel?"
> https://lists.fedoraproject.org/archives/list/users%40lists.fedoraproject...
> What you mentioned in this thread - "4.3.5-300 kernel", can be found here:
> https://kojipkgs.fedoraproject.org/packages/kernel/4.3.5/300.fc23/x86_64/
>
> "kernel-core-4.3.5-300.fc23.x86_64.rpm" and "kernel-modules-4.3.5-300.fc23.x86_64.rpm"
> are sufficient for the installation and testing:
> # rpm -ivh --oldpackage kernel-*-4.3.5-300.fc23.x86_64.rpm
> so that we can examine the output of:
> $ networkctl status <IFNAME>
> to see the driver assigned to the device
> Of course you can repeat:
> $ echo ; lspci -knn -d ::0280 ; echo ; lsusb ; echo ; lsusb -t ; echo
> and paste the output here, also.
>
> ~~~~~
>
> What you also mentioned in the above-mentioned thread - [...]VNAIKQSTZVULRQKBYR5EDDOMBWRYWXXI
> is the name assigned to the device - wlp4s6, which really does not correlates with the naming scheme, explained here:
> "How does the new naming scheme look like, precisely?"
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInter...
> https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_...
> i.e. "wlp4s6" seems to be a PCI based device, however D-Link DWA-192 is the USB based device.
Just further to my previous email, I have compiled the 8814au driver
following your instructions above and that has created device wlp3s0u2,
but the network is unable to activate it. The messages from dmesg are as
follows (what I haven't determined yet is whether or not the failure is
because I am currently using the ethernet interface).
[ 1363.001100] usb 10-1: USB disconnect, device number 2
[ 1366.435600] usb 10-2: new high-speed USB device number 3 using xhci_hcd
[ 1366.604162] usb 10-2: New USB device found, idVendor=2001, idProduct=331a
[ 1366.604166] usb 10-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 1366.604169] usb 10-2: Product: 11ac Adapter
[ 1366.604172] usb 10-2: Manufacturer: Realtek
[ 1366.604175] usb 10-2: SerialNumber: 123456
[ 6094.157799] RTL871X: module init start
[ 6094.157802] RTL871X: rtl8814au v4.3.21_17997.20160531
[ 6094.298894] RTL871X: rtw_ndev_init(wlan0) if1 mac_addr=6c:72:20:00:ac:c4
[ 6094.299451] usbcore: registered new interface driver rtl8814au
[ 6094.299452] RTL871X: module init ret=0
[ 6094.384280] rtl8814au 10-2:1.0 wlp3s0u2: renamed from wlan0
[ 6094.404086] IPv6: ADDRCONF(NETDEV_UP): wlp3s0u2: link is not ready
[ 6094.880887] IPv6: ADDRCONF(NETDEV_UP): wlp3s0u2: link is not ready
[ 6094.888146] IPv6: ADDRCONF(NETDEV_UP): wlp3s0u2: link is not ready
[ 6094.940359] IPv6: ADDRCONF(NETDEV_UP): wlp3s0u2: link is not ready
[ 6095.058090] IPv6: ADDRCONF(NETDEV_UP): wlp3s0u2: link is not ready
[ 6095.244405] RTL871X: assoc success
[ 6095.244668] RTL871X: set group key camid:1, addr:00:00:00:00:00:00,
kid:1, type:TKIP
[ 6095.245211] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0u2: link becomes ready
One question I have, in the 8814 instructions above you mentioned:
// Adds missing Vendor/Product ID
$ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A}, /* Edimax - Edimax */' os_dep/linux/usb_intf.c
Should the values inside the USB_DEVICE brackets be the idVendor and idProduct numbers mentioned in the dmesg output above?
regards,
Steve
7 years, 2 months
- 4
- 20
Fedora 25 USB WiFi plug and play recommendations
by cen
Hello
Any recommendations from community which USB WiFi card to buy that just
works with F25? I have BCM4352 but need UEFI (Win10 dual boot) so it's
unusable.
Again, plug&play, no messing around with kernel and drivers.
7 years, 2 months
- 2
- 1
In FC 15 only root can run the X server need HELP
by Willaim W. Austin
I recently upgraded a machine (my main workstation) from FC 23 to FC 24, and there's a problem
The install was from the Workstation version and the checksum correctgly matches (actually I always make 2 copies, just in case, which I hold on to forever - they both check).
I did the install, and intitially (until I added other users) everything was fine - no problems in logging in.
However, I have an imortant app which I support and it needs the entire root screen and can't coexist with plasma shell, so the machine normally runs in multi-user mode, and X sessions are accessed via /usr/bin/startx. (This has been working since the days of Redhat 5 through FC1 and up to and including FC23 - I never tried FC 24 - and has never given a bit of trouble.)
After I added a non-privileged user for myself the fun began. The biggest issue was that a non-privileged user could nto run an X-server (not via startx anyway). FWIW I can't run the Wayland server since I am using an NVIDIA GeForce GTX 950 and wayland doensn't handle it yet. The problem occurs whether I use the O/S nouveau drivers or install the proprieary (xO/S ?) Nvidia drivers.
Hardware details : CPU is Intel i7 with 6 cores (show up as 12 in Linux), MSI X99A Xpower motherboard with 32 GB memory (4 8gb sticks), 7 drives totalling ~24 TB of local disk space.
ERROR MESSAGE:
There have been 2 (each is the one-line err msg from a failed session attempt) - the current one is the latter, and both look as if they have been munged slightly:
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.c-common: line 46: XKB_IN_USE: unbound variablexinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.initrc-common: line 46: XKB_IN_USE: unbound variablexinit: connection to X server lost
LOG: /var/log - I can furnish a copy, but I didn't see any obvious "gotcha's" in it.
Now I am a former kernel hacker, was a contributor to XFree86, have been a Linus (and Solaris and HP-UX) SA for over 20 years, and I have been building my workstations and servers from off-the-shelf components since before the PC was invented, so I am not a newbie and generally I can solve most problems, and FWIW I don't think I've done anyting really stupid here. Finally, fWIW this particular machine ran FC 23 with not problems whatsoever. Just to make sure that something had no happened hardware wise, I switched the boot loader to look back at the FC23 partition, and it still boots and runs correctly without the Xorg problem.
I have gone to bugzilla and posted the bug, but so far it does not appear to have been looked at, so no help there.
This has been going on now for about 2 weeks. I tried to solve the problem for 3 days then blew the installation away and redid it, this time installing the server version.
Of course I had to add the X/desktop pieces and it took almost a day to get everyting that I needed installed. The same thing happened, and I am now on install # from the Workstaion spin. And yes, the same problem still happens every time.
I'm beginning to suspect that something in my own environment causes the problem, so I added a new, completely vanilla user ("dummy") and he seems to get the same results.
Any help and/or suggestions would be appreciated, and please feel free to contact me off list if that is easier for you.
Thanks,
william w. austin wwaustin(a)google.com
"life is just another phase i'm going through. this time, anyway ..."
7 years, 2 months
- 4
- 5
Lost kde task bar
by Fulko Hew
I've been fighting with F24 (gosh I miss the good old days) but today it's
totally disconnected on me.
My laptop has developed an intermittent backlight problem so i have it
driving my TV instead. While trying to resolve resolution issues between
and driving both the onboard LCD and the TV my KDE task bar has gone away.
Logging out and in doesn't restore it, and neither does a reboot. I also
tried starting Gnome, which does, but the Wi-fi doesn't start.
Can annyone suggest what to try next?
7 years, 2 months
- 2
- 2
Re: Lost kde task bar (resolved)
by Fulko Hew
On Thu, Feb 2, 2017 at 9:48 AM, Fulko Hew <fulko.hew(a)gmail.com> wrote:
> I've been fighting with F24 (gosh I miss the good old days) but today
> it's totally disconnected on me.
>
> My laptop has developed an intermittent backlight problem so i have it
> driving my TV instead. While trying to resolve resolution issues between
> and driving both the onboard LCD and the TV my KDE task bar has gone away.
>
> Logging out and in doesn't restore it, and neither does a reboot. I also
> tried starting Gnome, which does, but the Wi-fi doesn't start.
>
> Can annyone suggest what to try next?
>
After trying Gnome and XFCE, unplugging the TV, and a number of reboots,
everything has magically reappeared. So my problem has magically gone
away, as magically as it appeared. Sorry for the bother.
7 years, 2 months
- 1
- 0
Los efectos de compiz no funcionan en fedora 25 mate compiz
by Snaker Mota
>
> Hola a todos desde ASE dos meses instale fedora 25 con él escritorio mate
> compiz para poder usar los efectos pero no e podido usarlos por la razón de
> que no e podido instalar los drivers de mi targeta gráfica al pareser no
> hay manera de aserlo? Es que no es estable ?saludos
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org <javascript:;>
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> <javascript:;>
>
7 years, 2 months
- 2
- 1
RANT: installing fedora is now a real punishment!
by François Patte
I wanted to install fedora 25 after my defeat to have an encrypted raid
install with fedora24 (system cannot shutdown and I filed a bug report
with all possible log files as explain in systemd, but up to now nobody
cares...)
Install of f25 was (almost) easy *but* I am unable to login! I created a
user with a password but when I want to login system claims that the
password is incorrect. OK maybe I made a mistake, so I try to login as
root from the console : password is incorrect too!
I try to rescue the system: it takes ages to accept the passphrase for
encrypted /home (why does the recue need to mount /home?????) After
that, I am unable to set a new root password: if I ask "chpasswd" the
answer is: "missing new password on line 1" (of course I can see my new
password... but "missing new password..."
If I ask passwd, I have 1 second to type the password before falling
back to prompt... So I can't type anything!
WHAT A MESS!
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
7 years, 2 months
- 6
- 5