public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luca Casagrande <luca.casagrande@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Error building my first iso...
Date: Thu, 13 Jul 2006 08:58:02 +0200	[thread overview]
Message-ID: <200607130858.03433.luca.casagrande@gmail.com> (raw)
In-Reply-To: <44B564D0.10100@gentoo.org>

Thx for your help, now it builds the kernel..
The problem is in the install phase:

[..]
*** Warning: "tosh_smm" [drivers/video/neofb.ko] undefined!
--
  INSTALL sound/usb/snd-usb-audio.ko
  INSTALL sound/usb/snd-usb-lib.ko
  INSTALL sound/usb/usx2y/snd-usb-usx2y.ko
  INSTALL sound/pci/vx222/snd-vx222.ko
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F System.map  
2.6.16-reiser4-r3-nosmp; fi
WARNING: /lib/modules/2.6.16-reiser4-r3-nosmp/kernel/drivers/video/neofb.ko 
needs unknown symbol tosh_smm
--
* <<< Callback exit status: 1
* --udev is deprecated and no longer necessary as udev is on by default
* Gentoo Linux Genkernel; Version 3.3.11d
* Running with options: --callback=emerge  klibc splashutils wireless-tools 
madwifi-ng-tools madwifi-ng rfswitch ndiswrapper cryptsetup-luks 
sys-fs/device-mapper pcmciautils nvidia-kernel ati-drivers nvidia-glx 
sys-fs/captive rt2x00 bcm570x rtl8180 =media-tv/ivtv-0.6.2 nvidia-settings 
slmodem zd1211 ltmodem hsfmodem hcfpcimodem mwavem acerhk 
net-wireless/at76c503a --no-mountboot --kerneldir=/usr/src/linux --kernel-config=/var/tmp/gentoo.config --minkernpackage=/usr/portage/packages/gk_binaries/gentoo-2006.0.tar.bz2 
all --gensplash=default --udev

* ERROR: --callback failed!
!! catalyst: Runscript kernel build failed


Traceback (most recent call last):
  File "modules/livecd_stage2_target.py", line 324, in run_local
    self.build_kernel()
  File "modules/livecd_stage2_target.py", line 309, in build_kernel
    "Runscript kernel build failed")
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 102, in cmd
    raise CatalystError,myexc
CatalystError: <unprintable instance object>
None

!!! catalyst: Runscript aborting due to error.

Thanks for helping me
Luca

Alle 23:08, mercoledì 12 luglio 2006, Andrew Gaffney ha scritto:
> Luca Casagrande wrote:
> > * Linux Kernel 2.6.16-reiser4-r3-nosmp2.6.16-reiser4-r3 for x86...
> > * The build-host kernel does not appear to have loop device support.
> > * Please load loop support before running genkernel!
> > * ERROR: Load loop support!
>
> No, I have absolutely no idea what could possibly be wrong :P Recompile
> your kernel with support for the loopback device.

-- 
"L'ambizione è l'ultimo rifugio del fallito (Oscar Wilde)"

LINUX User #411601
jabber: casagrande@jabber.linux.it

 

-- 
gentoo-catalyst@gentoo.org mailing list



  parent reply	other threads:[~2006-07-13  6:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 20:53 [gentoo-catalyst] Error building my first iso Luca Casagrande
2006-07-12 21:08 ` Andrew Gaffney
2006-07-12 21:54   ` Chris Gianelloni
2006-07-13  6:58   ` Luca Casagrande [this message]
2006-07-13 16:42     ` Chris Gianelloni
2006-07-13 17:00       ` Luca Casagrande
2006-07-13 18:29         ` Chris Gianelloni
2006-07-14 10:43           ` Luca Casagrande
2006-07-14 12:34           ` Luca Casagrande

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200607130858.03433.luca.casagrande@gmail.com \
    --to=luca.casagrande@gmail.com \
    --cc=gentoo-catalyst@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox