vanilladpup 10.0.30 issues

[Clarity]

Hello @dimkr. I downloaded today's v10.0.30 ISO file to the SG2D USB disk's /BOOTISOS folder, along with a fresh copy of the v9.2.17 for a functional comparison.

I ask: Did you see my post here?
My reason for asking is that I cannot get v10 ISOs to behave shortly after boot. Seems that after FirstRUN is run all Menu apps/services dont run when clicked.

So that you understand my actions:

• I download the ISO file directly to the USB

• I always hit the Enter-key of the initial SG2D Menu screen

• SG2D, then, presents the ISOs in a list at the bottom of the listing

• Each VDPup distro boots to desktop when selected

• NO, stanza changes are taken upon booting for any of your PUPs; I merely hit the enter-key when the PUP presents its menu

• V9 distros work as one expects upon desktop use and navigations

• V10s desktop apps become unresponsive after a few moments with NO errors indicated. Thus, I cannot open a Geany or a terminal or ...

It maybe my test PC hardware (an i5 intel). Later today, if no feedback, I will try running it within a VM to see if the problem can be seen there, as well. (I already know that v9s ISO files boot and run well within QEMU-KVM as well as on bare-metal.)

Please advise

[dimkr]

@Clarity I don't know how this happened, but you're using the wrong kernel. Probably your boot loader is misconfigured?

EDIT: whoops, looks like the Debian kernel has been bumped to 5.19.11, and now dpup tracks Debian kernels.

EDIT 2: can you share the output of dmesg and more details about the hardware, especially exact CPU and GPU models?

[Clarity]

As noted on v10s booting, I get to desktop but the system's ability to launch apps is non-responsive. CAnnot access its files or capture DMESG.

BIOS.jpg (31.82 KiB) Viewed 1514 times

If you feel it would help, I could send a v9.2.17 bare-metal capture of DMESG (yet I know v9 and v10 are different distros) For example, Ctrl-Alt-Bkspace does not take me to the system console as it locks me in a black screen with a mouse pointer which has nothing to click that responds. Only available thing that works on this mouse black-screen is the PC's power-button which sends a bark-bark and then shuts down.

Anything else you feel would be helpful, I will provide.

BTW: The other save-sessions shown during boot in the picture,above, were captured by doing the following:

1. Boot to desktop

2. Immediately click to leave before doing ANYTHING

3. Allow system to save its state (session)

4. REbooting each time to see if it had circumvented the problem

But, taking that approach did not allow a reboot with the session to get around the problem where responds to program activation worked.

I could ONLY get Menu>Leave to work by doing that. If I waited a few moments on desktop, Leave will NOT launch to desktop.

Thus, your v10s distros is detecting something moments after booting or running FirstRUN which leads to this unresponsiveness.

[dimkr]

@Clarity Are you testing 10.0.x in a virtual machine? If yes, it has known limitations in a VM, and that's a very bad way to test it.

[Clarity]

@Clarity Are you testing 10.0.x in a virtual machine? ...

As explained, I have the same results either way, VM or bare-metal. v10 cannot focus any applications upon FirstRUN completion initially discovered in bare-metal boot and, also, verified in the VM shown, above.

Hope I have been clear in what has been found in the tests of "official" v9s versus v10s, available. Namely, a working desktop booting v9s along with the distro's apps, while v10s do not yield applications to run on desktop including the inability to get system to power off within desktop (Menu>Leave) and NO ability to Ctrl-Alt-Bksp to a console to power off.

[esos]

Booting FromISO v-10.0.31 and v-10.0.24 work ok using G4D on my PC with persistence (wifi,youtube, pulseaudio).
The only problem the display-resolution wont change.

[dimkr]

The only problem the display-resolution wont change.

What did you use to change it? Have you tried the graphics wizard?

[bigpup]

Booting FromISO v-10.0.31 and v-10.0.24 work ok using G4D on my PC with persistence (wifi,youtube, pulseaudio).
The only problem the display-resolution wont change.

What resolution are you trying to set it to?

What is the graphics hardware?
That could also be a clue to fix.

[esos]

I see over the graphics wizard with so many options and no matter I choosed it will stay by default resolution 1920x1080
The resolution for my tv-monitor suppose to be 1440x900

VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM]

Host bridge
• Advanced Micro Devices, Inc.
• VendorID=AMD/ATI RD9x0/RX980 Host Bridge
• VendorID=1002 DeviceID=5a14 Rev=02

IOMMU
• Advanced Micro Devices, Inc.
• VendorID=AMD/ATI RD890S/RD990 I/O Memory Management Unit IOMMU
• VendorID=1002 DeviceID=5a23

PCI bridge
• Advanced Micro Devices, Inc.
• VendorID=AMD/ATI RD890/RD9x0 PCI to PCI bridge PCI Express GFX port 1
• VendorID=1002 DeviceID=5a17
• Kernel Driver=pcieport

PCI bridge
• Advanced Micro Devices, Inc.
• VendorID=AMD/ATI RD890/RD9x0/RX980 PCI to PCI bridge PCI Express GPP Port 0
• VendorID=1002 DeviceID=5a18
• Kernel Driver=pcieport

[dimkr]

@esos Can you share the output of wlr-randr? Maybe your monitors run at different refresh rates, and both can do 60 Hz only when the TV is at 1920x1080.

[esos]

HDMI-A-1 "Samsung Electric Company SAMSUNG 0x00000001 (HDMI-A-1)"
Physical size: 160x90 mm
Enabled: yes
Modes:
720x400 px, 70.082001 Hz
640x480 px, 59.939999 Hz
640x480 px, 60.000000 Hz
640x480 px, 66.667000 Hz
640x480 px, 72.808998 Hz
640x480 px, 75.000000 Hz
720x480 px, 59.939999 Hz
720x480 px, 60.000000 Hz
800x600 px, 60.317001 Hz
800x600 px, 72.188004 Hz
800x600 px, 75.000000 Hz
832x624 px, 74.551003 Hz
1024x768 px, 60.004002 Hz
1024x768 px, 70.069000 Hz
1024x768 px, 75.028999 Hz
1280x720 px, 59.939999 Hz
1280x720 px, 60.000000 Hz
1152x864 px, 75.000000 Hz
1280x800 px, 59.910000 Hz
1360x768 px, 60.014999 Hz
1280x960 px, 60.000000 Hz
1440x900 px, 59.901001 Hz
1440x900 px, 74.984001 Hz
1280x1024 px, 60.020000 Hz
1280x1024 px, 75.025002 Hz
1680x1050 px, 59.882999 Hz
1600x1200 px, 60.000000 Hz
1920x1080 px, 23.976000 Hz
1920x1080 px, 24.000000 Hz
1920x1080 px, 29.969999 Hz
1920x1080 px, 30.000000 Hz
1920x1080 px, 59.939999 Hz
1920x1080 px, 60.000000 Hz (preferred, current)
Position: 0,0
Transform: normal
Scale: 2.000000

[dimkr]

@esos Are you sure the native resolution is 1440x900? According to this output, the native resolution is 1920x1080. Also, do you use multiple monitors? If yes - do you use a 60 Hz refresh rate on the other monitor(s)?

[esos]

Maybe I was not correctly explain.
The first booting of any Linux distros I will get always the default resolution 1920x1080. I can not use this resolution (too big) not even see the taskbar.
The suitable resolution is 1440x900.
Unfortunately v.10 will not allow me to change the resolution what I need.

No, I use only one tv-monitor

[dimkr]

Does wlr-randr --output HDMI-A-1 --mode 1440x900@59.901001 --scale 1 work?

[Clarity]

@esos & @dimkr. I seemed to remember a post that I saw awhile ago where @01micko gave a member some instructions on a TV setting that mitigates this problem that @esos is facing.

I cant find it, but was essential on a TV that I use to have before it died. This step for these TVs would benefit if it is made plain.

This means that you may not be fighting a distro problem, rather, this is a general hardware problem requiring a user environmental setting.

OR MAYBE, outside of the scope of this thread, the forum needs an area to discuss these kind of monitor issues since HDMI/DP is becoming the mainstay for effective screening of what we do in development and entertaining, especially in home use.

P.S. I am having the same issue reported a week ago where the v10 ISO file booting to bare-metal will, after desktop arrival, cease to respond within a minute/2 and will not allow applications to run via any mouse clicks. No shutdowning, no editing, no switching terminals, no ... just dead requiring hard-stop.

A recommendation to provide useful info would be appreciated.

[dimkr]

@Clarity Are you using the JWM flavor or the dwl flavor? Also, have you tried to press any key on the keyboard - maybe the screen is locked.

[esos]

@dimkr
For v10.0.24 it changed to suitable resolution 1440x900 but after reboot I got the default again 1920x1080.
For v10.0.31 it changed to something else. The display showed up only about 40% from the entire screen, the rest 60% just black/blank.