The AMD/ATI Bar & Grill

Vi0L0 · 2016-01-04 07:26:42

I will look at this after work, so after at least 8 hours from now.
BTW: what package version are you using?

Last edited by Vi0L0 (2016-01-04 07:31:41)

ElNinijo · 2016-01-04 16:16:49

catalyst-total-hd234k 13.1-32

nous · 2016-01-04 18:18:11

This might be a blast from the past (sorry for the awful pun), but I installed Unreal Tournament GOTY 1999 from the AUR archive at Github. Trying to launch it, I got segfaults with the following output:

OpenGL
libGL: AtiGetClientDriverName: 15.20.3 fglrx (screen 0)
libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/fglrx_dri.so
libGL error: OpenDriver: failed to open /usr/lib/xorg/modules/dri/fglrx_dri.so, error[/usr/lib/xorg/modules/dri/fglrx_dri.so: wrong ELF class: ELFCLASS64]
libGL error: OpenDriver: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
libGL error: OpenDriver: failed to open /usr/lib/dri/fglrx_dri.so, error[/usr/lib/dri/fglrx_dri.so: wrong ELF class: ELFCLASS64]
libGL error: OpenDriver: failed to open /usr/X11R6/lib32/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib32/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
ukiDynamicMajor: found major device number 249
ukiDynamicMajor: found major device number 249
ukiDynamicMajor: found major device number 249
ukiOpenDevice: node name is /dev/ati/card0
ukiOpenDevice: open result is 48, (OK)
ukiGetBusid returned 'PCI:1:0:0'
ukiOpenDevice: node name is /dev/ati/card1
ukiOpenDevice: UKI_ERR_NOT_ROOT
... cards 2-14 here
ukiOpenDevice: node name is /dev/ati/card15
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiDynamicMajor: found major device number 249
ukiOpenByBusid: Searching for BusID PCI:1:0:0
ukiOpenDevice: node name is /dev/ati/card0
ukiOpenDevice: open result is 48, (OK)
ukiOpenByBusid: ukiOpenMinor returns 48
ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
Segmentation fault

Redefining LIBGL_DRIVERS_PATH as 'usr/lib32/xorg/modules/dri:/usr/lib/xorg/modules/dri' to suppress the wrong ELF class errors, I've ended up with this:

OpenGL
libGL: AtiGetClientDriverName: 15.20.3 fglrx (screen 0)
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/fglrx_dri.so
ukiDynamicMajor: found major device number 249
ukiDynamicMajor: found major device number 249
ukiDynamicMajor: found major device number 249
ukiOpenDevice: node name is /dev/ati/card0
ukiOpenDevice: open result is 48, (OK)
ukiGetBusid returned 'PCI:1:0:0'
ukiOpenDevice: node name is /dev/ati/card1
ukiOpenDevice: UKI_ERR_NOT_ROOT
... cards 2-14 here
ukiOpenDevice: node name is /dev/ati/card15
ukiOpenDevice: UKI_ERR_NOT_ROOT
ukiDynamicMajor: found major device number 249
ukiOpenByBusid: Searching for BusID PCI:1:0:0
ukiOpenDevice: node name is /dev/ati/card0
ukiOpenDevice: open result is 48, (OK)
ukiOpenByBusid: ukiOpenMinor returns 48
ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
Signal: SIGSEGV [segmentation fault]
Aborting.
Exiting.
Name subsystem shut down
Allocation checking disabled
Segmentation fault

LIBGL_DEBUG was set at 'verbose'. Tested on 3.14.58 and 4.0.4 kernels with catalyst 12.9 and 12.15 and a HD7870. Any suggestions?

Vi0L0 · 2016-01-04 20:20:57

ElNinijo wrote:

catalyst-total-hd234k 13.1-32

ok, the updated driver is on the AUR, should work fine - should because I don't have hardware to test it.
Also please read comment that I posted there about testing driver - i'm looking for a "daredevil", if you have time - feel free to jump in .

@nous:
maybe:

coredumpctl
coredumpctl gdb <PID>

will give more debug info

Last edited by Vi0L0 (2016-01-04 20:25:22)

dens · 2016-01-09 16:51:36

Hi.
Like ElNinijo, i coulnd't build fglrx module for linux 4.3.3-2 but it worked for linux-lts 4.1.15-1 (i686).

I used catalyst-total-hd234k 13.1-32 from AUR.
With a Downgrade to linux 4.2.5-1 everything was fine.

I followed Vi0L0's advice and tried updated catalyst-total-hd234k 13.1-33.
Both modules for linux 4.3.3-2 and linux-lts 4.1.15-1 built correctly.

gcc49 4.9.3-1 was installed. Should i remove it now ?

Thank you Vi0l0 for your work !

Vi0L0 · 2016-01-10 15:09:31

dens wrote:

I followed Vi0L0's advice and tried updated catalyst-total-hd234k 13.1-33.
Both modules for linux 4.3.3-2 and linux-lts 4.1.15-1 built correctly.

So you are my daredevil , thank you.

dens wrote:

gcc49 4.9.3-1 was installed. Should i remove it now ?

Yes, it should be safe to remove. 13.1-33* doesn't use it.

dens · 2016-01-10 16:44:01

Vi0L0 wrote:

Yes, it should be safe to remove. 13.1-33* doesn't use it.

Ok, i tried it.

sudo pacman -R gcc49

catalyst_build_module all
Building fglrx module for 4.1.15-1-lts kernel ...
Ok.
Building fglrx module for 4.3.3-2-ARCH kernel ...
Ok.

It works!
Thanks again.

dens

fixide · 2016-01-12 22:36:45

I'll ask some stupid questions but I always stayed with the opensource driver.

Is the final catalyst is compatible with kernel 4.3 / 4.4? With the last mesa-git + DRI3? There is there a specific installation for users of modded kernels (ck) ?

clfarron4 · 2016-01-13 16:03:11

fixide wrote:

I'll ask some stupid questions but I always stayed with the opensource driver.
Is the final catalyst is compatible with kernel 4.3 / 4.4? With the last mesa-git + DRI3? There is there a specific installation for users of modded kernels (ck) ?

It works for dens, so it should just work for kernel 4.3. Hell knows about kernel 4.4, because that's not even become stable yet.

For custom kernels, use the catalyst-hook package, as it builds the module for all the kernels installed on your system.

Vi0L0 · 2016-01-13 17:34:02

Actually stable 4.4 was released 3 days ago. It is (unoficially - with community patches) supported by catalyst-test@AUR, catalyst-firepro@AUR, testing catalyst-total-hd234k@AUR and pkgs from [catalyst] repo. Other packages supports up to 4.3 kernel.
As for ck I wasn't using it for some time, can't tell for sure but should work just fine, if not - let me know.

Last edited by Vi0L0 (2016-01-13 17:39:44)

Jannis · 2016-01-13 19:48:42

I'm using catalyst-hook 15.12-1 with linux-ck-k10 4.3.3-2 and it works fine. Well, "fine" by catalyst standards... As in, it works and all but performance could be a lot better.

Amanda S · 2016-01-17 22:49:31

Vi0L0 wrote:

Amarildo wrote:
Vi0L0 wrote:
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).
So, how is it going?
Here is the source file of catalyst-grsec package: http://catalyst.wirephire.com/tarball/catalyst-grsec/
The bad side is that it has to be build on booted grsec kernel, if you want i can also give you catalyst-hook source but it will build modules only for grsec kernel...
For now it's kinda dirty and 15.9 only (but it works with gcc 5), in a free time (could be not that soon) I will try to modify it and add to main catalyst packages.
Tested on current community 4.2.7 grsec kernel, with kernel.grsecurity.harden_ipc set to 0, as it was the most easy and noobish solution to get rid of 'denied write of overly-permissive IPC object' error ;P
Edit: ok, got working grsec build-in into standard catalys-hook 15.9 package, will release it soon to stable repo and aur
So to summarize: there will be 2 big 15.9 updates today in stable repo, while none of them was tested by the community (cross your fingers)... don't like it, but catalyst-test is already owned by 15.11
edit2: on i686 im getting error while building fglrx module for community's grsec kernel:
cc1: error: fail to initialize plugin ./tools/gcc/size_overflow_plugin/size_overflow_plugin.so
somehow i feel that it will be gone after compiling linux-grsec from the ground - edit3: hehe, was right , compiling linux-grsec without changing a thing in config or anything fixed the problem, probably i686 community linux-grsec build should be fixed

Ok, so just to clarify:
[catalyst-stable] repo still has 15.9 but has been upgraded:
- gcc49 was removed, you can remove it as wel,
- new catalyst-hook and catalyst-generator packages contains new patches from crimson 15.11, also initial grsec kernel support has been added,
- catalyst pkg was removed, you should switch to catalyst-hook or catalyst-generator
Also AUR's catalyst, catalyst-generator and catalyst-hook were updated in same way.
There's also archive repository in case of problems:
[catalyst-stable-15.9-gcc49]
Server = http://mirror.rts-informatique.fr/archl … lyst/$arch
Server = http://catalyst.wirephire.com/repo/catalyst/$arch

Thanks, but I'm confused. If I just add your repo and install Catalyst as per Wiki, will it automatically build the grsec modules?

BTW, I'm using default linux-grsec x64 from Arch's repo.

Edit: Didnt make it.

+ building fglrx module for 4.3.3.201601161757-1-grsec kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log

I'll download what you posted to see if I can build it with that.

Last edited by Amanda S (2016-01-18 00:48:45)

Vi0L0 · 2016-01-18 13:30:33

The log should tell us whats going on. On x86_64 I'm often catching "cc1: error: incompatible gcc/plugin versions" error, which I believe is happening because I'm using gcc-multilib (while linux-grsec maintainer probably not). To fix this I'm simply compiling linux-grsec package from abs, and it's working fine. BTW will check newest linux-grsec build asap
edit: checked x86_64 catalyst-hook 15.12-1, woks fine on (compiled on my own, but without modifications) 4.3.3.201601171913-1-grsec

Last edited by Vi0L0 (2016-01-18 15:13:46)

Kozeid · 2016-01-19 20:13:40

catalyst-total@AUR is conflicting with lib32-libva.

resolving dependencies...
looking for conflicting packages...

Package (1)           New Version  Net Change

multilib/lib32-libva  1.6.2-1        0.25 MiB

Total Installed Size:  0.25 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [----------------------] 100%
(1/1) checking package integrity                   [----------------------] 100%
(1/1) loading package files                        [----------------------] 100%
(1/1) checking for file conflicts                  [----------------------] 100%
error: failed to commit transaction (conflicting files)
lib32-libva: /usr/lib32/dri exists in filesystem
Errors occurred, no packages were upgraded.

Please fix it.

Vi0L0 · 2016-01-19 22:11:16

Wow, this one must have been there for a long, long time! Thanks mate
Fixed in catalyst-total 15.9-10, other packages should catch this fix tomorrow

Amanda S · 2016-01-20 19:45:51

Vi0L0 wrote:

The log should tell us whats going on. On x86_64 I'm often catching "cc1: error: incompatible gcc/plugin versions" error, which I believe is happening because I'm using gcc-multilib (while linux-grsec maintainer probably not). To fix this I'm simply compiling linux-grsec package from abs, and it's working fine. BTW will check newest linux-grsec build asap
edit: checked x86_64 catalyst-hook 15.12-1, woks fine on (compiled on my own, but without modifications) 4.3.3.201601171913-1-grsec

Yes. I got it to build the modules just fine. However, when I issue the "aticonfig" command, this happens:

[root@amarildo ~]# aticonfig --initial
aticonfig: error while loading shared libraries: libGL.so.1: failed to map segment from shared object

Here's some info that might help:

[amarildo@amarildo catalyst-test]$ ldconfig -p | grep libGL.so.1
	libGL.so.1 (libc6,x86-64) => /usr/lib/libGL.so.1
	libGL.so.1 (libc6) => /usr/lib32/libGL.so.1

[amarildo@amarildo catalyst-test]$ echo $LD_LIBRARY_PATH

[amarildo@amarildo catalyst-test]$

What I have installed from Catalyst:

[root@amarildo ~]# pacman -S catalyst-hook catalyst-utils catalyst-libgl opencl-catalyst lib32-catalyst-utils lib32-catalyst-libgl lib32-opencl-catalyst
resolving dependencies...
looking for conflicting packages...
:: catalyst-libgl and mesa-libgl are in conflict (libgl). Remove mesa-libgl? [y/N] y
:: lib32-catalyst-libgl and lib32-mesa-libgl are in conflict (lib32-libgl). Remove lib32-mesa-libgl? [y/N] y
warning: dependency cycle detected:
warning: catalyst-libgl will be installed before its catalyst-utils dependency
warning: dependency cycle detected:
warning: catalyst-libgl will be installed before its catalyst-utils dependency

Packages (9) lib32-mesa-libgl-11.1.1-1 [removal]  mesa-libgl-11.1.1-1 [removal]
             catalyst-hook-15.12-1  catalyst-libgl-15.12-1  catalyst-utils-15.12-1
             lib32-catalyst-libgl-15.12-1  lib32-catalyst-utils-15.12-2
             lib32-opencl-catalyst-15.12-1  opencl-catalyst-15.12-1

Total Installed Size:  410.33 MiB
Net Upgrade Size:      410.32 MiB

:: Proceed with installation? [Y/n] 
(7/7) checking keys in keyring                               [################################] 100%
(7/7) checking package integrity                             [################################] 100%
(7/7) loading package files                                  [################################] 100%
(7/7) checking for file conflicts                            [################################] 100%
(9/9) checking available disk space                          [################################] 100%
(1/2) removing lib32-mesa-libgl                              [################################] 100%
(2/2) removing mesa-libgl                                    [################################] 100%
(1/7) installing catalyst-libgl                              [################################] 100%
(2/7) installing catalyst-utils                              [################################] 100%
----------------------------------------------------------------
PLEASE NOTE:
For these drivers to work, you must install kernel modules.

Simply use packages that provides auto re-compilation:
catalyst-hook or catalyst-daemon

OR use catalyst-generator package to generate catalyst-{kernver}
packages
----------------------------------------------------------------
You can use the tool 'aticonfig' to generate xorg.conf file.
--------------------- ^^^^^^^^^ --------------------------------
Add nomodeset to your kernel line in /boot/grub/menu.lst , ie.:
kernel /boot/vmlinuz-linux root=/dev/sda1 ro nomodeset
----------------------------------------------------------------
IMPORTANT:
fglrx was added into /etc/modules-load.d/catalyst.conf
----------------------------------------------------------------
	atieventsd (needs acpid pkg) on systemd:
systemctl enable atieventsd
systemctl start atieventsd
----------------------------------------------------------------
For more info and troubleshooting visit:
http://wiki.archlinux.org/index.php/ATI_Catalyst
----------------------------------------------------------------
-------------------------- SPLIT -------------------------------
catalyst-utils is splitted into:
catalyst-utils
catalyst-libgl
opencl-catalyst
You MOST probably want to also install catalyst-libgl
----------------------------------------------------------------
------------ DROPPED SUPPORT FOR RADEONS HD 5 6 k --------------
Please note that this release SADLY :( is
dropping support for pre-GCN cards so mainly
Radeons of series 5000 and 6000
----------------------------------------------------------------
Optional dependencies for catalyst-utils
    qt4: to run ATi Catalyst Control Center (amdcccle)
    libxxf86vm: to run ATi Catalyst Control Center (amdcccle) [installed]
    acpid: acpi event support / atieventsd
    catalyst-libgl: Catalyst drivers libraries symlinks. [installed]
    opencl-catalyst: OpenCL implemention for AMD Catalyst [pending]
    procps-ng: brings pgrep used in acpi event support [installed]
    lib32-catalyst-utils: Utilities and libraries (32-bit) [pending]
(3/7) installing catalyst-hook                               [################################] 100%
+ building fglrx module for 4.3.3.201601192226-1-grsec kernel ...
  ok.
+ building fglrx module for 4.3.3-3-ARCH kernel ...
  ok.
------------------------- ANGELA -------------------------------
To enable 'automatic re-compilation while system shutdown/reboot' 
feature run these commands as root:
systemctl enable catalyst-hook
systemctl start catalyst-hook

More info here:
https://bbs.archlinux.org/viewtopic.php?pid=1255575#p1255575
----------------------------------------------------------------
Optional dependencies for catalyst-hook
    linux-lts-headers: to build the fglrx module for the linux-lts kernel
(4/7) installing opencl-catalyst                             [################################] 100%
Optional dependencies for opencl-catalyst
    opencl-headers: headers necessary for OpenCL development
(5/7) installing lib32-catalyst-utils                        [################################] 100%
----------------------------------------------------------------
lib32-catalyst-utils works with [multilib] repository
----------------------------------------------------------------
-------------------------- SPLIT -------------------------------
lib32-catalyst-utils is splitted into:
lib32-catalyst-utils
lib32-catalyst-libgl
lib32-opencl-catalyst
----------------------------------------------------------------
Optional dependencies for lib32-catalyst-utils
    lib32-catalyst-libgl: Catalyst drivers libraries symlinks (32-bit) [pending]
    lib32-opencl-catalyst: OpenCL implemention for AMD Catalyst (32-bit) [pending]
(6/7) installing lib32-catalyst-libgl                        [################################] 100%
(7/7) installing lib32-opencl-catalyst                       [################################] 100%
Optional dependencies for lib32-opencl-catalyst
    opencl-headers: headers necessary for OpenCL development
[root@amarildo ~]# ldconfig -p | grep libGL.so.1
	libGL.so.1 (libc6,x86-64) => /usr/lib/libGL.so.1
	libGL.so.1 (libc6) => /usr/lib32/libGL.so.1

Then I remember that some Steam games faced the same problem, so I applied the same fix for aticonfig:

[root@amarildo ~]# setfattr -n user.pax.flags -v "m" /usr/bin/aticonfig 
[root@amarildo ~]# aticonfig --initial
Uninitialised file found, configuring.
Using /etc/X11/xorg.conf
Saving back-up to /etc/X11/xorg.conf.original-0

So, before rebooting, I must know: what else might need Pax permissions to run?

EDIT: Tried doing the same to amdccle, didn't work:

[root@amarildo ~]# setfattr -n user.pax.flags -v "m" /usr/bin/amdcccle
[root@amarildo ~]# amdcccle 
amdcccle: error while loading shared libraries: libQtGui.so.4: cannot open shared object file: No such file or directory

EDIT 2: After rebooting, the driver seems to load fine, but grsec is blocking some stuff and the login manager (be it slim or sddm) is black. After doing "sysctl kerne.pax.softmode=1" I was able to start the login manager. BUT REMEMBER: This is NOT a login manager vs grsec problem, it's completely related to Catalyst.

Last edited by Amanda S (2016-01-20 20:18:00)

Vi0L0 · 2016-01-21 08:10:27

Did you install qt4 package?

btw: atm i really don't have time to look @ grsec. It's rather hard to me to imagine how this could be catalyst fault when it's managed by a software able to controll stack or IPC. Not telling it's not possible, only hard to imagine. I want to know grsec but for now I just don't have time for this, probably in march I should find some day or two to sit on it. Latelly I have seen probably nice blog post about grsec if someone is interested: https://micahflee.com/2016/01/debian-grsecurity/ , when looking at the world of today I think that we should all consider using this and/or other methods which are exchanging security

Last edited by Vi0L0 (2016-01-21 08:31:34)

Amanda S · 2016-01-22 21:48:22

Vi0L0 wrote:

Did you install qt4 package?
btw: atm i really don't have time to look @ grsec. It's rather hard to me to imagine how this could be catalyst fault when it's managed by a software able to controll stack or IPC. Not telling it's not possible, only hard to imagine. I want to know grsec but for now I just don't have time for this, probably in march I should find some day or two to sit on it. Latelly I have seen probably nice blog post about grsec if someone is interested: https://micahflee.com/2016/01/debian-grsecurity/ , when looking at the world of today I think that we should all consider using this and/or other methods which are exchanging security

Nah, I don't use anything related to KDE. Not anymore at least

I noticed a lot of XFCE stuff, like plugins, are struggling to work with catalyst's grsec-modules. I don't have time to look this up too, so don't worry. For now I'll just use the non-grsec kernel, my time is so limited right now that I get home from work and have to start working at my PC immediately.

But don't give up, though. Your work here in Arch is amazing, specially on the grsec side of things (it's not easy to make Catalyst build it's modules on grsec). So I'm sure that everything you done so far will help others!

Cheers.

fixide · 2016-01-23 11:54:29

I just installed the catalyst and I have some worries.

The scrolling is slow in firefox. Catastrophic when the acceleration is enabled. And means when it is turned off (there is a deadline for scrolling starts).

[edit] 100% cpu use when scrolling (xorg).

And I can not run xvba in VLC.
vdpauinfo
display:: 0 screen: 0
[VS] Software VDPAU initialized backend library
libva info: VA-API Version 0.38.1
libva info: va_getDriverName () returns 0
libva info: User requested driver 'xvba'
libva info: Trying to open /usr/lib/dri//xvba_drv_video.so
libva info: Found init function __vaDriverInit_0_32
libva info: va_openDriver () returns 0

But when I try:
[00007f2a38c0bf48] avcodec decoder: Using OpenGL / VAAPI / libswscale backend for VDPAU for hardware decoding.
[00007f2a08001268] vdpau_display vout display error: video mixer area width query capabilities failure: VDP_STATUS_NO_IMPLEMENTATION
[00007f2a3c0fd018] core video output error: video output creation failed
[00007f2a38c0bf48] core decoder error: failed to create video output

I used xvba package from vi0l0. Aur libva-xvba-driver fail to build.

Any tips?

Last edited by fixide (2016-01-23 21:51:29)

Primoz · 2016-01-26 20:09:17

So I've decided to transfer from catalyst to af86-video-ati drivers, and so far so good.
I was convinced that having a APU means that I won't ever be able to use opensource drivers, but apparently I was wrong, or they got way better since 2011.

Anyway, I must recommend that everyone tries opensource drivers again (especially if you're like me, just assuming that they won't work), because you might be positively surprised.

I mostly did it because, this was last attempt at getting steam games, especially Medieval 2: Total War, to work better, and surprisingly (or maybe not) they actually do.

Last edited by Primoz (2016-01-26 20:10:03)

bleach · 2016-01-26 22:05:08

Primoz I completely agree. I have a r7 and it is highly supported but I would look to the matrix's in this case ATI to see whats what in support for your card; the open driver I find is always better as long as it has support for the features you want not to mention its integration from kernel onward.

UsernameClassifed · 2016-02-01 01:33:05

I was recommended here from this thread. I've been having trouble installing the Catalyst drivers. I've tried the various unofficial repositories, but to no avail. It says I need one xorg-server version, but after downgrading it, it wants the other version. The specific errors I've gotten are in the linked thread, but I can post them here if needed. Thank you all!

hippieben · 2016-02-01 03:06:53

So here's an interesting question. Is there anyway that I can do a sort of hybrid set up?

What I mean is to have a normal extended desktop on 2 displays (DVI + VGA) and then a second screen (HDMI) that would just be for movie playback on a TV? I'd plan to control it via ssh and mpv. Any suggestions on how to do this all on the same graphics card?

Vi0L0 · 2016-02-01 09:05:44

UsernameClassifed wrote:

I was recommended here from this thread. I've been having trouble installing the Catalyst drivers. I've tried the various unofficial repositories, but to no avail. It says I need one xorg-server version, but after downgrading it, it wants the other version. The specific errors I've gotten are in the linked thread, but I can post them here if needed. Thank you all!

Did you add [xorg117] repo atop of other repos of /etc/pacman.conf file and then perform pacman -Syuu?

pvinis · 2016-02-06 14:25:09

while updating, i read that support for radeon 5 was stopped. so which version of catalyst-hook do i need, with a radeon 5 card? and which repo? now i use [catalyst-stable] and [xorg117].

Arch Linux

#7276 2016-01-04 07:26:42

Re: The AMD/ATI Bar & Grill

#7277 2016-01-04 16:16:49

Re: The AMD/ATI Bar & Grill

#7278 2016-01-04 18:18:11

Re: The AMD/ATI Bar & Grill

#7279 2016-01-04 20:20:57

Re: The AMD/ATI Bar & Grill

#7280 2016-01-09 16:51:36

Re: The AMD/ATI Bar & Grill

#7281 2016-01-10 15:09:31

Re: The AMD/ATI Bar & Grill

#7282 2016-01-10 16:44:01

Re: The AMD/ATI Bar & Grill

#7283 2016-01-12 22:36:45

Re: The AMD/ATI Bar & Grill

#7284 2016-01-13 16:03:11

Re: The AMD/ATI Bar & Grill

#7285 2016-01-13 17:34:02

Re: The AMD/ATI Bar & Grill

#7286 2016-01-13 19:48:42

Re: The AMD/ATI Bar & Grill

#7287 2016-01-17 22:49:31

Re: The AMD/ATI Bar & Grill

#7288 2016-01-18 13:30:33

Re: The AMD/ATI Bar & Grill

#7289 2016-01-19 20:13:40

Re: The AMD/ATI Bar & Grill

#7290 2016-01-19 22:11:16

Re: The AMD/ATI Bar & Grill

#7291 2016-01-20 19:45:51

Re: The AMD/ATI Bar & Grill

#7292 2016-01-21 08:10:27

Re: The AMD/ATI Bar & Grill

#7293 2016-01-22 21:48:22

Re: The AMD/ATI Bar & Grill

#7294 2016-01-23 11:54:29

Re: The AMD/ATI Bar & Grill

#7295 2016-01-26 20:09:17

Re: The AMD/ATI Bar & Grill

#7296 2016-01-26 22:05:08

Re: The AMD/ATI Bar & Grill

#7297 2016-02-01 01:33:05

Re: The AMD/ATI Bar & Grill

#7298 2016-02-01 03:06:53

Re: The AMD/ATI Bar & Grill

#7299 2016-02-01 09:05:44

Re: The AMD/ATI Bar & Grill

#7300 2016-02-06 14:25:09

Re: The AMD/ATI Bar & Grill

Board footer