Maybe my frequent kernel building could be of some help to the community? And how to build?

Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Hello,

I own quite strong PC, 4 core Pentium. I recently started to build my 
kernel frequently, whenever I see a new patch on kernel.org I build 
again. Bothers me that I do it only for doing it. Maybe it could be of 
some help to the community? And if so, what would be more appreciated - 
linux-next patched kernel or gitN patched kernel? And how should I 
configure the kernel for this purpose? I am afraid of putting all the 
options on, yesterday I tried to put everything on as a module plus I 
tinkered with some other options that seemed innocent. The kernel was 
built but could not boot, saying that there was a problem with the root 
device, it could not recoginze /dev/sda2, which is my correct root 
device. I did not investigate much and reverted to working kernel.

Thanks in advance for your remarks.

Regards,

Piotr Hosowicz

-- 
"Chcemy waszego dobra!" - powiedział lider
socjaldemokratów. Zaniepokojeni obywatele
zaczeli ukrywać swoje dobra w bezpiecznych
miejscach.
NP:  -

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/16/10 12:02, Piotr Hosowicz wrote:
> Hello,
> 
> I own quite strong PC, 4 core Pentium. I recently started to build my
> kernel frequently, whenever I see a new patch on kernel.org I build
> again. Bothers me that I do it only for doing it. Maybe it could be of
> some help to the community? And if so, what would be more appreciated -
> linux-next patched kernel or gitN patched kernel? And how should I
> configure the kernel for this purpose? I am afraid of putting all the
> options on, yesterday I tried to put everything on as a module plus I
> tinkered with some other options that seemed innocent. The kernel was
> built but could not boot, saying that there was a problem with the root
> device, it could not recoginze /dev/sda2, which is my correct root
> device. I did not investigate much and reverted to working kernel.
> 
> Thanks in advance for your remarks.

Many linux-next builds are done daily: see
  http://kisskb.ellerman.id.au/kisskb/branch/9/

and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
daily and fix most build errors that I find in them.
(I am also using a quad-core PC with a cron job that finds the
next day's linux-next, downloads it, and does 50 builds.)

You are welcome to do the same or test mainline (with daily
builds) and/or Andrew Morton's mmotm patchset.

However, boot testing is probably even more helpful, such as you
have already tried.  The /dev/sda2 root problem is probably just a
configuration problem.  Would you like to try to diagnose it?

-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:

> You are welcome to do the same or test mainline (with daily
> builds) and/or Andrew Morton's mmotm patchset.

Saying "mainline" you mean the *gitN patch from kernel.org? I think I 
could do it. What is the ultimate source of the mmotm patch?

> However, boot testing is probably even more helpful, such as you
> have already tried.  The /dev/sda2 root problem is probably just a
> configuration problem.  Would you like to try to diagnose it?

I uninstalled that kernel and now I don't have that config.

Regards,

Piotr Hosowicz



-- 
"Polski system finansowy w okresie transformacji przejdzie do annałów
historii nonsensu, a logika polskich liberałów jest logika z pogranicza
surrealizmu". - Milton Friedman, laureat nagrody Nobla nazywany
papieżem wolnego rynku
NP: Miles Davis & John Coltrane - I Could Write a Book

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/16/10 12:33, Piotr Hosowicz wrote:
> Randy Dunlap wrote:
> 
>> You are welcome to do the same or test mainline (with daily
>> builds) and/or Andrew Morton's mmotm patchset.
> 
> Saying "mainline" you mean the *gitN patch from kernel.org? I think I
> could do it. What is the ultimate source of the mmotm patch?

Yes, daily mainline is either by daily *gitN patches or by using a linux-2.6.git
tree that you update at least once per day.

mmotm is announced on linux-kernel mailing list.  It is available as a tarball
of patches against mainline, e.g.:

mmotm-2010-0311-1313 ... applies to: 2.6.34-rc1

or in a git tree (somewhat delayed):

The mm-of-the-moment snapshot 2010-03-11-13-13 has been uploaded to

   http://userweb.kernel.org/~akpm/mmotm/

and will soon be available at

   git://zen-kernel.org/kernel/mmotm.git

See http://userweb.kernel.org/~akpm/mmotm/mmotm-readme.txt for more info.



>> However, boot testing is probably even more helpful, such as you
>> have already tried.  The /dev/sda2 root problem is probably just a
>> configuration problem.  Would you like to try to diagnose it?
> 
> I uninstalled that kernel and now I don't have that config.


-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:

> You are welcome to do the same or test mainline (with daily
> builds) and/or Andrew Morton's mmotm patchset.

I think that if Andrew's git repo is up to date usually I will be 
testing his work. Is this somethink what used to be suffixed -mm?

> However, boot testing is probably even more helpful, such as you
> have already tried.  The /dev/sda2 root problem is probably just a
> configuration problem.  Would you like to try to diagnose it?

Previously I wrote that I do not have the config - I forgot that I had 
built DEB package, so the config is there, I even have the source 
package, so I think we can diagnose it. Shall I send you the .config 
file off-list (there is some size limit as far as I know).

-- 
Z cyklu "Uroki demokracji", czyli pytania i odpowiedzi w teledurniejach:
- Jaką walutę mają Indie?
- Ramadan.
NP: Miles Davis, John Coltrane - Bye Bye Blackbird

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/16/10 20:24, Piotr Hosowicz wrote:
> Randy Dunlap wrote:
> 
>> You are welcome to do the same or test mainline (with daily
>> builds) and/or Andrew Morton's mmotm patchset.
> 
> I think that if Andrew's git repo is up to date usually I will be
> testing his work. Is this somethink what used to be suffixed -mm?

Yes, it used to be -mm.

>> However, boot testing is probably even more helpful, such as you
>> have already tried.  The /dev/sda2 root problem is probably just a
>> configuration problem.  Would you like to try to diagnose it?
> 
> Previously I wrote that I do not have the config - I forgot that I had
> built DEB package, so the config is there, I even have the source
> package, so I think we can diagnose it. Shall I send you the .config
> file off-list (there is some size limit as far as I know).

The size limit shouldn't stop a kernel config file.
Just send it, please.


-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/17/10 08:44, Piotr Hosowicz wrote:
> Randy Dunlap wrote:
> 
>>>> However, boot testing is probably even more helpful, such as you
>>>> have already tried.  The /dev/sda2 root problem is probably just a
>>>> configuration problem.  Would you like to try to diagnose it?
>>> Previously I wrote that I do not have the config - I forgot that I had
>>> built DEB package, so the config is there, I even have the source
>>> package, so I think we can diagnose it. Shall I send you the .config
>>> file off-list (there is some size limit as far as I know).
>>
>> The size limit shouldn't stop a kernel config file.
>> Just send it, please.
> 
> Ok, please find it attached.

OK, are you using lilo or grub?  Whatever boot loader it is, please
show us a working boot loader config entry and the failing boot loader
config entry.

The first thing that I would try is enabling CONFIG_DEVTMPFS and
CONFIG_DEVTMPFS_MOUNT, rebuild, reboot...

-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:

> OK, are you using lilo or grub?

I am using GRUB.

> Whatever boot loader it is, please
> show us a working boot loader config entry and the failing boot loader
> config entry.

This is the working one, one of working ones:

title		Debian GNU/Linux, kernel 2.6.34-rc1-nx-20100317-next-20100317+
root		(hd0,0)
kernel		/vmlinuz-2.6.34-rc1-nx-20100317-next-20100317+ root=/dev/sda2 ro 
quiet
initrd		/initrd.img-2.6.34-rc1-nx-20100317-next-20100317+


This is the failing one:

title		Debian GNU/Linux, kernel 2.6.34-rc1-nxa-20100315-next-20100315+
root		(hd0,0)
kernel		/vmlinuz-2.6.34-rc1-nxa-20100315-next-20100315+ root=/dev/sda2 
ro quiet
initrd		/initrd.img-2.6.34-rc1-nxa-20100315-next-20100315+

> The first thing that I would try is enabling CONFIG_DEVTMPFS and
> CONFIG_DEVTMPFS_MOUNT, rebuild, reboot...

Ok, thanks, I'll try.

-- 
Jest jedna korzyść z posiadania TV - jak dobrze
rozregulujesz odbiornik, trafisz na promieniowanie
mikrofalowe z początków Wszechświata.
NP:  -

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:

> The first thing that I would try is enabling CONFIG_DEVTMPFS and
> CONFIG_DEVTMPFS_MOUNT, rebuild, reboot...

I've rebuilt and it boots fine. Just after booting the kernel it had to 
think for a while and I was afraid that it won't boot at all. But it booted.

BTW What is this message during building about? Should I worry?

WARNING: modpost: Found 106 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'

Regards,

Piotr Hosowicz

-- 
"[Oleksy] dotknął naszych domów, naszych żon, naszych dzieci,
naszych psów, naszych ŚWINEK MORSKICH, on po prostu wkroczył
swoim głupim gadaniem w sferę prywatną, która musi być chro-
niona dla dobra każdego z nas" - powiedział Kwaśniewski.
NP:  -

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/17/10 10:49, Piotr Hosowicz wrote:
> Randy Dunlap wrote:
> 
>> The first thing that I would try is enabling CONFIG_DEVTMPFS and
>> CONFIG_DEVTMPFS_MOUNT, rebuild, reboot...
> 
> I've rebuilt and it boots fine. Just after booting the kernel it had to
> think for a while and I was afraid that it won't boot at all. But it
> booted.

Good.

> BTW What is this message during building about? Should I worry?
> 
> WARNING: modpost: Found 106 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'

"Worry" is probably too strong of a word there.  Any section mismatch
is a potential kernel Oops, but most of them don't cause problems.
If you do get an Oops or BUG or other problem, please post it to the
linux-kernel mailing list.

-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:

> On 03/16/10 12:02, Piotr Hosowicz wrote:
> > Hello,
> > 
> > I own quite strong PC, 4 core Pentium. I recently started to build my
> > kernel frequently, whenever I see a new patch on kernel.org I build
> > again. Bothers me that I do it only for doing it. Maybe it could be of
> > some help to the community? And if so, what would be more appreciated -
> > linux-next patched kernel or gitN patched kernel? And how should I
> > configure the kernel for this purpose? I am afraid of putting all the
> > options on, yesterday I tried to put everything on as a module plus I
> > tinkered with some other options that seemed innocent. The kernel was
> > built but could not boot, saying that there was a problem with the root
> > device, it could not recoginze /dev/sda2, which is my correct root
> > device. I did not investigate much and reverted to working kernel.
> > 
> > Thanks in advance for your remarks.
> 
> Many linux-next builds are done daily: see
>   http://kisskb.ellerman.id.au/kisskb/branch/9/
> 
> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
> daily and fix most build errors that I find in them.
> (I am also using a quad-core PC with a cron job that finds the
> next day's linux-next, downloads it, and does 50 builds.)
> 
> You are welcome to do the same or test mainline (with daily
> builds) and/or Andrew Morton's mmotm patchset.


One thing that you could do that no one focuses on is building
with some kconfig symbols disabled (ones that are typically enabled),
such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same time,
just various/random combinations of them.


---
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:

> One thing that you could do that no one focuses on is building
> with some kconfig symbols disabled (ones that are typically enabled),
> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same time,
> just various/random combinations of them.

I am glad I can help. At last I sat down to write the scripts, I was so 
excited I couldn't fall asleep ;-). I figured it out in such a way:

- separate system user for building
- in his crontab everyminute a build try starts with randomized options 
you mentioned - this works, I hope

The problem is that it requires my assistance, because it asks a few 
questions like in make oldconfig when there are new options available. I 
do not know how to fix this.

Here are the scripts:

# randomize-conf.sh

#!/bin/bash

NETENABLED=0
function enable_or_not(){
   if test $RANDOM -lt 16383 ; then
     if test $1=CONFIG_NET ; then
       NETENABLED=1
       echo $1=y
       return
     fi
     if test $1=CONFIG_INET && test $NETENABLED -eq 1 ; then
       if test $RANDOM -lt 16383 ; then
         echo $1=y
       else
         echo '# CONFIG_'$1' is not set'
       fi
       return
     fi
   else
     echo '# CONFIG_'$1' is not set'
   fi
}

while read LINE ; do
   FIRST=$(echo $LINE | cut -d '=' -f 1)
   case $FIRST in
     CONFIG_SMP)
       enable_or_not CONFIG_SMP
     ;;
     CONFIG_SYSFS)
       enable_or_not CONFIG_SYSFS
     ;;
     CONFIG_PROC_FS)
       enable_or_not CONFIG_PROC_FS
     ;;
     CONFIG_PM)
       enable_or_not CONFIG_PM
     ;;
     CONFIG_PCI)
       enable_or_not CONFIG_PCI
     ;;
     CONFIG_BLOCK)
       enable_or_not CONFIG_BLOCK
     ;;
     CONFIG_NET)
       enable_or_not CONFIG_NET
     ;;
     CONFIG_INET)
       enable_or_not CONFIG_INET
     ;;
     CONFIG_HOTPLUG)
       enable_or_not CONFIG_HOTPLUG
     ;;
     *)
       echo $LINE
   esac
done

# try-build.sh

#!/bin/bash

RCPT=phz@localhost

function tidy(){
   rm ../results/.config 2>/dev/null
   rm ../results/build.log 2>/dev/null
   rm ../BUILDING-NOW 2>/dev/null
}

cd ~/kernel/linux
if test -f ../BUILDING-NOW ; then
   exit 0
else
   touch ../BUILDING-NOW
   make mrproper
   cat ../config.all | ../randomize-conf.sh > ./.config
   make prepare
   cp .config ../results/
   make -j 10 2>&1 > ../results/build.log
   if test $? -ne 0 ; then
     (cat ../results/.config && cat ../results/build.log) | mail -s 
'Build failed at kernel phase' $RCPT
     mv ../results/.config ../results/.config.kf.$(date +%y%m%d-%H%M%S)
     tidy
     exit 0
   fi
   make -j 10 modules 2>&1 >> ../results/build.log
   if test $? -ne 0 ; then
     (cat ../results/.config && cat ../results/build.log) | mail -s 
'Build failed at modules phase' $RCPT
     mv ../results/.config ../results/.config.mf.$(date +%y%m%d-%H%M%S)
     tidy
     exit 0
   fi
   echo OK | mail -s 'ok' $RCPT
   tidy
fi



-- 
TV: "Rosjanki osiągnęły szczyt w niewłaściwym miejscu, w
niewłaściwym czasie i właściwie zupełnie niepotrzebnie."
NP: Mark Knopfler - Hard Shoulder
NB: 2.6.34-rc1-git9-a

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/21/10 20:31, Piotr Hosowicz wrote:
> Randy Dunlap wrote:
> 
>> One thing that you could do that no one focuses on is building
>> with some kconfig symbols disabled (ones that are typically enabled),
>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same time,
>> just various/random combinations of them.
> 
> I am glad I can help. At last I sat down to write the scripts, I was so
> excited I couldn't fall asleep ;-). I figured it out in such a way:
> 
> - separate system user for building
> - in his crontab everyminute a build try starts with randomized options
> you mentioned - this works, I hope
> 
> The problem is that it requires my assistance, because it asks a few
> questions like in make oldconfig when there are new options available. I
> do not know how to fix this.
> 
> Here are the scripts:
> 
> # randomize-conf.sh
> 
> #!/bin/bash
> 
> NETENABLED=0
> function enable_or_not(){
>   if test $RANDOM -lt 16383 ; then
>     if test $1=CONFIG_NET ; then
>       NETENABLED=1
>       echo $1=y
>       return
>     fi
>     if test $1=CONFIG_INET && test $NETENABLED -eq 1 ; then
>       if test $RANDOM -lt 16383 ; then
>         echo $1=y
>       else
>         echo '# CONFIG_'$1' is not set'
>       fi
>       return
>     fi
>   else
>     echo '# CONFIG_'$1' is not set'
>   fi
> }
> 
> while read LINE ; do
>   FIRST=$(echo $LINE | cut -d '=' -f 1)
>   case $FIRST in
>     CONFIG_SMP)
>       enable_or_not CONFIG_SMP
>     ;;
>     CONFIG_SYSFS)
>       enable_or_not CONFIG_SYSFS
>     ;;
>     CONFIG_PROC_FS)
>       enable_or_not CONFIG_PROC_FS
>     ;;
>     CONFIG_PM)
>       enable_or_not CONFIG_PM
>     ;;
>     CONFIG_PCI)
>       enable_or_not CONFIG_PCI
>     ;;
>     CONFIG_BLOCK)
>       enable_or_not CONFIG_BLOCK
>     ;;
>     CONFIG_NET)
>       enable_or_not CONFIG_NET
>     ;;
>     CONFIG_INET)
>       enable_or_not CONFIG_INET
>     ;;
>     CONFIG_HOTPLUG)
>       enable_or_not CONFIG_HOTPLUG
>     ;;
>     *)
>       echo $LINE
>   esac
> done
> 
> # try-build.sh
> 
> #!/bin/bash
> 
> RCPT=phz@localhost
> 
> function tidy(){
>   rm ../results/.config 2>/dev/null
>   rm ../results/build.log 2>/dev/null
>   rm ../BUILDING-NOW 2>/dev/null
> }
> 
> cd ~/kernel/linux
> if test -f ../BUILDING-NOW ; then
>   exit 0
> else
>   touch ../BUILDING-NOW
>   make mrproper
>   cat ../config.all | ../randomize-conf.sh > ./.config
>   make prepare

Hm, I'm not even familiar with "make prepare".  Instead at this point I use
"make oldconfig", and to help it along with answers (non-interactive answers,
that is), use 'yes', like:

    yes '' | make oldconfig

I think that this will fix what you described...


>   cp .config ../results/
>   make -j 10 2>&1 > ../results/build.log
>   if test $? -ne 0 ; then
>     (cat ../results/.config && cat ../results/build.log) | mail -s
> 'Build failed at kernel phase' $RCPT
>     mv ../results/.config ../results/.config.kf.$(date +%y%m%d-%H%M%S)
>     tidy
>     exit 0
>   fi
>   make -j 10 modules 2>&1 >> ../results/build.log
>   if test $? -ne 0 ; then
>     (cat ../results/.config && cat ../results/build.log) | mail -s
> 'Build failed at modules phase' $RCPT
>     mv ../results/.config ../results/.config.mf.$(date +%y%m%d-%H%M%S)
>     tidy
>     exit 0
>   fi
>   echo OK | mail -s 'ok' $RCPT
>   tidy
> fi


-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On 03/21/10 20:31, Piotr Hosowicz wrote:
>> Randy Dunlap wrote:
>>
>>> One thing that you could do that no one focuses on is building
>>> with some kconfig symbols disabled (ones that are typically enabled),
>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same time,
>>> just various/random combinations of them.
>> I am glad I can help. At last I sat down to write the scripts, I was so
>> excited I couldn't fall asleep ;-). I figured it out in such a way:
>>
>> - separate system user for building
>> - in his crontab everyminute a build try starts with randomized options
>> you mentioned - this works, I hope
>>
>> The problem is that it requires my assistance, because it asks a few
>> questions like in make oldconfig when there are new options available. I
>> do not know how to fix this.
>>
>> Here are the scripts:
>>
>> # randomize-conf.sh
>>
>> #!/bin/bash
>>
>> NETENABLED=0
>> function enable_or_not(){
>>   if test $RANDOM -lt 16383 ; then
>>     if test $1=CONFIG_NET ; then
>>       NETENABLED=1
>>       echo $1=y
>>       return
>>     fi
>>     if test $1=CONFIG_INET && test $NETENABLED -eq 1 ; then
>>       if test $RANDOM -lt 16383 ; then
>>         echo $1=y
>>       else
>>         echo '# CONFIG_'$1' is not set'
>>       fi
>>       return
>>     fi
>>   else
>>     echo '# CONFIG_'$1' is not set'
>>   fi
>> }
>>
>> while read LINE ; do
>>   FIRST=$(echo $LINE | cut -d '=' -f 1)
>>   case $FIRST in
>>     CONFIG_SMP)
>>       enable_or_not CONFIG_SMP
>>     ;;
>>     CONFIG_SYSFS)
>>       enable_or_not CONFIG_SYSFS
>>     ;;
>>     CONFIG_PROC_FS)
>>       enable_or_not CONFIG_PROC_FS
>>     ;;
>>     CONFIG_PM)
>>       enable_or_not CONFIG_PM
>>     ;;
>>     CONFIG_PCI)
>>       enable_or_not CONFIG_PCI
>>     ;;
>>     CONFIG_BLOCK)
>>       enable_or_not CONFIG_BLOCK
>>     ;;
>>     CONFIG_NET)
>>       enable_or_not CONFIG_NET
>>     ;;
>>     CONFIG_INET)
>>       enable_or_not CONFIG_INET
>>     ;;
>>     CONFIG_HOTPLUG)
>>       enable_or_not CONFIG_HOTPLUG
>>     ;;
>>     *)
>>       echo $LINE
>>   esac
>> done
>>
>> # try-build.sh
>>
>> #!/bin/bash
>>
>> RCPT=phz@localhost
>>
>> function tidy(){
>>   rm ../results/.config 2>/dev/null
>>   rm ../results/build.log 2>/dev/null
>>   rm ../BUILDING-NOW 2>/dev/null
>> }
>>
>> cd ~/kernel/linux
>> if test -f ../BUILDING-NOW ; then
>>   exit 0
>> else
>>   touch ../BUILDING-NOW
>>   make mrproper
>>   cat ../config.all | ../randomize-conf.sh > ./.config
>>   make prepare
> 
> Hm, I'm not even familiar with "make prepare".  Instead at this point I use
> "make oldconfig", and to help it along with answers (non-interactive answers,
> that is), use 'yes', like:
> 
>     yes '' | make oldconfig
> 
> I think that this will fix what you described...

No, it will not. The problem is somewhere in my randomizer. During build 
preparation it oldconfig-style asks eg for SMP which is enabled in the 
template. It should not ask. Now I observe that it functions randomly. 
Sometimes build procedes as expected, sometimes not. I must carefully 
think it through, possibly rewrite.

-- 
Z cyklu "Uroki demokracji", czyli pytania i odpowiedzi w teledurniejach:
- W którym kraju znajduje się Mount Everest?
- Hm, to nie Szkocja, prawda?
NP: Mark Knopfler - Piper To The End
NB: 2.6.34-rc1-git9-a

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Piotr Hosowicz wrote:
> Randy Dunlap wrote:
>> On 03/21/10 20:31, Piotr Hosowicz wrote:
>>> Randy Dunlap wrote:
>>>
>>>> One thing that you could do that no one focuses on is building
>>>> with some kconfig symbols disabled (ones that are typically enabled),
>>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same 
>>>> time,
>>>> just various/random combinations of them.
>>> I am glad I can help. At last I sat down to write the scripts, I was so
>>> excited I couldn't fall asleep ;-). I figured it out in such a way:
>>>
>>> - separate system user for building
>>> - in his crontab everyminute a build try starts with randomized options
>>> you mentioned - this works, I hope
>>>
>>> The problem is that it requires my assistance, because it asks a few
>>> questions like in make oldconfig when there are new options available. I
>>> do not know how to fix this.
>>>
>>> Here are the scripts:
>>>
>>> # randomize-conf.sh
>>>
>>> #!/bin/bash
>>>
>>> NETENABLED=0
>>> function enable_or_not(){
>>>   if test $RANDOM -lt 16383 ; then
>>>     if test $1=CONFIG_NET ; then
>>>       NETENABLED=1
>>>       echo $1=y
>>>       return
>>>     fi
>>>     if test $1=CONFIG_INET && test $NETENABLED -eq 1 ; then
>>>       if test $RANDOM -lt 16383 ; then
>>>         echo $1=y
>>>       else
>>>         echo '# CONFIG_'$1' is not set'
>>>       fi
>>>       return
>>>     fi
>>>   else
>>>     echo '# CONFIG_'$1' is not set'
>>>   fi
>>> }
>>>
>>> while read LINE ; do
>>>   FIRST=$(echo $LINE | cut -d '=' -f 1)
>>>   case $FIRST in
>>>     CONFIG_SMP)
>>>       enable_or_not CONFIG_SMP
>>>     ;;
>>>     CONFIG_SYSFS)
>>>       enable_or_not CONFIG_SYSFS
>>>     ;;
>>>     CONFIG_PROC_FS)
>>>       enable_or_not CONFIG_PROC_FS
>>>     ;;
>>>     CONFIG_PM)
>>>       enable_or_not CONFIG_PM
>>>     ;;
>>>     CONFIG_PCI)
>>>       enable_or_not CONFIG_PCI
>>>     ;;
>>>     CONFIG_BLOCK)
>>>       enable_or_not CONFIG_BLOCK
>>>     ;;
>>>     CONFIG_NET)
>>>       enable_or_not CONFIG_NET
>>>     ;;
>>>     CONFIG_INET)
>>>       enable_or_not CONFIG_INET
>>>     ;;
>>>     CONFIG_HOTPLUG)
>>>       enable_or_not CONFIG_HOTPLUG
>>>     ;;
>>>     *)
>>>       echo $LINE
>>>   esac
>>> done
>>>
>>> # try-build.sh
>>>
>>> #!/bin/bash
>>>
>>> RCPT=phz@localhost
>>>
>>> function tidy(){
>>>   rm ../results/.config 2>/dev/null
>>>   rm ../results/build.log 2>/dev/null
>>>   rm ../BUILDING-NOW 2>/dev/null
>>> }
>>>
>>> cd ~/kernel/linux
>>> if test -f ../BUILDING-NOW ; then
>>>   exit 0
>>> else
>>>   touch ../BUILDING-NOW
>>>   make mrproper
>>>   cat ../config.all | ../randomize-conf.sh > ./.config
>>>   make prepare
>>
>> Hm, I'm not even familiar with "make prepare".  Instead at this point 
>> I use
>> "make oldconfig", and to help it along with answers (non-interactive 
>> answers,
>> that is), use 'yes', like:
>>
>>     yes '' | make oldconfig
>>
>> I think that this will fix what you described...
> 
> No, it will not. The problem is somewhere in my randomizer. During build 
> preparation it oldconfig-style asks eg for SMP which is enabled in the 
> template. It should not ask. Now I observe that it functions randomly. 
> Sometimes build procedes as expected, sometimes not. I must carefully 
> think it through, possibly rewrite.

The randomizer is severely botched. First error is here:

 >>>         echo '# CONFIG_'$1' is not set'

Should be:

 >>>         echo '# '$1' is not set'

But it seems that it works, but I do not understand why. Needs rewrite, 
better config template line parsing.

Regards,

Piotr Hosowicz

-- 
Na przyjęciu chłopak pyta blondynkę:
- Czy mogę cię prosić do walca?
- Zgłupiałeś? To już nie miałeś czym przyjechać?
NP: Black Stone Cherry - Reverend Wrinkle
NB: 2.6.34-rc1-git9-a

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Piotr Hosowicz wrote:

 > But it seems that it works, but I do not understand why. Needs rewrite,
 > better config template line parsing.

I made it with Python, the scripts follow:

--- main try-build.sh

#!/bin/bash

RCPT=phz@localhost

function tidy(){
   rm ../results/.config 2>/dev/null
   rm ../results/build.log 2>/dev/null
   rm ../BUILDING-NOW 2>/dev/null
}

cd ~/kernel/linux
if test -f ../BUILDING-NOW ; then
   exit 0
else
   touch ../BUILDING-NOW
   make mrproper
   cat ../config.all | ../randomize-conf.py > ./.config
   make prepare
   cp .config ../results/
   make -j 10 2>&1 > ../results/build.log
   if test $? -ne 0 ; then
     (cat ../results/.config && cat ../results/build.log) | mail -s 
'Build failed at kernel phase' $RCPT
     mv ../results/.config ../results/.config.kf.$(date +%y%m%d-%H%M%S)
     tidy
     exit 0
   fi
   make -j 10 modules 2>&1 >> ../results/build.log
   if test $? -ne 0 ; then
     (cat ../results/.config && cat ../results/build.log) | mail -s 
'Build failed at modules phase' $RCPT
     mv ../results/.config ../results/.config.mf.$(date +%y%m%d-%H%M%S)
     tidy
     exit 0
   fi
   echo OK | mail -s 'ok' $RCPT
   tidy
fi

--- the randomizer:

#!/usr/bin/python

import sys
import re
import random

netenabled = 0
token = ""

def yesno():
	if random.random()>0.5:
		return 1
	else:
		return 0


def enable_or_not(atoken):
	if yesno():
		if atoken=="CONFIG_NET":
			netenabled = 1
			print atoken+"=y"
		else:
			if atoken=="CONFIG_INET":
				if yesno():
					print atoken+"=y"
				else:
					print "# "+atoken+" is not set" ;
			else:
				print atoken+"=y"
	else:
		print "# "+atoken+" is not set" ;

switch = {
	"CONFIG_SMP": enable_or_not("CONFIG_SMP"),
	"CONFIG_SYSFS": enable_or_not("CONFIG_SYSFS"),
	"CONFIG_PROC_FS": enable_or_not("CONFIG_PROC_FS"),
	"CONFIG_PM": enable_or_not("CONFIG_PM"),
	"CONFIG_PCI": enable_or_not("CONFIG_PCI"),
	"CONFIG_BLOCK": enable_or_not("CONFIG_BLOCK"),
	"CONFIG_NET": enable_or_not("CONFIG_NET"),
	"CONFIG_INET": enable_or_not("CONFIG_INET"),
	"CONFIG_HOTPLUG": enable_or_not("CONFIG_HOTPLUG")
	}

for line in sys.stdin:
	mo = re.match("(\w+)=(.*)", line)
	if mo:
		token = mo.group(1)
	else:
		mo = re.match("# (\w+) is not set", line)
		if mo:
			token = mo.group(1)
	if token!="CONFIG_MODULES":
		switch.get(token, enable_or_not(token))
	else:
		sys.stdout.write("CONFIG_MODULES=y\n")


-- 
Janusz Korwin-Mikke:
"Idiota z dyplomem to taki sam idiota,
jak przedtem - tylko z pretensjami."
NP: Mark Knopfler - Cleaning My Gun
NB: 2.6.34-rc2-nx-20100323-next-20100323+



-- 
Wzór Einsteina-Pitagorasa: E = mc2 = m(a2 + b2)
NP: Mark Knopfler - The Car Was The One
NB: 2.6.34-rc2-nx-20100323-next-20100323+

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/23/10 18:12, Piotr Hosowicz wrote:
> Piotr Hosowicz wrote:
> 
>> But it seems that it works, but I do not understand why. Needs rewrite,
>> better config template line parsing.
> 
> I made it with Python, the scripts follow:

Thanks for sharing them.

> --- main try-build.sh
> 
> #!/bin/bash
> 
> RCPT=phz@localhost
> 
> function tidy(){
>   rm ../results/.config 2>/dev/null
>   rm ../results/build.log 2>/dev/null
>   rm ../BUILDING-NOW 2>/dev/null
> }
> 
> cd ~/kernel/linux
> if test -f ../BUILDING-NOW ; then
>   exit 0
> else
>   touch ../BUILDING-NOW
>   make mrproper
>   cat ../config.all | ../randomize-conf.py > ./.config
>   make prepare
>   cp .config ../results/
>   make -j 10 2>&1 > ../results/build.log

'make' with no target also builds modules, so the 'make modules'
below isn't needed (it's extra work).

>   if test $? -ne 0 ; then
>     (cat ../results/.config && cat ../results/build.log) | mail -s
> 'Build failed at kernel phase' $RCPT
>     mv ../results/.config ../results/.config.kf.$(date +%y%m%d-%H%M%S)
>     tidy
>     exit 0
>   fi
>   make -j 10 modules 2>&1 >> ../results/build.log
>   if test $? -ne 0 ; then
>     (cat ../results/.config && cat ../results/build.log) | mail -s
> 'Build failed at modules phase' $RCPT
>     mv ../results/.config ../results/.config.mf.$(date +%y%m%d-%H%M%S)
>     tidy
>     exit 0
>   fi
>   echo OK | mail -s 'ok' $RCPT
>   tidy
> fi
> 
> --- the randomizer:
> 
> #!/usr/bin/python
> 
> import sys
> import re
> import random
> 
> netenabled = 0
> token = ""
> 
> def yesno():
>     if random.random()>0.5:
>         return 1
>     else:
>         return 0
> 
> 
> def enable_or_not(atoken):
>     if yesno():
>         if atoken=="CONFIG_NET":
>             netenabled = 1
>             print atoken+"=y"
>         else:
>             if atoken=="CONFIG_INET":
>                 if yesno():
>                     print atoken+"=y"
>                 else:
>                     print "# "+atoken+" is not set" ;
>             else:
>                 print atoken+"=y"
>     else:
>         print "# "+atoken+" is not set" ;
> 
> switch = {
>     "CONFIG_SMP": enable_or_not("CONFIG_SMP"),
>     "CONFIG_SYSFS": enable_or_not("CONFIG_SYSFS"),
>     "CONFIG_PROC_FS": enable_or_not("CONFIG_PROC_FS"),
>     "CONFIG_PM": enable_or_not("CONFIG_PM"),
>     "CONFIG_PCI": enable_or_not("CONFIG_PCI"),
>     "CONFIG_BLOCK": enable_or_not("CONFIG_BLOCK"),
>     "CONFIG_NET": enable_or_not("CONFIG_NET"),
>     "CONFIG_INET": enable_or_not("CONFIG_INET"),
>     "CONFIG_HOTPLUG": enable_or_not("CONFIG_HOTPLUG")
>     }
> 
> for line in sys.stdin:
>     mo = re.match("(\w+)=(.*)", line)
>     if mo:
>         token = mo.group(1)
>     else:
>         mo = re.match("# (\w+) is not set", line)
>         if mo:
>             token = mo.group(1)
>     if token!="CONFIG_MODULES":
>         switch.get(token, enable_or_not(token))
>     else:
>         sys.stdout.write("CONFIG_MODULES=y\n")
> 
> 


-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On 03/23/10 18:12, Piotr Hosowicz wrote:
>> Piotr Hosowicz wrote:
>>
>>> But it seems that it works, but I do not understand why. Needs rewrite,
>>> better config template line parsing.
>> I made it with Python, the scripts follow:
> 
> Thanks for sharing them.

Sorry to say but they are crap, the python script corrupts the config 
file, I do not know why. I'll try to solve it and post again.

>> --- main try-build.sh
>>
>> #!/bin/bash
>>
>> RCPT=phz@localhost
>>
>> function tidy(){
>>   rm ../results/.config 2>/dev/null
>>   rm ../results/build.log 2>/dev/null
>>   rm ../BUILDING-NOW 2>/dev/null
>> }
>>
>> cd ~/kernel/linux
>> if test -f ../BUILDING-NOW ; then
>>   exit 0
>> else
>>   touch ../BUILDING-NOW
>>   make mrproper
>>   cat ../config.all | ../randomize-conf.py > ./.config
>>   make prepare
>>   cp .config ../results/
>>   make -j 10 2>&1 > ../results/build.log
> 
> 'make' with no target also builds modules, so the 'make modules'
> below isn't needed (it's extra work).

Yes, but I wanted to have it separate to know when the build fails.

Regards,

Piotr Hosowicz

-- 
Miss World 2006: Jestem szczęśliwa, że mogę wspaniale uczestniczyć w
przeżyciu najpiękniejszych kobiet tutaj w Warszawie, gdzie Jan Paweł II,
papież, w Polsce, skąd pochodzi. Spotkałam się z Kościołem Mariackim
w Krakowie, który ciepło ludzi i wielka przyjaźń. Połowa mojego serca
zostanie w Polsce, a druga połowa pojedzie ze mną do mojego kraju.
NP: Mark Knopfler - Piper To The End
NB: 2.6.34-rc2-nx-20100324-next-20100324+

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/18/10 08:40, Randy Dunlap wrote:
> On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
> 
>> On 03/16/10 12:02, Piotr Hosowicz wrote:
>>> Hello,
>>>
>>> I own quite strong PC, 4 core Pentium. I recently started to build my
>>> kernel frequently, whenever I see a new patch on kernel.org I build
>>> again. Bothers me that I do it only for doing it. Maybe it could be of
>>> some help to the community? And if so, what would be more appreciated -
>>> linux-next patched kernel or gitN patched kernel? And how should I
>>> configure the kernel for this purpose? I am afraid of putting all the
>>> options on, yesterday I tried to put everything on as a module plus I
>>> tinkered with some other options that seemed innocent. The kernel was
>>> built but could not boot, saying that there was a problem with the root
>>> device, it could not recoginze /dev/sda2, which is my correct root
>>> device. I did not investigate much and reverted to working kernel.
>>>
>>> Thanks in advance for your remarks.
>>
>> Many linux-next builds are done daily: see
>>   http://kisskb.ellerman.id.au/kisskb/branch/9/
>>
>> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
>> daily and fix most build errors that I find in them.
>> (I am also using a quad-core PC with a cron job that finds the
>> next day's linux-next, downloads it, and does 50 builds.)
>>
>> You are welcome to do the same or test mainline (with daily
>> builds) and/or Andrew Morton's mmotm patchset.
> 
> 
> One thing that you could do that no one focuses on is building
> with some kconfig symbols disabled (ones that are typically enabled),
> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same time,
> just various/random combinations of them.

and CONFIG_SYSRQ=n  (just found some errors due to this one)


-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On 03/18/10 08:40, Randy Dunlap wrote:
>> On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
>>
>>> On 03/16/10 12:02, Piotr Hosowicz wrote:
>>>> Hello,
>>>>
>>>> I own quite strong PC, 4 core Pentium. I recently started to build my
>>>> kernel frequently, whenever I see a new patch on kernel.org I build
>>>> again. Bothers me that I do it only for doing it. Maybe it could be of
>>>> some help to the community? And if so, what would be more appreciated -
>>>> linux-next patched kernel or gitN patched kernel? And how should I
>>>> configure the kernel for this purpose? I am afraid of putting all the
>>>> options on, yesterday I tried to put everything on as a module plus I
>>>> tinkered with some other options that seemed innocent. The kernel was
>>>> built but could not boot, saying that there was a problem with the root
>>>> device, it could not recoginze /dev/sda2, which is my correct root
>>>> device. I did not investigate much and reverted to working kernel.
>>>>
>>>> Thanks in advance for your remarks.
>>> Many linux-next builds are done daily: see
>>>   http://kisskb.ellerman.id.au/kisskb/branch/9/
>>>
>>> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
>>> daily and fix most build errors that I find in them.
>>> (I am also using a quad-core PC with a cron job that finds the
>>> next day's linux-next, downloads it, and does 50 builds.)
>>>
>>> You are welcome to do the same or test mainline (with daily
>>> builds) and/or Andrew Morton's mmotm patchset.
>>
>> One thing that you could do that no one focuses on is building
>> with some kconfig symbols disabled (ones that are typically enabled),
>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same time,
>> just various/random combinations of them.
> 
> and CONFIG_SYSRQ=n  (just found some errors due to this one)

You mean CONFIG_SYSRQ=n exactly and mandatory in every config or this 
was just an example?

Regards,

Piotr Hosowicz

-- 
"Polski system finansowy w okresie transformacji przejdzie do annałów
historii nonsensu, a logika polskich liberałów jest logika z pogranicza
surrealizmu". - Milton Friedman, laureat nagrody Nobla nazywany
papieżem wolnego rynku
NP: John Coltrane & Miles Davis - On Green Dolphin Street
NB: 2.6.34-rc2-nx-20100325-next-20100325+

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/25/10 10:37, Piotr Hosowicz wrote:
> Randy Dunlap wrote:
>> On 03/18/10 08:40, Randy Dunlap wrote:
>>> On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
>>>
>>>> On 03/16/10 12:02, Piotr Hosowicz wrote:
>>>>> Hello,
>>>>>
>>>>> I own quite strong PC, 4 core Pentium. I recently started to build my
>>>>> kernel frequently, whenever I see a new patch on kernel.org I build
>>>>> again. Bothers me that I do it only for doing it. Maybe it could be of
>>>>> some help to the community? And if so, what would be more
>>>>> appreciated -
>>>>> linux-next patched kernel or gitN patched kernel? And how should I
>>>>> configure the kernel for this purpose? I am afraid of putting all the
>>>>> options on, yesterday I tried to put everything on as a module plus I
>>>>> tinkered with some other options that seemed innocent. The kernel was
>>>>> built but could not boot, saying that there was a problem with the
>>>>> root
>>>>> device, it could not recoginze /dev/sda2, which is my correct root
>>>>> device. I did not investigate much and reverted to working kernel.
>>>>>
>>>>> Thanks in advance for your remarks.
>>>> Many linux-next builds are done daily: see
>>>>   http://kisskb.ellerman.id.au/kisskb/branch/9/
>>>>
>>>> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
>>>> daily and fix most build errors that I find in them.
>>>> (I am also using a quad-core PC with a cron job that finds the
>>>> next day's linux-next, downloads it, and does 50 builds.)
>>>>
>>>> You are welcome to do the same or test mainline (with daily
>>>> builds) and/or Andrew Morton's mmotm patchset.
>>>
>>> One thing that you could do that no one focuses on is building
>>> with some kconfig symbols disabled (ones that are typically enabled),
>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same
>>> time,
>>> just various/random combinations of them.
>>
>> and CONFIG_SYSRQ=n  (just found some errors due to this one)
> 
> You mean CONFIG_SYSRQ=n exactly and mandatory in every config or this
> was just an example?

Sorry about that.  Just make it random (sometimes disabled).

-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On 03/25/10 10:37, Piotr Hosowicz wrote:
>> Randy Dunlap wrote:
>>> On 03/18/10 08:40, Randy Dunlap wrote:
>>>> On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
>>>>
>>>>> On 03/16/10 12:02, Piotr Hosowicz wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I own quite strong PC, 4 core Pentium. I recently started to build my
>>>>>> kernel frequently, whenever I see a new patch on kernel.org I build
>>>>>> again. Bothers me that I do it only for doing it. Maybe it could be of
>>>>>> some help to the community? And if so, what would be more
>>>>>> appreciated -
>>>>>> linux-next patched kernel or gitN patched kernel? And how should I
>>>>>> configure the kernel for this purpose? I am afraid of putting all the
>>>>>> options on, yesterday I tried to put everything on as a module plus I
>>>>>> tinkered with some other options that seemed innocent. The kernel was
>>>>>> built but could not boot, saying that there was a problem with the
>>>>>> root
>>>>>> device, it could not recoginze /dev/sda2, which is my correct root
>>>>>> device. I did not investigate much and reverted to working kernel.
>>>>>>
>>>>>> Thanks in advance for your remarks.
>>>>> Many linux-next builds are done daily: see
>>>>>   http://kisskb.ellerman.id.au/kisskb/branch/9/
>>>>>
>>>>> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
>>>>> daily and fix most build errors that I find in them.
>>>>> (I am also using a quad-core PC with a cron job that finds the
>>>>> next day's linux-next, downloads it, and does 50 builds.)
>>>>>
>>>>> You are welcome to do the same or test mainline (with daily
>>>>> builds) and/or Andrew Morton's mmotm patchset.
>>>> One thing that you could do that no one focuses on is building
>>>> with some kconfig symbols disabled (ones that are typically enabled),
>>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same
>>>> time,
>>>> just various/random combinations of them.
>>> and CONFIG_SYSRQ=n  (just found some errors due to this one)
>> You mean CONFIG_SYSRQ=n exactly and mandatory in every config or this
>> was just an example?
> 
> Sorry about that.  Just make it random (sometimes disabled).

Ok.

The problem I face and want to overcome now is that not all options can 
be random, some options require to be not y or no a tall, but a string 
or a number. So my plan is that first thing to be done is to do make 
defconfig and put it as a template to be used by my scripts. Then only 
the options that you enumerated earlier will be randomized. Is this correct?

-- 
- Poszedłem wczoraj z żoną do ZOO
- I jak?
- Nie wzięli...
NP:  -
NB: 2.6.34-rc2-nx-20100325-next-20100325+

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/25/10 10:48, Piotr Hosowicz wrote:
> Randy Dunlap wrote:
>> On 03/25/10 10:37, Piotr Hosowicz wrote:
>>> Randy Dunlap wrote:
>>>> On 03/18/10 08:40, Randy Dunlap wrote:
>>>>> On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
>>>>>
>>>>>> On 03/16/10 12:02, Piotr Hosowicz wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> I own quite strong PC, 4 core Pentium. I recently started to
>>>>>>> build my
>>>>>>> kernel frequently, whenever I see a new patch on kernel.org I build
>>>>>>> again. Bothers me that I do it only for doing it. Maybe it could
>>>>>>> be of
>>>>>>> some help to the community? And if so, what would be more
>>>>>>> appreciated -
>>>>>>> linux-next patched kernel or gitN patched kernel? And how should I
>>>>>>> configure the kernel for this purpose? I am afraid of putting all
>>>>>>> the
>>>>>>> options on, yesterday I tried to put everything on as a module
>>>>>>> plus I
>>>>>>> tinkered with some other options that seemed innocent. The kernel
>>>>>>> was
>>>>>>> built but could not boot, saying that there was a problem with the
>>>>>>> root
>>>>>>> device, it could not recoginze /dev/sda2, which is my correct root
>>>>>>> device. I did not investigate much and reverted to working kernel.
>>>>>>>
>>>>>>> Thanks in advance for your remarks.
>>>>>> Many linux-next builds are done daily: see
>>>>>>   http://kisskb.ellerman.id.au/kisskb/branch/9/
>>>>>>
>>>>>> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
>>>>>> daily and fix most build errors that I find in them.
>>>>>> (I am also using a quad-core PC with a cron job that finds the
>>>>>> next day's linux-next, downloads it, and does 50 builds.)
>>>>>>
>>>>>> You are welcome to do the same or test mainline (with daily
>>>>>> builds) and/or Andrew Morton's mmotm patchset.
>>>>> One thing that you could do that no one focuses on is building
>>>>> with some kconfig symbols disabled (ones that are typically enabled),
>>>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>>>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same
>>>>> time,
>>>>> just various/random combinations of them.
>>>> and CONFIG_SYSRQ=n  (just found some errors due to this one)
>>> You mean CONFIG_SYSRQ=n exactly and mandatory in every config or this
>>> was just an example?
>>
>> Sorry about that.  Just make it random (sometimes disabled).
> 
> Ok.
> 
> The problem I face and want to overcome now is that not all options can
> be random, some options require to be not y or no a tall, but a string
> or a number. So my plan is that first thing to be done is to do make
> defconfig and put it as a template to be used by my scripts. Then only
> the options that you enumerated earlier will be randomized. Is this
> correct?

Yes, that's one way to approach it.

Another way (similar) would be to use a combination of "make randconfig"
with KCONFIG_ALLCONFIG.  See Documentation/kbuild/kconfig.txt for info
on KCONFIG_ALLCONFIG.  Basically it allows you to tell kconfig values for
a subset of config symbols to be used.


-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On 03/25/10 10:48, Piotr Hosowicz wrote:
>> Randy Dunlap wrote:
>>> On 03/25/10 10:37, Piotr Hosowicz wrote:
>>>> Randy Dunlap wrote:
>>>>> On 03/18/10 08:40, Randy Dunlap wrote:
>>>>>> On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
>>>>>>
>>>>>>> On 03/16/10 12:02, Piotr Hosowicz wrote:
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I own quite strong PC, 4 core Pentium. I recently started to
>>>>>>>> build my
>>>>>>>> kernel frequently, whenever I see a new patch on kernel.org I build
>>>>>>>> again. Bothers me that I do it only for doing it. Maybe it could
>>>>>>>> be of
>>>>>>>> some help to the community? And if so, what would be more
>>>>>>>> appreciated -
>>>>>>>> linux-next patched kernel or gitN patched kernel? And how should I
>>>>>>>> configure the kernel for this purpose? I am afraid of putting all
>>>>>>>> the
>>>>>>>> options on, yesterday I tried to put everything on as a module
>>>>>>>> plus I
>>>>>>>> tinkered with some other options that seemed innocent. The kernel
>>>>>>>> was
>>>>>>>> built but could not boot, saying that there was a problem with the
>>>>>>>> root
>>>>>>>> device, it could not recoginze /dev/sda2, which is my correct root
>>>>>>>> device. I did not investigate much and reverted to working kernel.
>>>>>>>>
>>>>>>>> Thanks in advance for your remarks.
>>>>>>> Many linux-next builds are done daily: see
>>>>>>>   http://kisskb.ellerman.id.au/kisskb/branch/9/
>>>>>>>
>>>>>>> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
>>>>>>> daily and fix most build errors that I find in them.
>>>>>>> (I am also using a quad-core PC with a cron job that finds the
>>>>>>> next day's linux-next, downloads it, and does 50 builds.)
>>>>>>>
>>>>>>> You are welcome to do the same or test mainline (with daily
>>>>>>> builds) and/or Andrew Morton's mmotm patchset.
>>>>>> One thing that you could do that no one focuses on is building
>>>>>> with some kconfig symbols disabled (ones that are typically enabled),
>>>>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>>>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>>>>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same
>>>>>> time,
>>>>>> just various/random combinations of them.
>>>>> and CONFIG_SYSRQ=n  (just found some errors due to this one)
>>>> You mean CONFIG_SYSRQ=n exactly and mandatory in every config or this
>>>> was just an example?
>>> Sorry about that.  Just make it random (sometimes disabled).
>> Ok.
>>
>> The problem I face and want to overcome now is that not all options can
>> be random, some options require to be not y or no a tall, but a string
>> or a number. So my plan is that first thing to be done is to do make
>> defconfig and put it as a template to be used by my scripts. Then only
>> the options that you enumerated earlier will be randomized. Is this
>> correct?
> 
> Yes, that's one way to approach it.
> 
> Another way (similar) would be to use a combination of "make randconfig"
> with KCONFIG_ALLCONFIG.  See Documentation/kbuild/kconfig.txt for info
> on KCONFIG_ALLCONFIG.  Basically it allows you to tell kconfig values for
> a subset of config symbols to be used.

Ok, but at present is not working properly, as expected. The scripts now 
are like this, I returned to randomizing with bash:

--- try-build.sh

#!/bin/bash

RCPT=phz@localhost
CPUCNT=$(cat /proc/cpuinfo | grep ^processor | wc -l)

function tidy(){
   rm ../results/.config 2>/dev/null
   rm ../results/build.log 2>/dev/null
   rm ../BUILDING-NOW 2>/dev/null
}

cd ~/kernel/linux
if test -f ../BUILDING-NOW ; then
   exit 0
else
   touch ../BUILDING-NOW
   make mrproper
   cat ../config.all | ../randomize-conf2.sh > ./.config
   make oldconfig
   cp .config ../results/
   DT=$(date +%y%m%d-%H%M%S)	
   make -j $CPUCNT vmlinux 2>&1 | tee ../results/build.log
   if test $? -ne 0 ; then
     (cat ../results/.config && cat ../results/build.log) | mail -s 
'Build failed at kernel phase' $RCPT
     mv ../results/.config ../results/.config.kf.$DT
     mv ../results/build.log ../results/build.log.$DT
     tidy
     exit 0
   fi
   make -j $CPUCNT modules 2>&1 | tee -a ../results/build.log
   if test $? -ne 0 ; then
     (cat ../results/.config && cat ../results/build.log) | mail -s 
'Build failed at modules phase' $RCPT
     mv ../results/.config ../results/.config.mf.$DT
     mv ../results/build.log ../results/build.log.$DT
     tidy
     exit 0
   fi
   cp ../results/build.log ./
   rm BUILDING-NOW
   echo OK | mail -s 'ok' $RCPT
   tidy

fi


--- randomize-conf2.sh:

#!/bin/bash

NETENABLED=0
function enable_or_not(){
   if test $RANDOM -lt 16383 ; then
     if test $1=CONFIG_NET ; then
       NETENABLED=1
       echo $1=y
       return
     fi
     if test $1=CONFIG_INET && test $NETENABLED -eq 1 ; then
       if test $RANDOM -lt 16383 ; then
         echo $1=y
       else
         echo '# '$1' is not set'
       fi
       return
     fi
   else
     echo '# '$1' is not set'
   fi
}

cat ../config.all | grep -v CONFIG_SMP | grep -v CONFIG_SYSFS | grep -v 
CONFIG_PROC_FS | grep -v CONFIG_PM | grep -v CONFIG_PCI | grep -v 
CONFIG_BLOCK | grep -v CONFIG_NET | grep -v CONFIG_INET | grep -v 
CONFIG_HOTPLUG > ./cfg.tmp

(
enable_or_not CONFIG_SMP
enable_or_not CONFIG_SYSFS
enable_or_not CONFIG_PROC_FS
enable_or_not CONFIG_PM
enable_or_not CONFIG_PCI
enable_or_not CONFIG_BLOCK
enable_or_not CONFIG_NET
enable_or_not CONFIG_INET
enable_or_not CONFIG_HOTPLUG
)
cat ./cfg.tmp

I launch try-build.sh, but it still asks me about unspecified options, 
my config.all is produced by make defconfig or make oldconfig, dosen't 
matter still.

Do you see what the problem is?


-- 
Z cyklu "Uroki demokracji", czyli pytania i odpowiedzi w teledurniejach:
- Ile kół ma trójkołowiec?
- Dwa.
NP: Miles Davis and John Coltrane - Two Bass Hit
NB: 2.6.34-rc2-nx-20100325-next-20100325+

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On 03/25/10 11:35, Piotr Hosowicz wrote:

>>>>>>> One thing that you could do that no one focuses on is building
>>>>>>> with some kconfig symbols disabled (ones that are typically
>>>>>>> enabled),
>>>>>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>>>>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but
>>>>>>> latter
>>>>>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same
>>>>>>> time,
>>>>>>> just various/random combinations of them.
>>>>>> and CONFIG_SYSRQ=n  (just found some errors due to this one)
>>>>> You mean CONFIG_SYSRQ=n exactly and mandatory in every config or this
>>>>> was just an example?
>>>> Sorry about that.  Just make it random (sometimes disabled).

The config symbol above should be CONFIG_MAGIC_SYSRQ.


> Ok, but at present is not working properly, as expected. The scripts now
> are like this, I returned to randomizing with bash:
> 
> --- try-build.sh
> 
> #!/bin/bash
> 
> RCPT=phz@localhost
> CPUCNT=$(cat /proc/cpuinfo | grep ^processor | wc -l)
> 
> function tidy(){
>   rm ../results/.config 2>/dev/null
>   rm ../results/build.log 2>/dev/null
>   rm ../BUILDING-NOW 2>/dev/null
> }
> 
> cd ~/kernel/linux
> if test -f ../BUILDING-NOW ; then
>   exit 0
> else
>   touch ../BUILDING-NOW
>   make mrproper
>   cat ../config.all | ../randomize-conf2.sh > ./.config
>   make oldconfig

I am using:
    yes '' | make oldconfig

>   cp .config ../results/
>   DT=$(date +%y%m%d-%H%M%S)   
>   make -j $CPUCNT vmlinux 2>&1 | tee ../results/build.log
>   if test $? -ne 0 ; then
>     (cat ../results/.config && cat ../results/build.log) | mail -s
> 'Build failed at kernel phase' $RCPT
>     mv ../results/.config ../results/.config.kf.$DT
>     mv ../results/build.log ../results/build.log.$DT
>     tidy
>     exit 0
>   fi
>   make -j $CPUCNT modules 2>&1 | tee -a ../results/build.log
>   if test $? -ne 0 ; then
>     (cat ../results/.config && cat ../results/build.log) | mail -s
> 'Build failed at modules phase' $RCPT
>     mv ../results/.config ../results/.config.mf.$DT
>     mv ../results/build.log ../results/build.log.$DT
>     tidy
>     exit 0
>   fi
>   cp ../results/build.log ./
>   rm BUILDING-NOW
>   echo OK | mail -s 'ok' $RCPT
>   tidy
> 
> fi
> 
> 
> --- randomize-conf2.sh:
> 
> #!/bin/bash
> 
> NETENABLED=0
> function enable_or_not(){
>   if test $RANDOM -lt 16383 ; then
>     if test $1=CONFIG_NET ; then
>       NETENABLED=1
>       echo $1=y
>       return
>     fi
>     if test $1=CONFIG_INET && test $NETENABLED -eq 1 ; then
>       if test $RANDOM -lt 16383 ; then
>         echo $1=y
>       else
>         echo '# '$1' is not set'
>       fi
>       return
>     fi
>   else
>     echo '# '$1' is not set'
>   fi
> }
> 
> cat ../config.all | grep -v CONFIG_SMP | grep -v CONFIG_SYSFS | grep -v
> CONFIG_PROC_FS | grep -v CONFIG_PM | grep -v CONFIG_PCI | grep -v
> CONFIG_BLOCK | grep -v CONFIG_NET | grep -v CONFIG_INET | grep -v
> CONFIG_HOTPLUG > ./cfg.tmp

Note that these grep -v's drop any config that contains CONFIG_whatever,
such as CONFIG_PCI_QUIRKS.  If you just want to drop those config
symbols and no others, I guess you would add "-w" to the grep command.

> 
> (
> enable_or_not CONFIG_SMP
> enable_or_not CONFIG_SYSFS
> enable_or_not CONFIG_PROC_FS
> enable_or_not CONFIG_PM
> enable_or_not CONFIG_PCI
> enable_or_not CONFIG_BLOCK
> enable_or_not CONFIG_NET
> enable_or_not CONFIG_INET
> enable_or_not CONFIG_HOTPLUG
> )
> cat ./cfg.tmp
> 
> I launch try-build.sh, but it still asks me about unspecified options,
> my config.all is produced by make defconfig or make oldconfig, dosen't
> matter still.
> 
> Do you see what the problem is?

It's working for me just be using
  yes '' | make oldconfig


-- 
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:

>>>>> Sorry about that.  Just make it random (sometimes disabled).
> 
> The config symbol above should be CONFIG_MAGIC_SYSRQ.

Ok, but as you said bedore I did not make any modifications to the 
scripts for this symbol.

>> Ok, but at present is not working properly, as expected. The scripts now
>> are like this, I returned to randomizing with bash:
>>
>> --- try-build.sh
>>
>> #!/bin/bash
>>
>> RCPT=phz@localhost
>> CPUCNT=$(cat /proc/cpuinfo | grep ^processor | wc -l)
>>
>> function tidy(){
>>   rm ../results/.config 2>/dev/null
>>   rm ../results/build.log 2>/dev/null
>>   rm ../BUILDING-NOW 2>/dev/null
>> }
>>
>> cd ~/kernel/linux
>> if test -f ../BUILDING-NOW ; then
>>   exit 0
>> else
>>   touch ../BUILDING-NOW
>>   make mrproper
>>   cat ../config.all | ../randomize-conf2.sh > ./.config
>>   make oldconfig
> 
> I am using:
>     yes '' | make oldconfig
> 
>>   cp .config ../results/
>>   DT=$(date +%y%m%d-%H%M%S)   
>>   make -j $CPUCNT vmlinux 2>&1 | tee ../results/build.log
>>   if test $? -ne 0 ; then
>>     (cat ../results/.config && cat ../results/build.log) | mail -s
>> 'Build failed at kernel phase' $RCPT
>>     mv ../results/.config ../results/.config.kf.$DT
>>     mv ../results/build.log ../results/build.log.$DT
>>     tidy
>>     exit 0
>>   fi
>>   make -j $CPUCNT modules 2>&1 | tee -a ../results/build.log
>>   if test $? -ne 0 ; then
>>     (cat ../results/.config && cat ../results/build.log) | mail -s
>> 'Build failed at modules phase' $RCPT
>>     mv ../results/.config ../results/.config.mf.$DT
>>     mv ../results/build.log ../results/build.log.$DT
>>     tidy
>>     exit 0
>>   fi
>>   cp ../results/build.log ./
>>   rm BUILDING-NOW
>>   echo OK | mail -s 'ok' $RCPT
>>   tidy
>>
>> fi
>>
>>
>> --- randomize-conf2.sh:
>>
>> #!/bin/bash
>>
>> NETENABLED=0
>> function enable_or_not(){
>>   if test $RANDOM -lt 16383 ; then
>>     if test $1=CONFIG_NET ; then
>>       NETENABLED=1
>>       echo $1=y
>>       return
>>     fi
>>     if test $1=CONFIG_INET && test $NETENABLED -eq 1 ; then
>>       if test $RANDOM -lt 16383 ; then
>>         echo $1=y
>>       else
>>         echo '# '$1' is not set'
>>       fi
>>       return
>>     fi
>>   else
>>     echo '# '$1' is not set'
>>   fi
>> }
>>
>> cat ../config.all | grep -v CONFIG_SMP | grep -v CONFIG_SYSFS | grep -v
>> CONFIG_PROC_FS | grep -v CONFIG_PM | grep -v CONFIG_PCI | grep -v
>> CONFIG_BLOCK | grep -v CONFIG_NET | grep -v CONFIG_INET | grep -v
>> CONFIG_HOTPLUG > ./cfg.tmp
> 
> Note that these grep -v's drop any config that contains CONFIG_whatever,
> such as CONFIG_PCI_QUIRKS.  If you just want to drop those config
> symbols and no others, I guess you would add "-w" to the grep command.

Ok, corrected, now there is a -w switch.

>> (
>> enable_or_not CONFIG_SMP
>> enable_or_not CONFIG_SYSFS
>> enable_or_not CONFIG_PROC_FS
>> enable_or_not CONFIG_PM
>> enable_or_not CONFIG_PCI
>> enable_or_not CONFIG_BLOCK
>> enable_or_not CONFIG_NET
>> enable_or_not CONFIG_INET
>> enable_or_not CONFIG_HOTPLUG
>> )
>> cat ./cfg.tmp
>>
>> I launch try-build.sh, but it still asks me about unspecified options,
>> my config.all is produced by make defconfig or make oldconfig, dosen't
>> matter still.
>>
>> Do you see what the problem is?
> 
> It's working for me just be using
>   yes '' | make oldconfig

Ok, it seems to be working now, but I do not understand why my version 
doesn't.


-- 
- Dlaczego hipopotamy mają okrągłe stopy?
- By łatwo było przeskakiwać z lilii na lilię.
NP: Alice In Chains - Take Her Out
NB: 2.6.34-rc2-git2

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Piotr Hosowicz wrote:

>> It's working for me just be using
>>   yes '' | make oldconfig
> 
> Ok, it seems to be working now, but I do not understand why my version 
> doesn't.

I became so desperate with the fact that I do not understand why my 
version does not work as expected and with the fact that I am not a 
Python nor perl nor bash hacker I begun to write the randomizer in plain 
old php5-cli. Wow, .. how lame you'd say. ;-) It's possible that I will 
write all thing in it.

-- 
W korytarzach kremlowskich Breżniew spotyka Susłowa. Susłow pyta:
- Leonid, wiesz, że jeden but masz żółty, a drugi czarny?
- Wiem, Misza, chciałem nawet zmienić, ale w domu mam to samo,
   jeden żółty i jeden czarny.
NP: Lenny Kravitz - Again
NB: 2.6.34-rc2-nx-20100326-next-20100326+

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Piotr Hosowicz wrote:
> Piotr Hosowicz wrote:
> 
>>> It's working for me just be using
>>>   yes '' | make oldconfig
>>
>> Ok, it seems to be working now, but I do not understand why my version 
>> doesn't.
> 
> I became so desperate with the fact that I do not understand why my 
> version does not work as expected and with the fact that I am not a 
> Python nor perl nor bash hacker I begun to write the randomizer in plain 
> old php5-cli. Wow, .. how lame you'd say. ;-) It's possible that I will 
> write all thing in it.

Ok. That's all, I give up. I do not understand how this fscking thing 
works. I do make mrproper inside, then either gzip -cd /proc/config.gz > 
./.config followed by make oldconfig or make defconfig and then I 
execute the following script:

#!/usr/bin/php
<?

function yesno(){
	$x = rand();
	if ($x<getrandmax()/2){ return true; }else{ return false; }
}

function enable_or_not($atoken){
	if (yesno()){
		switch ($atoken){
			case "CONFIG_NET":
				$netenabled = true;
				print("CONFIG_NET=y\n");
				break;
			case "CONFIG_INET":
				if (yesno() and $netenabled){
					print("CONFIG_INET=y\n");
				}else print("# CONFIG_INET is not set\n");
				break;
			default:
				print($atoken."=y\n");
		}
	}else{
		print("# ".$atoken." is not set\n");
	}
}

$stdin = fopen("php://stdin", "r");
while ($inline = fgets($stdin)){
	$m = preg_match("/^(CONFIG_\w+)=([y|n])$/", $inline, $matches);
	if ($m){
		$option = $matches[1];
	}else{
		$m = preg_match("/^# (CONFIG_\w+) is not set$/", $inline, $matches);
		if ($m) { $option = $matches[1]; }else{ $option = false; };
	};
	switch ($option){
		case "CONFIG_MODULES":
			print "CONFIG_MODULES=y";
			break;
		case "CONFIG_NET":
			enable_or_not("CONFIG_NET");
			break;
		case "CONFIG_INET":
			enable_or_not("CONFIG_INET");
			break;
		case "CONFIG_SMP":
			enable_or_not("CONFIG_SMP");
			break;
		case "CONFIG_SYSFS":
			enable_or_not("CONFIG_SYSFS");
			break;
		case "CONFIG_PROC_FS":
			enable_or_not("CONFIG_PROC_FS");
			break;
		case "CONFIG_PM":
			enable_or_not("CONFIG_PM");
			break;
		case "CONFIG_PCI":
			enable_or_not("CONFIG_PCI");
		case "CONFIG_BLOCK":
			enable_or_not("CONFIG_BLOCK");
		case "CONFIG_HOTPLUG":
			enable_or_not("CONFIG_HOTPLUG");
		default:
			print($inline);
	} // switch
}; // while

?>

Nevertheless when I try to start building make again asks me for options 
which it should know, as I presume. How it works?


Regards,

Piotr Hosowicz

-- 
"Chcemy waszego dobra!" - powiedział lider
socjaldemokratów. Zaniepokojeni obywatele
zaczeli ukrywać swoje dobra w bezpiecznych
miejscach.
NP: Lenny Kravitz - Is there any love in your heart
NB: 2.6.34-rc2-git3

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Piotr Hosowicz wrote:
> Piotr Hosowicz wrote:
>> Piotr Hosowicz wrote:
>>
>>>> It's working for me just be using
>>>>   yes '' | make oldconfig
>>>
>>> Ok, it seems to be working now, but I do not understand why my 
>>> version doesn't.
>>
>> I became so desperate with the fact that I do not understand why my 
>> version does not work as expected and with the fact that I am not a 
>> Python nor perl nor bash hacker I begun to write the randomizer in 
>> plain old php5-cli. Wow, .. how lame you'd say. ;-) It's possible that 
>> I will write all thing in it.
> 
> Ok. That's all, I give up. I do not understand how this fscking thing 
> works. I do make mrproper inside, then either gzip -cd /proc/config.gz > 
> ./.config followed by make oldconfig or make defconfig and then I 
> execute the following script:
> 
> #!/usr/bin/php
> <?
> 
> function yesno(){
>     $x = rand();
>     if ($x<getrandmax()/2){ return true; }else{ return false; }
> }
> 
> function enable_or_not($atoken){
>     if (yesno()){
>         switch ($atoken){
>             case "CONFIG_NET":
>                 $netenabled = true;
>                 print("CONFIG_NET=y\n");
>                 break;
>             case "CONFIG_INET":
>                 if (yesno() and $netenabled){
>                     print("CONFIG_INET=y\n");
>                 }else print("# CONFIG_INET is not set\n");
>                 break;
>             default:
>                 print($atoken."=y\n");
>         }
>     }else{
>         print("# ".$atoken." is not set\n");
>     }
> }
> 
> $stdin = fopen("php://stdin", "r");
> while ($inline = fgets($stdin)){
>     $m = preg_match("/^(CONFIG_\w+)=([y|n])$/", $inline, $matches);
>     if ($m){
>         $option = $matches[1];
>     }else{
>         $m = preg_match("/^# (CONFIG_\w+) is not set$/", $inline, 
> $matches);
>         if ($m) { $option = $matches[1]; }else{ $option = false; };
>     };
>     switch ($option){
>         case "CONFIG_MODULES":
>             print "CONFIG_MODULES=y";
>             break;
>         case "CONFIG_NET":
>             enable_or_not("CONFIG_NET");
>             break;
>         case "CONFIG_INET":
>             enable_or_not("CONFIG_INET");
>             break;
>         case "CONFIG_SMP":
>             enable_or_not("CONFIG_SMP");
>             break;
>         case "CONFIG_SYSFS":
>             enable_or_not("CONFIG_SYSFS");
>             break;
>         case "CONFIG_PROC_FS":
>             enable_or_not("CONFIG_PROC_FS");
>             break;
>         case "CONFIG_PM":
>             enable_or_not("CONFIG_PM");
>             break;
>         case "CONFIG_PCI":
>             enable_or_not("CONFIG_PCI");
>         case "CONFIG_BLOCK":
>             enable_or_not("CONFIG_BLOCK");
>         case "CONFIG_HOTPLUG":
>             enable_or_not("CONFIG_HOTPLUG");

Sorry, 3 * break; should go where appropriate, I noticed it just now.

Regards,

Piotr Hosowicz



-- 
Demokracja to kult szakali wyznawany przez osły (Henry Louis Mencken)
NP: Lenny Kravitz - Let love rule
NB: 2.6.34-rc2-git3

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Randy Dunlap]

On Thu, 25 Mar 2010 10:29:35 -0700 Randy Dunlap wrote:

> On 03/18/10 08:40, Randy Dunlap wrote:
> > On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
> > 
> >> On 03/16/10 12:02, Piotr Hosowicz wrote:
> >>> Hello,
> >>>
> >>> I own quite strong PC, 4 core Pentium. I recently started to build my
> >>> kernel frequently, whenever I see a new patch on kernel.org I build
> >>> again. Bothers me that I do it only for doing it. Maybe it could be of
> >>> some help to the community? And if so, what would be more appreciated -
> >>> linux-next patched kernel or gitN patched kernel? And how should I
> >>> configure the kernel for this purpose? I am afraid of putting all the
> >>> options on, yesterday I tried to put everything on as a module plus I
> >>> tinkered with some other options that seemed innocent. The kernel was
> >>> built but could not boot, saying that there was a problem with the root
> >>> device, it could not recoginze /dev/sda2, which is my correct root
> >>> device. I did not investigate much and reverted to working kernel.
> >>>
> >>> Thanks in advance for your remarks.
> >>
> >> Many linux-next builds are done daily: see
> >>   http://kisskb.ellerman.id.au/kisskb/branch/9/
> >>
> >> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
> >> daily and fix most build errors that I find in them.
> >> (I am also using a quad-core PC with a cron job that finds the
> >> next day's linux-next, downloads it, and does 50 builds.)
> >>
> >> You are welcome to do the same or test mainline (with daily
> >> builds) and/or Andrew Morton's mmotm patchset.
> > 
> > 
> > One thing that you could do that no one focuses on is building
> > with some kconfig symbols disabled (ones that are typically enabled),
> > such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
> > CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
> > with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same time,
> > just various/random combinations of them.
> 
> and CONFIG_SYSRQ=n  (just found some errors due to this one)

and CONFIG_INPUT randomly enabled/disabled

Basically any major subsystem that can be enabled/disabled should be
tested.

---
~Randy

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On Thu, 25 Mar 2010 10:29:35 -0700 Randy Dunlap wrote:
> 
>> On 03/18/10 08:40, Randy Dunlap wrote:
>>> On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
>>>
>>>> On 03/16/10 12:02, Piotr Hosowicz wrote:
>>>>> Hello,
>>>>>
>>>>> I own quite strong PC, 4 core Pentium. I recently started to build my
>>>>> kernel frequently, whenever I see a new patch on kernel.org I build
>>>>> again. Bothers me that I do it only for doing it. Maybe it could be of
>>>>> some help to the community? And if so, what would be more appreciated -
>>>>> linux-next patched kernel or gitN patched kernel? And how should I
>>>>> configure the kernel for this purpose? I am afraid of putting all the
>>>>> options on, yesterday I tried to put everything on as a module plus I
>>>>> tinkered with some other options that seemed innocent. The kernel was
>>>>> built but could not boot, saying that there was a problem with the root
>>>>> device, it could not recoginze /dev/sda2, which is my correct root
>>>>> device. I did not investigate much and reverted to working kernel.
>>>>>
>>>>> Thanks in advance for your remarks.
>>>> Many linux-next builds are done daily: see
>>>>   http://kisskb.ellerman.id.au/kisskb/branch/9/
>>>>
>>>> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
>>>> daily and fix most build errors that I find in them.
>>>> (I am also using a quad-core PC with a cron job that finds the
>>>> next day's linux-next, downloads it, and does 50 builds.)
>>>>
>>>> You are welcome to do the same or test mainline (with daily
>>>> builds) and/or Andrew Morton's mmotm patchset.
>>>
>>> One thing that you could do that no one focuses on is building
>>> with some kconfig symbols disabled (ones that are typically enabled),
>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same time,
>>> just various/random combinations of them.
>> and CONFIG_SYSRQ=n  (just found some errors due to this one)
> 
> and CONFIG_INPUT randomly enabled/disabled
> 
> Basically any major subsystem that can be enabled/disabled should be
> tested.

Randy, but as for now (please find my messages) I do not know how to 
randomly generate .config, I do not understand how make oldconfig works. 
So I am stopped.

Regards,

Piotr Hosowicz

-- 
"Chcemy waszego dobra!" - powiedział lider
socjaldemokratów. Zaniepokojeni obywatele
zaczeli ukrywać swoje dobra w bezpiecznych
miejscach.
NP: Jane's Addiction - Everybody's Friend
NB: 2.6.34-rc3-next-20100401+

Re: Maybe my frequent kernel building could be of some help to the community? And how to build?

[Piotr Hosowicz]

Piotr Hosowicz wrote:
> Randy Dunlap wrote:
>> On Thu, 25 Mar 2010 10:29:35 -0700 Randy Dunlap wrote:
>>
>>> On 03/18/10 08:40, Randy Dunlap wrote:
>>>> On Tue, 16 Mar 2010 12:24:35 -0700 Randy Dunlap wrote:
>>>>
>>>>> On 03/16/10 12:02, Piotr Hosowicz wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I own quite strong PC, 4 core Pentium. I recently started to build my
>>>>>> kernel frequently, whenever I see a new patch on kernel.org I build
>>>>>> again. Bothers me that I do it only for doing it. Maybe it could 
>>>>>> be of
>>>>>> some help to the community? And if so, what would be more 
>>>>>> appreciated -
>>>>>> linux-next patched kernel or gitN patched kernel? And how should I
>>>>>> configure the kernel for this purpose? I am afraid of putting all the
>>>>>> options on, yesterday I tried to put everything on as a module plus I
>>>>>> tinkered with some other options that seemed innocent. The kernel was
>>>>>> built but could not boot, saying that there was a problem with the 
>>>>>> root
>>>>>> device, it could not recoginze /dev/sda2, which is my correct root
>>>>>> device. I did not investigate much and reverted to working kernel.
>>>>>>
>>>>>> Thanks in advance for your remarks.
>>>>> Many linux-next builds are done daily: see
>>>>>   http://kisskb.ellerman.id.au/kisskb/branch/9/
>>>>>
>>>>> and then I do 25 x86_32 randconfigs and 25 x64_64 randconfigs
>>>>> daily and fix most build errors that I find in them.
>>>>> (I am also using a quad-core PC with a cron job that finds the
>>>>> next day's linux-next, downloads it, and does 50 builds.)
>>>>>
>>>>> You are welcome to do the same or test mainline (with daily
>>>>> builds) and/or Andrew Morton's mmotm patchset.
>>>>
>>>> One thing that you could do that no one focuses on is building
>>>> with some kconfig symbols disabled (ones that are typically enabled),
>>>> such as CONFIG_SMP=n, CONFIG_SYSFS=n, CONFIG_PROC_FS=n, CONFIG_PM=n,
>>>> CONFIG_PCI=n, CONFIG_BLOCK=n, CONFIG_NET=n, CONFIG_INET=n (but latter
>>>> with CONFIG_NET=y), CONFIG_HOTPLUG=n.  Not all of these at the same 
>>>> time,
>>>> just various/random combinations of them.
>>> and CONFIG_SYSRQ=n  (just found some errors due to this one)
>>
>> and CONFIG_INPUT randomly enabled/disabled
>>
>> Basically any major subsystem that can be enabled/disabled should be
>> tested.
> 
> Randy, but as for now (please find my messages) I do not know how to 
> randomly generate .config, I do not understand how make oldconfig works. 
> So I am stopped.

Randy, sorry, I just now saw, that You advised to use:

yes '' | make oldconfig

I got it wrong, and used - to my confusion:

yes | make oldconfig

I'll get to it tommorrow.

Godd night.

Piotr Hosowicz

-- 
TV: "Jeszcze trzy ruchy i Otylia będzie szczęśliwa."
NP: Alice In Chains - All Secrets Known
NB: 2.6.34-rc3-next-20100401+

Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Hello,

Today I had built a new next kernel with these parameters. I did not get 
what I expected

aapi205:/usr/src/linux# cat /proc/cmdline
vga=791 root=/dev/sda2 ro quiet

CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="vga=791"
# CONFIG_CMDLINE_OVERRIDE is not set

Is the order important for kernel parameters?

-- 
Familiada:
- Zwierze w paski?
- Biedronka!
NP: Patrick O'Hearn - Magnificent River
NB: 2.6.34-rc2-next-20100329+

Re: Is root kernel parameter expected to be the first one or something?

[Randy Dunlap]

On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:

> Hello,
> 
> Today I had built a new next kernel with these parameters. I did not get 
> what I expected

I don't think I understand your question.
What did you expect?


> aapi205:/usr/src/linux# cat /proc/cmdline
> vga=791 root=/dev/sda2 ro quiet
> 
> CONFIG_CMDLINE_BOOL=y
> CONFIG_CMDLINE="vga=791"
> # CONFIG_CMDLINE_OVERRIDE is not set
> 
> Is the order important for kernel parameters?

Not that I can see or know of.

> -- 
> NB: 2.6.34-rc2-next-20100329+


---
~Randy

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
> 
>> Hello,
>>
>> Today I had built a new next kernel with these parameters. I did not get 
>> what I expected
> 
> I don't think I understand your question.
> What did you expect?

I expected higher resolution console, smaller font etc

Regards,

Piotr Hosowicz

-- 
"Pirotechnicy zdetonowali na warszawskim Okęciu podejrzane ładunki,
znalezione przy porzuconym motocyklu. Wszystko wskazuje na to, że
był to fałszywy alarm". Z polskiego na nasze: "rozp* komuś motor".
NP: Patrick O'Hearn - Approaching Summit
NB: 2.6.34-rc2-next-20100329+

Re: Is root kernel parameter expected to be the first one or something?

[Randy Dunlap]

On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:

> Randy Dunlap wrote:
> > On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
> > 
> >> Hello,
> >>
> >> Today I had built a new next kernel with these parameters. I did not get 
> >> what I expected
> > 
> > I don't think I understand your question.
> > What did you expect?
> 
> I expected higher resolution console, smaller font etc

Boy was I confused.  I thought that your question was about the root=
kernel boot parameter.

Well, there are several questions to be asked.  and one more comment.

1.  what video (framebuffer) driver are you using?
2.  is it builtin the kernel image or is it a loadable module?
3.  have you read Documentation/svga.txt and Documentation/fb/{fbcon,vesafb}.txt ?


And my comment is that your question (about video) would be better on the
linux-fbdev@vger.kernel.org mailing list.  It's not about kbuild/kconfig,
unless kconfig is not saving the build parameters correctly...


---
~Randy

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
> 
>> Randy Dunlap wrote:
>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
>>>
>>>> Hello,
>>>>
>>>> Today I had built a new next kernel with these parameters. I did not get 
>>>> what I expected
>>> I don't think I understand your question.
>>> What did you expect?
>> I expected higher resolution console, smaller font etc
> 
> Boy was I confused.  I thought that your question was about the root=
> kernel boot parameter.
> 
> Well, there are several questions to be asked.  and one more comment.
> 
> 1.  what video (framebuffer) driver are you using?

Ashamed to say, but I do not know. vga=791 works perfectly when I 
specifiy it via GRUB modification, either during pre-booting phase or in 
menu.lst. I thought that it would work if I enable it by the oprions I 
provided in the previous message.

> 2.  is it builtin the kernel image or is it a loadable module?

Loadable mofule I suppose, I can see nvidia.ko in /lib/modules/... - I 
install Nbvidia driver with Nvidia tool each time after kernel change. 
Each time the module has to be compiled anew.

> 3.  have you read Documentation/svga.txt and Documentation/fb/{fbcon,vesafb}.txt ?

No, I havent, yet.

> And my comment is that your question (about video) would be better on the
> linux-fbdev@vger.kernel.org mailing list.  It's not about kbuild/kconfig,
> unless kconfig is not saving the build parameters correctly...

But I don't know if it is a fb problem, I quoted kernel config 
parameters I used, may be there is a problem with them?

Regards,

Piotr Hosowicz

-- 
 > Jeden z powodów, dla których KRK nie był skłonny do
 > oddawania Biblii w ręce pospólstwa. Po rozmowie z
 > Jehowitami często można zrozumieć, dlaczego.
Tak. Ja na przykład zrozumiałem że Jan Chrzciciel był
kolejarzem - bo: "z kolei udał się nad Jordan".
NP: Mark Knopfler - So Far From The Clyde
NB: 2.6.34-rc2-next-20100329+

Re: Is root kernel parameter expected to be the first one or something?

[Randy Dunlap]

On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:

> Randy Dunlap wrote:
> > On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
> > 
> >> Randy Dunlap wrote:
> >>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
> >>>
> >>>> Hello,
> >>>>
> >>>> Today I had built a new next kernel with these parameters. I did not get 
> >>>> what I expected
> >>> I don't think I understand your question.
> >>> What did you expect?
> >> I expected higher resolution console, smaller font etc
> > 
> > Boy was I confused.  I thought that your question was about the root=
> > kernel boot parameter.
> > 
> > Well, there are several questions to be asked.  and one more comment.
> > 
> > 1.  what video (framebuffer) driver are you using?
> 
> Ashamed to say, but I do not know. vga=791 works perfectly when I 
> specifiy it via GRUB modification, either during pre-booting phase or in 
> menu.lst. I thought that it would work if I enable it by the oprions I 
> provided in the previous message.

That does sound, hm, suspicious.

> > 2.  is it builtin the kernel image or is it a loadable module?
> 
> Loadable mofule I suppose, I can see nvidia.ko in /lib/modules/... - I 
> install Nbvidia driver with Nvidia tool each time after kernel change. 
> Each time the module has to be compiled anew.

So this nvidia driver supports "vga=<value>" ?

> > 3.  have you read Documentation/svga.txt and Documentation/fb/{fbcon,vesafb}.txt ?
> 
> No, I havent, yet.


> > And my comment is that your question (about video) would be better on the
> > linux-fbdev@vger.kernel.org mailing list.  It's not about kbuild/kconfig,
> > unless kconfig is not saving the build parameters correctly...
> 
> But I don't know if it is a fb problem, I quoted kernel config 
> parameters I used, may be there is a problem with them?


Well, to me, all of the questions are about video/framebuffer usage.
That's why I recommended that mailing list.

Although if you are using the binary-only nvidia driver, it will probably
be difficult to help you.

---
~Randy

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:
> 
>> Randy Dunlap wrote:
>>> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
>>>
>>>> Randy Dunlap wrote:
>>>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Today I had built a new next kernel with these parameters. I did not get 
>>>>>> what I expected
>>>>> I don't think I understand your question.
>>>>> What did you expect?
>>>> I expected higher resolution console, smaller font etc
>>> Boy was I confused.  I thought that your question was about the root=
>>> kernel boot parameter.
>>>
>>> Well, there are several questions to be asked.  and one more comment.
>>>
>>> 1.  what video (framebuffer) driver are you using?
>> Ashamed to say, but I do not know. vga=791 works perfectly when I 
>> specifiy it via GRUB modification, either during pre-booting phase or in 
>> menu.lst. I thought that it would work if I enable it by the oprions I 
>> provided in the previous message.
> 
> That does sound, hm, suspicious.
> 
>>> 2.  is it builtin the kernel image or is it a loadable module?
>> Loadable mofule I suppose, I can see nvidia.ko in /lib/modules/... - I 
>> install Nbvidia driver with Nvidia tool each time after kernel change. 
>> Each time the module has to be compiled anew.
> 
> So this nvidia driver supports "vga=<value>" ?

I suppose it does because it works perfectly when I put it in menu.lst 
file in GRUB config or specify it in GRUB before the kernel boots.

>>> 3.  have you read Documentation/svga.txt and Documentation/fb/{fbcon,vesafb}.txt ?
>> No, I havent, yet.
> 
> 
>>> And my comment is that your question (about video) would be better on the
>>> linux-fbdev@vger.kernel.org mailing list.  It's not about kbuild/kconfig,
>>> unless kconfig is not saving the build parameters correctly...
>> But I don't know if it is a fb problem, I quoted kernel config 
>> parameters I used, may be there is a problem with them?
> 
> 
> Well, to me, all of the questions are about video/framebuffer usage.
> That's why I recommended that mailing list.

But I read a bit and this is not a case of framebuffer, pkain svga mode.

> Although if you are using the binary-only nvidia driver, it will probably
> be difficult to help you.

It is not binary-only, I have to rebuild the driver in every kernel change.

Regards,

Piotr Hosowicz

-- 
"Chcemy waszego dobra!" - powiedział lider
socjaldemokratów. Zaniepokojeni obywatele
zaczeli ukrywać swoje dobra w bezpiecznych
miejscach.
NP: Mark Knopfler - Hard Shoulder
NB: 2.6.34-rc2-next-20100329+

Re: Is root kernel parameter expected to be the first one or something?

[Randy Dunlap]

On Tue, 30 Mar 2010 00:44:28 +0200 Piotr Hosowicz wrote:

> Randy Dunlap wrote:
> > On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:
> > 
> >> Randy Dunlap wrote:
> >>> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
> >>>
> >>>> Randy Dunlap wrote:
> >>>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
> >>>>>
> >>>>>> Hello,
> >>>>>>
> >>>>>> Today I had built a new next kernel with these parameters. I did not get 
> >>>>>> what I expected
> >>>>> I don't think I understand your question.
> >>>>> What did you expect?
> >>>> I expected higher resolution console, smaller font etc
> >>> Boy was I confused.  I thought that your question was about the root=
> >>> kernel boot parameter.
> >>>
> >>> Well, there are several questions to be asked.  and one more comment.
> >>>
> >>> 1.  what video (framebuffer) driver are you using?
> >> Ashamed to say, but I do not know. vga=791 works perfectly when I 
> >> specifiy it via GRUB modification, either during pre-booting phase or in 
> >> menu.lst. I thought that it would work if I enable it by the oprions I 
> >> provided in the previous message.
> > 
> > That does sound, hm, suspicious.


OK, the above is the main problem, right?
If so, I'll try to find time to test it.


> >>> 2.  is it builtin the kernel image or is it a loadable module?
> >> Loadable mofule I suppose, I can see nvidia.ko in /lib/modules/... - I 
> >> install Nbvidia driver with Nvidia tool each time after kernel change. 
> >> Each time the module has to be compiled anew.
> > 
> > So this nvidia driver supports "vga=<value>" ?
> 
> I suppose it does because it works perfectly when I put it in menu.lst 
> file in GRUB config or specify it in GRUB before the kernel boots.
> 
> >>> 3.  have you read Documentation/svga.txt and Documentation/fb/{fbcon,vesafb}.txt ?
> >> No, I havent, yet.
> > 
> > 
> >>> And my comment is that your question (about video) would be better on the
> >>> linux-fbdev@vger.kernel.org mailing list.  It's not about kbuild/kconfig,
> >>> unless kconfig is not saving the build parameters correctly...
> >> But I don't know if it is a fb problem, I quoted kernel config 
> >> parameters I used, may be there is a problem with them?
> > 
> > 
> > Well, to me, all of the questions are about video/framebuffer usage.
> > That's why I recommended that mailing list.
> 
> But I read a bit and this is not a case of framebuffer, pkain svga mode.
> 
> > Although if you are using the binary-only nvidia driver, it will probably
> > be difficult to help you.
> 
> It is not binary-only, I have to rebuild the driver in every kernel change.


Where can I download the driver to look at it, please?


---
~Randy

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On Tue, 30 Mar 2010 00:44:28 +0200 Piotr Hosowicz wrote:
> 
>> Randy Dunlap wrote:
>>> On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:
>>>
>>>> Randy Dunlap wrote:
>>>>> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
>>>>>
>>>>>> Randy Dunlap wrote:
>>>>>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> Today I had built a new next kernel with these parameters. I did not get 
>>>>>>>> what I expected
>>>>>>> I don't think I understand your question.
>>>>>>> What did you expect?
>>>>>> I expected higher resolution console, smaller font etc
>>>>> Boy was I confused.  I thought that your question was about the root=
>>>>> kernel boot parameter.
>>>>>
>>>>> Well, there are several questions to be asked.  and one more comment.
>>>>>
>>>>> 1.  what video (framebuffer) driver are you using?
>>>> Ashamed to say, but I do not know. vga=791 works perfectly when I 
>>>> specifiy it via GRUB modification, either during pre-booting phase or in 
>>>> menu.lst. I thought that it would work if I enable it by the oprions I 
>>>> provided in the previous message.
>>> That does sound, hm, suspicious.
> 
> 
> OK, the above is the main problem, right?
> If so, I'll try to find time to test it.

Thanks in advance.

>>>>> 2.  is it builtin the kernel image or is it a loadable module?
>>>> Loadable mofule I suppose, I can see nvidia.ko in /lib/modules/... - I 
>>>> install Nbvidia driver with Nvidia tool each time after kernel change. 
>>>> Each time the module has to be compiled anew.
>>> So this nvidia driver supports "vga=<value>" ?
>> I suppose it does because it works perfectly when I put it in menu.lst 
>> file in GRUB config or specify it in GRUB before the kernel boots.
>>
>>>>> 3.  have you read Documentation/svga.txt and Documentation/fb/{fbcon,vesafb}.txt ?
>>>> No, I havent, yet.
>>>
>>>>> And my comment is that your question (about video) would be better on the
>>>>> linux-fbdev@vger.kernel.org mailing list.  It's not about kbuild/kconfig,
>>>>> unless kconfig is not saving the build parameters correctly...
>>>> But I don't know if it is a fb problem, I quoted kernel config 
>>>> parameters I used, may be there is a problem with them?
>>>
>>> Well, to me, all of the questions are about video/framebuffer usage.
>>> That's why I recommended that mailing list.
>> But I read a bit and this is not a case of framebuffer, pkain svga mode.
>>
>>> Although if you are using the binary-only nvidia driver, it will probably
>>> be difficult to help you.
>> It is not binary-only, I have to rebuild the driver in every kernel change.
> 
> 
> Where can I download the driver to look at it, please?

http://www.nvidia.com/object/linux_display_amd64_195.36.15.html

You download the driver and ru it :

bash downloaded_file.run


-- 
Janusz Korwin-Mikke:
"Generalnie rzecz biorąc, ja jestem w jednej dziedzinie za
równouprawnieniem, a mianowicie: żeby w małżeństwie było
50% mężczyzn i 50% kobiet."
NP: Mark Knopfler - Before Gas & TV
NB: 2.6.34-rc2-next-20100329+

Re: Is root kernel parameter expected to be the first one or something?

[Randy Dunlap]

On Tue, 30 Mar 2010 00:55:34 +0200 Piotr Hosowicz wrote:

> Randy Dunlap wrote:
> > On Tue, 30 Mar 2010 00:44:28 +0200 Piotr Hosowicz wrote:
> > 
> >> Randy Dunlap wrote:
> >>> On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:
> >>>
> >>>> Randy Dunlap wrote:
> >>>>> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
> >>>>>
> >>>>>> Randy Dunlap wrote:
> >>>>>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
> >>>>>>>
> >>>>>>>> Hello,
> >>>>>>>>
> >>>>>>>> Today I had built a new next kernel with these parameters. I did not get 
> >>>>>>>> what I expected
> >>>>>>> I don't think I understand your question.
> >>>>>>> What did you expect?
> >>>>>> I expected higher resolution console, smaller font etc
> >>>>> Boy was I confused.  I thought that your question was about the root=
> >>>>> kernel boot parameter.
> >>>>>
> >>>>> Well, there are several questions to be asked.  and one more comment.
> >>>>>
> >>>>> 1.  what video (framebuffer) driver are you using?
> >>>> Ashamed to say, but I do not know. vga=791 works perfectly when I 
> >>>> specifiy it via GRUB modification, either during pre-booting phase or in 
> >>>> menu.lst. I thought that it would work if I enable it by the oprions I 
> >>>> provided in the previous message.
> >>> That does sound, hm, suspicious.
> > 
> > 
> > OK, the above is the main problem, right?
> > If so, I'll try to find time to test it.
> 
> Thanks in advance.
> 
> >>>>> 2.  is it builtin the kernel image or is it a loadable module?
> >>>> Loadable mofule I suppose, I can see nvidia.ko in /lib/modules/... - I 
> >>>> install Nbvidia driver with Nvidia tool each time after kernel change. 
> >>>> Each time the module has to be compiled anew.
> >>> So this nvidia driver supports "vga=<value>" ?
> >> I suppose it does because it works perfectly when I put it in menu.lst 
> >> file in GRUB config or specify it in GRUB before the kernel boots.
> >>
> >>>>> 3.  have you read Documentation/svga.txt and Documentation/fb/{fbcon,vesafb}.txt ?
> >>>> No, I havent, yet.
> >>>
> >>>>> And my comment is that your question (about video) would be better on the
> >>>>> linux-fbdev@vger.kernel.org mailing list.  It's not about kbuild/kconfig,
> >>>>> unless kconfig is not saving the build parameters correctly...
> >>>> But I don't know if it is a fb problem, I quoted kernel config 
> >>>> parameters I used, may be there is a problem with them?
> >>>
> >>> Well, to me, all of the questions are about video/framebuffer usage.
> >>> That's why I recommended that mailing list.
> >> But I read a bit and this is not a case of framebuffer, pkain svga mode.
> >>
> >>> Although if you are using the binary-only nvidia driver, it will probably
> >>> be difficult to help you.
> >> It is not binary-only, I have to rebuild the driver in every kernel change.
> > 
> > 
> > Where can I download the driver to look at it, please?
> 
> http://www.nvidia.com/object/linux_display_amd64_195.36.15.html
> 
> You download the driver and ru it :
> 
> bash downloaded_file.run

but a large part of that file appears to be a pre-compiled binary.

---
~Randy

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Randy Dunlap wrote:

>> You download the driver and ru it :
>>
>> bash downloaded_file.run
> 
> but a large part of that file appears to be a pre-compiled binary.
> 

Yes, it is sort of runnable shell archive. It conatins binary drivers 
matching some common distro-supplied kernels and if it cannot math one 
it builds anew the driver for the system where it is run.

Regards,

Piotr Hosowicz

-- 
TV: "W tej chwili, że się tak wyrażę, zaliczonych mamy 17 zawodniczek."
NP: Mark Knopfler - Remembrance Day
NB: 2.6.34-rc2-next-20100329+

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Randy Dunlap wrote:
> On Tue, 30 Mar 2010 00:44:28 +0200 Piotr Hosowicz wrote:
> 
>> Randy Dunlap wrote:
>>> On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:
>>>
>>>> Randy Dunlap wrote:
>>>>> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
>>>>>
>>>>>> Randy Dunlap wrote:
>>>>>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> Today I had built a new next kernel with these parameters. I did not get 
>>>>>>>> what I expected
>>>>>>> I don't think I understand your question.
>>>>>>> What did you expect?
>>>>>> I expected higher resolution console, smaller font etc
>>>>> Boy was I confused.  I thought that your question was about the root=
>>>>> kernel boot parameter.
>>>>>
>>>>> Well, there are several questions to be asked.  and one more comment.
>>>>>
>>>>> 1.  what video (framebuffer) driver are you using?
>>>> Ashamed to say, but I do not know. vga=791 works perfectly when I 
>>>> specifiy it via GRUB modification, either during pre-booting phase or in 
>>>> menu.lst. I thought that it would work if I enable it by the oprions I 
>>>> provided in the previous message.
>>> That does sound, hm, suspicious.
> 
> 
> OK, the above is the main problem, right?
> If so, I'll try to find time to test it.

aapi205:/usr/src/linux# gzip -cd /proc/config.gz | grep -A 1 vga=791
CONFIG_CMDLINE="root=/dev/sda2 ro quiet vga=791"
CONFIG_CMDLINE_OVERRIDE=y
aapi205:/usr/src/linux# cat /proc/cmdline
root=/dev/sda2 ro quiet vga=791

First if all I tried to test whether the overriding code works at all, 
and it seems it works, I am now booted having edited 
root=/dev/nonexistent at GRUB prompt, and it seems that the values set 
at build time have overriden values set at GRUB prompt. But the vga=791 
parameter does not work at all, I have the usual console, with big 
characters.

-- 
- Dlaczego hipopotamy mają okrągłe stopy?
- By łatwo było przeskakiwać z lilii na lilię.
NP: Motörhead - Overkill
NB: 2.6.34-rc2-git4

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Piotr Hosowicz wrote:
> Randy Dunlap wrote:
>> On Tue, 30 Mar 2010 00:44:28 +0200 Piotr Hosowicz wrote:
>>
>>> Randy Dunlap wrote:
>>>> On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:
>>>>
>>>>> Randy Dunlap wrote:
>>>>>> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
>>>>>>
>>>>>>> Randy Dunlap wrote:
>>>>>>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> Today I had built a new next kernel with these parameters. I 
>>>>>>>>> did not get what I expected
>>>>>>>> I don't think I understand your question.
>>>>>>>> What did you expect?
>>>>>>> I expected higher resolution console, smaller font etc
>>>>>> Boy was I confused.  I thought that your question was about the root=
>>>>>> kernel boot parameter.
>>>>>>
>>>>>> Well, there are several questions to be asked.  and one more comment.
>>>>>>
>>>>>> 1.  what video (framebuffer) driver are you using?
>>>>> Ashamed to say, but I do not know. vga=791 works perfectly when I 
>>>>> specifiy it via GRUB modification, either during pre-booting phase 
>>>>> or in menu.lst. I thought that it would work if I enable it by the 
>>>>> oprions I provided in the previous message.
>>>> That does sound, hm, suspicious.
>>
>>
>> OK, the above is the main problem, right?
>> If so, I'll try to find time to test it.
> 
> aapi205:/usr/src/linux# gzip -cd /proc/config.gz | grep -A 1 vga=791
> CONFIG_CMDLINE="root=/dev/sda2 ro quiet vga=791"
> CONFIG_CMDLINE_OVERRIDE=y
> aapi205:/usr/src/linux# cat /proc/cmdline
> root=/dev/sda2 ro quiet vga=791
> 
> First if all I tried to test whether the overriding code works at all, 
> and it seems it works, I am now booted having edited 
> root=/dev/nonexistent at GRUB prompt, and it seems that the values set 
> at build time have overriden values set at GRUB prompt. But the vga=791 
> parameter does not work at all, I have the usual console, with big 
> characters.

This is on 2.6.34-rc2-git4, sorry, I forgot to say.

Regards,

Piotr Hosowicz

-- 
Z cyklu "Uroki demokracji", czyli pytania i odpowiedzi w teledurniejach:
- Ile kół ma trójkołowiec?
- Dwa.
NP:  -
NB: 2.6.34-rc2-git4

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Piotr Hosowicz wrote:
> Piotr Hosowicz wrote:
>> Randy Dunlap wrote:
>>> On Tue, 30 Mar 2010 00:44:28 +0200 Piotr Hosowicz wrote:
>>>
>>>> Randy Dunlap wrote:
>>>>> On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:
>>>>>
>>>>>> Randy Dunlap wrote:
>>>>>>> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
>>>>>>>
>>>>>>>> Randy Dunlap wrote:
>>>>>>>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> Today I had built a new next kernel with these parameters. I 
>>>>>>>>>> did not get what I expected
>>>>>>>>> I don't think I understand your question.
>>>>>>>>> What did you expect?
>>>>>>>> I expected higher resolution console, smaller font etc
>>>>>>> Boy was I confused.  I thought that your question was about the 
>>>>>>> root=
>>>>>>> kernel boot parameter.
>>>>>>>
>>>>>>> Well, there are several questions to be asked.  and one more 
>>>>>>> comment.
>>>>>>>
>>>>>>> 1.  what video (framebuffer) driver are you using?
>>>>>> Ashamed to say, but I do not know. vga=791 works perfectly when I 
>>>>>> specifiy it via GRUB modification, either during pre-booting phase 
>>>>>> or in menu.lst. I thought that it would work if I enable it by the 
>>>>>> oprions I provided in the previous message.
>>>>> That does sound, hm, suspicious.
>>>
>>>
>>> OK, the above is the main problem, right?
>>> If so, I'll try to find time to test it.
>>
>> aapi205:/usr/src/linux# gzip -cd /proc/config.gz | grep -A 1 vga=791
>> CONFIG_CMDLINE="root=/dev/sda2 ro quiet vga=791"
>> CONFIG_CMDLINE_OVERRIDE=y
>> aapi205:/usr/src/linux# cat /proc/cmdline
>> root=/dev/sda2 ro quiet vga=791
>>
>> First if all I tried to test whether the overriding code works at all, 
>> and it seems it works, I am now booted having edited 
>> root=/dev/nonexistent at GRUB prompt, and it seems that the values set 
>> at build time have overriden values set at GRUB prompt. But the 
>> vga=791 parameter does not work at all, I have the usual console, with 
>> big characters.
> 
> This is on 2.6.34-rc2-git4, sorry, I forgot to say.

Same results with 2.6.34-rc3, I've just tested.

-- 
Nie pytaj co rząd może zrobić dla ciebie. Pytaj, jak możesz temu zapobiec.
NP: Patrick O'Hearn - Facing the Sun
NB: 2.6.34-rc3

Re: Is root kernel parameter expected to be the first one or something?

[Piotr Hosowicz]

Piotr Hosowicz wrote:

> Same results with 2.6.34-rc3, I've just tested.

Same with 2.6.34-rc3-next-20100331+.

Regards,

Piotr Hosowicz

-- 
Z cyklu "Uroki demokracji", czyli pytania i odpowiedzi w teledurniejach:
- W którym mieście europejskim powstała pierwsza opera?
- Sydney.
NP: Peter Green Splinter Group - There's A River
NB: 2.6.34-rc3-next-20100331+