Sat, 31 Aug 2024 12:44:11 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: nvidia g05 or nouveau in TW Live/Install? Message-ID : <fee85465-ef85-4e51-9401-7c3359ff3402@gmail.com> Date & Time: Fri, 30 Aug 2024 20:28:06 -0500
[DCR] == "David C. Rankin" <drankinatty@gmail.com> has written:
DCR> On 8/28/24 5:13 AM, bent fender wrote: DCR> > So what I think I should try is recover the TW partition, then DCR> > chroot from Slackware and TRY to edit what needs editing so that DCR> > nouveau gets used on the next boot, which is a few fathoms over my DCR> > head. I did chroot and try to install the last nvidia 'run' driver file DCR> > but I don't think it helped any DCR> > (NVIDIA-Linux-x86_64-470.256.02.run).
DCR> Yikes - NO,
DCR> The .run file is the binary blob that "has to be DCR> patched". That is what I patched in the links to the repo I DCR> provided. You really have 2 options - both from chroot. [...] ]...] DCR> That whale is getting eaten -- slowly -- one bite at a time...
He has got another issue with the video driver.
Ben, please show ths resuls of;
Thanks for chiming in :-)
$ inxi -b
I think I did this with a really-booted TW using kernel arguments 3 and nomodeset (as opposed to a chrooted one): System: Host: localhost.localdomain Kernel: 6.10.5-1-default arch: x86_64 bits: 64 Desktop: KDE Plasma v: 6.1.4 Distro: openSUSE Tumbleweed 20240829 Machine: Type: Desktop Mobo: ASUSTeK model: Crosshair IV Formula v: Rev 1.xx serial: MB-1234567890 BIOS: American Megatrends v: 3029 date: 10/09/2012 CPU: Info: 8-core AMD FX-8150 [MCP] speed (MHz): avg: 2037 min/max: 1400/3600 Graphics: Device-1: NVIDIA GK107 [GeForce GT 640] driver: N/A Display: x11 server: X.Org v: 21.1.12 with: Xwayland v: 24.1.2 driver: X: loaded: nouveau,vesa unloaded: fbdev,modesetting failed: nv gpu: N/A resolution: 1920x1080 API: OpenGL v: 4.5 vendor: mesa v: 24.1.3 renderer: llvmpipe (LLVM 18.1.8 256 bits) Network: Device-1: Marvell Yukon Optima 88E8059 [PCIe Gigabit Ethernet with AVB] driver: sky2 Device-2: Linksys AE6000 802.11a/b/g/n/ac Wireless Adapter [MediaTek MT7610U] driver: mt76x0u type: USB Drives: Local Storage: total: 9.27 TiB used: 1.95 TiB (21.1%) Info: Memory: total: 16 GiB available: 15.6 GiB used: 1.35 GiB (8.6%) Processes: 266 Uptime: 0h 1m Shell: Bash inxi: 3.3.35 I also DL'd and burned openSUSE-Tumbleweed-DVD-x86_64-Snapshot20240829-Media.iso openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20240829-Media.iso openSUSE-Tumbleweed-NET-x86_64-Snapshot20240829-Media.iso checksums all good, each burn verified no errors Every way I could try behaved essentially the same: after a brief command line run the HDMI symb olappears and after that nothing but a blank screen. If I select some degrading options 'like' F3 console 1920x1080 F5 kernekl safe setting or NOACPI F6 driver NO then I might get graphic sliders showing "Loading basic drivers..." etc and THAT folowed by a blank black screen One one run (I think it might have been on the installed system and not one of the DVD's) I got a last command line read something like "start plymouth....". Someone already accused plymouth of being THE real culprit. A questions I cannot resist: why try for a GUI *at all* for things like rescue net install check media boot linux system ????? It would be much smarter to promt the user to insert a blank USB stick at the beginning that will be formatted fat and unto which the entire startup will be written! In addition there should be a back button at every 'station' with screen shots saved out to the same place. My 2 cents. This whole horror-show has been going on since March of last spring!