| View previous topic :: View next topic |
| Author |
Message |
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
 Posted: Mon Sep 24, 2007 12:20 pm Post subject: Nouveau overlay |
 |
|
Since one or two weeks ago the nouveau overlay ask for a password when syncing.
Obliviously I don't know this password, and I can't find it searching on the web, so I can't sync the overlay...
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
 |
DtZ
Tux's lil' helper
Joined: 09 Sep 2005
Posts: 124
|
| Posted: Wed Sep 26, 2007 6:02 pm Post subject: |
|
|
| Same problem here. So far I haven't found any solution, so I just moved all ebuilds to /usr/local/portage and removed the overlay. |
|
| Back to top |
|
|
ghutzl
Tux's lil' helper
Joined: 29 May 2005
Posts: 123
Location: Germany
|
| Posted: Wed Oct 10, 2007 7:18 am Post subject: |
|
|
| It is working again. I had the same problem yesterday and sent Hanno a mail about it. I got a reply today saying he was having problems with his apache installation recently, but it should be fixed now. I could add the nouveau overlay today. |
|
| Back to top |
|
|
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
| Posted: Mon Oct 15, 2007 8:45 pm Post subject: |
|
|
Today I rebuild x11-drm and I see this:
| Code: | --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-x11-base_-_x11-drm-99999999-15116.log"
open_wr: /usr/src/linux-2.6.23-git4/null.gcda
open_wr: /usr/src/linux-2.6.23-git4/null.gcda
open_wr: /usr/src/linux-2.6.23-git4/null.gcda
open_wr: /usr/src/linux-2.6.23-git4/null.gcda
open_wr: /usr/src/linux-2.6.23-git4/null.gcda
open_wr: /usr/src/linux-2.6.23-git4/null.gcda
-------------------------------------------------------------------------------- |
I don't know if it's related to today's kernel change...
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
|
hirakendu
Guru
Joined: 24 Jan 2007
Posts: 386
Location: san diego
|
| Posted: Mon Oct 15, 2007 8:55 pm Post subject: |
|
|
yeah, always use `FEATURES=-sandbox emerge <whatever>' if using a shiney new kernel and <whatever> is a package needing kernel sources to compile kernel modules.
_________________
Helium Sources || Gentoo Minimal Livecd |
|
| Back to top |
|
|
tarpman
Veteran
Joined: 04 Nov 2004
Posts: 1083
Location: Victoria, BC, Canada
|
| Posted: Mon Oct 15, 2007 10:25 pm Post subject: |
|
|
| hirakendu wrote: | | yeah, always use `FEATURES=-sandbox emerge <whatever>' if using a shiney new kernel and <whatever> is a package needing kernel sources to compile kernel modules. |
Why?
I've never had to do that, until 2.6.23 came along...
_________________
Saving the world, one kilobyte at a time. |
|
| Back to top |
|
|
hirakendu
Guru
Joined: 24 Jan 2007
Posts: 386
Location: san diego
|
| Posted: Mon Oct 15, 2007 10:55 pm Post subject: |
|
|
does it work? anyway, i always get those sandbox access control violations with bleeding edge kernels (since 2.6.19, which is when i started playing with rc kernels) so just a temporary workaround.
_________________
Helium Sources || Gentoo Minimal Livecd |
|
| Back to top |
|
|
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
| Posted: Tue Oct 16, 2007 7:32 am Post subject: |
|
|
| hirakendu wrote: | | yeah, always use `FEATURES=-sandbox emerge <whatever>' if using a shiney new kernel and <whatever> is a package needing kernel sources to compile kernel modules. |
I never had to do this when I changed kernel...
Now the problem is another, when I select 2.6.23-git4 from grub, I have a black screen...
I used the .config file from my gentoo-sources-2.6.22-r8, so I think there was a change on some keyworkds and something really important get lost...
Looking at the access violations, maybe it's a real kernel problem...
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
|
hirakendu
Guru
Joined: 24 Jan 2007
Posts: 386
Location: san diego
|
| Posted: Tue Oct 16, 2007 7:59 am Post subject: |
|
|
those access control violations - they usually disappeared as i observed the kernel became mainstream.
about the black screen - are you talking about X or the initial text mode in which the kernel and boot messages appear ? if its the latter, may be you missed some vesa/framebuffer things in drivers->graphics section. although in that case, you get the plain text mode. in worst case, may be your kernel is not booting at all  . ps : why are you using ~2.6.24 ?
_________________
Helium Sources || Gentoo Minimal Livecd |
|
| Back to top |
|
|
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
| Posted: Tue Oct 16, 2007 10:58 am Post subject: |
|
|
| hirakendu wrote: | | about the black screen - are you talking about X or the initial text mode in which the kernel and boot messages appear ? if its the latter, may be you missed some vesa/framebuffer things in drivers->graphics section. although in that case, you get the plain text mode. in worst case, may be your kernel is not booting at all . ps : why are you using ~2.6.24 ? |
I think the kernel didn't boot at all, because waiting some time X doesn't appears...
I'm using ~2.6.24 because I need b43 drivers for my bcm4318, with old bcm43xx I have the power control issue so I can get it work only for few seconds...
And b43 aren't in <=2.6.23
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
|
hirakendu
Guru
Joined: 24 Jan 2007
Posts: 386
Location: san diego
|
| Posted: Tue Oct 16, 2007 7:19 pm Post subject: |
|
|
so there are power control issues even with ndiswrapper and win32 drivers? does this mac80211 (bcm43xx_mac80211) driver also not end the power control issues ?
anyway, waiting for atleast an rc would be better. there is a gaping open merge window atm as you know  . (ps : are you using x86 or x86_64 ? and what processor ?)
btw, any idea if this b43 driver will be backported? (cos i am still in 2.6.22 dreamland :p.)
_________________
Helium Sources || Gentoo Minimal Livecd |
|
| Back to top |
|
|
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
| Posted: Tue Oct 16, 2007 8:12 pm Post subject: |
|
|
| hirakendu wrote: | | so there are power control issues even with ndiswrapper and win32 drivers? does this mac80211 (bcm43xx_mac80211) driver also not end the power control issues ? |
It's what I read here: https://forums.gentoo.org/viewtopic-p-4259069.html#4259069
With ndiswrapper it works fine, but I don't want to use ndiswrapper.
| hirakendu wrote: | | anyway, waiting for atleast an rc would be better. there is a gaping open merge window atm as you know . (ps : are you using x86 or x86_64 ? and what processor ?) |
x86_64 on an AMD athlon64 3000+ socket 939.
| hirakendu wrote: | | btw, any idea if this b43 driver will be backported? (cos i am still in 2.6.22 dreamland :p.) |
I already asked if a port is possible: https://forums.gentoo.org/viewtopic-p-4352984.html#4352984
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
|
b33fc0d3
Retired Dev
Joined: 22 Jun 2006
Posts: 128
|
| Posted: Sat Oct 20, 2007 2:55 am Post subject: |
|
|
| hirakendu wrote: | | btw, any idea if this b43 driver will be backported? (cos i am still in 2.6.22 dreamland :p.) |
Have a look at https://forums.gentoo.org/viewtopic-t-600890-highlight-.html. But the network stack from .22->.23/.24 is too big for there ever to be a backport for b43. |
|
| Back to top |
|
|
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
| Posted: Fri Oct 26, 2007 11:56 pm Post subject: |
|
|
Returning back to original topic, since some days I have a problem with 2 ebuilds storeds on the nouveau overlay:
x11-libs/libdrm-9999
x11-base/x11-drm-99999999
This is the output for libdrm:
| Code: | >>> Emerging (1 of 1) x11-libs/libdrm-9999 to /
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
>>> Unpacking source...
* git clone start -->
* repository: git://anongit.freedesktop.org/git/xorg/lib/libdrm
Initialized empty Git repository in /usr/portage/distfiles/git-src/libdrm/
fatal: The remote end hung up unexpectedly
fetch-pack from 'git://anongit.freedesktop.org/git/xorg/lib/libdrm' failed.
*
* ERROR: x11-libs/libdrm-9999 failed.
* Call stack:
* ebuild.sh, line 1687: Called dyn_unpack
* ebuild.sh, line 803: Called qa_call 'src_unpack'
* ebuild.sh, line 44: Called src_unpack
* ebuild.sh, line 1369: Called x-modular_src_unpack
* x-modular.eclass, line 287: Called x-modular_unpack_source
* libdrm-9999.ebuild, line 23: Called git_src_unpack
* git.eclass, line 280: Called git_fetch
* git.eclass, line 195: Called die
* The specific snippet of code:
* ${EGIT_FETCH_CMD} ${EGIT_OPTIONS} "${EGIT_REPO_URI}" ${EGIT_PROJECT} \
* || die "${EGIT}: can't fetch from ${EGIT_REPO_URI}."
* The die message:
* git.eclass: can't fetch from git://anongit.freedesktop.org/git/xorg/lib/libdrm.
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/x11-libs/libdrm-9999/temp/build.log'.
* |
And x11-drm exits with this message:
| Code: | | !!! A file listed in the Manifest could not be found: /usr/portage/local/layman/nouveau/x11-base/x11-drm/files/makefile.patch |
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
|
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
| Posted: Wed Oct 31, 2007 9:04 am Post subject: |
|
|
I sent a mail to Pekka Paalanen and he solved the problems.
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
|
JohnY
Guru
Joined: 26 Jul 2002
Posts: 305
|
| Posted: Wed Oct 31, 2007 7:55 pm Post subject: |
|
|
The compile problems are still as dracula1985 mentioned ....
JohnY |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Thu Nov 01, 2007 12:09 am Post subject: |
|
|
I still have the "git" problem with libdrm-9999, strangely enough
x11-drm was OK (this is my first attempt at installing nouveau). |
|
| Back to top |
|
|
JohnY
Guru
Joined: 26 Jul 2002
Posts: 305
|
| Posted: Sun Nov 04, 2007 6:33 pm Post subject: |
|
|
mesa-9999 just came down and is compiling now: Sunday 1:30 EST 4 November.
JohnY
edit: 1:37pm compile fails though.... |
|
| Back to top |
|
|
PeterH
n00b
Joined: 09 Nov 2005
Posts: 31
|
| Posted: Tue Nov 06, 2007 9:58 am Post subject: |
|
|
| fb wrote: | I still have the "git" problem with libdrm-9999, strangely enough
x11-drm was OK (this is my first attempt at installing nouveau). |
I have this problem as well. Anybody know of a solution? |
|
| Back to top |
|
|
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
| Posted: Tue Nov 06, 2007 4:41 pm Post subject: |
|
|
I sent another mail to Pekka Paalanen and now the problem has been solved.
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
|
JohnY
Guru
Joined: 26 Jul 2002
Posts: 305
|
| Posted: Wed Nov 07, 2007 2:37 am Post subject: |
|
|
Everything compiles now. Getting a fatal error inserting nouveau.ko (a lot of unknown symbols) after removing the old drm and nvidia binary and switching to 'eselect opengl set xorg-x11'.
Still investigating.... Nouveau overlay has bumped to version 38.
JohnY |
|
| Back to top |
|
|
dracula1985
Apprentice
Joined: 13 May 2005
Posts: 299
Location: Vicenza (Italy)
|
| Posted: Wed Nov 07, 2007 8:26 am Post subject: |
|
|
| JohnY wrote: | Everything compiles now. Getting a fatal error inserting nouveau.ko (a lot of unknown symbols) after removing the old drm and nvidia binary and switching to 'eselect opengl set xorg-x11'.
Still investigating.... Nouveau overlay has bumped to version 38.
JohnY |
No problems here, everything build and works fine.
_________________
Marco
"Man is least himself when he talks in his own person. Give him a mask, and he will tell you the truth." --Oscar Wilde. |
|
| Back to top |
|
|
JohnY
Guru
Joined: 26 Jul 2002
Posts: 305
|
| Posted: Thu Nov 08, 2007 7:28 pm Post subject: |
|
|
Got it straightened.... x11-drm's drm.ko was put in a different dir than the pre-nouveau drm.ko. Renamed the old one, copied the new one to the same dir and it all worked. Woot!
JohnY |
|
| Back to top |
|
|
fb
l33t
Joined: 08 Dec 2003
Posts: 636
Location: New Zealand
|
| Posted: Fri Nov 09, 2007 2:22 am Post subject: |
|
|
| JohnY wrote: | Got it straightened.... x11-drm's drm.ko was put in a different dir than the pre-nouveau drm.ko. Renamed the old one, copied the new one to the same dir and it all worked. Woot!
JohnY |
Can you give me some details? I have the same error but I cannot seem to find
where the old modules were and where I should copy my modules.
When I do "locate drm.ko" I get only the file in /lib/module/kernel-version/x11-drm/drm.ko. |
|
| Back to top |
|
|
JohnY
Guru
Joined: 26 Jul 2002
Posts: 305
|
| Posted: Fri Nov 09, 2007 6:12 am Post subject: |
|
|
Sure.
First I used find:
| Code: | | find // -name dro.ko -print |
because it finds the file in real time, I think locate depends on a database updated by a cron job.
In my case there was one drm.lo here: '/lib/modules/2.6.23-gentoo/kernel/drivers/char/drm/' (the older one) and one drm.ko here: '/lib/modules/2.6.23-gentoo/x11-drm/' (the one built from the nouveau overlay ). I renamed the older one and copied the newer one to the older one's location. Then rmmod drm.ko and modprobe drm.ko and restart X.
Does that help?
JohnY |
|
| Back to top |
|
|
|
Unsupported Software
