| FilipZ1 | Nvm. I corrected it. | 00:08 |
|---|---|---|
| FilipZ1 | It seem to be saved correctly now. | 00:10 |
| rrq | ok I've set up an nc receiver at borta.rrq.id.au again for you | 01:01 |
| rrq | I'm a bit busy today so will be on-off here | 01:01 |
| FilipZ | rrq: Again, the only thing I can see here is the "502 Bad Gateway". | 02:11 |
| rrq | https://borta.rrq.id.au/download | 02:12 |
| FilipZ | "Could not add your entry to the paste database: do not spam" on the "https://paste.debian.net/". What is it even supposed to mean? -_- The log file was of right size, as I split it. | 02:13 |
| FilipZ | I need to share this .log file. I only see there a couple of files to download. | 02:15 |
| rrq | I've set up an nc listener like before... | 02:16 |
| FilipZ | I didn't understand what was this command you mentioned earlier for. | 02:18 |
| rrq | nc -w 2 borta.rrq.id.au 12000 < logfile | 02:18 |
| rrq | that sends "logfile" via tcp to host borta.rrq.id.au port 12000 then waits 2 seconds at end | 02:19 |
| FilipZ | Done. I sent it, I think. | 02:19 |
| rrq | mmm nope .. hmm | 02:20 |
| FilipZ | "invalid port" | 02:20 |
| rrq | let's try again | 02:21 |
| FilipZ | Again, it lasts so long, like before, so it is probably the same. | 02:21 |
| rrq | something goes wrong | 02:22 |
| rrq | .. nothing received | 02:24 |
| FilipZ | This command is still in progress to me | 02:25 |
| rrq | maybe use: nc -w 2 108.61.184.72 12000 < logfile | 02:26 |
| FilipZ | Sorry. Earlier it was my fault. I somehow forgot to add < | 02:29 |
| FilipZ | But now with it I get an answer: "(UNKNOWN) [108.61.184.72] 12000 (?) : Connection refused" | 02:29 |
| rrq | ok got 187677 bytes | 02:30 |
| rrq | looks like the strace dump | 02:31 |
| FilipZ | Right. It is of this size. | 02:33 |
| rrq | line 1356: bringing up wlan0 yields in i/o error | 02:34 |
| FilipZ | So what to do next? | 02:36 |
| rrq | suggest h/w issue with wlan0 ... does wpa_supplicant write to syslog? | 02:36 |
| rrq | it would have made a note when wlan0 "failed" | 02:37 |
| rrq | I mean when it went down before | 02:37 |
| FilipZ | It does. I don't know whether the verbosity is enough, but it does | 02:38 |
| rrq | could you paste its error lines to https://paste.debian.net/ | 02:39 |
| rrq | it does suggest h/w issue or possibly some mistaken power management | 02:40 |
| rrq | possibly the least expensive is to get a USB dongle of "well supported by linux" kind; depends on how you value your time :) | 02:42 |
| FilipZ | https://paste.debian.net/1255998/ | 02:42 |
| FilipZ | Here. From that time. The log file modification timestamp is 04:08. | 02:43 |
| rrq | is the firmware installed & loaded? | 02:46 |
| rrq | iwlwifi looks unhappy already at start | 02:47 |
| rrq | if you have /lib/firmware/iwlwifi-7265D-22.ucode as well as /lib/firmware/iwlwifi-7265D-29.ucode then maybe try moving the latter file to /root for using the older firmware | 02:53 |
| rrq | but, I'm far from expert about firmware either in general or this specifically | 02:54 |
| rrq | my advice just came from a couple of seconds websearch | 02:55 |
| rrq | https://bbs.archlinux.org/viewtopic.php?id=265762 | 02:56 |
| rrq | the reason for moving iwlwifi-7265D-29.ucode to /root is for "backup" so you can put it back if there's no improvement | 02:57 |
| FilipZ | I thought that the newest iwlwifi firmware is installed and loaded. That would be the higher of 2 versions. | 03:14 |
| FilipZ | How should I check it? | 03:14 |
| FilipZ | Should I simply move the higher numbered version to the /root directory? | 03:17 |
| rrq | yes | 03:17 |
| rrq | and it looked like the kernel kept reloading so presumably it will try again and now found the -22.ucode | 03:18 |
| rrq | fiind | 03:18 |
| rrq | find | 03:18 |
| FilipZ | I did so. What should I do now? | 03:27 |
| FilipZ | ifdown, then ifup? | 03:27 |
| rrq | yes .. and keep an eye on syslog I suppose | 03:27 |
| FilipZ | Everything works for now. There are 3 iwlwifi related messages from the time when I turned on the interface, but they don't mention any version. | 03:33 |
| rrq | sounds good | 03:34 |
| rrq | at/after reboot there should be some mentioning about loading the firmware in either syslog or kern.log | 03:35 |
| rrq | but while it's working it's working :) | 03:35 |
| FilipZ | So thanks for the help! :) Why was it the older iwlwfi driver that should be left, though? | 04:02 |
| FilipZ | rrq: My connection just started breaking again. | 05:03 |
| FilipZ | https://paste.debian.net/1256001/ here are the syslog messages from this time. | 05:06 |
| FilipZ | By that it started breaking, I meant that there was a random disconnection, not that there was an issue where I couldn't do ifup. | 05:08 |
| FilipZ | At least this didn't happen yet. | 05:09 |
| FilipZ | I did ifdown, ifup to make sure that it will work possibly more stable for a while, then I checked the dhclient processes, and here are 3. | 05:11 |
| FilipZ | My connection malfunctions again. It didn't completely break yet, but it disconnects repeatedly, and when it doesn't there is a high packet loss | 07:03 |
| FilipZ | rrq: Are you here? | 07:03 |
| rrq | FilipZ: right.. kill any "spurious" dhclient (after ifdown) | 07:34 |
| FilipZ | I did so. | 07:35 |
| rrq | is syslog "better"? .. like the last one you pasted, which shows an ok reconnection | 07:35 |
| rrq | disconnection might be due to "weak service".. sudo iwlist wlan0 scanning incldes signal strength info | 07:37 |
| rrq | signal level above -50 dBm should be fine | 07:39 |
| FilipZ | rrq: https://paste.debian.net/1256012/ It is the part when it malfunctioned last time | 08:04 |
| FilipZ | I pasted 2 previous earlier, the latter one being a simillar case, when it didn | 08:04 |
| FilipZ | 't yet broke completely, just the connection malfunctioned. | 08:06 |
| FilipZ | And yes, It did reconnect automatically. | 08:06 |
| FilipZ | But it is still as bad as earlier. | 08:07 |
| rrq | signal level? | 08:08 |
| FilipZ | "sudo iwlist wlan0" returns "iwlist: unknown command `wlan0' (check 'iwlist --help')" | 08:10 |
| rrq | package wireless-tools | 08:10 |
| FilipZ | wpa_gui describes my current wi-fi connection, at the moment as with -72 dBm signal strength. | 08:11 |
| rrq | that's weak | 08:12 |
| FilipZ | But I have my internet access point about 30cm from my PC | 08:12 |
| FilipZ | The hotspot, I mean | 08:13 |
| rrq | what happens ti the signla if you move it to 60cm ? | 08:13 |
| FilipZ | I moved it 2 meters away, and it displays the same value for now | 08:14 |
| rrq | ok.. mmm what does "sudo iwconfig wlan0" say about "invalid" and "missed"? | 08:17 |
| FilipZ1 | I moved it 2m away and then it kept displaying -72dBm of the signal strength, and at some moment it broke completely again, so I cannot do ifup wlan0 | 08:21 |
| rrq | weak signal may be caused by either end, but -70 is very weak | 08:25 |
| rrq | does iwlist scanning show other APs, with stronger signals? (unless you are out in the bush of course) | 08:26 |
| rrq | is the hotspot in a case? and same signal without case? | 08:28 |
| rrq | maybe you should look into USB tethering | 08:29 |
| FilipZ1 | It did show more earlier, when it didn't break yet, I think | 08:31 |
| FilipZ1 | I meant that part of wpa_gui that lists the available networks. | 08:32 |
| FilipZ1 | That hotspot is just made by the phone. Its thin case doesn't make much difference, I think | 08:33 |
| FilipZ1 | Should I do Strace again, when in this problem state? | 08:35 |
| FilipZ1 | And as I mentioned earlier | 08:40 |
| FilipZ1 | "sudo iwlist wlan0" returned "iwlist: unknown command `wlan0' (check 'iwlist --help')" | 08:40 |
| FilipZ1 | It still does. I do have the wireless-tools package installed | 08:41 |
| FilipZ1 | And for now it cannot scan for the networks, when I cannot ifup wlan0 anyways, right? | 08:42 |
| FilipZ1 | Should I just restart the system now, or check output of some command as it is now | 08:43 |
| rrq | maybe "iwconfig wlan0" would show something | 08:58 |
| rrq | though, if the receiver is the cause of the weak signal maybe the best and cheapest is to get a new one | 09:00 |
| gnarface | all my testing points to a widespread problem with wifi drivers in the linux kernel causing this | 09:03 |
| gnarface | doesn't affect all hardware, but the only thing i could find that didn't have the problem and supported host mode and supported recent wifi security standards was something i had to patch the kernel for specifically (the pine64 sdio module for their A64 SoCs) | 09:05 |
| gnarface | (this thing: https://pine64.com/product/pine64-wifi-802-11bgn-bluetooth-4-0-module/) | 09:05 |
| gnarface | the only successful mitigation factor for the other stuff was to stay within 1 foot of the host and keep a constant ping running | 09:07 |
| gnarface | i suspect the issue is actually power management related | 09:07 |
| gnarface | but it's not affecting linux clients with most proprietary host devices, so i assume this comes down to some more proprietary shenanigans | 09:08 |
| gnarface | couldn't say which kernel it appeared in first, hadn't been using wifi for a long time | 09:09 |
| gnarface | maybe nothing past 802.11b ever actually worked right | 09:09 |
| FilipZ1 | rrq: iwconfig wlan0 gives the exact same output that I described before. | 09:25 |
| FilipZ1 | How can I fully restart the wireless device, without restarting the system? | 09:26 |
| gnarface | down the network, unload the driver, unplug the device, count to 10 | 09:29 |
| gnarface | that might work | 09:29 |
| gnarface | probably won't help, but it should reset the device | 09:29 |
| Walex | yes, often 'rmmod' and 'modprobe' the driver is the only way, especially after sleep etc. | 17:04 |
| Guest51 | Hello there! | 18:57 |
| gnarface | slow channel, if you have a question just ask and wait | 18:58 |
| Guest51 | Oh sorry! I don't have any questions. | 18:58 |
| Hanicef | Guest51: if you just want to chat, i'd recommend you to go to #devuan-offtopic | 18:58 |
| Guest51 | I just read about it, thanks! | 18:59 |
| Guest79 | help | 19:37 |
| Guest79 | how do i close xorg and slim | 19:37 |
| Guest79 | so i can install nvidia drivers | 19:37 |
| rwp | Hello Guest79. There isn't actually a GUI way to do that by default AFAIK. But you can "sudo service slim stop" and it will kill slim and the X session. | 19:40 |
| rwp | That will drop back to the Linux vt virtual terminal text console login. | 19:40 |
| rwp | But you can run X while installing drivers. After having installed drivers then rebooting is probably safest. Check the boot log for new driver errors. | 19:41 |
| cytokine_storm | hello, is there some way to make a iso of my entire devuan installation, so that when my ssd dies i can restore it on another new ssd on the same computer. | 19:58 |
| hagbard | cytokine_storm: boot from a stick, and use dd to copy the entire partition | 19:59 |
| hagbard | then you have an 1:1 image | 19:59 |
| hagbard | for example: dd if=/dev/sda3 of=backup.img bs=64M | 20:00 |
| rwp | cytokine_storm, Check out the Refracta installer. https://www.refracta.org/docs/readme.refractasnapshot.txt | 20:06 |
| rwp | Though a full image backup as suggested by hagbard will always be rock solid. If one can host the full space for it. | 20:07 |
| cytokine_storm | looking into it, thanks guys | 20:09 |
| furrymcgee | "runlevel 1 is used to put to system into a state where administrative tasks can be performed" man 8 shutdown | 20:16 |
| rwp | furrymcgee, I can't think of anything today that needs single user mode for maintenance. Can you? Best to ignore that old legacy and simply perform maintenance in the default run level 2. | 20:19 |
| rwp | Also a lot of that was for when administering a true multi-user machine with a terminal server and a hundred serial consoles with staff and students trying to log in. | 20:20 |
| rwp | Switching to single user mode kept all of those users off the serial ports and meant the admin could make administration without users causing files to be busy preventing unmounting and things like that. | 20:21 |
| onefang | sysv-rc-conf is sorta a GUI thing for dealing with these things. If console TUI counts as GUI. It can start and stop services. | 20:23 |
| rwp | I would like it if we brought chkconfig back alive again as it was quite sufficient. (I am still using my cached copy.) | 20:25 |
| furrymcgee | No I dont need it for anything other than announcing system is going into maintanace mode | 20:26 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!