[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Latest Xen-unstable with 2.6.30-rc3-tip: All modules missing


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Andreas Sommer <AndiDog@xxxxxx>
  • Date: Tue, 23 Jun 2009 09:53:14 +0100
  • Delivery-date: Tue, 23 Jun 2009 01:54:27 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I tried it again, and got the same make error when making the linux kernel myself. The last lines of the output are:

------------------------------------------------------------------
CC      arch/x86/boot/version.o
CC      arch/x86/boot/video-vga.o
CC      arch/x86/boot/video-vesa.o
CC      arch/x86/boot/video-bios.o
GZIP    arch/x86/boot/compressed/vmlinux.bin.gz
HOSTCC  arch/x86/boot/tools/build
MODPOST 1871 modules
CPUSTR  arch/x86/boot/cpustr.h
CC      arch/x86/boot/cpu.o
LD      arch/x86/boot/compressed/piggy.o
LD      arch/x86/boot/compressed/vmlinux
OFFSETS arch/x86/boot/offsets.h
OBJCOPY arch/x86/boot/vmlinux.bin
AS      arch/x86/boot/header.o
LD      arch/x86/boot/setup.elf
OBJCOPY arch/x86/boot/setup.bin
BUILD   arch/x86/boot/bzImage
Root device is (8, 1)
Setup is 13676 bytes (padded to 13824 bytes).
System is 1634 kB
CRC 19f3d9ae
Kernel: arch/x86/boot/bzImage is ready  (#1)
ERROR: "swiotlb_phys_to_bus" [drivers/gpu/drm/drm.ko] undefined!
ERROR: "swiotlb_phys_to_bus" [drivers/char/agp/sworks-agp.ko] undefined!
ERROR: "swiotlb_bus_to_phys" [drivers/char/agp/intel-agp.ko] undefined!
ERROR: "swiotlb_phys_to_bus" [drivers/char/agp/intel-agp.ko] undefined!
ERROR: "swiotlb_phys_to_bus" [drivers/char/agp/efficeon-agp.ko] undefined!
ERROR: "swiotlb_phys_to_bus" [drivers/char/agp/ati-agp.ko] undefined!
ERROR: "swiotlb_phys_to_bus" [drivers/char/agp/amd64-agp.ko] undefined!
ERROR: "swiotlb_phys_to_bus" [drivers/char/agp/amd-k7-agp.ko] undefined!
ERROR: "swiotlb_phys_to_bus" [drivers/char/agp/ali-agp.ko] undefined!
ERROR: "swiotlb_bus_to_phys" [drivers/char/agp/agpgart.ko] undefined!
ERROR: "swiotlb_phys_to_bus" [drivers/char/agp/agpgart.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
------------------------------------------------------------------

This is the configuration for the software IO TLB:

------------------------------------------------------------------

hostname-xen:/usr/src/xen-unstable/linux-2.6-pvops.git# find . | grep -i conf | xargs grep CONFIG_SWIO
./arch/x86/configs/x86_64_defconfig:CONFIG_SWIOTLB=y
./arch/ia64/configs/gensparse_defconfig:CONFIG_SWIOTLB=y
./arch/ia64/configs/bigsur_defconfig:CONFIG_SWIOTLB=y
./arch/ia64/configs/generic_defconfig:CONFIG_SWIOTLB=y
./arch/ia64/configs/tiger_defconfig:CONFIG_SWIOTLB=y
./arch/ia64/configs/sim_defconfig:CONFIG_SWIOTLB=y
./arch/ia64/configs/xen_domu_defconfig:CONFIG_SWIOTLB=y

------------------------------------------------------------------

What do I need to change?


Andreas Sommer wrote:
Hi,

I downloaded Xen-3.5-unstable from http://xenbits.xensource.com/xen-unstable.hg two days ago and built it without problems (make tools, make dist, make install). Well, the /lib/modules/2.6.30-rc3-tip/kernel directory now only contains the subdirectories "arch" and "drivers" - so where are all the other modules??? Of course Xen does not start correctly. It hangs at "Waiting for root file system..." - having no "fs" modules it could be hard to read a file system ;) And by the way: Yes, I created a initrd image for the new kernel (I'm on Debian).

I've also tried to build the Linux kernel under /usr/src/xen-unstable/linux-2.6-pvops.git completely. It then gives me MODPOST errors "ERROR: [xxx.ko] undefined!" for most of the AGP (or AGPGART?) modules. Having removed them, it builds but Xen cannot boot with that kernel.

Any suggestions?

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.