Can you bring up an wireless connection manually with iwconfig?
First off, thanks for mentioning it, lacking Linux experience i didn't know this command.
As it is, it didn't work. Here is what i did:
All these commands proceeded without error, but there was still no wireless connection after that.
Quote:
For sound, you could try the following in /etc/modprode.d/sound (or whatever filename is appropriate on fedora)
I found a file /etc/modprobe.d/alsa-base and modified it according to your suggestions. In fact it had a single line "options snd-hda-intel enable_msi=1" already in it.
Alas "update-modules" is not available on my system. I investigated and to my current information it is a tool solely used on S390 systems. If it is available on PC systems too where can i download it? Anyway, i rebooted, which should have the same effect but still no luck with the sound.
Hi,friends!!!
I have a problem with my integrated sound card AC97 on i815 and my version of FreeBSD is 4.5.I know that there is a driver for it called ich.c.gz,but the site containing it is unavaliable now.And is there another driver or some other ideas ?
z-z-z-z-z
:: email removed :: (1 Reply)
Hi All
I am having difficulty configuring sound on my system an wonder if anyone can help me.
xmms refuses to play telling me that
oss_open(): Failed to open audio device (/dev/sound/dsp): No such file or directory
what I have done to try and fix this is
1. create /dev/sound/dsp ... (7 Replies)
Dear all,
I have been using suse linux for as long as I can remember. However, for every installation I get the same problem.
Once the installation is completed, and all of my devices (brand new hardware, from reknown brands) are detected, I decide to start doing some work, and play some... (2 Replies)
I've been using FC2, but my sound card doesn't work
I'm new with linux systems..
but there says that needs to recompile kernel
how can i do it with a kernel 2.6.5 i386 ?
by the way,. my sound card chipset is an ESS 1869F, with a compaq deskpro Smal Form Factor. but i have not found a... (4 Replies)
I am very new at learning Linux/Unix so please bear with me. I am taking a Unix course and I had to install Fedora Core 2 on my laptop PC using Microsoft Virtual PC software. After installing the virtual PC software, I installed the fedora cd's that came with the course. My problem is... (0 Replies)
I've been fighting for a few days now with trying to get my soundcard to recognize. I am currently using a Latitude D630 with Sigmatel C-Major Audio using the Intel ICH8 Family.
My problem appears to be that the computer cannot detect a sound card but it was only able to install default drivers... (0 Replies)
I feel like the true definition of a newb but I guess you gotta start somewhere. I installed Gentoo on my laptop yesterday, it's a gnome based environment and I cannot get any wireless internet. The iwconfig and net-setup commands are not being recognized. I'm not sure what the problem is, I've... (1 Reply)
My sound is messed up. All I get is white noise when I try to watch Youtube or something. I'm running Solaris 10 SPARC on a Sun Ultra 5, which has a built-in speaker. How do I fix it? (4 Replies)
Hi All,
I have dula OS on my system. With Windows and Linux(FC9). On Windows wireless setting works fine with wireless enabled.
Have installed Linux recently. Wireless is enabled, but i am not sure how to configure or make settings.
My laptop is Compaq and OS is FC9.
Please can anybody help... (1 Reply)
I installed F12 around the time it was released and it picked up my wireless card and worked like a charm.....Suddenly last week everything stopped working and I receive what appears to be a driver error when wlan0 tries to load.
Error for wireless request "Set Mode" (8B06) :
SET failed on... (1 Reply)
Discussion started by: woodson2
1 Replies
LEARN ABOUT DEBIAN
osstest
osstest(1) OSS User Commands osstest(1)NAME
osstest - Open Sound System audio self test applet.
DESCRIPTION
The osstest applet is a simple test application that can be used to test functionality of the sound hardware installed in the system.
osstest performs a playback test for each installed audio device. If there are any "machine detectable" problems they will be reported. You
will first hear an audio sample played on the left speaker, then the right speaker and finally in stereo on both speakers.
It's user's responsibility to listen if the test sound is audible. If no sound output can be heard the possible reason is one of the fol-
lowing:
1. An error was reported by osstest. In this case there will usually not be any sound output. The error needs to be fixed before running
osstest again.
2. There is no headphones or speakers connected. Or the connection is not made correctly.
3. The mixer volume level is set to a too low value. By default it should be OK. The mixer level can be adjusted using the mixer, ossmix
and ossxmix utilities distributed with OSS.
4. Some notebooks have nonstandard volume control and/or speaker selection hardware that is not supported by OSS. It's very likely that
OSS doesn't support such vendor specific additions.
If no errors were reported and the test sound was audible it means that OSS and your sound hardware is functioning correctly. If you still
encounter problems with some sound applications the reason is almost certainly in the application. Check it's configuration or try to use
another equivivalent application.
If you are having problems with JDS, KDE and/or Gnome system sounds, you need to make sure that OSS gets started before the GUI environ-
ment. Refer to your operating system's startup procedures.
SAMPLE RATE DRIFT
The osstest utility measures a sample rate drift value after playing back the test sound. Ideally it should be 0% but in practice there
will be an error of few percents. 0% means that the 48000 Hz test file was played exactly at 48000 Hz sampling rate.
The sample rate measurement is based on the system timer which has limited precision. It's likely that less than 1% differenc between the
nominal and the measured sampling rates are actually caused by an error in the measurement. For this reason the drift reported by osstest
should not be used as any kind of quality measurement. However if the drift is very large it means that there is something wrong in the
system. The oscillator chip used with the sound chip is broken or the system clock is running at a wrong speed.
USING OSSTEST MANUALLY
The osstest utility is located in the /usr/bin directory. It can be run manually to test functionality of OSS and your sound hardware. When
invoked without any command line parameters osstest performs the default test on all devices. However it will skip some of the devices base
on the following rules.
o It is possible to test just one of the available audio devices by giving its number on command line (for example osstest 1). Use the
device index numbers reported by "ossinfo -a".
o Use the -l command line option to loop the test infinitely.
o Virtual mixer devices will not be tested. Use the -V command line option to force test of virtual devices.
o The actual (physical) audio devices will be tested directly (bypassing virtual mixer). If you want to test playback through vmix then
use the -V option.
o Multiple device files related with the same physical device will not be tested. Only the first one gets tested while the remaining ones
will be skipped. At this moment there is no way to force osstest to test this kind of devices.
o Only stereo devices will be tested. Future versions of osstest will be able to test mono and multi channel devices too. Also osstest
requires that the device supports the 16 bit signed format and 48kHz sampling rate.
o Send a SIGQUIT (Ctrl- on most terminals) to make osstest skip a device.
FILES
/usr/bin/osstest
SEE ALSO savemixer(1)AUTHOR
4Front Technologies
16 December 2012 osstest(1)