Speaker pop during PowerBook boot

Ever since installing Leopard, my PowerBook makes a rather loud pop noise from the internal speakers. It always happens during the boot process, at the point where the gray screen with the spinning gear changes to the blue screen. At that point, one of my speakers makes a single loud pop. It is usually the right speaker, but it has happened from the left once or twice. I don't have any external speakers connected. Anyone else seeing this?

I also have one of the new iMacs - one of the 20" models. I started having the same problem just a couple minutes ago. It worked without any problems for a solid week and a half, and now this? Puts a damper on the track I was working on in Logic. It just popped 3-4 times and then no sound eventhough my song was still playing and the volume meters on the mixer for each track were showing movement. Tried playing some songs in my iTunes library and still no sound - speaker output meter is at the halfway mark. My first thought was hardware issue, but who knows.

Similar Messages

  • There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?

    There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?

    Nah - that's just the normal boot process.
    Clinton

  • Kernel Panics during system boot, and no kind of network connectivity

    I've tried quite a lot of things here, so please read them all before you suggest something - and thanks for taking a look at my question (-:
    I recently got my Mac Pro back from the AlaskaMacStore (not an actual apple retail store, and they aren't very good at that), having brought it in for loss of FW800. They sent it to Apple, and I received it back, supposedly with a new motherboard - and my FW800 working. However, it proceeded to kernel panic (complete visual system freeze, not greyscreenofdeath - oddly enough, iTunes would never stop playing during them) at least once a day after that.
    Not wanting to deal with them again, I just used it like that and put up with it - but soon enough, I lost any sort of network connectivity as well. With AirPort connected to my Time Capsule's network (which worked fine on my Macbook Air and iPhone and various other devices), I was being told "...Self-Assigned IP address, and thus may not be able to connect to the internet...". Even connected directly via Ethernet to the Time Capsule, or directly via Ethernet to the cable modem, or directly via Ethernet to another Mac, or connected to another Mac's ad-hoc network, I could get absolutely no network communication going on of any sort.
    This was too much for me, as all of my work requires frequent and heavy internet access, so I gave in and took it back to the local mac store equivalent - they charged me 100$, and kept it two days, just to tell me they 'couldn't reproduce the problem'. I took the Mac Pro to a friend's house, and went through the same tests - connected to his modem, with his Ethernet cords, and to his wireless and other macs. Same deal, no connection or indication of a networking being connected beyond that blasted 'self-assigned IP' in Network prefs.
    Having no desire to be defrauded by the local fools again, I decided I didn't really have anything important on my internal hard drive, and decided to wipe the internals and re-install Leopard. My horrible luck continuing, I found my only Leopard disc to be cracked, prompting me to drive out and purchase a new one. Inserting this into my Mac Pro's drive, I found myself faced with yet another horrible problem.
    During the boot to the Leopard DVD, the grey loading screen (with the apple logo and the spinner) simply froze with the spinner pointing left. I left it for a while, expecting this to be part of what I'd previously experienced with the slow boot-from-DVD on a Macintosh... but after 30 minutes of waiting, I got quite worried, and booted back into my normal OS by holding down Option and selecting my RAID.
    Now, note this for later - it booted absolutely fine, and though I still had no network connectivity, the system had no problems. I changed the startup-disk to my RAID and then back to the Leopard DVD, naïvely thinking this would solve the problem, and ran into the same problem after restarting and booting to the Leopard DVD again.
    Dismissing this as a optical drive problem (haven't had occasion to use optical media in nearly 3 years, don't really trust it in general), I booted the Mac Pro into Firewire Target Disk mode, and connected it to my Macbook Pro, and then booted the Macbook Pro from the installation DVD. Again, note carefully here - there was nothing wrong with the DVD itself, as the Macbook Pro had no trouble booting to the DVD.
    I used Disk Utility to preform some planned modifications to the internal drives of my Mac Pro (erasing my previous inefficient RAID setup in favor of a new, faster (but less secure) RAID0 striped setup for my main two 1TB drives), and then proceeded to install a fresh Leopard onto the newly minted RAID. I usually cancel the 'disc checksum' that the Leopard DVD runs on itself, not really worrying about it, but in light of recent possible problems with the DVD, I went ahead and let it run - no problems, it completed and went straight into the normal install.
    The install itself completed in a timely manner, and my Macbook Pro re-booted automatically, to the newly Leopard-ed RAIDed internals on the Mac Pro. It booted to the new install without a hitch, played the Leopard intro video, and continued to the setup cube. I opted to shut down (by hitting command-q and selecting the shut down option), so I could set it up on the Mac Pro instead.
    Surprised was I, when I experienced the same grey loading screen freeze on the Mac Pro, booting to the newly clean install on the new RAID, that I had seen trying to boot to the Leopard disc. Worrying that my Leopard disc was, infact, corrupted in some way, I tried placing the Macbook Pro into firewire Target Disc Mode, and booting that drive over FW800 on the Mac Pro. Same freezing problem occurred.
    Well, now, the only installation that HADN'T kernel panicked on boot was the old install, and that had been erased for the new RAID configuration, so I was left without a way to boot to a working install and test things from the Term. This left me with Single User Mode, which I immediately booted into.
    Interestingly enough, there was no problem booting into Single User Mode - so I poked around a bit before mounting, and I had seemingly fine access to the entire filesystem of the new Leopard install, and nothing looked screwed up to my (albiet untrained) eye. After mounting and continuing the boot, it froze - but since this was verbose SUM, and not simple normal boot, I was able to see exactly where it froze: something about 'mDNSResponder starting', and then no input or output was accepted, leaving me assuming it had kernel panicked again.
    To test this, I again attempted to boot from the Leopard DVD on the Mac Pro, this time in verbose startup mode, and watched it freeze up at exactly the same point. After a little googling, I found some suggestions to disable the launchd plist for mDNSResponder - I tried SUM again, and did so, then continued with the boot. This time, there was no output relating to mDNSResponder, so the launchd change had worked; however, it still froze - this time, right after three lines, first something along the lines of 'Login Window Application Starting', and then two lines printing Ethernet IDs of some sort. After those Ethernet related lines, it again froze.
    What with the DNS and Ethernet bits showing up in the freezing, I was getting worried this was still tied into my NIC in some way, so I unplugged my Ethernet cords and tried the exact same boot again, and again disabled mDNSResponder. This time the only sensible thing before the freeze was the 'Login Window Application Starting' line, which seemed perfectly normal. I doubt there is/was anything wrong with that, so I'm assuming there's still some networking-related process freezing/panicking the computer, and it just doesn't happen to log in a visible way during startup.
    Does anybody have any suggestion as to what such a process might be, and how I can at least pause or kill it from SUM, so I can at least finish booting the computer?
    If I can't figure out a solution to this, I'll have to buy a new Mac Pro tomorrow morning... I have very, very pressing matters that can't wait for a new Mac Pro to ship, nor can they wait for me to ship this one to Apple and back (I live in Alaska, we have at least a weeks wait if nothing is seriously wrong when sending an Apple product in for repairs on our own), and nor can I wait 2 days for the local Apple store to tell me there's nothing wrong with it and then have to wait another week to, again, send it to Apple myself. I don't want to have to shell out for a new, expensive computer when there's a (most likely) perfectly good one sitting here... so any help would be MUCH appreciated.
    If you've read this far, phew, you deserve a cookie. That was one... long... post.
    (If you care, this post was cross-posted to my blog, at http://blog.elliottcable.name/posts/macpro_epicfail.xhtml)

    Talk about bad luck.
    The point at which the system "freezes" with the gray spinner (and just after the login window app starts) is right about the point the accelerated drivers should kick in for the video card.
    So a couple things could be going on.
    1) bad video card dragging down the bus
    2) The system board is fubar - this I think is likely - issues with onboard ethernet, and whats seems to be video card related.
    I would hazard to guess that the PCI-express bus has something wrong with it, ethernet and video live on the bus, SATA, and USB live in the southbridge.
    So, looks like a trip to a certified apple dealer/repair center is next for your Mac Pro - probably for a new system board, again?
    Something tells me that your system really didn't get to Apple for a new board.
    You can verify by looking at the serial ID tag on the system board, note the rev and serial # before and after such repairs.

  • Problem with udev during the boot

    Hi guys,
    Sorry if I didn't post this message in the good section but I didn't find any support section, so I supposed that this section was the most apropriate.
    So, I have a really ennoying problem with udevd since the latest kernel upgrade (3.2.2-1) during the boot.
    I have the following error at the boot:
    "udevd[37]: No such file or directory." and then the OS is unable to mount the disks and give me the weakest shell ever while saying me "You're on your own". Thank you Arch!
    I can't find any informations on google about this error, and I d'ont find a complete explanation of udev debug (specialy because no logs are written at this moment).
    Thank you very much guys.

    GreenTime wrote:
    qaws or someone else:
    Could you elaborate on how to just reinstall the kernel? Somehow I'm stuck
    Usually, you'll need a live CD (I recommend an ArchLinux Installation CD) or an LTS kernel sitting around on the same machine that can get you more or less into your favored machine.  It can also be done, by pxe/diskless booting from an installation (I'm a fan of quick and efficient)!  Then you have to mount all the necessary partitions /, /usr (sometimes /var if you need your packages) and most importantly /boot.  They have to be mounted underneath the rescue system being used , usually under /mnt.  Also needed is a mock-up of your /proc. /sys and /dev.  Once they are mounted accordingly, then you chroot into your installation you need to fix.  It helps if the rescue system has the same kernel, because the chroot'ed system usually tries to build your kernel based on the rescue system, but if you have your kernel package handy, it will build it with the packages modules & kernel.

  • How to disable loud speaker beep during install

    Is there a way to disable the the speaker beeping during install? Or at least lower its volume? Its extremely loud. Ive already removed the pcspkr module, but the beeping is still present.
    (I reinstall arch often and this is why I'm asking )

    echo "options snd-pcsp index=2" >> /etc/modprobe.d/modprobe.conf

  • Accessing the "speaker phone" during a call.

    Once I am in a call, how do I activate the speaker phone? While on the call, the "keypad" shows, but there seems to be no way to turn on the speaker phone. The only time I can put my call on the speaker is before I connect with the party I am calling. Many a time in the past few days, especially while "on hold" it would have been easier to lay the phone down and turn the speaker on. I can't do that once in the call.

    Phil:
    You show two screens. Let's call them the "black" screen and the "white" screen.
    When I go into "contacts" and I select a person I want to call in my contact list, and I use the little phone icon in the contact list to initiate the call, then the black screen shows up and stays active, and I can go to "speaker phone" by touching the speaker icon during the call if I want.
    However, if I make a call for a person or business I want to call, using the phone number I found on their business card or their website, (they are not in my contact list) and I use the large green phone icon of the phone app to start the call, I get the white screen, and then,if I want to switch to the speaker phone, I can't get there. There seems to be no way to get back to the black screens once a phone call is started.
    Also, thank you all others for responding to my issue.

  • I have a PowerBook 145B but something is wrong with the systemfolder so it wont boot. I've downloaded System 7.0.1 from Apple and put it on Floppys with my Macintosh Classic. The PowerBook boots from the floppy, after a minute its just white. What to do?

    I have a PowerBook 145B but something is wrong with the systemfolder so it wont boot. I've downloaded System 7.0.1 from Apple and put it on Floppys with my Macintosh Classic. The PowerBook boots from the floppy but after a minute it just comes up a window thats completely white.
    I've tried a lot of things, but my Macintosh classic (with original floppys) runs 7.0.0. And the PowerBook needs atleast 7.0.1 and did run 7.1.0 as original OS.
    How do I fix this?

    Because your PowerBook 145B shipped with OS 7.1, it can't run an earlier version of the Mac OS, such as 7.0.1.  Unfortunately, Apple never made OS 7.1 available for download.  You can run OS 7.5.1, 7.5.3, and 7.5.5 on your PowerBook, but I'd recommend doing so with the maximum amount of supported memory - 8 MBs.  The 19-part download of OS 7.5.3 is segmented, so that each one will fit on a 1.44 MB floppy disk.  The problem is that the 19-diskette set isn't an installer set as such, having no bootable disk.  It's solely intended to be used to transfer the individual segments to the resident hard drive in the computer.  Once that's done, double-clicking the first .smi segment creates the OS 7.5.3 installer disk image on the desktop, which you drag onto the hard drive icon.  This produces a folder with the OS 7.5.3 installer in it.  I've done this before with an old Mac LC and it works.  You can also download the 3-diskette OS 7.5.5 Update and run that.  These downloads can be found on the same page where you found the OS 7.0.1 download: Older Software Downloads.

  • Music volume slider shows "speaker" setting during "earphone" playback

    A volume setting is stored for playback through the iPhone's speaker, and another for when earphones are plugged in.
    I have noticed since updating to iOS 5.1 that the volume slider in the Music app sometimes displays the "speaker" level during "earphone" playback when switching between the two modes.
    Although the slider displays the incorrect volume level, the playback is at the earphone setting's volume, not the displayed volume.
    N.B. I have an iPhone 3GS, and the performance of the Music app has degraded with each iOS update; this seems to be due to the core software growing more complex. It is possible that there is just a very long delay between loading the Music app, it recognising the earphones are plugged in, and the volume slider widget being updated accordingly. I will report back with more clarification after more observation.

    *** UPDATE ***
    THIS PROBLEM IS NOT SOLVED.
    I thought it was purely a performance issue that was delaying the update of the volume slider. However, I've recently observed the slider displaying the speaker volume permanently with the headphones plugged in.
    Locking and unlocking the screen caused the slider to refresh.
    "Discussions" does not allow me to undo the "Solve" flag above. All I can do is state that this is an open issue here.

  • Kernel crashing during first boot on VirtualBox

    I'm trying to get install Arch Linux on VM running on my Windows 7, I set up the machine and everything else that was in the guide on wiki, but during first boot, I get kernel error and machine freezes.
    This is screenshot of error:
    http://i.imgur.com/msTUERH.png
    I'm new to Linux so I might have missed something obvious, don't be too harsh on me please
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --

    Mhm, I only have to suggestions (I am not a kernel-pro though):
    Enable PAE/NX at the "System -> Processor" tab in the vbox configuration
    If that does not work disable it and try to reconfigure the vm with minimal settings in virtualbox. For example, disable audio, networking, usb, 3d etc... and see wether your machine crashes or not.
    Last edited by Resauce (2014-12-08 07:12:47)

  • Rc.sysinit and btrfs: not show partition during the boot

    Hi,
    I see, during the boot, that show only partition NOT in btrfs...
    e.g i have two partitions: /dev/sda1 for / in ext4 and /dev/sda3 for /home in btrfs
    during the boot I see only /dev/sda1 clean but I don't see /dev/sda3...
    But partition mounted correctly.
    This my fstab
    /dev/sda1 / ext4 defaults,relatime,commit=10 0 1
    /dev/sda3 /home btrfs defaults,relatime 0 2
    /dev/sda2 swap swap defaults 0 0

    falconindy wrote:
    btrfs's fsck prog doesn't use the same name scheme as every other fsck prog (fsck.FSNAME). I don't know if renaming /sbin/btrfsck would be lethal to other btrfs utilities, so a symlink takes care of it:
    # ln -s /sbin/{btrfsck,fsck.btrfs}
    uhm...thank's...
    I'll try later, now I have experimented with udev, hal, usb device, xfce, default mount options

  • Token and smart card reader are not detected on Mavericks if not plugged on a USB port during system boot

    Well, both token and smart card reader are not detected on OS X 10.9 if not plugged on a USB port during system boot. So, if I am already working within the system and need to use my certificates I have to plug the token or smart card reader on a USB port and restart Mavericks.
    Token is a GD Starsign and Smart Card Reader is a SCR3310 v2.
    Thoughts?

    SCS is a very good app, since I've read that Apple has discontinued support for PC/SC interfaces after the release of Mountain Lion.
    (My previous installation was a Mavericks upgrade from Lion)
    However, I don't know what and how to debug using Smart Card Services. Do you know any commands to use?
    Apparently, the SC reader reports no issues: the LED is blinking blue when no smart card is present and becomes fixed blue when a smart card is inserted – according to the manuals, this shows that there is correct communication between the OS and the CCID reader.
    I don't know what to do; I'm beginning to hypothesize it's a digital signer issue. In fact, my smart card only supports one application called File Protector (by Actalis) to officially sign digital documents. This application seems to have major difficulties in identifying the miniLector EVO.
    The generic and ambiguous internal error comes when I try to manually identify the peripheral.
    Athena CNS is one of the Italian smart cards and is automatically recognized and configured (so it's correct – no doubts about this), while "ACS ACR 38U-CCID 00 00" seems to be the real name of the miniLector.
    (I'm assuming this because System Information also returns that the real manufacturer is ACS... bit4id is a re-brander)
    However, when I click on it and then tap OK, it returns internal error.
    As first attempt, I would try to completely erase&clean File Protector files to try a reinstall. Then, if this still doesn't work, I'd debug using the terminal.
    So:
    - Do you know any applications to 100% clean files created by an installer?
    - Do you have in mind any solutions that I might have forgotten?
    Thanks in advance from an OS X fan!

  • Loud Pop during startup after 10.5.6

    Post 10.5.6 I get a loud pop during the very end of the grey startup screen or right after the time verbose mode goes to a blue screen. Note it only happens when I have my speakers plugged into the headphones jack. I have Harman Kardon SoundSticks II attached. Any one else with external speakers getting this?

    Greetings,
    I have Bose speakers on One Mac, and Altecs on my Mac Pro, in another room - both are at 10.5.6 (combo update) and neither one pops at that point, nor at any other time for that matter.
    It's certainly not a global issue, just an issue for some folks.
    Cheers,
    M.

  • Noisy background noise when using speaker phone during calls

    Hi
    Phone: sony experia z3
    Does anyone have the same issue as me when you use the speaker phone during calls?
    There is a lot of background noise.The caller's voice also sounds echoish
    When I turn off the speaker and switch back to normal call it noise disappeared, the the caller's voice is clear.

    See if speaker voice enhancement is enabled.
    All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

  • Monitor Signal Drops During XP Boot

    Hello All!
    This is my first post on this forum, so please forgive me if I make any mistakes. I have recently bought a MSI Motherboard, and all was well until I turned my pc on without the monitor plugged in - now, the monitor signal drops during the boot up (at the xp screen when the bar is moving across the screen).
    My system setup is this
    Athlon xp 2000+
    MSI K7n2G Board
    Using the on-board graphics
    256mb DDR Kingston RAM 27000 (fully compatible with the board)
    120 GB Western Digital hard disk
    Liteon cd writer 52x 24x 52x
    Pioneer 106 DVD writer
    I believe I am running BIOS 3.5
    I tried booting up in safe mode and that boots up fine. I did a system restore to the day before I accidentally turned the machine on without the monitor plugged in, and that didn’t make any difference.
    I am clueless as to why this doesn’t work, and am hoping someone here could tell me how to solve this problem.
    Many thanks for any advice, and thanks for reading,
    Regards,
    Rupz112

    I have come across a similar problem before. The problem was that the monitor couldnt support the default resolution of windows XP so I went in safe mode and lowered the resolution and the problem was solved.

  • Hi, can iMovie give pronlems during the boot process from my iMac Mine. I have often after working with iMovie that i get during the boot Psi SDXH pause so the boot process stops

    hi,
    can iMovie give problems during the boot process from my iMac Mini?
    I have often, after working with iMovie that i get during the boot Psi SDXH pause
    so the boot process stops at this point
    I have often reinstall OSX Mavericks
    regards,
    HenkfromWinterswijk
    Netherlands

    Hello Federico,
    Your EliteBook is a Business model.  Your issue would be best answered on the HP Enterprise Business Community Forum
    Good luck!
    ↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Maybe you are looking for