| spine-o-saurus | anyone know how to get the apt update to connect? mine is stuck at 0% | 02:56 |
|---|---|---|
| gnarface | spine-o-saurus: you should just have to have a correct /etc/apt/sources.list file, assuming your network is working... | 02:58 |
| spine-o-saurus | deb http://deb.devuan.org/merged daedalus main contrib non-free | 02:59 |
| gnarface | hmm, missing some things, but looks right at least | 03:01 |
| gnarface | you're missing daedalus-updates and daedalus-security | 03:01 |
| gnarface | each on their own lines. a correct config has a minimum of 3 lines | 03:02 |
| gnarface | there's also a deb-src line for each, optionally | 03:02 |
| spine-o-saurus | ya i remember this happened last time. the only way to solve it was reinstall | 03:05 |
| gnarface | i'm sure it's just a handful of tiny config files referring to or inferring the presence of pulseaudio that you just have to get rid of | 03:05 |
| gnarface | it shouldn't require a whole reinstall | 03:05 |
| gnarface | at least, not for that part of the problem | 03:05 |
| gnarface | but you could be facing other problems additionally | 03:05 |
| gnarface | oh woops, sorry got confused about which channel i was in there, ignore that | 03:06 |
| gnarface | spine-o-saurus: relevant to your actual problem, last time you did what exactly? | 03:06 |
| spine-o-saurus | i added updates but now it is showing:Release file for http://deb.devuan.org/merged/dists/daedalus-updates/InRelease is not valid yet (invalid for another 7h 0min 6s). Updates for this repository will not be applied. | 03:07 |
| gnarface | is your system clock wrong? | 03:07 |
| gnarface | what does "date" output? | 03:07 |
| spine-o-saurus | oh ya let me reboot | 03:07 |
| gnarface | ... shouldn't even need a reboot | 03:08 |
| spine-o-saurus | ya time is correct per https://time.is/PST | 03:13 |
| gnarface | it shouldn't have needed a reboot... | 03:13 |
| spine-o-saurus | but now when i run apt update again stuck at 0% | 03:13 |
| gnarface | is the output of "date" correct? | 03:13 |
| spine-o-saurus | ya | 03:13 |
| gnarface | you sure your network is working? what do you get from "nslookup deb.devuan.org" (don't paste it in here though, just count how many records come back) | 03:14 |
| spine-o-saurus | ya browser is reaching network just fine | 03:14 |
| gnarface | firefox? firefox might be using google's dns over https service | 03:15 |
| gnarface | try nslookup and ping | 03:15 |
| spine-o-saurus | Fetched 47.0 kB in 4min 43s | 03:15 |
| spine-o-saurus | wait now it says this | 03:15 |
| * onefang wonders if dial up or morse code was involved? | 03:16 | |
| spine-o-saurus | i think it's working, but the status percent doesn't udpate to show the progress | 03:16 |
| spine-o-saurus | so all i'm seeing is 0% | 03:16 |
| spine-o-saurus | there might be something wrong with the apt update | 03:17 |
| gnarface | maybe you're actually having some display or terminal output issue? | 03:17 |
| gnarface | did you hit ctrl+s accidentally? | 03:17 |
| spine-o-saurus | no | 03:17 |
| gnarface | do you see the same problem with apt-get or aptitude? | 03:18 |
| spine-o-saurus | no. i don't remember that having the same issue before | 03:19 |
| gnarface | i mean right now | 03:19 |
| gnarface | is it literally only apt? | 03:19 |
| spine-o-saurus | same speed issue | 03:20 |
| spine-o-saurus | not even sure that can be fixed | 03:21 |
| gnarface | hard to say | 03:21 |
| spine-o-saurus | it just takes long time to complete & there is no progress indicator | 03:21 |
| gnarface | well the no progress indicator is the part that seems wrong. taking a long time could be normal. | 03:22 |
| gnarface | but i cannot reproduce here | 03:22 |
| spine-o-saurus | maybe it is the internet here | 03:22 |
| gnarface | you could try a few individual mirrors from the list, maybe find one you have a better route to | 03:23 |
| spine-o-saurus | ya how do i change that | 03:23 |
| gnarface | here, just pick one of these and put it in your sources.list instead of deb.devuan.org: http://deb.devuan.org/mirror_list.txt | 03:23 |
| spine-o-saurus | ok that is working now | 03:29 |
| rrq | that's not how mirroring works; the mirors might only serve with domain name deb.devuan.org... and some of them also serves with format CC.deb.devuan.org where CC is a country code | 03:29 |
| rrq | if you want to select a particular mirror you need to set up /etc/hosts (or a dns service) to make tha IP resolution | 03:30 |
| onefang | Um no, you can just pick one from that list and edit sources.list as gnarface said. | 03:31 |
| gnarface | thanks onefang | 03:31 |
| rrq | onefang: have you verified that? | 03:32 |
| gnarface | rrq: these are all accessible directly by their own hostnames too, which is why https sporadically breaks when you're using the round-robin | 03:32 |
| onefang | I do that on my desktop, to point to my own mirror, to eat my own dog food. | 03:33 |
| rrq | the servers have virtual services for particular domain names, and you cant't just use their IP or other names for them | 03:34 |
| onefang | Except that they Do respond to their own domain name. That's verified coz that's one of the tests apt-panopticon does. | 03:35 |
| rrq | eg mirror.rrq.au is not an HTTP service | 03:36 |
| gnarface | rrq: you can make a virtual service respond to two domain names, what you can't do is make a https key do that | 03:36 |
| rrq | yes and not all deb.devuan.org mirrors serve in other names than deb.devuan.org | 03:37 |
| onefang | rrq: how you set up yours is different to how most others set theirs up. | 03:37 |
| onefang | A lot of others have their package mirror on a sub directory. Your DNS trick wont help there. | 03:38 |
| rrq | ??? | 03:38 |
| rrq | DNS trick? | 03:38 |
| onefang | "rq: if you want to select a particular mirror you need to set up /etc/hosts (or a dns service) to make tha IP resolution" | 03:38 |
| rrq | yes the client sets up so that deb.devuan.org resolves to the mirror IP,... then the HTTP request will ask that server for service in the name of deb.devuan.org | 03:39 |
| rrq | because that's what the mirroring is about | 03:39 |
| onefang | We are talking about the client using one of those mirrors directly, you are talking about the DNS-RR. | 03:40 |
| rrq | again. mirror server do not need to serve the devuan content in any other name than deb.devuan.org | 03:40 |
| onefang | Again, MOST do. | 03:41 |
| rrq | so then you have to tell clients to use one of them and not the others | 03:41 |
| onefang | Which is what gnarface did. Both methods are useful sometimes. | 03:42 |
| rrq | how many is "most"; have you checked? | 03:42 |
| onefang | Off the top of my head I think yours is the only one that doesn't. | 03:42 |
| rrq | have you actually checked? | 03:43 |
| onefang | The details will be in apt-panopticon. | 03:43 |
| gnarface | i haven't checked myself, but also nobody has complained about that advice before | 03:44 |
| onefang | I sometimes give the same advice. | 03:44 |
| rrq | that's fine; it's not a good advice, but you do you | 03:45 |
| gnarface | well, i didn't know any of them might not be reachable by their own hostnames, but also nobody i gave that advice to has ever reported having trouble finding one they could reach that way, i don't even recall anyone complaining that any of them couldn't be reached that way... | 03:48 |
| gnarface | ...so "most" might be accurate | 03:48 |
| rrq | sure, but there is no requirement or expectation for devuan mirroring that they provide that service | 03:56 |
| rrq | hmm sledjhamr.org doesn't... ?? | 04:00 |
| gnarface | does for me | 04:04 |
| rrq | you get http://sledjhamr.org/merged/dists/archived.README (without it changing to https)? | 04:05 |
| gnarface | no, but http://sledjhamr.org/devuan/merged/dists/archived.README | 04:06 |
| gnarface | you'd have to put the /devuan/ part in sources.list too, but afaik should work fine... | 04:06 |
| onefang | That's what I said before, some use a sub directory. | 04:07 |
| gnarface | i probably should have mentioned that specifically to spine-o-saurus, but again, he didn't seem to have a problem, and after all it's listed explicitly as BaseURL in the mirror_list.txt | 04:08 |
| rrq | that's good and important yes | 04:12 |
| rrq | and in fact http://mirror.rrq.au/ does serve something as well ... my short-term memory is failing me :) | 04:19 |
| rrq | so I stand corrected; the advice of using the BaseURL is workable | 04:23 |
| Guest58 | be me, on Daedalus, do an apt-upgrade. | 10:01 |
| Guest58 | get this mess: | 10:01 |
| Guest58 | Setting up nvidia-persistenced (535.171.04-1~deb12u1) ... | 10:01 |
| Guest58 | Starting NVIDIA Persistence Daemon | 10:01 |
| Guest58 | nvidia-persistenced failed to initialize. Check syslog for more details. | 10:01 |
| Guest58 | invoke-rc.d: initscript nvidia-persistenced, action "start" failed. | 10:01 |
| Guest58 | dpkg: error processing package nvidia-persistenced (--configure): | 10:01 |
| Guest58 | installed nvidia-persistenced package post-installation script subprocess returned error exit status 1 | 10:01 |
| Guest58 | dpkg: dependency problems prevent configuration of nvidia-driver-full: | 10:01 |
| Guest58 | nvidia-driver-full depends on nvidia-persistenced; however: | 10:01 |
| Guest58 | Package nvidia-persistenced is not configured yet. | 10:01 |
| Guest58 | dpkg: error processing package nvidia-driver-full (--configure): | 10:01 |
| Guest58 | dependency problems - leaving unconfigured | 10:01 |
| Guest58 | Errors were encountered while processing: | 10:01 |
| Guest58 | nvidia-persistenced | 10:01 |
| Guest58 | nvidia-driver-full | 10:01 |
| Guest58 | E: Sub-process /usr/bin/dpkg returned an error code (1) | 10:01 |
| Guest58 | how fix? | 10:01 |
| fsmithred | I think if you install without Recommends you can avoid installing nvidia-persistenced which is not really required for the driver to work. | 10:10 |
| fsmithred | and I might be giving you old information. There might be another solution. | 10:10 |
| Guest58 | I should probably just blacklist it, if thats teh cure | 10:11 |
| fsmithred | dont install nvidia-driver-full | 10:12 |
| fsmithred | it's a metapackage and as you said, it depends on a problem package | 10:12 |
| fsmithred | just install the parts you need. (I don't know which ones) | 10:12 |
| fsmithred | probably nvidia-driver-some-version and some -dkms package and nvidia-settings if that's a separate package. | 10:13 |
| Guest58 | its worth a swing. time to reboot and see if it changed anything | 10:17 |
| Guest58 | BRB | 10:17 |
| fsmithred | good luck | 10:17 |
| Guest58 | no joy | 10:19 |
| fsmithred | which nvidia packages did you install? | 10:21 |
| fsmithred | need food. back in a few minutes. | 10:22 |
| Guest58 | grrr | 10:25 |
| Guest58 | nvidia-driver is already the newest version (535.216.01-1~deb12u1). | 10:25 |
| Guest58 | firmware-misc-nonfree is already the newest version (20230210-5). | 10:25 |
| Guest58 | when I reinstall the dkms, I get `autoinstall for dkms modules has been disabled.' | 10:28 |
| fsmithred | I don't know what that means | 10:38 |
| Guest58 | makes two of us | 10:38 |
| Guest58 | all I know for sure is that I still have no working nvidia drivers. :( | 10:39 |
| fsmithred | nvidia-driver, nvidia-support, nvidia-modprobe, nvidia-driver-bin and libgl-nvidia-glx | 10:41 |
| fsmithred | ^^^ found that in old log | 10:41 |
| * Guest58 reboots again | 10:44 | |
| Guest58 | nope | 10:47 |
| fsmithred | guesses here: blacklist nouveau? edit xorg.conf? | 10:52 |
| Guest58 | pretty sure nouveau is already blacklisted | 10:52 |
| cousin_luigi | Guest58: Could there be something to set in a configuration file? | 10:53 |
| Guest58 | thats what I'd like to know | 10:54 |
| cousin_luigi | Guest58: find /etc -name "*dkms*" | 10:54 |
| Guest58 | this was all working two days ago , until I did a silly apt-upgrade | 10:54 |
| cousin_luigi | hmmm | 10:54 |
| cousin_luigi | was dkms one of the updated packages? | 10:54 |
| Guest58 | probably. it was a big list. | 10:56 |
| Guest58 | I'd gona few months without updating | 10:56 |
| cousin_luigi | Guest58: Is there an /etc/dkms/no-autoinstall file? | 10:57 |
| Guest58 | ... yes | 10:57 |
| * Guest58 smacks face on wall | 10:58 | |
| cousin_luigi | Dunno if that's the way to go though, maybe it's a security precaution and there's a different workaround. | 10:59 |
| Guest58 | at this point, I THINK the drivers are installed, they're just not loading... | 11:03 |
| Guest58 | # modprobe nvidia | 11:10 |
| Guest58 | modprobe: FATAL: Module nvidia-current not found in directory /lib/modules/6.1.0-31-amd64 | 11:10 |
| Guest58 | modprobe: ERROR: ../libkmod/libkmod-module.c:1047 command_do() Error running install command 'modprobe -i nvidia-current ' for module nvidia: retcode 1 | 11:10 |
| Guest58 | modprobe: ERROR: could not insert 'nvidia': Invalid argument | 11:10 |
| * Guest58 goes to bed, will be back in 6.5 | 11:11 | |
| gnarface | there's a proper way to retrigger dkms manually, but you need build tools and the linux kernel headers package corresponding to your installed kernel for it to work right | 11:25 |
| gnarface | not sure if that's the only problem here but it definitely won't work right without it | 11:29 |
| * Guest8 yawns | 16:42 | |
| * Guest58 stabs graphics drivers with a logic probe | 17:57 | |
| Guest58 | nope. drivers still not working | 18:20 |
| dosensuppe2 | plasma41: thanks a lot! | 19:17 |
| dosensuppe2 | though for some reason applying 03,05,06,08 fails applying | 19:18 |
| dosensuppe2 | nevermind. I did it with git am like you said in the message and it didn't return any errors | 19:26 |
| dosensuppe2 | ok. I successfully built the package, but wasn't able to install it via the package manager due to dependency problems. | 20:22 |
| dosensuppe2 | I'll wait till it gets accepted into the release. thanks | 20:22 |
| dosensuppe2 | it's not *that* dire | 20:23 |
| dosensuppe2 | I just pulled the newest version from the git. probably doesn't go well with a stable debian install | 20:28 |
| dosensuppe2 | libpam-snapper_0.10.6-1.3_amd64.deb | 20:28 |
| dosensuppe2 | libpam-snapper-dbgsym_0.10.6-1.3_amd64.deb | 20:28 |
| dosensuppe2 | libsnapper7t64_0.10.6-1.3_amd64.deb | 20:28 |
| dosensuppe2 | libsnapper7t64-dbgsym_0.10.6-1.3_amd64.deb | 20:28 |
| dosensuppe2 | libsnapper-dev_0.10.6-1.3_amd64.deb | 20:28 |
| dosensuppe2 | snapper/ | 20:28 |
| dosensuppe2 | snapper_0.10.6-1.3_amd64.build | 20:28 |
| dosensuppe2 | snapper_0.10.6-1.3_amd64.buildinfo | 20:28 |
| dosensuppe2 | snapper_0.10.6-1.3_amd64.changes | 20:28 |
| dosensuppe2 | snapper_0.10.6-1.3_amd64.deb | 20:28 |
| dosensuppe2 | snapper-dbgsym_0.10.6-1.3_amd64.deb | 20:28 |
| dosensuppe2 | these are the built packages | 20:28 |
| plasma41 | dosensuppe2: What were the dependency problems? | 21:57 |
| plasma41 | dosensuppe2: Also which release are you building for? | 21:58 |
| plasma41 | dosensuppe2: Because of the t64 transition that occurred in testing/unstable, building a backport of the fixed snapper package requires one additional patch applied after the patchset that fixes Debian bug #976888. Here's that additional patch: https://paste.debian.net/1352889/ | 22:09 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!