Gentoo!

Originally posted by burns
Your a genius!!! Booting as I type:D:D:D
I slap you with a wet fish
haddock.gif
and I'm not talking single hand here, I'm talking double handed swing. It's just that I don't have a smilly for that.

Originally posted by riven
looks good.

not sure why 4K stacks would be a problem. ive never had any trouble.
The issue I had was that it boots but a lot of stuff like runscript, scripts in general wouldn't work.
 
I hate to be a pain, but I'm still getting a few errors on startup:
Code:
Bringing up eth0 (192.168.1.104)
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device

Error: Problem starting need services.
	Netmount was not started
Thanks so much for your help so far everybody:D. I deserved the fish:(.
 
Back to the kernel make sure you've compiled in your NIC

edit: are you using the "RealTek RTL-8139 PCI Fast Ethernet Adapter"?

edit2: you don't need to reboot back off the cd and chroot back in anymore since you've got a semi working system, you can just go straight into /usr/src/linux and do a make menuconfig
 
Last edited:
Originally posted by Mpemba Effect
Back to the kernel make sure you've compiled in your NIC
edit: are you using the "RealTek RTL-8139 PCI Fast Ethernet Adapter"?
Yeah thats the one. When I compile a new kernel, do I do it as I did before, then just restart?
//edit, do I need to recompile if I've already got support for the realtec in there?
 
Last edited:
Originally posted by burns
Yeah thats the one. When I compile a new kernel, do I do it as I did before, then just restart?

you say compiling took you an hour?

compile it as a module

go to help which will tell you what the module will be called

write it down

save your config

# make modules
# make modules_install

then
nano -w /etc/modules.autoload.d/kernel-2.6

add the module name into there and save.

then

# lsmod <module name>

# /etc/init.d/net.eth0 restart
 
Damn, no I'm not, I'm thinking of this computer. The linux one has an Origo PCI one in it. I think it's a Davicom chipset.
 
Originally posted by burns
Damn, no I'm not, I'm thinking of this computer. The linux one has an Origo PCI one in it. I think it's a Davicom chipset.
If you're unsure, you can always boot up the livecd which detected the card and do a "lsmod", it will tell you want drivers are loaded :)
 
Originally posted by Mpemba Effect
If you're unsure, you can always boot up the livecd which detected the card and do a "lsmod", it will tell you want drivers are loaded :)

tis a good plan, and then boot back into linux and do what i said! modules are the best option for you with such and old pc.
 
Sorry, I've got another one. I've got my grub.conf sorted out, and I used
Code:
emerge --usepkg gnome
to unpack Gnome from the packages CD. That seemed to go okay, but it did say at the end that one of my config files in /etc needed updating, but didn't identify which one. I don't really see what I can do about that, but if anyone knows what it's on about and can help that would be great.

Well I have linux appearing to work properly without the liveCD now, and as said Gnome is supposedly there, but when I select the Gentoo option in Grub, I end up in Linux, logged in as root, and it doesn't load Gnome automatically as I was expecting. As much as I've enjoyed the hours and hours and hours of fun learning that I've been suffe...er...experiencing, there's time for me to get better and do funky Gentoo-type CLI things later, but for now I'd just like to be able to have a relatively simple desktop on the machine in question. :(

How should I proceed please? :)
 
found it.

Device Drivers > Networking support > Ethernet (10 or 100Mbit) > Tulip family network device support >

now select yes for the:

"Tulip" family network device support

and yes for

Davicom DM910x/DM980x support (NEW)

then save your config and recompile the kernel with

# make && make modules modules_install

then copy the create image to /boot (remember to mount it first) and give it the same name as the current one you have, then reboot.

unfortunately you will have to recompile the whole kernel because the Tulip bit cant be a module
 
Back
Top Bottom