upport/dev archives are coming back so I could have hunted for this,
and (2) how can I stop udev from moving the interface around? TIA.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personall
:
You've gotten the best advice, about login vs subshells. Don't forget
one of the most basic things--you've got to export them! Once or twice
when I've been in a rush and thinking of other things I've forgotten,
and it's taken me even longer to diagnose. ;-)
--
ading the dri/glx modules in xorg.conf, put away but keep all the
alternative drivers, and try to get xorg-7.2 running right then
proceed with other things to be installed. After that's working I may
well return and try to sort this out again, possibly with the frame-
buffers enabled as an
rt drinking
decaf.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.fm - One of many happy users:
h
dule
had been removed. I was thinking of doing a binary search between 6.6.3
and 6.12.4 looking for where the mach64 module was first removed and
checking into that. Gives me something to try today, pending answers
for above.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers
.
It's another problem I'll chase down later--one at a time! But I wish
software wouldn't presume it knows what I need! evdev doesn't look
attractive.
> > But I guess I should go sign-up for X's mailing list to persue this.
>
> LOL - they can be helpful, bu
ame buffers for Mach64, but
that would be a module named afyfb. Xorg -configure calls for the ati
driver module.
But I guess I should go sign-up for X's mailing list to persue this.
Any
idea when we can get back in the mailing list archives, where I might
look this up?
Thanks for BLFS.
--
else last week.
That's helpful, thanks.
> So, if you want dri I guess you need to rebuild xorg.
I don't really think I do. I'd rather speed than eye-candy and
exploding windows. I think the without-xinerama is only in the server
build. I'm thinking just rebuilding th
roblem was the overlooked parens
already reported. Later, in apps, xsm wouldn't build without rsh, which
I have never built, so I took it out of the list. The X server doesn't
want to load DRI now, maybe a build error, but that's less serious than
my 7.5 errors. Thanks for chec
t;dri" (loader failed, 7)
...
(EE) AIGLX: DRI module not loaded
Thanks, again.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
Sheesh! Mea Culpa! Sorry...
make | tee ... &&
Not quite as obvious when something, (), is missing!
With them in place the build went to completion and
I'm marching on.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everyth
math-emu/float.h
/usr/src/linux-2.6.34.13/include/linux/limits.h
/usr/src/linux-2.6.34.13/include/linux/stddef.h
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse
7;t check the support archives yet.
Suggestions, please? TIA
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
h
then maybe I'll
advance with my next version of LFS/BLFS.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://ww
> Spaces in C are almost always ignored by the compiler except inside
> of quotes.
OK, so it's not causing the errors. Thanks, Bruce. I'll see if
anything else
comes up, but it's beginning to look like maybe I should try another
version
of X.
--
Paul Rogers
paulgro
There is a space
between the asterisk and the "S" on one statement. Is that optional, or
must they be contiguous, as they are in all the other statements? How
does the space change the meaning, if at all?
TIA
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
n" "asterisk" "space" "Saved...". Is that right?
xorg-server-1.8.2/Xext/panoramiXprocs.c:return
(*SavedProcVector[X_PolyFillRectangle])(client);
xorg-server-1.8.2/Xext/panoramiXprocs.c:result = (*
SavedProcVector[X_PolyFillRectangle])(client)
, but I had to try it.
I'm not sure what direction to proceed. I'm beginning to wonder if
fixing the polygon-fill error might bring some joy. I think I'll back
off for a day or two and see what inspiration comes. Still open to
suggestions, of course.
TIA
--
Paul Rogers
paulgrog
> IBM 7090/7094. Fall 1965. Punched cards. Fortran II. Been there,
> done that.
;-)
IBM 1620 for me.
They may call us old dinosaurs, but T. rex was a dinosaur! ;-)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you
is left.
It would be much more straight forward to try a different version of X--
the bug isn't in 6.8.2. I chose 7.5-3 because it was contemporaneous
with LFS-6.6, so I figured the two would work together.
>
> Yes. The mail archives are disabled for now due to overuse by bots.
> We
One ends up in the LFS main page.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.fm - Send y
issues".
> Did it shut itself down (i.e. it doesn't work, so yes, you do have a
> real problem), or did you kill it ?
No, I shut it down from the fluxbox menu. All I needed to see was if
the MTRR errors were still present at startup and shutdown. As you
noted this
setting MTRR (base =
0xe000, size = 0x0300, type = 1) Invalid argument (22)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
ybody know of troubles with those latest "not
stable" kernels? With the LFS-6.6 base, is it possible/advisable to
take a baby-step over the line and install an early 3.0 kernel? (Would
that make further LFS updates easier?)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~p
As mentioned elsewhere, I'm using a Conroe dual-core for compiling X,
-j2. I did see that Mesa won't compile correctly with multiprocessing,
but didn't catch such a warning for X. Is it possible using
multiprocessing for building X could be causing my MTRR errors?
--
Paul
mon packages you install
> because something else might need them.
Maybe the reason for that is I have a touch of Asperger's Syndrome. It
makes me want things very organized. I have a plan for what I want from
my LFS system. I plan, then execute, first things first.
--
Paul Rogers
paulg
unctional desktop. In the LFS book the approach is
forward-looking, i.e. "We need libc before we can proceed", while as
everybody is saying, in the BLFS book it's all backward-looking and only
finds dependencies that lead to one specific package. I think I spend
rather more time than mo
d
> "Gnome" sections of the BLFS book, plus the pages for "Firefox", etc,
> plus anything listed as a dependency for one of the above.
I did in a previous post. q.v.
> Your post is somewhat short on examples, so it's a little hard to see
> what you
e stripped away all the
foliage from the systems we use, we'd find underneath a fairly common,
consistent set of packages--from which our individual interests caused
divergences, mostly by addition. I think what the newbie wants is a
page in BLFS that lists the packages, and order, that get
back in 2003/4, when what one got was
simpler and more exposed. (I found a loose LFS-4.1 CD at a Goodwill
charity "Outlet" store, i.e. the last stop before the landfill, and my
own LFS has pretty much been my "daily-driver" since. But it was good
to have that early experienc
eryday for normal everyday stuff.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastmail.fm - IMAP acce
ntifying the bones of a manageable end-user "daily-driver", at
least getting them that far.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any addition
e inappropriate arguments. I'm thinking of
trying a different intel driver first, then maybe a different version
of the server.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not
s I did browse the blfs-dev mailing list of a
few years ago, settling on 7.5-3 as a likely candidate. What I need
is support for newer versions of Firefox-[357], and drivers that
work, intel, nv, ati, etc.
Should I be trying for a different version of X with this LFS-6.6?
--
Paul Rogers
paulgrog
mber in output stream: 16
waiting for X server to shut down ...error setting MTRR (base =
0xe000, size = 0x0300, type = 1) Invalid argument (22)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I
that seems to suggest to me that I can just recompile
libpciaccess alone, without recompiling everything else built after
that. Is that an appropriate couse of action?
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communica
vices, for example. (It's being built on
a 1.4Ghz Tualatin Pentium III, with the big compiling jobs exported to a
2.4GHz Conroe Core II--it is nice to see things fly by as fast as the
screen can scroll!)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second La
's being built on
a 1.4Ghz Tualatin Pentium III, with the big compiling jobs exported to a
2.4GHz Conroe Core II--it is nice to see things fly by as fast as the
screen can scroll!)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "
getting these same errors earlier when I had a bit of a
mixup in
versions.
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
tall
Python!
Oh well, that was scheduled for later anyhow
Thanks anyway. 8-)
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
Dang! Sorry for the 6.8.2 typo in the subject, previous.
- Original message -
From: Paul Rogers
To: blfs-support@linuxfromscratch.org
Subject: Mesa-6.8.2 compile failure addendum
Date: Sat, 15 Dec 2012 10:45:56 -0800
Kernel-2.6.39.4,
DRI enabled
agpgart for Intel BX...i8xx etc enabled
Kernel-2.6.39.4,
DRI enabled
agpgart for Intel BX...i8xx etc enabled
Went looking for i915 support in kernel, but not finding it . :-(
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not persona
_subdirs] Error 2
make[2]: Leaving directory `/usr/local/src/Mesa-7.8.2/src/mesa'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/usr/local/src/Mesa-7.8.2/src'
make: *** [default] Error 1
--
Paul Rogers
paulgrog...@fastmail.fm
http://www.xprt.net/~pgrogers/
Rogers' Seco
43 matches
Mail list logo
