Summary: | Baselayout 1.12.0-r1 breaks net.eth0, net.wlan0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aaron Sheldon <asheldon> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | tinaught |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aaron Sheldon
2006-06-04 07:22:32 UTC
To reproduce: emerge baselayout 1.12.0-r1 moving from original baselayout Reproducible: Always* *I want to re-check the net.wlan0 bug later, I'm not sure if I can reproduce it now that I've done the sudo cp workaround. Post if you need me to. Just to clarify, net.eth0 does still work for me after the baselayout change. In fact, I can't make it stop working. net.wlan0 just dies. (by which I mean it fails to start - I can downgrade and re-upgrade later if necessary.) I don't have a fancy wireless config. Just 3 lines. /etc/conf.d/wireless: essid_wlan0="dirt" key_dirt="0123456789" #not my actual key value, but it is 10-digit numeric config_dirt=( "dhcp" ) Using ndiswrapper for wireless support. lspci | grep Wireless 02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) emerge --info: Portage 2.0.54-r2 (default-linux/x86/no-nptl, gcc-3.4.5, glibc-2.3.6-r3, 2.6.16- gentoo-r8 i686) ================================================================= System uname: 2.6.16-gentoo-r8 i686 Intel(R) Pentium(R) 4 CPU 3.20GHz Gentoo Base System version 1.12.0 dev-lang/python: 2.4.2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/lib/X11/xkb /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/ distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 X a52 aac aim alsa apache2 apm asf audiofile automount avi bash-complet ion berkdb bidi bitmap-fonts bzip2 cdr cjk cli crypt cups curl dri dvd dvdr dvdr ead emboss encode exif expat fam foomaticdb fortran fuse gdbm gif glut gnome gpm gstreamer gtk gtk2 idn imagemagick imlib ipod ipv6 isdnlog jabber java javascri pt joystick jpeg kde lcms libg++ libwww mad mikmod mmx mmxext mng motif mp3 mpeg ncurses nls nsplugin ogg opengl openssh oscar oss pam pcmcia pcre pdflib perl p hp png pppd python qt quicktime rdesktop readline real reflection reiser4 reiser fs samba sdl session slp spell spl sse sse2 ssl stream subtitles svg tcpd theora tiff truetype truetype-fonts type1-fonts udev unicode usb v4l v4l2 vorbis wifi win32codecs wmf xine xinerama xml xml2 xmms xorg xscreensaver xv xvid yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXT RA_OPTS, PORTAGE_RSYNC_OPTS (In reply to comment #0) > First bug: net.eth0 starts no matter what. I don't have net.eth0 in my rc > (posted below) yet it seems to feel the need to start anyway. This behavior is > annoying since I'm on a laptop and am almost never on a wired network. that is coldplug - either the old script or a new udev. You can stop this by using the settings in /etc/conf.d/rc > > Second bug: net.wlan0 is completely borked. A workaround I found (I don't care > if it's a hack right now) is to do > > sudo cp /etc/init.d/net.eth0 /etc/init.d/net.wlan0 No it's not. net.wlan0 should be a symlink to net.lo otherwise it would never get updated in sync with baselayout upgrades. Lastly, please attach the actual error after re-creating the net.wlan0 net.lo symlink instead of just saying it's borked. |