Re: [CentOS] Centos 8 and logwatch
> I am trying to get logwatch working on CentOS 8. System is fully updated. > Usually install minimal version and then add only necessary with yum. > > On CentOS 7: install logwatch and get daily logwatch report on mail. > > On CentOS 8: install logwatch but no way to get mail. Looks like Postfix is no longer mandatory, I have to explicitly add it to my minimal kickstart whereas with 7, that was not the case. Check if you even have a local mta installed. jlc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum update security updates only
We utilize Spacewalk and the errata from https://cefs.steve-meier.de/ to
provide this function for CentOS.
Andrea
-Original Message-
From: CentOS On Behalf Of Jon Pruente
Sent: Friday, November 13, 2020 7:08 PM
To: CentOS mailing list
Subject: {EXTERNAL} Re: [CentOS] yum update security updates only
CAUTION: This email originated outside of BSWH; avoid action unless you know
the content is safe. Send suspicious emails as attachments to
badem...@bswhealth.org.
On Fri, Nov 13, 2020 at 6:02 PM Eric Chennells
wrote:
> Frank,
>
> Interesting thank you I didn't realize that. It used to be supported
> I believe, and there is a lot of out of date 3rd party documentation
> floating around google that suggests it does.
>
> Well it's just that many enterprises have policies which state that
> only security updates should be installed, which I suspect is exactly
> why that feature is no longer supported..
>
There are ways to get the metadata to do that, but it's still not officially
supported. And as for enterprises mandating only security updates, they
would/should pay for RHEL to get that kind of feature.
___
CentOS mailing list
CentOS@centos.org
https://urldefense.com/v3/__https://lists.centos.org/mailman/listinfo/centos__;!!JA_k2roV-A!XuXhHdKtZFfgqvwdbBq9PZb3K3TydTqyOHYfhFUGuM5eVBWP-eY3A7sFdZEJM8J5vg$
**
The information contained in this e-mail may be privileged and/or confidential,
and protected from disclosure, and no waiver of any attorney-client, work
product, or other privilege is intended. If you are the intended recipient,
further disclosures are prohibited without proper authorization. If you are not
the intended recipient (or have received this e-mail in error) please notify
the sender immediately and destroy this e-mail. Any unauthorized copying,
disclosure or distribution of the material in this e-mail is strictly forbidden
and possibly a violation of federal or state law and regulations. The sender
and Baylor Scott & White Health, and its affiliated entities, hereby expressly
reserve all privileges and confidentiality that might otherwise be waived as a
result of an erroneous or misdirected e-mail transmission. No employee or agent
is authorized to conclude any binding agreement on behalf of Baylor Scott &
White Health, or any affiliated entity, by e-mail without express written
confirmation by the CEO, the Senior Vice President of Supply Chain Services or
other duly authorized representative of Baylor Scott & White Health.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum update security updates only
On Fri, Nov 13, 2020 at 6:02 PM Eric Chennells wrote: > Frank, > > Interesting thank you I didn't realize that. It used to be supported I > believe, and there is a lot of out of date 3rd party documentation floating > around google that suggests it does. > > Well it's just that many enterprises have policies which state that only > security updates should be installed, which I suspect is exactly why that > feature is no longer supported.. > There are ways to get the metadata to do that, but it's still not officially supported. And as for enterprises mandating only security updates, they would/should pay for RHEL to get that kind of feature. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum update security updates only
On Nov 13, 2020, at 19:01, Eric Chennells wrote: > > Frank, > > Interesting thank you I didn't realize that. It used to be supported I > believe, and there is a lot of out of date 3rd party documentation floating > around google that suggests it does. > > Well it's just that many enterprises have policies which state that only > security updates should be installed, which I suspect is exactly why that > feature is no longer supported.. I don’t believe CentOS has ever supported it in any of the supported releases, although repos like EPEL do provide security metadata. RHEL supports the security flag to yum update, because they curate their repo metadata with that data, but it isn’t available to CentOS users. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum update security updates only
Frank, Interesting thank you I didn't realize that. It used to be supported I believe, and there is a lot of out of date 3rd party documentation floating around google that suggests it does. Well it's just that many enterprises have policies which state that only security updates should be installed, which I suspect is exactly why that feature is no longer supported.. Eric On Fri, Nov 13, 2020 at 3:55 PM Frank Cox wrote: > On Fri, 13 Nov 2020 15:52:08 -0800 > Eric Chennells wrote: > > > Does anyone know what's going on here? > > That is unsupported by Centos. So the short answer is, you can't do that. > > Any particular reason you can't just update your system fully? > > -- > Can we uninstall 2020 and install it again? This one has a virus. > MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum update security updates only
On Fri, 13 Nov 2020 15:52:08 -0800 Eric Chennells wrote: > Does anyone know what's going on here? That is unsupported by Centos. So the short answer is, you can't do that. Any particular reason you can't just update your system fully? -- Can we uninstall 2020 and install it again? This one has a virus. MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] yum update security updates only
Hello, I'm trying to do a yum update and only apply the security patches. I'm aware of yum update --security , however when I do that it fails to install any updates. I've tried this on a fresh 7.8.2003 (core) system, as well as the Centos 7 AMI on AWS, specifically ami-04a25c39dc7a8aebb and I get the same results. There are definitely security updates to apply. For each package which needs to be updated, it lists "" from updates removed (updateinfo). Does anyone know what's going on here? Thanks, Eric ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 and logwatch
Am 13.11.20 um 13:03 schrieb Blaž Bogataj: Hello I am trying to get logwatch working on CentOS 8. System is fully updated. Usually install minimal version and then add only necessary with yum. On CentOS 7: install logwatch and get daily logwatch report on mail. On CentOS 8: install logwatch but no way to get mail. Am I doing something wrong? Or miss something? /usr/sbin/sendmail installed? -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Logitech C922 webcam
On 11/13/2020 12:40 PM, H wrote: > On 10/02/2020 07:38 AM, H wrote: >> On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell >> wrote: >>> On 9/30/20 8:52 AM, H wrote: 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >>> Family USB 3.0 xHCI Controller >>> My system has these: >>> >>> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >>> Family USB xHCI (rev 05) >>> 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >>> Family USB EHCI #2 (rev 05) >>> 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >>> Family USB EHCI #1 (rev 05) >>> >>> lspci -s 00:14.0 -v >>> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >>> Family USB xHCI (rev 05) (prog-if 30 [XHCI]) >>> Subsystem: ASUSTeK Computer Inc. Device 201f >>> Flags: bus master, medium devsel, latency 0, IRQ 25 >>> Memory at dd60 (64-bit, non-prefetchable) [size=64K] >>> Capabilities: [70] Power Management version 2 >>> Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ >>> Kernel driver in use: xhci_hcd >>> Kernel modules: xhci_pci >>> >>> lspci -s 00:1a.0 -v >>> 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >>> Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI]) >>> Subsystem: ASUSTeK Computer Inc. Device 201f >>> Flags: bus master, medium devsel, latency 0, IRQ 16 >>> Memory at dd618000 (32-bit, non-prefetchable) [size=1K] >>> Capabilities: [50] Power Management version 2 >>> Capabilities: [58] Debug port: BAR=1 offset=00a0 >>> Capabilities: [98] PCI Advanced Features >>> Kernel driver in use: ehci-pci >>> Kernel modules: ehci_pci >>> >>> lspci -s 00:1d.0 -v >>> 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >>> Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI]) >>> Subsystem: ASUSTeK Computer Inc. Device 201f >>> Flags: bus master, medium devsel, latency 0, IRQ 23 >>> Memory at dd617000 (32-bit, non-prefetchable) [size=1K] >>> Capabilities: [50] Power Management version 2 >>> Capabilities: [58] Debug port: BAR=1 offset=00a0 >>> Capabilities: [98] PCI Advanced Features >>> Kernel driver in use: ehci-pci >>> Kernel modules: ehci_pci >>> >>> These are my kernel modules: >>> >>> lsmod | grep usb >>> btusb 53248 0 >>> btrtl 16384 1 btusb >>> btbcm 16384 1 btusb >>> btintel 20480 1 btusb >>> bluetooth 589824 41 btrtl,btintel,bnep,btbcm,rfcomm,btusb >>> snd_usb_audio 278528 1 >>> snd_usbmidi_lib 36864 1 snd_usb_audio >>> snd_hwdep 16384 2 snd_hda_codec,snd_usb_audio >>> snd_rawmidi 40960 1 snd_usbmidi_lib >>> snd_pcm 143360 5 >>> snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi >>> snd 98304 23 >>> snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm >>> usbhid 57344 0 >>> usbcore 290816 9 >>> uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci >>> >>> >>> This line is important: >>> >>> usbcore 290816 9 >>> uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci >>> >>> Notice the last two entries: xhci_hcd and ehci_pci >>> >>> Those correspond to: >>> >>> for my two usb 2 controllers: >>> >>> Kernel driver in use: xhci_hcd >>> Kernel modules: xhci_pci >>> >>> for my single usb 3 controller: >>> >>> Kernel driver in use: xhci_hcd >>> Kernel modules: xhci_pci >>> >>> >> >from your lspci: >>> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >>> Family USB 3.0 xHCI Controller >>> >>> This is the sole USB controller in your system and it's a USB 3 >>> controller >>> >>> so... in your case let's do: >>> >>> sudo lspci -s 00:14.0 -v >>> >>> then try: >>> >>> sudo modprobe usbcore >>> >>> and repeat: >>> >>> sudo lspci -s 00:14.0 -v >>> >>> see if the Kernel driver/module lines change. If they do, plug the >>> camera in and check for it to be recognized in lsusb >>> >>> >>> >>> >>> ___ >>> CentOS mailing list >>> CentOS@centos.org >>> https://lists.centos.org/mailman/listinfo/centos >> Thank you. Unfortunately I will not have access to this computer for some >> time, will let you know when I can try what you suggest. >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos > Hmm, did not have an opportunity to try your suggestion at the end of message > until today - after I did a BIOS update. The BIOS update, by the
Re: [CentOS] Logitech C922 webcam
On 10/02/2020 07:38 AM, H wrote: > On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell > wrote: >> On 9/30/20 8:52 AM, H wrote: >>> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >> Family USB 3.0 xHCI Controller >> My system has these: >> >> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >> Family USB xHCI (rev 05) >> 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >> Family USB EHCI #2 (rev 05) >> 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >> Family USB EHCI #1 (rev 05) >> >> lspci -s 00:14.0 -v >> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >> Family USB xHCI (rev 05) (prog-if 30 [XHCI]) >> Subsystem: ASUSTeK Computer Inc. Device 201f >> Flags: bus master, medium devsel, latency 0, IRQ 25 >> Memory at dd60 (64-bit, non-prefetchable) [size=64K] >> Capabilities: [70] Power Management version 2 >> Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ >> Kernel driver in use: xhci_hcd >> Kernel modules: xhci_pci >> >> lspci -s 00:1a.0 -v >> 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >> Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI]) >> Subsystem: ASUSTeK Computer Inc. Device 201f >> Flags: bus master, medium devsel, latency 0, IRQ 16 >> Memory at dd618000 (32-bit, non-prefetchable) [size=1K] >> Capabilities: [50] Power Management version 2 >> Capabilities: [58] Debug port: BAR=1 offset=00a0 >> Capabilities: [98] PCI Advanced Features >> Kernel driver in use: ehci-pci >> Kernel modules: ehci_pci >> >> lspci -s 00:1d.0 -v >> 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset >> Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI]) >> Subsystem: ASUSTeK Computer Inc. Device 201f >> Flags: bus master, medium devsel, latency 0, IRQ 23 >> Memory at dd617000 (32-bit, non-prefetchable) [size=1K] >> Capabilities: [50] Power Management version 2 >> Capabilities: [58] Debug port: BAR=1 offset=00a0 >> Capabilities: [98] PCI Advanced Features >> Kernel driver in use: ehci-pci >> Kernel modules: ehci_pci >> >> These are my kernel modules: >> >> lsmod | grep usb >> btusb 53248 0 >> btrtl 16384 1 btusb >> btbcm 16384 1 btusb >> btintel 20480 1 btusb >> bluetooth 589824 41 btrtl,btintel,bnep,btbcm,rfcomm,btusb >> snd_usb_audio 278528 1 >> snd_usbmidi_lib 36864 1 snd_usb_audio >> snd_hwdep 16384 2 snd_hda_codec,snd_usb_audio >> snd_rawmidi 40960 1 snd_usbmidi_lib >> snd_pcm 143360 5 >> snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi >> snd 98304 23 >> snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm >> usbhid 57344 0 >> usbcore 290816 9 >> uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci >> >> >> This line is important: >> >> usbcore 290816 9 >> uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci >> >> Notice the last two entries: xhci_hcd and ehci_pci >> >> Those correspond to: >> >> for my two usb 2 controllers: >> >> Kernel driver in use: xhci_hcd >> Kernel modules: xhci_pci >> >> for my single usb 3 controller: >> >> Kernel driver in use: xhci_hcd >> Kernel modules: xhci_pci >> >> > >from your lspci: >> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >> Family USB 3.0 xHCI Controller >> >> This is the sole USB controller in your system and it's a USB 3 >> controller >> >> so... in your case let's do: >> >> sudo lspci -s 00:14.0 -v >> >> then try: >> >> sudo modprobe usbcore >> >> and repeat: >> >> sudo lspci -s 00:14.0 -v >> >> see if the Kernel driver/module lines change. If they do, plug the >> camera in and check for it to be recognized in lsusb >> >> >> >> >> ___ >> CentOS mailing list >> CentOS@centos.org >> https://lists.centos.org/mailman/listinfo/centos > Thank you. Unfortunately I will not have access to this computer for some > time, will let you know when I can try what you suggest. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos Hmm, did not have an opportunity to try your suggestion at the end of message until today - after I did a BIOS update. The BIOS update, by the way, resulted in the complete loss of recognition of the Logitech camera, regardless of which USB ports I am trying... Anyway, your suggestion above follows:
Re: [CentOS] Centos 8 and logwatch
Hmm, it works fine for me, both as a cron job and when run directly. My system was last patched about 2 hours ago. Are you getting any mail? $ mail mail Subject: test test ^D $ If you get no message then logwatch isn't your issue. Next check your cron file, it ought to be in /etc/cron.daily/0logwatch Ensure that LOGWATCH_SCRIPT actually points to the code (typically /usr/sbin/logwatch) Check that the line for the following line: OPTIONS="--output mail" The actual invocation on my system is: $LOGWATCH_SCRIPT --range="between $day and yesterday" $OPTIONS As a final resort, edit 0logwatch and add the line "set -vx" just above the invocation. This will generate output which cron will attempt to send to root. Regards, Martin On 13/11/2020 12:03, Blaž Bogataj wrote: Hello I am trying to get logwatch working on CentOS 8. System is fully updated. Usually install minimal version and then add only necessary with yum. On CentOS 7: install logwatch and get daily logwatch report on mail. On CentOS 8: install logwatch but no way to get mail. Am I doing something wrong? Or miss something? Thanks in advance Blaz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Centos 8 and logwatch
Hello I am trying to get logwatch working on CentOS 8. System is fully updated. Usually install minimal version and then add only necessary with yum. On CentOS 7: install logwatch and get daily logwatch report on mail. On CentOS 8: install logwatch but no way to get mail. Am I doing something wrong? Or miss something? Thanks in advance Blaz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 188, Issue 2
Send CentOS-announce mailing list submissions to centos-annou...@centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-requ...@centos.org You can reach the person managing the list at centos-announce-ow...@centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. Release for CentOS Linux 7 (2009) on armhfp aarch64 i386 ppc64 ppc64le and power9 (Pablo Sebasti?n Greco) 2. Release for CentOS Linux 7 (2009) on the x86_64 Architecture (Johnny Hughes) -- Message: 1 Date: Thu, 12 Nov 2020 09:31:25 -0300 From: Pablo Sebasti?n Greco To: centos-annou...@centos.org Subject: [CentOS-announce] Release for CentOS Linux 7 (2009) on armhfp aarch64 i386 ppc64 ppc64le and power9 Message-ID: <9f9bc188-2372-b845-e424-0d9e30c74...@centosproject.org> Content-Type: text/plain; charset=utf-8; format=flowed I am pleased to announce the general availability of CentOS Linux 7 (2009) for across our alternative architectures. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 2009, derived from Red Hat Enterprise Linux 7.9. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. -- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 7 machine by just running 'yum update'. As with all CentOS Linux 7 components, this release was built from sources hosted at git.centos.org. In addition, SRPMs that are a byproduct of the build (and also considered critical in the code and buildsys process) are being published to match every binary RPM we release. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages are also being signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 7, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trimmed off from repos like Extras/ and Plus/ However this time we have also extended this to the SIG content hosted at mirror.centos.org, and some older End of Life content has been dropped. Everything we ever release, is always available on the vault service for people still looking for and have a real need for it. -- Special notes Altarch kernel: After RedHat's decision to deprecate power9 and aarch64 releases during the 7.7 cycle, and our decision to keep building them with the others (using the kernel from RHEL8), we decided to keep down this road. As 7.x and 8.x releases are not in sync, released kernel is 4.18.0-193.28.1 (8.2), but we're working on updating it to 4.18.0-240 (8.3) soon. -- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Details on the images are available on the mirrors in a file called 0_README.txt next to the isos. That file clearly highlights the difference in the images, and when one might be more suitable than the others. Altarch images can be downloaded at : http://mirror.centos.org/altarch/7/isos/ sha256sum for ppc64 1f53ccce8867412a91eca3d0dd99333ebef871ffba3b6fb3af7eb14e280dc653
[CentOS] Using anaconda gui without mouse
Hi, I should use Anaconda gui in CentOS 8.2 graphical way but the idrac doesn't map the mouse. What are the shortcuts for using only a keyboard? In particular it seems I'm blocked in the partitions page Any time I select one and press enter to configure the right side details/parameters, I don't find a way then to come back to the left side and move up/down to select another partition and configure its parameters. I would like to use it and not text install. Thanks, Gianluca ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MIDI on a VM
On 13/11/2020 09:09, J Martin Rushton via CentOS wrote: On 13/11/2020 07:01, Simon Matter wrote: On 12/11/2020 17:26, Ralf Prengel wrote: Hallo, witch virtualizer are you using. KVM/QEMU Sure that the virtual sound-device is connected with the right hardware? I can play CDs and listen to YouTube on the host, so I'm assuming the hardware is fine. I don't know how this works here but doesn't playing MIDI files mean you need a MIDI capable sound card which generates the sound? Maybe the virtual sound-device is only capable to play audio? Regards, Simon Very good point. I will investigate further. I had two models in my head: 1) The Frescobaldi playback module did the MIDI-> sound conversion. 2) The virtual card passed the signals on to the physical card. Perhaps your third model is correct. Extra information: I've run up YouTube with the virtual sound card set to ac97 and can play back a simple audio stream. Running the MIDI system has no effect. Furthermore the mixer shows a connection from Firefox, but doesn't show one from Frescobaldi. I think you've hit the nail on the head. Well done. Now how to fix it! Regards, Martin -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MIDI on a VM
On 13/11/2020 07:01, Simon Matter wrote: On 12/11/2020 17:26, Ralf Prengel wrote: Hallo, witch virtualizer are you using. KVM/QEMU Sure that the virtual sound-device is connected with the right hardware? I can play CDs and listen to YouTube on the host, so I'm assuming the hardware is fine. I don't know how this works here but doesn't playing MIDI files mean you need a MIDI capable sound card which generates the sound? Maybe the virtual sound-device is only capable to play audio? Regards, Simon Very good point. I will investigate further. I had two models in my head: 1) The Frescobaldi playback module did the MIDI-> sound conversion. 2) The virtual card passed the signals on to the physical card. Perhaps your third model is correct. -- J Martin Rushton MBCS ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
