udev brokes my S3Virge/GX2 video card

igadoter · 02-16-2009, 07:24 AM

Running udev cause malfunction of a video S3Virge/gx2 card (agp).
With udev not running card works well. After udev start monitor colapses
(there no input signal). This under 12.2 ver, but the same under 12.0.

Tested under Debian - it's OK.

So, I'sppose in Slack udev scripts something is missing.

Didier Spaier · 02-16-2009, 08:12 AM

Does that occur under X and/or in console mode ?

Anything interesting in the logs (mainly var/log/syslog and, if it happens under X, /var/log/Xorg.0.log).

To get more info, you could edit /etc/udev/udev.conf, replacing udev_log="err" by udev_log="info" or udev_log="debug".

igadoter · 02-16-2009, 10:53 AM

During the very start of the system, when the rc-files are executed. So I turn off the udev completely. Then I started the system in console mode. It was OK. I logged and started the udev which immediately turn off my monitor. That's why I suspect the udev.

Didier Spaier · 02-16-2009, 11:06 AM

Do you find anything interesting in the logs when you start udev ?

gegechris99 · 02-16-2009, 01:41 PM

Hello,

Did you make a clean install of Slackware 12.2 or did you upgrade from a previous version?

If you upgraded, pay attention to this extract from CHANGES_AND_HINTS.TXT

Quote:

As usual, there are changes in udev packaging that need mentioning...
First, be sure to move the /etc/rc.d/rc.udev.new over - the old
/etc/rc.d/rc.udev will not work with the new udev package (and the new
one won't work with the old udev package).
The system udev rules now reside in /lib/udev/rules.d/ instead of
/etc/udev/rules.d/ in older versions. There should never be a reason
to edit anything in /lib/udev/rules.d/, so if you think you have a case
where this is required, either you're wrong or it needs to be addressed
in the upstream source. However, you can override default rules by
placing one with an identical name inside /etc/udev/rules.d/
The rules files in /etc/udev/rules.d/ are still intended to (maybe) be
edited as needed by local system administrators, and as such, the rules
for optical and network devices will still be placed there.

igadoter · 02-20-2009, 09:47 AM

Quote:

Originally Posted by Didier Spaier

Does that occur under X and/or in console mode ?

Anything interesting in the logs (mainly var/log/syslog and, if it happens under X, /var/log/Xorg.0.log).

To get more info, you could edit /etc/udev/udev.conf, replacing udev_log="err" by udev_log="info" or udev_log="debug".

It is hard to me make any experiment like that. I did'nt posted this
but my monitor was damaged. So, it's dangereous.

igadoter · 02-20-2009, 09:48 AM

Quote:

Originally Posted by gegechris99

Hello,

Did you make a clean install of Slackware 12.2 or did you upgrade from a previous version?

If you upgraded, pay attention to this extract from CHANGES_AND_HINTS.TXT

It was clean install. So there are default settings.

Didier Spaier · 02-20-2009, 11:13 AM

Quote:

Originally Posted by igadoter

It is hard to me make any experiment like that. I did'nt posted this
but my monitor was damaged. So, it's dangereous.

Nope.

Changing the value of udev_log only change the verbosity of the logs, it does nothing to your monitor.

Have a look at the file /etc/udev.conf. Change the value to "info" or "debug" and look at the results in /var/log/syslog.

To know more:'man udev'.