Linux-Hardware Digest #680, Volume #14 Tue, 24 Apr 01 16:13:06 EDT
Contents:
Permedia 2v meltdown (nobody)
Re: 3rd Day Same Modem and Same story......
Re: 3rd Day Same Modem and Same story......
Re: Modem trouble (Jonadab the Unsightly One)
Re: Where can I buy bridgeboards? (CBFalconer)
EZonics II USB Webcam (Young4ert)
Re: ABIT KT7A-RAID ("Ferry van Doorn")
NEC 3.5" 1.2MB Floppy support ("Jan")
Re: LINUX on Compaq Deskpro XL ("Andreas Adler")
pctv miro ("H Brinkman")
Pentium I 133 +32 MB enough ? ("Jaap L.A.")
Re: 2.4.3, ATA100 & Hedrick's patches (Alberto BARSELLA)
can print only one page at a time (Sebastian Bossung)
Re: Pentium I 133 +32 MB enough ? (Philipp Lehman)
SMP, RH7.1 and Intel -- Can't they all just get along? (Jeff)
Re: Via82c driver for sound (Peter Christy)
Re: SMP, RH7.1 and Intel -- Can't they all just get along? ("Steve Wolfe")
kppp problems... ("Karim R. Sobhi")
----------------------------------------------------------------------------
From: nobody <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Permedia 2v meltdown
Date: Tue, 24 Apr 2001 15:15:54 GMT
A friend wrote r.e. his experience with a permedia 2v chip based card:
"The video card was the Eontronics Picasso, running the Permedia 2v
chipset. When I moved the mouse, the screen would pop with a rather
annoying sound, flash blue, then suddenly the monitor would shut down.
(Iiyama S901GT) I watched with alarm as a growing series of little dots
began to appear on my screen... a few more as the days went by. Finally
one evening, there was a noticable click.. black screen. nothing. POST
went "long beep - short beep short beep short beep" - which meant a
video RAM failure. Sure enough the card was toasted."
Anyone else heard of or experienced such a failure ?
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: 3rd Day Same Modem and Same story......
Date: Tue, 24 Apr 2001 15:30:03 -0000
Cute. Humorous. Uhm, interesting! Useful? No.
Fluri Dave wrote:
>
>
> "Hello, Mac's garage. May I help you?"
>
> "Umm, yes. My car won't go."
>
> "I see. What seems to be the trouble with it?"
>
> "Well, it won't go. Someone told me it might be the left-handed
> widget."
>
> "I see. Can you bring it in so we can have a look at it?"
>
> "Well, no, 'cause it won't go. But I did go to the parts place and
> I bought a left-handed widget."
>
> "And?"
>
> "No go."
>
> "Did you install the widget?"
>
> "Yes."
>
> "And did it make any difference?"
>
> "No, except that now, when I look under the car in the engine area, I
> see a left-handed widget lying on the ground."
>
> "How did you install it?"
>
> "I put it under the hood, where it goes."
>
> "I'm afraid you're going to have to bring your car in if you want us
> to fix it. I can send a tow-truck around."
>
> "No thanks, nazi pig!" *CCCLLLLIIIIICCCCCCKKKKKKK*
>
> --
>
> Dave Fluri
> North Bay, Ontario Canada
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: 3rd Day Same Modem and Same story......
Date: Tue, 24 Apr 2001 15:30:03 -0000
Oooh, I wish you hadn't said that. Now you will get all manner of postings
on the relative values of various operating systems. None of which will
help you (or me, as I am as new as you and have been following this
thread) get the answers you need. Peter might have been crass in his
remarks about your english, but you need not give him any fun by replying
to his childishness. He did offer some helpful information, tho. Take it.
Use it, ignore the rest.
Tina Carter wrote:
>
>
> My problem is with "someone" and not with entire linux users, What's
worst
> is that even some microsofty fight me now :(
> Anyway I'm not mac user but MAC is better compare to Windows me's
features.
>
> As far as nazism goes there is lot here.
>
>
> "Fluri Dave" <[EMAIL PROTECTED]>
wrote
> in message news:94s6d6$676$[EMAIL PROTECTED]...
> > "Hello, Mac's garage. May I help you?"
> >
> > "Umm, yes. My car won't go."
> >
> > "I see. What seems to be the trouble with it?"
> >
> > "Well, it won't go. Someone told me it might be the left-handed
> > widget."
> >
> > "I see. Can you bring it in so we can have a look at it?"
> >
> > "Well, no, 'cause it won't go. But I did go to the parts place and
> > I bought a left-handed widget."
> >
> > "And?"
> >
> > "No go."
> >
> > "Did you install the widget?"
> >
> > "Yes."
> >
> > "And did it make any difference?"
> >
> > "No, except that now, when I look under the car in the engine area, I
> > see a left-handed widget lying on the ground."
> >
> > "How did you install it?"
> >
> > "I put it under the hood, where it goes."
> >
> > "I'm afraid you're going to have to bring your car in if you want us
> > to fix it. I can send a tow-truck around."
> >
> > "No thanks, nazi pig!" *CCCLLLLIIIIICCCCCCKKKKKKK*
> >
> > --
> >
> > Dave Fluri
> > North Bay, Ontario Canada
>
>
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: [EMAIL PROTECTED] (Jonadab the Unsightly One)
Subject: Re: Modem trouble
Date: Tue, 24 Apr 2001 15:05:57 GMT
[EMAIL PROTECTED] (M. Buchenrieder) wrote:
> That's news to me, then. I was always under the impression that the
> drivers needed to be run in protected mode - which DOS obviously
> isn't capable of providing.
Protected mode is a CPU feature, provided by Intel 80386
CPUs and higher and anything fully compatible with them
(e.g., Athlon, Duron). It's as available under DOS as
under any other OS. Tons of DOS 3D games from the
pre-Windows-95 era (e.g., Descent) used protected mode.
PKZip uses protected mode if it detects a 386 or higher
CPU. It also knows how to use EMS, XMS, UMBs, or DPMI,
whichever is available. (Good software is flexible.)
However, a lot of winmodems don't bother to supply
DOS drivers on the grounds that "nobody uses DOS
anymore" (by which they mean that nobody buys a new
PC with DOS as the single pre-installed OS anymore).
It is certainly possible for a software modem to
come with DOS drivers. But with DOS you can easily
know for sure whether you're using a driver (just
note any changes to your config.sys and autoexec.bat
files); with Windows that's orders of magnitude more
complicated. Also, Windows often uses drivers when
it doesn't need drivers, for things like monitors
and parallel ports and real modems. DOS usually
only uses drivers when they serve a purpose (and
would be necessarily needed in another OS as well).
So getting your modem to work in DOS is a better
indication (than getting it to work in Windows) of
whether it will work in other OSes (e.g., Linux).
- jonadab
------------------------------
From: CBFalconer <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.periphs.scsi,comp.os.cpm,comp.sys.tandy
Subject: Re: Where can I buy bridgeboards?
Date: Tue, 24 Apr 2001 16:04:15 GMT
Sylvan Butler wrote:
>
> On Sun, 22 Apr 2001 05:24:59 -0700, Rick <[EMAIL PROTECTED]> wrote:
> >I beg to differ on that one. If you are using an ST225 - a cheap drive with
>
> Identical physically and electronically to the early ST238's...
>
> >relatively low quality media surface - and you are cramming more data onto it
> >by eliminating the fixed flux reversal pattern of MFM recording there will be
>
> Doesn't actually eliminate the flux reversals. MFM (modified
> frequency modulation) required clock bits, RLL (run length limited)
> does not, but uses the data as a clock unless the run length was too
> long, at which point it inserts a clock pattern.
>
> >as a second source for inducing read errors. The media surface and inaccurate
> >head positioning are far more likely to be a source for error under RLL than
> >any potential speed variation in the drive.
>
> But both media surface and inaccurate head positioning would affect
> MFM just as much. MFM has no greater tolerance for media errors or
> head positioning that did RLL. The only issue was electronics...
> Could the electronics accurately clock the greater amount of data,
> or would noise and latency issues disrupt the signal.
Each flux reversal is (ideally) an impulse. The electronics adds
rise and fall times, all exponentials, through various filters,
resulting in base line shifts, under and overshoots, etc. The
result is the discriminator fires at varying points, and slightly
alters the timing. All of this can be compensated, but was not so
necessary for MFM. The compensation can be as simple as a
discriminator threshold dependant on the recent flux transition
history, implemented through the (already present) data
accumulation shift register.
Things are complicated by actual magnetic effects on the disk
surface and heads, and varying transition separation between inner
and outer tracks. Todays drives use constant flux changes per
unit distance (more bits on outer tracks than on inner) so this
effect is more or less constant.
So, as you said, with the right electronics, any MFM drive is a
suitable RLL drive.
--
Chuck F ([EMAIL PROTECTED]) ([EMAIL PROTECTED])
http://www.qwikpages.com/backstreets/cbfalconer
(Remove "NOSPAM." from reply address. my-deja works unmodified)
mailto:[EMAIL PROTECTED] (for spambots to harvest)
------------------------------
From: Young4ert <[EMAIL PROTECTED]>
Subject: EZonics II USB Webcam
Date: Tue, 24 Apr 2001 16:06:06 GMT
I recently bought an EZonics II USB Webcam and learnt that the "webcam"
driver from http://webcam.sourceforge.net does not support this new version
of the EZonics II USB camera. I opened the camera and found the following
information:
Chipset: Conexant CN0352P 11226-11 E47676,1
I am wondering if there is such a driver source code that I can download
and give it a try. Alternatively, if there is no such a driver source for
this particularly chipset, can anyone please at least tell me where to
start to get this camera working under Linux?
TIA.
------------------------------
From: "Ferry van Doorn" <[EMAIL PROTECTED]>
Subject: Re: ABIT KT7A-RAID
Date: Tue, 24 Apr 2001 18:27:51 +0200
"Pavel Tom�ek" <[EMAIL PROTECTED]> wrote in message
news:9c3dqv$1s7u$[EMAIL PROTECTED]...
> Hi all,
>
> do anyone find drivers for IDE ONBOARD RAID controler for ABIT KT7A-RAID
> motherboard ? Manufacturer do not suply any drivers for NUX based systems
> ....
>
> help ...
>
>
There are drivers for this highpoint controller but there is no support for
the raid-fuction, only single disk support. Drivers can be found on:
http://www.highpoint-tech.com/370drivers.htm
or
http://www.linux-ide.org/
http://www.kernel.org/pub/linux/kernel/people/hedrick/
These drivers are probably already included in kernel 2.4(I'm not sure).
Grtz,
Ferry
------------------------------
From: "Jan" <[EMAIL PROTECTED]>
Subject: NEC 3.5" 1.2MB Floppy support
Date: Tue, 24 Apr 2001 19:52:45 +0300
Reply-To: "Jan" <[EMAIL PROTECTED]>
I have a "NEC FD1231T 3.5" floppy disk drive (mode 3)
using 1.2MB diskettes. Does the Linux (RedHat 7, Kernel v2.2.17)
support this kind of disk drives?
------------------------------
From: "Andreas Adler" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,de.comp.os.unix.linux.hardware
Subject: Re: LINUX on Compaq Deskpro XL
Date: Tue, 24 Apr 2001 19:16:03 +0200
Hello,
sorry for my bad english. I hope you understand ist.
I never saw a Compaq Deskpro XL with a QVision graphic card.
My ones in our company have a Elsa S3 Adapter. Have you tested with
VESA-Modes?
Best Regards
Andreas
"Ioan Alexandre Romoscanu" <[EMAIL PROTECTED]> schrieb im
Newsbeitrag news:[EMAIL PROTECTED]...
>
> Hello
>
> Did anyone install Linux (SUSE 6.x for instance) on a Compaq Deskpro XL?
> This PC has a QVision graphic card, and it is officially not supported.
> I wonder if it still works.
>
> Thanks for any emails
>
> A.I.R.
> --
> ___________________________________________
> alexandre ioan romoscanu - institut f�r mechanik
> CLA G31, eth zentrum, 8092 z�rich, schweiz
> tel. +41 1 632 77 54, +41 76 323 63 05
> fax.+41 1 632 11 45, [EMAIL PROTECTED]
> ___________________________________________
>
>
------------------------------
From: "H Brinkman" <[EMAIL PROTECTED]>
Subject: pctv miro
Date: Tue, 24 Apr 2001 17:51:00 GMT
Can anyone tell me how to configure a miro pctv rave card in redhat?
------------------------------
From: "Jaap L.A." <[EMAIL PROTECTED]>
Subject: Pentium I 133 +32 MB enough ?
Date: Tue, 24 Apr 2001 19:53:44 +0200
Hi,
I'm planning to install Linux Suse 6.0 on a P133 with 32 mb. I'd like to use
the KDE desktop. Will it work or will I get just as frustrated with it as I
am with win9x etc.
Has anybody experience with this ?
Jaap
------------------------------
From: Alberto BARSELLA <[EMAIL PROTECTED]>
Subject: Re: 2.4.3, ATA100 & Hedrick's patches
Date: 23 Apr 2001 14:39:49 +0200
[EMAIL PROTECTED] (Kenneth R�rvik) writes:
> They aren't. 2.4.x supports ATA100 just fine.
Not for me, unfortunately :(
I have a MSI K7 Pro2A (name?), with Via chipset.
I can't get past udma2.... if I try to set it manually to higher modes
I get a "Speed warning, modes 3/4/5 not supported.". I've tried the
ide0=ata66 flag, but it has no effect. As a result, I only get 15Mb/sec.
On 2.2.x it works just fine, running at 25 Mb/sec.
Maybe I should those patches out....even if at quick look they don't
patch anything in the VIA file....
Bye,
Alberto
--
Alberto BARSELLA - infringing US Pat. 5,443,036 every evening!
- check: http://www.delphion.com/details?pn=US05443036__
** Beliefs are dangerous. Beliefs allow the mind to stop functioning.
A non-functioning mind is clinically dead. Believe in nothing... **
------------------------------
From: Sebastian Bossung <[EMAIL PROTECTED]>
Subject: can print only one page at a time
Date: Tue, 24 Apr 2001 22:19:27 +0200
Hi,
when I try to print multi-page documents (i.e. lpr myfile.ps, where
myfile.ps has at least two pages), my printer will only print the first
page and apsfilter will give an errormessage to /var/log/messages:
"lpd: apsfilter: unable to print job"
Which is not very usefull to me. The interesting thing is, that the printer
will print multi-page ASCII file when printed to "raw".
Can anybody help me here? Thank a lot!
Sebastian
------------------------------
From: [EMAIL PROTECTED] (Philipp Lehman)
Subject: Re: Pentium I 133 +32 MB enough ?
Date: Tue, 24 Apr 2001 20:39:39 +0200
Jaap L.A. <[EMAIL PROTECTED]> wrote:
>I'm planning to install Linux Suse 6.0 on a P133 with 32 mb. I'd like to use
>the KDE desktop. Will it work or will I get just as frustrated with it as I
>am with win9x etc.
If you want a full blown install of the current KDE release:
yes. A basic Linux install and console apps will run fine, but
for the X window system 32 MB RAM is extremely tight.
Consider getting more RAM (having 64 MB will make a real
difference) and instead of using the latest and greatest KDE or
GNOME release, pick only essential components and pick them
with performance in mind. There are window managers with memory
footprints ranging from less than 50K to several MB, to give
just on example.
What kind of apps do you need besides the basic desktop
environment?
--
Philipp Lehman <[EMAIL PROTECTED]>
------------------------------
From: Jeff <[EMAIL PROTECTED]>
Subject: SMP, RH7.1 and Intel -- Can't they all just get along?
Date: Tue, 24 Apr 2001 15:20:57 -0400
If this is not the correct newsgroup, please forgive:
I'm trying to setup a RH 7.1 box with two pentium III 1 Gig processors and
1.5 Gig Ram. I've installed two partitions, one that works and one that
doesn't. The one that works is running RH 7.1 however using the BOOT
kernel, while the partition that doesn't work is attempting to a compiled
kernel with:
i. SMP flag set;
ii. RTC (Real Time Clock) flag set;
iii. MTRR (Memory Type Range Register) flag set; and
iv. No Advance Power Management flag set
As per the HOWTO.
And yet I get the following boot sequences messages prior to the "crash"
CPU1: Intel Pentium III (Coppermine) stepping 06
CPU1 has booted.
Total of 2 processors activated (4010.80 BogoMIPS).
Before bogocount - setting activated=1.
Boot done.
ENABLING IO_APIC IRQs
...changing IO-APIC physical APIC ID to 2 ... ok.
Synchronizing Arb IDs
..TIMER: vector=49 pin1=2 pin2=0
... And then nothing.
Any insight into how I can get this partition working would be greatfully
accepted.
It might be best to reply to my email as well as posting here, so that I
see your response.
Cheers
--
Jeff Gardiner System Administrator
[EMAIL PROTECTED]
The John. P. Robarts Research Institute
Second Law of Blissful Ignorance --
-- Inside every small problem is a large problem struggling to get out.
------------------------------
From: Peter Christy <[EMAIL PROTECTED]>
Subject: Re: Via82c driver for sound
Date: Tue, 24 Apr 2001 20:38:26 +0100
Reply-To: [EMAIL PROTECTED]
David Stites wrote:
> I installed the drivers finally, the documentation is not very good. cat
> /proc/asound/cards shows the card installed but cat /etc/modules.conf
>>/dev/snd/pcmD0C0c says device not configured. I don't see any
>>documentation on what to do when the install program fails. I guess I'll
>>have to buy a good book on sound and work it out for myself. I could buy a
>>$25 sound card but that would be giving up.
I know what you mean. It took me several goes to work it out! However, this
is what worked for me:
The bits that work or don't work seem to be EXTREMELY system dependant, so
here is a brief summary of my system:
Motherboard: Gigabyte GA-7ZM (Via KT-133 chipset) with a 700MHz Duron
processor.
BIOS setup: AC97 support ENABLED
MC97 (modem) DISABLED (might not be important - don't know!)
Legacy audio ENABLED (without this no MPU-401 or joystick.)
Soundblaster DISABLED (this is only used by real DOS)
OS: Linux-Mandrake 7.2
Kernel: 2.4.0 test 12
& 2.4.0 prerelease.
DevFS ENABLED.
Desktop: KDE 2.1 beta
The kernel should be compiled with sound support ON (to produce the
soundcore module), but no driver modules selected
Get the latest ALSA sound drivers. At the time of writing (Jan 2001) these
are 0.5.10. 0.5.9d may also work, but 10 has bug fixes for the AC97. I'm
now using 0.9.0beta3. It seems perfectly stable.
Unpack the TAR files into a spare directory (I use /usr/local/src/).
You should end up with three new directories, alsa-driver-0.5.10,
alsa-lib-0.5.10 and alsa-utils-0.5.10.
Enter the alsa driver directory, and do ./configure , make , make install.
NOTE: My compiler kept crashing during the make trying to make something
that had no relevance to the VIA chip. If you do
./configure --with-cards=via686a
it will ONLY build modules relevant to the via chipset. This saves time and
space! It also reduces the chance of a spurious compiler crash!
Next, go to the alsa lib directory and ./configure , make , make install .
You shouldn't need any options here.
Now do the same again in the alsa utils dorectory ( ./configure , make and
make install ). The utils aren't strictly necessary, but may be useful for
bug-hunting.
Now all the modules should be in place. If you reboot your system, you will
find some extra options under the "Startup Services" (traffic lights
symbol) in Drakconf. These are Alsasound and sound (sound may have been
there originally) MAKE SURE BOTH THESE ARE SWITCHED OFF! It seems that the
LM 7.2 startup calls the modules in the wrong sequence - as a result they
don't work. You MUST install them the hard way!
Actually, it isn't that hard! Go to /etc/modules (NOT /etc/modules.conf!)
and add the following lines:
snd-card-via686a
snd-pcm-oss
snd-mixer-oss
During boot-up, LM reads the contents of /etc/modules and installs the
requested modules. NOTE: This appears to be broken in 7.1 (at least, I
never got it to work!) 7.1 users will probably have to add these lines to
etc/rc.d/rc.local
/sbin/modprobe snd-card-via686a
/sbin/modprobe snd-pcm-oss
/sbin/modprobe snd-mixer-oss
NOTE AGAIN: I haven't tried this - its just a guess!
Now edit /etc/modules.conf, adding the following lines:
# ALSA native device support
alias char-major-116 snd
options snd snd_major=116 snd_cards_limit=1
alias snd-card-0 snd-card-via686a
# OSS-free setup
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
The alsa literature implies that you have to add an awful lot of other
stuff, but the latest releases seem to take care of all that for you
automatically.
Finally, if you're running DevFS, you need to add a couple of lines to
devfs.conf:
REGISTER sound/.* PERMISSIONS root.audio 660
REGISTER snd/.* PERMISSIONS root.audio 660
(If you're not running devfs, you probably need to do a ./snddevices from
inside the alsa-driver directory. Again, I haven't tried this, as I run
DevFS).
The literature tells you to add a line:
LOOKUP snd EXECUTE /sbin/modprobe snd
before the above two lines. When I tried this, my system crashed horribly
with dire warnings about corruption of the root filing system! In fact
there was nothing at all wrong with the filing system - devfs.conf already
had a line:
LOOKUP .* MODLOAD
which appears to already do everything required. Adding the extra line
confused it! So just add the two REGISTER lines after the LOOKUP line that
already exists.
Kmix, KDE's built in mixer is alsa aware, so all that is necessary to
unmute the channels is to slide the PCM and volume sliders up (remember to
save the new settings as default!). Because of all the pratting around I'd
done, kmix seemed to have two mixers attached to it, one of which didn't
work! The only way I found to tidy things up was to go into the
$HOME/.kde/share/config/ and delete all the kmix configuration files
(kmixctrlrc and kmixrc). These were then rewritten correctly after a reboot
(probably just logging out and in again would have been sufficient).
I now had sound working, but it was stammering and stuttering terribly. It
sounded like an interrupt problem, except that I have plenty of spare
interrupts and no error messages! Its taken me a week to find this last
problem and it turned out to be the aRts sound server! Disabling this has
cleared the last problem and I can now play both wave and midi files with
superb quality.
To disable aRts:
Open up KDE's Control Centre. Select Sound, then Sound Server. In the top
left hand corner is a check box to "Start aRts soundserver on kde startup".
Uncheck this box. It won't have any effect till you log out and back in
again. But then you should have working sound!
All this was done as root, by the way. To enable sound for users, they MUST
be members of the "audio" group.
There is probably something I've missed out along the way there, but I
think I've covered all the major points.
It does sound very good when you finally get it working!
--
Pete
[EMAIL PROTECTED]
------------------------------
From: "Steve Wolfe" <[EMAIL PROTECTED]>
Subject: Re: SMP, RH7.1 and Intel -- Can't they all just get along?
Date: Tue, 24 Apr 2001 13:52:49 -0600
What kind of chipset is on the motherboard?
steve
> If this is not the correct newsgroup, please forgive:
>
> I'm trying to setup a RH 7.1 box with two pentium III 1 Gig processors and
> 1.5 Gig Ram. I've installed two partitions, one that works and one that
> doesn't. The one that works is running RH 7.1 however using the BOOT
> kernel, while the partition that doesn't work is attempting to a compiled
> kernel with:
> i. SMP flag set;
> ii. RTC (Real Time Clock) flag set;
> iii. MTRR (Memory Type Range Register) flag set; and
> iv. No Advance Power Management flag set
>
> As per the HOWTO.
>
> And yet I get the following boot sequences messages prior to the "crash"
>
> CPU1: Intel Pentium III (Coppermine) stepping 06
> CPU1 has booted.
> Total of 2 processors activated (4010.80 BogoMIPS).
> Before bogocount - setting activated=1.
> Boot done.
> ENABLING IO_APIC IRQs
> ...changing IO-APIC physical APIC ID to 2 ... ok.
> Synchronizing Arb IDs
> ..TIMER: vector=49 pin1=2 pin2=0
>
> ... And then nothing.
>
> Any insight into how I can get this partition working would be greatfully
> accepted.
>
> It might be best to reply to my email as well as posting here, so that I
> see your response.
>
> Cheers
>
>
> --
> Jeff Gardiner System Administrator
> [EMAIL PROTECTED]
> The John. P. Robarts Research Institute
>
> Second Law of Blissful Ignorance --
> -- Inside every small problem is a large problem struggling to get out.
------------------------------
From: "Karim R. Sobhi" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.help,comp.os.linux.misc,comp.os.linux.questions,comp.os.linux.setup
Subject: kppp problems...
Date: Tue, 24 Apr 2001 22:05:16 +0200
i'm trying to connect my Linux Mandrake 7.1 to the internet through my
modem. the modem is compatible and when i query it it works fine. when i run
kppp, on the other hand, i get this on the log file:
Apr 24 21:52:38 Edgar pppd[927]: pppd 2.3.11 started by root, uid 0
Apr 24 21:52:38 Edgar pppd[927]: Using interface ppp0
Apr 24 21:52:38 Edgar pppd[927]: Connect: ppp0 <--> /dev/ttyS1
Apr 24 21:52:46 Edgar pppd[927]: Peer is not authorized to use remote
address 217.52.7.110
Apr 24 21:52:46 Edgar pppd[927]: Connection terminated.
Apr 24 21:52:46 Edgar pppd[927]: Connect time 0.2 minutes.
Apr 24 21:52:46 Edgar pppd[927]: Sent 380 bytes, received 407 bytes.
Apr 24 21:52:46 Edgar pppd[927]: Exit.
i'm sure the username and password are correct so i don't know where the
problem is. any ideas?
karim
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.hardware.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
