Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problems with System Boot.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Duplicate Threads
View previous topic :: View next topic  
Author Message
neilkfox
n00b
n00b


Joined: 19 Apr 2004
Posts: 11

PostPosted: Sat Apr 24, 2004 4:34 pm    Post subject: Problems with System Boot. Reply with quote

I have just installed the Gentoo OS on my machine.

All seemed well until my first boot after install.

I get the GRUB screen up with Gentoo Linux 2.4 and I hit enter.

I then see it loading drivers for different things, CD Rom HDD etcetc, then all of a sudden I get a number of lines stating

attempt to access beyond end of device
01:00 rw=0 want=4105 limit=4096

etc
etc
etc

It then comes up with a /# prompt

I can use ls but I don't seem to be able to do anything else.

Can anyone give me a hand or let me know what I have done wrong.

Thanks in advance

Neil
Back to top
View user's profile Send private message
sapphirecat
Guru
Guru


Joined: 15 Jan 2003
Posts: 376

PostPosted: Sat Apr 24, 2004 4:38 pm    Post subject: Reply with quote

Just a guess, but it sounds like you're running across bug 47450? Keep us posted...
_________________
Former Gentoo user; switched to Kubuntu 7.04 when I got sick of waiting on gcc. Chance of thread necro if you reply now approaching 100%...
Back to top
View user's profile Send private message
ddeacon
n00b
n00b


Joined: 23 Apr 2004
Posts: 22

PostPosted: Sat Apr 24, 2004 5:05 pm    Post subject: Reply with quote

So, if we ran into this, how do we adjust the size of the ramdisk?

I can't even launch any editors to edit files and adjust the size (if I could find where to adjust). I'm a bit a bit new at this.


Thanks,
Don.
Back to top
View user's profile Send private message
sapphirecat
Guru
Guru


Joined: 15 Jan 2003
Posts: 376

PostPosted: Sat Apr 24, 2004 5:50 pm    Post subject: Reply with quote

You should be able to reboot with the install CD, mount your /boot partition somewhere, and run nano. Roughly:
Quote:
mkdir /mnt/boot
mount -t ext3 /dev/hda2 /mnt/boot
nano /mnt/boot/grub/grub.conf

Change the bits in blue as necessary. grub.conf might be menu.lst too; that's changed at least once.
_________________
Former Gentoo user; switched to Kubuntu 7.04 when I got sick of waiting on gcc. Chance of thread necro if you reply now approaching 100%...
Back to top
View user's profile Send private message
b060
n00b
n00b


Joined: 24 Apr 2004
Posts: 70
Location: Mexico formerly known as Tenochtitlan

PostPosted: Sat Apr 24, 2004 7:16 pm    Post subject: Reply with quote

I wonder if you wrote properly
Code:
/etc/fstab

Why dont you try lilo and once you have a runing system then you try all over again to get the grub running
_________________
It's OK to be ignorant; it's not OK to play stupid but its your choice anyway
Back to top
View user's profile Send private message
neilkfox
n00b
n00b


Joined: 19 Apr 2004
Posts: 11

PostPosted: Sat Apr 24, 2004 7:42 pm    Post subject: Reply with quote

Thank you all for your comments and help. It was indeed bug 47450.

I changed the RAMDISK to 8000 and the system booted up fine.

Thanks again

Neil
Back to top
View user's profile Send private message
ddeacon
n00b
n00b


Joined: 23 Apr 2004
Posts: 22

PostPosted: Sun Apr 25, 2004 1:28 pm    Post subject: Reply with quote

I wasn't able to ever get around these errors by setting the ramdisk to 8000 thought I did by eliminating the ramdisk altogether. This leads me to two questions:

1) My configuration in grub.conf was:
kernel /boot/kernel-2.4.24 root=/dev/ram0 init=/linuxrc real_root=/dev/hda3
initrd /boot/initrd-2.4.24
ramdisk=8000

Is there anything wrong with this? I was still getting the error that it was trying to write past 4096 so I don't think the ramdisk size was getting put in right.

2) I ended up just making the grub.conf similar to the manual config instructions:
kernel /boot/kernel-2.4.24 root=/dev/hda3

getting rid of the whole initrd and ramdisk stuff.

I was able to at least boot now but is this liable to cause problems? I'm not sure what initrd does so I don't know the consequences of omitting it.

Thanks,
Don.
Back to top
View user's profile Send private message
sapphirecat
Guru
Guru


Joined: 15 Jan 2003
Posts: 376

PostPosted: Sun Apr 25, 2004 3:27 pm    Post subject: Reply with quote

ddeacon wrote:
1) My configuration in grub.conf was:
kernel /boot/kernel-2.4.24 root=/dev/ram0 init=/linuxrc real_root=/dev/hda3
initrd /boot/initrd-2.4.24
ramdisk=8000

Is there anything wrong with this? I was still getting the error that it was trying to write past 4096 so I don't think the ramdisk size was getting put in right.

The bug says it was added to the kernel parameter line, so I think the right way is these two lines:
Code:
kernel /boot/kernel-2.4.24 root=/dev/ram0 init=/linuxrc ramdisk=8000
initrd /boot/initrd-2.4.24

Quote:
I was able to at least boot now but is this liable to cause problems? I'm not sure what initrd does so I don't know the consequences of omitting it.

Well, if it boots successfully, it's fine for your particular scenario. AFAIK, the initrd contains copies of some drivers that might be needed to use the hard drive and stuff; once the root partition gets mounted, it can use modules in /lib/modules/(version) instead.

You might want to try manually configuring the kernel in the future, in case changes to genkernel change the need for a ramdisk. Keep a copy of your current kernel available in case you goof something up...
_________________
Former Gentoo user; switched to Kubuntu 7.04 when I got sick of waiting on gcc. Chance of thread necro if you reply now approaching 100%...
Back to top
View user's profile Send private message
ddeacon
n00b
n00b


Joined: 23 Apr 2004
Posts: 22

PostPosted: Mon Apr 26, 2004 4:50 pm    Post subject: Reply with quote

Thanks...putting the ramdisk part on the line ith the kernel did the trick...
Back to top
View user's profile Send private message
jaspersteller
n00b
n00b


Joined: 07 May 2004
Posts: 2

PostPosted: Fri May 07, 2004 7:21 am    Post subject: cant access tty job control turned off Reply with quote

ok i know what i got to do is add the ram disk 8000 onto my file but i need help mounting the drives im a noob at this so any help will be greatly appreciated im running 2.4.25 kernel and stage 3 x86 tarbal i just need to know the commands to load the drive and the path for nano to get to the grub.conf fie thanks guys
Back to top
View user's profile Send private message
trevor
n00b
n00b


Joined: 08 May 2004
Posts: 27
Location: /home/trevor

PostPosted: Sat May 08, 2004 2:42 pm    Post subject: Re: cant access tty job control turned off Reply with quote

jaspersteller wrote:
i just need to know the commands to load the drive and the path for nano to get to the grub.conf fie thanks guys


Code:
# mount /dev/hda3 /mnt/gentoo
# mount /dev/hda1 /mnt/gentoo/boot
# nano -w /mnt/gentoo/boot/grub/grub.conf


This is my first time helping somebody, so tell me how I did and the reults.
Back to top
View user's profile Send private message
pyromjm
n00b
n00b


Joined: 12 May 2004
Posts: 1

PostPosted: Wed May 12, 2004 10:44 am    Post subject: Reply with quote

Go to this link https://forums.gentoo.org/viewtopic.php?t=122656 and scroll down to where it says "Where is my grub.conf? "
-Pyromjm
Back to top
View user's profile Send private message
tomk
Bodhisattva
Bodhisattva


Joined: 23 Sep 2003
Posts: 7221
Location: Sat in front of my computer

PostPosted: Tue Jun 29, 2004 12:58 pm    Post subject: Reply with quote

Moved to Duplicate Threads, please see this topic:

https://forums.gentoo.org/viewtopic.php?t=152855

as well as those mentioned above.
_________________
Search | Read | Answer | Report | Strip
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Duplicate Threads All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum