Hej, tak for din tålmodighed!
Her kommer så resultatet (modemet er sat i):
henrik@henrik-laptop:~$ cat /etc/usb_modeswitch.conf && cat /lib/udev/rules.d/45-hotplug.rules && lsb_release -a && uname -a && lsusb
# /etc/usb_modeswitch.conf
#
# Last modified: 2008-04-15
#
# Configuration for usb_modeswitch, a mode switching tool for controlling
# flip flop (multiple device) USB gear
#
# Main purpose is to trigger the switching of several known UMTS modems
# from storage device mode ("ZeroCD TM" for use with MS Windows) to modem
# (serial) device mode
#
# Detailed instructions and a friendly forum on the homepage:
#
http://www.draisberghof.de/usb_modeswitch#
# News update: you want to read the paragraph about troubleshooting there
# if you run into problems !!!
# Just set or remove the comment signs (# and

in order to activate
# your device. (Actual entries are further down, after the reference.)
#
# For custom settings:
# Numbers can be decimal or hexadecimal, MessageStrings MUST be
# hexadecimal without prepended "0x". Digits 9-16 in the known
# MessageStrings are arbitrary; I set them to "12345678"
# What it all means (command line flags appended):
#
#
# * DefaultVendor -v <hex number>
# * DefaultProduct -p <hex number>
#
# This is the ID the USB device shows after having been plugged in.
# The program needs this; if not found -> no action.
#
#
# * TargetVendor -V <hex number>
# * TargetProduct -P <hex number>
#
# This is the ID the USB device after successful mode switching.
# ! From version 0.9.4 just for information purposes !
# Might be useful for testing in future versions
#
#
# * TargetClass -C <hex number>
#
# Some newer devices don't change IDs but switch device class. If
# the device has the target class -> no action (and vice versa)
#
#
# * MessageEndpoint -m <hex number>
#
# A kind of address inside the interface to which the "message"
# (the sequence that does the actual switching) is directed.
# Starting from version 0.9.7 the MessageEndpoint is autodetected
# if not given
#
#
# * MessageContent -M <hex string>
#
# A hex string containing the "message" sequence; it will be
# sent as a USB bulk transfer.
#
#
# * ResponseEndpoint -r <hex number>
# * NeedResponse -n <0/1> OBSOLETE; just give ResponseEndpoint
#
# Some devices were reported to require receiving the response of the
# bulk transfer to do the switching properly. Usually not needed.
#
#
# * DetachStorageOnly -d <0/1>
#
# Some devices just need to be detached from the usb-storage
# driver to initiate the mode switching. Using this feature
# instead of removing the whole usbstorage module keeps other
# storage devices working.
#
#
# * HuaweiMode -H <0/1>
#
# Some Huawei devices can be switched by a special control
# message.
#
#
# * SierraMode -S <0/1>
#
# Some Sierra devices can be switched by a special control
# message.
#
#
# * SonyMode -O <0/1>
#
# Some Sony-Ericsson devices can be switched by a special control
# message. This is experimental and might not have a stable result
#
#
# * ResetUSB -R <0/1>
#
# Some devices need a rougher treatment. If the switching seems
# to do something (run udevmonitor), but your system does not reflect
# it, try this somewhat brutal method to do a reset after switching.
# Mind that if your device switched OK before, this will probably set
# it back to storage mode ...
#
#
# * Interface -i <hex number>
# * Configuration -u <hex number>
# * AltSetting -a <hex number>
#
# More USB parameter to help with tricky devices and for doing lots
# of cruel experiments ...
#
#
# * CheckSuccess -s <number>
#
# Check for successful switch after <number> seconds (to let device
# settle). First, an interface access test: most devices vanish after
# switching and can't be accessed anymore. Second, a recount of target
# devices: one more than at the first count -> device switched fine. A
# settling time of 2 - 3 seconds is usually enough; your setup may vary
#
# All other entries are just ignored !
# Additional command line flags:
#
# Verbose output -W
# No output at all -q
# Other config file -c <file>
# AltSetting/Configuration changes and ResetUSB are executed after all
# other steps and can be combined
#
# If you find working codes and configurations, please contribute
# them!
;CheckSuccess=2
########################################################
# Huawei E1752
#
# Contributor:
DefaultVendor= 0x12d1
DefaultProduct= 0x1446
TargetVendor= 0x12d1
TargetProdct= 0x1001
MessageEndpoint= 0x01
MessageContent= "55534243000000000000000000000011060000000000000000000000000000"
SUBSYSTEM=="usb", SYSFS{idProduct}=="1446", SYSFS{idVendor}=="12d1", RUN+="/usr/sbin/usb_modeswitch"
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.10
Release: 9.10
Codename: karmic
Linux henrik-laptop 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 i686 GNU/Linux
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 049f:0086 Compaq Computer Corp. Bluetooth Device
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
henrik@henrik-laptop:~$