Wireless configuration and startup - The Gentoo way (part 2)

wizard_ct · n00b Joined: 08 Dec 2003 Posts: 37

Using baselayout-1.11.1 wireless is working great with my Prism 2.5 mini-pci card.

However, in addition to the crypt and /etc/profile issues, running emerge reduces my console to approximatly 1/4 the size of my viewable framebuffer screen. Has anyone seen this/have a hack to fix it?

Thanks.

DevSolar · Tux's lil' helper Joined: 07 Sep 2004 Posts: 82

I've seen this happen, too, but that was when I did "make menuconfig"...

I used baselayout 1.11.1 right from the start (i.e., not using 1.9.x first and then updating, but going for 1.11.1 with a fresh install). Two things I noticed where dependencies aren't really "clean":

* it needs sysvinit ~x86 (>=2.84 if I remember correctly);
* during boot, the system complains that it cannot find /bin/cryptsetup.

kamina · Posted: Wed Sep 29, 2004 4:50 am Post subject:

geekporn · n00b Joined: 17 Jan 2004 Posts: 17

Thanks for this solution... was having a bit of trouble with my wife breathing down my neck to get her wireless connection a bit more automated!

UberLord · Posted: Wed Sep 29, 2004 9:04 am Post subject:

UberLord · Posted: Wed Sep 29, 2004 9:06 am Post subject:

UberLord · Posted: Thu Sep 30, 2004 9:25 am Post subject:

NEW NET-SCRIPTS PACKAGE AVAILABLE

http://rsm.demon.co.uk/~roy/downloads/net-scripts-1.0.2.tar.bz2

Simply put the contents of the archive into /etc to install

Or, just replace the /etc/net.modules.d/wireless file with the similar one from the archive

There's a changelog in the archive.
I'm on holiday now for 2 weeks, so if any problems arise then they'll just have to wait :wink:

warning any people using the preferred_only var will have to change to the new associate_order var. See wireless.example for details

An older version net-scripts is included in baselayout-1.11.1 if you're wondering ......
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool

RK7 · n00b Joined: 11 Sep 2004 Posts: 9

after emerging the masked version of baselayout, i checked my /etc/conf.d directory to see if everything was updated properly, and for some reason there was no net.lo. any ideas what might be going on?

thanks.
_________________
RK.

dyqik · Posted: Sun Oct 03, 2004 10:53 am Post subject:

The ipw2100 disconnecting problem sounds like the same problem I've been having with the 0.11 ipw2200 drivers. (same disconnect after some time, and no dmesg errors). The 0.10 ipw2200 drivers wdidnt have that problem, so maybe an earlier version of the ipw2100 drivers don't either. Try the ipw2100.sf.net mailing list archive for driver support.

doalwa · Posted: Mon Oct 04, 2004 12:05 am Post subject:

UberLord, I just wanted to thank you for your great work, I just completed the task of joining my home network with a Dlink dwl-g502+ PCI card using Linuxants driver Loader..everythings working fine, including WEP encryption,thanks to your really cool startup script!

Anyway, you just totally rock, man!

_________________
Keepin' the Funk alive since 1983!

yamakawa · Guru Joined: 28 Jul 2003 Posts: 340

Wow! Brilliant!!!

vicG · n00b Joined: 31 Jan 2003 Posts: 21

Fool newb here --

Followed the steps verbatim:
mkdir -P /etc/portage

emerge sync

echo "=sys-apps/baselayout-1.11.0" >> /etc/portage/package.unmask

and when I emerged it, it grabbed baselayout 1.9.4.

So I deleted package.unmask, and changed it to

echo "=sys-apps/baselayout-1.11.0 ~x86" >> /etc/portage/package.keywords

(why does this one have to be in package.keywords and the other in package.unmask?)

I then re-ran emerge sync (sorry, but I wanted to follow the instructions exactly), but when I ran emerge -av sys-apps/baselayout again, it still grabbed 1.9.4.

Why am I getting this older version when everyone else is getting 1.11?

oisch · Tux's lil' helper Joined: 17 Jul 2002 Posts: 130

@UberLord: The /etc/conf.d/net.example says that there is a $ESSID global variable that I can use for example in the postup() function.
But this variable doesn't exist. Is this a bug in the current scripts or is it my mistake (I only test for $ESSID without any special tricks).

mope · Apprentice Joined: 23 Feb 2003 Posts: 206

DevSolar · Tux's lil' helper Joined: 07 Sep 2004 Posts: 82

@ vicG:

The packet version is 1.11.1.

jaycochran · n00b Joined: 08 Oct 2004 Posts: 1

For some reason my wireless card starts on system boot even though it is not on in the "default" runlevel

Neither my wired card "eth0" or my wireless card "eth1" are turned on through rc-update. The only network device that should start is "lo0" in the boot level. After the system boots, running /etc/init.d/net.eth1 status shows it started so some where the rc script was kicked off. "eth0" behaves the way it should and is not started.

I'm running baselayout-1.11.1 and everything else works just the way it should be. net.eth0 and net.eth1 are sym linked to net.lo

seppe · Posted: Sat Oct 09, 2004 12:29 pm Post subject:

Emerging this new and masked baselayout did b0rked some things:
I get several errors at boot that /usr/bin/cryptsetup (or something) doesn't exist, localmount service can't started either.
I did also

nyda · Apprentice Joined: 12 Aug 2004 Posts: 183

jcosters · Posted: Sun Oct 10, 2004 8:25 pm Post subject:

I have a problem using WEP and an ESSID with '.'s in it:

scoon · Posted: Mon Oct 11, 2004 1:51 pm Post subject:

roeles · n00b Joined: 10 Mar 2004 Posts: 3

10 times sorry if this has been posted already, but I did not see it yet in this nor the original thread.

I configured (afaik) correctly, but my wlan card seems to nag a little bit. It's a Sitecom WL-012. I had a successfull attempt at trying to connect to an Ad-Hoc network before, with the 'old' scripts (the wlanctl-ESSID files and such). It connected straight away when plugging in the thingy.
However, I had more and more trouble getting it to connect to my (WEP encrypted) AP. Therefore I got the ~x86 baselayout stuff.
I get this error when running /etc/init.d/net.wlan0 (wich points to net.lo btw):

ralle · Posted: Wed Oct 13, 2004 9:58 am Post subject:

concerning the 1/4 screen problem:

I only recognized this as root, so I copied .bash_profile and .bashrc from some user dir to the root dir (I did not have these files before).
Until now the problem has disappeared, but I am not completely sure because it only occured sometimes before, not always.

nyda · Apprentice Joined: 12 Aug 2004 Posts: 183

scoon · Posted: Wed Oct 13, 2004 10:12 am Post subject:

jcosters · Posted: Wed Oct 13, 2004 12:40 pm Post subject: