syslog of my brand-new rp3440

[I.Delic]

Hi guy's,

I get this in my syslog. I did't do nothing. I'm only viewing my syslog file ( tail -f)

Jul 7 08:23:58 nloos2u1 vmunix: gvid: ATI Radeon 7000 not supported on this hardware
Jul 7 08:24:02 nloos2u1 vmunix: gvid: ATI Radeon 7000 not supported on this hardware
Jul 7 12:08:27 nloos2u1 vmunix: gvid: ATI Radeon 7000 not supported on this hardware
Jul 7 12:08:31 nloos2u1 vmunix: gvid: ATI Radeon 7000 not supported on this hardware
Jul 7 14:40:29 nloos2u1 vmunix: gvid: ATI Radeon 7000 not supported on this hardware
Jul 7 14:45:14 nloos2u1 LVM[16212]: /usr/sbin/lvlnboot -v
Jul 7 14:45:39 nloos2u1 LVM[16991]: /usr/sbin/lvlnboot -v

Could you tel me what it means.
Thank you in advance

I know wat is lvlnboot but i don't know whay is it started .


Idriz

[Bill Hassell]

This error is probably from the Xwindows. The ATI Radeon 7000 is a video card adn Xwindows must be patched to support new hardware when it becomes supported. The latest Xwindow patch is PHSS_30871.

[Michael Tully]

Anytime 'lvlnboot' runs it get reported to syslog. Somebody could have run it, or there is some script being run from cron. I think even cutting an ignite tape would do this as well.

[I.Delic]

hi ,

Thank you foor your answers.
Is it possible to track lvnboot -v. who dit it, witch script ...etc.

Nobody use this machine . I jus got it. I'm the only "network-user" who use this machine.

I did not make IGNITE tape


Idriz

[Cheryl Griffin]

SAM is also notorious for running lvlnboot -v.

To track who ran lvlnboot, create a wrapper like the one Bill Hassell posted here for modprpw http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=426108 (see attachment)

[Bill Hassell]

As mentioned, every time lvlnboot -v is run, an entry is made in syslog. Since you have the date and time the commands were run (and they were both run within a minute of each other, you can look at root logins:

last -R root

and see where root was logged in on Jul 7 at about 2:45pm. As mentioned, lvlnboot -v will be run by sam whenever you work with disks and filesystems. NOTE: there is nothing wrong with the syslog message. syslog is not an error listing, it contains error messages, status messages, even debug messages and the content is under the control of the programs that wirte to syslog. In other words, there are lots of messages that can be ignored. You can put your own message there:

logger "This is a test"
tail -5 /var/adm/syslog/syslog.log

and you'll see your own message. Now you can adjust the level of logging so that information and debug messages are not logged at all (not a good idea) or the messages are logged in a different location. The config file is /etc/syslog.conf (see man syslogd).