Trisquel 7.0 flash disk and AMD Raedon/Limited Resolution

6 replies [Last post]
Bertel

I am a member!

Offline
Joined: 08/30/2010

With the following hardware, id display: VGA compatible controler RV380/M24C (Mobility Radeon X600 SE) and system settings, windows manager 'Metacity' I get this display resolutions:
Trisquel 6.01: 1280x800, 1289x720, 1152x768, 1024x768 and 800x600
Trisquel 7.0 : 1024x768 and 800x600

Trisquel 6.01 uses 'Gallium 0.4 on llvmpipe (LLVM 0x300)' as graphical driver, while Trisquel 7.0 uses 'VESA: C24' as graphical driver.

Till now I use Trisquel 7.0 on a flash disk but what about that driver if I install Trisquel 7.0 on my hard disk? What do you think, do I have to wait for the right graphical driver or can I add a # in front of the blacklist line in /etc/modprobe.d/disable-radeon.conf (than 'update-initramfs -u', both these actions as root or using sudo) to fix the resolution?

Legimet
Offline
Joined: 12/10/2013

Do you get a stretched screen? That's what happened to me on a laptop with Radeon and Trisquel 6 after upgrading to the saucy lts enablement stack. I'm going to test with Trisquel 7.0 soon.

Michał Masłowski

I am a member!

I am a translator!

Offline
Joined: 05/15/2010

Newer Radeon X driver versions require KMS, I think the one in 7.0
does. If you have the radeon kernel module disabled, there will be no
KMS and hence the VESA driver will be used, giving only 1024x768 and
800x600.

Enable the driver by commenting the blacklist line and running
update-initramfs -u. It might break resume from suspend, it should
otherwise work on pre-R600 cards. Newer ones might get a black screen.

Bertel

I am a member!

Offline
Joined: 08/30/2010

@ Legimet
Trisquel 7.0 showed me a stretched screen.

@ Michal Maslowski
Thanks for your explanation.

I enabled the driver by commenting the blacklist line.
Updating initramfs produced the folowing warnings:
update-initramfs: Generating /boot/initrd.img-3.13.0-30-generic
cryptsetup: WARNING: failed to detect canonical device of overlayfs
cryptsetup: WARNING: could not determine root device from /etc/fstab
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays
but yes, restarting and it did the job !

Legimet
Offline
Joined: 12/10/2013

Good to know that it worked, I will try this on the laptop. And thanks Michał Masłowski.

Should we file a bug report about this, to un-blacklist radeon?

Michał Masłowski

I am a member!

I am a translator!

Offline
Joined: 05/15/2010

It will make a black screen and no graphics on some newer GPUs (Debian
disables it for R600 and later if the firmware is not provided,
h-node.org has reports of newer cards having no graphics on Parabola).
A recent kernel change worsened it. On my RS690 laptop (older than
R600), modesetting without firmware breaks resume from suspend.

I think we should leave it blacklisted and document how to enable it. A
longer term solution would be to enable it only on specific GPUs, revert
driver changes breaking it on newer GPUs or replace the firmware.

Legimet
Offline
Joined: 12/10/2013

I think the installer could detect which GPU you have and decide. But for now, we should just document it.