Discuss April 2024

discuss@lists.centos.org

14 participants
17 discussions

Issues booting centos7 [dracut is failing to enable centos/root, centos/swap LVs]
by Yannis Milios 01 Feb '25

01 Feb '25

Hello, I'm having a strange problem booting a new centos7 installation. Below some background on this. [I have attached the tech details at the bottom of this message] I started a new CentOS7 installation on a VM, so far all good, o/s boots fine. Then I decided to increase VM disk size (initially was 10G) to 13G. Powered off the VM, increased the vhd via the hypervisor, booted from CentOS livecd, selected "recover my centos installation". Then I used the following sequence of commands to make the new vhd size "visible" to the o/s ... - ran fdisk /dev/sda and deleted partition 2. (This is the LVM partition where the o/s is stored. The first partition is /boot [xfs] partition *non lvm*.) - created a new partition with same starting sector as before deleting it, but a different ending sector (to reflect to the increased space). - set partition type to 8e (lvm), saved settings and exit. - ran pvresize and lvresize to make new space visible to the o/s.All good, I can see the space increase on 'lvdisplay centos/root'. - ran 'mount /dev/mapper/centos-root /mnt/root' to temporarily mount the o/s partition. - ran 'xfs_growfs /mnt/root' to resize the o/s fs to the new size. It was successful and I could actually chroot to the o/s and verify new disk size. - rebooted and tried to boot from hdd this time. Grub menu shows up and loads default kernel (3.10.0-862.9.1.el7.x86_64). - after initial kernel boot up process, booting continues to initrd and then it's where the problem starts... - looks like dracut has issues locating/enabling /dev/mapper/centos-root (lv) and as a result it cannot boot to the 'real' root fs (/). - while in dracut shell, I execute the following command sequence: 1. lvm lvchange -ay /dev/centos/root 2. lvm lvchange -ay /dev/centos/swap 3. ln -s /dev/mapper/centos-root /dev/root 4. exit ...and the o/s boots fine...so looks like the pv,vg,lv is detected properly while in initrd, but somehow dracut has difficulties enabling the root,swap LVs ? - While in o/s, I rebuild initrd by using: 'dracut -f -v -a lvm' Note, I have to use '-a lvm' as for some reason, if don't, the lvm utils (lvm,lvm_scan) are not being included to the initrd, not sure why this happens. After rebooting, same thing happens, I have to manually boot the system via dracut shell. I'm a bit stuck at this point, any clues what I'm doing wrong in here ? As I previously said, this is a new installation, so I could simply reinstall the whole thing, but I would rather try to find out some answer to why is this happening ... :-) [curiosity] Some additional details: ================== I've attached /run/initramfs/rdsosreport.txt file [generated while in inird] here: https://privatebin.net/?fdc4052c0c402884#gdB/QYR3IeR55SxUbjfrkZPQfJ7jMxiUxq… o/s ver=CentOS Linux release 7.5.1804 (Core) [root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 13G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 12.5G 0 part ├─centos-root 253:0 0 11.5G 0 lvm / └─centos-swap 253:1 0 1G 0 lvm [SWAP] [root@localhost ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rd.shell rhgb" GRUB_DISABLE_RECOVERY="true"

4 11

No suspend after update
by Michael B Allen 22 May '24

22 May '24

Just updated CentOS 9 Stream on a Lenovo T17 Gen 4 Intel and not it won't suspend with the following error: [ 52.604998] Restarting kernel threads ... done. [ 52.605111] OOM killer enabled. [ 52.605111] Restarting tasks ... done. [ 52.606604] random: crng reseeded on system resumption [ 52.616014] thermal thermal_zone9: failed to read out thermal zone (-61) [ 52.791625] PM: suspend exit [ 52.791733] PM: suspend entry (s2idle) [ 52.797260] Filesystems sync: 0.005 seconds [ 52.797579] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 52.799127] OOM killer disabled. [ 52.799128] Freezing remaining freezable tasks ... [ 72.805437] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 72.805450] task:NFSv4 callback state:I stack:0 pid:2191 ppid:2 flags:0x00004000 [ 72.805453] Call Trace: [ 72.805454] <TASK> [ 72.805456] __schedule+0x21b/0x550 [ 72.805463] schedule+0x2d/0x70 [ 72.805466] nfs41_callback_svc+0x186/0x190 [nfsv4] [ 72.805508] ? __pfx_autoremove_wake_function+0x10/0x10 [ 72.805512] ? __pfx_nfs41_callback_svc+0x10/0x10 [nfsv4] [ 72.805536] kthread+0xdd/0x100 [ 72.805538] ? __pfx_kthread+0x10/0x10 [ 72.805539] ret_from_fork+0x29/0x50 [ 72.805543] </TASK> Kernel: 5.14.0-404.el9.x86_64 How do I boot the previous kernel? Holding Shift down does nothing. Pressing escape brings up some kind of emergency screen that has no options other than to "Press any key to exit". Is CentOS 9 Stream considered stable enough to use as an everyday desktop? Mike

3 7

Problem 1: package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch from @System requires pki-servlet-4.0-api, but none of the providers can be installed
by Jelle de Jong 30 Apr '24

30 Apr '24

Dear CentOS members, Does someone know how to resolve this package conflict, it is creating security issues with freeipa dependencies. [root@freeipa01 ~]# yum update --refresh CentOS Stream 8 - AppStream 102 kB/s | 4.4 kB 00:00 CentOS Stream 8 - BaseOS 18 kB/s | 3.9 kB 00:00 CentOS Stream 8 - Extras 55 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 15 kB/s | 3.0 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 367 kB/s | 28 kB 00:00 Extra Packages for Enterprise Linux 8 - Next - x86_64 75 kB/s | 35 kB 00:00 Error: Problem 1: package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch from @System requires pki-servlet-4.0-api, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream - cannot install the best update candidate for package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch - cannot install the best update candidate for package pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch Problem 2: cannot install the best update candidate for package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch - both package tomcat-el-3.0-api-1:9.0.62-30.el8.noarch from appstream and tomcat-lib-1:9.0.62-30.el8.noarch from appstream obsolete pki-servlet-engine <= 1:9.0.50 - package tomcat-1:9.0.62-30.el8.noarch from appstream requires tomcat-lib = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcat-jsp-2.3-api-1:9.0.62-30.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcat-lib-1:9.0.62-30.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcatjss-7.7.1-1.module_el8.6.0+1038+e795ee4b.noarch from @System requires pki-servlet-engine >= 1:9.0.7, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System requires pki-servlet-4.0-api = 1:9.0.30-3.module_el8.5.0+854+e1c92b81, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream requires pki-servlet-4.0-api = 1:9.0.30-3.module_el8.5.0+854+e1c92b81, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream requires pki-servlet-4.0-api = 1:9.0.30-1.module_el8.4.0+595+e59c9af2, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream - cannot install the best update candidate for package tomcatjss-7.7.1-1.module_el8.6.0+1038+e795ee4b.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

2 1

Fwd: [clamav-users] ClamAV 1.0.X for EPEL 7 & 8
by Kenneth Porter 27 Apr '24

27 Apr '24

------------------------------------------------------------------------ *From:* Orion Poplawski via clamav-users [mailto:clamav-users@lists.clamav.net] *Sent:* Friday, April 26, 2024 at 5:05 PM *To:* ClamAV users ML *Cc:* Orion Poplawski *Subject:* [clamav-users] ClamAV 1.0.X for EPEL 7 & 8 With the help of John Sullivan and Sérgio M. Basto we have gotten the Fedora ClamAV 1.0.X package in shape to be built for EPEL 7 and 8. We have a COPR available now with builds of 1.0.6 ready for testing here: https://copr.fedorainfracloud.org/coprs/g/clamav/clamav-1.0/ We will likely push this to EPEL proper just after RHEL 8.10 is released, presumably in May. But testing and feedback of the COPR builds before that would be welcome. Orion -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Laneorion(a)nwra.com Boulder, CO 80301https://www.nwra.com/

1 0

RDO Caracal 2024.1 Released
by Amy Marrich 24 Apr '24

24 Apr '24

RDO Caracal 2024.1 Released The RDO community is pleased to announce the general availability of the RDO build for OpenStack 2024.1 Caracal for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Caracal is the 29th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-caraca… The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud SIG. The Cloud SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/caracal/highlights.html but here are some highlights: - Drivers with inactive CI were marked unsupported including Windows iSCSI Driver, Windows SMB Driver, Dell SC Series Storage Driver (iSCSI, FC), Dell VNX Storage Driver (FC, iSCSI) and Dell XtremeIO Storage Driver (iSCSI, FC). - New driver features were added, notably, Fujitsu ETERNUS DX extend volume on RAID group, Pure Storage synchronous replication, NetApp iSCSI LUN space allocation, Dell PowerFlex Active-Active support, Dell PowerMax configurable SRDF snapshots. - Designate now supports Catalog Zones (RFC 9432). This can improve the scalability of Designate pools managing a large number of zones and significantly reduce the provisioning time when adding additional DNS servers to a Designate pool. - Horizon now uses Django 4.2 as default and dropped Django 3.2 support. - Ironic has enabled RBAC support by default by changing the default values of [oslo_policy]enforce_scope and [oslo_policy]enforce_new_defaults to True. Additionally, we added [DEFAULT]rbac_service_project_name to define a project where users in that project are treated as having a service role. Please see Ironic release notes for full details. - Ironic has added the ability to drain active tasks from a conductor before shutdown. Sending a SIGUSR2 signal to an ironic-conductor will now attempt to complete running tasks with a timeout of [DEFAULT]drain_shutdown_timeout. No new tasks will be started on the conductor while it’s draining. - Support was added for the external-gateway-multihoming API extension. The L3 service plugins supporting it can now create multiple gateway ports per router. It is currently limited to the L3 OVN plugin. OpenStack Caracal is marked as Skip Level Upgrade Release Process or SLURP. According to this model ( https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…) this means that upgrades will only be supported from the Antelope 2023.1 release. RDO Caracal 2024.1 has been built and tested with the recently released Ceph 18.2.0 Reef version (https://docs.ceph.com/en/latest/releases/reef/) which has been published by the CentOS Storage SIG in the official CentOS repositories. *Note:* Follow the instructions in [RDO documentation]( https://www.rdoproject.org/install/install-with-ceph/) to install OpenStack and Ceph services in the same host. During Caracal cycle, some projects have been retired or declared inactive upstream. As such, the following packages for some projects are not present in the RDO Caracal 2024.1 release: - cinderlib - dib-utils - ec2api-tempest-plugin - ec2api - murano - murano-agent - muranoclient - murano-dashboard - murano-tempest-plugin - sahara - sahara-dashboard - sahara-image-elements - sahara-plugin-ambari - sahara-plugin-cdh - sahara-plugin-mapr - sahara-plugin-spark - sahara-plugin-storm - sahara-plugin-vanilla - sahara-tests - senlin - senlinclient - puppet-ec2api - puppet-etcd - puppet-haproxy - puppet-module-data - puppet-murano - puppet-qdr - puppet-rsyslog - puppet-sahara During the next release we will continue working on retiring inactive packages in order to ensure RDO content quality and security. Contributors: - During the Caracal cycle, we saw the following new RDO contributors: - Marihan Girgis - Balazs Gibizer - Fiorella Yanac Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 47 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and rdo-website repositories: - Ade Lee - Alfredo Moralejo Alonso - Amy Marrich (spotz) - Arx Cruz - Balazs Gibizer - Bernard Cafarelli - Bohdan Dobrelia - Chandan Kumar - Cyril Roelandt - Daniel Pawlik - Douglas Viroel - Emma Foley - Fabricio Aguiar - Fiorella Yanac - Gregory Thiemonge - Grzegorz Grasza - Harald Jensås - Jiří Podivín - Joan Francesc Gilabert - Joel Capitao - Karolina Kula - Lewis Denny - Lon Hohberger - Luigi Toscano - Luis Tomas Bolivar - Lukáš Piwowarski - Maor Blaustein - Marihan Girgis - Marios Andreou - Martin Kopec - Martin Magr - Mathieu Bultel - Michael Johnson - Nate Johnston - Pablo Rodríguez Nava - Priscila Gutierres - Rabi Mishra - Roberto Alfieri - Ronelle Landy - Shreshtha Joshi - Soniya Vyas - Szymon Datko - Takashi Kajinami - Tobias Urdin - Tristan De Cacqueray - Yatin Karel - Zane Bitter The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Dalmatian. Get Started To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. For those that do not have any hardware or physical resources, there is the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS IRC channels (#centos, #centos-cloud, #centos-devel in Libera.Chat network), however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube. *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz

1 0

Problem 2: Can't uninstall tigervnc-server-minimal.x86_64 without forcing removal of anaconda!
by Kay Schenk 23 Apr '24

23 Apr '24

Dear all --- I DO NOT want tigervnc on my system! I've done what I can changing dnf parameters on uninstall. If I try to deinstall it, it absolutely, positively wants to UNINSTALL anaconda no matter what options I provide. Running CentOS 8, one of the 4.18 xxxxx Any solutions? -- --- Kay Schenk

2 1

Figure out why kdump is not producing dmesg in CentOS stream 8
by public1020 13 Apr '24

13 Apr '24

I created a CentOS 8 stream machine on aws, and configured crashkernel in grub ``` $ cat /proc/cmdline BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-552.el8.x86_64 root=UUID=e52ef623-609b-4202-9b2c-ac7aba5c3bee ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 nvme_core.io_timeout=4294967295 nvme_core.max_retries=10 crashkernel=128M ``` Then I installed and verified kdump is functioning ``` # systemctl status kdump ● kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2024-04-13 08:42:55 UTC; 40s ago Process: 808 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS) Main PID: 808 (code=exited, status=0/SUCCESS) Apr 13 08:42:43 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Install squash loader *** Apr 13 08:42:43 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Stripping files *** Apr 13 08:42:44 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Stripping files done *** Apr 13 08:42:44 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Squashing the files inside the initramfs *** Apr 13 08:42:54 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Squashing the files inside the initramfs done *** Apr 13 08:42:54 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Creating image file '/boot/initramfs-4.18.0-552.el8.x86_64kdump.img' *** Apr 13 08:42:55 ip-172-31-2-139.ap-east-1.compute.internal dracut[1101]: *** Creating initramfs image file '/boot/initramfs-4.18.0-552.el8.x86_64kdump.img' done *** Apr 13 08:42:55 ip-172-31-2-139.ap-east-1.compute.internal kdumpctl[814]: kdump: kexec: loaded kdump kernel Apr 13 08:42:55 ip-172-31-2-139.ap-east-1.compute.internal kdumpctl[814]: kdump: Starting kdump: [OK] Apr 13 08:42:55 ip-172-31-2-139.ap-east-1.compute.internal systemd[1]: Started Crash recovery kernel arming. ``` Now I need to mimic kernel crash, so I used sysrq to do that ``` echo c > /proc/sysrq-trigger ``` However, after reboot, I didn't see a dmesg file in /var/crash as in CentOS 7.X ``` # ls /var/crash - nothing, empty folder - ``` The only thing I can see is /var/log/kdump.log ``` + 2024-04-13 08:35:56 /usr/bin/kdumpctl@679: ret=0 + 2024-04-13 08:35:56 /usr/bin/kdumpctl@680: set +x + 2024-04-13 08:42:55 /usr/bin/kdumpctl@675: /sbin/kexec -s -d -p '--command-line=BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-552.el8.x86_64 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 nvme_core.io_timeout=4294967295 nvme_core.max_retries=10 irqpoll nr_cpus=1 reset_devices cgroup_disable=memory mce=off numa=off udev.children-max=2 panic=10 rootflags=nofail acpi_no_memhotplug transparent_hugepage=never nokaslr novmcoredd hest_disable disable_cpu_apicid=0' --initrd=/boot/initramfs-4.18.0-552.el8.x86_64kdump.img /boot/vmlinuz-4.18.0-552.el8.x86_64 Try gzip decompression. Try LZMA decompression. + 2024-04-13 08:42:55 /usr/bin/kdumpctl@679: ret=0 + 2024-04-13 08:42:55 /usr/bin/kdumpctl@680: set +x + 2024-04-13 08:44:31 /usr/bin/kdumpctl@675: /sbin/kexec -s -d -p '--command-line=BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-552.el8.x86_64 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 nvme_core.io_timeout=4294967295 nvme_core.max_retries=10 irqpoll nr_cpus=1 reset_devices cgroup_disable=memory mce=off numa=off udev.children-max=2 panic=10 rootflags=nofail acpi_no_memhotplug transparent_hugepage=never nokaslr novmcoredd hest_disable disable_cpu_apicid=0' --initrd=/boot/initramfs-4.18.0-552.el8.x86_64kdump.img /boot/vmlinuz-4.18.0-552.el8.x86_64 Try gzip decompression. Try LZMA decompression. + 2024-04-13 08:44:31 /usr/bin/kdumpctl@679: ret=0 + 2024-04-13 08:44:31 /usr/bin/kdumpctl@680: set +x ``` I need the dmesg to understand what's causing the crash. How can I do that? P.S I have a kernel module that triggers a crash but I don't know why, and to demonstrated the problem with kdump, I use sysrq so anyone want to help can easily reproduce it.

2 4

Out-Of-Office
by Sivaramakrishna Polepalli 13 Apr '24

13 Apr '24

Hello, I will be OOO traveling from 03/28 to 05/06 returning back on 05/07. Please expect delays in my email responses. Please contact Aurus support prodsupport(a)aurusinc.com / Yogesh Baviskar ybaviskar(a)aurusinc.com for any support needs. Thanks Siva Polepalli +1 575-404-3272

1 0

None
by None 05 Apr '24

05 Apr '24

blank" do you not understand? ;) If you do not believe there is any problem, consider the complexity of Johnny Hughes's solution! If Johnny Hughes's solution works for him and he is happy with it, that is great -- more power to him. (The FAQ includes a write up of Johnny's solution.) I have two replies. 1) Back a couple of months ago, as a test, I tried his solution, and the screen on my Mag DX1495 still went blank with the two nVIDIA cards that I tested. 2) I would rather just plug in a card which works right out of the box on a standard, SUPPORTED kernel, than to go through all the complicated steps in Johnny's solution. But this is just my personal preference. I can use the nVIDIA cards in Linux with compatible monitors or in Windows with any monitor (as far as I know). BTW, the computer on which I am writing this email runs CentOS, and with this Acer 77c monitor, I am using an nVIDIA GeForce display card -- it works fine with THIS hardware. Rick Message: 7 Date: Tue, 21 Sep 2004 23:17:26 -0400 From: Christopher Blume <godsmoke(a)godsmoke.com> To: centos(a)caosity.org Subject: Re: [Centos] nVIDIA on CentOS 3.3 Hello Rick, I have to say, I found your notice of nVidia cards "not working" as a little odd. To begin with -- drivers *generally* do not vary between distributions of linux. So, the fact that your card "doesn't work" with CentOS means that something else went wrong -- not that the drivers don't exist, or don't function properly. First of all, I'd be interested to see where your conclusion that your monitor doesn't work with an nVidia card in linux came from -- what exactly did you experience/test to come to this statement? I don't know anything about Kudzu, but, let me tell you, the nVidia Riva TNT 2 is ABSOLUTELY supported by the linux kernel -- and XFree86 ABSOLUTELY runs on it. If it's not working on your system, instead of making conclusions about Linux as a whole, understand that there are probably issues with the configuration files you either manually wrote, or the programs CentOS/RHEL bundles with the distro did. nVidia cards have the absolute best support under linux of any video card -- and I highly doubt what you experienced was a driver issue -- if it was, it was because of some mangled patch that RedHat applied, because the driver for nVidia TNTs is used by tens of thousands of Linux users. Thank You, Christopher Blume

1 0

Out-Of-Office
by Sivaramakrishna Polepalli 04 Apr '24

04 Apr '24

Hello, I will be OOO traveling from 03/28 to 05/06 returning back on 06/07. Please expect delays in my email responses. Please contact Aurus support prodsupport(a)aurusinc.com / Yogesh Baviskar ybaviskar(a)aurusinc.com for any support needs. Thanks Siva Polepalli +1 575-404-3272

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2024