Re: RANT: installing fedora is now a real punishment!
On Wed, 2017-02-01 at 14:34 +0100, François Patte wrote: > [snip] > 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! > > Well, here's what Fedora says to do: https://docs.fedoraproject.org/en-US/Fedora/23/html/System_Administrato rs_Guide/sec-Changing_and_Resetting_the_Root_Password.html Sometimes these guidelines are a bit outdated, but it's a starting point, I guess. Personally, when I do an install, I do it in stages. I'll do a minimal installation, and then install all my software, environments, etc. later. That way, if something in the basic install screws up, I can do a reinstall more quickly -- in 15-30 mins or so. I used to try to install everything at the beginning, but ended up with having to repeat hour to 2 hour long installs. As an aside, my experience has been the opposite of yours. I did an upgrade that went well. About a week later, my dog knocked my laptop off the table, which caused physical damage to the hard drive. My box wouldn't boot -- many system files were damaged. So, I downloaded a small live version, and booted up. I was able to backup most of my home directory, and then did and fsck -c on the encrypted drive. About 2500 blocks were damaged, but it managed to rewrite the bad block inode. Then I installed fedora 25 from a live distro -- and it came up great. It took about 20 mins to install (and then an hour and a half to install all the software and such). billo ___ 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
On 02/01/2017 01:07 PM, Stephen Morris wrote:
> On 1/2/17 8:27 am, Rick Stevens wrote:
>> On 01/31/2017 01:47 PM, Stephen Morris wrote:
$ rfkill unblock wifi
OR
$ nmcli radio wifi on
IF
$ systemctl is-active NetworkManager
active
AND
subsequently
$ nmcli device wifi list
to show the APs within the range.
$ rpm -qi NetworkManager-wifi | grep Summary
Summary : Wifi plugin for NetworkManager
It is installed, right?
> 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?
>
It is not for for D-Link DWA-192 - VID/PID 2001:331a is already there
https://github.com/diederikdehaas/rtl8814AU/blob/driver-4.3.21/os_dep/linux/usb_intf.c#L208
>>> I've isolated one problem I have with this. Device wlp4s6 is still there
>>> and it is an old pci wireless device that I thought was dead. It looks
>>> like it wasn't and all the time that I thought I was using the DWA192 I
>>> was actually using the pci device, so I need to provide an apology to
>>> everyone who provided help on this, I was working under a false
>>> impression.
>>>
>>> But having compiled the 8814au driver that I downloaded from the web
>>> site you provided it seems to be using working now on the 5GHz channel,
>>> but the device has a blue light around the middle of it that the driver
>>> seems to be flashing all the time. When the device is active the light
>>> should be permanently on and goes out when connection to the net is
>>> lost. I could switch the light off but that defeats the purpose of what
>>> it is for. Under windows that process works correctly.
>>>
>>> In network manager the device it is talking to shows this: wlp3s0u2
>>> (0E:13:3D:F9:D2:A4). I thought the information within the brackets was
>>> the mac address of the device, but if I am correct it has determined the
>>> mac address incorrectly.
>> Yes, that should be the MAC address of the device. The newer kernels
>> number the network devices in the order they're discovered on the bus
>> and name them according to their position in the bus (e.g. "p4s0"
>> meaning PCI device 4, subdevice 0). Typically hardwired stuff starts
>> off with "en", wireless with "wl". Toss in USB and I'm not sure what
>> they'd be.
>>
>> In your case, the PCI device is probably found first and would be, by
>> default, the one NM tries to use. Your USB dongle would probably be
>> discovered last and you'll need to tell NM to use it in place of the
>> PCI card.
>>
>> Again, "ip link show" will show you the various network devices you
>> have, along with their names and in the "link/ether" line for each
>> device, the MAC address of the device. You can then use "ethtool -i
>> " to see which driver that device is using. Make note of
>> the MAC address of your new device and make sure it's using the driver
>> you expect it to use.
>>
>> If you really want to start from scratch, then in NM, I would delete
>> any existing configurations you have, then click "Add", then select
>> "Wi-Fi" in the "Connection Type" window. In the "Wi-Fi" tab, fill in
>> the SSID of your wireless network, select "Client" (or "Managed") in
>> the "Mode" field, then use the drop-down in "Device" and select the MAC
>> of the new device.
>>
>> Click the "Wi-Fi Security" tab, fill in the appropriate data. Finally,
>> click the "General" tab and tick the "Automatically connect to this
>> network when it is available" option, then click "Save". Hopefully,
>> it'll come right up with a DHCP address. If not, right-click on the NM
>> applet, disable networking, then re-enable it.
> Yesterday, after sending this message, I changed the contents within the
> brackets to the correct mac address, because as well as the entry in the
> list for the old pci card there was an entry with no device but had the
> correct the correct mac address within brackets.
> This morning I tried to compile a beta driver that from the website I
> got the impression was designed to support the rtl8812au, rtl8814au and
> rtl8821au chipsets but when compiled it produced and 8812.ko kernel
> module which when activated Fedora would not use for the device as the
> device could not be activated by networkmanager.
> Consequently I have just gone back to the rtl8814au driver and activated
> that which has then immediately enable the device. When I look at
> networkmanager at the existing definitions I was looking at yesterday
> that had the 3 devices in the 'Restrict to Device' list, that drop down
> list now only has one entry which is the entry for the usb device with
> the correct mac address (wlp3s0u2 (6C:72:20:00:AC:C4)). I'm no
Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
On 1/2/17 2:36 pm, poma wrote: On 31.01.2017 22:47, Stephen Morris wrote: [...] but the device has a blue light around the middle of it that the driver seems to be flashing all the time. When the device is active the light should be permanently on and goes out when connection to the net is lost. I could switch the light off but that defeats the purpose of what it is for. Under windows that process works correctly. http://support.dlink.com/ContactSupport.aspx?m=DWA-192 What was the reply from D-Link Support upon that question? I couldn't see anything in their frequently asked questions relative to this so I have sent them an email to ask them. I'm about to try to interface the source code for this driver to dkms so that it will get compiled every time I boot from a new kernel, but at the moment I'm not sure how to tell dkms where to find the source code, so I'll have to try to investigate that. regards, Steve ___ 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
On 1/2/17 8:27 am, Rick Stevens wrote:
On 01/31/2017 01:47 PM, Stephen Morris wrote:
$ rfkill unblock wifi
OR
$ nmcli radio wifi on
IF
$ systemctl is-active NetworkManager
active
AND
subsequently
$ nmcli device wifi list
to show the APs within the range.
$ rpm -qi NetworkManager-wifi | grep Summary
Summary : Wifi plugin for NetworkManager
It is installed, right?
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?
It is not for for D-Link DWA-192 - VID/PID 2001:331a is already there
https://github.com/diederikdehaas/rtl8814AU/blob/driver-4.3.21/os_dep/linux/usb_intf.c#L208
I've isolated one problem I have with this. Device wlp4s6 is still there
and it is an old pci wireless device that I thought was dead. It looks
like it wasn't and all the time that I thought I was using the DWA192 I
was actually using the pci device, so I need to provide an apology to
everyone who provided help on this, I was working under a false impression.
But having compiled the 8814au driver that I downloaded from the web
site you provided it seems to be using working now on the 5GHz channel,
but the device has a blue light around the middle of it that the driver
seems to be flashing all the time. When the device is active the light
should be permanently on and goes out when connection to the net is
lost. I could switch the light off but that defeats the purpose of what
it is for. Under windows that process works correctly.
In network manager the device it is talking to shows this: wlp3s0u2
(0E:13:3D:F9:D2:A4). I thought the information within the brackets was
the mac address of the device, but if I am correct it has determined the
mac address incorrectly.
Yes, that should be the MAC address of the device. The newer kernels
number the network devices in the order they're discovered on the bus
and name them according to their position in the bus (e.g. "p4s0"
meaning PCI device 4, subdevice 0). Typically hardwired stuff starts
off with "en", wireless with "wl". Toss in USB and I'm not sure what
they'd be.
In your case, the PCI device is probably found first and would be, by
default, the one NM tries to use. Your USB dongle would probably be
discovered last and you'll need to tell NM to use it in place of the
PCI card.
Again, "ip link show" will show you the various network devices you
have, along with their names and in the "link/ether" line for each
device, the MAC address of the device. You can then use "ethtool -i
" to see which driver that device is using. Make note of
the MAC address of your new device and make sure it's using the driver
you expect it to use.
If you really want to start from scratch, then in NM, I would delete
any existing configurations you have, then click "Add", then select
"Wi-Fi" in the "Connection Type" window. In the "Wi-Fi" tab, fill in
the SSID of your wireless network, select "Client" (or "Managed") in
the "Mode" field, then use the drop-down in "Device" and select the MAC
of the new device.
Click the "Wi-Fi Security" tab, fill in the appropriate data. Finally,
click the "General" tab and tick the "Automatically connect to this
network when it is available" option, then click "Save". Hopefully,
it'll come right up with a DHCP address. If not, right-click on the NM
applet, disable networking, then re-enable it.
Yesterday, after sending this message, I changed the contents within the
brackets to the correct mac address, because as well as the entry in the
list for the old pci card there was an entry with no device but had the
correct the correct mac address within brackets.
This morning I tried to compile a beta driver that from the website I
got the impression was designed to support the rtl8812au, rtl8814au and
rtl8821au chipsets but when compiled it produced and 8812.ko kernel
module which when activated Fedora would not use for the device as the
device could not be activated by networkmanager.
Consequently I have just gone back to the rtl8814au driver and activated
that which has then immediately enable the device. When I look at
networkmanager at the existing definitions I was looking at yesterday
that had the 3 devices in the 'Restrict to Device' list, that drop down
list now only has one entry which is the entry for the usb device with
the correct mac address (wlp3s0u2 (6C:72:20:00:AC:C4)). I'm not sure
what the u2 in the device name means, but I have 9 usb ports which are a
mixture of usb 2 and usb 3 ports for 8 of the ports, and a 9th port that
is self booting to allow updating of the motherboard bios from a usb stick.
My ethernet device has device name enp7s0.
regards,
Steve
--
- Rick Stevens
Re: RANT: installing fedora is now a real punishment!
You could also tryecho "password" | passwd root --stdin to get the root password changed to something you like. --- Regards, Kevin Martin On Wed, Feb 1, 2017 at 8:36 AM, Ralf Corsepius wrote: > On 02/01/2017 02:34 PM, François Patte wrote: > > 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've seen this happening, when permissions and/or ownership of ssh-related > directories were too open or incorrect[1]. > > To remedy this, try to boot from another medium (dvd/usb), mount your / > (and /home) and check permissions/ownership of /etc/ssh/* and > /home//.ssh. > > What I also experienced, was being unable to initially log-in with SELinux > enabled, seemingly because SELinux was broken after upgrades. > There, I first had to boot with SELinux disabled (Adding selinux=0 to the > grub-prompt) to get into the machine, issue a "touch /.autorelabel" and > reboot. > > Ralf > > [1] Seems to me as if previous Fedora versions allowed to set them to what > ssh nowadays considers "too open" and upgrades carried these over. > > > > ___ > 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: RANT: installing fedora is now a real punishment!
On 02/01/2017 02:34 PM, François Patte wrote: 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've seen this happening, when permissions and/or ownership of ssh-related directories were too open or incorrect[1]. To remedy this, try to boot from another medium (dvd/usb), mount your / (and /home) and check permissions/ownership of /etc/ssh/* and /home//.ssh. What I also experienced, was being unable to initially log-in with SELinux enabled, seemingly because SELinux was broken after upgrades. There, I first had to boot with SELinux disabled (Adding selinux=0 to the grub-prompt) to get into the machine, issue a "touch /.autorelabel" and reboot. Ralf [1] Seems to me as if previous Fedora versions allowed to set them to what ssh nowadays considers "too open" and upgrades carried these over. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: RANT: installing fedora is now a real punishment!
On Wed, Feb 01, 2017 at 02:34:32PM +0100, François Patte wrote: > 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! Is it possible that there's a problem with the keyboard configuration (either now or during the install)? > If I ask passwd, I have 1 second to type the password before falling > back to prompt... So I can't type anything! This is... odd. Can you describe in more detail what you are doing here? -- Matthew Miller Fedora Project Leader ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: RANT: installing fedora is now a real punishment!
On 01.02.2017 13:34, François Patte wrote:
> 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 [1]
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
Firstly, its NOT chpasswd but root@localhost # password and / or
root@localhost # passwd {USERNAME}
Secondly, /home has possible USER SPECIFIC pam.d/ sshd/ gnupg/ and other
assorted configs that can be VERY relevant for a rescue system.
--
Corey W Sheldon
ph: +1 (310).909.7672
0x8B4E89435A88E539 0x59276298D2264944
Freelance IT Consultant, Multi-Discipline Tutor
Fedora AmbaNA (linuxmodder)
Ameridea LLC Founder, President
Find me elsewhere:
https://gist.github.com/linux-modder/ac5dc6fa211315c633c9
"One must never underestimate the power of boredom...from which
creativity and laziness are borne, which can spark great works of chaos
and genius." --Anonymous
"Any man willing to retreat freedom for security is deserving of
neither." (Pp) -- Benjamin Franklin.
This document, including attachments, is intended for the person or
company named and contains confidential and/or legally privileged
information. Unauthorized disclosure, copying or use of this information
may be unlawful and is prohibited. If you are not the intended
recipient, please destroy this message and notify the sender.
Links:
--
[1] http://www.math-info.univ-paris5.fr/~patte
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
RANT: installing fedora is now a real punishment!
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 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: Dummy audio and no Wifi after upgrading to f25
On 02/01/2017 12:03 AM, Tomas Repik wrote: Thank you all, i solved both issues by installing yet another kernel. I tried like three or four of them before and with no result but the 4.8.6-300.fc25.x86_64 version is working just fine. Thank you for your support. The newer kernels didn't work? Current F25 kernel is 4.9.6. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Dummy audio and no Wifi after upgrading to f25
Thank you all, i solved both issues by installing yet another kernel. I tried like three or four of them before and with no result but the 4.8.6-300.fc25.x86_64 version is working just fine. Thank you for your support. Tomas - Original Message - > That usually means that no kernel module is registered to handle that > device. Do you still have one of the F24 kernels? If so, try booting > it and see if they are claimed there. Otherwise, show us the output of > "lspci". > ___ > 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
