I hope someone noticed that 2.1.131 broke the ps/2 busmouse driver.
It worked in 2.1.128.
-Dan
by Dan Holli » Sun, 06 Dec 1998 04:00:00
-Dan
by David Wrag » Sun, 06 Dec 1998 04:00:00
Would you like to provide some context? Just saying "X is broke" isn't
very useful. There were changes to the PS/2 mouse support not so long
ago (it got merged with the keyboard support) but that was before
2.1.128.
Dave Wragg
by Patrick Caulfie » Sun, 06 Dec 1998 04:00:00
Eh? Works fine here !Quote:> I hope someone noticed that 2.1.131 broke the ps/2 busmouse driver.
> It worked in 2.1.128.
> -Dan
Patrick
1. LCP problem (Linux 2.1.131, pppd 2.3.5)
My PPP dial connection stopped working a couple of days ago on my Linux
box (pppd 2.3.5 compiled with 2.1.131 kernel).
I never had a problem before. My guess is that my provider has changed
something which causes LCP negotiation failures.
I have no problem connecting to another provider with Linux and no
problem connecting to the faulty provider with windoze 95 (which bothers
me :-).
I have tried many different configurations of pppd (asyncmap,
compression, ...) with no result.
I get the following trace (with kdebug 31):
pppd[491]: pppd 2.3.5 started by root, uid 0
...
... modem connect, login, password: that works, no problems
...
pppd[491]: Serial connection established.
kernel: ppp_ioctl: set dbg flags to 1f0000
kernel: ppp_ioctl: set flags to 1f0000
kernel: ppp_tty_ioctl: set xasyncmap
kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
kernel: ppp_ioctl: set flags to 1f0000
kernel: ppp_ioctl: set mru to 5dc
kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
kernel: ppp_ioctl: set flags to 1f0000
kernel: ppp: write frame, count = 18
kernel: FF 03 C0 21 01 01 00 0E ...!....
kernel: 05 06 B1 10 6A D4 07 02 ....j...
kernel: 08 02 ..
pppd[491]: Using interface ppp0
pppd[491]: Connect: ppp0 <--> /dev/ttyS0
pppd[491]: sent [LCP ConfReq id=0x1 <magic 0xb1106ad4> <pcomp> <accomp>]
kernel: ppp: receive buffer, count = 2
kernel: 7E 7D ~}
kernel: ppp: tossing frame (e0)
kernel: ppp: receive buffer, count = 28
kernel: 23 21 7D 21 7D 21 7D 20 #!}!}!}
kernel: 7D 2E 7D 25 7D 26 7D 30 }.}%}&}0
kernel: 6A 7D 27 7D 22 7D 28 7D j}'}"}(}
kernel: 22 7D 21 7E "}!~
kernel: ppp: frame with bad fcs, length = 18
kernel: ppp: bad frame, count = 18
kernel: FF 03 00 03 21 01 01 00 ....!...
kernel: 0E 05 06 10 6A 07 02 08 ....j...
kernel: 02 01 ..
pppd[491]: sent [LCP ConfReq id=0x1 <magic 0xb1106ad4> <pcomp> <accomp>]
...
... more LCP requests failures
...
I do not think the bad fcs error is really that, but rather that the
received frame format is not recognized (I never had errors before and
it works perfectly with another provider).
I am really curious as to what is going on here and would really
appreciate some help from the experts.
Please let me know if you need the full trace.
Thank you very much in advance.
PS: I have sent a message to my provider asking him what they changed:
I'll report on that ASAP.
Jean-Luc Fontaine
--
http://worldserver2.oleane.com/urcam-aq/
2. Dynamic symbol resolution by name?
3. Riva TNT+Xfree 3.3.3+Linux 2.1.131 = system crashes
5. Linux 2.1.131 VFAT / SMP problems
6. Sparc Assembly Instructions "swap" and "swapa"
7. What is ioctl: I_GETSIG failed 131 ????
8. rpcbind, ttsession and Xsun: how to bind to loopback adaptor?
9. spd_vhi and localhost in 2.1.131
10. 10baseT oddness - 2.0.36/2.1.131
11. PROBLEM: 2.4.19-pre10-ac2 bug in page_alloc.c:131
12. Kernel 2.1.131 + ppp + APM
13. Can't not telnet other than 131.215.99.X (my domain).