Re: [SLUG] 486 sans dial-up? No Slashdot for you... Come back, one year!
Hi all, Well, I've tried Andrew's "" ATZ\d\d idea, to no avail (even in conjunction with Brian's previously mentioned init string), and although I thought Alexander's gpm-in-the-way idea might have been it... Sadly, no. I removed gpm a while ago when I pulled mousey out. It still baffles me though... Surely I've been through *every* ppp-related configuration file already? :D - Jeff --- e: [EMAIL PROTECTED] w: rsn i: 16341281 (jdub!) q: "A rest with a fermata is the moral opposite of the fast food restaurant with express lane." - James Gleick, Faster -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
Re: [SLUG] 486 sans dial-up? No Slashdot for you... Come back, one year!
Someone unmentioned as yet, do you by any chance have gpm running on that port? The modem lights may turn on and go off again when the script times out waiting for OK if something else is using the serial port. gpm may or may not print a "Danger Will Robinson!" (ok well it doesn't say that) message to /var/log/messages. Alexander Else Internet Operations Technician OzEmail / UUNET Asia Pacific Operations -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
Re: [SLUG] 486 sans dial-up? No Slashdot for you... Come back, one year!
Is LINUX talking on the right IRQ? If not, this causes things to work but vey slowly - including causing lights to blink but not getting anywhere. If your modem is set to an IRQ different to what LINUX thinks /dev/modem should be, you can change it with the setserial command or put the fix permanently in /etc/rc.d/rc.serial - something like: setserial /dev/modem irq 3 should do the trick (assuming the 'correct' irq is 3). trying to talk to the modem with minicom should give you a clue if this is the problem - if things take a long time, bet on the irq being the problem. If it doesn't work at all, then it may be something else. If you don't know the irq, you CAN: setserial /dev/modem irq 0 (where 0 means no irq instead of irq = 0) The kernel will then communicate with the modem in a different way. This is only an interim solution though, you should find out what the real irq is and do the rc.serial stuff when you know. Good luck, Gregg Jeff Waugh wrote: Hi all, In the middle of a procrastination-induced bedroom rearrangement, I decided to try getting my reliable old 486 to dial up properly. Sadly, it's a very confused little creature. It's running RedHat 6.0, and kernel 2.2.14 When issuing "ifup ppp0", the modem lights flash and finally rest with the three usual lights on (HS, MR and PW), plus the DTR light. It stays like this for a while, until the connection attempt times out. It doesn't even get to the dialtone. The same modem works fine on my chunky machine, so I thought duplicating the setup might work. I copied (and set correct permissions on) /etc/ppp/* and /etc/sysconfig/network-scripts/*ppp* but still to no avail. Same results - the DTR light goes on and times out. I forgot to grab a tail of the log file before I swapped the modem back to this machine, but it really didn't say too much beyond "Well, that mustn't have worked". There's essentially no difference between the setups (serial ports, etc). The kernel config is based on the same file, too. I'm using a simple ATZ for the init string. Any ideas? Jeff --- e: [EMAIL PROTECTED] w: rsn i: 16341281 (jdub!) q: "A rest with a fermata is the moral opposite of the fast food restaurant with express lane." - James Gleick, Faster -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text -- Gregg Jørgen Suaning Graduate School of Biomedical Engineering University of New South Wales Sydney, Australia 2052 Tel: + 61 2 9385 3916 Fax: + 61 2 9663 2108 Pager (via e-mail): [EMAIL PROTECTED] http://gsbme-lx040.gsbme.unsw.edu.au/~greggs "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." - unknown -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
Re: [SLUG] 486 sans dial-up? No Slashdot for you... Come back, one year!
At 02:07 13/02/2000 +1100, Andrew Macks wrote: Actually, you just reminded me of something I had to do here. Try "" ATZ\d or "" ATZ\d\d for the init. Andrew. The other things that have mentioned indicate that for some reason the modem is receiving responses but the responses it is sending are not being received, or not received by the correct process. This is likely to be because either there is an irq conflict or another program accessing the device. Jeff has mentioned that minicom worked for him so, on the assumption that no relevant settings have been changed since seeing the problem, i'm going to assume that all is well in terms of IRQs. This means that something else is accessing the device. I'm sticking with my gpm theory :) If gpm is running, would minicom be able to assert priority in access to/from the device? I'm thinking that this is why minicom is working but chat, lowest of the low, is still SOL. Alexander Else Internet Operations Technician OzEmail / UUNET Asia Pacific Operations -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
Re: [SLUG] 486 sans dial-up? No Slashdot for you... Come back, one year!
Does the serial card have a 16550 UART on it? If not, you're probably overflowing the port by the high speed. 19200 is the best you can expect out of an 8250 (aka: 16450) chip. Yes on my 8250 (486/100 cpu) 19200 is reliable, 38400 works but gets errors which ppp corrects, higher is madness. Got a twin 16550 board from David Reid cheap, yet to config. -- Brian Martin, [EMAIL PROTECTED] Future Software Pty Ltd, Sydney, Australia. -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
Re: [SLUG] 486 sans dial-up? No Slashdot for you... Come back, one year!
If not, you're probably overflowing the port by the high speed. 19200 is the best you can expect out of an 8250 (aka: 16450) chip. Actually to be accurate, the 8250 and 16450 are distinct beasts. The latter has a 1 byte buffer. Neither are to be used for high-speed modems though. -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
Re: [SLUG] 486 sans dial-up? No Slashdot for you... Come back, one year!
hi, i had the same trouble once. turned out to be a 25-9 connecter which didnt have all the pins. some old ones were missing some pins. swapped it with a new fully pinned one and away she went. so check your cabling, use connectors that have all the pins in place. even check the pinouts with a meter etc. Jeff Waugh wrote: Hi all, In the middle of a procrastination-induced bedroom rearrangement, I decided to try getting my reliable old 486 to dial up properly. Sadly, it's a very confused little creature. It's running RedHat 6.0, and kernel 2.2.14 When issuing "ifup ppp0", the modem lights flash and finally rest with the three usual lights on (HS, MR and PW), plus the DTR light. It stays like this for a while, until the connection attempt times out. It doesn't even get to the dialtone. The same modem works fine on my chunky machine, so I thought duplicating the setup might work. I copied (and set correct permissions on) /etc/ppp/* and /etc/sysconfig/network-scripts/*ppp* but still to no avail. Same results - the DTR light goes on and times out. I forgot to grab a tail of the log file before I swapped the modem back to this machine, but it really didn't say too much beyond "Well, that mustn't have worked". There's essentially no difference between the setups (serial ports, etc). The kernel config is based on the same file, too. I'm using a simple ATZ for the init string. Any ideas? Jeff --- e: [EMAIL PROTECTED] w: rsn i: 16341281 (jdub!) q: "A rest with a fermata is the moral opposite of the fast food restaurant with express lane." - James Gleick, Faster -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text -- _|_ | Thanks, iCafe PTY Limited Ben DonohueWeb Hosting Design [EMAIL PROTECTED]Small Business Office Networks Ph. 0011 61 2 9705 7520 http://www.icafe.com.au Mobile: 0417 018 600ACN 080 665 907 Freedom isn't doing what you want... Freedom is knowing what to do -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
Re: [SLUG] 486 sans dial-up? No Slashdot for you... Come back, one year!
You said that your using a 486, now pentiums were the first boards introduced with built in ide/floppy com/serial ports. Not necessarily! There were heaps of boards manufactured with com/ide etc onboard. Also, this machine happens to be a Compaq, so the board was custom built to include the lot. So is there possibly a hardware error with your com card??? No, the com ports work A-OK for other purposes, and the modem works under other operating systems on the same machine. Jeff --- e: [EMAIL PROTECTED] w: rsn i: 16341281 (jdub!) q: "For a list of ways detailing how technology has failed to improve our lives, please press 3." -- SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au To unsubscribe send email to [EMAIL PROTECTED] with unsubscribe in the text
