Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close
typodupeerror
×
BSD Operating Systems

Where Art Thou, BSD Winmodem Project? 29

Posted by timothy from the alack-alas dept.
JRAC writes: "Not long ago, anyone with a winmodem had pretty much no hope getting it to work under Linux. Now with projects like linmodems.org, Linux users with a dreaded winmodem actually have a chance at getting Linux to detect their modem. I myself am a Linux user with a winmodem which works fine, because mine has a Lucent chipset, which has fairly good Linux driver support. But I am trying to migrate to FreeBSD. I knew when I installed BSD that I had no chance getting my modem working, but it didn't bother me. Now after spending hours searching Google trying to find some Lucent drivers for FBSD, I have started to wonder when is someone going to start a BSD winmodem project? Aren't there any winmodem users out there running BSD that are tired of downloading drivers only to find they don't work. What we really need is bsdmodems.org"
This discussion has been archived. No new comments can be posted.

Where Art Thou, BSD Winmodem Project? More

Where Art Thou, BSD Winmodem Project?

Comments Filter:
  • I use FreeBSD as a home machine, and went through some pain to figure it wouldn't recognize my modem because it was a WinModem, and replaced it with a conventional modem.

    I think the reason there isn't more happening here is that FreeBSD is focused more on the server market. If you are running a server, you probably aren't using modem, you probably wouldn't want a WinModem, or you wouldn't mind paying for another modem if you needed to.

    I would like to see the project happen as well. However, I knew that Linux has going to have better support for the Desktop environment when I set up the machine, and could have used that and gotten WinModem support on the same hardware if that was a priority.

    In my case, I use FreeBSD widely for projects at work [summersault.com], so I chose to keep things simple by keeping the environment consistent at home.

  • Why? (Score:2, Insightful)

    by Detritus ( 11846 )
    This isn't meant to be flamebait, but why bother? It sounds like a great deal of work just to implement a fundamentally flawed concept. Real modems are cheap, work well and don't suck up expensive CPU cycles.

  • The drivers exist as .ko (Score:2, Informative)

    by Leimy ( 6717 )
    Kernel modules have existed for linmodems on BSD in the past. I "stumbled" over them a few months ago... [up to 6 months ago]. Check daily.daemonnews.org... They may have some information...

    Or you could just buy an external modem like everyone else in the world suggests.. Of course if you have a laptop this is a completely different problem. FBSD currently has shaky cardbus support so you woul have to obtain a REAL PCMCIA modem card and not a 32bit cardbus card. [PCMCIA is only 16bit if I recall correctly]
  • There's no funky name like "linmodem" that's appropriate for BSD.
  • I have no idea what would be involved, or if you have the time or inclination, but this sounds like it could be an ideal project for you to try to write your own drivers.

    Of course it'd be a task made harder without access to the internet, so you should probably buy another modem so you're able to get at those valuable online resources. :))
  • Spend a little extra for an actual modem next time. Why do people buy garbage anyway?

    - A.P.
  • In theory a winmodem could process the caller ID signal, right? Has anyone actually done this, or at least started to work on it?
    • I've never done this with a winmodem, but just plain old modems do this fine. AT#CID=1 (or #CID=2 for unformated output). I assume if you got a winmodem working and it supported caller id, it'd be the same.
  • though a native bsdmodem [sic] driver doesnt exist, the very kind mr watanabe kiyoshi has made a shim which allows the linux lucent lt linmodem drivers to work with freebsd.

    been using it the past 6 months without any problems whatsoever. you could find it at the end of this link [gsoft.com.au] on daniel o'connor's website.

    nevertheless, i echo the call for a bsd native software modem driver. there should be such an animal.

    • I actually have been trying to get my Lucent winmodem to dial with FreeBSD 4.3. I successfully got the modules etc. to install and I have a dial tone, but the dial tone stops after a while and I get an engaged (busy) tone.
  • I am aware of BSD focusing on the server market. But some home users do like to run BSD. On the subject of why don't I just buy a hardware modem. Well, one example of hardware modems being just as useless as winmodems, is, when I first switched to Linux, I bought a hardware modem, thinking I would have it up and running in no time. But I discovered that the hardware modem I bought, was not Linux compatible. The wonderful, works with anything, hardware modem still required drivers. Another reason why I'm stuck with a winmodem, is because I have no choice. I have no USB or serial port for a good external modem. I'm not going to waste my time and money (that I don't have) buying a whole new machine when there could be drivers being developed. I completely understand why most of you would think it's a stupid idea, because most of you have the wonderful choice of using a highspeed broadband connection that uses PPPoE or DHCP. But not all of us have that choice, we are stuck with dialup and pathetic winmodems. A few years back, Linux was no where near close to becoming a decent desktop PC OS, but now it's alot better, which means Windows users are switching to it, and bringing their winmodems along for the ride. As we saw Linux become more popular, we saw the winmodem problem get worse. BSD will most likely become more popular, and until we all live in a high speed future where everyone has a T1 line, we're going to have winmodems. A BSD winmodem project doesn't concern BDS users with broadband or a nice modem that works with any OS, it concerns winmodem users that are considering BSD. I'm not saying we should just start a BSD winmodem project right now, but it's something we should think about. I am happy using Linux with my winmodem. yes, it does suck my CPU dry, but it's all I've got.

  • http://www.geocities.com/wtnbkysh/ [geocities.com]

    Hopefully... Didn't try it yet but it looks like it uses the linux binary module with some FreeBSD patch code.

    • That is not a generic winmodem driver, it is a Lucent chipset driver. I actually use this driver and it works fine, but it doesn't help any non-Lucent users.

Slashdot Top Deals

Real Programmers don't eat quiche. They eat Twinkies and Szechwan food.

Close