Re: [gentoo-user] Re: new system, printing suddenly fails for all printers
Return Receipt Your Re: [gentoo-user] Re: new system, printing suddenly fails document: for all printers wasroland.punta...@br-automation.com received by: at:06.07.2009 14:41:57
Re: [gentoo-user] IDE is called hda
Return Receipt Your Re: [gentoo-user] IDE is called hda document: wasroland.punta...@br-automation.com received by: at:21.04.2009 15:18:53
Re: [gentoo-user] How to tie module name to Kernel CONFIG
Return Receipt Your Re: [gentoo-user] How to tie module name to Kernel CONFIG document: wasroland.punta...@br-automation.com received by: at:12.12.2008 15:40:44
Re: [gentoo-user] unknown symbol request_module
Hi cuciferus,
Thanks for pointing me to the gentoo wiki hardware list. It's impressive.
Still it does not have the
Gericom Supersonic 1000
which I am setting up.
I did find a .config on the net for the 2.4.18 kernel
http://techinfo.system33.de/LinuxOnGericom/index.html
http://www.tutorials.de/forum/linux-tutorials/144865-linux-bericht-debian-auf-gericom-notebook.html
(no .config posted)
but the 2.6 kernel config file is quite different, it seems.
Anyway, it would be interesting for me to find out the reason for the
described problem. I have found a similar mail from someone else not for
sound, but without solution/reason.
How can a kernel module not not know about the request_module symbol from
vmlinux?
Roland
[EMAIL PROTECTED] schrieb am 03.09.2008 08:17:00:
> On Monday 01 September 2008 15:45:56 Xav' wrote:
> > On Mon, 1 Sep 2008 12:33:28 +0200, Roland Puntaier
> >
> > <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > I am installing Gentoo on an older notebook of mine and have the
> >
> > following
> >
> > > problem:
> > >
> > > After a first try to make sound work, where I had OSS checked in the
> >
> > For a first start, OSS is now deprecated, so you have to use ALSA
instead
> > in the kernel.
> The kernel oss is now deprecated
> >
> > > kernel configuration,
> > > I followed the gentoo alsa guide
> > > http://www.gentoo.org/doc/en/alsa-guide.xml
> > >
> > > But got a lot of "unknown symbol" entries at boot (viewed afterwards
via
> > > dmesg).
> > > The first seems to be the reason for the others: unknown symbol
> > > request_module.
> > >
> > > request_module is defined in vmlinux (via "nm vmlinux | grep
> > > request_module")
> > > but not linked in soundcore.o ("nm soundcore.o | grep
request_module"
> >
> > says
> >
> > > U(ndefined))
> > >
> > > Since request_module is needed to load kernel modules, no kernel
modules
> > > can be loaded, and therefore symbols from such modules are not
there.
> > > This leads to the other "unknown symbol" messages. So the question
is,
> >
> > why
> >
> > > request_module does not get linked properly.
> > >
> > > What I already tried:
> > > I saved the .config and did
> > > make mrproper
> > > and restored .config.
> > > Then
> > > make && make modules_install
> > >
> > > But that did not help.
> > >
> > > Did somebody experience anything similar?
> > > Could somebody give me a hint how to solve this problem?
> >
> > I think your .config file will help us more than you expect, and also
the
> > output of your dmesg :)
> >
> > > Thanks in advance.
> > > Cheers. Roland
> >
> > Regards.
> >
> > Xavier Parizet
> For laptops you could eyeball the wiki for they have there a complete
setup
> for most of the laptops. Also on the wiki you'll find a nice oss4
tutorial.
> The first advantage of oss4 it's that is s much easier to setup.
> Also for further help you might try to be more specific: what laptop
model?
> what sound card because maybe by chance some of us already did setupthe
same
> model with success.
>
Re: [gentoo-user] unknown symbol request_module
CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set CONFIG_NLS_ISO8859_15=y # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set CONFIG_NLS_UTF8=y # CONFIG_DLM is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set CONFIG_ENABLE_WARN_DEPRECATED=y # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_MAGIC_SYSRQ=y CONFIG_UNUSED_SYMBOLS=y # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_SCHED_DEBUG is not set # CONFIG_SCHEDSTATS is not set CONFIG_TIMER_STATS=y # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_SLUB_STATS is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_HIGHMEM is not set CONFIG_DEBUG_BUGVERBOSE=y # CONFIG_DEBUG_INFO is not set # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_LIST is not set # CONFIG_DEBUG_SG is not set # CONFIG_FRAME_POINTER is not set # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_KPROBES_SANITY_TEST is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_LKDTM is not set # CONFIG_FAULT_INJECTION is not set # CONFIG_LATENCYTOP is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_SAMPLES is not set CONFIG_EARLY_PRINTK=y CONFIG_DEBUG_STACKOVERFLOW=y # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_DEBUG_RODATA is not set # CONFIG_DEBUG_NX_TEST is not set # CONFIG_4KSTACKS is not set CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_DOUBLEFAULT=y CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 CONFIG_IO_DELAY_0X80=y # CONFIG_IO_DELAY_0XED is not set # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=0 # CONFIG_CPA_DEBUG is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # CONFIG_SECURITY_FILE_CAPABILITIES is not set CONFIG_CRYPTO=y # CONFIG_CRYPTO_SEQIV is not set # CONFIG_CRYPTO_MANAGER is not set # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_XCBC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set # CONFIG_CRYPTO_MD5 is not set # CONFIG_CRYPTO_SHA1 is not set # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set # CONFIG_CRYPTO_GF128MUL is not set # CONFIG_CRYPTO_ECB is not set # CONFIG_CRYPTO_CBC is not set # CONFIG_CRYPTO_PCBC is not set # CONFIG_CRYPTO_LRW is not set # CONFIG_CRYPTO_XTS is not set # CONFIG_CRYPTO_CTR is not set # CONFIG_CRYPTO_GCM is not set # CONFIG_CRYPTO_CCM is not set # CONFIG_CRYPTO_CRYPTD is not set # CONFIG_CRYPTO_DES is not set # CONFIG_CRYPTO_FCRYPT is not set # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_586 is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_SEED is not set # CONFIG_CRYPTO_SALSA20 is not set # CONFIG_CRYPTO_SALSA20_586 is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_CAMELLIA is not set # CONFIG_CRYPTO_TEST is not set # CONFIG_CRYPTO_AUTHENC is not set # CONFIG_CRYPTO_LZO is not set CONFIG_CRYPTO_HW=y # CONFIG_CRYPTO_DEV_PADLOCK is not set # CONFIG_CRYPTO_DEV_GEODE is not set # CONFIG_CRYPTO_DEV_HIFN_795X is not set CONFIG_HAVE_KVM=y CONFIG_VIRTUALIZATION=y # CONFIG_KVM is not set # CONFIG_LGUEST is not set # CONFIG_VIRTIO_PCI is not set # CONFIG_VIRTIO_BALLOON is not set # # Library routines # CONFIG_BITREVERSE=y CONFIG_CRC_CCITT=y # CONFIG_CRC16 is not set # CONFIG_CRC_ITU_T is not set CONFIG_CRC32=y # CONFIG_CRC7 is not set # CONFIG_LIBCRC32C is not set CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y Xav' <[EMAIL PROTECTED]> schrieb am 01.09.2008 14:45:56: > On Mon, 1 Sep 2008 12:33:28 +0200, Roland Puntaier > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I am installing Gentoo on an older notebook of mine and have the > following > > problem: > > > > After a first try to make sound work, where I had OSS checked in the > > For a first start, OSS is now deprec
[gentoo-user] unknown symbol request_module
Hi,
I am installing Gentoo on an older notebook of mine and have the following
problem:
After a first try to make sound work, where I had OSS checked in the
kernel configuration,
I followed the gentoo alsa guide
http://www.gentoo.org/doc/en/alsa-guide.xml
But got a lot of "unknown symbol" entries at boot (viewed afterwards via
dmesg).
The first seems to be the reason for the others: unknown symbol
request_module.
request_module is defined in vmlinux (via "nm vmlinux | grep
request_module")
but not linked in soundcore.o ("nm soundcore.o | grep request_module" says
U(ndefined))
Since request_module is needed to load kernel modules, no kernel modules
can be loaded, and therefore symbols from such modules are not there.
This leads to the other "unknown symbol" messages. So the question is, why
request_module does not get linked properly.
What I already tried:
I saved the .config and did
make mrproper
and restored .config.
Then
make && make modules_install
But that did not help.
Did somebody experience anything similar?
Could somebody give me a hint how to solve this problem?
Thanks in advance.
Cheers. Roland
[gentoo-user] Roland Puntaier ist außer Haus.
Ich werde ab 18.08.2008 nicht im Büro sein. Ich kehre zurück am 30.08.2008.
