The AMD/ATI Bar & Grill

Niccola · 2015-10-09 00:05:10

Vi0L0 wrote:

@Niccola:
I just noted that I'm also getting problems on gdm (gnome itself is ok)... It was working no more than 3 weeks ago <sigh>. Check other dm - lxdm or sddm(im more like kde fan) - both works fine here.
If no success then look at /var/log/Xorg.0.log or journalctl -b and see if X loaded fglrx. Could be that it needs fglrx in conf file, and probably your conf wasn't generated by aticonfig because no adapters were find. You can check then something like:
# echo -e 'Section "Device"\n\tIdentifier "My GPU"\n\tDriver "fglrx"\nEndSection' > /etc/X11/xorg.conf.d/20-fglrx.conf
Just be sure that theres no other conflicting file in /etc/X11 dir
Edit: ah, you are on hybrid , it could complicate things a bit, don't forget to install xf86-video-intel then

@Vi0L0,
I also tried with lightdm which led me into a white screen with cursor only. I think each dm has its own behavior with this issue. So I'll try those dm you recommended

I took a record from Xorg.0.log during error (now Im on OpenSource driver): http://pastebin.com/8fKb21ax
Weird: the first error (EE) says intel module wasn't found. I don't know if xf86-video-intel was removed during fglrx installation
others errors (EE) refers to some Framebuffer:

can I manually generate a xorg.conf?

On Ubuntu, I had this no supported adapters found error but after rebooting it recognized ok. But on Arch this behavior doesn't happen

@olive,
I am on oss driver already. And I must say it is awesome! I want to install fglrx due to compare and see what is better for me (which one has better power management, better performance, etc..)

Vi0L0 · 2015-10-09 06:52:48

Lag says that X never touched fglrx. If you will return to catalyst I suggest to check is module loading well, ie. with `modprobe fglrx`.
Next step would be to generate conf file - since you are catching problems with aticonfig the simplest method is echo which I mentioned in previous post.

Primoz · 2015-10-09 12:52:28

I think I finally fixed my freezing problem...
After downgrading both mesa and linux-lts, I have yet to experience any freeze.

But now what? How long should it wait before upgrading both? Should I just go for it, and end the troubleshooting, that is try to recreate reasons for freezing in the first place?

I also did some quasi performance test, one previous post mentioned trying TF2, so I also did and my framerate was really really bad, like 39-40 tops. I assume it has something to do with the fact I have APU and not an actual graphics card.

innsmouthrain · 2015-10-09 18:27:54

Heeeeeeeey fellows,

have a look at this.

after pacman -Syu

[moth@charm ~]$ fglrxinfo 
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual!

So I realized that pxp-catalyst doesn't support 4.2 kernel and did the following:

pacman -Rns linux linux-headers
pacman -S linux-lts linux-lts-headers catalyst-hook catalyst-utils catalyst-libgl opencl-catalyst lib32-catalyst-utils lib32-catalyst-libgl lib32-opencl-catalyst mesa lib32-mesa xf86-video-ati

and of course

aticonfig --update
sudo pxp_switch_catalyst amd
startx

But still, no luck. Am I missing something?

EDIT:
Changed syslinux.cfg and made sure I was booted into linux-lts

Last edited by innsmouthrain (2015-10-10 16:24:00)

joelisntmyname · 2015-10-09 21:30:36

Primoz wrote:

I think I finally fixed my freezing problem...
After downgrading both mesa and linux-lts, I have yet to experience any freeze.

Same here.

Just looking at updates to linux-lts, they seem to have fixed an "inet deadlock" that affected the kernel versions that we experienced the issue on. I think there's a chance they're the same issue, so I might give upgrading it a go and see if it lasts.
https://projects.archlinux.org/svntogit … 5b96a48ab5
https://bugs.archlinux.org/task/46570

But that could be unrelated for all I know.

Primoz · 2015-10-11 09:11:53

Upgraded mesa to 11.0.3-1, so far I haven't experienced any freezes yet. Either mesa was never the problem, or the new version fixed those problems.
I'll probably update linux-lts when the next fixes come...

aslmaswd · 2015-10-12 04:23:17

atieventsd crashs after logout a graphical session.
I recommend using setting Restart=on-failure in atieventsd.service .

Primoz · 2015-10-12 08:55:12

Upgraded Linux-lts to 4.1.10-2, so far, so good.

I guess whatever it was, was fixed. (at least for me).

Vi0L0 · 2015-10-12 20:49:27

GNOME 3.18 journalctl -b, in both composited and classic(sic!):

 
gnome-session[988]: ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context
 gnome-session[988]: ERROR: error(#273) 1 compilation errors.  No code generated
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: Shader compilation failed:
 gnome-session[988]: Fragment shader failed to compile with the following errors:
 gnome-session[988]: ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context
 gnome-session[988]: ERROR: error(#273) 1 compilation errors.  No code generated
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: Failed to link GLSL program:
 gnome-session[988]: Vertex and Fragment shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:796: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:819: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:823: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:827: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:831: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-opengl.c:751: GL error (1280): Invalid enumeration value
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: Shader compilation failed:
 gnome-session[988]: Fragment shader failed to compile with the following errors:
 gnome-session[988]: ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context

Have no time to look closer today, but it looks like catalyst doesn't like 120 version of Shader and maybe the fix is to use the other version - if so it shouldn't be that hard to fix...

aslmaswd wrote:

atieventsd crashs after logout a graphical session.
I recommend using setting Restart=on-failure in atieventsd.service .

Thanks, will change that in free time

turtlepleasure · 2015-10-13 02:05:35

Vi0L0 wrote:

GNOME 3.18 journalctl -b, in both composited and classic(sic!):

 
gnome-session[988]: ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context
 gnome-session[988]: ERROR: error(#273) 1 compilation errors.  No code generated
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: Shader compilation failed:
 gnome-session[988]: Fragment shader failed to compile with the following errors:
 gnome-session[988]: ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context
 gnome-session[988]: ERROR: error(#273) 1 compilation errors.  No code generated
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: Failed to link GLSL program:
 gnome-session[988]: Vertex and Fragment shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:796: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:819: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:823: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:827: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:831: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-progend-glsl.c:213: GL error (1282): Invalid operation
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: driver/gl/cogl-pipeline-opengl.c:751: GL error (1280): Invalid enumeration value
 gnome-session[988]: (gnome-shell:1105): Cogl-WARNING **: Shader compilation failed:
 gnome-session[988]: Fragment shader failed to compile with the following errors:
 gnome-session[988]: ERROR: error(#271) Explicit version number 120 not supported by GL3 forward compatible context

Have no time to look closer today, but it looks like catalyst doesn't like 120 version of Shader and maybe the fix is to use the other version - if so it shouldn't be that hard to fix...

I just upgraded to gnome 3.18 and now have the same issue. Tried downgrading but doesn't seem to fix.

Vi0L0 · 2015-10-13 08:12:29

I downgraded whole bunch of packages to get it working. Thats why I'm thinking about finding some workaround or a real solution.
Don't want to criticize or insult, but this update feels like a beta testing. One update and I get not only DE completely broken but even related apps like known java project (ie. android-studio on which I have to work latelly) gets also broken (probably because of the changes in glib2)...
Is this some kind of hate over prioprietary things (I also prefer open source but hey, we are on Linux), or just miss in testing?
Theres no need to answer (I'm on Linux, hell I'm on Arch, things get broken here I know),
just saying (whining maybe :>, you can say here that I could get involved into beta testing and this would be true, but I simply don't have a time for this ).

Last edited by Vi0L0 (2015-10-13 09:22:45)

Panzerino · 2015-10-15 14:12:22

Vi0L0 wrote:

I downgraded whole bunch of packages to get it working. Thats why I'm thinking about finding some workaround or a real solution.
Don't want to criticize or insult, but this update feels like a beta testing. One update and I get not only DE completely broken but even related apps like known java project (ie. android-studio on which I have to work latelly) gets also broken (probably because of the changes in glib2)...
Is this some kind of hate over proprietary things (I also prefer open source but hey, we are on Linux), or just miss in testing?
Theres no need to answer (I'm on Linux, hell I'm on Arch, things get broken here I know),
just saying (whining maybe :>, you can say here that I could get involved into beta testing and this would be true, but I simply don't have a time for this ).

Dear Vi0L0,

You make enormous efforts this really sh...ty thing to work. And all we here appreciate enormously your effort and time dedicated to this subject.
But like we all see now, this thing is impossible to work stable, to BE stable in dynamically environment, simply because, the "boys" from ATI does not want working driver on Linux platform. And that is all. Bugs after bugs, new bugs. It is a joke. Really... .
The graphic subsystem is crucial- desktop machine, full of personal data, is not a subject to risky games.
In this aspect, all these here exercises are a pure form of masochism.

It is very painful to read all these pages here. What is not work- is not work!
Other way must be find.

Vi0L0 · 2015-10-18 09:35:19

GNOME 3.18 fix
In [catalyst] and [catalyst-stable] you may find a new package cogl 1.22.0-2. It brings fix for recent problems with new GNOME 3.18 and new GDM (it baheves strange with plasma though, after choosing plasma and entering password I have to switch to tty and then back to X to see plasma desktop, probably another bug).
Source and a patch is here: http://mirror.rts-informatique.fr/archl … src.tar.gz
Edit: patch itself:

--- 122/cogl/driver/gl/gl/cogl-driver-gl.c	2015-09-02 18:39:02.000000000 +0200
+++ 122b/cogl/driver/gl/gl/cogl-driver-gl.c	2015-10-18 10:37:14.052350142 +0200
@@ -419,7 +419,7 @@
   if (COGL_CHECK_GL_VERSION (ctx->glsl_major, ctx->glsl_minor, 1, 2))
     /* We want to use version 120 if it is available so that the
      * gl_PointCoord can be used. */
-    ctx->glsl_version_to_use = 120;
+    ctx->glsl_version_to_use = 150;
   else
     ctx->glsl_version_to_use = 110;

Not sure about if it will work with all video drivers, but AFAIK should work with all that supports OpenGL 3.2. It does work on oss ati.
Plus I've found that android-studio runs fine on GNOME 3.18, while it segfaults on plasma (when using current glib2).

Seems to work fine here on x86_64. Didn't test it on i686
Sorry for bringing it too late, really got more projects on my head than I need...
Fix was very easy to find and is probably noobish :>, log that I paste couple of comments above, about 120 version was all that was needed to find it.

Edit:

Panzerino wrote:

But like we all see now, this thing is impossible to work stable, to BE stable in dynamically environment, simply because, the "boys" from ATI does not want working driver on Linux platform.

We know this from the very beginging, that's why catalyst was removed from arch repos, long time before I appeared here.

Panzerino wrote:

And that is all. Bugs after bugs, new bugs. It is a joke. Really... .

Yup, it hasn't changed for years now. Well, in general catalyst is (slowly) evolving and is getting better shape, but bugs are still here.

Panzerino wrote:

In this aspect, all these here exercises are a pure form of masochism.

On Arch, where we are always on the edge - yes.
But on more stable systems it shouldn't be that bad.

Panzerino wrote:

It is very painful to read all these pages here. What is not work- is not work!
Other way must be find.

The other way is known and is called oss drivers.
Just not for everybody because for many still catalyst is the better option - sometimes performance is better, sometimes power management, some people are writing opencl software etc.

Last edited by Vi0L0 (2015-10-18 13:43:26)

ranjak · 2015-10-18 10:19:03

Thank you for this patch, I've updated the relevant bug report with it.

Amanda S · 2015-10-19 03:04:06

Hi Vi0l0. Have you had time to check why Catalyst can't build it's modules on linux-grsec?

Thanks.

Last edited by Amanda S (2015-10-19 03:04:19)

thol · 2015-10-19 15:35:29

Hey guys and @Vi0l0!

I've been following this thread and this other one https://bbs.archlinux.org/viewtopic.php?id=190236, regarding the AMD drivers for the mobile graphics cards 'Topaz' series (M260/M265).
A couple of months ago, when I installed (both the catalyst from Vi0l0 and the open source driver), it was just impossible to use, the performance was terrible, tearing was everywhere, etc etc.

Does anybody know something regarding this?

Much appreciated!

PhotonX · 2015-10-19 19:58:49

Hello everybody, just wanted to report that I had huge problems with 15.09 and an HD6770, in about 80% of the cases the boot is not successful (complete freeze, no video signal, no reaction to keyboard), but at the same time sometimes the boot succeeds and everything works as expected. After a week or two of struggle I decided to downgrade to 15.07 which fixed the issues for me.

Last edited by PhotonX (2015-10-19 20:06:33)

Vi0L0 · 2015-10-20 08:05:35

Amarildo wrote:

Hi Vi0l0. Have you had time to check why Catalyst can't build it's modules on linux-grsec?
Thanks.

I started work on grsec but had no time to finish as other bugs were more important. Now grsec is 1st on the catalyst list.
We still have problems with 4.2 kernel (hope AMD will solve it soon as ubuntu 15.10 should be released within days), so I'm going to work on 4.1 (yes, there's grsec-4.2 already on arch repos, I know).

Niccola · 2015-10-20 22:31:23

PhotonX wrote:

Hello everybody, just wanted to report that I had huge problems with 15.09 and an HD6770, in about 80% of the cases the boot is not successful (complete freeze, no video signal, no reaction to keyboard), but at the same time sometimes the boot succeeds and everything works as expected. After a week or two of struggle I decided to downgrade to 15.07 which fixed the issues for me.

@PhotonX,
this HD6770 is hybrid with Intel or is a single Desktop GPU ? Coz I also have a 6770M on my laptop alongside an Intel H3000 Hybrid system and I couldn't manage to install catalyst driver on my system until now, could you please help me by providing step-by-step information on how did you installed it?

@Vi0l0,
I couldn't install catalyst driver yet. I am quite new on this Arch thing and I can't (probably I don't know how to) find proper information on how install catalyst driver correctly (like a step by step tutorial). I don't like to ask for a stepbystep tutorial but I'm in hurry for OpenCL development which only catalyst is capable to support proper OpenCL.

I am still on radeon opensource

PhotonX · 2015-10-21 07:21:36

@Niccola: No, in my case it's just the desktop version of the HD6770, no M. If you just want to be able to switch between the two video cards in your laptop, have a look here: https://wiki.archlinux.org/index.php/PRIME This works without Catalyst. However, if you want to use Catalyst (i.e. to run some games which don't support the radeon driver), follow this: https://wiki.archlinux.org/index.php/AM … ss_support

Last edited by PhotonX (2015-10-21 07:21:51)

Smallville · 2015-10-21 12:37:04

PhotonX wrote:

Hello everybody, just wanted to report that I had huge problems with 15.09 and an HD6770, in about 80% of the cases the boot is not successful (complete freeze, no video signal, no reaction to keyboard), but at the same time sometimes the boot succeeds and everything works as expected. After a week or two of struggle I decided to downgrade to 15.07 which fixed the issues for me.

What is the 15.09 you talk and have downgrade ? I have the same issue and the same graphic card HD6770 and most times my system wont boot keep restarting what you have did to fix this ... what i have to downgrade. Im using mesa drivers.

Thx for the help

Last edited by Smallville (2015-10-21 12:42:35)

Niccola · 2015-10-21 16:06:01

Well, today I forced managed to get it work, by doing the following:

installed catalyst-test package

removed conflicting packages (which I develop using OpenCL):

sudo pacman -Rdd amdapp-sdk-nocatalyst amdapp-sdk cpyrit-opencl lib32-ocl-icd ocl-icd opencl-headers opencl-mesa

systemctl enabled and started atieventsd and catalyst-hook
aticonfig --initial still no supported adapters

But after a reboot (using nomodeset) I got stuck on boot and switched to TTY:
then
aticonfig --initial generated xorg.confg
pxp_switch_catalyst amd

after a reboot (using nomodest) Im still stuck on boot
However, I saw in Xorg.0.log that intel module was failed to Probe by ati:

atiddxProbe: fail to probe intel VGA device(EE)

So I probed it manually by blacklisting i915 and intel on /etc/modprobe.d/modprobe.conf:

blacklist i915
blacklist intel

Then it rebooted finally on login manager
However, couldn't start any GL application
So I found fglrx_dri.so wasn't properly loaded, also saw on Xorg.0.log:

(EE) AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory

Then I simlinked /usr/lib/fglrx_dri.so to /usr/X11R6/lib64/modules/dri/fglrx_dri.so:

ln -s /usr/lib/xorg/modules/dri/fglrx_dri.so /usr/X11R6/lib64/modules/dri/fglrx_dri.so

and it worked flawlessly!

I am now trying to reinstall AMD OpenCL SDK to get back to development.

I faced with some conflicts with catalyst-test:
opencl-catalyst, lib32-ocl-icd, lib32-opencl-catalyst and ocl-icd

EDIT: I finally managed to switch between Intel/AMD without force black/whitelisting intel module

On my system (which is hybrid: Intel+AMD laptop), if I use nomodeset on kernel cmd line, Intel graphic card is loaded with VESA module (VGA resolution really messy).
So, I managed to remove nomodeset from kernel boot line and everything works OK.

I just have on question so far:
Is it possible to switch between radeon/fglrx drivers without too much work?
I would like to use fglrx only for OpenCL development (I don't play games quite often)

Last edited by Niccola (2015-10-21 18:58:37)

PhotonX · 2015-10-21 17:54:24

@Smallville: Do you use the catalyst/ repo or the packages from the AUR? In first case you can see in /var/cache/pacman/pkg:

ls /var/cache/pacman/pkg/ | grep 'catalyst|15.07'

and downgrade with "pacman -U".

You will also need to downgrade the kernel to a version smaller 4.2, that is 4.1.6 or something.

Vi0L0 · 2015-10-21 20:03:21

I just updated wiki on pxp support, it was terribly wrong about -pxp packages, sorry for late update.

@Niccola:
I was never able to confirm anything about pxp on my own, so can you confirm that catalyst 15.9 works fine on newest xorg-server and xf86-video-intel from [extra] repos?
I'm also thinking about adding a couple of your notes to the wiki, if you don't mind

Edit:

Niccola wrote:

I faced with some conflicts with catalyst-test:
opencl-catalyst, lib32-ocl-icd, lib32-opencl-catalyst and ocl-icd

It's fine, intentional. You probably need opencl-headers, thought. Run `clinfo` to check basic cl informations. If you see "Device Type: CL_DEVICE_TYPE_GPU" it means you have gpu acceleration.

Niccola wrote:

Is it possible to switch between radeon/fglrx drivers without too much work?
I would like to use fglrx only for OpenCL development (I don't play games quite often)

Hmm... I would modify pxp_catalyst_switch script a bit so it could recognize separated xorg.confs for intel and radeon. Additional switch_to_radeon funtion and switch option inside of this script also sounds like a good plan. Not sure if blacklisting intel/radeon is a must have here.

PhotonX wrote:

@Smallville: Do you use the catalyst/ repo or the packages from the AUR? In first case you can see in /var/cache/pacman/pkg:
ls /var/cache/pacman/pkg/ | grep 'catalyst|15.07'
and downgrade with "pacman -U".

BTW There's also archive repo:

[catalyst-15.7]
Server = http://mirror.rts-informatique.fr/archlinux/repo/catalyst/$arch
#Server = http://catalyst.wirephire.com/repo/catalyst/$arch

It's archive so it's missing patched cogl package, but You can get it from regular [catalyst] repo

PhotonX wrote:

You will also need to downgrade the kernel to a version smaller 4.2, that is 4.1.6 or something.

or linux-lts, or linux-rt from AUR to not sit on outdated kernel for too long

Last edited by Vi0L0 (2015-10-21 20:45:29)

Smallville · 2015-10-21 22:11:19

PhotonX wrote:

@Smallville: Do you use the catalyst/ repo or the packages from the AUR? In first case you can see in /var/cache/pacman/pkg:
ls /var/cache/pacman/pkg/ | grep 'catalyst|15.07'
and downgrade with "pacman -U".
You will also need to downgrade the kernel to a version smaller 4.2, that is 4.1.6 or something.

Thank you
Thats work the kernel downgrade

Life saver

Last edited by Smallville (2015-10-21 22:11:30)

Arch Linux

#7151 2015-10-09 00:05:10

Re: The AMD/ATI Bar & Grill

#7152 2015-10-09 06:52:48

Re: The AMD/ATI Bar & Grill

#7153 2015-10-09 12:52:28

Re: The AMD/ATI Bar & Grill

#7154 2015-10-09 18:27:54

Re: The AMD/ATI Bar & Grill

#7155 2015-10-09 21:30:36

Re: The AMD/ATI Bar & Grill

#7156 2015-10-11 09:11:53

Re: The AMD/ATI Bar & Grill

#7157 2015-10-12 04:23:17

Re: The AMD/ATI Bar & Grill

#7158 2015-10-12 08:55:12

Re: The AMD/ATI Bar & Grill

#7159 2015-10-12 20:49:27

Re: The AMD/ATI Bar & Grill

#7160 2015-10-13 02:05:35

Re: The AMD/ATI Bar & Grill

#7161 2015-10-13 08:12:29

Re: The AMD/ATI Bar & Grill

#7162 2015-10-15 14:12:22

Re: The AMD/ATI Bar & Grill

#7163 2015-10-18 09:35:19

Re: The AMD/ATI Bar & Grill

#7164 2015-10-18 10:19:03

Re: The AMD/ATI Bar & Grill

#7165 2015-10-19 03:04:06

Re: The AMD/ATI Bar & Grill

#7166 2015-10-19 15:35:29

Re: The AMD/ATI Bar & Grill

#7167 2015-10-19 19:58:49

Re: The AMD/ATI Bar & Grill

#7168 2015-10-20 08:05:35

Re: The AMD/ATI Bar & Grill

#7169 2015-10-20 22:31:23

Re: The AMD/ATI Bar & Grill

#7170 2015-10-21 07:21:36

Re: The AMD/ATI Bar & Grill

#7171 2015-10-21 12:37:04

Re: The AMD/ATI Bar & Grill

#7172 2015-10-21 16:06:01

Re: The AMD/ATI Bar & Grill

#7173 2015-10-21 17:54:24

Re: The AMD/ATI Bar & Grill

#7174 2015-10-21 20:03:21

Re: The AMD/ATI Bar & Grill

#7175 2015-10-21 22:11:19

Re: The AMD/ATI Bar & Grill

Board footer