Re: i4b driver broken for -current?

2002-01-26 Thread Marc Ernst Eddy van Woerkom
/sys/netinet; cvs update -r 1.60 in.c if you use cvs instead of CVSup). OK, that worked fine, I'm able to establish a link again. Thanks! As Jörg already pointed out, a recent -current (I use one from Jan 20) works with 1.61 too (ispppcontrol - spppcontrol), I write this with a

Re: i4b driver broken for -current?

2002-01-22 Thread Marc Ernst Eddy van Woerkom
I think it was my patch. Something with mtx_initialized()?. Exactly. /sys/netinet; cvs update -r 1.60 in.c if you use cvs instead of CVSup). I mirror the cvs repository. 1.60 is from October too, so I should have it. freebsd.org or any other source) you have to use the userland ppp. I

Re: i4b driver broken for -current?

2002-01-22 Thread Alexander Leidinger
On 21 Jan, Joerg Wunsch wrote: You have to use rev. 1.60 of /sys/netinet/in.c (cd /sys/netinet; No, you're wrong. This bug has been fixed as one of the first of my Yeah! I love to be proven wrong in such situations. :-) series of committs that brought the i4b version of sppp back into

Re: i4b driver broken for -current?

2002-01-22 Thread Alexander Leidinger
On 22 Jan, Marc Ernst Eddy van Woerkom wrote: /sys/netinet; cvs update -r 1.60 in.c if you use cvs instead of CVSup). I mirror the cvs repository. 1.60 is from October too, so I should have it. As Jörg already pointed out, a recent -current (I use one from Jan 20) works with 1.61 too

i4b driver broken for -current?

2002-01-21 Thread Marc Ernst Eddy van Woerkom
Hello, anyone running a recent -current successfuly with the i4b ISDN drivers? I built -current around christmas, and had to applay a patch posted here in October to make a kernel with i4b drivers. However I don't manage to establish a kernel ppp connection to my provider since then. Regards,