The handbook suggests that emerge e1000 will install a driver for the Intel e1000 Gigabit Ethernet Adapter. Apparently the e1000 does not work on kernel 2.6 yet, so the compile fails. Two suggestions: 1) Update the handbook to point to a list of hardware that is supported on a given kernel, such as 2.6. 2) Update the emerge process to allow a driver build to fail gracefully if it does not support the kernel in question. Since this may not be just a problem with the e1000 driver, perhaps it should be addressed as an emerge/ebuild bug.
which one failed ? e1000-5.2.30.1.ebuild e1000-5.2.39.ebuild
net-misc/e1000-5.2.30.1 failed The symptoms seem the same as for bug 33805, problems with NR_IRQ* cause compiler errors.
OK. emerge e1000 works _AFTER_ the system is built. Step 7e in the handbook is a little premature in recommending that emerge e1000 be done at that point (prior to actually running on 2.6). I was able to run emerge e1000 without error after getting the new 2.6 system booted.
could i close this bug then ?
I still think a comment in the handbook regarding doing ebuilds in the livecd environment would save alot of people alot of time and grief. Maybe you could make a fix to Step 7e (Installing Separate Kernel Modules) or get someone else to look at it? A simple note to the effect that if you are building a kernel 2.6 from the livecd (if it isn't also 2.6) you should defer the ebuild of the listed subsystems until after rebooting with the newly built system. It would also be helpful to remind these users to do the ebuild later, around Step 11b in the handbook. With all the other 2.6 notes in the handbook, I was disappointed that something so obvious was not pointed out at Step 7e.
reassiging for handbook change
I've added a paragraph in the beginning of the installation instructions to inform the user that, if he wants to install a 2.6-based system, he should choose the "smp" kernel, the "gentoo" kernel otherwise.
