Gentoo!

paradigm · 5 Aug 2004 at 17:11

Originally posted by riven
are you hostnames set up ok?

paradigm did you compile it as a module? because that will need autoloading.

are you connecting to the right network?

linux defaults to 192.168.1.*

windows defaults to 192.168.0.*

My routers default is 192168.1.x anyway, as for wether i compiled it as a module :confused:

I just followed the handbook pretty much word for word there, but e1000.o is a line in /etc/modules.autoload.d/kernel-2.6

As for mpemba, nah im not giving up yet!

burns · 5 Aug 2004 at 17:11

Code:
Originally posted by Mpemba Effect
it's

Code:

cp arch/i386/boot/bzImage /boot/kernel-2.6.7-gentoo-r11

It's also a good idea to backup the old kernel since you know it works to some extent.

Sorry thats what I meant, I was reading off the handbook, but I did put 2.6.7 as I can see it in /boot. So the old one hasn't been backed up, but it's running the same as before, still giving the errors.

riven · 5 Aug 2004 at 17:12

Originally posted by paradigm
My routers default is 192168.1.x anyway, as for wether i compiled it as a module I just followed the handbook pretty much word for word there, but e1000.o is a line in /etc/modules.autoload.d/kernel-2.6

As for mpemba, nah im not giving up yet!

dont think you want that .o there

Mpemba Effect · 5 Aug 2004 at 17:14

Originally posted by burns
Sorry thats what I meant, I was reading off the handbook, but I did put 2.6.7 as I can see it in /boot. So the old one hasn't been backed up, but it's running the same as before, still giving the errors.

OK, now are you using DHCP? OR have you setup statics?

edit: forget what I just said, I'm just talking rubbish

You still getting this full error?

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

Did you compile the driver in or as a module?

burns · 5 Aug 2004 at 17:19

Yeah still getting the full error with the driver compiled in.

paradigm · 5 Aug 2004 at 17:21

thank you riven, it was the .o causing it.

Woo, working system!

Now, how do i go about setting up x and kde as my window manager?

riven · 5 Aug 2004 at 17:24

Originally posted by paradigm
thank you riven, it was the .o causing it.

Woo, working system!

Now, how do i go about setting up x and kde as my window manager?

cool

you RTFM

http://www.gentoo.org/doc/en/desktop.xml

Mpemba Effect · 5 Aug 2004 at 17:28

ok burns type

Code:

dmesg > /tmp/dmesg
lsmod > /tmp/lsmod

Reboot onto the livecd setup the net connection then type

Code:

dmesg > /tmp/dmesg.cd
lsmod > /tmp/lsmod.cd

Now since you can't send these by email or upload them you're going to need to save these 4 files to a floppy disk and email or upload them from elsewhere. Do this by putting in a floppy disk with enough space

Code:

mount /dev/fd0 /mnt/floppy
cp /tmp/lsmod.cd /mnt/floppy
cp /tmp/dmesg.cd /mnt/floppy
mount /dev/hda3 /mnt/gentoo
cp /mnt/gentoo/tmp/dmesg /mnt/floppy
cp /mnt/gentoo/tmp/lsmod /mnt/floppy
umount /mnt/floppy

burns · 5 Aug 2004 at 17:45

you want me to paste those into here? I still don't have any hosting working...

riven · 5 Aug 2004 at 18:14

Originally posted by burns
you want me to paste those into here? I still don't have any hosting working...

probably be easiest to email them to me and mpemba, because the dmesg's are going to be rather large!

Deadly Ferret · 5 Aug 2004 at 18:38

Originally posted by riven
# rc-update add xdm default
# nano -w /etc/rc.conf

at the bottom change it to:

DISPLAYMANAGER="gdm"
XSESSION="Gnome"

now when you boot it should boot to the gnome login

Thanks. I've done the above, but instead of going to Gnome, it goes to what I presume is X Windows. There is at first a login prompt which says "welcome to localhost", with a black & white zig-zag background. It will allow me to login as root, but not as my normal user. When I do login, it then gives me a CLI window called Xterm, and something called xsm which has four things in it: client list, session log, checkpoint, shutdown.

I've gone through the page on gentoo.org that M.E. linked to, and following its advice I logged in as my normal user (this is early on when I have an opportunity to login as root for maintenance; I then changeover to the normal user) and try to give the command

Code:

echo "exec gnome-session" > ~/.xinitrc

so that I can then just enter startx to bring up Gnome, but after the bit in code tags, bash says no such file or directory in /home/james/.xinitrc :confused:

Any ideas please?

riven · 5 Aug 2004 at 18:47

Code:
Originally posted by Deadly Ferret
Thanks. I've done the above, but instead of going to Gnome, it goes to what I presume is X Windows. There is at first a login prompt which says "welcome to localhost", with a black & white zig-zag background. It will allow me to login as root, but not as my normal user. When I do login, it then gives me a CLI window called Xterm, and something called xsm which has four things in it: client list, session log, checkpoint, shutdown.

I've gone through the page on gentoo.org that M.E. linked to, and following its advice I logged in as my normal user (this is early on when I have an opportunity to login as root for maintenance; I then changeover to the normal user) and try to give the command

Code:

echo "exec gnome-session" > ~/.xinitrc

so that I can then just enter startx to bring up Gnome, but after the bit in code tags, bash says no such file or directory in /home/james/.xinitrc

Any ideas please?

you did change the DISPLAYMANGER and XSESSION, not just add them at the bottom right?

DISPLAYMANGER is about halfway up the file.

it sounds like gnome just isnt there though. you have emerged it right? and arent assuming its already there like other distros.

riven · 5 Aug 2004 at 18:52

Originally posted by riven
probably be easiest to email them to me and mpemba, because the dmesg's are going to be rather large!

hmmm all i can really read out of it is that on your install no NIC is loaded and no modules are loaded.

just try doing

# modprobe tulip
# modprobe dmfe
# lsmod

post all of it including the commands.

i just want to check if its using modules on your kernel or not

mpemba might be able to read more into it though

Mpemba Effect · 5 Aug 2004 at 18:53

Are you typing

Code:

echo "exec gnome-session" > ~/.xinitrc

as root user or a normal user. If you did that as root the .xinitrc file is created in /root. You need to do that as a normal user.

burns · 5 Aug 2004 at 19:01

Code:

#modprobe tulip
FATAL: Module tulip not found
#modprobe dmfe
FATAL: Module dmfe not found
#lsmod
module     size     used by

I didn't think it was possible to load the davicom bit as a module and it had to be compiled in the kernel?

Deadly Ferret · 5 Aug 2004 at 19:03

Thanks.

Originally posted by riven
you did change the DISPLAYMANGER and XSESSION, not just add them at the bottom right?

DISPLAYMANGER is about halfway up the file.

it sounds like gnome just isnt there though. you have emerged it right? and arent assuming its already there like other distros.

Yes, I located the two in there and changed the existing settings for them, without adding anything else.

I definitely emerged Gnome yesterday, but beyond that it's just a blur really, and I can't remember what else I did once it had emerged.

Code:
Originally posted by Mpemba Effect
Are you typing

Code:

echo "exec gnome-session" > ~/.xinitrc

as root user or a normal user. If you did that as root the .xinitrc file is created in /root. You need to do that as a normal user.

Aye, it was as a normal user: james. I did accidentally do it as root at first though, and it said something. I can't remember what, but it made me realize my mistake, and so I then logged in as james and tried it again. Could that be why it doesn't work as a normal user now?

riven · 5 Aug 2004 at 19:04

Code:
Originally posted by burns

Code:

#modprobe tulip FATAL: Module tulip not found #modprobe dmfe FATAL: Module dmfe not found #lsmod module size used by

I didn't think it was possible to load the davicom bit as a module and it had to be compiled in the kernel?

i was just checking it was compiled in and hadnt made a module.

riven · 5 Aug 2004 at 19:08

Originally posted by Deadly Ferret
Thanks.

Yes, I located the two in there and changed the existing settings for them, without adding anything else.

I definitely emerged Gnome yesterday, but beyond that it's just a blur really, and I can't remember what else I did once it had emerged.

Aye, it was as a normal user: james. I did accidentally do it as root at first though, and it said something. I can't remember what, but it made me realize my mistake, and so I then logged in as james and tried it again. Could that be why it doesn't work as a normal user now?

if you
# emerge gentoolkit

then
# qpkg -I -v

you can see all installed packages

riven · 5 Aug 2004 at 19:10

haha, i made hitman due to the insane size of this thread

Mpemba Effect · 5 Aug 2004 at 19:29

Deadly, just edit the .xinitrc file by hand it's in /home/james. You'll need to type "ls -A" to see it as it's a hidden file.

burns, you'll need to double check that you have compiled the driver in. Before doing "make" do

Code:

cp .config /tmp
make mrproper
cp /tmp.config /usr/src
make menuconfig
# save and exit
make
# or make && make modules modules_install if you're using any modules