Problem with "make" command in Gentoo

Aenima427 · 03-23-2006, 05:49 AM

jomen, thank you for the tip on using make menuconfig. That made it MUCH easier =). Unfortunately, I had already downloaded all the files emerge needed before I read your post about wget and the emerge to file options.

So, now there's a new problem. Emerge wants ndiswrapper-1.2, but my card isn't supported until ndiswrapper-1.6 (they're up to 1.11 beta now). I thought it was because I needed to update portage, so I downloaded the current version, ran
tar -xvzf /path -C /usr then emerge regen. When that was finished running I tried to emerge ndiswrapper again, but it still wanted v.1.2.

I tried running make in the ndiswrapper-1.10 dir, and got the same errors as before. I copied all of my kernel source files to /lib/modules/2.6.15-gentoo-r5/build. No change. Then I looked through all the Makefile code in ndiswrapper and subdirectories to see if there was a KSRC variable I could change, but there wasn't.

What am I missing? I think I've recompiled my kernel (even though I'm not sure yet how to configure GRUB to boot it, need to do more research), I have a .config file and a system.map file now.

jomen · 03-23-2006, 10:38 AM

First:
you need to be running the kernel you just made for all this to work...
There is lots of info on how to set up grub to boot your new kernel -
-add it to the file /boot/grub/grub.conf - take the line already there as a reference...

Quote:

I tried running make in the ndiswrapper-1.10 dir, and got the same errors as before.

What error did you get?

If you really need the newer version - you need to "unmask" the package net-wireless/ndiswrapper
by giving this command (for example - you can as well copy and paste it to this file...:
echo "net-wireless/ndiswrapper" >> /etc/portage/package.keywords (if it is masked by "keyword")
echo "net-wireless/ndiswrapper" >> /etc/portage/package.unmask (if it is hard-masked )
man portage for more info.

It could happen that it still will not work - because ndiswrapper might (I didn't check...) need other masked packages as a dependency - do the same with them:
echo "some_package" >> /etc/portage/package.keywords

Aenima427 · 03-24-2006, 02:55 AM

Ok, I found an ebuild for ndiswrapper-1.9 on http://gentoo-portage.com/net-wireless/ndiswrapper/Dep

along with instructions on how to manually apply an ebuild on gentoo.org. I added ACCEPT_KEYWORDS="~x86" to /etc/make.conf
This is what happened:

Code:

 
localhost portage # ebuild /ndiswrapper-1.9.ebuild fetch

Traceback (most recent call last):
  File "/usr/bin/ebuild", line 48, in ?
    portage_ebuild = portage.portdb.findname(cpv)
  File "/usr/lib/portage/pym/portage.py", line 5227, in findname
    return self.findname2(mycpv)[0]
  File "/usr/lib/portage/pym/portage.py", line 5235, in findname2
    psplit=pkgsplit(mysplit[1])
IndexError: list index out of range

I have no idea what this means, and it wasn't mentioned in any of the man pages that I checked. If anyone can tell me what this means exactly, and how I can fix it, I would appreciate it. Thanks.

Edit: quotes around ~x86

jomen · 03-24-2006, 04:34 AM

Quote:

I added ACCEPT_KEYWORDS="~x86"

No!
Don't do this! This will make your _entire_ system make use testing packages and very likely lead to problems you are not ready to solve!
Do it as I suggested - then only the _one_ file you really need from testing/unstable branch is allowed but the rest of the system stays untouched.
use /etc/portage/package.keywords for what you want to do!

BTW: you already have this ebuild in your portage-tree!

No need to fetch is separately from somewhere!

Run: emerge --sync regularily - or at least before you want to build something new.
And pay attention to the messages at the end - when it finishes - sometimes it reminds you to something like:
An update to portage is available! It is highly recommended that you update portage now - before updating any other packages on your system.
Do that and you will stay out of trouble!

Aenima427 · 03-24-2006, 05:12 AM

It was masked by keyword, as you said. I will go back and remove the variable in make.conf. I don't need any more problems than I already have lol.

But, on the bright side, it worked! ndiswrapper sees my card and driver. Of course, now there are more problems. I have still been booting my older kernel, which does not have wireless_radio set. I set grub to boot my new kernel (keeping the old one as a menu choice, of course) but during boot sequence, a "Kernel Panic" error occurs and my system locks up. Maybe I don't have grub.conf configured right. Probably I made a mistake during make menuconfig.

Grub.conf looks like this (actually, this is menu.lst):

Code:

GNU nano 1.3.9              File: menu.lst

default 0
timeout 30
splashimage=(hd0,2)/grub/splash.xpm.gz
title=Gentoo Linux
root (hd0,2)
kernel /kernel-genkernel-x86-2.6.15-gentoo-r5 root=/dev/ram0 init=/linuxrc ramd$ 
initrd /initramfs-genkernel-x86-2.6.15-gentoo-r5

title=Gentoo New Kernel
root (hd0,2)
kernel /vmlinuz-2.6.15-gentoo-r5 root=/dev/ram0 init=/linuxrc ramd$


title=Windows XP
rootnoverify (hd0,0)
makeactive
chainloader +1

If it is a problem in the config, I will probably just reinstall Gentoo to clean up the mess, since I haven't done much that's been productive and I have files copied everywhere. I have learned alot though, in a large part due to this forum, and I should be able to get my system to the point it's at now in no time.

jomen · 03-24-2006, 05:33 AM

No - again...

No need to reinstall just because of a missing line in the bootloaders configuration - a reinstall would leave you with exactly the same and more work to do...

It seems you used genkernel - and you missed to give the initrd - like the one you have for the old kernel.
Find the initrd - copy it to /boot (where the other already is) and add the line to the grub-configuration-file.

Code:

title=Gentoo New Kernel
root (hd0,2)
kernel /vmlinuz-2.6.15-gentoo-r5 root=/dev/ram0 init=/linuxrc ramd$
initrd /initrd_which_is_missing_now

You can well do without an initrd - just need to compile the drivers for your / filesystem - as well as those for your chipset and disk into the kernel -rather than as modules.

Then the line would look like this:

kernel /vmlinuz-2.6.15-gentoo-r5 root=/dev/hdaX --> X being where / (not /boot) is

Aenima427 · 03-25-2006, 10:16 PM

Once again, thanks for all your help jomen

. Since everything seems to be working, except for the new kernel (which I am almost positive I configured wrong in the first place), I am planning to recompile using gentoo-sources, and try to make the most basic, working kernel I can. Once I have it running, I'll tweak it and play around with it as I learn more.

I was hoping to have gentoo online before spring break was over...just over a day left!

Aenima427 · 04-02-2006, 12:41 AM

Thanks to everyone who helped out. I ended up just installing SuSE, and had my wireless connection going in a couple hours. BTW, SuSE is incredibly easy to install...almost too easy. I'll be going back to Gentoo (maybe try Slackware first) once I enjoy some Linux internet