On 6/23/05, A. Khattri <[EMAIL PROTECTED]> wrote:
> On Wed, 22 Jun 2005, Ryan Viljoen wrote:
>
> > Yes it is the current one assuming you save the .config file when
> > exiting.
>
> Except when starting with a fresh new kernel.
>
> What I do is copy a working .config over to the new kernel and r
Thank you all for the replies!!
I think this little experience improved my knowledge and I'm starting to see the kernel as something not so scary :)
Having said that.. I have to recompile it again.. can't manage to start
alsa (I didn't built it in the kernel as the HOWTO said to), and the
same wit
On Wed, 22 Jun 2005, Ryan Viljoen wrote:
> Yes it is the current one assuming you save the .config file when
> exiting.
Except when starting with a fresh new kernel.
What I do is copy a working .config over to the new kernel and run "make
oldconfig" before doing the usual "make menuconfig", etc.
Yes it is the current one assuming you save the .config file when
exiting. This is obviously required for the compilation of the kernel.
Glad to hear you got it working.
Cheers
Rav
On 6/22/05, Fernando Meira <[EMAIL PROTECTED]> wrote:
> Yep.. it was just a boot parameters issue!!
>
> Just had
Yep.. it was just a boot parameters issue!!
Just had to clean the ram disk stuff, and the initrd line, and everything went well!!
For a future recompilitation, when I do "make menuconfig" or "make
xconfig", the configuration showed is the current one or a default one?
Logically, I would say that
Ok you say you compiled the kernel manually, all you need to do is
include support for the VFS file system in your kernel preferably
built in rather than a module. That should do the job. As for the
options for your kernel you dont need all the ram disk stuff that
genkernel uses.
Yours can simply b
Ok, still unsolved!
I know that this can happen due to 2 reasons:
1) wrong boot parameters,
2) compiled fs as module.
I've been checking the first reason, and I couldn't solve through it...
I use grub, and the first time I compiled the kernel using genkernel.
Now I compiled it manually. The boot
I should have read this mail before I rebooted.. :P
I end up with a
VDF-fs: No partition found (1)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
I will need to use the livecd to fix the prob.. after I find what's going on...
On 6/22/05, Ryan Viljoen <[EMAIL PROT
> My problem is that I assume that the new configuration replaces the
> previous one. So, I would need to replace all files.
You dont need to replace your old kernel files you can simply copy
them over to /boot under a different name so use:
My previous kernel has:
/boot/kernel-2.6.11-gentoo-r10
On Wed, 22 Jun 2005 11:03:09 +, Fernando Meira wrote:
> I am also aware of the "make install" option, but I guess this way is
> faster (since it does not rebuilds the kernel).
make install will not rebuild the kernel if it does not need to. If the
kernel and modules are newer than the .config
Hi,
this might be a mighty stupid question, but I have no experience on recompiling kernel...
I followed the instructions from the HOWTO and now I have to copy the new configuration to /boot.
My problem is that I assume that the new configuration replaces the previous one. So, I would need to repl
11 matches
Mail list logo
