problems building appletalk module with new kernel
 

On Dec 25, 2007 9:47 AM, Craig White <craigwhite@azapple.com> wrote:
> I've been doing this on CentOS 4 and CentOS 5 but after installing
> 2.6.18-53.1.4el kernel, I'm having a bit of a struggle...
>
> # make -C /lib/modules/2.6.18-53.1.4.el5/build
> SUBDIRS=/usr/src/appletalk modules
> make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> CC [M] /usr/src/appletalk/aarp.o
> CC [M] /usr/src/appletalk/ddp.o
> CC [M] /usr/src/appletalk/dev.o
> CC [M] /usr/src/appletalk/atalk_proc.o
> CC [M] /usr/src/appletalk/sysctl_net_atalk.o
> LD [M] /usr/src/appletalk/appletalk.o
> Building modules, stage 2.
> MODPOST
> CC /usr/src/appletalk/appletalk.mod.o
> LD [M] /usr/src/appletalk/appletalk.ko
> make: Leaving directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
>
> # make -C /lib/modules/2.6.18-53.1.4.el5/build
> SUBDIRS=/usr/src/appletalk modules_install
> make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> INSTALL /usr/src/appletalk/appletalk.ko
> DEPMOD 2.6.18-53.1.4.el5
> make: Leaving directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
>
> and here is my problem...
> # insmod /lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko
> insmod: error inserting
> '/lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko': -1 Invalid module
> format
>
> The above reflects an adjustment in my Makefile but it didn't seem to
> help
>
> why all of a sudden, this 'Invalid module format' ?
>
> Craig

I was able to build and install appletalk.ko under 2.6.18-53.1.4.

What do you see with:

/sbin/modinfo /lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko

Does the vermagic agree with your running kernel? Also, where did you
get the source for appletalk? Is that the stuff from net/appletalk in
your kernel's source tree?

Another option may be to follow the wiki:

http://wiki.centos.org/HowTos/BuildingKernelModules

Akemi
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

On Tue, 2007-12-25 at 10:20 -0800, Akemi Yagi wrote:
> On Dec 25, 2007 9:47 AM, Craig White <craigwhite@azapple.com> wrote:
> > I've been doing this on CentOS 4 and CentOS 5 but after installing
> > 2.6.18-53.1.4el kernel, I'm having a bit of a struggle...
> >
> > # make -C /lib/modules/2.6.18-53.1.4.el5/build
> > SUBDIRS=/usr/src/appletalk modules
> > make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> > CC [M] /usr/src/appletalk/aarp.o
> > CC [M] /usr/src/appletalk/ddp.o
> > CC [M] /usr/src/appletalk/dev.o
> > CC [M] /usr/src/appletalk/atalk_proc.o
> > CC [M] /usr/src/appletalk/sysctl_net_atalk.o
> > LD [M] /usr/src/appletalk/appletalk.o
> > Building modules, stage 2.
> > MODPOST
> > CC /usr/src/appletalk/appletalk.mod.o
> > LD [M] /usr/src/appletalk/appletalk.ko
> > make: Leaving directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> >
> > # make -C /lib/modules/2.6.18-53.1.4.el5/build
> > SUBDIRS=/usr/src/appletalk modules_install
> > make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> > INSTALL /usr/src/appletalk/appletalk.ko
> > DEPMOD 2.6.18-53.1.4.el5
> > make: Leaving directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> >
> > and here is my problem...
> > # insmod /lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko
> > insmod: error inserting
> > '/lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko': -1 Invalid module
> > format
> >
> > The above reflects an adjustment in my Makefile but it didn't seem to
> > help
> >
> > why all of a sudden, this 'Invalid module format' ?
> >
> > Craig
>
> I was able to build and install appletalk.ko under 2.6.18-53.1.4.
>
> What do you see with:
>
> /sbin/modinfo /lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko
>
> Does the vermagic agree with your running kernel? Also, where did you
> get the source for appletalk? Is that the stuff from net/appletalk in
> your kernel's source tree?
>
> Another option may be to follow the wiki:
>
> http://wiki.centos.org/HowTos/BuildingKernelModules
----
I think I see the problem...it appears that it installed and booted the
xen kernel

Will change and reboot with non-xen kernel

Thanks

Craig

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

On Tue, 2007-12-25 at 15:10 -0700, Craig White wrote:
> On Tue, 2007-12-25 at 10:20 -0800, Akemi Yagi wrote:
> > On Dec 25, 2007 9:47 AM, Craig White <craigwhite@azapple.com> wrote:
> > > I've been doing this on CentOS 4 and CentOS 5 but after installing
> > > 2.6.18-53.1.4el kernel, I'm having a bit of a struggle...
> > >
> > > # make -C /lib/modules/2.6.18-53.1.4.el5/build
> > > SUBDIRS=/usr/src/appletalk modules
> > > make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> > > CC [M] /usr/src/appletalk/aarp.o
> > > CC [M] /usr/src/appletalk/ddp.o
> > > CC [M] /usr/src/appletalk/dev.o
> > > CC [M] /usr/src/appletalk/atalk_proc.o
> > > CC [M] /usr/src/appletalk/sysctl_net_atalk.o
> > > LD [M] /usr/src/appletalk/appletalk.o
> > > Building modules, stage 2.
> > > MODPOST
> > > CC /usr/src/appletalk/appletalk.mod.o
> > > LD [M] /usr/src/appletalk/appletalk.ko
> > > make: Leaving directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> > >
> > > # make -C /lib/modules/2.6.18-53.1.4.el5/build
> > > SUBDIRS=/usr/src/appletalk modules_install
> > > make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> > > INSTALL /usr/src/appletalk/appletalk.ko
> > > DEPMOD 2.6.18-53.1.4.el5
> > > make: Leaving directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686'
> > >
> > > and here is my problem...
> > > # insmod /lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko
> > > insmod: error inserting
> > > '/lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko': -1 Invalid module
> > > format
> > >
> > > The above reflects an adjustment in my Makefile but it didn't seem to
> > > help
> > >
> > > why all of a sudden, this 'Invalid module format' ?
> > >
> > > Craig
> >
> > I was able to build and install appletalk.ko under 2.6.18-53.1.4.
> >
> > What do you see with:
> >
> > /sbin/modinfo /lib/modules/2.6.18-53.1.4.el5/extra/appletalk.ko
> >
> > Does the vermagic agree with your running kernel? Also, where did you
> > get the source for appletalk? Is that the stuff from net/appletalk in
> > your kernel's source tree?
> >
> > Another option may be to follow the wiki:
> >
> > http://wiki.centos.org/HowTos/BuildingKernelModules
> ----
> I think I see the problem...it appears that it installed and booted the
> xen kernel
>
> Will change and reboot with non-xen kernel
----
yup - that was it.

# lsmod|grep appletalk
appletalk 39980 36

OK, I thought I ended xen excursions by removing previous copy of xen
kernel but obviously it came back with updates. How do I make sure that
xen kernel doesn't get installed next time?

Craig

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

On Tue, 2007-12-25 at 15:20 -0700, Craig White wrote:
> On Tue, 2007-12-25 at 15:10 -0700, Craig White wrote:

> OK, I thought I ended xen excursions by removing previous copy of xen
> kernel but obviously it came back with updates. How do I make sure that
> xen kernel doesn't get installed next time?
>
----
will this do that?

# rpm -e kernel-xen-2.6.18-53.1.4.el5
xen
xen-libs
libvirt
libvirt-python
gnome-applet-vm
rhn-virtualization-host
python-virtinst
virt-manager

cuz that's what I did

Craig

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

On Dec 25, 2007 2:20 PM, Craig White <craigwhite@azapple.com> wrote:

> OK, I thought I ended xen excursions by removing previous copy of xen
> kernel but obviously it came back with updates. How do I make sure that
> xen kernel doesn't get installed next time?

Do a 'rpm -q kernel' and remove all -xen kernels installed.

Akemi
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

Craig White wrote:

On Tue, 2007-12-25 at 15:20 -0700, Craig White wrote:


On Tue, 2007-12-25 at 15:10 -0700, Craig White wrote:





OK, I thought I ended xen excursions by removing previous copy of xen
kernel but obviously it came back with updates. How do I make sure that
xen kernel doesn't get installed next time?



----
will this do that?

# rpm -e kernel-xen-2.6.18-53.1.4.el5
xen
xen-libs
libvirt
libvirt-python
gnome-applet-vm
rhn-virtualization-host
python-virtinst
virt-manager

cuz that's what I did

Craig


I think /etc/sysconfig/kernel holds the answer to curing the problem
"permanently".

Mine sez:
$ cat /etc/sysconfig/kernel
# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default
UPDATEDEFAULT=yes

# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel
$

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

On Tue, 2007-12-25 at 17:21 -0600, Robert wrote:
>
> Craig White wrote:
> > On Tue, 2007-12-25 at 15:20 -0700, Craig White wrote:
> >
> >> On Tue, 2007-12-25 at 15:10 -0700, Craig White wrote:
> >>
> >
> >
> >> OK, I thought I ended xen excursions by removing previous copy of xen
> >> kernel but obviously it came back with updates. How do I make sure that
> >> xen kernel doesn't get installed next time?
> >>
> >>
> > ----
> > will this do that?
> >
> > # rpm -e kernel-xen-2.6.18-53.1.4.el5
> > xen
> > xen-libs
> > libvirt
> > libvirt-python
> > gnome-applet-vm
> > rhn-virtualization-host
> > python-virtinst
> > virt-manager
> >
> > cuz that's what I did
> >
> > Craig
> >
> >
> I think /etc/sysconfig/kernel holds the answer to curing the problem
> "permanently".
> Mine sez:
> $ cat /etc/sysconfig/kernel
> # UPDATEDEFAULT specifies if new-kernel-pkg should make
> # new kernels the default
> UPDATEDEFAULT=yes
>
> # DEFAULTKERNEL specifies the default kernel package type
> DEFAULTKERNEL=kernel
> $
----
thanks...that explains it

Craig

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

On Tue, 2007-12-25 at 14:39 -0800, Akemi Yagi wrote:
> On Dec 25, 2007 2:20 PM, Craig White <craigwhite@azapple.com> wrote:
>
> > OK, I thought I ended xen excursions by removing previous copy of xen
> > kernel but obviously it came back with updates. How do I make sure that
> > xen kernel doesn't get installed next time?
>
> Do a 'rpm -q kernel' and remove all -xen kernels installed.
----
been there, done that...but that wasn't the answer.

/etc/sysconfig/kernel was the answer

Craig

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

On Dec 25, 2007 3:44 PM, Craig White <craigwhite@azapple.com> wrote:
>
> On Tue, 2007-12-25 at 14:39 -0800, Akemi Yagi wrote:
> > On Dec 25, 2007 2:20 PM, Craig White <craigwhite@azapple.com> wrote:
> >
> > > OK, I thought I ended xen excursions by removing previous copy of xen
> > > kernel but obviously it came back with updates. How do I make sure that
> > > xen kernel doesn't get installed next time?
> >
> > Do a 'rpm -q kernel' and remove all -xen kernels installed.
> ----
> been there, done that...but that wasn't the answer.
>
> /etc/sysconfig/kernel was the answer

I somehow had an impression that you originally installed the standard
kernel and then installed the xen kernel later to "play" with it.
However, from what you said it is now apparent (to me) that you
_originally_ installed the xen kernel. This is because
/etc/sysconfig/kernel is set up by anaconda at the install time and in
your case it had the "kernel-xen" defined. In this case, editing
/etc/sysconfig/kernel is indeed required because removing the xen
kernels would not touch that file. In other words, once set up by
anaconda, /etc/sysconfig/kernel remains the same regardless of what
kernel you install or remove at a later time.

Akemi
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

problems building appletalk module with new kernel
 

On Tue, 2007-12-25 at 16:39 -0800, Akemi Yagi wrote:
> On Dec 25, 2007 3:44 PM, Craig White <craigwhite@azapple.com> wrote:
> >
> > On Tue, 2007-12-25 at 14:39 -0800, Akemi Yagi wrote:
> > > On Dec 25, 2007 2:20 PM, Craig White <craigwhite@azapple.com> wrote:
> > >
> > > > OK, I thought I ended xen excursions by removing previous copy of xen
> > > > kernel but obviously it came back with updates. How do I make sure that
> > > > xen kernel doesn't get installed next time?
> > >
> > > Do a 'rpm -q kernel' and remove all -xen kernels installed.
> > ----
> > been there, done that...but that wasn't the answer.
> >
> > /etc/sysconfig/kernel was the answer
>
> I somehow had an impression that you originally installed the standard
> kernel and then installed the xen kernel later to "play" with it.
> However, from what you said it is now apparent (to me) that you
> _originally_ installed the xen kernel. This is because
> /etc/sysconfig/kernel is set up by anaconda at the install time and in
> your case it had the "kernel-xen" defined. In this case, editing
> /etc/sysconfig/kernel is indeed required because removing the xen
> kernels would not touch that file. In other words, once set up by
> anaconda, /etc/sysconfig/kernel remains the same regardless of what
> kernel you install or remove at a later time.
----
This system actually had a clean install of RHEL which still had about 6
months of entitlement left and it probably asked me about installing xen
and I failed to grasp the significance of that question/answer at the
time...I don't even recall seeing it.

I have since migrated the system to CentOS 5. I also have done CentOS 5
installations and noticed that the choice of xen install was fairly
obvious, perhaps I learned to pay attention.

In fact, I didn't even check until you had me do the modinfo and then I
ran uname to double check and it smacked me in the face...xen returned
on me for no apparent reason (but the apparent reason was
obviously /etc/sysconfig/kernel) and I learned something.

Obviously the choice of xen install includes not only
the /etc/sysconfig/kernel setting but also the xen support packages I
previously listed.

Craig

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos