Page: Previous  1, 2, 3  Next

techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Now we are getting somewhere. As I was suspecting, the multiple device/monitor repetitions in the xorg.conf file do not occur in real debian X11 generated xorg.conf file.

Here's the issues I have now corrected: you should not need to use -! 6 now to use -d, I'm glad you thought to try the override.

The failure to install fglrx-control.

So we have a sequence of failures. Unlike with mint/lmde, it's now somewhat debuggable.

here is what I get when doing a test debian sid install of fglrx-control:

:: Code ::
apt-cache policy fglrx-control fglrx-driver
fglrx-control:
  Installed: (none)
  Candidate: 1:14.3~beta1.0-1
  Version table:
     1:14.3~beta1.0-1 0
        500 http://mirror.peer1.net/debian/ unstable/non-free i386 Packages
        200 http://mirror.peer1.net/debian/ testing/non-free i386 Packages
fglrx-driver:
  Installed: (none)
  Candidate: 1:14.3~beta1.0-1
  Version table:
     1:14.3~beta1.0-1 0
        500 http://mirror.peer1.net/debian/ unstable/non-free i386 Packages
        200 http://mirror.peer1.net/debian/ testing/non-free i386 Packages


so both the packages are in debian sid/testing, as you can see. Then, a simuiated test install:

:: Code ::
$ apt-get install -s fglrx-control fglrx-driver
NOTE: This is only a simulation!
      apt-get needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  glx-alternative-fglrx glx-alternative-mesa glx-diversions libfglrx nvidia-installer-cleanup
Suggested packages:
  xvba-va-driver amd-opencl-icd
Recommended packages:
  fglrx-modules-dkms fglrx-kernel-14.3-beta1.0 libgl1-fglrx-glx fglrx-atieventsd libfglrx-amdxvba1
The following NEW packages will be installed:
  fglrx-control fglrx-driver glx-alternative-fglrx glx-alternative-mesa glx-diversions libfglrx
  nvidia-installer-cleanup
0 upgraded, 7 newly installed, 0 to remove and 1406 not upgraded.
Inst nvidia-installer-cleanup (20131102+1 Debian:unstable [i386])
Conf nvidia-installer-cleanup (20131102+1 Debian:unstable [i386])
Inst glx-diversions (0.4.1 Debian:unstable [i386])
Inst libfglrx (1:14.3~beta1.0-1 Debian:unstable [i386])
Inst glx-alternative-mesa (0.4.1 Debian:unstable [i386])
Inst glx-alternative-fglrx (0.4.1 Debian:unstable [i386])
Inst fglrx-driver (1:14.3~beta1.0-1 Debian:unstable [i386])
Inst fglrx-control (1:14.3~beta1.0-1 Debian:unstable [i386])
Conf glx-diversions (0.4.1 Debian:unstable [i386])
Conf libfglrx (1:14.3~beta1.0-1 Debian:unstable [i386])
Conf glx-alternative-mesa (0.4.1 Debian:unstable [i386])
Conf glx-alternative-fglrx (0.4.1 Debian:unstable [i386])
Conf fglrx-driver (1:14.3~beta1.0-1 Debian:unstable [i386])
Conf fglrx-control (1:14.3~beta1.0-1 Debian:unstable [i386])


again, no issues. It's possible you are A: using bad repositories, or B: your network connection is failing during the install.

You can check this by leaving X, do: ctrl + alt + F1, then login as root, then do: service lightdm stop

which is what sgfxi does too, then do:
:: Code ::
apt-get install -d  fglrx-driver fglrx-control


and look for any error messages. The -d means download only.

That's the first problem in the system, and it's not caused by sgfxi. The failure to let you use -d was a problem and that is now corrected.

fglrx is in fact running your system, at least that is what Xorg.0.log says, so the driver install worked, at least in part, even though the amd driver installer says it failed.

Solve the issue of why the fglrx-control is failing to download and install first.

Just so you understand it, so far there is NO similarity between the lmde failure and this failure, zero. No corrupted xorg.conf file, and if we can get the dkms stuff installed we can test the dkms part too.

radeon should work if radeon xorg driver supports your card.

Here's some general long term advice for running GNU / Linux and amd video cards. If you can avoid it, use nvidia, if you cannot avoid it, use older amd cards, avoid the new ones. Avoid new kernels, amd has terrible release cycle now, and only rarely does a new fglrx/catalyst stable release. The last one for example was 13.12 I believe. Betas are going to be beta quality, unlike nvidia, whose betas almost always work.

But you have too many separate issues at this point, you have to resolve them one at a time.

When logged in out of X with lightdm shutdown/stopped, do this simple test: ping google.com
and see if you get a valid IP address response. If you do, you have a working internet connection, if you do not, you do not have a connection, assuming you have ping. However, sgfxi always checks for connection too, and it will tell you if none is present, which makes me suspect your repos.

let me see your repos:

first:
:: Code ::
ls /etc/apt/sources.list /etc/apt/sources.list.d/*.list


then:
:: Code ::
cat /etc/apt/sources.list /etc/apt/sources.list.d/*.list


I will do this for sgfxi debugger too since this exposes more possible issues.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Please note: new sgfxi has these debuggering data features added.

I also fixed some not working debugger stuff, so there should be more now.
Back to top
Andjety
Status: Interested
Joined: 29 Mar 2014
Posts: 11
Reply Quote
:: Quote ::
Here's some general long term advice for running GNU / Linux and amd video cards. If you can avoid it, use nvidia, if you cannot avoid it, use older amd cards, avoid the new ones. Avoid new kernels, amd has terrible release cycle now, and only rarely does a new fglrx/catalyst stable release. The last one for example was 13.12 I believe. Betas are going to be beta quality, unlike nvidia, whose betas almost always work.



Thank you for this advice. Actually, i have long understand that i made the wrong choice. But there is no other way at this time...

The only problem with the repository (i think) is that the non-free repository was missing, and i corrected that, and it has later found the fglrx-driver

Here is my repos:

:: Code ::
# deb cdrom:[Debian GNU/Linux jessie-DI-a1 _Jessie_ - Official Snapshot i386 DVD Binary-1 20140318-11:10]/ jessie contrib main

#deb cdrom:[Debian GNU/Linux jessie-DI-a1 _Jessie_ - Official Snapshot i386 DVD Binary-1 20140318-11:10]/ jessie contrib main

deb http://ftp.ch.debian.org/debian/ jessie main
deb-src http://ftp.ch.debian.org/debian/ jessie main

deb http://security.debian.org/ jessie/updates main contrib
deb-src http://security.debian.org/ jessie/updates main contrib

# jessie-updates, previously known as 'volatile'
deb http://ftp.ch.debian.org/debian/ jessie-updates main contrib
deb-src http://ftp.ch.debian.org/debian/ jessie-updates main contrib

# jessie-backports, previously on backports.debian.org
deb http://ftp.ch.debian.org/debian/ jessie-backports main contrib
deb-src http://ftp.ch.debian.org/debian/ jessie-backports main contrib

# non-free
deb http://ftp.ch.debian.org/debian/ jessie main contrib non-free


# Liquorix sources added by smxi
deb http://liquorix.net/debian/ sid main



I don't know if the problem come from sgfxi, but what i know, is that this driver works fine with ubuntu on the other side on my hard drive, without any effort.
I was thinking, well, it should also work with debian.

It worked also with fedora 19. I guess i should follow your advice, and avoid new kernel when one is working fine.

I will test sgfxi -n and sgfxi -d, and sgfxi -B one more time.
Back to top
Andjety
Status: Interested
Joined: 29 Mar 2014
Posts: 11
Reply Quote
Using sgfxi-n , i have a black screen when starting x. Radeon has never well worked with my card, but it should, because this card begin to be old enbough now.

Using sgfxi-d , same issue as before.
Back to top
Andjety
Status: Interested
Joined: 29 Mar 2014
Posts: 11
Reply Quote
sgxi -B

Here is the error:
:: Code ::
cat /usr/share/ati/fglrx-install.log
Supported adapter detected.
Check if system has the tools required for installation.
Uninstalling any previously installed drivers.
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Message] Kernel Module : Found kernel module build environment, generating kernel module now.
AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/3.13-1-686-pae/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-headers-3.13-1-686-pae'
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_agp.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_debug.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_io.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_pci.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_str.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_iommu.o
/lib/modules/fglrx/build_mod/2.6.x/kcl_iommu.c: In function 'KCL_IOMMU_CheckInfo':
/lib/modules/fglrx/build_mod/2.6.x/kcl_iommu.c:191:28: error: 'struct dev_archdata' has no member named 'iommu'
     if ( pdev->dev.archdata.iommu )
                            ^
make[4]: *** [/lib/modules/fglrx/build_mod/2.6.x/kcl_iommu.o] Error 1
make[3]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.13-1-686-pae'
make: *** [kmod_build] Error 2
build failed with return value 2
[Error] Kernel Module : Failed to compile kernel module - please consult readme.
[Reboot] Kernel Module : update-initramfs

Back to top
Andjety
Status: Interested
Joined: 29 Mar 2014
Posts: 11
Reply Quote
The debugger file:

webcloud6.zaclys.com/public.php?service=files&t=a514e1fece64a31b6e2197041021c350
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Ok, piece by piece we are fixing some things. I can tell you a bit more, suggestions.

To truly test radeon, do this: sgfxi -n

which will remove all blacklisting etc, then try this:

rm /etc/X11/xorg.conf

then reboot so you boot into a kernel with modesetting/kms not blacklisted. Note that you should always upgrade debian testing fully to bring everything up to current with: apt-get dist-upgrade, that will pull in all pieces including new xorg stuff, but sgfxi will also pull in those new pieces if they were missing.

sometimes X works better today without xorg.conf with native xorg free drivers.

Further: it appears that lmde is using a broken xorg.conf generator, I had suspected that, but now it looks more likely.

I thought sgfxi checked for non free in repos but I will double check the code.

To add non-free just add to the regular lines: non-free, don't create a new line, that will result in doubled repo errors in apt.

deb ftp.ch.debian.org/debian/ jessie main contrib non-free

that means: use main, contrib, and non-free

sgfxi was supposed to do this automatically but apparently it did not work.

Do not add non-free to security repos. I do not know about the backports.

I am not aware of jesse having backports, by the way, it's testing/sid currently, there is nothing to backport. Once it goes stable, yes, maybe it's fine before, I don't know.

Here's a critical issues: dkms can only be used together with the distribution kernels, period. That is because the kernel and driver are matched. With fglrx this is obviously a problem once a distro goes stable, but again, you are using jesse so the version is I believe the new beta, not sure, but I think it is, in the dkms driver package. In other words, only use the -d dkms debian driver option if you are also using the debian kernel, this is not optional, they must both be the debian version for success, the fglrx debian package is tested only against the debian kernel.

I cannot tell you why the actual beta installer is failing, that is not related to sgfxi, that's a bug you have to file upstream with amd, and I can already tell you that is a waste of time.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Ok, now the non free apt detection is working, but note that it only works with debian.org repos, there's too many other debian repos to handle so I'm leaving that as is.

But that failure did come from a situation I normally do not see, contrib being present and non-free being missing. Usually both are there or missing, now sgfxi handles this case properly, I think.

The sgfxi -B error is a matter for upstream, amd/ati, but they actually have a newer driver for beta now, but sgfxi does not have it due to packaging changes by amd, something they do constantly, the last one I cannot really handle cleanly so I'm leaving it alone to see what happens with amd driver packaging in the future. If it changes too much more I will just drop amd support in sgfxi, we'll see how it goes.

That's not related to this set of issues, but the new amd beta may be installable for you. The -B failure you are getting should not be related to the other issues, those are in the driver itself, sgfxi cannot fix those.

I expect, by the way, fglrx support to get increasingly bad from amd, and I can tell you firsthand, it's getting nearly impossible to support fglrx linux in sgfxi anymore, I can still do it a little, but amd is making it VERY hard, it's almost to my eyes as if they were trying to dump their linux support by making it worse every year.
Back to top
Andjety
Status: Interested
Joined: 29 Mar 2014
Posts: 11
Reply Quote
Ok. It seems to me that i have to give up with that. I really made a long effort, but it really take to much of my time, for something i am far away to understand. It works on ubuntu, so i will use ubuntu gnome.

What i don't understand:
Ubuntu is based on debian. With ubuntu, i only have to install fglrx-driver, and it works. Why is it not the same with debian?

Next time, i will not by an ati card, that for sure.

Thank you for the time you took for that.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
As to why, ubuntu is ubuntu and debian is debian, the two should not be thought of as the same.

Some packages in ubuntu are the same, most in fact, but only the same as of the date they were taken from the debian package pool.

Possible reasons it doesn't work: the driver needs a patch, the kernel is different, the driver and kernel are different.

Remember, in ubuntu, they release frozen pool, so when you install ubuntu, you are installing debian sid from about 3 to 9 months ago. The ubuntu kernel and drivers are released to work together.

You did provide a lot of helpful feedback and have let me fix some smaller issues in sgfxi, but the problem of fglrx in linux is far more serious than most people realize, I fully expect almost no support from amd in the future, they have already gone from their very bad and non functioning release cycle of one driver per month to about one driver every 4 months, maybe 5, no pattern yet since it takes longer for each new stable release.

I have for a long time thought of dropping fglrx support in sgfxi, which would be sad, but it's becoming non viable to support something that is increasingly starting to look like it's designed to not work in linux, at least amd couldn't make it worse if they actually tried.

The final thing on ubuntu, if you use the ubuntu fglrx package, and the ubuntu kernel, those are designed to work together, in fact, one of the only distros, along with redhat/fedora, that amd actually supports is ubuntu.
Back to top
Display posts from previous:   
Page: Previous  1, 2, 3  Next
All times are GMT - 8 Hours