no..I am using the stock kernel i686 Best regards, Liu Yu Fei, Eric Computer Science, CUHK On Thu, Sep 30, 2010 at 8:22 PM, Dan McGee <dpmcgee@xxxxxxxxx> wrote: > On Thu, Sep 30, 2010 at 3:52 AM, Liu Yu Fei, Eric > <hoveringnowings@xxxxxxxxx> wrote: > > My VPS is also on Linode. > > I have just changed my mkinitcpio.conf to > > > > MODULES="xen-fbfront evtchn xenfs xen-blkfront xen-netfront xen-kbdfront > > netxen_nic" > > HOOKS="base udev autodetect pata scsi sata filesystems" > > > > However, when executing the command "mkinitcpio -k 2.6.35-ARCH", I got > the > > following errors: > > > > ERROR: module 'xen_fbfront' not found > > ERROR: module 'evtchn' not found > > ERROR: module 'xenfs' not found > > ERROR: module 'xen_blkfront' not found > > ERROR: module 'xen_netfront' not found > > ERROR: module 'xen_kbdfront' not found > > > > And then I check for the kernel module files: > > > > darkwhite@www:~$ ls > > /lib/modules/2.6.35-ARCH/kernel/drivers/input/xen-kbdfront.ko > > ls: cannot access > > /lib/modules/2.6.35-ARCH/kernel/drivers/input/xen-kbdfront.ko: No such > file > > or directory > > darkwhite@www:~$ ls > > /lib/modules/2.6.35-ARCH/kernel/drivers/net/xen-netfront.ko > > ls: cannot access > > /lib/modules/2.6.35-ARCH/kernel/drivers/net/xen-netfront.ko: No such file > or > > directory > > darkwhite@www:~$ ls > > /lib/modules/2.6.35-ARCH/kernel/drivers/video/xen-fbfront.ko > > ls: cannot access > > /lib/modules/2.6.35-ARCH/kernel/drivers/video/xen-fbfront.ko: No such > file > > or directory > > darkwhite@www:~$ ls > /lib/modules/2.6.35-ARCH/kernel/drivers/xen/evtchn.ko > > ls: cannot access /lib/modules/2.6.35-ARCH/kernel/drivers/xen/evtchn.ko: > No > > such file or directory > > darkwhite@www:~$ ls > > /lib/modules/2.6.35-ARCH/kernel/drivers/xen/xenfs/xenfs.ko > > ls: cannot access > > /lib/modules/2.6.35-ARCH/kernel/drivers/xen/xenfs/xenfs.ko: No such file > or > > directory > > darkwhite@www:~$ ls > > /lib/modules/2.6.35-ARCH/kernel/drivers/net/netxen/netxen_nic.ko > > /lib/modules/2.6.35-ARCH/kernel/drivers/net/netxen/netxen_nic.ko > > > > So I am wondering whether there is something wrong during the packaging > > process? > > Are you building your own kernel? These files are in the Arch stock > kernel package: > > $ find /lib/modules/ -name 'xen*.ko' > /lib/modules/2.6.35-ARCH/kernel/drivers/net/xen-netfront.ko > /lib/modules/2.6.35-ARCH/kernel/drivers/block/xen-blkfront.ko > /lib/modules/2.6.35-ARCH/kernel/drivers/xen/xenfs/xenfs.ko > /lib/modules/2.6.35-ARCH/kernel/drivers/input/xen-kbdfront.ko > /lib/modules/2.6.35-ARCH/kernel/drivers/video/xen-fbfront.ko > > $ find /lib/modules/ -name 'xen*.ko' | xargs pacman -Qo > /lib/modules/2.6.35-ARCH/kernel/drivers/net/xen-netfront.ko is owned > by kernel26 2.6.35.7-1 > /lib/modules/2.6.35-ARCH/kernel/drivers/block/xen-blkfront.ko is owned > by kernel26 2.6.35.7-1 > /lib/modules/2.6.35-ARCH/kernel/drivers/xen/xenfs/xenfs.ko is owned by > kernel26 2.6.35.7-1 > /lib/modules/2.6.35-ARCH/kernel/drivers/input/xen-kbdfront.ko is owned > by kernel26 2.6.35.7-1 > /lib/modules/2.6.35-ARCH/kernel/drivers/video/xen-fbfront.ko is owned > by kernel26 2.6.35.7-1 >
