Linux-Development-Sys Digest #392, Volume #8 Fri, 5 Jan 01 18:13:19 EST
Contents:
Re: Kernel Non-boot ("mpierce")
Re: Doing Trans-Proxy for UDP services - how to use MSG_PROXY? (Andi Kleen)
Re: IPChains incompatible with Kernel 2.4.0-test12 (Andi Kleen)
Re: Kernel Non-boot (Anders Larsen)
Re: Moving processes (Robert Hofner)
Re: removing mouse causes Linux to crash/hang. kernel 2.4 (Kasper Dupont)
Re: ioperm() (Kasper Dupont)
Assigning signals to IRQs ([EMAIL PROTECTED])
ISA/PCI resource management (Max Ischenko)
Re: ISA/PCI resource management (Kasper Dupont)
Re: two mice on a linux box (Kasper Dupont)
raw datas on serial port (Ionel GARDAIS)
Re: raw datas on serial port (Grant Edwards)
Re: raw datas on serial port (Kasper Dupont)
Re: ISA/PCI resource management (Max Ischenko)
Re: Kernel 2.4 (Markus Kossmann)
Re: ioperm() (Jonathan Buzzard)
kernel 2.4.0 + RAID causes problems ("Oliver Kowalke")
Re: mounting floppy ("Hung P. Tran")
Re: ioperm() (Kaz Kylheku)
Re: Kernel Non-boot ("mpierce")
Re: mounting floppy ([EMAIL PROTECTED])
Generating core file ("Gene Chang")
Re: mounting floppy ("Peter T. Breuer")
Yamaha CDRW 4416E (Rob King)
----------------------------------------------------------------------------
From: "mpierce" <[EMAIL PROTECTED]>
Subject: Re: Kernel Non-boot
Reply-To: [EMAIL PROTECTED]
Date: Fri, 05 Jan 2001 11:23:38 GMT
Paul,
Thanks for replying.
I do:
1) make xconfig
2) make dep && make clean && make bzImage
3) make modules && make modules_install
Make runs flawlessly for everything - no errors reported;
no unresolved dependencies
(cd /lib/modules - everything there; cd /usr/src/linux)
4) cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.0-test12
5) cp System.map /boot/System.map-2.4.0-test12
6) depmod -a
7) cd /boot
8) rm System.map
9) ln -s System.map-2.4.0-test System.map; ln -s vmlinuz-2.4.0-test
vmlinuz
10) vi /etc/lilo.conf & vi /boot/grup/menu.lst with appropriate entry to
boot kernel (I actually yank default linux and modify it for each file)
11) /sbin/lilo & sh /boot/grub/install.sh (I do grub last so it is default
loader)
12) reboot
I've repeated this at least 7 or 8 times; kernel starts out as follows:
Uncompressing linux...
OK, booting the kernel
System froze at this point
I cannot figure this out and I've tried kernel 2.4.0-test9; no problems
compiling 2.2.18 (but this doesn't have USB support which is what I need).
Marvin
--
In article <r7n139.r9h.ln@jefe>, "Paul Sackun" <[EMAIL PROTECTED]>
wrote:
> In article <MzS46.44119$[EMAIL PROTECTED]>, mpierce
> wrote:
>>Mandrake 7.2, kernel 2.2.17-21
>>
>>Compiled new kernel-2.4.0-test12 Compiled & install modules - no runs,
>>no drips, no errors. Mv bzImage to vmlinuz-2.4.0-test12 to make a boot
>>disk
>
> I think the problem might be in the last step. Please describe what you
> mean by
> "Mv bzImage to vmlinuz-2.4.0-test12 to make a boot disk" and I might be
> able to help. Did you rerun lilo? Copy System.map to the right place??
>
>
------------------------------
From: Andi Kleen <[EMAIL PROTECTED]>
Subject: Re: Doing Trans-Proxy for UDP services - how to use MSG_PROXY?
Date: 05 Jan 2001 13:05:34 +0100
Charles Reindorf <[EMAIL PROTECTED]> writes:
> Whilst I think I have half of a clue as to how to do it, based on what I
> saw, it would be nice to track down some notes / documentation /
> previous code that also uses this feature. I wonder if anyone can help.
It will not be documented, because 2.4 dropped that interface.
-Andi
------------------------------
From: Andi Kleen <[EMAIL PROTECTED]>
Subject: Re: IPChains incompatible with Kernel 2.4.0-test12
Date: 05 Jan 2001 13:18:11 +0100
"Markus Spiritus Familiaris" <[EMAIL PROTECTED]> writes:
> Hi!
> I just installed the new hackerkernel 2.4.0-test12 on my linux box
> i achieved to compile and everything, machine boots up.
>
> but there's a problem:
> kernel gives out the following:
> "IPCHains FAILED: Incompatible with this kernel: Protocol not available"
> I have turned on the options required for NAT/IPCHAINS in the kernel
> compilation questions, but it still doesnt work;
> i dont know why.
> hm.
> i have SuSE 6.3 installed on my box. With the standard kernel supplied with
> this package (i think its 2.2.13 or so) masquerading works.
> I
>
>
> Help would be very appreciated.
It looks like you didn't enable the ipchains compat layer.
You need to turn on the ipchains compatibility in the kernel, or make sure
to load the module.
-Andi
------------------------------
From: Anders Larsen <[EMAIL PROTECTED]>
Subject: Re: Kernel Non-boot
Date: Fri, 05 Jan 2001 13:35:45 +0100
mpierce wrote:
>
[snip]
> I cannot figure this out and I've tried kernel 2.4.0-test9; no problems
> compiling 2.2.18 (but this doesn't have USB support which is what I need).
> Marvin
Huh?
2.2.18 *does* have USB support (2.2.17 and below didn't)!
I admit I haven't tried it yet, though (due to lack of USB devices).
cheers
Anders
------------------------------
From: Robert Hofner <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.networking,comp.unix.programmer
Subject: Re: Moving processes
Date: Thu, 04 Jan 2001 18:34:05 +0200
Look at the Mosix project.
Robert
"Derek M. Flynn" wrote:
> frederik wrote:
>
> > I am currently working on an implementation of a Mobile Agent platform. The
> > agents run in different processes on several host machines in a network.
> > The agents and thus the processes have to be movable from one host to
> > another for load balancing purposes.
> > Does anybody know wether it is possible to capture the state of a running
> > process, transfer it to another host and restarting it on the other machine
> > in the same state as it left the first one
>
> Look at the work being done by the Condor project at:
>
> http://www.cs.wisc.edu/condor/
>
> In addition, they wrote an article that you might try to find:
>
> "Checkpointing and Migration of UNIX Processes in the Condor Distributed
> Processing System" Dr Dobbs Journal, February 1995
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: removing mouse causes Linux to crash/hang. kernel 2.4
Date: Fri, 05 Jan 2001 14:15:38 +0000
Robert Redelmeier wrote:
>
> Kasper Dupont wrote:
> > found that the keyboard driver used under
> > DOS detects the keyboard being pluged in
> > makes a beep and updates the keyboards
> > state.
> >
> > But if this should not be possible why is
> > it that DOS supports it?
>
> Just because something isn't recommended doesn't
> mean that MS-DOS won't do it :)
>
> Actually, I doubt DOS has anything to do with it,
> the beep is more probably in your machine's BIOS.
>
> The kbd controller probably generates some spurious
> int 9's when [dis]connected. Your mobo has BIOS code
> to detect and reinitialize the kbd. It may even have
> "self-healing" fuses. But Linux replaces all
> of BIOS and doesn't have this re-init code.
>
> -- Robert
I have just verified, the beep and the reinitializing
of the keryboard is done by DOS not by the BIOS. Int
9 is also completely replaced by the DOS keyboard
driver.
The DOS keyboard driver is optional the BIOS keyboard
driver can be used as well, but the DOS driver has
some additional features.
This particular feature could also be implemented in
Linux, which I think would be a good idea.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: ioperm()
Date: Fri, 05 Jan 2001 14:28:09 +0000
[EMAIL PROTECTED] wrote:
>
> Hi,
>
> I'm trying to develop a little program to manage the serial port and a
> digital I/O module but I get a SIGSEGV error message. The I/O module is
> located at the addresses 200H-203H, and the code of the program is:
>
> #include <sys/io.h>
>
> main(){
> int i = ioperm(0x200,4,1);
> outb(0x202,0x36);
> }
>
> Could anybody tell me what is happening? Thanks in advance.
>
> Jose Luis Ayala
>
> Sent via Deja.com
> http://www.deja.com/
Many people have made that mistake, the order of the
arguments to outb is incorrect. It should read:
outb(0x36,0x202);
--
Kasper Dupont
------------------------------
From: [EMAIL PROTECTED]
Subject: Assigning signals to IRQs
Date: Fri, 05 Jan 2001 14:31:02 GMT
Hi,
I am trying to develop a program (a user-mode process, not a kernel
driver) that works with ports. May I assign a signal (like SIGALRM or
another one) to the interrupt of the serial port (IRQ4)? I think it is
possible if this were a kernel driver, but I'm not sure with a user-mode
process.
Thanks in advance.
Jose Luis Ayala
Sent via Deja.com
http://www.deja.com/
------------------------------
From: Max Ischenko <[EMAIL PROTECTED]>
Subject: ISA/PCI resource management
Date: 5 Jan 2001 16:56:18 +0200
Hi there.
I've heard that Linux 2.4 has much imporoved resource management facilities.
I've searched Documentation but didn't find anything.
What I look for is how to query the kernel what hardware is present on the
system.
--
..you could spend *all day* customizing the title bar. Believe me. I
speak from experience."
(By Matt Welsh)
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: ISA/PCI resource management
Date: Fri, 05 Jan 2001 15:59:41 +0000
Max Ischenko wrote:
>
> Hi there.
>
> I've heard that Linux 2.4 has much imporoved resource management facilities.
> I've searched Documentation but didn't find anything.
>
> What I look for is how to query the kernel what hardware is present on the
> system.
>
> --
> ..you could spend *all day* customizing the title bar. Believe me. I
> speak from experience."
> (By Matt Welsh)
The program can get a lot of information by reading
/proc/pci or /proc/bus/pci.
--
Kasper Dupont
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: two mice on a linux box
Date: Fri, 05 Jan 2001 15:54:58 +0000
David Baldwin wrote:
>
> Hi there, has anyone ever tried running two mice on a linux box at once?
> I'm not worried about pointers on the screen, just as long as I can pick up
> the input from the second device in my program.
> (I've been trying to do this on mac but without any success so far)
>
> I'm a complete newbie to linux apart from a bit of telnet, but willing to
> learn if it means I can get this done!
>
> if anyone's got any advice/files or urls that'd be fantastic!
> thanks
> dave
Having two different programs using two different mice
is not different from the usual ways of acessing mice.
Normally there are two programs using the mouse, gpm
and X. Gpm is used in textmode on the virtual consoles.
Each of the two programs has a configuration file
specifying which mouse is to be used.
The documentation for gpm should help you understand
the concepts. Looking on the sourcecode should explain
the more technical aspects, I haven't seen the source
so I don't know how complicated it is.
--
Kasper Dupont
------------------------------
From: Ionel GARDAIS <[EMAIL PROTECTED]>
Subject: raw datas on serial port
Date: Fri, 05 Jan 2001 17:12:02 +0100
Reply-To: [EMAIL PROTECTED]
Hi,
How to write raw datas to the serial port ?
Does the MS-DOS ASM functions works ?
thx,
ioio
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: raw datas on serial port
Date: Fri, 05 Jan 2001 16:16:02 GMT
In article <[EMAIL PROTECTED]>, Ionel GARDAIS wrote:
>How to write raw datas to the serial port ?
You use write().
The normal open(), read(), write() calls work on serial devices
("/dev/ttyS0" for example). Use tcXXXX() calls to configure
the device.
$ man termios
Also read the Serial-Programming-HOWTO:
http://www.linuxdoc.org/HOWTO/Serial-Programming-HOWTO.html
>Does the MS-DOS ASM functions works ?
No.
--
Grant Edwards grante Yow! This ASEXUAL
at PIG really BOILS
visi.com my BLOOD... He's
so... so... URGENT!!
------------------------------
From: Kasper Dupont <[EMAIL PROTECTED]>
Subject: Re: raw datas on serial port
Date: Fri, 05 Jan 2001 16:24:07 +0000
Ionel GARDAIS wrote:
>
> Hi,
>
> How to write raw datas to the serial port ?
> Does the MS-DOS ASM functions works ?
>
> thx,
> ioio
In most cases you should go through the
drivers made for the purpose like /dev/ttyS0.
If reading/writing this device is not
enough there might be some ioctl commands
that will do what you want.
If there is no ioctl that can do what you
want there might be a need for a new feature
in future kernels.
If you still want to do raw access study the
man pages for outb, ioperm and iopl.
Notice you should write outb(value,port);
almost everybody write arguments in wrong
order the first time.
--
Kasper Dupont
------------------------------
From: Max Ischenko <[EMAIL PROTECTED]>
Subject: Re: ISA/PCI resource management
Date: 5 Jan 2001 18:55:37 +0200
At Fri, 05 Jan 2001 15:59:41 +0000 Kasper Dupont wrote:
> Max Ischenko wrote:
>>
>> Hi there.
>>
>> I've heard that Linux 2.4 has much imporoved resource management
>> facilities. I've searched Documentation but didn't find anything.
>>
>> What I look for is how to query the kernel what hardware is present on
>> the system.
> The program can get a lot of information by reading
> /proc/pci or /proc/bus/pci.
And where the format of that file is described?
--
Computers are good at following instructions, but not at reading your mind.
-- D. Knuth
------------------------------
From: Markus Kossmann <[EMAIL PROTECTED]>
Subject: Re: Kernel 2.4
Date: Fri, 05 Jan 2001 18:34:29 +0100
David Findlay wrote:
[...]
> Has anyone got NVdriver to go, with any patching?
There is patch for 2.4 (prerelease) available on
http://www.galois.de/linux/nvidia/
--
Markus Kossmann
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Jonathan Buzzard)
Subject: Re: ioperm()
Date: Fri, 5 Jan 2001 13:19:38 +0000
In article <93466i$5eu$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] writes:
> Hi,
>
> I'm trying to develop a little program to manage the serial port and a
> digital I/O module but I get a SIGSEGV error message. The I/O module is
> located at the addresses 200H-203H, and the code of the program is:
>
> #include <sys/io.h>
>
> main(){
> int i = ioperm(0x200,4,1);
> outb(0x202,0x36);
> }
>
> Could anybody tell me what is happening? Thanks in advance.
>
Why on earth are you using ioperm and direct port access? Take a look
at the serial port programing HOWTO to get an idea. You should be opening
/dev/ttySxx and using read/write and ioctl's to manipulate the serial port.
JAB.
--
Jonathan A. Buzzard Email: [EMAIL PROTECTED]
Northumberland, United Kingdom. Tel: +44(0)1661-832195
------------------------------
From: "Oliver Kowalke" <[EMAIL PROTECTED]>
Subject: kernel 2.4.0 + RAID causes problems
Date: Fri, 5 Jan 2001 21:35:39 +0100
Hi,
my system is a debian2.2r2 (i386) with software raid (level 0,1). I'm using
a 2.2.16 kernel (raid patches) - no problems. Today I compiled a 2.4.0
kernel with the same options. If I try to boot - the kernel fails to boot:
on boot prompt:
fsck.ext2 : no such file on directory while trying to open /dev/md0 (null):
superblock could not be read or does not describe a correct ext2 filesystem
Why can kernel 2.2.16 mount the / (/dev/md0) and the 2.4.0 kernel doesn't?
under 2.2.16 cfdsik can read the partition tables of devices which build the
raid system.
please help!
thanks,
Oliver
------------------------------
From: "Hung P. Tran" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: mounting floppy
Date: Fri, 05 Jan 2001 21:20:07 GMT
Your tip certainly help.
Thank you to all who response. I've check the device major/minor number
and it seems fine. Nothing is wrong with fstab. Yes, it seems like Redhat 6.1
does include the floppy driver. I've checked my /var/log/dmesg and found
the following error:
Floppy drive(s): fd0 is 1.44M
floppy0: Floppy io-port 0x03f0 in use
Anyone has any idea.
Thanks,
hung
[EMAIL PROTECTED] wrote:
> In article <[EMAIL PROTECTED]>,
> "Hung P. Tran" <[EMAIL PROTECTED]> wrote:
> > I have a standard installation (using typical installation)
> > of Redhat Linux 6.1. I am having problem mounting floppy
> > drive. I tried:
> >
> > mount -t msdos /dev/fd0 /mnt/floppy <RETURN>
> >
> > and get the error: the kernel does NOT recognize /dev/fd0 as
> > a block device (may be 'insmod driver' ?)
> >
> > Any idea ? It seems like the regular Redhat installation does
> > NOT include the floppy driver.
>
> Redhat 6.1 does include the floppy driver (on my system).
> Maybe the drive has failed, have you tested it with a
> boot floppy?
>
> >
> > Please advice.
>
> Check the file /var/log/dmesg for logs of the floppy drive init
> at boot time, that should give you some clue what is broken.
> Look right after the logs of hard drive init(s)
> My dmesg logs look like this:
>
> <snip>
> hda: Seagate Technology ST31276A
> hdb: WDC AC2420F
> hdc: ATAPI 20X CD-ROM drive, 128kB Cache
> Uniform CDROM driver Revision: 2.56
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> <snip>
>
> Hope this helps
> Bluster
>
> Sent via Deja.com
> http://www.deja.com/
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Subject: Re: ioperm()
Reply-To: [EMAIL PROTECTED]
Date: Fri, 05 Jan 2001 21:49:50 GMT
On Fri, 5 Jan 2001 13:19:38 +0000, Jonathan Buzzard
<[EMAIL PROTECTED]> wrote:
>In article <93466i$5eu$[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] writes:
>> Hi,
>>
>> I'm trying to develop a little program to manage the serial port and a
>> digital I/O module but I get a SIGSEGV error message. The I/O module is
>> located at the addresses 200H-203H, and the code of the program is:
>>
>> #include <sys/io.h>
>>
>> main(){
>> int i = ioperm(0x200,4,1);
>> outb(0x202,0x36);
>> }
>>
>> Could anybody tell me what is happening? Thanks in advance.
>>
>
>Why on earth are you using ioperm and direct port access? Take a look
Why, to ensure that the code only runs on an Intel PC with a 16550A
UART, of course, and that when it does run, it requires root privs!
Silly question. ;)
------------------------------
From: "mpierce" <[EMAIL PROTECTED]>
Subject: Re: Kernel Non-boot
Reply-To: [EMAIL PROTECTED]
Date: Fri, 05 Jan 2001 22:24:39 GMT
Anders,
Thanks for replying.
Kernel2.2.18 has failed repeatedly to recognise my zip250 drive which is
dev/sda4 or dev/sda1 as being valid. All entries are correct. When I
install Mandrake kernel2.4.0-0.31mdk, the devives are correctly recognised
and configured. Problem with the rpm is that the does not install correct
and cannot be modified. As a result, I have no PCMCIA support and while
RPM kernel boots up correctly, I cannot connect to the net.
I no longer play around on my working machine which is stable preferring
instead to swap HD for development for obvious reasons.
Marvin
In article <[EMAIL PROTECTED]>, "Anders Larsen"
<[EMAIL PROTECTED]> wrote:
> mpierce wrote:
>>
> [snip]
>> I cannot figure this out and I've tried kernel 2.4.0-test9; no problems
>> compiling 2.2.18 (but this doesn't have USB support which is what I
>> need). Marvin
>
> Huh?
> 2.2.18 *does* have USB support (2.2.17 and below didn't)!
> I admit I haven't tried it yet, though (due to lack of USB devices).
>
> cheers
> Anders
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: mounting floppy
Date: Fri, 05 Jan 2001 22:23:56 GMT
In article <[EMAIL PROTECTED]>,
"Hung P. Tran" <[EMAIL PROTECTED]> wrote:
>
> Your tip certainly help.
> Thank you to all who response. I've check the device major/minor
number
> and it seems fine. Nothing is wrong with fstab. Yes, it seems like
Redhat 6.1
> does include the floppy driver. I've checked my /var/log/dmesg and
found
> the following error:
>
> Floppy drive(s): fd0 is 1.44M
> floppy0: Floppy io-port 0x03f0 in use
>
> Anyone has any idea.
>
It seems another device may be using the same I/O port address
as the floppy drive (0x3f0).
Check if this is true in the /proc/ioports file, the device
using the 03f0 port address should be listed in there. Mine
looks like this:
<snip>
03f0-03f5 : floppy
03f6-03f6 : ide0
03f7-03f7 : floppy DIR
<snip>
If there is another device using that I/O port then you must
change its setting so the floppy can use it. If there is not,
then the floppy drive may well have failed on you, have you
been able to test the drive with a boot floppy?
Hope this helps,
Bluster
Sent via Deja.com
http://www.deja.com/
------------------------------
From: "Gene Chang" <[EMAIL PROTECTED]>
Subject: Generating core file
Date: Fri, 5 Jan 2001 14:26:43 -0800
Hi there:
I am writing an application which uses a shared library(.so). My problem is
this:
If my application has a default, it will create a core file.
If the segfault is in the shared lib, I only get a Segmentation fault
message but not core dump.
Anybody has an idea why? I have the source code and build environment for
all the code.
Thanks.
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: mounting floppy
Date: Fri, 5 Jan 2001 23:27:30 +0100
In comp.os.linux.misc Hung P. Tran <[EMAIL PROTECTED]> wrote:
> Floppy drive(s): fd0 is 1.44M
> floppy0: Floppy io-port 0x03f0 in use
check /proc/ioports.
Peter
------------------------------
From: Rob King <[EMAIL PROTECTED]>
Subject: Yamaha CDRW 4416E
Date: Fri, 05 Jan 2001 18:10:11 -0500
Hi i have this burner as my secondary ide slave with a pioneer 16x
dvd-rom as it's primary, and when i boot in linux, the burner won't read
anything, i would like to now, if this is a problem with my system, or
if it is uncommon.
------------------------------
** 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 the
comp.os.linux.development.system newsgroup.
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-Development-System Digest
******************************
