I'm getting an error for dm-crypt mappings at bootup... the same thing in the previous post about "Failed to setup a mapping or swap device.: integer expression expected"

I'm not sure if that has anything to do with the fact that now cardmgr fails to start now. It says Make sure that you have PCMCIA modules built or support compiled into the kernel, but I certainly do and it was working for previous builds of this kernel before I emerge the new baselayout. Any known fixes?

Oh, and the /etc/init.d/net.xxx script doesn't work at all. ("Looks like there was a probem loading the firmware for ra0.") So I'm starting it by hand... I never understood what good net.xxx did anyway.

First of all, thanks very much for a great improvement to the wireless scripts. The merge into baselayout has greatly improved things.

I got it working mostly, where I now have my wired as eth0 built in (and many thanks for the configurability of the DHCP timeout, BTW...when I'm not wired (e.g., on an airplane) it sucked having to wait forever for it to not get an address). I was getting annoyed enough to consider installing DHCPD and using a loopback plug...

My problem now is getting the multiple key option to work with the AP. It works OK with just one, of course, but I'd like to try to understand the entirety of it.

Working config is the following (conf.d/wireless, just the relevant lines):
I've obfuscated the key and AP name.

eth1 does not support setting keys
or the parameter "mac_key_Bobo" or "key_Bobo" is incorrect
Failed to associate with any preferred access points on eth1

My access point is a stock Linksys WRT54G, configured with Bobo as the ESSID, no SSID broadcast (there are enough other wide open APs for folks to pick), WEP 128-bit encryption, and MAC address filtering. My Linux box is Gentoo 2.6.8-r3 with orinoco_pci drivers for my ThinkPad T30's built in Intersil Prism 2.

On a related note, I am also getting the dm-crypt issue after emerging the new baselayout. It boots OK, but it seems that for some reason the check in /etc/init.d/checkfs for the existence of /etc/conf.d/cryptfs actually passes, even though the file isn't there, so at the end, the line 244 gets called:

Code:

ewend ${cryptfs_status} 'Failed to setup a mapping or swap device.'

I've noticed this seems to be harmless (swap is actually still mounted OK, all systems functioning normal), but it was puzzling. I was more annoyed that I've spent too much time in recent years in the Windows world and my scripting skills are too rusty to have figured it out on my own.

And the set of PS1 in baselayout 1.11.x was also annoying, but I fixed that by editing /etc/profile again and modifying the else off the /etc/bash/bashrc test (which doesn't exist, and I was too lazy to build it):

I too get dm-crypt mappings errors at boot, and I have no idea what it is. I can't understand why installing a wireless card does this and removes the colors from my prompt.

It is an experimental version of baselayout - if you don't want those error's then you can always go back to an earlier version and use the wireless ebuild.

Quote:

Oh, and the /etc/init.d/net.xxx script doesn't work at all. ("Looks like there was a probem loading the firmware for ra0.") So I'm starting it by hand... I never understood what good net.xxx did anyway.

Could you post the output of the following please - sounds like a similar problem to the ipw2200 user above