On Sun, Nov 8, 2009 at 08:45, Dale rdalek1...@gmail.com wrote:
daid kahl wrote:
I tried closely comparing the current working kernel with newly built
one. I mean side by side with `make menuconfig' running in both sources.
I cannot tell what it is I'm overlooking.
Please do not do this.
Daniel da Veiga wrote:
On Sun, Nov 8, 2009 at 08:45, Dale rdalek1...@gmail.com wrote:
daid kahl wrote:
Sounds like he may as well use that genkernel thingy that Gentoo has.
It never has worked for me but he may have better luck. It may even
work on the first try. LOL
I've
I tried closely comparing the current working kernel with newly built
one. I mean side by side with `make menuconfig' running in both sources.
I cannot tell what it is I'm overlooking.
Please do not do this. Instead emerge kccmp to compare kernel
configurations! It is much easier...trust
daid kahl wrote:
I tried closely comparing the current working kernel with newly built
one. I mean side by side with `make menuconfig' running in both sources.
I cannot tell what it is I'm overlooking.
Please do not do this. Instead emerge kccmp to compare kernel
configurations!
daid kahl daid...@gmail.com writes:
2009/11/4 Harry Putnam rea...@newsguy.com:
I'll say right from the start, that building a new kernel, has always
been a problem for me. I don't remember ever not having a problem, in
10+ yrs..
Many people here seem to find it completely easy... not me.
Graham Murray graham at gmurray.org.uk writes:
You have to copy the .config from the running (old)
kernel to the new kernel directory before running make oldconfig. If you
start with the default config, then you have to run make menuconfig (or
config or xconfig) to customise it every time.
John H. Moe john...@optusnet.com.au writes:
I stopped using that option in my systems, as there is now a AHCI SATA
option to use instead. It appears CONFIG_ATA_SFF (which CONFIG_ATA_PIIX
requires) is deprecated. From the help on it:
Do you notice some kind of difference from switching?
On 11/3/2009 11:10 PM, Harry Putnam wrote:
hamiltonhamil...@pobox.com writes:
Just checking - but you didn't mention: did you copy the .config to the
new kernel src directory? If not, that would certainly explain the
disparity in configuration settings you're seeing.
I think you can say
On 11/04/2009 06:16 AM, james wrote:
Graham Murray graham at gmurray.org.uk writes:
You have to copy the .config from the running (old)
kernel to the new kernel directory before running make oldconfig. If you
start with the default config, then you have to run make menuconfig (or
config or
Mike Edenfield kut...@kutulu.org writes:
The 'make' man page wouldn't know anything about the kernel's
makefile. You want the README file that's included in the top of the
kernel source folder. That file says, among other things:
make oldconfig Default all questions based on the contents
On 2009-11-04, Harry Putnam rea...@newsguy.com wrote:
Just checking - but you didn't mention: did you copy the
.config to the new kernel src directory? If not, that would
certainly explain the disparity in configuration settings
you're seeing.
I think you can say make `oldconfig' and the
Am Mittwoch 04 November 2009 02:46:54 schrieb Harry Putnam:
But am I missing some critical driver?
Harddisk (CONFIG_BLK_DEV_SD=y), maybe? That's one reason for unknown block
device.
Bye...
Dirk
signature.asc
Description: This is a digitally signed message part.
Am Mittwoch 04 November 2009 05:10:52 schrieb Harry Putnam:
I think you can say make `oldconfig' and the `old config' is supposed to
be incorporated so no I didn't
No, that's only half of the truth. You need to copy .config from your old
kernel first. I'd compile the config into the kernel,
Dirk Heinrichs dirk.heinri...@online.de writes:
If it still won't work, you can also post your kernel config and the output
of
lspci -vv here and somebody will find out what's wrong/missing.
Good input thanks. I did get it working. It was an IDE selection I
missed.
From the lspci -vv
Harry Putnam wrote:
I think you can say make `oldconfig' and the `old config' is supposed to
be incorporated so no I didn't
The 'oldconfig' option needs your old .config for input (that where
old comes from :-)
I usually manually go through the 'make menuconfig' as well after doing
this to
Harry Putnam wrote:
John H. Moe john...@optusnet.com.au writes:
I stopped using that option in my systems, as there is now a AHCI SATA
option to use instead. It appears CONFIG_ATA_SFF (which CONFIG_ATA_PIIX
requires) is deprecated. From the help on it:
Do you notice some kind of
Volker Armin Hemmann volkerar...@googlemail.com writes:
your drivers for the ide disks have to be built INTO THE KERNEL! NOT MODULES.
Is that really a hard rule? I've done it both ways successfully in the
past.
And in fact, I didn't record my first builds on this kernel but I'm
pretty sure my
On 11/03/2009 02:29 PM, Harry Putnam wrote:
I'll say right from the start, that building a new kernel, has always
been a problem for me. I don't remember ever not having a problem, in
10+ yrs..
Many people here seem to find it completely easy... not me.
So I'm back in the soup.
[I hope
walt w41...@gmail.com writes:
There's no reason to use menuconfig after running oldconfig, If your
old kernel was using all of the hardware, then the new kernel should,
too, just with oldconfig.
I don't know about that. I found a whole lot of stuff different when
I ran menuconfig and
On Tue, 03 Nov 2009 17:02:18 -0800, walt w41...@gmail.com wrote:
On 11/03/2009 02:29 PM, Harry Putnam wrote:
I'll say right from the start, that building a new kernel, has always
been a problem for me. I don't remember ever not having a problem, in
10+ yrs..
Many people here seem to find
hamilton hamil...@pobox.com writes:
On Tue, 03 Nov 2009 17:02:18 -0800, walt w41...@gmail.com wrote:
On 11/03/2009 02:29 PM, Harry Putnam wrote:
I'll say right from the start, that building a new kernel, has always
been a problem for me. I don't remember ever not having a problem, in
10+
Harry Putnam wrote:
hamilton hamil...@pobox.com writes:
On Tue, 03 Nov 2009 17:02:18 -0800, walt w41...@gmail.com wrote:
On 11/03/2009 02:29 PM, Harry Putnam wrote:
I'll say right from the start, that building a new kernel, has always
been a problem for me. I don't
Harry Putnam rea...@newsguy.com writes:
I think you can say make `oldconfig' and the `old config' is supposed to
be incorporated so no I didn't
If I had put .confg into the new sources, then plain make menuconfig
is what I would have used.
That is the wrong way round! make oldconfig uses
On Wednesday 04 November 2009 03:46:54 Harry Putnam wrote:
Volker Armin Hemmann volkerar...@googlemail.com writes:
your drivers for the ide disks have to be built INTO THE KERNEL! NOT
MODULES.
Is that really a hard rule? I've done it both ways successfully in the
past.
If you do not
24 matches
Mail list logo
