Re: Sound
lets try lspci | grep audio in a terminal first and see what you
have
for a sound chip
Worryingly, that just returns to the command prompt with no output
displayed!
Grep is case sensitive. Try adding the '-i' flag to ignore case
differences, ala:
lspci | grep -i audio
Mark
--
I don't believe I understand all I know about this.
--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Relevant Pages
- Re: Importing selected data from a fixed length text file.
... downloading the Gnu utilities from http://unxutils.sourceforge.net/ ... Then use a command like this at a command prompt to run grep and copy ... each type containing diffrent field information and sizes. ...
(microsoft.public.access.externaldata) - Re: can getopts tell flags from arguments?
... but the rules about what is a "flag" aren't what ... The only way an option argument can be missing is if the option is ... grep: option requires an argument -- e ...
(comp.unix.shell) - Re: Problem using grep through the unix shell: doesnt accept a regular expression in filename
... > However it works perfectly when i execute it on the command prompt by ... file for reading, and affects that to the standard input of grep, ... then the script will read from ...
(comp.unix.shell) - Re: Grep string with spaces
... > may have to fall back on evaluating the grep and setting a flag, ... > dropping into the next if only if the flag is set. ... command as a do nothing, you have to have a command here ...
(comp.unix.shell) - Re: script question
... work because the "read line" corrupts the lines by removing whitespace. ... you're misusing the -f flag. ... Second, by using the -m 1 flag, you're telling grep to stop after finding ... here's a sed script that should do what you want: ...
(comp.unix.questions) |
|
