Arch Linux

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

[RESOLVED] Issue with fglrx and OpenBox

Hey guys, I'm somewhat of a noob, having only ever used "easier" distros like Ubuntu and Mandrake in the past, and even that having been several years ago. That being said, I installed Arch on my Toshiba laptop two weeks ago and have been learning a lot since then. I had pretty much everything working fairly easily and had all but abandoned my Windows partition over the past week, even when doing work.

Then came today.

I'm not sure what broke, but something apparently happened this morning shortly after I did an update when I had a lockup that required a reboot. Upon rebooting, my keyboard, Synaptics touchpad, and external mouse no longer worked, rendering my machine useless, at least in X. I reviewed Xorg.0.log, and it seemed like for some reason udev and evdev were going crazy, trying to use the 'synaptics' driver for everything from the webcam to the lid switch. InputClasses also seemed to be assigned arbitrarily. Not knowing where the heck to start, I first reinstalled udev, xorg-server, and the xf86-inputs. Then, not knowing what else to do, I started experimenting with my xorg.conf setup and eventually managed to get my keyboard and external mouse back somehow.

At this point, my Synaptic touch pad is still not working at all, but this sadly isn't my biggest concern now. Somewhere along the way, my resolution in OpenBox decided to go all squashy, despite that I hadn't touched any of the video-related settings in Xorg.conf. Fglrx still seems to be working fine, and everything looks great in LXDM. Things also seem normal when OpenBox first loads, but several seconds later the screen flashes and I get a weird, horizontally stretched resolution that distorts fonts and, oddly, won't let me move my cursor into the lower 20% of the screen. I've done everything from rerunning 'aticonfig --initial' to reinstalling the catalyst package. Nada.

Add in that, sometime in the last half hour, my wifi also stopped cooperating, even via terminal. Wicd won't even start, but also does not throw any errors. I have no idea where to even begin with this new problem, nor what might have caused it since I have done absolutely zilch to wifi related stuff as far as I'm aware.

Can anyone tell me why my install seems to be imploding, or at least help me fix some small part of it to preserve my sanity? At this point would it be better for me to just backup my /home folders and start from scratch?

Here's xorg.conf, which only contains video settings. Everything else is in xorg.conf.d.

Section "ServerLayout"
	Identifier     "aticonfig Layout"
	Screen      0  "aticonfig-Screen[0]-0" 0 0
	Option	    "Composite" "Enable"
	Option	    "AIGLX" "True"
EndSection

Section "Module"
EndSection

Section "ServerFlags"
	Option	    "AutoAddDevices" "true"
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]-0"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]-0"
	Driver      "fglrx"
	BusID       "PCI:1:5:0"
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]-0"
	Device     "aticonfig-Device[0]-0"
	Monitor    "aticonfig-Monitor[0]-0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes "1366x768_60.00"
	EndSubSection
EndSection

Section "DRI"
	Mode         0666
EndSection

And here's the end of Xorg.0.log, which I think is related to whatever is going on with my resolution.

[    18.864] (II) fglrx(0): Restoring Recent Mode via PCS is not supported in RANDR 1.2 capable environments
[    25.565] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    25.566] (II) fglrx(0): Printing DDC gathered Modelines:
[    25.566] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    30.634] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    30.634] (II) fglrx(0): Printing DDC gathered Modelines:
[    30.634] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    30.659] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    30.659] (II) fglrx(0): Printing DDC gathered Modelines:
[    30.659] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    32.088] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    32.088] (II) fglrx(0): Printing DDC gathered Modelines:
[    32.088] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    32.340] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    32.340] (II) fglrx(0): Printing DDC gathered Modelines:
[    32.340] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    32.558] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    32.558] (II) fglrx(0): Printing DDC gathered Modelines:
[    32.558] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    33.256] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    33.256] (II) fglrx(0): Printing DDC gathered Modelines:
[    33.256] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    33.630] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    33.630] (II) fglrx(0): Printing DDC gathered Modelines:
[    33.630] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    33.929] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    33.930] (II) fglrx(0): Printing DDC gathered Modelines:
[    33.930] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    34.184] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    34.184] (II) fglrx(0): Printing DDC gathered Modelines:
[    34.184] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    34.630] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    34.630] (II) fglrx(0): Printing DDC gathered Modelines:
[    34.630] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    34.673] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    34.673] (II) fglrx(0): Printing DDC gathered Modelines:
[    34.673] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    34.738] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    34.738] (II) fglrx(0): Printing DDC gathered Modelines:
[    34.738] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    34.768] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    34.768] (II) fglrx(0): Printing DDC gathered Modelines:
[    34.768] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    35.046] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    35.047] (II) fglrx(0): Printing DDC gathered Modelines:
[    35.047] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    35.274] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    35.275] (II) fglrx(0): Printing DDC gathered Modelines:
[    35.275] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    35.298] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    35.298] (II) fglrx(0): Printing DDC gathered Modelines:
[    35.298] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    35.858] (II) fglrx(0): xdl_xs110_atiddxDisplayScreenEnableDisplays
[    36.358] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.358] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.358] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    36.436] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.436] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.436] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    36.536] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.537] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.537] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    36.580] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.580] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.580] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    36.627] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.627] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.627] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    36.684] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.684] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.684] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    36.746] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.746] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.746] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    36.801] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.801] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.801] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    36.847] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    36.847] (II) fglrx(0): Printing DDC gathered Modelines:
[    36.847] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    37.124] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    37.124] (II) fglrx(0): Printing DDC gathered Modelines:
[    37.124] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    37.163] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    37.163] (II) fglrx(0): Printing DDC gathered Modelines:
[    37.163] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)
[    37.193] (II) fglrx(0): EDID vendor "AUO", prod id 8284
[    37.193] (II) fglrx(0): Printing DDC gathered Modelines:
[    37.193] (II) fglrx(0): Modeline "1366x768"x0.0   72.00  1366 1414 1446 1494  768 771 777 803 -hsync -vsync (48.2 kHz)

Help?

Last edited by CBAmazing (2012-02-25 16:54:47)

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

Fixed the wifi issue. Dbus was not loaded for some reason.

The video issue is still giving me fits, however.

cfr

Member

From: Cymru

Registered: 2011-11-27

Posts: 7,178

Re: [RESOLVED] Issue with fglrx and OpenBox

What was updated?

You're not running gnome by any chance, are you?

---

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

No, just OpenBox. The only upgrades around the time everything went to crap were libart-lgpl, libxdamage, libxrender, and xorg-fonts-misc.

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

Okay, so what I've determined is that xrandr is forcing a resolution of 1366x984, when my native resolution is 1366x768.  Unfortunately I can't seem to make it take the correct resolution.  Strangely, I'm pretty sure the area I can move my cursor is in is 1366x768, and the remaining 200-odd pixels at the bottom of the screen are off limits for whatever reason.  It's like I'm stuck between resolutions or something.

Any ideas?

shyn

Member

Registered: 2009-09-23

Posts: 16

Re: [RESOLVED] Issue with fglrx and OpenBox

Do you tried to boot without xorg.conf? It's not necessary recently, the xorg.conf.d is enough.

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

Yes, I have tried that. The reason I have xorg.conf (and not xorg.conf.d/20-gpudriver.conf) is that the catalyst software doesn't recognize 20-gpudriver.conf.  As you can see above, my xorg.conf is pretty much the standard file generated by 'aticonfig -initial'.  I did try moving the video settings to 20-gpudriver.conf and getting rid of xorg.conf, with the same exact results.  I then got rid of both, and x would not start at all because no video driver is loaded.  Here's the last few lines of Xorg.0.log with no xorg.conf:

(EE) Failed to load module "ati" (module does not exist, 0)
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) No drivers available.

Fatal server error:
no screens found

Why does it try loading those standard drivers but not fglrx?  Is there somewhere else fglrx should be specified other than in xorg.conf or xorg.conf.d?

The most confusing thing to me is the part where everything looks awesome in LXDM and for the first several seconds after OpenBox loads.  Then the screen flickers and it comes back looking like it's been jumped on repeatedly by a fat guy.  I'm admittedly a newb, but it seems like that would mean something that's loading after X starts and OpenBox starts loading is causing this.  I even tried commenting out everything in autostart, but I get the same thing regardless.

Last edited by CBAmazing (2012-02-18 15:33:46)

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

Just as a short update, logging out of OpenBox and returning to LXDM carries the wonkiness over to LXDM until a reboot.  I installed FluxBox just to experiment, and it loads perfectly fine without any crazy resolution issues.  It definitely seems like this is something that OpenBox or some OpenBox configuration file that I'm unaware of is doing.  That said, I'd rather not switch permanently to a different window manager if I don't have to.

t1nk3r3r

Member

From: The Pacific Northwest

Registered: 2011-03-22

Posts: 79

Re: [RESOLVED] Issue with fglrx and OpenBox

For starters, 'xorg.conf' supercedes 'xorg.conf.d'.  'fglrx' itself does not rely on 'xorg.conf' but 'aticonfig'/AMDCCCLE does.  You can use the file or the directory, but not both.  If you want to use xorg.conf, make sure everything from xorg.conf.d/*.conf is included.
X will never look for 'fglrx' by default.  You might blacklist the 'radeon' module if you don't plan to use the open source driver.

Check out:
https://wiki.archlinux.org/index.php/Fg … figuration
https://wiki.archlinux.org/index.php/Xo … ze_and_DPI

Secondly, Openbox and Fluxbox are merely Window Managers.  AFAIK they do not handle the resolution.
https://wiki.archlinux.org/index.php/Window_Manager

LXDM is the Display Manager (for logging in only).
https://wiki.archlinux.org/index.php/Display_Manager

How do you start Openbox? Fluxbox? LXDE?
Which daemons are you loading?

It is always a good idea to have /home on a separate partition.  This way you can wipe the rest of your system without losing personal files (and retain some settings).

In my experience, reinstalling tends not to fix anything.  When all else fails: write down your uid/gid, make note of which partition is /home (e.g. sda5), print the output of 'pacman -Qe' and install from scratch.

The wiki should be your Arch handbook.  Man pages are helpful too.

---

--------------------------The only wasted day is one in which you learn nothing.--------------------------

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

For starters, 'xorg.conf' supercedes 'xorg.conf.d'.  'fglrx' itself does not rely on 'xorg.conf' but 'aticonfig'/AMDCCCLE does.  You can use the file or the directory, but not both.  If you want to use xorg.conf, make sure everything from xorg.conf.d/*.conf is included.
X will never look for 'fglrx' by default.  You might blacklist the 'radeon' module if you don't plan to use the open source driver.

Check out:
https://wiki.archlinux.org/index.php/Fg … figuration
https://wiki.archlinux.org/index.php/Xo … ze_and_DPI

Secondly, Openbox and Fluxbox are merely Window Managers.  AFAIK they do not handle the resolution.
https://wiki.archlinux.org/index.php/Window_Manager

LXDM is the Display Manager (for logging in only).O
https://wiki.archlinux.org/index.php/Display_Manager

How do you start Openbox? Fluxbox? LXDE?
Which daemons are you loading?

It is always a good idea to have /home on a separate partition.  This way you can wipe the rest of your system without losing personal files (and retain some settings).

In my experience, reinstalling tends not to fix anything.  When all else fails: write down your uid/gid, make note of which partition is /home (e.g. sda5), print the output of 'pacman -Qe' and install from scratch.

The wiki should be your Arch handbook.  Man pages are helpful too.

Thanks for the reply.  I'm not quite a complete novice to Linux as a whole (just Arch), so I know most of the things you said, but the help is appreciated.  I have read all of the Wiki articles you posted already multiple times trying to solve this issue, as well as countless other Wiki articles and forum posts.  I spent several hours trying to resolve this issue on my own before ever asking for help.  I already treat the Wiki and this forum as my handbooks, and normally I am able to resolve any issues I face on my own.

I was originally under the impression that xorg.conf and xorg.conf.d worked as you say, as well.  In practice, however, they load in conjunction.  My current understanding is if I had GPU settings in a .conf file in xorg.conf.d as well as in xorg.conf, the settings in xorg.conf would supercede those in xorg.conf.d.  On the other hand, because I -only- have GPU settings in xorg.conf, and all of my other settings (such as keyboard and other inputs) are in separate files in xorg.conf.d, it loads them independently as there is no conflict.  I know this is true because all of my keyboard settings currently load with this setup, not to mention all of the evdev 'catch-alls' from 10-evdev.conf that I can see working in my Xorg.0.log file.  While it may not be the preferred setup, it works for me so that aticonfig/Catalyst is happy.

I also never intended to imply that OpenBox itself was responsible for my issue.  As I said, OpenBox first loads in my native resolution and looks fine.  It isn't until 4-5 seconds later that the screen flickers and returns in an incorrect, squashed resolution with a very wrong aspect ratio.  It should be mentioned that I -can- change the resolution after this, but only to other resolutions with the same, incorrect aspect ratio.  I don't think OpenBox itself is causing this, but it seems apparent to me that OpenBox is loading something that -is- causing it, as I -only- have this issue inside of OpenBox.  LXDM looks perfect pre-login, and Fluxbox has always displayed everything in my native resolution without my intervention.  Once I load OpenBox and trigger this issue, however, logging out of OpenBox and back into LXDM, or subsequently into Fluxbox, does not solve the issue.  It originates with loading OpenBox and persists until reboot.

As for my specific start-up configuration, LXDM is loaded via inittab.  From there, I log directly into OpenBox (or Fluxbox, as the case may now be).  I like Fluxbox for what it is, but I would be much happier to get OpenBox working again.

Straight from rc.conf:

DAEMONS=(autofglrx !dbus hal syslog-ng wicd @acpid @alsa)

Any other ideas?

Last edited by CBAmazing (2012-02-20 10:38:01)

Gusar

Member

Registered: 2009-08-25

Posts: 3,607

Re: [RESOLVED] Issue with fglrx and OpenBox

You can use the file or the directory, but not both.

Wrong. You can very much use both. xorg.conf the equivalent of xorg.conf.d/99-something.conf, as in it is parsed last, after all the other files in the dir. This means xorg.conf has the highest priority, but everything set in other files is still in effect. So you do *not* need to include everything from the dir into xorg.conf, it can contain just the fglrx specific bits.

And the reason you need fglrx specific bits is a deliberate choice: As CBAmazing noticed, only the open source driver will be loaded by default (along with the fallbacks). To use fglrx, you need to explicitly activate it. But doing so requires at minimum only four lines:

Section "Device"
    Identifier  "Radeon Card"
    Driver      "fglrx"
EndSection

Whether you put those in xorg.conf or in xorg.conf.d/50-blah.conf makes no difference.

Last edited by Gusar (2012-02-20 10:43:41)

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

You can use the file or the directory, but not both.

Wrong. You can very much use both. xorg.conf the equivalent of xorg.conf.d/99-something.conf, as in it is parsed last, after all the other files in the dir. This means xorg.conf has the highest priority, but everything set in other files is still in effect.

Beat you to it. Thanks for the confirmation that my understanding was right, though.

t1nk3r3r

Member

From: The Pacific Northwest

Registered: 2011-03-22

Posts: 79

Re: [RESOLVED] Issue with fglrx and OpenBox

I stand corrected.  And re-reading the man page for xorg.conf, it does indeed say that _all_ file locations are parsed.  I always assumed values that weren't stated would be autodetected (as some are).

Back to the issue at hand:
- I've used fglrx for the better part of four years, not familiar with the 'autofglrx' daemon.
- Any reason for using 'hal' and not loading 'dbus'?  I've been using Openbox for awhile and not needed it.

       ...The third option at log in, which is Openbox       without a session manager, uses the openbox-session       command to
       start  Openbox.  On  log  in, openbox will run the ~/.config/openbox/autostart.sh script if it exists, and will run the
       system-wide script /etc/xdg/openbox/autostart.sh otherwise. You may place anything you want  to  run  automatically  in
       those files...

- You said you had LXDM starting from /etc/inittab?  Do you have ~/.xinitrc ?
- Given your non-standard resolution, I would consider explictly stating modelines in xorg.conf (a PITA I know).
- I would also scan _everything_ in /var/log to see what openbox was doing if nothing is found in config files or startup scripts.

---

--------------------------The only wasted day is one in which you learn nothing.--------------------------

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

The 'autofglrx' package is the fglrx daemon for the alternate 'catalyst-daemon' package, which is available in the AUR.  It's the same driver as the fglrx package, but it auto-recompiles the fglrx module at boot if it detects a kernel upgrade.  I switched to this package from the standard fglrx driver after I had started having this problem, so it is not the culprit.

I installed hal because it is required to view some DRM-protected content on Amazon Prime's streaming video service.  Dbus is commented out because it is loaded automatically by hal. This was something that I changed shortly before the problems began, but I have tried switching it back without any change to the resolution problem.

Yes, LXDM starts from /etc/inittab, and I do have ~/.xinitrc.  Here it is:

#!/bin/bash
export BROWSER=chromium   
syndaemon -t -k -i 2 -d &
exec ck-launch-session dbus-launch openbox-session
xrandr --size 1366x768 &
xrandr --fb 1366x 768 &
cairo-compmgr &

The xrandr lines were an unsuccessful attempt to force the correct resolution.

I have not tried putting ModeLines in xorg.conf.  I will attempt that later tonight, but I do not have high hopes considering I can't seem to force ModeLines with xrandr.  I have been through practically every log in /var/log, but if the ModeLines don't change anything, I will also further pore over them tonight and update this thread with anything suspicious I find.  Thanks for the brainstorming. 

Last edited by CBAmazing (2012-02-20 22:51:42)

CBAmazing

Member

Registered: 2012-02-17

Posts: 10

Re: [RESOLVED] Issue with fglrx and OpenBox

Sorry, I got busy with other things and haven't had time to reply to this thread lately. I tried adding ModeLines to xorg.conf for the screen's native resolution, but it had no effect. I eventually got frustrated while poring through all of the log files and finding nothing, so I went with a fresh install, formatting my root partition. That cleared up whatever the problem was, and I've since reinstalled the fglrx drivers with no issues, so it was not any configuration file in my home directory nor a problem with the driver itself. Hopefully it stays away.

Thanks for the help, guys.