* DocScrutinizer05 ACKs furrywolf | 03:04 | |
DocScrutinizer05 | alas particularly for BT it seems polypaudio is inevitable | 03:05 |
---|---|---|
DocScrutinizer05 | the PA-free alternative died a few years ago | 03:05 |
furrywolf | there's no way to use bluetooth without pulse? | 03:12 |
furrywolf | googling says https://github.com/Arkq/bluez-alsa works great, and is alive. | 03:18 |
gnarface | hmmm. have you tried it in ascii yet? | 03:19 |
furrywolf | I don't use bluetooth, so haven't tried it at all... | 03:20 |
furrywolf | if everything else really does require pulse, we probably should package and distribute that. | 03:22 |
gnarface | yea i think there's a showstopper though | 03:24 |
gnarface | it used to be in debian | 03:24 |
gnarface | it got pulled for a reason | 03:25 |
gnarface | it may not have even been a good reason, i don't know | 03:25 |
furrywolf | "encourages people not to use pulseaudio" is their idea of a good reason... | 03:25 |
gnarface | very likely, but my point is someone would have put it back by now probably if they hadn't strategically blocked it somehow compatibility-wise | 03:26 |
furrywolf | also, anyone else finding packages.debian.org to either be down or to have changed something that breaks google links to it? | 03:26 |
gnarface | seems to be up for me | 03:28 |
gnarface | redirecting to https now, maybe that's new? | 03:29 |
furrywolf | https://packages.debian.org/wheezy/bluez-alsa is from a google search | 03:29 |
furrywolf | it gives " | 03:30 |
furrywolf | two or more packages specified (bluez-alsa wheezy) | 03:30 |
furrywolf | " | 03:30 |
furrywolf | obviously parsing the url wrong... | 03:30 |
furrywolf | the only thing I can find about it being dropped is "use pulseaudio". | 03:31 |
gnarface | i agree with you that there's clearly an agenda | 03:31 |
gnarface | i'm just saying they won't have left it at that. they'd have made sure to cram jam a monkey wrench in there somewhere to keep people from proving them wrong. | 03:32 |
golinux | furrywolf: Try apulse | 03:33 |
golinux | I haven't needed it yet hut many people have to get around PA | 03:33 |
gnarface | will that work with bluetooth audio? i didn't think apulse was that fancy. | 03:33 |
golinux | Dunno. Do some searches on the lists and forum | 03:33 |
furrywolf | it sounds like there was a period where bluez-alsa did not work with bluez5, so they used that as justification for removing it, and never re-packaged it when it was as expectedly promptly fixed. | 03:33 |
furrywolf | golinux: the topic is making bluetooth audio hardware work without pulse, not making applications work without pulse. :) | 03:34 |
furrywolf | and how, as is getting increasingly typical, debian "accidentally" killed a way to not use pulse. | 03:34 |
Centurion_Dan | furrywolf: do we need to build bluez-alsa for devuan? | 03:35 |
Centurion_Dan | can somebody build it and prove it works?? | 03:35 |
gnarface | my bluetooth dongle stopped working even earlier, so i can't | 03:35 |
furrywolf | also, it looks like bluez dropped normal communications methods and started only talking over dbus, which was why bluez-alsa originally broke. | 03:36 |
furrywolf | Centurion_Dan: I don't have any bluetooth hardware to test with. | 03:36 |
gnarface | i have this one bluetooth dongle that worked in kernel 3.1 | 03:36 |
gnarface | not a version before or after | 03:36 |
gnarface | i tried to file a bug report and the maintainer told me if i could find the bug myself and point it out to him he'd fix it, but only if i also mailed him the hardware (which he could only say he would almost certainly not bother returning) | 03:38 |
gnarface | so i went to radio shack and bought a 12' headphone cable | 03:39 |
gnarface | problem solved | 03:39 |
furrywolf | https://www.raspberrypi.org/blog/raspbian-stretch/ raspbian packages and uses bluez-alsa themselves to make bluetooth work from rpis without pulse. | 03:39 |
furrywolf | "From a user point of view, everything should still work exactly as before – the only change is that if you still wish to use PulseAudio for some other reason, you will need to install it yourself." I like these people! | 03:40 |
gnarface | interesting | 03:40 |
gnarface | i wonder if pulse finally proved too heavy for the rpi cpu | 03:40 |
gnarface | well if they made it work with raspbian it might still require systemd somehow though | 03:41 |
gnarface | right? | 03:41 |
furrywolf | and/or too utter shit. | 03:41 |
gnarface | no, raspbian doesn't give a crap about reliability | 03:41 |
furrywolf | lol | 03:41 |
gnarface | they break their own kernel firmware almost 4 of every 5 updates | 03:41 |
gnarface | they would have had to pull it because it literally cripples performance | 03:42 |
gnarface | and not just a little | 03:43 |
gnarface | they'd be handwaving the problem away otherwise | 03:43 |
furrywolf | https://archive.raspberrypi.org/debian/pool/main/b/bluealsa/ looks like they're packaging it for all archs... some of them updated this month. | 03:43 |
gnarface | interesting... | 03:43 |
furrywolf | bluealsa_0.9_amd64.deb2018-10-11 11:08 | 03:43 |
gnarface | there was something else needed | 03:43 |
gnarface | a simple pairing app | 03:43 |
gnarface | also absorbed by systemd | 03:44 |
gnarface | i was under the impression it could be replicated with a simple python script though | 03:44 |
furrywolf | anyone here have bluetooth hardware and working (i.e. pulse-free) audio and want to try that package out? | 03:44 |
furrywolf | also, do the raspbian people have other packages we should be distributing? lol | 03:45 |
gnarface | omxplayer | 03:48 |
gnarface | but that's more arm-specific | 03:49 |
gnarface | well, rpi specific | 03:49 |
gnarface | at least | 03:49 |
gnarface | not sure if the bananna pis use the same video chip or not | 03:49 |
gnarface | even with patches for the video decoding hardware though, vlc is too cpu hungry for a rpi1 if you don't overclock it | 03:50 |
gnarface | so omxplayer is the only really viable player for rpi1 | 03:50 |
furrywolf | I can't imagine ever wanting to play video on a pi in the first place. | 03:51 |
gnarface | it works really well at 1080p@60 | 03:54 |
gnarface | ... if you're using omxplayer and the video is in a supported encoding and pixel format | 03:54 |
gnarface | it actually makes a nice video player for how low power it is | 03:54 |
furrywolf | I have no desire for a video player. lol | 03:55 |
gnarface | oh, heh, well then it would be an exercise in futility for you | 03:55 |
gnarface | the video decoder supports h264 as long as it's yuv420p | 03:57 |
gnarface | and also mpeg2 if you pay like $2.50 extra for the key | 03:57 |
gnarface | (but it's easy to exceed the bandwidth capabilities of the poor little thing with a mpeg2 stream so i can't imagine how useful that would be) | 03:58 |
furrywolf | I've been thinking of getting an rpi to log data from my weather station and solar system, to replace a failed nslu2... no video. :P | 04:00 |
gnarface | i still think you're better off with something from pine64.org | 04:01 |
furrywolf | I'm not sure what's wrong with the nslu2... lights do things, but it's not talking to anything. | 04:01 |
furrywolf | that pine64 website really sucks. | 04:08 |
gnarface | their website sucks and their ordering process is a mess | 04:11 |
gnarface | frankly they're just a bunch of kids | 04:11 |
gnarface | but they don't exhibit the overt greed i see from Broadcom | 04:11 |
gnarface | their hardware is carefully designed and generously priced | 04:12 |
gnarface | if mainline software support is lagging well... it's a sideffect of youthful ambition | 04:12 |
gnarface | i'm confident the mainline kernel support will catch up | 04:12 |
gnarface | for a headless server though, the mainline kernel already does all that fine | 04:13 |
gnarface | where the support is lagging is on stuff mobile users would want... camera, audio, bluetooth, hdmi output, gpu acceleration, etc | 04:13 |
furrywolf | "The Pine A64 board supports SD, SDHC, and SDXC format microSD card – this means the largest capacity is 256GB. Please note that if a microSD card is formatted as an FAT32 file format, the maximum capacity is 32GB." seriously, they fucking listen to microsoft's force-people-to-use-exfat crap? I do not like these people. | 04:14 |
gnarface | hmmm | 04:17 |
gnarface | i think they just get a lot of android users who don't know shit so they have to warn them about that stuff | 04:17 |
gnarface | keep in mind that 3.11-BSwhatever kernel is the android kernel | 04:18 |
gnarface | so these things boot android too | 04:18 |
furrywolf | the only thing they're warning you about is that they intentionally crippled it to comply with microsoft's corruption of the sd card standard. | 04:18 |
gnarface | oh, i see what you're saying | 04:19 |
gnarface | i'm not sure that's actually the case though | 04:19 |
furrywolf | normal linux doesn't care in the slightest what filesystem you put on the card... the 32gb-fat32-on-sd limit is, however, required for official licensing of the sd card spec. | 04:20 |
gnarface | i'm reading that as a warning about the limitation of fat32 not the hardware | 04:20 |
furrywolf | no, there's no technical reason for it. | 04:20 |
furrywolf | it's a legal reason. | 04:20 |
gnarface | but it's only a problem if you're using fat32 to being with... | 04:21 |
gnarface | what would you be doing with fat32 on a headless linux logging server? | 04:21 |
furrywolf | if you officially license the sd spec, you're required to reject sd cards over 32gb with fat32 filesystems on them. | 04:21 |
gnarface | really? | 04:21 |
furrywolf | yep | 04:21 |
gnarface | and that's not a limit of fat32 | 04:21 |
furrywolf | yep | 04:21 |
gnarface | i thought the natural limit for fat32 was lower than 32GB actually | 04:22 |
gnarface | anyway | 04:22 |
gnarface | i'm assuming the sd card license was already tied to the boards by the manufacturer | 04:22 |
gnarface | keep in mind these guys aren't manufacturing this stuff either | 04:22 |
gnarface | it's just rebranded android hardware | 04:22 |
furrywolf | most devices made before >32gb cards were a thing will happily use 64gb or 128gb cards with fat32 systems on them anyway... then when the big cards come out, devices that wanted to officially use them had to intentionally add checks to reject them. | 04:22 |
gnarface | so it may have been a choice the manufacturer made that they had to keep with in order to keep the cheap hardware | 04:23 |
gnarface | (in order to re-use an existing design as the base instead of having to design something from scratch like they're sopine boards) | 04:23 |
gnarface | *their | 04:23 |
furrywolf | it was due to microsoft's influence on the sd spec... they wanted to discourage use of non-microsoft operating systems, by making devices use filesystems that linux etc couldn't read. | 04:24 |
gnarface | heh, seems like they wasted a lot of effort on that. someone should have told them fat32 was already supported | 04:24 |
furrywolf | there is still no legal-in-the-US support for >32gb sd cards on linux. | 04:24 |
gnarface | i'm gonna have to test that | 04:25 |
furrywolf | oh, it works fine. | 04:25 |
furrywolf | it's just moved to a non-US-based FUSE module, not the kernel. | 04:25 |
gnarface | i am actually not sure i have any sd or microsd cards larger than 32GB here | 04:26 |
gnarface | but i've never put fat32 on them anyway | 04:27 |
furrywolf | you must not own any consumer electronics? :P | 04:27 |
furrywolf | for example, a digital camera, a mp3 player,... | 04:28 |
gnarface | i guess not | 04:28 |
gnarface | i mean i have several smaller cards just none above 32GB | 04:28 |
furrywolf | I mean, that all consumer electronics only work with fat32... | 04:32 |
furrywolf | if you never put fat32 on them, you must not be using any of them in consumer electronics. | 04:33 |
gnarface | hmmm | 04:42 |
gnarface | you're right, i think the wii does use encrypted files on fat32 | 04:43 |
gnarface | i'm pretty sure the wii-u reformats the entire thing though once you put it in | 04:43 |
gnarface | what i meant is that, as a general rule, i don't use fat32 on them in linux | 04:47 |
gnarface | i've not tested fat32's limits in this context | 04:48 |
furrywolf | I do, because I add or remove files from these devices from linux. heh. | 04:48 |
furrywolf | i.e. put mp3s on the mp3 player, or download images from my camera. | 04:48 |
golinux | (Some people just don't get that this is a devuan help channel) | 04:52 |
furrywolf | I add and remove files from my fat32-formatted cards from devuan. :P | 04:53 |
gnarface | sorry | 04:53 |
nacelle | its all washing out anyways now that MS has released the patents around that to OIN | 04:55 |
golinux | #debianfork | 04:58 |
* man_in_shack flails | 09:08 | |
blerg | How can I get my laptop to suspend when I close the lid? Debian wiki says a systemd service replaced pm-utils. Do pm-utils still work? | 12:13 |
djph | in devuan, they should | 12:14 |
blerg | djph: Cool. (I am using Devuan) | 12:14 |
blerg | Now to figure out how to get a display manager to play nice with Stumpwm. | 12:15 |
ejr | wew lads, after about half a year of not using devuan, i am back now, and more happy with it than ever :) | 12:29 |
jyri | hi | 13:41 |
pilgrimm | Pardon if this is a stupid question, does anyone know if the Wacom digitizer on Lenovo's Yoga 720s work with Devuan? | 13:42 |
pilgrimm | Using my other casual drawing pc that has plain deb on it because my main workhorse crapped out, but I want to go back to devuan :< | 13:45 |
jyri | anyone aware that ceres has totally broken GTK support on applications? I mean that even $ reportbug | 13:46 |
jyri | zsh: segmentation fault reportbug | 13:46 |
jyri | strace points to GTK problems and any program that uses GTK refuses to launch | 13:46 |
jyri | pilgrim: don't know without trying :) | 13:47 |
gnarface | pilgrimm: the kernel is the same | 13:49 |
gnarface | hardware support shouldn't be different unless it somehow requires systemd | 13:49 |
gnarface | jyri: has this been happening for a long time? | 13:50 |
pilgrimm | gnarface: ah so it's a kernel thing then. i thought it was a package thing but then again that actually checks out from my experiences | 13:50 |
pilgrimm | I'm using sysvinit on debian and it works fine with my pen so I highly doubt it's dependent on systemd. Thank you for the response, now I'm confident enough to put devuan on here :) | 13:52 |
jyri | gnarface: I just noticed it today | 13:53 |
gnarface | pilgrimm: it probably does also need some or another xorg package and maybe some config snippet, but that usually comes along with a standard xorg install | 13:53 |
gnarface | at least these, i'm guessing: xserver-xorg-input-wacom, libwacom-bin, libwacom-common, libwacom2 | 13:54 |
gnarface | except where systemd was removed, the packages and dependences are all the same as on debian | 13:55 |
gnarface | jyri: i care, but i can't do anything about it. i'll avoid updating today. thanks for the warning :) | 13:55 |
gnarface | jyri: (i do assume this type of thing will get fixed upstream) | 13:56 |
jyri | gnarface: ok :) I do apt update ; apt -y upgrade ; apt -y autoremove ; apt clean every morning when I come to the office (this is my workstation) | 13:56 |
gnarface | oh boy | 13:56 |
gnarface | ceres on a workstation | 13:56 |
jyri | :D | 13:56 |
gnarface | that takes a special type of bravery | 13:56 |
jyri | I like to live on the edge | 13:56 |
jyri | it has only once bitten me in the ass before (then it was worse since it removed Xorg) | 13:57 |
jyri | but that one was easy to downgrade, now I'm not sure which package caused this since it wasn't any that has gtk on the name of it | 13:59 |
gnarface | well, it's worth checking the debian bug tracker to see if anyone else has noticed it | 14:00 |
sickness | hi all | 17:13 |
sickness | what is the best/fastest way to install ceres? install devuan ascii then change sources.list then do a dist-upgrade? (that is the advice I've found on the forums) | 17:15 |
jyri | sickness: that's it | 17:16 |
jyri | but, don't install today, I think that I run in an bug that messes up gtk | 17:17 |
sickness | jyri: ah, I was just curious to test it, nothing production, so even if it explodes it's ok :) | 17:22 |
golinux | jyri: https://igurublog.wordpress.com/2012/11/05/gnome-et-al-rotting-in-threes/ | 17:33 |
golinux | The gnome/GTK thing has been coming for a long time | 17:34 |
golinux | sickness et al: Be aware that there are some packages that are newer in ascii than in beowulf or ceres. | 17:35 |
golinux | Our workflow is changing to now modify packages in ceres and let them move down to older releases. | 17:36 |
pankerini | Wow, I didn't imagine the GTK/gnome problem lasted this long | 17:37 |
sickness | ah, ok | 17:40 |
golinux | Yeah, it's been a long time coming . . . | 17:49 |
golinux | Bottom line is that the gnome sickness goes hand in hand with the systemd sickness | 17:50 |
premoboss | hi | 18:01 |
premoboss | devuan ascii 64 bit. already did update/upgrade. Amule is quite instable, it crash often (at least 4 times today). | 18:02 |
premoboss | PC with 4GiB Ram ,a nd 200G of free space, fs is ext4. | 18:03 |
enyc | premoboss: hrrrm silyl question, does the machine memtest86+ ok? i'd then look in kernel log (dmesg) to see what sort of crashes... | 18:06 |
premoboss | ok, i go for kernel log. | 18:07 |
fsmithred | premoboss, did you see this bug report? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846061 | 18:08 |
premoboss | fsmithred, no i go to read now. | 18:09 |
premoboss | ah... then is that. | 18:09 |
fsmithred | looks like it didn't get fixed. Last post says use the jessie version | 18:10 |
premoboss | 2 time ago when he drashed, i got a pop ul windows wint error similar to that bug... it was like a "debug" window, you can do "close" or "continue" but if i choose "continue", it iterate in endless loop so i was forced to chose "close" | 18:11 |
premoboss | so, we must wait for bugfix, ok. | 18:12 |
fsmithred | maybe it's fixed in sid/ceres. That report is 18 months old. Check the changelog. | 18:15 |
nemo | golinux: heh. Redhat GnomeOS (in comments on that link) - yeah prettymuch | 18:18 |
nemo | golinux: I wonder when we'll get SystemDKernel | 18:18 |
nemo | they kinda already tried to inject themselves in there once already and were beaten back | 18:19 |
nemo | but that was when Linus was not busy removing himself from power | 18:19 |
MinceR | gkh already has write access to Linus' branch | 18:26 |
MinceR | so it's not long until systemd-kerneld | 18:26 |
* nemo sighs | 18:27 | |
nemo | welp. BSD is still an option | 18:27 |
pankerini | Year of the Hurd Desktop soon | 18:28 |
golinux | So is forking the kernel | 18:29 |
KatolaZ | yeah, sure.... | 18:29 |
KatolaZ | :D | 18:29 |
MinceR | hurd is dead | 18:29 |
MinceR | and who will maintain the kernel fork? | 18:30 |
MinceR | https://www.gnu.org/software/hurd/open_issues/systemd.html | 18:30 |
nemo | problem with forking is the ever growing burden of integrating useful stuff from the other side of fork, and maintaining enough people. it's about the community vote, and so far at least the community is unfortunately like... maybe 5% anti-systemd to 95% "I have a desktop, who cares" | 18:30 |
KatolaZ | MinceR: the hobbits | 18:30 |
nemo | I kinda wonder what the % is amongst active linux/FOSS contributors | 18:30 |
MinceR | it seems to me that the "modern" side isn't interested in implementing useful stuff anyway | 18:30 |
MinceR | so i wouldn't worry about that | 18:30 |
nemo | MinceR: well... the corporate coders will presumably implement anything they are assigned to do. | 18:31 |
nemo | MinceR: heh '<pochu> let's create our own init system, make it better than anyone else<pochu> let's create our own init system, make it better than anyone else' | 18:32 |
nemo | MinceR: «With hookers, and blackjack» | 18:32 |
KatolaZ | nemo: the percentage of what? | 18:32 |
nemo | https://www.youtube.com/watch?v=e35AQK014tI | 18:33 |
nemo | KatolaZ: I was just wondering if literally everything in the entire linux ecosystem could become systemd dependent, or if the % of those who actually help build stuff under linux in userspace regular apps, desktops or system might push back | 18:34 |
nemo | if anti-systemd sentiment is stronger in that group, it'd be harder for that to happen | 18:34 |
KatolaZ | still don't get the point, but I guess it's OK | 18:35 |
KatolaZ | :) | 18:35 |
KatolaZ | there is no reason why everything at the application leve should depend on systemd | 18:36 |
KatolaZ | there are some applications which might need some of the facilities made available by systemd | 18:36 |
KatolaZ | e.g., session management | 18:36 |
KatolaZ | but none of those is *necessary* | 18:36 |
KatolaZ | (meaning that there are always other ways of obtaining the same result without using the facility made available by systemd) | 18:37 |
MinceR | it's kind of like that most mono applications don't need the "non-core" parts not covered in microsoft's useless "promise" | 18:37 |
MinceR | and yet all major mono applications use them anyway | 18:37 |
KatolaZ | it's a bit different MinceR | 18:37 |
MinceR | in the "modern" world, necessity is not a factor | 18:37 |
KatolaZ | why would an editor need to know what init system is currently running? | 18:38 |
MinceR | so that it can depend on systemd | 18:38 |
KatolaZ | non sequitur | 18:38 |
MinceR | business as usual | 18:38 |
KatolaZ | but which business? | 18:38 |
MinceR | red hat's | 18:39 |
KatolaZ | MinceR: red hat does not develop everything in the FOSS world... | 18:39 |
MinceR | indeed, they just aim to destroy everything in the FOSS world | 18:40 |
nemo | KatolaZ: there's no reason why it *has* to - but it could be harder and harder to avoid, what if gtk3 did *everything* over dbus and relied on a systemd specific implementation | 18:43 |
KatolaZ | nemo: it's already like that :) | 18:43 |
nemo | KatolaZ: can't predict the future but what it *feels* like is an all consuming glob trying to shove everything into process 0 or the kernel | 18:43 |
KatolaZ | welcome to 2018 | 18:43 |
nemo | KatolaZ: can't be totally like that since you guys are still able to shim it out | 18:44 |
KatolaZ | uh? | 18:44 |
KatolaZ | gnome is not installable cleanly in devuan | 18:44 |
nemo | KatolaZ: hm? devuan has gtk3 apps | 18:44 |
nemo | and ones using dbus even | 18:44 |
fsmithred | nemo, I have a no-dbus build with most of the apps that normally are included in Refracta | 18:44 |
nemo | KatolaZ: but yes gnome3 is not installable | 18:44 |
KatolaZ | I know nemo | 18:44 |
KatolaZ | :) | 18:44 |
nemo | I was just trying to imagine rot spreading | 18:44 |
KatolaZ | even if in principle it's just a matter of a wrong dep on the debian package | 18:45 |
KatolaZ | since it should be possible for GNOME to work with libpam-systemd | 18:45 |
nemo | It's like someone looked at Microsoft Windows with its HTML parsing and font rendering and widget drawing in ring 0 and though "man, that's a damn good idea. | 18:45 |
KatolaZ | which is provided by elogind | 18:45 |
nemo | " | 18:45 |
nemo | linux kernel - now with wayland | 18:46 |
nemo | blazing fast UIs! | 18:46 |
KatolaZ | that's not gonna happen nemo | 18:46 |
nemo | Did you guys ever read the MS justification for why they did that? I thought it was pretty funny | 18:46 |
nemo | it boiled down to - we aren't fast enough to compete w/ OS with real security measures otherwise, and, we're gonna be super careful | 18:47 |
nemo | last year there was a priv escalation in the UI code... | 18:47 |
KatolaZ | nemo: I stopped caring about M$ more or less at the same time I got the first PC | 18:47 |
KatolaZ | :) | 18:47 |
nemo | still need to use it for work unfortunately | 18:47 |
nemo | but major win on my part, just last month I got our first *OFFICIAL* linux server at the office | 18:48 |
nemo | until that point they were adamant that they could only support Windows | 18:48 |
nemo | this allows for a possible transition once Win 7 is EOL'd | 18:48 |
KatolaZ | the few times I had to use windoes, I just used cygwin under it | 18:48 |
nemo | only issue is Oracle which irritatingly charges more for the Linux builds even though the performance is better - I think the logic is if you're using linux you must be a big operation and therefore they can extract more from you | 18:49 |
nemo | so convincing them to relicense the db and other oracle junk under linux might be a sticking point | 18:49 |
nemo | but who knows | 18:49 |
nemo | BTW, that linux server is Ubuntu 14.04 - I am hoping to convince them to allow me to transition it to Devuan Ascii before next spring EOL of ubuntu 14.04 but they might just force me to upgrade to 16.04 instead | 18:53 |
UsL | hello vuans! So, my system changes sometimes and the values in /etc/fancontrol settings becomes outdated. hwmon02 is suddenly hwmon01 and so on. Is there a way to solve that or make the fans go 100% when settings are outdated? | 19:03 |
KatolaZ | UsL: what do you mean by "my system changes sometimes"? | 19:48 |
UsL | Device path of hwmon2 has changed | 19:56 |
UsL | Device name of hwmon2 has changed | 19:56 |
UsL | Configuration appears to be outdated, please run pwmconfig again | 19:56 |
UsL | so in this instance hwmon0 is acpitz | 19:57 |
UsL | hwmon1 is dell_smm | 19:57 |
UsL | changed places | 19:57 |
UsL | it can happen now and then.. Have not pin pointed the reason | 19:58 |
terra | Anyone able to properly boot from devuan iso with grub2 ? | 22:02 |
terra | I'm able to boot but installer is trying to find a cdrom device. | 22:02 |
golinux | Comment out the cdrom line in /etc/fstab | 22:09 |
golinux | terra: ^^^ | 22:09 |
terra | really? | 22:11 |
negev | hi | 22:23 |
negev | running beowulf i'm seeing consistently high cpu usage indicated in top, with no apparent processes listed using anywhere near what the total is indicated as | 22:24 |
negev | anyone else seeing this? | 22:24 |
negev | 4.18.0-2-amd64 on a xen vps | 22:24 |
golinux | terra: Yeah, misread your question | 22:25 |
leo | negev: try atop instead of top | 23:04 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!