Motherboard no rear audio when "disable front panel jack detection" not selected

I recently built this system.
Motherboard: MSI P67A-G43 (B3) LGA 1155 Intel P67 SATA 6Gb/s USB 3.0 ATX Intel Motherboard
Processor: Intel Core i7-2600 Sandy Bridge 3.4GHz LGA 1155 95W Quad-Core Desktop Processor Intel HD Graphics 2000 BX80623I72600
Memory: G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL7D-8GBXH
Video Card: EVGA SuperClocked 012-P3-1572-AR GeForce GTX 570 (Fermi) 1280MB 320-bit GDDR5
HD 1: OCZ Solid 3 SLD3-25SAT3-120G 2.5" 120GB SATA III MLC
HD 2: Western Digital Caviar Black WD2002FAEX 2TB 7200 RPM SATA 6.0Gb/s 3.5" Internal Hard Drive
Additional NIC: Rosewill RC-400 10/ 100/ 1000Mbps PCI V2.2, 32/64-bit, 33/66MHz Networking LAN Card
DVD: SAMSUNG Black Blu-ray Combo SATA Model SH-B123L LightScribe Support - OEM
Power Supply: OCZ ZT Series 750W Fully-Modular 80PLUS Bronze High Performance Power Supply
Case: Antec One Hundred Black Steel / Plastic ATX Mid Tower Computer Case
I also have an old Creative 4.1 speaker system (been around for about 10 years from system to system)
It worked flawlessly....until.....this morning my daughter was watching NetFlix and she plugged in the headphones. The sound muted the rears (as it is supposed to do) and sound came through the headphones (front jack) as it was supposed to do. She said some popup appeared to which she didn't read and just hit OK (doh!). Now I am unable to get any sound out of the rear speakers when unplugging the headphones. After much playing around, if I un-check "disable front panel jack detection" in the MSI Audio Manager then the sound once again works from the rear, however (as can be expected) it doesn't mute it when the headphone jack is re-plugged in. Strange, thing is that this worked before this morning. It's like it is always detecting the headphones and therefore mutes the rears.

Additional information.
I also have to set: "Separate all input jacks as independent input devices" in the MSI Audio Manager (Device advanced settings) in order to get my microphone to work too.
What the heck happended? What's wrong?
MSI, got any ideas?

Similar Messages

Front panel audio wont mute rear audio when headphones are in.

Hello,
As the title says my sound isn't muted on the rear speakers when I plug in my headphones. The front panel audio didn't work at first, it said in the manual to disable front panel jack detection. Once I did this the audio came through the front panel, but is not muted at the rear, so I have sound from both the headphones that are plugged into the front and the speakers that are in the rear. The option to mute the rear output when headphones are plugged in is enabled, the speakers are plugged into the green jack, the rear speakers are set to stereo line out and the front is set to headphones.
Can anyone help, at the moment I have to keep unplugging the speakers to listen through the headphones without disturbing anyone else, which with the placement of my computer is not convenient.

Hello,
I have used the link, but the drivers just install the same one I already had (both the rar and the exe do this), even if I remove the previous drivers via programs and features. Unfortunately the problem still persists, I am really stumped as to what is causing it. I am not sure if I have AC'97 or HD Audio connectors on the front of the case, as the case came with absolutely no documentation. I have provided a link to the manufacturers website if that could help in anyway.
http://www.xionusa.com/Product-case-Xion2.asp

Noise when using Front-Panel headphone j

This message is for those who may experience noise in headphones plugged into a case's front jack. These noises would likely be heard if one uses a quality phone set with good isolation. (not noise cancelling type) and during quiet times, such as when no music or other audio source is being played, or perhaps when listening to programming with very high dynamic range and the frequent, very low loudness passages of music, etc.. There is no problem with the card. (I'm using an Xtreme Gamer card) The problem will be with the header panel on the case itself. You need to isolate the case ground from the other grounds coming in from the various board headers, such as USB, the sound card, etc. I accomplished this by scraping away the foil from around the stud landings on the panel module board. Of course you need to exercise care when performing such a modification but you will be rewarded with absolute, golden silence, when that's what you should be getting. Again, there is NO problem with the card.

If it is possible to remove the circuit board assembly for the front panel jacks from the case, you can see how the circuit foil "traces" on the board are connected. In my situation, and probably yours, you may find that the mounting screws that hold the circuit board to the computer case will also have the foil traces under them and that those traces will be a common ground to the rest of the circuits on the board. The problem arises because the computer case ground is at a somewhat different "signal" level than the grounds coming into the circuit board from the various "header" connectors, that is, the connectors you mate with the corresponding pins on your sound card, as well as the USB pins, if you choose to hook them up too. There is a great deal of strange noises that can be present in a given motherboard's circuits and associated grounds. All the ground connections from the headers coming into the board should only go to the individual connectors on the front panel. I cut away the foil paths where the grounds were all run together on the circuit board, thus isolating them from one another, as well as cut away the foil under the mounting screws. You may even have to cut foil from both sides of the board, depending on your model. You need to take care not to open up a circuit when making those cuts. A good, sharp Xacto knife or utility knife should work fine.
I found it strange that the designers of the board didn't consider the problem of "ground loops", which is what the problem is defined as. Ground loops, as you can see now, can happen when when a circuit or even separate components altogether, such as a computer, TV and HIFI system are all connected together. In the?HIFI setup case, hum results because the point of incoming cable ground for your TV and/or Internet are at a different 60 Hz voltage from the ground in your home's wiring,?to which your computer is connected for power. This causes a current to flow through the audio cable shields that is large enough to induce a voltage into the audio equipment. I've even heard of ground loops so bad that people have seen sparks when trying to hook up the audio cables between the pieces of equipment. Almost anyone who has a system hookup such as I described has run into that problem of hum when using their computer's audio into their HIFI setup. The only relief is to get some type of ground "isolator" that connects between the incoming cable and your TV and/or Internet cable modem. A quick and dirty solution is to use a grounding adapter in the AC connection for your computer and other equipment that uses a grounding plug. This, of course, is not recommended, but will kill the hum for now. I thought I would throw in the HIFI setup hum problem since, as I said, many people are suffering from that problem.
Even if the header grounds were all shorted together, the problem would be no where near as bad as having the case ground shorted to the header grounds, which was the way mine was made.
I know this is a looooonnnnnng winded post but trying to explain something like this in writing is not easy. Hopefully you will now have a better understanding of what I meant the first time, even though it was by no means a short post either.

Reference to control on main front panel fails when subvi front panel is closed?

Hi All,
I'm experiencing an odd bug. In my code, I use a subvi to control a piece of hardware. This subvi has controls for all of the functions of my hardware.
I'm changing the value of one of these controls from my main front panel by running a reference to a knob on my main front panel into the subvi, grabbing the value of the knob with a property node, and then updating the value of the subvi control using a signaling property node.
This works fine when my subvi front panel is open but fails to work at all when the subvi front panel is closed.
I'm new to labview , so any help is appreciated.
Thanks,
Arpan
Solved!
Go to Solution.

What is your LabVIEW version?
Front panels that are not shown are typically not updated and might not even be loaded into memory.
The presence of certain code elements (e.g. property nodes) often forces the front panel to be in memory even if it is not shown, but I haven't studied it in a long time so there might be subtleties. Maybe somebody from NI can give more details.
If it does not work unles the FP is open, open the front panel minimized to avoid distraction.
Can you attach some code? Maybe there are better ways to do all this anyway.
LabVIEW Champion . Do more with less code and in less time .

Failure saving file .html when printing front panel

Hi,
i´m trying to print the front panel of my VI, selecting HTML file option and it reports an error and doesn´t create the html file. Only if i select black and white on the html printing options i get a file, but i need it in colour. It happneds only with one VI but this failure didn´t use to appeard.
Recently i´ve install labview2011 and this project came from labview2010, which is still on system.
Thanks and excuse my pour and rusty english.

hi Ángeniero
could you please post your vi?
thanx
Renn
Kudos always welcome for helpful posts

MSI GF615M-P33:Front Panel Jack headphone issues.

When plugged in front panel can't hear people talking in videos(no matter what software I use) nor mp3 files but I can hear music alright.
At the rear sound panel it works well.
I got the newest Realtek HD Audio Manager driver....

Found out that front panel jack place is a little bit up........If I put it in totally it sounds quietly.
I have to find a good "location" in female jack to have good volune....

Connecting nFORCE motherboard (audio) to AUDIGY2 front panel

Can I make use of an AUDIGY2 front panel with an nFORCE motherboard (audio) ?

I'd like to connect my Audigy2 front panel to my nForce motherboard...

Asus Xonar DGX no rear sound / mic. Front panel sound/mic ok. [SOLVED]

Hi guys,
I have a ASUS Xonar DGX PCI-E GX2.5 sound card since my onboard audio crapped out on my motherboard. I just did a first time install on my desktop and the rear portion of my card refuses to work. If I connect up my speakers to my analog output in the back I don't have any options in my sound manager for the analog output to just be a 2.0 system. I get 4.0, 4.1, 5.0, 5.1. All of which do not work obviously. Also my microphone doesn't work plugged into the actual card. If I plug them into the front panel audio, both the microphone and headphone out work. I did some searching, and it seems like a likely cause has something to do with amixer being multichannel. I tried several commands but wasn't successful in getting the audio to work through the back. Any help would be useful, I'm still trying to learn a lot about Arch while doing all this. Thanks in advance!
Solution. Using Alsamixer in terminal and selecting the analog out as stereo headphones, instead of stereo headphones (fp).
Last edited by 15goudreau (2014-08-04 21:56:36)

Search for vid and pid combination, ergo 13f6:8788 in your case. This should be one of the search terms, vid and pid could be also separated, other search terms could include oxygen, sonar, dgx and so on. Simple google search should turn something up.
Edit: The point is to locate a thread/post where the support for this card was implemented/talked about. It could provide some further insight.
The simplest approach would be to download linux-rt sources from aur with yaourt, modify PKGBUILD, compile and then install.
yaourt -G linux-rt
cd linux-rt
Copy this into PKGBUILD replacing the original:
# Maintainer: Joakim Hernberg <[email protected]>
# Contributor: Ray Rashif <[email protected]>
# Contributor: timbosa <[email protected]>
# Contributor: Tobias Powalowski <[email protected]>
# Contributor: Thomas Baechler <[email protected]>
pkgbase=linux-rt
pkgname=('linux-rt' 'linux-rt-headers' 'linux-rt-docs') # Build realtime patched -rt kernel
#pkgname=linux-custom # Build kernel with a different name
_kernelname=${pkgname#linux}
_basekernel=3.14
_releasever=12
_rtpatchver=rt9
pkgrel=1
_pkgver=${_basekernel}.${_releasever}
pkgver=${_basekernel}.${_releasever}_${_rtpatchver}
arch=('i686' 'x86_64')
url="http://rt.wiki.kernel.org/"
license=('GPL2')
makedepends=('xmlto' 'docbook-xsl' 'kmod' 'inetutils' 'bc')
options=('!strip')
source=("https://www.kernel.org/pub/linux/kernel/v3.x/linux-${_basekernel}.tar.xz"
"https://www.kernel.org/pub/linux/kernel/v3.x/patch-${_pkgver}.xz"
"https://www.kernel.org/pub/linux/kernel/projects/rt/${_basekernel}/patch-${_pkgver}-${_rtpatchver}.patch.xz"
# the main kernel config files
'config' 'config.x86_64'
# standard config files for mkinitcpio ramdisk
"${pkgname}.preset"
'change-default-console-loglevel.patch'
'0001-Bluetooth-allocate-static-minor-for-vhci.patch'
'0002-module-allow-multiple-calls-to-MODULE_DEVICE_TABLE-p.patch'
'0003-module-remove-MODULE_GENERIC_TABLE.patch'
'0006-genksyms-fix-typeof-handling.patch'
'0007-asus-xonar-dgx.patch')
md5sums=('b621207b3f6ecbb67db18b13258f8ea8'
'89a5af1f3609d0c27e63fea298dd80ed'
'2aa3614e488efa939007a1c428406c30'
'a8126ad28c0a902a575397cacd099db2'
'843119a441c942efc5ec4b73c3c6ced5'
'eb14dcfd80c00852ef81ded6e826826a'
'6623d69fdc936d707990ca060dabd2ce'
'6839ddec74a5300beff1709a81b0e4f3'
'706549e8a05f33f7fc697f28c0ca71d2'
'd23fc66be93ebce698bd7da844789de1'
'16a161979f846b049e90daea907c35dd'
'SKIP')
prepare() {
cd "${srcdir}/linux-${_basekernel}"
# add upstream patch
msg "apply patch-${_pkgver}"
patch -p1 -i "${srcdir}/patch-${_pkgver}"
# add realtime patch
msg "applying patch-${_pkgver}-${_rtpatchver}.patch"
patch -p1 -i "${srcdir}/patch-${_pkgver}-${_rtpatchver}.patch"
# add latest fixes from stable queue, if needed
# http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git
# set DEFAULT_CONSOLE_LOGLEVEL to 4 (same value as the 'quiet' kernel param)
# remove this when a Kconfig knob is made available by upstream
# (relevant patch sent upstream: https://lkml.org/lkml/2011/7/26/227)
msg "change-default-console-loglevel.patch"
patch -p1 -i "${srcdir}/change-default-console-loglevel.patch"
# Fix vhci warning in kmod (to restore every kernel maintainer's sanity)
msg "0001-Bluetooth-allocate-static-minor-for-vhci.patch"
patch -p1 -i "${srcdir}/0001-Bluetooth-allocate-static-minor-for-vhci.patch"
# Fix atkbd aliases
msg "0002-module-allow-multiple-calls-to-MODULE_DEVICE_TABLE-p.patch"
patch -p1 -i "${srcdir}/0002-module-allow-multiple-calls-to-MODULE_DEVICE_TABLE-p.patch"
msg "0003-module-remove-MODULE_GENERIC_TABLE.patch"
patch -p1 -i "${srcdir}/0003-module-remove-MODULE_GENERIC_TABLE.patch"
# Fix generation of symbol CRCs
# http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dc53324060f324e8af6867f57bf4891c13c6ef18
msg "0006-genksyms-fix-typeof-handling.patch"
patch -p1 -i "${srcdir}/0006-genksyms-fix-typeof-handling.patch"
msg "0007-asus-xonar-dgx.patch"
patch -p1 -i "${srcdir}/0007-asus-xonar-dgx.patch"
msg "All patches have successfully been applied"
if [ "${CARCH}" = "x86_64" ]; then
cat "${srcdir}/config.x86_64" > ./.config
else
cat "${srcdir}/config" > ./.config
fi
# if [ "${_kernelname}" != "" ]; then
# sed -i "s|CONFIG_LOCALVERSION=.*|CONFIG_LOCALVERSION=\"${_kernelname}\"|g" ./.config
# sed -i "s|CONFIG_LOCALVERSION_AUTO=.*|CONFIG_LOCALVERSION_AUTO=n|" ./.config
# fi
# set extraversion to pkgrel
#sed -ri "s|^(EXTRAVERSION =).*|\1 -${pkgrel}|" Makefile
# set localversion to pkgrel-rt
sed -i "s|CONFIG_LOCALVERSION=.*|CONFIG_LOCALVERSION=\"-${pkgrel}${_kernelname}\"|g" ./.config
# don't run depmod on 'make install'. We'll do this ourselves in packaging
sed -i '2iexit 0' scripts/depmod.sh
# get kernel version
make prepare
# load configuration
# Configure the kernel. Replace the line below with one of your choice.
#make menuconfig # CLI menu for configuration
#make nconfig # new CLI menu for configuration
#make xconfig # X-based configuration
#make oldconfig # using old config from previous kernel version
# ... or manually edit .config
# rewrite configuration
yes "" | make config >/dev/null
# stop here
# this is useful to configure the kernel
#msg "Stopping build"; return 1
build() {
cd "${srcdir}/linux-${_basekernel}"
make ${MAKEFLAGS} LOCALVERSION= bzImage modules
package_linux-rt() {
pkgdesc="The Linux Kernel and modules (with realtime preemption)."
#groups=('base')
depends=('coreutils' 'linux-firmware' 'kmod' 'mkinitcpio>=0.7')
optdepends=('crda: to set the correct wireless channels of your country')
# provides=("kernel26${_kernelname}=${pkgver}")
# conflicts=("kernel26${_kernelname}")
# replaces=("kernel26${_kernelname}")
backup=("etc/mkinitcpio.d/${pkgname}.preset")
install=${pkgname}.install
cd "${srcdir}/linux-${_basekernel}"
KARCH=x86
# get kernel version
_kernver="$(make LOCALVERSION= kernelrelease)"
# _basekernel=${_kernver%%-*}
# _basekernel=${_basekernel%.*}
mkdir -p "${pkgdir}"/{lib/modules,lib/firmware,boot}
make LOCALVERSION= INSTALL_MOD_PATH="${pkgdir}" modules_install
cp arch/$KARCH/boot/bzImage "${pkgdir}/boot/vmlinuz-${pkgname}"
# add vmlinux
install -D -m644 vmlinux "${pkgdir}/usr/src/linux-${_kernver}/vmlinux"
# set correct depmod command for install
cp -f "${startdir}/${install}" "${startdir}/${install}.pkg"
true && install=${install}.pkg
sed \
-e "s/KERNEL_NAME=.*/KERNEL_NAME=${_kernelname}/" \
-e "s/KERNEL_VERSION=.*/KERNEL_VERSION=${_kernver}/" \
-i "${startdir}/${install}"
# install mkinitcpio preset file for kernel
install -D -m644 "${srcdir}/${pkgname}.preset" "${pkgdir}/etc/mkinitcpio.d/${pkgname}.preset"
sed \
-e "1s|'linux.*'|'${pkgname}'|" \
-e "s|ALL_kver=.*|ALL_kver=\"/boot/vmlinuz-${pkgname}\"|" \
-e "s|default_image=.*|default_image=\"/boot/initramfs-${pkgname}.img\"|" \
-e "s|fallback_image=.*|fallback_image=\"/boot/initramfs-${pkgname}-fallback.img\"|" \
-i "${pkgdir}/etc/mkinitcpio.d/${pkgname}.preset"
# remove build and source links
rm -f "${pkgdir}"/lib/modules/${_kernver}/{source,build}
# remove the firmware
rm -rf "${pkgdir}/lib/firmware"
# gzip -9 all modules to save 100MB of space
find "${pkgdir}" -name '*.ko' -exec gzip -9 {} \;
# make room for external modules
ln -s "../extramodules-${_basekernel}${_kernelname:--rt}" "${pkgdir}/lib/modules/${_kernver}/extramodules"
# add real version for building modules and running depmod from post_install/upgrade
mkdir -p "${pkgdir}/lib/modules/extramodules-${_basekernel}${_kernelname:--rt}"
echo "${_kernver}" > "${pkgdir}/lib/modules/extramodules-${_basekernel}${_kernelname:--rt}/version"
# Now we call depmod...
depmod -b "$pkgdir" -F System.map "$_kernver"
# move module tree /lib -> /usr/lib
mv "$pkgdir/lib" "$pkgdir/usr"
package_linux-rt-headers() {
pkgdesc="Header files and scripts for building modules for linux kernel (with realtime preemption)."
# provides=("kernel26${_kernelname}-headers=${pkgver}")
# conflicts=("kernel26${_kernelname}-headers")
# replaces=("kernel26${_kernelname}-headers")
install -dm755 "${pkgdir}/usr/lib/modules/${_kernver}"
cd "${pkgdir}/usr/lib/modules/${_kernver}"
ln -sf ../../../src/linux-${_kernver} build
cd "${srcdir}/linux-${_basekernel}"
install -D -m644 Makefile \
"${pkgdir}/usr/src/linux-${_kernver}/Makefile"
install -D -m644 kernel/Makefile \
"${pkgdir}/usr/src/linux-${_kernver}/kernel/Makefile"
install -D -m644 .config \
"${pkgdir}/usr/src/linux-${_kernver}/.config"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/include"
for i in acpi asm-generic config crypto drm generated keys linux math-emu \
media net pcmcia scsi sound trace uapi video xen; do
cp -a include/${i} "${pkgdir}/usr/src/linux-${_kernver}/include/"
done
# copy arch includes for external modules
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/arch/x86"
cp -a arch/x86/include "${pkgdir}/usr/src/linux-${_kernver}/arch/x86/"
# copy files necessary for later builds, like nvidia and vmware
cp Module.symvers "${pkgdir}/usr/src/linux-${_kernver}"
cp -a scripts "${pkgdir}/usr/src/linux-${_kernver}"
# fix permissions on scripts dir
chmod og-w -R "${pkgdir}/usr/src/linux-${_kernver}/scripts"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/.tmp_versions"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/arch/${KARCH}/kernel"
cp arch/${KARCH}/Makefile "${pkgdir}/usr/src/linux-${_kernver}/arch/${KARCH}/"
if [ "${CARCH}" = "i686" ]; then
cp arch/${KARCH}/Makefile_32.cpu "${pkgdir}/usr/src/linux-${_kernver}/arch/${KARCH}/"
fi
cp arch/${KARCH}/kernel/asm-offsets.s "${pkgdir}/usr/src/linux-${_kernver}/arch/${KARCH}/kernel/"
# add docbook makefile
install -D -m644 Documentation/DocBook/Makefile \
"${pkgdir}/usr/src/linux-${_kernver}/Documentation/DocBook/Makefile"
# add dm headers
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/md"
cp drivers/md/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/md"
# add inotify.h
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/include/linux"
cp include/linux/inotify.h "${pkgdir}/usr/src/linux-${_kernver}/include/linux/"
# add wireless headers
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/net/mac80211/"
cp net/mac80211/*.h "${pkgdir}/usr/src/linux-${_kernver}/net/mac80211/"
# add dvb headers for external modules
# in reference to:
# http://bugs.archlinux.org/task/9912
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-core"
cp drivers/media/dvb-core/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-core/"
# and...
# http://bugs.archlinux.org/task/11194
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/"
cp include/config/dvb/*.h "${pkgdir}/usr/src/linux-${_kernver}/include/config/dvb/"
# add dvb headers for http://mcentral.de/hg/~mrec/em28xx-new
# in reference to:
# http://bugs.archlinux.org/task/13146
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-frontends/"
cp drivers/media/dvb-frontends/lgdt330x.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-frontends/"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/i2c/"
cp drivers/media/i2c/msp3400-driver.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/i2c/"
# add dvb headers
# in reference to:
# http://bugs.archlinux.org/task/20402
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/usb/dvb-usb"
cp drivers/media/usb/dvb-usb/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/usb/dvb-usb/"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-frontends"
cp drivers/media/dvb-frontends/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/dvb-frontends/"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/tuners"
cp drivers/media/tuners/*.h "${pkgdir}/usr/src/linux-${_kernver}/drivers/media/tuners/"
# add xfs and shmem for aufs building
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/fs/xfs"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}/mm"
cp fs/xfs/xfs_sb.h "${pkgdir}/usr/src/linux-${_kernver}/fs/xfs/xfs_sb.h"
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p "${pkgdir}"/usr/src/linux-${_kernver}/`echo ${i} | sed 's|/Kconfig.*||'`
cp ${i} "${pkgdir}/usr/src/linux-${_kernver}/${i}"
done
chown -R root.root "${pkgdir}/usr/src/linux-${_kernver}"
find "${pkgdir}/usr/src/linux-${_kernver}" -type d -exec chmod 755 {} \;
# strip scripts directory
find "${pkgdir}/usr/src/linux-${_kernver}/scripts" -type f -perm -u+w 2>/dev/null | while read binary ; do
case "$(file -bi "${binary}")" in
*application/x-sharedlib*) # Libraries (.so)
/usr/bin/strip ${STRIP_SHARED} "${binary}";;
*application/x-archive*) # Libraries (.a)
/usr/bin/strip ${STRIP_STATIC} "${binary}";;
*application/x-executable*) # Binaries
/usr/bin/strip ${STRIP_BINARIES} "${binary}";;
esac
done
# remove unneeded architectures
rm -rf "${pkgdir}"/usr/src/linux-${_kernver}/arch/{alpha,arc,arm,arm26,arm64,avr32,blackfin,c6x,cris,frv,h8300,hexagon,ia64,m32r,m68k,m68knommu,metag,mips,microblaze,mn10300,openrisc,parisc,powerpc,ppc,s390,score,sh,sh64,sparc,sparc64,tile,unicore32,um,v850,xtensa}
package_linux-rt-docs() {
pkgdesc="Kernel hackers manual - HTML documentation that comes with the Linux kernel (with realtime preemption)."
# provides=("kernel26${_kernelname}-docs=${pkgver}")
# conflicts=("kernel26${_kernelname}-docs")
# replaces=("kernel26${_kernelname}-docs")
cd "${srcdir}/linux-${_basekernel}"
mkdir -p "${pkgdir}/usr/src/linux-${_kernver}"
cp -al Documentation "${pkgdir}/usr/src/linux-${_kernver}"
find "${pkgdir}" -type f -exec chmod 444 {} \;
find "${pkgdir}" -type d -exec chmod 755 {} \;
# remove a file already in linux package
rm -f "${pkgdir}/usr/src/linux-${_kernver}/Documentation/DocBook/Makefile"
# vim:set ts=8 sts=2 sw=2 et:
Then create the file '0007-asus-xonar-dgx.patch' with the following content:
--- a/sound/pci/oxygen/oxygen.c 2014-08-01 20:45:20.299191180 +0200
+++ b/sound/pci/oxygen/oxygen.c 2014-08-01 20:46:11.179947117 +0200
@@ -105,7 +105,7 @@
{ OXYGEN_PCI_SUBID(0x10b0, 0x0219), .driver_data = MODEL_CMEDIA_REF },
{ OXYGEN_PCI_SUBID(0x13f6, 0x0001), .driver_data = MODEL_CMEDIA_REF },
{ OXYGEN_PCI_SUBID(0x13f6, 0x0010), .driver_data = MODEL_CMEDIA_REF },
- { OXYGEN_PCI_SUBID(0x13f6, 0x8788), .driver_data = MODEL_CMEDIA_REF },
+ { OXYGEN_PCI_SUBID(0x13f6, 0x8788), .driver_data = MODEL_XONAR_DGX },
{ OXYGEN_PCI_SUBID(0x147a, 0xa017), .driver_data = MODEL_CMEDIA_REF },
{ OXYGEN_PCI_SUBID(0x1a58, 0x0910), .driver_data = MODEL_CMEDIA_REF },
/* Asus Xonar DG */
Finally run makepkg, should there be errors try removing the src dir first 'yes|rm -r src', then run makepkg again. Should there still be an error post here.
As for the patch, should there be no real difference there is also MODEL_XONAR_DG, might be worth trying out.
Last edited by emeres (2014-08-01 22:34:05)

Option for disabling front panel Update?

I just wanted to know is there any option in the VI properties or somewhere to disable the updation of Front panel controls and Indicators?. When I run an RT code it has a big cluster so when I open that vi the whole RT gets hanged and getting restarted giving an error message as software error, I want to fix this and debug the RT code. Any suggestion please.
The best solution is the one you find it by yourself

Are you looking for 'Defer Front Pannel' property?
Also, don't use the FP for RT code. any way it does not going to help after you building the RT EXE.
Even, you can use the 'Shared Variable' to debug the RT code and pass the data between RT and Windows.
Regards,
Yogesh Redemptor
Regards,
Yogesh Redemptor
Attachments:
Defer Front Panel Update.vi ‏12 KB

Disabling Front Panel Controls

Hello,
Currently I am working on trying to disable/gray out between 10-20 front panel controls when a start button is pressed, and then enabling them at the completion of the test. Currently I am using property nodes which all are wired to a constant of which state I want which works perfectly. My question lies with there being another way other than having a bunch of property nodes filling up my event structure. Ive read where people had subVI's that used references to do this same function, but is there a way to do this right in the block diagram of my current VI? Thank you!

So you have to create references of your front panel controls, this can be quick, since you can select multiple, and with right click you create references.
I have attached a version LV2010.
edit: another advice:
You have to create only once these references. Usually it is comfortable to bundle all the references into a cluster, and use this wire through your whole code. In this way you can just unbundle those references which at the actual location you need to play with, put them into an array, and use the above FOR loop to change their properties...
Like this:

How do I prevent scroll bar use from disabling front panel updates?

I have two top-level VIs running simultaneously using different execution systems. The first VI has a list box scroll bar. When the scroll bar is used by the operator, updates to the second VI front panel are temporarily blocked. This is due to the single user interface thread shared by both VIs. I there anyway to allow the second VI to update its front panel while the first VI is bound to its scroll bar?

Hi,
Your problem seems to be a bit more complex. I created two vi's, one with a simple loop, the other with a list box (both running in different execution systems). The first isn't noticeably affected by moving the listbox' scrollbar.
It there an increase in processor load when you move the scrollbar? That could stop the other vi from updating. Perhaps you can isolate the problem (remove all irrelevant code) and post the remaining vi's?
Regards,
Wiebe.
"wwwbrown" <[email protected]> wrote in message news:[email protected]..
I have two top-level VIs running simultaneously using different execution systems.  The first VI has a list box scroll bar.  When the scroll bar is used by the operator, updates to the second VI front panel are temporarily blocked.  This is due to the single user interface thread shared by both VIs.  I there anyway to allow the second VI to update its front panel while the first VI is bound to its scroll bar?

Dialog box problem when controlling front panel remotely

I have encountered an issue with the Web Publishing Tool- I have a VI that calls a subvi that uses the Promt User for Input function. When controlling the front panel from another computer I get a message saying that you "Cannot control subVI front panels remotely" and points you to the machine actually running LabView to enter the information in the Prompt User dialog box. I set the subVI front panel to show when called, which does show the front panel of the subVI, but still get the error related to the dialog box.
Is there any way to make this work? Am I missing something obvious?
Thanks,
Nathan

Hi Nathan.
There are some limitations with dialog boxes in remote applications. This tutorial has some good examples and explanations on functionality to avoid with web applications. Additionally, the LabVIEW online Help offers some general guidance for Viewing and Controlling Front Panels Remotely, which may help you in further developing your application.
Hope that helps!
Lorielle P.
Applications Engineer
National Instruments

Button Function Problem When Showing Front Panel of Sub VI

Good Afternoon,
I have a created a simplified version of a much more complicated vi to illustrate the problem I am having. Attached is a main vi and a sub vi. The main vi has a boolean which says to open or close the front panel of the sub-vi. This works great. However, the other push button ( " My Button Function" ) on the main vi does not work properly when the sub-vi front panel is being displayed. It is supposed to be a "switch until released" button. However, if you try to click and hold it down while the sub-vi panel is displayed it acts as if I am clicking the button rather than being able to hold it down? I was wondering why showing the sub-vi front panel makes this happen? And also, if anyone has any recommendations to fixing this problem?
Attachments:
main.vi ‏12 KB
sub.vi ‏5 KB

What is happening is the loop is running very fast. It is constantly reading the open SubVI button and opening the subVI if true, even if the subVI front panel is already open. If you are trying to hold down the other button, the opening of the subVI front panel is taking away the focus from the main VI and thus acting like you let up on the button.
Maintain the status of the subVI in a shift register and only open or close it if the status changes. See attached Main VI.
Attachments:
main.vi ‏12 KB

Hide / Disable Front Panel

Long story, long:
I created a small utility as a VI. The utility accepts command line arguments, reads a file, outputs (using .NET) to the console, and then should exit. The front panel is blank, and the program should complete in a fraction of a second. In fact, I bet the "application" overhead takes more time than the actual program. I would have coded this in another language, but I can only read the cluster written to a binary file with LabVIEW.
Environment:
Windows XP, LabVIEW 8.2.1, .NET Framework 3.5
Long story, short:
How do I prevent a LabVIEW program from
displaying the front panel and showing up in the Taskbar?
Solved!
Go to Solution.

There is also an option to close just the front panel, try it with the 100% transparently option also
Rodrigo Cuenca
www.cidesi.com

Front Panel objects do not stay in place after saving, closing, and reopening the VI.

I have been working with a couple of versions of a main VI. The original VI was given to me so that I could add additional functionalities to it. I had been designing the front panel of the latest version of the VI on a Dell laptop running Windows 7 and LabView 2011 SP1 using a monitor with a resolution of 1920x1080. My booleans, numerics, and plots on the front panel had always stayed in place after saving, closing, and reopening the VI. Once in the field, I connected my laptop to a cRIO9073 and used my laptop screen with a resolution of 1366x768 to operate the VI. I made some changes to the VI, saved it, and reopened it. This time I noticed that the front panel objects had become overlapped, resized, and generally rearranged. I tried fixing the objects but I noticed that they reverted back to the incorrect positions after saving and reopening the VI. I was successful in keeping the objects in position a couple of times, but when I would open the VI at a later time, the objects were again rearranged. This is happening on both my monitor and laptop screen. The original version of the VI, however, does not behave this way and I have opened it on both my monitor and laptop screen. In this version, the front panel objects always stay in place. Both VI's have the same window size properties. Could I have corrupted the latest version of my VI somehow? Below are screenshots of the front panels of both VI's.
Attachments:
Blender Controller Original.PNG ‏140 KB
Blender Controller.PNG ‏203 KB

Hi Miguel,
It is possible to programmatically set or change the position of front panel objects. (for example: http://digital.ni.com/public.nsf/allkb/4D0DA06B43195B3F862572F3000AF2D3?OpenDocument) However, if you haven’t intentionally done that, it seems unlikely that it is the problem.
Have you tried copying the entire block diagram in to a new VI to see if the problem persists? While it is unlikely, you are right that it is possible for VIs to become corrupted. I’ve never heard of a situation like this except in the situation where the settings Tom had you check have been changed. Here is some information about those settings:
http://digital.ni.com/public.nsf/allkb/7567EF257B9CFDF986256F630073228F?OpenDocument
Since there was no rearrangement when you copied the front panel to a new VI, you might try copying the block diagram a little bit at a time to see if there is some particular part of it that creates the problem somehow.
K. Johnson

Motherboard no rear audio when "disable front panel jack detection" not selected

Similar Messages

Maybe you are looking for