You are not logged in.

#1 2012-05-10 10:43:20

Triston J. Taylor
Banned
Registered: 2011-10-20
Posts: 41

Kernel dumping messages to console

I have some modules that have been bugging me for a year now that keep dumping info to the console instead of the klog.

Well, I was just perusing the system commands by typing names and tabulating a completion when I found this:

setterm

The manual for it says `setterm -msg off' disables kernel messages on the console. So I switched over to console 2 and tried it out on my wireless card module: brcms (one of those culprits making my system look broken... during bootup and login)

So now that I know how to disable these messages, how can I make this command run before almost any daemons startup and what not so when the boot status is scrolling I don't hear about *dev*lun* and *pci* during the system startup?

Is it safe to run terminal commands in rc.conf? Kind of a newb question but I'd like some validation/suggestion on this if possible before I reconfig.

I've decided, that the messages never show up before the "Arch Linux" logo (in /etc/rc.sysinit) at boot so what I've done is insert the command just after the logo is printed. Will reboot and see what happens.

It has certainly hidden the udev kernel messages. Some logs are still not being caught. I don't want to see these notices during boot. If it doesn't say:

message                                                     [SUCCESS|FAIL]

I.D.G.A.F. ! That's what log files and recovery environments are for!

logging in to a tty, the kmod messages are still showing up from the brcms module sad I would like to say I'm aggravated, but I'm beyond that; I'm gravely dissapointed at this point.

Last edited by Triston J. Taylor (2012-05-10 11:24:11)


systemd has its advantages; of these the most damaging are: corporatization, security bottlenecks, control obfuscation, and micro-managed forward compatibility pitfalls. Free Software meets Dictatorship. What a maroon.

Offline

#2 2012-05-10 12:17:19

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,498
Website

Re: Kernel dumping messages to console

Before you get aggravated and dissapointed, try STFF


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2012-05-11 01:19:52

Triston J. Taylor
Banned
Registered: 2011-10-20
Posts: 41

Re: Kernel dumping messages to console

I'm assuming you mean search the ¢%#$¤€³ forum? lol. Well maybe if they had a better description I'd have found it. Didn't think it was directly related to the internal wireless card since udev and a few other tools randomly decide to garble my TTY sessions and boot status. i've even looked at the module code and it blatantly spits that crap out without respect of the environment. I've got it. Next time I'll hire an elf to do my work for me!

*lol* I appreciate the help. I have many things to worry about. Unfortunately this is just one annoyance I have been battling for a year. Decided to take a crack at it again today. UR Awesome. Don't forget it.

On a side note... this more descriptive and properly located post will hopefully direct some poor soul in the right direction.

Last edited by Triston J. Taylor (2012-05-11 01:22:58)


systemd has its advantages; of these the most damaging are: corporatization, security bottlenecks, control obfuscation, and micro-managed forward compatibility pitfalls. Free Software meets Dictatorship. What a maroon.

Offline

#4 2012-05-11 01:24:04

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,498
Website

Re: Kernel dumping messages to console

I'm glad that worked.  There are also several threads on output from udev.  The most common solution is to put your wireless module in your MODULES array - brcmsmac in this case.

I'm not awesome, but this community is.  Use it.  Any issue you're facing has almost certainly been faced and solved by others here.  Learn from those experiences.  No need for elves, just some reading of the wiki or googling the forums.

I strongly agree that good titles are needed on forum posts.  But on the flip side, I had the same problem with my brcmsmac sending lots of output over the tty.  I think I only had to try two different goolge queries before I found the relevant threads on this forum that solved the issue.  It took about 5 minutes.  The udev issue was solved similarly as quick.

Last edited by Trilby (2012-05-11 01:29:07)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#5 2012-05-11 01:54:46

Triston J. Taylor
Banned
Registered: 2011-10-20
Posts: 41

Re: Kernel dumping messages to console

Great tips. Thanks again. But I'll have to disagree with your self contradiction: I'm not awesome this community (of which you are a member) is smile

I see this alot on the internet. People who like to visit the forums often, forget that others aren't so well adjusted to that environment. You should always remember this. There is nothing wrong with asking for guidance in the most trivial of situations because in the end, new documentation related to a specific issue is made available. Even if it is a redirection, it increases the number of relevent search engine hits.

I had this installed before I went messing with my libs and screwed the system up royally:

pacman -S arch-firefox-search

Indispensable Tool for an Arch Enthusiast it is. Nice hat.

Last edited by Triston J. Taylor (2012-05-11 02:03:54)


systemd has its advantages; of these the most damaging are: corporatization, security bottlenecks, control obfuscation, and micro-managed forward compatibility pitfalls. Free Software meets Dictatorship. What a maroon.

Offline

Board footer

Powered by FluxBB