Originally posted by zika
View Post
Announcement
Collapse
No announcement yet.
Getting Open Source 3D graphics on R6XX/R7XX cards (NO FGLRX)
Collapse
X
-
Originally posted by Neo_The_User View PostMesa is kernel independent so yes. 7.7-devel will work. I've used it on 2.6.24 and it worked just fine.
Update: It works now. It seems that external USB disk does not start in some predesignated time sometime ... That disk was not here when the crashes happened so that is not the culprit for those experiences.Last edited by zika; 25 October 2009, 02:14 PM.
Comment
-
Originally posted by Neo_The_User View PostRe-installing a distro because X is broken is never ever necessary nor recommended. Next time, post /var/log/Xorg.0.log, dmesg, and xorg.conf file to pastebin so I can help you (or anybody who knows the answer) for next time. Thanks.
Comment
-
zika,
Are you east of UTC (i.e. GMT +xx)? If so, it could be due to the bugs below. I'm in Australia and experienced them when I resized my Jaunty partition and installed Karmic alpha4 (or 5, I forgot).
Binary package hint: e2fsprogs When you are East of UTC, and your hardware clock is in localtime not UTC, and you have to force power down, fsck fails on boot because the last write time is in the future. This is caused by a bug in the ext3/4 filesystem code in kernel, where it updates the superblock last write time from the system clock after replaying the journal - but the system clock contains localtime not UTC since we haven't had an opportunity to correct it yet. Ted Tso (ext3/4 upstr...
Binary package hint: gparted Running from a live cd image of ubuntu 9.04 through virtual box. When trying to shrink a partition (on a virtual box HDD) I got a message saying the e2fsck should be run on the affected partition. It was run and finished without errors: check file system on /dev/sda5 for errors and (if possible) fix them 00:04:02 ( SUCCESS ) e2fsck -f -y -v /dev/sda5 .... shrink file system 00:00:01 ( ERROR ) resize2fs /dev/sda5 15791863K resize2f...
Comment
-
Originally posted by pvautrin View Postzika,
Are you east of UTC (i.e. GMT +xx)? If so, it could be due to the bugs below. I'm in Australia and experienced them when I resized my Jaunty partition and installed Karmic alpha4 (or 5, I forgot).
Binary package hint: e2fsprogs When you are East of UTC, and your hardware clock is in localtime not UTC, and you have to force power down, fsck fails on boot because the last write time is in the future. This is caused by a bug in the ext3/4 filesystem code in kernel, where it updates the superblock last write time from the system clock after replaying the journal - but the system clock contains localtime not UTC since we haven't had an opportunity to correct it yet. Ted Tso (ext3/4 upstr...
https://bugs.launchpad.net/ubuntu/+s...ed/+bug/373409
Comment
-
Originally posted by zika View PostSince I'm using xorg-edgers also with 2.6.32-999, what is going to happen to my graphics if I upgrade to Lucid at this stage when xorg-edgers does not have Lucid covered? Am I going to degrade my graphics experience or what?
Note that xorg-edgers just tracks the development, it is not a guarantee of best performance or stability.
Comment
-
Originally posted by tormod View PostThere are no Lucid packages at this point so don't worry And if the packages you have installed (from a PPA) have a higher version than the Lucid version, they will not be upgraded.
Note that xorg-edgers just tracks the development, it is not a guarantee of best performance or stability.
Comment
-
Originally posted by zika View PostWhere can I find best performance and stability. I've searched around and came to xorg-edgers. When do You plan to open Lucid branch?
As long as you are capable of identifying when things work or not, and know how to revert to an older set of packages, and can tolerate the odd hang or crash, there is not much problem in using xorg-edgers IMO.
The Lucid branch will start soon, as soon as there will be some new Lucid Xorg packages, next week probably. For now only the Lucid kernel has been updated for what the Xorg stack is concerned.
Comment
Comment