Re: [gentoo-amd64] Re: Laptop freeze

[Tonko Mulder]

On 7/7/08, Beso <givemesugarr@×××××.com> wrote:
> 2008/7/6 Tonko Mulder <tonko.mulder@×××××.com>:
>
> >
> > On 7/6/08, Beso <givemesugarr@×××××.com> wrote:
> > >
> > > as i've told you the x11 ebuilds are really good and the overall quality
> of
> > > the git xorg is quite impressive. the cairo and glitz ebuilds always
> have
> > > some problems with autoconf, but once in a while they compile. i think
> that
> > > this is due to some autoconf-wrapper issues, but i'm not sure.GL development package gentoo use the
> > > portage ones instead of the 9999 versions for them.
> > Already running the portage one :)
> >
> >
> > >  as for eselect-opengl i have 1.0.6-r2 installed well and without
> issues.
> > > i've posted my bz2 for opengl. try putting it in your distfiles
> directory
> > > and retry installing.
> > Thanks for the bz2, after putting it in my distfiles all I had to do
> > was adjust the ebuild to accept my keyword (~amd64) and it didn't have
> > any trouble installing.
> >
>
> i thought that you already were on ~amd64 since you asked for 1.0.6 ebuild
> that should be coded as unstable for amd64 branch... well, it doesn't really
> matter much...
I am on ~amd64 as far as I know, although amd64 appears in my emerge
--info for some reason.
>
> >
> > I'll see when the git cairo wants to install.
> > Now I have another weird problem, I use my wireless network card (an
> > Atheros AR5006EG or and AR5007EG, lspci isn't that accurate I heard)
> > with ndiswrapper and sometimes it works and connects right away and
> > sometimes it can't detect any networks. And at times it detects the
> > networks but it can't connect for some reason.
> >
>
> this is one of the things i've failed with.... there's a post in the forum
> if you search ar5006eg that points to an ebuild they say it works (a
> modified madwifi-ng driver) but i wasn't able to have it working (i think
> that it's limited to x86 architecture). as for ndiswrapper i know that the
> latest kernels are removing some ndiswrapper needed calls. also the
> ndiswrapper is known to be quite buggy: it either works well or doesn't
> really work.... i've had some terific experiences with it some time ago with
> the bcm wifi boards and stopped using it at all. i preffer not having a
> functionality than using that stuff installed. for what it worths, do you
> have the wpa_supplicant and the linux wireless utils (iwconfig and other
> utils) installed?!
I do have wpa_supplicant and the wireless utils installed.
>
>
> >
> > Does anyone has an hint on that? Or anything else that helps, since
> > this is quite annoying
> >
> >
> >
> > >
> > > >
> > > >
> > > >
> > > >
> > > > On 6/30/08, Tonko Mulder <tonko.mulder@×××××.com> wrote:
> > > > > After trying a few things a lot of thing refused to compile, so I
> got
> > > > >  my external hard drive and started a new installation with the 2008
> > > > >  profile and the x11 overlay. And so far it is going well, if
> > > > >  everything goes well I will move that installation to my current
> one.
> > > > >
> > > > >  Just to keep you posted :)
> > > > >
> > > > >
> > > > >  On 6/21/08, Beso <givemesugarr@×××××.com> wrote:
> > > > >  > 2008/6/21 Tonko Mulder <tonko.mulder@×××××.com>:
> > > > >  >
> > > > >  >> I'm in the middle of a emerge -e world, since the new portage
> > > requested
> > > > >  >> this.
> > > > >  >> A lot of things fail to compile, among these are
> > > x11-libs/libX11-9999
> > > > >  >> / libXext-9999 and libXi-9999
> > > > >  >> I don't know if they will compile later on or should I remove
> every
> > > > >  >> driver for X?
> > > > >  >> I believe that was in Beso's post.
> > > > >  >
> > > > >  >
> > > > >  > probably they failed because of the new libxcb api which has
> removed
> > > 2
> > > > >  > useless libtool archive files that shouldn't be used from the
> start.
> > > the
> > > > >  > other thing that might cause problems is portage deps resolver
> which
> > > > >  > sometime is bad and would emerge some packages after the ones
> > > requiring
> > > > >  > them. this usually happens often in an emerge -e world.
> > > > >  > if you try to rebuild them after the world rebuild and you cannot
> > > build them
> > > > >  > again, remove the installed versions (with emerge --unmerge
> libX11
> > > linXext
> > > > >  > libXi ) and reemerge them with emerge --oneshot libX11 libXext
> libXi.
> > > at
> > > > >  > that point they should emerge.  if they don't emerge emerge the
> > > portage ones
> > > > >  > with xorg-server from portage and post the emerge logs so we can
> help
> > > you
> > > > >  > out. you'll get also xorg-server error surely since libX11 isn't
> the
> > > one
> > > > >  > required as dep and, as i've told you, probably also libXtst and
> > > xdpyinfo.
> > > > >  > today i have a little spare time and i'll search out for the
> > > synaptics
> > > > >  > ebuild (with patches) to post in the case you own a synaptics or
> alps
> > > > >  > touchpad.
> > > > >  >
> > > > >  >
> > > > >  > --
> > > > >  > dott. ing. beso
> > > > >  >
> > > > >
> > > > --
> > > > gentoo-amd64@l.g.o mailing list
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > dott. ing. beso
> > >
> > --
> >
> >
> >
> > gentoo-amd64@l.g.o mailing list
> >
> >
>
>
>
> --
> dott. ing. beso
-- 
gentoo-amd64@l.g.o mailing list