From: Magnus L. <mag...@ra...> - 2002-01-30 04:10:52
|
tor...@st... said: > What's your hardware config/X version ? > ah sorry, forgot that. amd duron 800 mhz, 384 mb ram, geforce 2 mx, > soundblaster live (if it matters), kernel 2.4.16-k7, and xfree86 4.1.0 > with non-free nvidia drivers 1.0.2313 (glx) / 1.0.2314 (kernel > module). hope that's it :) > best regards torgeir I have noticed the same problem. Not with xine though, but with xawtv. No picture, just gray window. Almost the same config; only difference is 2.4.17 kernel and 256 MB RAM. The problem shows only when X has been running for some hours. After restarting X, the xawtv picture is back again. Now that I think of it, I should have tried disabling Xvideo to see if the problem is related to that. I'll do that next time I get the "gray window". I've also had the X server crash once or twice when launching xawtv. From what I recall, I did not have this problem before I upgraded to nvidias latest drivers (1.0.2313/1.0.2314). With version 1.0.1541 of the nvidia drivers I don't remember ever seeing this happen. I must admit though, that I only ran lk 2.4.17 for ten days with nvidia driver 1.0.1541 so it could be a kernel thing too. On the other hand, I did run 2.4.16 and 2.4.17pre kernels for more than a month with the 1.0.1541 driver. Combined with your experience, I guess this would indicate that something happened in the nvidia driver between the two releases. ...OR the weird things started when I began feeding the mem=nopentium option to kernel about a week ago. After all, I have been running lk 2.4.17 with nvidia 1.0.2314 since December 31 and I didn't experience anything unusual during the first few weeks... hmmmm, I should do some more systematic testing. Torgeir, you don't by chance use the mem=nopentium option, do you? Regards, Magnus |
From: Torgeir S. H. <tor...@st...> - 2002-01-30 14:02:45
|
> I think you should download Nvidia kernel module source rpm > and recompile it for you kernel 2.4.16 because binary rpm supplied by Nvidia designed > for 2.4.7 (RH 7.2): that's more or less what i did. i installed the nvidia kernel source debian package, compiled it into a binary debian package and installed it, according to the steps in /usr/share/doc/nvidia-kernel-src/README.Debian. the description of the resulting binary package reads "NVIDIA binary kernel module for Linux 2.4.16", so i think that part is ok. best regards torgeir |
From: Magnus L. <mag...@ra...> - 2002-01-30 18:08:32
|
tor...@st... said: > > kernel and 256 MB RAM. The problem shows only when X has been running for some > > hours. After restarting X, the xawtv picture is back again. Now that I think > > here, the problem always shows. Great! That will make it easier to debug ...I hope :) > > >From what I recall, I did not have this problem before I upgraded to nvidias > > latest drivers (1.0.2313/1.0.2314). With version 1.0.1541 of the nvidia > > i've been running 2.4.16-k7 and 1.0.2313/4 since before christmas, and > never had the problem until i upgraded to xine 0.9.8. it might have been > some other package that was upgraded during an apt-get, the only thing i > know for sure is that the previous version worked, and the new one > doesn't. i just tried mplayer as well, and for some reason it works > well, but avifile-player still doesn't. Are you using the Xvideo output plugin (-VXv)? Does the problem persist if you try the XShm output plugin (-VXShm)? If I get the "grey window" problem when I get home tonight, I will try the XShm plugin to see if the problems could be Xvideo related. > > > I guess this would indicate that something happened in the nvidia driver > > between the two releases. > > i haven't had any other version of the nvidia drivers installed, but > perhaps the new drivers really is the problem, and that they've just > been nice to me for a while or something.. :) It wouldn't be the first time an Athlon/Duron system appeared to behave inconsistently :( Computers are supposed to be consistent. If not, there is IMHO generally a software bug or flawed harware somewhere in the system. > > > ...OR the weird things started when I began feeding the mem=nopentium option > > to kernel about a week ago. After all, I have been running lk 2.4.17 with > > actually, that's about the same time i started feeding mem=nopentium as > well, and also about the same time i upgraded xine. i tried removing the > mem=nopentium line and rebooted ten minutes ago though, and xine still > comes up with it's gray window.. > OK, so it's possible that mem=nopentium only makes a hidden problem visible on my system. Sounds reasonable since, AFAIK, disabling 4MB pages should only adversely affect performance. I'll try downgrading to nvidia drivers 1.0.1541, but even the result from that operation may not be conclusive. The lurking problem might not show up in xawtv anymore, but somewhere else instead :( Does anyone have any ideas on how to hunt this critter down? > best regards > torgeir > /Magnus |
From: Torgeir S. H. <tor...@st...> - 2002-01-30 18:40:26
|
> Are you using the Xvideo output plugin (-VXv)? Does the problem persist if you > try the XShm output plugin (-VXShm)? If I get the "grey window" problem when I xshm seems to work, so i guess the problem is xv then (which would make sense considering avifile-player has the same gray window problem). i've always used the default video output plugin, so if that was xv in the previous version as well, it means xv has been working at some point. > It wouldn't be the first time an Athlon/Duron system appeared to behave > inconsistently :( Computers are supposed to be consistent. If not, there is are intel processors much better at such consistency? best regards torgeir |
From: Magnus L. <mag...@ra...> - 2002-01-30 18:59:34
|
tor...@st... said: > xshm seems to work, so i guess the problem is xv then (which would > make sense considering avifile-player has the same gray window > problem). i've always used the default video output plugin, so if that > was xv in the previous version as well, it means xv has been working > at some point. Could you try using the Xv output plugin, but with AGP disabled. I think = it = would be interesting to see if the problem is AGP related in any way. AGP= = support is easily disabled through the use of the NvAgp option in the XFr= ee86 = config file (/etc/X11/XF86Config-4 with XFree86-4.1 on Red Hat Linux). He= re is = an excerpt from Nvidia's driver README: Option "NvAgp" "0" ... disables AGP support Option "NvAgp" "1" ... use NVAGP, if possible Option "NvAgp" "2" ... use AGPGART, if possible Option "NvAGP" "3" ... try AGPGART; if that fails, try NVAGP The default is 3 (the default was 1 until after 1.0-1251). The NvAgp option goes into the nvidia device section. > > It wouldn't be the first time an Athlon/Duron system appeared to beha= ve = > > inconsistently :( Computers are supposed to be consistent. If not, th= ere > are intel processors much better at such consistency? probably not, but they have been around longer so kernel developers have = caught up with many of Intel's features (read bugs) :) > best regards torgeir = /magnus |
From: Torgeir S. H. <tor...@st...> - 2002-01-30 19:41:49
|
> Could you try using the Xv output plugin, but with AGP disabled. I think it > would be interesting to see if the problem is AGP related in any way. AGP the problem seems to be unrelated to agp, as none of the settings made a difference. just for information, some guy on irc suggested loading the v4l x module, but that didn't work either. more suggestions are welcome! :) best regards torgeir |
From: Magnus L. <mag...@ra...> - 2002-01-30 19:54:16
|
tor...@st... said: > the problem seems to be unrelated to agp, as none of the settings made > a difference. just for information, some guy on irc suggested loading > the v4l x module, but that didn't work either. more suggestions are > welcome! :) what about older nvidia drivers, specifically 1.0.1541? ...but, of course, you have to be a real masochist to switch between different nvidia drivers just for fun :) > best regards torgeir /magnus |
From: imdos <im...@im...> - 2002-01-30 21:51:41
|
On Wed, 2002-01-30 at 20:54, Magnus Lindstr=F6m wrote: >=20 > tor...@st... said: > > the problem seems to be unrelated to agp, as none of the settings made > > a difference. just for information, some guy on irc suggested loading > > the v4l x module, but that didn't work either. more suggestions are > > welcome! :) >=20 > what about older nvidia drivers, specifically 1.0.1541? ...but, of course= , you=20 > have to be a real masochist to switch between different nvidia drivers ju= st=20 > for fun :) >=20 Actually, i still get the best quality using 1.0.1251 ( Problem with v4l otherwise ). And i don't bother too much about frame-rates, because i rarely play games! > > best regards torgeir=20 >=20 > /magnus >=20 >=20 |
From: Magnus L. <mag...@ra...> - 2002-01-30 23:30:54
|
mag...@ra... said: > tor...@st... said: > > the problem seems to be unrelated to agp, as none of the settings mad= e > > a difference. just for information, some guy on irc suggested loading= > > the v4l x module, but that didn't work either. more suggestions are > > welcome! :) > = > what about older nvidia drivers, specifically 1.0.1541? ...but, of cour= se, you = > have to be a real masochist to switch between different nvidia drivers = just = > for fun :) > = I found a sequence of actions that will deterministically crash my X serv= er: 1. log in with gdm 2. launch xawtv 3. quit xawtv 4. close X session by logging out 5. log in again 6. launch xawtv = ...... CRASH! I downgraded the nvidia drivers from version 1.0.2313/1.0.2314 to 1.0.154= 1 and the problem disappeared. I don't know whether the "gray window" iss= ue is also gone, but I would like to think that. Now I'll try to get a back trace of the crash and see if I can figure out= where the crash occurs. /magnus |
From: James <ja...@pi...> - 2002-01-31 11:30:01
|
On Thu, Jan 31, 2002 at 12:30:45AM +0100, Magnus Lindstrvm wrote: | I downgraded the nvidia drivers from version 1.0.2313/1.0.2314 to 1.0.1541 and the problem disappeared. I don't know whether the "gray window" issue is also gone, but I would like to think that. Email the nice people at lin...@nv.... They'll love to hear about this. It seems the newest NVIDIA drivers are a little broken. TV-OUT support on my Geforce is rather broken (it works once... then I start X and it never works again). -- I will stop talking about the twelve inch pianist 6AD6 865A BF6E 76BB 1FC2 | www.piku.org.uk/public-key.asc E4C4 DEEA 7D08 D511 E149 | www.piku.org.uk wn...@cv...t.hx (rot13'd) |
From: Torgeir S. H. <tor...@st...> - 2002-01-30 08:12:58
|
> kernel and 256 MB RAM. The problem shows only when X has been running for some > hours. After restarting X, the xawtv picture is back again. Now that I think here, the problem always shows. > >From what I recall, I did not have this problem before I upgraded to nvidias > latest drivers (1.0.2313/1.0.2314). With version 1.0.1541 of the nvidia i've been running 2.4.16-k7 and 1.0.2313/4 since before christmas, and never had the problem until i upgraded to xine 0.9.8. it might have been some other package that was upgraded during an apt-get, the only thing i know for sure is that the previous version worked, and the new one doesn't. i just tried mplayer as well, and for some reason it works well, but avifile-player still doesn't. > I guess this would indicate that something happened in the nvidia driver > between the two releases. i haven't had any other version of the nvidia drivers installed, but perhaps the new drivers really is the problem, and that they've just been nice to me for a while or something.. :) > ...OR the weird things started when I began feeding the mem=nopentium option > to kernel about a week ago. After all, I have been running lk 2.4.17 with actually, that's about the same time i started feeding mem=nopentium as well, and also about the same time i upgraded xine. i tried removing the mem=nopentium line and rebooted ten minutes ago though, and xine still comes up with it's gray window.. best regards torgeir |