| Xenguy | https://paste.debian.net/ resolves fine here. I'm not sure I understand the problem report | 03:19 |
|---|---|---|
| bb|hcb | Xenguy: I have seen some discussion on the bind mailing list that it fails to resolve with newer versions of bind. It is misconfig in the domain that is cname of paste.debian.net. E.g. from the public resolvers 9.9.9.9 works while 9.9.9.11 fails | 03:30 |
| Xenguy | Wow, sounds unfortunate, and way above my pay-grade | 03:32 |
| bb|hcb | DNSSEC FTW | 03:34 |
| rwp | Xenguy, Look at https://dnsviz.net/d/snow-crash.org/dnssec/ to see details of the breakage. | 04:56 |
| Xenguy | Thank rwp , I will but not tonight, my sponge is saturated : -) | 04:57 |
| Xenguy | *Thanks | 04:57 |
| rwp | It's just a web page report on the problem. And you asked! But no worries. Nothing we can do about it. I think we wait for the weekday IT techs at snow-crash.org to fix it this next week. | 05:02 |
| Xenguy | rwp, True, I did at that | 05:30 |
| gnarface | devurandom: nvidia drivers were broken recently in debian stable in the 6.1.0-18 kernel, if that's the upgrade you are talking about it wouldn't expect graphics to be working at all for you in fact... only solution at the moment is to downgrade to 6.1.0-17 and wait for them to fix it | 05:53 |
| gnarface | (i heard 6.1.0-17 has some samba issue though, so if you're using that you may have to downgrade even further, but earlier kernel builds are still in the repos) | 05:59 |
| Bandit7 | hi | 07:30 |
| debdog | oy | 07:31 |
| Bandit7 | hey can anyone help me out with wifi | 10:28 |
| Bandit7 | basically network manager or connman wont let me scan wifi, i can only connect via the dhcp client thing setup during installation | 10:29 |
| debdog | Bandit7: same happened to me. only solution I've found so far is setting /etc/network/interfaces. no clue atm how to make connman or n-m working. | 10:32 |
| debdog | unfortunately I have no access to the laptop on which that happens atm. what hardware do you have? IIRC in my case it was broadcom ath9 (or similar) | 10:34 |
| debdog | Bandit7: plus, can you please do a "dmesg | grep wlan"? | 10:36 |
| Bandit7 | Sure, the result on that dmesg command is: | 10:47 |
| Bandit7 | [ 64.604491] wlan0: 80 MHz not supported, disabling VHT | 10:47 |
| Bandit7 | [ 64.614748] wlan0: authenticate with 88:ad:43:e2:4a:98 (local address=28:c2:dd:d3:b3:9d) | 10:47 |
| Bandit7 | [ 64.614755] wlan0: send auth to 88:ad:43:e2:4a:98 (try 1/3) | 10:47 |
| Bandit7 | [ 64.618422] wlan0: authenticated | 10:47 |
| Bandit7 | [ 64.620673] wlan0: associate with 88:ad:43:e2:4a:98 (try 1/3) | 10:47 |
| Bandit7 | [ 64.626872] wlan0: RX AssocResp from 88:ad:43:e2:4a:98 (capab=0x1431 status=0 aid=1) | 10:47 |
| Bandit7 | [ 64.627267] wlan0: associated | 10:47 |
| Bandit7 | [ 64.736999] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 88:ad:43:e2:4a:98 | 10:47 |
| Bandit7 | my computer is CPU: AMD A4-6210 APU with AMD Radeon R3 Graphics (4) @ 1.800GHz | 10:47 |
| Bandit7 | GPU: AMD ATI Radeon R3 Graphics | 10:47 |
| debdog | hmm, ok, that ouput is different to the one I got. so the culprit might be a different one. | 10:55 |
| debdog | anyhow, I gotta run. just stick around, someone else might have an idea! | 10:56 |
| Bandit7 | ok thanks take care | 10:58 |
| gnarface | Bandit7: what's the model of the wifi device and of the wifi router you're trying to use? that wlan0 paste doesn't show any specific signs of failure, just saying that the router isn't accepting its highest speed rating | 11:03 |
| gnarface | you might have better luck increasing logging verbosity in wpasupplicant then watching /var/log/daemon.log while you try to connect | 11:03 |
| Bandit7 | the wifi thingy in my pc is: 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01) | 11:05 |
| Bandit7 | I will try that let's see what happens | 11:05 |
| Bandit7 | wifi still dead | 11:08 |
| gnarface | Bandit7: you do have the firmware for it, right? | 11:12 |
| gnarface | i'm not sure if that one needs firmware, but if it does it would be in the package "firmware-realtek" i think | 11:13 |
| Bandit7 | yeah i have that firmware and the amd firmware too | 11:14 |
| gnarface | i gotta afk for a bit, only ideas i have are the mundane things, troubleshooting dhcp/network-manager etc (mostly by amputation) | 11:16 |
| gnarface | you might have luck poking at the router settings itself | 11:16 |
| gnarface | did this used to work before, or is this a new hardware combination you're trying? | 11:16 |
| gnarface | if you can get a high verbosity log from /var/log/daemon.log while the connection attempt is happening, that might lend some more clues | 11:17 |
| Bandit7 | this same hardware worked fine when I was using a different linux distro, both connman and network managed behaved normally | 11:18 |
| Bandit7 | well thank you for the ideas, i will try messing with those things and see if anything changes | 11:18 |
| rrq | is wlan0 configured in /etc/network/interfaces? .. doing that might stop network-manager and connman from touching it | 11:21 |
| gnarface | seems like there might be some issue with both connman and network-manager in the recent versions, as that's a repeated complaint over the past couple days, but i'll be back later to look at your logs if you can dig them up | 11:22 |
| gnarface | defining the connection manually in /etc/network/interfaces may have sabotaged network manager, but alternately it might be the solution too if network manager is just broken and needs to be disabled/uninstalled until fixed | 11:22 |
| gnarface | (maybe someone else here who had just recently also suffered through this apparent regression can help you with the basics of that) | 11:23 |
| gnarface | Bandit7: any luck digging up those wpasupplicant logs? | 11:59 |
| gnarface | to be clear, it looks like from just the part you pasted that the wifi actually connects, so we need more information. the failure may actually be DHCP related | 12:00 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!