Tiny Core Linux

Tiny Core Base => TCB Bugs => Topic started by: coreplayer2 on August 20, 2012, 04:35:30 PM

Title: I realise this is not an error but..
Post by: coreplayer2 on August 20, 2012, 04:35:30 PM

I am constantly explaining to folks that this is not an error per se..  But the messages get a lot of attention which ultimately raises flags and doubt of stability in the whole operation.  So is there any way to hide the caching messages, it's not like we have any control over the issue, a USB thumb stick is what it is..

2x USB thumb drive's connected here
(http://db.tt/tvLa7MfK)

Title: Re: I realise this is not an error but..
Post by: tinypoodle on August 20, 2012, 05:23:07 PM

Not clear what you refer to...

Title: Re: I realise this is not an error but..
Post by: gerald_clark on August 20, 2012, 05:48:20 PM

Did you try the 'quiet' boot option?

Title: Re: I realise this is not an error but..
Post by: coreplayer2 on August 20, 2012, 07:28:08 PM

All my systems use the quiet boot code,
"quiet" boot code doesn't suppress the cache messages 

Messages occur if booting from a frugal install on a USB thumb drive, and
when booting to a freshly downloaded CorePlus ISO, 4 cache messages are displayed any time for each USB Thumb Drive attached to the system.

Title: Re: I realise this is not an error but..
Post by: tinypoodle on August 20, 2012, 08:08:51 PM

Messages pertaining to attached storage media are generated by the kernel, not specific to core.
See boot parameters in kernel docs for advanced options of finetuning.

Linux defaults - not a bug.

Title: Re: I realise this is not an error but..
Post by: coreplayer2 on August 20, 2012, 08:15:52 PM

Thanks, like I said in the beginning I know it's not an error (bug) but am  looking for a way to suppress these messages which I haven't found yet..

Title: Re: I realise this is not an error but..
Post by: tinypoodle on August 20, 2012, 08:23:19 PM

Main reason I pointed that out is that thread is posted under "TCB Bugs"

Title: Re: I realise this is not an error but..
Post by: coreplayer2 on August 20, 2012, 08:25:36 PM

Ah ha!  ok well I couldn't find a more appropriate place here sounds as good a place as any to me.. :)

Title: Re: I realise this is not an error but..
Post by: curaga on August 21, 2012, 06:24:06 AM

"quiet" sets the log level to 4. Replace with "loglevel=N" where N is the level you want, see kernel-parameters.txt.

Title: I realise this is not an error but..
Post by: coreplayer2 on August 21, 2012, 10:22:10 AM

Thanks will investigate this option

Title: Re: I realise this is not an error but..
Post by: roberts on August 22, 2012, 03:18:09 PM

Try replacing quiet with loglevel=3
It should suppress the spurious messages mentioned.

Title: Re: I realise this is not an error but..
Post by: coreplayer2 on August 22, 2012, 04:47:07 PM

Thanks roberts & curaga for the advise,  replacing quiet with loglevel=3 does in fact suppress the messages

Thank you

Title: Re: I realise this is not an error but..
Post by: lverns on August 25, 2012, 02:55:37 PM

Awesome! I've got to try this solution. I've had to live with those messages for 8 months :)

Title: Re: I realise this is not an error but..
Post by: roberts on August 25, 2012, 03:29:00 PM

Replacing quiet with loglevel=3 for 4.6 release.

Title: Re: I realise this is not an error but..
Post by: curaga on August 25, 2012, 03:34:53 PM

Actually, instead of not showing errors (which the user may want to see), I'd prefer to change these two messages to warnings.

Just like in the squashfs code, we disagree with upstream that these messages qualify as errors. But since making this kernel change isn't urgent, let's lower the log level for now and in tc 5 do it the proper way, returning quiet.