[hsflinux] Problem installing beta02110301

[Tony Earnshaw]

tir, 2002-11-05 kl. 10:35 skrev Brian Dolan:


> Below are the contents of the file "hsfconfig-buildlog.txt".
> Apparently there is a problem with trying to compile "linuxres.c"
> 
> Can anyone help?

Looks to me as if at least 1/3 of the barf has to do with power
management.

I can only refer to the FAQ, attached, which deals, apart from anything
else, with this question - as well as that of kernel versions.:

Best,

Tony

--

> -- hsfconfig-buildlog.txt follows--
> 
> rm -f *.o *.a
> make[1]: Entering directory `/usr/lib/hsf/modules/osspec'
> rm -f *.o *.a
> make[1]: Leaving directory `/usr/lib/hsf/modules/osspec'
> * Compiling mod_osspec.c
> make -C osspec all
> make[1]: Entering directory `/usr/lib/hsf/modules/osspec'
> * Compiling osmemory.c
> * Compiling osstring.c
> * Compiling osdebug.c
> * Compiling osfloat.c
> * Compiling osstdio.c
> * Compiling osmodule.c
> * Compiling osnvm.c
> * Compiling ostime.c
> * Compiling linuxres.c
> linuxres.c:112: parse error before `pm_request_t'
> linuxres.c:112: warning: `struct pm_dev' declared inside parameter list
> linuxres.c:112: warning: its scope is only this definition or declaration,
> linuxres.c:112: warning: which is probably not what you want.
> linuxres.c:113: warning: function declaration isn't a prototype
> linuxres.c: In function `linux_pm_callback':
> linuxres.c:114: `dev' undeclared (first use in this function)
> linuxres.c:114: (Each undeclared identifier is reported only once
> linuxres.c:114: for each function it appears in.)
> linuxres.c:121: `rqst' undeclared (first use in this function)
> linuxres.c:123: warning: unreachable code at beginning of switch statement
> linuxres.c: In function `cnxthsf_LinuxInitPowerManagement':
> linuxres.c:149: warning: passing arg 1 of `apm_register_callback' from incompatible pointer type
> linuxres.c:149: warning: assignment makes pointer from integer without a cast
> linuxres.c:151: dereferencing pointer to incomplete type
> linuxres.c:147: warning: unused variable `pcidev'
> linuxres.c: In function `cnxthsf_LinuxTermPowerManagement':
> linuxres.c:160: warning: passing arg 1 of `apm_unregister_callback' from incompatible pointer type
> make[1]: *** [linuxres.o] Error 1
> make[1]: Leaving directory `/usr/lib/hsf/modules/osspec'
> make: *** [osspec] Error 2
> 
> 
> -- End of hsfconfig-buildlog.txt --
> _______________________________________________
> hsflinux mailing list
> hsflinux at lists.mbsi.ca
> http://www.mbsi.ca/mailman/listinfo/hsflinux
-- 

Tony Earnshaw

Could have been Henrik Ibsen's, Ole Bull's,
Henrik Wergelands's, Camilla Collet's and more's
last words, but weren't: «Fanden helder, helder
det at have sadset, end det at ikke have sadset
i det hele taget.»

e-post:		tonni at billy.demon.nl
www:		http://www.billy.demon.nl



-------------- next part --------------


1) I have an HCF modem. Can I use these drivers?

	No, these drivers are only for the Conexant HSF (softmodem)
	family, not for the HCF (controllerless) chips.
	HCF drivers are available from http://www.mbsi.ca/cnxtlindrv/hcf

2) The modem returns "NO DIALTONE" when I try to dial

	Please check your line cord and country settings (with hsfconfig --country).
	If they are correct and the "NO DIALTONE" problems persist, you
	may try disabling dialtone detection with the "ATX3" command.

	If this still doesn't work, you should report the problem to us.

3) The modem returns CONNECT messages with bogus connection speeds, like
   "CONNECT 9600" or "CONNECT 115200"

	Use "ATW1" to enable reporting of line speed, error correction protocol
	and DTE speed. See the command set reference manual
	(100498D_RM_HxF_Released.pdf) for details.

4) The modem works, but I can't hear anything when dialing

	Please check the Ln and Mn settings in AT&V. They should be L1 and M1.
	If not, change them with the command: ATL1M1&W

	If you still cannot hear any call progress sounds, and use a
	modem model that does not have its own speaker (such as on a notebook),
	verify your audio mixer settings (using aumix or equivalent utility) to
	ensure that the volume levels are high enough and that the "PhoneIn"
	channel is not muted. 

	On modems (such as many MC97 units) requiring that call progress sound
	be extracted in software by the driver and played through the normal
	sound subsystem, no sound is presently available. We hope to implement
	it one day.

5) My modem's PCI ID is 127a:1025 or 127a:2005 and it doesn't work

	You probably should try the HCF driver. Some early HCF modems are
	incorrectly identified as HSF in some versions of the PCI ID lists
	used by lspci and the linux kernel. Also, a few modem vendors have
	tried to save costs by omitting the EEPROM where device IDs are stored,
	causing the same default ID built into the bus interface chip to be
	used for both HCF and HSF devices.

6) Changing serial port parameters with "setserial" on ttySHxF0 or /dev/modem
   doesn't work.

	Since this modem driver provides a virtual serial interface, which
	is not directly connected to a physical UART like a normal serial
	port, it is not possible and would not make sense to configure
	it with "setserial". Therefore you shouldn't use this command
	on the ports associated with this driver.

7) I installed the driver, and now the /dev/ttySHxF0 or /dev/modem device is
   supposed to be there but it doesn't exist.

	On devfs-based systems (such as Mandrake), the missing device
	node is often a sign that the driver modules didn't load or initialize
	properly. Try "modprobe hsfserial", then check the /var/log/messages
	file or or run "dmesg" to see any kernel error messages that could
	provide a clue as to why loading of the driver failed.

8) I have an ACPI-based machine and the driver is crashing or not loading

	It might be necessary to recompile a generic kernel from
	ftp.kernel.org with the latest ACPI (and perhaps also
	KACPID kernel lost interrupt) patches from
		http://sf.net/projects/acpi/

9) The modem disconnects or the system crashes as soon as or shortly after
   I start the graphical desktop (X, GNOME, KDE, etc..) or use the sound card.

	Some users have reported conflicts between certain sound card drivers,
	(especially AC97 devices) and our modem drivers. Most graphical
	desktops access sound devices when starting up.
	We are investigating these problems and are hoping to find solutions
	soon. Meanwhile, we recommend disabling any conflicting modules while
	you use the modem.  If you experience a conflict, please report it.