|
Other BSD and UNIX/UNIX-like Any other flavour of BSD or UNIX that does not have a section of its own. |
|
Thread Tools | Display Modes |
|
|||
Post install help
hey guys
Just install DragonFly-2.6.3 and i'm having trouble with what to do next ? being trying to connect my 3g usb-modem so that i can update sys and put some programs on but have no idea, have been search here and everywhere but with no success. then found out that the kernel sources come with the cd version and tried to compile them but having problems doing that, i extracted the src-sys.tgz in /usr and cd to /usr/src and tried to make it but gets error message " make:dont know how to make /usr/src/sys/boot/pc32/boot2/////////// and so on am i doing something wrong tried doing the way the handbook said about compiling the kernel but i get a error message "must make buildworld first" so tried that and get error message "mtree: line 1 too long" so now im lost could someone help me please cheers dave |
|
|||
Try here - mailing list (link is at DFBSD web page)
-> IRC channel: #dragonflybsd on EFNet To be honest I don't know what is your problem? 3g usb-modem or DFBSD setup? For DragonFlyBSD setup, try handbook or new handbook (can't post links, due to new member post limit) Code:
pkg_radd -v nano mc links modular-xorg-server modular-xorg-drivers modular-xorg-libs modular-xorg-apps modular-xorg-fonts freefonts openbox |
|
|||
thanks klanger for your reply i check out your ideas
my problem was orginally trying to connect to the internet through my huawei usb-modem as this is the only way i can get online,i just wanted to build my new dfbsd as i use linux on my laptop and setup dfbsd on my pc.never used bsd before and find it interesting tried searching for usb-modem etc. here and feebsd forum but most say about adding things to your kern.conf but cant find where it is locate. cheers dave |
|
|||
If this your 1st time with BSD and you want to use this system as main OS, I thing you should try FreeBSD first (if you don't like cli installer there is a faster&more GUI way via PC-BSD GUI installer).
The main reason is that the community is bigger (there fore more problems are either solved or you'll solve them quicker), there are more pkg and the ports are more up-to-date etc. Don't get me wrong DragonFlyBSD is fantastic (HAMMER ect - I'm using it now on my eeepc) but I think it is better to start with something easier and after a while get your hands dirty in DFBSD. In fact, DFBSD is "based" on FBSD so if you get to work your hardware in FBSD it should (hmmm) in the end work with DFBSD. Eg. wifi in eeepc under DFBSD is activated the same way as in FBSD 7.2. With applications it seems that linux is nearly "bleeding", then there is FBSD and then other BSD (with DFBSD). |
|
|||
My "(Hmmm)" meant that
|
|
|||
cheers fellows i will give the other bsd`s ago but really wanted to keep dragonfly
|
|
|||
In that case, try IRC channel - you can find there Matthew Dillon and talk to him.
|
|
|||
cheers klanger
|
|
|||
sorry klanger
mayb you help with why my sys want pick my usb-modem properly,heres my dmesg Code:
May 15 23:05:00 halt: halted by root May 15 23:05:00 syslogd: exiting on signal 15 May 15 23:06:09 syslogd: kernel boot file is /boot/kernel May 15 23:06:09 kernel: Copyright (c) 2003-2010 The DragonFly Project. May 15 23:06:09 kernel: Copyright (c) 1992-2003 The FreeBSD Project. May 15 23:06:09 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 15 23:06:09 kernel: The Regents of the University of California. All rights reserved. May 15 23:06:09 kernel: DragonFly v2.6.3-RELEASE #4: Mon May 3 09:54:14 PDT 2010 May 15 23:06:09 kernel: root@test28.backplane.com:/usr/obj/usr/src-misc/sys/GENERIC May 15 23:06:09 kernel: TSC clock: 2412088902 Hz, i8254 clock: 1193194 Hz May 15 23:06:09 kernel: CPU: Intel(R) Celeron(R) CPU 2.40GHz (2412.08-MHz 686-class CPU) May 15 23:06:09 kernel: Origin = "GenuineIntel" Id = 0xf33 Stepping = 3 May 15 23:06:09 kernel: Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> May 15 23:06:09 kernel: Features2=0x41d<SSE3,DTES64,MON,DS_CPL,CNXT-ID> May 15 23:06:09 kernel: real memory = 1342111744 (1279 MB) May 15 23:06:09 kernel: avail memory = 1286721536 (1227 MB) May 15 23:06:09 kernel: md0: Malloc disk May 15 23:06:09 kernel: kbd1 at kbdmux0 May 15 23:06:09 kernel: ACPI: RSDP 0xf6680 00014 (v0 GBT ) May 15 23:06:09 kernel: ACPI: RSDT 0x4fff3000 0002C (v1 GBT AWRDACPI 42302E31 AWRD 01010101) May 15 23:06:09 kernel: ACPI: FACP 0x4fff3040 00074 (v1 GBT AWRDACPI 42302E31 AWRD 01010101) May 15 23:06:09 kernel: ACPI: DSDT 0x4fff30c0 03A01 (v1 GBT AWRDACPI 00001000 MSFT 0100000C) May 15 23:06:09 kernel: ACPI: FACS 0x4fff0000 00040 May 15 23:06:09 kernel: ACPI: APIC 0x4fff6b00 00068 (v1 GBT AWRDACPI 42302E31 AWRD 01010101) May 15 23:06:09 kernel: npx0: <math processor> on motherboard May 15 23:06:09 kernel: npx0: INT 16 interface May 15 23:06:09 kernel: Using XMM optimized bcopy/copyin/copyout May 15 23:06:09 kernel: cryptosoft0: <software crypto> on motherboard May 15 23:06:09 kernel: acpi0: <GBT AWRDACPI> on motherboard May 15 23:06:09 kernel: acpi0: Power Button (fixed) May 15 23:06:09 kernel: Warning: ACPI is disabling APM's device. You can't run both May 15 23:06:09 kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 May 15 23:06:09 kernel: acpi_button0: <Power Button> on acpi0 May 15 23:06:09 kernel: fdc0: <NEC 72065B or clone> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 May 15 23:06:09 kernel: fdc0: FIFO enabled, 8 bytes threshold May 15 23:06:09 kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 May 15 23:06:09 kernel: sio0: type 16550A May 15 23:06:09 kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 May 15 23:06:09 kernel: sio1: type 16550A May 15 23:06:09 kernel: ppc0: <Standard parallel printer port> port 0x378-0x37f irq 7 on acpi0 May 15 23:06:09 kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode May 15 23:06:09 kernel: ppbus0: <Parallel port bus> on ppc0 May 15 23:06:09 kernel: plip0: <PLIP network interface> on ppbus0 May 15 23:06:09 kernel: lpt0: <Printer> on ppbus0 May 15 23:06:09 kernel: lpt0: Interrupt-driven port May 15 23:06:09 kernel: ppi0: <Parallel I/O> on ppbus0 May 15 23:06:09 kernel: atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0 May 15 23:06:09 kernel: atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 May 15 23:06:09 kernel: kbd0 at atkbd0 May 15 23:06:09 kernel: cpu0: <ACPI CPU> on acpi0 May 15 23:06:09 kernel: cpu_cst0: <ACPI CPU C-State> on cpu0 May 15 23:06:09 kernel: pcib0: <Host to PCI bridge> pcibus 0 on motherboard May 15 23:06:09 kernel: pir0: <PCI Interrupt Routing Table: 8 Entries> on motherboard May 15 23:06:09 kernel: pci0: <PCI bus> on pcib0 May 15 23:06:09 kernel: agp0: <VIA 8703 (P4M266x/P4N266) host to PCI bridge> mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 May 15 23:06:09 kernel: pcib1: <PCI-PCI bridge> at device 1.0 on pci0 May 15 23:06:09 kernel: pci1: <PCI bus> on pcib1 May 15 23:06:09 kernel: vgapci0: <VGA-compatible display> mem 0xe8000000-0xe807ffff,0xe4000000-0xe7ffffff,0xec000000-0xecffffff irq 11 at device 0.0 on pci1 May 15 23:06:09 kernel: pci0: <simple comms> (vendor 0x125d, dev 0x2838) at device 6.0 irq 10 May 15 23:06:09 kernel: uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 11 at device 16.0 on pci0 May 15 23:06:09 kernel: usb0: <VIA 83C572 USB controller> on uhci0 May 15 23:06:09 kernel: usb0: USB revision 1.0 May 15 23:06:09 kernel: uhub0: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 May 15 23:06:09 kernel: uhub0: 2 ports with 2 removable, self powered May 15 23:06:09 kernel: uhci1: <VIA 83C572 USB controller> port 0xd800-0xd81f irq 5 at device 16.1 on pci0 May 15 23:06:09 kernel: usb1: <VIA 83C572 USB controller> on uhci1 May 15 23:06:09 kernel: usb1: USB revision 1.0 May 15 23:06:09 kernel: uhub1: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 May 15 23:06:09 kernel: uhub1: 2 ports with 2 removable, self powered May 15 23:06:09 kernel: uhci2: <VIA 83C572 USB controller> port 0xdc00-0xdc1f irq 10 at device 16.2 on pci0 May 15 23:06:09 kernel: usb2: <VIA 83C572 USB controller> on uhci2 May 15 23:06:09 kernel: usb2: USB revision 1.0 May 15 23:06:09 kernel: uhub2: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 May 15 23:06:09 kernel: uhub2: 2 ports with 2 removable, self powered May 15 23:06:09 kernel: pci0: <serial bus, USB> (vendor 0x1106, dev 0x3104) at device 16.3 irq 12 May 15 23:06:09 kernel: isab0: <PCI-ISA bridge> at device 17.0 on pci0 May 15 23:06:09 kernel: isa0: <ISA bus> on isab0 May 15 23:06:09 kernel: atapci0: <VIA 8235 UDMA133 controller> port 0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 May 15 23:06:09 kernel: ata0: <ATA channel 0> on atapci0 May 15 23:06:09 kernel: ad0: 4125MB <FUJITSU MPC3043AT 6018> at ata0-master UDMA33 May 15 23:06:09 kernel: acd0: CDRW <LITE-ON CD-RW SOHR-5238S/4S04> at ata0-slave UDMA33 May 15 23:06:09 kernel: ata1: <ATA channel 1> on atapci0 May 15 23:06:09 kernel: pci0: <multimedia, audio> (vendor 0x1106, dev 0x3059) at device 17.5 irq 10 May 15 23:06:09 kernel: vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xe800-0xe8ff mem 0xee001000-0xee0010ff irq 11 at device 18.0 on pci0 May 15 23:06:09 kernel: miibus0: <MII bus> on vr0 May 15 23:06:09 kernel: ukphy0: <Generic IEEE 802.3u media interface> on miibus0 May 15 23:06:09 kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto May 15 23:06:09 kernel: vr0: MAC address: 00:0f:ea:1a:fe:8b May 15 23:06:09 kernel: pmtimer0 on isa0 May 15 23:06:09 kernel: fdc1: cannot reserve I/O port range May 15 23:06:09 kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 May 15 23:06:09 kernel: sc0: <System console> at flags 0x100 on isa0 May 15 23:06:09 kernel: sc0: VGA <16 virtual consoles, flags=0x300> May 15 23:06:09 kernel: it0 at port 0x290-0x297 on isa0 May 15 23:06:09 kernel: ppc1: cannot reserve I/O port range May 15 23:06:09 kernel: ip: MPSAFE May 15 23:06:09 kernel: arp: MPSAFE May 15 23:06:09 kernel: CAM: Configuring 2 busses May 15 23:06:09 kernel: CAM: finished configuring all busses (0 left) May 15 23:06:09 kernel: cd0 at ata0 bus 0 target 1 lun 0 May 15 23:06:09 kernel: cd0: <LITE-ON CD-RW SOHR-5238S 4S04> Removable CD-ROM SCSI-0 device May 15 23:06:09 kernel: cd0: 33.000MB/s transfers May 15 23:06:09 kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present May 15 23:06:09 kernel: Mounting root from ufs:/dev/serno/07179341.s1a May 15 23:06:09 kernel: tryroot serno/07179341.s1a May 15 23:06:09 kernel: Mounting devfs May 15 23:06:23 login: ROOT LOGIN (root) ON ttyv0 May 15 23:06:34 kernel: umass0: <HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/0.00, addr 2> on uhub0 May 15 23:06:34 kernel: cd8 at umass-sim0 bus 0 target 0 lun 0 May 15 23:06:34 kernel: cd8: <HUAWEI Mass Storage 2.31> Removable CD-ROM SCSI-2 device May 15 23:06:34 kernel: cd8: 1.000MB/s transfers May 15 23:06:34 kernel: cd8: Attempt to query device size failed: NOT READY, Medium not present May 15 23:08:38 kernel: umass1: <Kingston DataTraveler 2.0, class 0/0, rev 2.00/2.00, addr 3> on uhub0 May 15 23:08:38 kernel: da8 at umass-sim1 bus 1 target 0 lun 0 May 15 23:08:38 kernel: da8: <Kingston DataTraveler 2.0 1.00> Removable Direct Access SCSI-2 device May 15 23:08:38 kernel: da8: 1.000MB/s transfers May 15 23:08:38 kernel: da8: 954MB (1953792 512 byte sectors: 64H 32S/T 954C) Last edited by vermaden; 21st May 2010 at 11:07 AM. Reason: Use [ code ] tags. |
|
|||
Do you have
Code:
usbd_enable="YES" I have no experience with usb-modems but what I have noticed was that my usb-mouse worked after adding above line to rc.conf. There are some problems with mounting usb-sticks later but try it any way, maybe this is it. |
|
|||
cheers i will give it ago and get back to you
|
|
|||
i,ve just put that line in /etc/rc.conf and reboot and still the same.
i have read on here about putting "device ucom + device usbd" in your kern.conf but i cannot find where kern.conf is .in linux it is all in your /usr/src but after i installed dfbsd there was no /usr/src until i found out that the livecd had the kernel source codes , so i cp them to /usr and unpacked it and now i have /usr/src .but now kern.conf for the current kernel,read that i can build kernel from there (dfbsd + freebsd handbook) so i tried that but it tells me that i have to buildworld first and my understanding is to build world you need internet access which brings me back to my orginally problem off how to get my usb-modem to work.Is my understanding correct or is therea way off downloading something from another computer so i can buildworld and build kernel cheers dave |
|
|||
all good now fixed everything got my huawei usbmodem to work and now have a fully blown dflbsd yephee
|
|
|||
oh, come on... share the fix with us
|
|
|||
i came across this quick guide to seting it all up and yep heeeeeee it is all working
here is that guide : Connecting to the Internet with UMTS on NetBSD All you need is a laptop with cardbus slot (PCMCIA) and a datacard which is supported by NetBSD. The card will appear as an USB modem to the kernel. In my example I am using an Option N.V. MC3G (Vodafone Mobile Connect Card). First of all you have to make sure the datacard is recognized by the kernel: ohci0 at cardbus0 function 0: vendor 0x1045 product 0xc861 (rev. 0x10) ohci0: OHCI version 1.0, legacy support usb5 at ohci0: USB revision 1.0 uhub5 at usb5: vendor 0x1045 OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub5: 2 ports with 2 removable, self powered ubsa0 at uhub5 port 1 ubsa0: Vodafone Vodafone Mobile Connect Card - 3G, rev 2.00/0.00, addr 2 ucom0 at ubsa0 portno 0 ucom0 means we have successfully attached a serial adapter. ugen0 would mean the card is not yet supported. The device can be accessed through /dev/ttyU0. For a test, we add the following line to /etc/remote to communicate with the modem: ucom0:dv=/dev/ttyU0:br#460800a=none:dc: Then connect to the modem as root and try some AT commands: # tip ucom0 connected at OK atz OK ati Manufacturer: Option Wireless Technology Model: 129 Revision: 3.1.2 (Date: Mar 08 2004, Time: 11:54:30) OK at&v &C: 1; &D: 2; &F: 0; E: 1; I: 0; L: 0; M: 0; Q: 0; V: 1; X: 4; Z: 0; S0: 0; S3: 13; S4: 10; S5: 8; S6: 2; S7: 50; S8: 2; S9: 6; S10: 14; S11: 95; +ICF: 3,3; +IFC: 2,2; +IPR: 115200; +DR: 0; +DS: 0,0,2048,6; +CBST: 7,0,1; +CHSN: 0,0,0,0; +CSCS: "IRA"; +CSTA: 129; +CR: 0; +CRC: 0; +CMEE: 0; +CGDCONT: (1,"IP","web.vodafone.de",,0,0) ,(2,"IP","web.vodafone.de",,1,0),(3,"IP","web.voda fone.de",,1,0); +CGEQREQ: (1,4,0,0,0,0,1,1500,"0E0","0E0",3,0,0); +CGEQMIN: ; +CGQREQ: ; +CGQMIN: ; +CGEREP: 0,0; +CGCLASS: "A"; +CGSMS: 3; +CSMS: 0; +CMGF: 0; +CSCA: "",; +CSMP: ,,0,0; +CSDH: 0; +FCLASS: 0; +FDD: 0; +FAR: 0; +FCL: 0; +FIT: 0,0; +ES: ,,; +ESA: 0,,,,0,0,255,; +CRLP: 61,61,48,6; +CPIN: ,; +CGATT: 1; +CGACT: (1,0),(2,0),(3,0); +CPBS: "SM"; +CPMS: "SM","SM","SM"; +CNMI: 0,0,0,0,0; +FTS: 0; +FRS: 0; +FTH: 3; +FRH: 3; +FTM: 96; +FRM: 96; +CCUG: 0,0,0; +CUSD: 0; +CFUN: 1; +CREG: 0; +CGREG: 0; +COPS: 0,0,"",3; +COLP: 0; +CLIP: 0; +CLIR: 0; +CLVL: 2; +CHLD: ; +CTFR: "",; +CCWA: 0,3,7; +CPOL: 0,2,"",0,0,0; +STPD: 0,; +STGC: 0; +STCR: 0,"","",""; +STMS: 0,0; +STTONE: 0,1,500; +STRT: 0; _OPOS: 0,0; _OPSYS: 0,0; _OSBM: 4; _OSQI: 0; _OGCVI: 0; _OSSYS: 0; _OSEC: 0; _OLT: 0; _OLOOP: 0,0 OK When you can talk to the modem as shown above you are nearly done. The card is fully supported and only some configuration is standing between you and a wireless internet connection. While at it you may want to disable the PIN on your SIM card. Otherwise you have to enter it every time the card is inserted or the system is rebooted. This can be a problem, because you can set the PIN only once. Afterwards this will produce an error. Type the following line while connected with the modem and replace "1234" with your valid PIN: at+clck="sc",0,"1234" If you do not want to disable the PIN, you have to enter it with the command at+cpin="1234" now. In both cases it should take only a few seconds before the blinking of both LEDs changes into a blinking of either the green (GPRS) or the blue one (UMTS) alone. The signal quality can be checked with at+csq: at+csq +CSQ: 15,0 OK 15 is a quite good value for UMTS. Possible levels are between 0 and 31. Now you should choose if you prefer UMTS or GPRS connections: AT_OPSYS=0,2 GPRS only AT_OPSYS=1,2 UMTS only AT_OPSYS=2,2 Prefer GPRS AT_OPSYS=3,2 Prefer UMTS The provider is set with AT+CGDCONT, but it should already be preconfigured when receiving your SIM card. When missing, the configuration for Vodafone would be: AT+CGDCONT=1,"IP","web.vodafone.de" All the settings done above will be stored onto the SIM card, so we never have to bother about it again. Next step is the configuration of the internet access via PPP (point to point protocol)! For the pppd daemon to work we have to provide a configuration and a chat script for our provider (Vodafone in this case). After activating pppd in /etc/rc.conf ppp_peers="vodafone" the daemon will read its options from /etc/ppp/peers/vodafone. The directories /etc/ppp and /etc/ppp/peers probably have to be created first. Then I am using a config file like this: noauth connect "/usr/sbin/chat -v -f /etc/ppp/peers/vodafone.chat" /dev/ttyU0 460800 local defaultroute noipdefault usepeerdns novj user "vodafone" password "vodafone" persist maxfail 0 noauth The provider doesn't have to authenticate itself. connect Specifies the chat-script to use when connecting (see below). /dev/ttyU0 The modem device to use. 460800 Usual bps rate for UMTS. local Don't use modem control lines. Not required for UMTS. defaultroute Set the default route to this PPP connection, after it has been successfully established. noipdefault The provider supplies us with a local IP address during IPCP negotiation. usepeerdns Query the provider for DNS addresses and create /etc/ppp/resolv.conf with it. novj Diable Van Jacobsen header compression (Vodafone doesn't support it?). user "vodafone" User name for authentication. password "vodafone" Password for authentication. persist Always try to reconnect, when the connection fails or is lost. maxfail 0 Never give up after failed connection attempts. The chat-script (/etc/ppp/peers/vodafone.chat) is not much more than a simple dialing of *99***1#: TIMEOUT 3 ECHO ON ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED '' '\rAT' '' ATZ TIMEOUT 6 OK 'ATDT*99***1#' As soon as a connection to the provider was established successfully, we have a valid default route and a recent resolv.conf in /etc/ppp/. Now you could either use /etc/ppp/ip-up to copy resolv.conf or just create a link: # cd /etc # ln -s /etc/ppp/resolv.conf resolv.conf That's all. Every time the system is booted you will be connected to the internet via UMTS, provided it is available. Now some fine tuning could be done. For example to delay pppd until /dev/ttyU0 is ready, or to allow LAN connections via DHCP, when you returned to your office. Frank Wille, September 2008 |
|
|||
i came across this quick guide to seting it all up and yep heeeeeee it is all working
here is that guide : Connecting to the Internet with UMTS on NetBSD All you need is a laptop with cardbus slot (PCMCIA) and a datacard which is supported by NetBSD. The card will appear as an USB modem to the kernel. In my example I am using an Option N.V. MC3G (Vodafone Mobile Connect Card). First of all you have to make sure the datacard is recognized by the kernel: ohci0 at cardbus0 function 0: vendor 0x1045 product 0xc861 (rev. 0x10) ohci0: OHCI version 1.0, legacy support usb5 at ohci0: USB revision 1.0 uhub5 at usb5: vendor 0x1045 OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub5: 2 ports with 2 removable, self powered ubsa0 at uhub5 port 1 ubsa0: Vodafone Vodafone Mobile Connect Card - 3G, rev 2.00/0.00, addr 2 ucom0 at ubsa0 portno 0 ucom0 means we have successfully attached a serial adapter. ugen0 would mean the card is not yet supported. The device can be accessed through /dev/ttyU0. For a test, we add the following line to /etc/remote to communicate with the modem: ucom0:dv=/dev/ttyU0:br#460800a=none:dc: Then connect to the modem as root and try some AT commands: # tip ucom0 connected at OK atz OK ati Manufacturer: Option Wireless Technology Model: 129 Revision: 3.1.2 (Date: Mar 08 2004, Time: 11:54:30) OK at&v &C: 1; &D: 2; &F: 0; E: 1; I: 0; L: 0; M: 0; Q: 0; V: 1; X: 4; Z: 0; S0: 0; S3: 13; S4: 10; S5: 8; S6: 2; S7: 50; S8: 2; S9: 6; S10: 14; S11: 95; +ICF: 3,3; +IFC: 2,2; +IPR: 115200; +DR: 0; +DS: 0,0,2048,6; +CBST: 7,0,1; +CHSN: 0,0,0,0; +CSCS: "IRA"; +CSTA: 129; +CR: 0; +CRC: 0; +CMEE: 0; +CGDCONT: (1,"IP","web.vodafone.de",,0,0) ,(2,"IP","web.vodafone.de",,1,0),(3,"IP","web.voda fone.de",,1,0); +CGEQREQ: (1,4,0,0,0,0,1,1500,"0E0","0E0",3,0,0); +CGEQMIN: ; +CGQREQ: ; +CGQMIN: ; +CGEREP: 0,0; +CGCLASS: "A"; +CGSMS: 3; +CSMS: 0; +CMGF: 0; +CSCA: "",; +CSMP: ,,0,0; +CSDH: 0; +FCLASS: 0; +FDD: 0; +FAR: 0; +FCL: 0; +FIT: 0,0; +ES: ,,; +ESA: 0,,,,0,0,255,; +CRLP: 61,61,48,6; +CPIN: ,; +CGATT: 1; +CGACT: (1,0),(2,0),(3,0); +CPBS: "SM"; +CPMS: "SM","SM","SM"; +CNMI: 0,0,0,0,0; +FTS: 0; +FRS: 0; +FTH: 3; +FRH: 3; +FTM: 96; +FRM: 96; +CCUG: 0,0,0; +CUSD: 0; +CFUN: 1; +CREG: 0; +CGREG: 0; +COPS: 0,0,"",3; +COLP: 0; +CLIP: 0; +CLIR: 0; +CLVL: 2; +CHLD: ; +CTFR: "",; +CCWA: 0,3,7; +CPOL: 0,2,"",0,0,0; +STPD: 0,; +STGC: 0; +STCR: 0,"","",""; +STMS: 0,0; +STTONE: 0,1,500; +STRT: 0; _OPOS: 0,0; _OPSYS: 0,0; _OSBM: 4; _OSQI: 0; _OGCVI: 0; _OSSYS: 0; _OSEC: 0; _OLT: 0; _OLOOP: 0,0 OK When you can talk to the modem as shown above you are nearly done. The card is fully supported and only some configuration is standing between you and a wireless internet connection. While at it you may want to disable the PIN on your SIM card. Otherwise you have to enter it every time the card is inserted or the system is rebooted. This can be a problem, because you can set the PIN only once. Afterwards this will produce an error. Type the following line while connected with the modem and replace "1234" with your valid PIN: at+clck="sc",0,"1234" If you do not want to disable the PIN, you have to enter it with the command at+cpin="1234" now. In both cases it should take only a few seconds before the blinking of both LEDs changes into a blinking of either the green (GPRS) or the blue one (UMTS) alone. The signal quality can be checked with at+csq: at+csq +CSQ: 15,0 OK 15 is a quite good value for UMTS. Possible levels are between 0 and 31. Now you should choose if you prefer UMTS or GPRS connections: AT_OPSYS=0,2 GPRS only AT_OPSYS=1,2 UMTS only AT_OPSYS=2,2 Prefer GPRS AT_OPSYS=3,2 Prefer UMTS The provider is set with AT+CGDCONT, but it should already be preconfigured when receiving your SIM card. When missing, the configuration for Vodafone would be: AT+CGDCONT=1,"IP","web.vodafone.de" All the settings done above will be stored onto the SIM card, so we never have to bother about it again. Next step is the configuration of the internet access via PPP (point to point protocol)! For the pppd daemon to work we have to provide a configuration and a chat script for our provider (Vodafone in this case). After activating pppd in /etc/rc.conf ppp_peers="vodafone" the daemon will read its options from /etc/ppp/peers/vodafone. The directories /etc/ppp and /etc/ppp/peers probably have to be created first. Then I am using a config file like this: noauth connect "/usr/sbin/chat -v -f /etc/ppp/peers/vodafone.chat" /dev/ttyU0 460800 local defaultroute noipdefault usepeerdns novj user "vodafone" password "vodafone" persist maxfail 0 noauth The provider doesn't have to authenticate itself. connect Specifies the chat-script to use when connecting (see below). /dev/ttyU0 The modem device to use. 460800 Usual bps rate for UMTS. local Don't use modem control lines. Not required for UMTS. defaultroute Set the default route to this PPP connection, after it has been successfully established. noipdefault The provider supplies us with a local IP address during IPCP negotiation. usepeerdns Query the provider for DNS addresses and create /etc/ppp/resolv.conf with it. novj Diable Van Jacobsen header compression (Vodafone doesn't support it?). user "vodafone" User name for authentication. password "vodafone" Password for authentication. persist Always try to reconnect, when the connection fails or is lost. maxfail 0 Never give up after failed connection attempts. The chat-script (/etc/ppp/peers/vodafone.chat) is not much more than a simple dialing of *99***1#: TIMEOUT 3 ECHO ON ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED '' '\rAT' '' ATZ TIMEOUT 6 OK 'ATDT*99***1#' As soon as a connection to the provider was established successfully, we have a valid default route and a recent resolv.conf in /etc/ppp/. Now you could either use /etc/ppp/ip-up to copy resolv.conf or just create a link: # cd /etc # ln -s /etc/ppp/resolv.conf resolv.conf That's all. Every time the system is booted you will be connected to the internet via UMTS, provided it is available. Now some fine tuning could be done. For example to delay pppd until /dev/ttyU0 is ready, or to allow LAN connections via DHCP, when you returned to your office. Frank Wille, September 2008 |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How - To install GNOME vile I install OpenBSD ? | looop | OpenBSD Installation and Upgrading | 6 | 24th April 2010 08:58 PM |
post-install green text w/o shell | standardFoo | NetBSD Installation and Upgrading | 5 | 2nd May 2008 11:12 PM |