[SOLVED] AMD hd 7670M, screen shows strange lines on boot.

Ztcoracat · 03-02-2014, 09:17 PM

Quote:

If the graphical corruption is UEFI related, what would I have to do to convert OpenSUSE to boot with UEFI off

Go into the BIOS and disable the secure boot.
http://www.maketecheasier.com/disabl...-in-windows-8/

If that doesn't work than maybe colorpurple21859 or mostlyharmless will know another way.

http://www.linuxquestions.org/questi...ed-4175447533/
http://en.opensuse.org/openSUSE:UEFI

colorpurple21859 · 03-02-2014, 09:46 PM

this might help
https://aps2.toshiba-tro.de/kb0/TSB2B03F30002R01.htm

AndrewAmmerlaan · 03-03-2014, 02:53 AM

There is good news and there is bad news.

The good news is I am sure this is UEFI related because with UEFI turned of the mageia live cd does not show graphical corruption.

The bad news is that somehow during the processes of testing the live cd in non-UEFI mode, the grub got removed or broken, even worse I can not recover grub from the opensuse live cd through yast, I am trying to recover grub using the opensuse dvd.

Quote:

Go into the BIOS and disable the secure boot.

Just disabling secure boot is not enough, I needed to change boot mode from UEFi to CSM

colorpurple21859 · 03-03-2014, 04:38 AM

This should reinstall grub using the cd/dvd. Make sure you put the computer back in efi mode

Code:

sudo mount /dev/<root partition> /mnt
sudo mount /dev/sda1 /mnt/boot/efi

sudo mount --bind /dev /mnt/dev

sudo mount --bind /dev/pts /mnt/dev/pts

sudo mount --bind /proc /mnt/proc

sudo mount --bind /sys /mnt/sys

Code:

sudo chroot /mnt

Code:

grub-install
or
grub-install --recheck 
update-grub

Quote:

exit && sudo umount /mnt/dev && sudo umount /mnt/dev/pts && sudo umount /mnt/proc && sudo umount /mnt/sys && sudo umount /mnt

Then reboot

AndrewAmmerlaan · 03-03-2014, 05:34 AM

That didn't work for some odd reason, I think because of UEFI, however I discovered that when UEFI was off I got presented with a GRUb command line thingy, after some googling, I found that I could boot by typing:
find /boot/grub/stage1
root (hd0,7)
kernel /boot/vmlinuz
initrd /boot/initrd
boot
Then I reinstalled the GRUb through yast in Non- UEfI mode, becuase the sytem was booted in non UEFI mode.
I think I accidentally converted grub to Non-UEFI mode with the live-cd.
Also in Non-UEFI mode there is no graphical corruption using the fglrx driver, this means that the flgrx driver has a bug with UEFI mode.

Thanks for all the help, I really appreciate it.

colorpurple21859 · 03-03-2014, 08:19 AM

Glad you got it sorted out. In my post 19 I must have been half asleep. It should have been mount you root partition to /mnt and then mount the efi fat32 partition, which with a windows install is usually /dev/sda1, to /mnt/boot/efi, not mount /dev/sda1 /mnt. that is why it didn't work. I edited post 19 and corrected what was wrong. The efi fat32 partition may be something different if windows is not installed.

SnakeHaveYou · 04-01-2014, 01:26 AM

Hi, hi had the same problem, here is some info:

The problem seems to be the GOP (Graphics Output Protocol) mode support:

Grub2-EFI and/or ELILO doesn't seem to use/support GOP (Graphics Output Protocol), wich SEEMS to be required by the ATI 7670m to boot correctly into the OS, if using an UEFI/GPT scheme installation..

Since i have an original Windows 8.x license, i needed to stay in an UEFI/GPT scheme.

So after messing and testing arround with the Grub2-EFI modelines, i realised that when i changed the Grub2 resolution, the lines/artifacts reduced to a square, in the top-left side of the screen (1/4 the size of the screen).
Of course, after all the mess, i broke Grub2 and ELILO.. lol..

Flashed into a flashdrive the rEFInd bootloader, and checked the config file (refind.conf), in the resolution section, and i saw that there was a new mode: GOP
Uncommented the GOP mode resolution line, and OpenSUSE/Fedora booted without artifacts! No shifted screen, no strange lines.. All fixed!

The line is:

Code:

#resolution 3

You'll need to uncomment ONLY that line, and change the "3" acording to your maximum screen resolution:

The values can be 0, 1, 2, 3, or 4 referring to the 640x480, 800x600, 1024x768, 1280x1024, or 1440x900 screen resolutions respectively

For my laptop, the value is 2, because the maximum resolution of my screen is 1366x768. Higher values will fallback to 640x480

After that, installed the rEFInd rpm into OpenSUSE/Fedora, and i deleted the Grub2, ELILO and OpenSUSE/Fedora folders in /boot/efi/EFI/
I keeped the rEFInd and Microsoft folders

Here is the thread i started in OpenSUSE forum: Thread

AndrewAmmerlaan · 04-02-2014, 09:24 AM

I tried installing refind, but it does not boot after restart, I found this on the web:

Quote:

I would also recommend installing experimenting with the efibootmgr. Grub2-EFI does support GOP.
However, you must manually insert the following to grub.cfg to enable GRUB to pass the video mode correctly to the kernel.
Code:

insmod efi_gop
insmod efi_uga
insmod font

if loadfont ${prefix}/unicode.pf2
then
insmod gfxterm
set gfxmode=auto
set gfxpayload=keep
terminal_output gfxterm
fi

I am unsure were in the grub.cfg I should paste this.

SnakeHaveYou · 04-02-2014, 06:59 PM

Mmmm.. Are you using:

- UEFI mode in BIOS?
- Native EFI install?

rEFInd should work out of the box.. After the Toshiba logo, rEFInd menu should appear..

If not, at boot, press repeatedly F12. The boot selection should appear.
Press enter on the HDD, and select one of the bootloaders. Try all of them, until rEFInd menu appear

AndrewAmmerlaan · 04-03-2014, 07:35 AM

I am using UEFI, but the refind oprion does not show up in the list of bootmanagers

SnakeHaveYou · 04-03-2014, 07:34 PM

Quote:

Originally Posted by AndrewAmmerlaan

I am using UEFI, but the refind oprion does not show up in the list of bootmanagers

Well, that's unespected!

Look at my video: https://www.youtube.com/watch?v=ogcsVK-6q6c

In the video, i'm using an native EFI install, with Grub2-EFI, rEFInd with GOP enabled, and Kernel 3.14 with Radeon Open Source drivers..
Kernel 3.14 with Grub2-EFI on our laptops, is doing worst.. Not even the Open Source Radeon drivers works..

AndrewAmmerlaan · 04-04-2014, 04:04 AM

I am going to do a full system reset, removing all partitions and all data, and going to install linux in csm mode, because this solves all graphics problems. The graphical corruption must be a bug with fglrx and uefi, the radeon driver does work with uefi but has poor preformance.

Ztcoracat · 04-05-2014, 12:51 PM

Quote:

Originally Posted by AndrewAmmerlaan

I am going to do a full system reset, removing all partitions and all data, and going to install linux in csm mode, because this solves all graphics problems. The graphical corruption must be a bug with fglrx and uefi, the radeon driver does work with uefi but has poor preformance.

I am suspicious of the fglrx driver too. The restricted driver from the repository only provides a limited amout of support.
(I haven't tested the current one yet)
I discovered that particular driver does not support 3D acceleration.

This is the newer ones I found in the Ubuntu repo-

Code:

fglrx (2:13.101-0ubuntu0.0.1) [restricted]
    Video driver for the AMD graphics accelerators
fglrx-amdcccle (2:13.101-0ubuntu0.0.1) [restricted]
    Catalyst Control Center for the AMD graphics accelerators

The first one is the driver and the second is the graphical software.
http://packages.ubuntu.com/precise-updates/

I have the ATI/AMD catalyst Proprietary Linux x86 Display driver installed on my system and it has been buggy:-
13.12 is buggy but I'm not sure about the current Beta 14.3 yet--
I'm slowly finding out that the proprietary drivers are crap. I haven't found evidence yet that AMD is at fault but it seems very possible.
http://support.amd.com/en-us/downloa...p?os=Linux+x86

Sharing what I have ran into and hope the information helps.

AndrewAmmerlaan · 04-05-2014, 01:03 PM

These problems are 100% sure AMD's fault, and they know about it, if you look at the release notes there is a list of unsolved bugs.
As I understand it the Amd driver for linux is maintained by a voluntary team, Amd's priorities are not with linux but with windows, therefore the Amd drivers for linux will never be as good as their windows drivers. There are some distros which include fglrx as default, they seem to work fine with fglrx, don't know how they do it.

Ztcoracat · 04-05-2014, 01:59 PM

Quote:

Originally Posted by AndrewAmmerlaan

These problems are 100% sure AMD's fault, and they know about it, if you look at the release notes there is a list of unsolved bugs.
As I understand it the Amd driver for linux is maintained by a voluntary team, Amd's priorities are not with linux but with windows, therefore the Amd drivers for linux will never be as good as their windows drivers. There are some distros which include fglrx as default, they seem to work fine with fglrx, don't know how they do it.

It's a shame that it's this way.

I've been testing the fglrx with Voyager and Elementary OS Luna and you are right: the fglrx as default works fine, like you said.

I'm thinking that the developer that built the driver could explain how they do it.

It sure would be good if more Linux Developers had the time and could solve this issue. This (graphics corruption) has caused a lot of grief.
Sadly so the dist-upgrade cmd breaks the fglrx and the fglrx-amdccle driver--

For what it's worth; if I was a developer I most certainly would contribute to this cause indefinitely! -