Created attachment 39997 [details]
output of hwinfo

OK. Please tell me whether yast handles it OK when hwinfo does report it as a   
modem.  
If it misbehaves, it may be related to bug 74292. 

I'm sorry, but that is exactly the question I thought you were going 
to answer. 

I see. Currently I am not sure so I think testing it is the simplest way to 
answer. 
But I cannot test it myself as I don't have the hardware and even if I had it, 
hwinfo would not let yast see it. So please change hwinfo and run yast and 
tell me the results. What would be the point of hiding the modem in hwinfo? 
Hiding yast bugs? 

I neither have the modem nor any idea what the correct values are hwinfo 
should report. Sorry, I can't help. 

It should be enough that it appear in hwinfo --modem, see comment 0. 

No, it certainly is not. 

Arvin, can you talk with Steffen about this? It seems simple to me but we 
appear not to understand each other. 

The setup of that modem is a bit more complicated than of a normal, see
http://portal.suse.com/sdb/en/2004/05/thallma_91_smartlink.html.

I see three possibilities:

1) Full support: Detect the modem, install smartlink-softmodem package,
   configure /etc/sysconfig/slmodemd, finally configure ifcfg-modemX.

2) Partial support: Dectect modem once the smartlink driver has been
   configured by hand and just configure ifcfg-modemX.

3) Do nothing.

PM has to decide about that.

I would love to have full support if this is possible to do.

Reassigning to the new maintainer of yast2-network.

*** Bug 88512 has been marked as a duplicate of this bug. ***

*** Bug 153112 has been marked as a duplicate of this bug. ***

Steffen, hwinfo says Requires: kernel-nongpl, but that package was droped.
Instead of that we have smartlink-softmodem, smartlink-softmodem-kmp-bigsmp and smartlink-softmodem-kmp-default
Could you update hwinfo for this?

As of SL 10.3, the package provides hardware info via supplements & modalias.

If there's anything else hwinfo needs to do here, let me know.

Arvin, can you provide hwinfo from 10.3b1?

hwinfo --modem reports nothing.
hwinfo --usb gives attached output.

Created attachment 158440 [details]
hwinfo output

*** Bug 284287 has been marked as a duplicate of this bug. ***

Actually I think this bug and 284287 are different problems, the modem in
bug 284287 is already detected as a modem, but apparently there are problems
configuring it (yast2-network or smartlink-softmodem problem), while in this
case the modem is not even detected as modem meaning yast2 has no chance to
configure it (-> hwinfo bug).

Steffen, I believe you might need to mark this Unclassified device as Modem.

Steffen, what do you mean about suggestion in comment #20?
Or is that slusb bug, that can be solved in slusb driver?

Ok, made it a modem. Arvin, please create such a hd.ids file:

# cat /var/lib/hardware/hd.ids
 vendor.id              usb 0x0483
&device.id              usb 0x7554
+baseclass.id           0x102
+subclass.id            0x00
+driver.module.modprobe slusb

and give it a try. Does it work?

Hm, just seen that slusb is blacklisted. Is this bug really relevant for 10.3?

In 10.3 Beta 3 it's reported as modem without this extra file.

-> hwinfo --modem
37: USB 00.0: 10200 Modem                                       
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_483_7554_noserial_if0
  Unique ID: FKGF.9HVP+p7+bK9
  Parent ID: pBe4.DvXC4y8Bsa4
  SysFS ID: /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.0
  SysFS BusID: 2-1:1.0
  Hardware Class: modem
  Model: "SGS Thomson Microelectronics 56k SoftModem"
  Hotplug: USB
  Vendor: usb 0x0483 "SGS Thomson Microelectronics"
  Device: usb 0x7554 "56k SoftModem"
  Revision: "2.00"
  Device File: /dev/ttyACM0
  Speed: 12 Mbps
  Module Alias: "usb:v0483p7554d0200dc02dsc00dp00ic02isc80ipFF"
  Driver Info #0:
    Driver Status: slusb is not active
    Driver Activation Cmd: "modprobe slusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #33 (Hub)

(In reply to comment #23 from Steffen Winterfeldt)
> Hm, just seen that slusb is blacklisted. Is this bug really relevant for 10.3?

Steffen, what exactly does it mean? What should be the replacement?

Arvin, could you check that the modem really works?
And confirm that slusb is there as a correct requirement?

I don't have a telephone-line so I can't do any real tests.

ad 25: no idea, I just noticed slusb in /etc/modprobe.d/blacklist. But
maybe that is ok.

Reinhard do you have an analog line in your office ?

Is the line really needed? If you manage to configure the modem and get "NO CARRIER" when trying to dial in I'd consider that a success already.

(In reply to comment #28 from Karsten Keil)
> Reinhard do you have an analog line in your office ?

Yes, I have an analog line as well as ways to connect analog equipment to the ISDN lines.

(In reply to comment #27 from Steffen Winterfeldt)
> ad 25: no idea, I just noticed slusb in /etc/modprobe.d/blacklist. But
> maybe that is ok.
> 

This might be to prevent automatic loading of the module, because as the module
is binary-only that would taint always the kernel when the package is installed
even if the module is not in use. My guess.

this was fixed in bug #284287 but for /dev/SL* only

Created attachment 174711 [details]
fixed yast2-network

Can you test attached file?
It handles ttyACM same way like ttySL (from bug #284287) ...

Yast detects the modem and can configure it. But afterwards it does not
work:

-> /etc/init.d/slmodemd start
Starting SmartLink Modem driver: startproc:  exit status of parent of /usr/sbin/slmodemd: 255

-> /usr/sbin/slmodemd 
error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
error: cannot setup device `/dev/slamr0'

System is d210 if somebody wants to test.

Arvin, can you confirm comment #35?

No, it does not work. No matter what I have tried the error message
stays the same.

Sorry, but in this case I don't know what to fix.
We need some expert on this issue