dear sirs,
i used scanmodem and then followed the advice given...
all you may want to see of my stuff is enclosed
the modem worked once and then no more, a day later it worked several times, next day nothing happened, today nothing – one real moody device, innit?
modem runs smoothly under winxp
'timed out while dialling...' loop causes modem crash ('modem not responding'); have to stop-and-restart slmodemd -a to fix
rarely, loop says 'no carrier' too – in such a case, modem doesn't crash
mydebug.txt says nothing, no wonder, i daresay, what with no ppp session started
i searched archives but found not that much; sweetest post by one hazel who was grateful to have learned a lot, but her problem (looks a lot like mine) was never solved
btw: in slmodemd gcc4.3 & 2 there's no 'files' file, no automatizing scripts (got mine from gcc3)
btw: in novellsuse (which i use) slmodemd or some equivalent was part of the installation, i assume,
also the alsa drivers, and things are supposed to get automatized through configuration process in kinternet, which didn't work, which was why i got to you in the first place (wvdial by itself is the better choice anyway)
as for dmesg: there is a line
'ACPI: PCI interrupt for device 0000:00:1f.6 disabled'
bit farther below two lines
'ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 6 (level, low) -> IRQ 6
PCI: Setting latency timer of device 0000:00:1f.6 to 64'
q: is this the fix? (guess it's not a bootup problem anyway, tried pci=routeirq and pollirq to no avail)
what do you say to all that?
gonna pester the wvdial guys, too
sincerely yours, tobias
--
"Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ...
Jetzt GMX ProMail testen: http://www.gmx.net/de/go/promail
