I have SuSE 9.2 with an integrated Intel Graphics card using the i810 driver. GLX is very stable until I start another X session. Then 3D acceleration stops working on both sessions. I’m probably missing a module to load or something in my /etc/profile. Any ideas?
This is really strange and should not happen. Also I don’t know why /etc/profile would have something to do with this issue.
Unfortunately I cannot say more.
One more thing. glxinfo shows that direct rendering is enabled. But glxgears and my 3d screensaver show differently.
do you mean before or after starting a new session ?
did you looked at your logs (/var/logs/message, /var/log/XFree86 and such). What about dmesg ? Everything fine for them ?
Ok, dmesg gives me this interesting bit:
[drm] Initialized i915 1.1.0 20040405 on minor 0:
This is interesting because I’m using the i810 driver and chipset.
This was in my /var/log/messages
May 30 12:47:07 dell modprobe: FATAL: Error inserting sonypi (/lib/modules/2.6.8-24.14-smp/kernel/drivers/char/sonypi.ko): No such device
I don’t know what sonypi is.
I’m not so sure about these error either. They’re from the xorg log file:
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
Try xf86config or xf86cfg to change that. Apply your card. Maybe your installer made a mistake, so maybe you’ll also have to tell it to your linux distributor (suze) of that issue.
Do you have an SMP (multi processors ?) If not, I advise you to change your kernel for a non smp. Or recompile it yourself.
I built my xorg.conf file myself. I configured it to use the i810 driver.
I have a P4 w/ hyperthreading. That’s why I use the smp kernel.
More symptoms. As I stated when I log in to KDE I have great acceleration. In fact I get about 900 FPS. When I log in a second KDE user acceleration is lost for both sessions. However, I recently discovered that if I log the first session out and then back in, I have acceleration. When I switch to the second session, acceleration does not work. Then when I switch back to the first session, acceleration is lost again. So it appears that it is a problem with switching Virtual Terminals. Upon a VT switch, acceleration is lost. Please Help.
I really cannnot help you much. Sorry for that but unfortunately I’m not a genius that can guess all…
To my opinion you shoudln’t use an SMP version of the kernel, even on hyperthreaded cpus.
HyperThreaded is not multi-processor. Don’t confuse such things if you don’t want to get in trouble with your machine.
Just to clear something up: Yes, you should use SMP with hypertreading. HT may not be real multiprocessor, but to the operating system it looks like multiprocessor…
As for the original problem: I’m not sure if what you attempt is even possible. You’re asking for two X servers to share a piece of hardware, I’m not sure if the driver can handle that… It certanly has nothing to do with two sessions, but with two X servers being active.
You could however try updating to the most recent driver (are there Linux drivers for Intel hardware?), or at least the most recent Xfree or Xorg…
I have the most recent of both the driver and xorg. This driver has always been a little picky about 3D acceleration. Although it works great when working, it only works in 16 bit depth. So, I guess it is the driver. I’ll have to buy a new motherboard with PCI Express and get a good Nvidia. When that happens I’ll know for sure and update here. Thanks for everyone’s help.
I’m not sure of what you said Overmind. For me, there’s no real reason for having an SMP kernel on a HT cpu. HT has been made for improving threading support on cpus not for faking 2 cpus. Otherwise, that simply means that a single non HT cpu could also take profit from SMP. After all, any cpu knows how to do multithreading, not all at the rate of HT but suffisant enough.
At least Athlon X2 could take profit from SMP because there’s really two cpu cores so we can see them in /proc.
Well, anyway that’s not the source of his problem.
About multiple X sessions, I’m almost pretty sure that almost all graphic card drivers could support it and there’s no real warns about unsupported hardware on common documentation.
This topic was automatically closed 183 days after the last reply. New replies are no longer allowed.