Re: Help with getting a script to run at bootup..
From: Scott Gardner (gardners14_at_cox.net)
Date: 06/16/04
- Next message: graham: "Re: Failure to get MPlayer to work properly"
- Previous message: baskitcaise: "Re: Help with getting a script to run at bootup.."
- In reply to: Scott Gardner: "Re: Help with getting a script to run at bootup.."
- Next in thread: Kevin Nathan: "Re: Help with getting a script to run at bootup.."
- Reply: Kevin Nathan: "Re: Help with getting a script to run at bootup.."
- Reply: baskitcaise: "Re: Help with getting a script to run at bootup.."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 16 Jun 2004 03:25:02 -0700
Scott Gardner wrote:
> Scott Leighton wrote:
>
>> Scott Gardner wrote:
>>
>>>
>>> Then, I reboot the computer, and press F2 to watch the details as the
>>> system
>>> boots up. I can see the output from my "mute_digital" script running
>>> right before the details screen goes away, so I'm pretty sure it's
>>> running at startup, but after I get to my desktop, there's no sound, and
>>> when I run alsamixer, the optical output isn't muted.
>>>
>>
>> Did you take a look at /var/log/boot.msg to see if any error
>> message flashed on the screen?
>>
>> Scott
>>
>>
>
> Here's the output from boot.msg. I included the commands that executed
> right before and right after my script, to make sure I didn't miss
> anything: My script is the one title "mute_digital"
>
>
> <notice>start services (splash_late)
> <notice>exit status of (splash_late) is (0)
> <notice>start services (mute_digital)
> numid=163,iface=MIXER,name='Audigy Analog/Digital Output Jack'
> ; type=BOOLEAN,access=rw---,values=1
> : values=off
> <notice>exit status of (mute_digital) is (0)
> <notice>start services (webmin smb)
>
>
> The text that's returned by the script is the same as if I run it from a
> command line.
>
> Scott Gardner
Found out a little bit more about the problem. I decided to play an album
while booting up the system. During the bootup, as soon as the system
loads the emu101k service, I get sound from my sound card. Then X starts,
and I get the KDE desktop. While the KDE splash screen is displayed, there
are several icons in the splash screen that progressively go from dim to
bright as KDE loads. The second icon is a wrench ("services", I think?),
and the third icon is a globe ("Devices" perhaps?). Anyway, right about
the time the wrench icon goes bright and it starts working on the globe
icon, the sounds cuts off again.
So, I think there's something in the KDE environment that's re-enabling the
optical output of my sound card and killing the analog output. The script
I added to the rc5 directory looks like it's unnecessary, since the sound
actually worked even before my script executed. It's something that
happens later when KDE is loading that's re-enabling the optical output and
screwing me.
I'll try to find the KDE component that's doing it, but in the meantime, is
there a place I can put my script so that it will execute after KDE is
finished loading?
Thanks again,
Scott Gardner
- Next message: graham: "Re: Failure to get MPlayer to work properly"
- Previous message: baskitcaise: "Re: Help with getting a script to run at bootup.."
- In reply to: Scott Gardner: "Re: Help with getting a script to run at bootup.."
- Next in thread: Kevin Nathan: "Re: Help with getting a script to run at bootup.."
- Reply: Kevin Nathan: "Re: Help with getting a script to run at bootup.."
- Reply: baskitcaise: "Re: Help with getting a script to run at bootup.."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|