| View previous topic :: View next topic |
| Author |
Message |
Teklmanx
n00b
Joined: 26 Apr 2003
Posts: 25
Location: Bahamas
|
 Posted: Sat Feb 04, 2006 5:12 pm Post subject: Wireless GNAP Problem on a WRAP.2c board |
 |
|
Hey guys, has anyone had any luck with getting madwifi-driver or wireless-tools on a gnap setup? I bought this WRAP.2c board and a atheros based wireless mini-pci card to go with it... only problem is my gnap_make process fails everytime. Help please :/
_________________
-<-_.: )|( :._->- |
|
| Back to top |
|
 |
Teklmanx
n00b
Joined: 26 Apr 2003
Posts: 25
Location: Bahamas
|
| Posted: Wed Feb 08, 2006 12:34 am Post subject: |
|
|
Basically what happens is everytime I try to add madwifi-driver as an extension it fails.
Here's the contents of my extensions.conf:
# List of extensions to build
extensions: madwifi-driver
madwifi-driver/packlist: madwifi-driver
#OEF
Here's the command I run:
gnap_make -t extensions -p portage-latest.tar.bz2 -e /gnap/specs
Here's the log:
http://tekmanx.serveftp.com/~tekmanx/gnap-out.txt
*Note I get the same error regardless of the portage source I use be it an overlay of the root system's portage.. the latest snapshot or the one that comes with the gnap pkg.
_________________
-<-_.: )|( :._->- |
|
| Back to top |
|
|
widan
Veteran
Joined: 07 Jun 2005
Posts: 1512
Location: Paris, France
|
| Posted: Wed Feb 08, 2006 1:21 am Post subject: |
|
|
Your problem is this:
| Code: | !!! All ebuilds that could satisfy "madwifi-driver" have been masked.
!!! One of the following masked packages is required to complete your request:
- net-wireless/madwifi-driver-0.1401.20060117 (masked by: ~x86 keyword)
- net-wireless/madwifi-driver-0.1_pre20050420-r1 (masked by: ~x86 keyword)
- net-wireless/madwifi-driver-0.1420.20060201 (masked by: ~x86 keyword)
For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook. |
The madwifi-driver ebuild is masked, so the binary package isn't built, but the rest of the process seems to continue in spite of the error. Later, when it tries to use it to generate the image, it fails because the binary package doesn't exist.
You can try to unmask the version you want. From the command you're using, the process seems to use its own portage snapshot, so you will need to unpack that somewhere, unmask the package in that tree, regenerate the digest, then rebuild the snapshot tarball from the modified tree, and retry.
Of course if you have a way to use something like package.keywords to unmask things selectively, you can do that instead. I don't know if the GNAP-making process handles that though. |
|
| Back to top |
|
|
Teklmanx
n00b
Joined: 26 Apr 2003
Posts: 25
Location: Bahamas
|
| Posted: Wed Feb 08, 2006 12:00 pm Post subject: |
|
|
I guess I'm out of luck then. The docs for gnap say nothing about unmasking packages.. hopefuly a dev comes by and shows me some way of hacking through it. What good is an embedded OS without full wifi support? :/
Thanks man.
_________________
-<-_.: )|( :._->- |
|
| Back to top |
|
|
widan
Veteran
Joined: 07 Jun 2005
Posts: 1512
Location: Paris, France
|
| Posted: Wed Feb 08, 2006 1:17 pm Post subject: |
|
|
Even if there is no way to do it in the proper way, you can try to do it by modifying the snapshot tarball directly. Visibly the script that makes the image uses its own portage snapshot (portage-latest.tar.bz2).
- Untar that snapshot somewhere.
- Edit the appropriate ebuild for the version you want (it will be in <path_to_snapshot>/net-wireless/madwifi-driver/madwifi-driver-<version>.ebuild) and replace "~x86" by "x86" in the KEYWORDS line.
- Rebuild the digest by running "ebuild <path_to_snapshot>/net-wireless/madwifi-driver/madwifi-driver-<version>.ebuild digest".
- Recreate the snapshot tarball with the modified ebuild in it.
- Try to create your GNAP image using that modified snapshot rather than the original one.
|
|
| Back to top |
|
|
Teklmanx
n00b
Joined: 26 Apr 2003
Posts: 25
Location: Bahamas
|
| Posted: Wed Feb 08, 2006 1:35 pm Post subject: |
|
|
I will try this ASAP! I actually spoke to a few people on IRC about what exactly makes a package masked. I thought it would have veeb files outside of the portage snapshot. Now that I got new word on this I'll try it ans let you know. Thanks.
_________________
-<-_.: )|( :._->- |
|
| Back to top |
|
|
Teklmanx
n00b
Joined: 26 Apr 2003
Posts: 25
Location: Bahamas
|
| Posted: Fri Feb 10, 2006 2:56 am Post subject: |
|
|
I think I got a step further.. now it fails while trying to unmount some volume.. check it out let me know what you think:
http://tekmanx.serveftp.com/~tekmanx/gnap-out.txt
*Note.. this volume is not mounted when I run the mount command.
_________________
-<-_.: )|( :._->- |
|
| Back to top |
|
|
richard.scott
Veteran
Joined: 19 May 2003
Posts: 1497
Location: Oxfordshire, UK
|
| Posted: Wed Feb 28, 2007 4:24 pm Post subject: |
|
|
Hi,
Have you got this to work?
You need to untar the gnap specs and update them to build the madwifi drivers at the same time as the kernel.
Give this a go:
| Code: | # cd /tmp/
tmp # mkdir gnap
tmp # cd gnap
gnap # tar xjpvf /usr/lib/gnap/gnap-specs.tar.bz2 |
In the /tmp/gnap directory there will be some files we need to update......
edit the livecd.conf file and add the follwing:
| Code: | boot/kernel/gentoo/packages:
cbqinit
htbinit
madwifi-ng
madwifi-ng-tools
pcmcia-cs |
edit the packages.conf file and remove the lines for:
and add in:
If you need to unmask any files then edit the /tmp/gnap/portage_confdir/ directory. These files are coppied into the /etc/portage directory and act in th exact same way your normal /etc/portage directory does.
You'll also need to update the kernel.config file that is used to build the GNAP kernel. To do this create a bash script as follows:
| Code: | #!/bin/bash
cp -f /tmp/gnap/kernel.config /usr/src/linux/.config
cd /usr/src/linux
make menuconfig
cp -f /usr/src/linux/.config /tmp/gnap/kernel.config
|
once you run that you can then configure your kernel with the parts you need for your wireless setup / chipset support etc. Be careful what you remove tho, cos GNAP requires some parts to be left in there. Things for the file systems spring to mind.
 The above scripts assumes you are running hardened-sources on your development server as this is what will be used on the gnap system. If you are not currently running hardened-sources then please edit the /tmp/gnap/kernel.config file by hand!
To the build the thing you need to add an -e option to gnap_make i.e something like this should do the trick:
| Code: | | # gnap_make -e /tmp/gnap -t all |
Oh, you'll also need to edit the /tmp/gnap/common.conf file as this is incorrect for the latest version of catalyst. You need to change the following:
| Code: | | CATALYST_NAME='catalyst2' |
to become:
| Code: | | CATALYST_NAME='catalyst' |
EDIT: and I had to also change the following to as I was having problems with the hardened toolchain and uclibc
| Code: | | PROFILE="uclibc/x86/hardened" |
Was changed to:
| Code: | | PROFILE="uclibc/x86/" |
Once you do that, you should be able to re-build your gnap setup.
Optional: You may want to remove your existing /var/tmp/catalyst/ directory as its from the old catalyst build. Don't worry, Catalyst and Gnap re-create the contents of this directory as required. |
|
| Back to top |
|
|
|
Gentoo on Alternative Architectures
