[hsflinux] Various problems with the new driver for AMD64 on
SuSE 9.0 and 9.1
Linuxant support (Jonathan)
support at linuxant.com
Wed Dec 22 15:48:26 EST 2004
Hi,
for SuSE 9.0, we are aware of this build problem and it will be fixed in
the next release of the driver.
For the multiple problems on SuSE 9.1, please generate and send us 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 at linuxant.com
patheve2 wrote:
> Hello
>
> On my laptop (Asus L5DF with Athlon64 and chipset nForce 3 150), I am
> trying to install this new
> driver. My two systems : SuSE 9.0 AMD64 (kernel 2.4.21-260) and SuSE 9.1
> AMD64 (kernel
> 2.6.8-24.5 coming from SuSE 9.2). Hereafter the various problem per
> system :
>
> 1- SuSE 9.0 :
> ============
>
> The detailed informations during installation :
>
> ===
> rpm -ivh hsfmodem-7.18.00.01x86_64full-1.x86_64.rpm
> warning: hsfmodem-7.18.00.01x86_64full-1.x86_64.rpm: V3 DSA signature:
> NOKEY, key ID 5dfbf7dc
> Preparing... ###########################################
> [100%]
> Removing old /etc/hsfmodem
> Removing old /usr/lib/hsfmodem
> 1:hsfmodem ###########################################
> [100%]
> Conexant HSF softmodem driver, version 7.18.00.01x86_64full
>
> If you need license keys, assistance or more information, please go to:
> http://www.linuxant.com/
>
> When reporting a problem for the first time, please send
> us the file generated by "hsfconfig --dumpdiag".
>
> No pre-built modules for: SuSE-9.0 linux-2.4.21-260-default x86_64
>
> Trying to automatically build the driver modules...
> (this requires a C compiler and proper kernel sources to be installed)
>
> Building modules for kernel 2.4.21-260-default, using source directory
> /lib/modules/2.4.21-260-default/build. Please wait...
>
> ERROR: Module build failed!
> Please examine the log file "/tmp/hsfconfig-buildlog.txt" to determine why.
> error: %post(hsfmodem-7.18.00.01x86_64full-1) scriptlet failed, exit
> status 1
> ===
>
> And in the hsfconfig-buildlog.txt file, there's this :
>
> ===
> rm -rf *.o GPL/*.o *.ko GPL/*.ko *.mod.c GPL/*.mod.c .*.cmd GPL/.*.cmd
>
> GCC -DEXPORT_SYMTAB -o mod_osspec.o mod_osspec.c
>
> GCC -o osservices.o osservices.c
> osservices.c: In function `OsForkWait':
> osservices.c:751: error: too many arguments to function
> `call_usermodehelper_R84a291c8'
> osservices.c: In function `OsInit':
> osservices.c:1196: warning: int format, different type arg (arg 2)
> osservices.c:1196: warning: int format, different type arg (arg 3)
> make: *** [osservices.o] Error 1
> ===
>
> How to solve this problem. No idea :-) ?
>
>
> 2- SuSE 9.1 :
> ===========
>
> The detailed informations during installation :
>
> ===
> rpm -ivh hsfmodem-7.18.00.01x86_64full-1.x86_64.rpm
> warning: hsfmodem-7.18.00.01x86_64full-1.x86_64.rpm: V3 DSA signature:
> NOKEY, key ID 5dfbf7dc
> Preparing... ###########################################
> [100%]
> 1:hsfmodem ###########################################
> [100%]
> Conexant HSF softmodem driver, version 7.18.00.01x86_64full
>
> If you need license keys, assistance or more information, please go to:
> http://www.linuxant.com/
>
> When reporting a problem for the first time, please send
> us the file generated by "hsfconfig --dumpdiag".
>
> No pre-built modules for: SuSE-9.1 linux-2.6.8-24.5-default x86_64
>
> Trying to automatically build the driver modules...
> (this requires a C compiler and proper kernel sources to be installed)
>
> Building modules for kernel 2.6.8-24.5-default, using source directory
> /lib/modules/2.6.8-24.5-default/build. Please wait...
> done.
>
> Automatically guessed region (using timezone): "FRANCE"
>
> Setting region for modem unit 0: "FRANCE"
>
> To change, use "hsfconfig --region" or "AT+GCI=<T35code>"
> The current region can be displayed by entering "ATI9" in a terminal
> program.
>
> Note: kernel module snd-via82xx-modem overridden by hsfmc97via
> Note: kernel module snd-intel8x0m overridden by hsfmc97ich hsfmc97sis
> Note: kernel module snd-atiixp-modem overridden by hsfmc97ati
>
> Current parameters: ("hsfconfig --info")
>
> Config for modem unit 0: /dev/ttySHSF0
> Device instance: 0-PCI-10de:00d9-1043:1856
> HW revision : CXT22
> HW profile name: hsfmc97ich
> Registration ID: 10B3-4CB2-40A3
> License owner : unknown
> License key : FREE
> License status : FREE (max 14.4kbps data only)
> Current region : FRANCE (T.35 code: 003D)
>
> The /dev/modem alias (symlink) points to /dev/ttySHSF0
>
> To enable full 56K modem and FAX functionality, enter your license
> information
> with "hsfconfig --license".
>
> License owner and key data must EXACTLY match the information respectively
> provided to and by Linuxant. Otherwise, license status will remain "FREE"!
> ===
>
> In fine, the device ttySHSF0 did not exist, the first one was ttySHSF2
> (ttyS0 is for the serial port, ttyS1 is for irda
> port). I deleted the original link modem and did an other symbolic link
> with ttySHSF2 ..... but no answer with wvdial
> or kppp. Hummm .... So, why not to perform a reboot .... and I got this
> (according to dmesg) :
>
> ===
> hsfengine: module license 'see LICENSE file distributed with driver'
> taints kernel.
> ACPI: PCI interrupt 0000:00:06.1[B] -> GSI 10 (level, low) -> IRQ 10
> PCI: Setting latency timer of device 0000:00:06.1 to 64
> HSF: ERROR: not a Conexant modem<3>
> cnxthsf_cnxt_serial_add: ComCtrlOpen failed (1)
> hsfich: probe of 0000:00:06.1 failed with error -5
> ===
>
> About loaded modules, according to lsmod :
>
> ===
> hsfusbcd2 77744 0
> hsfmc97sis 68264 0
> hsfmc97ati 66072 0
> hsfmc97ali 73376 0
> hsfmc97via 69296 0
> hsfmc97ich 71848 0
> hsfpcibasic2 76200 0
> hsfserial 24740 7
> hsfusbcd2,hsfmc97sis,hsfmc97ati,hsfmc97ali,hsfmc97via,hsfmc97ich,hsfpcibasic2
>
> hsfengine 1631104 1 hsfserial
> hsfosspec 114576 9
> hsfusbcd2,hsfmc97sis,hsfmc97ati,hsfmc97ali,hsfmc97via,hsfmc97ich,hsfpcibasic2,hsfserial,hsfengine
>
> usbcore 122368 8
> usbserial,usbhid,ehci_hcd,ohci_hcd,hsfusbcd2,hsfosspec
> hsfsoar 65192 7
> hsfusbcd2,hsfmc97sis,hsfmc97ati,hsfmc97ali,hsfmc97via,hsfmc97ich,hsfpcibasic2
>
> ===
>
> And the device ttySHFS2 disappeared after reboot !!! So, I used
> "hsfconfig" and rebuilt all the devices. The link modem -> ttySHSF0 is
> right and wvdial or kppp give an answer when /dev/modem is i
> interrogated. With Yast, I can configure a PPP connection for kinternet.
> And it works fine : I can surf on the web after PPP connection. I can
> use NOW the internal modem !! ...... But after a second reboot, I can
> see the same error messages during boot and some ttySHSF devices
> disappeared. I have to use hsfconfig and regenerate these devices
> or stop then restart the process (/etc/rc.d/hsf stop, /etc/rc.d/hsf
> start) => how to explain such a behaviour ? Is it a bug or something else ?
>
> Thanks for your help
>
> Regards
>
> Pascal
>
>
>
> _______________________________________________
> hsflinux mailing list
> hsflinux at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/hsflinux
More information about the hsflinux
mailing list