Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #222766 > unrolled thread

Can't get started

Back to article view | Back to linux.debian.user

Contents

  Can't get started Matthew Campbell <trenix25@pm.me> - 2020-05-28 02:40 +0200
    Re: Can't get started Peter Ehlert <peter@sdi-baja.com> - 2020-05-28 03:20 +0200
    Re: Can't get started David Wright <deblis@lionunicorn.co.uk> - 2020-05-28 05:00 +0200
      Re: Can't get started Matthew Campbell <trenix25@pm.me> - 2020-05-28 14:50 +0200
        Re: Can't get started Dan Ritter <dsr@randomstring.org> - 2020-05-28 16:00 +0200
          Re: Can't get started Greg Wooledge <wooledg@eeg.ccf.org> - 2020-05-28 16:10 +0200
            Re: Can't get started Dan Ritter <dsr@randomstring.org> - 2020-05-28 16:10 +0200
          Re: Can't get started Peter Ehlert <pb21a@sdi-baja.com> - 2020-05-28 16:10 +0200
            Re: Can't get started Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-29 10:30 +0200
        Re: Can't get started David Wright <deblis@lionunicorn.co.uk> - 2020-05-28 16:10 +0200
          Re: Can't get started Matthew Campbell <trenix25@pm.me> - 2020-05-29 00:00 +0200
            Re: Can't get started David Wright <deblis@lionunicorn.co.uk> - 2020-05-29 06:00 +0200
              Re: Can't get started Matthew Campbell <trenix25@pm.me> - 2020-05-29 11:00 +0200
          Re: Can't get started Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-29 10:40 +0200
            Re: Can't get started David Wright <deblis@lionunicorn.co.uk> - 2020-05-29 16:40 +0200
              Re: Can't get started Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-29 18:00 +0200
                Re: Can't get started David Wright <deblis@lionunicorn.co.uk> - 2020-05-29 22:00 +0200
                  Re: Can't get started Matthew Campbell <trenix25@pm.me> - 2020-05-29 22:20 +0200
                  Re: Can't get started Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-30 07:30 +0200
                    Re: Can't get started David Wright <deblis@lionunicorn.co.uk> - 2020-05-30 23:20 +0200
                      Re: Can't get started Andrei POPESCU <andreimpopescu@gmail.com> - 2020-06-01 08:40 +0200
                        Re: Can't get started David Wright <deblis@lionunicorn.co.uk> - 2020-06-01 20:30 +0200
              Re: Can't get started Matthew Campbell <trenix25@pm.me> - 2020-05-29 22:10 +0200
                Re: Can't get started David Wright <deblis@lionunicorn.co.uk> - 2020-05-30 04:50 +0200
        Re: Can't get started Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-29 10:30 +0200
    Re: Can't get started David Christensen <dpchrist@holgerdanske.com> - 2020-05-28 06:40 +0200
      Re: Can't get started David Christensen <dpchrist@holgerdanske.com> - 2020-05-28 06:50 +0200

Page 1 of 2  [1] 2  Next page →

#222766 — Can't get started

[Multipart message — attachments visible in raw view] — view raw

The netinst CD leaves a lot to be desired. I had to download a nonfree wifi firmware package with my tablet and install it just to get the Linux system on the laptop to recognize the wifi adapter. I still can't get the wifi to work which makes installation impossible. Many of the network related commands do not exist. I cannot just download a package without being able to connect the laptop to the Internet which is impossible if I can't get a wifi connection. I am using Debian 10.4 Buster on a laptop that uses an Intel Centrino Duo CPU. My wifi adapter is registering as wlp3s0. Each "package" to be installed requires the single use of a blank DVD to transfer the file to Linux. I have a very limited number of blank DVDs. It is up, but down, according to ip addr. It says no carrier. The wifi is on and available. The signal strength is sufficient. It is presently offering an open wifi access point. The ssid is correct. How do I fix this? I cannot connect a phone or any other device to the laptop to help "get it started," nor should I need to. The netinst CD should have everything a new user could need to get things working.

name=Matthew%20Campbell&email=trenix25%40pm.me

[toc] | [next] | [standalone]

#222767

paragraphs, try them.

sorry but I can't follow you, you ave a number of issues and complaints 
mixed together

On 5/27/20 5:15 PM, Matthew Campbell wrote:
> The netinst CD leaves a lot to be desired. I had to download a nonfree 
> wifi firmware package with my tablet and install it just to get the 
> Linux system on the laptop to recognize the wifi adapter. I still 
> can't get the wifi to work which makes installation impossible. Many 
> of the network related commands do not exist. I cannot just download a 
> package without being able to connect the laptop to the Internet which 
> is impossible if I can't get a wifi connection. I am using Debian 10.4 
> Buster on a laptop that uses an Intel Centrino Duo CPU. My wifi 
> adapter is registering as wlp3s0. Each "package" to be installed 
> requires the single use of a blank DVD to transfer the file to Linux. 
> I have a very limited number of blank DVDs. It is up, but down, 
> according to ip addr. It says no carrier. The wifi is on and 
> available. The signal strength is sufficient. It is presently offering 
> an open wifi access point. The ssid is correct. How do I fix this? I 
> cannot connect a phone or any other device to the laptop to help "get 
> it started," nor should I need to. The netinst CD should have 
> everything a new user could need to get things working.
>
> name=Matthew%20Campbell&email=trenix25%40pm.me
>
>
>
>

[toc] | [prev] | [next] | [standalone]

#222771

On Thu 28 May 2020 at 00:15:50 (+0000), Matthew Campbell wrote:
> The netinst CD leaves a lot to be desired. I had to download a nonfree wifi firmware package with my tablet and install it just to get the Linux system on the laptop to recognize the wifi adapter. I still can't get the wifi to work which makes installation impossible. Many of the network related commands do not exist. I cannot just download a package without being able to connect the laptop to the Internet which is impossible if I can't get a wifi connection. I am using Debian 10.4 Buster on a laptop that uses an Intel Centrino Duo CPU. My wifi adapter is registering as wlp3s0. Each "package" to be installed requires the single use of a blank DVD to transfer the file to Linux. I have a very limited number of blank DVDs. It is up, but down, according to ip addr. It says no carrier. The wifi is on and available. The signal strength is sufficient. It is presently offering an open wifi access point. The ssid is correct. How do I fix this? I cannot connect a phone or any other device to the laptop to help "get it started," nor should I need to. The netinst CD should have everything a new user could need to get things working.

If I understand your situation, which I might not, try putting this in
the /etc/network/interfaces file:

allow-hotplug wlp3s0
iface wlp3s0 inet dhcp
      wpa-ssid YOUR-WIFI-SSID
      wpa-psk  YOUR-WIFI-PASSWORD

which may get the wifi working for you. (Reboot if necessary.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222801

[Multipart message — attachments visible in raw view] — view raw

Thank you for your polite response. The wifi access point is open so it does not use a password. I don't know if the netinst CD includes the wpasupplicant package. ip addr is saying that Linux cannot detect a signal from the wifi router. I will consider trying DHCP instead of static to see if it makes a difference. I can only hope the netinst CD has included any necessary packages to try DHCP.

name=Matthew%20Campbell&email=trenix25%40pm.me

-------- Original Message --------
On May 27, 2020, 7:50 PM, David Wright wrote:

> On Thu 28 May 2020 at 00:15:50 (+0000), Matthew Campbell wrote:
>> The netinst CD leaves a lot to be desired. I had to download a nonfree wifi firmware package with my tablet and install it just to get the Linux system on the laptop to recognize the wifi adapter. I still can't get the wifi to work which makes installation impossible. Many of the network related commands do not exist. I cannot just download a package without being able to connect the laptop to the Internet which is impossible if I can't get a wifi connection. I am using Debian 10.4 Buster on a laptop that uses an Intel Centrino Duo CPU. My wifi adapter is registering as wlp3s0. Each "package" to be installed requires the single use of a blank DVD to transfer the file to Linux. I have a very limited number of blank DVDs. It is up, but down, according to ip addr. It says no carrier. The wifi is on and available. The signal strength is sufficient. It is presently offering an open wifi access point. The ssid is correct. How do I fix this? I cannot connect a phone or any other device to the laptop to help "get it started," nor should I need to. The netinst CD should have everything a new user could need to get things working.
>
> If I understand your situation, which I might not, try putting this in
> the /etc/network/interfaces file:
>
> allow-hotplug wlp3s0
> iface wlp3s0 inet dhcp
> wpa-ssid YOUR-WIFI-SSID
> wpa-psk YOUR-WIFI-PASSWORD
>
> which may get the wifi working for you. (Reboot if necessary.)
>
> Cheers,
> David.

[toc] | [prev] | [next] | [standalone]

#222805

Matthew Campbell wrote: 
> Thank you for your polite response. The wifi access point is open so it does not use a password. I don't know if the netinst CD includes the wpasupplicant package. ip addr is saying that Linux cannot detect a signal from the wifi router. I will consider trying DHCP instead of static to see if it makes a difference. I can only hope the netinst CD has included any necessary packages to try DHCP.
> 

The netinst CD is for installation from the network. It is
purposefully stripped down.

It does not contain non-free firmware, including the firmware
that must be loaded on some Intel wifi devices to get them to
work.

You probably want a full installer with lots of packages on it,
and especially a version which includes non-free firmware.

Also, USB sticks are rewritable and most systems can boot from
them.

-dsr-

[toc] | [prev] | [next] | [standalone]

#222808

On Thu, May 28, 2020 at 09:58:36AM -0400, Dan Ritter wrote:
> The netinst CD is for installation from the network. It is
> purposefully stripped down.
> 
> It does not contain non-free firmware, including the firmware
> that must be loaded on some Intel wifi devices to get them to
> work.
> 
> You probably want a full installer with lots of packages on it,
> and especially a version which includes non-free firmware.

Note that these two things are orthogonal.  You can get an unofficial
CD-sized installer with non-free firmware, but without desktop
environments and other large packages.  Or you can get a DVD-sized
installer with desktop environments but without non-free firmware.
Or you can get a DVD-sized installer with both.

The official Debian installers lack non-free firmware packages for
philosophical reasons, not size reasons.

[toc] | [prev] | [next] | [standalone]

#222811

Greg Wooledge wrote: 
> On Thu, May 28, 2020 at 09:58:36AM -0400, Dan Ritter wrote:
> > The netinst CD is for installation from the network. It is
> > purposefully stripped down.
> > 
> > It does not contain non-free firmware, including the firmware
> > that must be loaded on some Intel wifi devices to get them to
> > work.
> > 
> > You probably want a full installer with lots of packages on it,
> > and especially a version which includes non-free firmware.
> 
> Note that these two things are orthogonal.  You can get an unofficial
> CD-sized installer with non-free firmware, but without desktop
> environments and other large packages.  Or you can get a DVD-sized
> installer with desktop environments but without non-free firmware.
> Or you can get a DVD-sized installer with both.

The original question mentioned DVDs repeatedly, so I figured
that your last sentence is what he wants. Probably.

-dsr-

[toc] | [prev] | [next] | [standalone]

#222810

Use the non-free netinstall ISO

On May 28, 2020 6:58:54 AM Dan Ritter <dsr@randomstring.org> wrote:

> Matthew Campbell wrote:
>> Thank you for your polite response. The wifi access point is open so it 
>> does not use a password. I don't know if the netinst CD includes the 
>> wpasupplicant package. ip addr is saying that Linux cannot detect a signal 
>> from the wifi router. I will consider trying DHCP instead of static to see 
>> if it makes a difference. I can only hope the netinst CD has included any 
>> necessary packages to try DHCP.
>>
>
> The netinst CD is for installation from the network. It is
> purposefully stripped down.
>
> It does not contain non-free firmware, including the firmware
> that must be loaded on some Intel wifi devices to get them to
> work.
>
> You probably want a full installer with lots of packages on it,
> and especially a version which includes non-free firmware.
>
> Also, USB sticks are rewritable and most systems can boot from
> them.
>
> -dsr-

[toc] | [prev] | [next] | [standalone]

#222851

[Multipart message — attachments visible in raw view] — view raw

On Jo, 28 mai 20, 07:02:49, Peter Ehlert wrote:
> Use the non-free netinstall ISO

Fully agreed.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#222809

On Thu 28 May 2020 at 12:40:44 (+0000), Matthew Campbell wrote:
> On May 27, 2020, 7:50 PM, David Wright wrote:
> > On Thu 28 May 2020 at 00:15:50 (+0000), Matthew Campbell wrote:
> >> The netinst CD leaves a lot to be desired. I had to download a nonfree wifi firmware package with my tablet and install it just to get the Linux system on the laptop to recognize the wifi adapter. I still can't get the wifi to work which makes installation impossible. Many of the network related commands do not exist. I cannot just download a package without being able to connect the laptop to the Internet which is impossible if I can't get a wifi connection. I am using Debian 10.4 Buster on a laptop that uses an Intel Centrino Duo CPU. My wifi adapter is registering as wlp3s0. Each "package" to be installed requires the single use of a blank DVD to transfer the file to Linux. I have a very limited number of blank DVDs. It is up, but down, according to ip addr. It says no carrier. The wifi is on and available. The signal strength is sufficient. It is presently offering an open wifi access point. The ssid is correct. How do I fix this? I cannot connect a phone or any other device to the laptop to help "get it started," nor should I need to. The netinst CD should have everything a new user could need to get things working.
> >
> > If I understand your situation, which I might not, try putting this in
> > the /etc/network/interfaces file:
> >
> > allow-hotplug wlp3s0
> > iface wlp3s0 inet dhcp
> > wpa-ssid YOUR-WIFI-SSID
> > wpa-psk YOUR-WIFI-PASSWORD
> >
> > which may get the wifi working for you. (Reboot if necessary.)
> >
> Thank you for your polite response.
> The wifi access point is open so it does not use a password.

Whenever I've met an open network, I've been on the road, and using a
client like wicd to connect. I can only assume that one leaves out
the password line, or sets it to an empty string.

> I don't know if the netinst CD includes the wpasupplicant package.

Yes. During installation on this machine, it was the 8th package
to be explicitly installed, according to apt's history.log.

It would help to post whether your netinst was one that included
firmware (helps for laptops and suchlike) or not. Also, an outline
of how far you have progressed in the installation. From your OP,
I've presumed you've installed a system with the installer via
wireless, but can't get wifi connectivity since then.

> ip addr is saying that Linux cannot detect a signal from the wifi router.

I didn't know   ip addr   showed that, but I assume the router still
works after you finished a wireless installation.

> I will consider trying DHCP instead of static to see if it makes a difference.

I have no experience of setting up wifi statically—I don't see how
this would work with a portable device. For simplicity therefore,
I set up all my machines in the same manner, generally switching
from ifupdown (the default for non-DE systems) to wicd, my own
preference from years of use.

Which connection method are you attempting to use yourself?

> I can only hope the netinst CD has included any necessary packages to try DHCP.

Yes, it's built into busybox for the actual installation, and then the
real package is installed in the main tranche.

But, if I'm not out of date, there might not be a seamless transition
from wireless during installation to wireless post-installation for
non-DE installers. You may have to update /e/n/i yourself as I showed
earlier.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222836

[Multipart message — attachments visible in raw view] — view raw

Thank you for your polite response. I downloaded the netinst CD disc image and wrote it on a disc and booted from that. Windows can use the wifi adapter in the laptop, but Linux can't. I did specify in my initial post that I also downloaded a firmware package and installed that. I have since downloaded a much larger disc image, about 1.3 GB, but I have not yet had the time to explore it.

The wifi is my own, in my own living room. Windows could not connect if I used WPA2. Only two devices that can connect, that I'm aware of, are in signal range of the 5 GHz access point. Both are already allowed on the wifi.

name=Matthew%20Campbell&email=trenix25%40pm.me

-------- Original Message --------
On May 28, 2020, 7:00 AM, David Wright wrote:

> On Thu 28 May 2020 at 12:40:44 (+0000), Matthew Campbell wrote:
>> On May 27, 2020, 7:50 PM, David Wright wrote:
>> > On Thu 28 May 2020 at 00:15:50 (+0000), Matthew Campbell wrote:
>> >> The netinst CD leaves a lot to be desired. I had to download a nonfree wifi firmware package with my tablet and install it just to get the Linux system on the laptop to recognize the wifi adapter. I still can't get the wifi to work which makes installation impossible. Many of the network related commands do not exist. I cannot just download a package without being able to connect the laptop to the Internet which is impossible if I can't get a wifi connection. I am using Debian 10.4 Buster on a laptop that uses an Intel Centrino Duo CPU. My wifi adapter is registering as wlp3s0. Each "package" to be installed requires the single use of a blank DVD to transfer the file to Linux. I have a very limited number of blank DVDs. It is up, but down, according to ip addr. It says no carrier. The wifi is on and available. The signal strength is sufficient. It is presently offering an open wifi access point. The ssid is correct. How do I fix this? I cannot connect a phone or any other device to the laptop to help "get it started," nor should I need to. The netinst CD should have everything a new user could need to get things working.
>> >
>> > If I understand your situation, which I might not, try putting this in
>> > the /etc/network/interfaces file:
>> >
>> > allow-hotplug wlp3s0
>> > iface wlp3s0 inet dhcp
>> > wpa-ssid YOUR-WIFI-SSID
>> > wpa-psk YOUR-WIFI-PASSWORD
>> >
>> > which may get the wifi working for you. (Reboot if necessary.)
>> >
>> Thank you for your polite response.
>> The wifi access point is open so it does not use a password.
>
> Whenever I've met an open network, I've been on the road, and using a
> client like wicd to connect. I can only assume that one leaves out
> the password line, or sets it to an empty string.
>
>> I don't know if the netinst CD includes the wpasupplicant package.
>
> Yes. During installation on this machine, it was the 8th package
> to be explicitly installed, according to apt's history.log.
>
> It would help to post whether your netinst was one that included
> firmware (helps for laptops and suchlike) or not. Also, an outline
> of how far you have progressed in the installation. From your OP,
> I've presumed you've installed a system with the installer via
> wireless, but can't get wifi connectivity since then.
>
>> ip addr is saying that Linux cannot detect a signal from the wifi router.
>
> I didn't know ip addr showed that, but I assume the router still
> works after you finished a wireless installation.
>
>> I will consider trying DHCP instead of static to see if it makes a difference.
>
> I have no experience of setting up wifi statically—I don't see how
> this would work with a portable device. For simplicity therefore,
> I set up all my machines in the same manner, generally switching
> from ifupdown (the default for non-DE systems) to wicd, my own
> preference from years of use.
>
> Which connection method are you attempting to use yourself?
>
>> I can only hope the netinst CD has included any necessary packages to try DHCP.
>
> Yes, it's built into busybox for the actual installation, and then the
> real package is installed in the main tranche.
>
> But, if I'm not out of date, there might not be a seamless transition
> from wireless during installation to wireless post-installation for
> non-DE installers. You may have to update /e/n/i yourself as I showed
> earlier.
>
> Cheers,
> David.

[toc] | [prev] | [next] | [standalone]

#222842

On Thu 28 May 2020 at 21:54:11 (+0000), Matthew Campbell wrote:
> On May 28, 2020, 7:00 AM, David Wright wrote:
> > On Thu 28 May 2020 at 12:40:44 (+0000), Matthew Campbell wrote:
> >> On May 27, 2020, 7:50 PM, David Wright wrote:
> >> > On Thu 28 May 2020 at 00:15:50 (+0000), Matthew Campbell wrote:
> >> >> The netinst CD leaves a lot to be desired. I had to download a nonfree wifi firmware package with my tablet and install it just to get the Linux system on the laptop to recognize the wifi adapter. I still can't get the wifi to work which makes installation impossible. Many of the network related commands do not exist. I cannot just download a package without being able to connect the laptop to the Internet which is impossible if I can't get a wifi connection. I am using Debian 10.4 Buster on a laptop that uses an Intel Centrino Duo CPU. My wifi adapter is registering as wlp3s0. Each "package" to be installed requires the single use of a blank DVD to transfer the file to Linux. I have a very limited number of blank DVDs. It is up, but down, according to ip addr. It says no carrier. The wifi is on and available. The signal strength is sufficient. It is presently offering an open wifi access point. The ssid is correct. How do I fix this? I cannot connect a phone or any other device to the laptop to help "get it started," nor should I need to. The netinst CD should have everything a new user could need to get things working.
> >> >
> >> > If I understand your situation, which I might not, try putting this in
> >> > the /etc/network/interfaces file:
> >> >
> >> > allow-hotplug wlp3s0
> >> > iface wlp3s0 inet dhcp
> >> > wpa-ssid YOUR-WIFI-SSID
> >> > wpa-psk YOUR-WIFI-PASSWORD
> >> >
> >> > which may get the wifi working for you. (Reboot if necessary.)
> >> >
> >> Thank you for your polite response.
> >> The wifi access point is open so it does not use a password.
> >
> > Whenever I've met an open network, I've been on the road, and using a
> > client like wicd to connect. I can only assume that one leaves out
> > the password line, or sets it to an empty string.
> >
> >> I don't know if the netinst CD includes the wpasupplicant package.
> >
> > Yes. During installation on this machine, it was the 8th package
> > to be explicitly installed, according to apt's history.log.
> >
> > It would help to post whether your netinst was one that included
> > firmware (helps for laptops and suchlike) or not. Also, an outline
> > of how far you have progressed in the installation. From your OP,
> > I've presumed you've installed a system with the installer via
> > wireless, but can't get wifi connectivity since then.
> >
> >> ip addr is saying that Linux cannot detect a signal from the wifi router.
> >
> > I didn't know ip addr showed that, but I assume the router still
> > works after you finished a wireless installation.
> >
> >> I will consider trying DHCP instead of static to see if it makes a difference.
> >
> > I have no experience of setting up wifi statically—I don't see how
> > this would work with a portable device. For simplicity therefore,
> > I set up all my machines in the same manner, generally switching
> > from ifupdown (the default for non-DE systems) to wicd, my own
> > preference from years of use.
> >
> > Which connection method are you attempting to use yourself?
> >
> >> I can only hope the netinst CD has included any necessary packages to try DHCP.
> >
> > Yes, it's built into busybox for the actual installation, and then the
> > real package is installed in the main tranche.
> >
> > But, if I'm not out of date, there might not be a seamless transition
> > from wireless during installation to wireless post-installation for
> > non-DE installers. You may have to update /e/n/i yourself as I showed
> > earlier.
> >
> Thank you for your polite response. I downloaded the netinst CD disc image and wrote it on a disc and booted from that.

It's the name of the .iso image that tells us what was available for
the installer. You can see what firmware was needed and used with:
# less /var/log/installer/syslog
and searching for firmware. Note that the majority of matches will be
for errors, like:

 check-missing-firmware: looking for firmware file iwlwifi-7260-17.ucode requested by iwlwifi
 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
 check-missing-firmware: missing firmware files (iwlwifi-7260-17.ucode) for iwlwifi
 check-missing-firmware: installing firmware package /cdrom/firmware/firmware-iwlwifi_20190114-1_all.deb

(IIRC root, or sudo, is needed to read this log unless you're a
member of the adm group.)

> Windows can use the wifi adapter in the laptop, but Linux can't.

That's usual, because Windows will have any required firmware included.

> I did specify in my initial post that I also downloaded a firmware package and installed that.

There are many such packages. My cache, which serves five machines,
contains 7 nonfree firmware packages. The 386 installer with firmware
has 23.

I have since downloaded a much larger disc image, about 1.3 GB, but I have not yet had the time to explore it.
> 
> The wifi is my own, in my own living room. Windows could not connect if I used WPA2.

Does that mean you are running Windows XP or older? Otherwise,
something is misconfigured. You should be running WPA2-PSK.

> Only two devices that can connect, that I'm aware of, are in signal range of the 5 GHz access point. Both are already allowed on the wifi.

No comment.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222855

[Multipart message — attachments visible in raw view] — view raw

It's an old laptop factory loaded with Windows Vista.

name=Matthew%20Campbell&email=trenix25%40pm.me

-------- Original Message --------
On May 28, 2020, 8:49 PM, David Wright wrote:

> On Thu 28 May 2020 at 21:54:11 (+0000), Matthew Campbell wrote:
>> On May 28, 2020, 7:00 AM, David Wright wrote:
>> > On Thu 28 May 2020 at 12:40:44 (+0000), Matthew Campbell wrote:
>> >> On May 27, 2020, 7:50 PM, David Wright wrote:
>> >> > On Thu 28 May 2020 at 00:15:50 (+0000), Matthew Campbell wrote:
>> >> >> The netinst CD leaves a lot to be desired. I had to download a nonfree wifi firmware package with my tablet and install it just to get the Linux system on the laptop to recognize the wifi adapter. I still can't get the wifi to work which makes installation impossible. Many of the network related commands do not exist. I cannot just download a package without being able to connect the laptop to the Internet which is impossible if I can't get a wifi connection. I am using Debian 10.4 Buster on a laptop that uses an Intel Centrino Duo CPU. My wifi adapter is registering as wlp3s0. Each "package" to be installed requires the single use of a blank DVD to transfer the file to Linux. I have a very limited number of blank DVDs. It is up, but down, according to ip addr. It says no carrier. The wifi is on and available. The signal strength is sufficient. It is presently offering an open wifi access point. The ssid is correct. How do I fix this? I cannot connect a phone or any other device to the laptop to help "get it started," nor should I need to. The netinst CD should have everything a new user could need to get things working.
>> >> >
>> >> > If I understand your situation, which I might not, try putting this in
>> >> > the /etc/network/interfaces file:
>> >> >
>> >> > allow-hotplug wlp3s0
>> >> > iface wlp3s0 inet dhcp
>> >> > wpa-ssid YOUR-WIFI-SSID
>> >> > wpa-psk YOUR-WIFI-PASSWORD
>> >> >
>> >> > which may get the wifi working for you. (Reboot if necessary.)
>> >> >
>> >> Thank you for your polite response.
>> >> The wifi access point is open so it does not use a password.
>> >
>> > Whenever I've met an open network, I've been on the road, and using a
>> > client like wicd to connect. I can only assume that one leaves out
>> > the password line, or sets it to an empty string.
>> >
>> >> I don't know if the netinst CD includes the wpasupplicant package.
>> >
>> > Yes. During installation on this machine, it was the 8th package
>> > to be explicitly installed, according to apt's history.log.
>> >
>> > It would help to post whether your netinst was one that included
>> > firmware (helps for laptops and suchlike) or not. Also, an outline
>> > of how far you have progressed in the installation. From your OP,
>> > I've presumed you've installed a system with the installer via
>> > wireless, but can't get wifi connectivity since then.
>> >
>> >> ip addr is saying that Linux cannot detect a signal from the wifi router.
>> >
>> > I didn't know ip addr showed that, but I assume the router still
>> > works after you finished a wireless installation.
>> >
>> >> I will consider trying DHCP instead of static to see if it makes a difference.
>> >
>> > I have no experience of setting up wifi statically—I don't see how
>> > this would work with a portable device. For simplicity therefore,
>> > I set up all my machines in the same manner, generally switching
>> > from ifupdown (the default for non-DE systems) to wicd, my own
>> > preference from years of use.
>> >
>> > Which connection method are you attempting to use yourself?
>> >
>> >> I can only hope the netinst CD has included any necessary packages to try DHCP.
>> >
>> > Yes, it's built into busybox for the actual installation, and then the
>> > real package is installed in the main tranche.
>> >
>> > But, if I'm not out of date, there might not be a seamless transition
>> > from wireless during installation to wireless post-installation for
>> > non-DE installers. You may have to update /e/n/i yourself as I showed
>> > earlier.
>> >
>> Thank you for your polite response. I downloaded the netinst CD disc image and wrote it on a disc and booted from that.
>
> It's the name of the .iso image that tells us what was available for
> the installer. You can see what firmware was needed and used with:
> # less /var/log/installer/syslog
> and searching for firmware. Note that the majority of matches will be
> for errors, like:
>
> check-missing-firmware: looking for firmware file iwlwifi-7260-17.ucode requested by iwlwifi
> check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
> check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
> check-missing-firmware: missing firmware files (iwlwifi-7260-17.ucode) for iwlwifi
> check-missing-firmware: installing firmware package /cdrom/firmware/firmware-iwlwifi_20190114-1_all.deb
>
> (IIRC root, or sudo, is needed to read this log unless you're a
> member of the adm group.)
>
>> Windows can use the wifi adapter in the laptop, but Linux can't.
>
> That's usual, because Windows will have any required firmware included.
>
>> I did specify in my initial post that I also downloaded a firmware package and installed that.
>
> There are many such packages. My cache, which serves five machines,
> contains 7 nonfree firmware packages. The 386 installer with firmware
> has 23.
>
> I have since downloaded a much larger disc image, about 1.3 GB, but I have not yet had the time to explore it.
>>
>> The wifi is my own, in my own living room. Windows could not connect if I used WPA2.
>
> Does that mean you are running Windows XP or older? Otherwise,
> something is misconfigured. You should be running WPA2-PSK.
>
>> Only two devices that can connect, that I'm aware of, are in signal range of the 5 GHz access point. Both are already allowed on the wifi.
>
> No comment.
>
> Cheers,
> David.

[toc] | [prev] | [next] | [standalone]

#222853

[Multipart message — attachments visible in raw view] — view raw

On Jo, 28 mai 20, 09:00:52, David Wright wrote:
> On Thu 28 May 2020 at 12:40:44 (+0000), Matthew Campbell wrote:
> 
> > I will consider trying DHCP instead of static to see if it makes a difference.
> 
> I have no experience of setting up wifi statically—I don't see how
> this would work with a portable device. 

Every reasonable network configuration manager has the option for a 
static IP configuration, per WiFi. Network Manager certainly does and 
Wicd did as well last time I used it (many years ago).

The installer will also ask for a manual configuration if DHCP doesn't 
work (regardless if WiFi or wired) and even if DHCP works, there is an 
option for static configuration.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#222875

On Fri 29 May 2020 at 11:36:03 (+0300), Andrei POPESCU wrote:
> On Jo, 28 mai 20, 09:00:52, David Wright wrote:
> > On Thu 28 May 2020 at 12:40:44 (+0000), Matthew Campbell wrote:
> > 
> > > I will consider trying DHCP instead of static to see if it makes a difference.
> > 
> > I have no experience of setting up wifi statically—I don't see how
> > this would work with a portable device. 
> 
> Every reasonable network configuration manager has the option for a 
> static IP configuration, per WiFi. Network Manager certainly does and 
> Wicd did as well last time I used it (many years ago).
> 
> The installer will also ask for a manual configuration if DHCP doesn't 
> work (regardless if WiFi or wired) and even if DHCP works, there is an 
> option for static configuration.

Sorry, I didn't make myself clear. The first half of my sentence
applies, at least post-installation. I have on occasion typed the
static information into the installer, but that info doesn't (didn't?)
survive the reboot (the subject of a thread in early 2018 where I was
misquoted).

In the second half, I wasn't doubting that static would technically
function, but that almost any user would be unsatisfied by a tablet
or laptop with a statically configured wifi connection. It "works"
about as well as locking one's OAP bus pass in a safe deposit box
at the local bank.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222886

[Multipart message — attachments visible in raw view] — view raw

On Vi, 29 mai 20, 09:29:26, David Wright wrote:
> 
> In the second half, I wasn't doubting that static would technically
> function, but that almost any user would be unsatisfied by a tablet
> or laptop with a statically configured wifi connection. It "works"
> about as well as locking one's OAP bus pass in a safe deposit box
> at the local bank.

The settings are *per wireless network*, so by default one gets DHCP for 
every new/other network, even if e.g. the wireless at home is configured 
for static IP.

Hope this clarifies,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#222898

On Fri 29 May 2020 at 18:53:10 (+0300), Andrei POPESCU wrote:
> On Vi, 29 mai 20, 09:29:26, David Wright wrote:
> > 
> > In the second half, I wasn't doubting that static would technically
> > function, but that almost any user would be unsatisfied by a tablet
> > or laptop with a statically configured wifi connection. It "works"
> > about as well as locking one's OAP bus pass in a safe deposit box
> > at the local bank.
> 
> The settings are *per wireless network*, so by default one gets DHCP for 
> every new/other network, even if e.g. the wireless at home is configured 
> for static IP.

I'm not sure which default you mean.

The OP appears to have installed Debian onto a laptop from a netinst CD
via wifi. (With ethernet, the problems would not arise. [pace Charles])
No idea how much software was installed in d-i itself, but ifupdown
should always be present, and was likely used during installation.
However, at the end if the d-i, (disclaimers as always), that
configuration is removed, so the information may have to be reentered.
That's what

allow-hotplug wlp3s0
iface wlp3s0 inet dhcp
      wpa-ssid YOUR-WIFI-SSID
      wpa-psk  YOUR-WIFI-PASSWORD

does. We were told "wlp3s0", we know the OP knows YOUR-WIFI-SSID, and
there's no YOUR-WIFI-PASSWORD. (I didn't know about any no-password bug.)
For most, if not all, network configuration software, a stanza in
/e/n/i will prioritize ifupdown. (I can't speak for systemd: it gets
it hopelessly wrong with system timekeeping.)

To avoid starting over, I've suggested how to find whether and which
firmware might be required, asked for the name of the original .iso,
and fixed the /e/n/i for wifi in case there's no other configurator.
(I haven't seen any evidence of a fight over the network's configuration.)

I've yet to see any virtue in using a static configuration¹ at home
and dhcp everywhere else. And I can't suggest a stanza for /e/n/i
as I have no idea how their network is numbered. So I don't see any
point in putting a static configuration into /e/n/i, or even learning
about it. You can't do it anywhere else.

However, the only other suggestions I've seen so far are to start
over, so perhaps others can take over here. I've forgotten whether
there are any wrinkles with installing from CD sets or DVDs; it's
too long ago.

¹ Static, that is, from the point of view of the PC. I use static
IP numbers, but they're issued by the router, which makes spotting
any interlopers easier (assuming you reserve a range for
"foreign" assignment).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222900

[Multipart message — attachments visible in raw view] — view raw

I tried to go to debian.org with the web browser in Windows, but it wouldn't let me. I had a friend download the netinst CD with his phone, along with a web server app. Then I downloaded the netinst CD from his phone, while in the same room, since we were both on the same wlan. I then wrote the netinst CD image onto a blank DVD with a program in Windows and booted the DVD.

name=Matthew%20Campbell&email=trenix25%40pm.me

-------- Original Message --------
On May 29, 2020, 12:51 PM, David Wright wrote:

> On Fri 29 May 2020 at 18:53:10 (+0300), Andrei POPESCU wrote:
>> On Vi, 29 mai 20, 09:29:26, David Wright wrote:
>> >
>> > In the second half, I wasn't doubting that static would technically
>> > function, but that almost any user would be unsatisfied by a tablet
>> > or laptop with a statically configured wifi connection. It "works"
>> > about as well as locking one's OAP bus pass in a safe deposit box
>> > at the local bank.
>>
>> The settings are *per wireless network*, so by default one gets DHCP for
>> every new/other network, even if e.g. the wireless at home is configured
>> for static IP.
>
> I'm not sure which default you mean.
>
> The OP appears to have installed Debian onto a laptop from a netinst CD
> via wifi. (With ethernet, the problems would not arise. [pace Charles])
> No idea how much software was installed in d-i itself, but ifupdown
> should always be present, and was likely used during installation.
> However, at the end if the d-i, (disclaimers as always), that
> configuration is removed, so the information may have to be reentered.
> That's what
>
> allow-hotplug wlp3s0
> iface wlp3s0 inet dhcp
> wpa-ssid YOUR-WIFI-SSID
> wpa-psk YOUR-WIFI-PASSWORD
>
> does. We were told "wlp3s0", we know the OP knows YOUR-WIFI-SSID, and
> there's no YOUR-WIFI-PASSWORD. (I didn't know about any no-password bug.)
> For most, if not all, network configuration software, a stanza in
> /e/n/i will prioritize ifupdown. (I can't speak for systemd: it gets
> it hopelessly wrong with system timekeeping.)
>
> To avoid starting over, I've suggested how to find whether and which
> firmware might be required, asked for the name of the original .iso,
> and fixed the /e/n/i for wifi in case there's no other configurator.
> (I haven't seen any evidence of a fight over the network's configuration.)
>
> I've yet to see any virtue in using a static configuration¹ at home
> and dhcp everywhere else. And I can't suggest a stanza for /e/n/i
> as I have no idea how their network is numbered. So I don't see any
> point in putting a static configuration into /e/n/i, or even learning
> about it. You can't do it anywhere else.
>
> However, the only other suggestions I've seen so far are to start
> over, so perhaps others can take over here. I've forgotten whether
> there are any wrinkles with installing from CD sets or DVDs; it's
> too long ago.
>
> ¹ Static, that is, from the point of view of the PC. I use static
> IP numbers, but they're issued by the router, which makes spotting
> any interlopers easier (assuming you reserve a range for
> "foreign" assignment).
>
> Cheers,
> David.

[toc] | [prev] | [next] | [standalone]

#222912

[Multipart message — attachments visible in raw view] — view raw

On Vi, 29 mai 20, 14:51:23, David Wright wrote:
> 
> I'm not sure which default you mean.

The defaults of the user-oriented network managers, like Network Manager 
and Wicd. They provide a much friendlier experience for laptops that are 
carried around and are frequently connected to different wireless 
networks.
 
> I've yet to see any virtue in using a static configuration¹ at home
> and dhcp everywhere else. 

[...]

> ¹ Static, that is, from the point of view of the PC. I use static
> IP numbers, but they're issued by the router, which makes spotting
> any interlopers easier (assuming you reserve a range for
> "foreign" assignment).

ISP provided router with no support for DHCP reservations, combined with 
running something like barrier on the laptop.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#222934

On Sat 30 May 2020 at 08:27:14 (+0300), Andrei POPESCU wrote:
> On Vi, 29 mai 20, 14:51:23, David Wright wrote:
> > 
> > I'm not sure which default you mean.
> 
> The defaults of the user-oriented network managers, like Network Manager 
> and Wicd. They provide a much friendlier experience for laptops that are 
> carried around and are frequently connected to different wireless 
> networks.

I deliberately avoided assuming that such packages had already
been installed. I always have to install wicd after the first
reboot, by which time I have reestablished connectivity with
ifupdown just as I described in this thread. (I don't use NM.)

My only worry was whether systemd-networkd gives way gracefully
to a configured ifupdown, or fights it like systemd-timesyncd vs ntp.

> > I've yet to see any virtue in using a static configuration¹ at home
> > and dhcp everywhere else.
> 
> [...]
> 
> > ¹ Static, that is, from the point of view of the PC. I use static
> > IP numbers, but they're issued by the router, which makes spotting
> > any interlopers easier (assuming you reserve a range for
> > "foreign" assignment).
> 
> ISP provided router with no support for DHCP reservations, combined with 
> running something like barrier on the laptop.

I can't understand what you're trying to describe here. My footnote
was to explain that I appreciate a desire to have fixed IP addresses
for devices when they're at home, but they're not going to hold as
soon as you leave. I reserve everything up to .199 on my main router
for devices we own, so that casual devices will appear as .2xx.
Again, it's just a convenience.

But none of that is essential for making a connection. I can't tell
whether you're just saying that the OP might not be able to copy my
particular setup (so what?), or describing some extraordinary ISPs
who rent out routers that would prevent my suggestion of putting
dhcp in /e/n/i from working at all.

BTW what's barrier?

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web