On Tue, 7 Dec 1999, Stephen P. Molnar, Ph.D. wrote:

> I replaced the slower isa modem on my Mandrake/Venus system with a pci 
> modem with a Lucent Technologies chip set.  I'm happy with the performance 
> in Win95, but am having trouble in Linux (I realize that I'mn the bleeding 
> edge, but there do seen to be a few people out there working on the problem).
> 
> I've just downloaded ltmodem-0_9_4-1.tar.gz.
> 
> Here's the make log:

exactly what magic compiler you got that doesn't use - for switches..?
 
> ilter.c o filter.o
> cc O2 g Wall W Wnoparentheses Wstrictprototypes Werror fcommon    c p

Anybody spot this guy as a windows coder other than me, pretty redundant
warnings no :)

[..]
> make: *** Warning:  Clock skew detected.  Your build may be 
> incomplete.
>
>
> In spite of the warning (which I don't understand) I ran make install.  The 
> log is:
> 
> make: *** Warning: File `Makefile' has modification time in the future 
> (944542811 > 944532775)

Somebody will correct me (i hope) if i'm wrong but thats EPOCH time(?),
the number of seconds elapsed sence (ummm, big blank) 1962?
(ok babble out of the way)

Notice how one is different from the other roughly 10,000 seconds.

cd /programs/src/whatever_i_snipped
find . |xargs touch

All better no more error, now "make distclean all" to rebuild 

[..]
> make: *** Warning:  Clock skew detected.  Your build may be incomplete.
> 
> 
> When I attempted to dial in to my ISP I got the following:
> 
> ltmodem version 0.9.4
> 00:14.0 Communication controller: Lucent Microelectronics Unknown 56K Modem 
> (rev 01)
> Mars chipset detected.
>       Subsystem: Unknown device 141b:9300
>       Flags: bus master, medium devsel, latency 0, IRQ 5
>       Region 0: Memory at e6000000 (32bit, nonprefetchable)
>       Region 1: I/O ports at e800
>       Region 2: I/O ports at ec00
>       Capabilities: [f8] Power Management version 1
> Initialising with ports at e800 and ec00, assuming portbase at ec00.
> Resetting modem...
> .....
> Init: read_dsp_ram did not set dp_byte_f to 1.
> io_task(3, (null), 0): not implemented.
> # Initializing modem... Resetting modem...
> RAM read errors detected, failure count: 2.
> .....
> Init: read_dsp_ram did not set dp_byte_f to 1.
> # fail

Looks like something that needs reported to them, but try it with a
coldboot and warmboot from windows and see if that has any effect.
also the io's should match your windows io, as apparently it's assumeing
them 
 
> Is it possible to get ltmodem to work?  Any help will be appreciated.

Yes it is.
 
> Thanks in advance.
> 
> Stephen P. Molnar, Ph.D.                      Life is a fuzzy set
> Foundation for Chemistry                      Stochastic and multivariant
> http://web.jadeinc.com/FoundationChem
> 

--
MandrakeSoft          http://www.mandrakesoft.com/
                                        --Axalon

Reply via email to