Display resolution of Sabayon 19.03 in Flash drive based live session

Issues Related to Hardware (Sound, Video, Printers, Scanners, Webcams, Touchpads, Keyboards, Sensors, Drives, GRUB, etc.)

Moderator: Moderators

Post Reply
mmmmna
Baby Hen
Posts: 2
Joined: Sun Feb 28, 2010 2:32

Display resolution of Sabayon 19.03 in Flash drive based live session

Post by mmmmna » Thu Oct 10, 2019 18:35

Hey all.

Testing Sabayon ATM. New to Sabayon, been using various Linux distros since 1999.

Currently booting the live session on an old eMachines AMD64X2 and 4G ram.

Live session boots only in Safe mode, and the display resolution isn't good. I get something like 720 x 640 in the live safe mode session.

Installed is Ubuntu Mate 18.04, it is set at 1680 x 1050.

Important details:
System has onboard nVidia graphics (GeForce 6100 nForce 405, part of the whole mainboard chipset) but nothing is attached to that port.
System has add-in ATI card where my display is attached via that cards DVI port.

In Ubuntu, LSHW reports the ATI graphics as follows:

Code: Select all

*-display
             description: VGA compatible controller
             product: RV710 [Radeon HD 4350/4550]
             vendor: Advanced Micro Devices, Inc. [AMD/ATI]
             physical id: 0
             bus info: [email protected]:02:00.0
             version: 00
             width: 64 bits
             clock: 33MHz
             capabilities: vga_controller bus_master cap_list rom
             configuration: driver=radeon latency=0
             resources: irq:27 memory:e0000000-efffffff memory:fdee0000-fdeeffff ioport:bc00(size=256) memory:c0000-dffff
I'm looking to set the display resolution much higher while I'm in the live session.

Fitzcarraldo
Sagely Hen
Posts: 8195
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: Display resolution of Sabayon 19.03 in Flash drive based live session

Post by Fitzcarraldo » Sun Oct 13, 2019 10:49

What video driver does /var/log/Xorg.0.log indicate is being loaded? Are there any error messages in /var/log/Xorg.0.log that might indicate what is happening?

Post Reply