Page 1 of 1

graphical boot & radeon

PostPosted: Jun 2nd, '11, 02:00
by celt
When trying livecd everything was OK, but after installation on boot i get scrolling error message.
In dmesg after successful loading i was found:

[drm:radeon_ttm_backend_bind] *ERROR* failed to bind 1294 pages at 0x00000000
radeon 0000:01:00.0: object_init failed for (5300224, 0x00000002)
[drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (5300224, 2, 4096, -22)

WARNING: at drivers/gpu/drm/radeon/radeon_gart.c:176 radeon_gart_bind+0x196/0x1a0 [radeon]()
Hardware name: GA-MA78LM-S2
trying to bind memory to unitialized GART !
Modules linked in: fuse dm_mod cpufreq_ondemand cpufreq_conservative cpufreq_powersave powernow_k8 freq_table
mperf snd_hda_codec_hdmi snd_hda_intel snd_emu10k1 snd_hda_codec snd_usbmidi_lib snd_ac97_codec snd_rawmidi ac
97_bus snd_util_mem snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss
snd_pcm snd_timer snd_mixer_oss snd floppy uvcvideo joydev videodev snd_page_alloc soundcore i2c_piix4 evdev u
as button processor k10temp sp5100_tco serio_raw wmi sg sr_mod r8169 usb_storage mii pata_atiixp ata_piix ahci
libahci libata sd_mod scsi_mod crc_t10dif ext4 jbd2 crc16 uhci_hcd ohci_hcd ehci_hcd usbhid hid usbcore radeo
n ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Pid: 39, comm: plymouthd Tainted: G W 2.6.38.7-server-1.mga #1
Call Trace:
[<c0153cb2>] ? warn_slowpath_common+0x72/0xa0
[<f3dcd616>] ? radeon_gart_bind+0x196/0x1a0 [radeon]
[<f3dcd616>] ? radeon_gart_bind+0x196/0x1a0 [radeon]
[<c0153d83>] ? warn_slowpath_fmt+0x33/0x40
[<f3dcd616>] ? radeon_gart_bind+0x196/0x1a0 [radeon]
[<f3c7bf66>] ? __ttm_tt_get_page+0x76/0x110 [ttm]
[<f3dcb151>] ? radeon_ttm_backend_bind+0x31/0xa0 [radeon]
[<f3c7c61f>] ? ttm_tt_populate+0x6f/0x90 [ttm]
[<f3c7c68c>] ? ttm_tt_bind+0x4c/0x70 [ttm]
[<f3c7df7e>] ? ttm_bo_handle_move_mem+0x17e/0x380 [ttm]
[<f3c7eebf>] ? ttm_bo_move_buffer+0x12f/0x150 [ttm]
[<f3c7ef88>] ? ttm_bo_validate+0xa8/0x120 [ttm]
[<f3c7f259>] ? ttm_bo_init+0x259/0x310 [ttm]
[<f3dcc2e0>] ? radeon_bo_create+0xb0/0x290 [radeon]
[<f3dcc35f>] ? radeon_bo_create+0x12f/0x290 [radeon]
[<f3dcc100>] ? radeon_ttm_bo_destroy+0x0/0xa0 [radeon]
[<f3de2ea9>] ? radeon_gem_object_create+0x79/0x100 [radeon]
[<f3de32e7>] ? radeon_gem_create_ioctl+0x67/0xe0 [radeon]
[<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
[<f3a54d31>] ? drm_ioctl+0x1e1/0x450 [drm]
[<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
[<f3de3280>] ? radeon_gem_create_ioctl+0x0/0xe0 [radeon]
[<c0485468>] ? schedule_hrtimeout_range_clock+0x108/0x1a0
[<c0174f50>] ? hrtimer_wakeup+0x0/0x30
[<c0175a66>] ? hrtimer_start_range_ns+0x26/0x30
[<f3a54b50>] ? drm_ioctl+0x0/0x450 [drm]
[<c02301dd>] ? do_vfs_ioctl+0x7d/0x590
[<c02a72d6>] ? tomoyo_init_request_info+0x46/0x50
[<c02a3c5e>] ? tomoyo_path_number_perm+0x2e/0xf0
[<c0257105>] ? sys_epoll_wait+0x75/0x350
[<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
[<c017b768>] ? ktime_get_ts+0xf8/0x120
[<c02a6027>] ? tomoyo_file_ioctl+0x17/0x20
[<c0230777>] ? sys_ioctl+0x87/0x90
[<c01709b1>] ? sys_clock_gettime+0x71/0xb0
[<c0486734>] ? syscall_call+0x7/0xb
[<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
[<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 02:09
by isadora
Sorry celt, can't help you on this one.
You'll have to wait for the more experienced graphical colleagues. ;-)

But anyway, very welcome to the Mageia-forum!!!
Hope you'll find here, what you are hoping for.
And honestly........................i give it a very good chance.

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 02:22
by ahmad
This looks similar to: https://bugs.mageia.org/show_bug.cgi?id=1471

Try booting with radeon.modeset=0 ; when booting, at the GRUB screen press F3 select "default" then press Enter, in the command line that appears type:
Code: Select all
radeon.modeset=0

then press Enter.

When the system boots, post the output of:
rpm -q radeon-firmware

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 02:44
by celt
yep, setting radeon.modeset=0 has helped
radeon-firmware does not installed

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 02:58
by isadora
celt wrote:yep, setting radeon.modeset=0 has helped
radeon-firmware does not installed

Marking this topic as [SOLVED]? ;-)

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 03:18
by celt
isadora wrote:
celt wrote:yep, setting radeon.modeset=0 has helped
radeon-firmware does not installed

Marking this topic as [SOLVED]? ;-)


yes, and thank you all :)

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 04:09
by ahmad
celt wrote:yep, setting radeon.modeset=0 has helped
radeon-firmware does not installed

But that's not the fix, just a workaround. What's the output of:
Code: Select all
su
dmesg | grep firmware

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 14:42
by celt
r8169 0000:02:00.0: eth0: unable to apply firmware patch rtl_nic/rtl8168d-2.fw

well, that's all and it's not interesting )

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 18:02
by ahmad
OK, probably the kernel only tries to load the firmware for the graphics card when KMS is enabled.

Install the radeon-firmware package (and remove radeon.modeset=0 from /boot/grub/menu.lst if you added it manually), then recreate the kernel(s) initrd:
Code: Select all
su
bootloader-config --action rebuild-initrds

then try booting without radeon.modeset=0, see if it works.

As for:
r8169 0000:02:00.0: eth0: unable to apply firmware patch rtl_nic/rtl8168d-2.fw

I suggest you install kernel-firmware-extra .

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 19:02
by celt
Well, after rebuilding initrds error messages disappear.
Thank you.

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 19:21
by ahmad
So, indeed it was a duplicate of https://bugs.mageia.org/show_bug.cgi?id=1471 , thanks to tmb's comment in the bug report for the solution.

Re: graphical boot & radeon

PostPosted: Jun 2nd, '11, 22:43
by revjack
It doesn't seem to like my radeon 3200 either.