SOLVED! Re: how dangerous would it be to switch to 5.1-current?
un1du2el
un1du2el at gmx.net
Wed Nov 19 23:52:33 PST 2003
It's working! But I don't know exactly why...
I did the following:
1. Change setup to isppp
2. Test => failed
3. Put in an AVM Fritz PCI v2
4. Rebuild kernel with new device ifpi2, reboot
5. Test => failed
6. Removed AVM Fritz PCI v2
7. Rebuild kernel with old device isic, reboot
8. Change BIOS setting "PNP OS = no"
9. Change BIOS setting "Resource configuration = auto"
10. Change setup to tun0
11. Test => passed
So what I actually did was to change two BIOS settings (which I changed
to "PNP=YES", "configuration=manual, reserve irq5 for isa" after the
first test yesterday failed) and recompile the kernel one more time.
Markus D.
Gary Jennejohn wrote:
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
>
> "un1du2el" writes:
>
>>I've just tried to use an isppp setup with 5.1-R and the same thing
>>happens. In fact it fails on first attempt, dials a second time, the
>>connection is closed from the other side and the nothing ever happens
>>again (no dialouts etc.).
>>
>>Attached is a redirected log output from isdnd.
>>
>>I use this card:
>>isic0 at port 0x1b00-0x1b1f,0x16e0-0x16ff,0x6e0-0x6ff,0xee0-0xeff,
>>0x1300-0x131f,0x300-0x31f,0xb00-0xb1f irq 5 flags 0x4 on isa0
>>isic0: passive stack unit 0
>>isic0: AVM A1 or Fritz!Card Classic
>>
>>The same setup works perfectly with 4.9-R.
>>
>
>
> If you do spppcontrol does it show the correct values for your
> access information (password, user-name, etc.)? I just used my
> ifpi2 under -current yesterday with no problems whatsoever.
>
> ---
> Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de
>
More information about the freebsd-isdn
mailing list