Re: [Dri-devel] Mach64 DRM: Permission denied: even for root?
mach64_state.c:682: warning: concatenation of string literals with __FUNCTION__ is deprecated. This feature will be removed in future Yes. I noticed this doo But it's only warnings. I think so. (II) ATI(0): [drm] loaded kernel module for mach64 driver (II) ATI(0): [drm] drmSetBusid failed (6, PCI:1:0:0), Permission denied (EE) ATI(0): [dri] DRIScreenInit Failed Exactly what I have. So we assume it's gcc:((( Is it possible to do something here. I would not like to downgrade to gcc 2.96 (to much pain) but still would like to use binary snapshots. Is it a big job to make drm directory buildable by gcc3? I could try to do it myself - just tell me where to put debug statements... So I have the same permission problem and it only occurs with gcc 3. :(( Does this mean gcc 3 sucks?:) Actually, transition from 2.96 to 3.1 was not easy - had to rebuild all c++ progs... Sergey, does your X-server lock up, too? No. I did not notice this. Just no DRM... Regards, Sergey ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 DRM: Permission denied: even for root?
On Thu, 2002-05-30 at 13:22, Felix Kühling wrote: When I started the Xserver it locked up after the first few 2D operations while loading the window manager. But I could kill it with the secure access key. I didn't see anything suspicious in XFree86.1.log or the syslog at the point of the failure. When DRI is disabled, the DRM is out of the picture actually. I'll try what happens when I disable DRI in XF86Config (when I get home). It is disabled due to the 'permissions' problem... Could my problem be that the DRM module is compiled with 3.0 and the rest of the kernel with 2.95? It worked with the kernel and the mach64 module compiled with 2.95 but all user space stuff compiled with 3.0. Right, that was probably my problem back then. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 DRM: Permission denied: even for root?
Again and again I take snapshots, again Permission denied even for root. What could this be? Can it be related to gcc 3.1 I use to build the kernel module in the snapshot? Really strange situation to me... Regards, Sergey ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 DRM: Permission denied: even for root?
On 30 May 2002 00:25:08 +0100 Sergey V. Udaltsov [EMAIL PROTECTED] wrote: Again and again I take snapshots, again Permission denied even for root. What could this be? Can it be related to gcc 3.1 I use to build the kernel module in the snapshot? Really strange situation to me... Regards, Sergey Hmm, I started using gcc-3.0.4 recently. I'm having 2 compiler versions installed. I noticed that Makefile.linux in linux/drm/kernel ignores my settings in host.def and uses the old compiler. I tried compiling the kernel module with gcc-3.0.4 now. The first obvious thing was that I got lots of these warnings: mach64_state.c:682: warning: concatenation of string literals with __FUNCTION__ is deprecated. This feature will be removed in future But it's only warnings. When I started the Xserver it locked up after the first few 2D operations while loading the window manager. But I could kill it with the secure access key. I didn't see anything suspicious in XFree86.1.log or the syslog at the point of the failure. But I see the following DRM related messages earlier in XFree86.1.log: (II) ATI(0): [drm] SAREA 2200+1212: 3412 drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 6, (OK) drmGetBusid returned '' (II) ATI(0): [drm] loaded kernel module for mach64 driver (II) ATI(0): [drm] drmSetBusid failed (6, PCI:1:0:0), Permission denied (EE) ATI(0): [dri] DRIScreenInit Failed So I have the same permission problem and it only occurs with gcc 3. Sergey, does your X-server lock up, too? Regards, Felix __\|/_____ ___ ___ __Tschüß___\_6 6_/___/__ \___/__ \___/___\___You can do anything,___ _Felix___\Ä/\ \_\ \_\ \__U___just not everything [EMAIL PROTECTED]o__/ \___/ \___/at the same time! ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Mach64 DRM: Permission denied: even for root?
Hi all Just took the latest (27.05) drm binary snapshot for Mach64. And cannot get DRI working any more. In XFree86.0.log I see: 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) ATI(0): [drm] drmSetBusid failed (7, PCI:1:0:0), Permission denied (EE) ATI(0): [dri] DRIScreenInit Failed Even if I start just X from root shell! How is it possible? What's wrong with my configuration? It seems DRM security reached the highest possible level:) Cheers, Sergey ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Mach64 DRM: Permission denied: even for root?
On 27 May 2002, Sergey V. Udaltsov wrote: Hi all Just took the latest (27.05) drm binary snapshot for Mach64. And cannot get DRI working any more. In XFree86.0.log I see: 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) ATI(0): [drm] drmSetBusid failed (7, PCI:1:0:0), Permission denied (EE) ATI(0): [dri] DRIScreenInit Failed Even if I start just X from root shell! How is it possible? What's wrong with my configuration? It seems DRM security reached the highest possible level:) Cheers, Sergey That's odd. Do you have a mode specified for the DRI device in XF86Config? -- Leif Delgass http://www.retinalburn.net ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
