Linux-Setup Digest #784, Volume #20 Thu, 8 Mar 01 10:13:09 EST
Contents:
gcc include files (Fabrice Lhomme)
Cisco and Syslog ("Thomas Paine")
Re: [HELP] lucent winmodem (Jerry)
Re: Something to chew on.. (Scott Schaefer)
PPPoE connect timed out ("ELF")
Re: ADSL Problem Can some body help me in this problem (Rod Smith)
Re: Princeton Flat Panel Monitor w/ ATI Xpert 128 (ekk)
----------------------------------------------------------------------------
From: Fabrice Lhomme <[EMAIL PROTECTED]>
Subject: gcc include files
Date: Thu, 08 Mar 2001 14:39:29 +0100
Hi,
After a new Redhat 6.0 installation, gcc can't find the include files
(not in the default /usr/include but in
/usr/i386-glibc20-linux/include).
I assume I'll have the same problem with common libraries that will not
be in /usr/lib.
Where can I give gcc the path to it's headers/libraries ?
Best regards,
Fabrice.
------------------------------
From: "Thomas Paine" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,comp.os.linux.security
Subject: Cisco and Syslog
Date: Thu, 8 Mar 2001 07:55:51 -0600
Reply-To: "Thomas Paine" <[EMAIL PROTECTED]>
I added the following lines to the syslog.conf, but nothing ends up in
the cisco.log
# Syslogging for switches
user.* /var/log/cisco.log
I then pointed a switches logging host to this same box, but nothing ever
shows up in the log file. I'm I doing something wrong?
--
Thanks,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thomas Paine ([EMAIL PROTECTED])
University of Wisconsin - Eau Claire
Computing & Networking Services
Famous Last Words
"Did you hear thunder? Oh well hurry up and putt." (JD)
------------------------------
From: Jerry <[EMAIL PROTECTED]>
Subject: Re: [HELP] lucent winmodem
Date: Thu, 08 Mar 2001 22:05:28 -0800
Nader wrote:
> You may try the latest serial driver from
> http://serial.sourceforge.net/: 5.05. Also, the serial settings may need
> to be modified. Here's what my part of my dmesg looks like with kernel
> 2.2.16 and serial 5.05:
>
> --
> Serial driver version 5.05 (2000-09-14) with MANY_PORTS
> SHARE_IRQ DETECT_IRQ SERIAL_PCI enabled
> ---
> Also, what are your setserial settings (setserial -ag /dev/ttyS*)?
Hi Nader,
Thanx for the help. I've got the serial driver from sourceforge, although
it
doesn't seem to come with comprehensive documentation... anyway, the
long (and boring) list below is from my 'setserial -ag /dev/ttyS*', hope
there'll
be more hints from you.
Have a nice day :-)
########################################################################
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
/dev/ttyS1, Line 1, UART: unknown, Port: 0x02f8, IRQ: 3
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
/dev/ttyS10, Line 10, UART: unknown, Port: 0x02b0, IRQ: 5
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal Fourport
/dev/ttyS11, Line 11, UART: unknown, Port: 0x02b8, IRQ: 5
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal Fourport
/dev/ttyS12, Line 12, UART: unknown, Port: 0x0330, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS13, Line 13, UART: unknown, Port: 0x0338, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS14, Line 13, UART: unknown, Port: 0x0338, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
Hayes ESP enhanced mode configuration:
RX trigger level: -22286, TX trigger level: 2052
Flow off level: 16403, Flow on level: -10176
RX timeout: 255, DMA channel: -65
/dev/ttyS15, Line 15, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS16, Line 16, UART: unknown, Port: 0x0100, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS17, Line 17, UART: unknown, Port: 0x0108, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS18, Line 18, UART: unknown, Port: 0x0110, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS19, Line 19, UART: unknown, Port: 0x0118, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS2, Line 2, UART: unknown, Port: 0x03e8, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
/dev/ttyS20, Line 20, UART: unknown, Port: 0x0120, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS21, Line 21, UART: unknown, Port: 0x0128, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS22, Line 22, UART: unknown, Port: 0x0130, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS23, Line 23, UART: unknown, Port: 0x0138, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS24, Line 24, UART: unknown, Port: 0x0140, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS25, Line 25, UART: unknown, Port: 0x0148, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS26, Line 26, UART: unknown, Port: 0x0150, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS27, Line 27, UART: unknown, Port: 0x0158, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS28, Line 28, UART: unknown, Port: 0x0160, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS29, Line 29, UART: unknown, Port: 0x0168, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS3, Line 3, UART: unknown, Port: 0x02e8, IRQ: 3
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS30, Line 30, UART: unknown, Port: 0x0170, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS31, Line 31, UART: unknown, Port: 0x0178, IRQ: 12
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS32, Line 32, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS33, Line 33, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS34, Line 34, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS35, Line 35, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS36, Line 36, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS37, Line 37, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS38, Line 38, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS39, Line 39, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS4, Line 4, UART: unknown, Port: 0x01a0, IRQ: 2
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal Fourport
/dev/ttyS40, Line 40, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS41, Line 41, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS42, Line 42, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS43, Line 43, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS44, Line 44, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS45, Line 45, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS46, Line 46, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS47, Line 47, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS48, Line 48, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS49, Line 49, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS5, Line 5, UART: unknown, Port: 0x01a8, IRQ: 2
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal Fourport
/dev/ttyS50, Line 50, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS51, Line 51, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS52, Line 52, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS53, Line 53, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS54, Line 54, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS55, Line 55, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS56, Line 56, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS57, Line 57, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS58, Line 58, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
Q: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS6, Line 6, UART: unknown, Port: 0x01b0, IRQ: 2
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal Fourport
/dev/ttyS60, Line 60, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS61, Line 61, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS62, Line 62, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS63, Line 63, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 0, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal
/dev/ttyS7, Line 7, UART: unknown, Port: 0x01b8, IRQ: 2
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal Fourport
/dev/ttyS8, Line 8, UART: unknown, Port: 0x02a0, IRQ: 5
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal Fourport
/dev/ttyS9, Line 9, UART: unknown, Port: 0x02a8, IRQ: 5
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal Fourport
#########################################################################
>
>
> Jerry wrote:
>
> > Good day,
> >
> > I think the Lucent winmodem in my Compaq presario 1926 notebook
> > is just one step away from working.
> >
> > I'm using RH7 with kernel 2.4 and this is my modem:
> > ##############################################################
> > 00:09.0 Communication controller: Lucent Microelectronics WinModem 56k
> > (rev 01)
> > Subsystem: AMBIT Microsystem Corp. Presario 56k V.90 DFi Modem
> > Flags: medium devsel, IRQ 3
> > Memory at f4000000 (32-bit, non-prefetchable) [size=256]
> > I/O ports at 10e0 [size=8]
> > I/O ports at 1400 [size=256]
> > Capabilities: [f8] Power Management version 2
> > ##############################################################
> >
> > It seems that the 00:0a.0 (btw, what is it?) as assumed by Lucent
> > is being used by my esssolo sound card, so my system hangs every time
> > when I tried to load the lucent driver. btw, my BIOS doesn't support IRQ
> >
> > customerization.
> > --
> > Regards,
> > Jerry
------------------------------
Date: Thu, 08 Mar 2001 09:15:54 -0500
From: Scott Schaefer <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.security
Subject: Re: Something to chew on..
"Peter T. Breuer" wrote:
>
> In comp.os.linux.setup Olli Rajala <[EMAIL PROTECTED]> wrote:
> > On Wed, 7 Mar 2001 02:05:39 +0100, "Markus G" <[EMAIL PROTECTED]>
> > Why 420? What's the "magic" behind that number? It's not 2^n, that's
> > why I'm asking this.
>
> What makes you think it's not 2^n? How many hundredths of a second are
> there in 420 days anyway?
>
> 100 * 3600 * 24 * 420 = hmmmmmmm
>
> (about 7500000 * 420, or about 3 200 000 000, which curiously is
> between 2 or 4 times 1024^3, if my envelope calculation is right)
>
> Peter
Storing 'uptime' in a 32-bit value:
max unsigned 32 bit value = 4294967296
1 day = 8640000 "hundredths of seconds"
4294967296 / 86400000 = 497.1026962963 days
------------------------------
From: "ELF" <[EMAIL PROTECTED]>
Subject: PPPoE connect timed out
Date: Thu, 8 Mar 2001 22:02:42 +0800
Dear guys
i am using caldera, rp-pppoe. IMS ultraline (PPPoE with set top box plus
ethernet card) but always "timed out" when i connect everytime . i have
remove "mru" in adsl-connect . i have minimum requirment of kernel and ppp
what else i need to take care? what kinds of config or deamon do i need?
have post this problem before, but seems no idea. wish someone have some
experience in it.
Thanks for million
------------------------------
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: ADSL Problem Can some body help me in this problem
Date: Thu, 08 Mar 2001 14:28:38 -0000
Reply-To: [EMAIL PROTECTED]
[Posted and mailed]
In article <[EMAIL PROTECTED]>,
Patrick Peter <[EMAIL PROTECTED]> writes:
> printable
>
> Hello Sir/Madam
>
> I am running Suse Linux 7.1. My server is connected to a HUB and the =
> HUB is connected ADSL modem. Also my Windows computer is connected to =
>
> HUB and the connection for that is working. My suse connection is not =
>
> working. I don't have any static IP address for this connection. All I
> =
> have is Dynamic IP address. Please help me to do this.
It depends on how your ISP assigns IP addresses, and whether you can
get two of them. If your ISP uses DHCP, using a Linux DHCP client
(pump, dhcpcd, and dhclient are the most popular) should work. At least
one of these comes standard with all Linux distributions, and can be
configured with the normal Linux networking tools (somewhere in YaST
for SuSE).
Most dynamic IP addresses for ADSL are assigned via PPPoE, though. For
this, you'll need a PPPoE client. I'd be surprised if SuSE 7.1 didn't
come with one of these, given that it's brand-new and SuSE is known for
including everyting (even the kitchen sink) in its distributions. The
most popular PPPoE client for Linux is Roaring Penguin, but there are
others. I've got links to several at
http://www.rodsbooks.com/network/network-dsl.html.
Note that many ISPs employ techniques to prevent people from obtaining
more than one IP address at a time. If DHCP, this is most often done by
examining the MAC address of the connecting system. For PPPoE, it's done
by tracking usernames and passwords. Either way, you may not be able to
get more than one IP address. Also, your current configuration directly
exposes both machines to the Internet, which increases your security
risks. IMHO, a better solution in most cases is to use a dedicated
hardware router. (Many of these are reviewed at
http://www.practicallynetworked.com/reviews/.) Alternatively, you could
use one computer as the router -- connect the DSL modem to one computer,
then use another Ethernet card to connect this computer to the second
one (either via your existing hub or via a crossover cable). Using a
computer in this way is cheaper, but less secure. If you use a dedicated
hardware router, *IT* handles the DHCP or PPPoE connection to the ISP,
and your local computers use DHCP or static IP addresses on a local
private network. The router uses a technique called NAT or IP
masquerading to share the Internet connection.
--
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration
------------------------------
From: ekk <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x
Subject: Re: Princeton Flat Panel Monitor w/ ATI Xpert 128
Date: Thu, 08 Mar 2001 09:42:12 -0500
Actually, I tried using GNOME instead of XFCE, and GNOME works fine. Too bad,
I like the simplicity of XFCE.
Thanks again,
Ken
ekk wrote:
> Thanks for your reply,
> I was afraid of that. We have had some trouble with screen blanking using
> anything higher than XFree86 3.3.5-3. I specifically have had trouble with
> the version that comes with RedHat 6.2, and XFree86 4.0.1. I will give 4.0.2
> a shot, but I am doubtful it won't blank also.
>
> An explanation of the screen blanking problem-
> Our software uses a motif DrawingAreaWidget as it's main window area.
> Sometimes, when the mouse is clicked inside the drawing area, the screen
> blanks temporarily. As soon as the mouse button is released, the screen
> returns to normal. It doesn't occur with XFree86 3.3.5-3, so I'm sure it
> isn't something to do with the software. I've posted questions about this on
> the motif newsgroups, but I never got any response.
>
> I'm open to ideas . . .
> Ken
> Joshua Baker-LePain wrote:
>
> > In comp.os.linux.x ekk <[EMAIL PROTECTED]> wrote:
> >
> > > I have a Princeton LCD 17" monitor I want to hook up to a box with an
> > > ATI Xpert 128 graphics card. I am trying to get the Mach64 server to
> > > work with a resolution of 1280x1024. Actually, I would feel better if
> > > I could get it to work at any resolution. I'm not extremely comfortable
> > > with the Modelines in the XF86Config file, although I went through the
> > > XFree86 Video Timings HOWTO, and I still couldn't get X to work. So, my
> > > question is: Has anyone had any experience getting a flat panel monitor
> > > to work with this specific card? If not, can you suggest an alternative
> > > card?
> >
> > I haven't used that specific card. However, in my experience, flat
> > panels work much better with XFree86 4.0.x than with 3.3.x. They seem
> > to be *very* particular about their modelines. And, since XFree 4 detects
> > them from the monitor itself, they get their preferred modelines.
> >
> > FWIW, I've got an IBM T84H hooked up to a VooDoo3 3000. It worked in
> > XFree3, but the pictures wasn't all that sharp. It looks great in XF4.
> > I also had it hooked up to an Elsa Synergy Force (Dell OEM GeForce 256
> > based board), working with the nv driver. There, it only worked in
> > analog mode, not digital (it has dual inputs).
> >
> > Good luck.
> >
> > --
> > Joshua Baker-LePain
> > Department of Biomedical Engineering
> > Duke University
------------------------------
** 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.setup.
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-Setup Digest
******************************
