WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: firmware-radeon small bug  (Read 3677 times)

Offline nick65go

  • Hero Member
  • *****
  • Posts: 635
firmware-radeon small bug
« on: August 19, 2014, 03:38:20 PM »
in my fresh loaded /tmp/tcloop/firmware-radeon/usr/local/tce.installed the file firmware-radeon is like:
#!/bin/sh\nudevadm trigger

I think it should be like:
#!/bin/sh
udevadm trigger


Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: firmware-radeon small bug
« Reply #1 on: August 19, 2014, 03:55:09 PM »
Interesting, ok thanks will check and fix

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: firmware-radeon small bug
« Reply #2 on: August 19, 2014, 04:19:14 PM »
Interesting indeed..   this was not one I'd updated previously but have fixed it and notified the creator/maintainer

have you fixed your copy?

Offline nick65go

  • Hero Member
  • *****
  • Posts: 635
Re: firmware-radeon small bug
« Reply #3 on: August 19, 2014, 04:42:44 PM »
Hi core64 team, thanks again for your hard work!
I am back to core/core64 because my archlinux64 has crashed, by my forced updated :-\ . Anyway, I started to hate the intrusive allover systemd dependency. I could easy fix most things in core as I have been useing it for 3 years. My Dell9400 BIOS bug is that X1400 GPU fan starts and never stop on core, so I try core64. And here I had succes with:
echo low > /sys/class/drm/card0/device/power_profile &

I am also "remastering" core64 to do not have need for bootlocal.sh backup:
modprobe -r pcspkr && echo blacklist pcspkr >> /etc/modprobe.d/blacklist.conf
loadkmap < /usr/share/kmap/azerty/fr-pc.kmap &

I still pay with aboriginal toybox to replace busybox (or at least to be static linked against uclib or musl), and copy files in /lib/firmware.. so not yet helpfully for the community.
« Last Edit: August 19, 2014, 05:01:22 PM by nick65go »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10741
Re: firmware-radeon small bug
« Reply #4 on: August 20, 2014, 12:10:54 AM »
Both of those can be done with bootcodes?

blacklist=pcspkr kmap=azerty/fr-pc
The only barriers that can stop you are the ones you create yourself.

Offline nick65go

  • Hero Member
  • *****
  • Posts: 635
Re: firmware-radeon small bug
« Reply #5 on: August 20, 2014, 11:28:15 AM »
Both of those can be done with bootcodes?

blacklist=pcspkr kmap=azerty/fr-pc

Thanks curaga, this I did from the beginning. And I read the wiki too.

- still there is some old info in wiki about Xorg input classes (Section "InputDevice" is ignored, now is "InputClass" for synaptics and keyboards wthen edev is used by default).
- I am dissecting core in bits, to remember how a great suite of programs could fit in so small size. So I wonder why we have now a link in the root (/linuxrc, we were good even without it) and a lot of extra links in /lib (like libc.so.6 -> lib-2.17.so,  instead of simple one renamed as libc.so.6 which ldd shows as needed).

It will not make a huge difference in size or speed, I know. But the spirit of the core is to be the smallest and easy to understand (pedantic, didactic). Not any extra fat if not used, or use better alternative replacement.

The easy acceptance of bloat like pulseaudio, or systemd, are examples of cancer spread to linux.
Do we need a monolitic aor modular kernel? I prefer modular up to the bones, for learning.

This is not criticism, just my rant over.
« Last Edit: August 20, 2014, 01:12:04 PM by nick65go »