IP Camera -

2017-01-26 Thread Bob Goodwin 
Does anyone have any experience with the 
Foscam C1 IP camera. Like many things it 
wants Outlook Explorer for set up and 
operation, perhaps my iPhone would work? 
But I really want to deal with it via my 
Fedora 25 workstation.


New, out of the box my router assigns it 
an address 192.168.1.15 and I can access 
that from Firefox but it wants a .exe 
plugin installed, I can download that 
but I don't expect that to work on my 
system.


I've tried VLC which works with some 
much older cameras that use mjpg, but I 
haven't been able to find a string that 
doesn't produce an error and worse yet 
locks up VLC for an annoying period of time.


Some googling suggeststhat rtsp is 
required, dnf install rtsp results in 
not available ...


What do I have to do to make this work?

Bob


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

Re: IP Camera -

2017-01-26 Thread Samuel Sieb 

On 01/26/2017 10:44 AM, Bob Goodwin wrote:

I've tried VLC which works with some much older cameras that use mjpg,
but I haven't been able to find a string that doesn't produce an error
and worse yet locks up VLC for an annoying period of time.

Some googling suggeststhat rtsp is required, dnf install rtsp results in
not available ...

If you can find a valid url or port, you could try mplayer.  It has 
support for rtsp.

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

Re: IP Camera -

2017-01-26 Thread Bob Goodwin 

On 01/26/17 14:01, Samuel Sieb wrote:
On 01/26/2017 10:44 AM, Bob Goodwin 
wrote:
I've tried VLC which works with some 
much older cameras that use mjpg,
but I haven't been able to find a 
string that doesn't produce an error
and worse yet locks up VLC for an 
annoying period of time.


Some googling suggeststhat rtsp is 
required, dnf install rtsp results in

not available ...

If you can find a valid url or port, 
you could try mplayer.  It has support 
for rtsp.
___ 




+

Ok, I installed mplayer, not familiar 
with it but I get the following:


$ mplayer 
rtsp://admin:@192.168.1.15:88/videoMain
Creating config file: 
/home/bobg/.mplayer/config
MPlayer 1.3.0-6.2.1 (C) 2000-2016 
MPlayer Team

do_connect: could not connect to socket
connect: No such file or directory
Failed to open LIRC support. You will 
not be able to use your remote control.


Playing 
rtsp://admin:@192.168.1.15:88/videoMain.

Resolving 192.168.1.15 for AF_INET6...

Couldn't resolve name for AF_INET6: 
192.168.1.15
Connecting to server 
192.168.1.15[192.168.1.15]: 88...


rtsp: read error.
librtsp: buffer overflow in rtsp_get

It still has the default settings, user 
admin and the password is empty. Not 
sure if I can set the password from the 
browser, have not attempted that.


Dunno what to do from there?

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

Re: IP Camera -

2017-01-26 Thread Jack Craig 
On Thu, Jan 26, 2017 at 11:35 AM, Bob Goodwin 
wrote:

On 01/26/17 14:01, Samuel Sieb wrote:
>
>
> It still has the default settings, user admin and the password is empty.
> Not sure if I can set the password from the browser, have not attempted
> that.
>
> Dunno what to do from there?
>






*port ...http://elinux.org/RPi-Cam-Web-Interface
*
*to fedora?! Just kidding, ...  *  😕
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: RIP Fedora?

2017-01-26 Thread Sylvia Sánchez 
Hello,

You should make a fresh install.  Fedora 24 and 25 are the latest, Fedora
23 is already unsupported.

Cheers,
Sylvia



On 18 January 2017 at 18:48, Phil Neck <1nc0mun1c...@gmail.com> wrote:

> Okay ... now I have your attention ...
>
> A funny thing happened to me the other day ...
>
> I tried upgrading a Fedora 22 VM which was running on about 30 different
> VMware architectures to Fedora 23. All but a couple worked perfectly but a
> couple (Both Dell servers) didn't. On these I can only describe what I was
> seeing as '64-bitty' problems ... checksums failing ... that kind of thing.
>
> I then had the idea of trying to build the machine 'from scratch' using a
> Fedora 25 CD image. Similar results ... the machines the original 22-23
> convertion worked on went fine, but the other two ... no dice. They
> wouldn't even load beyond initial kernel boot and into install screen.
>
> I thought best to start at the bottom and work up, so spoke to Dell ...
> they had no reports of problems with their machines and VMware (yeah ... I
> know ... they never do ... but)
>
> Then spoke to VMWare to be told:
>
> =
>
> "My name is gfdgfdgfdg and I will be working with you to resolve your
> issue for Support Request 7657576576576.
>
> I understand from your case description that Fedora 25 64 bit  VM won't
> boot.
> Please find the list of the supported OS on the ESXi host. Fedora is not
> supported on ESXi but rather on Workstation and Fusion.
>
> https://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_
> Compatibility_Guide.pdf
>
> If you are using Workstation or Fusion, please raise a case with the
> concerned team to assist you however its not supported as a guest OS on
> ESXi.
>
> Let me know if you have any questions or if we are good to close the case
> for now.
>
> ==
>
> I appreciate that this note is low on technical facts (by design). because
> I'm not really as as interested in the technical minucia of the problem, as
> the more general situation. Can anyone explain what changed between FC22
> and FC23? What caused VMware to drop support? Is there any practical way
> around this?
>
> I have hundreds of Fedora based VMs out there running versions from
> 'stoneage' to the latest, all working fine EXCEPT those on the two machines
> mentioned.
>
> I have a heck of a decision to make in the in the next few days, but it
> sounds like its going to be RIP Fedora :(
>
> Any insight most gratefully appreciated
>
> Thanks
>
> Phil.
>
>
> ___
> 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

Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0

2017-01-26 Thread Stephen Morris 

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/download/for_home/wireless_adapters/wireless_adapters_ac1750_dual-band/ew-7833uac
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip

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-debug.patch
 | 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 cor

Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0

2017-01-26 Thread Stephen Morris 

On 25/01/2017 00:17, Terry Polzin wrote:

Stephen,

I think that Poma finds it extraordinary that your device was working 
with a driver for a completely different chipset.  I know I do.
I can understand that. The iwconfig output could have been showing the 
wrong driver, but at the time I also raised a bug on bugzilla around the 
fact that the driver would not active the 5GHz channel on the adapter, 
which at the moment has gone nowhere.


regards,
Steve



On Tue, Jan 24, 2017 at 12:12 AM, 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/download/for_home/wireless_adapters/wireless_adapters_ac1750_dual-band/ew-7833uac


>

http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip


>
> 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-debug.patch


| 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

Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0

2017-01-26 Thread Terry Polzin 
bus 010 device 002 is a pci device not a usb device the way I read this
output.

On Thu, Jan 26, 2017 at 4:17 PM, Stephen Morris 
wrote:

> On 25/01/2017 00:17, Terry Polzin wrote:
>
>> Stephen,
>>
>> I think that Poma finds it extraordinary that your device was working
>> with a driver for a completely different chipset.  I know I do.
>>
> I can understand that. The iwconfig output could have been showing the
> wrong driver, but at the time I also raised a bug on bugzilla around the
> fact that the driver would not active the 5GHz channel on the adapter,
> which at the moment has gone nowhere.
>
> regards,
> Steve
>
>
>> On Tue, Jan 24, 2017 at 12:12 AM, 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/g
>> lobal/download/for_home/wireless_adapters/wireless_adapters_
>> ac1750_dual-band/ew-7833uac
>> > global/download/for_home/wireless_adapters/wireless_adapters
>> _ac1750_dual-band/ew-7833uac>
>> >
>> http://www.edimax.com/edimax/mw/cufiles/files/download/Drive
>> r_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>> > er_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip>
>> >
>> > 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-debug.patch
>> > master/disable-debug.patch>
>> | 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
>> > master/linux-4.7.patch>
>> | patch -p1
>> > $ curl -s
>> https://raw.githubusercontent.com/pld-linux/rtl8812au/master
>> /linux-4.8.patch
>> > 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
>>

Re: cifs mount not working with uid option?

2017-01-26 Thread Stephen Morris 

On 24/01/2017 22:06, Gianluca Cecchi wrote:
On Tue, Jan 24, 2017 at 1:04 PM, Gianluca Cecchi 
mailto:gianluca.cec...@gmail.com>> wrote:


Hello,
my system is an updated Fedora 25.
A previously working windows share mounted via cifs is not working
now (I have not the details of it but I know only that it is a DFS
share, managed by a cluster of two windows 2012 R2 servers)
After some attempts, I have verified that the critical point seems
to be the "uid=1000" option that I previously used to map
permission of files and to be able to change them.

entry in fstab working
\\my.windows.domain\home\path1\path2\path3 /myshare
 cifs  noauto,_netdev,credentials=/etc/smbcred_myshare  0 0


entry in fstab not working (verified the same from command line,
doubling the slashes in this case)
\\my.windows.domain\home\path1\path2\path3 /myshare
 cifs

 noauto,_netdev,forceuid,uid=1000,credentials=/etc/smbcred_myshare
 0 0

NOTE: I tried both with and without the forceuid option when using
the uid= one but no go in both.

Of course my linux username is not the same as the username used
in credential file.
If I mount without uid I get all files owned by root and not able
to modify anything in Linux.
Any hint on what to try?

Thanks in advance,
Gianluca



I forgot to say that using the uid option I get this kind of message:

# mount /asishare/
mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
#

But no mount takes place...
I am using CIFS to mount a windows share on a NAS device attached to my 
router, but I am not using the uid option, instead I am using the user= 
and password= options to specify the userid and password that I have 
defined on my NAS device. The userid and password also happen to match 
my Linux userid and password. With these options I have write access 
from Linux and Windows can see the files also. Before adding these two 
options I was getting the same issue you are reporting, of Root being 
the owner, but Windows had no issues, even though I had specified 
internally in the device that it was public. Why do you need the uid 
option when you are supplying a credentials file, I would have assumed 
the credentials file would be specifying the information that would give 
your Linux userid the required access?
Also, if the device you are mounting is on a remote server, could your 
issue be that the server no longer gives the users listed in your 
credentials file access to the path you are trying to mount?


regards,
Steve




___
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

Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0

2017-01-26 Thread Stephen Morris 

On 27/01/2017 07:24, Terry Polzin wrote:
bus 010 device 002 is a pci device not a usb device the way I read 
this output.
The output that shows bus 010 device 002 as being a Dlink device (which 
is what my usb device is, and is the only Dlink device I have) is from 
lsusb, which I thought only showed usb interfaces and not pci, is that 
not correct?


regards,
Steve



On Thu, Jan 26, 2017 at 4:17 PM, Stephen Morris 
mailto:samor...@netspace.net.au>> wrote:


On 25/01/2017 00:17, Terry Polzin wrote:

Stephen,

I think that Poma finds it extraordinary that your device was
working with a driver for a completely different chipset.  I
know I do.

I can understand that. The iwconfig output could have been showing
the wrong driver, but at the time I also raised a bug on bugzilla
around the fact that the driver would not active the 5GHz channel
on the adapter, which at the moment has gone nowhere.

regards,
Steve


On Tue, Jan 24, 2017 at 12:12 AM, poma
mailto:pomidorabelis...@gmail.com>
>> 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/download/for_home/wireless_adapters/wireless_adapters_ac1750_dual-band/ew-7833uac


   
>
>

http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip


   
>
>
> 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_v

Re: Repair/upgrade damaged Fedora 23 system

2017-01-26 Thread Tom H 
On Tue, Jan 3, 2017 at 4:19 PM, Chris Murphy  wrote:
>
> Fedora's GRUB puts the grub.cfg on the EFI System partition. It's
> non-standard. Path is /boot/efi/EFI/fedora/
>
> Please don't use grub2-install which is obsolete on UEFI computers.

This is a Fedora "peculiarity." On other distros, you can run:

grub-install --target=x86_64-efi --efi-directory=/boot/efi
--bootloader-id=whatever --recheck
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org