Gentoo!

riven · 5 Aug 2004 at 21:39

Originally posted by burns
hmm, kernel panic: VFS: Unable to mount root fs on hda3
oh dear.

oh dear indeed. you did keep you old config then made changes to that right?

burns · 5 Aug 2004 at 21:41

Originally posted by riven
oh dear indeed. you did keep you old config then made changes to that right?

I'm thinking maybe I didn't. I guess I'll have to boot off the live CD and try again?

Mpemba Effect · 5 Aug 2004 at 21:43

Originally posted by burns
I'm thinking maybe I didn't. I guess I'll have to boot off the live CD and try again?

Correct. Always keep a backup of anything you change. Fortunately I copied your .config post earlier and it can be found here - http://forums.overclockers.co.uk/showthread.php?s=&postid=2980908#post2980908

riven · 5 Aug 2004 at 21:44

Originally posted by burns
I'm thinking maybe I didn't. I guess I'll have to boot off the live CD and try again?

looks like it.

you should have keep your 1st working kernel as a backup which you can boot back too incase something like this happens

Deadly Ferret · 5 Aug 2004 at 21:44

Originally posted by riven
have you checked that Gnome is in you X sessions folder as the gentoo docs say to check?

It says: Gnome Xsession. Sounds promising, I take it that means Gnome is properly emerged?

riven · 5 Aug 2004 at 21:50

scrap that it, gdm must be installed

you did do this right?

env-update && source /etc/profile

riven · 5 Aug 2004 at 22:01

if you still cant get gnome to work, then setting up your network card would be the best idea, then if you like, me or mpemba could ssh in and see if we can figure it out.

mpemba will probably be best if you do want to go that route because ive never used ssh, but im sure its simple and the man page is pretty good.

Deadly Ferret · 5 Aug 2004 at 22:10

Yep. Aside from xscreensaver, I precisely followed the guide.

Thanks for the offer, I'll try to setup networking tomorrow and with luck my mind shall not fail me. I haven't the mental energy to do it this evening. Going to chill out and watch the Sign Of Four, a Sherlock Holmes mystery, and enjoy a cognac & cigar. There are simple pleasures in life that rank much higher than all this computing guff.

PS: I have noticed that the guide says that the contents of /etc/X11/Sessions should be Xsession Gnome, but I get Gnome Xsession. Could them being the other way around have any meaning/impact whatsoever? I feel silly for asking, but if it did turn out to be the problem I'd feel even more silly if I hadn't mentioned it.

Mpemba Effect · 5 Aug 2004 at 22:19

Originally posted by Deadly Ferret
Yep. Aside from xscreensaver, I precisely followed the guide.

Thanks for the offer, I'll try to setup networking tomorrow and with luck my mind shall not fail me. I haven't the mental energy to do it this evening. Going to chill out and watch the Sign Of Four, a Sherlock Holmes mystery, and enjoy a cognac & cigar. There are simple pleasures in life that rank much higher than all this computing guff.

PS: I have noticed that the guide says that the contents of /etc/X11/Sessions should be Xsession Gnome, but I get Gnome Xsession. Could them being the other way around have any meaning/impact whatsoever? I feel silly for asking, but if it did turn out to be the problem I'd feel even more silly if I hadn't mentioned it.

Everyone needs a break after 2 days of cramming

You've done a mighty fine job so far mate

Mpemba Effect · 5 Aug 2004 at 22:21

To Burns

One thing to remember, the reason why your previous kernels all booted with the same lilo error is because you much run /sbin/lilo after each kernel recompile.

Deadly Ferret · 5 Aug 2004 at 22:33

Originally posted by Mpemba Effect
Everyone needs a break after 2 days of cramming You've done a mighty fine job so far mate

Thanks. I just had one last idea, and it might actually be relevant this time. I thought about that command I couldn't run properly when logged in as a normal user, and decided to try: gnome-session. It appears to be a valid command, but it returned this line (gnome-session:5027): Gtk-WARNING **: cannot open display: Does this give any clues?

riven · 5 Aug 2004 at 22:33

Originally posted by Deadly Ferret
Yep. Aside from xscreensaver, I precisely followed the guide.

Thanks for the offer, I'll try to setup networking tomorrow and with luck my mind shall not fail me. I haven't the mental energy to do it this evening. Going to chill out and watch the Sign Of Four, a Sherlock Holmes mystery, and enjoy a cognac & cigar. There are simple pleasures in life that rank much higher than all this computing guff.

PS: I have noticed that the guide says that the contents of /etc/X11/Sessions should be Xsession Gnome, but I get Gnome Xsession. Could them being the other way around have any meaning/impact whatsoever? I feel silly for asking, but if it did turn out to be the problem I'd feel even more silly if I hadn't mentioned it.

no, they are 2 files, they are just getting listed in a different order.

have a nice relaxing time. i shall be up bright and early again tomorrow

riven · 5 Aug 2004 at 22:34

Originally posted by Deadly Ferret
Thanks. I just had one last idea, and it might actually be relevant this time. I thought about that command I couldn't run properly when logged in as a normal user, and decided to try: gnome-session. It appears to be a valid command, but it returned this line (gnome-session:5027): Gtk-WARNING **: cannot open display: Does this give any clues?

nah, that just means you tried to run gnome without X started. x must start to initialize the displays, hence the error (gtk being the api used by gnome)

Deadly Ferret · 5 Aug 2004 at 22:37

Oh well, that's enough novice ideas from me. Catch you tomorrow, and thanks for today.

burns · 5 Aug 2004 at 23:30

I can't even get the kernel to copy into the boot partition now, I do cp arch/i386/boot/bzImage /boot/kernel-2.6.7-gentoo-r11 and it reruns cannot stat arch/i386/boot/bzImage: no such file or directory.

This is right after I just compiled the kernel, I don't get it. This is really stating to **** me off.

Mpemba Effect · 5 Aug 2004 at 23:39

use the full path

/usr/src/linux/arch/i386/boot/bzImage

burns · 6 Aug 2004 at 10:29

ok, now I mount boot and root,
copy the kernel to /boot/kernel-2.6.7-gentoo-r11,
do cd /boot
ls -l
and the kernel isn't there, it's still yesterday's one?

Mpemba Effect · 6 Aug 2004 at 10:32

Originally posted by burns
ok, now I mount boot and root,
copy the kernel to /boot/kernel-2.6.7-gentoo-r11,
do cd /boot
ls -l
and the kernel isn't there, it's still yesterday's one?

Code:

cd /boot
mv kernel-2.6.7-gentoo-r11 kernel-2.6.7-gentoo-r11.old
cp /usr/src/linux/arch/i386/boot/bzImage /boot/kernel-2.6.7-gentoo-r11

burns · 6 Aug 2004 at 10:35

cannot stat kernel-2.6.7-gentoo-r11 : No such file or directory
The same if I add /boot to the begining.
Should I have mounted hda1 to /boot after chrooting or somthing? It was the first thing I did once the live CD booted.

Damn, I had a typo, 3 days of linux is doing my head in.

burns · 6 Aug 2004 at 10:47

Hurrah! I have it booting with no error messages now, now to setup networking and check it is actually working...
Cheers for all your help and sticking with this through my dumb mistakes

//edit -bash: net-setup: command not found