Menu
▾
▴
dri-users
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
(25) |
Apr
(38) |
May
(9) |
Jun
(39) |
Jul
(64) |
Aug
(73) |
Sep
(86) |
Oct
(91) |
Nov
(112) |
Dec
(90) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(158) |
Feb
(178) |
Mar
(305) |
Apr
(269) |
May
(302) |
Jun
(126) |
Jul
(171) |
Aug
(143) |
Sep
(146) |
Oct
(96) |
Nov
(105) |
Dec
(100) |
| 2002 |
Jan
(112) |
Feb
(50) |
Mar
(91) |
Apr
(88) |
May
(99) |
Jun
(217) |
Jul
(95) |
Aug
(129) |
Sep
(107) |
Oct
(283) |
Nov
(261) |
Dec
(153) |
| 2003 |
Jan
(203) |
Feb
(129) |
Mar
(125) |
Apr
(159) |
May
(120) |
Jun
(165) |
Jul
(185) |
Aug
(181) |
Sep
(149) |
Oct
(165) |
Nov
(199) |
Dec
(165) |
| 2004 |
Jan
(121) |
Feb
(155) |
Mar
(246) |
Apr
(132) |
May
(113) |
Jun
(59) |
Jul
(146) |
Aug
(58) |
Sep
(96) |
Oct
(150) |
Nov
(143) |
Dec
(66) |
| 2005 |
Jan
(194) |
Feb
(193) |
Mar
(127) |
Apr
(53) |
May
(74) |
Jun
(43) |
Jul
(45) |
Aug
(83) |
Sep
(72) |
Oct
(74) |
Nov
(103) |
Dec
(79) |
| 2006 |
Jan
(129) |
Feb
(116) |
Mar
(124) |
Apr
(97) |
May
(44) |
Jun
(48) |
Jul
(22) |
Aug
(38) |
Sep
(23) |
Oct
(68) |
Nov
(62) |
Dec
(41) |
| 2007 |
Jan
(41) |
Feb
(27) |
Mar
(22) |
Apr
(19) |
May
(17) |
Jun
(11) |
Jul
(5) |
Aug
(6) |
Sep
(13) |
Oct
(21) |
Nov
(13) |
Dec
(18) |
| 2008 |
Jan
(25) |
Feb
(7) |
Mar
(19) |
Apr
|
May
(12) |
Jun
(12) |
Jul
(3) |
Aug
(14) |
Sep
(5) |
Oct
|
Nov
(5) |
Dec
(4) |
| 2009 |
Jan
|
Feb
(4) |
Mar
|
Apr
(2) |
May
(2) |
Jun
(3) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(7) |
| 2010 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|
From: Mike M. <ch...@mi...> - 2010-12-03 23:02:41
|
Hello dri-devel/users, It looks like these lists are no-longer in use, except for some bug tracker tickets there is vary little traffic on these lists. The lists currently being used are here: http://lists.freedesktop.org/mailman/listinfo/dri-devel http://lists.freedesktop.org/mailman/listinfo/dri-users I'm just informing you of this because I've just discovered it for myself and I wanted to make you aware that you may still be a subscriber. I'm also testing to see if the new lists will receive this message. |
|
From: Dariush F. <da...@fo...> - 2010-02-27 15:35:05
|
Hi, is HDMI audio already supposed to work using a RS690 GPU? (on a current 2.6.33 kernel) r600_audio_chipset_supported() in r600_audio.c indicates this, but r600_audio_init() doesn't seem to be called anywhere from the rs690 code paths. As a quick hack I tried to add a call to r600_audio_init() to the end of rs690_init(). dmesg output indicates "[drm] Enabling audio support", but audio still won't work. cheers Dariush |
|
From: Ekhlas S. <ekh...@re...> - 2010-02-06 00:05:12
|
Hi, I am trying to install Mesa 7.7 on a RHEL 5.4 64-bit machine. I was compiling Mesa with direct rendering using make linux-dri-x86-64 and I got the following error after the compilation runs for quite some time: ../../lib64/libGL.so: undefined reference to `drmOpenOnce' ../../lib64/libGL.so: undefined reference to `XDamageAdd' ../../lib64/libGL.so: undefined reference to `drmCloseOnce' My web search tells me I need to upgrade libdrm packages. But I have installed the latest packages of libdrm(libdrm 2.4.17). Same with XDamage (version 1.1.2). Can someone please help me? Why am I getting this error? Thanks. Ekhlas. |
|
From: Norbert P. <pre...@lo...> - 2009-12-25 16:53:33
|
Any remarks on that, or suggestions where to post it. It is 100%
reproducible, and turning KMS off fixes it, so it has to be in KMS?!?!
On Mo, 21 Dez 2009, Norbert Preining wrote:
> Hi everyone,
>
> I have a very strange thing going on:
> laptop: sony vaio z11
> linux 2.6.32, 2.6.32.2
> Intel Mobile Intel® GM45 Express Chipset
> Debian/unstable up2date
> xserver-xorg-video-intel 2.9.1-1
> xserver-xorg 7.4-4
> KMS enabled in the kernel config file
>
> The problem is that under special circumstances closing the lid and
> reopening it does not turn back on the backlight.
>
> When I do NOT log into any session -> it works (backlight back on)
> when I log into a session that does not touch dri/drm -> it works
> (like twm, or lxde)
> when I log into a session with dri/drm (composite?) like kde/gnome
> -> backlight remains off after opening the lid and cannot
> be reactivated again
>
> I tried that several times and it is 100% reproducible.
>
> As soon as I deactivate KMS it works again under all circumstances.
>
> So I assume that it has something to do with the KMS, but I have
> no idea how to track that down any further.
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
BOLSOVER
One of those brown plastic trays with bumps on, placed upside down in
boxes of chocolates to make you think you're-getting two layers.
--- Douglas Adams, The Meaning of Liff
|
|
From: Norbert P. <pre...@lo...> - 2009-12-21 18:37:47
|
Hi everyone,
I have a very strange thing going on:
laptop: sony vaio z11
linux 2.6.32, 2.6.32.2
Intel Mobile Intel® GM45 Express Chipset
Debian/unstable up2date
xserver-xorg-video-intel 2.9.1-1
xserver-xorg 7.4-4
KMS enabled in the kernel config file
The problem is that under special circumstances closing the lid and
reopening it does not turn back on the backlight.
When I do NOT log into any session -> it works (backlight back on)
when I log into a session that does not touch dri/drm -> it works
(like twm, or lxde)
when I log into a session with dri/drm (composite?) like kde/gnome
-> backlight remains off after opening the lid and cannot
be reactivated again
I tried that several times and it is 100% reproducible.
As soon as I deactivate KMS it works again under all circumstances.
So I assume that it has something to do with the KMS, but I have
no idea how to track that down any further.
Any help is much appreciated.
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
There are of course many problems connected with life, of
which some of the most popular are `Why are people born?'
Why do they spend so much of the
intervening time wearing digital watches?'
--- The Book.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
|
|
From: Alex D. <ale...@gm...> - 2009-12-21 15:47:51
|
On Sat, Dec 19, 2009 at 7:44 PM, ny...@li... <ny...@li...> wrote: > ---------- Initial Header ----------- >> On Sat, Dec 19, 2009 at 12:48 PM, ny...@li... <ny...@li...> wrote: >> >> What part got rejected? Can you send me the radeon_atombios.c.rej? >> >> Another alternative is to download the drm-radeon-testing branch: >> >> http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-testing >> >> and apply the patch to that. >> >> >> >> Alex >> > >> > >> > Hi Alex, >> > Here's the rejected hunk vs. vanilla linux-2.6.32 tree. >> >> Looks like pretty much the whole patch. >> >> > Could you confirm the correct 'git' command? >> > >> > git clone git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git >> >> yes: >> git clone git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git >> cd drm-2.6 >> git checkout -b drm-radeon-testing origin/drm-radeon-testing >> >> Alex > > Eureka! That branch with your patch works great. > I get a 180x56 console, transition between X11 and console > is flawless and takes no noticeable time. > > Do you need me to collect any info from the system? > Many thanks for your help, Alex! Great. Dave should pick up the patch and it will show up in the next kernel. Alex |
|
From: Alex D. <ale...@gm...> - 2009-12-19 18:48:28
|
On Sat, Dec 19, 2009 at 12:48 PM, ny...@li... <ny...@li...> wrote: >> What part got rejected? Can you send me the radeon_atombios.c.rej? >> Another alternative is to download the drm-radeon-testing branch: >> http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-testing >> and apply the patch to that. >> >> Alex > > > Hi Alex, > Here's the rejected hunk vs. vanilla linux-2.6.32 tree. Looks like pretty much the whole patch. > Could you confirm the correct 'git' command? > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git yes: git clone git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git cd drm-2.6 git checkout -b drm-radeon-testing origin/drm-radeon-testing Alex > > Cheers, > Daide > |
|
From: Alex D. <ale...@gm...> - 2009-12-19 16:08:14
|
On Sat, Dec 19, 2009 at 9:56 AM, ny...@li... <ny...@li...> wrote: > ---------- Initial Header ----------- > > From : "Alex Deucher" ale...@gm... > To : "Davide Manzella" ny...@li... > Cc : dri...@li... > Date : Fri, 18 Dec 2009 11:41:29 -0500 > Subject : Re: [Dri-users] KMS & Mobility Radeon X1400 (LifeBook N6410): black console on internal display > > > > > > >> The problem is the video bios on your card has the same ddc line >> specified for both LVDS and VGA so they get combined as the same >> connector. The attached patch should fix the issue. Can you confirm? >> Can you also send me a copy of your video bios? >> >> (as root): >> cd /sys/bus/pci/devices/<pci bus id>/ >> echo 1 > rom >> cat rom > /tmp/vbios.rom >> echo 0 > rom >> >> Alex > > > Hello Alex, > Please find in attachement the vbios of the n6410. > I've got a rejected chunk patching vs. linux-2.6.32 tree (vanilla). > Thanks for your time and prompt answers! > > |diff --git a/drivers/gpu/drm/radeon/radeon_atombios.c b/drivers/gpu/drm/radeon/radeon_atombios.c > |index b5912c2..321044b 100644 > |--- a/drivers/gpu/drm/radeon/radeon_atombios.c > |+++ b/drivers/gpu/drm/radeon/radeon_atombios.c > -------------------------- > Patching file drivers/gpu/drm/radeon/radeon_atombios.c using Plan A... > Hunk #1 succeeded at 610 (offset -135 lines). > Hunk #2 FAILED at 622. > 1 out of 2 hunks FAILED -- saving rejects to file drivers/gpu/drm/radeon/radeon_atombios.c.rej > Hmm... Ignoring the trailing garbage. > done What part got rejected? Can you send me the radeon_atombios.c.rej? Another alternative is to download the drm-radeon-testing branch: http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=shortlog;h=refs/heads/drm-radeon-testing and apply the patch to that. Alex |
|
From: Alex D. <ale...@gm...> - 2009-12-18 16:41:44
|
On Fri, Dec 18, 2009 at 10:44 AM, Davide Manzella <ny...@li...> wrote: > Hello All, > > The system is a Fujitsu-Siemens LifeBook N6410 with on-board > ATI Mobility Radeon X1400. > > Testing with vanilla linux-2.6.32 and > libdrm, Mesa, xf86-video-ati all from git (2009-12-15). > > I've blacklisted both 'radeon' and 'radeonfb' in /etc/modprobe.d/blacklist.conf > to prevent problems at boot, also I've removed any 'vga=' in > the bootloader (GRUB) configuration. > > As root, logged in the first virtual console: > #modprobe radeon > > Puff! The internal display turns completely black but... > After several reboots with the tree-finger-salute, > I've come to realize that the system wasn't in hang and thought > about connecting an external monitor to the VGA connector on the back, > just before the modprobe command... > Surprise! That worked and I got a nice 160x64 console. > The problem is the video bios on your card has the same ddc line specified for both LVDS and VGA so they get combined as the same connector. The attached patch should fix the issue. Can you confirm? Can you also send me a copy of your video bios? (as root): cd /sys/bus/pci/devices/<pci bus id>/ echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom Alex > The next thing I've tryied is a plain 'startx' (no modprobe in advance). > That seems to trigger the 'radeon' autoloading, the X11 server > starts 1440x900 but when I ctl+alt+f1...f6, > I'll stare at a black internal display. > > Some interesting lines from syslog: > > Dec 17 15:32:55 pancho-11 kernel: [drm] radeon: Initializing kernel modesetting. > Dec 17 15:32:55 pancho-11 kernel: [drm] register mmio base: 0xF0000000 > Dec 17 15:32:55 pancho-11 kernel: [drm] register mmio size: 65536 > Dec 17 15:32:55 pancho-11 kernel: ATOM BIOS: M54P > > [snip] > Dec 17 15:32:55 pancho-11 kernel: [drm] radeon: ib pool ready. > Dec 17 15:32:55 pancho-11 kernel: [drm] ib test succeeded in 0 usecs > Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: adapter [] registered > Dec 17 15:32:55 pancho-11 kernel: [drm] Radeon Display Connectors > Dec 17 15:32:55 pancho-11 kernel: [drm] Connector 0: > Dec 17 15:32:55 pancho-11 kernel: [drm] VGA > Dec 17 15:32:55 pancho-11 kernel: [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 > 0x7e48 0x7e48 0x7e4c 0x7e4c > Dec 17 15:32:55 pancho-11 kernel: [drm] Encoders: > Dec 17 15:32:55 pancho-11 kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1 > Dec 17 15:32:55 pancho-11 kernel: [drm] LCD1: INTERNAL_LVTM1 > Dec 17 15:32:55 pancho-11 kernel: [drm] Connector 1: > Dec 17 15:32:55 pancho-11 kernel: [drm] S-video > Dec 17 15:32:55 pancho-11 kernel: [drm] Encoders: > Dec 17 15:32:55 pancho-11 kernel: [drm] TV1: INTERNAL_KLDSCP_DAC2 > Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: master_xfer[0] W, addr=0x50, len=1 > Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: master_xfer[1] R, addr=0x50, len=128 > Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: NAK from device addr 0x50 msg #0 > Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: master_xfer[0] W, addr=0x50, len=1 > Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: master_xfer[1] R, addr=0x50, len=1 > Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: NAK from device addr 0x50 msg #0 > Dec 17 15:32:55 pancho-11 kernel: ------------[ cut here ]------------ > Dec 17 15:32:55 pancho-11 kernel: WARNING: at > drivers/gpu/drm/drm_crtc_helper.c:1032 drm_helper_initial_config+0x36/0x52 > [drm_kms_helper]() > Dec 17 15:32:55 pancho-11 kernel: Hardware name: LifeBook N6410 > Dec 17 15:32:55 pancho-11 kernel: No connectors reported connected with modes > Dec 17 15:32:55 pancho-11 kernel: Modules linked in: radeon(+) ttm > drm_kms_helper drm i2c_algo_bit ipv6 usbhid usb_storage arc4 ecb firewire_ohci > firewire_core iwl3945 uhci_hcd iwlcore joydev intel_agp ehci_hcd agpgart > crc_itu_t usbcore i2c_i801 tg3 yenta_socket rsrc_nonstatic ohci1394 mac80211 > cfg80211 rfkill psmouse libphy pcmcia_core ieee1394 pcspkr > led_class rtc_cmos sg rtc_core serio_raw input_polldev evdev rtc_lib > Dec 17 15:32:55 pancho-11 kernel: Pid: 1675, comm: modprobe Not tainted > 2.6.32-o1a #2 > Dec 17 15:32:55 pancho-11 kernel: Call Trace: > Dec 17 15:32:55 pancho-11 kernel: [<c1023a4f>] warn_slowpath_common+0x65/0x7c > Dec 17 15:32:55 pancho-11 kernel: [<f8077c64>] ? > drm_helper_initial_config+0x36/0x52 [drm_kms_helper] > Dec 17 15:32:55 pancho-11 kernel: [<c1023a9a>] warn_slowpath_fmt+0x24/0x27 > Dec 17 15:32:55 pancho-11 kernel: [<f8077c64>] > drm_helper_initial_config+0x36/0x52 [drm_kms_helper] > Dec 17 15:32:55 pancho-11 kernel: [<f8375ad0>] radeon_modeset_init+0x453/0x45d > [radeon] > Dec 17 15:32:55 pancho-11 kernel: [<f83654a6>] radeon_driver_load_kms+0xbd/0xcb > [radeon] > Dec 17 15:32:55 pancho-11 kernel: [<f80eaa58>] drm_get_dev+0x2c3/0x3a3 [drm] > Dec 17 15:32:55 pancho-11 kernel: [<f83996c4>] radeon_pci_probe+0xd/0x96 > [radeon] > Dec 17 15:32:55 pancho-11 kernel: [<c1117176>] local_pci_probe+0xe/0x10 > Dec 17 15:32:55 pancho-11 kernel: [<c11177cc>] pci_device_probe+0x43/0x66 > Dec 17 15:32:55 pancho-11 kernel: [<c116b45a>] driver_probe_device+0x7e/0xf2 > Dec 17 15:32:55 pancho-11 kernel: [<c116b511>] __driver_attach+0x43/0x5f > Dec 17 15:32:55 pancho-11 kernel: [<c116ae7b>] bus_for_each_dev+0x3d/0x67 > Dec 17 15:32:55 pancho-11 kernel: [<c116b32e>] driver_attach+0x14/0x16 > Dec 17 15:32:55 pancho-11 kernel: [<c116b4ce>] ? __driver_attach+0x0/0x5f > Dec 17 15:32:55 pancho-11 kernel: [<c116a926>] bus_add_driver+0x94/0x1c4 > Dec 17 15:32:55 pancho-11 kernel: [<c110786e>] ? kset_find_obj+0x23/0x4e > Dec 17 15:32:55 pancho-11 kernel: [<c116b73f>] driver_register+0x79/0xe0 > Dec 17 15:32:55 pancho-11 kernel: [<c1117991>] __pci_register_driver+0x38/0x95 > Dec 17 15:32:55 pancho-11 kernel: [<f80e74ac>] drm_init+0x5d/0xb5 [drm] > Dec 17 15:32:55 pancho-11 kernel: [<f80ab000>] ? radeon_init+0x0/0xae [radeon] > Dec 17 15:32:55 pancho-11 kernel: [<f80ab0ac>] radeon_init+0xac/0xae [radeon] > Dec 17 15:32:55 pancho-11 kernel: [<c1001139>] do_one_initcall+0x4c/0x131 > Dec 17 15:32:55 pancho-11 kernel: [<c1042ab9>] sys_init_module+0xa7/0x1de > Dec 17 15:32:55 pancho-11 kernel: [<c1002888>] sysenter_do_call+0x12/0x26 > Dec 17 15:32:55 pancho-11 kernel: ---[ end trace 99b99882e4dab160 ]--- > Dec 17 15:32:55 pancho-11 kernel: [drm] Initialized radeon 2.0.0 20080528 for > 0000:01:00.0 on minor 0 > > > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > -- > _______________________________________________ > Dri-users mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-users > |
|
From: Davide M. <ny...@li...> - 2009-12-18 15:55:21
|
Hello All, The system is a Fujitsu-Siemens LifeBook N6410 with on-board ATI Mobility Radeon X1400. Testing with vanilla linux-2.6.32 and libdrm, Mesa, xf86-video-ati all from git (2009-12-15). I've blacklisted both 'radeon' and 'radeonfb' in /etc/modprobe.d/blacklist.conf to prevent problems at boot, also I've removed any 'vga=' in the bootloader (GRUB) configuration. As root, logged in the first virtual console: #modprobe radeon Puff! The internal display turns completely black but... After several reboots with the tree-finger-salute, I've come to realize that the system wasn't in hang and thought about connecting an external monitor to the VGA connector on the back, just before the modprobe command... Surprise! That worked and I got a nice 160x64 console. The next thing I've tryied is a plain 'startx' (no modprobe in advance). That seems to trigger the 'radeon' autoloading, the X11 server starts 1440x900 but when I ctl+alt+f1...f6, I'll stare at a black internal display. Some interesting lines from syslog: Dec 17 15:32:55 pancho-11 kernel: [drm] radeon: Initializing kernel modesetting. Dec 17 15:32:55 pancho-11 kernel: [drm] register mmio base: 0xF0000000 Dec 17 15:32:55 pancho-11 kernel: [drm] register mmio size: 65536 Dec 17 15:32:55 pancho-11 kernel: ATOM BIOS: M54P [snip] Dec 17 15:32:55 pancho-11 kernel: [drm] radeon: ib pool ready. Dec 17 15:32:55 pancho-11 kernel: [drm] ib test succeeded in 0 usecs Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: adapter [] registered Dec 17 15:32:55 pancho-11 kernel: [drm] Radeon Display Connectors Dec 17 15:32:55 pancho-11 kernel: [drm] Connector 0: Dec 17 15:32:55 pancho-11 kernel: [drm] VGA Dec 17 15:32:55 pancho-11 kernel: [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c Dec 17 15:32:55 pancho-11 kernel: [drm] Encoders: Dec 17 15:32:55 pancho-11 kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1 Dec 17 15:32:55 pancho-11 kernel: [drm] LCD1: INTERNAL_LVTM1 Dec 17 15:32:55 pancho-11 kernel: [drm] Connector 1: Dec 17 15:32:55 pancho-11 kernel: [drm] S-video Dec 17 15:32:55 pancho-11 kernel: [drm] Encoders: Dec 17 15:32:55 pancho-11 kernel: [drm] TV1: INTERNAL_KLDSCP_DAC2 Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: master_xfer[0] W, addr=0x50, len=1 Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: master_xfer[1] R, addr=0x50, len=128 Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: NAK from device addr 0x50 msg #0 Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: master_xfer[0] W, addr=0x50, len=1 Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: master_xfer[1] R, addr=0x50, len=1 Dec 17 15:32:55 pancho-11 kernel: i2c i2c-1: NAK from device addr 0x50 msg #0 Dec 17 15:32:55 pancho-11 kernel: ------------[ cut here ]------------ Dec 17 15:32:55 pancho-11 kernel: WARNING: at drivers/gpu/drm/drm_crtc_helper.c:1032 drm_helper_initial_config+0x36/0x52 [drm_kms_helper]() Dec 17 15:32:55 pancho-11 kernel: Hardware name: LifeBook N6410 Dec 17 15:32:55 pancho-11 kernel: No connectors reported connected with modes Dec 17 15:32:55 pancho-11 kernel: Modules linked in: radeon(+) ttm drm_kms_helper drm i2c_algo_bit ipv6 usbhid usb_storage arc4 ecb firewire_ohci firewire_core iwl3945 uhci_hcd iwlcore joydev intel_agp ehci_hcd agpgart crc_itu_t usbcore i2c_i801 tg3 yenta_socket rsrc_nonstatic ohci1394 mac80211 cfg80211 rfkill psmouse libphy pcmcia_core ieee1394 pcspkr led_class rtc_cmos sg rtc_core serio_raw input_polldev evdev rtc_lib Dec 17 15:32:55 pancho-11 kernel: Pid: 1675, comm: modprobe Not tainted 2.6.32-o1a #2 Dec 17 15:32:55 pancho-11 kernel: Call Trace: Dec 17 15:32:55 pancho-11 kernel: [<c1023a4f>] warn_slowpath_common+0x65/0x7c Dec 17 15:32:55 pancho-11 kernel: [<f8077c64>] ? drm_helper_initial_config+0x36/0x52 [drm_kms_helper] Dec 17 15:32:55 pancho-11 kernel: [<c1023a9a>] warn_slowpath_fmt+0x24/0x27 Dec 17 15:32:55 pancho-11 kernel: [<f8077c64>] drm_helper_initial_config+0x36/0x52 [drm_kms_helper] Dec 17 15:32:55 pancho-11 kernel: [<f8375ad0>] radeon_modeset_init+0x453/0x45d [radeon] Dec 17 15:32:55 pancho-11 kernel: [<f83654a6>] radeon_driver_load_kms+0xbd/0xcb [radeon] Dec 17 15:32:55 pancho-11 kernel: [<f80eaa58>] drm_get_dev+0x2c3/0x3a3 [drm] Dec 17 15:32:55 pancho-11 kernel: [<f83996c4>] radeon_pci_probe+0xd/0x96 [radeon] Dec 17 15:32:55 pancho-11 kernel: [<c1117176>] local_pci_probe+0xe/0x10 Dec 17 15:32:55 pancho-11 kernel: [<c11177cc>] pci_device_probe+0x43/0x66 Dec 17 15:32:55 pancho-11 kernel: [<c116b45a>] driver_probe_device+0x7e/0xf2 Dec 17 15:32:55 pancho-11 kernel: [<c116b511>] __driver_attach+0x43/0x5f Dec 17 15:32:55 pancho-11 kernel: [<c116ae7b>] bus_for_each_dev+0x3d/0x67 Dec 17 15:32:55 pancho-11 kernel: [<c116b32e>] driver_attach+0x14/0x16 Dec 17 15:32:55 pancho-11 kernel: [<c116b4ce>] ? __driver_attach+0x0/0x5f Dec 17 15:32:55 pancho-11 kernel: [<c116a926>] bus_add_driver+0x94/0x1c4 Dec 17 15:32:55 pancho-11 kernel: [<c110786e>] ? kset_find_obj+0x23/0x4e Dec 17 15:32:55 pancho-11 kernel: [<c116b73f>] driver_register+0x79/0xe0 Dec 17 15:32:55 pancho-11 kernel: [<c1117991>] __pci_register_driver+0x38/0x95 Dec 17 15:32:55 pancho-11 kernel: [<f80e74ac>] drm_init+0x5d/0xb5 [drm] Dec 17 15:32:55 pancho-11 kernel: [<f80ab000>] ? radeon_init+0x0/0xae [radeon] Dec 17 15:32:55 pancho-11 kernel: [<f80ab0ac>] radeon_init+0xac/0xae [radeon] Dec 17 15:32:55 pancho-11 kernel: [<c1001139>] do_one_initcall+0x4c/0x131 Dec 17 15:32:55 pancho-11 kernel: [<c1042ab9>] sys_init_module+0xa7/0x1de Dec 17 15:32:55 pancho-11 kernel: [<c1002888>] sysenter_do_call+0x12/0x26 Dec 17 15:32:55 pancho-11 kernel: ---[ end trace 99b99882e4dab160 ]--- Dec 17 15:32:55 pancho-11 kernel: [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0 |
|
From: Nicolas C. <nic...@ym...> - 2009-08-20 09:41:39
|
Hello,
I have an application which must to synchronize with the vertical synchronisation of my display.
To do this synchronization, I use a function of GLX (glXWaitVideoSyncSGI).
This function call the function DRM to wait the vertical synchronization (drmWaitVBlank) and the driver (drm.ko) does a wait on the pipe A of my Xserver.
But my output (LVDS) of my Xserver is connected to the pipe B and so the driver (drm.ko) does a wake up on the pipe B.
So my applicaton is not synchronized with my display.
I would like to know how to configure my application for it uses the pipe B when it does a wait for the vertical synchronization.
Where I can configure my application for it uses the pipe B for the VSync ?
Is it in the xorg.conf or elsewhere?
Thanks, Nicolas
|
|
From: Nicolas C. <nic...@ym...> - 2009-08-17 14:01:35
|
Hi all,
I try to use the vertical synchronization on a program which use the functions of openGL (glXWaitVideoSyncSGI), but the driver drm.ko does a wait (DRM_WAIT_ON, function : drm_wait_vblank, file : drm_irq.c) on the crtc 0 and does a wake up (DRM_WAKEUP) on the crtc 1 so, I haven't synchronisation on my display, the wait take 3 secondes (3*DRM_HZ)
So I would like to know how to resolve this problem of crtc. I would like that the wait and the wake up use the same crtc (1). Somebody can help me ?
Thanks, Nicolas
|
|
From: Philipp K. K. <pk...@sp...> - 2009-06-29 05:23:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eric Appleman schrieb: > Hi, I was wondering how I would I file a bug against the aforementioned > suspects with the respect the following issue I am observing in Wine: > http://bugs.winehq.org/show_bug.cgi?id=18232 > > How would I best describe this bug when filing? > > Thanks in advance. > > - Eric Setting LIBGL_DEBUG=verbose before running the application could yield furhter information related to the problem. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpIT9gACgkQbtUV+xsoLpoeiwCeI8ylf8yDdk3Z80XhGWWSTu8n dn8AoKw61a5R6Pd3WQ6NfOWbTABRZaW+ =/oSz -----END PGP SIGNATURE----- |
|
From: Younes M. <you...@gm...> - 2009-06-29 02:35:05
|
On Sun, Jun 28, 2009 at 9:53 PM, Eric Appleman<era...@gm...> wrote: > Hi, I was wondering how I would I file a bug against the aforementioned > suspects with the respect the following issue I am observing in Wine: > http://bugs.winehq.org/show_bug.cgi?id=18232 > > How would I best describe this bug when filing? Probably the same way you described it in the Wine bug. I don't know how Intel folks diagnose performance problems, but I suspect OProfile runs for Touhou 10 and Touhou 11 would help. |
|
From: Eric A. <era...@gm...> - 2009-06-29 02:23:48
|
Hi, I was wondering how I would I file a bug against the aforementioned suspects with the respect the following issue I am observing in Wine: http://bugs.winehq.org/show_bug.cgi?id=18232 How would I best describe this bug when filing? Thanks in advance. - Eric |
|
From: Fekete N. <fe...@gm...> - 2009-05-24 18:58:24
|
Hello, I have an old laptop (Dell Latitude CPx H500 GT), which has an ATI Rage Mobility P/M AGP 2x card. (If I see well on forums, it uses the mach64 architecture.) I've installed openSUSE 11.1 with KDE 4. Because direct rendering isn't supported on this card by default, I tried to build the drivers based on this guide: http://dri.freedesktop.org/wiki/Building. I followed the steps until 1.9 without errors, I just got warning messages during the steps, I hope that isn't important. But then, actually I don't have a symlink /etc/X11/X, nor a /usr/X11R6/bin/XFree86 or /usr/X11R6/bin/Xorg directory (only a symlink xauth, which is pointing to /bin/xauth) so I don't know, how to proceed. Now DRM loads at startup, but it doesn't detect my card. dmesg says: [drm] Initialized drm 1.1.0 20060810 mach64: disagrees about version of symbol struct_module (the second line is listed 5 times) modprobe mach64 says: FATAL: Error inserting mach64 (/lib/modules/2.6.27.21-0.1-pae/kernel/char/drm/mach64.ko): Invalid module format Could someone help me? Thanks in advance, Norbi |
|
From: Enno F. <e.f...@ti...> - 2009-05-12 20:19:48
|
I fail miserably to write a direct rendering program. I think DRI is properly installed on my system, at least glxgears confirms Direct rendering: Yes. My program initializes all kind of things but when it comes to make something current I get probably confused between all contexts and windows/drawables. Is there anywhere a tutorial that tells me how to write a DRI client program (not how to compile and install DRI) or a very simple program that I could have a look at. Appreciate any pointers. Enno Fennema |
|
From: Enno F. <e.f...@ti...> - 2009-04-20 16:08:30
|
Enno Fennema wrote: > I am totally new in the drm area but try to get access to the registers > on my Radeon 9200SE. I tried > ... > I am lost and would appreciate any help. > > Enno The differences between the Precision Insight documentation and xf86drm documentation (does such a thing exist?) led me astray. Think I am on my way. Enno |
|
From: Enno F. <e.f...@ti...> - 2009-04-19 19:28:00
|
I am totally new in the drm area but try to get access to the registers
on my Radeon 9200SE. I tried
drm = drmOpen("radeon", NULL);
which returns a file descriptor 5. I thought I then had to do
rv = drmAddMap(drm, 0xfbe00000, 0x10000, DRM_REGISTERS, 0, &mapHandle);
which returns rv = -13. The documentation says the 2nd parameter should
be the physical address of the register area and is probaly wrong (it is
the linear (?) address in BAR2 of the Radeon configuration area) but how
do I find the physical address of a memory mapped IO area? Or should any
of the other arguments be different or should I call something else?
I am lost and would appreciate any help.
Enno
|
|
From: Alex D. <ale...@gm...> - 2009-02-04 15:34:12
|
On Wed, Feb 4, 2009 at 4:03 AM, Chris Collins <ch...@eo...> wrote: > Hey Thanks Alex, > > On Wed, Feb 04, 2009 at 02:41:47AM -0500, Alex Deucher wrote: > >> > Where do I look to see the drm currently on my system? >> >> should be in /usr/lib > > So, my current distribution "Slackware 12.2" has libdrm 2.3.0 > > chris@ira:~$ ls -l /usr/lib/libdrm.so* > lrwxrwxrwx 1 root root 15 2011-01-16 13:18 /usr/lib/libdrm.so -> libdrm.so.2.3.0* > lrwxrwxrwx 1 root root 15 2011-01-16 13:18 /usr/lib/libdrm.so.2 -> libdrm.so.2.3.0* > -rwxr-xr-x 1 root root 34556 2007-02-11 17:06 /usr/lib/libdrm.so.2.3.0* > > In order to test and debug, I need to build the latest development version. > I'm not exactly sure how. > > There is the wiki entry > 1. Building the DRI with X.org and Mesa > 1.3. Building libdrm > > http://dri.freedesktop.org/wiki/Building#head-b3fb665c9f24b4a32424b78428c082e830832250 > > Is this the route to build the latest development build? > Or, is there some other guide to refer to, for building and testing libdrm? yeah, that should do it. you may want to backup your old libdrm first. Alex |
|
From: Chris C. <ch...@eo...> - 2009-02-04 09:03:19
|
Hey Thanks Alex, On Wed, Feb 04, 2009 at 02:41:47AM -0500, Alex Deucher wrote: > > Where do I look to see the drm currently on my system? > > should be in /usr/lib So, my current distribution "Slackware 12.2" has libdrm 2.3.0 chris@ira:~$ ls -l /usr/lib/libdrm.so* lrwxrwxrwx 1 root root 15 2011-01-16 13:18 /usr/lib/libdrm.so -> libdrm.so.2.3.0* lrwxrwxrwx 1 root root 15 2011-01-16 13:18 /usr/lib/libdrm.so.2 -> libdrm.so.2.3.0* -rwxr-xr-x 1 root root 34556 2007-02-11 17:06 /usr/lib/libdrm.so.2.3.0* In order to test and debug, I need to build the latest development version. I'm not exactly sure how. There is the wiki entry 1. Building the DRI with X.org and Mesa 1.3. Building libdrm http://dri.freedesktop.org/wiki/Building#head-b3fb665c9f24b4a32424b78428c082e830832250 Is this the route to build the latest development build? Or, is there some other guide to refer to, for building and testing libdrm? Thanks again, --Chris |
|
From: Alex D. <ale...@gm...> - 2009-02-04 07:41:51
|
On Tue, Feb 3, 2009 at 9:46 PM, Chris Collins <ch...@eo...> wrote: > Hello, > > What is the difference between my 'system drm' and building > a new libdrm 2.4.4? the libdrm shipped with your system vs. building the upstream libdrm. If there is a problem with your local libdmr, it may be fixed in the upstream version. > > Where do I look to see the drm currently on my system? should be in /usr/lib Alex |
|
From: Chris C. <ch...@eo...> - 2009-02-04 03:16:05
|
Hello, What is the difference between my 'system drm' and building a new libdrm 2.4.4? Where do I look to see the drm currently on my system? --Chris |
|
From: R. A. K. <rak...@gm...> - 2008-12-10 18:00:19
|
On Wed, Dec 10, 2008 at 12:25 PM, Roger D Vargas <ro...@eh...> wrote: > R. Aditya Kadambi escribió: > > I have this card on my laptop and DRI does work fine. I am running > > Kubuntu 8.10. It has Mesa 7.2. > Hmm, Im using gentoo, stable. Mesa is 6.5, xf86-video-ati is 6.6.3, xorg > 7.2. It won't work on that driver versions. You need to upgrade. > > > > > > > ------------------------------------------------------------------------------ > SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. > The future of the web can't happen without you. Join us at MIX09 to help > pave the way to the Next Web now. Learn more and register at > > http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ > -- > _______________________________________________ > Dri-users mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-users > |
|
From: Roger D V. <ro...@eh...> - 2008-12-10 17:35:38
|
R. Aditya Kadambi escribió: > I have this card on my laptop and DRI does work fine. I am running > Kubuntu 8.10. It has Mesa 7.2. Hmm, Im using gentoo, stable. Mesa is 6.5, xf86-video-ati is 6.6.3, xorg 7.2. |
27 messages has been excluded from this view by a project administrator.