Linux-Misc Digest #105, Volume #28 Thu, 14 Jun 01 02:13:02 EDT
Contents:
Re: hardware autodetection (Wroot)
Re: How much is Linux (TM) worth? (Wroot)
Problems configuring Network connection Mandrake-8.0 (Rajesh Radhakrishnan)
Re: hardware autodetection (Alexander Viro)
Re: Linux X goes away??? ("JT")
uninstalling software (Ben)
Re: Slackware 7.1: Lilo and X problems (Stanislaw Flatto)
Re: mnt vfat ("Tom Edelbrok")
Re: Writing an OS from scratch ("Steven J. Hathaway")
Re: Kernel messages: is it really hd? ("Tom Edelbrok")
Re: uninstalling software ("Steven J. Hathaway")
what was that game? ("Jcarnes")
Re: Compiling kernel for Red Hat 7.1 ("Meeko J. Raccoon")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Wroot)
Crossposted-To: alt.os.linux,comp.unix.bsd.freebsd.misc
Subject: Re: hardware autodetection
Date: 13 Jun 2001 21:11:18 -0700
John Hasler <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> Whining does no one any
> good.
Wrong! I feel much better.
Wroot
------------------------------
From: [EMAIL PROTECTED] (Wroot)
Subject: Re: How much is Linux (TM) worth?
Date: 13 Jun 2001 21:14:49 -0700
Marek Zawadzki <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> I say, let's make Linus sell the trademark (not the system, though:), then
> let's share the money, then let's call Linux Linux2, sell it again, and so
> on, and so forth :).
>
> -marek
>
> while (1) {
> $money = sell("Linux".$pf, Microsoft,
> $10000000000000000000000000000000000);
> send($money/$number_of_linux_users, $linux_users);
> if (!defined($pf)) $pf=0;
> $pf++;
> }
PERL sucks.
------------------------------
From: Rajesh Radhakrishnan <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux
Subject: Problems configuring Network connection Mandrake-8.0
Date: Thu, 14 Jun 2001 00:13:11 -0400
Hi,
I have an 3com 3c509 NIC and have to use the DHCP protocol. I haven't
been to able to get it to work. Tried with Mandrake Control Center then
did the old linux way.
I ran 'modprobe 3c509' and it didn't give me any message. Then I ran
'dhcpd -h <name> eth0' and get the following mesg.
Setting Rx ... to 0
Setting Rx ... to 1
eth0: infinite loop in interface, error 2001 (think those are the
exact words)
eth0: infinite loop in interface, error 2001
....
and keeps printing the above 'eth0...' statement and finally exits.
'ifup eth0' failed and in 'ifconfig -a' the TX field is always the same
in eth0 device.
Any suggestions...
Thanks
Rajesh
------------------------------
From: [EMAIL PROTECTED] (Alexander Viro)
Crossposted-To: alt.os.linux,comp.unix.bsd.freebsd.misc
Subject: Re: hardware autodetection
Date: 14 Jun 2001 00:25:41 -0400
In article <[EMAIL PROTECTED]>,
Peter T. Breuer <[EMAIL PROTECTED]> wrote:
>Do as you would with any company that acts like that .. turn up
>at the shop you bought from, and tell them you'll avoid
>that companies products, and would they please get their pcmcia cards
>from reputable manufacturers who write drivers for their hardware that
>enable you to use it!
C|N>K
OK, I should've known better that drinking coffee while reading news.
Had you ever seen the dungpiles hardware manufacturers try to pass for
drivers? No? Well, consider yourself lucky. I had. Saying that it's
crap is an insult to innocent fecal matter. There are exceptions,
but usually they have nobody who would be able to pass C 101,
let alone knew something about Unix kernel programming. Race-free code?
Forget it.
--
"You're one of those condescending Unix computer users!"
"Here's a nickel, kid. Get yourself a better computer" - Dilbert.
------------------------------
From: "JT" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.admin,comp.os.linux.hardware,comp.os.linux.questions,comp.os.linux.x,linux.redhat.install,linux.redhat.misc
Subject: Re: Linux X goes away???
Date: Thu, 14 Jun 2001 04:30:41 GMT
"J Sloan" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]...
> JT wrote:
>
> > Running RH7.0. I never can be assured if Linux is going to come up in X.
> > Sometimes it does and somethings its just a blank black screen. When it
> > doesn't I have to re-install the who OS over again. Running Matrox
Millenium
> > G200 8mgs ram.
>
> bzzt, wrong answer - reinstalling may be the
> windows way of fixing problems, but it's not
> the answer in the Unix world.
>
> Look in the sys logs to find out what is
> making the X server unhappy -
>
> > What confuses me, why would it work sometimes and sometimes not?
>
> Flaky hardware?
>
> the log entries will shed more light.
>
> cu
>
> jjs
>
>
bzzt, wrong reply! You loose. Being a newbie, I'm sure the first time you
installed Linux, you decide to re-install yourself one time or another.
Yes, log entries would be a good thing to post here. No, its not flaky
hardware in this case.
------------------------------
From: [EMAIL PROTECTED] (Ben)
Subject: uninstalling software
Date: 13 Jun 2001 21:33:39 -0700
Hi all,
I was just wondering if there is a way to uninstall software under
Linux. I know hiow to do it for rpm packages but I don't know how to
uninstall software that is installed from binary files. Also I don't
have the log for the installation path... Is there a way?
Thanks
Ben
------------------------------
From: Stanislaw Flatto <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.setup
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==
------------------------------
From: "Tom Edelbrok" <[EMAIL PROTECTED]>
Subject: Re: mnt vfat
Date: Thu, 14 Jun 2001 05:04:56 GMT
This works for me: (in /etc/fstab)
/dev/hda1 /mnt/c-drive vfat exec,dev,suid,rw 1 1
/dev/hda6 /mnt/d-drive vfat exec,dev,suid,rw 1 1
The above mounts my local-machine C: and D: partitions in rw mode every time
I boot.
Dave <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Successfully mounted a vfat partition in Linux. Can't write to it
though...
>
> what's the right line to put in /etc/fstab
>
> help strongly appreaciated!!
>
> Dave.
------------------------------
Date: Wed, 13 Jun 2001 22:07:44 -0700
From: "Steven J. Hathaway" <[EMAIL PROTECTED]>
Subject: Re: Writing an OS from scratch
> My first OS.
This was done on an old 8080/8085/Z80 system with 1Mbps S100 backplane.
Initial memory load was done via toggle switches to load bit patterns into
memory, then signaling an interrupt to tell the CPU to start executing those
bit patterns from a specified location.
Then came the matter of writing a primitive device driver to read paper tape.
And the ability to create codes on paper tape with an appropriate paper tape
punch device. This code was also initially transferred to memory, until I
acquired an EPROM programming device onto which to install a primitive
BIOS of interrupt routines to handle various devices.
After puting BIOS code into EPROM, I could then create a dumb assembler
program to convert character sequences from a dumb ASCII terminal
into executable program binary. These sequences were copied to paper tape.
>From this, I was able to create a better assembly language interpreter
and refine device drivers, such as those necessary to support 8-inch
floppy disks and 5Meg hard disk drives.
I then created a delay circuit and wired it into the power supply and some
solid state logic to force a startup interrupt to the CPU when power was
applied to the system and transients had subsided to a safe level. From
this I had the beginnings of a computer from which a DOS style operating
system (i.e. CPM) could be obtained and re-engineered for my computer
hardware.
With the tools that CPM supported, I could write cross-compilers, and
other operating system development tools, including writing code for
Motorola 6800 processors, DEC PDP8, PDP-11, PDP-15, KL-1090,
IBM360, et. al.
But what a time-consuming venture when PCs were hobyist-hacker
tools. (Before Apple, Before Microsoft).
------------------------------
From: "Tom Edelbrok" <[EMAIL PROTECTED]>
Subject: Re: Kernel messages: is it really hd?
Date: Thu, 14 Jun 2001 05:12:32 GMT
Using the 2.2.xx kernel won't help. I have just upgraded to 2.2.14 and
2.2.19 to play with both, and they both periodically these exact same kind
of hard drive error messages. My hard drive has no problem when running
under Windows 98, NTWS, or NT Server, so perhaps Linux is just really clever
at finding errors or else it is really stupid and is reporting errors that
don't exist.
I don't know the answer to this problem, but I do know it occurs commonly on
2.2.xx on my machine (once every couple days if transferring a very large
file of about 20meg ?).
Tom
Dave Uhring <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> rennix wrote:
>
> > Hi,
> >
> > since about 1 week I get these messages. They appear in the logfiles
> > as well as on the console. I dont get them when I log in remote
> > though....
> >
> > Anyway
> >
> > Is this really a hard drive error or is it just a problem with the DMA
> > BusMastering?
> > I wonder if could solve the problem just by rebooting the box and
> > disabling the DMA with hdparm - since (I guess) DMA is now enabled per
> > default in the 2.4.x kernel.
> >
> > Its an RH7.0 with 2.4 kernel with a 20 GB HD which serves as Web- and
> > FTPServer.
> > Thats why I didnt reboot yet. Shit hits the fan if the box doesnt come
> > up again.
> >
> /snip/
> >
> >
> > Any suggestion is aprecciated
> >
> > Thanx
> >
>
> The 2.4.X kernel is your problem here. Boot from the 2.2.XX kernel and
> your problems will disappear.
>
> I installed Red Hat 7.1 on a system which gave the exact same error
> messages with RH's 2.4.2 kernel and got rid of the problem by installing a
> 2.2.19 kernel.
>
> Fundamentally, if you are using legacy hardware then use a legacy kernel.
>
------------------------------
Date: Wed, 13 Jun 2001 22:20:33 -0700
From: "Steven J. Hathaway" <[EMAIL PROTECTED]>
Subject: Re: uninstalling software
Ben wrote:
> Hi all,
> I was just wondering if there is a way to uninstall software under
> Linux. I know hiow to do it for rpm packages but I don't know how to
> uninstall software that is installed from binary files. Also I don't
> have the log for the installation path... Is there a way?
>
> Thanks
>
Software uninstall is not fully functional with the public software
distributions, unless the packages are for a commercial Linux
distribution, and that you only install software supported by the
Linux distribution using the tools offered by the Linux distribution.
Otherwise uninstall operations are bound to cause problems more often
than not. If you have a mixed bag of software products, You should
keep your own log of what objects go where, their systems dependencies,
and their special configuration files, and sometimes system startup
scripts. The more dependencies that the software has, it makes
software removal more difficult if not impossible and have a
workable computer system.
- Steve Hathaway
------------------------------
From: "Jcarnes" <[EMAIL PROTECTED]>
Subject: what was that game?
Date: Thu, 14 Jun 2001 05:31:48 GMT
I am trying to find the name and eventually the source code for a game that
came with one of the 6.x versions of Red Hat linux. It might have been
"marbles" or "sameGame"? It was played by clicking on a colored sphere, and
all like-colored spheres touching it would then disappear, and the stack
would drop down.... Any Ideas?
thanks
------------------------------
From: "Meeko J. Raccoon" <[EMAIL PROTECTED]>
Subject: Re: Compiling kernel for Red Hat 7.1
Crossposted-To: comp.os.linux.redhat
Reply-To: [EMAIL PROTECTED]
Date: Thu, 14 Jun 2001 05:40:20 GMT
Well, I did figure out what the problem was, and indeed it was something
simple and quite stupid of me to overlook. I am using a floppy to boot
the system, and I wasn't writing the lilo information to the floppy, only
to the hard drive. I did a lilo -b /dev/fd0 and now everything works
fine, and I'm using my custom 2.4.5 kernel.
-Meeko
> * Meeko wrote:
>> I'm sure there is a very simple solution to this, but I just can't
>> seem to figure it out. I am trying to compile kernel 2.4.5 for my
>> RH7.1 system. I have done all the steps I normally do to compile a
>> kernel (I have done this repeatedly for several RH distributions
>> without a problem, so its not like I don't know what I'm doing).
>>
>> I downloaded the kernel source, untarred it to /usr/src/linux, cd'd to
>> linux, make mrproper, make xconfig, spent 30 minutes making sure every
>> setting is how I want it, saved configuration and exited, make dep,
>> make clean, make bzImage, make modules, make modules_install, moved
>> the kernel from arch/i386/blah blah... to /boot/vmlinuz-2.4.5-source,
>> moved System.map to /boot, removed the old symlinks and created new
>> symlinks for vmlinuz -> vmlinuz-2.4.5-source; System.map ->
>> System.map-2.4.5, edited /etc/lilo.conf, ran lilo, and rebooted.
>
> What's the output of /sbin/lilo ?
> Can you boot the new kernel if you specify it at the Lilo prompt?
>
> -Jan
>
------------------------------
** 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.misc.
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-Misc Digest
******************************
