Volume Control/Icon is gone (Ubuntu 10.04)
The alsa sound driver, and volume control icon don't always work in 10.04.
First, You may have this, or may not, but the Volume Control needs to be running.
Click on System>Preferences>Startup Applications
Click +Add, then input:
Name: Volume Control
Command: gnome-volume-control-applet
Comment: Launch volume control applet
Next, The top bar panel needs the volume and login icon. It's done with something called Indicator.
(Someone else already asked why it's called "indicator" :) )
Right Click on Panel (Top Bar)
Click Indicator Applet
Click Add button
You may need to reboot to take effect.
Friday, November 9, 2012
Wednesday, November 7, 2012
HowTo: Restore an Ubuntu system with a bad kernel, broken network driver, unbootable system.
http://askubuntu.com/questions/28099/how-to-restore-a-system-after-accidentally-removing-all-kernels
When you lose a network driver, or have a bad kernel for some reason, this will get you going.
You are starting a working system, then setting up the essentials to chroot into your broken system. The kernel, drivers and things you need are borrowed from the working system. Then you can reinstall packages, until it's working again.
First boot from a Live Ubuntu DVD/USB. Select Try without installing. Open a terminal, and follow the instructions in the Link. Your mileage may vary, I'll try an example with sda1 boot, and sda2 root filesystem.
# Mount the root filesystem to /mnt
mount /dev/sda2 /mnt
# Check /mnt for a root filesystem (bin var etc ...)
ls /mnt
# Mount the boot partition to /mnt/boot
mount /dev/sda1 /mnt/boot
# Check /mnt/boot for kernels, if not, figure out where they are.
ls /mnt/boot
# Mount the system partitions from the Host OS.
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /dev /mnt/dev
# Chroot to your linux where everything works now...
chroot /mnt
# now you at / in your old linux.
# set the environment
mount -t devpts none /dev/pts
export HOME=/root
export LC_ALL=C
# Verify you have a working network
nslookup google.com
ping google.com
At this point you can apt-get packages and fix your system.
--- after chroot
# See what kernels you already have.
ls /boot
# See what kernels you might want.
apt-cache search linux-image
# Depending on space in /boot, install an old and new one you might like
# An old generic one in the preempt list might not appear in the regular list
apt-get install linux-image-<2 .6.32-36=".6.32-36">-generic
You can fix about anything wrong with a bad system with this!
When you lose a network driver, or have a bad kernel for some reason, this will get you going.
You are starting a working system, then setting up the essentials to chroot into your broken system. The kernel, drivers and things you need are borrowed from the working system. Then you can reinstall packages, until it's working again.
First boot from a Live Ubuntu DVD/USB. Select Try without installing. Open a terminal, and follow the instructions in the Link. Your mileage may vary, I'll try an example with sda1 boot, and sda2 root filesystem.
# Mount the root filesystem to /mnt
mount /dev/sda2 /mnt
# Check /mnt for a root filesystem (bin var etc ...)
ls /mnt
# Mount the boot partition to /mnt/boot
mount /dev/sda1 /mnt/boot
# Check /mnt/boot for kernels, if not, figure out where they are.
ls /mnt/boot
# Mount the system partitions from the Host OS.
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /dev /mnt/dev
# Chroot to your linux where everything works now...
chroot /mnt
# now you at / in your old linux.
# set the environment
mount -t devpts none /dev/pts
export HOME=/root
export LC_ALL=C
# Verify you have a working network
nslookup google.com
ping google.com
At this point you can apt-get packages and fix your system.
--- after chroot
# See what kernels you already have.
ls /boot
# See what kernels you might want.
apt-cache search linux-image
# Depending on space in /boot, install an old and new one you might like
# An old generic one in the preempt list might not appear in the regular list
apt-get install linux-image-<2 .6.32-36=".6.32-36">-generic
You can fix about anything wrong with a bad system with this!
Subscribe to:
Posts (Atom)
