Red Hat Bugzilla – Bug 133889
ISDN support broken
Last modified: 2007-11-30 17:10:50 EST
Description of problem: In FC3Test1, ISDN support was fine, except that the network wizard didn't "know" whether an interface was up. However, it was possible to click the activate and deactivate buttons and thus activate or deactivate the interface. In FC3Test2, ISDN support no longer works, and I can't connect from home to the internet, anymore. Why is it so (what changed in either the kernel or isdn package that broke the support?) and wat should I do. My ISDN card uses the well supported Cologne chipset. Version-Release number of selected component (if applicable): FC3test2 How reproducible: install a new ISDN connection/interface and restart the isdn service (using the gui), or try to activate the interface (again, using the gui). The error message in either case is that the ISDN libraries couldn't be loaded. Actual results: see above Expected results: internet is up and running Additional info:
I'm guessing this is a udev issue. What /dev nodes does ISDN use? (If this is clearly not a udev issue, please feel free to reassign back.)
Oops... should have read the report slower. Can you please copy the *EXACT* error message?
Created attachment 104687 [details] PNGs of error message and related dialog boxes besides the PNGs, there are also two text files with the output of lspci -v and of isdnctrl. AF
could you please send followings infos for debugging: - the output of "cat /etc/sysconfig/isdncard" - the output of lsmod, please start isdn with "/etc/init.d/isdn start" before - the output of "cat /etc/sysconfig/network-scripts/ifcfg-Econophone" - the output of "isdnctrl list all", please make sure that you have to start ISDN before.
for the output of "isdnctrl list all" you also have to start "ifup Econophone" after starting ISDN service. thanks
isdn devices /dev/isdn* are missing or not created from udev. for more infos please take a look at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134525 i assign it to correct component. *** This bug has been marked as a duplicate of 134525 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.