Re: [Dri-devel] R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0), Permission denied

2002-10-09 Thread Ilia Zadorozhko

On Tuesday 08 October 2002 17:52, Jens Owen wrote:
 Ilia Zadorozhko wrote:
  Hi people,
  Help me please getting DRI to work.
  I've installed latest (rage128-20021008-linux.i386.tar.bz2) versions of
  DRI. Function drmSetBusid requires some kind of permission, which I can't
  understand. Launching X from root gives the same results. Please, help !
 
  Some info and logs:
  Kernel 2.4.19
  - lsmod -
  Module  Size  Used by
  r128   88132   0
  agpgart31840   1
  ---ls -l /dev/dri/---
  crw-rw-rw-1 root root 226,   0 ïËÔ  7 17:14 card0
  ---XF86Config-4
  Section DRI
  Mode0666
  EndSection
  XFree86.0.log---
  XFree86 Version 4.2.0 / X Window System
  .
  (--) PCI:*(2:0:0) ATI Rage 128 Pro PF rev 0, Mem @ 0xf000/26,
  0xff9fc000/14, I/O @ 0xd800/8, BIOS @ 0xff9c/17
  ...
  (==) R128(0): Write-combining range (0xf000,0x200)
  drmOpenDevice: minor is 0
  drmOpenDevice: node name is /dev/dri/card0
  drmOpenDevice: open result is 7, (OK)
  drmOpenDevice: minor is 0
  drmOpenDevice: node name is /dev/dri/card0
  drmOpenDevice: open result is 7, (OK)
  drmOpenDevice: minor is 0
  drmOpenDevice: node name is /dev/dri/card0
  drmOpenDevice: open result is 7, (OK)
  drmGetBusid returned ''
  (II) R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0), Permission denied
  (EE) R128(0): [dri] DRIScreenInit failed.  Disabling DRI.
  
  
 Ilia,

 Maybe it's a kernel module problem.  Make sure your AGPGART module is
 loaded into the kernel before the r128 module.  If that doesn't work,
 post the output from dmesg.

Jens, 
This is a dmesg log you asked for.
--- dmesg --
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 321M
agpgart: agpgart: Detected an Intel i815, but could not find the secondary 
device. Assuming a non-integrated video card.
agpgart: Detected Intel i815 chipset
agpgart: AGP aperture is 64M @ 0xf800
[drm] AGP 0.99 on Intel i815 @ 0xf800 64MB
[drm] Initialized r128 2.2.0 20010917 on minor 0
-


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0), Permission denied

2002-10-08 Thread Ilia Zadorozhko

Hi people, 
Help me please getting DRI to work.
I've installed latest (rage128-20021008-linux.i386.tar.bz2) versions of DRI. 
Function drmSetBusid requires some kind of permission, which I can't 
understand. Launching X from root gives the same results. Please, help !

Some info and logs:
Kernel 2.4.19
- lsmod -
Module  Size  Used by
r128   88132   0
agpgart31840   1
---ls -l /dev/dri/---
crw-rw-rw-1 root root 226,   0 ïËÔ  7 17:14 card0
---XF86Config-4
Section DRI
Mode0666
EndSection
XFree86.0.log---
XFree86 Version 4.2.0 / X Window System
.
(--) PCI:*(2:0:0) ATI Rage 128 Pro PF rev 0, Mem @ 0xf000/26, 
0xff9fc000/14, I/O @ 0xd800/8, BIOS @ 0xff9c/17
...
(==) R128(0): Write-combining range (0xf000,0x200)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmGetBusid returned ''
(II) R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0), Permission denied
(EE) R128(0): [dri] DRIScreenInit failed.  Disabling DRI.




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0),Permission denied

2002-10-08 Thread Jens Owen

Ilia Zadorozhko wrote:
 Hi people, 
 Help me please getting DRI to work.
 I've installed latest (rage128-20021008-linux.i386.tar.bz2) versions of DRI. 
 Function drmSetBusid requires some kind of permission, which I can't 
 understand. Launching X from root gives the same results. Please, help !
 
 Some info and logs:
 Kernel 2.4.19
 - lsmod -
 Module  Size  Used by
 r128   88132   0
 agpgart31840   1
 ---ls -l /dev/dri/---
 crw-rw-rw-1 root root 226,   0 ïËÔ  7 17:14 card0
 ---XF86Config-4
 Section DRI
 Mode0666
 EndSection
 XFree86.0.log---
 XFree86 Version 4.2.0 / X Window System
 .
 (--) PCI:*(2:0:0) ATI Rage 128 Pro PF rev 0, Mem @ 0xf000/26, 
 0xff9fc000/14, I/O @ 0xd800/8, BIOS @ 0xff9c/17
 ...
 (==) R128(0): Write-combining range (0xf000,0x200)
 drmOpenDevice: minor is 0
 drmOpenDevice: node name is /dev/dri/card0
 drmOpenDevice: open result is 7, (OK)
 drmOpenDevice: minor is 0
 drmOpenDevice: node name is /dev/dri/card0
 drmOpenDevice: open result is 7, (OK)
 drmOpenDevice: minor is 0
 drmOpenDevice: node name is /dev/dri/card0
 drmOpenDevice: open result is 7, (OK)
 drmGetBusid returned ''
 (II) R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0), Permission denied
 (EE) R128(0): [dri] DRIScreenInit failed.  Disabling DRI.
 
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Dri-devel mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/dri-devel
 
 

Ilia,

Maybe it's a kernel module problem.  Make sure your AGPGART module is 
loaded into the kernel before the r128 module.  If that doesn't work, 
post the output from dmesg.

-- 
/\
  Jens Owen/  \/\ _
   [EMAIL PROTECTED]  /\ \ \   Steamboat Springs, Colorado



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0), Permission denied

2002-10-08 Thread Felix Kühling

On Tue, 8 Oct 2002 11:29:44 +0300
Ilia Zadorozhko [EMAIL PROTECTED] wrote:

 Hi people, 
 Help me please getting DRI to work.
 I've installed latest (rage128-20021008-linux.i386.tar.bz2) versions of DRI. 
 Function drmSetBusid requires some kind of permission, which I can't 
 understand. Launching X from root gives the same results. Please, help !
 
 Some info and logs:
 Kernel 2.4.19
 - lsmod -
 Module  Size  Used by
 r128   88132   0
 agpgart31840   1
 ---ls -l /dev/dri/---
 crw-rw-rw-1 root root 226,   0 ïËÔ  7 17:14 card0
 ---XF86Config-4
 Section DRI
 Mode0666
 EndSection
 XFree86.0.log---
 XFree86 Version 4.2.0 / X Window System
 .
 (--) PCI:*(2:0:0) ATI Rage 128 Pro PF rev 0, Mem @ 0xf000/26, 
 0xff9fc000/14, I/O @ 0xd800/8, BIOS @ 0xff9c/17
 ...
 (==) R128(0): Write-combining range (0xf000,0x200)
 drmOpenDevice: minor is 0
 drmOpenDevice: node name is /dev/dri/card0
 drmOpenDevice: open result is 7, (OK)
 drmOpenDevice: minor is 0
 drmOpenDevice: node name is /dev/dri/card0
 drmOpenDevice: open result is 7, (OK)
 drmOpenDevice: minor is 0
 drmOpenDevice: node name is /dev/dri/card0
 drmOpenDevice: open result is 7, (OK)
 drmGetBusid returned ''
 (II) R128(0): [drm] drmSetBusid failed (7, PCI:2:0:0), Permission denied
 (EE) R128(0): [dri] DRIScreenInit failed.  Disabling DRI.
 
 

José, didn't we see such problems with the Mach64 driver some months
ago, when mixing compiler versions? I don't remember which combination
it was that had these problems.

Ilia, make sure that the kernel module is compiled with the same
compiler version as your kernel (in case you have several versions
installed).

Cheers,
   Felix

   __\|/_____ ___ ___
__Tschüß___\_6 6_/___/__ \___/__ \___/___\___You can do anything,___
_Felix___\Ä/\ \_\ \_\ \__U___just not everything
  [EMAIL PROTECTED]o__/   \___/   \___/at the same time!


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel