What about the jumper setting on the modem?
Jay
>
> Heya list! (^;
>
> I have a problem..(we all do)..but this one's with my mouse. It has
> dogged (moused?) this machine since day 1 of rhl-5. I've tried every
> combination of hardware swap short of the m'board to sus it thatta way,
> but I begin to think it's somewhere else.
>
> If I were on my Amiga, I'd say it was a case of a nasty mouseblanker
> hack standing on everything...without blanking the mouse pointer. None the
> less, if the mouse is left motionless for an indeterminent amount of time,
> anything that's involved shuttling stuff across the kernel..say, like a
> ftp or netscape up/download, simply stops dead in it's tracks.
>
> In netscape's case, the event is noticable by the activity animation
> mysteriously stopping. Worse though...other times the anim will stop, and
> the transfer will continue in the background...then, sometimes I can leave
> the mouse motionless for hours on end with no ill effects, and yet other
> times, it can happen in under 20 seconds...look;
>
> ::simple scenario, I've hooked to my isp, and ping my gw addr::
>
> 64 bytes from 203.55.207.66: icmp_seq=0 ttl=255 time=234.0 ms
> 64 bytes from 203.55.207.66: icmp_seq=1 ttl=255 time=160.0 ms
> 64 bytes from 203.55.207.66: icmp_seq=2 ttl=255 time=150.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=3 ttl=255 time=140.1 ms
>
> ..nothing surprizing, but I haven't touched the mouse yet...
>
> 64 bytes from 203.55.207.66: icmp_seq=12 ttl=255 time=140.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=13 ttl=255 time=140.0 ms
> 64 bytes from 203.55.207.66: icmp_seq=14 ttl=255 time=140.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=15 ttl=255 time=620.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=16 ttl=255 time=140.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=17 ttl=255 time=12510.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=18 ttl=255 time=11530.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=19 ttl=255 time=10550.0 ms
> 64 bytes from 203.55.207.66: icmp_seq=20 ttl=255 time=9730.0 ms
> 64 bytes from 203.55.207.66: icmp_seq=21 ttl=255 time=8760.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=22 ttl=255 time=7770.1 ms
> 64 bytes from 203.55.207.66: icmp_seq=23 ttl=255 time=6790.1 ms
>
>
> ..to cite this visually (using the tx & rx leds), I saw pings going out,
> and pongs coming back {140.0ms being norm], but after seq_16, the pongs
> stopped...and stayed stopped, even though this thing is still pinging
> merrily away..blink...blink...blink.
>
> Then...the *moment* I touch the mouse (say 10s after things stop),
> there's a great flood of incoming from the server instantly, telling me
> '..no, that wasn't lost, just 12510.1ms late..', but it **appears** like
> the serial line to the modem is holding off the receive?? Same goes for
> everything this affects....the moment I toucha da mouse, things restart.
>
> Any ideas anyone?
>
>
>
>
> _______________________________________________________
> How come inbuilt thermal shutdown circuits in most
> IC's don't save the device from burnout? db
> _______________________________________________________
>
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe" as the Subject.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
