Search:

Thanks - I figured out how to set it as default in most ALSA apps and in Phonon.


However, although the plugin is definitely being used (as stereo is no longer upmixed which seemed to happen...

After creating the plug:51to40 device and telling everything to use it, it's become clear that indeed, mplayer is in the wrong.

So, different question now - how would I go about setting...

I might have figured out why - maybe mplayer is parsing the wave file's channels differently? Does anyone know how wave files are parsed as far as channels are concerned by mplayer and xine...

I'm incredibly confused about this. It seems to be that everything has a different idea about which channel is which.

First of all, my sound card:

00:1b.0 Audio device [0403]: Intel Corporation...

Hmm, all I've been able to find out from searches is that the driver used is iwlagn - which is probably already installed...

Just a random guess - maybe the device node has already been created but just in an odd place. Try:

ls /dev/*lp*

ls /dev/*/*lp*

if anything comes back other than the standard /dev/lp0, etc.,...

Please post the output of:

lspci -nn

(if it's a non-USB card)

or:

lsusb

tar.bz2 will save a lot of space, but take more time.

tar -cvjf file.tar.bz2 place_to_backup_from

Try fiddling with settings to do with ACPI in the BIOS - make sure you write down what they were beforehand so you can change them back if it makes it worse!

Looks to me like disk read errors - either your HDD is failing, or for some reason coming out of suspend (which seemed to fail according to the log) made the HDD go weird.

It's an onboard card as he said in the OP.

Make sure that when you re-installed XP/7 you correctly installed the proper drivers.

Could you please give the output of:

lspci -nn


(This command displays device numbers as well as names, which are much easier to search)

(Don't know why the previous poster didn't ask for...

Give the output of the following commands:

lspci -nn

lsusb


(the first lists all PCI devices with their device numbers and names, which is a common way to plug devices in internally; the...

Give the output of the following command:

lspci -nn


If any of the devices have "Broadcom" in the name, try typing:

sudo aptitude install b43-fwcutter

Answer yes to any prompts you get,...

Hello, just bought a USB dialup modem (second hand for just the cost of postage so I don't care much if this is not possible). I've googled and the results don't look promising, but I thought I'd ask...

kill is used for PIDs, killall for executable names.

To pring a process into the foreground that you have backgrounded with &, you can type fg

Finally, if a process won't die, you can stick...

Gnome will parse autorun.inf files - I don't know if it'll blindly run any sort of executable though. I don't use it, I've just heard from someone who does that it parses autorun.inf for things like...

What is your graphics card?

If you don't know, post the output of lspci -nn | grep VGA

The easiest way to do that would be to write a udev/HAL (is that still used?) rule that launches a command-line media player like mplayer - how you would go about doing this I don't know. You could...

It actually makes sense why they both evolved like they did too - Unix comes from the time when teletypewriters were used to input commands, so the command names were made short - as with command...

I meant fundamental in the sense that it can't really be prevented without a major rethink - as opposed to one that can just be patched up.

And you only need the quotes if your $PATH has a space...

You can probably change the restart/shutdown commands in the login screen options to something that won't actually restart the computer - but then you'd have to log in in order to reboot at all.

Most UNIX distros in the early 90s (according to some old documents I've read; I've never actually used anything that early) had the PATH set up as I described in my previous post, but this was...

./ is a security feature. Consider the following scenario:

Some ******* placed a file called "ls" in a tarball and made it executable - it contains the following line:


rm -rf ~

(remove,...

You should move your computer temporarily to by your router and plug it in with an Ethernet cable in order to get internet so you can install the drivers.