Search:

Question deleted (I hadn't done near enough homework before I posted it). I still have a related problem, you can see it here if interested:...

I just asked a similar question over at AskUbuntu.

What ended up working for me was relying on the "Scanning for btrfs filesystems" that happens at boot and keeping fstab pointing to the UUID...

OK, I fixed it - I now have the Unity interface.

OK, the first procedure immediately below is not what I did, but I think it should work and, if it works, will be much faster than what I did....

Same here.

I just upgraded from 10.10 to 11.04 and have the same problem. My old Docky bar is at the bottom of the screen, so I can get a terminal, launch this browser, etc. - but I have no Unity interface!

Actually I ended up simply executing "sudo install-mbr /dev/sda" - all the data on sda1 is still there (partition info was not affected) - but grub is gone, so it will never accidentally boot from...

And that bootinfoscript is great - it would have shown me the problem right away:


=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for hi.
=> No...

That was basically it. The boot was not first in the BIOS, but that had been working fine for months because none of the other disks had grub installed/were bootable. But sometime in the last day...

I damaged my grub2 config. I can still easily launch my otherwise healthy Ubuntu 10.10 64 bit system using Partition Magic's Super Grub Disk 2's "detect any OS" utility, but when I try to boot from...

OK, that makes senses and is all I need know.



I was doing a bit of reading, and it's seems like the origin of the two points is:

/media = removable drives
/mnt = temporary mounting (for...

OK, I sorta get that - but I'm not sure if the "right" thing to do is have them automounted or not. Are you saying that if fstab is correct, automounting will not occur, and that is the preferred...

Bump - surely this must be a common problem?

Part of it is a permissions issue. I was able to get R/W access with the combination of:

sudo chown -R fred:fred /media/disk0
and
sudo chown -R 666 /media/disk0

on each drive.

I still...

I just upgraded from 9.10 to 10.10 and simultaneously added 4 new hard drives.

However I can not read or write to any of the disks (without sudo). They are also showing up twice (mounted and...

Of course! That fixed it. Thanks.

Grub2 always boots the first item on the grub menu. I edited my
/etc/default/grub to this:


# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
...

I had the same problem. I'm not sure exactly what I did that finally worked; I tried a lot of things including:
uninstalled the new alsa using the upgrade script ("-r" option, I believe),
...

It's working now. I'd gone back to using the onboard sound, then I messed around with trying a newer alsa ppa (see the ALSA Upgrade Script discussion). Then I uninstalled all that, ran the modified...

I'm still a bit confused - I thought this would show up in Synaptic after I added the PPA ("sudo add-apt-repository ppa:ubuntu-audio-dev"), but I didn't see anything. Would you mind spelling out...

Hi lidex,

This may not be exactly what you want, since I re-enabled my on-board audio so I'd have sound, so my HDA Intel is the current/active/working sound card right now. When I get a chance...

Just installed an Asus Xonar DS sound card. Installed the latest ALSA 1.0.23 drivers. The new drivers see my sound card just fine:

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0:...

I fixed it. Went in to Synaptic Package Manager and found one or two installed packages with ALSA and an older version number. Removed them, rebooted, re-ran the script, and now I've got 1.0.23!
...

Interesting... On my system
'cat /proc/asound/version' reports 1.0.22.1
but alsamixer version is 1.0.23...

I did! I just looked again and verified it. Copied straight out of my script:


PACKAGE=1.0.23
setpack () {
DRIVER=alsa-driver-1.0.23
FIRMWARE=alsa-firmware-1.0.23
LIB=alsa-lib-1.0.23...

Thanks for the tip. I just tried it on Karmic with your changes, and while it referred to 1.0.23 hundreds of times during the build/install, after I reboot and then "cat /proc/asound/version", I...