I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
Thanks!
Ciao! Ryan
I can connect to FC ssh server only as root. ssh message: Connection to fctest closed by remote host. Connection to fctest closed. What can I do?
Best regards Alor Long
On Wed, 2004-09-29 at 16:04, Alor wrote:
I can connect to FC ssh server only as root. ssh message: Connection to fctest closed by remote host. Connection to fctest closed. What can I do?
1. Check if you are allowing users to log in 2. Check /etc/ssh/sshd_config or its variant Try connecting using -vv (very verbose) and look at the logs or the debug printouts
Btw, you really should not permit root logins.
eg: PermitRootLogins no
Best regards Alor Long
Try connecting using -vv (very verbose) and look at the logs or the debug printouts
alor@minsc:~> ssh -vv 10.7.123.2 OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f 11812: debug1: Reading configuration data /etc/ssh/ssh_config 11812: debug1: Applying options for * 11812: debug1: Rhosts Authentication disabled, originating port will not be trusted. 11812: debug1: ssh_connect: needpriv 0 11812: debug1: Connecting to 10.7.123.2 [10.7.123.2] port 22. 11812: debug1: Connection established. 11812: debug1: identity file /home/alor/.ssh/identity type -1 11812: debug2: key_type_from_name: unknown key type '-----BEGIN' 11812: debug2: key_type_from_name: unknown key type '-----END' 11812: debug1: identity file /home/alor/.ssh/id_rsa type 1 11812: debug1: identity file /home/alor/.ssh/id_dsa type -1 11812: debug1: Remote protocol version 1.99, remote software version OpenSSH_3.6.1p2 11812: debug1: match: OpenSSH_3.6.1p2 pat OpenSSH* 11812: Enabling compatibility mode for protocol 2.0 11812: debug1: Local version string SSH-2.0-OpenSSH_3.4p1 11812: debug1: SSH2_MSG_KEXINIT sent 11812: debug1: SSH2_MSG_KEXINIT received 11812: debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 11812: debug2: kex_parse_kexinit: ssh-rsa,ssh-dss 11812: debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se 11812: debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se 11812: debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 11812: debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 11812: debug2: kex_parse_kexinit: none 11812: debug2: kex_parse_kexinit: none 11812: debug2: kex_parse_kexinit: 11812: debug2: kex_parse_kexinit: 11812: debug2: kex_parse_kexinit: first_kex_follows 0 11812: debug2: kex_parse_kexinit: reserved 0 11812: debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 11812: debug2: kex_parse_kexinit: ssh-rsa,ssh-dss 11812: debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se 11812: debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se 11812: debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 11812: debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 11812: debug2: kex_parse_kexinit: none,zlib 11812: debug2: kex_parse_kexinit: none,zlib 11812: debug2: kex_parse_kexinit: 11812: debug2: kex_parse_kexinit: 11812: debug2: kex_parse_kexinit: first_kex_follows 0 11812: debug2: kex_parse_kexinit: reserved 0 11812: debug2: mac_init: found hmac-md5 11812: debug1: kex: server->client aes128-cbc hmac-md5 none 11812: debug2: mac_init: found hmac-md5 11812: debug1: kex: client->server aes128-cbc hmac-md5 none 11812: debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent 11812: debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP 11812: debug1: dh_gen_key: priv key bits set: 135/256 11812: debug1: bits set: 1573/3191 11812: debug1: SSH2_MSG_KEX_DH_GEX_INIT sent 11812: debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY 11812: debug1: Host '10.7.123.2' is known and matches the RSA host key. 11812: debug1: Found key in /home/alor/.ssh/known_hosts:2 11812: debug1: bits set: 1589/3191 11812: debug1: ssh_rsa_verify: signature correct 11812: debug1: kex_derive_keys 11812: debug1: newkeys: mode 1 11812: debug1: SSH2_MSG_NEWKEYS sent 11812: debug1: waiting for SSH2_MSG_NEWKEYS 11812: debug1: newkeys: mode 0 11812: debug1: SSH2_MSG_NEWKEYS received 11812: debug1: done: ssh_kex2. 11812: debug1: send SSH2_MSG_SERVICE_REQUEST 11812: debug1: service_accept: ssh-userauth 11812: debug1: got SSH2_MSG_SERVICE_ACCEPT 11812: debug1: authentications that can continue: publickey,password,keyboard-interactive 11812: debug1: next auth method to try is publickey 11812: debug1: try privkey: /home/alor/.ssh/identity 11812: debug1: try pubkey: /home/alor/.ssh/id_rsa 11812: debug2: we sent a publickey packet, wait for reply 11812: debug1: authentications that can continue: publickey,password,keyboard-interactive 11812: debug1: try privkey: /home/alor/.ssh/id_dsa 11812: debug2: we did not send a packet, disable method 11812: debug1: next auth method to try is keyboard-interactive 11812: debug2: userauth_kbdint 11812: debug2: we sent a keyboard-interactive packet, wait for reply 11812: debug1: authentications that can continue: publickey,password,keyboard-interactive 11812: debug2: we did not send a packet, disable method 11812: debug1: next auth method to try is password alor@10.7.123.2's password: 11812: debug2: we sent a password packet, wait for reply 11812: debug1: ssh-userauth2 successful: method password 11812: debug1: channel 0: new [client-session] 11812: debug1: send channel open 0 11812: debug1: Entering interactive session. 11812: debug2: callback start 11812: debug1: ssh_session2_setup: id 0 11812: debug1: channel request 0: pty-req 11812: debug1: channel request 0: shell 11812: debug1: fd 3 setting TCP_NODELAY 11812: debug2: callback done 11812: debug1: channel 0: open confirm rwindow 0 rmax 32768 11812: debug1: channel_free: channel 0: client-session, nchannels 1 Connection to 10.7.123.2 closed by remote host. Connection to 10.7.123.2 closed. 11812: debug1: Transferred: stdin 0, stdout 0, stderr 83 bytes in 0.2 seconds 11812: debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 553.0 11812: debug1: Exit status -1
Am Mi, den 29.09.2004 schrieb Alor um 11:55:
alor@minsc:~> ssh -vv 10.7.123.2 OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f
11812: debug1: Remote protocol version 1.99, remote software version OpenSSH_3.6.1p2 11812: debug1: match: OpenSSH_3.6.1p2 pat OpenSSH* 11812: Enabling compatibility mode for protocol 2.0 11812: debug1: Local version string SSH-2.0-OpenSSH_3.4p1
How is that a topic for the test list? From OpenSSH version numbers I do not see any Fedora Core test release involved.
Alexander
How is that a topic for the test list? From OpenSSH version numbers I do not see any Fedora Core test release involved.
I`m testing FC3 test2 but client machine on FC1.
It had been OK as I uncommented next lines in /etc/sshd_config :
HostKey /etc/ssh/ssh_host_key HostKey /etc/ssh/ssh_host_rsa_key
Thanks.
Best Regards, Alor.
Am Mi, den 29.09.2004 schrieb Alor um 19:13:
How is that a topic for the test list? From OpenSSH version numbers I do not see any Fedora Core test release involved.
I`m testing FC3 test2 but client machine on FC1.
FC3t2 has openssh-server-3.9p1-3.i386.rpm, not version 3.6.1p2. So its hardly an FC3t2 machine your are connecting. The string from debug mode matches an FC2. Else it should have appeared
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1 debug1: match: OpenSSH_3.9p1 pat OpenSSH*
It had been OK as I uncommented next lines in /etc/sshd_config :
HostKey /etc/ssh/ssh_host_key
You better want to avoid SSH protocol version 1 for security reasons.
HostKey /etc/ssh/ssh_host_rsa_key
I wonder, because those are default settings, active regardless they are commented. See the comment in the sshd_config itself:
# The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options change a # default value.
Alor.
Alexander
Am Mi, den 29.09.2004 um 19:44 +0200, Alexander Dalloz schrieb:
HostKey /etc/ssh/ssh_host_rsa_key
I wonder, because those are default settings, active regardless they are commented.
I'm too. But while this line is commented connect allow only for root if it permitted.
Alor.
Nobody with any advice? Anyone else have one of these new Intel motherboards with sound working in FC3T2?
I've now compiled the alsa-drivers and tried modprobing the azx driver, which works, and things seem to work (programs don't complain about no sound card and such), except I hear nothing. alsamixer does not show the sound muted, so I don't think that's the problem. system-config-soundcard still says "No soundcards detected." :-(
Thanks!
Ciao! Ryan
On Tue, 28 Sep 2004 15:09:14 -0700, Mister Ribbit mister.ribbit@gmail.com wrote:
I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
Try a logout/login of gnome. Can you play soundfiles using the "aplay" or "ogg123" commands from the comandline after loading the modules? If yes, go off editing /etc/modprobe.conf.
tor, 30.09.2004 kl. 06.21 skrev Mister Ribbit:
Nobody with any advice? Anyone else have one of these new Intel motherboards with sound working in FC3T2?
I've now compiled the alsa-drivers and tried modprobing the azx driver, which works, and things seem to work (programs don't complain about no sound card and such), except I hear nothing. alsamixer does not show the sound muted, so I don't think that's the problem. system-config-soundcard still says "No soundcards detected." :-(
Thanks!
Ciao! Ryan
On Tue, 28 Sep 2004 15:09:14 -0700, Mister Ribbit mister.ribbit@gmail.com wrote:
I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
A logout/login doesn't seem to fix it. As for aplay, it doesn't complain, but I get no sound.
Thanks for the suggestions! Should I try filing a bug somewhere?
Ciao! Ryab
On Thu, 30 Sep 2004 12:50:46 +0200, Kyrre Ness Sjobak kyrre@solution-forge.net wrote:
Try a logout/login of gnome. Can you play soundfiles using the "aplay" or "ogg123" commands from the comandline after loading the modules? If yes, go off editing /etc/modprobe.conf.
tor, 30.09.2004 kl. 06.21 skrev Mister Ribbit:
Nobody with any advice? Anyone else have one of these new Intel motherboards with sound working in FC3T2?
I've now compiled the alsa-drivers and tried modprobing the azx driver, which works, and things seem to work (programs don't complain about no sound card and such), except I hear nothing. alsamixer does not show the sound muted, so I don't think that's the problem. system-config-soundcard still says "No soundcards detected." :-(
Thanks!
Ciao! Ryan
On Tue, 28 Sep 2004 15:09:14 -0700, Mister Ribbit mister.ribbit@gmail.com wrote:
I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
Hmm... maybe you should. I would suggest "kernel".
You said aplay dont complain. Did you give it a file to play? ie. aplay /path/to/wawe.waw ? In alsamixer, are the volumes turned up? Does modprobe snd-??? give any messages? lsmod? can you get any sound out of ogg123?
Kyrre
tor, 30.09.2004 kl. 20.22 skrev Mister Ribbit:
A logout/login doesn't seem to fix it. As for aplay, it doesn't complain, but I get no sound.
Thanks for the suggestions! Should I try filing a bug somewhere?
Ciao! Ryab
On Thu, 30 Sep 2004 12:50:46 +0200, Kyrre Ness Sjobak kyrre@solution-forge.net wrote:
Try a logout/login of gnome. Can you play soundfiles using the "aplay" or "ogg123" commands from the comandline after loading the modules? If yes, go off editing /etc/modprobe.conf.
tor, 30.09.2004 kl. 06.21 skrev Mister Ribbit:
Nobody with any advice? Anyone else have one of these new Intel motherboards with sound working in FC3T2?
I've now compiled the alsa-drivers and tried modprobing the azx driver, which works, and things seem to work (programs don't complain about no sound card and such), except I hear nothing. alsamixer does not show the sound muted, so I don't think that's the problem. system-config-soundcard still says "No soundcards detected." :-(
Thanks!
Ciao! Ryan
On Tue, 28 Sep 2004 15:09:14 -0700, Mister Ribbit mister.ribbit@gmail.com wrote:
I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
I'll file a bug in "kernel", I suppose.
I tried playing a wave file with aplay, yes. As for volume, alsamixer only shows me two bars with this device, namely master and capture. Turning both all the way up does not help. modprobe does not complain when I install the snd-azx module, and lsmod just shows the snd-azx and all the other snd modules it needs loaded into memory. Nothing fishy.
I can't get sounds out of anything, using ALSA or OSS or anything.
Thanks!
Ciao! Ryan
On Thu, 30 Sep 2004 20:36:47 +0200, Kyrre Ness Sjobak kyrre@solution-forge.net wrote:
Hmm... maybe you should. I would suggest "kernel".
You said aplay dont complain. Did you give it a file to play? ie. aplay /path/to/wawe.waw ? In alsamixer, are the volumes turned up? Does modprobe snd-??? give any messages? lsmod? can you get any sound out of ogg123?
Kyrre
tor, 30.09.2004 kl. 20.22 skrev Mister Ribbit:
A logout/login doesn't seem to fix it. As for aplay, it doesn't complain, but I get no sound.
Thanks for the suggestions! Should I try filing a bug somewhere?
Ciao! Ryab
On Thu, 30 Sep 2004 12:50:46 +0200, Kyrre Ness Sjobak kyrre@solution-forge.net wrote:
Try a logout/login of gnome. Can you play soundfiles using the "aplay" or "ogg123" commands from the comandline after loading the modules? If yes, go off editing /etc/modprobe.conf.
tor, 30.09.2004 kl. 06.21 skrev Mister Ribbit:
Nobody with any advice? Anyone else have one of these new Intel motherboards with sound working in FC3T2?
I've now compiled the alsa-drivers and tried modprobing the azx driver, which works, and things seem to work (programs don't complain about no sound card and such), except I hear nothing. alsamixer does not show the sound muted, so I don't think that's the problem. system-config-soundcard still says "No soundcards detected." :-(
Thanks!
Ciao! Ryan
On Tue, 28 Sep 2004 15:09:14 -0700, Mister Ribbit mister.ribbit@gmail.com wrote:
I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
Am Donnerstag, den 30.09.2004, 11:22 -0700 schrieb Mister Ribbit:
A logout/login doesn't seem to fix it. As for aplay, it doesn't complain, but I get no sound.
You of course unmuted Master- and PCM-Volume with alsamixer? (Maybe someone suggested this already, if, please forgive me)
Thanks for the suggestions! Should I try filing a bug somewhere?
I tried this today on another intel board and failed also until now. Seems merely and upstream issue ATM AFAICS.
Cu thl
On Thu, 30 Sep 2004 12:50:46 +0200, Kyrre Ness Sjobak kyrre@solution-forge.net wrote:
Try a logout/login of gnome. Can you play soundfiles using the "aplay" or "ogg123" commands from the comandline after loading the modules? If yes, go off editing /etc/modprobe.conf.
tor, 30.09.2004 kl. 06.21 skrev Mister Ribbit:
Nobody with any advice? Anyone else have one of these new Intel motherboards with sound working in FC3T2?
I've now compiled the alsa-drivers and tried modprobing the azx driver, which works, and things seem to work (programs don't complain about no sound card and such), except I hear nothing. alsamixer does not show the sound muted, so I don't think that's the problem. system-config-soundcard still says "No soundcards detected." :-(
Thanks!
Ciao! Ryan
On Tue, 28 Sep 2004 15:09:14 -0700, Mister Ribbit mister.ribbit@gmail.com wrote:
I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
I only have a Master, no PCM with this device. Not sure why the mixer is so sparse (I assume because the driver is in its infant stages), but no changes in the mixer seem to help.
What do you mean by this being an upstream issue?
Thanks!
Ciao! Ryan
On Thu, 30 Sep 2004 20:46:30 +0200, Thorsten Leemhuis fedora@leemhuis.info wrote:
Am Donnerstag, den 30.09.2004, 11:22 -0700 schrieb Mister Ribbit:
A logout/login doesn't seem to fix it. As for aplay, it doesn't complain, but I get no sound.
You of course unmuted Master- and PCM-Volume with alsamixer? (Maybe someone suggested this already, if, please forgive me)
Thanks for the suggestions! Should I try filing a bug somewhere?
I tried this today on another intel board and failed also until now. Seems merely and upstream issue ATM AFAICS.
Cu thl
On Thu, 30 Sep 2004 12:50:46 +0200, Kyrre Ness Sjobak kyrre@solution-forge.net wrote:
Try a logout/login of gnome. Can you play soundfiles using the "aplay" or "ogg123" commands from the comandline after loading the modules? If yes, go off editing /etc/modprobe.conf.
tor, 30.09.2004 kl. 06.21 skrev Mister Ribbit:
Nobody with any advice? Anyone else have one of these new Intel motherboards with sound working in FC3T2?
I've now compiled the alsa-drivers and tried modprobing the azx driver, which works, and things seem to work (programs don't complain about no sound card and such), except I hear nothing. alsamixer does not show the sound muted, so I don't think that's the problem. system-config-soundcard still says "No soundcards detected." :-(
Thanks!
Ciao! Ryan
On Tue, 28 Sep 2004 15:09:14 -0700, Mister Ribbit mister.ribbit@gmail.com wrote:
I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
-- Thorsten Leemhuis fedora@leemhuis.info
Am Freitag, den 01.10.2004, 09:19 -0700 schrieb Mister Ribbit:
I only have a Master, no PCM with this device.
Odd. Don't know if this is normal with hdaudio.
[...]
What do you mean by this being an upstream issue?
Means: I think (but may be wrong) nobody at redhat or from the fedora community will do anything about it ATM. So it's better to file a bug at the kernel bugzilla course there is no driver for it in the kernel ATM.
But thats also not the best idea (I think) course the alsa people are working on audio-drivers in the kernel and they also have a Bug-tracking system online -- so there may be the best place.
But maybe even that is wasted time as it seems they are working on azalia-drivers already. And if they are ready they will land in the kernel sooner or later, and then they'll land in fedora sooner or later on it own. ;-)
HTH
CU thl
On Thu, 30 Sep 2004 20:46:30 +0200, Thorsten Leemhuis fedora@leemhuis.info wrote:
Am Donnerstag, den 30.09.2004, 11:22 -0700 schrieb Mister Ribbit:
A logout/login doesn't seem to fix it. As for aplay, it doesn't complain, but I get no sound.
You of course unmuted Master- and PCM-Volume with alsamixer? (Maybe someone suggested this already, if, please forgive me)
Thanks for the suggestions! Should I try filing a bug somewhere?
I tried this today on another intel board and failed also until now. Seems merely and upstream issue ATM AFAICS.
Cu thl
On Thu, 30 Sep 2004 12:50:46 +0200, Kyrre Ness Sjobak kyrre@solution-forge.net wrote:
Try a logout/login of gnome. Can you play soundfiles using the "aplay" or "ogg123" commands from the comandline after loading the modules? If yes, go off editing /etc/modprobe.conf.
tor, 30.09.2004 kl. 06.21 skrev Mister Ribbit:
Nobody with any advice? Anyone else have one of these new Intel motherboards with sound working in FC3T2?
I've now compiled the alsa-drivers and tried modprobing the azx driver, which works, and things seem to work (programs don't complain about no sound card and such), except I hear nothing. alsamixer does not show the sound muted, so I don't think that's the problem. system-config-soundcard still says "No soundcards detected." :-(
Thanks!
Ciao! Ryan
On Tue, 28 Sep 2004 15:09:14 -0700, Mister Ribbit mister.ribbit@gmail.com wrote:
I have the new Intel HD Audio on board my Intel D915GEV motherboard, and I'm trying to get it working. I think I can do it if I compile the driver that Intel supplies on their web page, but they say that the driver has been handed off to the ALSA project, and I've found it in the alsa-driver 1.0.6 package (but not 1.0.5). I was wondering if FC3 would ship with an updated kernel to have the 1.0.6 driver (or the new 1.0.6a) so that it would be working straight out of the box in the future. Or, maybe you are on that set of drivers, and somehow have lost the azx driver for this hardware.
-- Thorsten Leemhuis fedora@leemhuis.info
-
Alexander Dalloz -
Alor -
Kyrre Ness Sjobak -
Mister Ribbit -
Ow Mun Heng -
Thorsten Leemhuis -
Аlor