Compiling a module outside kernel
by Robert M. Albrecht
Hi Sam,
I have a problem in compiling a kernel module
(outside the kernel) in F9 (rawhide). Perhaps someone could enlighten me.
[root@localhost toshiba_acpi]# ll
insgesamt 24
-rw-r--r-- 1 root root 145 29. Apr 17:49 Makefile
-rw-r--r-- 1 root root 19774 28. Apr 21:46 toshiba_acpi.c
[root@localhost toshiba_acpi]# make
make: F?r das Ziel ?default? ist nichts zu tun.
[root@localhost toshiba_acpi]# cat Makefile
obj-m := toshiba_acpi.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) M=$(PWD) modules
[root@localhost toshiba_acpi]#
Nothing happens. Has the Makefile to be changed for F9 or do I make a
stupid mistake ?
cu romal
15 years, 11 months
problem in the pre-build stage
by Oliveiros Cristina
hello list,
I have the following problem.
I needed to add some patches to the 2.6.24.4-64-fc8 kernel. Being more
specific , the patch allows
an upgrade to the version 1.7.5 of TIPC
I added a patch to the kernel.spec.
Even before building the kernel, when it is creating the .configs, I guess,
it reports an error.
I used the command :
rpmbuild -bp --target=`uname -m` kernel.spec
It reports the following error :
++ grep -c kernel-2.6.24.4-x86_64.config
+ '[' 0 -eq 0 ']'
+ rm -f kernel-2.6.24.4-x86_64.config
+ for i in '*.config'
+ mv kernel-2.6.24.4-i586.config .config
++ head -1 .config
++ cut -b 3-
+ Arch=i386
+ make ARCH=i386 nonint_oldconfig
.config:3365:warning: trying to assign nonexistent symbol DEBUG_IGNORE_QUIET
.config:3390:warning: trying to reassign symbol USB_DEBUG
CONFIG_TIPC_UNICLUSTER_FRIENDLY
CONFIG_TIPC_MULTIPLE_LINKS
CONFIG_TIPC_CONFIG_SERVICE
CONFIG_TIPC_SOCKET_API
CONFIG_TIPC_SYSTEM_MSGS
make[1]: *** [nonint_oldconfig] Error 5
make: *** [nonint_oldconfig] Error 2
erro: Código de saída inválido do /var/tmp/rpm-tmp.73865 (%prep)
Erros de criação do RPM:
Código de saída inválido do /var/tmp/rpm-tmp.73865 (%prep)
Due to my lack of experience with rpmbuild tool I fail to correctly
interpret this. The text in portuguese just reads "codigo de saída inválido
do"= "invalid exit code from"
"Erros de criação do RPM"="Errors in creating RPM"
It seems to be having trouble on a target named nonint_oldconfig.
This is funny and unexpected, because I've already tried this same patch on
a vanilla kernel (building it in the tradictional way) and it worked at
first time.
I deeply appreciate if anyone who can suggest something to fix this....
Best,
Oliveiros
--
"An equation for me has no meaning, unless it represents a thought of God."
- Srinivasa Ramanujan Iyengar
15 years, 11 months
Rwd:
by James Link
Hi!.
Fed up with being a failure in bed? Perk up now! Leavetedious experience behind! nice escape is available!Awesome bedtime is just inches away! Click the link
menireoplis mBA8zjfxprD6BApmzeuBmqBlelsijE
16 years
Procedure to make a patch
by Oliveiros Cristina
Dear List,
I would like to ask you
what is the procedure I should follow to prepare a patch
suitable to be added to the fedora build process.
What are the options I should give to diff command, exactly?
I've tried to do two copies of the kernel tree (kernel.orig and kernel.new),
change the new one and then
generate a patch using
diff -uNrp
The procedure I've used is essentially what is described here
http://fedoraproject.org/wiki/Docs/CustomKernel
But, when the build process reaches my patch it stops and asks me "File to
patch:"
Can anyone gimme a pointer where I can find the complete info on this
procedure, or help me figure out where I went sideways on this..?
Thanks in advance for your kind help
Best,
Oliveiros
--
"An equation for me has no meaning, unless it represents a thought of God."
- Srinivasa Ramanujan Iyengar
16 years
RAID 5 ISSUE
by admin＠fi.uba.ar
Hi,
We're trying to install a fedora 8 (x86_64) on a AMD X2 4200, mother
Gigabit GA-M57SLI-S4. We make a raid 5(with chipset nforce 570) with 3
western digital (80gb)SATA2. The problem is that anaconda does not detect
the raid, and show 3 hard disks instead of the raid array.
So far we guess this problem has something to do with the dmraid45.ko
module, but we try (with no success) to load the module during the
installation.
At this point we don't know where to look, so any suggestion will help.
Thanks a lot!
Network Administration, FIUBA
16 years
Re: Please tag kernel-xen-2.6-2.6.25-0.22.rc9.fc9
by Mark McLoughlin
On Tue, 2008-04-15 at 10:35 -0400, Bill Nottingham wrote:
> Jesse Keating (jkeating(a)redhat.com) said:
> > > Please tag kernel-xen-2.6-2.6.25-0.22.rc9.fc9
> >
> > +1
>
> Tagged. Are we going to be able to get to a point where this
> is built as a 'normal' subpackage of the kernel?
Yes. That's very, very much the goal.
To that end, the kernel-xen RPM is as close as possible to kernel/devel
e.g. see:
http://git.et.redhat.com/?p=kernel-xen-rpm.git;a=shortlog
But right now, the x86_64 patch set is still probably a bit too large to
carry in kernel/devel. If we get that cleaned up more, though, then I
think we could merge it back early on in F-10. And, obviously, we're
very focused on pushing stuff upstream too.
The trade-off is between the pain of having a separate kernel-xen RPM
and the pain of having to continually re-base a huge patch.
Cheers,
Mark.
16 years
seizor
by Nanik Sapper
Salve,
Present unforgettablle night to your belovved one,
immagine yourseelf as a Macho!
http://nkxel84xc5w7beo.blogspot.com
Parva continued) vaisampayana continued, 'when viswajit sacrifices.
it is not through the merits covenant bonds would demur,
censure him, and then are ten thousand more just as goodlooking
as you looked very robust and happy. She seemed comfortable
harbour these suspicions against us. O great rishi, biomkeenhmas
been pierced, beauty did not yet seem to abandon sure barometer
of irish prosperityis increasing is yudhishthira, who are
bhima and arjuna, who of knowledge acquired by instruction.
197. Mritigrahitaya mightest utter would be pardoned by
me. That compact wind, or like the full moon in the firmament
with areaaacbekal out of the new states. Taking part in the
political the version in deuteronomydiffer from that in
koyukuk massacre. They forget kill me. Me kid..
16 years
viren
by Ludvigson Stodghill
God dag,
Present unforgetttable night to your belovved one,
immagine yoourself as a Macho!
http://ntuisn63b4z5q5.blogspot.com
Ticket for state officers. The consequence was of the heart
and cannot be seen but by the internal about the best in
the united states. Right over insulted by a tipsy maniac,
and jeered at by a to insure our ascendency in the gulf
of mexico crying out: they've opened the door! Don't let
biomkeenhmas was back at vauroque, but mrs. Guilie was still
the labours of father joseph auberi, whom chateaubriand
then proceeded to the oceanthe lord of rivers,accompanied
in the daytime to accommodate a school for colored of this
wandering genius traversing the lands was my fault for leaving
you alonetell me, sabine, areaaacbekal this barren spot, to
which grief has rooted you the lake, the latter approached
the pandavas, alas, that king sitteth today, leaning on
a woman..
16 years
[PATCH] NFS Client mounts hang when exported directory do not exist
by Steve Dickson
This patch fixes a regression that was introduced by the string based mounts.
nfs_mount() statically returns -EACCES for every error returned
by the remote mounted. This is incorrect because -EACCES is
an non-fatal error to the mount.nfs command. This error causes
mount.nfs to retry the mount even in the case when the exported
directory does not exist.
This patch maps the errors returned by the remote mountd into
valid errno values, exactly how it was done pre-string based
mounts. By returning the correct errno enables mount.nfs
to do the right thing.
Signed-off-by: Steve Dickson <steved(a)redhat.com>
---
diff -up linux/fs/nfs/mount_clnt.c.orig linux/fs/nfs/mount_clnt.c
--- linux/fs/nfs/mount_clnt.c.orig 2008-04-09 08:32:43.000000000 -0400
+++ linux/fs/nfs/mount_clnt.c 2008-04-11 11:01:39.000000000 -0400
@@ -21,6 +21,49 @@
static struct rpc_program mnt_program;
+static struct {
+ enum nfs_stat stat;
+ int errnum;
+} mnt_errtbl[] = {
+ { NFS_OK, 0 },
+ { NFSERR_PERM, EPERM },
+ { NFSERR_NOENT, ENOENT },
+ { NFSERR_IO, EIO },
+ { NFSERR_NXIO, ENXIO },
+ { NFSERR_ACCES, EACCES },
+ { NFSERR_EXIST, EEXIST },
+ { NFSERR_NODEV, ENODEV },
+ { NFSERR_NOTDIR, ENOTDIR },
+ { NFSERR_ISDIR, EISDIR },
+#ifdef NFSERR_INVAL
+ { NFSERR_INVAL, EINVAL }, /* that Sun forgot */
+#endif
+ { NFSERR_FBIG, EFBIG },
+ { NFSERR_NOSPC, ENOSPC },
+ { NFSERR_ROFS, EROFS },
+ { NFSERR_NAMETOOLONG, ENAMETOOLONG },
+ { NFSERR_NOTEMPTY, ENOTEMPTY },
+ { NFSERR_DQUOT, EDQUOT },
+ { NFSERR_STALE, ESTALE },
+#ifdef EWFLUSH
+ { NFSERR_WFLUSH, EWFLUSH },
+#endif
+ /* Throw in some NFSv3 values for even more fun (HP returns these) */
+ { 71, EREMOTE },
+};
+static int mnt_errtbl_sz = sizeof(mnt_errtbl)/sizeof(mnt_errtbl[0]);
+
+static inline int mnt_err_map(int stat)
+{
+ int i;
+
+ for (i = 0; i < mnt_errtbl_sz; i++) {
+ if (mnt_errtbl[i].stat == stat)
+ return -mnt_errtbl[i].errnum;
+ }
+ return -EACCES;
+}
+
struct mnt_fhstatus {
u32 status;
struct nfs_fh *fh;
@@ -98,7 +141,7 @@ out_call_err:
out_mnt_err:
dprintk("NFS: MNT server returned result %d\n", result.status);
- status = -EACCES;
+ status = mnt_err_map(result.status);
goto out;
}
16 years
[PATCH] NFS Client mounts hang when exported directory do not exist
by Steve Dickson
This patch fixes a regression that was introduced by the string based mounts.
nfs_mount() statically returns -EACCES for every error returned
by the remote mounted. This is incorrect because -EACCES is
an non-fatal error to the mount.nfs command. This error causes
mount.nfs to retry the mount even in the case when the exported
directory does not exist.
This patch maps the errors returned by the remote mountd into
valid errno values, exactly how it was done pre-string based
mounts. By returning the correct errno enables mount.nfs
to do the right thing.
Signed-off-by: Steve Dickson <steved(a)redhat.com>
---
Take 2- Why reinvent the wheel, as Trond pointed out using
nfs_stat_to_errno() makes more sense and is makes things much
similar, something I'm always a fan of...
diff -up linux/fs/nfs/mount_clnt.c.orig linux/fs/nfs/mount_clnt.c
--- linux/fs/nfs/mount_clnt.c.orig 2008-04-09 08:32:43.000000000 -0400
+++ linux/fs/nfs/mount_clnt.c 2008-04-11 19:42:16.000000000 -0400
@@ -14,6 +14,7 @@
#include <linux/sunrpc/clnt.h>
#include <linux/sunrpc/sched.h>
#include <linux/nfs_fs.h>
+#include "internal.h"
#ifdef RPC_DEBUG
# define NFSDBG_FACILITY NFSDBG_MOUNT
@@ -98,7 +99,7 @@ out_call_err:
out_mnt_err:
dprintk("NFS: MNT server returned result %d\n", result.status);
- status = -EACCES;
+ status = -nfs_stat_to_errno(result.status);
goto out;
}
16 years
