Timeline for Hide Complete Boot Message from RPI booting
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 6, 2017 at 18:19 | history | protected | goldilocks♦ | ||
| Jun 6, 2017 at 22:34 | answer | added | dev.pt | timeline score: 2 | |
| Mar 1, 2017 at 15:03 | answer | added | Brett Reinhard | timeline score: 4 | |
| Feb 27, 2017 at 12:34 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 26, 2017 at 5:27 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| S Dec 25, 2016 at 0:30 | history | suggested | tlhIngan | CC BY-SA 3.0 |
Fixed English
|
| Dec 24, 2016 at 23:27 | answer | added | tlhIngan | timeline score: 2 | |
| Dec 24, 2016 at 23:22 | review | Suggested edits | |||
| S Dec 25, 2016 at 0:30 | |||||
| Jul 11, 2016 at 21:11 | history | tweeted | twitter.com/StackRaspi/status/752611286026948613 | ||
| Sep 24, 2015 at 3:54 | comment | added | Arun Kumar K S | Added console=tty3 to my cmdline.txt but it still shows some messages like this [3.226117] GPIO $bb890000 = 0x24800000 [3.226431] GPIO $bb890004 = 0x24024 I want to hide this too | |
| Sep 23, 2015 at 15:16 | comment | added | goldilocks♦ | Right, I'm just clarify what those parameters are. Someone who knows this, knows that they are not pi specific, and (hopefully) recognizes that the linux world is orders of magnitude bigger than the pi world, and that a basic rule of online research is to investigate in the broadest context possible, not the narrowest. By proliferating the idea that these things are pi-specific, you encourage other people to waste their time barking up the wrong tree. | |
| Sep 23, 2015 at 15:06 | comment | added | bobstro | And how do you set those parameters on the Raspberry Pi? On every desktop linux system I've used, it's been grub or lilo bootloader or equivalent. On the RPi, it's different. Which is my point. The means by which you pass those parameters -- many of which are specific to the RPi -- is via /boot/cmdline.txt. Would answers about configuring grub really help? | |
| Sep 23, 2015 at 14:49 | comment | added | goldilocks♦ |
@bobstro I'll tell you exactly what cmdline.txt is. It's command line parameters passed to the kernel by the bootloader. The kernel passes some of these on to init. The most significant parameters from your post are console and loglevel, used by the kernel and potentially init. Note they are documented in the vanilla source and are not specific to the pi.
|
|
| Sep 23, 2015 at 14:43 | comment | added | bobstro | For that to be true, the instructions provided would have to actually work on the RPi. Unless those parameters are included in /boot/cmdline.txt -- which is certainly uncommon if not completely unique among platforms -- instructions found elsewhere may not work at all, regardless of the theory. | |
| Sep 23, 2015 at 14:41 | comment | added | goldilocks♦ |
@bobstro The means you mention in your answer are in fact not pi specific (beyond being set in cmdline.txt instead of a bootloader config, although the former is really a form of the latter), even if you may not recognize it. However, it's still a decent answer.
|
|
| Sep 23, 2015 at 14:32 | comment | added | bobstro | There are aspects of this question that are very RPi-specific. We should make sure there aren't RPi considerations before discouraging legitimate questions, particularly since we're still in Beta limbo. | |
| Sep 23, 2015 at 13:37 | comment | added | dhruvvyas90 |
A quick solution would be redirecting it to tty console other than tty1 by specifying it in cmdline.txt. (like this one --> console=tty3) so that it doesn't get reflected on screen. It works for me (I'm using an HDMI display).
|
|
| Sep 23, 2015 at 13:32 | comment | added | goldilocks♦ | The messages you've shown are not from the kernel, they are from init. There are various init systems around used on Raspberry Pi GNU/Linux distros, the two principle ones are Debian's SysV style init, which this looks to be, used on Raspbian wheezy and perhaps Kali (I'm not sure), and Systemd, used on Raspbian jessie and Arch. How you quash init messages at boot depends on which of those you are using, and is better investigated at Unix & Linux, since it is not a pi specific issue. | |
| Sep 23, 2015 at 12:37 | history | asked | Arun Kumar K S | CC BY-SA 3.0 |