Page 175 of 212

Posted: Thu 04 Sep 2014, 05:39
by saintless
Hi, Dan.
dancytron wrote:Am I correct in concluding that the mplayer is set up (compiled??) to not to work in the console framebuffer?
I'm not sure what are the compiling options. This is how mplayer was compiled on my old PIII machine following Fred's instruction:
http://ip-208-109-22-214.ip.secureserve ... 920#778356
After that "strip -s mplayer" was executed.
Compiling on my hardware was needed to make it work on very old hardware. Fred uploaded few testing mplayer2 files first and any of them wasn't working for me till mplayer2 was compiled on my machine.

Toni

Kernel Headers

Posted: Thu 04 Sep 2014, 08:29
by Meshworks

Code: Select all

root@wheezy:~# uname -a
Linux wheezy 3.13.6-porteus #1 SMP PREEMPT Fri Mar 7 07:25:21 Local time zone must be set--s i686 GNU/Linux
root@wheezy:~# 
Hi ... how can i find & install the headers required to compile the Proprietory ATI graphics driver?

ty in advance!

Posted: Thu 04 Sep 2014, 08:59
by saintless
Hi, Meshworks.

I'm sure Fred will answer proper to your question.
My guess is Porteus is Slackware based and it should be compatible with Slackware headers. Till you get better answer here some ready for use modules from porteus for kernel 3.13.6:
http://dl3.porteus.org/i486/archive/Por ... 0/drivers/
Maybe the amd driver will work for you.

Toni

Posted: Thu 04 Sep 2014, 09:27
by Meshworks
hehehehe ty Saintless - love ur avatar!

I chose this distro because I thought it was debian based ... that's right yes?!?!
ED: ooh.. just checked the porteus.org site ... ur right its slackware!

ty for the link ... ill try that driver over the next hour (sloooow wifi here) and come back with result,

Would still like the correct kernel header files so i can compile other drivers.

ED: OMG now I'm properly confused again ... I have setup the compiler out of the debian repo (all seems well) and im about to set up a driver from a slackware source. So ... Can we rename this distro 'bastard-dog' due to the multiple parentage?! (joke)

Posted: Thu 04 Sep 2014, 10:55
by saintless
Meshworks wrote:ED: OMG now I'm properly confused again ... I have setup the compiler out of the debian repo (all seems well) and im about to set up a driver from a slackware source. So ... Can we rename this distro 'bastard-dog' due to the multiple parentage?! (joke)
Don't be confused :)
It is still Debian but if I'm correct you are using Fred's Porteus-Wheezy - it is Debian with kernel from Porteus and using systemd boot. Since the kernel is from Porteus (or Slackware based) you can't use Debian headers here. Otherwise the system is debian and all packages are downloaded and installed from debian repository. Excluding the kernel related stuff Porteus-Wheezy is Debian Wheezy.
For 100% Debian Wheezy with Debian kernel, headers, etc use DebianDog - OpenBox or Jwm version.
We have also Puppy kernel available if you like to experiment.

Toni

Posted: Thu 04 Sep 2014, 11:11
by Meshworks
Thanks Saintless ... The driver seems to load (change of res in the bootup text) but leads to a black screen which will not CTRL-ALT-BKSPACE.

Conflict with the builtin driver?!

As you (correctly) guessed I'm currently on porteus wheezy..

GTG for an hour or two ... Should I try DebianDog when I get back? or is there a way to resolve this black screen?

TY again.

Posted: Thu 04 Sep 2014, 12:48
by saintless
Hi, Meshworks.

Unfortunately I use very old hardware and I can't test personally the problem you have. I suggest wait for a day or two till Fred reads your posts before changing to DebianDog. Maybe he will have some solution for the black screen issue or give some advice to test something more.

We had one similar problem with amd driver with DebianDog and all I can do for the moment is to point the related posts:
http://murga-linux.com/puppy/viewtopic. ... 519#791519
The answer to this method:
http://www.murga-linux.com/puppy/viewto ... 886#791886
And more information links and suggestion for testing:
http://www.murga-linux.com/puppy/viewto ... 228#793228

If you decide to test DebianDog googling for amd/ati driver compiling problem for Debian is what you need. All solutions for Debian are fully compatible the same way for DebianDog.

Toni

Posted: Thu 04 Sep 2014, 16:21
by fredx181
Hi Meshworks,
I don't really know much about installing drivers so can't help you with that.
Anyway here's a .deb for installing the kernel headers version 3.13.6
linux-headers-3.13.6-porteus_i386.deb is here:

https://googledrive.com/host/0ByBgCDlZZ ... /Packages/
Install by opening a terminal in the folder you downloaded the deb and do:

Code: Select all

dpkg -i linux-headers-3.13.6-porteus_i386.deb
It works well for me installing the virtualbox kernel modules, didn't test more.
Good luck!

Edit: As Toni suggested maybe it's better to install DebianDog for 100% debian compatibility.
In fact the only difference is the kernel version, for the rest it's the same (and you have choice for different boot-methods including porteus-boot and choice of two desktop environments, Jwm or openbox_xfce)

Fred

Posted: Thu 04 Sep 2014, 17:39
by saintless
fredx181 wrote:...here's a .deb for installing the kernel headers version 3.13.6
linux-headers-3.13.6-porteus_i386.deb is here:

https://googledrive.com/host/0ByBgCDlZZ ... /Packages/
Hi, Fred, uploaded here also:
http://www.smokey01.com/saintless/Porte ... s_i386.deb

Toni

Posted: Thu 04 Sep 2014, 17:43
by fredx181
Hi Toni,
Here's a way to keep flashplayer-choice up-to-date when version 11 is changed on http://smokey01.com/OscarTalks/
function flasplayer11:

Code: Select all

# As long flashplayer is at version 11.xxx this should work even when OscarTalks updates it.
flasplayer11() {
mkdir /usr/lib/mozilla
mkdir /usr/lib/mozilla/plugins
cd /usr/lib/mozilla/plugins
# Sort of wildcard workaround for wget: 'flashplayer11*'
wget -r -e robots=off -nd -l1 -A "flashplayer11*" http://smokey01.com/OscarTalks/
# Create variable to continue
FLASH=$(ls flashplayer11*)
mv $FLASH ${FLASH}.tar.gz
tar -zxvf ${FLASH}.tar.gz
rm -f ${FLASH}.tar.gz
# Strip .pet from filename to get directory name.
DIRFLASH=$(echo "${FLASH}" | sed '$s/....$//')
mv $DIRFLASH/usr/lib/mozilla/plugins/libflashplayer.so /usr/lib/mozilla/plugins/libflashplayer.so
rm -fr $DIRFLASH
}
Edit;
Thanks Toni, I hope it works allright.

Fred

Posted: Thu 04 Sep 2014, 17:50
by saintless
Thanks, Fred :)
Link added to the fixes post.

Toni

Posted: Thu 04 Sep 2014, 19:02
by Meshworks
Thanks guys.

Ill try a recompile of the official Catalyst 14 drivers ... the kernel module failed.

Code: Select all

Supported adapter detected.
Check if system has the tools required for installation.
Uninstalling any previously installed drivers.
Unloading radeon module...
Error: Module radeon is in use
Unloading drm module...
libkmod: ERROR ../libkmod/libkmod-module.c:1802 kmod_module_get_holders: could not open '/sys/module/drm/holders': No such file or directory
Error: Module drm is in use
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Message] Kernel Module : Found kernel module build environment, generating kernel module now.
AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/3.13.6-porteus/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
/usr/libexec/gcc/i486-slackware-linux/4.8.2/cc1: error while loading shared libraries: libmpfr.so.4: cannot open shared object file: No such file or directory
/usr/libexec/gcc/i486-slackware-linux/4.8.2/cc1: error while loading shared libraries: libmpfr.so.4: cannot open shared object file: No such file or directory
make[1]: Entering directory `/usr/src/linux-3.13.6'
/usr/src/linux-3.13.6/arch/x86/Makefile:98: stack protector enabled but no compiler support
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/usr/libexec/gcc/i486-slackware-linux/4.8.2/cc1: error while loading shared libraries: libmpfr.so.4: cannot open shared object file: No such file or directory
/usr/lib/gcc/i486-slackware-linux/4.8.2/../../../../i486-slackware-linux/bin/as: error while loading shared libraries: libbfd-2.23.52.0.1.20130226.so: cannot open shared object file: No such file or directory
make[2]: *** [/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1
make[1]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/usr/src/linux-3.13.6'
make: *** [kmod_build] Error 2
build failed with return value 2
[Error] Kernel Module : Failed to compile kernel module - please consult readme.
[Reboot] Kernel Module : update-initramfs

Code: Select all

Uninstalling any previously installed drivers.
Unloading radeon module...
Error: Module radeon is in use
tells me that the radeon driver is active - so its poss that the ati driver pkg may work here with some messing.

Posted: Thu 04 Sep 2014, 23:23
by Meshworks
lsmod ... shows radeon driver active...

Code: Select all

root@wheezy:~# lsmod
Module                  Size  Used by
...
drm_kms_helper         23928  1 radeon
ttm                    35148  1 radeon
...
root@wheezy:~# 
so...

Code: Select all

echo blacklist radeon > /etc/modprobe.d/blacklist.conf
and reboot...

now in vesa graphics with radeon blacklisted...

copied amd-catalyst-14.3_beta-porteus-v3.0-i486-1ftm.xzm
... and reboot

thought it would work ... but again black screen lockup.

I should really be using a pae version... heres my laptop ... which distro / kernel suits best? I'm gonna try debiandog tomoz.

My laptop spec...
http://www.asus.com/Notebooks_Ultrabooks/X102BA/
Asus X102BA
AMD Radeon HD 8180
AMD 2x A4
4GB Ram

Posted: Fri 05 Sep 2014, 05:18
by saintless
Thanks for posting the result, Meshworks!
Please, read the first two post here before starting with DebianDog.
http://www.murga-linux.com/puppy/viewtopic.php?t=93225
This is from the first post.
saintless wrote:DebianDog has kernel 3.2.0-4-486. If it works for your hardware you need nothing more. If it doesn't, please, read here how to boot easy with different kernel.
For modern multi-core machines it will be better to use (026-kernel-3.14-Pae.tar.gz - Debian kernel-3.14-0.bpo.1-686-Pae) or (022-kernel-686-pae.zip - Debian kernel-3.2.0-4-686-Pae) separate module from the link above.
If you have troubles booting with separate pae kernel module write here or in DebianDog thread. Maybe this post will help you also about booting with kernel-3.14-0.bpo.1-686-Pae:
http://www.murga-linux.com/puppy/viewto ... 594#793594

Toni

New version of flite_hts_engine uploaded

Posted: Fri 05 Sep 2014, 14:08
by mcewanw
flite_hts_engine is a reasonably good quality Text To Speech (TTS) synthesiser in an incredibly small package considering it includes the voice data (approx 1.6MB download).

New version (deb package for DebianDog and dotpet for Puppy), that seems to have fixed the problem of occasional garbled text can be downloaded, for now at least, via its main thread post here:

http://www.murga-linux.com/puppy/viewto ... 505#365897

flite_hts_engine does have some limitations, as briefly discussed in that post, however, the relatively good voice quality compared to say standard flite, makes it very useful and the limitations could be worked around via more sophisticated driving scripts.

Cheers, William

Posted: Fri 05 Sep 2014, 14:19
by saintless
Thank you, William!

Both (pet and deb) uploaded here in case dropbox links are deleted in time:
http://www.smokey01.com/saintless/Fredx ... 5_i386.deb
http://www.smokey01.com/saintless/Fredx ... stdout.pet

Edit: Works also for DebianDog-Squeeze :)

Toni

Posted: Fri 05 Sep 2014, 15:37
by fredx181
Hi Meshworks,
You could maybe try this after installing the linux-headers 3.13.6 .deb on Porteus-Wheezy:
http://wiki.cchtml.com/index.php/Debian ... t_package.
Or do a google search on 'debian Catalyst 14' to find more.
Just concentrate on debian, not slackware.
And you can load the DEVX:
http://www.smokey01.com/saintless/Debia ... 2.squashfs
(right-click > save link as)

Fred

mount-wizard

Posted: Sun 07 Sep 2014, 10:55
by anikin
Hi Toni, Fred,

Iguleder's dslr ==>http://murga-linux.com/puppy/viewtopic. ... 306#798306 has an elegant mounting applet. Can you please, have a look at it? Would be nice to have it in DD.

Code: Select all

root@debian:~# /opt/bin/mount-wizard
/opt/bin/mount-wizard: line 91: gtkdialog1: command not found
Here it goes:

Code: Select all

#!/bin/sh

# mount-wizard: a partition mounting wizard

_choose_action() {
	i=0

	echo "<wtitle>Mounting Wizard</wtitle>
<hbox>"

	for partition in $1
	do
		[ 0 -eq $i ] && echo "	<vbox>"

		case "$partition" in
			*mmc*)
				type="sd"
				;;
			*sr*)
				type="disc"
				;;
			*)
				type="drive"
				;;
		esac

		echo "<frame>
<hbox>
	<pixmap>
		<input file>/usr/share/pixmaps/$type.xpm</input>
	</pixmap>
	<vbox>
		<text>
			<label>$partition</label>
		</text>"

		mountpoint -q "/mnt/$partition" > /dev/null 2>&1
		if [ 0 -eq $? ]
		then
				echo "<button>
	<label>Browse</label>
	<action>echo ACTION=browse</action>
	<action>echo PARTITION=$partition</action>
	<action>EXIT=ok</action>
</button>
<button>
	<label>Unmount</label>
	<action>echo ACTION=unmount</action>
	<action>echo PARTITION=$partition</action>
	<action>EXIT=ok</action>
</button>"
		else
			echo "<button>
	<label>Mount</label>
	<action>echo ACTION=mount</action>
	<action>echo PARTITION=$partition</action>
	<action>EXIT=ok</action>
</button>"
		fi

		echo "</vbox>
	</hbox>
</frame>"

		i=$((1 + $i))
		if [ 5 -eq $i ]
		then
			echo "</vbox>"
			i=0;
		fi
	done

	[ 0 -ne $i ] && echo "</vbox>"

	echo "</hbox>"
}

# list all partitions
partitions=""
cd /sys/class/block
for partition in sd* mmc* sr*
do
	case "$partition" in
		*[0-9])
			partitions="$partition $partitions"
			;;
	esac
done

# let the user choose a partition
eval $(_choose_action "$partitions" | gtkdialog1 -s)
[ "abort" = "$EXIT" ] && exit 1

# perform the chosen action
case "$ACTION" in
	browse)
		rox "/mnt/$PARTITION"
		;;

	mount)
		[ ! -d "/mnt/$PARTITION" ] && mkdir "/mnt/$PARTITION"
		mount "/dev/$PARTITION" "/mnt/$PARTITION"
		if [ 0 -eq $? ]
		then
			rox "/mnt/$PARTITION"
		else
			rmdir "/mnt/$PARTITION"
		fi
		;;

	unmount)
		umount "/mnt/$PARTITION"
		[ 0 -eq $? ] && rmdir "/mnt/$PARTITION"
		;;
esac

Re: mount-wizard

Posted: Sun 07 Sep 2014, 15:08
by saintless
Hi, Anikin.

Code: Select all

root@debian:~# /opt/bin/mount-wizard
/opt/bin/mount-wizard: line 91: gtkdialog1: command not found
Sorry, I tried but I can't compile gtkdialog the same way as it is compiled to run this script. Looking at the scripts /dslr-master/patches/gtkdialog1-x86_64.patch and /dslr-master/packages/gtkdialog1.sh we need to install old lenny packages libgtk1.2-dev , libglib1.2-dev and this is impossible in wheezy. I tried to cheat the Control file but it does not help. The compiler exits with error.
The only way I see is someone more experienced than me to re-write the script for gtkdialog version included in DebianDog.

What you can test is to extract gtkdialog1 from dslr, move it in /opt/bin and start mount-wizard script. Maybe it will work.

Toni

Posted: Sun 07 Sep 2014, 15:27
by saintless
fredx181 wrote:Hi Meshworks,
You could maybe try this after installing the linux-headers 3.13.6 .deb on Porteus-Wheezy:
http://wiki.cchtml.com/index.php/Debian ... t_package.
Or do a google search on 'debian Catalyst 14' to find more.
Just concentrate on debian, not slackware.
And you can load the DEVX:
http://www.smokey01.com/saintless/Debia ... 2.squashfs
(right-click > save link as)

Fred
Seems someone builded fglrx in OpenBox DebianDog as separate module + compiz: DEVILDOG There is also chance for pae kernel build from what I read.
This is the content of 07-devildog-0.1-compiz-ati.squashfs/lib/modules/fglrx/make.3.2.0-4-486.log:

Code: Select all

AMD kernel module generator version 2.1
.
Active kernel:
uname -a = Linux dog 3.2.0-4-486 #1 Debian 3.2.51-1 i686 GNU/Linux
uname -s = Linux
uname -m = i686
uname -r = 3.2.0-4-486
uname -v = #1 Debian 3.2.51-1
.
Target kernel:
uname -a = Linux dog 3.2.0-4-486 #1 Debian 3.2.51-1 i686 GNU/Linux
uname -s = Linux
uname -m = i686
uname -r = 3.2.0-4-486
uname -v = #1 Debian 3.2.51-1
.
file /proc/kallsyms says: SMP=1
file /lib/modules/3.2.0-4-486/build/include/generated/autoconf.h says: SMP=0
0
file /lib/modules/3.2.0-4-486/build/include/generated/autoconf.h says: MODVERSIONS=1
0
1
file /lib/modules/3.2.0-4-486/source/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space
.
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/3.2.0-4-486/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-4-486'
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_agp.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_debug.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_ioctl.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_io.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_pci.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_str.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_iommu.o
/lib/modules/fglrx/build_mod/2.6.x/kcl_iommu.c: In function 'KCL_IOMMU_CheckInfo':
/lib/modules/fglrx/build_mod/2.6.x/kcl_iommu.c:190:21: warning: unused variable 'pdev' [-Wunused-variable]
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl.o
  CC [M]  /lib/modules/fglrx/build_mod/2.6.x/kcl_wait.o
  LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /lib/modules/fglrx/build_mod/2.6.x/fglrx.mod.o
  LD [M]  /lib/modules/fglrx/build_mod/2.6.x/fglrx.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-486'
build succeeded with return value 0
.
duplicating results into driver repository...
target location: /lib/modules/fglrx
the debug info stripped from the kernel module
copying fglrx.ko
copying logfile of build
*** end of build log ***
I can't test it but maybe it will help someone.

Edit: Some more information from the source

Toni