On 08/03/14(Sat) 14:26, Jan Stary wrote: > This is current/macppc on a Mac Mini, see full dmesg below. > It works fine, but the Radeon graphics, which is > radeondrm0 at pci0 dev 16 function 0 "ATI Radeon 9200" rev 0x01 > might have some problems. > > This is how the boot sequence ends: > > root on wd0a (d2e7005f40cdabc7.a) swap on wd0b dump on wd0b > drm: initializing kernel modesetting (RV280 0x1002:0x5962 0x1002:0x5962). > error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM > drm: Using generic clock info > radeondrm0: VRAM: 128M 0x0000000098000000 - 0x000000009FFFFFFF (64M used) > trying to bind memory to uninitialized GART ! > error: [drm:pid0:radeon_ttm_backend_bind] *ERROR* failed to bind 1 pages at > 0x00000000 > error: [drm:pid0:radeon_wb_init] *ERROR* (-22) create WB bo failed > error: [drm:pid0:r100_init] *ERROR* Disabling GPU acceleration > drm: radeon: cp finalized > drm: radeon: cp finalized > Finalizing pool allocator > ttm_pool_mm_shrink_fini stub > drm: Zone kernel: Used memory at exit: 0 kiB > drm: radeon: ttm finalized > drm: Forcing AGP to PCI mode > error: [drm:pid0:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM > drm: Using generic clock info > radeondrm0: VRAM: 128M 0x0000000098000000 - 0x000000009FFFFFFF (64M used) > radeondrm0: GTT: 512M 0x0000000078000000 - 0x0000000097FFFFFF > drm: PCI GART of 512M enabled (table at 0x000000000294A000). > drm: Connector Table: 6 (mini external tmds) > drm: No valid Ext TMDS info found in BIOS > drm: No TV DAC info found in BIOS > radeon_i2c_put_byte stub > radeon_i2c_put_byte stub > radeon_i2c_put_byte stub > radeon_i2c_put_byte stub > radeon_i2c_put_byte stub > radeondrm0: 1280x1024 > wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0 > wskbd1: connecting to wsdisplay0 > wsdisplay0: screen 1-5 added (std, vt100 emulation) > > Is this anything to worry about?
Not really. > What can I do to debug what radeon is complaining about? You can try to figure out why AGP is no longer working, you'll need to enable appleagp for that in your kernel, if you find why I'm interested :) > The graphics seems to work fine, > and I can run X with machdep.allowaperture=0 > (a good opportunity to thank all those > who have been working on KMS!). > > One silly problem I am having with the graphics > is that the textures of games/frozen-bubble are broken > http://stare.cz/~hans/.tmp/fb.jpg > For those of you deprived of the orgastic joys of frozen-bubble, > the ball to be shooted should be shooting from a canon, > and there is a penguin angling the canon to the left. > In the left part, the level is supposed to be written. > > I don't know if this is frozen-bubble's problem, > or a symptom of something wrong with my graphics. Or simply just a bug in the driver(s), was it working before? Coud you try with software rendering only, by setting LIBGL_ALWAYS_SOFTWARE before launching the application? See the Mesa page [0] for more informations. Martin [0] http://www.mesa3d.org/envvars.html
