SliTaz Forum

Problems with display

(7 posts) (3 voices)

• Started 4 years ago by guest_account
• Latest reply from guest_account
• This topic is not resolved

Tags:

No tags yet.

1. 

   guest_account
   

   offline

   Member

   I'm still using rev 2019-01 of Slitaz Core.

   I noticed regressions in it:

   --when the monitor suspends after the default 10 minutes, it seems to not enter the "suspension" state correctly; normally it should display the constant "no signal" message, but it intermittently switches between pitch black and the message.

   --I noticed this build is no longer able to boot in desktops/laptops with ATI gpus. Always fails loading a driver and thus never can start X session.

   Has all this been fixed in current weekly?

   Posted 4 years ago #
2. 

   mojo
   

   offline

   Key Master

   On my computers with ATI radeon graphics the radeon kernel module loads and prevents the vesa driver from working.
   Due to a change in the depends of some package linux-drm that owns radeon.ko.xz is now included on any flavor with xorg-server. It's not specified on the package.list of core.
   The error message:
   vesa: Ignoring device with a bound kernel driver
   The workaround I use is to tab the boot menu and add modprobe.blacklist=radeon to the kernel commandline. Radeon isn't loaded,vesa works,Xsession starts.

   Posted 4 years ago #
3. 

   guest_account
   

   offline

   Member

   So just downloaded latest weekly ISO.

   First tried to boot directly with no tweakings (except the language preferences). In the boot process, logs all go correctly until the part "Loading console keymap: es [HECHO]".
   After this it gets freezed there with nothing more and CD drive even stops working.

   Exact same result when appending your modprobe line in kernel options (done by hitting Tab key when selecting language; aside tweaking language preferences I add the modprobe line afterwards. Dunno if its the correct way).

   Posted 4 years ago #
4. 

   Ceel
   

   offline

   Administrator

   @guest_account,

   Not sure you entered the command at the right place.
   Change the language and press [Enter].
   Then you have a second menu select Core and hit [Tab].
   Add modprobe.blacklist=radeon here and press [Enter].

   Posted 4 years ago #
5. 

   guest_account
   

   offline

   Member

   Did just like you said.

   Duting boot process, several seconds after the
   [CODE]Starting inetd daemon: inetd... [ DONE ]
   Starting ntpd daemon: ntpd... [ DONE ][CODE]

   I get
   [CODE]slitaz login: cik_cp: Failed to load firmware "radeon/KABINI_pfp.bin"
   [drm:cik_init] *ERROR* Failed to load firmware!
   radeon 0000:00:01.0: Fatal error during CPU init
   [drm] radeon: finishing device
   [TTM] Finalizing pool allocator
   [TTM] Finalizing DMA pool allocator
   [TTM] Zone kernel: Used memory at exit: 0 kiB
   [TTM] Zone highmem: Used memory at exit: 0 kiB
   [drm] radeon: ttm finalized
   radeon: probe of 0000:00:01.0 failed with error -12[/CODE]

   Posted 4 years ago #
6. 

   guest_account
   

   offline

   Member

   Something?

   Still not fixed in weekly...

   Posted 4 years ago #
7. 

   guest_account
   

   offline

   Member

   Aren't we being racists?

   Posted 4 years ago #

RSS feed for this topic

Reply

You must log in to post.