External display brightness becomes dim - Ubuntu 22.04 LTS [closed] - brightness

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 days ago.
Improve this question
System configuration:
Dell XPS 13 9310 2-in-1 laptop
Intel i7 11th Gen
Mesa Intel XE Graphics (TGL GT2)
Ubuntu 22.04 LTS 64 bit
Gnome version 42.5
Wayland windowing system
External displays used:
Dell S2817Q (4k)
HP 2509M
HDMI to USB-C Adapter used:
Mokin MUC0501B
I used HP 2509M for around 3-4 months and suddenly one day, the external display brightness just dimmed. I had not changed any brightness settings at all, neither on the laptop nor on the external display itself. Then I switched to the Dell display and after roughly the same amount of time, I am facing the same issue with this display.
I tried upgrading the display drivers, and also tried the xrandr command, but to no effect.
| xrandr -q |grep " connected"
XWAYLAND12 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 620mm x 340mm
| xrandr --output XWAYLAND12 --brightness 0.9

Related

OutOfMemoryError: CUDA out of memory [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 19 hours ago.
Improve this question
Running webui user batch file for stable diffusion always gives me the error message,
"OutOfMemoryError: CUDA out of memory. Tried to allocate 30.00 MiB (GPU 0; 2.00 GiB total capacity; 1.41 GiB already allocated; 19.18 MiB free; 1.47 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation. See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF"
This happens seemingly after everything has installed, so it takes quite a while to reach this point
Is this an issue I can fix or is the message trying to tell me that my PC spec isn't good enough. I'm new to this so I couldn't find any other "OutOfMemory" errors and i'm not sure how i can fix this.
This happens seemingly after everything has installed, so it takes quite a while to reach this point
Is this an issue I can fix or is the message trying to tell me that my PC spec isn't good enough. I'm new to this so I couldn't find any other "OutOfMemory" errors and i'm not sure how i can fix this.
GeForce GT 710
8GB Installed RAM
Intel(R) Core(TM) i7-2600 CPU # 3.40GHz 3.40 GHz

Ubuntu 22.04 updated failed [closed]

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 days ago.
Improve this question
I ran software updater last night, and it indicated that it completed normally and asked me to reboot. I assume that is was updating the kernel from 5.15.0-58-generic to 5.15.0-60-generic. On reboot, I received a bunch of messages ending with "kernel panic: No working init found." Using the advanced boot options, I found that .58 version was available. It indicated major disk problems and said to run fsck, which I did. I pressed "y" about a hundred times, and then .58 booted normally while .60 still produces a kernel panic. I then saved all my personal files. Right now, .58 seems to be running normally, and Software Updater runs with no problems.
I want to avoid reloading the OS, as I have custom WiFi and printer software that requires extra effort, as well as Virtual Box. And yes, the have been running happily through many updates. What are my options?

pxe booting http retrieval failures [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am attempting to pxe chain boot with http download. The problem I am having is the file retrieval always just stops on one of the random files below, at some random % complete. Usually it is the boot.wim, but I assume this is only because it is the largest. It has stopped on a simple font file as well though.
What could be causing this sporadic download behavior?
If I attempt a windows download off the samba share where those files are, the download is 1-2 secs. If I wget it from a nix host its about the same. Only when pxe is attempting to retrieve them does it seem to have an issue. I am fairly new to all this so hopefully I am giving good info. Samba server is running via apache.
I have tried numerous builds of kernel and boot.wim. Frankly, Im at a loss.
<%#
kind: PXELinux
name: Windows PXELinux
oses:
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
%>
DEFAULT linux
LABEL linux
KERNEL ipxe.lkrn
APPEND dhcp && chain <%= foreman_url('iPXE') %>
IPAPPEND 2
the chain then goes to:
#!ipxe
kernel http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/wimboot gui
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segmono_boot.ttf segmono_boot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/fonts/wgl4_boot.ttf wgl4_boot.ttf
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/bootmgr bootmgr.exe
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/BCD BCD
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot/boot.sdi boot.sdi
initrd http://puppet.lab.beer.town:717/sources/Microsoft/Windows/6.3/../boot/boot.wim boot.wim
imgstat
boot
Edit 1:
here is a screenshot showing the connection just freezing. all the established # 0, are the files that worked fine. the one stuck here is the boot wim (this time)
Issue here was the ipxe version on the server was like 3 years old. We git cloned it, and remade(make) the ipxe.lkrn. Files download just fine now.

Hyper V: Network Adapter Drivers [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
It seems I need to use legacy adapter drivers to get network connections with older version of windows and fedora (fedora 14 and windows xp), but with the newer versions I can use regular network adapters. Is there a way I can install the correct drivers needed for the regular network adapters to connect on the older guest OS's or are the drivers needed to connect incompatible windows xp and fedora 14?
Hyper-V has two kinds of NICs: emulated and synthetic. Emulated corresponds to what your refer to as 'legacy'. Synthetic corresponds to what you call a 'regular network adapter'.
To operate a synthetic NIC, the guest OS needs extra drivers. These are called Integration Services
AFAIK, Hyper-V ships with drivers for WindowsXP. They come in the form of an ISO that you can add to attach to the VM's DVD drive. Under the Hyper-V manager, connect to the VM (select the VM, then use Action -> Connect...), and in the window that pops use Action -> Insert Integration Services Setup Disk. You install the drivers from inside the Guest O/S.
For Linux OS's, you should download Linux Integration Services 3.4, which is the latest at the time of writing. Unfortunately, only CentOS and RHEL are explicitly supported. You can try installing the RPMs that come with Linux Integration Services, but its unclear whether they will work properly.
Good luck!
Update:
Hyper-V drivers have been added to the linux kernel. I posted details on how to determine if they are available with your distro on my blog.

Serial / Com Port monitor for Windows x64 [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
Can anyone recommend any good Com port monitor tools, like Portmon, which also work on Windows x64? Ideally something open source / freeware would be good.
Old question, but very relevant. While serial ports may be gone from consumer devices these days, it is still very much used in industrial hardware, point of sale hardware, radios, etc. In my case I was trying to capture a communications session from a configuration software tool for some hardware equipment.
In the end I found a commercial app from Eltima Software called Serial Port Monitor which did the trick for me on Windows 7 x64.
UPDATE in 2020: This very old question was relevant in 2010, but is now obsolete. There are plenty of open source serial monitor tools nowadays, notably the Arduino serial monitor tool, just to name one. This question can probably be deleted as it is no longer 'a problem.'
My original answer from 2010: The only one I have found for x64 is "Advanced Serial Port Monitor," which is really quite good. Not free, priced at $60 USD for a single user license. There is a 15-day trial. Honestly, I've been hoping (for quite a while now) that Mark R. would release a 64-bit version of portmon.

Resources