Re: Debian Installer Bug -Wifi driver not installed
Peter Ehlert writes: > SOLVED Thank You Very Much, Peter^^^ (because that is very important part in installing i think) Sincerely, -- ^고맙습니다 _地平天成_ 감사합니다_^))//
Re: Debian Installer Bug -Wifi driver not installed
SOLVED add this to /etc/NetworkManager/NetworkManager.conf per bug #835553 [device] wifi.scan-rand-mac-address=no That worked for me with a Ralink Technology, Corp. RT5370 Wireless Adapter on Debian Stretch. Thank you very much. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842422#40 On 11/9/19 8:18 AM, Peter Ehlert wrote: I have a desktop computer running Debian Buster Mate that I want to move to a different location and use Wifi. Using a cheap USB dongle NetworkManager Applet detects the device, lets me select from available networks, accepts password, but will not connect..and after a few moments it closes.. Thinking the drivers were not installed (user error) I tried a fresh Net install alongside. firmware-10.1.0-amd64-netinst.iso I unplugged the ethernet cable was unplugged, the installer detected the USB device, install worked as expected. First boot, again the device is detected with NetworkManager Applet, but same thing... will not connect and after a few moments it closes. I also tried Buster Mate Live. debian-live-10.1.0-amd64-mate+nonfree.iso D-I installer works but the result is the same as the Net installer. device detected, but will not connect. Running a Live session device detected, but will not connect. Ubuntu Mate works, Linux Mint Mate works. ... I am at a loss of where to begin. Network: Device-1: Intel 82579LM Gigabit Network driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: 10:60:4b:73:2b:08 Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb IF: wlx0013efcc2c72 state: down mac: 2e:be:92:09:c9:f5 System: Host: 6300buster Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster) Machine: Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF === as a reality check I moved the USB Wifi dongle to another machine one meter away and it has the same problem device detected, but will not connect. System: Host: z620-9 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster)
Re: Debian Installer Bug -Wifi driver not installed
On Sat, 9 Nov 2019, Peter Ehlert wrote: > Date: Sat, 9 Nov 2019 13:28:02 > From: Peter Ehlert > To: debian-user@lists.debian.org > Subject: Re: Debian Installer Bug -Wifi driver not installed > Resent-Date: Sat, 9 Nov 2019 18:45:09 + (UTC) > Resent-From: debian-user@lists.debian.org > > > On 11/9/19 9:25 AM, Patrick Bartek wrote: > > On Sat, 9 Nov 2019 06:16:17 -0800 > > Peter Ehlert wrote: > > > >> I have a desktop computer running Debian Buster Mate that I want to move > >> to a different location and use Wifi. > >> Using a cheap USB dongle NetworkManager Applet detects the device, lets > >> me select from available networks, accepts password, but will not > >> connect..and after a few moments it closes.. > >> > >> Thinking the drivers were not installed (user error) I tried a fresh Net > >> install alongside. > >> ?firmware-10.1.0-amd64-netinst.iso > >> I unplugged the ethernet cable was unplugged, the installer detected the > >> USB device, install worked as expected. > >> First boot, again the device is detected with NetworkManager Applet, but > >> same thing... will not connect and after a few moments it closes. > >> > >> I also tried Buster Mate Live. > >> ?debian-live-10.1.0-amd64-mate+nonfree.iso > >> D-I installer works but the result is the same as the Net installer. > >> device detected, but will not connect. > >> Running a Live session device detected, but will not connect. > >> > >> Ubuntu Mate works, Linux Mint Mate works. > >> > >> ... I am at a loss of where to begin. > >> > >> > >> > >> > >> Network: > >> ? Device-1: Intel 82579LM Gigabit Network driver: e1000e > >> ? IF: eno1 state: up speed: 100 Mbps duplex: full mac: 10:60:4b:73:2b:08 > >> ? Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb > >> ? IF: wlx0013efcc2c72 state: down mac: 2e:be:92:09:c9:f5 > >> > >> > >> System: > >> ? Host: 6300buster Kernel: 4.19.0-6-amd64 x86_64 bits: 64 > >> ? Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster) > >> Machine: > >> ? Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF > >> === > >> as a reality check I moved the USB Wifi dongle to another machine one > >> meter away and it has the same problem > >> device detected, but will not connect. > >> > >> System: > >> ? Host: z620-9 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE > >> 1.20.4 > >> ? Distro: Debian GNU/Linux 10 (buster) > >> > > A few months ago I had to do the same thing -- switch from wired to > > wireless on this box that only had ever run wired -- but with Stretch. > > Since I don't run a desktop environment (window manager only Openbox) > > and sysvinit instead of systemd, I did the configuration manually. I > > didn't need a network config tool as I would only be connecting to one > > wireless (and only one) access point. > > > > Have you installed wpa supplicant? And is it configured properly? > wpasupplicant is installed > > > > Have you installed the firmware for your particular USB dongle? As > > you're using a ralink device, it will be named firmware-ralink or > > something similar. It's in the non-free repo. > firmware-ralink is installed > > Check /etc/network/interfaces and /etc/NetworkManager/ Is all > > configured properly? > I will review, but don't have much of an idea what the configurations should > be > > > > Read the man pages for interfaces, wpa_supplicant, etc. Also Debian > > does have wikis on configuring wireless. > thanks, I will work on understanding that too > > > > B > > Check version numbers on network manager packages on all three of these systems. It could be you need to wait for debian to update network manager so its version number matches linux mint mate and ubuntu mate. > > > > > > --
Re: Debian Installer Bug -Wifi driver not installed
On 11/9/19 9:25 AM, Patrick Bartek wrote: On Sat, 9 Nov 2019 06:16:17 -0800 Peter Ehlert wrote: I have a desktop computer running Debian Buster Mate that I want to move to a different location and use Wifi. Using a cheap USB dongle NetworkManager Applet detects the device, lets me select from available networks, accepts password, but will not connect..and after a few moments it closes.. Thinking the drivers were not installed (user error) I tried a fresh Net install alongside. firmware-10.1.0-amd64-netinst.iso I unplugged the ethernet cable was unplugged, the installer detected the USB device, install worked as expected. First boot, again the device is detected with NetworkManager Applet, but same thing... will not connect and after a few moments it closes. I also tried Buster Mate Live. debian-live-10.1.0-amd64-mate+nonfree.iso D-I installer works but the result is the same as the Net installer. device detected, but will not connect. Running a Live session device detected, but will not connect. Ubuntu Mate works, Linux Mint Mate works. ... I am at a loss of where to begin. Network: Device-1: Intel 82579LM Gigabit Network driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: 10:60:4b:73:2b:08 Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb IF: wlx0013efcc2c72 state: down mac: 2e:be:92:09:c9:f5 System: Host: 6300buster Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster) Machine: Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF === as a reality check I moved the USB Wifi dongle to another machine one meter away and it has the same problem device detected, but will not connect. System: Host: z620-9 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster) A few months ago I had to do the same thing -- switch from wired to wireless on this box that only had ever run wired -- but with Stretch. Since I don't run a desktop environment (window manager only Openbox) and sysvinit instead of systemd, I did the configuration manually. I didn't need a network config tool as I would only be connecting to one wireless (and only one) access point. Have you installed wpa supplicant? And is it configured properly? wpasupplicant is installed Have you installed the firmware for your particular USB dongle? As you're using a ralink device, it will be named firmware-ralink or something similar. It's in the non-free repo. firmware-ralink is installed Check /etc/network/interfaces and /etc/NetworkManager/ Is all configured properly? I will review, but don't have much of an idea what the configurations should be Read the man pages for interfaces, wpa_supplicant, etc. Also Debian does have wikis on configuring wireless. thanks, I will work on understanding that too B
Re: Debian Installer Bug -Wifi driver not installed
On Sat, 9 Nov 2019 06:16:17 -0800 Peter Ehlert wrote: > I have a desktop computer running Debian Buster Mate that I want to move > to a different location and use Wifi. > Using a cheap USB dongle NetworkManager Applet detects the device, lets > me select from available networks, accepts password, but will not > connect..and after a few moments it closes.. > > Thinking the drivers were not installed (user error) I tried a fresh Net > install alongside. > firmware-10.1.0-amd64-netinst.iso > I unplugged the ethernet cable was unplugged, the installer detected the > USB device, install worked as expected. > First boot, again the device is detected with NetworkManager Applet, but > same thing... will not connect and after a few moments it closes. > > I also tried Buster Mate Live. > debian-live-10.1.0-amd64-mate+nonfree.iso > D-I installer works but the result is the same as the Net installer. > device detected, but will not connect. > Running a Live session device detected, but will not connect. > > Ubuntu Mate works, Linux Mint Mate works. > > ... I am at a loss of where to begin. > > > > > Network: > Device-1: Intel 82579LM Gigabit Network driver: e1000e > IF: eno1 state: up speed: 100 Mbps duplex: full mac: 10:60:4b:73:2b:08 > Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb > IF: wlx0013efcc2c72 state: down mac: 2e:be:92:09:c9:f5 > > > System: > Host: 6300buster Kernel: 4.19.0-6-amd64 x86_64 bits: 64 > Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster) > Machine: > Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF > === > as a reality check I moved the USB Wifi dongle to another machine one > meter away and it has the same problem > device detected, but will not connect. > > System: > Host: z620-9 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 > Distro: Debian GNU/Linux 10 (buster) > A few months ago I had to do the same thing -- switch from wired to wireless on this box that only had ever run wired -- but with Stretch. Since I don't run a desktop environment (window manager only Openbox) and sysvinit instead of systemd, I did the configuration manually. I didn't need a network config tool as I would only be connecting to one wireless (and only one) access point. Have you installed wpa supplicant? And is it configured properly? Have you installed the firmware for your particular USB dongle? As you're using a ralink device, it will be named firmware-ralink or something similar. It's in the non-free repo. Check /etc/network/interfaces and /etc/NetworkManager/ Is all configured properly? Read the man pages for interfaces, wpa_supplicant, etc. Also Debian does have wikis on configuring wireless. B
Debian Installer Bug -Wifi driver not installed
I have a desktop computer running Debian Buster Mate that I want to move to a different location and use Wifi. Using a cheap USB dongle NetworkManager Applet detects the device, lets me select from available networks, accepts password, but will not connect..and after a few moments it closes.. Thinking the drivers were not installed (user error) I tried a fresh Net install alongside. firmware-10.1.0-amd64-netinst.iso I unplugged the ethernet cable was unplugged, the installer detected the USB device, install worked as expected. First boot, again the device is detected with NetworkManager Applet, but same thing... will not connect and after a few moments it closes. I also tried Buster Mate Live. debian-live-10.1.0-amd64-mate+nonfree.iso D-I installer works but the result is the same as the Net installer. device detected, but will not connect. Running a Live session device detected, but will not connect. Ubuntu Mate works, Linux Mint Mate works. ... I am at a loss of where to begin. Network: Device-1: Intel 82579LM Gigabit Network driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: 10:60:4b:73:2b:08 Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb IF: wlx0013efcc2c72 state: down mac: 2e:be:92:09:c9:f5 System: Host: 6300buster Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster) Machine: Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF === as a reality check I moved the USB Wifi dongle to another machine one meter away and it has the same problem device detected, but will not connect. System: Host: z620-9 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster)
Debian Installer Bug -Wifi driver not installed
I have a desktop computer running Debian Buster Mate that I want to move to a different location and use Wifi. Using a cheap USB dongle NetworkManager Applet detects the device, lets me select from available networks, accepts password, but will not connect..and after a few moments it closes.. Thinking the drivers were not installed (user error) I tried a fresh Net install alongside. firmware-10.1.0-amd64-netinst.iso I unplugged the ethernet cable was unplugged, the installer detected the USB device, install worked as expected. First boot, again the device is detected with NetworkManager Applet, but same thing... will not connect and after a few moments it closes. I also tried Buster Mate Live. debian-live-10.1.0-amd64-mate+nonfree.iso D-I installer works but the result is the same as the Net installer. device detected, but will not connect. Running a Live session device detected, but will not connect. Ubuntu Mate works, Linux Mint Mate works. ... I am at a loss of where to begin. Network: Device-1: Intel 82579LM Gigabit Network driver: e1000e IF: eno1 state: up speed: 100 Mbps duplex: full mac: 10:60:4b:73:2b:08 Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb IF: wlx0013efcc2c72 state: down mac: 2e:be:92:09:c9:f5 System: Host: 6300buster Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster) Machine: Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF === as a reality check I moved the USB Wifi dongle to another machine one meter away and it has the same problem device detected, but will not connect. System: Host: z620-9 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: MATE 1.20.4 Distro: Debian GNU/Linux 10 (buster)
Debian installer bug
After choosing network card, it cannot be changed during setup, even if I press Network setup. Used Netinstall CD 6.0.4 i386 and text setup. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/361551333989...@web40.yandex.ru
Re: Debian installer bug
On Mon, 09 Apr 2012 20:36:39 +0400, Рыжков Алексей wrote: After choosing network card, it cannot be changed during setup, even if I press Network setup. Used Netinstall CD 6.0.4 i386 and text setup. What do you mean by it cannot be changed? You mean an additional NIC is no detected once you have choosen one to proceed with the installation or that you can't change the network settings (IP address, netmask...)? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jlv6qn$ss9$2...@dough.gmane.org
Re: discover1 vs discover vs discover2 debian installer bug
On Mon, 2005-05-16 at 10:30 -0400, Mitchell Laks wrote: On Monday 16 May 2005 10:04 am, Mitchell Laks wrote: discover issues: I have seen references to /media/cdrom0 and /media/cdrom2 not being created as a result of a bug in discover. apt-cache show discover1 is what i have loaded. it is credited to the debian installer team version 1.7.7 is current. discover2 is version 2.0.7-2.1 credited to the discover workers and is in conflict with discover1. i did a debian sarge install with i guess discover1. is my problem the need to switch to discover2 which fixed the bug? Even though I googled and found a ubunto thread that claimed that the /media/cdom0 was fixed with later discover versions, and i tried this solution and I am running sid, and upgraded to discover = discover2 from discover1, i still have the problem. Desktop System Setup with Debian GNU/Linux 3.1 'Sarge' located at http://thegoldenear.org/toolbox/unices/desktop-system-setup-debian-sarge.html#installation mentions this problem abd suggests work around. (In Installation section): When asked during the installation if you want 'discover' to manage /media/cdrom0, choose 'no' otherwise gnome-volume-manager won't be able to auto-mount discs for you when inserted and logged in as a normal user. (this may now be fixed). In troubleshooting section. gnome-volume-manager won't be able to auto-mount discs when inserted if discover/discover1 is managing /media/cdrom0 because that directory will get removed by discover/discover1. To fix this, either choose not to have discover/discover1 do this at installation (see note in the 'Installation' section; or uninstall discover/discover1 (but we don't yet know of other ramifications of doing this); or there should be a way of disabling this aspect of discover/discover1 once its installed, but we don't know of it yet) I wonder if one should simple reconfigure discover to stop it from removing CDROM. sudo dpkg-reconfigure discover1 if so has this been passed to the debian installer team? i am suprised to have to do mkdir /media/cdrom[01] each time i reboot. I know how to write my own init script to do this, and yet it seems stupid to have to do this. what is overwriting /media or over mounting /media??? mitchell -- __ Ivan Teliatnikovphone: +61 2 9351 2031 F05, Edgworth David Bld. fax: +61 2 9351 0184 School of Geosciences email: [EMAIL PROTECTED] Univrsity of Sydney www: http://www.geosci.usyd.edu.au Australia __ -- __ Ivan Teliatnikovphone: +61 2 9351 2031 F05, Edgworth David Bld. fax: +61 2 9351 0184 School of Geosciences email: [EMAIL PROTECTED] Univrsity of Sydney www: http://www.geosci.usyd.edu.au Australia __ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: discover1 vs discover vs discover2 debian installer bug
On Monday 23 May 2005 10:22 am, Ivan Teliatnikov wrote: Desktop System Setup with Debian GNU/Linux 3.1 'Sarge' located at http://thegoldenear.org/toolbox/unices/desktop-system-setup-debian-sarge.ht ml#installation mentions this problem abd suggests work around. (In Installation section): When asked during the installation if you want 'discover' to manage /media/cdrom0, choose 'no' otherwise gnome-volume-manager won't be able to auto-mount discs for you when inserted and logged in as a normal user. (this may now be fixed). You are 100% right! As soon as I changed this setting by running dpkg-reconfigure discover1 I was able to create a directory /media/cdrom1 and /media/cdrom0 without it going away on reboot. I should point out a typo in that web-page posting though. if you run dpkg-reconfigure on discover1 it does not mention /media/cdrom0. It talks about /dev/cdrom1 instead. Thats why i never tried the other setting :). this must be a typo as well. thank you! Mitchell In troubleshooting section. gnome-volume-manager won't be able to auto-mount discs when inserted if discover/discover1 is managing /media/cdrom0 because that directory will get removed by discover/discover1. To fix this, either choose not to have discover/discover1 do this at installation (see note in the 'Installation' section; or uninstall discover/discover1 (but we don't yet know of other ramifications of doing this); or there should be a way of disabling this aspect of discover/discover1 once its installed, but we don't know of it yet) I wonder if one should simple reconfigure discover to stop it from removing CDROM. sudo dpkg-reconfigure discover1 if so has this been passed to the debian installer team? i am suprised to have to do mkdir /media/cdrom[01] each time i reboot. I know how to write my own init script to do this, and yet it seems stupid to have to do this. what is overwriting /media or over mounting /media??? mitchell -- __ Ivan Teliatnikovphone: +61 2 9351 2031 F05, Edgworth David Bld. fax: +61 2 9351 0184 School of Geosciences email: [EMAIL PROTECTED] Univrsity of Sydney www: http://www.geosci.usyd.edu.au Australia __ -- __ Ivan Teliatnikovphone: +61 2 9351 2031 F05, Edgworth David Bld. fax: +61 2 9351 0184 School of Geosciences email: [EMAIL PROTECTED] Univrsity of Sydney www: http://www.geosci.usyd.edu.au Australia __ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
discover1 vs discover vs discover2 debian installer bug
discover issues: I have seen references to /media/cdrom0 and /media/cdrom2 not being created as a result of a bug in discover. apt-cache show discover1 is what i have loaded. it is credited to the debian installer team version 1.7.7 is current. discover2 is version 2.0.7-2.1 credited to the discover workers and is in conflict with discover1. i did a debian sarge install with i guess discover1. is my problem the need to switch to discover2 which fixed the bug? if so has this been passed to the debian installer team? mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: discover1 vs discover vs discover2 debian installer bug
On Monday 16 May 2005 10:04 am, Mitchell Laks wrote: discover issues: I have seen references to /media/cdrom0 and /media/cdrom2 not being created as a result of a bug in discover. apt-cache show discover1 is what i have loaded. it is credited to the debian installer team version 1.7.7 is current. discover2 is version 2.0.7-2.1 credited to the discover workers and is in conflict with discover1. i did a debian sarge install with i guess discover1. is my problem the need to switch to discover2 which fixed the bug? Even though I googled and found a ubunto thread that claimed that the /media/cdom0 was fixed with later discover versions, and i tried this solution and I am running sid, and upgraded to discover = discover2 from discover1, i still have the problem. if so has this been passed to the debian installer team? i am suprised to have to do mkdir /media/cdrom[01] each time i reboot. I know how to write my own init script to do this, and yet it seems stupid to have to do this. what is overwriting /media or over mounting /media??? mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
