zoom modem firmware download

[blister]

Hi,

I've had no luck in configuring a Creative Blaster serial modem, like many others online, and have decided that the Zoom 3049C serial modem is the one to go for.

But I went to the Zoom support site and it looks as if I'd have to attach the modem to a Windows PC and download a firmware update for Linux. As a newbie I don't like the sound of that.

Quite apart from the mechanics of the download, wouldn't the fact that it's come through Windows affect it?

[banzaikai]

A file, by any other OS, will still flash just as sweet...

(Apologies to The Bard)

What they're talking about is "Flashing" the EEPROM in the modem. They just haven't gotten off their duffs to write a Linux-native way of doing it, so you need a Winbox to do it. In any event, yes, flashing the file in Windows is the same as any other OS, since the file is a "Binary", and is OS-independant (even my VIC-20 can flash a chip, provided I've got the required memory to hold it).

What'll happen is this (more-or-less):

1) Uncompress the binary file
2) Check modem to see if it's already got >= version #
3) If not, then send the binary data to the "flasher"
4) Check to make sure it wrote/saved okay (checksums)
5) Reset modem for changes to take effect (runs new programming allowing the Linux features to be used)
6) Once running under Linux, you'll then forget about Windows alltogether (a good thing)

If you don't already have one, I'd recommend a UPS on that computer if you'll be flashing things, as even a momentary power hiccup will really ruin your day.

banzai "mad flasher" kai

[bs_texas]

Originally posted by blister
But I went to the Zoom support site and it looks as if I'd have to attach the modem to a Windows PC and download a firmware update for Linux.
Where did you see that?

Before DSL, I was using a Zoom 3049c. I don't recall upgrading the firmware. I think most external serial modems will work with linux out of the box.

[blister]

Hello Banzaikai and BS-2003,

Well, I saw the download thru Windows information on the Zoom support website. I said on my original post that I didn't fancy it, and having read what I'd have to do, I've now gone right off the idea.

Golly, I'm a newbie. I've got to the stage where I can install the couple of distros I've chosen but that's all. Checksums, flashers and binary files are beyond me.

I believed what I read that serial modems worked out of the box and bought the Creative model to find that it didn't. I don't want to waste any more money.

Isn't there a distro that makes installing modems easy? Isn't there a modem mainly designed to work with Linux? Linux should be a lot easier than this.

Thanks for your replies. Any more advice would be welcomed.

[bs_texas]

Originally posted by blister
Isn't there a distro that makes installing modems easy? Isn't there a modem mainly designed to work with Linux? Linux should be a lot easier than this.

hehe... welcome to the club. :cool:

[banzaikai]

Well...

I looked up the modem, and it should work (just not the V.92 features). Try using KPPP to set it up, selecting the actual /dev/ttyS# that it's on:

com1 = /dev/ttyS0 (3F8)
com2 = /dev/ttyS1 (2F8)
com3 = /dev/ttyS2 (3E8)
com4 = /dev/ttyS3 (2E8)

(if you type it in, remember the "S" is uppercase!)

KPPP usually defaults to /dev/modem, but I've found going "right to the source" works better. At least, it did with my NewComm V.90/56kefx.

Once the port is found, then it should inquire the modem from there - you'll see those lights on the front blink like crazy. A few seconds later, it should pop up with the correct modem type (probably "Hayes V.90 or compat.").

Afterwards, you're good to go. Just type in the ISP stuff, and save settings.

If you still want the Zoom, it'll pretty much be the same. Remember, the flashing just updates the firmware - you don't need to flash to get things going, as the old "Hayes" default usually works. The flash just provides for better support for the V.92 features (Modem-on-hold, Internet call-waiting, etc.). If you're just dialing out, then don't sweat it.

banzai "Rarely over 46Kbps" kai

[blister]

Hello Banzakai,

I have, unfortunately, tried to use KPPP a dozen times. I enter ttyS1 (my modem is on the com2 port) and I get nothing like you describe.

One light, the TR (terminal ready) light comes on but nothing else. Certainly no flashing lights. The screen panel just shows 'initialising modem' and hangs there.

Now I've just discovered by trawling the Web that the CHAP authentication code used by my ISP won't work with Linux. However I've never got that far.

I'm using an old Windows computer at the moment and I'm wondering if I should connect the modem to it and see if it works. Perhaps the modem is at fault.

I appreciate your interest in this.

Best wishes,

[banzaikai]

Errr...

My old (RH 7.2) version of Linux supports PAP/CHAP, so it will work perfectly with your ISP.

The problem seems to be your cable, modem, or com port. Things to check:

Make sure com2 is enabled in your BIOS (usually under "Peripherals", set up as PortB or COM2 at address 2F8). Com2 will use Irq3, so check that there are no conflicts - and disable Plug-aNd-Play while you're in there.

The Modem Ready (MR) light tells you the modem has initialized, and is waiting commands. The Terminal Ready (TR) is set by the computer before commands are sent via Transmit Data (TxD) and Recieve Data (RxD) lines. How the data is sent is up to you. My preference is for RTS/CTS (Hardware) handshaking, which requires a 7-wire cable. If you don't have one, then you'll have to use Xon/Xoff protocol (slower).

Your lights may vary, but mine include:
AA = Auto Answer mode (for faxes, voicemail, or BBS use)
CD = Carrier Detected - modem on other end
CS = Connect Speed - on my modem, V.90 in use
OH = Off Hook - dialing/in use
RTS = Request to Send (handshake)
CTS = Clear to Send (handshake)

These lights will let you know what's going on, but if you're not getting anything on TxD/RxD (or RTS/CTS), then my hunch is you have a cable that has pins 2 & 3 reversed. Popping the modem on a Winbox (or another box of any kind) will help us out. You may also try a different cable.

If you have access (or happen to have one -like me) to an RS-232 checker, this will help out by letting you know if the port is at fault. Radio Shack should still sell them... Hmm... Can't find it on the website. Let's go to JDR... http://www.jdr.com/interact/item.asp?itemno=GR-GENDERMT
You'll need two 25-9pin adaptors, or check for a DB9 version. But this is for later, until then try:

1) Plug modem into Winbox. If it works, then cable and modem are okay. If it doesn't work, then either cable or modem is shot.

2) Plug back into Linuxbox, and try using com1 (ttyS0) if possible. If modem doesn't work, then problem is with either the port or dialer. Port problems can include:
A) Reversed pinout (swapped pins)
B) Port not enabled (BIOS)
C) Power to port control logic (+5, +12, and -12 V)
D) Small "pico" fuses on port blown (if mobo/card designer used them)
E) Bad RS-232 converter chips (1488/89 type), typically non-repairable for laypersons.

3) If lights flash, but modem still doesn't get queried, then it's the dialer (KPPP) setup. Try using hardware (RTS/CTS) handshaking, 115200 baud, 8N1 dataset, and PAP/CHAP protocol. Use Generic or Hayes Compat. modem setting.

Again, even if the V.92 doesn't work with Linux that well, the modem should still run as a V.90 just fine, as it does with my NewComm on an old 2.4.17 kernel. In fact, this very modem was being used on my Amigas (any) with JRComm and MiamiTCP/iBrowse. No problems.

Let me know what you find out...

banzai "My C=64 uses Bob's Term Pro" kai

[blister]

Hello Banzaikai,

I'm connected to JustLinux via my Creative Blaster modem. Hooray, hooray, hooray.

I connected the modem to my old Windows computer and it worked fine. When I reconnected it to my Linux computer I used the 1st serial port instead of the second one I'd been using; I checked the Bios and found that the port wasn't at 2F8; disabled plugnplay; selected RTS/CTS and PAP/CHAP in KPPP, and away I went first time.

I dunno exactly which of the above did the trick - maybe more than one of them - but, whichever, it was all down to you and the trouble you've taken.

I don't know where you get all your knowledge from, but I really appreciate your willingness to share it with a newbie like me. I was on the verge of throwing the modem and the computer in the bin a couple of times but, now, I can get down to learning something about Linux.

Many, many thanks. I'm in your debt.

[KarrottoP]

Somebody can correct me if I am wrong....I am at work late and these may be the rantings of a crazy man.

One of the com ports on the back of you computer is shared with an internal com device....probably a modem of some sort....and thats why it will not function......this is done on the hardware level not in the software.....I have a zoom modem that I am using for a fax server I recently got set up and it works great....I have found that internal modems (softmodems/winmodems) are garbage for linux...but that is just as well, who needs that bulky stuff eating away at your precious processing power......Ok fine Ill go back to getting this stupid server upgraded.

[banzaikai]

from: blister
I'm connected to JustLinux via my Creative Blaster modem. Hooray, hooray, hooray.


Told ya it'd work :D
As they say in Nihon, "Banzai!"


from: blister
I checked the Bios and found that the port wasn't at 2F8


That was the problem. If you tell Linux (or any x86 machine) to look for something at com2/ttyS1, it's gonna look at port 2F8, and nowhere else. Since most BIOSs let you set the port address, I figured portB wasn't at 2F8 (or there was something wrong with it).


from: blister
I don't know where you get all your knowledge from, but I really appreciate your willingness to share it with a newbie like me. I was on the verge of throwing the modem and the computer in the bin a couple of times but, now, I can get down to learning something about Linux.
Many, many thanks. I'm in your debt.


I'll ask the Mods for a raise. What's +10% of $0.00? ;)

I got my start way back when (1977?) with the TRS-80 Model I, got hooked on Commodores (VIC-20 through Amiga 4000), and now have a couple of Linux boxes. All still work, by the way.

You can pay me back by helping out anyone here that needs it. It's why JL is here, after all. And keep asking questions...


from: Karrottop
One of the com ports on the back of you computer is shared with an internal com device....probably a modem of some sort....and thats why it will not function


Not always/not quite. If the port were shared, you'd get a POST error (address conflict). If the Irq were the same, you wouldn't, as Irqs can be shared. I'm sure it's the latter you're thinking of.
In the good ol' days of 8088/8086 PCs, you only had 8 Irqs (0-7). Obviously, not enough for everyone. So, they allowed for the odd com ports (1/3) to share Irq4, and the even (2/4) to share Irq3. As long as only one thing was happening at a time (with DOS, this was the case), there wasn't a problem. Once things got to "pseudo" multi-tasking (Win3x), then this got to be a problem. Nowadays, the internal modems set themselves up as com5 (ttyS4) at ports like "C800" or somesuch, well away from the lower legacy standards. But since blister was using one of the legacy ports, it had to be something on the order of what I mentioned (and it was!).

banzai "Real Multitasker" kai