Hi,we can see the following information in the output of the 'hsfconfig --info' command:
--- Note: HDA support not compiled in the driver ---This is because the file '/lib/modules/2.6.25-gentoo-r7/extra/hsfhda.ko' is not present on your system. Perhaps this is a compilation issue, you should run the 'make' command in the '/usr/lib/hsfmodem/modules' directory to determine if the compilation of the 'hsfhda.ko' module is properly done or not.
Regards, Jonathan Technical specialist / Linuxant www.linuxant.com support@xxxxxxxxxxxx Robo Tronic wrote:
Hi, in these days I did some testing with the external alsa-driver-1.0.17 and linuxant's patch (alsa-driver-1.0.17-1.patch). The alsa-driver installation and patching worked perfectly, sound works and now scanModem is able to find my modem (see attached ModemData.txt). In spite of that, hsfconfig doesn't detect anything... I've tried two versions of hsfmodem package, "7.68.00.09x86_64full" and the latest "7.68.00.12x86_64full", but it's the same. Attached you can find "hsfconfig --dumpdiag" output from both package versions. About the questions asked in my previous email, I've found some answers by myself: Q1- Is the alsa-driver patch available only for the 1.0.17 release of alsa-driver or is there a version for older releases? A1- I've seen that on linuxant's site (http://www.linuxant.com/alsa-driver/) they were added patches also for alsa releases 1.0.16 and 1.0.15. Good. Q2- How can I know which alsa release is shipped within a particular kernel version before actually installing the kernel? A2- Issuing "cat /usr/src/linux/include/sound/version.h" displays alsa version. Hope to find a solution. Thank you, MarcoFrom: robotronic_2k@xxxxxxxxxxx To: support@xxxxxxxxxxxx CC: marvin.stodolsky@xxxxxxxxx; discuss@xxxxxxxxxxxxx; dep@xxxxxxxxx Subject: RE: Marco, Italy [eid-20080729-2f2] Date: Sat, 2 Aug 2008 00:00:03 +0200 Hi, thanks to your explanations I think that now the situation is a bit more clear for me. The problem is not related to a wrong version of "snd-hda-intel.ko". I am able to correctly compile and load the custom module provided with the hsfmodem package. There are two cases: 1) Unfortunately, when the custom module (and it's brother "snd-hda-codec.ko") is loaded, I don't see any codec#1 device, so the modem isn't detected. 2) When I use the default gentoo-kernel module "snd-hda-intel.ko" (which doesn't need "snd-hda-codec.ko"), I can access codec#1 but hsfconfig still doesn't detect anything. The latest "hsfdiag.txt" I've sent to you is related to this test case, where I've renamed the custom module "/lib/modules/2.6.25-gentoo-r6/updates/snd-hda-intel.ko" into "snd-hda-intel.ko.HSFORIG" and copied here (into "updates" directory) the original gentoo-kernel module ("snd-hda-intel.ko", 685433 bytes). For the first case, as you said before, I suppose the problem is because the functionality provided by the replacement module "is no longer being maintained, because of many technical issues. Basically, this feature no longer works on some 2.6.25 and will not work on 2.6.26 and future kernels". So that module is outdated or at least not functioning properly with my 2.6.25 kernel. I've just installed a brand new 2.6.26 kernel for testing and I confirm that in this scenario the module even fails to build. For the second case, I think the "only" problem is that the default alsa in-kernel driver lacks that little but essential alsa-driver patch. It seems that the only way to go is the first you told me, using the latest external alsa-driver-1.0.17 plus linuxant's patch. Given that, now there's the problem with Gentoo's policy to maintain only the in-kernel alsa driver, which on 2.6.25-r6 kernel is 1.0.16rc2 release. So, if I've understood all correctly and you don't have any other suggestions, I may involve in this (or a separate) discussion the Gentoo ALSA team, as you wish. Finally, some other questions come to my mind: - Is the alsa-driver patch available only for the 1.0.17 release of alsa-driver or is there a version for older releases? In Gentoo's masked software repository there's an external alsa-driver package which I can test, but it's 1.0.16 release, so the actual patch shouldn't be appropriate. - How can I know which alsa release is shipped within a particular kernel version before actually installing the kernel? - I still don't understand *who* refused linuxant's patch submission and why? Thanks, MarcoDate: Fri, 1 Aug 2008 11:28:24 -0400 From: support@xxxxxxxxxxxx To: robotronic_2k@xxxxxxxxxxx CC: marvin.stodolsky@xxxxxxxxx; discuss@xxxxxxxxxxxxx; dep@xxxxxxxxx Subject: Re: Marco, Italy [eid-20080729-2f2] Hi, snd-hda-codec.ko and snd-hda-intel.ko are both part of the HDA bus driver. This is the situation with older versions of alsa-driver, nowadays, all the snd-hda-codec.ko code is in the snd-hda-intel.ko module so the snd-hda-codec.ko module is no longer present. If 'modprobe snd-hda-intel' doesn't automatically load snd-hda-codec, then you don't need it. The vanilla Linux kernel comes with its own version of alsa-driver. I doubt that this is an init. script issue, I think it could be the wrong snd-hda-intel.ko module that is loaded. Note that when you manually compile alsa-driver, the modules will be copied in '/lib/modules/$kernel_ver/kernel/sound'.I can see these modules in the '/lib/modules/$kernel_ver/updates' directory: --- -rw-r--r-- 1 root root 499740 Jul 28 21:10 snd-hda-codec.ko -rw-r--r-- 1 root root 685433 Jul 29 21:57 snd-hda-intel.ko -rw-r--r-- 1 root root 30087 Jul 28 21:10 snd-hda-intel.ko.HSFORIG --- It is important to note that modules in the 'updates' directory always have priority over the other modules, this is a hardcoded behavior in depmod. If the patched alsa-driver installation was successful, you should try to use these commands as root: --- mv /lib/modules/2.6.25-gentoo-r6/updates/* /root depmod hsfconfig --- You should say "yes" to the hsfconfig attempt to recompile the modules. Regards, Jonathan Technical specialist / Linuxant www.linuxant.com support@xxxxxxxxxxxx Robo Tronic wrote:Hi, I've attached the required log file. In this situation I've noticed that the kernel module "snd-hda-codec.ko" is no longer automatically loaded. If could be of some help, at boot time the alsasound init script is executed before hsf init script. I've tried to switch the init scripts order but it's the same: codec#1 is present but no modem detected. I've also tried to manually load at the end the missing codec module with "insmod /lib/modules/2.6.25-gentoo-r6/updates/snd-hda-codec.ko" but the result doesn't change. BTW, I didn't understand if "snd-hda-codec.ko" is a required integral part of HSF drivers or if it is something optional... When you said that the patch was submitted to the ALSA team, did you intend the Gentoo ALSA team or the developers at alsa-project.org? I suppose the first, otherwise I don't explain why the latest "alsa-driver-1.0.17" is still available and actively updated on alsa-project.org... I suppose it's a Gentoo-only choice to concentrate in developing the in-kernel driver and abandoning the external package, isn't it? With your help, once diagnosed the problem, it'll be great to involve the Gentoo ALSA team and suggest them to think about including the patch into gentoo-kernel sources. Unfortunately, I don't have any knowledge to try it by myself, but I'll be glad in helping the community with some testing or debugging! Let me know if you need something else. Thank you, MarcoDate: Wed, 30 Jul 2008 11:00:41 -0400 From: support@xxxxxxxxxxxx To: robotronic_2k@xxxxxxxxxxx CC: marvin.stodolsky@xxxxxxxxx; discuss@xxxxxxxxxxxxx; dep@xxxxxxxxx Subject: Re: Marco, Italy [eid-20080729-2f2] Hi, the relationship between the HSF driver and alsa-driver is only relevant for HDA modems. The problem is that essentially, the HSF driver provides a codec driver for the HDA modem but unlike the AC97 bus, there is no way with the current alsa-driver HDA design to provide a codec driver as a separate/external module. So we have to replace the snd-hda-intel.ko (and snd-hda-codec.ko if present) with a custom version in order to support HDA modems. The HSF driver has a built-in version of the HDA bus driver based on alsa-driver in order to easily replace the snd-hda-intel.ko module on the machine of the user. This functionality is no longer being maintained, because of many technical issues. Basically, this feature no longer works on some 2.6.25 and will not work on 2.6.26 and future kernels. Patching the alsa-driver package is now the way to go. The patch was submitted to the ALSA development team but was refused, since it as now easier to load a binary only (the HSF driver proprietary modules) into the kernel. However, you could always ask Gentoo developers if they could not add our patch to their kernels, it will greatly help all HSF HDA users. The patch is available at: http://www.linuxant.com/alsa-driver/ and we will continue to update the patch to make it work on newer alsa-driver releases when they come out. It is possible that the patch provided on our web site can be directly applied to the kernel, but this possibility has not been tested, this is something you could try out. For the "codec#1 file is present but the HSF driver is not working" problem, I will need more information. While you have this problem, please send us the output of the output of 'dumpdiag'. Type the following in a root shell: --- hsfconfig --dumpdiag --- Just send us the generated file located in /tmp ('hsfdiag.txt'). It'll help us solve the problem. Regards, Jonathan Technical specialist / Linuxant www.linuxant.com support@xxxxxxxxxxxx Robo Tronic wrote:First of all, thank you both for your precious time: I really appreciate that. I admit that I am a bit confused about the behavior of HSF driver and alsa-driver, and I really don't know anything about what there's "under the cover". Anyway I tried a little, probably silly, thing... Since with the original gentoo snd-hda-intel.ko kernel module the modem seems to be recognized (codec#1 is present), I've replaced the module created by hsfconfig into "/lib/modules/2.6.25-gentoo-r6/updates" with the original version and rebooted the system. Now the audio works well (it always worked), I can see codec#1 *but* hsfconfig still doesn't recognize the modem: isn't that strange or my test is totally meaningless? About the tailored alsa-driver-linuxant, I wished to give it a try but unfortunately I've found that the use of alsa-driver on Gentoo Linux is deprecated and not supported anymore: the package is hard-masked in the portage repository and is not maintained or updated, as stated from the Gentoo Linux ALSA Guide (http://www.gentoo.org/doc/en/alsa-guide.xml): ----- "Historically, Gentoo offered two ways to get ALSA up and running: the in-kernel driver and the external alsa-driver package. The two solutions essentially do the same thing; this made supporting the external package extremely difficult and time-consuming. The Gentoo maintainers decided to discontinue support for the alsa-driver package, concentrating their resources on the ALSA drivers available within the Linux kernel. This guide will focus solely on configuring ALSA via the in-kernel driver. If you still require the alsa-driver package, please email the Gentoo ALSA maintainers with why the in-kernel drivers don't work for you. Be sure to include detailed error logs." ----- I know that this is not a Linuxant problem, but is eventually possible to include the patch into the in-kernel drivers? Could I hope that one day this issue will be fixed without the need of the external alsa-driver package? I'll ask you before to understand if this could be a good reason for eventually contacting the Gentoo ALSA team. And... Given my "test" results, are we sure that alsa-driver-linuxant will really do the trick? Tomorrow I will try to build a slightly new kernel version, from 2.6.25-gentoo-r6 to 2.6.25-gentoo-r7 and see what happens. Finally, a question about scanModem: when codec#1 is available, why doesn't the script find anything? Many thanks again, Marco ----------------------------------------Date: Tue, 29 Jul 2008 14:36:40 -0400 From: support@xxxxxxxxxxxx To: marvin.stodolsky@xxxxxxxxx CC: robotronic_2k@xxxxxxxxxxx; discuss@xxxxxxxxxxxxx; dep@xxxxxxxxx Subject: Re: Fwd: Marco, Italy [eid-20080729-2f2] Hi, it's a better idea to install alsa-driver-linuxant first but it can be installed after the HSF driver without any problems. Note however that some pre-compiled HSF driver packages do have an explicit dependency on alsa-driver-linuxant, in this case, it's necessary to install alsa-driver-linuxant first. Regards, Jonathan Technical specialist / Linuxant www.linuxant.com support@xxxxxxxxxxxx Marvin Stodolsky wrote:Jonathan, Should the alsa-driver-linuxant be installed before the hsfmodem package? Or doesn't it make a difference? MarvS On Tue, Jul 29, 2008 at 11:09 AM, Linuxant support (Jonathan) wrote:Hi, Marco has correctly identified the problem, since the file /proc/asound/card0/codec#1 is no longer present, the modem is not detected at all on the HDA bus. The HSF driver provides it's own HDA bus driver but it's getting outdated, using alsa-driver-linuxant is recommended now: http://www.linuxant.com/alsa-driver/ Hopefully with an up-to-date alsa-driver, the modem will be detected. Regards, Jonathan Technical specialist / Linuxant www.linuxant.com support@xxxxxxxxxxxx Marvin Stodolsky wrote:Jonathan, This is a HDA based conexant chip modem. Please advise Marco MarvS ---------- Forwarded message ---------- From: RoboTronic Date: Mon, Jul 28, 2008 at 4:43 PM Subject: Marco, Italy To: discuss@xxxxxxxxxxxxx Hi, I have a Dell Inspiron 1720 laptop and I am not able to configure the internal modem on my Gentoo Linux box. It's clearly an hsfmodem but since scanModem hasn't detected any modem card, I've booted into Windows Vista Home Premium and collected some info about the device: -------------------------------------------------------------------------------- *** Modem Diagnostics: ATQ0V1E0 - OK AT+GMM - +GMM: Conexant HDA D330 MDC V.92 Modem AT+FCLASS=? - 0,1 AT#CLS=? - Not supported AT+GCI? - +GCI: 59 AT+GCI=? - +GCI: (00,01,02,03,04,05,06,07,09,0A,0B,0C,0D,0E,0F,10,11,12,13,14,15,16,19,1A,1B,1C,1D,1E,1F,20,21,22,23,24,25,26,27,28,29,2A,2B,2C,2D,2E,2F,30,31,32,33,34,35,36,37,38,39,3A,3B,3C,3D,3E,40,41,43,44,45,46,47,48,49,4B,4C,4D,4E,4F,50,51,52,53,54,55,56,57,58,59,5A,5B,5C,5E,5F,60,61,62,63,64,65,66,67,68,69,6A,6B,6C,6D,6E,6F,70,71,72,73,74,75,76,77,78,79,7A,7B,7C,7D,7E,7F,80,81,82,83,84,85,86,87,88,89,8A,8B,8C,8D,8E,8F,90,92,93,94,96,97,98,99,9A,9B,9C,9D,9E,9F,A0,A1,A2,A3,A4,A5,A6,A7,A8,A9,AA,AB,AC,AD,AE,AF,B0,B1,B2,B3,B4,B5,B6,B7,B8,B9,BA,BB,BC,BD,BE,BF,C1,C2,C3,C4,C5,C7,C8,C9,CA,CB,CC,CD,CE,CF,D0,D1,D2,D3,D4,D5,D6,D7,D8,D9,DA,DB,DC,DD,DE,DF,E0,E1,E2,E3,E4,E5,E6,E7,E8,EB,EC,ED,EE,EF,F0,F1,F2,F3,F4,F5,F7,F8,F9,FA,FB,FC,FE) ATI1 - 255 ATI2 - OK ATI3 - SoftK56V_B2.1_V7.59.00 ATI4 - Conexant HDA D330 MDC V.92 Modem ATI5 - 089 ATI6 - SoftK56 CModem Version 12 Rksample Version 342 ATI7 - 255 -------------------------------------------------------------------------------- *** Modem Details: Hardware ID = HDAUDIO\FUNC_02&VEN_14F1&DEV_2C06&SUBSYS_14F1000F&REV_1000\4&23AD9263&0&0102 | |_ Vendor = 14F1 |_ Device = 2C06 |_ SubSys = 000f:14f1 Compatible IDs = HDAUDIO\FUNC_02&CTLR_VEN_8086&CTLR_DEV_284B&VEN_14F1&DEV_2C06&REV_1000 HDAUDIO\FUNC_02&CTLR_VEN_8086&VEN_14F1&DEV_2C06&REV_1000 HDAUDIO\FUNC_02&VEN_14F1&DEV_2C06&REV_1000 HDAUDIO\FUNC_02&CTLR_VEN_8086&CTLR_DEV_284B&VEN_14F1&DEV_2C06 HDAUDIO\FUNC_02&CTLR_VEN_8086&VEN_14F1&DEV_2C06 HDAUDIO\FUNC_02&VEN_14F1&DEV_2C06 HDAUDIO\FUNC_02&CTLR_VEN_8086&CTLR_DEV_284B&VEN_14F1 HDAUDIO\FUNC_02&CTLR_VEN_8086&VEN_14F1 HDAUDIO\FUNC_02&VEN_14F1 HDAUDIO\FUNC_02&CTLR_VEN_8086&CTLR_DEV_284B HDAUDIO\FUNC_02&CTLR_VEN_8086 HDAUDIO\FUNC_02&GF&VEN_14F1&DEV_2C06&SUBSYS_14F1000F&REV_1000 HDAUDIO\FUNC_02 Father = PCI\VEN_8086&DEV_284B&SUBSYS_01F21028&REV_02\3&2b8e0b4b&0&D8 Same level = HDAUDIO\FUNC_01&VEN_8384&DEV_76A0&SUBSYS_102801F2&REV_1002\4&23ad9263&0&0001 Driver = oem5.inf:HSF_MODEM:ModemX:7.59.0.0:hdaudio\func_02&ven_14f1&dev_2c06&subsys_14f1000f Driver Details = Version 7.59.0.0 (16-NOV-2006) [ Note: I've translated properties' names from Italian to English, probably there are some mistakes! ] -------------------------------------------------------------------------------- That particular vendor/device seems supported by hsf drivers but hsfconfig modem detection fails. Attached you can find scanModem and "hsfconfig --dumpdiag" output. The interesting thing I've found is that with the default Gentoo kernel module "snd_hda_intel" loaded, I am able to query codec#1: metalbox ~ # cat /proc/asound/card0/codec#1 Codec: Conexant ID 2c06 Address: 1 Vendor Id: 0x14f12c06 Subsystem Id: 0x14f1000f Revision Id: 0x100000 Modem Function Group: 0x2 Differently, after hsfmodem kernel modules installation, the codec#1 device disappears, and I'm left only with codec#0 (the sound card). I'm using the official Linuxant drivers, version 7.68.00.09 (x86_64). I've also tried Dell's OEM drivers (http://linux.dell.com/files/ubuntu/hardy/modem-drivers/hsf/hsfmodem-7.68.00.09x86_64oem.tar.gz), but nothing changes... Thanks in advance for your help, and feel free to ask if I've missed something in my explanation! Cheers, Marco_________________________________________________________________ Leggi la tua posta direttamente dal cellulare! http://windowslivemobile.msn.com/Homepage.aspx?lang=it-it_________________________________________________________________ Tutta la posta in un solo posto… scarica Windows Live Mail!!! http://get.live.com/wlmail/overview_________________________________________________________________ Windows Live Mail: il programma gratuito per gestire tutta la tua posta! http://get.live.com/wlmail/overview_________________________________________________________________ Leggi le tue mail sotto l’ombrellone con Windows Live Mobile!http://windowslivemobile.msn.com/BrowserServiceHotmail.aspx?lang=IT-IT
