From: Stefan M. <mo...@ir...> - 2009-08-20 17:00:34
|
Everytime I power-on my Macbook Pro, it of course emits the usual "apple jingle". Is there a way I can turn it off? Stefan |
From: Justin P. M. <jus...@gm...> - 2009-08-20 17:27:03
|
Stefan Monnier wrote: > Everytime I power-on my Macbook Pro, it of course emits the usual "apple > jingle". Is there a way I can turn it off? > > > Stefan > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > > With the imac you can load osx and turn down the main volume to eliminate that "gong" sound. on the macbook(ati) seems to work and then not work. |
From: Michael C. <mdc...@gm...> - 2009-08-20 18:43:26
|
> Everytime I power-on my Macbook Pro, it of course emits the usual "apple > jingle". Is there a way I can turn it off? I'm the only Mac coder in an office full of Windows engineers, so they all know when I've arrived at work! You should know that that sound is the report that the Mac has passed its Power On Self Test. If it fails there are various unpleasant noises that are played instead. It's not just there for marketing purposes. Mike -- Michael David Crawford mdcrawford at gmail dot com GoingWare's Bag of Programming Tricks http://www.goingware.com/tips/ |
From: Fritz N. <nx0...@ya...> - 2009-08-20 21:08:10
|
Michael wrote: > > Everytime I power-on my Macbook Pro, it of course emits the usual "apple > > jingle". Is there a way I can turn it off? > > I'm the only Mac coder in an office full of Windows engineers, so they > all know when I've arrived at work! > > You should know that that sound is the report that the Mac has passed > its Power On Self Test. If it fails there are various unpleasant > noises that are played instead. It's not just there for marketing > purposes. > > Mike Maybe OT but if you still have OSX on your machine http://www.macupdate.com/info.php/id/16425 may help you. Just turn the volume down and you can still hear all those unpleasant noises when your machine's time has come. nico -- mailto: Fritz Neumann - nx0...@ya... |
From: Justin P. M. <jus...@gm...> - 2009-08-20 23:28:42
|
Fritz Neumann wrote: > Michael wrote: > >>> Everytime I power-on my Macbook Pro, it of course emits the usual "apple >>> jingle". Is there a way I can turn it off? >>> >> I'm the only Mac coder in an office full of Windows engineers, so they >> all know when I've arrived at work! >> >> You should know that that sound is the report that the Mac has passed >> its Power On Self Test. If it fails there are various unpleasant >> noises that are played instead. It's not just there for marketing >> purposes. >> >> Mike >> > Maybe OT but if you still have OSX on your machine > http://www.macupdate.com/info.php/id/16425 > may help you. > Just turn the volume down and you can still hear all those unpleasant noises > when your machine's time has come. > > nico > be careful i turned the sound off on my imac, then a few weeks later notice scrambled noises from the speaker when running osx. (couldn't fix it until luckily they updated the firmware). but I could be wrong. Justin P. Mattock |
From: Stefan M. <mo...@ir...> - 2009-08-25 19:00:29
|
>> Everytime I power-on my Macbook Pro, it of course emits the usual "apple >> jingle". Is there a way I can turn it off? > I'm the only Mac coder in an office full of Windows engineers, so they > all know when I've arrived at work! > You should know that that sound is the report that the Mac has passed > its Power On Self Test. If it fails there are various unpleasant > noises that are played instead. It's not just there for marketing > purposes. I'm somewhat annoyed by the beep produced by my PC, but I learned to live with it. The same may hold for my Macbook Pro, except that the sound is more obnoxious. There is obviously some way to change its volume, but I can't find how to do that from GNU/Linux. Stefan |
From: Stefan M. <mo...@ir...> - 2009-08-25 18:53:52
|
> With the imac you can load osx > and turn down the main volume to > eliminate that "gong" sound. > on the macbook(ati) seems > to work and then not work. Installing OSX just to turn off that damned sound seems a bit excessive. Stefan |
From: Justin P. M. <jus...@gm...> - 2009-08-25 19:32:19
|
Stefan Monnier wrote: >>> Everytime I power-on my Macbook Pro, it of course emits the usual "apple >>> jingle". Is there a way I can turn it off? >>> >> I'm the only Mac coder in an office full of Windows engineers, so they >> all know when I've arrived at work! >> You should know that that sound is the report that the Mac has passed >> its Power On Self Test. If it fails there are various unpleasant >> noises that are played instead. It's not just there for marketing >> purposes. >> > > I'm somewhat annoyed by the beep produced by my PC, but I learned to > live with it. The same may hold for my Macbook Pro, except that the > sound is more obnoxious. There is obviously some way to change its > volume, but I can't find how to do that from GNU/Linux. > > > Stefan > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > > I guess if you don't want to install osx to the hard drive you can put it on en external ieee1394 disk.(this way you have a copy of that system for whatever reason). As for using linux to disable this, not sure! Justin P. Mattock |
From: Sam N. <sa...@th...> - 2009-08-27 22:47:04
|
On Tue, 2009-08-25 at 12:32 -0700, Justin P. Mattock wrote: > I guess if you don't want to install osx to the > hard drive you can put it on en external ieee1394 > disk.(this way you have a copy of that system for > whatever reason). I've considered doing that but have never convinced myself it's worth the effort. Though the noise is particularly galling. > As for using linux to disable this, not sure! As I understand it the volume gets stored as an EFI variable, so I always imagined that it would be possible to fix it from the efi shell, if you knew what to change. I generally picture doing this by finding someone with a similar macbook and MacOS and convincing them to: * turn down the volume in Mac * reboot int rEFIt * run the efi shell * figure out which settings are applicable * save the appropriate crazy long string to vfat or something And then I'd boot rEFIt and try to enter that magic "volume=0" string. I suppose if this was a sane idea, it would also work just as well by booting in efi mode and using the efivars kernel driver to edit the value. If anyone goes down this road, please pass along your results. :) sam |
From: Stefan M. <mo...@ir...> - 2009-08-28 17:19:17
|
> As I understand it the volume gets stored as an EFI variable, so I > always imagined that it would be possible to fix it from the efi shell, > if you knew what to change. > I generally picture doing this by finding someone with a similar macbook > and MacOS and convincing them to: > * turn down the volume in Mac > * reboot int rEFIt > * run the efi shell > * figure out which settings are applicable > * save the appropriate crazy long string to vfat or something I could try that, except I have no idea what the "figure out which settings are applicable" step should look like: the few tiems I tried to run the efi shell (mostly to see what it looked like), I got the impression that no command worked there. If someone has some hints of commands I could/should start with, that would help. Of course, I'm not sure the volume is actually saved in an EFI var. After all, even with MacOSX, changing the boot sound's volume can only be done indirectly (by setting the general volume). Stefan |
From: Alexandre B. <al...@bo...> - 2009-08-29 02:21:47
|
Le vendredi 28 août 2009 à 13:18, Stefan Monnier a écrit: > I could try that, except I have no idea what the "figure out which > settings are applicable" step should look like: the few tiems I tried to > run the efi shell (mostly to see what it looked like), I got the > impression that no command worked there. If someone has some hints of > commands I could/should start with, that would help. Hi, the variable you are looking for is named "SystemAudioVolume". When the sound is muted in OS X System properties, it is equal to 0x80, so I guess the most significant bit is a flag. Otherwise, the value seems to represent a percentage, taking values between 0x03 up to 0x64 (but the scale is not linear, as 25% in System properties is represented by 0x32). Or at least this is how it seems to work on my 2006 Mac Pro. To modify this in the EFI shell, it seems that you have to use the dmpstore command, saving the variable to a file, modifying the file, then loading it back. Regards, Alex |
From: Sam N. <sa...@th...> - 2009-09-09 20:37:57
|
On Sat, 2009-08-29 at 04:02 +0200, Alexandre Boeglin wrote: > Hi, the variable you are looking for is named "SystemAudioVolume". > When > the sound is muted in OS X System properties, it is equal to 0x80, so > I > guess the most significant bit is a flag. Otherwise, the value seems > to > represent a percentage, taking values between 0x03 up to 0x64 (but the > scale is not linear, as 25% in System properties is represented by > 0x32). > > Or at least this is how it seems to work on my 2006 Mac Pro. > > To modify this in the EFI shell, it seems that you have to use the > dmpstore command, saving the variable to a file, modifying the file, > then loading it back. Hey! that works fine. Thanks very much Alex. For posterity the process on my non-pro2,1 goes something like this: #<Boot EFI shell> #<spend 30 minutes finding the page break switch for help :) > Shell>help -b #<cd to a writable partition (I had booted from a refit CD, so fs0 was the disk, fs1 was the 100MB efi partition)> Shell>fs1: fs1:\> #<dump the nvram variable> fs1:\>dmpstore SystemAudioVolume -s sav.txt #<edit the the dumped variable with a hexeditor (probably wiser to keep the original dump and edit a copy)> fs1:\>hexedit save.txt #<load the new nvram variable> fs1:\>dmpstore SystemAudioVolume -l sav.txt #<exit to refit and reboot> fs1:\>exit Enjoy the BONGless restart. So for a while it wasn't apparent what value to change with the hexeditor, and tbh, not being familiar with any hexeditor, I'm not sure I got it right. Further experimentation indicates I may have just borked it, but apparently that also serves to make it shut up. The files (now back in Debian) look like this: $ cat SystemAudioVolume.txt $SystemAudioVolumeaC|*��K���A�\��q <-with no newline $ hexdump -C SystemAudioVolume.txt 00000000 24 00 00 00 53 00 79 00 73 00 74 00 65 00 6d 00 |$...S.y.s.t.e.m.| 00000010 41 00 75 00 64 00 69 00 6f 00 56 00 6f 00 6c 00 |A.u.d.i.o.V.o.l.| 00000020 75 00 6d 00 65 00 00 00 10 61 43 7c 2a ab bb 4b |u.m.e....aC|*..K| 00000030 a8 80 fe 41 99 5c 9f 82 07 00 00 00 01 00 00 00 |...A.\..........| 00000040 71 |q| 00000041 (In hexedit.efi the 00000041 line did not appear.) Since running dmpstore SystemAudioValume by itself returned output something like: 00000: 71 "q" I took a guess and replaced the 71 with Alex's 80 getting: $ hexdump -C SystemAudioVolume80.txt 00000000 24 00 00 00 53 00 79 00 73 00 74 00 65 00 6d 00 |$...S.y.s.t.e.m.| 00000010 41 00 75 00 64 00 69 00 6f 00 56 00 6f 00 6c 00 |A.u.d.i.o.V.o.l.| 00000020 75 00 6d 00 65 00 00 00 10 61 43 7c 2a ab bb 4b |u.m.e....aC|*..K| 00000030 a8 80 fe 41 99 5c 9f 82 07 00 00 00 01 00 00 00 |...A.\..........| 00000040 80 |.| 00000041 Which turned off the bong and I'm happy. But for kicks I also tried 32 (for 25% more BONG) $ hexdump -C sav.txt 00000000 24 00 00 00 53 00 79 00 73 00 74 00 65 00 6d 00 |$...S.y.s.t.e.m.| 00000010 41 00 75 00 64 00 69 00 6f 00 56 00 6f 00 6c 00 |A.u.d.i.o.V.o.l.| 00000020 75 00 6d 00 65 00 00 00 10 61 43 7c 2a ab bb 4b |u.m.e....aC|*..K| 00000030 a8 80 fe 41 99 5c 9f 82 07 00 00 00 01 00 00 00 |...A.\..........| 00000040 32 |2| 00000041 But that also gave me silence, so I think I'm doing it 'wrong.' However reloading the original (71) file did bring back the bonging. So I don't think any of this is particularly dangerous for those who may want to here the noise again someday. :) |