new computer needs to use nomodeset=0 only an issue with F96-CE_4

[bigpup]

All other computers I have used F96-CE_4 to boot.
They boot to working desktop and get correct display using the nouveau driver.
All these computers have Nvidia hardware.
Even used the Nvidia Geforce GTX 2060 card in them.

A new computer I built is using a MSI PRO Z690-a DDR4 motherboard.
CPU i7 12700K
A Nvidia Geforce GTX 2060 card
UEFI bios is set to use the Nvidia card for graphics.
The integrated CPU graphics is disabled in UEFI bios.

When I boot this new computer it boots to a black screen.

If I add nomodeset=0 to the boot loader config entry.

It will boot to a working desktop.
However, as it should using nomodeset=0, it is using the vesa driver, and a low resolution setting.

Other newer Puppy versions will boot OK on this new computer and they use the nouveau driver.
Bookworm Pup64 10.0.2, Slacko64 8.2.1, etc.......

Looking for ideas......
ANYONE got any idea why this new computer will not use the nouveau driver when booting with F96-CE_4?

Note:
F96-CE_4 and all other Puppy versions I have tried.
Fresh installs on a USB drive, first boot, and not using a save.

[bigpup]

Update:

I have installed the NVIDIA-Linux-x86_64-525.89.02.run driver package.

Using this driver, I can get it to boot to a working desktop, with a resolution setting of 1920X1080.

However, the nouveau driver should be able to do it also, but it is not working.

[Grey]

MSI

My favorite company of all motherboard manufacturers

ANYONE got any idea why this new computer will not use the nouveau driver when booting with F96-CE_4?

New motherboards have more and more settings in UEFI. Maybe something needs to be turned on or off somewhere.

In general, somewhere on the forum there was definitely material on how to view logs with errors after the launch. However, not every version of Puppy supports this by default, perhaps you need to build F96-CE with the logs option enabled.

[rockedge]

changing the kernel and modules in F96-CE_4 to one you know works with that graphics setup might do the trick.

[charlie6]

Hi all,
here running an Acer Laptop
Acer Aspire V3-771 (version: V2.18)
Mainboard Acer VA70_HC (version: Type2 - Board Version)
• BIOS Insyde Corp. V2.18 | Date: 02/25/2013 | Type: UEFI
• CPU Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz (2 cores)
• RAM Total: 5765 MB | Used: 2601 MB (45.1%) | Actual Used: 1114 MB (19.3%)

I've had the same issue - boot to a black screen - let us say «erraticaly», i.e. sometimes at first switch on, sometimes after several switch on / switch off trials; sometimes wait a few hours after PC unplugged from electric supply ...?
So I remember I had a similar issue a few years ago and could fix it by adding the following file named 20-intel.conf - or replacing the existing one (*) - in /etc/X11/xorg.conf.d
(*) I've renamed the former as 20-intelDOT.conf

Code: Select all

Section "Device"  
   Identifier  "Intel Graphics"
   Driver      "intel"
   Option      "AccelMethod"     "uxa"
EndSection

FC96-CE_4 boots now straight on flawlessly since a few weeks !

For information here are the video stuffs specs:

01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1)
Subsystem: Acer Incorporated [ALI] GeForce 710M

# report-video
lspci: -s: Invalid bus number
RAPPORT VIDÉO fossapup64, version 9.6
Processor: Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz

X.Org X Server 1.20.13
X Protocol Version 11, Revision 0

Description de la puce:

00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09)
Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0686]
Kernel driver in use: i915
Kernel modules: i915

Requested by /etc/X11/xorg.conf:
Profondeur (bits, ou niveaux): 24
Modules à charger: glx
Pilotes à charger: intel

Examen du fichier de démarrage de Xorg (/var/log/Xorg.0.log):
Pilote chargé (et actuellement utilisé): intel
Modules chargés: dri2 fb glx libinput synaptics wacom

Rendu actuel de l'écran:
Resolution: 1600x900 pixels (423x238 millimeters)
Depth: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 4000 (IVB GT2)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 21.2.6

Monitor : card0-LVDS-1
Model : N173FGE-L23
WxH (cm) : 39x22

... les infos ci-dessus ont été également enregistrées dans /tmp/report-video
#

and

Here are the /var/log/Xorg.0.log (upon X fail) file:

to be noticed: «(EE) Segmentation fault at address 0x0» warning befor the end

end of /var/log/Xorg.0.log part (from (EE) comments)

...
[ 17.657] (II) Initializing extension GLX
[ 19.320] (II) AIGLX: Loaded and initialized nouveau
[ 19.320] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 19.320] (II) Initializing extension XFree86-VidModeExtension
[ 19.320] (II) Initializing extension XFree86-DGA
[ 19.320] (II) Initializing extension XFree86-DRI
[ 19.320] (II) Initializing extension DRI2
[ 19.321] (II) NOUVEAU(0): NVEnterVT is called.
[ 19.321] (EE)
[ 19.321] (EE) Backtrace:
[ 19.321] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5588fb9feddc]
[ 19.322] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f9d5973e3c0]
[ 19.322] (EE) 2: /usr/lib/xorg/Xorg (xf86RandR12CreateScreenResources+0x56c) [0x5588fb919b7c]
[ 19.322] (EE) 3: /usr/lib/xorg/Xorg (InitExtensions+0x6a8) [0x5588fb90c428]
[ 19.322] (EE) 4: /usr/lib/xorg/Xorg (InitFonts+0x279) [0x5588fb8a0f29]
[ 19.322] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f9d5955c0b3]
[ 19.322] (EE) 6: /usr/lib/xorg/Xorg (_start+0x2e) [0x5588fb88aaae]
[ 19.322] (EE)
[ 19.322] (EE) Segmentation fault at address 0x0
[ 19.322] (EE)
Fatal server error:
[ 19.322] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 19.322] (EE)
[ 19.322] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 19.322] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 19.322] (EE)
[ 19.322] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 19.322] (II) NOUVEAU(0): NVLeaveVT is called.
[ 19.391] (EE) Server terminated with error (1). Closing log file.

and the grub.cfg menuentry:

menuentry "Puppy/FC96_CE on sda2" {
insmod ext2
search --no-floppy --fs-uuid --set=root 68609e3f-b414-4a19-8b1b-132465be1a54
echo "Loading vmlinuz"
linux /Puppy/Kirk/vmlinuz pmedia=atahd pdrv=68609e3f-b414-4a19-8b1b-132465be1a54 psubdir=/Puppy/Kirk pfix=fsck,fsckp TZ=CET-1CEST,M3.5.0,M10.5.0/3
echo "Loading initrd.gz"
initrd /Puppy/Kirk/initrd.gz
}

Hope this could help
Charie

[vtpup]

new Asus 14x OLED laptop
6.0.12-FP (x86_64) F96-CE Radky latest
max available screen resolution = 2880x1800 120 fps
stickpup generated install to USB stick

I've had a similar problem with black screen after boot (with dash in upper left corner), while otherwise the computer seems to boot to completion (I hear the pup bark).

I just tried adding nomodeset=0 to grub.cfg, and now it boots to an 800x600 screen. I can't get higher resolution through xrandr, after boot as 800x600 is the only choice.

I'm going to try the above @charlie6 mod to substitute /etc/X11/xorg.conf.d 20-intel.conf .

I've also found a reference that there could be some difficulty related using an EFI thumdrive for a UEFI system here:

https://bbs.archlinux.org/viewtopic.php?id=259451

[vtpup]

new Asus 14x OLED laptop
6.0.12-FP (x86_64) F96-CE Radky latest
max available screen resolution = 2880x1800 120 fps
stickpup generated install to USB stick

I've had a similar problem with black screen after boot (with dash in upper left corner), while otherwise the computer seems to boot to completion (I hear the pup bark).

I just tried adding nomodeset=0 to grub.cfg, and now it boots to an 800x600 screen. I can't get higher resolution through xrandr, after boot as 800x600 is the only choice.

I'm going to try the above @charlie6 mod to substitute /etc/X11/xorg.conf.d 20-intel.conf .

I've also found a reference that there could be some difficulty related using an EFI thumdrive for a UEFI system here:

https://bbs.archlinux.org/viewtopic.php?id=259451

The @charlie6 mod to substitute /etc/X11/xorg.conf.d 20-intel.conf did not work to start X. It did however yield a console screen with the usual message about starting xwin and xoegwixard. However none of those choices worked to start X.

I'm back to starting with nomodeset=0 and only 800x600 resolution.

Any further help would be appreciated.

[vtpup]

Finally gave up, computer returned.

[AQUAR]

This puppy distro also defaults to the VESA driver on older hardware (just has the MBR way of booting) with only an Nvidea GPU in it.
Only tried FC96-CE_4 it as it was a later "fossa" effort. No such issues with fossapup64.