SilverSurfer60

Sorry I should have been a bit more precise and said the 'mandriva safe mode', which when selected will boot into single user mode. Sorry for the inaccuracy.

What about erasing the single user mode from the boot menu. You could also remove the dvd/cdrom from the boot order in the bios. Password protect the bios so that you can reactivate if you need.

The solution you are after depends on the router and its dhcp server. You require the router to be able to supply the hostname/ip address to each computer on the same network. Some do some don't. It also depends on your gateway address. I assume you are using the router as the gateway? Other than the router maintaining the host/ip addresses you could set up one of you always on computers to act as a dhcp server. This is one area where Mandriva is a little more secure than windoze, in that one has to purposely open up the network to this sort of behavior. I hope there is something there that you can use.

Try disabling pulse audio in the MCC. snd-hda-intel doesn't seem to play well with pulse audio.

It's fixed. How I don't know :blink: After much heavy reading, running scripts the line input suddenly burst into life. I have checked all the saved data and there is nothing different in channels, controls etc. The only thing I can think of is the Jack Plug Socket was not connecting properly. I think this because I pushed on the plug a little bit harder, by accident I add, and it was after this things started working. Maybe a mechanical fault after all. I should have thought of testing that before with all my years of fault finding on office machinery. You know thing where one looks straight past the obvious. The bottom line is Alsa, snd-hda-intel works, and so does my sound now.

I've thrown the rattle out of the pram(baby buggy) today. Soundblaster has gone in and onboard card disabled. Thank you for the assistance but I feel the card is just too new for the Alsa drivers. I will try again when I can afford to waste a day or too. ;)

As I don't appear to have either of the .conf files you suggest I elected to add the lines to /etc/modprobe.conf with no effect. I have tried alsactl -r init NVidia (NVidia being the card) and got the result:- Unknown hardware: "HDA-Intel" "VIA VT1708S" "HDA:11060397,104383b7,00100000" "0x1043" "0x83b7" Hardware is initialized using a guess method Which would confer with what you said earlier about snd_hda_intel being started in auto. I will now do the bed-time read of the website you pointed me to. Thank you for your patience in this. I find it really interesting.

Right I found cat /proc/interrupts gave me a list interrupts and noticed that HDA_intel shares an interrupt with USB3. The only interrupt that was vacant was interrupt 4. Can I force hda_intel to use the vacant interrupt, or some other one? I have included the output of the above command line if you wish to take a look. interrupts.txt

Yes the contents of /etc/asound.state do match the output of the script. Finding out the exact details for the card is a bit iffy. It's identified as '02:00.1 Audio device: nVidia Corporation Device 0be3 (rev a1)' Googleing does not really help, as I posted earlier there is a number of requests for information on this card. The system bios is too new to be upgraded and gives very little information on the card itself. One thing I have thought about is the possibility of an interrupt clash. Unfortunately I don't know how to fault find this on Linux. What's your thoughts on that Scarecrow?

It's the force!!!

Yes, blacklisting the defunct module has got rid of the timeout. Unfortunately it has not cured the problem. What I did notice, by accident, when I booted up I got sound via the line in, I had a sound source playing, however when the login screen appeared the sound disappeared. So I switched from graphical boot screen to text and sure enough had sound until Alsa was started. So the problem is with Alsa would think. Just what I don't know.

Got a temporary workaround. Using the SoundBlaster from my other machine. Thank you Scarecrow, I haven't given up yet just needed to get things computer working with sound.

Got the script and run it. I have posted as an attachment so that anyone not wishing to read it doesn't need to. alsa_info_output.txt

# lsmod | grep snd snd_pcsp 10256 1 snd_hda_codec_via 53764 1 snd_seq_dummy 2984 0 snd_hda_intel 26144 2 snd_seq_oss 30368 0 snd_seq_midi_event 7428 1 snd_seq_oss snd_seq 52528 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 7600 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 38208 0 snd_hda_codec 86048 2 snd_hda_codec_via,snd_hda_intel snd_hwdep 7752 1 snd_hda_codec snd_pcm 78024 4 snd_pcsp,snd_hda_intel,snd_pcm_oss,snd_hda_codec snd_timer 21836 2 snd_seq,snd_pcm snd_mixer_oss 16644 1 snd_pcm_oss snd 62564 19 snd_pcsp,snd_hda_codec_via,snd_seq_dummy,snd_hda_intel,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,snd_mixer_oss soundcore 8128 1 snd snd_page_alloc 9452 2 snd_hda_intel,snd_pcm The modules seem to be loaded. I have not tried running OSS yet.

dmesg | grep intel ALSA hda_intel.c:695: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000 No hits with grep snd or sound.

It would appear that I have libalsa2 installed. I have just compiled and installed a new release of alsa version 1.0.22 from the website. There is a slight increase in volumes, yet the channel map is the same. I have found that I don't actually need a sound input to the main board from the cdrom to provide sound from an audio cd. :unsure: They still play without one.

Thank you for that Jill, however I keep going in circles and end up with the system chosen snd_hda_intel. This works somewhat but some of the channels are mapped to the wrong volume control and regardless the 'Line' channel does not work at all. I have (a rather ancient) tv card, brooktree, which works fine and I have to take an internal connector from this card and use the CD connector on the main board. The downside to that is I can't play CD's without going in to the box and swapping the cables about. As you can imagine there are a number of remedies out on the net, but not one is a definitive answer. It does appear as though I may have to wait for Alsa to catch up with the times.

The main board is Asus M478-AM: Dual DDR, S-ATA 11, PCIe x16, 2xPCI If that helps Scarecrow.

Splashed out and got myself a built for me computer comprising of :- Tower Case Processor AMD Athlon X2 3000GHz/2MB cache Ram 4GB Dual DDR 800MHZ Motherboard ASUS M4N Dual DDR2 USB x 6 250 GB ata Hard Drive with 8MB cache Graphics Nvidia Geforce 8400GS Pci Express Sound card Onboard 6 Channel (5.1) High Def : More on this later Memory card reader 52 in 1 And of course Mandriva 2010 OS. What can I say but it flies. The only downside is the sound card. I have been busy with google and there seems to be plenty of problems but no conclusive answers. The card is recognised as requiring the snd_hda_intel driver. Without Pulse I can get the sound working of a fashion. The Line input doesn't work, and can't seem to arrange a Master volume control for kmix. I have a feeling that the sound card may be a bit advanced for the Linux Kernel. I'll keep digging and hopefully come up with a solution. In the mean time if anyone has ideas as to what can try I will be grateful. Thank you in advance. 02:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce 210] (rev a2) 02:00.1 Audio device: nVidia Corporation Device 0be3 (rev a1) The relevant lines from lspci. Rather cryptic Audio Device clue :huh:

Thank you for the clarification YinYeti. It's quite logical when you see it. Shouldn't the final statement in the switch loop be 'case: default', as a catch all other inputs? I understand the style of syntax depends on the language being used but generalized there's not a lot of difference.

I think you are correct. You can use XFdrake from the cli.

Is there any difference, apart from the code, of using a switch statement as opposed to elseif? This is not a criticism more of a question.

Have you installed wpa_supplicant? Happy New Year.

Merry Christmas John, Isadora. John, I don't have a definitive answer but have you checked the card is seated properly, or the cable fitted snug. I would expect you to have looked at these. In all my computing years I have never had a video, sound or any other card go bad on me. I have had main boards go, but then it was the power supply at fault. So I'm afraid it's a case of waiting for someone to come along that could say what the the problem is, or try another card of course.

There'll be no fun left then