Here are the results of the 2 commands for kernel 2.6.32-5: *dmesg | grep modeset [ 7.265735] [drm] radeon kernel modesetting enabled. [ 7.267335] [drm] radeon: Initializing kernel modesetting.
*dmesg | grep radeon [ 7.265735] [drm] radeon kernel modesetting enabled. [ 7.265834] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 7.265881] radeon 0000:01:00.0: setting latency timer to 64 [ 7.267335] [drm] radeon: Initializing kernel modesetting. [ 7.269719] [drm] radeon: 256M of VRAM memory ready [ 7.269760] [drm] radeon: 512M of GTT memory ready. [ 7.269847] radeon 0000:01:00.0: irq 34 for MSI/MSI-X [ 7.269851] radeon 0000:01:00.0: radeon: using MSI. [ 7.269912] [drm] radeon: irq initialized. [ 7.270335] platform radeon_cp.0: firmware: requesting radeon/RV620_pfp.bin [ 7.537724] platform radeon_cp.0: firmware: requesting radeon/RV620_me.bin [ 7.713378] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 7.876660] [drm] radeon: ib pool ready. [ 8.127092] fb0: radeondrmfb frame buffer device [ 8.127127] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0 It seems fine. Regards and thanks for your time. Johan 2012/5/9 Arnt Karlsen <a...@c2i.net>: > On Wed, 9 May 2012 14:06:30 +0900, Johan wrote in message > <caks5mhqkqwbcmujdneckfyeyckaj-herk+xvcoewyqohzok...@mail.gmail.com>: > >> Under kernel 3.2.0-2, I have: >> *dmesg |grep modeset >> [ 7.111909] [drm] radeon kernel modesetting enabled. >> [ 7.112268] [drm] initializing kernel modesetting (RV620 >> 0x1002:0x95C5 0x1028:0x0342). >> >> *dmesg |grep radeon >> [ 7.111909] [drm] radeon kernel modesetting enabled. >> [ 7.111991] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) >> -> IRQ 16 [ 7.111997] radeon 0000:01:00.0: setting latency timer >> to 64 [ 7.112558] radeon 0000:01:00.0: VRAM: 256M >> 0x0000000000000000 - 0x000000000FFFFFFF (256M used) >> [ 7.112561] radeon 0000:01:00.0: GTT: 512M 0x0000000010000000 - >> 0x000000002FFFFFFF >> [ 7.115303] [drm] radeon: 256M of VRAM memory ready >> [ 7.115304] [drm] radeon: 512M of GTT memory ready. >> [ 7.115368] radeon 0000:01:00.0: irq 50 for MSI/MSI-X >> [ 7.115373] radeon 0000:01:00.0: radeon: using MSI. >> [ 7.115404] [drm] radeon: irq initialized. >> [ 7.581930] radeon 0000:01:00.0: WB enabled >> [ 7.613104] [drm] radeon: ib pool ready. >> [ 7.613633] [drm] radeon: power management initialized >> [ 7.752123] fbcon: radeondrmfb (fb0) is primary device >> [ 8.177088] fb0: radeondrmfb frame buffer device >> [ 8.177095] [drm] Initialized radeon 2.12.0 20080528 for >> 0000:01:00.0 on minor 0 >> >> This looks fine, does it ? > > ..yup, you have everything working allright now? > >> Do you want me to run the same commands on kernel 2.6.32-5 ? > > ..your problem, your thread, your decision. ;o) > >> Regards >> Johan >> >> 2012/5/8 Arnt Karlsen <a...@c2i.net>: >> > On Tue, 8 May 2012 13:23:29 +0900, Johan wrote in message >> > <caks5mhq_bp+f11zkdkehqrvdjez8joaunr51an2dybjqs8f...@mail.gmail.com>: >> > >> >> I installed firmware-linux, firmware-linus-non-free, libdrm2 and >> >> libdrm-radeon1. I think that radeon is starting with KMS because >> >> there is a file called radeon-kms.conf in /etc/modprobe.d/ that >> >> contains "options radeon modeset=1". >> > >> > ..verify that with e.g. 'dmesg |grep modeset' or 'dmesg |grep >> > radeon' or some such search. >> > >> >> This fixed the problem for kernels 3.2.0-1 and 3.2.0-2. >> >> There is however still a problem with kernel 2.6.32-5 : rectangle >> >> of random black and white pixels disappeared but gnome login screen >> >> doesn't work. I don't know if Debian want to fix this or not. If >> >> yes, I would be glad to help in terms of testing. >> >> >> >> Thanks a lot for your help. >> >> Regards. >> >> Johan > > -- > ..med vennlig hilsen = with Kind Regards from Arnt Karlsen > ...with a number of polar bear hunters in his ancestry... > Scenarios always come in sets of three: > best case, worst case, and just in case. > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20120509115240.20c2d...@celsius.lan > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caks5mhts4bbxs8b3rd_pd6n3own4fwibw+59kw-wbyow0x+...@mail.gmail.com