onefang | https://www.theregister.com/2022/03/05/nvidia_stolen_certificate/ A story about the recent leaks of nVidia files that covers one of their old Windows drivers signing certificates. No mention of any Linux driver signing certificate. Be careful. | 08:49 |
---|---|---|
djph | onefang: do they even sign their *.run files? | 13:18 |
onefang | Dunno, I don't use nVidia stuff. | 13:23 |
onefang | .deb files are signed though. | 13:24 |
buZz | i dont think any OS uses signed drivers beside those winxp derivatives | 13:25 |
gnarface | uh | 13:40 |
gnarface | actually the nvidia drivers for linux are signed starting at the 900 series and for all cards after that | 13:40 |
buZz | ah, nice | 13:40 |
gnarface | it's been a big barer for fully supporting the newer cards with nouveau | 13:40 |
buZz | gnarface: the -drivers- are ? or just installers | 13:40 |
buZz | oh gee | 13:41 |
gnarface | afaik the drivers too, and that's why nouveau can't support them | 13:41 |
gnarface | nvidia promised to actually release the keys and straight up lied | 13:41 |
gnarface | that was like 4 generations ago now so i guess people are over it | 13:41 |
onefang | Well now the leakers might have released the keys. lol | 13:41 |
gnarface | heh, yea well the nouveau team is bound by US legal jurisdictions, so it won't help them but the chances of someone else releasing a driver now seem strong | 13:42 |
gnarface | i guess we'll see | 13:42 |
gnarface | the chances of seeing a drive-by trojan horse crypto miner virus seems strong too now | 13:44 |
onefang | Think there is one already. | 13:44 |
buZz | gnarface: those have existed for at least as long as monero has | 13:44 |
onefang | Drifting off topic, back on topic, if you install nVidia drivers in your Devuan, maybe double check the signatures and stuff. | 13:46 |
ham5urg | I have a vent attached via i2c. I need to write a init script as well as the fan-script itself. Is there any sysV init howto for dummies you can recommend? | 14:23 |
ham5urg | the fan-script is simple, should I merge it into the init-script? | 14:26 |
ham5urg | I guess no as the fan-script should run as a daemon. | 14:27 |
rwp | ham5urg, If it is simple you might consider adding it to the /etc/rc.local script. Be aware that by default it is "sh -e" meaning please watch the exit code status. | 15:04 |
ham5urg | That is a good hint. I prepared already an init-script. https://paste.debian.net/1233096/ My first try of an init-script. Is this acceptable? | 15:07 |
gnarface | looks right at first glance anyway | 15:09 |
ham5urg | I consider to change fancontrol.py to fancontrol.sh. All I need is a 'while true; do...' in a sh-script I guess. | 15:15 |
eyalroz | Hello Devuaners, I have a question about panel keyboard layout indicators... | 15:33 |
eyalroz | Well, a few questions really. | 15:34 |
eyalroz | Recently, and occasionally, my Cinnamon keyboard applet somehow dies. So, | 15:35 |
eyalroz | 1. How can I determine why that happens? | 15:35 |
eyalroz | 2. How can I start it after it's died | 15:35 |
eyalroz | 3. Can I make it "auto-restart" upon dying? | 15:35 |
eyalroz | Also, there's a panel applet named "iBus", which presents a (poor-contrast) keyboard layout selector. | 15:36 |
eyalroz | 4. How can I prevent it from starting? | 15:36 |
eyalroz | 5. Can I customize its colors? | 15:36 |
blastwave | ^ that is a lot of questions. I have no clue but that was a lot. I would think that the "applet" is an actual binary exec somewhere. Surely it can be simply run? | 15:41 |
ham5urg | My simple fancontroller for Raspberry Pi4 Compute Module on top of IO board. /etc/init.d/fancontrol https://paste.debian.net/1233101/ _and_ /usr/local/sbin https://paste.debian.net/1233101/ | 16:02 |
ham5urg | Any critics welcome | 16:02 |
ham5urg | Sorry, identical links. https://paste.debian.net/1233100/ | 16:05 |
eyalroz | blastwave has lieft, but I'll still answer his question... if I knew what the applet binary was called, I'd run it... | 16:24 |
syco | \o/ this has been a f*** PITA, but i finally managed to install devuan ond raid root + my two pre-existing arrays, got wifi and xorg to work too :) | 16:30 |
syco | but damnit .. to me days and lots of retrys to figure ou how to make this work | 16:31 |
syco | havent had such a complicated linux install since ... a long long time a go | 16:31 |
syco | but llok ma! ne systemd !!! \o/ | 16:31 |
syco | (need to change my keyboard batteries, sorry) | 16:33 |
syco | just need to get the other gaming keeboard witch requires a proprietary driver and the scanner (proprietary crap too) to work | 16:34 |
syco | but that's for tomorrow .. beer time \o/ | 16:35 |
eyalroz | syco: Was it really harder than installing Debian on the same hardware setup? | 17:12 |
syco | eyalroz, no, the thing is i wanted an install on raid1 / | 17:14 |
syco | but the installer didn't see my arrays | 17:14 |
syco | desktop live did see them but not desktop | 17:14 |
syco | also the deplay setting where detecte fine on desktop-live, not on desktop | 17:15 |
syco | on desktop-live, the installer didn't want to install on a md device | 17:16 |
syco | so it took me some time to sort it all out | 17:16 |
syco | s/deplay/display | 17:16 |
fsmithred | syco, if you use the cli installer in the live isos, you can install to raid if you manually set up the raid first | 17:22 |
fsmithred | but any of the installer isos should have seen your raid, I think. Maybe you have to boot into rescue mode to get that. | 17:23 |
syco | well, i finally managed to install using the desktop image, using expert install mode | 17:24 |
fsmithred | oh, good | 17:24 |
syco | wifi was a problem too, a had 3 different cards, none of witch worked ootb (rtl, brcm, orinocco) i put in antoher rtl and it finally worked | 17:25 |
blastwave | has anyone else been seeing "Errors were encountered while processing: nvidia-persistenced" followed by "E: Sub-process /usr/bin/dpkg returned an error code (1)" ? | 18:52 |
gnarface | make sure it matches the version of the rest of your nvidia drivers | 18:55 |
gnarface | if it's from the previous version just uninstall it | 18:55 |
gnarface | they keep adding and removing it from the package set but they don't make it smart enough to uninstall the older versions | 18:55 |
gnarface | it might be optional in either case | 18:56 |
eyalroz | (sigh) Ok, let me focus my questions a bit... | 21:00 |
eyalroz | What's the path of the cinnamon keyboard layout applet? | 21:00 |
eyalroz | (If it's a separate executable, that is) | 21:00 |
buZz | eyalroz: if its something you installed with apt , you could see with 'dpkg -L xxx' what files it put on your system | 22:06 |
eyalroz | buZz: cinnamon is installed with apt, but I don't know which package specifically to search for | 22:23 |
buZz | 'dpkg -l' displays all installed packages, maybe pipe it through | grep cinna | 22:31 |
fsmithred | eyalroz, it looks like everything is just part of the cinnamon binary. I fired up an old cinnamon live-iso and looked at top and ps ax while playing with settings and startup apps. | 23:02 |
sgage | Most applet-y things are autostarted at loging (don't know about Cinnamon) | 23:12 |
sgage | If Cinnamon has a control panel selection for 'autostarts', I would look there | 23:13 |
sgage | and if it's being started there, you can edit the command line, which will | 23:14 |
sgage | show you the existing command line. Again, I use other DE's - not super familiar | 23:14 |
sgage | with Cinnamon, but that's often how it goes | 23:14 |
sgage | . | 23:14 |
eyalroz | sgage: Well, it seems the enabled state of the keyboard applet is locked | 23:22 |
eyalroz | which is fine, except... when it's gone for mysterious reasons, I can't restart it | 23:22 |
eyalroz | fsmithred: Thanks. Although I'm not sure how it's possible for cinnamon to not crash, but somehow forget about there being multiple layouts. | 23:23 |
sgage | I don't quite know what you mean by 'locked'. Can you right-click on it and unlock it? | 23:23 |
sgage | When I'm messing with this kind of stuff, sometimes ps ax |grep keyboard, e.g., | 23:24 |
sgage | might be helpful. | 23:24 |
fsmithred | I tried exactly that and got nothing | 23:25 |
sgage | How strange. I don't know Cinnamon at all, really. | 23:26 |
fsmithred | wow, I rebooted the cinnamon iso, and I've gone through setup screens for startup apps and for panel applets | 23:30 |
fsmithred | several times | 23:30 |
fsmithred | in circles | 23:31 |
fsmithred | if I try to add the keyboard panel applet, the screen says it's already active. But I can't find it in the panel. | 23:31 |
fsmithred | and there seems to be no way to edit the commands for any of these things. | 23:32 |
brocashelm | i used cinnamon briefly in my minttard days; it's "pretty" to look at, but unstable (random screen freezes) and nowhere near as customizable as other des | 23:32 |
brocashelm | although when i installed cinnamon for devuan ceres, i got a blank desktop (even with the core and other meta packages) | 23:32 |
fsmithred | in a vm? | 23:33 |
brocashelm | although i am aware that debian's cinnamon maintainer quit because he liked plasma more | 23:33 |
brocashelm | in a vm and on hardware | 23:33 |
brocashelm | the only des outside of xfce that are fully functional for me are mate, lxqt, and lxde | 23:34 |
brocashelm | plasma was broken for me | 23:34 |
brocashelm | even with kwin installed | 23:35 |
fsmithred | there are a few things at /usr/bin/cinnamon* | 23:38 |
fsmithred | eyalroz, maybe some clues are in ~/.xsession-errors | 23:43 |
eyalroz | Well, I have restarted my session since it last happened, but I do see a lot of this: | 23:44 |
eyalroz | ![1646502097,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current> | 23:44 |
eyalroz | group from the event: 0 | 23:45 |
eyalroz | so, 5632 occurrences of that. | 23:46 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!