Linux-Development-Sys Digest #401, Volume #8 Tue, 9 Jan 01 15:13:13 EST
Contents:
Re: Kernel2.4.0 - Unusual panic (Fred Broce)
Looking for unique ID on a Intel system ... (ratz)
Re: device driver dev ("Andy Jeffries")
Re: device driver dev ("Andy Jeffries")
tq_timer and wait queues problem (Perego Paolo)
measure time since program-start in ms (Ralf Edrich)
__libc_global_ctor ("Eric Bus")
quickam and other webcam driver?? (Jerome Corre)
Re: Linux OS for the Apple Mac (Robert Kaiser)
Re: Maturity of Bonobo and CORBA ("Joachim Rosskopf")
Re: 2.2.18 won't boot diskless (Tom Daley)
Re: code language for Linux kernel (Kaz Kylheku)
Re: lilo for secondary IDE ("Hung P. Tran")
Re: Maturity of Bonobo and CORBA ("Edgar F. Hilton")
Re: Linux OS for the Apple Mac (Grant Edwards)
----------------------------------------------------------------------------
From: Fred Broce <[EMAIL PROTECTED]>
Subject: Re: Kernel2.4.0 - Unusual panic
Date: Tue, 09 Jan 2001 09:08:46 -0500
The ide driver is not installed by default..Enable it!
fb
mpierce wrote:
> System is LM7.2 - fresh install; kernel 2.2.17-21mdk
> Downloaded and compiled new 2.4.0 release w/o any runs, drips or errors.
> Have not had any luck getting a 2.4.0 to boot on my Mandrake system and
> need this kernel for USB.
>
> Unusual kernel panic problem:
> request_module[block-major -3] root fs not mounted
> VFS: Cannot open root device "hda1" or 03:01
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:01
> - Computer freezes at this point -
>
> I tried using both grub and lilo. My lilo.conf setup is:
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> vga=normal
> default=linux
> keytable=/boot/us.klt
> lba32
> prompt
> timeout=300
> message=/boot/message
> menu-scheme=wb:bw:wb:bw
> image=/boot/vmlinuz
> label=linux
> root=/dev/hda1
> append=" ide1=autotune ide0=autotune"
> vga=788
> read-only
> image=/boot/bzImage
> label=linux-new
> root=/dev/hda1
> #append=" ide1=autotune ide0=autotune"
> #vga=788
> read-only
> image=/boot/vmlinuz
> label=linux-nonfb
> root=/dev/hda1
> append=" ide1=autotune ide0=autotune"
> read-only
> image=/boot/vmlinuz
> label=failsafe
> root=/dev/hda1
> append=" ide1=autotune ide0=autotune failsafe"
> read-only
> other=/dev/fd0
> label=floppy
> unsafe
>
> My grub setup is:
> timeout 10
> color black/cyan yellow/cyan
> i18n (hd0,0)/boot/grub/messages
> keytable (hd0,0)/boot/us.klt
> altconfigfile (hd0,0)/boot/grub/menu.once
> default 0
>
> title linux
> kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 ide1=autotune ide0=autotune vga=788
>
> title linux-2.4.0
> kernel (hd0,0)/boot/bzImage root=/dev/hda1
>
> title linux-nonfb
> kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 ide1=autotune ide0=autotune
>
> title failsafe
> kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 ide1=autotune ide0=autotune failsafe
> title floppy
> root (fd0)
> chainloader +1
>
> Does anyone have a clue as to why 2.4.0 refuses to boot on a newly
> installed Mandrake 7.2 with the kernel panic error?
------------------------------
From: ratz <[EMAIL PROTECTED]>
Subject: Looking for unique ID on a Intel system ...
Date: Tue, 09 Jan 2001 15:47:48 +0100
Hi,
For some decryption scheme where I generate the key dynamically on each
node I'd like to have some few bytes that are not random but uniqe on
each system. I thought, well let's use the cpuid flag of the PIII CPU
but I haven't yet managed to write a tool to get it nor is it very flexible
with other CPUs. Another approach would have been to take the station node
address of a NIC but this doesn't work either until the eeprom of the NIC
is initialized (before it's FF:FF:FF:FF:FF:FF). Does someone have some bright
idea how I could define/get a uniq ID for each system I build? I don't mind
changing the kernel sources. Stuff like md5sum /proc/bus/pci/devices or
hdparm -I /dev/hda or vortex-diag -# 1 -v | awk '{print $4}' won't work.
During the research I've been writing some modules, one of them I'm still
not sure what the hell I try to access:
/*
* cpuid2.c
*
* x86 CPUID access device Version 2
* This is derived work from H. Peter Anvin who wrote the original big code
* which I still don't really understand ;)
*
* Compile: gcc -c cpuid2.c -O6 -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes
*
*/
#include <linux/module.h>
#include <linux/types.h>
#include <linux/init.h>
#include <linux/poll.h>
MODULE_AUTHOR("Roberto Nibali <[EMAIL PROTECTED]>");
MODULE_DESCRIPTION("x86 generic CPUID deployer Version 2");
MODULE_PARM(reg, "i");
EXPORT_NO_SYMBOLS;
u32 data[4]={0,0,0,0};
u32 reg=1;
extern inline void do_cpuid(u32 reg, u32 *data) {
cpuid(reg, &data[0], &data[1], &data[2], &data[3]);
}
int init_module(void) {
int i=0;
printk(KERN_INFO "cpuid2: Started with reg=%d\n", reg);
do_cpuid(reg, data);
for (; i<4; i++){
printk(KERN_INFO "%d", data[i]);
}
printk(KERN_INFO "\n");
return(0);
}
void cleanup_module(void) {
printk(KERN_INFO "cpuid2: Stopped\n");
}
Can someone explain me what registers I exactly get the info from?
I know, it's kinda strange writing a kernel module and not exactly
knowing what it does but this one is special.
Any hint or pointers appreciated (also RTFM),
Roberto Nibali, ratz
--
mailto: `echo [EMAIL PROTECTED] | sed 's/[NOSPAM]//g'`
------------------------------
From: "Andy Jeffries" <[EMAIL PROTECTED]>
Subject: Re: device driver dev
Date: Tue, 09 Jan 2001 16:13:28 +0000
> What you need for a print isn't really a driver; it's just a filter and
> is done is user space. You can get the basic idea from the gimp-print
> source.
Do you know if any of the other printers in gimp-print are
"GDI-Printers". I have vague memories of GDI calls from my Windows
programming days, but I have next to no idea of how PostScript works (I
believe most of the printer drivers convert xyz to PS/PCL).
Any pointers for information (other than "Use the source, Luke!")?
Cheers,
--
Andy Jeffries
Lead-developer of Scramdisk for Linux
Developer of original Scramdisk Delphi Component
------------------------------
From: "Andy Jeffries" <[EMAIL PROTECTED]>
Subject: Re: device driver dev
Date: Tue, 09 Jan 2001 16:14:25 +0000
>>> Check out gimp-print. It might support that printer.
>
>>No it doesn't. Anyone have any more ideas?
>
> Sure, write some code and add it to gimp-print. That's how new support
> happens.
Absolutely, just checking for duplicated effort before I embark on that
task. Ionel and I are in discussion about having a go at this project
together.
Having a need and scratching it.....
--
Andy Jeffries
Lead-developer of Scramdisk for Linux
Developer of original Scramdisk Delphi Component
------------------------------
From: Perego Paolo <[EMAIL PROTECTED]>
Subject: tq_timer and wait queues problem
Date: 9 Jan 2001 16:03:44 GMT
Hi guys, I've registred a function in the tq_timer wait queue within a module
I'm writing. In cleanup_module I call a sleep_on to stops rmmod until the
function scheduled remove itself from the wait queue.
Well, this works fine in all kernel 2.4.0-testXX kernel series but it doesn't
work in the 2.4.0 final release, and I can't understand why! :(
Any suggestion?
--
$>cd /pub
$>more beer
(0>
//\ Perego Paolo <[EMAIL PROTECTED]> Tutor at D.S.I. University of Milan
V_/_ 'The future will not remember, the past doesn't forget.'
I'm Linux zion 2.4.0-test11 #2 Tue Jan 9 14:57:00 CET 2001 i586
------------------------------
From: Ralf Edrich <[EMAIL PROTECTED]>
Subject: measure time since program-start in ms
Date: Tue, 09 Jan 2001 17:25:00 +0100
Hi,
is it possible to measure the time since program-start with precision of
1 ms ?
All I've read about now deals with around 10 ms.
tia,
Ralf
------------------------------
From: "Eric Bus" <[EMAIL PROTECTED]>
Subject: __libc_global_ctor
Date: Tue, 9 Jan 2001 17:50:17 +0100
Hi,
when I try to compile glibc-2.1.2 I get an unresolved symbol
"__libc_global_ctor" when compiling in the db2 directory. I don't know what
to do. My kernel is 2.2.18
Sincerely,
Eric Bus
[EMAIL PROTECTED]
------------------------------
From: Jerome Corre <[EMAIL PROTECTED]>
Subject: quickam and other webcam driver??
Date: Tue, 09 Jan 2001 16:46:09 GMT
Hi,
I have an old B&W quickcam, which works very well under linux.
Unfortunately I can't find any place where I can by another one!
I was wondering what quickcam (color, color2, color 2 USB, ...) or other
cam (the creativelabs ones for example) are supported under linux. If
they are is it still possible to by them new?
Thanks for any help
regards
--
Jerome Corre
Sent via Deja.com
http://www.deja.com/
------------------------------
From: [EMAIL PROTECTED] (Robert Kaiser)
Subject: Re: Linux OS for the Apple Mac
Date: 9 Jan 2001 11:16:45 GMT
In article <[EMAIL PROTECTED]>,
Kasper Dupont <[EMAIL PROTECTED]> writes:
>
> Check <URL:http://www.linux-m68k.org/>
> Notice that you need to have MMU and FPU.
> I don't know if theese are builtin to
> MC68030 or if they have to be installed
> separately.
MMU is built in (unless it's an MC68EC030), FPU isn't. Does
Linux/68k _require_ an FPU ? I thought there was an optional
FPU emulation as in Linux/i386 ?
Rob
------------------------------
From: "Joachim Rosskopf" <[EMAIL PROTECTED]>
Subject: Re: Maturity of Bonobo and CORBA
Date: Tue, 09 Jan 2001 19:03:29 +0100
In article <[EMAIL PROTECTED]>, "Edgar F. Hilton"
<[EMAIL PROTECTED]> wrote:
> I am interested in writing some applications in Linux that heavily rely
> on CORBA. Does anybody know how well CORBA and Bonobo work in Linux?
> Any caveats that I should be aware of? My applications are intended
> to work in an Enterprise environment, so any comments that are relevant
> on the subject would be much appreciated so that I may retain my job...
> ;)
>
> -Edgar
>
> --
> Edgar F. Hilton FSMLabs, Inc. voice: 850.893.0300
> www.fsmlabs.com fax: 206.350.4EFH www.rtlinux.com
>
Hello,
I'am also currently working at a project concerning a CORBA hardware
interface for java applications. I work with Mico a free, almost complete
CORBA implementation. I think Bonobo fits best for GNOME applications but
that depends on your problem. If you are interested in Mico visit
http://www.mico.org
Joachim
------------------------------
From: [EMAIL PROTECTED] (Tom Daley)
Subject: Re: 2.2.18 won't boot diskless
Date: 9 Jan 2001 18:15:40 GMT
In article <93d1rb$n1t$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Tom Daley) writes:
> In article <93cmds$ils$[EMAIL PROTECTED]>,
> Uri Schonfeld <[EMAIL PROTECTED]> writes:
>> Tom Daley wrote:
>> You did compile network support into the kernel and not as a module, right?
>>
>
> It is on my systems at home. I'll check when I get home tonight.
> My face will be red if I overlooked something this simple.
>
Yes, the network support is NOT a module.
--
===================================================================
| o Tom Daley |
| ___ </v Woodland Park, CO |
| ___ -\ [EMAIL PROTECTED] |
| ___ / (719) 785-4227 |
| (*) Linux! |
===================================================================
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Subject: Re: code language for Linux kernel
Reply-To: [EMAIL PROTECTED]
Date: Tue, 09 Jan 2001 18:27:28 GMT
On 9 Jan 2001 11:12:13 GMT, Robert Kaiser <[EMAIL PROTECTED]> wrote:
>In article <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] (Kaz Kylheku) writes:
>> How would you, for instance, save the registers of the running task and
>> restore ther registers of another task using only C?
>
>You could do it with setjmp()/longjmp(), but of course these
>functions themselves need to be implemented in assembler.
However they are part of the standard language, so they are fair game.
After all, the assignment operator also needs to be implemented in
assembler too, and that's not ruled out!
Unfortunately, the language forbids using longjmp to restart a function
whose execution has already terminated. Using setjmp and lonjmp for
thread context switching is an abuse of these functions.
------------------------------
From: "Hung P. Tran" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,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: "Edgar F. Hilton" <[EMAIL PROTECTED]>
Subject: Re: Maturity of Bonobo and CORBA
Date: Tue, 09 Jan 2001 14:50:30 -0500
==============BB5FECFF1F2ABDB617D3C6F6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hmm... but, isn't MICO one of the slowest if not the slowest free
CORBA implementation?
-Edgar
Joachim Rosskopf wrote:
> In article <[EMAIL PROTECTED]>, "Edgar F. Hilton"
> <[EMAIL PROTECTED]> wrote:
>
> > I am interested in writing some applications in Linux that heavily rely
> > on CORBA. Does anybody know how well CORBA and Bonobo work in Linux?
> > Any caveats that I should be aware of? My applications are intended
> > to work in an Enterprise environment, so any comments that are relevant
> > on the subject would be much appreciated so that I may retain my job...
> > ;)
> >
> > -Edgar
> >
> > --
> > Edgar F. Hilton FSMLabs, Inc. voice: 850.893.0300
> > www.fsmlabs.com fax: 206.350.4EFH www.rtlinux.com
> >
> Hello,
> I'am also currently working at a project concerning a CORBA hardware
> interface for java applications. I work with Mico a free, almost complete
> CORBA implementation. I think Bonobo fits best for GNOME applications but
> that depends on your problem. If you are interested in Mico visit
> http://www.mico.org
>
> Joachim
--
Edgar F. Hilton FSMLabs, Inc.
voice: 850.893.0300 www.fsmlabs.com
fax: 206.350.4EFH www.rtlinux.com
==============BB5FECFF1F2ABDB617D3C6F6
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hmm... but, isn't MICO one of the slowest if not the slowest free
CORBA implementation?
<p>-Edgar
<p>Joachim Rosskopf wrote:
<blockquote TYPE=CITE>In article <[EMAIL PROTECTED]>, "Edgar
F. Hilton"
<br><[EMAIL PROTECTED]> wrote:
<p>> I am interested in writing some applications in Linux that heavily
rely
<br>> on CORBA. Does anybody know how well CORBA and Bonobo work
in Linux?
<br>> Any caveats that I should be aware of? My applications
are intended
<br>> to work in an Enterprise environment, so any comments that are relevant
<br>> on the subject would be much appreciated so that I may retain my
job...
<br>> ;)
<br>>
<br>> -Edgar
<br>>
<br>> --
<br>> Edgar F.
Hilton
FSMLabs, Inc. voice: 850.893.0300
<br>> www.fsmlabs.com fax:
206.350.4EFH
www.rtlinux.com
<br>>
<br>Hello,
<br>I'am also currently working at a project concerning a CORBA hardware
<br>interface for java applications. I work with Mico a free, almost complete
<br>CORBA implementation. I think Bonobo fits best for GNOME applications
but
<br>that depends on your problem. If you are interested in Mico visit
<br><a href="http://www.mico.org">http://www.mico.org</a>
<p>Joachim</blockquote>
<pre>--
Edgar F.
Hilton
FSMLabs, Inc.
voice:
850.893.0300
www.fsmlabs.com
fax:
206.350.4EFH
www.rtlinux.com</pre>
</html>
==============BB5FECFF1F2ABDB617D3C6F6==
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: Linux OS for the Apple Mac
Date: Tue, 09 Jan 2001 19:54:10 GMT
In article <93erut$7nk$[EMAIL PROTECTED]>, Robert Kaiser wrote:
>> Check <URL:http://www.linux-m68k.org/>
>> Notice that you need to have MMU and FPU.
>> I don't know if theese are builtin to
>> MC68030 or if they have to be installed
>> separately.
>
>MMU is built in (unless it's an MC68EC030), FPU isn't. Does
>Linux/68k _require_ an FPU ?
It used to. IIRC, it no longer does. I had Linux running on a
Mac II (si?) a while back but gave up on it. The video
controller was plain-jane frame buffer with no accelleration
(which made X painfully slow), and the SCSI controller was a
horrible CPU hog. I suppose it would have been OK as long as
you didn't use X11 and didn't use the hard drive.
--
Grant Edwards grante Yow! -- Hello,
at POLICE? I"ve got ABBOTT &
visi.com COSTELLO here on suspicion
of HIGHWAY ROBBERY!!
------------------------------
** 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
******************************
