Re: [gentoo-user] dev-libs/efreet-9999 revision 57773 fails to emerge

2011-03-15 Thread Ian Lee
On 15/03/11 19:15, Mick wrote:
 I'm trying to emerge the latest dev-libs/efreet-, but it fails as shown 
 below:

 =
 Emerging (1 of 2) dev-libs/efreet- from enlightenment
  * Package:dev-libs/efreet-
  * Repository: enlightenment
  * Maintainer: enlightenm...@gentoo.org
  * USE:amd64 elibc_glibc kernel_linux multilib nls userland_GNU
  * FEATURES:   ccache sandbox userpriv usersandbox
 Unpacking source...
  * subversion switch start --
  *  old repository: http://svn.enlightenment.org/svn/e/trunk/efreet@56636
  *  new repository: http://svn.enlightenment.org/svn/e/trunk//efreet
 Usrc/tests/ef_data_dirs.c
  U   src/tests/compare
 Usrc/tests/ef_utils.c
 Usrc/tests/ef_cache.c
 Usrc/tests/main.c
  U   src/tests/data/sub
  U   src/tests/data
 Usrc/tests/efreet_icon_cache_dump.c
  U   src/tests
 Usrc/lib/efreet_menu.c
 Usrc/lib/efreet_utils.h
 Usrc/lib/efreet_desktop_command.c
 Usrc/lib/efreet_desktop.c
 Usrc/lib/efreet_base.c
 Usrc/lib/efreet_desktop.h
 Usrc/lib/efreet_private.h
 Usrc/lib/efreet_ini.c
 Usrc/lib/efreet.c
 Usrc/lib/efreet_trash.c
 Usrc/lib/efreet_mime.c
 Usrc/lib/efreet_icon.c
 Usrc/lib/efreet_icon.h
 Usrc/lib/efreet_uri.c
 Usrc/lib/efreet_utils.c
 Usrc/lib/efreet_xml.c
 Usrc/lib/efreet_cache_private.h
 Usrc/lib/efreet_cache.c
 Usrc/bin/efreet_icon_cache_create.c
 Usrc/bin/efreet_desktop_cache_create.c
 UChangeLog
 Udoc/head.html
 Uautogen.sh
  U   .
 Updated to revision 57773.
  *working copy: /usr/portage/distfiles/svn-src/enlightenment//efreet

 Source unpacked in /var/tmp/portage/dev-libs/efreet-/work
 Preparing source in /var/tmp/portage/dev-libs/efreet-/work/efreet ...
  * Running eautoreconf in '/var/tmp/portage/dev-libs/efreet-/work/efreet' 
 ...
  * Running aclocal -I m4 ...   [ ok ]
  * Running libtoolize --copy --force --install --automake ...  [ ok ]
  * Running aclocal -I m4 ...   [ ok ]
  * Running autoconf ...[ ok ]
  * Running autoheader ...  [ ok ]
  * Running automake --add-missing --copy ...   [ ok ]
  * Running elibtoolize in: efreet/
  *   Applying portage-2.2.patch ...
  *   Applying sed-1.5.6.patch ...
  *   Applying as-needed-2.2.6.patch ...
  * Removing useless C++ checks ... [ ok ]
 Source prepared.
 Configuring source in /var/tmp/portage/dev-libs/efreet-/work/efreet 
 ...
  * econf: updating efreet/config.sub with /usr/share/gnuconfig/config.sub
  * econf: updating efreet/config.guess with /usr/share/gnuconfig/config.guess
 ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-
 gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --
 sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-icon-
 cache --disable-static
 configure: WARNING: unrecognized options: --disable-icon-cache
 checking for a BSD-compatible install... /usr/bin/install -c
 checking whether build environment is sane... yes
 checking for a thread-safe mkdir -p... /bin/mkdir -p
 checking for gawk... gawk
 checking whether make sets $(MAKE)... yes
 checking build system type... x86_64-pc-linux-gnu
 checking host system type... x86_64-pc-linux-gnu
 checking how to print strings... printf
 checking for style of include used by make... GNU
 checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
 checking whether the C compiler works... yes
 checking for C compiler default output file name... a.out
 checking for suffix of executables... 
 checking whether we are cross compiling... no
 checking for suffix of object files... o
 checking whether we are using the GNU C compiler... yes
 checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
 checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
 checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3
 checking for a sed that does not truncate output... /bin/sed
 checking for grep that handles long lines and -e... /bin/grep
 checking for egrep... /bin/grep -E
 checking for fgrep... /bin/grep -F
 checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-
 gnu/bin/ld
 checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
 checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
 checking the name lister (/usr/bin/nm -B) interface... BSD nm
 checking whether ln -s works... yes
 checking the maximum length of command line arguments... 1572864
 checking whether the shell understands some XSI constructs... yes
 checking whether the shell understands +=... yes
 checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... 
 -r
 checking for x86_64-pc-linux-gnu-objdump... 

Re: [gentoo-user] XDG_CONFIG_DIRS and XDG_DATA_DIRS env variables with E17

2011-02-27 Thread Ian Lee
On 26/02/11 16:41, Mick wrote:
 Where are being these set?

 I currently have:

 $ echo $XDG_CONFIG_DIRS
 /etc/xdg

 $ echo $XDG_DATA_DIRS
 /usr/local/share:/usr/share

 I'm asking because although Enlightenment-17 picks up the kde menu from 
 there, 
 it does not seem to recognise the respective application icons.  If I set the 
 icons manually with absolute paths (e.g. 
 /usr/share/icons/oxygen/48x48/apps/knode.png, instead of the generic 
 knode.png) then I end up with duplicate menu entries for each application 
 when 
 I launch kde.
Go to settings-settings panel.

In the Look category find the Icon Theme option.

Set you icon theme to Oxygen.


For the duplicates:

Check ~/.local/share/applications/ 
You should find the .desktop files of the applications you changed to
absolute paths,
kde is probably picking up these and the system ones in
/usr/share/applications.
The ~/.local ones should not be needed





Re: [gentoo-user] why always display this when kernel start

2011-01-15 Thread Ian Lee

 ls -l /fixit/dev/{console,null}
 crw--- 1 root tty  5, 1 10. Jun 2010  /mnt/dev/console
 crw-rw-rw- 1 root root 1, 3 10. Jun 2010  /mnt/dev/null

Eh? You list /fixit/dev and get files in /mnt/dev, did you symlink
/fixit  to /mnt?

I would have expected

ls -l /fixit/dev/{console,null}
crw--- 1 root root 5, 1 Jun 26  2010 /fixit/dev/console
crw-rw-rw- 1 root root 1, 3 Jun 26  2010 /fixit/dev/null


The warning message is stored in /etc/issue I believe. The gentoo init
scripts, put it there if /dev/null or /dev/console don't exist.

Once you are sure that that /dev/null and /dev/console are on your root
partition, you should find the original in /etc/issue.devfix, mine looks
like:


This is \n.\O (\s \m \r) \t



swap this with /etc/issue and reboot.





Re: [gentoo-user] problems adding local overlay and ebuild

2010-09-01 Thread Ian Lee

On 01/09/10 11:21, Arnau Bria wrote:

Hi all,

I'd like to install mcollective and developer provides its ebuild.
so I've followed http://en.gentoo-wiki.com/wiki/Overlay for adding a
local overlay.

*I had a problem when adding
source /usr/local/portage/layman/make.conf to my make.conf. That file
does not exists and layman has no make.conf file. Anyway, removing that line
and following the other steps makes my ebuilds available to emerge.

so this is my structure:
# ls -R /usr/local/portage/*
/usr/local/portage/dev-ruby:
stomp

/usr/local/portage/dev-ruby/stomp:
ChangeLog  Manifest  stomp-1.1.6.ebuild  stomp-1.1.ebuild

/usr/local/portage/multi-tool:
mcollective

/usr/local/portage/multi-tool/mcollective:
ChangeLog  files  Manifest  mcollective-0.4.7.ebuild  mcollective-0.4.8.ebuild

/usr/local/portage/multi-tool/mcollective/files:
client.cfg.dist.patch  mcollectived.conf  mcollectived.init  
server.cfg.dist.patch

/usr/local/portage/profiles:
repo_name


So now I try to install new package:

# emerge multi-tool/mcollective

  * IMPORTANT: 1 news items need reading for repository 'gentoo'.
  * Use eselect news to read news items.

Calculating dependencies /

!!! Invalid or corrupt dependency specification:

Conditional without parenthesis: 'server?'

('ebuild', '/', 'multi-tool/mcollective-0.4.8', 'merge')

server? || ( =dev-ruby/stomp-1.1=dev-ruby/stomp-1.1.6 )=dev-lang/ruby-1.8

This package can not be installed. Please notify the 'multi-
tool/mcollective-0.4.8' package maintainer about this problem.
... done!


and it complains about server line.

I've tried to add a parenthesis to that line, and after new digest, it
still complains about that line.


so, anyone with more experience could help me? is there a real problem
with the ebuild? or the problem is mine? (most probable :-) ).

*Instead of pasting ebuild code, I paste download link:

http://code.google.com/p/mcollective/downloads/list


Thanks in advance,


Try replacing the DEPEND= line with

DEPEND=server? ( || ( =dev-ruby/stomp-1.1 =dev-ruby/stomp-1.1.6 ) )




Re: [gentoo-user] problems adding local overlay and ebuild

2010-09-01 Thread Ian Lee

On 01/09/10 13:57, Arnau Bria wrote:

On Wed, 01 Sep 2010 12:25:03 +0100
Ian Lee wrote:

Hi Ian,


Try replacing the DEPEND= line with

DEPEND=server? ( || ( =dev-ruby/stomp-1.1=dev-ruby/stomp-1.1.6 ) )


fails on manifest:

# ebuild mcollective-0.4.8.ebuild manifest
Error(s) in metadata for 'multi-tool/mcollective-0.4.8':
   DEPEND: server? ( || ( =dev-ruby/stomp-1.1=dev-ruby/stomp-1.1.6 ) 
)=dev-lang/ruby-1.8 )
 invalid atom: ''
   RDEPEND: server? ( || ( =dev-ruby/stomp-1.1=dev-ruby/stomp-1.1.6 ) 
)=dev-lang/ruby-1.8 )
 invalid atom: ''

Cheers,


Oops may bad. I missed off the last dependency

Should read

DEPEND==dev-lang/ruby-1.8
server? ( || ( =dev-ruby/stomp-1.1 =dev-ruby/stomp-1.1.6 ) )



Re: [gentoo-user] lvm problem -- is timing?

2009-06-21 Thread Ian Lee

Neil Bothwick wrote:

On Sun, 21 Jun 2009 15:16:49 -0600, Maxim Wexler wrote:


mount: /dev/vg/tmp already mounted on /tmp
mount: tmpfs already mounted on /tmp


It's nothing to do with your problem, but why are you mounting two
filesystems on /tmp?


  Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.


Can you confirm this is the SD card?

I still think there may be a delay in the kernel seeing the SD card, this
used to happen with my Eee. Have you tried adding a sleep command to the
relevant part of init.d/bootmisc?

How large is the SSD in your Eee? Is it really necessary to have a volume
group spanning the SSD and SD card, two very different devices?


Would I be correct in thinking the SSD is a sata device while the SD is 
a usb device??


How are you USB drivers compiled in the kenrnel?



Re: [gentoo-user] uvesafb will not work on my dell d820 laptop?

2009-06-20 Thread Ian Lee

John covici wrote:

Hi.  I have a Dell Latitude D820 laptop and for the life of me, I
can't get uvesafb to work.  There are no messages, I just get the 25
lines by 80 column screen.  I emerged clib, and v86d and made sure my
.config had /usr/share/v86d/initramfs as the initramfs source, and I
have uvesafb built in to the kernel.  My boot time command line
arguments to lilo are:
init=/linuxrc ramdisk=8192 real_root=/dev/sda5 udev
video=uvesafb:1024x768 speakup.synth=spkout
(all on one line in the original).

Attached is my emerge --info and my kernel config -- assistance would
be appreciated.






According to you kernel config, uvesafb is not built in to the kernel, 
but as a module. Try building it in to the kernel and not as a module.



Ian



Re: [gentoo-user] Re: x86 versus amd64 - where is it set / overwritten

2009-02-13 Thread Ian Lee

Nikos Chantziaras wrote:

Helmut Jarausch wrote:

On 13 Feb, Nikos Chantziaras wrote:

Helmut Jarausch wrote:

Hi,

I'm working on an AMD opteron, definitely an AMD64 machine.

/etc/make.conf  contains
CHOST=x86_64-pc-linux-gnu

my profile is
default/linux/amd64/2008.0/desktop

Still, when emerging sci-libs/acml, portage
fetches the 32-bit variant of the package.
The SRC_URI depends on use flags x86 and amd86.
This package is fetch restricted.  It shouldn't actually fetch 
anything.   You have to download the correct tarball and place it in 
/usr/portage/distfiles.




OK, my wording was wrong. I did fetch the 64-bit version but emerge
didn't use it, but told me to fetch the 32-bit version.


Hmm.  Get that one too then and see which one is picked when the actual 
emerge starts.  It could be that it needs both.  If it ends up building 
the 32-bit one only, then I guess it's time for a bug report :)





Its definitely a 64/32 bit problem and nothing to do with the int64 use 
flag?









Re: [gentoo-user] Change colours of xterm

2009-02-08 Thread Ian Lee

Mike Kazantsev wrote:

On Sat, 07 Feb 2009 17:57:18 +
Ian Lee i...@leehouse.eclipse.co.uk wrote:


but still no white on black xterm, what am I missing??


You can try putting

XTerm*background:   #001800
XTerm*foreground:   #A8A8A8

to ~/.Xresources
WFM




Thanks that worked.


I got finally got a system config rather than user config working
(not that i needed a system config)

/etc/X11/Xresources:
add

*customization: -color


/etc/env.d/10xpaths:
change
XFILESEARCHPATH=/etc/X11/%T/%N:/usr/share/X11/%T/%N
to
XFILESEARCHPATH=/etc/X11/%T/%N%C:/usr/share/X11/%T/%N%C

/etc/X11/app-defaults/XTerm-color now works.




[gentoo-user] Change colours of xterm

2009-02-07 Thread Ian Lee
I use to have a white text on black xterm, but since my last reinstall I 
have not been able to change the colours.


I have copied the /usr/share/X11/app-defaults/XTerm-color to 
/etc/X11/app-defaults and changed the options to


*VT100*foreground: gray90
*VT100*background: black

I have XFILESEARCHPATH = /etc/X11/%T/%N:/usr/share/X11/%T/%N

but still no white on black xterm, what am I missing??

thanks Ian



Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

2008-12-29 Thread Ian Lee

Neil Bothwick wrote:

On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:


Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf




That's in /etc/conf.d/rc on mine.  Has it moved?


It moved in the switch from baselayout1 to baselayout2/openrc.



This could be what four looking for

http://bugs.gentoo.org/show_bug.cgi?id=206518



Ian



Re: [gentoo-user] Re: What is starting net.eth1 [not in rc-update]

2008-12-29 Thread Ian Lee

Dale wrote:

Harry Putnam wrote:

Ian Lee i...@leehouse.eclipse.co.uk writes:

  

Ian Lee wrote:


Neil Bothwick wrote:
  

On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote:



Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf



That's in /etc/conf.d/rc on mine.  Has it moved?
  

It moved in the switch from baselayout1 to baselayout2/openrc.




This could be what four looking for

http://bugs.gentoo.org/show_bug.cgi?id=206518



Ian

  

try putting rc_coldplug=no in conf.d/udev or /etc/rc.conf  i would
assume the udev init script checks both places


I can tell you from trying that just now... that is not a good
solution.

First setting rc_coldplug=no has some very bad effects:
1) caused my KVM switch setup to be ignored completely, where as with
   with the default yes  the kvm is recognized soon as I get past
   grub

2) Very strange behavior with the `screen' tool.  I call screen and
   get started but if I do `C-a c' (which should start another screen)
   Instead it prompts me to login and then takes the original screen
   so I can only get one screen, completely defeating the purpose of
   `screen'. 



I'm also wondering about the wisdom introduciing some esoteric places
to control services.  If someone needs sophisticated controls they can
set that up, but for the rest of us  /etc/conf.d and rc-update should
be THE central tools to have basic services started at boot.

There should be nothing scrolling thru the network softlinks
attempting to start anything it finds.



  


If you check mine and Neils post, one of ours will do just what you want
and still allow you to have hotplug set to yes.  It just tells hotplug
not to start networks itself and leave it to your own settings with
rc-update.  There may also be other things that you can set in there as
well. 


Dale

:-)  :-)



According to the comments hotplugging of services is not allowed by 
default, so why do the net.* services get started?




Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

2008-12-28 Thread Ian Lee

Harry Putnam wrote:

I don't have an entry for net.eth1 in rc-update show

I don't have any mention of eth1 in /etc/conf.d/net
(only eth0)

Nonetheless something continues to try to start net.eth1 during boot.
What else controls that?  If its not in rc-update or /etc/conf.d/net
it shouldn't happen.

I have a few other boot problems...I'm not sure where they arise from.

hwclock is meddling about during shutdown.
Again, it isn't shown in rc-update 
and /etc/conf.d/hwclock has this in it:


  # If you want to set the Hardware Clock to the current System Time
  # during shutdown, then say YES here.  You normally don't need to
  # do this if you run a ntp daemon.
  clock_systohc=NO

Still, on a shutdown I can't get past this output:
 
 hwclock waiting for localmount

 (Over and over)

I have to hit a manual reset on the computer to get past 
  hwclock waiting for localmount


Also klogd cannot be stopped by reboot or shutdown.  But at least,
unlike hwclock, after a pause the shutdown proceeds anyway.

 eix -Ic openrc
  sys-apps/openrc (0@12/25/08): OpenRC manages the services, startup
  and shutdown of a host

 eix -Ic udev
  [I] sys-fs/udev (135...@12/24/08): Linux dynamic and persistent device
  naming support (aka userspace devfs)




1) net.eth1 problem

There is a udev hook for starting net.* init scripts, 
/lib/udev/rules.d/90-network.rules to be precise



2) Openrc problem
I'm asuming here the openrc problems are from a recent upgrade you have 
done and not inslalled the the runlevels required sadly they are not 
done automatically. Have a look in /usr/share/openrc/runlevels these are 
needed for openrc to work copy any that don't exist in /etc/runlevels 
most important are sysinit and shutdown, boot and default are likey to 
be fine






Re: [gentoo-user] What is starting net.eth1 [not in rc-update]

2008-12-28 Thread Ian Lee

Dirk Heinrichs wrote:

Am Sonntag, 28. Dezember 2008 12:50:41 schrieb Ian Lee:


2) Openrc problem
I'm asuming here the openrc problems are from a recent upgrade you have
done and not inslalled the the runlevels required sadly they are not
done automatically. Have a look in /usr/share/openrc/runlevels these are
needed for openrc to work copy any that don't exist in /etc/runlevels
most important are sysinit and shutdown, boot and default are likey to
be fine


Hmm, I have the same problem here, but I do have all the directories from 
/usr/share/openrc/runlevels in /etc/runlevels.


Bye...

Dirk

I just found this it might help

http://bugs.gentoo.org/252380



Re: [gentoo-user] Re: What is starting net.eth1 [not in rc-update]

2008-12-28 Thread Ian Lee

Harry Putnam wrote:

Ian Lee i...@leehouse.eclipse.co.uk writes:


1) net.eth1 problem

There is a udev hook for starting net.* init scripts,
/lib/udev/rules.d/90-network.rules to be precise


The script is very brief 
There is no mention of net.eth1 in that script


  SUBSYSTEM==net, ACTION==add,RUN+=net.sh %k start
  SUBSYSTEM==net, ACTION==remove, RUN+=net.sh %k stop

Further it says not edit this script since it gets overwritten on
update.

Apparently this is not the place to alter what happens at runlevels.



2) Openrc problem
I'm asuming here the openrc problems are from a recent upgrade you
have done and not inslalled the the runlevels required sadly they are
not done automatically. Have a look in /usr/share/openrc/runlevels
these are needed for openrc to work copy any that don't exist in
/etc/runlevels most important are sysinit and shutdown, boot and
default are likey to be fine


They are all present in /etc/runlevels.

And again I see no reference to net.eth1 or hwclock




that udev rule starts any found network devices on your system net.sh is 
just a  wrapper to the net.* scripts in init.d, if you never use eth1 
then remove net.eth1 from /etc/init.d.





Re: [gentoo-user] uvesafb and screen resolution

2008-03-25 Thread Ian Lee

Ricardo Saffi Marques wrote:
On Tue, Mar 25, 2008 at 5:37 PM, Alexander Meinke [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:


Try to determine possible resolutions by typing hwinfo
--framebuffer. Use the
hex code 0x... and put it as kernel parameter in your grub.conf.


Okay, *that* I didn't know. :-)
I do know 1440x900 is a supported resolution on my machines since it's 
the native resolution of their screen's.
 


For 1400x1050 with kernel 2.6.24-r3 I am using the following lines:
title Gentoo GNU/Linux (gentoo-sources-2.6.24-r3)
root (hd0,1)
kernel /gentoo-sources-2.6.24-r3 root=/dev/sda5 vga=0x344


So after the change from the vesafb-tng to the actual uvesafb on the 
kernel, it actually IS necessary to use the vga=something trick on the 
boot line, then?

I'll do it and tell the results.

Thanks a lot, Alexander!

Best regards,

Saffi

--
Ricardo Saffi Marques
Laboratório de Administração e Segurança de Sistemas (LAS/IC)
Universidade Estadual de Campinas (UNICAMP)
Cell: +55 (19) 8128-0435
Skype: ricardo_saffi_marques
Website: http://www.rsaffi.


i always thought vga= was only used by the old vesafb driver
i use video=uvesafb:1024x768-32
i cant get any wide screen modes to work at all, anybody else know how??
--
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Viewing BBC videos on Gentoo

2008-02-10 Thread Ian Lee
Jeff Cranmer wrote:
 Has anyone had any luck viewing videos on news.bbc.co.uk using gentoo?

 I have Firefox and mplayerplug-in installed, however I cannot view videos, 
 either with the embedded player or the standalone.

 Jeff
   
It's a flash based player mplayer wont work
-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Viewing BBC videos on Gentoo

2008-02-10 Thread Ian Lee
Ian Lee wrote:
 Jeff Cranmer wrote:
   
 Has anyone had any luck viewing videos on news.bbc.co.uk using gentoo?

 I have Firefox and mplayerplug-in installed, however I cannot view videos, 
 either with the embedded player or the standalone.

 Jeff
   
 
 It's a flash based player mplayer wont work
   
If you're using 64 bit firefox net-www/nspluginwrapper is a good way to
get flash working or theres firefox-bin
-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] [query] kernel-2.6.24 + ndiswrapper

2008-02-09 Thread Ian Lee
dell core2duo wrote:
 Hi all,
I was using kernel 2.6.23 till now and everything was working
 pretty well.
  My wireless card is ---0c:00.0 Network controller: Broadcom
 Corporation BCM94311MCG wlan mini-PCI (rev 01).
 It was working fine with kernel 2.6.23 with ndiswrapper. Yesterday i
 upgraded to kernel 2.4.26. And my wireless card
 stopped working.  It says that eth1 does not exist.
 Some important out are below
 ---
 flukebox # ndiswrapper -l
 bcmwl5 : driver installed
 device (14E4:4311) present
 flukebox # /etc/init.d/net.eth1 start
  * Starting eth1
  * /etc/conf.d/wireless is deprecated
  * Please put all settings in /etc/conf.d/net
  * /etc/conf.d/wireless is deprecated
  * Please put all settings in /etc/conf.d/net
  *   Configuration not set for eth1 - assuming DHCP
  *   Bringing up eth1
  * dhcp
  *   network interface eth1 does not exist
  *   Please verify hardware or kernel module
 (driver)  
 
 [ !! ]
 flukebox #
 

 I didn't have any kernel built-in module for bcmxx .
 Can somebody help me here. Any help would be appreciated.

 TIA,
 flukebox





Have u rebuilt the ndiswprapper kernel module for the new kernel?
try reinstalling ndiswrapper
-- 
gentoo-user@lists.gentoo.org mailing list



Re: [gentoo-user] Make errors with new kernel-gentoo-2.6.23-r3

2007-12-07 Thread Ian Lee
Mick wrote:
 Hi All,

 I've installed the new kernel and I can't compile the various driver modules 
 for it.  So far both net-wireless/rt2570-20070209 and 
 media-libs/svgalib-1.9.25 failed.  This is the error message of the latter:
 
   CC 
 [M]  
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/i810.o
   CC 
 [M]  
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/interrupt.o
 In file included 
 from 
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/interrupt.c:5:
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/kernel26compat.h:74:
  
 warning: 'struct file_operations' declared inside parameter list
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/kernel26compat.h:74:
  
 warning: its scope is only this definition or declaration, which is probably 
 not what you want
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/kernel26compat.h:
  
 In function 'devfs_register_chrdev':
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/kernel26compat.h:76:
  
 error: implicit declaration of function 'register_chrdev'
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/kernel26compat.h:
  
 In function 'devfs_unregister_chrdev':
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/kernel26compat.h:80:
  
 error: implicit declaration of function 'unregister_chrdev'
 make[2]: *** 
 [/var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/interrupt.o]
  
 Error 1
 make[2]: *** Waiting for unfinished jobs
 In file included 
 from 
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/main.c:48:
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/kernel26compat.h:
  
 In function 'devfs_unregister_chrdev':
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/kernel26compat.h:80:
  
 error: void value not ignored as it ought to be
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/main.c:
  
 In function 'svgalib_helper_ioctl':
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/main.c:363:
  
 warning: 'deprecated_irq_flag' is deprecated (declared at 
 include/linux/interrupt.h:64)
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/main.c:363:
  
 warning: passing argument 2 of 'request_irq' from incompatible pointer type
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/main.c:
  
 In function 'svgalib_helper_open':
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/main.c:451:
  
 warning: 'deprecated_irq_flag' is deprecated (declared at 
 include/linux/interrupt.h:64)
 /var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/main.c:451:
  
 warning: passing argument 2 of 'request_irq' from incompatible pointer type
 make[2]: *** 
 [/var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper/main.o]
  
 Error 1
 make[1]: *** 
 [_module_/var/tmp/portage/media-libs/svgalib-1.9.25/work/svgalib-1.9.25/kernel/svgalib_helper]
  
 Error 2
 make[1]: Leaving directory `/usr/src/linux-2.6.23-gentoo-r3'
 make: *** [default] Error 2
  * 
  * ERROR: media-libs/svgalib-1.9.25 failed.
  * Call stack:
  *   ebuild.sh, line 1701:  Called dyn_compile
  *   ebuild.sh, line 1039:  Called qa_call 'src_compile'
  *   ebuild.sh, line   44:  Called src_compile
  *   svgalib-1.9.25.ebuild, line   78:  Called linux-mod_src_compile
  *linux-mod.eclass, line  518:  Called die
  * The specific snippet of code:
  *  emake HOSTCC=$(tc-getBUILD_CC) 
 CC=$(get-KERNEL_CC) 
 LDFLAGS=$(get_abi_LDFLAGS) \
  *${BUILD_FIXES} ${BUILD_PARAMS} 
 ${BUILD_TARGETS} \
  *  || die Unable to make ${BUILD_FIXES} 
 ${BUILD_PARAMS} ${BUILD_TARGETS}.
  *  The die message:
  *   Unable to make  KDIR=/lib/modules/2.6.23-gentoo-r3/build default.
  * 
 

 Can you make sense of this?
   
there is a bug report for svgalib on kernel 2.6.23 here:
http://bugs.gentoo.org/show_bug.cgi?id=195632

There is a patch for the bug, but when it'll be in portage you'll have
to wait and see
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] New kernel broken nvidia-drivers

2007-12-06 Thread Ian Lee
Randy Barlow wrote:
 I updated from 2.6.22-gentoo-r9 to 2.6.23-gentoo-r3, and now
 nvidia-drivers-1.0-7185 won't build.  I use the older drivers because I
 have a Riva TNT2.  When I change the /usr/src/linux link to the old
 kernel source, the package builds just fine, so I'm thinking that
 something is broken with my new config.  I attached the build log.  It
 complains about some things not being defined, like nv_pte_t_cache.  Is
 this a kernel config problem?  I didn't find it in bugs.gentoo, but
 google found a few others having the same issue with some other versions
 of nvidia-drivers.

   
according to the nvidia site version 71.86.01 is the lastest TNT2
drivers have tried these they are in the portage tree
-- 
[EMAIL PROTECTED] mailing list