Tobias It is common experience that modem drivers can die sometimes when loaded, and unloading and reloading snd_intel8x0m can solver the problem. Also check that your System is not set to periodically try to restart the eth0 channel, as that will kill browsing under ppp0, through change in DNS specs. Also read through Jacque's PostInstall Howto at http://linmodems.technion.ac.il on tuning issues. MarvS On Sun, Jan 18, 2009 at 10:58 AM, <knallcharge@xxxxxxx> wrote: > hi, > i wrote before but forgot to attach > in the meantime, modem works fine, ie could be better, but ok > back then i had the nocarrier loop which i was advised could be due to traffic > noise on the line (guesswork by your adviser, what with no scanmodem output > at hand), it wasn't, it is just this: on this benq machine w/ hdacard + > intel-softmodem-(sub)chipset you always! have to remove+reinsert > snd_intel8x0m before starting slmodemd, from then on wvdial works fine as > long as the machine runs, you can disconnect as often as you like... > only problem that remains: modem hangs up on code 16 (meaning it hangs up > cause it feels like hanging up) this could be improved (up to like 40 running > minutes average till hangup) when everything concerned w/ sound is completely > shutdown: kill kmixer and set silent mode on the whole machine - no warning > sounds etc (hate that anyway) > from the list i gather that interference w/ sound in configurations similar to > mine is yet unsolved > my sound hardware is that bad, and my interest in sound on computers at large > is that minimal, that i, for one, don't give a dam; still, things should work > the way they're meant to, not, like, like on crutches > question: when snd_intel8x0m is needed by both sound and modem - what is it > that prevents people from having that driver twice, say, once under a > different name, serving thus independently to both devices? see, this is not > a real suggestion on how to think about things - given this worked in any > way, everybody would have it thus long since - i'm asking, cause i would like > to know, if the specific 'place' where the drivers are needed, where > they 'contact' the hardware, if these 'places' are known? the overall picture > is that the driver's 'grip' on the hardware seems to be feeble...is this > touching the proprietary/patented things issue? could i - as an end user try > contacting any one to put the problem to some appropriate ear? who might this > be, intel, agere, benq? i wouldn't mine buying a driver if necessary, and > possible...better to have a working device based on a mix of licensing > philosophies (as almost everybody has anyway) than a pure thing that doesn't > do what it's supposed to > > > another q is related to dmesg (doesn't seem to be part of the problems, > though, only asking for learning reasons and hope answering takes up but a > sec, thanks), i asked before, your guy didn't feel like answering, no wonder > (he couldn't have a look on my dmesg): > > when i see this > ACPI: PCI Interrupt Link [LNKF] (IRQs 5 6 10 11) *0, disabled. > ACPI: PCI Interrupt Link [LNKG] (IRQs 5 6 10 11) *7 > ACPI: PCI Interrupt Link [LNKH] (IRQs 5 6 10 11) *0, disabled. > is the 2nd line here a trial at fixing? > and is this > ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 6 > PCI: setting IRQ 6 as level-triggered > ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 6 (level, low) -> > IRQ 6 > ACPI: PCI interrupt for device 0000:00:1f.6 disabled > a fix followed by another blow to it? > and this > 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 > a fix, only to get this, further down > ACPI: PCI interrupt for device 0000:00:1f.6 disabled > 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 > to fix again, this time for good? > what causes this on-and-off? > > thanks for your help, tobias > > > > > > > > > >
