Linux-Setup Digest #195, Volume #21 Wed, 9 May 01 16:13:17 EDT
Contents:
PCI modem 3COM/USR 2977 (Mark Slagell)
Re: inetd (J Hayward)
Re: Need Module for 3c905B-TX NIC card for RedHat 6.2 (David)
harddisk wierdness ... failed to respond for 5 minutes (Professor Bruno)
Re: Raid 1 (Mirror) ("Christian Bachmaier")
Re: Compiling 2.4.4 kernel (Thierry Pot)
Re: anyone have solution install RH7.1 on 16M RAM ("tin")
buffer setting for iptables? ("tin")
setup a CANON BJC-5000 printer (Thierry Pot)
LILO no boot .. says "LIL-" then just hangs there ("Counts")
r128_do_wait_for_fifo failed in kernel 2.4.2 ("FEEB")
Re: Compiling 2.4.4 kernel
Re: SOLVED: Shutdown for non root users (Kevin)
...dup2: Bad file descriptor [FAILED] .../dev/null: Read-only file system ("Brian
Wildasinn")
Re: Red Hat Linux 7 With RCA (AT&T@Home) Cable Modem (Ian Pilcher)
user mount ("Martin Greco")
Re: ...dup2: Bad file descriptor [FAILED] .../dev/null: Read-only file system
("Brian Wildasinn")
GRUB really is better than LILO! (Was: Re: GRUB: How to install to hard disk
(without installing Linux) ?) (Kenny McCormack)
----------------------------------------------------------------------------
From: Mark Slagell <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: PCI modem 3COM/USR 2977
Date: Wed, 09 May 2001 13:17:02 -0500
I've been surfing around for the world's collected wisdom on making this
modem work but am coming up empty so far. Possibly relevant info is
below. Can anybody shed light?
TIA
-- Mark
===========================
>uname -a
Linux pc5053 2.2.18 #4 Mon Apr 9 14:58:16 CDT 2001 i686 unknown
===========================
>lspci -v
[...]
01:0b.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610
(rev 01) (prog-if 02 [16550])
Subsystem: US Robotics/3Com USR 56k Internal FAX Modem
(Model 2977)
Flags: medium devsel, IRQ 3
I/O ports at dff0
Capabilities: [dc] Power Management version 2
===========================
>cat /proc/pci
[...]
Bus 1, device 11, function 0:
Serial controller: Unknown vendor Unknown device (rev 1).
Vendor id=12b9. Device id=1008.
Medium devsel. IRQ 3.
I/O at 0xdff0 [0xdff1].
===========================
>cat /proc/interrupts
CPU0
0: 247814 XT-PIC timer
1: 4923 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 32587 XT-PIC eth0
9: 12746 XT-PIC Intel ICH 82801AA
12: 69297 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 961293 XT-PIC ide0
15: 7 XT-PIC ide1
NMI: 0
===========================
>setserial /dev/ttyS3 port 0xdff0 autoconfig auto_irq
>setserial -g /dev/ttyS3
/dev/ttyS3, UART: unknown, Port: 0xdff0, IRQ: 3
>minicom
[unresponsive on /dev/ttyS3]
===========================
>[tried setserial with uart as 16550A, 16450, etc, no difference]
>[tried setserial options: ^fourport, skip_test. no difference]
>[tried changing IRQ with setpci, managed to lock up the machine a few times]
------------------------------
From: J Hayward <[EMAIL PROTECTED]>
Subject: Re: inetd
Crossposted-To: comp.os.linux.misc
Date: Wed, 9 May 2001 11:18:46 -0700
Hello,
inetd had been replaced by xinetd in RH 7.x. Since Mandrake is based on RH,
I assume it has been replaced on Mandrake also.
man xinetd
man xinetd.conf
Regards,
Jim H
Norman Zhang wrote:
> I'm using Linux Mandrake 8.0. But I can't seem to be able to find inetd on
> the distribution CDs. All I see is xinetd. Has inetd being removed? Where
> can I find inetd? I search www.rpmfind.net, and there seems to be one for
> RedHat 6.2.
>
> Thanks and Regards,
> Norman
>
>
>
------------------------------
From: David <[EMAIL PROTECTED]>
Subject: Re: Need Module for 3c905B-TX NIC card for RedHat 6.2
Date: Wed, 09 May 2001 18:27:14 GMT
M Yasir Khan wrote:
>
> Hi all,
>
> Could anyone please send me or let me know the location for the NIC card
>
> driver for RedHat 6.2.
>
> My NIC Card is "3c905B-TX" . At the time of installation linux picks
> 3c59x automatically.... but it does not work.
>
> I'd been on 3Com site to get the proper driver for linux, but the driver
>
> I found there was for Linux 5.2 or 6.0. That driver didn't work for my
> 6.2 box....
>
> Could anyone Please solve my problem... Please reply me on my email
> "[EMAIL PROTECTED]" too.
>
> Regards,
>
> Yasir.
It's in the kernel sources. Use the 3c59x module.
--
Confucius say: He who play in root, eventually kill tree.
Registered with the Linux Counter. http://counter.li.org
ID # 123538
Completed more W/U's than 99.193% of seti users. +/- 0.01%
------------------------------
From: [EMAIL PROTECTED] (Professor Bruno)
Crossposted-To: linux.redhat,comp.os.linux.hardware,comp.infosystems.www.servers.unix
Subject: harddisk wierdness ... failed to respond for 5 minutes
Date: 9 May 2001 18:30:07 GMT
Greetings,
Today I encountered something out of my realm in the /var/log/messages file.
At first, I thought that our server was hacked and we were
experiencing a denial of service attack. However, once the server
started responding and having done a few checks of our trips it
didn't appear to be the case.
Then looking at the /var/log/messages file I saw some things
which I've never seen. Any guidance with respect to this
would be greatly appreciated.
Details: RH6.2 Linux with latest patches, 2 20GB IDE HD's, 512 MB RAM,
2 P3-800 CPUs, running primarily as a web server w/ 1.5 mill hits per month;
also running sendmail, MySQL, PostgreSQL, et cetera.
Thanks!
Max Pyziur
[EMAIL PROTECTED]
###########################################
May 9 13:48:59 brama kernel: hda: irq timeout: status=0xd0 { Busy }
May 9 13:49:29 brama kernel: ide0: reset timed-out, status=0x80
May 9 13:49:29 brama kernel: hdb: status error: status=0x00 { }
May 9 13:49:29 brama kernel: hdb: drive not ready for command
May 9 13:49:29 brama kernel: hdb: status error: status=0x00 { }
May 9 13:49:29 brama kernel: hdb: drive not ready for command
May 9 13:49:29 brama kernel: hdb: status error: status=0x00 { }
May 9 13:49:29 brama kernel: hdb: drive not ready for command
May 9 13:49:29 brama kernel: hdb: status error: status=0x00 { }
May 9 13:49:29 brama kernel: hdb: drive not ready for command
May 9 13:49:59 brama kernel: ide0: reset timed-out, status=0x80
May 9 13:49:59 brama kernel: hda: status timeout: status=0x80 { Busy }
May 9 13:56:18 brama kernel: hda: drive not ready for command
May 9 13:56:18 brama kernel: ide0: reset timed-out, status=0x80
May 9 13:56:18 brama kernel: hdb: status error: status=0x00 { }
May 9 13:56:19 brama telnetd[12728]: ttloop: peer died: EOF
May 9 13:56:19 brama inetd[459]: pid 12728: exit status 1
May 9 13:56:19 brama kernel: hdb: drive not ready for command
May 9 13:56:19 brama kernel:
May 9 13:56:19 brama kernel: wait_on_bh, CPU 1:
May 9 13:56:19 brama kernel: irq: 0 [0 0]
May 9 13:56:19 brama kernel: bh: 1 [1 0]
May 9 13:56:19 brama kernel: <[c010bf0d]> <[c016aaf9]> <[c016b0ce]> <[c017a100
[...]
and then eventually
May 9 13:56:20 brama kernel: EXT2-fs error (device ide0(3,5)): ext2_read_inode:
unable to read inode
block - inode=588985, block=1179661
May 9 13:56:20 brama kernel: hdb: status error: status=0x00 { }
May 9 13:56:20 brama kernel: hdb: drive not ready for command
May 9 13:56:20 brama kernel: hdb: status error: status=0x00 { }
May 9 13:56:20 brama kernel: hdb: drive not ready for command
May 9 13:56:20 brama kernel: ide0: reset: success
------------------------------
From: "Christian Bachmaier" <[EMAIL PROTECTED]>
Subject: Re: Raid 1 (Mirror)
Date: Wed, 9 May 2001 20:29:50 +0200
Hello,
try it with the boot-root-raid-lilo-Howto at www.linuxdoc.org,
thats how i did that.
Greetings,
Chris
--
| if you can click, use windows, |
| but if you can read, try linux |
--
| if you can click, use windows, |
| but if you can read, try linux |
"Armando Duarte" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:9dbo39$icb$[EMAIL PROTECTED]...
> Hi.
> I have a lx box with redhat 6.2, with one disk. Is there any way to
install
> a second disk, impelmenting raid, without reintalling the all system?
(with
> NT it is possible...)
> Thank's.
>
> --
> -------------------------------------------
> Armando Duarte
> Centro Hospitalar de Coimbra (http://www.chc.min-saude.pt)
> Departamento de Informa��o para a Gest�o
> Telef. 351 39 800080; 351 39 800192
> [EMAIL PROTECTED]
>
>
>
>
------------------------------
From: Thierry Pot <[EMAIL PROTECTED]>
Subject: Re: Compiling 2.4.4 kernel
Date: Wed, 9 May 2001 20:39:01 +0200
Reply-To: [EMAIL PROTECTED]
>
> 2.4.4 compiles fine here without 'fatal errors'. But then again -
> without knowing what error, it is _quite_ difficult to help...
>
> Rasmus
>
That's true !!
I might say it is quite impossible !! ;)
------------------------------
From: "tin" <[EMAIL PROTECTED]>
Crossposted-To:
alt.comp.linux,comp.os.linux.admin,comp.os.linux.networking,comp.os.linux.questions,comp.os.linux.redhat,comp.os.linux.security
Subject: Re: anyone have solution install RH7.1 on 16M RAM
Date: Thu, 10 May 2001 02:22:46 +0800
not the swap partitions problem
is redhat will popup "not enought RAM to install "
before install process
anyway thank you very much
"James Richard Tyrer" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> tin wrote:
>
> > anyone have solution install RH7.1 on 16M RAM
> > Intel p100 box
>
> I had RH 5.2 running on a 486 with 8 MB of RAM and 127MB+ Swap; it did
> work. X was a bit slow and I didn't use a desktop -- NO KDE or GNOME --
> just fvwm or twm to run applications.
>
> You could probably install RH7.1. You can make a standard install if
> you have a large enough disk. But you will probably find KDE or GNOME
> too slow and if you want to try them you would need 256MB of Swap.
> There is a theory that two 127MB Swap partitions are faster than one
> large one. As I said above, you will probably want to use fvwm or twm
> to run X applications. GUI applications will not be very fast.
>
> On the other hand if you want it for Console only, it should be OK.
>
> But, I would add memory if you have room for it on the Mother Board.
>
> If it is an old type of memory, try picking it up used at Computer
> Renaissance.
>
> JRT
>
>
------------------------------
From: "tin" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.admin,comp.os.linux.networking,comp.os.linux.questions,comp.os.linux.redhat
Subject: buffer setting for iptables?
Date: Thu, 10 May 2001 02:26:43 +0800
hi all:
did iptables can set more RAM for iptables doing buffer? increase speed ?
thank you very much
--
[EMAIL PROTECTED]
------------------------------
From: Thierry Pot <[EMAIL PROTECTED]>
Subject: setup a CANON BJC-5000 printer
Date: Wed, 9 May 2001 20:47:48 +0200
Reply-To: [EMAIL PROTECTED]
I used to look for a driver for this printer.
I have not found one?
But does somebody can print whith this printer under linux ?
I use slackware distribution and kernel 2.4.4
I know BJC5000 is a windows printer but I heard that somebody succeed to
print under linux with a bjc600 driver ... does anybody can confirm ?
------------------------------
From: "Counts" <[EMAIL PROTECTED]>
Crossposted-To: dc.org.linux-users,comp.os.linux.advocacy
Subject: LILO no boot .. says "LIL-" then just hangs there
Date: Wed, 9 May 2001 14:57:47 -0400
I installed everything successfully (Slackware 4.1), recompiled a kernel,
rebooted, everything worked as expected. Then, not long afterwards on
another reboot, LILO just hangs. I have to boot using a floppy now. Any
suggestions on how to fix this?
Should I uninstall LILO and then re-install?
Thanks for any suggestions.
Bob
------------------------------
From: "FEEB" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: r128_do_wait_for_fifo failed in kernel 2.4.2
Date: Wed, 09 May 2001 15:09:34 -0400 (EDT)
Reply-To: "FEEB" <[EMAIL PROTECTED]>
Since I installed RedHat 7.1 distribution with kernel 2.4.2 on a 2xPIII
1GHz system, I am getting these in the system log:
kernel: [drm:r128_do_wait_for_idle] *ERROR* r128_do_wait_for_idle failed!
I was not able to find any reference to this message anywhere.
Does anyone know, what it means?
Thanks
Frank Bures, <grandial at softex.cz>
------------------------------
From: [EMAIL PROTECTED] ()
Subject: Re: Compiling 2.4.4 kernel
Date: Wed, 09 May 2001 19:24:51 GMT
On Wed, 9 May 2001 20:39:01 +0200, Thierry Pot <[EMAIL PROTECTED]> wrote:
>>
>> 2.4.4 compiles fine here without 'fatal errors'. But then again -
>> without knowing what error, it is _quite_ difficult to help...
>>
>> Rasmus
>>
>
>That's true !!
>I might say it is quite impossible !! ;)
Never mind. I blew away the directory tree, untar'd again and redid
the configuration. This time it compiled with no problems at all.
------------------------------
From: [EMAIL PROTECTED] (Kevin)
Subject: Re: SOLVED: Shutdown for non root users
Crossposted-To: alt.os.linux,comp.os.linux.misc
Date: Wed, 09 May 2001 19:28:37 GMT
Thanks so much for posting your solution with SOLVED in the
subject line. That makes it easier to find *answers* in
newsgroup archives instead of just the *problems*.
Cheers....
--
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.
------------------------------
From: "Brian Wildasinn" <[EMAIL PROTECTED]>
Subject: ...dup2: Bad file descriptor [FAILED] .../dev/null: Read-only file system
Date: Wed, 9 May 2001 12:02:33 -0700
Hi,
Read lots of Dejanews (er Google) posts regarding failed initialization
scripts in /etc/rc.d.
The RedHat guides were informative about the sequence of how to boot up a
running system.
After Lilo and the kernel pass control to init something gets out of whack.
It seems that /etc/rc.d/rc.sysinit can't do its job right, which is really
weird. I was using my 6.9 (Pinstripe) edition of RedHat when one day the
Acer Extensa 670CDT notebook decided to go into its BIOS. Upon reboot the
system hasn't been able to boot into multiuser mode.
Here's my observations, but without a cure yet:
Reinstalled via "Update" my system using an installation CDROM.
Reboot: ...dup2: Bad file descriptor
Ran "Expert" mode in CDROM and fscked the unmounted filesystem
Reboot: ...dup2: Bad file descriptor
Ran command prompt from anoter distro's CDROM & fscked again:
Reboot: ...dup2: Bad file descriptor
Rebooted and dropped into single user mode, mounted the installation CDROM
and remounted the filesystem read-write; & ran `rpm -vv -i --force
/mnt/cdrom/RedHat/RPMS/base*rpm
Reboot: ...dup2: Bad file descriptor
Curioristy began to set in so I remounted as read-write the filesystem and
manually started the various services in /etc/rc.d/init.d/* . These scripts
including the last one, linuxconf, returned [OK]. My prompt reading
root@(none). Startx works. In a Gnome-terminal I reboot the system using
`shutdown -r now`.
Reboot: ...dup2: Bad file descriptor.
Noticing that most of the /etc/ scripts mention RedHat 6.0, I transfer a
etc_rh6.0.tgz tarball by sneakernet via a floppy. With a backup etc.tgz made
I copy etc_rh6.0/rc.d/* over to /etc.
Reboot: ...dup2: Bad file descriptor.
Since that didn't work I restored the backup etc.tgz scripts I made, so I
could keep looking for a solution.
It appears that rc.sysinit has NOT been able to complete its job: Viewing a
boot screen I see that rc.sysinit fails at `action "Mounting proc
filesystem" mount -n -t proc /proc /proc` with all the next action
statements of the /etc/rc.d/rc.sysinit script consecutively failing as well,
dumping me back into logging in single-user mode to continue. Other a
Dejanews report similar errors with commenters suggesting fscking from a
boot disk or CDROM:
>Mounting proc filesystem dup2: Bad file descriptor [FAILED]
>configuring kernel parameters dup2: Bad file descriptor [FAILED]
>Setting Clock (utc): Wed May 9 12:31:31 PDT 2001 dup2:Bad file descriptor
[FAILED]
>Loading default keymap/etc/rc.d/rc.sysinit: /dev/null: Read-only File
system [FAILED]
>Activacting swap partitions dup2: Bad file descriptor [FAILED]
>Setting hostname localhost dup2: Bad file descriptor [FAILED]
/etc/rc.sysinit: /dev/null: Read-only file system
/etc/rc.sysinit: /dev/null: Read-only file system
>checking root filesystem dup2:
Remounting read-write the root file system, the /proc filesystem is able to
be mounted.
However, upon rebooting the proc file system is added to /etc/mtab as
none /proc /proc
The rhl-rg-6.2en guide states at "2. System Administration: The Boot
Process, Init, and Shutdown" states, "Init [first] runs
/etc/rc.d/rc.sysinit, which sets your path, sets up networking if necessary,
starts swapping, checks the filesystems, and so on. Basically, rc.sysiit is
taking care of everything that your system needs to have done at system
initialization." The guide goes on to say that Init implements the
/etc/inittab file for description of how to setup each runlevel.
The manual 8 page for init suggests not using 0 (halt), 6 (reboot), or 1
(single user). So I've set linuxconf runlevel to 5
Could someone tell me which rpm from the installation CDROM will replace the
/etc/rc.init scripts?
------------------------------
From: Ian Pilcher <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,comp.os.linux.misc
Subject: Re: Red Hat Linux 7 With RCA (AT&T@Home) Cable Modem
Date: Wed, 09 May 2001 19:53:30 GMT
Wouldnt You Like to Know wrote:
>
> I have seen several somewhat condensed articles on getting AT&T@Home
> cable modems to run with Red Hat Linux, but nothing has been very
> comprehensive. It also seems the configuration may be different based
> on the geography you are in. I happen to be in the Chicagoland
> (western suburbs) area.
>
AFAIK, AT&T@Home uses standard DHCP. The twist is that you do need to
specify the "DHCP hostname" in your request. Red Hat's GUI tools don't
provide a way to do this, but you can edit the network configuration
script for the appropriate interface (probably
/etc/sysconfig/network-scripts/ifcfg-eth0) and add a line which reads
"DHCP_HOSTNAME=<name>", where <name> is the computer name you were
assigned.
--
========================================================================
Ian Pilcher [EMAIL PROTECTED]
========================================================================
------------------------------
From: "Martin Greco" <[EMAIL PROTECTED]>
Subject: user mount
Date: Wed, 9 May 2001 16:13:12 -0300
Hi.
I tried to set the "user" swith in the fstab file in some devices as said in
the mount man pages, but I still can't mount them with user accounts.
any suggestions?
--
-
Martin Greco
Soporte Residencial - int. 2001
Sinectis Rosario - Rioja 1659
Tel: 0810-999-0700
------------------------------
From: "Brian Wildasinn" <[EMAIL PROTECTED]>
Subject: Re: ...dup2: Bad file descriptor [FAILED] .../dev/null: Read-only file system
Date: Wed, 9 May 2001 12:27:58 -0700
Here's what my /etc/mtab & /etc/fstab say:
/etc/mtab:
/dev/hda1 / ext2 rw 0 0
none /dev/pts devpts rwgid=5,mode=620 0 0
none /proc proc rw 0 0
/etc/fstab:
/dev/hda1 / ext2 defaults
1 1
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy_msdos msdos noauto,owner,rw 0 0
/dev/fd0 /mnt/floppy_unix ext2 noauto,owner,rw 0 0
/proc /proc proc defaults
0 0
Any help is appreciated!
Brian
"Brian Wildasinn" <[EMAIL PROTECTED]> wrote in message
news:9dc66r$bud$[EMAIL PROTECTED]...
> Remounting read-write the root file system, the /proc filesystem is able
to
> be mounted.
> However, upon rebooting the proc file system is added to /etc/mtab as
>
> none /proc /proc
>
------------------------------
From: [EMAIL PROTECTED] (Kenny McCormack)
Crossposted-To: comp.os.linux.misc
Subject: GRUB really is better than LILO! (Was: Re: GRUB: How to install to hard disk
(without installing Linux) ?)
Date: 9 May 2001 15:00:44 -0500
Reply-To: [EMAIL PROTECTED]
In article <9db0dn$mbk$[EMAIL PROTECTED]>,
Kenny McCormack <[EMAIL PROTECTED]> wrote:
>In article <[EMAIL PROTECTED]>,
>Frank Ranner <[EMAIL PROTECTED]> wrote:
>...
>>> And, to get to the real point, can I create a small ext2fs partition on the
>>> disk, and put the stuff from the floppy there (doing all this from a Linux
>>> boot/rescue floppy) - without installing Linux on the machine - and have
>>> GRUB find the stuff there and work (w/o the floppy being present) ?
>
>>you can have grub on a fat disk, in \boot\grub
>>From memory you point to it using
>>root (hd0,0)
>>setup (hd0)
>
>Glad to hear it. I'll give it a shot.
Worked a treat. No need to install Linux or any EXT2FS file systems. I
highly reccomment this to anyone having troubles with LILO.
One thing about it, though, that I found "hinkey". You have to copy the
contents of the /boot/grub directory from the floppy to /boot/grub on the
(FAT) hard disk. This works just fine, but the funny things is this: You
can put it into /grub instead and the installer will find it (You can tell
from the error messages that it looks in both dirs), but the glitch is that
it won't fine the "menu.lst" file in /grub - that *has* to be in /boot/grub.
That's what I find weird - that it lets you install from /grub, but silently
ignores the "menu.lst" file if you do.
------------------------------
** 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
******************************
