The secrets of yast......

I have an annoying problem with my umts-pcmcia modem (Huawei E620). Networkmanager does not dial from it. BUT if I do a hardware recognition in Yast (hardware info), it does work perfectly from networkmanager afterwards! :open_mouth:

Therefor, when yast stops quite some seconds showing “modem” he does something solving my problem.
Is there a way to see verbosely “what exactly” does yast during the modem recognition? I could force it to be done while starting KDE and getting rid of a lot of annoyance.

Does anybody know the “secret” of yast?

Using apowerpoint presentation about Yast I found /proc/modules.
How can I find out which modules are probed when yast is probing “modem”?

I found: pcmcia_core 39140 4 ssb,yenta_socket,pcmcia,rsrc_nonstatic, Live 0xffffffffa01f6000

This could be the pcmcia modem. How can I know? Or is this the pcmcia interface? I do not have any other pcmci adapter attached.

Not really sure what you’re asking but

lsmod shows modules that are loaded but this looks the same as /proc/… just proc is lower level and more direct. As for what module does what modinfo if you’re lucky will give you a description for the module.

As for seeing I suspect it is just loading a module which you maybe able to work out from looking at lsmod before and after. As for automagically think this has the info Kernel module configuration - openSUSE may find it is automagically using the wrong one but correcting it, which if is the case blacklisting maybe the solution.

Yes, thank you, these are very good hints. In /proc I get an enormous list of 36 pages that however make reference only twice to modem…and more or less tell me they are not correct. On what the system log:
Before using yast hardware info (syslog)

Jan 20 17:51:27 linux-xu0v modem-manager: (/dev/ttyUSB0) opening serial device…
Jan 20 17:51:28 linux-xu0v modem-manager:** Closing device ‘/dev/ttyUSB0’**
Jan 20 17:51:28 linux-xu0v dbus-daemon: Rejected send message, 6 matched rules; type=“method_return”, sender=":1.8" (uid=0 pid=3492 comm="/usr/sbin/modem-manager “) interface=”(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.7" (uid=0 pid=3441 comm="/usr/sbin/NetworkManager “))
Jan 20 17:51:28 linux-xu0v dbus-daemon: Rejected send message, 6 matched rules; type=“method_return”, sender=”:1.8" (uid=0 pid=3492 comm="/usr/sbin/modem-manager “) interface=”(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.7" (uid=0 pid=3441 comm="/usr/sbin/NetworkManager “))
Jan 20 17:51:28 linux-xu0v dbus-daemon: Rejected send message, 6 matched rules; type=“method_return”, sender=”:1.8" (uid=0 pid=3492 comm="/usr/sbin/modem-manager “) interface=”(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.7" (uid=0 pid=3441 comm="/usr/sbin/NetworkManager “))
**
After:**
Jan 20 18:07:51 linux-xu0v modem-manager: (/dev/ttyUSB0) opening serial device…
Jan 20 18:07:51 linux-xu0v pppd[5371]: Plugin /usr/lib64/pppd/2.4.4/nm-pppd-plugin.so loaded.

Jan 20 18:07:51 linux-xu0v kernel: PPP generic driver version 2.4.2
Jan 20 18:07:51 linux-xu0v pppd[5371]: pppd 2.4.5 started by root, uid 0
Jan 20 18:07:51 linux-xu0v dbus-daemon: Rejected send message, 4 matched rules; type=“method_return”, sender=”:1.7" (uid=0 pid=3441 comm="/usr/sbin/NetworkManager “) interface=”(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.39" (uid=0 pid=5371 comm="/usr/sbin/pppd nodetach lock nodefaultroute user b"))
Jan 20 18:07:51 linux-xu0v pppd[5371]: Using interface ppp0
Jan 20 18:07:51 linux-xu0v pppd[5371]: Connect: ppp0 <–> /dev/ttyUSB0
Jan 20 18:07:51 linux-xu0v dbus-daemon: Rejected send message, 4 matched rules; type=“method_return”, sender=":1.7" (uid=0 pid=3441 comm="/usr/sbin/NetworkManager “) interface=”(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.39" (uid=0 pid=5371 comm="/usr/sbin/pppd nodetach lock nodefaultroute user b"))
Jan 20 18:07:51 linux-xu0v dbus-daemon: Rejected send message, 4 matched rules; type=“method_return”, sender=":1.7" (uid=0 pid=3441 comm="/usr/sbin/NetworkManager “) interface=”(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.39" (uid=0 pid=5371 comm="/usr/sbin/pppd nodetach lock nodefaultroute user b"))
Jan 20 18:07:51 linux-xu0v pppd[5371]: CHAP authentication succeeded
Jan 20 18:07:51 linux-xu0v pppd[5371]: CHAP authentication succeeded
Jan 20 18:07:51 linux-xu0v dbus-daemon: Rejected send message, 4 matched rules; type=“method_return”, sender=":1.7" (uid=0 pid=3441 comm="/usr/sbin/NetworkManager “) interface=”(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.39" (uid=0 pid=5371 comm="/usr/sbin/pppd nodetach lock nodefaultroute user b"))
Jan 20 18:07:51 linux-xu0v kernel: PPP BSD Compression module registered
Jan 20 18:07:51 linux-xu0v kernel: PPP Deflate Compression module registered

I will dig into the info you gave me. The automagically thing may be a good candidate…