Re: [DNG] noisy computer
Already used iotop ? apt-get install iotop On Sun, 2018-07-01 at 21:25 -0400, Hendrik Boom wrote: > After upgrading my server to Ascii (which I did successfully using the > instructions in > https://devuan.org/os/documentation/dev1fanboy/upgrade-to-ascii although > it did not go flawlessly I noticed that it was making a regular, > repeated click-click noise, a pair of clicks about every 1.1 second. > > Later, I noticed its hard-disk-in-use light blinking at the same time as > the noise. > > I conclude that something in the system is using the hard drive every > 1.1 seconds, night and day. > > Any ideas for tracking down what is doing this? > > -- hendrik > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] noisy computer
After upgrading my server to Ascii (which I did successfully using the instructions in https://devuan.org/os/documentation/dev1fanboy/upgrade-to-ascii although it did not go flawlessly I noticed that it was making a regular, repeated click-click noise, a pair of clicks about every 1.1 second. Later, I noticed its hard-disk-in-use light blinking at the same time as the noise. I conclude that something in the system is using the hard drive every 1.1 seconds, night and day. Any ideas for tracking down what is doing this? -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
Hi , El 01/07/18 a las 16:38, aitor_czr escribió: I'll send you a video in a few minutes showing a bug in the netstat icon of wicd using non renamed devices (I have not been able to reproduce this bug in the case of renamed devices). Here you are the video (low quality): gnuinos.org/wicd.mpg Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
Hi again, El 01/07/18 a las 16:20, Haines Brown escribió: On Sun, Jul 01, 2018 at 07:30:30AM -0400, Haines Brown wrote: Stefan, sorry to be dense. With the help of ThinkPenguin I finally resolved the problem and wlan0 is now my interface name, not wlx. In any case, simply modifying /etc/network/interfaces to use that address didn't work (I replaced all instances of wlan0 with wlx, but I might have gone too far). Because my online search failed to come up with the solution, it may be useful to describe it here. I simplify by leaving out references to NetworkManager (if present it should be stopped) and for setting up a static IP address. The full directions are at: www.thinkpenguin.com/gnu-linux/how-configure-wifi-card-using-command-line-or-terminal With ascii I had to modify one step a bit. The following assumes that wpasupplicant and wireless-tools have been installed, and also the appropriate driver for the wireless card or dongle is accessible. It assumes that /etc/resolv.conf points to the name server, which in my case is my router's IP address. It also assumes there is only one wireless interface. 1. Create (or replace) a wpa_supplicant.conf file: # wpa_passphrase "" > /etc/wpa_supplicant.conf 2. Replace the wireless stanza in /etc/network/interfaces with: auto wlan0 iface wlan0 inet dhcp wpa-driver nl80211 wpa-conf /etc/wpa_supplicant.conf The value of the driver is extracted from iwconfig line: IEEE 802.11bgn 3. Activate the connection # ifconfig wlan0 up # ping -c 5 google.com My ifconfig now shows wlan0 to be UP and RUNNING. My only open question is that DHCP has assigned an IP address different than before. I've not checked to see if it differs from the old ethernet IP address as well. Haines You can also active the connection using ISC-DHCP-CLIENT by the following way: # dhclient wlan0 use "dhclient -r" for killing all the previous clients. Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
Hi Steve, El 01/07/18 a las 00:50, Steve Litt escribió: On Sat, 30 Jun 2018 17:06:09 -0400 Haines Brown wrote: I've long struggled with a problem with a new installation of ascii. I can get an ethernet connection, but with a usb WiFi dongle using an Atheros chip, my wlan0 interface gets automatically changed to wl, and so cannot communicate with DHCP. Look back through the archives a couple years, and you'll find one of my emails with a shellscript to tell you all wifi device names and all wired ethernet names. A couple days after I submitted it, somebody else improved it. A shellscript like that belongs on every computer, so it can be invoked from every init script and run file and other shellscripts needing the exact name of network devices. The behaviour is different using renamed or non renamed network devices. I'll send you a video in a few minutes showing a bug in the netstat icon of wicd using non renamed devices (I have not been able to reproduce this bug in the case of renamed devices). The bug appears after running: # ip link set down once you are connected to the router. The netstat icon of wicd will not change, even being disconnected. The behaviour of my code for the backend of simple-netaid was similar (the same bug); so, i decided to add some code taken from the iproute2 project: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/ This weekend i've been working on that. Here you are the code: http://gnuinos.org/IPROUTE2/ I'll inform you in the course of today. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
On Sun, 1 Jul 2018 10:20:10 -0400, Haines wrote in message <20180701142010.gt1...@engels.historicalmaterialism.info>: > On Sun, Jul 01, 2018 at 07:30:30AM -0400, Haines Brown wrote: > > Stefan, sorry to be dense. > > With the help of ThinkPenguin I finally resolved the problem and wlan0 > is now my interface name, not wlx. In any case, simply > modifying /etc/network/interfaces to use that address didn't work (I > replaced all instances of wlan0 with wlx, but I > might have gone too far). > > Because my online search failed to come up with the solution, it may > be useful to describe it here. I simplify by leaving out references to > NetworkManager (if present it should be stopped) and for setting up a > static IP address. The full directions are at: > www.thinkpenguin.com/gnu-linux/how-configure-wifi-card-using-command-line-or-terminal > With ascii I had to modify one step a bit. > > The following assumes that wpasupplicant and wireless-tools have been > installed, and also the appropriate driver for the wireless card or > dongle is accessible. It assumes that /etc/resolv.conf points to the > name server, which in my case is my router's IP address. It also > assumes there is only one wireless interface. > > 1. Create (or replace) a wpa_supplicant.conf file: > > # wpa_passphrase "" > > /etc/wpa_supplicant.conf > > 2. Replace the wireless stanza in /etc/network/interfaces with: > > auto wlan0 > iface wlan0 inet dhcp > wpa-driver nl80211 ..totally fine this far. > wpa-conf /etc/wpa_supplicant.conf ..totally fine this far on networks you control or trust. But everywhere? > The value of the driver is extracted from iwconfig line: IEEE > 802.11bgn > > 3. Activate the connection > > # ifconfig wlan0 up > > # ping -c 5 google.com > > My ifconfig now shows wlan0 to be UP and RUNNING. My only open > question is that DHCP has assigned an IP address different than > before. I've not checked to see if it differs from the old ethernet > IP address as well. > > Haines -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
On Sun, Jul 01, 2018 at 07:30:30AM -0400, Haines Brown wrote: > Stefan, sorry to be dense. With the help of ThinkPenguin I finally resolved the problem and wlan0 is now my interface name, not wlx. In any case, simply modifying /etc/network/interfaces to use that address didn't work (I replaced all instances of wlan0 with wlx, but I might have gone too far). Because my online search failed to come up with the solution, it may be useful to describe it here. I simplify by leaving out references to NetworkManager (if present it should be stopped) and for setting up a static IP address. The full directions are at: www.thinkpenguin.com/gnu-linux/how-configure-wifi-card-using-command-line-or-terminal With ascii I had to modify one step a bit. The following assumes that wpasupplicant and wireless-tools have been installed, and also the appropriate driver for the wireless card or dongle is accessible. It assumes that /etc/resolv.conf points to the name server, which in my case is my router's IP address. It also assumes there is only one wireless interface. 1. Create (or replace) a wpa_supplicant.conf file: # wpa_passphrase "" > /etc/wpa_supplicant.conf 2. Replace the wireless stanza in /etc/network/interfaces with: auto wlan0 iface wlan0 inet dhcp wpa-driver nl80211 wpa-conf /etc/wpa_supplicant.conf The value of the driver is extracted from iwconfig line: IEEE 802.11bgn 3. Activate the connection # ifconfig wlan0 up # ping -c 5 google.com My ifconfig now shows wlan0 to be UP and RUNNING. My only open question is that DHCP has assigned an IP address different than before. I've not checked to see if it differs from the old ethernet IP address as well. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
On Sun, 1 Jul 2018 15:59:18 +0200, Stefan wrote in message <201807011559.18028.li...@stefan-krusche.de>: > I think, you are on the right track here. Check how your interfaces > are named with > > ip addr > > or > > sudo ifconfig ..if that fails, append " -a " to see "the other interfaces." -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
El 01/07/18 a las 13:30, Haines Brown escribió: If on the other hand I change the interface file on the ascii machine to use the wireless dongle's mac address, such as wlx2123ff1a1794, by making the first two lines of the interface read: auto wlx2123ff1a1794 iface wlx2123ff1a1794 inet dhcp ... wpa_supplicant fails to bring up wlx2123ff1a1794. lol, it works for me :) Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
Am Sonntag 01 Juli 2018 schrieb Stefan Krusche:
> Hello Haines,
>
> I certainly am no expert on this, but I'll try to help.
>
> Am Sonntag 01 Juli 2018 schrieb Haines Brown:
> > Does not a /etc/udev/rules.d/70-persistent-net-rules file with the
> > following content not force udev to assign wlan0 to the interface rather
> > than use wlx?
> >
> > # PCI device 0x1814:0x0601 (rt2800pci)
> > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}==" > mac address>", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", \
> > NAME="wlan0"
>
> I think so. That's what you suggested in the first place and what I
> proposed.
>
> > If on the other hand I change the interface file on the ascii machine to
> > use the wireless dongle's mac address, such as wlx2123ff1a1794, by making
> > the first two lines of the interface read:
> >
> > auto wlx2123ff1a1794
> > iface wlx2123ff1a1794 inet dhcp
> > ...
> >
> > wpa_supplicant fails to bring up wlx2123ff1a1794.
>
> I think, you are on the right track here. Check how your interfaces are
> named with
>
> ip addr
>
> or
>
> sudo ifconfig
>
> and change /etc/network/interfaces accordingly.
That is,
> > auto wlx2123ff1a1794
> >iface wlx2123ff1a1794 inet dhcp
should probably be
auto wlan0
iface wlan0 inet dhcp
Good luck!
Stefan
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
Hello Haines,
I certainly am no expert on this, but I'll try to help.
Am Sonntag 01 Juli 2018 schrieb Haines Brown:
> Does not a /etc/udev/rules.d/70-persistent-net-rules file with the
> following content not force udev to assign wlan0 to the interface rather
> than use wlx?
>
> # PCI device 0x1814:0x0601 (rt2800pci)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}==" mac address>", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", \
> NAME="wlan0"
I think so. That's what you suggested in the first place and what I proposed.
> If on the other hand I change the interface file on the ascii machine to
> use the wireless dongle's mac address, such as wlx2123ff1a1794, by making
> the first two lines of the interface read:
>
> auto wlx2123ff1a1794
> iface wlx2123ff1a1794 inet dhcp
> ...
>
> wpa_supplicant fails to bring up wlx2123ff1a1794.
I think, you are on the right track here. Check how your interfaces are named
with
ip addr
or
sudo ifconfig
and change /etc/network/interfaces accordingly.
Regards,
Stefan
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
On Sun, Jul 01, 2018 at 11:30:46AM +0200, Stefan Krusche wrote:
> Am Samstag 30 Juni 2018 schrieb Haines Brown:
> > c) alter the default policy for picking a different naming
> > scheme by copying /lib/udev/rules.d/80-net-link-setup.rules to
> > /etc/udev/rules.d/ and then edit it appropriately.
> >
> > In my devuan jessie machine, there is such a file and it has
> > two lines. One is:
> >
> > # PCI device 0x1814:0x0601 (rt2800pci) \
> > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
> > ATTR{address}=="68:1c:a2:04:21:74", ATTR{dev_id}=="0x0", \
> > ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
> >
> > There is another line # PCI device 0x8086:0x153b (e1000e) \
> > SUBSYSTEM=="net", ...
> >
> > However, on my new ascii machine, the directory /etc/udev/rules.d/ is
> > empty. Can I simply copy the 70-persistent-net.rules file from my old
> > Devuan jessie machine to the new ascii machine and uncomment the two
> > lines?
>
> Hello Haines,
>
> I have two network interfaces, one integrated and one additional networkcard,
> which of the names got switched by udev. I applied exactly the solution which
> you describe with placed these udev rules, so, I believe, the configuration
> from your jessie system will work. Just make sure that the MAC address
> matches
> on the new system. My lines:
>
> # PCI device 0x10ec:0x8139 (8139too)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
> ATTR{address}=="00:ac:bd:ce:df:xz", ATTR{dev_id}=="0x0", ATTR{type}=="1", \
> KERNEL=="eth*", NAME="net0"
>
> # PCI device 0x10ec:0x8168 (r8169)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
> ATTR{address}=="01:ac:bd:ce:df:xz", ATTR{dev_id}=="0x0", ATTR{type}=="1", \
> KERNEL=="eth*", NAME="lan0"
>
> Regards,
> Stefan
Stefan, sorry to be dense. I tried to copy the 70-persistent-net-rules
file from jessie /etc/udev/rules.d/ to the empty ascii
/etc/udev/rules.d/ directory. I changed the mac address to that of the
jessie wireless dongle (the value of ether that shows up with #
ifconfig).
Still No DHCPOFFERS.
I've assumed that the 70-persistent-net-rules file in /etc/udev/rules.d)
overwrites /lib/udev/rules.d/75-persistent-net-rules file.
Does not a /etc/udev/rules.d/70-persistent-net-rules file with the
following content not force udev to assign wlan0 to the interface rather
than use wlx?
# PCI device 0x1814:0x0601 (rt2800pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", \
NAME="wlan0"
If on the other hand I change the interface file on the ascii machine to
use the wireless dongle's mac address, such as wlx2123ff1a1794, by making
the first two lines of the interface read:
auto wlx2123ff1a1794
iface wlx2123ff1a1794 inet dhcp
...
wpa_supplicant fails to bring up wlx2123ff1a1794.
Haines
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
Am Samstag 30 Juni 2018 schrieb Haines Brown:
> c) alter the default policy for picking a different naming
> scheme by copying /lib/udev/rules.d/80-net-link-setup.rules to
> /etc/udev/rules.d/ and then edit it appropriately.
>
> In my devuan jessie machine, there is such a file and it has
> two lines. One is:
>
> # PCI device 0x1814:0x0601 (rt2800pci) \
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
> ATTR{address}=="68:1c:a2:04:21:74", ATTR{dev_id}=="0x0", \
> ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
>
> There is another line # PCI device 0x8086:0x153b (e1000e) \
> SUBSYSTEM=="net", ...
>
> However, on my new ascii machine, the directory /etc/udev/rules.d/ is
> empty. Can I simply copy the 70-persistent-net.rules file from my old
> Devuan jessie machine to the new ascii machine and uncomment the two
> lines?
Hello Haines,
I have two network interfaces, one integrated and one additional networkcard,
which of the names got switched by udev. I applied exactly the solution which
you describe with placed these udev rules, so, I believe, the configuration
from your jessie system will work. Just make sure that the MAC address matches
on the new system. My lines:
# PCI device 0x10ec:0x8139 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
ATTR{address}=="00:ac:bd:ce:df:xz", ATTR{dev_id}=="0x0", ATTR{type}=="1", \
KERNEL=="eth*", NAME="net0"
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
ATTR{address}=="01:ac:bd:ce:df:xz", ATTR{dev_id}=="0x0", ATTR{type}=="1", \
KERNEL=="eth*", NAME="lan0"
Regards,
Stefan
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
