I have an issue with my machine. The volume is 100% on startup, and I need that fixed. I looked around and found THIS on stackoverflow. However I cannot find the rc-default file I need to edit to make that solution work. I'm running Karmic. Anyone else find a solution to this problem?
View 9 RepliesAnybody have a good way to set the volume level to about 25% during a Gnome login? I sometimes have it to 100% watching movies, then I shutdown. The next day, the login sound is so loud it makes the windows (and my brain) rattle!
View 1 Replies View RelatedI am using UNR 9.04 with Alsa 1.0.22.1 For some reason everytime I reboot my volume levels reset to headphone & speaker muted and headphone/speaker/PCM levels all set to 0%.
Does anyone know if there something I can that will allow my levels to be the same after I reboot? or if there is a script out there that will set my levels on startup?
If there isn't a script what would I do to create my own? also what would I do to have it auto run at startup?
I am installing Ubuntu server 10.10 onto a machine with a 1 tb Hard drive. I have had a host of other problems installing but that is for another thread. My question here is that it takes so long to format such a big drive, and I have heard and read that LVM starts with a small partition and expands it as more room is needed. So the installer crashed and started over so this time I decided to choose 'Guided - Use entire disk and set up LVM' instead of just 'Guided - Use Entire Disk'. So it is asking me to set the size of the LVM Volume. Am I setting the size of the initial volume? or am I setting the max size the volume can expand to?
View 14 Replies View RelatedHow-To set the mixer volume level at system startup or login. A funny story that led up to this how-to first...
I made the obvious mistake of leaving my volume level set to nearly maximum. Of course, Ubuntu's default behavior is to restore the mixer to its last known state - a point of much irritation at that moment. This had been a problem in the past as well, and today was the last straw. So, I did some research, for quite some time I might add, and decided to be a good community member and share my findings. It seems that there are all sorts of opinions around the web. The dominant opinion is that a mixer should always be restored to its last known state, that this is all well and good, and why would you ever want it to work any other way. Lots of people suggested that the startup sound be disabled, which was not a terrible solution, but was still a work-around as it means that the next sound bite to be played is the alarming one.
Needless to say, I wanted to find out what I would call the "proper" way to set the mixer level at startup. As my laptop uses PulseAudio, and my office desktop uses ALSA audio, the methods were different. My focus was for PulseAudio as that was the original purpose. I note here that my method for ALSA is less detailed as it is not the default for Ubuntu audio these days. So, if you are using ALSA, you might have to be a little creative to make my ALSA note fit your needs. I have attached 2 files to this post, one for ALSA and one for PulseAudio.
Every time I boot input volume is set to the lowest possible setting... and no-one can hear me.
How can I get this to be at max automatically? (Specific setting visible below)
ALSA mixer resets my speaker volume to zero and changes my USB headset volume to a very low level. How can I get ALSA Mixer to remember my volume settings from last boot or if there's no other option, a way I can make it adjust the levels to a predetermined level automatically on startup. I'm using 10.10 with pulseaudio.
View 3 Replies View RelatedI have an mdadm/lvm2 volume with 4 HDs that I created in Ubuntu 10.04. I just upgraded the computer to Ubuntu 10.10.
I redid the mdadm commands to get volume up and running, did mdadm --detail --scan > /etc/mdadm/mdadm.conf to get the configuration file.
But now, every time I reboot, it tells me that the volume is not ready. /proc/mdstat says that I always have one disk of the volume "inactive" as md_d127. I need to stop this volume and reassemble the whole thing to get it working.
This is what I get out of mdadm --detail --scan and put inside /etc/mdadm/mdadm.conf:
And this is my /proc/mdstat on boot:
I need to do mdadm -S /dev/md_d127, mdadm -S /dev/md127, mdadm -A --scan to get this volume working again.
This did not happen with Ubuntu 10.04. I'm really fearing the loss of my raid5 data now.
one of the servers is the "main guy" which has NIS and NFS. the others mount the partition and can log in whith the same "main" account.
my problem is that i need to call a startup script "settings.sh" to set some enviroment variables for the cluster to work.
this script is on the NFS folder.
i would like if possible to call this script as early as possible, even before login phase, since they are servers and can be shutdown, restarted, etc.
at the moment i need to log via ssh into every one of the 4 nodes and do "source /opt/cfc/sge/default/common/settings.sh" manually each time they reboot.
i would like to put this script somewhere so that it gets called after the NFS mount, but without the need to log into an account. is possible?
otherwise i could set the nodes to automatically login into the main account..
im a little confused on something really simple, i know. But on the past i always used .bash_rc, this time i dont want to take that solution.
I have conky running a simple script on my Ubuntu 11.04 install. Running conky from using ALT-F2 is fine, but I have have conky added to the startup list, and when it runs from this, the conky window is different (ie not integrated with desktop layer). It has some shadowing around the edge and it seems to be on a layer other than the desktop. In addition to this, it stops running after a short while. I then run conky from ALT-F2 again and it's appears as I want, and stays there all day. I have included what I think is the relevant code below from my conkyrc. Has anyone had similar issues with a suitable way to resolve the problem?
Code:
own_window yes
own_window_transparent yes
own_window_type override
#own_window_type desktop
#own_window_type normal
#
own_window_type conky
own_window_class Conky
I have a dual boot machine; sometimes I want to use windows for something Linux won't do.
It boots up Linux by default, so if I want Windows, I need to interrupt it at the beginning.
It would be more convenient if I could tell it, when I shut down, what to reboot into.
Kontact automatically starts when I start up my computer. I can't find the setting for this. How can I change it?
View 9 Replies View RelatedMy software RAID setup is as follows.
/dev/md0 (made from sda1 and sdb1) RAID1 /boot partition
/dev/md1 (made from sda2, sdb2, and sdc2) RAID5 / partition
Earlier on I had some trouble with my sda drive, it dropped itself from both arrays, screwing up the mirroring of my two raid partitions participating in the /boot partition. I eventually got everything sorted out and back in sync. (I also have grub installed to MBR on both sda and sdb). Things are working fine regarding that, but since then I've had this issue:
During boot up, I'll get an error message that it could not mount my /boot partition (when fstab is set to either /dev/md0 or the UUID). It claims c9ab814c-47ea-492d-a3be-1eaa88d53477 does not exist!
My fstab:
Code:
[mark@mark-box ~]$ cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Wed Jan 20 16:34:41 2010
[code]....
As far as I know, it isn't neccessary for /boot to be mounted always, correct? Although, as I understand, I need to have it mounted whenever making kernel changes correct?
When installing Samba and Webmin I use the application "system-config-services" or (if it is easier to find for you that way) menu->Administration->Service management. In this application I can start the services I need (nmb, smb, webmin), but the enable/disable at startup setting is greyed out... Even when I start the application as root it still gives me no possibility to configure the services to start up on boot. This should be possible. It works this way in Fedora 13 and Fedora 14, so why not in Fedora 15?
Before reporting a bug, I would like to ask if other users here have the same problem (and -if possible- a solution)... In the mean tim I guess it is back to the old way of configurating services - sigh..
[edit] I tried to remove the [SOLVED] from the title, but the forum software does not seems to allow me to do that... I thought it was solved by installing xinetd, but I was happy a bit too early. I still have no answer for this problem.
Is there a way to default volume to 100% in the terminal with gnome-volume-control-applet or any other program? I am setting up a dedicated Zsnes machine which boots into Fluxbox but the volume is muted by default. There isn't a man page for gnome-volume-control-applet.
When I log into Gnome the volume is set to 100%, but Fluxbox is always set to mute.
I've got my xubuntu 10.10 install just about perfect on a little acer aspire d250, apart from a small sound useability issue: In the interests of simplicity and resource usage I removed pulseaudio. After a bit of fiddling I got it so that my USB soundcard (ProDac) is recognized and automatically set as the default soundcard when plugged in. Any sound applications automatically use the USB sound if it present, no need to around with pulse. The only problem is that my netbook's volume control keys still only control the master volume of the inbuilt soundcard, and have no effect on the usb sound. Does anyone know of a way to change which sound device these keys actually effect? I'd like to write a little script so that when the usb device is detected the keys are remapped.
View 1 Replies View RelatedI'm running Kubuntu 10.10 32 bit on an old DFI KT600AL motherboard based system using the onboard VIA 3058 AC97 audio (because it supports front panel audio connections and none of the add-in PCI soundcards I have do). I have an old Gateway/STB TVPCI TV tuner card (mainly wanted the FM radio part to work) hooked up to the cd audio connector on the motherboard because the digital audio over the pci bus apparently isn't supported for this card (neither is the onboard analog mixer on the tv tuner card, I had to hack a CD-ROM audio cable and solder it to the audio outputs of the tv tuner module on the TV tuner card). When I use the master channel as the master channel (selected in Kmix) then as one would expect it affects the output volume of all other audio playing on the system except that which is being handled by the PCM channel. On Windows the PCM channel was also affected by the "Volume Control" slider such that ALL volume levels were reduced when moving the slider. I'm hoping someone can help me figure out how to make it work like this on Kubuntu.
First off I should warn you that I (like many users of older hardware that is not properly supported under PulseAudio) have uninstalled PulseAudio (because it's garbage) and am using Alsa to manage my audio hardware. I would think that there would be some way to do this using the 'amixer' application to add the PCM channel as a component of the 'Master' channel so that when the volume is turned down using the 'Master' channel control it will affect the PCM channel too (at least the output to the speaker jack, not necessarily the capture or mix volume though), but I'm not really any good at doing things from a terminal window and the options for the amixer command kind of confused me.
I used Ubuntu 10.10 (64 bit) on IMac i7. As far as, I remember, after installing Pulse-Audio Equalizer, for each restart of the system, after login screen, system sets volume to maximum value. What can I do?
View 1 Replies View Relatedsince using 10.04 I have a big problem with my usb headset (freetalk everyman)
1. Problem: I cannot regulate the volume of the phones (output) anymore with gnome-volume-control. By default the volume is set to 100% which is way too loud. When I set it under 100% there is no sound at all. Values over 100% work.
2. Problem: The X server is freezing iregulary when I connect the headset and disconnect it, Magic SysRq works. I checked Xorg.0.log and found out that it recognizes the usb headset as keyboard:
[Code]...
I'm using 10.04 now and it runs ok, except one strange thing in the Volume control applet. Sometimes, when I click on the volume slider, it moves up. Even if I try to slide it down, it moves up on every click. The same when I click left of it - it keeps moving up! This is very annoying at night when the music gets loud and wakes everybody. It happens with or without Compiz turned on
View 3 Replies View RelatedI am struggling with a problem with the volume control... when i try to adjust the volume with the sliding bar i can not do it. If i put the scrollbar to the 0 position, it is muted. when i move it to anywhere else, i get the full volume. From other programs like vlc, i can adjust the volume with no problem.
View 2 Replies View RelatedMy volume control seems to have only three settings: TOO LOUD, VERY QUIET, OFF. If I adjust the Master volume slider from the Panel, only about the right 1/8th has any effect and if I slide it past about the 95% mark, I get no sound at all. At the far-right end of the volume control, I get total volume. It's basically like the slider only has any impact in the top 5% of it's space. Below 95% of the slide, there is zero volume.
It's so drastic, that one tap down of the volume button on my keyboard kills the sound (because it nudges the slider past that 95% mark). This happens in the Audio settings, etc., system-wide. If I adjust the volume for an individual app from within the app (MPlayer, for example) it behaves exactly as expected (that is, app volume works smoothly, it's just master volume that has this issue). I have run through most of the "obvious" things-- I'm wondering if I broke something by installing the extra KDE packages to get Amarok to work.
In Intrepid Ibex, I was using the left Super key as Volume Down and the right Super key as Volume Up, because it was just so convenient.
However when I go to the "Keyboard Shortcuts" window in Karmic, it doesn't let me assign the Super keys to anything. I mean like, I can use the Super Keys along with other keys, but not by themselves.
Is it somehow possible to use the Super keys for Volume Up and Volume Down in Karmic?
It seems that when I adjust the volume with the volume wheel on the side of my notebook, the OS messes up. Nothing is clickable, I cannot type anything, in order to get a working computer again I have to hard reset it.Why is this happening? I have never experienced this. I have a Toshiba Satellite that I recently installed Ubuntu on.
View 5 Replies View RelatedI'm running squeeze (last updated today), and everything has been working great. There is only thing that would simplify my life minutely..Anybody know how can I have the volume buttons on my laptop change the "pcm" channel volume rather than "master"? If they could control pcm, then I could adjust the volume coming out of my headphones or my computer speaker (both controlled by pcm, but not master...seems strange to me) with just one click.I tried to find this info online, but all results seem to refer to an older version. The simple "click here, set this" solution no longer is possible.
View 2 Replies View RelatedDebian Squeeze 6.0.0 on a Thinkpad T43, sound volume is not synchronized between the laptop volume buttons and GNOME's Volume Applet. So if I turn the volume all the way down with the physical buttons, the volume applet may still indicate 75%.I did not have this problem in Debian Lenny. Pressing the volume buttons used to show a volume bar on the screen, as did pressing the mute button.
View 8 Replies View RelatedI don't know much about lvm and I've managed to screw up a drive. I had a 500GB drive with FC14 on it and I wanted to copy over a load of data to my new 1TB that was replacing it. I set up my new install the same way as the old...including the same volume names (error number 1 I think) I successfully mounted the old/500GB drive (using vgscan and vgchange -a y etc.) using a laptop (running FC13) and an external hdd cradle. I could access the files I wanted but this wasn't the machine I wanted to copy them to (I was doing this while waiting for the install to finish on the new drive).
When I tried the same process on the new install I found that having two lvm with the same name meant I couldn't mount the external one. So I opened the disk utility (palimsest) and was going to change the name of the old volume group but it wouldn't let me do that. I then thought maybe I could get away with just changing the name of the partition where the files were and maybe I could add it to the mounted group or something so I changed it to lv_home2. This changed the name of my new/1TB lv_home to lv_home2 as well. So thinking that wasn't the answer I just changed the name of the new lv_home2 back to lv_home.
From that point on I haven't been able to see the old drives partitions (the new volume group still works so far). I has a physical volume but the volume group and volume names are gone from view. When I try to vgscan on my main computer or the laptop I had it working on earlier I get:
[Code]....
I'm rearranging a bunch of disks on my server at home and I find myself in the position of wanting to move a bunch of LVM logical volumes to another volume group. Is there a simple way to do this? I saw mention of a cplv command but this seems to be either old or not something that was ever available for linux.
View 2 Replies View RelatedJust wondering if anyone else experienced this. I have been using Ubuntu for half a year now and I love it. I just installed Kubuntu Desktop to try it out and I found that I can't get near as high volume with it than I do with Ubuntu. Ubuntu is even way louder than the Windows that used to be on here.
So why is there a change in the max of volume? I am a huge music person and that is the only thing holding me back from getting rid of gnome. I like how fresh and clean KDE is.
Code:
I have a system with a 2TB RAID level 1 installed (2 x 2TB drives, configured as RAID1 through the BIOS). I installed Centos 5.5 and it runs fine. I now added another 2x2TB drives and configured them as RAID1 through the BIOS.
How do I add this new RAID volume to the existing logical volume?