Bionicpup32 8.0 fails to change screen resolution

[Kjellinux]

So, the trials begin. I downloaded BionicPup32 8.0 and created a bootable USB. Next I connected the USB to my test rig, an Acer Aspire 3100 with 512MB RAM. It booted without problems and displayed the QickSetup first-run settings screen. The current/default setting was 800x600. I checked the box Run Video Wizard and tried using the top two options in the Xorg Video Wizard to change the resolution to 1280x800, but it remained at 800x600.

I searched the forum for "changing screen resolution", but couldn't find anything useful. Any advice on how I can proceed?

[bigpup]

Need some info.
menu->System->Pup-Sysinfo->Devices->Display->Video-info

Post the information it gives.
I need to see what is providing graphics and what driver is being used.

Also in a terminal
enter:

Code: Select all

xrandr

Is the resolution you want listed?

[Kjellinux]

@bigpup

I tried to follow your instructions, but I ran into some problems. I manage to connect to Internet (fixed but not wireless), but there seems to be no browser. The icon is there, but when I click it, nothing happens.

menu->System->Pup-Sysinfo->Devices->Display->Video-info

This generates output that I can copy into a text editor, but I don't know how to pass it on, since I don't have a browser.

Also in a terminal
enter:

Code: Select all

xrandr

Is the resolution you want listed?

No, the only resolution listed there is 800 x 600.

So far I'm running the OS from a USB.

[bigpup]

menu->System->Pup-Sysinfo->Devices->Display->Video-info

This generates output that I can copy into a text editor, but I don't know how to pass it on, since I don't have a browser.

Can you tell me what driver is being used? (driver loaded)
What the graphics hardware is?

xrandr in terminal
the only resolution listed there is 800 x 600

That is strange.
It should list more resolutions.

[bigpup]

but I ran into some problems. I manage to connect to Internet (fixed but not wireless), but there seems to be no browser. The icon is there, but when I click it, nothing happens.

This is clasic problems you would have if the install of Bionicpup32 8.0 was a bad install.
It does happen, sometimes.

I would do a fresh new download of the Bionicpup iso file.
Store this iso on some other drive, than the USB you want to install on.
Delete the install on the USB.
Make a fresh new install using the new downloaded iso.

If you are installing to a USB that has a windows format (fat32) and Windows used it.
Good chance the file system is fragmented and that can mess up the install.
Best if you could do a completely new format of the USB partition.
Than install Bionicpup to it.

How exactly are you doing the install to USB?
That can be an issue.

[one]

but I ran into some problems. I manage to connect to Internet (fixed but not wireless), but there seems to be no browser. The icon is there, but when I click it, nothing happens.

This is clasic problems you would have if the install of Bionicpup32 8.0 was a bad install.
It does happen, sometimes.

[...]
How exactly are you doing the install to USB?

@Kjellinux
Now that you have three different threads running it's time to answer @bigpup 's question ...

[Kjellinux]

@bigpup

This is clasic problems you would have if the install of Bionicpup32 8.0 was a bad install.
It does happen, sometimes.

I wouldn't be the least surprised if it has happened to my current install...

I would do a fresh new download of the Bionicpup iso file.

That sounds like a good idea.

If you are installing to a USB that has a windows format (fat32) and Windows used it.
Good chance the file system is fragmented and that can mess up the install.

It has definitely been used with a Windows machine.

How exactly are you doing the install to USB?
That can be an issue.

I downloaded it to a Windows machine and used Balenaetcher to create the bootable USB.

I guess my second attempt will be to use a Linux machine. The test rig is currently running Lubuntu and I have another machine running Linux Mint.

Recommendations on a suitable program to create a bootable USB are welcome.

[Kjellinux]

@one

@Kjellinux
Now that you have three different threads running it's time to answer @bigpup 's question ...

I had to leave the computers for a while to perorm some civic duties (Covid vaccin, dose 2/2). No side effects so far.

Since my first thread about choice of distributions began to divert to my attempts to get a particular distribution running, I felt it was better to start dedicated threads to the particular problems I encounterd.

All the help I'm getting is much appreciated! Eventually I hope I will have BionicPup32 8.0 up and running.

[williams2]

If you are using the vesa driver, the number of resolutions will be limited.

If you are running, for example, a nvidia or radeon driver, but it does not start properly and fallsback to vesa, the number of resolutions will be limited.

What error messages are there in /tmp/xerrs.log /var/log/Xorg.0.log ?

grep EE /tmp/xerrs.log /var/log/Xorg.0.log

grep WW /tmp/xerrs.log /var/log/Xorg.0.log

I have a desktop that works properly using the nvidia driver in XenialPup64
but falls back to the vesa driver in BionicPup64.

[bigpup]

I downloaded it to a Windows machine and used Balenaetcher to create the bootable USB.

I guess my second attempt will be to use a Linux machine. The test rig is currently running Lubuntu and I have another machine running Linux Mint.

Recommendations on a suitable program to create a bootable USB are welcome.

Using Windows is OK, but Balenaetcher seems to have problems, sometimes.
People report better luck using Rufus Installer:
https://rufus.akeo.ie/

Defraging the partition you are going to download the Bionicpup32 iso to, would be a good idea, before you do the download.
Do you know how to run Windows defrag program to defrag?

[Kjellinux]

@bigpup

Can you tell me what driver is being used? (driver loaded)
What the graphics hardware is?

According to the specifications it's an ATI Radeon® Xpress 1100.

How can I find out what driver is being used?

[bigpup]

This should provide the driver in use info.
menu->System->Pup-Sysinfo->Devices->Display->Video-info

[Kjellinux]

@bigpup

This should provide the driver in use info.
menu->System->Pup-Sysinfo->Devices->Display->Video-info

Again, it output a lot of text, but I hope the following will include the most relevant:

Chip description:
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc [AMD/ATI] RS482M [Mobility Radeon Xpress 200] [1002:5975]
Subsystem: Acer Incorporated [ALI] Device [1025:009f]
Kernel modules: radeon

Driver loaded (and currently in use): ati
Loaded modules: dbe ddc evdev fb fbdevhw glx int10 shadow synaptics vbe vesa

[bigpup]

That is the info needed.

It is using the radeon ati driver.
That should be providing a lot of different resolution options.

I would definitely do a delete and completely fresh new install of Bionicpup32 8.0

Even if it dropped down to vesa mode, It still should provide a bunch of resolution options.

[Kjellinux]

@bigpup

I would definitely do a delete and completely fresh new install of Bionicpup32 8.0

That will indeed be my next step. And this time I will verify the checksum as well. I just have to figure out how first...

[OscarTalks]

It is difficult to advise because only you have your specific hardware in front of you, but:-

There are 2 drivers specifically for radeon/ati graphics cards, one is called radeon and the other is called ati. The ati one is much smaller and more basic than the radeon one, but your system has automatically loaded the ati one in your test rig. It is quite likely that the radeon one would not work even if you forced it to load.

However you do have other options which might give you better screen resolutions.
You should try switching to either the vesa or modesetting graphics driver. These are generic.
To do this, in the shutdown dialog window, click the Exit to Prompt button
From there you type xorgwizard and press enter.
Use the keyboard arrows and carriage return (enter) to navigate the options for "set video driver"
When you have gone through the selection and "OK" steps,
You then type xwin and press enter to see if you can get back to X with the different driver loaded.
If one does not work, go back through the xorgwizard > selection > xwin steps again to try another.

[bigpup]

Just to add to using xorgwizard.

You may have to type in the driver name in the selection slot.
It's drop down list, may or may not, have the driver in the list.

[Kjellinux]

@OscarTalks @bigpup

You should try switching to either the vesa or modesetting graphics driver.

This I will most likely try out later on. Right now I have Precise Light 5.7.2 up and running (with the correct screen resolution from start). I just need to get a browser installed somehow.

[Kjellinux]

@bigpup

Need some info.
menu->System->Pup-Sysinfo->Devices->Display->Video-info

Post the information it gives.

VIDEO REPORT: BionicPup32, version 19.03
Processor: Mobile AMD Sempron(tm) Processor 3500+

X.Org X Server 1.19.6
Release Date: 2017-12-20

Chip description:
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] [1002:5975]
Subsystem: Acer Incorporated [ALI] Device [1025:009f]
Kernel modules: radeon

Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1280x800
Modules requested to be loaded: dbe

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): ati
Loaded modules: dbe ddc evdev fb fbdevhw glx int10 shadow synaptics vbe vesa

Actual rendering on monitor:
Resolution: 800x600 pixels (333x212 millimeters)
Depth: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 10.0.0, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 20.0.8

...the above also recorded in /tmp/report-video

Also in a terminal
enter:

Code: Select all

xrandr

xrandr.png (26.31 KiB) Viewed 1303 times

[Kjellinux]

@williams2

What error messages are there in /tmp/xerrs.log /var/log/Xorg.0.log ?

grep EE /tmp/xerrs.log /var/log/Xorg.0.log

grep WW /tmp/xerrs.log /var/log/Xorg.0.log

EE.png (101.98 KiB) Viewed 1303 times

WW.PNG (73.73 KiB) Viewed 1303 times

[Kjellinux]

@OscarTalks

There are 2 drivers specifically for radeon/ati graphics cards, one is called radeon and the other is called ati. The ati one is much smaller and more basic than the radeon one, but your system has automatically loaded the ati one in your test rig. It is quite likely that the radeon one would not work even if you forced it to load.

How could I force the radeon driver to load?

However you do have other options which might give you better screen resolutions.
You should try switching to either the vesa or modesetting graphics driver. These are generic.
To do this, in the shutdown dialog window, click the Exit to Prompt button
From there you type xorgwizard and press enter.
Use the keyboard arrows and carriage return (enter) to navigate the options for "set video driver"
When you have gone through the selection and "OK" steps,
You then type xwin and press enter to see if you can get back to X with the different driver loaded.
If one does not work, go back through the xorgwizard > selection > xwin steps again to try another.

I tried both vesa and modesetting but I'm still stuck with 800x600.

[Jafadmin]

If this LT has 512 meg of RAM, the specs say up to 128 meg can be shared as video memory.
My guess is that this LT doesn't have the right club for this tee. Add another 256 meg of ram.

[williams2]

Sometimes the monitor's builtin EDID Extended Display Identification Data fails.
But usually there is a WW warning message of a checksum failure, which you don't have.

You do have "VESA No valid modes left" WW messages.
I suspect the drivers have limited support for your older hardware.
I have a desktop that uses the Vesa driver because the Nvidia driver doesn't start.

On this machine, grep Modeline /var/log/Xorg.0.log list 122 lines, each line looking like this:

Code: Select all

[    40.250] (II) RADEON(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync -vsync (67.5 kHz eP)

The following shows that my machine is using the Radeon driver:

Code: Select all

grep 'loading driver' /var/log/Xorg.0.log
[    34.739] 	loading driver: radeon

[OscarTalks]

I would not recommend trying to force the radeon driver to load. It is probably incompatible with the older hardware which is why it did not get loaded automatically. There are options within xorgwizard to choose drivers from a list or nominate one by name (the xorgwizard has changed over time in Puppy and I am not sure how the one in Bionic32 is), but beware you don't end up in a black screen that you can't find your way out of.

I know you have had other suggestions, but Dpup Stretch would be a good Puppy for you to try. It uses Debian Stretch packages so it is from around the same era as Bionic. It is 32bit. People have reported that it works well in older hardware. Use the version with the older kernel (k4.1_ISO rather than the k4.19_ISO) for older hardware such as your test rig. I would be interested to know if it offers you better screen resolutions. Also it has Palemoon browser rather than Light browser so interesting to compare. I run a remastered version as one of my everyday Puppies and I am something of a fan of reviving older hardware too.
http://smokey01.com/radky/Woof/dpup32.htm

[Kjellinux]

@Jafadmin

If this LT has 512 meg of RAM, the specs say up to 128 meg can be shared as video memory.
My guess is that this LT doesn't have the right club for this tee. Add another 256 meg of ram.

I 'm testing three Puppy versions in parallel, BionicPup32 8.0, Slacko 6.3.2 and Precise Light 5.7.2. I have created bootable USBs for all three in exactly the same way. BionicPup32 8.0 is the only one with this issue. The other two boot into the right resolution (1280x800) automatically. If RAM was the issue, I would expect the other two to cause the same problem.

[Kjellinux]

@williams2

Sometimes the monitor's builtin EDID Extended Display Identification Data fails.
But usually there is a WW warning message of a checksum failure, which you don't have.

I 'm testing three Puppy versions in parallel, BionicPup32 8.0, Slacko 6.3.2 and Precise Light 5.7.2. I have created bootable USBs for all three in exactly the same way. BionicPup32 8.0 is the only one with this issue. The other two boot into the right resolution (1280x800) automatically. If the monitor's builtin EDID Extended Display Identification Data was the problem, I would expect all three versions to have the same problem, but it's only BionicPup32 8.0 that causes this problem.

You do have "VESA No valid modes left" WW messages.
I suspect the drivers have limited support for your older hardware.

Again, I would expect that to cause the same problem with all three versions. On the other hand, the monitor's builtin EDID is in the hardware, so it must be the same for all three versions, whereas VESA is in the software. Could it be that BionicPup32 8.0 does something differently?

The following shows that my machine is using the Radeon driver:

Code: Select all

grep 'loading driver' /var/log/Xorg.0.log
[    34.739] 	loading driver: radeon

When I run the same command I get no output.

grep.png (12.71 KiB) Viewed 1400 times

[Kjellinux]

@OscarTalks

I would not recommend trying to force the radeon driver to load. It is probably incompatible with the older hardware which is why it did not get loaded automatically. There are options within xorgwizard to choose drivers from a list or nominate one by name

I managed to load the radeon driver through the nominate by name option in xorgwizard. There was no improvement.

beware you don't end up in a black screen that you can't find your way out of.

Been there! The first few times I managed to fix things with a hard reset, but now I seem to have killed the Exit to Prompt option for good...

I know you have had other suggestions, but Dpup Stretch would be a good Puppy for you to try. It uses Debian Stretch packages so it is from around the same era as Bionic. It is 32bit. People have reported that it works well in older hardware. Use the version with the older kernel (k4.1_ISO rather than the k4.19_ISO) for older hardware such as your test rig. I would be interested to know if it offers you better screen resolutions. Also it has Palemoon browser rather than Light browser so interesting to compare.

I will add it to my list of versions to test.

I am something of a fan of reviving older hardware too.

I don't know if I qualify as a fan, but I se a value in giving older machines a second life. And I like the challenge of finding out just how old hardware can still be used.

[bigpup]

Again, I would expect that to cause the same problem with all three versions. On the other hand, the monitor's builtin EDID is in the hardware, so it must be the same for all three versions, whereas VESA is in the software. Could it be that BionicPup32 8.0 does something differently?

Bionicpup32 8.0 is using a different Linux kernel.
The Linux kernel is mainly providing hardware support.

Sure, some older hardware is supported, but not every possible ones.

Stop thinking, any Puppy version is going to work, on every possible computer hardware, setup.
Not going to happen.
That is why, there is always, several versions of Puppy offered and kept active.

There has been some luck, in replacing the Linux kernel, to getting stuff working better.
Going from a kernel series lower or higher than the one in the Puppy version.
Newer kernel series 5 for very new hardware.
Series 4 or 3 for older or very old hardware.
Even the version, in a kernel series, can affect hardware support.

[Kjellinux]

@bigpup

Bionicpup32 8.0 is using a different Linux kernel.

Code: Select all

uname -r

returns "4.9.163-lxpup-32-pae".

There has been some luck, in replacing the Linux kernel, to getting stuff working better.

This will definitely be my next thing to test.

Is there some utility in Puppy that can be used for this (there seem to be utilities for just about everything)? Are there some step by step instructions available on how to replace the kernel?

A tempting first thought would be to check out what kernels the other two versions use (this I will do regardless) and try one of them, but the name of the existing kernel (especially the "lxpup-32" part) suggests I need to chose from a limited set that BionicPup32 8.0 can use. If so, where can I find out which kernels can be used?

[williwaw]

(especially the "lxpup-32" part) suggests I need to chose from a limited set that BionicPup32 8.0 can use. If so, where can I find out which kernels can be used?

Pee bee is the developer of lxpup and bionic32? the name may just be an artifact of shared development. Maybe ask in the bionic32 thread?
viewtopic.php?f=115&t=165

alternately, you might get by switching with any pup. no utility that I am aware of , but its not very hard. A new topic asking how to could be useful to others