| 1 |
Hi, thanks for recalling of emerge usage |
| 2 |
|
| 3 |
I have set opengl and dri, Xorg seems to see properly agp, but kdm |
| 4 |
failed to aquire on it |
| 5 |
|
| 6 |
difference between 3.5 and 4.0, it's that 3.5 even if they fail, they |
| 7 |
seems to use it properly by not 4.0 |
| 8 |
|
| 9 |
I will wait for another version, more usable |
| 10 |
|
| 11 |
4.0.2 has some disturbing bug, that should be correct in svn now |
| 12 |
wait and cross leg for 4.0.3 or 4.0.4 version |
| 13 |
How this version don't be disturb for downloading by "Page Not Found" |
| 14 |
exception (Error 404 :) ) |
| 15 |
Ok I get out |
| 16 |
|
| 17 |
See ya |
| 18 |
|
| 19 |
Dale a écrit : |
| 20 |
> cypherstrong wrote: |
| 21 |
>> Ok I have found why kdm-4.0 don't work |
| 22 |
>> |
| 23 |
>> They doesn't support seamless login over pam even with nullpassword and |
| 24 |
>> nopassword activated !!! |
| 25 |
>> I use pamusb with a key, and login won't done without password sets ... |
| 26 |
>> I will ask to kde team why ... |
| 27 |
>> |
| 28 |
>> I have look in kdm.log and I have found another problem |
| 29 |
>> |
| 30 |
>> (II) Module already built-in |
| 31 |
>> (II) Module already built-in |
| 32 |
>> (II) Module already built-in |
| 33 |
>> (EE) VIA(0): [drm] drmAgpAcquire failed 19 |
| 34 |
>> expected keysym, got XF86KbdLightOnOff: line 70 of pc |
| 35 |
>> expected keysym, got XF86KbdBrightnessDown: line 71 of pc |
| 36 |
>> expected keysym, got XF86KbdBrightnessUp: line 72 of pc |
| 37 |
>> The XKEYBOARD keymap compiler (xkbcomp) reports: |
| 38 |
>> |
| 39 |
>>> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 |
| 40 |
>>> symbols |
| 41 |
>>> Ignoring extra symbols |
| 42 |
>>> |
| 43 |
>> Errors from xkbcomp are not fatal to the X server |
| 44 |
>> |
| 45 |
>> VIA(0) drmAgepAcquire failed |
| 46 |
>> |
| 47 |
>> The result is the same between kdm-3.5 and kdm-4.0 except on display |
| 48 |
>> speed |
| 49 |
>> |
| 50 |
>> If I use kdm-4.0, the screen display is really slow, I really think agp |
| 51 |
>> is totally disabled, and everything take long time to be show even if I |
| 52 |
>> use kde-4.0 or kde-3.5 session |
| 53 |
>> |
| 54 |
>> Now I have try the same on kdm-3.5, speed is good on kde-4.0 or kde-3.5, |
| 55 |
>> I think agp is good on it |
| 56 |
>> |
| 57 |
>> I have look in Xorg.0.log, dri and agp are well activated |
| 58 |
>> |
| 59 |
>> What happen ? Did I miss a use option ? |
| 60 |
>> |
| 61 |
>> opengl and dri are totally activated on my use, |
| 62 |
>> |
| 63 |
>> perhaps I have to try another drivers for via unichrome ? |
| 64 |
>> |
| 65 |
>> In kernel, I have disabled AGP for VIA (because i think it's not a via |
| 66 |
>> unichrome drivers), and activate DRI for VIA (it's a via unichrome dri |
| 67 |
>> drivers) |
| 68 |
>> |
| 69 |
>> with or without AGP for VIA in kernel, I have the same message on all |
| 70 |
>> log, so ... |
| 71 |
>> |
| 72 |
>> Did you have an idea ? |
| 73 |
>> |
| 74 |
>> |
| 75 |
>> |
| 76 |
> |
| 77 |
> I'm not real sure but I do have the USE flag dri in my make.conf. |
| 78 |
> xorg-server is the package that shows it uses it but there may be |
| 79 |
> other packages. |
| 80 |
> |
| 81 |
> To find out if you have a flag enabled or not, you can do a emerge -pv |
| 82 |
> <package-name> and then look in the list to see if it is enabled or |
| 83 |
> not. Something like this: |
| 84 |
> |
| 85 |
> root@smoker / # emerge -pv xorg-server |
| 86 |
> |
| 87 |
> These are the packages that would be merged, in order: |
| 88 |
> |
| 89 |
> Calculating dependencies... done! |
| 90 |
> [ebuild R ] x11-base/xorg-server-1.3.0.0-r5 USE="dri ipv6 nptl |
| 91 |
> sdl xorg xprint -3dfx -debug -dmx -kdrive -minimal" |
| 92 |
> INPUT_DEVICES="keyboard mouse -acecad -aiptek -calcomp -citron |
| 93 |
> -digitaledge -dmc -dynapro -elo2300 -elographics -evdev -fpit |
| 94 |
> -hyperpen -jamstudio -joystick -magellan -microtouch -mutouch -palmax |
| 95 |
> -penmount -spaceorb -summa -synaptics -tek4957 -ur98 -vmmouse -void |
| 96 |
> -wacom" VIDEO_CARDS="nvidia -apm -ark -chips -cirrus -cyrix -dummy |
| 97 |
> -epson -fbdev -fglrx -glint -i128 -i740 -i810 (-impact) -imstt -mach64 |
| 98 |
> -mga -neomagic (-newport) -nsc -nv -r128 -radeon -rendition -s3 |
| 99 |
> -s3virge -savage -siliconmotion -sis -sisusb (-sunbw2) (-suncg14) |
| 100 |
> (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) -tdfx -tga -trident |
| 101 |
> -tseng -v4l -vesa -vga -via -vmware -voodoo" 0 kB |
| 102 |
> |
| 103 |
> Total: 1 package (1 reinstall), Size of downloads: 0 kB |
| 104 |
> root@smoker / |
| 105 |
> |
| 106 |
> If you have color on yours, red is enabled and blue is disabled. If |
| 107 |
> not color, the flags with the minus sign is front are disabled. You |
| 108 |
> can do a euse -i <flag name> to see a short, very short, description |
| 109 |
> of what the flag does or it's use. |
| 110 |
> |
| 111 |
> If you change make.conf, you can do a emerge -avN world to make sure |
| 112 |
> all the needed packages are recompiled with the changes. |
| 113 |
> |
| 114 |
> I have never seen that error before. Not real sure what to think |
| 115 |
> about it. Anybody else here have a clue?? |
| 116 |
> |
| 117 |
> Dale |
| 118 |
> |
| 119 |
> :-) :-) |
Archives