I would like to see ltmodem support out-the-box for boxed sets, and have 
working packages, that with drakconnect (on beta2) do most things right 
(drakconnect will install them when a ltmodem is found if they are 
accessible by urpmi).

The problem is still that drakconnect for some reason insists on making a 
link for /dev/modem (at present it asks you which of 8 serial ports to 
use, or if /usr/lib/libDrakx/network/modem.pm is patched, whatever device 
is listed there for ltmodem, in 9.1 this was ttyS14), and this breaks 
auto-loading of the lt_serial module (which works via 'alias /dev/modem 
lt_serial' in modules.conf, and registering the symlink via devfs).

With the current status, the modem will work fine after configuration by 
drakconnect (I assume it loads the module), but on next boot it is broken.

I can add 'lt_serial' to /etc/modules in %post instead, but this should 
not be necessary.

Can someone please fix this? (or make a better ltmodem package). Hmm, I 
have tried some fixes (to network/modem.pm), but am not sure I have tested 
correctly ... so I am not sure if my attempts to fix worked or not .. will 
need to test more before I submit a patch since it seems I will have to 
uninstall the ltmodem packages for each test, and you *must* reboot to see 
if it works afterwards.

Anyway, the current srpm can be found here:
http://ranger.dnsalias.com/mandrake/cooker/ltmodem-8.26a9-3mdk.src.rpm

(BTW, this is all on beta2 ... will try to update to cooker tomorrow)

Regards,
Buchan

-- 
|----------------Registered Linux User #182071-----------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************

Reply via email to