| adhoc | you have iwconfig installed ? | 00:01 |
|---|---|---|
| SOFTWIFI | iw? | 00:01 |
| SOFTWIFI | I am on testing | 00:01 |
| SOFTWIFI | Oh, yes I do. | 00:02 |
| SOFTWIFI | I have iwconfig, iw, ifconfig and ip | 00:05 |
| rwp | The command to adjust the transmit power is something like "iw dev wlan0 set txpower limit 30" or something similar. It's been a while since I played with it. | 00:10 |
| SOFTWIFI | Did I miss messages? | 00:12 |
| gnarface | yes | 00:13 |
| gnarface | <rwp> The command to adjust the transmit power is something like "iw dev wlan0 set txpower limit 30" or something similar. It's been a while since I played with it. | 00:13 |
| SOFTWIFI | ifconfig wlan0 down; sleep 1; iw wlan0 set txpower limit 100; sleep 1; ifconfig wlan0 up | 00:14 |
| rwp | SOFTWIFI, Try "iw help | less +/txpower" and look at the online syntax guide. It's confusing. I would have to try several combinations. | 00:14 |
| SOFTWIFI | I think it might have started working somehow? | 00:15 |
| SOFTWIFI | I kept getting the exact same txpower out of iw wlan0 info | 00:15 |
| SOFTWIFI | so I monitored with while iwconfig wlan0 | grep -o -e 'Tx-Power.*$' -e 'Frequency:[^ ]*' | tr '\n' ' ' ; do echo; sleep 3; done | 00:16 |
| SOFTWIFI | Yeah, it's saying 1dBm instead of 15dBm now! | 00:17 |
| SOFTWIFI | I was hitting 80deg C chassis temps streaming video with the laptop in my lap so it was urgent ^^' must've overlooked something. | 00:18 |
| SOFTWIFI | The commands I posted are what ended up working. Oh and set txpower has an "acceptable value set", e.g. 100 200 300 work but no in-between values. | 00:19 |
| SOFTWIFI | Okay, thanks for the second pair of eyes on this. | 00:19 |
| adhoc | iwconfig has been renamed iw ? | 00:22 |
| SOFTWIFI | No it's a new command, I think it's different from iwconfig | 00:22 |
| SOFTWIFI | Like with ifconfig / ip | 00:22 |
| adhoc | ok, nice. | 00:22 |
| adhoc | got it. | 00:23 |
| rwp | adhoc, No. Like a lot of classic utilities it was rewritten and the new one is the currently in fashion one to use. | 00:23 |
| adhoc | in fashion, eh? | 00:23 |
| adhoc | is that devuan specific or from upstream ? | 00:24 |
| rwp | However in the wifi space it appears that the wireless tools versions are not leaving soon and so even though they have been rewritten and theoretically replaced the older ones are still functioning correctly and one could keep using them for a while longer yet. | 00:24 |
| rwp | adhoc, Upstream changes. | 00:24 |
| rwp | With ifconfig and ip however the Linux kernel has been dorking with the network interfaces and ifconfig really cannot do everything that it needs to do now. One really does need to start using ip for Linux systems. (BSD folks keep using a different ifconfig command which continues to be a kitchen sink of everything, but that's BSD not Linux.) | 00:27 |
| adhoc | speaking of things changing, has devuan been infected with wayland? | 00:27 |
| rwp | Not by default. But you can install wayland on Devuan. | 00:27 |
| SOFTWIFI | I also use OpenBSD and Windows and ARM and PPC so it's okay, nothing ever works | 00:27 |
| adhoc | SOFTWIFI: things should work. that is the point of buildig these things. | 00:28 |
| rwp | A lot of people work cross platform and would prefer to keep using ifconfig for the finger memory of it. But... Linux has deviated. One sometimes is forced to move with it. Fortunately ip is not terrible. | 00:28 |
| SOFTWIFI | Not in one go is what I mean, I just went back from OpenBSD to Devuan testing/experimental bc OpenBSD is too hard to get a touchpad + touchscreen working comfortably. It's going into the virtual machine for today. | 00:29 |
| darwin | also, why is kernel 6.12 called bpo? Is it fine to use for long-term support (LTS) PCs for average users? | 04:29 |
| darwin | it's up to 6.14 now, and 6.15 soon. I use 6.13 on Slackware, personally, but would be using 6.14 if ZFS works | 04:29 |
| darwin | 6.13 was several months ago... | 04:30 |
| darwin | i see, it's 'backports o-something'? Tried installing it but 'cannot initiate connection to deb.devuan.org' suddenlt | 04:34 |
| darwin | on one PC, not the other; never mind that issue | 04:35 |
| fsmithred | bpo kernels are for hardware that's too new for the stable kernel | 04:45 |
| fsmithred | they don't get security patches, you just have to get the next bpo kernel | 04:46 |
| fsmithred | check your dns | 04:46 |
| fsmithred | and good night | 04:47 |
| darwin | also for new features | 04:48 |
| darwin | can I set to automatically install a standard bpo kernel (low-latency would be nice, but not real-time due to security)? | 04:51 |
| gnarface | wouldn't recommend it but check to see if there's a linux-image-[arch] metapackage in backports, that might work | 05:07 |
| gnarface | the linux-image-amd64 package from stable, for example, is what makes normal updates automatically include the next stable kernel | 05:07 |
| gnarface | if there's one of those in backports too (i forget if there is) then that should do it | 05:07 |
| gnarface | of course you would need to keep backports enabled in your sources.list as well for this to work, which i do not advise | 05:08 |
| darwin | aptitude bug: i did 'aptitude search " linux"' but get results without leading space such as gobjc-9-arm-linux | 05:08 |
| gnarface | stuff from backports isn't as well tested against the rest of the system as the normal stuff, so you have a much higher chance of conflicts if you start using too much from there at once | 05:08 |
| gnarface | i don't think you want to be searching with leading space | 05:09 |
| gnarface | i think you want to actually search for: ^linux\-image | 05:09 |
| gnarface | or maybe even: ^linux\-image\-6\. | 05:09 |
| gnarface | (don't forget to get the corresponding linux-headers-* package too, if you need it) | 05:10 |
| darwin | i know but GNU/Linux OS distributions that have more large/active teams or more testers have been testing everything past 6.1 to 6.14 generally without many problems... 6.1 is significantly old | 05:10 |
| darwin | thanks | 05:10 |
| darwin | every so often there are major performance improvements or helpful features, not just drivers | 05:10 |
| gnarface | you're fundamentally mistaken about something here; keep in mind that we get those kernels direct from debian, and their reason for the stable release to still have 6.1 is not because of lack of man power, it's frozen purposefully at that version to prevent unexpected regressions, because this distro is for doing work | 05:29 |
| gnarface | and make no mistake, they backport all the important security and stability fixes to it, it's not just a vanilla 6.1 kernel | 05:29 |
| gnarface | yes, that might mean waiting until the next release for certain new features (or using backports) but decades of experience shows very clearly that those new features usually come hand-in-hand with unacceptable risks to security, stability, and data integrity | 05:30 |
| gnarface | if you'd rather live your life closer to the bleeding edge, you're free to upgrade to the testing or unstable releases, which will get those new features very quickly, along with all the risks (i recommend you make a backup first though) | 05:31 |
| gnarface | the unstable release would be a very similar experience to using any of those other bleeding-edge or "rolling release" distros, both in frequency of major version updates and unexpected regressions | 05:33 |
| gnarface | i used to do it myself for many years, because i'm also a gamer, but games are getting better in general at not needing such bleeding-edge versions of everything (mostly) | 05:34 |
| gnarface | and of course you're free to build and install your own kernel from any source you like | 05:35 |
| gnarface | generally it's more trouble than it's worth though unless you need a specific feature for a specific purpose | 05:36 |
| gnarface | (backports exists to catch the most popular of those cases) | 05:36 |
| darwin | yes; I made mistake: Slackware-stable uses 5.15 and sometimes keeps same kernel for years (even five years) unless there are stability/security fixes... Slackware-current isn't rolling release, and doesn't have as many problems as those despite sometimes adding 0-day kernels to testing set (even faster than rolling release like Arch)... are there other options to install newer (6.13, 6.14) in Devuan from a testing version? | 06:02 |
| CueXXIII | darwin: you can build the kernel yourself from source, and if you run make bindeb-pkg you get some nice .deb packages (in the parent of the build dir) you can install | 07:14 |
| gnarface | yes, you could probably also get the debian kernel source package from ceres and use the tools to build packages from it | 08:20 |
| gnarface | if you're careful you can probably just manually copy the kernel binary and modules from another distro you like and use them even, but it's not advised | 08:21 |
| joerg | test | 17:16 |
| plasma41 | joerg: ack test | 17:54 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!