Re: 2 kernel warnings
At Mon, 04 Apr 2011 16:59:10 +0200, Michel Dänzer wrote: > > Does Mesa Git master work any better? Also, you could try using the Mesa > r600g driver instead of the classic r600 driver (or vice versa). Mesa was compiled with --enable-gallium-r600: http://projects.archlinux.org/svntogit/packages.git/tree/mesa/trunk/PKGBUILD I'll try mesa-git. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: 2 kernel warnings
At Mon, 04 Apr 2011 16:15:45 +0200, Michel Dänzer wrote: > > On Sam, 2011-04-02 at 01:57 +0400, Sergej Pupykin wrote: > > > > here are 2 kernel warnings from dmesg. > > > > kernel 2.6.38.2 > > xf86-video-ati 6.14.1 > > xorg-server 1.10.0.901 > > mesa 7.10.1 > > RV620 > > > > Are they already known or should I report a bug? > > They're generic symptoms of GPU lockups. Do the lockups happen when you > do anything particular? Yes, at least first trace is from 'Need for Speed: Hot Pursuit 2' under wine 1.3.16. It caused display corruption, so I killed Xorg from console. Second, not sure, probably from 'Need for Speed: Porsche Unleashed'. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
2 kernel warnings
Hi, here are 2 kernel warnings from dmesg. kernel 2.6.38.2 xf86-video-ati 6.14.1 xorg-server 1.10.0.901 mesa 7.10.1 RV620 Are they already known or should I report a bug? Apr 2 01:45:33 home kernel: [ cut here ] Apr 2 01:45:33 home kernel: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x433/0x4a0 [radeon]() Apr 2 01:45:33 home kernel: Hardware name: P5K SE/EPU Apr 2 01:45:33 home kernel: GPU lockup (waiting for 0x005A58D5 last fence id 0x005A58CF) Apr 2 01:45:33 home kernel: Modules linked in: snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ppp_async crc_ccitt sco bnep iptable_nat xt_state xt_tcpudp xt_multiport iptable_filter ip_tables x_tables jfs vboxnetflt vboxnetadp vboxdrv usbser ial rtnet3070ap rt3070ap rtutil3070ap gspca_zc3xx gspca_main tuner_simple tuner_types tea5767 ir_lirc_codec lirc_dev tda7432 ir_sony_decoder ir_jvc_decoder bttv btcx_r isc ir_rc6_decoder ir_rc5_decoder ir_nec_decoder rc_core tveeprom tuner tvaudio st iTCO_wdt iTCO_vendor_support asus_atk0110 nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_def rag_ipv4 nf_conntrack_ftp nf_conntrack tun coretemp usbhid hid ide_cd_mod usb_storage loop rfcomm l2cap btusb bluetooth rfkill usblp fuse sr_mod uhci_hcd ehci_hcd usbc ore bsd_comp sha1_generic arc4 ecb ppp_mppe ppp_synctty l2tp_ip l2tp_ppp pppox ppp_generic slhc l2tp_netlink l2tp_core atl1 mii ahci libahci snd_hda_codec_hdmi snd_hda _codec_realtek snd_hda_intel snd_hda_codec snd_emu10k1 snd_util_mem snd_ac97_codec snd_rawmidi snd_hwdep snd_bt87x snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd soundcore ac97_bus shpchp pci_hotplug videobuf_dma_sg videobuf_core v4l2_common videodev v4l2_compat_ioctl32 serio_raw emu10k1_gp gameport psmouse evdev i2c_i801 firewire_ohci firewire_core crc_itu_t intel_agp intel_gtt cdrom thermal processor button rade on ttm drm_kms_helper drm i2c_algo_bit i2c_core reiserfs ext4 jbd2 crc16 ext3 mbcache jbd ata_generic ata_piix pata_acpi sd_mod pata_marvell libata scsi_mod ide_core Apr 2 01:45:33 home kernel: Pid: 5927, comm: nfshp2.ori Tainted: GW 2.6.38-ARCH #1 Apr 2 01:45:33 home kernel: Call Trace: Apr 2 01:45:33 home kernel: [] ? warn_slowpath_common+0x7a/0xb0 Apr 2 01:45:33 home kernel: [] ? warn_slowpath_fmt+0x41/0x50 Apr 2 01:45:33 home kernel: [] ? radeon_fence_wait+0x433/0x4a0 [radeon] Apr 2 01:45:33 home kernel: [] ? __mutex_lock_slowpath+0x239/0x320 Apr 2 01:45:33 home kernel: [] ? autoremove_wake_function+0x0/0x40 Apr 2 01:45:33 home kernel: [] ? radeon_sync_obj_wait+0xc/0x10 [radeon] Apr 2 01:45:33 home kernel: [] ? ttm_bo_wait+0xa8/0x1c0 [ttm] Apr 2 01:45:33 home kernel: [] ? ttm_bo_move_accel_cleanup+0xab/0x320 [ttm] Apr 2 01:45:33 home kernel: [] ? radeon_move_blit.isra.3+0x114/0x180 [radeon] Apr 2 01:45:33 home kernel: [] ? radeon_move_ram_vram.isra.5+0x120/0x150 [radeon] Apr 2 01:45:33 home kernel: [] ? ttm_bo_list_ref_sub+0x24/0x30 [ttm] Apr 2 01:45:33 home kernel: [] ? ttm_eu_list_ref_sub+0x33/0x50 [ttm] Apr 2 01:45:33 home kernel: [] ? radeon_bo_move+0x1d8/0x1e0 [radeon] Apr 2 01:45:33 home kernel: [] ? ttm_bo_handle_move_mem+0x106/0x370 [ttm] Apr 2 01:45:33 home kernel: [] ? ttm_bo_move_buffer+0x14a/0x160 [ttm] Apr 2 01:45:33 home kernel: [] ? ttm_bo_list_ref_sub+0x24/0x30 [ttm] Apr 2 01:45:33 home kernel: [] ? ttm_eu_list_ref_sub+0x33/0x50 [ttm] Apr 2 01:45:33 home kernel: [] ? ttm_bo_validate+0x94/0x110 [ttm] Apr 2 01:45:33 home kernel: [] ? radeon_bo_list_validate+0x7c/0xe0 [radeon] Apr 2 01:45:33 home kernel: [] ? radeon_cs_parser_relocs+0x1f8/0x230 [radeon] Apr 2 01:45:33 home kernel: [] ? radeon_cs_ioctl+0x9c/0x1e0 [radeon] Apr 2 01:45:33 home kernel: [] ? drm_ioctl+0x3e4/0x4c0 [drm] Apr 2 01:45:33 home kernel: [] ? radeon_cs_ioctl+0x0/0x1e0 [radeon] Apr 2 01:45:33 home kernel: [] ? __pte_alloc+0xeb/0x150 Apr 2 01:45:33 home kernel: [] ? handle_mm_fault+0x1b0/0x330 Apr 2 01:45:33 home kernel: [] ? radeon_kms_compat_ioctl+0xf/0x30 [radeon] Apr 2 01:45:33 home kernel: [] ? compat_sys_ioctl+0xe1/0x1390 Apr 2 01:45:33 home kernel: [] ? do_mmap_pgoff+0x34c/0x360 Apr 2 01:45:33 home kernel: [] ? read_tsc+0x9/0x20 Apr 2 01:45:33 home kernel: [] ? getnstimeofday+0x52/0xe0 Apr 2 01:45:33 home kernel: [] ? do_gettimeofday+0x15/0x50 Apr 2 01:45:33 home kernel: [] ? sysenter_dispatch+0x7/0x2e Apr 2 01:45:33 home kernel: ---[ end trace d4b962395e262d5c ]--- Mar 28 01:14:31 home kernel: [ cut here ] Mar 28 01:14:31 home kernel: WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x429/0x490 [radeon]() Mar 28 01:14:31 home kernel: Hardware name: P5K SE/EPU Mar 28 01:14:31 home kernel: GPU lockup (waiting for 0x02350E48 last fence id 0x02350E41) Mar 28 01:14:31 home kernel: Modules link
Re: Periodically GPU softreset with Xorg freeze
On 11.12.2010 00:38, Jerome Glisse wrote: Should be good, glxinfo | grep render should show gallium . It works without problem slightly longer, but after ~10 hours I get oops (below) But Xorg still alive, just hangs for a few seconds. *** hpet1: lost 1 rtc interrupts radeon :01:00.0: GPU lockup CP stall for more than 10023msec [ cut here ] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:244 radeon_fence_wait+0x376/0x3e0 [radeon]() Hardware name: P5K SE/EPU GPU lockup (waiting for 0x009288AE last fence id 0x009288AD) Modules linked in: snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul ppp_async crc_ccitt nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc sco bnep iptable_nat xt_state xt_tcpudp xt_multiport iptable_filter ip_tables x_tables jfs vboxnetflt vboxnetadp vboxdrv usbserial rtnet3070ap rt3070ap rtutil3070ap gspca_zc3xx gspca_main st iTCO_wdt iTCO_vendor_support asus_atk0110 nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack tun coretemp usbhid hid ide_cd_mod usb_storage loop rfcomm l2cap btusb bluetooth rfkill usblp fuse sr_mod uhci_hcd ehci_hcd usbcore bsd_comp sha1_generic arc4 ecb ppp_mppe ppp_synctty l2tp_ip l2tp_ppp pppox ppp_generic slhc l2tp_netlink l2tp_core atl1 mii ahci libahci snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_emu10k1 snd_util_mem snd_ac97_codec snd_rawmidi snd_hwdep snd_bt87x snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd soundcore ac97_bus shpchp pci_hotplug ir_lirc_codec lirc_dev ir_sony_decoder videobuf_dma_sg ir_jvc_decoder videobuf_core ir_rc6_decoder v4l2_common videodev v4l2_compat_ioctl32 ir_rc5_decoder v4l1_compat ir_nec_decoder ir_common ir_core serio_raw emu10k1_gp gameport psmouse evdev i2c_i801 firewire_ohci firewire_core crc_itu_t radeon ttm drm_kms_helper i2c_algo_bit drm i2c_core intel_agp intel_gtt cdrom thermal processor button rtc_cmos rtc_core rtc_lib reiserfs ext4 jbd2 crc16 ext3 mbcache jbd ata_generic ata_piix pata_acpi sd_mod pata_marvell libata scsi_mod ide_core Pid: 6942, comm: X Tainted: GW 2.6.37-rc5-custom #2 Call Trace: [] warn_slowpath_common+0x7a/0xb0 [] warn_slowpath_fmt+0x41/0x50 [] radeon_fence_wait+0x376/0x3e0 [radeon] [] ? autoremove_wake_function+0x0/0x40 [] radeon_sync_obj_wait+0xc/0x10 [radeon] [] ttm_bo_wait+0xf9/0x1b0 [ttm] [] radeon_gem_wait_idle_ioctl+0x8e/0x110 [radeon] [] drm_ioctl+0x3d4/0x4b0 [drm] [] ? radeon_gem_wait_idle_ioctl+0x0/0x110 [radeon] [] ? save_i387_xstate+0xdb/0x230 [] ? recalc_sigpending+0x16/0x40 [] ? do_signal+0x17d/0x7c0 [] do_vfs_ioctl+0x95/0x540 [] sys_ioctl+0x81/0xa0 [] system_call_fastpath+0x16/0x1b ---[ end trace 4553c3fda2bae70d ]--- [drm] Disabling audio support radeon :01:00.0: GPU softreset radeon :01:00.0: R_008010_GRBM_STATUS=0xA0003030 radeon :01:00.0: R_008014_GRBM_STATUS2=0x0003 radeon :01:00.0: R_000E50_SRBM_STATUS=0x20C0 radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x7FEE radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x0001 radeon :01:00.0: R_008010_GRBM_STATUS=0xA0003030 radeon :01:00.0: R_008014_GRBM_STATUS2=0x0003 radeon :01:00.0: R_000E50_SRBM_STATUS=0x200080C0 radeon :01:00.0: GPU reset succeed radeon :01:00.0: WB enabled [drm] ring test succeeded in 0 usecs [drm] ib test succeeded in 1 usecs [drm] Enabling audio support *** ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Periodically GPU softreset with Xorg freeze
At Fri, 10 Dec 2010 12:30:25 -0500, Jerome Glisse wrote: > > Still test with r600g master, i don't know what kwin does when all > effect are disabled, it might still do things like compiz. Is it enough to build fresh version of these packages? libgl-git-gallium: http://aur.archlinux.org/packages.php?ID=38091 ati-dri-git-gallium: http://aur.archlinux.org/packages.php?ID=38090 Both of them use git://anongit.freedesktop.org/git/mesa/mesa and builds gallium enabled ati drivers and libgl libgl options (http://aur.archlinux.org/packages/libgl-git-gallium/libgl-git-gallium/PKGBUILD): ./autogen.sh \ --prefix=/usr \ --with-dri-driverdir=/usr/lib/xorg/modules/dri \ --with-dri-drivers=swrast \ --enable-glx-tls \ --with-driver=dri \ --enable-xcb \ --disable-egl \ --disable-glu \ --disable-glut \ --disable-glw \ --enable-gallium \ --enable-gallium-swrast ati-dri options (http://aur.archlinux.org/packages/ati-dri-git-gallium/ati-dri-git-gallium/PKGBUILD): ./autogen.sh --prefix=/usr \ --with-dri-driverdir=/usr/lib/xorg/modules/dri \ --with-dri-drivers=radeon,r200,r300,r600 \ --enable-glx-tls \ --with-driver=dri \ --enable-xcb \ --disable-glu \ --disable-glut \ --enable-gallium \ --enable-gallium-radeon \ --enable-gallium-r600 \ --disable-glw ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Periodically GPU softreset with Xorg freeze
At Fri, 10 Dec 2010 10:13:24 -0500, Jerome Glisse wrote: > > You use a compositor ? If so please try r600g mesa/master. > Who is compositor? It is default KDE4, all effects are disabled in KDE. Window manager is KWin. Composite extension is enabled. Section "Extensions" Option "Composite" "Enable" Option "XVideo""Enable" Option "RENDER""Enable" Option "DAMAGE""Enable" EndSection ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Periodically GPU softreset with Xorg freeze
Hi, I have periodically X freezes with following (may be incomplete) data in dmesg. kernel 2.6.37-rc5 xf86-video-ati 6.13.2 mesa 7.9 KDE 4.5.4 RV620 chipset no activity needed to reproduce it *** Dec 10 16:06:54 home kernel: [drm] Disabling audio support Dec 10 16:06:54 home kernel: radeon :01:00.0: GPU softreset Dec 10 16:06:54 home kernel: radeon :01:00.0: R_008010_GRBM_STATUS=0xA0003030 Dec 10 16:06:54 home kernel: radeon :01:00.0: R_008014_GRBM_STATUS2=0x0003 Dec 10 16:06:54 home kernel: radeon :01:00.0: R_000E50_SRBM_STATUS=0x20C0 Dec 10 16:06:54 home kernel: radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x7FEE Dec 10 16:06:54 home kernel: radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x0001 Dec 10 16:06:54 home kernel: radeon :01:00.0: R_008010_GRBM_STATUS=0xA0003030 Dec 10 16:06:54 home kernel: radeon :01:00.0: R_008014_GRBM_STATUS2=0x0003 Dec 10 16:06:54 home kernel: radeon :01:00.0: R_000E50_SRBM_STATUS=0x200080C0 Dec 10 16:06:54 home kernel: radeon :01:00.0: GPU reset succeed Dec 10 16:06:54 home kernel: radeon :01:00.0: WB enabled Dec 10 16:06:54 home kernel: [drm] ring test succeeded in 1 usecs Dec 10 16:06:54 home kernel: [drm] ib test succeeded in 1 usecs Dec 10 16:06:54 home kernel: [drm] Enabling audio support Dec 10 16:07:26 home kernel: SysRq : Emergency Sync Alt+SysRq+S, Alt+SysRq+B pressed here *** ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[PATCH] improve radeon.man. Was Re: ForceTVOut option in KMS
Hi, this patch adds couple of words to ForceTVOut option description. Hope it will prevent others from confusion. Now description is: *** Option "ForceTVOut" "boolean" (UMS only) Enable this option to force TV-out to always be detected as attached. The default is off. Use kernel features to force TV-out in KMS. *** 0001-man-page-add-kms-ums-info-to-ForceTVOut-option.patch Description: Binary data ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: ForceTVOut option in KMS
On 09.12.2010 01:16, Sergej Pupykin wrote: I am still wondered why UMS detects TV but KMS does not. Can it be because of ForceTVOut in xorg.conf ? (in the same way as with video= parameter) ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: ForceTVOut option in KMS
On 09.12.2010 00:41, Alex Deucher wrote: It should probably be renamed to "9-pin_DIN-1" since grub doesn't parse spaces correctly when passing the parameters to the kernel. I replaced it to dot. Now my tv-out (https://bugs.freedesktop.org/show_bug.cgi?id=29494) works with "video=DVI-I-1:1280x1024...@60e video=9-pin.DIN-1:1024x768...@60e" I am still wondered why UMS detects TV but KMS does not. Do you know if DRM maintainers will rename connector name or which bootloader treats spaces correctly? lilo, grub2? ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: ForceTVOut option in KMS
On 09.12.2010 00:21, Alex Deucher wrote: "video=9-pin DIN-1:1024x768...@60e" but kernel panics saying about bad variable name I don't think you have a space in the name. grub doesn't deal with it properly unfortunately. drm_connector_enum_list contains "9-pin DIN". Then it used in drm_fb_helper.c as fb_get_options(drm_get_connector_name(fb_helper_conn->connector), &option) drm_get_connector_name() function just sprintfs: snprintf(buf, 32, "%s-%d", drm_connector_enum_list[connector->connector_type].name, connector->connector_type_id); so if I understand correctly we have "9-pin DIN-1" in fb_get_options() call. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: ForceTVOut option in KMS
On 07.12.2010 01:49, Sergej Pupykin wrote: On 04.12.2010 13:59, Sergej Pupykin wrote: Hi, how can I force TV-out on in KMS? I found video kernel option explanation on http://nouveau.freedesktop.org/wiki/KernelModeSetting I add video=DVI-I-1:1280x1024...@60e video=DIN-1:1024x768...@60e into grub/menu.lst but it affects only DVI-I-1 output, it looks like 2nd video option is ignored. Also I try to add single "video=DIN-1:1024x768...@60e" without success. In dmesg I can see "forcing DVI-I-" but can not see anything about DIN It looks like TV output named as "9-pin DIN-1" according to /sys/class/drm/ ls -1 /sys/class/drm/ card0 card0-9-pin DIN-1 card0-DVI-I-1 card0-VGA-1 controlD64 ttm version Does anybody know how to pass space into kernel parameter? I try quotes: video="9-pin DIN-1:1024x768...@60e" and "video=9-pin DIN-1:1024x768...@60e" but kernel panics saying about bad variable name ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: ForceTVOut option in KMS
On 04.12.2010 13:59, Sergej Pupykin wrote: Hi, how can I force TV-out on in KMS? I found video kernel option explanation on http://nouveau.freedesktop.org/wiki/KernelModeSetting I add video=DVI-I-1:1280x1024...@60e video=DIN-1:1024x768...@60e into grub/menu.lst but it affects only DVI-I-1 output, it looks like 2nd video option is ignored. Also I try to add single "video=DIN-1:1024x768...@60e" without success. In dmesg I can see "forcing DVI-I-" but can not see anything about DIN *** booting with both video options *** [drm] radeon kernel modesetting enabled. radeon :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 radeon :01:00.0: setting latency timer to 64 [drm] initializing kernel modesetting (RV620 0x1002:0x95C5). [drm] register mmio base: 0xFE8E [drm] register mmio size: 65536 ATOM BIOS: RV620 radeon :01:00.0: VRAM: 256M 0x - 0x0FFF (256M used) radeon :01:00.0: GTT: 512M 0x1000 - 0x2FFF [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 64bits DDR [TTM] Zone kernel: Available graphics memory: 1028022 kiB. [TTM] Initializing pool allocator. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. radeon :01:00.0: irq 40 for MSI/MSI-X radeon :01:00.0: radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV620 Microcode [drm] ring test succeeded in 1 usecs [drm] radeon: ib pool ready. [drm] ib test succeeded in 0 usecs [drm] Enabling audio support failed to evaluate ATIF got AE_BAD_PARAMETER Radeon i2c bit bus 0x90: Test OK Radeon i2c bit bus 0x91: Test OK Radeon i2c bit bus 0x92: Test OK Radeon i2c bit bus 0x93: bus seems to be busy [drm:radeon_i2c_create] *ERROR* Failed to register bit i2c 0x93 Radeon i2c bit bus 0x14: Test OK [drm] Radeon Display Connectors [drm] Connector 0: [drm] DIN [drm] Encoders: [drm] TV1: INTERNAL_KLDSCP_DAC2 [drm] Connector 1: [drm] VGA [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [drm] Encoders: [drm] CRT2: INTERNAL_KLDSCP_DAC2 [drm] Connector 2: [drm] DVI-I [drm] HPD1 [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] DFP1: INTERNAL_KLDSCP_LVTMA [drm] Internal thermal controller with fan control [drm] radeon: power management initialized [drm] forcing DVI-I-1 connector ON [drm] fb mappable at 0xD0141000 [drm] vram apper at 0xD000 [drm] size 5242880 [drm] fb depth is 24 [drm]pitch is 5120 Console: switching to colour frame buffer device 160x64 fb0: radeondrmfb frame buffer device drm: registered panic notifier [drm] Initialized radeon 2.6.0 20080528 for :01:00.0 on minor 0 ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
ForceTVOut option in KMS
Hi, how can I force TV-out on in KMS? As I understand >> Option "ForceTVOut" "true" makes no sense if KMS enabled. Both xrandr --output DIN --set 'load detection' 1 xrandr --output DIN --set 'load detection' 0 do not help as well as xrandr --output DIN --mode xrandr always prints DIN disconnected 1024x768+1280+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768_60.00 59.9*+ .. (I have Option "TVDACLoadDetect" "false" Option "TVStandard" "pal" Option "ATOMTvOut" "true" Option "ForceTVOut" "true" in xorg.conf and these options works fine in UMS) ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Monitor switches on/off infinitely after waking up from DPMS
At Thu, 2 Dec 2010 01:18:47 -0500, Alex Deucher wrote: > >> Btw, 2.3.36.1 shows temperature ~40C, 2.6.37-rc4 - ~80C. I hope this bug > >> is in sensors code and video card does not melt) > > > > The thermal sensor code was changed in this commit: > http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=b2298fd27127f872881048fd37cb9217a648ae06 Does it mean temperature really 80C, lm-sensors should be fixed or this is new kernel driver bug? ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Monitor switches on/off infinitely after waking up from DPMS
On 02.12.2010 02:16, Sergej Pupykin wrote: On 01.12.2010 23:03, Alex Deucher wrote: Does it work ok with older kernels? How about newer ones? kernel 2.6.37-rc4 installed. I am waiting 2-3 days for this problem. Reproduced on this kernel too. Trying 2.6.35.7 Btw, 2.3.36.1 shows temperature ~40C, 2.6.37-rc4 - ~80C. I hope this bug is in sensors code and video card does not melt) ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Monitor switches on/off infinitely after waking up from DPMS
On 01.12.2010 23:03, Alex Deucher wrote: Does it work ok with older kernels? How about newer ones? kernel 2.6.37-rc4 installed. I am waiting 2-3 days for this problem. Btw, 2.3.36.1 shows temperature ~40C, 2.6.37-rc4 - ~80C. I hope this bug is in sensors code and video card does not melt) ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Monitor switches on/off infinitely after waking up from DPMS
At Wed, 01 Dec 2010 20:30:23 +0300, Sergej Pupykin wrote: > > > Hi, > > I see following on my machine: > - DPMS swithes monitor off > - I touch keyboard to wake it up > - then it blinks switching on and off infinitely after reboot Sorry, until I reboot it with Ctrl+Alt+F1 and Ctrl+Alt+Delete then. But sometimes only SysRq+S, SysRq+B helps. > (it happens about 1 time per day, sometimes it wakes up successfully) > > Should I throw it out or it is software problem? It starts after > kernel 2.6.36.1 update. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Monitor switches on/off infinitely after waking up from DPMS
Hi, I see following on my machine: - DPMS swithes monitor off - I touch keyboard to wake it up - then it blinks switching on and off infinitely after reboot (it happens about 1 time per day, sometimes it wakes up successfully) Should I throw it out or it is software problem? It starts after kernel 2.6.36.1 update. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Hello, (Related to https://bugs.freedesktop.org/show_bug.cgi?id=25586) I still get subj error after switching to git. (As I understand it contains related fbLocation fixes) But it works much longer on my x86_64 than xf86-video-ati-6.13.2. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: RV620 TV-out
On 11.08.2010 02:06, Alex Deucher wrote: File a bug (https://bugs.freedesktop.org) and attach your xorg log and dmesg output. Done: https://bugs.freedesktop.org/show_bug.cgi?id=29494 ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: RV620 TV-out
On 10.08.2010 20:35, Sergej Pupykin wrote:
At Tue, 10 Aug 2010 12:26:41 -0400,
Alex Deucher wrote:
That scenario is not supported and only happens to work by luck with
ums. Since the encoder is shared between the DIN port and the analog
portion of the DVI port, you can't really use them both at the same
time. It should work with the DIN and the VGA port.
Thanks, I'll try to remove DVI2VGA connector and plug monitor into
VGA. But there is interesting thing: I bought DVI2VGA connector while
experimenting with CRTC settings. :) It solves TV-out problem in UMS
mode.
Strange things with CRTCs<->output assigning...
I checked VGA, but still have no success with TV. Moreover it seems VGA
has issues with getting available modes. If I do xinit with or without
xorg.conf it sets improper frequencies. Easiest way I found is 60Hz
limit ('VertRefresh 40.0 - 60.0') however monitor can 75Hz and console
works in this mode. Probably I can set proper modeline to get 75Hz but
driver can not detect it automatically.
Full story below (hope it help clarify what happens):
~2 year ago I bought ATI HD3450 and wasted quite much time before I
catch that VGA and DIN can not use different CRTCs. Then I bought
DVI2VGA connector and TV works fine on CRTC#0, DVI on CRTC#1. TV was
broken after I switch to KMS.
May be TV has the same issue as VGA and I should make proper raw mode
with --newmode?
$ xrandr --verbose
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
DIN disconnected (normal left inverted right x axis y axis)
Identifier: 0x51
Timestamp: 1418833
Subpixel: no subpixels
Clones:
CRTCs: 0 1
Transform: 1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
filter:
tv standard:pal
supported: ntsc pal pal-mpal-60
ntsc-j scart-palpal-cn secam
load detection: 1 (0x0001) range: (0,1)
VGA-0 connected 1280x1024+0+0 (0x54) normal (normal left inverted right
x axis y axis) 340mm x 270mm
Identifier: 0x52
Timestamp: 1418833
Subpixel: no subpixels
Clones:
CRTC: 0
CRTCs: 0 1
Transform: 1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
filter:
EDID:
000026cdd6461211
0b0f01030e221b782a5e50a6544c9926
145054bfef008180714f010101010101
010101010101bc34009851002a401090
1300540e111e00ff00303534
3932533533303433373000fd0037
4b18530e000a20202020202000fc
00504c453433302f3433310a20200059
load detection: 1 (0x0001) range: (0,1)
1280x1024 (0x54) 108.0MHz +HSync +VSync *current +preferred
h: width 1280 start 1328 end 1440 total 1688 skew0 clock
64.0KHz
v: height 1024 start 1025 end 1028 total 1066 clock
60.0Hz
1024x768 (0x55) 65.0MHz -HSync -VSync
h: width 1024 start 1048 end 1184 total 1344 skew0 clock
48.4KHz
v: height 768 start 771 end 777 total 806 clock
60.0Hz
800x600 (0x56) 40.0MHz +HSync +VSync
h: width 800 start 840 end 968 total 1056 skew0 clock
37.9KHz
v: height 600 start 601 end 605 total 628 clock
60.3Hz
800x600 (0x57) 36.0MHz +HSync +VSync
h: width 800 start 824 end 896 total 1024 skew0 clock
35.2KHz
v: height 600 start 601 end 603 total 625 clock
56.2Hz
640x480 (0x58) 25.2MHz -HSync -VSync
h: width 640 start 656 end 752 total 800 skew0 clock
31.5KHz
v: height 480 start 490 end 492 total 525 clock
60.0Hz
DVI-0 disconnected (normal left inverted right x axis y axis)
Identifier: 0x53
Timestamp: 1418833
Subpixel: horizontal rgb
Clones:
CRTCs: 0 1
Transform: 1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
filter:
load detection: 1 (0x0001) range: (0,1)
coherent: 1 (0x0001)range: (0,1)
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: RV620 TV-out
At Tue, 10 Aug 2010 12:26:41 -0400, Alex Deucher wrote: > That scenario is not supported and only happens to work by luck with > ums. Since the encoder is shared between the DIN port and the analog > portion of the DVI port, you can't really use them both at the same > time. It should work with the DIN and the VGA port. Thanks, I'll try to remove DVI2VGA connector and plug monitor into VGA. But there is interesting thing: I bought DVI2VGA connector while experimenting with CRTC settings. :) It solves TV-out problem in UMS mode. Strange things with CRTCs<->output assigning... ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: RV620 TV-out
On 10.08.2010 02:05, Alex Deucher wrote: How about 800x600 or 1024x768? Also, are you using the analog or digitial part of the DVI connector? If you are using the analog part, it uses the same encoder as the DIN connector so you can only use one or the other. I'll check other modes today. Yes, I use DVI2VGA connector, so it is analog. But without KMS both TV and monitor work fine. I need just reboot with nomodeset parameters to get it. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: RV620 TV-out
On 09.08.2010 11:10, Alex Deucher wrote: Does tv-out work with kms if you force it on with xrandr? load detection, which is used for detection on tv-out, is not always reliable. Hello, Alex, I try $ xrandr --addmode DIN 640x480 $ xrandr --output DIN --crtc 0 --mode 640x480 --right-of DVI-0 $ xrandr Screen 0: minimum 320 x 200, current 1920 x 1024, maximum 8192 x 8192 DIN disconnected 640x480+1280+0 (normal left inverted right x axis y axis) 0mm x 0mm 640x48072.8* VGA-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 340mm x 270mm 1280x1024 75.0*+ 60.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48072.8 75.0 66.7 60.0 720x40070.1 But there is no picture on TV. Also I try $ xrandr --newmode tv 25.2 640 656 752 800 480 490 492 525 -HSync -VSync $ xrandr --addmode DIN tv $ xrandr --output DIN --mode tv $ xrandr Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192 DIN disconnected 640x480+0+0 (normal left inverted right x axis y axis) 0mm x 0mm tv 59.5* VGA-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 340mm x 270mm 1280x1024 75.0*+ 60.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48072.8 75.0 66.7 60.0 720x40070.1 with the same result. $ xrandr --output DIN --set "load detection" 0 has no effect too. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: RV620 TV-out
On 07.08.2010 05:23, Alex Deucher wrote: On Fri, Aug 6, 2010 at 5:41 PM, Sergej Pupykin wrote: Should I report bug, or it is known issue and it is needed to change status on wiki? It should work in KMS as well. What kernel are you using? There were some issues fixed in 2.6.35. I use 2.6.35 (http://repos.archlinux.org/wsvn/packages/kernel26/repos/testing-x86_64/) ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
RV620 TV-out
Hello, All, I checked http://www.x.org/wiki/RadeonFeature and http://www.x.org/wiki/RadeonFeatureUMS On both pages TV-out marked as done. But on my card it works only in UMS mode. In KMS xrandr always reports DIN disconnected (normal left inverted right x axis y axis) tv standard:pal supported: ntsc pal pal-mpal-60 ntsc-j scart-palpal-cn secam load detection: 1 (0x0001) range: (0,1) Single difference is in kernel parameters: (/boot/grub/menu.lst) title Arch Linux [/boot/vmlinuz26] root (hd0,0) kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/d950a14f-fc0c-451d-b0d4-f95c2adefee3 ro quiet radeon.modeset=1 initrd /boot/kernel26.img title Arch Linux no modeset [/boot/vmlinuz26] root (hd0,0) kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/d950a14f-fc0c-451d-b0d4-f95c2adefee3 ro quiet radeon.modeset=0 nomodeset initrd /boot/kernel26.img Should I report bug, or it is known issue and it is needed to change status on wiki? ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
