Created attachment 46761 [details]
Y2logs

What ISDN HW which drivers ? 
 

Sorry I miss that the information is already in the old y2log files. 
According these you have a Fritz!Card PCI and you are using the AVM binonly 
drivers. 
These drivers are not included in OpenSUSE, OpenSUSE only contain GPL drivers 
and full OpenSource software. 
You can install the kernel-<type>-nongpl-<version>.rpm from 
ftp://ftp.suse.com   (or better mirrors) 
path: 
/pub/suse/i386/10.0/SUSE-Linux10.0-Beta2-Extra/kernel-modules+firmware/CD1/suse/i586/ 
 
If ISDN is your only internet connection, you can change the ISDN driver 
temporary to HiSax until you install the drivers. 
 

Switching to the HiSax driver worked perfect! It took less than 1 minute to
solve this once I knew where the error was.

However, I would have expected YaST to
-tell me that the driver is not available any longer
-suggest to try out the HiSax driver or get the rpm you named

For me (and probably many others) ISDN is the only way to the internet, so a
broken ISDN config after an update is a MAJOR showstopper.

I do not think that we can handle this in YaST. Maybe in the Release Notes. 
Adrian ? 

You cannot handle this? All that is necessary is


if ((driver_is_AVM_binonly)&&(package_not_available(AVM_binonly))
{
   switch_driver_to_HiSax;
   messagebox("Your ISDN driver...");
}

Please don't tell me that this is too difficult!

Yes it is doable, but it's not that easy and here are more problems. 
 
1. You want keep the driver and download the needed package or install self      
compiled driver. 
2. The needed config change must be implemented for each card (and for some 
cards no alternativ driver exist), since the config is different. 
3. At the moment all setup is the same for OpenSUSE and the other products, 
so you really need some extra info about what is included and what not. 
Missing driver package is not enough, since it maybe not be selected by all 
configurations. 
4. It's too late, Installation flow and text are froozen with BETA1 (because 
translation process and manual printing is started), so adding some popup 
is not possible. 
5. We didn't support cross product updates in the past. 
 

I didn't find any mention of this in the RC1 release notes. Is it going to be
there in the final version?

we will not fix this one anymore for 10.1, closing.