ATI Drivers Slackware

Download drv from ATI AMD page

untar
NAME --extract NewDirectory

get Patch:
ati_to_gpl.patch
from: ???
" Source of patch
#!/bin/sh
sed -i /MODULE_LICENSE\(/'s/".*"/"GPL"/' firegl_public.c
"
go to :
./NewDirectory/common/lib/modules/fglrx/build_mod/
!apply patch here!

Go to New Directory
ati-installer.sh 8.11 Slackware/All
! 8.11 - is driver version
in parent directory will be created two packages:
fglrx-module-8.552-x86-1_kernel_2.6.28.tgz
fglrx-x710-8.552-x86-1.tgz

upgradepkg --install-new ... # for them

!!! IF use once driver and change kernel Version DELETE this directory and extract again, because of internal links that is created to old kernel!!!

If fglrx apps crash with drivers 9.2 version need to check old files position and delete by hand old ati libs. Usually in /usr/lib/xorg/*/* and links too. /usr/lib/.

simple rsync with ssh rsyncd.conf

Right synt is:

rsync -av --rsh="ssh" *.* sshuser at host.com:/full_path

--safe-links - do not follow links otside copied tree


/etc/rsyncd.conf:
motd file = /etc/motd
max connections = 25
syslog facility = local3

# rsync -a rbm.myftp.org::backup /root/routers/backups/rbm/ >/dev/null 2>&1
# RSYNC_PASSWORD=userpass rsync -a user@host.mine.com::backup /local dir/

[backup]
     comment = Backup area
     path = /backup
     read only = yes
     list = yes
     uid = nobody
     gid = nobody
     auth users = user
     secrets file = /etc/rsyncd.secrets

/etc/rsyncd.secret
user:userpass

It's important:
chmod 600 /etc/rsyncd.secrets

KDE4 some short notes

1. When start new X App:

"Maximum number of clients reached"

Read by my lips carefully:
/etc/rc.d/rc.messagebus stop - for slack rc.dbus
/etc/rc.d/rc.hald stop
rm /var/run/dbus/system_bus_socket
/etc/rc.d/rc.messagebus start
/etc/rc.d/rc.hald start

If under KDE or X env must restart them some future is broken because dbus-daemon socket change ???
try:
lshal
dbus-monitor


skype - Stupid Pyhon
ps ax | grep python
No need to kill will end alone when see that is not an loptop if it is not:
4177 ? S 0:00 /usr/bin/python /usr/bin/guidance-power-manager
kill 4177 - change PID

And all will be ok

2. Your USB keyboard is repeat pressed key very often and unnecessarily - my Logitech mx5000 have this problem and many other...

Go in System Settings - Keyboard - Enable Keyboard repeat - Disable or change Delay to Higher Value.

3. For GTK app use: lxappearance - to change Theme, Icons, fonts.

slackware mkinitrd

mkinitrd - no big deal

!!! All options must be supplied, because mkinitrd change on the fly when create initrd image !!!

mkinitrd - first time to create tree

mkinitrd -c -L -f ext3 -r /dev/mapper/Sea1t-root -k 2.6.27 -k 2.6.27 -m ext3 - for My with LVM2

-c - remove old initrd
-L - LVM support - copy some LVM commands
-f - type of Root FS - look carefully for EXT3 some times mkfs do not create journal must be made on hand tune2fs -j /dev/... . This will brooke initrd if it's for root or other auto mount part.
-r - which part to use for rootfs only /dev/mapper/... is right
-k - load modules from /lib/modules/supplied by You argument - VERSION HERE/... !!! - if not supplied
-m - initrd try to load modules

mkinitrd get 'uname -r' which is wrong in most cases !!!

OPTIOPNS:
1. cat initrd /init to see for changes:
mount -o ro /dev/' Your root' /mnt
exit

This will boot Your System in not very proper way if something is wrong with initrd, and you stuck in prompt inside initrd.

2. initrd - can be chaged ot Fly with boot Live CD.

-See Blog for - Grub install and

- use:
mkdir 'some dir'
cd 'some dir'
gzip 'initrd image.gz'
cpio -id < 'initrd image'

This will unshrink image, edit
!!! mkinitrd ... with all options


!!! After many try i figured out that SELinux troubling boot with:
these Errors :

"Can't execute /bin/init"

"linux failed to execute /init"

"No init found"

and some strange errors like module for fs of main partitition isn't compiled in kernel.
!!!
DISABLE : Security options -> Enable different security models - or try SELinux :)

grub install

Инсталиране на груб - проблемни ситуации

If get "Grub Hard Disk Error" most times problem is

From - info grub - Native install

in command prompt start: Personaly i use SLAX Live CD
- boot
- mount root part somewhere
- "chroot"
- mount all include boot if use separated part.
after that install grub:

grub

root (hd0,0) - for disk 0, part 1
find /boot/grub/stage1 - this not only show part with grub but get new PATH for GRUB ROOT with menu stages and etc...
setup (hd0) - This command will install the GRUB boot loader on the Master Boot
or
setup (hd0,0) - If you install GRUB into a partition or a drive other than the first one, you must chain-load GRUB from another boot loader. Refer to the manual for the boot loader to know how to chain-load GRUB.

P.S.
http://grub.enbug.org/LVMandRAID
GRUB has support for LVM and RAID since version 1.95

insmod lvm
insmod raid
grub-mkimage --output=/boot/grub/core.img ext2 pc gpt biosdisk lvm

LILO support boot from LVM

Test HTTPS https

Test HTTPS
openssl s_client -no_tls1 -no_ssl3 -connect www.google.com:443



http://www.owasp.org/index.php/Testing_for_SSL-TLS

mplayer HD video on smaller screen no lag play without problems

- get latest svn
- recompile
This is close to 20G HD Movie

mplayer /mnt/hd/1/Troy.DC.2004.HDDVD.1080p.DTS.x264.dxva-EuReKa/3.\ Movie/Troy.DC.2004.HDDVD.1080p.DTS.x264.dxva-EuReKa.mkv -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all

-vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all

- some body of MPLayer TEAM made it show.