View previous topic :: View next topic |
Author |
Message |
idella4 Retired Dev
Joined: 09 Jun 2006 Posts: 1600 Location: Australia, Perth
|
Posted: Tue Jul 15, 2008 6:17 am Post subject: boot up on new kernel and hardware stalls[SOLVED] |
|
|
hi all.
This is actually and old installation but the nature of the problem is appropriate to a new install/
I last booted it up ok about 6 months ago, then I started recently to update it. I ran into a queue of dependency issues that simply didn't happen two years ago. It was my USE flags. I had heaps of them and they created circular dependencies. I got rid of enough to clear them, but initially I unmerged a few packaged attempting to remove blocks. Now I can't tell whether that's the root of the problem or not. Who knows.
I've just implanted the new source kernel and compiled and put the kernel in place in boot in the same way as always. My oldish genny can't complete boot up. It stops at that dreaded point of switching to root. Curiously the error reports it's looking for an nfs server which can't be found. Why an nfs server???
I'm rusty at this so can someone point me toward where I retrieve the log to start getting genny bootable again please? 'll take a quick look too. _________________ idella4@aus
Last edited by idella4 on Fri Jul 18, 2008 4:59 am; edited 2 times in total |
|
Back to top |
|
|
d2_racing Bodhisattva
Joined: 25 Apr 2005 Posts: 13047 Location: Ste-Foy,Canada
|
Posted: Tue Jul 15, 2008 11:29 am Post subject: |
|
|
Hi, what was your old kernel ? Also, maybe you have switched from and old ATAPI section to the new SATA-PATA section.
Can you post your lspci plz ? |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Tue Jul 15, 2008 3:39 pm Post subject: |
|
|
Please post the actual error message that you are receiving. That will help us figure out if it is failing because you don't have the appropriate SATA/PATA support, or if it is for some other reason. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
cyrillic Watchman
Joined: 19 Feb 2003 Posts: 7313 Location: Groton, Massachusetts USA
|
Posted: Tue Jul 15, 2008 7:28 pm Post subject: Re: boot up on new kernel and hardware stalls |
|
|
idella4 wrote: | Curiously the error reports it's looking for an nfs server which can't be found. Why an nfs server??? |
Take a look at this thread : Kernel panic: Does not like my harddrive or partitions |
|
Back to top |
|
|
idella4 Retired Dev
Joined: 09 Jun 2006 Posts: 1600 Location: Australia, Perth
|
Posted: Wed Jul 16, 2008 4:05 am Post subject: |
|
|
Tx for some answers.
the lspci
Quote: | 00:00.0 Host bridge: nVidia Corporation Unknown device 07c3 (rev a2)
00:00.1 RAM memory: nVidia Corporation Unknown device 07cb (rev a2)
00:01.0 RAM memory: nVidia Corporation Unknown device 07cd (rev a1)
00:01.1 RAM memory: nVidia Corporation Unknown device 07ce (rev a1)
00:01.2 RAM memory: nVidia Corporation Unknown device 07cf (rev a1)
00:01.3 RAM memory: nVidia Corporation Unknown device 07d0 (rev a1)
00:01.4 RAM memory: nVidia Corporation Unknown device 07d1 (rev a1)
00:01.5 RAM memory: nVidia Corporation Unknown device 07d2 (rev a1)
00:01.6 RAM memory: nVidia Corporation Unknown device 07d3 (rev a1)
00:02.0 RAM memory: nVidia Corporation Unknown device 07d6 (rev a1)
00:03.0 ISA bridge: nVidia Corporation Unknown device 07d7 (rev a2)
00:03.1 SMBus: nVidia Corporation Unknown device 07d8 (rev a1)
00:03.2 RAM memory: nVidia Corporation Unknown device 07d9 (rev a1)
00:03.4 RAM memory: nVidia Corporation Unknown device 07c8 (rev a1)
00:04.0 USB Controller: nVidia Corporation Unknown device 07fe (rev a1)
00:04.1 USB Controller: nVidia Corporation Unknown device 056a (rev a1)
00:08.0 IDE interface: nVidia Corporation Unknown device 056c (rev a1)
00:09.0 Audio device: nVidia Corporation Unknown device 07fc (rev a1)
00:0a.0 PCI bridge: nVidia Corporation Unknown device 056d (rev a1)
00:0b.0 PCI bridge: nVidia Corporation Unknown device 056e (rev a1)
00:0c.0 PCI bridge: nVidia Corporation Unknown device 056f (rev a1)
00:0d.0 PCI bridge: nVidia Corporation Unknown device 056f (rev a1)
00:0e.0 IDE interface: nVidia Corporation Unknown device 07f0 (rev a2)
00:0f.0 Ethernet controller: nVidia Corporation Unknown device 07dc (rev a2)
00:10.0 VGA compatible controller: nVidia Corporation Unknown device 07e3 (rev a2)
01:06.0 Ethernet controller: Atheros Communications, Inc. AR5005G 802.11abg NIC (rev 01)
|
Let me add that I've just had to replace my motherboard, so this is all new hardware, but the same happened on the old one before it died. It appears that the hardware is probably irrelevant. I would think it's because of the package dependency issue and removing some packages.
I shall have to re-boot and note the error message with a pen. Be back and re-post.
Back
Quote: | Root-NFS: No server availabe, guving up.
VFS: Unable to mount root fs via NFS, trying floppy
VFS: Insert the root floppy and press ENTER |
Why on earth is it dealing with nfs?? It's supposed to mount the root file system where it's already been told where it is in the usual kernel arguement. _________________ idella4@aus |
|
Back to top |
|
|
idella4 Retired Dev
Joined: 09 Jun 2006 Posts: 1600 Location: Australia, Perth
|
Posted: Wed Jul 16, 2008 4:56 am Post subject: |
|
|
cyrillic you're a veteran. That looks like a match up.
Once having changed the settings, you need to recompile and generate a new kernel for boot, do you not? _________________ idella4@aus |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Wed Jul 16, 2008 5:09 am Post subject: |
|
|
idella4 wrote: | cyrillic you're a veteran. That looks like a match up.
Once having changed the settings, you need to recompile and generate a new kernel for boot, do you not? |
Yes, you will need to recompile the kernel and copy it over to the boot directory (make sure /boot is mounted before doing so). _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
idella4 Retired Dev
Joined: 09 Jun 2006 Posts: 1600 Location: Australia, Perth
|
Posted: Wed Jul 16, 2008 6:28 am Post subject: |
|
|
eh, It didn't work.
I adjusted the settings according to what you gave the other user. I honestly expected it would go in.
Should you not disable the root nfs setting as well in the .config?
kalos can you tell me how and why to mount /boot before doing so?
I never have and it's always worked ok. _________________ idella4@aus |
|
Back to top |
|
|
NathanZachary Moderator
Joined: 30 Jan 2007 Posts: 2605
|
Posted: Wed Jul 16, 2008 3:52 pm Post subject: |
|
|
Well, the default /etc/fstab has /boot set to noauto, which means that it is not automounted. For that reason, you would have to do:
before attempting to copy over a new kernel:
Code: |
cp arch/x86/boot/bzImage /boot/kernel-name-here
|
If you have removed the noauto option from /boot in your fstab though, you won't have to mount it manually. _________________ “Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio--- |
|
Back to top |
|
|
d2_racing Bodhisattva
Joined: 25 Apr 2005 Posts: 13047 Location: Ste-Foy,Canada
|
Posted: Wed Jul 16, 2008 3:55 pm Post subject: |
|
|
kalos wrote: | Well, the default /etc/fstab has /boot set to noauto, which means that it is not automounted. For that reason, you would have to do:
|
This is for security reason, if you mess up your Gentoo, you will not crash your grub MBR loader |
|
Back to top |
|
|
idella4 Retired Dev
Joined: 09 Jun 2006 Posts: 1600 Location: Australia, Perth
|
Posted: Thu Jul 17, 2008 3:15 am Post subject: |
|
|
ok thanks for that, but that was a minor add-on. What about the nfs block on bootup?? _________________ idella4@aus |
|
Back to top |
|
|
d2_racing Bodhisattva
Joined: 25 Apr 2005 Posts: 13047 Location: Ste-Foy,Canada
|
Posted: Thu Jul 17, 2008 11:13 am Post subject: |
|
|
Have you enable the NFS support inside your kernel, if yes, then disable it.
Also, are you sure that you have [*] for your system file, because something it happens when you don't have ext2 or ext3 support inside your kernel and you want to boot on a ext2 or ext3 partition. |
|
Back to top |
|
|
idella4 Retired Dev
Joined: 09 Jun 2006 Posts: 1600 Location: Australia, Perth
|
Posted: Fri Jul 18, 2008 2:05 am Post subject: |
|
|
Quote: |
Also, are you sure that you have [*] for your system file
|
d2 what does this mean? _________________ idella4@aus |
|
Back to top |
|
|
d2_racing Bodhisattva
Joined: 25 Apr 2005 Posts: 13047 Location: Ste-Foy,Canada
|
Posted: Fri Jul 18, 2008 2:13 am Post subject: |
|
|
Are you sure that you have selected the file system inside your kernel and not in module.
When you use make menuconfig, when you choose an option as a module it's has this : [M] and when it's inside the kernel you have this : [*] |
|
Back to top |
|
|
idella4 Retired Dev
Joined: 09 Jun 2006 Posts: 1600 Location: Australia, Perth
|
Posted: Fri Jul 18, 2008 3:34 am Post subject: |
|
|
Oh ok I get you now. Compile internally rather than a loadable module. Eh, I've disabled nfs, but what settings are you suggesting require the [*] setting?
This may be solved but I will do a re-boot and return soon. _________________ idella4@aus |
|
Back to top |
|
|
d2_racing Bodhisattva
Joined: 25 Apr 2005 Posts: 13047 Location: Ste-Foy,Canada
|
Posted: Fri Jul 18, 2008 3:39 am Post subject: |
|
|
I mean your partition type file system.
Exemple :
Code: |
/dev/sda8 on / type ext3 (rw,noatime)
|
Since I want to boot my box, I need to compile internally the EXT3 support, and if not I cannot boot at all. |
|
Back to top |
|
|
idella4 Retired Dev
Joined: 09 Jun 2006 Posts: 1600 Location: Australia, Perth
|
Posted: Fri Jul 18, 2008 4:59 am Post subject: |
|
|
ok Thanks. I have it sorted. It was kernel settings sure enough. It boots. _________________ idella4@aus |
|
Back to top |
|
|
d2_racing Bodhisattva
Joined: 25 Apr 2005 Posts: 13047 Location: Ste-Foy,Canada
|
Posted: Fri Jul 18, 2008 11:10 am Post subject: |
|
|
So, what did you change in your kernel in order to boot ? |
|
Back to top |
|
|
|