Linux-Hardware Digest #38, Volume #14 Fri, 15 Dec 00 21:13:07 EST
Contents:
Re: Modem busy ("Doug Kramer")
Re: Modem problems ("Doug Kramer")
Eisa Dac960 ("Jim Goodall")
Re: Trident problems with RH7 and signal 11 with RH ("Doug Kramer")
Linux on COMPAQ deskpro EX PC (Bertrand)
Re: ATI Rage Fury ("Doug Kramer")
Re: How do I test serial ports, find modem? ([EMAIL PROTECTED])
crossover cable (root)
Re: DVD playing in Linux ([EMAIL PROTECTED])
Re: Modem busy (Paul Pygeon)
Re: Modem problems (James Richard Tyrer)
Re: crossover cable (jens)
Re: Eisa Dac960 (Cokey de Percin)
----------------------------------------------------------------------------
Reply-To: "Doug Kramer" <[EMAIL PROTECTED]>
From: "Doug Kramer" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake,alt.os.linux.dial-up
Subject: Re: Modem busy
Date: Fri, 15 Dec 2000 17:41:24 -0500
Try setting your UARTS to unknown and the ttyS2 UART to 16550A.
Example (command line):
setserial /dev/ttyS0 UART unknown
setserial /dev/ttyS1 UART unknown
setserial /dev/ttyS2 UART 16550A
setserial /dev/ttyS3 UART unknown
Another thing you have to tell Drake what modem you are using (maybe it's
DrakeConfigure). Personally I would try this first before anything else I
mentioned here. I don't know the mechanics behind Drake, it might do it
all!?
The final thing it to check your "rc.local" to see if modem is noticed at
start-up. Should have the following command in it (if not add it to the
bottom) "/sbin/setserial /dev/ttyS2 UART 16550A"
See if this works!
"Ilya Sterin" <[EMAIL PROTECTED]> wrote in message
news:91dl29$7p5$[EMAIL PROTECTED]...
> Configured
>
> setserial /dev/ttyS2 port 0xa400 irq 9 autoconfig
>
> running setserial -g /dev/ttyS2 outputs the uart so the setserial
> worked.
>
> Now when I try to use kppp to query modem or dial it says modem busy.
> I have a USB mouse that I use and ttyS0 for my keyboard. The irq 9 is
> used by some VIA drivers, but even when I configure the ttyS2 to irq 15
> or any other it says busy. I don't link to /dev/modem and in kppp set
> it to ttyS2. Nothing seems to work, keeps saying busy. I harddrake it
> recognizes the modem as USRobotics Pro (it's not a winmodem, but PCI).
> I saw lots of post with this issue, but no solutions posted.
> My soundcard uses irq 5, so that's not a conflict. Can someone please
> help. Thanks.
>
>
> Ilya Sterin
>
>
> Sent via Deja.com
> http://www.deja.com/
------------------------------
Reply-To: "Doug Kramer" <[EMAIL PROTECTED]>
From: "Doug Kramer" <[EMAIL PROTECTED]>
Subject: Re: Modem problems
Date: Fri, 15 Dec 2000 17:55:41 -0500
I would imagine you would have to go back and change your "isapnp.conf"
settings to reflect your new IRQ & port settings and line out the old
ones.Then I would run /dev/ttyS3 again to see if they are showing the new
settings. Then UART unknown all your other ttyS0-4 (with the exception of 3
which should be set to 16550A). Then change your "rc.local" or your
"boot.local" so your new hardware setting load during your boot-up with the
command "/sbin/setserail /dev/ttyS3 UART 16550A".
Believe me I know your frustration with both pieces of hardware!
"E-Comm" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I have an ISA PnP US Robotics Sportster 33600 on P133 running Corel
> Linux 1.2. I had it running under the following settings:
> port = 0x02E8
> irq = 5
> uart = 16550A
> sttS3
> This settings were added to '/etc/isapnp.conf', which reported no
> conflicts. These settings were also added to '/etc/rc.boot/0setserial'
> with no problems reported. I had been using the modem for more than
> three months.
>
> During all this time I have been using Corel Linux, I have been
> struggling to get the sound card to work. I got it to work with
> Slackware 7. Well, after much tenacity and sleepless nights, with the
> help of 'sndconfig' I finally got it to work last night. To day I found
> out that the modem was not longer working.
> Apparently the settings were no longer accepted by CLOS, so I changed
> them to:
> port = 0x03e8
> irq = 5
> and the rest is the same....
> Although there are no conflicts, KDE Dial-Up still reports the modem is
> busy.
>
> Does anyone have an idea about what is going on?
>
> I am interested in anything you can pitch in, no matter how irrelevant
> it might sound to you, you input could trigger a realization.
>
> Thanks in advance.
>
>
------------------------------
From: "Jim Goodall" <[EMAIL PROTECTED]>
Subject: Eisa Dac960
Date: Fri, 15 Dec 2000 23:00:13 -0000
Hi Guys,
I've got a 486 that I've downloaded the "486" distro of Mandrake for. This
particular 486 has an old eisa mylex dac960 raid controller.
I've hooked an external CD drive up to it, loaded the dos drivers and ran
the install program on the CD which created an install directory on the 10
meg "C:" drive I created.
I then ran the install from the C: drive, but when I got to the part where
it asks about the SCSI cards I select dac960 the install says "Could not be
found anywhere in you system" So I tried again without the SCSI dos drivers
loaded (Clean Boot), but it said the same!?
Consequently I cannot see the CD drive, so the install cannot continue :-(
Any ideas?
Thanx
--
Jim Goodall
[EMAIL PROTECTED]
Remember - If it ain't Novell it can't be much good!
------------------------------
Reply-To: "Doug Kramer" <[EMAIL PROTECTED]>
From: "Doug Kramer" <[EMAIL PROTECTED]>
Subject: Re: Trident problems with RH7 and signal 11 with RH
Date: Fri, 15 Dec 2000 18:04:53 -0500
My laptop has a Trident Cyber 9397DVD PCI/AGP.
Your problem sounds much like mine during installation. I did a 'text' type
install of RH7. Worked great!
<[EMAIL PROTECTED]> wrote in message news:91doi7$b36$[EMAIL PROTECTED]...
> I've a:
>
> Trident 975
> Abit KA7-100
> K7@750
> 96Mb
> Quantum Fireball EX6.4Gb
> Seagate 2.2Gb
> HP 9100i CDRW
> PCI NE2000 compatible (RT8029)
> AWE64
>
> and I get two kinds of problem with RH7:
>
> a) I can't partition the drive: With either DD or FDISK I get a signal
> 11 when I try to partition and that's all!!
> b) My Trident 975 does such a strange thing like don't drawing any
> background (I get a black background in the installation procedure
> instead the gray). It also doesn't redraw the screen, so I get a black
> screen with the hat drawed in the background mixed with some text (in
> black!!!) with a line highlited in white, and when I click over the
> "next" arrow, it draw over the last screen... It's a mess!!!
>
> I have a) over RH6.2 and RH7. With Gentus Linux (came with the mother)
> the machine does something similar (no signal 11, but it reinitialize).
> The trident VGA works well with RH6.2, so seems to be a RH7 problem...
> Any ideas?
>
>
> Sent via Deja.com
> http://www.deja.com/
------------------------------
From: Bertrand <[EMAIL PROTECTED]>
Subject: Linux on COMPAQ deskpro EX PC
Date: Fri, 15 Dec 2000 23:08:44 GMT
I intend to buy a compaq deskpro XE PC (PIII 733 Mhz, with 10Gb hdd, 128
Mb sdram, ethernet card 10/100, chipset i815, video controller intel 3D
AGP on the mother board, and onboard SB compatible sound chip).
Is it possible to run linux on this pc ?, my greatest fear is about the
onboard video and/or soundcard.
Thanks for your answers
Bertrand
------------------------------
Reply-To: "Doug Kramer" <[EMAIL PROTECTED]>
From: "Doug Kramer" <[EMAIL PROTECTED]>
Subject: Re: ATI Rage Fury
Date: Fri, 15 Dec 2000 18:13:52 -0500
I am having problems with mine so I don't have room to talk!
But wouldn't you want to install ATI Wonder SVGA server for your Rage 128
chip? I thought that's what XFree86 suggested for this ATI hardware instead
of the old Mach64 server under version 4.01.
You want the R128 driver.
"Robert" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> i've tried lots of things on xf86config, perhaps a lower-level
> configuration
> can solve the problem. and what about the xserver? i'm using the mach64
> server
> and i've set the card to number 104 in xf86config, does it matter?
>
> James Richard Tyrer wrote:
> >
> > Robert wrote:
> >
> > > Hi all!
> > > anyone been succesful on configuring an ATI Rage Fury under xfree86
> > > 4.0.1?
> > > i actually can only get 640x480, which is *pathetic*
> >
> > At the risk of being redundant:
> >
> > Section "Screen"
> > Identifier "Screen 1"
> > Device "ATI Rage IIC"
> > Monitor "NEC MultiSync3V"
> > DefaultDepth 24
> >
> > Subsection "Display"
> > Depth 24
> > Modes "1024x768"
> > ViewPort 0 0
> > EndSubsection
> > EndSection
> >
> > Ad some other Modes if you want, need, and you monitor can support them.
> >
> > But this isn't enough, you have to have the proper horizontal refresh
> > and vertical sync rates. And, don't enter something that your monitor
> > won't handle or you may give new meaning to the term "smoke test".
> >
> > Section "Monitor"
> >
> > Identifier "NEC MultiSync3V"
> >
> > HorizSync 31.5 - 48.5
> >
> > VertRefresh 50-70
> >
> > EndSection
> >
> > The above range will support 1024 x 768.
> >
> > These are copies from my XFree86Config file.
> >
> > And, I presume that your driver (device) is also correct:
> >
> > Section "Device"
> > Identifier "ATI Rage IIC"
> > Driver "ati"
> > #VideoRam 4096
> > EndSection
> >
> > The documentation says not to tell it how much VRAM you have unless it
> > can't figure it out for itself -- put in the figure, but leave it
> > commented out.
> >
> > JRT
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: How do I test serial ports, find modem?
Date: Fri, 15 Dec 2000 23:37:01 GMT
Michael Kantor <[EMAIL PROTECTED]> wrote:
>
> I am trying to install an ISA modem (USR real modem, real jumpers, has
> worked under linux before). The only way I could avoid BIOS
complaints
> of address conflicts was to set the jumpers to allow PnP
configuration.
> Now I don't know where the modem is. I have tried pointing minicom at
> ttyS0 through ttyS4. It always claims to be dialing, but the phone
line
> remains free.
>
> How can I probe the serial ports to see where the modem is,
Search the /var/log/dmesg file for logs of the tty init, e.g.
# grep tty /var/log/dmesg
ttyS01 at 0x02f8 (irq = 3) is a 16550A
#
That should tell you where the kernel (hopefully) found the modem
when it felt around at boot time.
> and send the modem commands to see if it's working?
Pipe the modem commands to the port you found using the command above,
then cat the same port, e.g. if modem is on ttyS1:
# echo AT > /dev/ttyS1 ; cat /dev/ttyS1
OK
#
If you get the "OK" back from the modem then you've found the right tty.
HTH
Bluster
Sent via Deja.com
http://www.deja.com/
------------------------------
From: root <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: crossover cable
Date: Fri, 15 Dec 2000 12:31:40 -0500
I'm trying to connect the two computers I have at home with a crossover
cable. I have cable modem (att@home). One computer has two NICs (an SMP
EtherPower and a linksys card) and the other has a 3com card. If I plug
the cable modem in any of these 3 cards separately, I can connect to the
outer world without a hitch (after configuring the interface and the
routing table, of course). The only thing that I can't do is have the
computers talk to each other. I noticed that when I plug the cable modem
into any of the card, the leds light up, but when I plug the crossover
cable, neither end lights up, so I suspect it is a hardware problem. Is
this normal? Do I change the cable? Do I get a hub?
Thanks!
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: DVD playing in Linux
Date: Fri, 15 Dec 2000 23:53:59 GMT
In article <[EMAIL PROTECTED]>,
Randall Skelton <[EMAIL PROTECTED]> wrote:
> I have read what I can on www.opendvd.org, www.linuxtv.org and
> www.linuxvideo.org but I still have questions about the support of DVD
> players under linux.
>
> Firstly, is it possible?
it is possible. check out these URLs:
http://xine.sourceforge.net
http://gape.ist.utl.pt/ment00/linuxdvd.html
regards,
Fred
Sent via Deja.com
http://www.deja.com/
------------------------------
From: Paul Pygeon <[EMAIL PROTECTED]>
Subject: Re: Modem busy
Crossposted-To: alt.os.linux.mandrake,alt.os.linux.dial-up
Date: Fri, 15 Dec 2000 19:58:14 -0500
Hi,
>Nothing seems to work, keeps saying busy. I harddrake it
> recognizes the modem as USRobotics Pro (it's not a winmodem, but PCI).
> I saw lots of post with this issue, but no solutions posted.
> My soundcard uses irq 5, so that's not a conflict. Can someone please
> help. Thanks.
>
I've the same problem except that I have a USB scanner. When Mandrake
recognize my scanner, my USR PRO modem become busy at all time. If I remove
usb support, my modem works fine.
I've tried many hacks to make modem and scanner working without success.
Hope you find solution.
Know this don't help you but maybe someone have find a solution.
------------------------------
From: James Richard Tyrer <[EMAIL PROTECTED]>
Subject: Re: Modem problems
Date: Sat, 16 Dec 2000 01:10:01 GMT
This is a multi-part message in MIME format.
==============D47284637D98ABBCC09214A3
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
E-Comm wrote:
> I have an ISA PnP US Robotics Sportster 33600 on P133 running Corel
> Linux 1.2. I had it running under the following settings:
> port = 0x02E8
> irq = 5
> uart = 16550A
> sttS3
> This settings were added to '/etc/isapnp.conf', which reported no
> conflicts. These settings were also added to '/etc/rc.boot/0setserial'
> with no problems reported. I had been using the modem for more than
> three months.
>
> During all this time I have been using Corel Linux, I have been
> struggling to get the sound card to work. I got it to work with
> Slackware 7. Well, after much tenacity and sleepless nights, with the
> help of 'sndconfig' I finally got it to work last night. To day I found
> out that the modem was not longer working.
> Apparently the settings were no longer accepted by CLOS, so I changed
> them to:
> port = 0x03e8
> irq = 5
> and the rest is the same....
> Although there are no conflicts, KDE Dial-Up still reports the modem is
> busy.
The "modem is busy" error can also be caused by the failure of "Kppp" to
find the modem.
There seems to be a basic conceptual problem with the use of "setserial"
or its GUI equivalent.
You say that you changed the port address to "0x03e8". But, what did you
actually do?
The port address is hardware. Did you change it with jumpers or how? Or,
did the BIOS change it?
The command "setserial" does absolutely nothing to the hardware. What it
sets is the software driver: 'serial'.
The hardware port address is a given fact. You configure the software
driver to find it.
I don't exactly know how ISA PnP works -- my system is all PCI. But, I am
guessing that you can't change the hardware -- only the BIOS can.
You probably have an interrupt conflict between the modem and the sound
card. What to do about this depends on the type of sound card you have.
Most BIOSs allow you to reserve a particular interrupt for "Legacy ISA"
or reserve an IRQ for a specific PCI slot. Depending on what type of
sound card you have (PCI, ISA PnP, or ISA with jumpers) one of these
options might work.
==============D47284637D98ABBCC09214A3
Content-Type: text/x-vcard; charset=us-ascii;
name="tyrerj.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for James Richard Tyrer
Content-Disposition: attachment;
filename="tyrerj.vcf"
begin:vcard
n:Tyrer;James Richard
tel;fax:call first
tel;home:(520) 648-3720
x-mozilla-html:FALSE
org:JRT Engineering
adr:;;1468 North Rio Sonora;Green Valley;Arizona;85614-4007;USA
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;-4576
fn:James Richard Tyrer
end:vcard
==============D47284637D98ABBCC09214A3==
------------------------------
From: jens <[EMAIL PROTECTED]>
Subject: Re: crossover cable
Date: Sat, 16 Dec 2000 01:16:34 GMT
On Fri, 15 Dec 2000 12:31:40 -0500, root <[EMAIL PROTECTED]>
wrote:
>I'm trying to connect the two computers I have at home with a crossover
>cable. I have cable modem (att@home). One computer has two NICs (an SMP
>EtherPower and a linksys card) and the other has a 3com card. If I plug
>the cable modem in any of these 3 cards separately, I can connect to the
>outer world without a hitch (after configuring the interface and the
>routing table, of course). The only thing that I can't do is have the
>computers talk to each other. I noticed that when I plug the cable modem
>into any of the card, the leds light up, but when I plug the crossover
>cable, neither end lights up, so I suspect it is a hardware problem. Is
>this normal? Do I change the cable? Do I get a hub?
>
>Thanks!
Are you actually using a 'crossover' cable or are you using a
'straight' cable ? The results you indicate would suggest to me that
your crossover cable isn't crossing over.
In my experience the connect lights will light up when all is well
(you can however configure some cards and monkey with the lights)
Is it a commercial cable or a self-built ? If self built, that is the
likely cause if commercial built was the package sealed when you got
it? Could someone have put in the wrong cable by mistake ? Heck, it
could have been screwed up in the factory.
If the jacks are clear plastic, see if you can identify the insulator
culorings on the individual jacks to verify that they are crossing
over.
Last but not least, some high speed modems have a crossover button
that could interfere in your thought processes when you are trying to
sort all things out (the kind of catch 22 that bites you in the behind
when you are not watching)
Good luck
Jens
------------------------------
From: Cokey de Percin <[EMAIL PROTECTED]>
Subject: Re: Eisa Dac960
Date: Sat, 16 Dec 2000 01:15:34 GMT
Jim Goodall wrote:
>
> Hi Guys,
>
> I've got a 486 that I've downloaded the "486" distro of Mandrake for. This
> particular 486 has an old eisa mylex dac960 raid controller.
>
> I've hooked an external CD drive up to it, loaded the dos drivers and ran
> the install program on the CD which created an install directory on the 10
> meg "C:" drive I created.
>
> I then ran the install from the C: drive, but when I got to the part where
> it asks about the SCSI cards I select dac960 the install says "Could not be
> found anywhere in you system" So I tried again without the SCSI dos drivers
> loaded (Clean Boot), but it said the same!?
>
> Consequently I cannot see the CD drive, so the install cannot continue :-(
>
> Any ideas?
>
> Thanx
>
> --
> Jim Goodall
> [EMAIL PROTECTED]
> Remember - If it ain't Novell it can't be much good!
I believe you're SOL. I believe the current drivers only support the PCI
'DAC960PG' and up varients. I suggest you go to Mylex and follow the
Linux DAC driver links for the most current information.
Best
Cokey
--
==================================================================
Cokey de Percin, DBA Email:
Mynd Corp. (Soon to be CSC) Work - [EMAIL PROTECTED]
Columbia, South Carolina Home - [EMAIL PROTECTED]
------------------------------
** 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
******************************
