previous
2022-12-03
---------- 2022-12-04 ----------
05:19:08 <rkta> alsa is not listing my pc speaker. How can I change the sound level? It's very loud.
05:20:52 <hagbard> If alsa knows it, then you can set the volume with alsamixer.
05:21:05 <hagbard> Or do you mean the Mainboard beeper?
05:21:41 <hagbard> Its loudness can't be set.
05:30:13 <rkta> the mainboard beeper. Iirc I had it as an alsa channel on other devices, but not in this one.
05:32:37 <hagbard> I think it can only be an alsa channel, if it's not an actual classical physical beeper, but is emulated by the sound chip/driver.
05:35:11 <rkta> that makes sense
05:35:54 <hagbard> An actual pc-speaker would just be a tiny bit of hardwired hardware, with no way to influence its level by software.
06:54:54 <leitz> Trying to update a node, and getting "release file for .... is not valid yet". How do I either remove that repo, or is there another option?
06:56:16 <hagbard> Is maybe your clock way off?
06:57:48 <hagbard> that would explain getting a date in the "future"
06:59:02 <hagbard> I there's a problem with a specific repo mirror, choosing a different one would help: https://pkgmaster.devuan.org/mirror_list.txt
06:59:17 <leitz> yup, thanks. On boot, it didn't have internet connectivity. Rebooting, to see if ntp starts up on its own.
07:19:44 <leitz> Date was still off, chrony was not installed. Fixed the latter, which fixed the former, and the upgrade is in progress.
07:20:37 <leitz> It's an old Dell E6500, having issues. I have to look at an i801_smbus transaction timeout error, and figure out why trying to look at Firefox settings locks up the computer.
08:47:49 <leitz> If I want to blacklist a module, but there is no /etc/modprobe.d directory, is it okay to create it?
08:57:25 <debdog> leitz: I'd say yes.
09:00:12 <leitz> looks like I'm blind, it was there. I wrote blacklist.conf, but to no avail. Do the modules need to be in their own files?
09:00:52 <leitz> And hey, debdog, thanks! My chat screen still showed the last time you answered a question for me. :)
09:03:40 <debdog> no, one .conf can contain more than one module. just to be certain, you have a "blacklist $module_name" and a new line in there?
09:05:06 <leitz> debdog, yeah, it was a few weeks ago.
09:06:34 <leitz> So, /etc/modprobe.d/blacklist.conf didn't stop the boot error. Neither did single files nor putting "install <module> /bin/true".
09:07:36 <leitz> I'm not sure if it's related, but on build it asked for a "regulatory.db" for some non-free hardware. No idea how to go about that.
09:15:38 <devuanconsumer> Hi guys. I installed devuan on a new system with a ryzen 7950x processor with an integrated GPU. I have the following issues: 1) no temps are showing up 2) small resolution due to not being able to find graphics drivers for it on synaptic. I tried sudo sensors-detect without success. I also tried installing the packages without success: amd64-mirocode, firmware-amd-graphics, sudo sensors-detectand running What is the repository to try new
09:15:39 <devuanconsumer> kernals?
09:17:11 <devuanconsumer> should I try the backports or the experimental?
09:18:59 <divad27182> with new devices... you might need to wait a few months for linux to implement things...
09:19:22 <devuanconsumer> ryzen 7950 was released at the end of september
09:19:27 <devuanconsumer> so must i wait 6 months or a year?
09:19:41 <divad27182> possible
09:19:58 <divad27182> there should be something, but you might be missing some bits for a time.
09:21:54 <divad27182> and you might need to wait longer for it to be in a distribution kernel
09:22:11 <devuanconsumer> should I simply try both backports and experimental?
09:22:14 <divad27182> checking Linux 6.0.11 for "7950" now
09:22:41 <devuanconsumer> how can I do what you're doing
09:23:18 <divad27182> Well, in this case, I downloaded the 6.0.11 kernel a day or so ago, and unpacked it.
09:23:32 <divad27182> now I CDed into the source tree and ran: find . -type f -exec grep 7950 {} +
09:23:44 <divad27182> download from www.kernel.org
09:24:03 <devuanconsumer> how do i install it?
09:24:09 <devuanconsumer> im a newb lol
09:24:11 <devuanconsumer> compared to u
09:24:15 <divad27182> you might just try googling "linux" and your CPU model
09:27:15 <divad27182> for the sensors... You might try looking to see if you have anything in /sys/class/thermal/
09:32:39 <devuanconsumer> ok I will look into it
09:33:06 <leitz> How do I totally blacklist i2c_i801 and i2c_smb modules? Can I just remove the i2c packages?
09:33:06 <divad27182> four instances so far of "7950" in sources, at least one more expected. None relevant.
09:34:04 <divad27182> you can blacklist a module by putting a blacklist line in a file matching /etc/modprobe.d/*.conf
09:34:19 <leitz> divad27182, so far that's not working.
09:35:32 <divad27182> I think I've seen that once or twice. I think you might need to remove (or rename) the files in /lib/modules/....
09:52:49 <divad27182> leitz: I think there is a requirement the filename end in .conf in this case.
09:53:13 <devuanconsumer> @divad, I looked inside the sys/class/thermal and there are 31 components there it looks the same as on my pc where sensors are detected
09:54:15 <divad27182> assuming some where thermal_zone*, those should report temperatures.
09:55:30 <divad27182> not sure where else to look...
09:55:59 <divad27182> hard drives may require another package to report their temps.... at least, they used to.
09:56:28 <devuanconsumer> how do I install this https://github.com/ocerman/zenpower
09:56:30 <devuanconsumer> for devuan
09:56:33 <devuanconsumer> i'm a newb
09:56:36 <devuanconsumer> please check out this link
09:56:42 <divad27182> there are 3 other pieces of hardware called a "7950" that I've seen in the kernel
09:57:54 <divad27182> with caution....
09:58:35 <divad27182> that appears at first glance to be a kernel mod/patch...
09:59:53 <divad27182> so the first step is to get a working kernel source build....
10:00:16 <divad27182> well... and as that hasn't changed sine 2020, I would not expect it to work for your CPU.
10:00:37 <divad27182> on the other hand, if it is a matter of IDs, you might be able to whitelist something
10:07:40 <devuanconsumer> ok so I restarted with the new 6.0.0.0 driver from synaptic package after adding experimental and backports to sourceslist and it booted up with more sensors
10:07:51 <devuanconsumer> now i am seeing tctl and tccd1 and tccd2
10:07:54 <divad27182> devuanconsumer: In any case: you asked how to install that. The ubuntu instructions have a good chance of working (ubuntu could be callsed a sibling distribution to devuan).
10:08:02 <devuanconsumer> they seem to be the cpu temps
10:08:30 <divad27182> seems possible.
10:08:40 <divad27182> newer kernels support newer CPUs.
10:08:50 <devuanconsumer> thank you for the help man
10:08:52 <devuanconsumer> this is good enough
10:09:00 <devuanconsumer> i don't care about the resolution apu for the 7950
10:09:07 <devuanconsumer> it sucks its only 1000x700
10:09:11 <devuanconsumer> because no graphics driver
10:09:13 <devuanconsumer> but thats fine
10:09:15 <divad27182> well
10:09:19 <devuanconsumer> i just want to see the temps for this mining rig
10:09:23 <devuanconsumer> they're for mining :)
10:09:27 <divad27182> that might just be a matter of find the right driver to install
10:09:29 <devuanconsumer> i want to overclock
10:09:43 <devuanconsumer> i already tried all of them in the synaptic manager
10:09:47 <divad27182> or even just parameterize it right
10:09:57 <devuanconsumer> even though shitty resolution, i can play 4k videos while mining
10:09:58 <divad27182> synaptic just installs packages.
10:10:13 <divad27182> now load the right module into the kernel... or parameterize it right
10:10:25 <devuanconsumer> i need practical instructions lol
10:10:45 <divad27182> well...
10:11:13 <divad27182> check out the contents of /var/log/Xorg.0.log
10:11:23 <divad27182> it may tell you about your video system.
10:12:33 <devuanconsumer> ok
10:12:43 <devuanconsumer> is there a command i can run
10:12:45 <devuanconsumer> i don't remember
10:12:47 <divad27182> make sure your monitor is better than the resolution you are seeing, as the card/OS may not be willing to do better than the monitor
10:12:58 <devuanconsumer> my monitor is definitely good
10:13:07 <devuanconsumer> display port 1.4 and hdmi 2.0
10:13:17 <divad27182> I think there is readedid, but I think that tells you about the monitor.
10:14:12 <leitz> divad27182, I had already added a blacklist.conf to /lib/modules.d
10:14:20 <u-amarsh04> my /etc/X11/xorg.conf just has the following 4 lines:
10:14:25 <u-amarsh04> Section "Device"
10:14:27 <u-amarsh04> Identifier "Radeon Cape Verde"
10:14:28 <u-amarsh04> Driver "amdgpu"
10:14:29 <divad27182> You could try gvidm and see what it offers for resolutions
10:14:29 <u-amarsh04> EndSection
10:14:48 <divad27182> leitz: I think it may be modprobe.d not modules.d
10:14:57 <u-amarsh04> the text in quotes on the Identifier line doesn't really matter
10:15:57 <u-amarsh04> and my /etc/modprobe.d/local.conf blocks radeon as I use amdgpu:
10:15:59 <u-amarsh04> blacklist radeon
10:16:45 <divad27182> devuanconsumer: What u-amarsh04 is saying is probably a good solution for you.
10:17:29 <u-amarsh04> but also, I build my own kernels
10:17:30 <devuanconsumer> i am only using the integrated graphics on 7950x
10:17:34 <devuanconsumer> no radeon graphics card
10:17:38 <devuanconsumer> no discrete graphics card
10:17:46 <devuanconsumer> no nvidia graphics card
10:18:05 <divad27182> didn't amd buy radeon?
10:18:08 <u-amarsh04> that 7950x apu should still use the amdgpu module
10:18:17 <devuanconsumer> which one is that
10:18:19 <u-amarsh04> AMD bought ATI
10:18:25 <devuanconsumer> what package?
10:18:29 <devuanconsumer> in synaptic
10:18:31 <divad27182> not packages.
10:18:38 <devuanconsumer> what module?
10:18:39 <divad27182> edit files, maybe reboot.
10:18:52 <devuanconsumer> specific instructions please :)
10:18:59 <leitz> divad27182, you're right, I just mistyped.
10:19:06 <u-amarsh04> amdgpu is a kernel module, should be all kernels over the last several years
10:19:50 <divad27182> so put a line reading "amdgpu" (no quotes) in file /etc/modules
10:20:19 <divad27182> then put the four lines u-amarsh05 showed into /etc/X11/xorg.conf
10:20:31 <u-amarsh04> and make sure that you have the package: xserver-xorg-video-amdgpu installed
10:20:57 <divad27182> yes, then do "modprobe amdgpu", then restart your X server.
10:21:13 <devuanconsumer> how do i restart x server
10:21:37 <divad27182> might be enough to logout and back in.
10:21:49 <divad27182> might need to "kill" the server.
10:21:58 <divad27182> might need to reboot.
10:22:16 <divad27182> for a newb, if not too inconvenient, I would say reboot.
10:22:24 <u-amarsh04> yes, when I log out of the graphical desktop, the desktop manager restarts the X server
10:23:38 <u-amarsh04> if you are still having issues, checking /var/log/Xorg.0.log may help
10:25:12 <devuanconsumer> ok let me try
10:33:20 <divad27182> I have another thought about those sensors. You said you had installed "sensors-detect". Did you run "sensors-detect"? It doesn't try to detect sensors just because you've installed it.
10:40:31 <u-amarsh04> will be idling, after 2am here
10:41:52 <divad27182> 10AM here - need to get breakfast.
10:42:56 <devuanconsumer> Here is my log info u-amarsh04 https://pastebin.com/9XUtuc5d
10:50:43 <divad27182> did you get the lines entered into /etc/X11/xorg.conf ?
10:54:55 <divad27182> (The pastebin doesn't show any evidence of "amdgpu")
11:05:18 <devuanconsumer> ok great now i busted my computer
11:05:29 <devuanconsumer> after rebooting with all the fixes
11:05:34 <devuanconsumer> it's asking for "gklogin 01"
11:06:03 <devuanconsumer> "gk01 login:"
11:06:10 <devuanconsumer> how do i fix this :/
11:06:41 <devuanconsumer> i did all of this : /etc/X11/xorg.conf just has the following 4 lines:
11:06:41 <devuanconsumer> Section "Device"
11:06:41 <devuanconsumer> Identifier "Radeon Cape Verde"
11:06:41 <devuanconsumer> Driver "amdgpu"
11:06:41 <devuanconsumer> EndSection
11:06:43 <devuanconsumer> <u-amarsh04> and my /etc/modprobe.d/local.conf blocks radeon as I use amdgpu: blacklist radeon
11:06:45 <devuanconsumer> divad27182> put a line reading "amdgpu" (no quotes) in file /etc/modules
11:07:23 <devuanconsumer> divad27182: and u-amarsh04: please help
11:07:32 <divad27182> ok... that much is promising.
11:07:57 <divad27182> did you <u-amarsh04> and make sure that you have the package: xserver-xorg-video-amdgpu installed
11:08:09 <devuanconsumer> yes
11:08:17 <devuanconsumer> it was already installed
11:08:29 <devuanconsumer> in the etc/modules
11:08:35 <devuanconsumer> what was the file name
11:08:36 <divad27182> OK. login
11:08:37 <devuanconsumer> i added one
11:08:44 <devuanconsumer> i don't understand how to login
11:08:51 <devuanconsumer> "gk01 login:"
11:08:54 <devuanconsumer> how?
11:09:05 <divad27182> that is the login prompt, text mode variant.
11:09:15 <devuanconsumer> so how do i login though
11:09:20 <devuanconsumer> i don't know lol
11:09:27 <divad27182> you enter your username. Then it prompts for password
11:09:35 <devuanconsumer> ok before i do that
11:09:47 <devuanconsumer> put a line reading "amdgpu" (no quotes) in file /etc/modules, what was the name of the file suppose to be for this
11:09:57 <devuanconsumer> i added a file for modules.d
11:10:08 <devuanconsumer> named amdgpu.conf and added amdgpu
11:10:23 <divad27182> actually, the filename is "/etc/modules"
11:10:26 <divad27182> no .d
11:10:29 <divad27182> no subdirectory.
11:10:36 <devuanconsumer> lol
11:10:37 <divad27182> just a simple list
11:11:42 <divad27182> in any case, you need to get logged in, go find /var/log/Xorg.0.log
11:11:47 <divad27182> and see what the errors are
11:12:00 <divad27182> why X failed to start
11:12:06 <devuanconsumer> well
11:12:13 <devuanconsumer> i logged in and it didn't login to desktop
11:12:26 <devuanconsumer> it continued in the text mode
11:12:30 <divad27182> right. No X -> no desktop.
11:12:39 <devuanconsumer> how do i get desktop?
11:12:45 <divad27182> start X.
11:12:57 <devuanconsumer> do i type start X?
11:13:05 <devuanconsumer> "start X" without ""
11:13:09 <divad27182> which means first: find out why X did not start.
11:13:16 <divad27182> so: no desktop for now.
11:13:34 <devuanconsumer> so what do i type in the text mode
11:13:49 <divad27182> try: less /var/log/Xorg.0.log
11:14:13 <divad27182> you need to look for lines with EE (or maybe FF) in the front
11:16:09 <divad27182> Some will be problems, some not.
11:17:03 <divad27182> (apparently it doesn't use FF... so just "(EE)" lines)
11:17:17 <divad27182> probably near or at the end
11:17:47 <devuanconsumer> it says there's a parse error "section" is not a valid keyword in this section
11:17:55 <devuanconsumer> problem parsing the config file
11:18:00 <devuanconsumer> error parsing the config file
11:18:04 <devuanconsumer> no screens found
11:18:22 <devuanconsumer> this is for the xorg.conf
11:18:47 <devuanconsumer> > etc/X11/xorg.conf
11:19:05 <divad27182> ok. that file's syntax is painfully critical.
11:19:06 <devuanconsumer> can i edit the xorg.conf from the text line?
11:19:25 <gnarface> devuanconsumer: note, sensors are in the package "lm-sensors"
11:19:25 <divad27182> yes. What editor's do you know? and have installed?
11:19:39 <gnarface> devuanconsumer: (you have to install that first then run sensors-detect)
11:21:36 <gnarface> for the xorg.conf try editing it with nano
11:21:43 <gnarface> that's probably the simplest choice
11:21:58 <devuanconsumer> ok but how do it get the terminal text to remove the command
11:22:11 <devuanconsumer> i mean to clear what i brought up
11:22:46 <gnarface> q to exit less, also q to exit man pages; "man xorg.conf" for syntax details on that file
11:23:11 <gnarface> note letter-case matters in that file
11:23:14 <divad27182> at this point.... you might be better off finding someone who knows linux to come in and help you.
11:25:01 <gnarface> devuanconsumer: example amdgpu device section (note that the string in "Identifier" has to match the string in "Device" under the "Screen" section: https://paste.debian.net/1262835/)
11:25:12 <devuanconsumer> ok so i opened it with nano
11:25:19 <gnarface> the strings in VendorName and BoardName don't matter
11:25:39 <divad27182> Does it match what you pasted before?
11:25:39 <gnarface> there's a bunch of other options but you probably don't need them right now
11:25:48 <divad27182> or are there punctuation or spelling errors?
11:26:20 <gnarface> it has to be "Section" not "section" too, be careful
11:26:43 <divad27182> right... "painfully critical"
11:26:57 <devuanconsumer> ok let me try
11:26:57 <divad27182> case matters on everything not quoted.
11:27:19 <gnarface> well, case matters on some of the quoted stuff too like "amdgpu"
11:27:30 <divad27182> true
11:27:59 <divad27182> the amount of whitespace doesn't matter. The presence does. "End Section" is not the same as "EndSection"
11:28:20 <devuanconsumer> what am i looking for under man xorg.conf
11:28:20 <divad27182> but it is OK to write:
11:28:29 <divad27182> Driver "amdgpu"
11:28:48 <gnarface> devuanconsumer: for xorg.conf you should read the whole thing, but ignore it for now just copy my example
11:29:09 <devuanconsumer> ok copy your example from the pastebin
11:29:15 <divad27182> But in your case, I think you may have written "section" instead of "Section"
11:29:22 <gnarface> that's what it sounds like to me
11:31:18 <divad27182> next obvious question: are you using xdm, gdm, kdm, or something else. Once you've edited and saved, you can do "invoke-rc.d xdm start" (or whichever other one you are using) to try to start the desktop.
11:31:20 <gnarface> or forgot to close a previous section or something like that
11:31:41 <divad27182> I suspect only one section at this point.
11:35:06 <devuanconsumer> ok so i rebooted and it didn't work
11:35:29 <gnarface> checked the xorg log again, if you made any meaningful change the error will also be different
11:35:35 <divad27182> OK. Login, read Xorg.0.log again
11:35:39 <devuanconsumer> ok
11:36:24 <divad27182> The invoke-rc.d variant will be faster than a reboot, and leave you where you were if it doesn't work.
11:36:44 <gnarface> yea but it probably has to be restart or stop then start not just start
11:37:05 <devuanconsumer> the error is the same
11:37:10 <divad27182> actually... you are right....
11:37:35 <devuanconsumer> "Section" is not a valid keyword
11:37:47 <gnarface> devuanconsumer: alright, you're gonna want to learn this stuff yourself eventually but if you put the whole xorg.conf in paste.debian.net i'll proofread it for you
11:38:12 <devuanconsumer> yeah im trying to learn lol
11:38:37 <devuanconsumer> i'm not sure how to put everything from xorg.conf in debian past if i only have textmode
11:39:00 <devuanconsumer> can't i just delete everything in xorg and reboot
11:39:08 <divad27182> that could work
11:39:16 <divad27182> assuming it was empty to begin with
11:39:21 <gnarface> it might work, but it might work without using the amdgpu driver
11:39:42 <gnarface> give it a try but you might end up missing out on hardware accel (the log file changes will make it obvious)
11:39:42 <divad27182> right. You might not get the resolution.
11:40:06 <gnarface> if the log file still doesn't change after that you're probably looking at the wrong log file
11:40:42 <divad27182> possible, but that would imply he is running multiple X servers
11:41:07 <gnarface> no if it's an upgraded system it could just be the change from running suid root to running as own user
11:41:20 <devuanconsumer> lol it worked!
11:41:24 <gnarface> it can have moved from /var/log/Xorg.0.log to ~/.local/share/xorg/Xorg.0.log and left behind the old log
11:41:26 <devuanconsumer> i am learning haha
11:41:38 <gnarface> devuanconsumer: check the log now to see if amdgpu shows up at all
11:43:58 <divad27182> well... good luck
11:48:32 <gnarface> the best way to learn how to make a custom xorg.conf in your case is to read the man page for xorg.conf and the man page for amdgpu while looking at some examples in the wild that are known to work
11:48:44 <gnarface> (and your error log of course)
11:49:08 <gnarface> in my case it wasn't necessary to put the amdgpu module in /etc/modules but it was for several other modules for me so ymmv
11:49:21 <gnarface> you might also need a boatload of mesa libraries to make all the hardware accel work right
11:49:38 <gnarface> everything you need is in the repo though, just don't go downloading packages from 3rd party location
11:51:13 <devuanconsumer> ok here are the pastes
11:51:34 <devuanconsumer> https://pastebin.com/VL6TzN2W
11:51:35 <devuanconsumer> https://pastebin.com/gqc4TpvR
11:51:46 <devuanconsumer> one is for the log and the other the man xorg.conf
11:53:34 <gnarface> devuanconsumer: sorry i don't trust pastebin
11:54:12 <gnarface> you're gonna have to either just /msg it to me here or figure out how to use paste.debian.net somehow if you want me to look
11:54:44 <gnarface> if your gui is up now it shouldn't be a problem
11:57:39 <devuanconsumer> ok do u prefer the paste.debian.net?
11:57:52 <gnarface> doesn't really matter but that'll be faster
11:58:15 <devuanconsumer> https://pastebin.com/VL6TzN2W
11:58:16 <devuanconsumer> https://pastebin.com/gqc4TpvR
11:58:22 <gnarface> that's still pastebin
11:59:02 <gnarface> if you /msg it to me you just have to wait a minute for it to come through due to rate limiting
12:01:42 <devuanconsumer> oops sorry
12:01:43 <devuanconsumer> lol
12:01:53 <devuanconsumer> my daughter is sick and i thought i copied and pasted it right
12:02:51 <devuanconsumer> https://paste.debian.net/1262838/
12:02:52 <devuanconsumer> https://paste.debian.net/1262839/
12:02:54 <devuanconsumer> here they are
12:03:22 <devuanconsumer> i also just added amdgpu to the etc/modules
12:03:26 <devuanconsumer> i didn't have that part right
12:03:37 <gnarface> ok, these are two identical pastes of the bottom of the xorg.conf man page, i already have a copy of it installed here so i don't need to see that
12:04:08 <gnarface> what i want to see is your actual xorg.conf attempt and the Xorg.0.log from before and after you deleted the xorg.conf
12:04:18 <gnarface> so that'd be 3 total links
12:04:43 <gnarface> if you don't have the older log still that's fine
12:07:21 <devuanconsumer> ok let me see
12:08:02 <devuanconsumer> i took a picture of the log before
12:08:10 <devuanconsumer> is there a website u trust i can add it to?
12:08:54 <devuanconsumer> this was my conf attempt Section "Device"
12:08:55 <devuanconsumer> Identifier "Radeon Cape Verde"
12:08:55 <devuanconsumer> Driver "amdgpu"
12:08:55 <devuanconsumer> EndSection
12:09:43 <devuanconsumer> oh i see pastedebian has a file
12:09:46 <devuanconsumer> feature
12:15:21 <gnarface> that was really the only thing in your xorg.conf?
12:15:29 <gnarface> no other lines besides that?
12:15:33 <onefang> Finally got JACK sorted out. The audio setup on my super desktop is complex. Though the last thing solved was "jiggle this cable a bit to get stereo out of that particular port". lol
12:15:57 <onefang> Now to try out all that wonderful audio and MIDI software.
12:16:14 <gnarface> onefang: you might want to disable "Auto-Mute Mode" in alsamixer if furnished, it can cause trouble
12:16:52 <gnarface> i had a problem with it triggering at the wrong time due to loose connections
12:16:54 <onefang> Haven't spotted that yet.
12:17:14 <gnarface> if jack takes over your alsamixer view like pulseaudio does, you'll have to make sure it's not running first
12:17:18 <onefang> Not using alsamixer anyway.
12:17:36 <gnarface> it would be a hardware feature exposed by the driver to alsamixer directly
12:17:54 <gnarface> it may or may not be furnished, but if you're not using a laptop on the go it's probably not worth it
12:18:05 <onefang> I have a Plantronics RIG mini mixer.
12:18:33 <onefang> I said "super desktop", this ain't no lappy. lol
12:19:41 <devuanconsumer> yes that was it
12:20:02 <devuanconsumer> how can i find out what the device identifier is for my APU using the terminal linux
12:20:23 <gnarface> devuanconsumer: the "Identifier" field is arbitrary, you can pick whatever you want
12:20:46 <gnarface> devuanconsumer: what is important is that it matches what's in the "Screen" section, which you don't have but you need
12:21:27 <gnarface> you don't need the whole xorg.conf anymore, you don't need any of it, but if you include some of it, there's a minimum of those two things: a valid "Device" section and a valid "Screen" section
12:22:50 <gnarface> without them, things should work but will probably fall back on the generic modesetting driver which is missing support many of your GPU's best features
12:22:58 <gnarface> support for*
12:23:00 <devuanconsumer> how do i figure out the valid screen
12:23:03 <devuanconsumer> lol
12:23:04 <devuanconsumer> :/
12:23:16 <gnarface> hang on i'll just give you one
12:23:39 <gnarface> what's your display's native resolution?
12:24:36 <devuanconsumer> devuanconsumer@gk01:~$ lspci -vnn | grep VGA -A 12
12:24:36 <devuanconsumer> libkmod: ERROR ../libkmod/libkmod-config.c:657 kmod_config_parse: /etc/modprobe.d/local.conf line 1: ignoring bad line starting with 'blacklist'
12:24:36 <devuanconsumer> 0f:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164e] (rev c1) (prog-if 00 [VGA controller])
12:24:36 <devuanconsumer> Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
12:24:37 <devuanconsumer> Flags: bus master, fast devsel, latency 0, IRQ 255
12:24:39 <devuanconsumer> Memory at fce0000000 (64-bit, prefetchable) [size=256M]
12:24:43 <devuanconsumer> Memory at fcf0000000 (64-bit, prefetchable) [size=2M]
12:24:45 <devuanconsumer> I/O ports at e000 [disabled] [size=256]
12:24:47 <devuanconsumer> Memory at fc900000 (32-bit, non-prefetchable) [size=512K]
12:24:49 <devuanconsumer> Capabilities: <access denied>
12:24:51 <devuanconsumer> Kernel modules: amdgpu
12:24:53 <devuanconsumer> 0f:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1640]
12:24:55 <devuanconsumer> Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1640]
12:24:57 <devuanconsumer> Flags: bus master, fast devsel, latency 0, IRQ 119
12:24:59 <devuanconsumer> devuanconsumer@gk01:~$ xrandr
12:25:01 <devuanconsumer> xrandr: Failed to get size of gamma for output default
12:25:03 <devuanconsumer> Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
12:25:05 <devuanconsumer> default connected primary 1024x768+0+0 0mm x 0mm
12:25:07 <devuanconsumer> 1024x768 76.00*
12:25:09 <devuanconsumer> its 1024x768 and i can't edit it to make it higher lol
12:25:13 <devuanconsumer> the display section has no other options
12:25:33 <gnarface> don't you have a manufacturer's manual to verify from?
12:25:48 <devuanconsumer> my amd manual?
12:25:51 <devuanconsumer> yes
12:25:58 <gnarface> for the display
12:26:01 <gnarface> not for the cpu
12:27:03 <devuanconsumer> oh
12:27:23 <devuanconsumer> the highest i have is 2560x1440 (16:9)
12:27:58 <gnarface> does it happen to mention horizontal and vertical refresh ranges in there too?
12:28:01 <devuanconsumer> i am basically switching screens to my main pc and the ryzen one lol
12:28:30 <devuanconsumer> devuanconsumer@devuanrig:~$ xrandr
12:28:31 <devuanconsumer> Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
12:28:31 <devuanconsumer> DVI-D-0 disconnected (normal left inverted right x axis y axis)
12:28:31 <devuanconsumer> HDMI-0 disconnected (normal left inverted right x axis y axis)
12:28:31 <devuanconsumer> DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
12:28:31 <devuanconsumer> 2560x1440 59.95 + 165.08* 144.00 120.00
12:28:33 <devuanconsumer> 1920x1200 59.88
12:28:35 <devuanconsumer> 1920x1080 119.88 60.00 59.94 50.00
12:28:37 <devuanconsumer> 1680x1050 59.95
12:28:39 <devuanconsumer> 1600x1200 60.00
12:28:43 <devuanconsumer> 1280x1024 75.02 60.02
12:28:45 <devuanconsumer> 1280x800 59.81
12:28:47 <devuanconsumer> 1280x720 59.94 50.00
12:28:49 <devuanconsumer> 1152x864 75.00
12:28:51 <devuanconsumer> 1024x768 75.03 60.00
12:28:53 <devuanconsumer> 800x600 75.00 60.32
12:28:55 <devuanconsumer> 720x576 50.00
12:28:57 <devuanconsumer> 720x480 59.94
12:28:59 <devuanconsumer> 640x480 75.00 59.94 59.93
12:29:01 <devuanconsumer> DP-1 disconnected (normal left inverted right x axis y axis)
12:29:03 <devuanconsumer> DP-2 disconnected (normal left inverted right x axis y axis)
12:29:05 <devuanconsumer> DP-3 disconnected (normal left inverted right x axis y axis)
12:29:07 <devuanconsumer> DP-4 disconnected (normal left inverted right x axis y axis)
12:29:09 <devuanconsumer> DP-5 disconnected (normal left inverted right x axis y axis)
12:29:13 <devuanconsumer> let me look on the website
12:29:28 <gnarface> careful with multi-line pastes in this channel, you can get kicked by flood protect bot
12:29:39 <gnarface> better to use paste.debian.net for anything over 3 lines
12:30:00 <devuanconsumer> oops :/
12:30:43 <devuanconsumer> here is my monitor : https://www.dell.com/en-us/shop/dell-27-curved-gaming-monitor-s2722dgm/apd/210-azzp/monitors-monitor-accessories
12:31:41 <devuanconsumer> I don't see anything about horizontal or vertical refresh rates
12:32:41 <devuanconsumer> Here is the Native Resolution QHD 2560 x 1440 (DisplayPort: 165 Hz, HDMI: 144 Hz)
12:32:43 <gnarface> stand by
12:33:25 <gnarface> it's under the support section
12:33:56 <gnarface> in a pdf, i found it
12:33:59 <gnarface> gimme a minute to type this up
12:35:40 <devuanconsumer> ok thanks you are the bomb
12:35:59 <devuanconsumer> I was looking up xorg.conf file examples on the internet
12:36:07 <devuanconsumer> and was thinking about trying some but i'll go with yours
12:37:56 <gnarface> are you using HDMI or DisplayPort? the refresh ranges are different
12:38:06 <devuanconsumer> hdmi for that one
12:38:19 <devuanconsumer> there is hdmi1 and hdmi2
12:38:19 <gnarface> there's two?
12:38:26 <gnarface> you have two displays at once?
12:38:30 <gnarface> that does complicate things
12:38:36 <devuanconsumer> no i have one display, with two ports
12:38:49 <devuanconsumer> and am using the same display for my main computer and the ryzen 7950
12:38:55 <gnarface> oh i see
12:38:58 <gnarface> ok, whew
12:39:05 <devuanconsumer> is that ok?
12:39:09 <gnarface> yea, try this then: https://paste.debian.net/1262840/
12:39:17 <gnarface> wait, hang on that one isn't perfect
12:39:29 <gnarface> this one: https://paste.debian.net/1262841/
12:39:34 <devuanconsumer> LMAO
12:39:43 <devuanconsumer> take advantage of the sections that don't matter lol
12:40:10 <devuanconsumer> ok so i copy that into the xorg.conf and reboot?
12:41:07 <gnarface> replace your current xorg.conf with that then reboot yes (reboot isn't actually necessary but easier to understand)
12:41:36 <gnarface> if it complains about it or doesn't work, just remove it again
12:41:57 <gnarface> it might want a ServerLayout section but we're trying without for now
12:42:34 <gnarface> some of the optional stuff you still sometimes want to use if you don't like default behaviors but i'm picky about these things
12:42:42 <gnarface> my own xorg.conf is ... exhaustive
12:43:02 <gnarface> here's your monitor manual by the way https://dl.dell.com/content/manual3890536-dell-s2722dgm-monitor-user-s-guide.pdf?language=en-us
12:43:11 <gnarface> you should download that pdf and keep a copy locally
12:43:43 <gnarface> if you switch to DisplayPort later you're gonna want it as a reference
12:44:17 <gnarface> in my experience auto-detect doesn't usually do this stuff perfectly so if you want optimal behavior you still have to be explicit about certain things
12:47:08 <gnarface> also you should install mesa-utils if you haven't already, because it'll pull in most of the critical hardware-acceleration librarires
12:47:11 <gnarface> libraries*
12:47:16 <gnarface> devuanconsumer: ^
12:47:27 <devuanconsumer> thank you. I am waiting for it to load. It's blinking with a _
12:48:01 <gnarface> uh... none of this should have affected boot
12:49:10 <gnarface> is it still just stuck?
12:49:26 <devuanconsumer> yeah
12:49:34 <gnarface> you had a gui login setup?
12:49:58 <devuanconsumer> it just got stuck after I decrypted LUKS
12:50:06 <devuanconsumer> with password
12:50:17 <gnarface> this shouldn't have affected boot, but if your HDMI cable can't handle the max res it might have affected the GUI
12:50:24 <gnarface> what does ctrl+alt+f2 do?
12:50:51 <devuanconsumer> it prompts me to login through text
12:51:16 <gnarface> oh, well this really should not have changed anything
12:51:26 <gnarface> the boot process doesn't read this file
12:51:32 <gnarface> did you change anything else before rebooting?
12:53:45 <gnarface> if not, you're gonna need to backup the xorg log file and move the xorg.conf out of the way and reboot again
12:53:56 <gnarface> and i will need to see that xorg log to see what went wrong
12:54:36 <gnarface> first guess is your HDMI cable can't carry 2560x1440, i assume it's not one that came with the monitor?
12:55:32 <gnarface> i hope you have another boot disk around, like a live image or the installer disk or just even another machine you can write one from ...
12:55:58 <gnarface> devuanconsumer: ^^
12:56:01 <devuanconsumer> https://ibb.co/cTnNQqH
12:56:08 <devuanconsumer> here is a picture of the error
12:56:10 <devuanconsumer> on the log
12:56:20 <gnarface> sigh, don't trust that either, can you use imgur.com instead?
12:56:28 <gnarface> i have... reasons
12:56:30 <devuanconsumer> YES for sure
12:56:55 <gnarface> wait so you were able to log in after ctrl+alt+f2 or what?
12:57:06 <gnarface> i didn't see you say how you got past the blinking "_"
12:59:49 <devuanconsumer> what other websites do you trust? i can't upload to imgur
12:59:54 <gnarface> note, imgur.com makes it seem like you have to sign up but you do not have to sign up
13:00:04 <gnarface> just click on the upload button on the front and it'll let you post anonymously
13:00:10 <devuanconsumer> yes i logged in to the text version
13:00:37 <gnarface> here do this
13:00:45 <gnarface> move the xorg log to your home directory
13:00:59 <gnarface> then move xorg conf to your home directory too
13:01:19 <gnarface> then reboot again and log in normally and you can just use paste.debian.net for the error as normal
13:01:21 <gnarface> make sense?
13:02:10 <gnarface> you might actually just be able to get the GUI up by running "startx" though after moving the xorg.conf out of the way
13:02:20 <gnarface> don't delete it, just back it up somewhere
13:02:35 <gnarface> a full reboot should not typically be necessary
13:03:00 <gnarface> but make sure whatever you do that you back up the log too so we can see it, because when you start the gui again it'll be overwritten
13:03:29 <devuanconsumer> https://imgur.com/a/BoxSFN8
13:03:59 <gnarface> none of those are errors, that's all fine
13:04:03 <gnarface> scroll down to the bottom
13:04:15 <gnarface> you're looking for lines with (EE) in them, specifically
13:06:11 <devuanconsumer> ok
13:06:21 <devuanconsumer> it says no screen found
13:06:31 <devuanconsumer> screen 0 deleted because of no matching config section
13:06:48 <devuanconsumer> devices detected, but none match those in the config file
13:06:57 <devuanconsumer> no screens found
13:07:07 <gnarface> ok, stand by, revision 2 coming
13:07:13 <devuanconsumer> please check the log file for additional revisions
13:07:20 <devuanconsumer> so is the screen name incorrect?
13:07:35 <gnarface> you might just be able to delete the line: Identifier "Screen0"
13:07:52 <devuanconsumer> ok i can do that
13:08:14 <gnarface> try that while i work on a more complete config file for you
13:10:33 <devuanconsumer> i tried it and rebooted. It didn't work
13:10:39 <devuanconsumer> It loaded the text login screen
13:10:49 <gnarface> different error though right? what error?
13:11:00 <devuanconsumer> let me check
13:12:45 <devuanconsumer> it says problem parsing the config file
13:12:47 <devuanconsumer> no screens found
13:12:58 <devuanconsumer> error parsing the config file
13:12:59 <gnarface> ok, stand by, just cleaning up something based on my config
13:13:10 <devuanconsumer> you have a paypal?
13:13:13 <devuanconsumer> you've helped me a lot
13:13:17 <devuanconsumer> let me send you something ;P
13:14:13 <gnarface> https://paste.debian.net/1262850/
13:14:15 <gnarface> here, try this config
13:15:14 <gnarface> and actually when you try that, REMOVE the "amdgpu" from your /etc/modules file, i'm really not sure it should be preloaded like that, i vaguely remember it could cause problems
13:15:29 <gnarface> but use this xorg.conf verbatim
13:15:43 <gnarface> you should not have needed to blacklist "radeon" either just fyi
13:16:09 <gnarface> i can't be sure that won't cause problems either
13:16:22 <gnarface> but at least this xorg.conf file shouldn't have any parse errors or missing sections
13:16:33 <devuanconsumer> ok so i'll undo all the changes they had me do and copy your xorg.conf
13:16:59 <gnarface> did you install mesa-utils already?
13:17:16 <devuanconsumer> i will if its not on boot up
13:17:17 <devuanconsumer> let me try
13:17:44 <gnarface> i am not sure what all changes you made, don't uninstall anything, just remove the blacklist of radeon and the preload of amdgpu
13:18:14 <gnarface> we're trying to match my working systems here as closely as possible
13:19:00 <devuanconsumer> no other changes made
13:19:29 <devuanconsumer> i left the synaptic packages default (AMD/Radeon)
13:19:30 <devuanconsumer> its booting now
13:19:51 <devuanconsumer> oops
13:20:04 <devuanconsumer> i mean my computer is loading just barely going to login to put changes in xorg
13:28:26 <devuanconsumer> do i need to have mesa-utils-extra installed?
13:28:38 <devuanconsumer> what about firmware-amd-graphics
13:28:48 <devuanconsumer> mesa-utils was already installed
13:28:50 <devuanconsumer> after this i reboot
13:29:58 <gnarface> you do need firmware-amd-graphics, i don't have mesa-utils-extra should not be necessary... other stuff you might be missing is just for some games (vulkan libraries might not be present by default but "mesa-utils" should have got you everything for most opengl and video i think)
13:30:39 <gnarface> if you have mesa-utils and firmware-amd-graphics i think none of the other missing mesa stuff should affect xorg just coming up right
13:31:40 <gnarface> it would just be for like wine or support for certain video players/codecs that might be missing in addition to that
13:31:44 <gnarface> i think you're good to reboot
13:33:09 <gnarface> if i'm wrong the xorg log will let you know
13:33:48 <devuanconsumer> yes
13:33:57 <devuanconsumer> it's saying that i need it while loading stuff
13:34:23 <devuanconsumer> ok let me install and try again
13:37:06 <gnarface> devuanconsumer: here's the ones i have installed, ignore versions (i'm on unstable) and :i386 duplicates (they're for wine and steam) https://paste.debian.net/1262855/
13:37:45 <gnarface> main parts of the base package names should be mostly unchanged for you though
13:40:17 <gnarface> particularly, make sure you have libgl1-mesa-dri and libgl1-mesa-glx, but i had assumed mesa-utils or firmware-amd-graphics would get those for you already
13:41:52 <divad27182> still at it, I see.
13:42:21 <gnarface> yea :-/ always a struggle the first time
13:45:26 <devuanconsumer> fuck
13:45:35 <devuanconsumer> now it freezes and doesn't even login
13:46:04 <devuanconsumer> here is a picture
13:46:11 <devuanconsumer> https://imgur.com/a/9eMmze4
13:47:25 <gnarface> hmm, you're on stable?
13:47:41 <gnarface> i wonder if you need the backports kernel and firmware
13:48:09 <gnarface> you might need a newer kernel and firmware to support this hardware
13:48:27 <gnarface> sorry you'll have to move the xorg.conf out of the way again but don't delete it
13:48:42 <gnarface> you got your install disk or a live cd to recover from?
13:49:00 <onefang> I did need the stable-backports kernel for my newish AMD graphics card.
13:49:10 <onefang> But I'm off to bed now.
13:49:26 <gnarface> devuanconsumer: yea, seems likely you'll need the backports kernel and firmware-amd-graphics
13:49:41 <devuanconsumer> ok
13:49:47 <devuanconsumer> let me try loggin in with the old kernal
13:49:52 <devuanconsumer> and i do have a live disk
13:51:41 <gnarface> you should be able to access the harddrive from the live disk to move the xorg.conf out of the way
13:53:32 <devuanconsumer> q
13:54:57 <gnarface> devuanconsumer: don't panic, i know it doesn't look like it but this is actually progress
13:57:09 <devuanconsumer> ok i logged back in
13:57:14 <devuanconsumer> with the old kernal
13:57:17 <devuanconsumer> now what
13:57:26 <devuanconsumer> i double check that i have all the same drivers installed
13:57:35 <devuanconsumer> and then in the mean time tell me how to install backports kernel
13:57:54 <gnarface> alright, we'll install the backports kernel for you, first paste.debian.net your /etc/apt/sources.list file just so i can sanity check it before i tell you what to add
13:59:37 <devuanconsumer> ok lol
14:03:20 <devuanconsumer> https://paste.debian.net/1262859
14:03:22 <devuanconsumer> here it is
14:03:45 <gnarface> hmm, yikes, you got experimental in there, not sure how safe that is
14:03:55 <gnarface> but you already have backports it looks like so no changes should be necessary
14:04:01 <devuanconsumer> i'll remove it
14:04:13 <gnarface> just comment it out by adding a # to the start of the line
14:05:02 <devuanconsumer> ok sounds good
14:05:07 <devuanconsumer> now what do i do next
14:06:37 <gnarface> alright, try this, but before you say "Y" just paste here in channel what it says it's gonna install first: apt-get update && apt-get -t chimaera-backports --no-install-recommends install linux-image-amd64 firmware-amd-graphics
14:06:50 <gnarface> i wanna make sure it's gonna get the right thing
14:09:59 <gnarface> (we might have to actually pick a kernel by name specifically, that "linux-image-amd64" is just a meta-package, and i'm not sure it's defined for backports)
14:11:23 <gnarface> devuanconsumer: ^
14:13:26 <devuanconsumer> it just says
14:13:32 <devuanconsumer> the following packages will be upgraded
14:13:36 <devuanconsumer> linux-image-amd64
14:13:53 <devuanconsumer> can i go into synaptic and install it there?
14:14:14 <gnarface> i am not sure, i don't use synaptic... does it have a way for you to see backports packages ?
14:14:26 <devuanconsumer> i can see linux-images there
14:14:33 <gnarface> need to know which versions
14:14:41 <devuanconsumer> which version must i install?
14:14:53 <gnarface> i don't know specifically but if you tell me the highest version shown i'll know if it's enough
14:15:16 <gnarface> stock is 5.10 and the backports one should be significantly higher than .10
14:15:30 <gnarface> but you need to make sure you have the backports version of firmware-amd-graphics to match
14:18:17 <devuanconsumer> oh ok
14:19:07 <devuanconsumer> so there are 5.18
14:19:08 <devuanconsumer> 5.19
14:19:11 <devuanconsumer> and 6.0
14:19:14 <devuanconsumer> which should i install?
14:19:17 <devuanconsumer> 5.19?
14:19:32 <gnarface> here, from the command line this search should work: apt-cache -t chimaera-backports search ^linux-image
14:19:46 <gnarface> i'm not sure if you're also seeing experimental in there, make sure it's just the backports one
14:20:21 <gnarface> i think all 3 should be new enough but i don't want you to also introduce extra instability
14:21:26 <devuanconsumer> https://paste.debian.net/1262862
14:21:31 <devuanconsumer> here is the output
14:22:43 <gnarface> well looks like the latest is 6.0, so if you want that one use this: apt-get -t chimaera-backports --no-install-recommends install linux-image-6.0.0-0.deb11.2-amd64 firmware-amd-graphics
14:23:35 <gnarface> if you prefer 5.18 or 5.19 use linux-image-5.18.0-0.deb11.4-amd64 or linux-image-5.19.0-0.deb11.2-amd64 in place of the 6.0 one
14:23:43 <gnarface> ignore the rest of them, they're for other purposes
14:24:15 <gnarface> this change will require a reboot
14:24:30 <gnarface> but don't put the xorg.conf back on the first try, make sure it even boots first
14:24:48 <devuanconsumer> yeah so it looks like thats the one i have installed
14:25:07 <gnarface> you already had 6.0 installed?? what does "uname -a" say?
14:25:16 <devuanconsumer> i just booted into the 5.10 because with the firmware-amd-graphics it didn't boot
14:25:26 <devuanconsumer> after i added your xorg.conf
14:26:04 <gnarface> well keep in mind that if you tried to use the stable firmware-amd-graphics version with the backports kernel it might not have worked
14:26:15 <devuanconsumer> ah
14:26:19 <devuanconsumer> so i should uninstall it
14:26:27 <devuanconsumer> and then try it with your xorg.conf then
14:26:34 <devuanconsumer> i think i tried that already and it didn't work lol
14:26:36 <devuanconsumer> let me try again
14:26:45 <devuanconsumer> i'll uninstall the firmware-amd-graphics
14:26:46 <gnarface> well you should install the backports version of firmware-amd-graphics
14:26:51 <gnarface> it won't work without it either
14:27:07 <devuanconsumer> ok do i have to boot into the new kernel and do it like that?
14:27:12 <devuanconsumer> in synaptic?
14:27:24 <gnarface> it might seem to work by falling back on a more generic driver
14:27:36 <gnarface> won't matter if you do it with 1 or 2 reboots, give it a try
14:27:49 <gnarface> how new is this hardware exactly?
14:28:48 <devuanconsumer> the motherboard is from last month
14:28:58 <devuanconsumer> gpu ryzen 7950x is from september 2022
14:29:07 <devuanconsumer> apu*
14:33:49 <gnarface> devuanconsumer: lol i pushed the wrong button and accidentally shut my computer down, if you responded i missed it sorry
14:37:47 <hagbard> [20:28:48] <devuanconsumer> the motherboard is from last month
14:37:47 <hagbard> [20:28:58] <devuanconsumer> gpu ryzen 7950x is from september 2022
14:37:47 <hagbard> [20:29:07] <devuanconsumer> apu*
14:38:03 <gnarface> wow i wonder if even the 6.0 kernel in backports isn't new enough?
14:38:23 <gnarface> (thanks hagbard)
14:38:50 <devuanconsumer> well the backports
14:38:54 <devuanconsumer> did enable the cpu temps
14:39:02 <devuanconsumer> that were available with 5.10
14:39:04 <devuanconsumer> so thats a plus
14:39:18 <devuanconsumer> so i installed the amd firmware and it still didn't boot
14:39:24 <devuanconsumer> the latest is 2021
14:39:35 <devuanconsumer> so i had to login with the old kernel
14:39:45 <devuanconsumer> im going to just try to install the mesa libraries you have
14:39:56 <devuanconsumer> and try it with the old kernel 5.10
14:40:37 <gnarface> well do try with all those libraries but it's possible that you're gonna need an even newer kernel or firmware than what's in the repos, you're gonna have to consult some forums or mailing lists about that... this should be a known quantity just not one i know off the top of my head
14:40:47 <gnarface> i'm totally jealous of your gear though
14:41:13 <gnarface> with the generic modesetting driver you should be fine you just won't get optimal performance
14:41:33 <gnarface> they'll probably have an update out in a month or two
14:42:10 <gnarface> if you're into building kernels maybe there's source you can compile to make it work but that's gonna take more time than i have at the moment to walk you through that
14:42:33 <gnarface> sorry we didn't get it working though, i was hoping it'd be easy
14:42:51 <gnarface> there's nothing like seeing the desktop come up at full resolution for the first time on new hardware
14:48:11 <devuanconsumer> thanks gnarface
14:48:15 <devuanconsumer> i'm happy with the temps for now!
14:48:19 <devuanconsumer> thanks for helping me out!
14:49:10 <gnarface> no problem, let us know if you figure out the rest of it
14:53:41 <devuanconsumer> how did you get newer versions of the mesa files
14:53:49 <devuanconsumer> i dont see the same versions in synaptic package manager
14:53:51 <devuanconsumer> gnarface
14:55:22 <gnarface> devuanconsumer: oh, i'm on ceres (unstable) and i wouldn't recommend it but there's always the possibility it has something even newer than backports that might help you, it's just that usually even unstable is about 6 months behind reality and your hardware is so very new
2022-12-04
next