The problem I had was because of me. The KMS boot option needs 3 modules to be built in the initrd. My fault was creating a copy of /etc/mkinitcpio.conf to /etc/mkinitcpio-kms.conf, which creates /boot/kernel26-kms.img. Since this is useless (one can build the three modules in the stock kernel26.img and choose KMS using i915.modeset=1 or i915.modeset=0) So I changed all my machines to that setup, except my workstation which used the old kernel26-kms.img. So reinstalling the (arch) kernel did not fixed it: I needed to rebuild kernel26-kms.img Probably KDE was crashing because of its desktop effects... I'll see for the bug report. Even with this, KDE is a great desktop IMO. 2009/5/29 David C. Rankin, J.D.,P.E. <drankinatty@xxxxxxxxxxxxxxxxxx> > On or about Wednesday 27 May 2009 at approximately 15:08:51 Nicolas > Bigaouette > composed: > > Did that too, without success... > > > > 2009/5/27 Andrea Scarpino <andrea@xxxxxxxxxxxxx> > > > > > On 27/05/2009, Nicolas Bigaouette <nbigaouette@xxxxxxxxx> wrote: > > > > So the problem is not that it is failing to load i810 or vesa, the > > > > server just tries to load them but they are not used. > > > > > > Yes, I am stupid -.-' you said KDM works, so X works. > > > > > > try to move ~/.kde4 dir to somewhere and start kde > > > > > > -- > > > Andrea `BaSh` Scarpino > > > Arch Linux Developer > > Threads like this do not build my confidence for making the jump > from kde3 to > kde4. Imagine, one crash or weird boot up and you get 5 hours of dorking > with "why won't my kde4 start." > > Nicolas, I've save a few threads on this from the other list, I'll > pick > through them and if I get anything other than the normal move .kde4 and > force > a rebuild of the config, I'll post it here. Good luck, and remember -- File > the bug report.... > > -- > David C. Rankin, J.D.,P.E. > Rankin Law Firm, PLLC > 510 Ochiltree Street > Nacogdoches, Texas 75961 > Telephone: (936) 715-9333 > Facsimile: (936) 715-9339 > www.rankinlawfirm.com >
