[SOLVED] Yet another microphone capture with Intel HD Audio 82801H

Hello,
I have a macbook pro 4.1.
I have been using Gentoo for years and after wanting to change, I decided to go for Arch Linux.
So I reinstalled my macbook with Arch and so far, I can't make the audio work correctly.
My problems are:
- no microphone working
- no switch between speakers and headphones when I plug them
Here is the output of lspci:
lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
My modprobe.d/soud.conf:
alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
#alias snd-card-0 snd-hda-intel
#alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=mb5 enable_msi=1 power_save=0
#options snd-hda-intel model=laptop
alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss
As you can see, I tried several "model=" options (mb, laptop, ...). Only the "mb5" allows me to hear something from the speaker.
I discussed about my Gentoo experience because on this same laptop, I had it working perfectly on a kernel 2.6.39.
So I thought maybe some option in the ARCH kernel conflicts with it (I am kind of desperate).
I therefore compiled a custom kernel and removed a lot of modules that were useless for me... still no luck!
As a note, on Gentoo, I didn't have to specify the model.
To be fully complete in my description, on Gentoo, I was on 64 bits and here, I'm on 32 (for different reasons).
And I have Pulseaudio installed, not that I want to but as I like Gnome 3... But even without (unsintalling Gnome 3 and Pulseaudio), I still had the same issues, so to me, it doesn't seem to be coming from Pulseaudio, but I could be wrong.
And to answer the obvisous: no I don't have anything muted on alsamixer except "Line" and "Beep".
Thanks in advance for your help because it drives me a bit crazy...
Last edited by theseus (2011-08-24 16:04:52)

Welcome to Arch! I run both Arch and Gentoo and like them both. I have my doubts that your sound problem is an Arch specific issue (but stranger things have happened).
If my google-fu is any good, it seems that the general consensus on getting ALSA to behave with a Macbook Pro 4.1 is:
   options snd_hda_intel model=mbp3
Here's just one (old) example:
http://osdir.com/ml/linux.ports.mactel. … 00003.html
You tried that one yet?

Similar Messages

  • Yet another MacBook Pro with display issues (NVdia chip)

    Exactly one year and 1 week after purchase, my video controller started freaking out. So just 1 week out of warranty, my display started flickering, blinking, showing garbled clumps of pixels and got progressively worse over the last week until, now, it locks up and/or reboots after about 15 minutes of uptime.
    I have:
    - installed all updates, including firmware
    - reset PRAM
    - re-seated RAM
    - replaced RAM
    - used SMC FanControl to try and keep the GPU cool
    - parked the MacBook in front of the fan/air conditioner in an attempt to keep the GPU cool
    - ran the Hardware Test, which returned a faulty video controller
    None of the above have had any positive effect whatsover.
    I've dug through these forums and hunted around the rest of the net for more info. Every symptom points to the NVidia GeForce issue. It seemed to be heat related. Maybe it was at first (even though max temps were never over 180 F), but after just one more day it doesn't seem to matter anymore. The machine is just FUBAR.
    Tomorrow, I'm taking it in to the Apple store for service. Everything I've read here tells me it'll be at $1,000 logic board replacement since I'm a week out of warranty. Needless to say, if I come home tomorrow with a $1,000 receipt AND no laptop I'm going to be pretty upset.
    What really concerns me is that, if I have to get the logic board replaced, they'll just put in yet another faulty board with another NVdia chip that will do the same thing all over again. There has to be another option, short of just getting a new iMac or tower with an ATI card instead. What else can I do?

    bikemonkey wrote:
    I think my GPU is borked too.
    http://noizesurge.com/downloads/gpu1.jpg
    http://noizesurge.com/downloads/gpu2.jpg - incidentally my computer had completely frozen at this point.
    I'm pretty sure from observing these types of glitches that this is a hardware fault. I shall ring Apple on Monday and hopefully they can pick it up and sort it all out! Does anyone know roughly how long a turnaround is in the UK?
    Yes, your video controller is toast. That's exactly how mine looked.
    Just to make certain, run the Hardware Test:
    - Put in DVD 1 that came with your MacBook Pro.
    - Shut down
    - Restart, holding the D key
    - You'll be put into test mode, run the default test (no need to run the robust test at this stage)
    I'm betting it will return a message that looks like: "4VDC/1/40000003: videocontroller"
    If so, your logic board will have to be replaced.
    The Apple Store I went to (Michigan Ave, Chicago) told me it would take 5-7 days. I'm not sure what UK times would be like, but I'd expect a little longer.
    bikemonkey wrote:
    Incidentally, people are saying that they've have logic boards and what not replaced only for the problem to reoccur. Does this mean nVidia haven't properly fixed the issue?
    Correct. Nvidia hasn't done a thing about this (that I'm aware of), and Apple seems to be putting the same logic boards with the faulty Nvidia chips back in.
    Until we see a new/refreshed line of MacBook Pro's, I think we're stuck.

  • Yet another dead mic with Win7 64-bit upgrd - Portege M700

    Title says it all.  Mics used to work fine on this machine under Windows XP. Under Win7, except as I note below, the mic has inaudibly low volume with any Control Panel Sound settings. I've spent huge amounts of time trying to solve this. After seeing all the similar posts (with no solutions, it seems) from users of many different Toshiba laptops, I'm about to start spreading the meme across the Internet that Toshiba laptops can't use mics.
    I started by upgrading to Win7 then adding just the 64-bit drivers I need from Toshiba's support site. No joy.  Then I started from a clean Win7 upgrade (64-bit Home) using Toshiba's upgrade script.  Nope.  Installed latest generic drivers from Realtek.  Hmm .. some progress, maybe: now with some Sound settings I can get slightly more volume but the mic input is drowned out by white noise-ish hissing.  All right, disable any other sound sources I can adjust: disable Chicony webcam driver from Device Manager. Hmm, now mike volume can get fairly high but the hissing still drowns it out.
    Toshiba: At some level, this is a problem between Microsoft and Realtek, I know. But you can help us.  MS changed the audio model significantly since Win XP, including (god knows why!) giving up the little audio mixer app that used to let you adjust levels for different sound sources.  And Realtek's generic driver doesn't provide one either.  So just give us a way to adjust levels for different audio inputs!  Maybe I haven't Googled sufficiently and some hacker out there has one, but I kinda doubt it ... if it requires driver-level access as I suspect, Microsoft's new DRM-motivated hammerlock limiting us to signed drivers prevents us from fixing this ourselves.  (It also means we can't access our ext3 partitions without extreme measures, but that's another rant.)  So CAN SOME TOSHIBA ENGINEER PLEASE LET MANAGEMENT KNOW THEY'RE ABOUT TO DESTROY THEIR LAPTOP FRANCHISE OVER AUDIO ISSUES?  Just cut, paste, and forward a couple dozen of these threads.  Sure, it's a career risk but (wo)man up to it!  Audio really matters to laptop buyers nowadays ... without Skype, I'll have do carry Yet Another Device when I'm traveling.  Heck, I've personally bought at least 6 Toshiba laptops over the years and I'm starting to shop for a replacement.  Anything but Toshiba, I'm sorry to say :-(
    Oh, in case somebody has an idea of something else I can try, the specific model is PPM70U-1KC01DB

    Title says it all.  Mics used to work fine on this machine under Windows XP. Under Win7, except as I note below, the mic has inaudibly low volume with any Control Panel Sound settings. I've spent huge amounts of time trying to solve this. After seeing all the similar posts (with no solutions, it seems) from users of many different Toshiba laptops, I'm about to start spreading the meme across the Internet that Toshiba laptops can't use mics.
    I started by upgrading to Win7 then adding just the 64-bit drivers I need from Toshiba's support site. No joy.  Then I started from a clean Win7 upgrade (64-bit Home) using Toshiba's upgrade script.  Nope.  Installed latest generic drivers from Realtek.  Hmm .. some progress, maybe: now with some Sound settings I can get slightly more volume but the mic input is drowned out by white noise-ish hissing.  All right, disable any other sound sources I can adjust: disable Chicony webcam driver from Device Manager. Hmm, now mike volume can get fairly high but the hissing still drowns it out.
    Toshiba: At some level, this is a problem between Microsoft and Realtek, I know. But you can help us.  MS changed the audio model significantly since Win XP, including (god knows why!) giving up the little audio mixer app that used to let you adjust levels for different sound sources.  And Realtek's generic driver doesn't provide one either.  So just give us a way to adjust levels for different audio inputs!  Maybe I haven't Googled sufficiently and some hacker out there has one, but I kinda doubt it ... if it requires driver-level access as I suspect, Microsoft's new DRM-motivated hammerlock limiting us to signed drivers prevents us from fixing this ourselves.  (It also means we can't access our ext3 partitions without extreme measures, but that's another rant.)  So CAN SOME TOSHIBA ENGINEER PLEASE LET MANAGEMENT KNOW THEY'RE ABOUT TO DESTROY THEIR LAPTOP FRANCHISE OVER AUDIO ISSUES?  Just cut, paste, and forward a couple dozen of these threads.  Sure, it's a career risk but (wo)man up to it!  Audio really matters to laptop buyers nowadays ... without Skype, I'll have do carry Yet Another Device when I'm traveling.  Heck, I've personally bought at least 6 Toshiba laptops over the years and I'm starting to shop for a replacement.  Anything but Toshiba, I'm sorry to say :-(
    Oh, in case somebody has an idea of something else I can try, the specific model is PPM70U-1KC01DB

  • Yet another major gripe with APE - restricting connection to home network

    Yet another serious issue I have with APE is the fact that since very often, the computer just can't see the base station (even when it is located 30 inches from it...) it will just automatically connect to the next available open wifi network, which happens to be my neighbor's... that way I often finding myself surfing someone's else's unsecured network and it's ******* me off.
    I tried to delete all wireless networks from system preferences/network/Airport but this does not makes a difference. Any idea on how to restrict my computer to the APE or at least have Mac OS warn me every time before it connects to an unsecured wireless network?
    Thanks.

    Somewhat easy: I'm assuming you're using Leopard, mainly because I ran through the options from leopard. Other versions of OS X may have slightly different placement or names...
    Click on the airport icon in the menu bar.
    Choose "Open Network Preferences"
    Select "Airport"
    There's a checkbox labeled "Ask to join new networks" Make sure it is enabled.
    Select "advanced..." (it's a button, lower right)
    You can change the connection order by dragging your network to the top of the list.
    You can also click on a connection you don't want, then click on the '-' button below it to remove that connection. (and at least the first time, the computer will ask you if you want to connect)
    You can go a step futher, by de-selecting the checkbox labeled "Remember any network this computer has joined" That way it won't add anything to your list of 'remembered' networks.
    Message was edited by: pariah0

  • Yet another export issue with Aperture 3

    Judging by a search of topics, there seem to be a myriad of problems associated with getting files out of Aperture, some of which represent occult setting issues, others which seem to be actual bugs.  I've run into an issue which seems to defy categorization, and I'm not sure if it's me doing something wrong, or if it is actually yet another bug with this software.  I've been an Aperture user since 1.0 and I have to say the current version I'm running (3.4.3) is by far the worst yet.  Anyway, enough whining.  Here are the issues:
    I'm running Aperture on a 6 core Mac Pro with Lion 10.7.5.  There are two thing happening. 
    1.  Exporting JPEGs is INCREDIBLY slow - perhaps as long as 4 or 5 minutes for a 3MB file. 
    2.  This is the one driving me batty right now.  Tried exporting a batch of images as JPEGs at the 50% original size setting.  The master files are large 16 bit TIFF images from Nikon D800 RAW files, post-processed in Nik HDR Efex Pro 2.  They are 80-100MB in size.  When I export the images to a file on my Desktop, it consistently exports 6- 10 KB thumbnails.  I've checked and rechecked my export settings and can find nothing amiss there.  Has anyone else had a similar experience?  Could the view I'm working in have anything to do with this?  I work 95% of the time in split view.
    Thanks,
    Russ

    I agree that there re a lot of posts about exporting, but a very large number of them refer to the same thing, and it's not a bug, but rather a misunderstanding.
    For instance:
    Tried exporting a batch of images as JPEGs at the 50% original size setting.
    Okay.
    The master files are large 16 bit TIFF images from Nikon D800 RAW files, post-processed in Nik HDR Efex Pro 2
    Not relevant.
    They are 80-100MB in size. 
    Not relevant either.
    Why?
    Because size refers to the dimensions of the image. So a 1,000 x 1,000 pixel image exported at 50% will turn out as 500 x 500 pixels.
    Were you expecting a jpeg between 40 and 50 MB? That's Jpeg quality or the amount of compression applied to the image. And as you're compressing a lossless format (tiff) to a lossy one, and one with an aggressive compression algorithm, he resulting Jpeg, even at high quality, will be much, much smaller, more likely in the 6 - 8 MB range.
    That's the nature - and indeed the point - of Jpegs.
    So, if you're getting 6 - 10 kb images, you're exporting at a very low Jepg Quality.
    This may also explain why it's taking so long to export. Getting rid on 99.99% of the data and compressing into 10kb is always going to take time.

  • [SOLVED] No sound on SPDIF with Intel ICH10 Sound Card

    Hi everyone,
    I'm coming from Fedora 12 and recently got a fresh installed Archlinux. I'm very satisfied by the distribution and everything works just as expect for the moment, except one thing : SPDIF output of my sound card.
    I installed the following packages :
    $ pacman -Qs alsa
    local/alsa-firmware 1.0.20-2
    ALSA firmware package
    local/alsa-lib 1.0.22-1
    An alternative implementation of Linux sound support
    local/alsa-plugins 1.0.22-1
    Extra alsa plugins
    local/alsa-utils 1.0.22-2
    An alternative implementation of Linux sound support
    My actual configuration in a few commands :
    $ aplay -L
    null
    Discard all samples (playback) or generate zero samples (capture)
    default:CARD=Intel
    HDA Intel, STAC92xx Analog
    Default Audio Device
    front:CARD=Intel,DEV=0
    HDA Intel, STAC92xx Analog
    Front speakers
    surround40:CARD=Intel,DEV=0
    HDA Intel, STAC92xx Analog
    4.0 Surround output to Front and Rear speakers
    surround41:CARD=Intel,DEV=0
    HDA Intel, STAC92xx Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
    surround50:CARD=Intel,DEV=0
    HDA Intel, STAC92xx Analog
    5.0 Surround output to Front, Center and Rear speakers
    surround51:CARD=Intel,DEV=0
    HDA Intel, STAC92xx Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
    surround71:CARD=Intel,DEV=0
    HDA Intel, STAC92xx Analog
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
    iec958:CARD=Intel,DEV=0
    HDA Intel, STAC92xx Digital
    IEC958 (S/PDIF) Digital Audio Output
    hdmi:CARD=Intel,DEV=0
    HDA Intel, INTEL HDMI 0
    HDMI Audio Output
    $ aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    card 0: Intel [HDA Intel], device 3: INTEL HDMI 0 [INTEL HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
    The following command :
    $ aplay -D front:CARD=Intel,DEV=0 tmp/Norrlanda.wav
    gives me sound on the analog (HP) output but this one :
    $ aplay -D iec958:CARD=Intel,DEV=0 tmp/Norrlanda.wav
    gives absolutly nothing (I tested the HDMI output and it's fully functionnal).
    I unmuted everything that could be unmuted on alsamixer and tested varied combo of options snd_hda_intel model=XXXX (as I read that those type of card can have issue of this kind). I try to delete the /etc/asound.state file, various configuration in /etc/asound.conf. But nothing.
    In last resort, I rebooted on a F12 LiveCD and there… everything works fine ! The SPDIF output works just great, without any manipulation (with the same command as above). I tried to import the configuration of /etc/alsa, /etc/pulse and /etc/modprobe.d from this F12 LiveCD (looking if there was any special options about sound card I can just copy/paste to Archlinux) but this failed one more time.
    I really really don't see what I can do to solve this problem (and I already spend 2 entire days on this issue without any result… frustrating). So if someone's got a solution or suggestion (some configurations I can try) on this issue, any help would be greatly appreciated.
    Last edited by DojoMortal (2010-05-01 21:31:41)

    Thx to jonnor on the IRC Archlinux Channel, it works now !!
    For everyone experiencing the same problem with DG45 intel sound card (Codec: IDT 92HD73E1X5 to be accurate), the documented module is not the right one. Use model=no-jd if you want to have the SPDIF output functionnal.

  • [SOLVED] Yet another time issue...

    Hi there,
    I'm having some crazy, hair pulling, head banging UTC time issues on both my dual boot (Arch & Windows 8) desktop and single boot laptop.
    I've been searching and following a mulitude of old threads and the official Wiki guide, however, I simply cannot get UTC time to stay correct between reboots. I've installed Arch a fair few times now, both before and after the switch to systemd and in dual and single boot setups and have never had time related issues like this before...
    Here's a run down of the whole sorry story....
    Fresh install - set time with hwclock --systohw utc as suggested in the beginners guide.
    First boot - time an hour out - huh? cat /etc/adjtime and ls -l /etc/localtime - everything as it should be... UTC and symlink to /usr/share/zoneinfo/Europe/London. Nonetheless I duly follow the Time guide on the wiki, get to know timedatectl a bit, and soon after, time is set to be correct. Great.
    Reboot. Time an hour out. Whaaaa??. Start googling, finding a plethora of bbs links to others with similar issues, decide to use NTP. Install, ntpd -qg. All good again. Time right. Phew...
    Reboot. Nope. Arrrrgggghhhh. (Bare in mind - at this point I haven't even booted the Windows 8 disc, and I went through the exact same process on my Arch only laptop...)
    More googling, thread reading. Find out that hwclock and ntp might be in conflict. Delete /etc/adjtime, reinstall tzdata, re-follow Time article to the letter and reenable NTP to start at boot.
    Reboot - time is foward an hour yet again. Bang head repeatedly on desk. Then suddenly - 10 mins or so after boot - NTP kicks in, and time is magically goes back an hour to the correct time! Surely NTP should be doing this early in the boot process, not 10 minutes after? But OK, at least something is happening...
    Next I dare to boot into Windows, and yup, time an hour out. Expected, but frustrating nonetheless. Add the registry tweak as suggested in the guide, and turn off the Windows time synchronisation. During which I noticed that Windows 8 time is set to UTC by default, not localtime, which is what the wiki says. Is this a Windows 8 thing?
    I can't help thinking, that if this is the case, and the Wiki advise is written under the assumption that Windows time is always localtime, that perhaps this is the route of my problem....
    Anyway, Windows time all good now, reboot Arch, time again wrong untill NTP finally kicks in - sigh. Reboot to Windows. Time an hour back. Gaaaahhhh - WTF?!! reset it to be correct. Try again. Same thing. Oops, forgot to mention that on each reboot, I check the BIOS clock, which remains persistently correct during the whole debarkle...
    Ok, so I try without the registry hack and turn Windows sync back on. Still fucked. I try various combinations of the two, I try resetting Arch time over and over again. With NTP - late sync. With hwclock only, or both hwclock & NTP - totally fucked! Eventually, I give up on UTC in Arch, set it localtime, delete registry key, turn Windows time sync back on, and thus far all good......
    TL;DR - couldn't get hwclock to set UTC time correctly across reboots. NTP worked (sort of), but after each reboot it would take ten minutes for the time to sync and the clock to move back an hour to the correct time. Localtime just works...
    My question is - why is the wiki (and the timedatectl status output for that matter) - so adamant that we should use UTC? From what I can gather, as long as I boot Windows around the DST time. or manually move the clock forward or back an hour - all should be well, no? Or are there other issues that I may run into that I've missed? The thing I'm most concerned about is data corruption due to timestamp issues...
    Also, why does the wiki repeatedly say that Windows uses localtime, when this doesn't appear to be the case in Eight? Does the wiki need updating or is Windows lying to me? I know which I'd put my money on ;-)
    Finally can anyone explain why my time was always an hour forward after a reboot, even when the time was set correctly before, the BIOS showed the correct time, and NTP was in use?
    Sorry for the crazy long posting, but this issue has been driving me totally batty!! Any light-shedding greatfully appreciated :-)
    Last edited by knowayhack (2013-08-10 15:24:09)

    Ok, so I set the clock back an hour in the BIOS, booted Windows - time right - YAY.
    Rebooted Arch - time right. OMFG - pure joy!!!
    I have to say, I still find it odd that this is how it works, and would like to confirm that things are looking as they should in the output from the following commands....
    toby@archy ~ > timedatectl status
          Local time: Sat 2013-08-10 15:42:56 BST
      Universal time: Sat 2013-08-10 14:42:56 UTC
            Timezone: Europe/London (BST, +0100)
         NTP enabled: n/a
    NTP synchronized: no
    RTC in local TZ: no
          DST active: yes
    Last DST change: DST began at
                      Sun 2013-03-31 00:59:59 GMT
                      Sun 2013-03-31 02:00:00 BST
    Next DST change: DST ends (the clock jumps one hour backwards) at
                      Sun 2013-10-27 01:59:59 BST
                      Sun 2013-10-27 01:00:00 GMT
    toby@archy ~ > sudo hwclock --debug
    sudo: timestamp too far in the future: Aug 10 16:39:24 2013
    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
        #1) Respect the privacy of others.
        #2) Think before you type.
        #3) With great power comes great responsibility.
    [sudo] password for toby:
    hwclock from util-linux 2.23.2
    Using /dev interface to clock.
    Last drift adjustment done at 1376148264 seconds after 1969
    Last calibration done at 1376148264 seconds after 1969
    Hardware clock is on UTC time
    Assuming hardware clock is kept in UTC time.
    Waiting for clock tick...
    ...got clock tick
    Time read from Hardware Clock: 2013/08/10 14:43:20
    Hw clock time : 2013/08/10 14:43:20 = 1376145800 seconds since 1969
    Sat 10 Aug 2013 15:43:20 BST  -0.953640 seconds
    Is it OK to now reinstall NTP to keep the clock in sync on Arch, and are the Windows reg tweaks still necessary on Windows 8?
    Thank you guys SOOO much for all the unbelievabley speedy help on this issue - you have no idea how much this has been stressing me out!!
    Last edited by knowayhack (2013-08-10 14:54:31)

  • No sound with Intel HD audio [solved]

    Hi,
    I recently set up my laptop with archlinux, and I'm getting no sound. I have the drivers for my chip installed, there is nothing unusual in dmesg, and alsamixer detects the card fine, but even after I unmute the card, I get nothing. when I start up kde, I get this message:
    Sound server informational message:
    Error while initializing the sound driver:
    device /dev/dsp can't be opened (No such file or directory)
    The sound server will continue, using the null output device.
    It may be as simple as making /dev/dsp a symbolic link to the correct device, but I'm not sure which device that would be.
    alsamixer tells me:
    Card: HDA Intel
    Chip:SigmaTel STAC9221 A1
    Thanks in advance.
    Last edited by Zerathidune (2007-03-10 03:35:45)

    do you belong to the audio group?
    as root
    "gpasswd -a USER audio"
    as user at konsole type
    "alsamixer"
    anything come up ?
    awhile back i had an issue with line jack sense i forget weather on/off

  • [Solved]Yet Another HAL / Mounting issue....

    My issue can be avoided by manually mounting a device, just to get that out there.
    Whenever I transfer a larger file ( > 200mb) onto a removable USB device formated in either FAT or any non-journaled filesystem, Thunar will *pretend* like its unmounting the device but after about 20 seconds it states:
    Failed to unmount "<device name>".
    Did not receive a reply. Possible causes include: the remote application did not send a reply,
    the message bus security policy blocked the reply, the reply timeout expired,
    or the network connection was broken.
    On top of the message, my data written is mostly corrupt.
    What I know:
    ** Thunar uses exo-unmount to unmount devices given a HAL uuid. Maybe this is failing? Any clue how to debug this?
    ** 20-storage-methods.fdi states that all vfat mounted devices have 'flush' and 'async' mount options... could this be an issue?
    ** I'm part of the 'storage' and 'power' groups.
    ** i start XFCE using ck-launch-session startxfce4
    I've made sure that the device has no other handles and is not open in any window. My system(s) all have new and updated HAL and DBUS, as well as every other package. Running 'sync' after writing the files sometimes fixes the issue. Does anyone have a fix for why removable drives aren't "sending a reply" ? Thanks!
    --Anthony
    Last edited by anthonyclark (2010-09-22 17:48:13)

    Alright ... well. I managed to solve this kind of. As per my last post regarding the same exact issue, I must've missed a reply from Inxsible telling me to use the FIRST suggest UDEV rule from the arch udev wiki.
    The result of this is basically...
    *Device inserted
    *Mounted in /media/<device name> automatically
    *(No access via Thunar sidepane since it gets mounted with `mount`)
    *No need to manually unmount
    *just unplug or power off the device and it gets "lazy" unmounted via `unmount`
    Downside:
    *Mounting a drive via TrueCrypt creates a directory in /media that doesn't get automatically deleted.
    *Not a solution to Thunar having response issues with unmounting.
    /etc/udev/rules.d/11-media-by-label-auto-mount.rules
    KERNEL!="sd[a-z][0-9]", GOTO="media_by_label_auto_mount_end"
    # Import FS infos
    IMPORT{program}="/sbin/blkid -o udev -p %N"
    # Get a label if present, otherwise specify one
    ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
    ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
    # Global mount options
    ACTION=="add", ENV{mount_options}="relatime"
    # Filesystem-specific mount options
    ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},utf8,gid=100,umask=002"
    # Mount the device
    ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}", RUN+="/bin/mount -o $env{mount_options} /dev/%k /media/%E{dir_name}"
    # Clean up after removal
    ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/umount -l /media/%E{dir_name}", RUN+="/bin/rmdir /media/%E{dir_name}"
    # Exit
    LABEL="media_by_label_auto_mount_end"
    Last edited by anthonyclark (2010-09-22 03:50:00)

  • [solved]Yet Another "X won't start" thread

    I get the black screen when i try to startx. i followed the wiki entry to set up X, but it doesn't work. Now, what i want to know is, how do i go back on a fresh install to an older version of X, that *doesn't* use HAL?
    Last edited by GypsyJoker (2009-11-28 01:05:05)

    It happened to me too. I use LXDE and everything was fine until last X.org update (prior to today's) when the blank screen started happening after every restart. I discovered that if I edit /etc/xdg/lxsessions/LXDE/autostart file as root and close it, even without changing anything, not resaving the file, not doing anything to it, then I was able to enter to X with startx as always. Weird, isn't it?
    Afortunately, today I've updated my x.org server and seems everything is fine again.
    Last edited by david.ptm56 (2009-11-21 18:33:22)

  • Yet another BtBroadband user with slow connection....

    Hi all.
     I've been having this problem for over a month now. Just before xmas our internet connection went down.
    I phoned Bt, went through all the usual tests to be told there was nothing wrong with them and it was my equipment. Ok, no problem, I went out and bought a new router, got it home, plugged it in, still no internet.
     Phoned Bt again, spoke to different person at callcenter, went through all the usual tests to be told that, yes, there was a problem with the line and to give it a few days for them to sort out. I gave it a few days and, amazing, the internet came back on. Problem was it was very slow. Ok, I thought, new modem, fixed connection, maybe I need to give it a few days to speed up. It's been a month now and it's gotten slower. So slow infact that when I ran the Bt Speedtester it said that my download speed was 59kps. This was the same speed I was getting back in '97 with my old dial-up modem (ah the memories...).
    Anyway, called Bt again, explained all the above and was directed to thier online guide for improving the connection speeds, not very helpfull. Prior to the line problems in december, I was getting speeds up 21000kps. The line was rated for speeds between 4000-21000kps. My property is less than a 1km from the exchange, my router is connected to the main socket and I didn't have any problems prior to the line problems last year.
    I have been searching through the previous posts on this forum and can see many other people with similar issues. One post stated that, because of thier line problems Bt had downgraded thier bandwith while the problem was dealt with, but had forgotten to increase it back to normal speed once it had been sorted.
     This could be the issue with my connection and if any of the moderators are out there, could this be looked into, it would be deeply appreciated.
    My Btspeedtester results and modem stats are as follows:
     Download speedachieved during the test was - 59 Kbps
     For your connection, the acceptable range of speedsis 100-250 Kbps.
     Additional Information:
     Your DSL Connection Rate :286 Kbps(DOWN-STREAM), 888 Kbps(UP-STREAM)
     IP Profile for your line is - 135 Kbps
    The throughput of Best Efforts (BE) classes achieved during the test is - 0.64:11.33:89.14 (SBE:NBEBE)
    These figures represent the ratio while sententiously passing Sub BE, Normal BE and Priority BE marked traffic.
    Upload speed achieved during the test was - 728 Kbps
     Additional Information:
     Upstream Rate IP profile on your line is - 888 Kbps
    Router:
    Type     Interleave Path             
       Status     SHOWTIME             
    Downstream     Upstream
          Data rate(Kbps)     
    286Kb     888Kb
       Noise Margin     
    21     14
       Output power(dBm)     
    0     257
       Attenuation(dB)     
    21     7
    I hope someone can help. Thanks in advance.

    "If line instability is shown to stabilise normally the exchange equipment will remove the banding however on some occasions it does not release,and bt can release it manually but they like to see hub stats that show that during the line has been stable for a minimum of 5days but 10 is prefered" I'm not sure whose brainwashed you with this stuff, however. FaCT: BT retail complain to BTw about stuck banded profiles, and yes they can reset the INP, but if the line characteristics don't improve, it goes back to where it was. They also operate to strict protocol, and don't put lightweight preference on whether its seen a fixed rate at 5 days or 10. Truth is if the line is seeing high noise margin and not improving, it has a problem, and often can't be fixed, or take advantage of 21CN. Or sometimes it can be fixed, by the customer, if they choose to, or are capable of. It's not in BT's remit to fix home induced noise, but it is for the line, if its possible. They (BTw) can change any workiing parameter they see fit on DLM, but the main reason for it, is to run in AUTO. In other words, they don't do it for all and sundry, or at the drop of a hat, without good reason. Hence, they don't set "preference" for seeing stable connections. They tend to let the physics do its job.
    Click the star if my posts have helped.

  • Yet Another Popping Issue with Xtremegamer Fatal1ty

    When I start or stop a song/sound, 90% of the time, I either get a popping sound or something that sounds like it's playing a fraction of a second worth of a song at a higher volume than the songs are playing at. Maybe it's just some sort of interference rather than that fraction of a song, who knows. Sometimes there's a pop or crackle somewhere in a song but it might just be the track.
    I don't know what the hell to do. I've tried everything: reseating the card in both of my free PCI slots, reinstalling drivers, updating BIOS. I know it's getting a little old hearing people bash Creative all the time but these guys really need to get their act together. I can't believe they would let this crap fly.
    Message Edited by genzeleam on 0-29-2008 0:56 AM

    Any suggestions?

  • Yet another strange issue with Mailbox

    Hi everybody,
    I updated my MacBook Pro to Mavericks 10.9.1 a week ago, and a very annoying and scary issue appeared on my computer (I had been using 10.9.0 before, and hadn't been facing any issues).
    After the initial update, my Inboxes (I use Gmail) have become completely blank, empty, while in the web interface they appear absolutely ok (hundreds of mails there). It's also all good on my iPhone.
    All the new mails I receive are being shown in the Inboxes, but not the ones that were there before the update.
    Moreover, some folders also appear empty (you can take a look here http://d.pr/i/CDjn) while they have hundreds of mails inside.
    What should I do?
    Thanks a lot for your kind help!

    Okay, so I removed it and set it up again, but it went back very quickly and everything is the same - seems like the mail info "sits" somewhere on the hard drive, so it's not being set up again from the very scratch.
    How to set it up from scratch?

  • Intel HD Audio Jack Detection

    I have recently got a new computer case with Intel HD Audio so I can plug my headphones in, and not have the sound playing in the back, but I'm having a issue with ALSA cancelling the back audio, not sure if there is a easy fix or not...
    Motherboard model is a GIGABYTE EP45T-UD3LR... Intel P45 chipset. Audio Card is a Realtek ALC888 Chipset
    All the fixes I have looked at have seemed like to me like they are specific to a laptop, not a general fix.
    It's not really that big of a issue if it doesn't work, but it would be nice if I can get it to work.
    Any suggestions?
    Last edited by themattbeballin (2010-12-26 06:10:05)

    I have to agree but I doubt most people notice. Not a lot a audiophiles anymore. Intel HD specs are typical of a low costs digital to analog converter. You won't find many laptops that spend a lot on sound quality. Although their are a couple PC's that have certified sound with better sound cards. I would think your Macbook like mine has a optical digital connection through the audio jack. If you really want better D/A conversion you could buy a external D/A converter and connect through the optical output. Personally I use a pair of SkullCandy Hesh 2's and find the sound very good. I certainly have heard worse. At least S/N ratio is pretty good. Some laptops I have had in the past really had some nasty background hiss.

  • Excise Invoice is captured with another Po  -During MIGO- Only refer Excise

    Hi,
    I have did a PO with two line item say Material M1 and M2..
    step1-  We did J1IEX with capture excise invoice option for material M1 and M2.
    step 2-  We did GR for material M1 only where i have selected my excise tab as Only refer Excise
    step 3-  Now we are trying to do GR for 2nd line item material M2, where we getting error msge as
    *Excise Invoice is captured with another Purchase Order
    Message no. 4F278*
    I have searched in forum and found related info in the belw links
    CIN related error at the time of GRN
    GR for Import PO,
    where experts are suggesting to apply a note 843490 &994052. seems these notes for older version.. my client version is ECC 6.03
    Please let me know if any note available or any other methods to solve my issue (we don't want to put the excise invoice with suffix of * or /1).
    regards
    Jay
    Edited by: Jayakumar Raju A.S on Sep 6, 2010 11:28 AM

    Hi,
    System takes only single excise invoice in system.
    here i suggest wat u can do ( very tricky)
    for first goods receipt excise invoice is 123
    then u cant give same for other GR it will give an error at this time u can provide excise invoice as (123.).
    Means one dot at beginnig or at the end.
    Note : Hence forth for same excise invoice u should have only one GR.

Maybe you are looking for