Mailing List Archive: Gentoo: User

kernel build - back in the soup.

1 2

View All

Index | Next | Previous | View Threaded

johnmoe at optusnet

Nov 4, 2009, 2:50 PM

Post #26 of 32 (289 views)
Permalink

Re: Re: kernel build - back in the soup. [In reply to]

Harry Putnam wrote:
> "John H. Moe" <johnmoe [at] optusnet> 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?
>
>
>
Well, my understanding is that SATA controllers can operate in one of
two modes: AHCI (or native) mode, which allows for the full capabilities
(read: SPEED) of the SATA interface, and an IDE-compatible mode, for
things like Windows XP (which I use at work) that doesn't, by default,
understand SATA. If you try to load WinXP on to a PC with SATA, you
either have to switch the SATA controller to IDE-mode, which allows
WinXP to see it as a normal IDE hard drive, or load a SATA driver at
install time (from a floppy! One of the few things I still need 3.5"
floppies for).

Translating this to Linux (at home), I chose the AHCI option when it
showed up in one kernel upgrade, and when I saw in the help for ATA_SFF
that it's the "legacy IDE interface", I figured I didn't need it, so I
left it out.

So if I understand this correctly, you should use the AHCI option if
your SATA controller is in "AHCI" or "Native" mode, and the ATA_SFF
option if you're in "IDE" or "Compatible" mode.

Hope this helps (and makes sense)

John Moe

daidxor at gmail

Nov 7, 2009, 3:26 AM

Post #27 of 32 (277 views)
Permalink

Re: kernel build - back in the soup. [In reply to]

2009/11/4 Harry Putnam <reader [at] newsguy>:
> 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.
>
> 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 me, I tried brute-force as
well!

Regards,
daid

reader at newsguy

Nov 7, 2009, 12:20 PM

Post #28 of 32 (274 views)
Permalink

Re: kernel build - back in the soup. [In reply to]

daid kahl <daidxor [at] gmail> writes:

> 2009/11/4 Harry Putnam <reader [at] newsguy>:
>> 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.
>>
>> 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 me, I tried brute-force as
> well!

Thanks for the tip... that tool does look useful. At least for
kernel comparison I think it might beat the poop out of the ediff mode
in emacs. Although the emacs tools are better in general.

I managed to get the kernel figured out... (with plenty of help here)
but I think I'll tinker with kccmp, see how it works, and be ready for
next time.

Really though, the whole problem was due to my foolish failure to put
the old .config into the new sources, before running `make oldconfig".
I think it would have gone off nice and smooth if I had.

Answering a dozen or so questions on the cmdline beats the poop out of
flopping around in menuconfig, or even worse, 2 instances of
menuconfig.

What is really maddening is that I once knew how to do the stuff with
.config and `make oldconfig'. Here lately I seem to forget things I
once knew if I don't use the knowledge for a mnth or two.

daidxor at gmail

Nov 8, 2009, 2:42 AM

Post #29 of 32 (284 views)
Permalink

Re: Re: kernel build - back in the soup. [In reply to]

>>> 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 me, I tried brute-force as
>> well!
>
> Thanks for the tip... that tool does look useful. At least for
> kernel comparison I think it might beat the poop out of the ediff mode
> in emacs. Although the emacs tools are better in general.
>
> I managed to get the kernel figured out... (with plenty of help here)
> but I think I'll tinker with kccmp, see how it works, and be ready for
> next time.

It's really easy. You just run it with two configuration files as
inputs, and it gives a nice X display with different settings, and
then settings that are only in one config or the other (resulting from
different kernel versions or sub-config options).

> Answering a dozen or so questions on the cmdline beats the poop out of
> flopping around in menuconfig, or even worse, 2 instances of
> menuconfig.
>
> What is really maddening is that I once knew how to do the stuff with
> .config and `make oldconfig'. Here lately I seem to forget things I
> once knew if I don't use the knowledge for a mnth or two.
>
I always do it from the command line with a web-browser searching
http://cateee.net/ for any config I don't know what it is.

~daid

rdalek1967 at gmail

Nov 8, 2009, 2:45 AM

Post #30 of 32 (281 views)
Permalink

Re: Re: kernel build - back in the soup. [In reply to]

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! It is much easier...trust me, I tried brute-force as
>>> well!
>>>
>> Thanks for the tip... that tool does look useful. At least for
>> kernel comparison I think it might beat the poop out of the ediff mode
>> in emacs. Although the emacs tools are better in general.
>>
>> I managed to get the kernel figured out... (with plenty of help here)
>> but I think I'll tinker with kccmp, see how it works, and be ready for
>> next time.
>>
>
> It's really easy. You just run it with two configuration files as
> inputs, and it gives a nice X display with different settings, and
> then settings that are only in one config or the other (resulting from
> different kernel versions or sub-config options).
>
>
>> Answering a dozen or so questions on the cmdline beats the poop out of
>> flopping around in menuconfig, or even worse, 2 instances of
>> menuconfig.
>>
>> What is really maddening is that I once knew how to do the stuff with
>> .config and `make oldconfig'. Here lately I seem to forget things I
>> once knew if I don't use the knowledge for a mnth or two.
>>
>>
> I always do it from the command line with a web-browser searching
> http://cateee.net/ for any config I don't know what it is.
>
> ~daid
>
>
>

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

Dale

:-) :-)

danieldaveiga at gmail

Nov 9, 2009, 7:57 AM

Post #31 of 32 (281 views)
Permalink

Re: Re: kernel build - back in the soup. [In reply to]

On Sun, Nov 8, 2009 at 08:45, Dale <rdalek1967 [at] gmail> 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. Instead emerge kccmp to compare kernel
>>>> configurations! It is much easier...trust me, I tried brute-force as
>>>> well!
>>>>
>>> Thanks for the tip... that tool does look useful. At least for
>>> kernel comparison I think it might beat the poop out of the ediff mode
>>> in emacs. Although the emacs tools are better in general.
>>>
>>> I managed to get the kernel figured out... (with plenty of help here)
>>> but I think I'll tinker with kccmp, see how it works, and be ready for
>>> next time.
>>>
>>
>> It's really easy. You just run it with two configuration files as
>> inputs, and it gives a nice X display with different settings, and
>> then settings that are only in one config or the other (resulting from
>> different kernel versions or sub-config options).
>>
>>
>>> Answering a dozen or so questions on the cmdline beats the poop out of
>>> flopping around in menuconfig, or even worse, 2 instances of
>>> menuconfig.
>>>
>>> What is really maddening is that I once knew how to do the stuff with
>>> .config and `make oldconfig'. Here lately I seem to forget things I
>>> once knew if I don't use the knowledge for a mnth or two.
>>>
>>>
>> I always do it from the command line with a web-browser searching
>> http://cateee.net/ for any config I don't know what it is.
>>
>> ~daid
>>
>>
>>
>
> 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 been using genkernel for 4+ years, of course had some problema
along the way, nothing that couldn't be handle.

I find it really easy to use.

Yeah, it worked first time, some tweaking later and BANG! It was perfect!
--
Daniel da Veiga

rdalek1967 at gmail

Nov 9, 2009, 9:57 AM

Post #32 of 32 (282 views)
Permalink

Re: Re: kernel build - back in the soup. [In reply to]

Daniel da Veiga wrote:
> On Sun, Nov 8, 2009 at 08:45, Dale <rdalek1967 [at] gmail> 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 been using genkernel for 4+ years, of course had some problema
> along the way, nothing that couldn't be handle.
>
> I find it really easy to use.
>
> Yeah, it worked first time, some tweaking later and BANG! It was perfect!
>

I tried that thing several times in its early days, it never made a
kernel that would even boot up. I did better doing mine by hand. I
have not tried it recently so I am sure it has improved a lot by now.
It may build a mighty fine kernel now but I can do the same thing with
oldconfig and know for sure what I am getting.

Dale

:-) :-)

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads