@Prexy Well then itās either AMD or Intel⦠what are the computer specs?
So I run the ARC GPUās in PCI 3.0 slots, no rebar (for memory) so performance is not as good if in a Motherboard with PCIe 4.0 and rebar, but works fine, the encoders/decoders work, I have oneAPI running, but I doubt you need that.
I switched over to an older computer with an intel chip. Display is perfect. I do this switch periodically to get updates installed. But that means I canāt show the specs you wanted to see until I switch back.
I have been reading a newer thread where compatibility errors arose with both kernel 6.10 and 6.11 and nvidia. What a mess!
Given what I showed you in comment #32, Iāll bet a fresh TW installation void of the taint of any proprietary software of any kind would simply make your 730 work just like my 10de:1288 720. Possibly simpler, borrow the SSD out of a different TW PC with AMD or Intel GPU only to prove the possibility. One with Leap instead of TW would not suffice unless you first installed its kernel-default-extra, as thatās the source of Leapās nouveau kernel module. Actually, first wouldnāt be a necessity, but youād be stuck at 1024x768 until it was done.
@mrmazda driver is N/A and nouveau is loaded⦠the real issue is what is stopping even the nouveau driver from loading⦠and being able to remove it from initrd, which should happen.
Does Prexy, or does Prexy not, wish to use FOSS to the exclusion of proprietary software? If he does, then he will absolutely need to use the nouveau kernel module, if he wishes to use any displayās native resolution of more than 1024x768.
Iād be happy to use FOSS if I can get it to work. Also, I have a CD with a net install and I would gladly do a reinstall with it. But I have two considerations. The PC is dual boot with Windows and I have lots of data I donāt want to lose. I seem to remember that you can do a ārepairā with an install disk that would cover those two concerns.
However, I live in a retirement community and our Internet has been down for a while this evening. So, anything I try will have to wait until the morning. Iām responding on my phone and donāt know if it comes through properly.
This is @Prexy . I am posting from a live usb and had to create a new account.
The display is working perfectly on kernel-default 6.11.0.-1.1 using a MicroOS driver. Iām going to see if I can install these files on my hard drive.
I do not think you should have cancelled this operation. By cancelling it did not allow zypper to rebuild the NVidia kernel modules. Please do correct me if this is not the case.
Iād like to try and find out what driver it may have that ordinary TW does not. What is the .iso filename you downloaded? Does it match any found on http://download.opensuse.org/tumbleweed/appliances/ ?
I went to the site you linked. I donāt remember which of the TW iso I used. I made a usb and a DVD of the file. Installing the files to run nouveau, I rebooted and got the same result as when all the nvidia files were still installed.
Giving up hope of fixing the problems, which were growing, I used the usb to install TW over the broken install. It worked! None of the nvidia files installed. The MicroOS driver and kernel-firmware were the only files installed.
So you deleted the .iso file already? I think if you insert the USB in a running system a file manager will report a title that probably equates to that name. It probably wouldnāt hurt to check out its /etc/os-release file, which may have something useful to report. Simply āMicroOSā isnāt sufficient.
The title of the usb is only āopenSUSE_Tumbleweed_KDE_Liveā and the os-release file shows this
NAME="openSUSE Tumbleweed"
# VERSION="20241003"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20241003"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20241003:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20241003"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"
I have minor adjustments to make to get back to where I was, but the re-install was a fix.
I think from reading two current Fedora mailing list threads that āMicroOSā driver that inxi doesnāt know about is the āsimpledrmā driver thatās existed for quite some time but only become available as standard backup to preferred drivers as of 6.11 kernel. Please pastebin an Xorg.o.log like the boot that caused generation of your inxi output with unidentified display driver āN/Aā here.