ok, this is a linux and tech bLog-entry today. more or less a reminder for if i will ever be in a situation like i was several hours ago, and to help people to shorten the time wasted on debugging and fixing. for all those that are neither interested in a) technical stuff, b) being a ONE customer using umts, or c) linux shell-stuff i apologise, but good news for you: you can actually skip the rest of this article. still reading? yippah, let's get on... today i got to test a umts card by phone-/internet-service-provider ONE. i got the novatel wireless inc. merlin U630 card. the first (though unfortunately not working) setup was made as described to this site. most values do not work for a correct ONE setup, so they had to be adjusted. additionally i could not find any site that gave me a running config, so here is the guide which made this card work for me: at first make sure you have those tools installed (package-names are for a debian-system): remark: ping and minicom are optional and for debugging purpose. secondly check if the card was found and initialised correctly by the kernel (make sure module "serial_cs" is loaded...) here's a minicom session done initially for debugging purposes: the first script involved is called /etc/ppp/umts.chat: "<PIN>" is the pin as provided by ONE. the second script, "umts" contains these fine lines: "ttyXX" is the device the card gets assigned to. check dmesg(8) for more infos. and to put all the pieces together, finally my script combining all this stuff: and here is some output by the script... yeah, online! ;)