Slackware :: HDMI Sound After Building A New Kernel ( Slackware 13.1 )?
Aug 21, 2010
I'm currently trying to install unRaid on Slackware following this tutorial :[URL].. I'm new to Linux and after many hours, i finally managed to build the new kernel for unRAID (2.6.32.9). But audio on HDMI port doesn't work I tried alsaconf without success. HDMI sound works when i boot into the old kernel.
Since there was a lot of talk about virtualization I thought I try kvm -- before I used VirtualBox. I took the SlackBuild from SlackBuilds.org and got an error with u8 as type in /usr/include/scsi/scsi.h. (sorry, I don't have the exact error message anymore..) I searched for its definition and I only found __u8 in /usr/include/linux/types.h. Then I searched the web and found a "fix" which says I have to change u8 from /usr/include/scsi/scsi.h to __u8. This problem was solved, but when I run the SlackBuild now it stops at some point and I don't know why. These are the last few lines of output:
CC arm-softmmu/translate.o CC arm-softmmu/tcg/tcg.o CC arm-softmmu/tcg/tcg-runtime.o CC arm-softmmu/fpu/softfloat.o ..... LINK i386-softmmu/qemu AR arm-softmmu/libqemu.a LINK arm-softmmu/qemu-system-arm root@tux:/home/christian/Downloads/kvm#
I put an echo after the make for building kvm and I put an echo after "make install". None of them are printed.
I have a brand new installation of 13.37 but I can't seem to get the nvidia-kernel (64 bit only) Slackbuild from slackbuilds.org to build. I have the nvidia driver installed and working on 13.1 so I am not desperate yet: although I thought that it could just be something with the older Nvidia driver so I waited for the updated release but it fails in the same way.I have uninstalled xf86-video-nouveau and installed xf86-video-nouveau-blacklist-noarch-1.txz from /extra.I have also installed libvdpau from SBo. The nvidia-driver Slackbuild builds fine.I am using the stock 2.6.37.6 huge kernel but have also tried the 2.6.38.4 kernel from /extra and the 2.6.38.7 kernel from Slackware-current.Here is the error message I am seeing:
I am having trouble getting sound to work through hdmi, I changed the device in the kde settings for multimedia and it now works in Amarok but Mplayer and VLC are refusing.
This is the error i am getting with mplayer:
I have disabled my sound card in the bios to save confusion (on my part) Upgraded my kernel to 2.6.37. My gfx card is a NV gt 430 xt
I'm very keen on getting Mumble installed on my slackware -current 64 bit install. I found a slackbuild script for 12.2 here, but changing the version number resulted in failure. I also tried following the build instructions on the Mumble website, which failed with the following.
Code: neil@slackbox:~/Downloads/mumble/mumble-1.2.2$ qmake -recursive main.pro Reading /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead. WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
I'm trying to build erlang-otp using slackbuild script from http://slackbuilds.org/. I've got these errors while building:
Code: checking lex output file root... configure: error: cannot find output from flex; giving up configure: error: /bin/sh '/tmp/SBo/otp_src_R14B01/lib/megaco/./configure' failed for megaco/. configure: error: /bin/sh '/tmp/SBo/otp_src_R14B01/lib/configure' failed for lib GNU flex is in system, so I have no idea what has goes wrong. Maybe someone know the issue?
I just upgraded my Slackware64-current version to the latest kernel 2.6.32.3. Almost everything works just fine, except that I have no sound on the command line and in web browsers, anymore. I don't get any sound out of the command line program play and Flash.
For example, I have a few .wav files, that I can play with Kaffeine and Amarok, but when I try to play them with play on the command line, the program runs and displays that it plays the file, but I don't hear any sound. The same happens with XMMS, too: It displays the usual graphics showing the dynamics and the progress, but my speakers remain silent.
Also, alsaconf doesn't detect my audio hardware, anymore. I have onboard sound and a Creative X-Fi PCI card. Usually both were "seen" by alsaconf. Now it tells me, that it can't identify any audio cards.
On the other hand, when I go into the multimedia section of the KDE system settings, I can "Test" the audio hardware, and the onboard sound works great and I can hear the KDE welcome sound. I have already remove all packages withe 'alsa' in their name and re-installed them, including their compat32 peers, and rebooted several times. Up to now to no avail. Does anyone have a clue, what the problem is caused by?
it's possible to compile the 2.6.37 kernel patched with the autogroup patch on a Slackware 13.1 system running 2.6.33.4-smp with 2.6.33.4 headers? I just compiled and installed the 2.6.37-autogroup kernel from AUR on my ARCH setup and I like it especially when using firefox with lots of tabs open and other background apps also running. I did notice a speed and smothness difference in my ARCH testing setup with this kernel patch and I can get same results in 13.1??
I'm trying to bring my Slackware system back to life as my XP HDD is dying... I've got everything working except for my audio. I got a new motherboard (ASRock P43DE3) and it has a VIA VT1708S as the onboard audio. Is there any way I can get this working without rebuilding the kernel?
after update to slackware current 4 days ago i cant get sound working in wine in starcraf 2 i mean i got sound in instalation but not in game and i get error when i wanna configure sound in winecfg
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element err:alsa:wine_snd_pcm_recover underrun occurred err:alsa:wine_snd_pcm_recover underrun occurred
in game i dont got that error but sound dont work btw my sound card is asus xonar essence stx
I updated my kernel in slackware current but can't install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.How can i install lilo so i can boot into my sistem??
I installed Slackware 13 in VirtualBox 3.1 (seehere)When I'm logged in as a normal user, I get a mesage that Intel *** (sound device) doesn't work anymore and I hear no sound.But it works very fine when I'm logged in as root.
I did some research and located a nice packaging script "nspluginwrapper.SlackBuild" so I decided to go that route and build a Slackware package for nspluginwrapper. The error I get is the inability to find /usr/include/gnu-32.h when it is building the nspluginviewer. Not realizing that the viewer is what is used by the Browser I edited the configure script to not build that piece and it worked fine after that but of course that defeated what I was trying to do. What it looks like is that I need to have 32 bit headers or both headers and libraries installed to be able to build the viewer. I just want to use the acrobat reader plugin in Firefox. Would someone please provide an explanation of what I need to do to build nsplguinwrapper viewer?
I'm using Slackware 13.1, just messing around with some stuff before I upgrade to 13.37. I really want to get a decent build of Desmume working, but the 3D engine for it requires OSMesa to be enabled. I've removed the initial Mesa package that I installed from the Slackware DVD and I'm trying to recompile mesa-7.8.1 so that OSMesa is available for the system. However, I keep running into problems.
Code:
./configure --enable-gl-osmesa
When I run those options for the configure command and compile it, Mesa builds alright and gives me a working libGL just fine. It also gives me libOSMesa. Yet, when I compile Desmume to specifically use OSMesa, its configure script says that it can't find OSMesa at all. But running ldconfig -p, the output shows libOSMesa.so in /usr/lib. The symlink is up to date too, and I've recreated it several times.
Code:
./configure --with-driver=osmesa
When I build Mesa using these configure options, I don't get libGL (well, that's expected, the manual says as much will happen). But apparently libOSMesa is installed just fine. When I went to compile Desmume, no gripes about OSMesa, but Desmume needs both libGL and OSMesa to work properly.
So my question is, how can I install Mesa so that I have OpenGL and OSMesa working together? I've been able to get one working, but not both. I don't know how to get OpenGL on Slackware without using the Mesa package, but the package isn't cooperating. I'm on Intel graphics too.
I've been trying to install Compiz 0.8.4 from the source code provided by the Compiz people.
However, when I run make on the first set of code (compiz-0.8.4 tar package), it halts with the following error:
Code:
As well as --disable-gconf and --disable-gnome since gnome isn't install on Slackware (I've also tried it without those, but it picks up on it anyway and throws them out). The folder I'm running this from is /root/Desktop/Compiz Fusion/compiz-0.8.4.
I'm building a NAS, based on the Intel SS4200. There are 4 drive bays in the machine for use with SATA disks, two of which I plan on filling now, the other two which I plan on filling later. The box also includes an IDE connector to which I will connect an 8GB Disk on Module onto which I will install Slackware. I wish to have all drives in the box show up as one contiguous volume. What partitioning/LVM/RAID configuration can I use which will allow me to:
1. Add a disk and transparently grow the available space of the volume? 2. Replace a disk with a larger disk and transparently grow the available space of the volume? 3. Lose a disk to hardware failure and replace it with a new one with no data loss?
If I use RAID 5, I'm pretty certain I can get numbers 1 and 3 above, but I'm not sure about number 2. The downside is that I'd have to start with 3 disks in the machine, and I'm unsure if adding a 4th disk whose size is larger than each of the 3 starting disks would lead to wasted space. For instance, if I start with three 1TB drives in RAID 5, and then add a 2TB 4th drive, would my available size go from 2TB to 3TB? Or from 2TB to 3.xTB?
Is it important in a RAID 5 setup to have all disks the same size? With LVM, I can certainly get number 1 above, but what about 2 and 3? I know you can use LVM to present many disks or partitions as one contiguous volume, but if I have two 1TB drives in one volume, and only have 300GB of data, then would the second drive remain empty until I broke the 1TB barrier? In this case, it's wasted space from the get go. I suppose another option would be to start with RAID 1 until I can afford a third disk.
When adding the new disk, could I switch to RAID 5 without data loss? I'm planning on maintaining a full mirror of the NAS on some USB disks as a backup, so if configuration changes to the NAS require wiping the disks and restoring from backup, it's not a total loss. However, it certainly makes me nervous to be in a state where only one copy of the data exists, so I'd rather find a solution where I can add and upgrade disks in the NAS without relying on the backup copies.
I've done a clean install of Slackware 13.37 64-bit and am having trouble with building the Perl modules for Bugzilla 4.x.x (downloaded yesterday with bzr). This same problem exists with both Bugzilla stable and 4.1.2+.Executing checksetup.pl results in
Code: checksetup.pl * This is Bugzilla 4.1.2+ on perl 5.12.3
Trying to get Midori browser from SBOpkg's and one of the dependencies is libsoup.configure: error: GLIB 2.21.3 or later is required to build libsoup.Anyone able to give me a pointer in the right direction to overcome this.
I use Slackware 13.0 with the 2.6.33.2 kernel, and I use GnomeSlackbuild.I tried to get help on their discussion group, but I didn't get any.I'm trying to build gnome-power-manager 2.30, because it uses the new upower interface (so it seems). I have GTK+ 2.18.9.
So I've wanting to try out the new development branch of compiz (0.9). I made some slackbuilds a while back and installed all of the necessary packages for the compiz window manager. However when ever I tried to launch the program using "compiz --replace ccp &" I would get a segmentation fault. I forgot about it but today I decided to give it another go and after a few hours I decided to try and see what would happen if I just built compiz-core from source with out using a slackbuild, and sure enough it now works. I have hacked the script trying different combinations to try and make it work but no matter what I try unless I install from scratch (directly into the tree) it will not work. If anyone has any ideas on how to fix this so I can make an actual slack package please let me know. Also I used the main developers forum post as a referencem you can view his instructions here [URL]..
I would like to recompile my kernel to add few modules to it but I would like to keep my current configuration so as not to have troubles with missing drivers for my hardware and stuff.
I'm getting ready to install Slackware64_13.1 (finally), and I may then install Eric's multilib packages. The slackbuild for Wine at Slackbuilds.org states:
[code]...
has anyone built WINE with the 32-bit compatibility packages? Does it work?
