User avatar
elmapache
Posts: 16
Joined: Fri Jul 21, 2017 2:51 pm

I can't make OSS4 work in Raspbian Jessie

Sun Aug 06, 2017 9:14 am

Hello. I'm trying to replace ALSA for OSS4 in my Raspberry Pi 3 Model B running Raspbian Desktop. I've tried to do this compiling OSS4 sources and installing from the Raspbian repository without success. Any help please?

Code: Select all

sudo apt-get install oss4-source oss4-gtk oss4-base raspberrypi-kernel-headers
sudo module-assistant prepare
sudo module-assistant auto-install oss4

cd core && rm -f *.o *.ko *.mod.c *.mod.o .*.cmd modules.order
Module.symvers limits.h && rm -rf .tmp_versions && cd ..
cd drivers && rm -f *.o *.ko *.mod.c *.mod.o .*.cmd modules.order
osscore_symbols.inc && rm -rf .tmp_versions && cd ..
/usr/bin/make  -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory '/usr/src/modules/oss4'
cd core && rm -f *.o *.ko *.mod.c *.mod.o .*.cmd modules.order
Module.symvers limits.h && rm -rf .tmp_versions && cd ..
cd drivers && rm -f *.o *.ko *.mod.c *.mod.o .*.cmd modules.order
osscore_symbols.inc && rm -rf .tmp_versions && cd ..
for templ in ; do \
    cp $templ `echo $templ | sed -e 's/_KVERS_/4.9.35-v7+/g'` ; \
  done
for templ in `ls debian/*.modules.in` ; do \
    test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}

                                   <Aceptar>
 ${templ%.modules.in}.backup 2>/dev/null || true; \
   sed -e 's/##KVERS##/4.9.35-v7+/g ;s/#KVERS#/4.9.35-v7+/g ;
   s/_KVERS_/4.9.35-v7+/g ; s/##KDREV##//g ; s/#KDREV#//g ; s/_KDREV_//g  ' <
   $templ > ${templ%.modules.in}; \
  done
  dh_testroot
  dh_clean -k
  dh_clean: Compatibility levels before 9 are deprecated (level 5 in use)
  dh_clean: dh_clean -k is deprecated; use dh_prep instead
  dh_installdirs lib/modules/4.9.35-v7+/kernel/oss4
  dh_installdirs: Compatibility levels before 9 are deprecated (level 5 in
   use)
  # Build the modules
   /usr/bin/make -C /usr/src/linux-headers-4.9.35-v7+
   M=/usr/src/modules/oss4/core modules
make[2]: Entering directory '/usr/src/linux-headers-4.9.35-v7+'
    CC [M]  /usr/src/modules/oss4/core/oss_core.o
   gcc: error: -mfloat-abi=soft and -mfloat-abi=hard may not be used together
  scripts/Makefile.build:293: recipe for target
  '/usr/src/modules/oss4/core/oss_core.o' failed
   make[3]: *** [/usr/src/modules/oss4/core/oss_core.o] Error 1
   Makefile:1490: recipe for target '_module_/usr/src/modules/oss4/core'
   failed
  make[2]: *** [_module_/usr/src/modules/oss4/core] Error 2
   make[2]: Leaving directory '/usr/src/linux-headers-4.9.35-v7+'
   debian/rules:42: recipe for target 'binary-modules' failed
  make[1]: *** [binary-modules] Error 2
  make[1]: Leaving directory '/usr/src/modules/oss4'
   /usr/share/modass/include/common-rules.make:56: recipe for target
   'kdist_build' failed
When I try to install oss4-dkms from packages:

Code: Select all

First Installation: checking all kernels...
dpkg: aviso: la versión `*-*' tiene una sintaxis errónea: el número de versión no empieza por un dígito
It is likely that 4.9.35-v7+ belongs to a chroot's host
Building initial module for 4.9.35-v7+
Error! Bad return status for module build on kernel: 4.9.35-v7+ (armv7l)
Consult /var/lib/dkms/oss4/4.2-build2010/build/make.log for more information.
make.log:

Code: Select all

DKMS make.log for oss4-4.2-build2010 for kernel 4.9.35-v7+ (armv7l)
dom ago  6 11:10:38 CEST 2017
make: Entering directory '/usr/src/linux-headers-4.9.35-v7+'
  CC [M]  /var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o
gcc: error: -mfloat-abi=soft and -mfloat-abi=hard may not be used together
scripts/Makefile.build:293: recipe for target '/var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o' failed
make[1]: *** [/var/lib/dkms/oss4/4.2-build2010/build/core/oss_core.o] Error 1
Makefile:1490: recipe for target '_module_/var/lib/dkms/oss4/4.2-build2010/build/core' failed
make: *** [_module_/var/lib/dkms/oss4/4.2-build2010/build/core] Error 2
make: Leaving directory '/usr/src/linux-headers-4.9.35-v7+'
Placa: Raspberry Pi 3 Model B.
Sistema operativo: OpenBSD 6.2.

Return to “Troubleshooting”