Am 18.07.2012 16:02, schrieb Sudaraka Wijesinghe:

Hi Everyone,

I'm playing with a custom kernel just for the fun of it, Everything
works fine except it's very noisy when it boots. I'm using the same
loglevel (4) as the default kernel that is in the Arch repo. And I have
turned off many debug options under kernel hacking section.
It does quiet down when I add the "quiet" parameter to the kernel
command line.

What I was wondering is how the Arch kernel is keeping it quiet without
using the command line parameter (quiet), is it using a patch for that
or something?

Thanks,


P.s.
Messages I get are hardware probing, state changes and file system
mount, etc.



Do you use systemd? Have a look here:

https://wiki.archlinux.org/index.php/Systemd#Q:_Why_do_I_get_log_messages_on_my_console .3F

On 07/18/2012 08:32 PM, martin kalcher wrote:
> Am 18.07.2012 16:02, schrieb Sudaraka Wijesinghe:
>> Hi Everyone,
>>
>> I'm playing with a custom kernel just for the fun of it, Everything
>> works fine except it's very noisy when it boots. I'm using the same
>> loglevel (4) as the default kernel that is in the Arch repo. And I have
>> turned off many debug options under kernel hacking section.
>> It does quiet down when I add the "quiet" parameter to the kernel
>> command line.
>>
>> What I was wondering is how the Arch kernel is keeping it quiet without
>> using the command line parameter (quiet), is it using a patch for that
>> or something?
>>
>> Thanks,
>>
>>
>> P.s.
>> Messages I get are hardware probing, state changes and file system
>> mount, etc.
>>
>
> Do you use systemd? Have a look here:
>
> https://wiki.archlinux.org/index.php/Systemd#Q:_Why_do_I_get_log_messages_on_my_console .3F
>

No, I'm using initscripts, and it does quiet down when I use the kernel
command line parameter as explained in there, but I was wondering how
default Arch kernel is doing it without the command line parameter.

Thanks for the reply.

On Wed, Jul 18, 2012 at 5:02 PM, Sudaraka Wijesinghe
<sudaraka.wijesinghe@gmail.com> wrote:
> Hi Everyone,
>
> I'm playing with a custom kernel just for the fun of it, Everything
> works fine except it's very noisy when it boots. I'm using the same
> loglevel (4) as the default kernel that is in the Arch repo. And I have
> turned off many debug options under kernel hacking section.
> It does quiet down when I add the "quiet" parameter to the kernel
> command line.
>
> What I was wondering is how the Arch kernel is keeping it quiet without
> using the command line parameter (quiet), is it using a patch for that
> or something?

It's specified in kernel configuration at compile time:

CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4

--
Mantas MikulÄ—nas

> No, I'm using initscripts, and it does quiet down when I use the kernel
> command line parameter as explained in there, but I was wondering how
> default Arch kernel is doing it without the command line parameter.

It's a patch:
% grep -R loglevel /var/abs/core/linux
/var/abs/core/linux/change-default-console-loglevel.patch: #define
MINIMUM_CONSOLE_LOGLEVEL 1 /* Minimum loglevel we let people use */

/var/abs/core/linux/PKGBUILD: 'change-default-console-loglevel.patch'

/var/abs/core/linux/PKGBUILD: patch -Np1 -i
"${srcdir}/change-default-console-loglevel.patch"

Download the package via ABS and examine it for yourself

Greetings,
Christoph

On 07/18/2012 09:35 PM, Christoph Vigano wrote:
>> No, I'm using initscripts, and it does quiet down when I use the kernel
>> command line parameter as explained in there, but I was wondering how
>> default Arch kernel is doing it without the command line parameter.
>
> It's a patch:
> % grep -R loglevel /var/abs/core/linux
> /var/abs/core/linux/change-default-console-loglevel.patch: #define
> MINIMUM_CONSOLE_LOGLEVEL 1 /* Minimum loglevel we let people use */
>
> /var/abs/core/linux/PKGBUILD: 'change-default-console-loglevel.patch'
>
> /var/abs/core/linux/PKGBUILD: patch -Np1 -i
> "${srcdir}/change-default-console-loglevel.patch"
>
> Download the package via ABS and examine it for yourself
>
> Greetings,
> Christoph
>

Thanks Christoph, I was able to solve the issue using your suggestion.
It never occurred me to look in there