1 |
2008/7/6 Tonko Mulder <tonko.mulder@×××××.com>: |
2 |
|
3 |
> On 7/6/08, Beso <givemesugarr@×××××.com> wrote: |
4 |
> > |
5 |
> > as i've told you the x11 ebuilds are really good and the overall quality |
6 |
> of |
7 |
> > the git xorg is quite impressive. the cairo and glitz ebuilds always have |
8 |
> > some problems with autoconf, but once in a while they compile. i think |
9 |
> that |
10 |
> > this is due to some autoconf-wrapper issues, but i'm not sure. use the |
11 |
> > portage ones instead of the 9999 versions for them. |
12 |
> Already running the portage one :) |
13 |
> |
14 |
> > as for eselect-opengl i have 1.0.6-r2 installed well and without issues. |
15 |
> > i've posted my bz2 for opengl. try putting it in your distfiles directory |
16 |
> > and retry installing. |
17 |
> Thanks for the bz2, after putting it in my distfiles all I had to do |
18 |
> was adjust the ebuild to accept my keyword (~amd64) and it didn't have |
19 |
> any trouble installing. |
20 |
> |
21 |
|
22 |
i thought that you already were on ~amd64 since you asked for 1.0.6 ebuild |
23 |
that should be coded as unstable for amd64 branch... well, it doesn't really |
24 |
matter much... |
25 |
|
26 |
|
27 |
> |
28 |
> I'll see when the git cairo wants to install. |
29 |
> Now I have another weird problem, I use my wireless network card (an |
30 |
> Atheros AR5006EG or and AR5007EG, lspci isn't that accurate I heard) |
31 |
> with ndiswrapper and sometimes it works and connects right away and |
32 |
> sometimes it can't detect any networks. And at times it detects the |
33 |
> networks but it can't connect for some reason. |
34 |
> |
35 |
|
36 |
this is one of the things i've failed with.... there's a post in the forum |
37 |
if you search ar5006eg that points to an ebuild they say it works (a |
38 |
modified madwifi-ng driver) but i wasn't able to have it working (i think |
39 |
that it's limited to x86 architecture). as for ndiswrapper i know that the |
40 |
latest kernels are removing some ndiswrapper needed calls. also the |
41 |
ndiswrapper is known to be quite buggy: it either works well or doesn't |
42 |
really work.... i've had some terific experiences with it some time ago with |
43 |
the bcm wifi boards and stopped using it at all. i preffer not having a |
44 |
functionality than using that stuff installed. for what it worths, do you |
45 |
have the wpa_supplicant and the linux wireless utils (iwconfig and other |
46 |
utils) installed?! |
47 |
|
48 |
|
49 |
> |
50 |
> Does anyone has an hint on that? Or anything else that helps, since |
51 |
> this is quite annoying |
52 |
> > |
53 |
> > > |
54 |
> > > |
55 |
> > > |
56 |
> > > |
57 |
> > > On 6/30/08, Tonko Mulder <tonko.mulder@×××××.com> wrote: |
58 |
> > > > After trying a few things a lot of thing refused to compile, so I got |
59 |
> > > > my external hard drive and started a new installation with the 2008 |
60 |
> > > > profile and the x11 overlay. And so far it is going well, if |
61 |
> > > > everything goes well I will move that installation to my current |
62 |
> one. |
63 |
> > > > |
64 |
> > > > Just to keep you posted :) |
65 |
> > > > |
66 |
> > > > |
67 |
> > > > On 6/21/08, Beso <givemesugarr@×××××.com> wrote: |
68 |
> > > > > 2008/6/21 Tonko Mulder <tonko.mulder@×××××.com>: |
69 |
> > > > > |
70 |
> > > > >> I'm in the middle of a emerge -e world, since the new portage |
71 |
> > requested |
72 |
> > > > >> this. |
73 |
> > > > >> A lot of things fail to compile, among these are |
74 |
> > x11-libs/libX11-9999 |
75 |
> > > > >> / libXext-9999 and libXi-9999 |
76 |
> > > > >> I don't know if they will compile later on or should I remove |
77 |
> every |
78 |
> > > > >> driver for X? |
79 |
> > > > >> I believe that was in Beso's post. |
80 |
> > > > > |
81 |
> > > > > |
82 |
> > > > > probably they failed because of the new libxcb api which has |
83 |
> removed |
84 |
> > 2 |
85 |
> > > > > useless libtool archive files that shouldn't be used from the |
86 |
> start. |
87 |
> > the |
88 |
> > > > > other thing that might cause problems is portage deps resolver |
89 |
> which |
90 |
> > > > > sometime is bad and would emerge some packages after the ones |
91 |
> > requiring |
92 |
> > > > > them. this usually happens often in an emerge -e world. |
93 |
> > > > > if you try to rebuild them after the world rebuild and you cannot |
94 |
> > build them |
95 |
> > > > > again, remove the installed versions (with emerge --unmerge libX11 |
96 |
> > linXext |
97 |
> > > > > libXi ) and reemerge them with emerge --oneshot libX11 libXext |
98 |
> libXi. |
99 |
> > at |
100 |
> > > > > that point they should emerge. if they don't emerge emerge the |
101 |
> > portage ones |
102 |
> > > > > with xorg-server from portage and post the emerge logs so we can |
103 |
> help |
104 |
> > you |
105 |
> > > > > out. you'll get also xorg-server error surely since libX11 isn't |
106 |
> the |
107 |
> > one |
108 |
> > > > > required as dep and, as i've told you, probably also libXtst and |
109 |
> > xdpyinfo. |
110 |
> > > > > today i have a little spare time and i'll search out for the |
111 |
> > synaptics |
112 |
> > > > > ebuild (with patches) to post in the case you own a synaptics or |
113 |
> alps |
114 |
> > > > > touchpad. |
115 |
> > > > > |
116 |
> > > > > |
117 |
> > > > > -- |
118 |
> > > > > dott. ing. beso |
119 |
> > > > > |
120 |
> > > > |
121 |
> > > -- |
122 |
> > > gentoo-amd64@l.g.o mailing list |
123 |
> > > |
124 |
> > > |
125 |
> > |
126 |
> > |
127 |
> > |
128 |
> > -- |
129 |
> > dott. ing. beso |
130 |
> > |
131 |
> -- |
132 |
> gentoo-amd64@l.g.o mailing list |
133 |
> |
134 |
> |
135 |
|
136 |
|
137 |
-- |
138 |
dott. ing. beso |