Is something cooking in the vcard driver kitchen? I
understand nvidia has released the driver codes. So
I removed the nvidia driver and installed nouveau on
TW and Slowroll but on both of them kernel 7 still only
goes as far as a black screen with nothing on it, same
as without nouveau. At this rate when 6.5 slides off
the grub list both my systems go tango-uniform?

On Fri, 23 Feb 2024 07:58:21 -0500
bad sector <forgetski@_INVALID.net> wrote:

> Is something cooking in the vcard driver kitchen? I
> understand nvidia has released the driver codes. So
> I removed the nvidia driver and installed nouveau on
> TW and Slowroll but on both of them kernel 7 still only
> goes as far as a black screen with nothing on it, same
> as without nouveau. At this rate when 6.5 slides off
> the grub list both my systems go tango-uniform?
>
Hi
You mean kernel 6.7.5? Nvidia has the open driver for Turing cards or
better, there is still nouveau...

When you uninstalled the nvidia driver, did you make sure nouveau was
removed from the blacklist, any xorg.conf removed, grub options removed
etc.

All good here with the 550.40.07 driver, the other system uses the rpm
and it's fine too.

--
Cheers Malcolm °¿° (Linux Counter #276890)
Tumbleweed 20240221 | GNOME Shell 45.3 | 6.7.5-1-default
HP Z440 | Xeon E5-2695 V4 X36 @ 2.10GHz | Quadro T400/Tesla P4
up 2 days 22:49, 2 users, load average: 0.17, 0.08, 0.09

On 2/23/24 09:32, Malcolm wrote:
> On Fri, 23 Feb 2024 07:58:21 -0500
> bad sector <forgetski@_INVALID.net> wrote:
>
>> Is something cooking in the vcard driver kitchen? I
>> understand nvidia has released the driver codes. So
>> I removed the nvidia driver and installed nouveau on
>> TW and Slowroll but on both of them kernel 7 still only
>> goes as far as a black screen with nothing on it, same
>> as without nouveau. At this rate when 6.5 slides off
>> the grub list both my systems go tango-uniform?
>>
> Hi
> You mean kernel 6.7.5? Nvidia has the open driver for Turing cards or
> better, there is still nouveau...
>
> When you uninstalled the nvidia driver, did you make sure nouveau was
> removed from the blacklist, any xorg.conf removed, grub options removed
> etc.
>
> All good here with the 550.40.07 driver, the other system uses the rpm
> and it's fine too.

I did better, I just burnt yesterday's TW live KDE
and did a fresh install, it gives be a login prompt
and nothing else, in recovery mode it gives me an
empty black screen. I never asked for an nvidia
driver so I presume that nouveau is active, so
how come it suddenly cannot work my card which it
could do before? I'm posting THIS form my Slowroll

--
openSUSE Tumbleweed , Kernel=6.5.9-1-default on x86_64,
DM=sddm, DE=KDE, ST=x11,grub2, GPT, BIOS-boot

On Fri, 23 Feb 2024 21:20:19 -0500
bad sector <forgetski@_INVALID.net> wrote:

> On 2/23/24 09:32, Malcolm wrote:
> > On Fri, 23 Feb 2024 07:58:21 -0500
> > bad sector <forgetski@_INVALID.net> wrote:
> >
> >> Is something cooking in the vcard driver kitchen? I
> >> understand nvidia has released the driver codes. So
> >> I removed the nvidia driver and installed nouveau on
> >> TW and Slowroll but on both of them kernel 7 still only
> >> goes as far as a black screen with nothing on it, same
> >> as without nouveau. At this rate when 6.5 slides off
> >> the grub list both my systems go tango-uniform?
> >>
> > Hi
> > You mean kernel 6.7.5? Nvidia has the open driver for Turing cards
> > or better, there is still nouveau...
> >
> > When you uninstalled the nvidia driver, did you make sure nouveau
> > was removed from the blacklist, any xorg.conf removed, grub options
> > removed etc.
> >
> > All good here with the 550.40.07 driver, the other system uses the
> > rpm and it's fine too.
>
> I did better, I just burnt yesterday's TW live KDE
> and did a fresh install, it gives be a login prompt
> and nothing else, in recovery mode it gives me an
> empty black screen. I never asked for an nvidia
> driver so I presume that nouveau is active, so
> how come it suddenly cannot work my card which it
> could do before? I'm posting THIS form my Slowroll
>
>
Hi
Don't use slowroll so no idea, does it see the device from lspci, eg
/sbin/lspci -nnk | grep -EA3 "VGA|Display|3D"

--
Cheers Malcolm °¿° (Linux Counter #276890)
Tumbleweed 20240221 | GNOME Shell 45.3 | 6.7.5-1-default
HP Z440 | Xeon E5-2695 V4 X36 @ 2.10GHz | Quadro T400/Tesla P4
up 0:10, 2 users, load average: 1.05, 0.61, 0.29

On 2/23/24 21:55, Malcolm wrote:
> On Fri, 23 Feb 2024 21:20:19 -0500
> bad sector <forgetski@_INVALID.net> wrote:
>
>> On 2/23/24 09:32, Malcolm wrote:
>>> On Fri, 23 Feb 2024 07:58:21 -0500
>>> bad sector <forgetski@_INVALID.net> wrote:
>>>
>>>> Is something cooking in the vcard driver kitchen? I
>>>> understand nvidia has released the driver codes. So
>>>> I removed the nvidia driver and installed nouveau on
>>>> TW and Slowroll but on both of them kernel 7 still only
>>>> goes as far as a black screen with nothing on it, same
>>>> as without nouveau. At this rate when 6.5 slides off
>>>> the grub list both my systems go tango-uniform?
>>>>
>>> Hi
>>> You mean kernel 6.7.5? Nvidia has the open driver for Turing cards
>>> or better, there is still nouveau...
>>>
>>> When you uninstalled the nvidia driver, did you make sure nouveau
>>> was removed from the blacklist, any xorg.conf removed, grub options
>>> removed etc.
>>>
>>> All good here with the 550.40.07 driver, the other system uses the
>>> rpm and it's fine too.
>>
>> I did better, I just burnt yesterday's TW live KDE
>> and did a fresh install, it gives be a login prompt
>> and nothing else, in recovery mode it gives me an
>> empty black screen. I never asked for an nvidia
>> driver so I presume that nouveau is active, so
>> how come it suddenly cannot work my card which it
>> could do before? I'm posting THIS form my Slowroll
>>
>>
> Hi
> Don't use slowroll so no idea, does it see the device from lspci, eg
> /sbin/lspci -nnk | grep -EA3 "VGA|Display|3D"

I'm posting from Slowroll because the Tumbleweed I just installed
is unusable. Once I get it running I can leave it as Tumbleweed
or change it to Slowroll just by editing the repos to use to
Slowroll from that point forward.

Booting that 'freshie', I can log-in as user and do startx
but the resolution is ridiculous

# /sbin/lspci -nnk | grep -EA3 "VGA|Display|3D"
06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107
[GeForce GT 640] [10de:0fc1] (rev a1)
Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1258]
Kernel modules: nouveau
06:00.1 Audio device [0403]: NVIDIA Corporation GK107 HDMI Audio
Controller [10de:0e1b] (rev a1)

So as I suspected nouveau is in control but in name only
because 640x480 is not what I call control of a 1920x1080
monitor.

BTW the reason for the new install is that I can't get
vbox working right in the others (posted in alt.os.linux),
in Slowroll I have to log-in twice each time, and all of
them work GUI only with kernel 6.5 but no 7's.

On Fri, 23 Feb 2024 23:20:41 -0500
bad sector <forgetski@_INVALID.net> wrote:

<snip>
>
> I'm posting from Slowroll because the Tumbleweed I just installed
> is unusable. Once I get it running I can leave it as Tumbleweed
> or change it to Slowroll just by editing the repos to use to
> Slowroll from that point forward.
>
> Booting that 'freshie', I can log-in as user and do startx
> but the resolution is ridiculous
>
> # /sbin/lspci -nnk | grep -EA3 "VGA|Display|3D"
> 06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107
> [GeForce GT 640] [10de:0fc1] (rev a1)
> Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1258]
> Kernel modules: nouveau
> 06:00.1 Audio device [0403]: NVIDIA Corporation GK107 HDMI Audio
> Controller [10de:0e1b] (rev a1)
>
> So as I suspected nouveau is in control but in name only
> because 640x480 is not what I call control of a 1920x1080
> monitor.
>
> BTW the reason for the new install is that I can't get
> vbox working right in the others (posted in alt.os.linux),
> in Slowroll I have to log-in twice each time, and all of
> them work GUI only with kernel 6.5 but no 7's.
>
>
Hi
So switch to the kms driver by uninstalling xf86-video-nouveau.

--
Cheers Malcolm °¿° (Linux Counter #276890)
Tumbleweed 20240222 | GNOME Shell 45.3 | 6.7.5-1-default
HP Z440 | Xeon E5-2695 V4 X36 @ 2.10GHz | Quadro T400/Tesla P4
up 1:19, 2 users, load average: 0.23, 0.32, 1.29

On 2/23/24 23:36, Malcolm wrote:
> On Fri, 23 Feb 2024 23:20:41 -0500
> bad sector <forgetski@_INVALID.net> wrote:
>
> <snip>
>>
>> I'm posting from Slowroll because the Tumbleweed I just installed
>> is unusable. Once I get it running I can leave it as Tumbleweed
>> or change it to Slowroll just by editing the repos to use to
>> Slowroll from that point forward.
>>
>> Booting that 'freshie', I can log-in as user and do startx
>> but the resolution is ridiculous
>>
>> # /sbin/lspci -nnk | grep -EA3 "VGA|Display|3D"
>> 06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107
>> [GeForce GT 640] [10de:0fc1] (rev a1)
>> Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1258]
>> Kernel modules: nouveau
>> 06:00.1 Audio device [0403]: NVIDIA Corporation GK107 HDMI Audio
>> Controller [10de:0e1b] (rev a1)
>>
>> So as I suspected nouveau is in control but in name only
>> because 640x480 is not what I call control of a 1920x1080
>> monitor.
>>
>> BTW the reason for the new install is that I can't get
>> vbox working right in the others (posted in alt.os.linux),
>> in Slowroll I have to log-in twice each time, and all of
>> them work GUI only with kernel 6.5 but no 7's.
>>
> Hi
> So switch to the kms driver by uninstalling xf86-video-nouveau.

It wasn't installed and I could not improve on the 640/480
resolution issue

managed to install the nvidia (Wayland) drivers so at least
for the time being I don't have to fret kernel upgrades into
the 7's and above.

On 2/23/24 09:32, Malcolm wrote:
> On Fri, 23 Feb 2024 07:58:21 -0500
> bad sector <forgetski@_INVALID.net> wrote:
>
>> Is something cooking in the vcard driver kitchen? I
>> understand nvidia has released the driver codes. So
>> I removed the nvidia driver and installed nouveau on
>> TW and Slowroll but on both of them kernel 7 still only
>> goes as far as a black screen with nothing on it, same
>> as without nouveau. At this rate when 6.5 slides off
>> the grub list both my systems go tango-uniform?
>>
> Hi
> You mean kernel 6.7.5? Nvidia has the open driver for Turing cards or
> better, there is still nouveau...

Yes I meant 6.7

This was not on my latest TW or Slowroll install
but the problem was a totally blank black screen
when trying to boot a kernel above 6.5. It's been
eating at me since!

A few minutes ago, on spec, I looked at the grub
editables and to my ASTONISHMENT the boot drive
was showing as 'hd1,gp15' instead of 'hd0,gpt15'.
I edited it to 'hd0...' and F10 booted to at least
a log-in prompt.

My hardware at the time is a 1tb ssd as sata-1
and a 2tb spinner as sata-2 or watever else it may
show up as except 1.

So continuing my hunch I ran the grub ritual in
Yast with the data drive removed. The grub arguments
now all read 'hd0,gpt15' AS THEY ALWAYS SHOULD HAVE.

I then reconnected the data drive and repeated the
exercise but the FUBAR did not repeat itself. At
this time all booted kernels get me to at least a
log-in prompt so this particuolar issue seems fixed
and was probably the result of index and config
files being read on some previous Yast-grub sessions
INSTEAD of looking at what ACTUALLY IS on the disk.

The other issue, the one of getting only a log-in prompt
with kernel 6.7 is the other thread.