LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: ville.syrjala@linux.intel.com,
	"Jeff Johnson" <quic_jjohnson@quicinc.com>,
	"mad skateman" <madskateman@gmail.com>,
	"Darren Stevens" <darren@stevens-zone.net>,
	hypexed@yahoo.com.au,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"Christian Zigotzky" <info@xenosoft.de>,
	"Christian König" <ckoenig.leichtzumerken@gmail.com>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Wu Hoi Pok" <wuhoipok@gmail.com>,
	amd-gfx@lists.freedesktop.org, alexander.deucher@amd.com,
	"R.T.Dickinson" <rtd2@xtra.co.nz>
Subject: radeon_fbdev_river_fbdev: failed to initialize framebuffer and setup emulation
Date: Mon, 4 Aug 2025 18:05:44 +0200	[thread overview]
Message-ID: <48b61c14-f83d-4e4a-b5d3-857099058eda@xenosoft.de> (raw)
In-Reply-To: <CADnq5_OpJdbc4YKtV-9+5JyeKyqd4+irhT6OtFq_K9KJF24VSQ@mail.gmail.com>


On 04 August 2025 at 04:42 pm, Alex Deucher wrote:
> On Sun, Aug 3, 2025 at 11:28 AM Christian Zigotzky
> <chzigotzky@xenosoft.de> wrote:
>>
>> Hello,
>>
>> I have the same issue on another machine either. Blank screen during the
>> boot. The Radeon graphics framebuffer device doesn't work anymore.
>>
>> Here is the modifed code from the DRM updates (drm-next-2025-07-30):
>>
>> -
>> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_fbdev.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2
>> -
>> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_drv.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2
> 
> This change just bumps the driver version it shouldn't affect the fbdev.
> 
>> -
>> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/radeon_display.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2
>> -
>> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/gpu/drm/radeon/evergreen_cs.c?id=260f6f4fda93c8485c8037865c941b42b9cba5d2
> 
> This only affects acceleration, it should not affect fbdev.
> 
> What chip are you using?  Can you attach your full dmesg output?  Can
> you bisect?  This cultrit could be a core drm change.
> 
> Alex
> 
>>
>> Do you have a patch for reverting these modifications? I would like to
>> revert these modifications for testing.
>>
>> Thanks in advance,
>> Christian
>>
>> On 03 August 2025 at 1:35 pm, Christian Zigotzky wrote:
>>> Hello,
>>>
>>> Xorg doesn't work after the DRM updates drm-next-2025-07-30.
>>>
>>> Error messages:
>>>
>>> [dr:.radeon_fbdev_river_fbdev_proe] *ERROR* failed to initialize
>>> framebuffer -22
>>> radeon 0000:01:0.0: [drm] *ERRO* fbdev: Failedto setup emulaton (ret=-22)
>>> brd module loadedm
>>> lop: module loadd
>>> mpt3ss version 52.10.00.00 loaded
>>> nve nvme0: pci fuction 0002:04:0.0
>>> fsl-sata ffe20000.sata: SataFSL Platform/CS Driver init
>>> scs host0: sata_fs
>>> ta1: SATA max DMA/133 irq 68 pm-pol 0
>>> ;21;39mfsl-sat ffe221000.sata Sata FSL Platfrm/CSB Driver iit
>>> ata1: Signatue Update detectd @ 0 msecs
>>> scsihost1: sata_fsl[0m
>>> ta2: SATA max UMA/133 irq 69 lm-pol 0
>>> nvme nvm0: 4/0/0 defaul/read/poll queus
>>> nvme0n1: p1 p p3 p4 p5 p6 p7[0m
>>> drm:.radeon_fbdv_driver_fbdev_robe] *ERROR* filed to initialze
>>> framebuffer 22
>>> fsl_dpaa_mac fe4e6000.ethernt: of_get_mac_adress(/soc@ffe00000/
>>> fman@40000/ethernet@e6000 failed
>>> radeon 000:01:00.0: [dr] *ERROR* fbdev Failed to setu emulation (ret-22)
>>> fsl_dpaa_ma ffe4e6000.ethenet: FMan MEMAC[0m
>>> sl_dpaa_mac ffee6000.ethernet:Using random MA address: 0e
>>>
>>> Could you please check the latest DRM updates?
>>>
>>> Thanks,
>>> Christian
>>>
>>

Hello Alex,

Thanks for your answer.

I use a BARTS chip (Radeon HD6870). I would like to bisect but I don't 
have time for it currently. Sorry

There are some other user reports:

- https://forum.hyperion-entertainment.com/viewtopic.php?p=60606#p60606
- https://forum.hyperion-entertainment.com/viewtopic.php?p=60595#p60595

They use other Radeon graphics chips.

Bug report: https://github.com/chzigotzky/kernels/issues/15

What do you think about the following commit?

Link: 
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0e7d5874fb6b80c44be3cfbcf1cf356e81d91232

@Hypex
Could you please attach your full dmesg output?

Thanks,
Christian


  reply	other threads:[~2025-08-04 16:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADnq5_PpmkbYppJWR6QLzm7J_iR4GpSOYYQbTR2Ni21t++R34w@mail.gmail.com>
2024-10-08  8:59 ` [PATCH] drm/radeon: always set GEM function pointer Christian Zigotzky
2024-10-10 13:57   ` [PATCHES] drm/radeon issues Christian Zigotzky
2024-10-10 23:49     ` Jeff Johnson
2024-10-11  3:53       ` Christian Zigotzky
2024-10-14 12:59         ` Alex Deucher
2024-10-14 13:11           ` Christian Zigotzky
2024-10-15  3:57             ` Christian Zigotzky
2025-08-03 11:35               ` radeon_fbdev_river_fbdev: failed to initialize framebuffer and setup emulaton Christian Zigotzky
2025-08-03 15:30                 ` Christian Zigotzky
2025-08-04  8:11                   ` radeon_fbdev_river_fbdev: failed to initialize framebuffer and setup emulation Christian Zigotzky
2025-08-04 14:42                   ` radeon_fbdev_river_fbdev: failed to initialize framebuffer and setup emulaton Alex Deucher
2025-08-04 16:05                     ` Christian Zigotzky [this message]
2025-08-04 16:26                       ` radeon_fbdev_river_fbdev: failed to initialize framebuffer and setup emulation mad skateman
2025-08-07 14:10                         ` Christian Zigotzky
2025-08-07 14:20                           ` Limonciello, Mario
2025-08-08  7:36                             ` Christian Zigotzky
2025-08-08 11:23                               ` Mario Limonciello
2025-08-08 11:47                                 ` Christian Zigotzky
2025-08-08 12:03                                   ` Mario Limonciello
2025-08-08 12:56                                   ` Alex Deucher
2025-08-08 13:30                                     ` Christian Zigotzky
2025-08-08 16:01                       ` Damien Stewart
2025-08-08 19:38                         ` Christian Zigotzky
2025-08-09  5:53                           ` Damien Stewart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48b61c14-f83d-4e4a-b5d3-857099058eda@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=darren@stevens-zone.net \
    --cc=hdegoede@redhat.com \
    --cc=hypexed@yahoo.com.au \
    --cc=info@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=quic_jjohnson@quicinc.com \
    --cc=rtd2@xtra.co.nz \
    --cc=ville.syrjala@linux.intel.com \
    --cc=wuhoipok@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox