Linux-Setup Digest #436, Volume #21 Thu, 14 Jun 01 01:13:10 EDT
Contents:
Re: problem with lo interface (Michael Meissner)
Newbie Monitor help ("Steve")
Re: ipchain settings for "soft" router (chris)
Re: Why is my sound card locking up my machine? (Rand Simberg)
Re: Netscape's network connection was refused by the server (Dave Uhring)
Re: how to kill process when kill -9 is not working ? (Dave Uhring)
Can I LINUX on this PC? ("Guz")
Re: Slackware 7.1: Lilo and X problems (Stanislaw Flatto)
----------------------------------------------------------------------------
Subject: Re: problem with lo interface
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 13 Jun 2001 22:11:22 -0400
"John W. Price" <[EMAIL PROTECTED]> writes:
> Hi all:
>
> When I boot my system (laptop running RH 6.2, kernel 2.2.17-14), it
> doesn't create the lo interface. This seems (I'm no expert) to prevent
> me from sending mail directly from my box; I have to go through a mailer
> on another box. If I create the interface, with the command
>
> ifconfig lo 127.0.0.1
>
> everything works fine. It would be nice, however, if this happened
> automatically when I boot. According to the boot messages, however,
> this is happening. If I look at the output of dmesg, I get:
>
> Jun 10 13:26:34 bmkn3 network: Bringing up interface lo succeeded
>
> However, when I run ifconfig after booting, it's not there. Ideas?
>
> Thanks in advance,
> John
(Std. disclaimer, I work on GCC, and not Linux, so this is all IMHO)
I suspect something got messed up. Try starting X (if it isn't started
already), and run netcfg. Go into the interfaces section, and see whether lo
is set to be actived at boot time. If it isn't, mark it so and reboot. If you
are a text kind of guy, look at:
/etc/sysconfig/network-scripts/ifcfg-lo
It should be something like:
DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
# If you're having problems with gated making 127.0.0.0/8 a martian,
# you can change this to something else (255.255.255.255, for example)
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback
BOOTPROTO=none
Also, you want to check:
/etc/sysconfig/network
and it should have the line:
NETWORKING=yes
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: "Steve" <[EMAIL PROTECTED]>
Subject: Newbie Monitor help
Date: Wed, 13 Jun 2001 21:17:22 -0500
I had used the graphic monitor and resolution change in KDE to
change to my specific video card and to a 1024x768 refresh rate.
The settings worked fine for the rest of the session. However, on
reboot, my machine now boots to text mode rather than graphical.
When I do a startx, it tries to go graphical but then bails back
out to text mode and gives me the following error:
Fatal Server Error:
Could not open font 'fixed'
I tried to change the settings back using xf86config but that did
not help. Can someone help me out? I am using Mandrake 7,2
------------------------------
From: [EMAIL PROTECTED] (chris)
Crossposted-To:
alt.os.linux,comp.os.linux,comp.os.linux.admin,comp.os.linux.networking,comp.os.linux.redhat,linux.redhat,linux.redhat.misc,comp.os.linux.questions
Subject: Re: ipchain settings for "soft" router
Date: 13 Jun 2001 19:44:19 -0700
remember:
first input chain then forward and then output chain.
an example:
ipchains -P input DENY
ipchains -P forward DENY
ipchains -P output DENY
ipchains -A input -s 127.0.0.1 -j ACCEPT
ipchains -A input -s internal_subnet -d 0/0 -i eth0 (1) -j ACCEPT
ipchains -A input -s external -d 0/0 -i eth1 (0) -j ACCEPT
ipchains -A input -s 0/0 -d external -i eth1 (0) -j ACCEPT ## don't do
it!!!!!
ipchains -A input -s 0/0 -d 0/0 -j -l DENY
ipchains -A forward -s internal_subnet -d 0/0 -j MASQ
ipchains -A forward -s 0/0 -d 0/0 -j -l DENY
ipchains -A output -s 127.0.0.1 -d 0/0 -j ACCEPT
ipchains -A output -s external -d 0/0 -i eth1 (0) -j ACCEPT
ipchains -A output -s internal_subnet -d internal_subnet -i eth0 (1)
-j ACCEPT
ipchains -A output -s 0/0 -d internal_subnet -i eth0 (1) -j ACCEPT
##don't!!!!!
ipchains -A output -s 0/0 -d 0/0 -j -l DENY
the packets come from the internal subnet going into input chain
(ACCEPT), then they are going to forward chain (MASQ),
then to the output chain (ACCEPT).
when they are coming back to your system:
first input chain (specify the protocols and ports to allow
!!!!;ACCEPT),then forward chain (MASQ),
then output chain (ACCEPT; the packets must going out to internal LAN
(Clients))
when you make "NAT-connections" with ipchains the packets will pass
all 3 chains.
not on "normal" connections (ssh from a client in internal LAN to
firwall i.e)
hope this helps!
"Qisheng Pan" <[EMAIL PROTECTED]> wrote in message news:<9g3mbc$6dm$[EMAIL PROTECTED]>...
> My server/router is running on Redhat linux 7.1 and has Dual NIC (eth0 and
> eth1). eth1 connects to a cable modem that provides Internet service. eth0
> connects to internal subnetwork. It has worked fine on Windows95 with Sygate
> 3.1. However, it has problem on linux with ipchains.
>
> Following offical ip-chain-howto and ip-masquerade-howto, I set ipchains as
> follows:
>
> (1) Modify /etc/sysconfig/network and change FORWARD_IPV4=false to
> FORWARD_IPV4=true
>
> (2) At the end of /etc/rc.d/rc.local, I add the following code:
>
> /sbin/depmod -a
> /sbin/modprobe ip_masq_ftp
> echo "1" > /proc/sys/net/ipv4/ip_forward
> echo "1" > /proc/sys/net/ipv4/ip_always_defrag
>
> # As dynamic IP users of (DHCP) cable modem, I set:
> echo "1" > /proc/sys/net/ipv4/ip_dynaddr
>
> /sbin/ipchains -M -S 7200 10 160
>
> # As dynamic IP users of (DHCP) cable modem, I set:
> /sbin/ipchains -A input -j ACCEPT -i eth1 -s 0/0 67 -d 0/0 68 -p udp
>
> /sbin/ipchains -P forward DENY
> /sbin/ipchains -A forward -i eth1 -s 192.168.10.0/24 -j MASQ
>
> The linux server/router can connect to Internet. PCs on internal subnet can
> also ping outside IPs, but they can not visit them by HTTP or Telnet. They
> cannot even resolve the name (though I already set DNS in resolv.conf). If I
> use IP address directly on netscape, the error message is:
>
> "netscape's network connection was refused by the server
> xxx.xxx.xxx.xxx, The server may not be accepting connection
> or may be busy. Try connecting again later".
>
> If anyone know what is the problem? Maybe probem come from firewall. But I
> don't know how to fix it. Any suggestion is welcome. Thanks.
------------------------------
From: [EMAIL PROTECTED] (Rand Simberg)
Crossposted-To: comp.os.linux.x
Subject: Re: Why is my sound card locking up my machine?
Date: Thu, 14 Jun 2001 04:08:48 GMT
On Wed, 13 Jun 2001 01:03:29 GMT, in a place far, far away,
[EMAIL PROTECTED] (Rand Simberg) made the phosphor on my
monitor glow in such a way as to indicate that:
>I've got a new cm8338-based sound card that I'm trying to use in my
>RH6.2 system (running 2.2.19 of my own build). After many travails
>(available in another thread in c.o.l.setup for those interested) I
>got the drivers installed.
>
>I can run 'modprobe cmpci' and it doesn't squawk, other than to tell
>me that my /etc/modules.conf is more recent than ../../modules.dep.
>
>I can load the mixer, and the CD player. But when I try to actually
>make it make some kind of sound (e.g., esd from the command line), the
>system locks up instantly and has to be hard rebooted.
>
>I've looked at /proc/interrupts and /proc/ioports and see no conflicts
>of cmpci with anything else. What other diagnostics can I do to see
>why sound attempts send the machine off to never-never land?
Never mind. I upgraded to 2.4.5, installed the card in the kernel,
and the problem disappeared.
Thanks for nothin' ;-)
--
simberg.interglobal.org * 310 372-7963 (CA) 307 739-1296 (Jackson Hole)
interglobal space lines * 307 733-1715 (Fax) http://www.interglobal.org
"Extraordinary launch vehicles require extraordinary markets..."
Replace first . with @ and throw out the "@trash." to email me.
Here's my email address for autospammers: [EMAIL PROTECTED]
------------------------------
From: Dave Uhring <[EMAIL PROTECTED]>
Subject: Re: Netscape's network connection was refused by the server
Date: Wed, 13 Jun 2001 23:11:25 -0500
Bob Bourne wrote:
> Three examples:
> Netscape's network connection was refused by the server
> home.netscape.com
> etc.
> Netscape's network connection was refused by the server
> www.debian.org
> etc.
> Netscape's network connection was refused by the server
> packages.debian.org
> etc.
> She's asking for Configuration location (URL)
> and SOCKS Host:
> Lynx connects and downloads, OK.
> [Communicator 4.77]
> [dist: debian 2.2 R3 i386, 3cdrom set]
> [$ export http_proxy="http://proxy.sale.vic.australis.com.au:80/"; - has
> [been
> set.]
> Any ideas greatly appreciated.
> PM - replies to me fine.
> Bob Bourne.
Configure your proxy server in Netscape. Edit, Preferences, Advanced,
Proxies.
------------------------------
From: Dave Uhring <[EMAIL PROTECTED]>
Subject: Re: how to kill process when kill -9 is not working ?
Date: Wed, 13 Jun 2001 23:19:00 -0500
DVHandorf wrote:
> Yes, if likk -9 PID does not work, the only thing left short of rebooting
> is
> changing the runlevel. Just log in as root, type init 1, and when a
> prompt shows up(not password) type init (your previous runlevel here).
>
Kill the parent process.
# ps -efl | grep <process>
The parent process is listed in the 5th column (PPID).
------------------------------
From: "Guz" <[EMAIL PROTECTED]>
Subject: Can I LINUX on this PC?
Date: Wed, 13 Jun 2001 23:48:36 -0500
Hi there:
I have a self built PC with:
815E chipset on CUSL2 MoBoard
BIOS 1003
PIII 800EB -133
512SDRAM memory 133.(non ecc).
Sound Card is SB Live! Platinum.
OS W98SE
And I have the 3 CDs packet from Debian-Linux.
Can I install this OS on this PC? ...
In the file "boot.bat" It says that
" CPU is in V86-Mode (May be WINDOWS, EMM386, QEMM, 386MAX,...) You need
pure 386/486 real mode or a VCPI server to boot Linux..."
One more question:
I can't boot from my CD-ROM Drive, How can I make a bootable Floppy Disc in
order to have acces to my CD and install all the rest?
Any comments?... Thanks in advance.
------------------------------
From: Stanislaw Flatto <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.misc
Subject: Re: Slackware 7.1: Lilo and X problems
Date: Thu, 14 Jun 2001 15:08:20 +1000
This is a multi-part message in MIME format.
==============B77F29E9F532C5CC79C4EBDB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Attached find my lilo.conf and XF86Config which perform by invoking frame
buffering on slack 7.1.
Stanislaw.
Slack user from Ulladulla.
Michael Pye wrote:
> OK, first problem first. The installer tried to install lilo (on the MBR, my
> hardware doesn't leave any choice) it failed. I have had a look at
> /etc/lilo.conf and tried several different configurations, including using
> liloconfig, it always happens as follows:
>
> # lilo
> Fatal: Kernel /vmlinuz is too big.
>
> Now I have no idea how the kernel got too big, it is a fresh install, and it
> wasn't to big last time I installed Slackware. I used the same kernel image
> (bare.i). Any help would be appreciated.
>
> Now, after I use the kernel image I used to install (bare.i) from a floppy,
> and then use
>
> boot: mount root=/dev/hda6
>
> I can boot into my system. However, I cannot start X.
>
> $ startx
> Fatal server error:
> open_framebuffer: failed to open /dev/fb0 (no such device)
>
> How can I rectify this state of affairs. I was looking forward to making use
> of Slackware (the last install was defective for different reasons, I
> customised it too much and didn't end up with a functional system, though it
> did boot fine with lilo...)
>
> Thanks in anticipation
>
> MP
==============B77F29E9F532C5CC79C4EBDB
Content-Type: text/plain; charset=us-ascii;
name="lilo.conf"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="lilo.conf"
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32
boot = /dev/hda
#compact # faster, but won't work on all systems.
delay = 50
# Normal VGA console
# vga = normal
# VESA framebuffer consoles begin
#================================
# vga=792 # 1024x768x16M
# vga=791 # 1024x768x64k
# vga=790 # 1024x768x32k
# vga=773 # 1024x768x256
#================================
vga=789 # 800x600x16M
# vga=788 # 800x600x64k
# vga=787 # 800x600x32k
# vga=771 # 800x600x256
#================================
# vga=786 # 640x480x16M
# vga=785 # 640x480x64k
# vga=784 # 640x480x32k
# vga=769 # 640x480x256
#================================
# VESA framebuffer consoles end
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = slak
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda3
label = heb
table = /dev/hda
# DOS bootable partition config ends
==============B77F29E9F532C5CC79C4EBDB
Content-Type: text/plain; charset=us-ascii;
name="XF86Config"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="XF86Config"
# XF86Config auto-generated by XF86Setup
#
# Copyright (c) 1996 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# See 'man XF86Config' for info on the format of this file
# This XF86Config file is designed for use with the Linux framebuffer console.
# This generic interface should work with nearly all video cards (although
# not every card will support every resolution). To use the Linux framebuffer
# console, you need to enable these kernel options:
# Using 'make menuconfig', in 'console drivers', enable:
# [*] VGA text console
# [*] Video mode selection support
# [*] Support for frame buffer devices (EXPERIMENTAL)
# [*] VESA VGA graphics console
# [*] Advanced low level driver options
# <*> 8 bpp packed pixels support
# <*> 16 bpp packed pixels support
# <*> 24 bpp packed pixels support
# <*> 32 bpp packed pixels support
# <*> VGA characters/attributes support
# [*] Select compiled-in fonts
# [*] VGA 8x8 font
# [*] VGA 8x16 font
# If you have a Matrox or ATI Mach64, you might try enabling the options having
# to do with those cards as well. However, if the card is VESA compliant, you
# don't really need to (and it might cause problems, possibly)
#
# To get the kernel to start in VESA framebuffer mode, you need to pass it
# a vga= init string at boot time. For example, if you use LILO you'll
# probably find a vga=normal string in your /etc/lilo.conf. If you edit that
# to one of the values in this table:
#
# Colours 640x480 800x600 1024x768 1280x1024 1600x1200
# --------+---------------------------------------------
# 256 | 769 771 773 775 796
# 32,768 | 784 787 790 793 797
# 65,536 | 785 788 791 794 798
# 16.8M | 786 789 792 795 799
#
# ...such as this for 1024x768x64k:
# vga = 791
# and then reinstall LILO by running 'lilo' as root, then at the next boot
# Linux should start in a VESA framebuffer console mode.
#
# For more information on how to activate the Linux frame buffer, see
# /usr/src/linux/Documentation/fb/vesafb.txt, and the mini HOWTO 'Vesafb'.
# This can be found at ftp://ftp.cdrom.com/pub/linux/slackware/docs/mini/Vesafb
#
# Enjoy! :)
# -- [EMAIL PROTECTED]
#
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
EndSection
Section "ServerFlags"
EndSection
Section "Keyboard"
Protocol "Standard"
AutoRepeat 500 30
LeftAlt Meta
RightAlt Meta
ScrollLock Compose
RightCtl Control
XkbKeycodes "xfree86"
XkbTypes "default"
XkbCompat "default"
XkbSymbols "us(pc101)"
XkbGeometry "pc"
XkbRules "xfree86"
XkbModel "pc104"
XkbLayout "us"
EndSection
Section "Pointer"
# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Protocol "Microsoft"
# On Linux, /dev/mouse is usually a link to the real mouse device. This is
# generally the PS/2 mouse device /dev/psaux, or one of the serial ports
# such as /dev/ttyS0 or /dev/ttyS1. If /dev/mouse isn't working, you can try
# relinking it to one of the other mouse devices, or using one of these
# devices directly. If your mouse needs a kernel module, you might also look
# at /etc/rc.d/rc.modules to make sure it's getting loaded at boot time.
Device "/dev/mouse"
# Device "/dev/psaux"
# Device "/dev/ttyS0"
# Device "/dev/ttyS1"
Emulate3Timeout 50
Resolution 100
Buttons 3
Emulate3Buttons
EndSection
Section "Monitor"
Identifier "Primary Monitor"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30-65
VertRefresh 50-100
EndSection
Section "Device"
Identifier "Primary Card"
EndSection
Section "Screen"
Driver "FBDev"
Device "Primary Card"
Monitor "Primary Monitor"
SubSection "Display"
# This must match the display depth you're using for your framebuffer console.
# If it doesn't, you'll get this error when you try to run 'startx':
# Fatal server error:
# fbdevScreenInit: unable to set screen params (Invalid argument)
# If that happens, try one of the other color depth choices.
# Uncommment one of the choices below:
# Depth 8
# Depth 16
# Depth 24
Depth 32
Modes "default"
EndSubSection
EndSection
==============B77F29E9F532C5CC79C4EBDB==
------------------------------
** 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
******************************
