Hi guys! Hope this is the appropriate place to ask this question, but here it goes.

I have a Dell Inspiron 7520 laptop with integrated Intel and ATI graphics.

Recently I've installed Debian 12 on it, using Plasma.

Everything is fine and dandy, but there's a problem; when the system comes back from sleep, or I boot up the PC with the lid closed down, the screen never comes back. The system is running, but there is no screen.

Also, it's not just a blank screen, it does not get power, no backlight, no image on the screen if I shine a flashlight onto it and look hard.

Interrestingly, if I switch sessions to any ttys, the screen comes back and the terminal session displays fine. If I Alt+F7 back to the graphical session, the screen turns off again.

In theory, every graphics driver should be installed, I have non-free-firmware in my sources.list, all the packages that the Debian documentation mentions are installed.

Don't know, if relevant, but same on both X11 and Wayland.

Any ideas?

Thanks, guys :)

Some specs of the machine:

• CPU: Intel Core i7 (3rd Gen) 3612QM / 2.1 GHz
• GPU: Intel HD Graphics 4000 + AMD Radeon HD 7730M (switchable*)
• RAM: 16GB**

*: Not sure this switchable thingamajig works, tho. Haven't really tested, the only purpose of this machine is to start OBS and begin outputting video on NDI.

**: Though 16GB is not really supported on paper I guess and had some really funky issues before, not sure what was the real purpose, the system is rock solid since the last few OS installs.

Hello guys!

I'm encountering some strange behaviour with audio controls and volumes, nothing extreme serious, just moderate annoyance source, so I thought maybe you can help me sort this one out! Also I hope this is the right community for this...

(intro)

The thing is, I'm running Debian Bookworm, with Plasma and I have a rather strange audio setup. It has its legacy reasons, but I use a sound card (CMI8738/CMI8768, it has 5.1 output), and as for the speakers, I've got a pair of active 2.0 speakers and an active subwoofer (which was a part of a 2.1 system, but now I just use only the woofer). These are connected separately to the card; the stereo pair goes to the green output jack (front) and the subwoofer goes to another, which I think is the center+woofer output.

For some reason, the center and woofer was swapped on my card, or the subwoofer was hooked to the other channel, no idea, but I was managed to change them in pulsaudio's config /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf and modifying [Mapping analog-surround-*], changing the order of lfe and front-center in channel-map.

Then I noticed I can't really control the woofer, it worked, the setup was working, but not in the way I wanted to. The goal was to make the system actually control the outputs as intended and think about it as a 2.1. Amongst the profiles, there were no 2.1 option, only stereo, quadrophonic, 5.1 and 7.1.

By adding this line to ~/.config/pulse/default.pa...

load-module module-combine channels=3 channel_map=front-left,front-right,lfe

...and also editing ~/.config/pulse/daemon.conf by adding these to it (tho honestly I don't really remember, why)...

remixing-produce-lfe = yes
remixing-consume-lfe = yes
lfe-crossover-freq = 120
enable-remixing = yes

...I was managed to create a virtual output that behaves actually like 2.1. I can control both left and right channels and also the woofer on its own. Neat!

(the problem)

Now I have two volume controls. One for the "real" output - the 5.1 profile and the virtual one, the 2.1.

In Plasma toolbar, changing the volume with the scroll wheel is unpredictable, or, at least, I haven't really figured out how it works at the moment; sometimes it controls the real output, sometimes the virtual. On my left screen, it usually controls the real, on the right, most of the times it controls the virtual. But it just changed at the moment as I tried out, typing this post. Now both of them controls the real one.

The goal would be to have the real output constantly on 100%, and every volume controlling action should be take place on the virtual output.

Also, another strange thing is that even tho it looks like everything is fine and dandy, the overall output is low. When this happens, usually on the real output the left, right and woofer channels themselves are changed to lower (probably a previous state of the virtual output) volumes.

This all seems pretty random and unpredictable. If it works, it's awesome, and problems doesn't occur for days, but sometimes they do, and I have no idea why.

Any ideas?

(tl;dr)

I'd like to know why my volume controls (scroll wheel, volume keys) have effect on seemingly random outputs, and why do the volume of each channel that is present in my virtual output get change ON the physical setup (so the left, right and subwoofer sliders in the 5.1 output) persistently.

Thanks!

I'm still blown away by this track; it's just amazing IMO

Not sure if it's NSFW tho...

Hi all. Tho I have this problem a long time, I try to ask here too.

When I use PicoProbe for debug my code with Visual Studio Code (or Codium), can't get serial monitor working on the target Pico.

I have hooked up everything correctly, the probe's Rx/Tx GPIOs are connected to the target's UART0 Tx/Rx correctly (checked it, Tx-Rx and Rx-Tx, swapped it, no data at all. Tried to touch the wires to random spots, garbage appeared on the serial monitor, so the probe is probably listening)

Using USB as UART, connected directly to the target device does give me serial output, but through the probe and with UART, absolutely nothing.

I used the 'hello_serial' example project, built it with Codium (or VSCode), using the same plugins the pico_installer would setup. (MS CMake Tools, MS C++ tools and Cortex debug).

Debugging with openocd, or just running the built firmware on it's own and listening to it with the probe has the same result: nothing.

Same on Windows, same on Linux.

Anyone has any idea? I can program the Picos this way, but I really need serial for debugging. I could use two USB cables, but soonly enough that won't work.

Am I missing something? I did lots of search, but this feature should just work.

edit: fixed some typos

by Tim Follin

Ron Swanson takes a trip to City 17.