Right off the bat, I'd like to say, the install screen looks much better than the last 2 betas. But.... the network setup on the older cd's worked, on the new one, it doesn't on my system. Not quite sure what changed, or how to fix it, but it's definitely not working right anymore.

So far, I've not had complete success installing gentoo on this box. I have installed it on another x86 test box and it was running for a short while (had to give up the drive to another project) so now I don't have the config's I used to set that box up, not that anything would be exactly the same anyways.

Basically, is there a way to find out which files changed for autodetection of the modules/hardware and then modify the iso and insert the older file into the iso? Net-setup eth0 doesn't detect the nic on the new iso, but did on the older ones. It comes up with an error now, saying no network cards detected and starts lo but nothing else. I know the nic works, because I can boot off the older cd and the network comes right up._________________http://www.1and1.com/?k_id=16196755 click me for cheap linux based web hosting.

Last edited by d_adams on Sat Dec 20, 2003 2:49 pm; edited 1 time in total

Well, Neo not sure about exactly which file is used for the auto detection on the livecd, but if you have the space, you could use loop to mount each iso and save each to a folder in your home, then look for what is different. Then change and use mkisofs to remake the iso and burn it.

Make a mount point some where like /mnt/iso
mkdir /mnt/iso
Then
mount -o loop -t iso9660 iso_location_to_mountwhere_to_mount
like so:
mount -o loop -t iso9660 /home/decibels/KNOPPIX*.iso /mnt/iso

Then copy it some where like your home folder:
cp -Rv /mnt/iso/* /home/yourname/foldername

After you copy that one to your home folder you can umount the loop and mount the other cdiso on there. And do the same thing. Now you have two iso's extracted to you home folder.
Find the changes and correct the iso you want.

Then (think I got this right, haven't done mkisofs in awhile):
change directory to where you have the iso you want to make. So if have it in /home/Neo/customiso then

Had to use modprobe and the mfg listed (mine was bcm, for the broadcom nic) which then started eth0, so networking is a go. Kinda feel like a serious noob, but never had the autoloader fail before on hardware detection. Thanks for the pointers on the iso setup Mr. D, I'll give that a try later just to be messing around some.

IceDigger, try "modprobe via-rhine" and see if that gets you anything.
That's the only via module listed in /mnt/cdrom/lib/modules/2.6.0/kernel/drivers/net
If that doesn't work, look at the chipset on the card itself, look for Realtek, which is a common generic 10/100 chip. If that's there, try modprobe 8139cp or 8139too

After the modprobe command, do /sbin/ifconfig and it should output lo and eth0 parameters if it's working right._________________http://www.1and1.com/?k_id=16196755 click me for cheap linux based web hosting.

Anyone know why it isn't loading in 2.5.50? all my other modules work.

Naturally, this was a different kernel, but seems to be the same problem. I didn't dig too deep, but here's the link http://linux-kernel.skylab.org/lkml20021208 which is a year old problem it seems. Not sure what else to say on it at this point. Someone with a little more knowledge may step in on this one._________________http://www.1and1.com/?k_id=16196755 click me for cheap linux based web hosting.

Have you tried compiling it in the kernel rather than as module?
Some things work that way, I have had problems compiling the
tulip driver in kernel, works as module. Also, with Alsa stuff recently
had to play with a combo or ways (some modules others in kernel)
to get it to compile right.

I would be interested if works in the kernel. You'll get an error
about insmod 8139too at boot, but if works in kernel, just
remove it from either /etc/modules.autoload or /etc/modules.autoload.d/kernel-name_________________Support bacteria – they’re the only culture some people have.”

d_adams, can you try it. I don't have the luxury of having a Opteron system . If works we can tell him how to do it and/or send him the /usr/src/linux/.config file._________________Support bacteria – they’re the only culture some people have.”

No need to hit f2 on initial screen, just put in smp and it will load the smp kernel. After it boots, then do the modprobe. I always do passwd first (set root pw) switch to 2nd screen and log in, pull up the install text and switch back to f1 for the install. Currently on emerge system (took a short nap, I work nights) which should take a couple of hours._________________http://www.1and1.com/?k_id=16196755 click me for cheap linux based web hosting.

Just finished installing gentoo up until mozilla plus X and pekwm, the only problem i was having was nvidia driver it keeps on lock up. looks like i have to wait for another release or another good patch. I dont know why gkrellm is masked but it compiled and runs fine here.

_________________"You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, the Swiss hold the America's cup, France accusing the US of arrogance and Germany doesn't want to go to war."

The first x86-64 patchkit for the 2.6.0 linux kernel has been released. The patchkit
has fixes for many serious bugs (including data corruption iossues) on x86-64 that didn't make it
in official 2.6.0. Please don't bother reporting any 2.6 x86-64 problems to me if you didn't
apply the patchkit first.

Some of the issues fixed look pretty important. It looks like Linux on AMD64 won't be ready for primetime for a while yet, though the 32-bit versions seem to work fine.[/url]_________________The greatest deeds are still undone, the greatest songs are still unsung...

Ok, looks like people are using the forums. I'm the
amd64 project lead at this time, and I usually do not
check the forums. You all should join the gentoo-amd64
mailing list, or the #gentoo-amd64 IRC channel on irc.freenode.net

Anyhow, I released a 12/21/2003 livecd that fixes the issues with
the 12/17 livecd. There was just a lack of testing on my part.

Also, in reference to that last post, gentoo-dev-sources is the
kernel you need to/must use as it has the patches from
x86-64.org already.

Hope to see you all on some other form of communication. It's
simply too hard to parse out amd64 material from the forums,
since there is no specific amd64 group.

Also, you all can post bugs like these to bugs.gentoo.org, as
that's the main place I look to resolve issues.