[gentoo-user] QEMU -nographic Option with OVMF
Hi, I decided to bite the bullet yesterday and switch from clunky, and generally untoward, VirtualBox to QEMU/KVM for developing kernel modules. I have a working Gentoo VM with all the bells and whistles I need/want (UEFI booting, NIC passthrough, SSH forwarding, NFSv4 support, etc.), but it's running in an SDL window, which means the guest TTY will become confused and pretty much unusable whenever I change the window size. (Which is rather often since I use a tiling window manager.) Since I'll only be using the TTY, the '-nographic' option to QEMU seems appropriate, but this causes the initial bootloader screen (OVMF/EDK-II) and GRUB to hang on stdout (screenshot attached). Here's my QEMU invocation script: #!/bin/bash exec qemu-system-x86_64 \ -enable-kvm \ -cpu host \ -drive file=Gentoo-VM.img,if=virtio \ -nic user,hostfwd=tcp:127.0.0.1:-:22 \ -m 4G \ -smp 12 \ -name "Gentoo VM" \ -bios /usr/share/edk2-ovmf/OVMF_CODE.fd \ -nographic \ $@ I have to spawn another terminal to kill the QEMU process. I can make a bit of progress by telling the kernel to direct early messages to ttyS0, which does display the early bootup messages from Linux, but then hangs just before a login prompt would be shown (screenshot attached). console=tty0 console=ttyS0,9600n8 Again, I can't do anything other than a `pkill qemu` from elsewhere. Any ideas from someone more familiar with QEMU hosting Linux guests? I've only been using it for a day, most of which has been trying to fix this annoying behaviour. Cheers. -- Oliver Dixon suugaku.co.uk FD40 39CD FDEB E22D B265 6DFD A9C4 3889 4CA9 3AEC signature.asc Description: PGP signature
[gentoo-user] USB WiFi dongle for gentoo based AP
Does anyone have experience with USB WiFi dongles? - I have purchased a couple of ones with different chip sets and cant find a satisfactory one: ralink 2870: just usable, but well known problem with errors when stressed. (IoT power switches are resetting and powecycling equipment including computers when the connection dropped/reconnects due to errors/timeouts in my case) atheros (9k_htc): limited by linux driver to two VAP's, patches to add VAP's didnt work with later kernels (has been awhile, has this changed?) Realtek (various): messy and limited functionality in the linux driver support out of kernel, limited coverage in kernel, mostly cant seem to do VAP's at all. specs needed: Works with hostapd VAP/VLAN's - up to 8 VAP's, preferably more. Can handle a lot of (30 or so, mostly IoT ESP2866 and the like) WiFi clients 2.4 Mhz, G/N standard USB3 preferred but optional BillK
[gentoo-user] Re: openrc-run for containers
Hi,
I've got the integration working how I imagined. It is using s6-svscan to
manage the containers, hopefully not abusing something. General idea is to
have supervision control over containers, ie to allow start up in a given
runlevel, have the ability to manage dependency start between given
containers and start/stop using openrc (referenced
https://wiki.gentoo.org/wiki/S6).
Assuming containers are already running, ie given instance of whoami
container:
*docker run -p 80:80 -d -it --name whoami traefik/whoami*
The "run" script, /var/svc.d/whoami/run:
#!/bin/execlineb -P
exec docker start -a whoami
The "finish" script, /var/svc.d/whoami/finish
*#!/bin/execlineb -Ps6-permafailon 60 1 2 exit*
The init.d, conf.d. Cat /etc/conf.d/container.whoami:
*INSTANCE=whoami*
Cat /etc/init.d/container:
*#!/sbin/openrc-rundescription="A supervised test service with a
logger"supervisor=s6s6_service_path=/run/openrc/s6-scan/${INSTANCE}depend()
{ need s6-svscan}stop_pre() { docker stop ${INSTANCE}}*
Finally, [openrc-run, ln -s /etc/init.d/container
/etc/init.d/container.whoami] /etc/initd.d/container.whoami start, stop
work as expected (docker ps |grep whoami does not return anything, after
running "/etc/init.d/container.whoami stop"):
List containers
root@ # *docker ps |grep whoami*
68bd2ed585ed traefik/whoami
"/whoami"35 minutes ago Up 34 minutes
0.0.0.0:80->80/tcp whoami
root@ # *./container.whoami stop*
container.whoami |whoami
container.whoami | * Stopping container.whoami ...
[ ok ]
root@ # *docker ps |grep whoami*
root@ #* ./container.whoami start*
container.whoami | * Starting container.whoami ...
[ ok ]
root@ # docker ps |grep whoami
68bd2ed585ed traefik/whoami
"/whoami"35 minutes ago Up 3 seconds
0.0.0.0:80->80/tcp whoami
root@ # *ps xf -o pid,ppid,pgrp,euser,args*
PID PPID PGRP EUSERCOMMAND
21056 1 21056 root /bin/s6-svscan /run/openrc/s6-scan
21058 21056 21056 root \_ s6-supervise whoami/log
21059 21056 21056 root \_ s6-supervise whoami
27584 21059 27584 root | \_ docker start -a whoami
Similar to above, using s6-svstat:
root@ # *s6-svstat /run/openrc/s6-scan/whoami*
up (pid 27584) 752 seconds
root@ # *./container.whoami stop*
container.whoami |whoami
container.whoami | * Stopping container.whoami ...
[ ok ]
root@ #* s6-svstat /run/openrc/s6-scan/whoami*
down (exitcode 2) 1 seconds, normally up, ready 1 seconds
root@ #* ./container.whoami start*
container.whoami | * Starting container.whoami ...
[ ok ]
root@h003 /e/init.d # s6-svstat /run/openrc/s6-scan/whoami
up (pid 6722) 3 seconds
The goal of all this has been to incorporate containers into
/etc/runlevels. I am not sure if there is a better way, have I missed
something by not using s6-overlay or the like? I am not familiar enough to
know.
An outstanding issue, in the s6 run script, i would like to parametrize the
instance name, I don't know how to do it, as it is currently hard coded:
The "run" script, /var/svc.d/whoami/run:
#!/bin/execlineb -P
exec docker start -a *whoami*
But once that is done, then all running containers could be incorporated by
updating the conf.d for INSTANCE name, templating a /var/svc.d/
folder and linking to /etc/init.d/container, ie:
/etc/init.d/container.whoami
/etc/init.d/container.cadvisor
/etc/init.d/container.traefik
[put under control of s6]
/etc/runlevels/20/s6-svscan
...
This is kind of asymmetric, ie container start is in s6, whereas stop
[docker] is in openrc, but I am not seeing a different way, the goal is to
have robust services running. When system boots, s6-scan will start all the
containers automatically, but then further operations, ie for things like
manual failover etc, is possible using standard platform openrc -
effectively docker - start/stop commands.
kind regards
On Thu, May 13, 2021 at 5:17 AM Damo wrote:
> Hi,
>
> I've been running docker containers for a while, where I pass
> "--restart=always" into the run command, so the containers restart
> automatically after reboot. I want to have more control over the startup
> order of the containers, ie integrate into openrc start/stop and put into
> different runlevels.
>
> I've had mixed success so far. I would be interested if someone else has
> working solution. My runlevels look something like this:
>
> rl100
> container.registry
> rl90
> container.auth
> container.router
> boot
> ...
>
> FYI, i've found systemd is doing it nicely, where systemctl start/stop
> works as I would expect. I see a hardcoded dependency into the
> container PID in the unit file (podman in this case):
>
> [root@]# cat /usr/lib/systemd/system/container-libvirt-exporter.service
>
> #
>
> [Unit]
> Description=Podman container-libvirtd-exporter.service
> Documentation=man:podman-generate-systemd(1)
>
> [Service]
> Restart=always
> ExecStart=/usr/bin/podman start libvirtd-exporter
>
Re: [gentoo-user] Windows 10 Pro 64bit in Virtualbox
On Sunday, 23 May 2021 19:39:24 BST the...@sys-concept.com wrote: > Thank Michael for the update. It is handy. > When you are talking about "transparency" you mean inside Windows 10, isn't > it? Yes, under Settings > Personalization > Colors > Transparency Effects. > I've experimented with resizing Windows 10 32bit (currently installed) using > gparted and it went very well, no problems. I'm not sure with switching to > Windows 10 64bit will help or not. I've always run MSWindows 10 64bit, so I can't report on differences in performance, other than the obvious benefit in multitasking and hungry applications requiring more RAM than a 32bit will cope with. As far as I know switching from 32bit to 64bit involves reinstalling, so this would be the time to also allocate the virtual disk space you think you would need and allow another 15G to 20G on top for future upgrades. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Windows 10 Pro 64bit in Virtualbox
On 5/23/21 4:04 AM, Michael wrote: >> On Sat, May 22, 2021, 17:02 wrote: >>> Is anybody running Windows 10 Pro 64bit in Virtualbox? >>> Is it stable? >>> Is it easy to resize? > > I forgot to mention stability and resizing ... > > In one case after a major update the Win10 desktop became terribly unstable, > menus not showing up, everything on the desktop taking minutes to respond to > a > mouse click or keyboard press. Eventually I realised the transparency had > been enabled by the update and this was cause any desktop graphics to render > partially and with a lot of latency. Disabling transparency restored the > previous normal desktop behaviour. This was on a host with an old AMD-Radeon > APU. Other video cards and drivers may not have such a problem, but I > thought > it worth mentioning. > > Resizing the C:\ drive partition is straight forward, in most cases. You can > use 'VBoxManage modifyhd' in a terminal to increase the virtual disk size, or > the VBox GUI Virtual Media Manager tab. Then use the Windows Disk > Management, > or boot the VM with GParted and resize the OS partition & filesystem. > However, Windows 10 tends to create additional partitions as part of > installation, or subsequent major updates. These are called System Reserve > Partitions (SRP). Initially one is created at the start of the disk to > contain bitlocker, boot and Windows Restore data. After certain major > updates, or if the Windows 10 installation was an in situ upgrade from an > older Windows 7 installation, such an SRP can be placed after the C:\ drive. > In one case, changing an installed system from MBR to GPT/UEFI also created > an > ESP after the C:\ drive. It follows you won't be able to increase the size > of > the C:\ partition without moving any partitions following it out of the way > first, increasing C:\, then restoring the moved partitions. Since an > otherwise 5 minute disk & partition resizing exercise can develop into a > prolonged and pre-planned effort, you'd be better off sizing up the virtual > disk before you start installing MSWindows. > > Big upgrade releases every six months may require more temporary storage > space > to create a backup in case the upgrade fails. If enough space is not > available on the disk, the the OS will ask you to insert a USB drive to be > used during the upgrade. You can also create and attach a new virtual disk > for this purpose. > > Finally, there's the Windows 10 'Storage Spaces' replacing Dynamic Disks, if > you want to create a RAID in software. I understand you use it to add more > disks/partitions, like you would with a RAID, but I have never used this to > know what it can achieve in terms of resizing. Thank Michael for the update. It is handy. When you are talking about "transparency" you mean inside Windows 10, isn't it? I've experimented with resizing Windows 10 32bit (currently installed) using gparted and it went very well, no problems. I'm not sure with switching to Windows 10 64bit will help or not.
Re: [gentoo-user] Audio through second HDMI output on GPU?
On Sun, 23 May 2021 at 19:42, Mark Knecht wrote: > 1) instead of aplay -l please run aplay -L My aplay -L was more or less identical to Dale's on the HDMI part, except for going all the way to DEV 6. > 2) Also provide the output of > > cat /proc/asound/card2/codec#0 This was also more or less the same, probably simple because of the different models of GPU. In case any of the smaller differences are interesting to you, here's that output. # cat /proc/asound/card1/codec#0 Codec: Nvidia GPU 83 HDMI/DP Address: 0 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x10de0083 Subsystem Id: 0x104385aa Revision Id: 0x100100 No Modem Function Group found Default PCM: rates [0x0]: bits [0x0]: formats [0x0]: Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=0, o=0, i=0, unsolicited=0, wake=0 Node 0x04 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP Pincap 0x0994: OUT Detect HBR HDMI DP Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=01, enabled=1 Devices: 4 *Dev 00: PD = 1, ELDV = 1, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 01: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 02: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 03: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Connection: 4 0x0a* 0x0b 0x0c 0x0d Node 0x05 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP Pincap 0x0994: OUT Detect HBR HDMI DP Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=05, enabled=1 Devices: 4 *Dev 00: PD = 1, ELDV = 1, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 01: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 02: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 03: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Connection: 4 0x0a* 0x0b 0x0c 0x0d Node 0x06 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP Pincap 0x0994: OUT Detect HBR HDMI DP Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=09, enabled=1 Devices: 4 Dev 00: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 01: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 02: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] *Dev 03: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Connection: 4 0x0a* 0x0b 0x0c 0x0d Node 0x07 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP Pincap 0x0994: OUT Detect HBR HDMI DP Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=0d, enabled=1 Devices: 4 Dev 00: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 01: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 02: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] *Dev 03: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Connection: 4 0x0a* 0x0b 0x0c 0x0d Node 0x08 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP Pincap 0x0994: OUT Detect HBR HDMI DP Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Devices: 4 *Dev 00: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 01: PD = 0, ELDV = 0, IA = 0, Connections [ 0x00* 0xb758 0x8884 0x ] Dev 02: PD = 0, ELDV = 0, IA = 0, Connections [ 0x00* 0xb758 0x8884 0x ] Dev 03: PD = 0, ELDV = 0, IA = 0, Connections [ 0x00* 0xb758 0x8884 0x ] Connection: 4 0x0a* 0x0b 0x0c 0x0d Node 0x09 [Pin Complex] wcaps 0x407381: 8-Channels Digital CP Pincap 0x0994: OUT Detect HBR HDMI DP Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Devices: 4 *Dev 00: PD = 0, ELDV = 0, IA = 0, Connections [ 0x0a* 0x0b 0x0c 0x0d ] Dev 01: PD = 0, ELDV = 0, IA = 0, Connections [ 0x00* 0xb758 0x8884 0x ] Dev 02: PD = 0, ELDV = 0, IA = 0, Connections [ 0x00* 0xb758 0x8884 0x ] Dev 03: PD = 0, ELDV = 0, IA = 0, Connections [ 0x00* 0xb758 0x8884 0x ] Connection: 4 0x0a* 0x0b 0x0c 0x0d Node 0x0a [Audio Output] wcaps 0x62b1: 8-Channels Digital Stripe Converter: stream=5, channel=0 Digital: Enabled Digital category: 0x0 IEC Coding
Re: [gentoo-user] Audio through second HDMI output on GPU?
Mark Knecht wrote: > > Dale and Arve, > As I do home studio type recording using Linux I always find this > topic quite interesting but because of the more complicated setup of > my audio environment which makes use of a Hammerfall DSP card driving > the speaker but utilizes the internal Intel sound card for general > audio, along with cables outside to hook the two together, I'm just > not sure what I see on my system is very helpful to you two. > Nonetheless I do have an older NVidia GPU and would like to understand > what's going on with all of this. > > A couple of requests: > > 1) instead of aplay -l please run aplay -L > > 2) Also provide the output of > > cat /proc/asound/card2/codec#0 > > Note: Your card number may well be different than mine > card0=Hammerfall, card1=Internal Intel sound, card2=NVidia > > Also, there is an old (2014) document online from NVidia that > provides a lot of info on Alsa device naming and how NVidia GPUs > handle audio. It's one of the better ones I've found online making the > dangerous assumption that it hasn't all changed. There's lots of info > in this document about system config edits for non-pulseaudio users > and things that might possibly be of interest to Gentoo users with > configuration more like Arve's, but again, that's a guess on my part. > > https://download.nvidia.com/XFree86/gpu-hdmi-audio-document/ > > No rush on any of this. > > Thanks, > Mark While what I have is working, I wouldn't mind having info in case it stops working or I need to change my video player. I don't have a card2 but I do have a card0 and card1. I'm including both since I'm not sure what is what. Plus it may help someone else. Since I snipped previous, this is the setting for my TV. alsa:device=hw=1.7 root@fireball / # aplay -L null Discard all samples (playback) or generate zero samples (capture) default:CARD=SB HDA ATI SB, VT2020 Analog Default Audio Device sysdefault:CARD=SB HDA ATI SB, VT2020 Analog Default Audio Device front:CARD=SB,DEV=0 HDA ATI SB, VT2020 Analog Front output / input surround21:CARD=SB,DEV=0 HDA ATI SB, VT2020 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=SB,DEV=0 HDA ATI SB, VT2020 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=SB,DEV=0 HDA ATI SB, VT2020 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=SB,DEV=0 HDA ATI SB, VT2020 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=SB,DEV=0 HDA ATI SB, VT2020 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=SB,DEV=0 HDA ATI SB, VT2020 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=SB,DEV=0 HDA ATI SB, VT2020 Digital IEC958 (S/PDIF) Digital Audio Output hdmi:CARD=NVidia,DEV=0 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=1 HDA NVidia, HDMI 1 HDMI Audio Output hdmi:CARD=NVidia,DEV=2 HDA NVidia, HDMI 2 HDMI Audio Output hdmi:CARD=NVidia,DEV=3 HDA NVidia, HDMI 3 HDMI Audio Output hdmi:CARD=NVidia,DEV=4 HDA NVidia, HDMI 4 HDMI Audio Output hdmi:CARD=NVidia,DEV=5 HDA NVidia, HDMI 5 HDMI Audio Output root@fireball / # cat /proc/asound/card0/codec#0 Codec: VIA VT2020 Address: 0 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x11060441 Subsystem Id: 0x1458a014 Revision Id: 0x100100 No Modem Function Group found Default PCM: rates [0x0]: bits [0x0]: formats [0x0]: Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 GPIO: io=1, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x08 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Front Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="VT2020 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0 Amp-Out vals: [0x2a 0x2a] Converter: stream=5, channel=0 PCM: rates [0x5e0]: 44100 48000 88200 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 Power: setting=D0, actual=D0 Node 0x09 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Surround Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=5, channel=0 PCM: rates [0x5e0]: 44100 48000 88200 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 Power: setting=D0, actual=D0 Node 0x0a [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Center Playback Volume", index=0, device=0 ControlAmp: chs=1, dir=Out, idx=0, ofs=0 Control: name="LFE Playback Volume", index=0, device=0 ControlAmp:
Re: [gentoo-user] Audio through second HDMI output on GPU?
On Sun, May 23, 2021 at 10:09 AM Dale wrote: > > Arve Barsnes wrote: > > On Sun, 23 May 2021 at 18:22, Dale wrote: > >> If you ever figure it out, please post what did it. I watch TV from my > >> puter too. Right now, I tell Smplayer to send audio to the TV by giving > >> it the device name like you did. Thing is, none of the entries in the > >> drop down menu in settings works. Odd but it is what it is. > > Might be worth checking if the smplayer front-end is messing something > > up, by going straight through mpv. My last steps for playing video > > through the TV, with the audio going there as well: > > > > Get a list of all the audio devices on your system. > > $ mpv --audio-device=help > > > > Use the correct device in your video command. > > DISPLAY=:0.1 mpv --audio-device=alsa/hdmi:CARD=NVidia,DEV=0 -fs video.mkv > > > > Also check what Mark mentioned about muted channels on the output card > > through alsamixer. > > > > Regards, > > Arve > > > > > > > When I set mine up, I just set output driver to user defined and entered > alsa:device=hw=1.7 in settings. I only want Smplayer to output to the > TV. Everything else goes to the speakers hooked to the computer itself. > > The day may come when I use something other than Smplayer to watch TV > tho. If, or when, that day comes I'll have to figure out how to get the > audio to work with it. Right now, I'm still able to use the old gnome > player still. It's going to die one day tho since it is no longer > maintained. > > I do find these audio topics interesting tho. It seems it should be > easy to send sound to any place it can go but it isn't easy to do for > real. It seems it is a problem for a lot of people doing what I think > is at least somewhat common. > > Either way, glad you got it working. It took me days to figure out mine > too. > > Dale > > :-) :-) Dale and Arve, As I do home studio type recording using Linux I always find this topic quite interesting but because of the more complicated setup of my audio environment which makes use of a Hammerfall DSP card driving the speaker but utilizes the internal Intel sound card for general audio, along with cables outside to hook the two together, I'm just not sure what I see on my system is very helpful to you two. Nonetheless I do have an older NVidia GPU and would like to understand what's going on with all of this. A couple of requests: 1) instead of aplay -l please run aplay -L 2) Also provide the output of cat /proc/asound/card2/codec#0 Note: Your card number may well be different than mine card0=Hammerfall, card1=Internal Intel sound, card2=NVidia Also, there is an old (2014) document online from NVidia that provides a lot of info on Alsa device naming and how NVidia GPUs handle audio. It's one of the better ones I've found online making the dangerous assumption that it hasn't all changed. There's lots of info in this document about system config edits for non-pulseaudio users and things that might possibly be of interest to Gentoo users with configuration more like Arve's, but again, that's a guess on my part. https://download.nvidia.com/XFree86/gpu-hdmi-audio-document/ No rush on any of this. Thanks, Mark
Re: [gentoo-user] Audio through second HDMI output on GPU?
Arve Barsnes wrote: > On Sun, 23 May 2021 at 18:22, Dale wrote: >> If you ever figure it out, please post what did it. I watch TV from my >> puter too. Right now, I tell Smplayer to send audio to the TV by giving >> it the device name like you did. Thing is, none of the entries in the >> drop down menu in settings works. Odd but it is what it is. > Might be worth checking if the smplayer front-end is messing something > up, by going straight through mpv. My last steps for playing video > through the TV, with the audio going there as well: > > Get a list of all the audio devices on your system. > $ mpv --audio-device=help > > Use the correct device in your video command. > DISPLAY=:0.1 mpv --audio-device=alsa/hdmi:CARD=NVidia,DEV=0 -fs video.mkv > > Also check what Mark mentioned about muted channels on the output card > through alsamixer. > > Regards, > Arve > > When I set mine up, I just set output driver to user defined and entered alsa:device=hw=1.7 in settings. I only want Smplayer to output to the TV. Everything else goes to the speakers hooked to the computer itself. The day may come when I use something other than Smplayer to watch TV tho. If, or when, that day comes I'll have to figure out how to get the audio to work with it. Right now, I'm still able to use the old gnome player still. It's going to die one day tho since it is no longer maintained. I do find these audio topics interesting tho. It seems it should be easy to send sound to any place it can go but it isn't easy to do for real. It seems it is a problem for a lot of people doing what I think is at least somewhat common. Either way, glad you got it working. It took me days to figure out mine too. Dale :-) :-)
Re: [gentoo-user] Audio through second HDMI output on GPU?
On Sun, 23 May 2021 at 18:22, Dale wrote: > If you ever figure it out, please post what did it. I watch TV from my > puter too. Right now, I tell Smplayer to send audio to the TV by giving > it the device name like you did. Thing is, none of the entries in the > drop down menu in settings works. Odd but it is what it is. Might be worth checking if the smplayer front-end is messing something up, by going straight through mpv. My last steps for playing video through the TV, with the audio going there as well: Get a list of all the audio devices on your system. $ mpv --audio-device=help Use the correct device in your video command. DISPLAY=:0.1 mpv --audio-device=alsa/hdmi:CARD=NVidia,DEV=0 -fs video.mkv Also check what Mark mentioned about muted channels on the output card through alsamixer. Regards, Arve
Re: [gentoo-user] Audio through second HDMI output on GPU?
Arve Barsnes wrote: > On Sun, 23 May 2021 at 16:14, Mark Knecht wrote: >> Well, good news no matter how it happened. >> >> Hopefully it still works after a reboot. I guess we'll find out. > Indeed. Might even have been a reboot that made it work, but at least > I know my system and my TV has the capabilities I wanted. > > Cheers for trying to help! > > Regards, > Arve > > If you ever figure it out, please post what did it. I watch TV from my puter too. Right now, I tell Smplayer to send audio to the TV by giving it the device name like you did. Thing is, none of the entries in the drop down menu in settings works. Odd but it is what it is. Dale :-) :-)
Re: [gentoo-user] Audio through second HDMI output on GPU?
On Sun, 23 May 2021 at 16:14, Mark Knecht wrote: > Well, good news no matter how it happened. > > Hopefully it still works after a reboot. I guess we'll find out. Indeed. Might even have been a reboot that made it work, but at least I know my system and my TV has the capabilities I wanted. Cheers for trying to help! Regards, Arve
Re: [gentoo-user] Audio through second HDMI output on GPU?
On Sun, May 23, 2021 at 5:47 AM Arve Barsnes wrote: > > On Sun, 23 May 2021 at 13:21, Arve Barsnes wrote: > > Eric's links were very interesting, and the pi people's solution > > seemed to be something simple, but their fix seems to also be in > > firmware, with a link to a giant, mostly binary, git commit. It made > > me think, though, if there was something in my kernel config that > > could be stopping the sound from getting through though, so that will > > be my next direction of inquiry. If this TV required something special > > in the pi firmware, maybe that is something I've managed to exclude > > from my own build. > > Welp, everything out the window, I have no idea what, if anything, > I've changed since I started this investigation. > > aplay -D plughw:1,3 sample.wav > > It works now! :D > > Cheers, > Arve Well, good news no matter how it happened. Hopefully it still works after a reboot. I guess we'll find out. Cheers, Mark
Re: [gentoo-user] Audio through second HDMI output on GPU?
On Sun, 23 May 2021 at 13:21, Arve Barsnes wrote: > Eric's links were very interesting, and the pi people's solution > seemed to be something simple, but their fix seems to also be in > firmware, with a link to a giant, mostly binary, git commit. It made > me think, though, if there was something in my kernel config that > could be stopping the sound from getting through though, so that will > be my next direction of inquiry. If this TV required something special > in the pi firmware, maybe that is something I've managed to exclude > from my own build. Welp, everything out the window, I have no idea what, if anything, I've changed since I started this investigation. aplay -D plughw:1,3 sample.wav It works now! :D Cheers, Arve
Re: [gentoo-user] Audio through second HDMI output on GPU?
On Sat, 22 May 2021 at 00:51, Mark Knecht wrote: > OK, so what does alsamixer tell you? On my system I hit F6, choose the card > and then F3 for Playback. I see the 7 channels. Hitting 'M' changes the mute > setting but all the volumes are at 0 and hitting '+' doesn't raise the > volume. It's been so long since I looked at spdif stuff that I don't remember > if spdif supports volume this way. Will research a bit. Yeah, I see exactly the same. The first one, I think, was muted originally, but I unmuted all of these when I originally started trying to figure this out, before my first mail to this list. I can't be 100% sure, but I think the first one was the only one that was muted. Output from amixer and aplay and others make me think that this first one, is the one 'aplay -l' marks as device 3, and as the TV. Unmuting didn't change anything though, and when I went to check again now, all 7 channels are unmuted. > The problem right now is we don't know if the channel is transmitting at a > volume of 0, not transmitting at all, or possibly the TV is receiving audio > data but not accepting it due to format issues. Indeed. If I am indeed transmitting anything (at least aplay actually plays the sample file in real-time, so something is getting processed), how could I even figure out what the TV is doing about it. I'm starting to collect good reasons for replacing this aging 10+ year old TV :) > I see a response from eric so I would certainly look into what he's pointing > you toward. Eric's links were very interesting, and the pi people's solution seemed to be something simple, but their fix seems to also be in firmware, with a link to a giant, mostly binary, git commit. It made me think, though, if there was something in my kernel config that could be stopping the sound from getting through though, so that will be my next direction of inquiry. If this TV required something special in the pi firmware, maybe that is something I've managed to exclude from my own build. Cheers, Arve
Re: [gentoo-user] Windows 10 Pro 64bit in Virtualbox
> On Sat, May 22, 2021, 17:02 wrote: > > Is anybody running Windows 10 Pro 64bit in Virtualbox? > > Is it stable? > > Is it easy to resize? I forgot to mention stability and resizing ... In one case after a major update the Win10 desktop became terribly unstable, menus not showing up, everything on the desktop taking minutes to respond to a mouse click or keyboard press. Eventually I realised the transparency had been enabled by the update and this was cause any desktop graphics to render partially and with a lot of latency. Disabling transparency restored the previous normal desktop behaviour. This was on a host with an old AMD-Radeon APU. Other video cards and drivers may not have such a problem, but I thought it worth mentioning. Resizing the C:\ drive partition is straight forward, in most cases. You can use 'VBoxManage modifyhd' in a terminal to increase the virtual disk size, or the VBox GUI Virtual Media Manager tab. Then use the Windows Disk Management, or boot the VM with GParted and resize the OS partition & filesystem. However, Windows 10 tends to create additional partitions as part of installation, or subsequent major updates. These are called System Reserve Partitions (SRP). Initially one is created at the start of the disk to contain bitlocker, boot and Windows Restore data. After certain major updates, or if the Windows 10 installation was an in situ upgrade from an older Windows 7 installation, such an SRP can be placed after the C:\ drive. In one case, changing an installed system from MBR to GPT/UEFI also created an ESP after the C:\ drive. It follows you won't be able to increase the size of the C:\ partition without moving any partitions following it out of the way first, increasing C:\, then restoring the moved partitions. Since an otherwise 5 minute disk & partition resizing exercise can develop into a prolonged and pre-planned effort, you'd be better off sizing up the virtual disk before you start installing MSWindows. Big upgrade releases every six months may require more temporary storage space to create a backup in case the upgrade fails. If enough space is not available on the disk, the the OS will ask you to insert a USB drive to be used during the upgrade. You can also create and attach a new virtual disk for this purpose. Finally, there's the Windows 10 'Storage Spaces' replacing Dynamic Disks, if you want to create a RAID in software. I understand you use it to add more disks/partitions, like you would with a RAID, but I have never used this to know what it can achieve in terms of resizing. signature.asc Description: This is a digitally signed message part.
