RV730 PRO [Radeon HD 4650] Woes
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Ok, hope you can help.
My screen resolution is 1600 by 1200 and it should be 1920 X 1080. It's OK if I am just working with text but will surely want right proportions editing images or watching videos.
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650]
is my graphics card.
Maybe important, this is the monitor: HPw2338h
Went to https://trisquel.info/en/wiki/configure-2d-and-3d-graphics-acceleration to get this discouraging news:
The radeon driver, usually listed as free software, depends heavily on a non-free firmware blob that we strip from our linux-libre kernel. Support for ATI/AMD cards is weak, with no 2D/3D acceleration and modesetting problems.
Damn those blobs!
I once had a problem like this using a toshiba rezga 42" TV and googled enough to find an xorg.conf that somebody else in the same boat had contrived with success, so the fix was pretty much as easy as copying his config and moving the original config to .old and replacing it with the other guy's.
Haven't gotten that lucky this time.
my xorg.conf as it is:
Section "Device"
Identifier "Default"
Option "GLXVBlank" "on"
EndSection
What can I do?
I am a translator!
I don't know if there is some other workaround (I doubt it) ->
you will have to downgrade your kernel. I'm using jxself's 3.10.75 (also ati crap here..) with debian 8 and it works great!
OK, if that's what I got to do.
Will an older kernel break anything I have installed? I've never rolled back a kernel.
Is this what I've got now (uname -a)
Linux three-tower.localdomain 3.13.0-49-lowlatency #83+7.0trisquel2 SMP PREEMPT Tue Apr 14 11:43:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
I am a translator!
It shouldn't. I mean, it didn't break anything on my lappy - anyway backup first! Then go for it.
cheers!
Thanks SuperTramp and all the posts on http://trisquel.info/en/forum/screen-resolution-0
I followed meydlo's suggested steps but for some reason the 3.11 kernel he got wasn't found though I had added the repository to the list. Having earlier followed the instructions to set up the http://jxself.org/linux-libre/ repository, I used apt to get linux-libre64-3.10. I had already commented out the modprobe.d references to radeon.
Also, never mentioned outsudoing myself using addgroup -G wireshark to get wireshark running earlier but as a result I know about the user grub and have his password handy. Rebooted and chose the 3.10 kernel and voila! 1920 X 1080 resolution looks kind of strange after a couple of weeks at 1600 X 1200. But I'll get used to it. ^v*
Is the best way to remove the other kernels via the synaptic?
I am a translator!
De nada Geshmy..
use synaptics or rm them by terminal..it's the same I guess..
p.s- on debian 8 I just needed to install the jxself 3.10.76 and that's all. Didn't need to mousepad the modprobe.d to comment anything. But I did change my grub with
GRUB_DEFAULT="1>2"
GRUB_TIMEOUT=0
and then update-grub
so the jxself kernel boots automatically an without hesitation..
cheers!
I followed meydlo's suggested steps but for some reason the 3.11 kernel he got wasn't found though I had added the repository to the list.
You should not do that. Just grab the .deb you want from http://packages.trisquel.info/toutatis-updates/linux-image and install it (e.g., with 'dpkg -i' or with GDebi). meydlo pretends that the version 3.11.0-20 is the last version that allows him to get a correct resolution. However, I doubt security fixes (the last number) can introduce such a regression. I would therefore take http://packages.trisquel.info/toutatis-updates/amd64/linux-image-3.11.0-26-generic/download
Is the best way to remove the other kernels via the synaptic?
It is a good way to remove kernels. However I would advise against removing all kernels but the one that is supposed to work. Especially without testing it first!
To test it, you can start by disabling GRUB's password, which is useless according to its developers ( https://www.gnu.org/software/grub/manual/grub.html#Security ). To do so, make all lines of /etc/grub.d/01_PASSWORD start with "#". You need administrative rights to edit that file (here with GEdit):
$ gksu gedit /etc/grub.d/01_PASSWORD
You then need to run the following command for the change to be applied:
$ sudo update-grub
When rebooting, you will then be able able to choose, at GRUB, the "advanced options" (or something similar) and to boot the kernel you have just installed.
If you can then get the correct resolution, tell us. We can then explain how modifying GRUB_DEFAULT in /etc/default/grub can turn the kernel the default.
Oh, yes as far as I know it found the correct resolution on it's own, 1920 X 1080 is correct according to Hp specs for this monitor.
Take a look at https://www.gnu.org/software/grub/manual/grub.html#Simple-configuration to learn how to boot on the 3.11 (or 3.10) kernel by default. The variables, which are mentioned, are in /etc/default/grub, which must be edited (here with GEdit) with administrative permissions:
$ gksu gedit /etc/default/grub
The easiest way to go may be to choose as the default kernel the last one that was booted:
GRUB_DEFAULT="saved"
GRUB_SAVEDEFAULT="true"
For the modifications to be taken into consideration, you must then execute:
$ sudo update-grub
Thanks For your help!
I stayed with the 3.10 kernel for now. Maybe upgrade to the 3.11 later.
I tried to keep the grub password, yeah, a nuisance but quirky, I like quirky.
But Magic Banana, I did your steps re grub a little out of order, my grub.conf file reads
GRUB_DEFAULT="saved"
GRUB_SAVEDEFAULT="true"
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
and I did $ sudo update-grub
then rebooted and was right back into the 3.13 kernel with fat resolution.
So I rebooted again to the 3.10 kernel and made all lines of /etc/grub.d/01_PASSWORD start with "#" did the update-grub again
rebooted and this time 3.10 kernel and proper resolution happened by default so it's good. I guess it's all dependent on a passwordless grub?
Since I have Fedora 21 and Centos 7 installed on the hard drive also, could I do grub-update while in either of those to have that grub would handle bootups after that?
I have no reason to do that, just wondering.
A more important question might be is grub needed in each OS?
then rebooted and was right back into the 3.13 kernel with fat resolution.
It may be that the last kernel that was used was not saved (since your GRUB was not configured in this way) and, when rebooting for the first time after the reconfiguration, GRUB chose the latest kernel, i.e., one more reboot where you would have chosen the 3.10 kernel and everything would have been OK afterwards. It is just a guess though.
Since I have Fedora 21 and Centos 7 installed on the hard drive also, could I do grub-update while in either of those to have that grub would handle bootups after that?
The configuration in the file /etc/default/grub of the system at work would then be used.
A more important question might be is grub needed in each OS?
You have one single bootloader for the whole computer. It usually is in the MBR of the disk.
> It may be that the last kernel that was used was not saved
That seems like a good bet, I didn't think to try rebooting twice.
> You have one single bootloader for the whole computer. It usually is in the MBR of the disk.
So, are you saying that that command writes over previous contents in the MBR so for instance if in Fedora right now I did $ sudo update-grub, it would write over the Trisquel grub-update result I'm using now? And is it possible to install two OSes without bootloaders and depend on a third with grub to do the os-probe and be able to configure boot up options for all three?
Maybe even install grub as a stand alone, then do subsequent installs in a way that doesn't disturb the installed grub, and every time you boot it does os-probe and updates itself. I did see the man pages for grub numbered into the 30s so maybe you can even make it stand on it's head and spit green nickels if you know how.
I didn't think to try rebooting twice.
Rebooting once, but manually choosing version 3.10 this one time, would have been enough if I guessed right (what is not sure at all).
So, are you saying that that command writes over previous contents in the MBR so for instance if in Fedora right now I did $ sudo update-grub, it would write over the Trisquel grub-update result I'm using now?
As far as I understand (but I am no expert and exclusively run Trisquel): yes.
And is it possible to install two OSes without bootloaders and depend on a third with grub to do the os-probe and be able to configure boot up options for all three?
I am not sure you can install an OS and not install a bootloader with it. As far as I remember (that was more than 10 years ago), installing Windows XP after GNU/Linux was deleting GRUB... and Windows' bootloader, which you never see, only boots Windows. At least, that is what I understood. But, again, I am no expert.
EDIT:
Thinking a little more, it might actually be possible. Remembering my installs of Gentoo GNU/Linux (still more than 10 years ago), the bootloader was the last thing you were installing before rebooting into the system you just built. It still is the case: https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation
I guess that one could skip that last step, reboot into a previously installed system (GRUB would not know of the new one) and run 'update-grub' from there so that the new system is discovered and added to GRUB's entries. That said, most installers (with Gentoo, the user is the installer!) such as Trisquel's do not give you a choice. They install a bootloader. The question is: can you remove it afterwards (I mean remove its files, not what is in the MBR) in all systems but one? Apparently Synaptic would let me remove GRUB's packages without a warning. But I did not proceed because I only have Trisquel installed (not to mention that I am a coward!).
cool, thanks for clarification.
- Vous devez vous identifier ou créer un compte pour écrire des commentaires