6 distros, 1 HD ? wtf !

Okey. I see your problem. I had it too. Try this. It's safe and worked for me.

Open the terminal and type

Press S and select the HD-Audio Generic option. Scroll to automute and disable it now turn up all the volume options Press Esc to exit

Done!

************************************************************************

use https://wiki.debian.org/NetworkManager !!!

Well you're not authorized. Who owns the filesystem?

I guess you formatted it with mkfs (or left it on the installer) and now it has root:root privileges. In that case read up on chown ('man chown'. You did want to learn, did you? :P ), then mount it as root (preferably using terminal) and change the privileges to the user.

You could try to reinstall grub (with no usb attached). Try
as root.

The first command installs grub to MBR (actually wherever you tell it to, but you should install it to MBR). The sdX is the physical disk you want grub on (not a partition, so no numbers, like 'sda1').
The second command updates the grub.cfg file.

You put the bootloader on the usb. Note that the bootloader (grub) is NOT the same thing as the /boot partition.

hey friends,

i didn't understand a thing about the bootloader or grub. First i can tell you guys, while doing the installation i selected the partition of 500mb size as the /boot and rest of the stuff. Then at the end it couldn't boot without usb. After reading from several webpages forums i knew one thing that i have to repair the grub and that i did using a grub-repair-disk. I downloaded the iso file and put it in a usb using unetbootin and ran recommended repair option. Afterwards, debian could boot up own it's own. I have no idea how to manipulate grub to do provide options at the grub menu of several distros.

About file system, i think i might have left the two drives to : do not use option.
any idea how i can modify this without doing reinstallation?

Now, wifi, audio, video works. Still in thunar i can't see icons.


Please reply, i l be waiting.

Ok, but again, the bootloader is not the same thing as /boot. You put /boot on its own partition, and that's fine, but where to put the bootloader is a completely separate question. It usually asks after the partitioning is done, before it starts the installation. You don't pick a mount point or a partition, you pick a drive, and apparently you picked the usb drive.

As Captain Pinkeye said in his post, you can fix this with grub-install and update-grub.

Is it still necessary? i used grub-repair. If yes please elaborate a bit.

I didn't understand it really. What do u mean by /dev/sdX what is sdX if not denoting a partition. should i write sd0 if i have only one hard disk?

Also how can i solve my mounting problems which i showed in my second snapshot before and no icons.

I mis-read your post, I thought you said "Afterwards, debian couldn't boot up on it's own", implying that nothing had changed. It does appear that it fixed your problem.

For the record, Linux and Windows treat drives and partitions very differently. In Windows, you don't see anything until you have a drive, with a partition, with a filesystem, and it's mounted, at which point it shows up as C: or D: or whatever stupid name Windows decides to give it.

In Linux, you can see everything. You can see and manipulate bare drives, or bare partitions, or filesystems, or you can mount them, and you can mount them wherever you want in the common directory structure (instead of each drive having its own, separate directory structure). In Linux, drives are called sdX, where X can be a, b, c, d, and so on. So one drive would be sda, another would be sdb, etc. Within each drive, you have partitions. These are called sdX#, so the first partition on sda would be sda1, the second partition on sda would be sda2, and so on.

What he was saying is that when you go to install grub, you do it on the drive itself, not the partition. So if you wanted it on sda, you would choose /dev/sda, rather than, say, /dev/sda3 which might contain your /boot partition.

You should write sda.
There and there is a quick overview you could find useful. Basically, sda denotes your first harddrive, sda1 first partition on that harddrive.

What exactly do you want to modify? Do you want to format them (you can use Gparted) or add them as existing partitions to the system (you can do that by editing fstab)?

Best to use a less mechanical distro!

try this:

http://www.linuxmint.com/

http://www.salixos.org/

http://www.opensuse.org/en/

http://aptosid.com/

http://fedoraproject.org/

@Captain Pinkeye

I just want to access the two other empty drives as data partitions. RIght now i am getting error as No Authority in THunar when i click on them.

If you want to access data on an additional drive you need to first create a mount point, then create a filesystem, then mount the filesystem. If you want the partitions to be mounted on boot, you need to put a proper entry in the /etc/fstab file. If you are not familiar with these actions, you need to post back with what you do and do not know.

hello everyone..
i am trying to install NS2 i followed the instructions and installed NS2 correctly. Checked its correctness via typing ns after its complete installation but when i tried to check whether nam is installed correctly but i am unable to see the animator window. i always get segmentation fault.please help me and tell whats the problem and how to resolve it..
thank you.

jyotipandey:

Please start a new thread as your questions is unrelated to the topic of this thread.

@yancek: dude thanks for your help appreciate it big time!

now back to mounting. I used Ub previously. So while using it a user can just click on the partition which is visible at left part of the file manager and then it gets mounted. This is what i want. When i click on partition i just get not authorized error.

this theory part that u talked about is perfect. How do i do this?

editing fstab will mount everything directly which is not problematic but i would like to go the UB way as i mentioned before.