Date: Mon, 7 Jun 1999 13:52:46 -0700 (MST) From: John Reynolds~ <jreynold@sedona.ch.intel.com> To: freebsd-questions@freebsd.org Subject: sio code--how much changed from 2.2.x -> 3.x? Message-ID: <14172.12574.525740.416458@hip186.ch.intel.com>
next in thread | raw e-mail | index | archive | help
Hello FreeBSD'ers, I have recently configured a new box with 3.1-RELEASE and am having a terrible time getting any sort of comm program running with the modem that I purchased. The modem is an ActionTec DeskLink Master (ISA) V.90. I have the modem in on COM2 and can call into my ISP under Windows '98 just fine (except I can't connect to their V.90 lines--the modem has never auto-negotiated back down to a proper speed, I must call their V.34 lines). However, under FreeBSD, when I load up minicom (1.82 I think--whatever version came with 3.1-RELEASE in the ports tree) I cannot connect to even the V.34 lines at my ISP. I can hear the modem call out, then the negotiate 'screech' then I get "NO CARRIER". The modem just hangs up as soon as it's about to make a good connection (or so it seems--I don't know if it's the ISP hanging up, suffice to say I can use this same modem under Win98 and a different computer with different modem to the same ISP very reliably). I thought at first "maybe this port of minicom is broken" (which still may be true--I don't know what I'm fighting here!), so I tried to get userland PPP working. I have my PPP setup correct and verified (having another FreeBSD machine in the house connecting to the same ISP) but I get the same wierd behavior. When PPP is trying to dial in, I hear the dial, hear some negotiation, then boom--it hangs up. Adding to the wierdness, I took my friend's USR modem, plugged it into my 3.1-RELEASE machine and could at least call into my ISP's numbers with minicom--but I couldn't use the auto-dialer--I had to type ATDT<number> to get it to successfully connect. However, userland PPP didn't even like this USR modem and did the "hangup at connection" thing right away. The thing that makes me suspect something in 3.x sio code is that I can take this modem and plug it into my other FreeBSD box running 2.2.8-STABLE and it works fine with minicom (previous version...1.75 I think) and userland PPP. I've searched the PR database looking for stuff related to sio code to no avail so I'm asking here: what sorts of changes were made from 2.2.x to 3.x in the sio code? Were there major architectural changes that might have introduced the bugs when dealing with certain chipsets (the ActionTec modem uses a lucent chipset BTW)? Any sio programmer gurus out there want to speculate? My machine config is as follows: ASUS P2B-DS motherboard with 1 Pentium II 450, BIOS 1009 serial and parallel port stuff all build onto mo-board (don't know make and model however) ActionTec Desklink master, ISA, on COM2 I've never had any problems switching modem after modem in 2.x (been using FreeBSD since 2.0.5 and when 14.4k modems were "it") so this problem has me quite befuddled. Does anybody have other advice? Things to try? Are there any "SIO_DEBUG" config options or something that I could compile my kernel with to provide more information as to what's going on in that layer? I'm open to all suggestions! Thanks, -Jr ps: I can't CVSup to 3.2-STABLE to see if things get better either ... cuz I can't get my PPP link up :) ... quite a catch .22 :-| -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14172.12574.525740.416458>