Linux-Setup Digest #384, Volume #20 Tue, 9 Jan 01 15:13:09 EST
Contents:
kernel-2.4.0 on Linux-Mandrake 7.2 (Filippo Palombi)
Re: HELP! : mysterious ext2 undeletable directory (Thaddeus L Olczyk)
Can't print under RH7, could under RH6.2 (Mike Percy)
Re: can't execute an executable file..... (James Rose)
Re: USR 56k modem setup (Dave Barnett)
2.4 and mountd,nfsd RPC timeout (Brandon)
Re: clock problem (paul marwick)
Re: physical disks (Dave Barnett)
Re: lilo for secondary IDE ("Hung P. Tran")
Re: physical disks (H.Bruijn)
Re: help: getting modem to work ([EMAIL PROTECTED])
Re: startx doesn't start X (Bill Unruh)
Re: startx doesn't start X (Bill Unruh)
Re: Genius GE2500III SE network card (M. Buchenrieder)
hlt vs. idle (Manni Heumann)
----------------------------------------------------------------------------
From: Filippo Palombi <[EMAIL PROTECTED]>
Subject: kernel-2.4.0 on Linux-Mandrake 7.2
Date: Tue, 9 Jan 2001 19:27:44 +0100
Dear all,
I tried to install kernel 2.4.0 on Linux Mandrake 7.2. I have an Athlon
Thunderbird 800Mhz, and I have specified the processor in the menuconfig.
When I give the make command, I get
============================================================================
scripts/split-include include/linux/autoconf.h include/config
gcc -D__KERNEL__ -I/home/filippo/linux/include -Wall -Wstrict-prototypes
-O2 -fomit-fram
e-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
-march=i686 -malign-fu
nctions=4 -c -o init/main.o init/main.c
In file included from /home/filippo/linux/include/linux/irq.h:57,
from /home/filippo/linux/include/asm/hardirq.h:6,
from /home/filippo/linux/include/linux/interrupt.h:45,
from /home/filippo/linux/include/asm/string.h:296,
from /home/filippo/linux/include/linux/string.h:21,
from /home/filippo/linux/include/linux/fs.h:23,
from /home/filippo/linux/include/linux/capability.h:17,
from /home/filippo/linux/include/linux/binfmts.h:5,
from /home/filippo/linux/include/linux/sched.h:9,
from /home/filippo/linux/include/linux/mm.h:4,
from /home/filippo/linux/include/linux/slab.h:14,
from /home/filippo/linux/include/linux/malloc.h:4,
from /home/filippo/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/home/filippo/linux/include/asm/hw_irq.h: In function `x86_do_profile':
/home/filippo/linux/include/asm/hw_irq.h:198: `current' undeclared (first
use in this fu
nction)
/home/filippo/linux/include/asm/hw_irq.h:198: (Each undeclared identifier
is reported on
ly once
/home/filippo/linux/include/asm/hw_irq.h:198: for each function it appears
in.)
In file included from /home/filippo/linux/include/asm/string.h:296,
from /home/filippo/linux/include/linux/string.h:21,
from /home/filippo/linux/include/linux/fs.h:23,
from /home/filippo/linux/include/linux/capability.h:17,
from /home/filippo/linux/include/linux/binfmts.h:5,
from /home/filippo/linux/include/linux/sched.h:9,
from /home/filippo/linux/include/linux/mm.h:4,
from /home/filippo/linux/include/linux/slab.h:14,
from /home/filippo/linux/include/linux/malloc.h:4,
from /home/filippo/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/home/filippo/linux/include/linux/interrupt.h: In function `raise_softirq':
/home/filippo/linux/include/linux/interrupt.h:89: `current' undeclared
(first use in thi
s function)
/home/filippo/linux/include/linux/interrupt.h: In function
`tasklet_schedule':
/home/filippo/linux/include/linux/interrupt.h:160: `current' undeclared
(first use in th
is function)
/home/filippo/linux/include/linux/interrupt.h: In function
`tasklet_hi_schedule':
/home/filippo/linux/include/linux/interrupt.h:174: `current' undeclared
(first use in th
is function)
In file included from /home/filippo/linux/include/linux/string.h:21,
from /home/filippo/linux/include/linux/fs.h:23,
from /home/filippo/linux/include/linux/capability.h:17,
from /home/filippo/linux/include/linux/binfmts.h:5,
from /home/filippo/linux/include/linux/sched.h:9,
from /home/filippo/linux/include/linux/mm.h:4,
from /home/filippo/linux/include/linux/slab.h:14,
from /home/filippo/linux/include/linux/malloc.h:4,
from /home/filippo/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/home/filippo/linux/include/asm/string.h: In function `__constant_memcpy3d':
/home/filippo/linux/include/asm/string.h:305: `current' undeclared (first
use in this fu
nction)
/home/filippo/linux/include/asm/string.h: In function `__memcpy3d':
/home/filippo/linux/include/asm/string.h:312: `current' undeclared (first
use in this fu
nction)
make: *** [init/main.o] Error 1
================================================================================
Can anyone tell me what's the problem and how can I overcome it ?
thanks.
--
Filippo
------------------------------
From: [EMAIL PROTECTED] (Thaddeus L Olczyk)
Crossposted-To: comp.os.linux.misc
Subject: Re: HELP! : mysterious ext2 undeletable directory
Date: Tue, 09 Jan 2001 18:28:34 GMT
Reply-To: [EMAIL PROTECTED]
On Tue, 09 Jan 2001 14:38:48 GMT, Dorin Ioan MARINCA
<[EMAIL PROTECTED]> wrote:
>Hi!
>
>I need help for the following problem:
>
>Context: RH 6.2 original kernel
>First symptom: ext2 root filesystem full.
>I have searched for a big file (+10M).
>Result: a (mysterious) junkbuster (web browsing filter) log directory:
>/var/log/junkbuster : size +11M
>'drwxr--r-- 2 73 73 11067392 Jan 8 14:04 junkbuster'
>the directory and not the contents!!!
>a 'ls' inside blocks...
>a '# rm -rf /var/log/junkbuster' run in a infinite loop.
>
>How can I remove this file?
>
>I have tried (forced) fsck without results. No bad blocks also...
>
>Thanks for any sugestions...
>
>d.i.m.
Something similar happened to me recently. I supect that you have
misdiagnosed the problem. BTW junkbuster is a http proxy that filters
cookies banner ads etc. I dont think that is your problem.
Try find . -name"*" that probably blocks too.
Try find . -name "*.gz" lots of junk looks like
xxx.1.gz.3.gz.2.gz.5.gz etc.
BTW does df tell you the file system is full, or is that simply a
system error.
If df tells you that a file system is not full and you get full errors
that tells you that you are running out of inodes ( exceeding the max
number of files permited on a partition ).
The way to fix this is pick some filename that appears in find . -name
"*.gz" for example mail/mail_errors.1.gz.2.gz.3.gz
and do:
find . -name "mail/mail_errors*"|xargs rm -f
go over several different files like this
( you can actually start several such command in different terminal
windows ). After a while, you should be able to do
find . -name "*.gz"|xargs rm -f
It should take a while.
After you are done get an upgraded version of logrotate.
A bug in it is what caused your problem.
------------------------------
From: Mike Percy <[EMAIL PROTECTED]>
Subject: Can't print under RH7, could under RH6.2
Date: Tue, 09 Jan 2001 15:13:15 -0500
Reply-To: [EMAIL PROTECTED]
Stupid me, I upgraded from 6.2 to 7.0 and can't get my remote printer setup. I
have a HP4 with jetdirect card, to which I was able to print, no problems, with
following printcap entry:
lp:\
:sd=/var/spool/lpd/lp:\
:mx#0:\
:sh:\
:rm=hp4:\
:rp=raw:\
:if=/var/spool/lpd/lp/filter:
along with correct entry in /etc/hosts.
Now, despite trying all afternoon, I can't get it setup correctly. I can print
to printer from other boxes, and can ping from the new RH7 box. So I know the
problem must be in printcap setup or lpd.
lpc>status
Printer Printing Spooling Jobs Server Subserver Redirect
Status/(Debug)
lp@grimlok@2-tigers enabled enabled 0 none none
lpc>
When I print test pages, etc., they seem to spool OK, but never show up in the
spool directory, nor on the queue, and certainly don't get to the printer.
Any help?
=========== Minimal anti=spam measure: remove _nospam to reply ===========
"Each game of chess means there's one less variation left to be played.
Each day got through means one or two less mistakes remain to be made."
Seen on the net: "Microsoft is to computers as McDonalds is to food"
------------------------------
From: [EMAIL PROTECTED] (James Rose)
Subject: Re: can't execute an executable file.....
Date: Tue, 09 Jan 2001 18:32:13 GMT
>>your path. That is where bash and others look for commands. Type
>>/a.out and see what happens.
>
>Make that
> ./a.out
>
Oops. Yeah that would be what I MEANT to type.
------------------------------
From: Dave Barnett <[EMAIL PROTECTED]>
Subject: Re: USR 56k modem setup
Date: Tue, 09 Jan 2001 12:50:43 -0600
Reply-To: [EMAIL PROTECTED]
Bruce:
Not sure about the USR internal modem, but for the external modem, you
have to do some configuration.
On USR's site, they have instructions for configuring the modem for use
with a unix system.
HTH.
Cheers,
Dave
--
Dave Barnett System Software Engineer x1434
"If a person with multiple personalities threatens suicide, is that
considered a hostage situation?"
- George Carlin
------------------------------
From: Brandon <[EMAIL PROTECTED]>
Subject: 2.4 and mountd,nfsd RPC timeout
Date: Tue, 09 Jan 2001 13:52:16 -0500
Hi there,
I just compiled kernel 2.4 on my slack 7 machine, and suddenly mountd
and nfsd fail on startup. The exact messages are both: "Cannot register
service: RPC: Timed out" Now, I don't use NFS, and I think both of
those daemons are only important to NFS, so I suppose with some
tinkering I could figure out how to remove them, but I'd really like to
know what caused the problem. Did I not include something in the kernel
build, or are the daemons imcompatible with 2.4?
On a related note, my video driver (nvidia's NVdriver, patched and
recompiled for 2.4) suddenly ceased to work after the upgrade too,
needing dependencies: __vmalloc, irq_stat, and a couple others.
Thanks,
Brandon
------------------------------
From: [EMAIL PROTECTED] (paul marwick)
Subject: Re: clock problem
Date: Tue, 09 Jan 2001 19:01:03 -0000
On Mon, 8 Jan 2001 20:28:08 +0100, Marc Balsys <[EMAIL PROTECTED]> wrote:
> i have a problem with my system clock. after using linix my system clock is
> not correct any more.
> e.g. december 26 10 oclock
It sounds as though you've set Linux to use the hardware clock during
install.
paul
--
paul marwick - Chipping Norton, Oxfordshire, UK
remove the numbers for e-mail
---
------------------------------
From: Dave Barnett <[EMAIL PROTECTED]>
Subject: Re: physical disks
Date: Tue, 09 Jan 2001 13:03:15 -0600
As root, type "fdisk -l" (without the quotes). You'll get a listing of
all your drives, and the partition tables they have.
--
Dave Barnett System Software Engineer x1434
I tried sniffing coke once, but the ice cubes got stuck in my nose.
------------------------------
From: "Hung P. Tran" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.system,comp.os.linux.misc
Subject: Re: lilo for secondary IDE
Date: Tue, 09 Jan 2001 19:15:05 GMT
Thank you to all those response especially Dave for all the
helpful info. For everyone info, I did run lilo after modify lilo.conf
(please note that I got an "L" upon attemping reboot). I did
also verify that my BIOS can boot from a secondary IDE drive (with
DOS). However, I have to add:
disk = /dev/hdc
bios = 0x80
as Dave recommended to get my secondary IDE to boot linux.
Thanks again to all who response,
hung
Dave Platt wrote:
> >> I am trying to make a boot hard drive to boot from a
> >> secondary IDE. My lilo.conf is as followed:
> >>
> >> #boot=/dev/fd0
> >> boot=/dev/hdc
>
> #snip
>
> >> The same lilo.conf will not work. All I get is an "L" and then
> >> a bunch of 01 dump onto the screen. I also try to use "linear"
> >> to no avail. Any advice.
> >>
> >
> >Did you rerun lilo after changing that parameter? You have
> >to install lilo in the MBR of hdc. Also, lilo creates the
> >map file and install it.
>
> A normal PC BIOS will boot only from the MBR of the primary hard
> drive. It won't even "look" for the secondary hard drive MBR. The
> normal way to boot a Linux system from a secondary hard drive is to
> put LILO in the MBR of the primary hard drive (or put the standard MBR
> there, and put LILO in the boot block of the active partition on the
> primary hard drive). You can have the kernel itself, and the root
> filesystem on the secondary hard drive, but the MBR and active active
> partition normally need to be on the primary drive.
>
> There are some BIOSes which can be configured to boot from the
> secondary hard drive. There's a gotcha to enabling this feature,
> though. Most disk-resident MBR and bootloader code isn't written to
> be booted from a secondary drive (it "assumes" that the system is on
> the primary drive). In order to cope with this lacking, the BIOS
> doesn't just load the MBR etc. from the secondary drive - it actually
> *swaps* the two drives at the BIOS level.
>
> In a standard system, the first bootable disk (typically the master on
> the IDE primary controller) is referred to as device 0x80 in the I/O
> calls to the BIOS. The second drive is 0x81, and so forth.
>
> If you tell your BIOS to swap controllers, it actually assigns device
> ID 0x80 to the master drive on the secondary controller. Thus, when a
> standard MBR is loaded from this drive and executed, it "thinks" that
> it's really on the primary drive, and has no difficulty reading the
> partition table and the O/S boot blocks. A similar thing occurs if
> you have a SCSI controller, and tell your BIOS to "boot SCSI" - the
> 0x80 drive ID is assigned to the first disk device on the first SCSI
> controller, rather than to the IDE primary master.
>
> When /sbin/lilo is run to install LILO, it has to write information
> into the MBR-resident portion of LILO, and into its own boot catalog,
> which tells the boot code where to find each portion of the code being
> booted. It must figure out which BIOS disk identifier is used for
> each drive, and identify the location of each bootable bit of code by
> (drive ID, location, size).
>
> The /sbin/lilo installer normally honors the standard BIOS
> conventions... IDE primary master, IDE primary slave, IDE secondary,
> SCSI, in that order. This works just fine for a standard setup. It
> will NOT work if you've told your BIOS to swap drives or controllers
> around, because the BIOS ordering will disagree with the ordering that
> the LILO installer assumed.
>
> The net result will be the sort of thing you're observing... the first
> (MBR-resident) portion of LILO will load, but the subsequent sections
> won't load properly, because the MBR-resident portions of LILO will be
> using the wrong device IDs.
>
> The way around this problem is to use _explicit_ device IDs in your
> /etc/lilo.conf file. Figure out what device IDs your BIOS is going to
> assign at boot time, and then tell LILO to use precisely these IDs.
>
> As an example: I have a system with two IDE hard drives, and one IDE
> hard drive. In a standard setup, the IDE drive would be 0x80, and the
> two SCSI drives would be 0x81 and 0x82. However, I've told my BIOS
> that I want to boot from SCSI (the IDE drive is strictly for bulk
> storage), and so it reorganizes the drive IDs (SCSI first, IDE
> second). In my lilo.conf file, I say:
>
> #
> # LILO is installed in the boot sector of the extended partition at
> # /dev/sda2. The disk's MBR is standard.
> #
> disk = /dev/sda
> bios = 0x80
> disk = /dev/sdb
> bios = 0x81
> disk = /dev/hda
> bios = 0x82
> boot = /dev/sda2
> install = /boot/boot.b
> delay = 50
>
> and so forth. This gives LILO the information it needs to build the
> boot-map files with the correct drive IDs, and the system boots up from
> the SCSI drives just fine.
>
> I suspect that you may need to do something similar. If you're
> telling your BIOS to boot from the secondary controller, you'll need to
> say something like:
>
> disk = /dev/hda
> bios = 0x81
> disk = /dev/hdc
> bios = 0x80
>
> to swap around the BIOS drive IDs for the drives on these two
> controllers.
>
> --
> Dave Platt [EMAIL PROTECTED]
> Visit the Jade Warrior home page: http://www.radagast.org/jade-warrior/
> I do _not_ wish to receive unsolicited commercial email, and I will
> boycott any company which has the gall to send me such ads!
------------------------------
From: [EMAIL PROTECTED] (H.Bruijn)
Subject: Re: physical disks
Date: 9 Jan 2001 19:19:46 GMT
Reply-To: [EMAIL PROTECTED]
On 9 Jan 2001 13:56:20 GMT, Me allegedly wrote:
>Is it /etc/fstab where I learn about what physical hard disks I have? Where
>can I learn more about this?
/etc/fstab contains the partition information you put in, as in which
disc is mounted where. For the information regarding the /etc/fstab
file look at "man fstab" and "man mount".
dmesg
most likely gives a list of devices detected at boot,
/sbin/fdisk -l /dev/hda
gives the partitioning of the disc /dev/hda
/sbin/hdparm -i /dev/hda
gives as list with the hardware settings and info of the device hda.
--
If a trainstation is the place where trains stop, what is a workstation?
========================================================================
Herman Bruijn mail: [EMAIL PROTECTED]
The Netherlands website: http://hermanbruijn.com
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: alt.linux,alt.os.linux,aus.computers.linux
Subject: Re: help: getting modem to work
Date: Tue, 09 Jan 2001 19:05:49 GMT
In article <[EMAIL PROTECTED]>,
goble@gtech wrote:
> Hi All;
>
> Iam running RedHat 6.2. Iam trying to follow the how-to to connect to
> the internet.
>
> My modem is on com3 (/dev/ttyS2), but it seems not to work.
>
> Here is what I have;
>
> >/etc/syslog.conf
> >local2.* /var/log/ppp
> >daemon.* /var/log/ppp
>
> killall -1 syslogd
>
> >/etc/resolv.conf
> nameserver 127.0.0.1
> nameserver 230.48.5.1
>
> >/etc/host.conf
> order hosts, bind
> >chmod a+r /etc/resolv.conf /etc/host.conf
>
> >/usr/sbin/pppd
> I get a line of garbage which repeats about 10 times and then the
> command exits.
>
> >/etc/ppp/options
> lock
> crtscts
> defaultroute
>
> chmod a+rwx /dev/ttyS2
>
> /usr/sbin/pppd /dev/ttyS2 57600 debug user username connect
> "/usr/sbin/chat -v '' AT OK ATDT85534300 CONNECT '\d\c'"
>
> Jan 6 18:29:15 gtech pppd[798]: pppd 2.3.11 started by root, uid 0
> Jan 6 18:29:16 gtech chat[799]: send (AT^M)
> Jan 6 18:29:16 gtech chat[799]: expect (OK)
> Jan 6 18:29:35 gtech chat[799]: ^M
> Jan 6 18:30:01 gtech chat[799]: alarm
> Jan 6 18:30:01 gtech chat[799]: Failed
> Jan 6 18:30:01 gtech pppd[798]: Connect script failed
> Jan 6 18:30:02 gtech pppd[798]: Exit.
>
>
If you are sure your modem can work with linux then this is a way that
should get your modem initialized.
1) logon as root, and at the command prompt type: cat /proc/pci
2)Scroll down until you find the data for the serial controller. it
will probably look like this
/*
Bus 0, device 15, function 0:
Serial controller: Unknown vendor Unknown device (rev1).
Vendor id=12b9. Device id=1008
Medium devsel. IRQ 10.
I/O at 0x1890 [0x1891].
*/
3) Make a note of the values for IRQ and I/O port (use the number not
in the brackets). For instance it would be 10 and 0x1890.
4) Then at the command prompt type
setserial /dev/ttyS# irq 10 port 0x1890 autoconfig
# = what ever port you are using
5) Then at the command prompt type ln -s /dev/ttyS# /dev/modem
6) now use minicom - easy to get to from the GUI
programs->internet->minicom
7) minicom should initialize the modem and will say "OK"
8) next configure your modem and interne settings..make sure to use the
same port ttyS#.
9) if this works, then you want to write steps 4 and 5 in rc.local so
that the modem is initialized automatically everytime you reboot or
else you will need to do this set of steps manually each time.
10) also while in minicom if you type ATI3 you see the type of modem
you have displayed on the screen.
I hope this helps.
Sean
Sent via Deja.com
http://www.deja.com/
------------------------------
From: [EMAIL PROTECTED] (Bill Unruh)
Subject: Re: startx doesn't start X
Date: 9 Jan 2001 19:29:16 GMT
In <[EMAIL PROTECTED]> "Robert Lock" <[EMAIL PROTECTED]> writes:
]After months of relatively painless use of Mandrake 7.0, the following has
]occurred:
]type "startx" <cr>
]Screen blanks out for approx 20 sec and then returns this -
]_FontTransSocketUNIXConnect. Can't connect: errno = 111
]Failed to set default font path 'unix/:1'
]Fatal server error:
]could not open default font 'fixed'
]X connection to :0.0 broken (explicit kill or server shutdown).
the xfs daemon probably is not running
/etc/rc.d/xfs restart
------------------------------
From: [EMAIL PROTECTED] (Bill Unruh)
Subject: Re: startx doesn't start X
Date: 9 Jan 2001 19:36:22 GMT
In <[EMAIL PROTECTED]> "Robert Lock" <[EMAIL PROTECTED]> writes:
>typing "df" returns
> Available use mounted on
>/dev/hda1 0 100% /
Yup your problem. Erase stuff in / to make room.
A number of possibilities-- you have some file in /var/log or /var/log/*
which is HUGE. get rid of it. (first try to see why it is so huge)
There is some other huge file in there somewhere.
du -x /var
will list the sizes of all files in /var
du -x /
will list the sizes of all files on the / partition.
>/dev/hda1 * 1 102 205600+ 83 linux
Should be enough room for a / partition.
>Question1: What is the recommended way of dealing with this situation?
ERase the problem files.
>Question 2: How do I prevent this from recurring?
Find out why some file is filling up and correct the problem.
------------------------------
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: Genius GE2500III SE network card
Date: Tue, 9 Jan 2001 14:07:24 GMT
Martin =?iso-8859-1?Q?W=FCrthner?= <[EMAIL PROTECTED]> writes:
>I am running SuSE 6.4 with kernel 2.2.16 and I have a Genius PCI ehternet
>card: GE2500III SE. Under Windows, this is installed as a Realtek RTL
>8029(AS) card and works fine.
And that's it. A standard RTL8029 clone.
[...]
>Jan 9 13:43:19 escher kernel: WARNING: The PCI BIOS assigned this PCI
>NE2k card to IRQ 0, which is unlikely to work!.
[...]
Yawn. A quick check with http://www.deja.com/home_ps.shtml
would have given you the answer in seconds.
>Jan 9 13:43:19 escher kernel: You should use the PCI BIOS setup to assign
>a valid IRQ line.
[...]
And that's the solution. Set the BIOS option "PNP-OS" to "No".
You're running a system with one of the common (but nonetheless
broken) implementations where PNP-OS means that the BIOS won't
touch the PCI cards at all - which is just plain stupid.
Michael
--
Michael Buchenrieder * [EMAIL PROTECTED] * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
------------------------------
From: [EMAIL PROTECTED] (Manni Heumann)
Subject: hlt vs. idle
Date: 9 Jan 2001 19:59:35 GMT
Hi,
while playing aroung with my new 2.4 kernel and lmsensors, I
asked myself whether there was anything I could do to keep my
power eating processor from frying. Configuring the kernel, I
found to options, and I don't know which one I need, or whether
they are even identical:
There is an option to make idle calls to the processor while
idle.
And there is the option to send the hlt instruction.
Can anybody tell me what the difference is? Which one is the
magic power saving function?
TIA,
Manni
------------------------------
** 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
******************************
