spO | https://bugs.launchpad.net/ubuntu/karmic/+source/fglrx-installer/+bug/440233 <-- this is why ati sucks, I haven't been able to play 1080p movies since karmic fresh install | 03:43 |
---|---|---|
ubottu | Ubuntu bug 440233 in fglrx-installer "fglrx fails at startup because of missing amdpcsdb.default + removal leaves bad settings in Xorg.conf" [High,Confirmed] | 03:43 |
=== _stink__ is now known as _stink_ | ||
superm1 | spO, do you have a reliable way to reproduce that bug from a fresh install? | 03:58 |
spO | yes | 03:58 |
spO | use 3000-3999 ati series card | 03:58 |
spO | install karmic | 03:58 |
superm1 | i've seen it reported a few times, but people tend to be messing with their systems | 03:58 |
spO | enable fglrx | 03:59 |
spO | done | 03:59 |
spO | it is a bug for only 3000-3999 series cards | 03:59 |
superm1 | i would tend to believe that's not all there is to reproducing it otherwise everyoen would reproduce it | 03:59 |
superm1 | a missing conf file only on certain hardware? | 03:59 |
superm1 | that's ridiculous | 03:59 |
spO | nope | 03:59 |
superm1 | being incompatible with hardware, that's a different bug | 04:00 |
spO | everyone can reproduce it , they mostly do not enable fglrx like i do | 04:00 |
superm1 | well how are you enabling it? | 04:00 |
superm1 | that's exactly what i'm getting at, we don't have an EXACT scenario to reproduce it | 04:00 |
spO | i gave you the exact one okay | 04:03 |
spO | i can enable it via xwindows or through the driver via download amd site | 04:03 |
spO | i will try something again | 04:05 |
spO | but i doubt it will work | 04:05 |
spO | okay | 04:05 |
spO | if it makes you happy | 04:05 |
spO | superm1, look at this | 04:06 |
spO | https://launchpad.net/ubuntu/+source/fglrx-installer/+bugs | 04:06 |
spO | that suggests that everyone else does have it | 04:06 |
spO | not just a few | 04:06 |
spO | understand? | 04:06 |
spO | thanks for driving through | 04:06 |
superm1 | i'm glad to help debug this problem, I just need a set of reproducible steps that I can run through to evaluate what causes it | 04:07 |
superm1 | and that list of bugs just suggests that there are a lot of people with bugs | 04:07 |
superm1 | not a lot of people who are missing amdpcsdb.default | 04:07 |
spO | fine | 04:08 |
spO | i will in a few days | 04:08 |
spO | my system is doing something right now and i rather not reboot | 04:08 |
spO | http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg1843314.html | 04:23 |
superm1 | which still doesn't give a scenario to reproduce it | 04:26 |
spO | superm1, maybe i hate you maybe i don't | 04:29 |
spO | what should it be? | 04:29 |
superm1 | 1) install karmic. 2) touch file X, Y, Z. 3) install package A,B 4) install fglrx using hardware drivers tool | 04:30 |
superm1 | or maybe: | 04:30 |
superm1 | 1) install karmic. 2) touch file X, Y, Z. 3) install package A,B 4) install fglrx version D.E.F from AMD website | 04:30 |
spO | i guessi can install karmic on a flash drive? | 04:30 |
spO | i dont' really want to do a fresh install like this url suggests | 04:31 |
spO | what do you think? | 04:31 |
superm1 | you are able to, just make sure that you pick the right device to install the boot loader to in the advanced dialog at the end | 04:31 |
spO | how big does it have to be at least ? | 04:31 |
spO | 2gb? | 04:31 |
superm1 | it will default to your first BIOS drive usually, which can cause some weird stuff for you | 04:31 |
superm1 | not sure these days what the minimum is | 04:31 |
superm1 | worst comes to worst, it will fill up and not work | 04:31 |
Cur5ed | Hello all, I am running Intrepid amd64 in low graphics mode, I get an error at startup saying "intel(0): No valid modes". Is this a problem in xorg.conf or a bug in intel driver or what? | 14:15 |
Cur5e | When I get an error in Xorg saying "intel(0): No valid modes" does this mean a problem in xorg.conf or a problem in intel driver itself?? | 17:44 |
mac_v | hmm , anyone know how to disable KMS in kernel .32 ? | 20:05 |
mac_v | for ATI | 20:05 |
bryce | https://wiki.ubuntu.com/X/KernelModeSetting | 20:07 |
Sarvatt | what package is xcb proto in? dont see an x11proto-* for it | 20:16 |
Sarvatt | oh wow I'm slow, xcb-proto it is :D | 20:16 |
bryce | xcb-proto yeag | 20:17 |
bryce | weird, wonder why that's named differently | 20:17 |
Sarvatt | need xcb-proto 1.6 and libxcb 1.5 from unstable to build xvmc support for intel now :( | 20:22 |
Sarvatt | source format 3, go figure | 20:22 |
Sarvatt | cant sync it | 20:22 |
jcristau | bryce: it's named differently because it's unrelated | 20:25 |
bryce | jcristau, unrelated? | 20:26 |
jcristau | it's not the C protocol headers for a specific extension | 20:27 |
jcristau | it's xml descriptions for the protocol | 20:27 |
bryce | ah | 20:27 |
jcristau | sort of related since it's all X11, but still | 20:27 |
Sarvatt | got a patch to make evtouch compile fine against xserver 1.7/1.8, http://sarvatt.com/downloads/patches/901_xserver_1_7_fix.patch | 20:51 |
Sarvatt | no clue if things work though, nothing to test it on. uploaded it to edgers though | 20:52 |
Sarvatt | would something like this work for an xserver-xorg-input-joystick udev rule? http://sarvatt.com/downloads/joystick_rules.txt | 22:39 |
Sarvatt | i have no clue how they work, just saw there was a ID_INPUT_JOYSTICK in 60-persistent-input.rules and copied the stuff out of the old fdi using the synaptics udev rule as a template | 22:45 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!