You are not logged in.

#1 2009-05-15 09:12:15

Feeelix
Member
Registered: 2009-05-14
Posts: 4

KDEbase but cant start :/ ( edited first post)

Ok, what am I missing here, I have Asus EeePc 701¸, did everything by the book, but chosen kdebase instead of kde because of small 4gig mem card in my Eee...
Added exec startkde to xinitrc, but after I type startx i get bunch of errors and no KDE...
also onstalled HAL and added to daemons, and used hwd -xa to autoconfigure xorg

Using config file: "/etc/X11/xorg.conf"
(EE)Failed to load module "type1" (module does not exist, 0 )
(EE)Failed to load module "freetype" (module does not exist, 0 )
(EE) intel(0): (EE)Failed to set tiling on front buffer: rejected by kernel
(EE) intel(0): (EE)Failed to set tiling on back buffer: rejected by kernel
(EE) intel(0): (EE)Failed to set tiling on depth buffer: rejected by kernel
Setting master
The XKEYBOARD keymap compiler (xkbcomp) reports:

> Error                     Cant find file "croat" for symbols include
>                              Exiting
>                              Abandoning symbols file "default"
Errors from xkbcomp are not fatal to the X server
(EE) config/hal: NewInputDeviceRequest Failed (8)
(EE) config/hal: NewInputDeviceRequest Failed (8)
(EE) config/hal: NewInputDeviceRequest Failed (8)
(EE) config/hal: NewInputDeviceRequest Failed (8)
(EE) config/hal: NewInputDeviceRequest Failed (8)
/etc/X11/xinit/xinitrc line 4: exec: startkde: not found

Waiting for X server to shut down .Droping master
error setting MTRR (base = 0xd0000000, size = 0x10000000, type = 1) Invalid argument (22)


EDIT: I checked LOG and problem seems to be:
1. some directories for the fonts are missing, but those are only WW

2. Errors are:

-failed to load module type1 and freetype
-failed to set tilling
and
-adding input device: macintosh, assus eepc extra butons, SynPS/2 synptics touchpad, AT translated Set2 keyboard and video bus...



Please anyone knows how to fix this..

Last edited by Feeelix (2009-05-15 12:28:11)

Offline

#2 2009-05-15 17:30:45

Feeelix
Member
Registered: 2009-05-14
Posts: 4

Re: KDEbase but cant start :/ ( edited first post)

ok pacman -S xf86-video-intel-legacy solved first problem, no more:
(EE) intel(0): (EE)Failed to set tiling on front buffer: rejected by kernel
(EE) intel(0): (EE)Failed to set tiling on back buffer: rejected by kernel
(EE) intel(0): (EE)Failed to set tiling on depth buffer: rejected by kernel

But second problem remains, input device request failed for all devices (macintosh, assus eepc extra butons, SynPS/2 synptics touchpad, AT translated Set2 keyboard and video bus...)

anyone ??????

Offline

#3 2009-05-30 00:20:40

liquidsunshine
Member
Registered: 2008-07-30
Posts: 7

Re: KDEbase but cant start :/ ( edited first post)

First, on behalf of the community, I apologize for the delay in anyone responding.  Maybe I can help.  smile

Note the line "/etc/X11/xinit/xinitrc line 4: exec: startkde: not found" in the error messages you pasted.  This means that the startkde application doesn't exist on your hard drive.  I'm pretty sure there's more to the KDE dependencies than just "kdebase."  You can likely get away with less than the full-blown kde meta-package, but something is missing. 

In particular, you'll need the "kde-workspace" package in extra for the "startkde" program.  That might be all you need to get it working, but it might not.  Try installing it and see if it works.  If not, post back here.

----
As for "-failed to load module type1 and freetype" you should be able to fix that by editing /etc/X11/xorg.conf (that's the default X configuration file, at least) and commenting out the lines in section "Module" that correspond to freetype and type1.  Similarly, the font directories problem can be fixed by commenting out the appropriate "FontPath" lines in the "Files" section. 

The hardware request failures I'm not sure about, since I don't have an EeePc.

The "error setting MTRR (base = 0xd0000000, size = 0x10000000, type = 1) Invalid argument (22)" I'm trying to get rid of, myself, although it won't prevent gnome from starting; it only causes issues when using "startx".

Offline

Board footer

Powered by FluxBB