re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
On Mon, 2 Jul 2001, mr sam jooky wrote: >>Somewhere between 2.4.2 and 2.4.5-ac13, PCMCIA card insertion and >>removal appears to have broken on my Toshiba Libretto. On 2.4.2 all was >>fine. On both 2.4.5-ac13 and ac22 it's broken. The whole machine >>freezes >>solid, no SAK-s, SAK-u, SAK-b, no Ctrl-Alt-Fn to switch VC's. No >>messages >>are issued. Problem occurs when inserting/removing any of YE-Data >>PCMCIA >>floppy, TDK Smartmedia adapter (ide_cs), or 3c589 ethernet card. > >On my IBM Thinkpad 390E my PCMCIA works fine with 2.4.5, on very rare >occasions >the mouse will drift diagonaly to the lower right corner. I read in the kernel >sources that this happens normaly due to probing of the PCMCIA which screws up >the mouse device. It happens so rarely I have not yet taken the time to try to >debug it. > >- >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >the body of a message to [EMAIL PROTECTED] >More majordomo info at http://vger.kernel.org/majordomo-info.html >Please read the FAQ at http://www.tux.org/lkml/ ... Just FYI.(maybe worthless without ksymoops report) My ThinkPad 600X(Coppermine 500 MHZ, 100 MHZ SDRAM 320 MB, NeoMagic 256Z Video chipset, UDMA3 IDE hdd, cardbus IBM Etherjet 10/100 - Xircom oem, tulip 21143 compatible, external mii tranceiver - Cirrus CS46XX sound chipset) was completely locked up the system while loading yenta_socket and other modules. But, Mr. David Hinds' pcmcia-cs-3.1.26(i82365, tulip_cs) always works well. This was the first time for me to try to experiment with built-in pcmcia support of regular linux kernel after 2.4.0 kernel was released. I have been using only pcmcia-cs-3.1.2x since I bought 600X in Dec 2000, because pcmcia drivers of 2.4.0-testX kernel doesn't worked wel at that time. I use kernel-2.4.3-ac22, gcc-2.96-88, binutils-2.11.90.0.19, glibc-2.2.3, XFree86-4.1.0, ..). -- Where there is a will, there is a way. [EMAIL PROTECTED] For the future of you and me! [EMAIL PROTECTED] fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
On Mon, 2 Jul 2001, mr sam jooky wrote: Somewhere between 2.4.2 and 2.4.5-ac13, PCMCIA card insertion and removal appears to have broken on my Toshiba Libretto. On 2.4.2 all was fine. On both 2.4.5-ac13 and ac22 it's broken. The whole machine freezes solid, no SAK-s, SAK-u, SAK-b, no Ctrl-Alt-Fn to switch VC's. No messages are issued. Problem occurs when inserting/removing any of YE-Data PCMCIA floppy, TDK Smartmedia adapter (ide_cs), or 3c589 ethernet card. On my IBM Thinkpad 390E my PCMCIA works fine with 2.4.5, on very rare occasions the mouse will drift diagonaly to the lower right corner. I read in the kernel sources that this happens normaly due to probing of the PCMCIA which screws up the mouse device. It happens so rarely I have not yet taken the time to try to debug it. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ... Just FYI.(maybe worthless without ksymoops report) My ThinkPad 600X(Coppermine 500 MHZ, 100 MHZ SDRAM 320 MB, NeoMagic 256Z Video chipset, UDMA3 IDE hdd, cardbus IBM Etherjet 10/100 - Xircom oem, tulip 21143 compatible, external mii tranceiver - Cirrus CS46XX sound chipset) was completely locked up the system while loading yenta_socket and other modules. But, Mr. David Hinds' pcmcia-cs-3.1.26(i82365, tulip_cs) always works well. This was the first time for me to try to experiment with built-in pcmcia support of regular linux kernel after 2.4.0 kernel was released. I have been using only pcmcia-cs-3.1.2x since I bought 600X in Dec 2000, because pcmcia drivers of 2.4.0-testX kernel doesn't worked wel at that time. I use kernel-2.4.3-ac22, gcc-2.96-88, binutils-2.11.90.0.19, glibc-2.2.3, XFree86-4.1.0, ..). -- Where there is a will, there is a way. [EMAIL PROTECTED] For the future of you and me! [EMAIL PROTECTED] fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: compile error about do_softirq in 2.4.5-ac21
On Sun, 1 Jul 2001, Byeong-ryeol Kim wrote:
>On Sat, 30 Jun 2001, Keith Owens wrote:
>
>>On Sat, 30 Jun 2001 10:07:20 +0900 (KST),
>>Byeong-ryeol Kim <[EMAIL PROTECTED]> wrote:
>>>>>background.c:57: `do_softirq_Rf0a529b7' undeclared (first use in \
>>>>>this function)
>>
>>Missing include in fs/jffs2/background.c. spin_unlock_bh() needs the
>>definition of do_softirq(). Against 2.4.5-ac21, will fit -ac22 as well.
>>
>>Index: 5.52/fs/jffs2/background.c
>>--- 5.52/fs/jffs2/background.c Sun, 22 Apr 2001 07:25:55 +1000 kaos
>(linux-2.4/Z/d/7_background 1.1 644)
>>+++ 5.52(w)/fs/jffs2/background.c Sat, 30 Jun 2001 14:13:12 +1000 kaos
>(linux-2.4/Z/d/7_background 1.1 644)
>>@@ -43,6 +43,7 @@
>> #include
>> #include
>>+#include
>> #include
>> #include "nodelist.h"
>...
>
>Thank you.
>But, it is proved to be that jffs2/background.c includes 'linux/smp_lock.h',
>'linux/smp_lock.h' includes 'asm/smplock.h' and 'asm/smplock.h' includes
>'linux/interrupt.h'.
>Is it correct to put 'linux/interrupt.h' into jffs2/background.c in this
>situation?
...
Please, ignore my previous mail about 'linux/interrupt.h'.
I bypassed the '#ifndef CONFIG_SMP ... #endif' wrapper in linux/smp_lock.h.
...
#ifndef CONFIG_SMP
#define lock_kernel() do { } while(0)
#define unlock_kernel() do { } while(0)
#define release_kernel_lock(task, cpu) do { } while(0)
#define reacquire_kernel_lock(task) do { } while(0)
#define kernel_locked() 1
#else
#include
#endif /* CONFIG_SMP */
...
Thanks,
--
Where there is a will, there is a way. [EMAIL PROTECTED]
For the future of you and me! [EMAIL PROTECTED]
fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: compile error about do_softirq in 2.4.5-ac21
On Sat, 30 Jun 2001, Keith Owens wrote: >On Sat, 30 Jun 2001 10:07:20 +0900 (KST), >Byeong-ryeol Kim <[EMAIL PROTECTED]> wrote: >>>>background.c:57: `do_softirq_Rf0a529b7' undeclared (first use in \ >>>>this function) > >Missing include in fs/jffs2/background.c. spin_unlock_bh() needs the >definition of do_softirq(). Against 2.4.5-ac21, will fit -ac22 as well. > >Index: 5.52/fs/jffs2/background.c >--- 5.52/fs/jffs2/background.c Sun, 22 Apr 2001 07:25:55 +1000 kaos >(linux-2.4/Z/d/7_background 1.1 644) >+++ 5.52(w)/fs/jffs2/background.c Sat, 30 Jun 2001 14:13:12 +1000 kaos >(linux-2.4/Z/d/7_background 1.1 644) >@@ -43,6 +43,7 @@ > #include > #include >+#include > #include > #include "nodelist.h" ... Thank you. But, it is proved to be that jffs2/background.c includes 'linux/smp_lock.h', 'linux/smp_lock.h' includes 'asm/smplock.h' and 'asm/smplock.h' includes 'linux/interrupt.h'. Is it correct to put 'linux/interrupt.h' into jffs2/background.c in this situation? -- Where there is a will, there is a way. [EMAIL PROTECTED] For the future of you and me! [EMAIL PROTECTED] fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: compile error about do_softirq in 2.4.5-ac21
On Sat, 30 Jun 2001, Keith Owens wrote: On Sat, 30 Jun 2001 10:07:20 +0900 (KST), Byeong-ryeol Kim [EMAIL PROTECTED] wrote: background.c:57: `do_softirq_Rf0a529b7' undeclared (first use in \ this function) Missing include in fs/jffs2/background.c. spin_unlock_bh() needs the definition of do_softirq(). Against 2.4.5-ac21, will fit -ac22 as well. Index: 5.52/fs/jffs2/background.c --- 5.52/fs/jffs2/background.c Sun, 22 Apr 2001 07:25:55 +1000 kaos (linux-2.4/Z/d/7_background 1.1 644) +++ 5.52(w)/fs/jffs2/background.c Sat, 30 Jun 2001 14:13:12 +1000 kaos (linux-2.4/Z/d/7_background 1.1 644) @@ -43,6 +43,7 @@ #include linux/jffs2.h #include linux/mtd/mtd.h +#include linux/interrupt.h #include linux/smp_lock.h #include nodelist.h ... Thank you. But, it is proved to be that jffs2/background.c includes 'linux/smp_lock.h', 'linux/smp_lock.h' includes 'asm/smplock.h' and 'asm/smplock.h' includes 'linux/interrupt.h'. Is it correct to put 'linux/interrupt.h' into jffs2/background.c in this situation? -- Where there is a will, there is a way. [EMAIL PROTECTED] For the future of you and me! [EMAIL PROTECTED] fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: compile error about do_softirq in 2.4.5-ac21
On Sun, 1 Jul 2001, Byeong-ryeol Kim wrote:
On Sat, 30 Jun 2001, Keith Owens wrote:
On Sat, 30 Jun 2001 10:07:20 +0900 (KST),
Byeong-ryeol Kim [EMAIL PROTECTED] wrote:
background.c:57: `do_softirq_Rf0a529b7' undeclared (first use in \
this function)
Missing include in fs/jffs2/background.c. spin_unlock_bh() needs the
definition of do_softirq(). Against 2.4.5-ac21, will fit -ac22 as well.
Index: 5.52/fs/jffs2/background.c
--- 5.52/fs/jffs2/background.c Sun, 22 Apr 2001 07:25:55 +1000 kaos
(linux-2.4/Z/d/7_background 1.1 644)
+++ 5.52(w)/fs/jffs2/background.c Sat, 30 Jun 2001 14:13:12 +1000 kaos
(linux-2.4/Z/d/7_background 1.1 644)
@@ -43,6 +43,7 @@
#include linux/jffs2.h
#include linux/mtd/mtd.h
+#include linux/interrupt.h
#include linux/smp_lock.h
#include nodelist.h
...
Thank you.
But, it is proved to be that jffs2/background.c includes 'linux/smp_lock.h',
'linux/smp_lock.h' includes 'asm/smplock.h' and 'asm/smplock.h' includes
'linux/interrupt.h'.
Is it correct to put 'linux/interrupt.h' into jffs2/background.c in this
situation?
...
Please, ignore my previous mail about 'linux/interrupt.h'.
I bypassed the '#ifndef CONFIG_SMP ... #endif' wrapper in linux/smp_lock.h.
...
#ifndef CONFIG_SMP
#define lock_kernel() do { } while(0)
#define unlock_kernel() do { } while(0)
#define release_kernel_lock(task, cpu) do { } while(0)
#define reacquire_kernel_lock(task) do { } while(0)
#define kernel_locked() 1
#else
#include asm/smplock.h
#endif /* CONFIG_SMP */
...
Thanks,
--
Where there is a will, there is a way. [EMAIL PROTECTED]
For the future of you and me! [EMAIL PROTECTED]
fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
compile error about do_softirq in 2.4.5-ac21
I met following error while compiling 2.4.5-ac21: I know, of course, this error was reported several times as the compile problem of 2.4.6-preX, and there posted a patch about it by Mr. Keith Owens. I confirmed It had been applied to include/asm-i386/softirq.h of 2.4.5-ac21). But I see this in 2.4.5-ac21 again, and confused so much. I use Red Hat 7.1 (with up to latest errata updates + kernel-2.4.5-ac19, glibc-2.2.3, gcc-2.96-88, binutils-2.11.90.0.15, etc.) BTW, this error ocurred on both K6-II+ desktop(no-name) and Pentium III 500 MHZ noteboot(IBM ThkinPad 600X), and compiler was the same on both machines. Before trying to compile, I applied a patch about drivers/net/Config.in posted to this list by Mr. Keith Owens. Long lines were wrapped by me. ... make[2]: Leaving directory `/usr/src/linux-2.4.5-ac21/fs/jffs' make -C jffs2 modules ... gcc -D__KERNEL__ -I/usr/src/linux-2.4.5-ac21/include -Wall \ -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer \ -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 \ -march=k6 -DMODULE -DMODVERSIONS \ -include /usr/src/linux-2.4.5-ac21/include/linux/modversions.h \ -c -o background.o background.c background.c: In function `jffs2_garbage_collect_trigger': background.c:57: `do_softirq_Rf0a529b7' undeclared (first use in \ this function) background.c:57: (Each undeclared identifier is reported only once background.c:57: for each function it appears in.) background.c: In function `jffs2_stop_garbage_collect_thread': background.c:87: `do_softirq_Rf0a529b7' undeclared (first use in this \ function) background.c: In function `jffs2_garbage_collect_thread': background.c:141: `do_softirq_Rf0a529b7' undeclared (first use in this \ function) make[2]: *** [background.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.5-ac21/fs/jffs2' make[1]: *** [_modsubdir_jffs2] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.5-ac21/fs' make: *** [_mod_fs] Error 2 -- Where there is a will, there is a way. [EMAIL PROTECTED] For the future of you and me! [EMAIL PROTECTED] fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
compile error about do_softirq in 2.4.5-ac21
I met following error while compiling 2.4.5-ac21: I know, of course, this error was reported several times as the compile problem of 2.4.6-preX, and there posted a patch about it by Mr. Keith Owens. I confirmed It had been applied to include/asm-i386/softirq.h of 2.4.5-ac21). But I see this in 2.4.5-ac21 again, and confused so much. I use Red Hat 7.1 (with up to latest errata updates + kernel-2.4.5-ac19, glibc-2.2.3, gcc-2.96-88, binutils-2.11.90.0.15, etc.) BTW, this error ocurred on both K6-II+ desktop(no-name) and Pentium III 500 MHZ noteboot(IBM ThkinPad 600X), and compiler was the same on both machines. Before trying to compile, I applied a patch about drivers/net/Config.in posted to this list by Mr. Keith Owens. Long lines were wrapped by me. ... make[2]: Leaving directory `/usr/src/linux-2.4.5-ac21/fs/jffs' make -C jffs2 modules ... gcc -D__KERNEL__ -I/usr/src/linux-2.4.5-ac21/include -Wall \ -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer \ -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 \ -march=k6 -DMODULE -DMODVERSIONS \ -include /usr/src/linux-2.4.5-ac21/include/linux/modversions.h \ -c -o background.o background.c background.c: In function `jffs2_garbage_collect_trigger': background.c:57: `do_softirq_Rf0a529b7' undeclared (first use in \ this function) background.c:57: (Each undeclared identifier is reported only once background.c:57: for each function it appears in.) background.c: In function `jffs2_stop_garbage_collect_thread': background.c:87: `do_softirq_Rf0a529b7' undeclared (first use in this \ function) background.c: In function `jffs2_garbage_collect_thread': background.c:141: `do_softirq_Rf0a529b7' undeclared (first use in this \ function) make[2]: *** [background.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.5-ac21/fs/jffs2' make[1]: *** [_modsubdir_jffs2] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.5-ac21/fs' make: *** [_mod_fs] Error 2 -- Where there is a will, there is a way. [EMAIL PROTECTED] For the future of you and me! [EMAIL PROTECTED] fingerprint = 1429 8AAF 8A2C 6043 DA2E BD4C 964C 2698 687D 4B7D - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
buz.c of 2.4.4
I met follwing erros which was workarounded by put define KMALLOC_MAXSIZE 131072 borrowed from af_unix.c of 2.4.3-ac14. But I'm convinced of this. below lines were wrapped by me for readabilities' sake. -D__KERNEL__ -I/usr/src/linux-2.4.4/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 \ -march=k6 -DMODULE -DMODVERSIONS -include \ /usr/src/linux-2.4.4/include/linux/modversions.h -c -o buz.o buz.c buz.c: In function `v4l_fbuffer_alloc': buz.c:188: `KMALLOC_MAXSIZE' undeclared (first use in this function) buz.c:188: (Each undeclared identifier is reported only once buz.c:188: for each function it appears in.) buz.c: In function `jpg_fbuffer_alloc': buz.c:262: `KMALLOC_MAXSIZE' undeclared (first use in this function) buz.c:256: warning: `alloc_contig' might be used uninitialized in this function buz.c: In function `jpg_fbuffer_free': buz.c:322: `KMALLOC_MAXSIZE' undeclared (first use in this function) buz.c:316: warning: `alloc_contig' might be used uninitialized in this function buz.c: In function `zoran_ioctl': buz.c:2837: `KMALLOC_MAXSIZE' undeclared (first use in this function) make[3]: *** [buz.o] Error 1 make[3]: Leaving directory `/usr/src/linux-2.4.4/drivers/media/video' make[2]: *** [_modsubdir_video] Error 2 make[2]: Leaving directory `/usr/src/linux-2.4.4/drivers/media' make[1]: *** [_modsubdir_media] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.4/drivers' make: *** [_mod_drivers] Error 2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.3-ac12
On Mon, 23 Apr 2001, Byeong-ryeol Kim wrote: > On Sun, 22 Apr 2001, Alan Cox wrote: > > > > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o > > > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved > > > > symbol rwsem_up_write_wake > > > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved > > > > symbol rwsem_down_write_failed > > > > > > Same thing with tdfx.o... > > > > "Works for me" as ever. What configuration options are you using. This sounds > > like some of the code is built with each kind of semaphore. > > > I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4 > rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III > 500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12 > are the same. > I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list > which seemed to be applied in gcc-2.95.4 CVS tree). I retried to compile 2.4.3-ac12 with Red Hat's 2.96-81(that of 7.1) without the patch previously applied. This time, I noticed strange thing.(I guess, it would not be a compiler problem). While doing 'depmod -ae -F /boot/System.map-2.4.3-ac12 2.4.3-ac12' there was no error as far as rwsem_* is concerned, but when doing simply 'depmod -ae', the result was the same as before.( the same kernel configuration, modutils is original 2.4.5-1 fetched from kernel site). 1) 'depmod -ae -F /boot/system.map-2.4.3-ac12 2.4.3-ac12' depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o depmod: __bad_udelay depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o depmod: get_hardsect_size 2) 'depmod -ae' depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o depmod: rwsem_up_write_wake depmod: rwsem_up_read_wake depmod: rwsem_down_write_failed depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o depmod: __bad_udelay depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o depmod: rwsem_up_read_wake depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o depmod: rwsem_up_write_wake depmod: rwsem_up_read_wake depmod: rwsem_down_write_failed depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o depmod: get_hardsect_size > > # > # Automatically generated make config: don't edit > # > CONFIG_X86=y > CONFIG_ISA=y > # CONFIG_SBUS is not set > CONFIG_UID16=y > > # > # Code maturity level options > # > CONFIG_EXPERIMENTAL=y > > # > # Loadable module support > # > CONFIG_MODULES=y > CONFIG_MODVERSIONS=y > CONFIG_KMOD=y > > # > # Processor type and features > # > # CONFIG_M386 is not set > # CONFIG_M486 is not set > # CONFIG_M586 is not set > # CONFIG_M586TSC is not set > # CONFIG_M586MMX is not set > # CONFIG_M686 is not set > # CONFIG_MPENTIUMIII is not set > # CONFIG_MPENTIUM4 is not
Re: Linux 2.4.3-ac12
On Sun, 22 Apr 2001, Alan Cox wrote: > > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o > > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved > > > symbol rwsem_up_write_wake > > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved > > > symbol rwsem_down_write_failed > > > > Same thing with tdfx.o... > > "Works for me" as ever. What configuration options are you using. This sounds > like some of the code is built with each kind of semaphore. I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4 rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III 500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12 are the same. I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list which seemed to be applied in gcc-2.95.4 CVS tree). BTW, I applied the follwing patch posted to this list: --- 2.4.3-ac12/include/asm-i386/compiler.h Sat Apr 21 22:56:03 2001 +++ 2.4.3-ac12/include/asm-i386/compiler.h Sat Apr 21 22:56:43 2001 @@ -0,0 +1,13 @@ +#ifndef __I386_COMPILER_H +#define __I386_COMPILER_H 1 + +/* Somewhere in the middle of the GCC 2.96 development cycle, we implemented + a mechanism by which the user can annotate likely branch directions and + expect the blocks to be reordered appropriately. Define __builtin_expect + to nothing for earlier compilers. */ + +#if __GNUC__ == 2 && __GNUC_MINOR__ < 96 +#define __builtin_expect(x, expected_value) (x) +#endif + +#endif /* __I386_COMPILER_H */ --- 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:38 2001 +++ 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:57 2001 @@ -38,6 +38,7 @@ #include #include +#include #include #include depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o depmod: rwsem_up_write_wake depmod: rwsem_up_read_wake depmod: rwsem_down_write_failed depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o depmod: __bad_udelay depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o depmod: rwsem_up_read_wake depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o depmod: rwsem_up_write_wake depmod: rwsem_up_read_wake depmod: rwsem_down_write_failed depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o depmod: get_hardsect_size # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUM4 is not set CONFIG_MK6=y # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y
Re: Linux 2.4.3-ac12
On Sun, 22 Apr 2001, Alan Cox wrote: Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved symbol rwsem_up_write_wake /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved symbol rwsem_down_write_failed Same thing with tdfx.o... Works for me as ever. What configuration options are you using. This sounds like some of the code is built with each kind of semaphore. I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4 rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III 500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12 are the same. I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list which seemed to be applied in gcc-2.95.4 CVS tree). BTW, I applied the follwing patch posted to this list: --- 2.4.3-ac12/include/asm-i386/compiler.h Sat Apr 21 22:56:03 2001 +++ 2.4.3-ac12/include/asm-i386/compiler.h Sat Apr 21 22:56:43 2001 @@ -0,0 +1,13 @@ +#ifndef __I386_COMPILER_H +#define __I386_COMPILER_H 1 + +/* Somewhere in the middle of the GCC 2.96 development cycle, we implemented + a mechanism by which the user can annotate likely branch directions and + expect the blocks to be reordered appropriately. Define __builtin_expect + to nothing for earlier compilers. */ + +#if __GNUC__ == 2 __GNUC_MINOR__ 96 +#define __builtin_expect(x, expected_value) (x) +#endif + +#endif /* __I386_COMPILER_H */ --- 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:38 2001 +++ 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:57 2001 @@ -38,6 +38,7 @@ #include asm/system.h #include asm/atomic.h +#include asm/compiler.h #include linux/wait.h #include linux/rwsem.h depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o depmod: rwsem_up_write_wake depmod: rwsem_up_read_wake depmod: rwsem_down_write_failed depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o depmod: __bad_udelay depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o depmod: rwsem_up_read_wake depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o depmod: rwsem_up_write_wake depmod: rwsem_up_read_wake depmod: rwsem_down_write_failed depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o depmod: get_hardsect_size # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUM4 is not set CONFIG_MK6=y # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_WP_WORKS_OK=y
Re: Linux 2.4.3-ac12
On Mon, 23 Apr 2001, Byeong-ryeol Kim wrote: On Sun, 22 Apr 2001, Alan Cox wrote: Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved symbol rwsem_up_write_wake /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved symbol rwsem_down_write_failed Same thing with tdfx.o... Works for me as ever. What configuration options are you using. This sounds like some of the code is built with each kind of semaphore. I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4 rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III 500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12 are the same. I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list which seemed to be applied in gcc-2.95.4 CVS tree). I retried to compile 2.4.3-ac12 with Red Hat's 2.96-81(that of 7.1) without the patch previously applied. This time, I noticed strange thing.(I guess, it would not be a compiler problem). While doing 'depmod -ae -F /boot/System.map-2.4.3-ac12 2.4.3-ac12' there was no error as far as rwsem_* is concerned, but when doing simply 'depmod -ae', the result was the same as before.( the same kernel configuration, modutils is original 2.4.5-1 fetched from kernel site). 1) 'depmod -ae -F /boot/system.map-2.4.3-ac12 2.4.3-ac12' depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o depmod: __bad_udelay depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o depmod: get_hardsect_size 2) 'depmod -ae' depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o depmod: rwsem_up_write_wake depmod: rwsem_up_read_wake depmod: rwsem_down_write_failed depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o depmod: __bad_udelay depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o depmod: rwsem_up_read_wake depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o depmod: rwsem_up_write_wake depmod: rwsem_up_read_wake depmod: rwsem_down_write_failed depmod: rwsem_down_read_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o depmod: rwsem_up_write_wake depmod: rwsem_down_write_failed depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o depmod: get_hardsect_size # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUM4 is not set CONFIG_MK6=y # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y
unresolved symbols of 2.4.3-ac11
I see follwing error messages while 'make modules_install' after
compiling 2.4.3-ac11 kernel.
make[1]: Entering directory `/usr/src/linux-2.4.3-ac11/arch/i386/lib'
make[1]: Nothing to be done for `modules_install'.
make[1]: Leaving directory `/usr/src/linux-2.4.3-ac11/arch/i386/lib'
cd /lib/modules/2.4.3-ac11; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.3-ac11; fi
depmod: *** Unresolved symbols \
in /lib/modules/2.4.3-ac11/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac11/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size
depmod: get_hardblocksize
I applied late ppp patch of Paul Mackerras posted to this list yesterday
or so(with my own patch about sk_chk_symbol into netsyms.c) and 3c90x(BC
series) patch(1.0.1i) of 3COM to vanilla 2.4.3-ac11 source.
# sh /usr/src/linux/scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux progress.plw.net 2.4.3-ac10 #7 Sat Apr 21 03:47:02 KST 2001 i586 unknown
Gnu C 2.95.3
Gnu make 3.79.1
binutils 2.11.90.0.5
util-linux 2.10s
mount 2.10r
modutils 2.4.5
e2fsprogs 1.19
reiserfsprogs 3.x.0j
pcmcia-cs 3.1.20
PPP2.4.0
isdn4k-utils 3.1beta7
Linux C Library2.2.3
Dynamic linker (ldd) 2.2.3
Procps 2.0.7
Net-tools 1.59
Console-tools 0.3.3
Sh-utils 2.0
Modules Loaded ip_conntrack_ftp ip_nat_ftp ipt_MASQUERADE ppp_async
ppp_generic nfsd lockd sunrpc parport_pc lp parport 3c90x iptable_mangle iptable_nat
ip_conntrack iptable_filter ip_tables md sb sb_lib uart401 sound soundcore
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
CONFIG_MK6=y
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_TSC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_TOSHIBA=m
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
#
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PM=y
# CONFIG_ACPI is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC1000=m
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCPROBE_ADDRESS=
CONFIG_MTD_DOCPROBE_HIGH=y
CONFIG_MTD_DOCPROBE_55AA=y
#
# RAM/ROM Device Drivers
#
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PMC551=m
CONFIG_MTD_PMC551_BUGFIX=y
# CONFIG_MTD_PMC551_DEBUG is not set
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
#
# Linearly Mapped Flash Device Drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
# CONFIG_MTD_JEDEC is not set
CONFIG_MTD_PHYSMAP=m
CONFIG_MTD_PHYSMAP_START=800
CONFIG_MTD_PHYSMAP_LEN=400
CONFIG_MTD_PHYSMAP_BUSWIDTH=2
#
# Drivers for chip mappings
#
# CONFIG_MTD_MIXMEM is not set
CONFIG_MTD_NORA=m
# CONFIG_MTD_OCTAGON is not set
unresolved symbols of 2.4.3-ac11
I see follwing error messages while 'make modules_install' after
compiling 2.4.3-ac11 kernel.
make[1]: Entering directory `/usr/src/linux-2.4.3-ac11/arch/i386/lib'
make[1]: Nothing to be done for `modules_install'.
make[1]: Leaving directory `/usr/src/linux-2.4.3-ac11/arch/i386/lib'
cd /lib/modules/2.4.3-ac11; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.3-ac11; fi
depmod: *** Unresolved symbols \
in /lib/modules/2.4.3-ac11/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac11/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size
depmod: get_hardblocksize
I applied late ppp patch of Paul Mackerras posted to this list yesterday
or so(with my own patch about sk_chk_symbol into netsyms.c) and 3c90x(BC
series) patch(1.0.1i) of 3COM to vanilla 2.4.3-ac11 source.
# sh /usr/src/linux/scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux progress.plw.net 2.4.3-ac10 #7 Sat Apr 21 03:47:02 KST 2001 i586 unknown
Gnu C 2.95.3
Gnu make 3.79.1
binutils 2.11.90.0.5
util-linux 2.10s
mount 2.10r
modutils 2.4.5
e2fsprogs 1.19
reiserfsprogs 3.x.0j
pcmcia-cs 3.1.20
PPP2.4.0
isdn4k-utils 3.1beta7
Linux C Library2.2.3
Dynamic linker (ldd) 2.2.3
Procps 2.0.7
Net-tools 1.59
Console-tools 0.3.3
Sh-utils 2.0
Modules Loaded ip_conntrack_ftp ip_nat_ftp ipt_MASQUERADE ppp_async
ppp_generic nfsd lockd sunrpc parport_pc lp parport 3c90x iptable_mangle iptable_nat
ip_conntrack iptable_filter ip_tables md sb sb_lib uart401 sound soundcore
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
CONFIG_MK6=y
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_TSC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_TOSHIBA=m
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
#
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PM=y
# CONFIG_ACPI is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC1000=m
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOC2001=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCPROBE_ADDRESS=
CONFIG_MTD_DOCPROBE_HIGH=y
CONFIG_MTD_DOCPROBE_55AA=y
#
# RAM/ROM Device Drivers
#
CONFIG_MTD_SLRAM=m
CONFIG_MTD_PMC551=m
CONFIG_MTD_PMC551_BUGFIX=y
# CONFIG_MTD_PMC551_DEBUG is not set
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
#
# Linearly Mapped Flash Device Drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
# CONFIG_MTD_JEDEC is not set
CONFIG_MTD_PHYSMAP=m
CONFIG_MTD_PHYSMAP_START=800
CONFIG_MTD_PHYSMAP_LEN=400
CONFIG_MTD_PHYSMAP_BUSWIDTH=2
#
# Drivers for chip mappings
#
# CONFIG_MTD_MIXMEM is not set
CONFIG_MTD_NORA=m
# CONFIG_MTD_OCTAGON is not set
Re: [PATCH] PPP update against 2.4.4-pre5
On Fri, 20 Apr 2001, Paul Mackerras wrote:
> Brown-paper bag time...
>
> The patch I sent earlier didn't include the accompanying changes to
> if_ppp.h and ppp_channel.h. Here they are.
>
> Paul.
>
> diff -urN linux/include/linux/if_ppp.h pmac/include/linux/if_ppp.h
> --- linux/include/linux/if_ppp.h Tue Mar 28 04:28:55 2000
> +++ pmac/include/linux/if_ppp.h Mon Mar 5 12:16:15 2001
> @@ -1,4 +1,4 @@
> -/* $Id: if_ppp.h,v 1.19 1999/03/31 06:07:57 paulus Exp $ */
> +/* $Id: if_ppp.h,v 1.21 2000/03/27 06:03:36 paulus Exp $ */
>
> /*
> * if_ppp.h - Point-to-Point Protocol definitions.
> @@ -21,7 +21,7 @@
> */
>
> /*
> - * ==FILEVERSION 2324==
> + * ==FILEVERSION 2724==
> *
> * NOTE TO MAINTAINERS:
> * If you modify this file at all, please set the above date.
> @@ -130,6 +130,8 @@
> #define PPPIOCSCOMPRESS _IOW('t', 77, struct ppp_option_data)
> #define PPPIOCGNPMODE_IOWR('t', 76, struct npioctl) /* get NP mode */
> #define PPPIOCSNPMODE_IOW('t', 75, struct npioctl) /* set NP mode */
> +#define PPPIOCSPASS _IOW('t', 71, struct sock_fprog) /* set pass filter */
> +#define PPPIOCSACTIVE_IOW('t', 70, struct sock_fprog) /* set active filt */
> #define PPPIOCGDEBUG _IOR('t', 65, int) /* Read debug level */
> #define PPPIOCSDEBUG _IOW('t', 64, int) /* Set debug level */
> #define PPPIOCGIDLE _IOR('t', 63, struct ppp_idle) /* get idle time */
> diff -urN linux/include/linux/ppp_channel.h pmac/include/linux/ppp_channel.h
> --- linux/include/linux/ppp_channel.h Mon Apr 2 02:20:35 2001
> +++ pmac/include/linux/ppp_channel.h Thu Apr 19 19:16:39 2001
> @@ -22,7 +22,6 @@
> #include
> #include
> #include
> -#include
>
> struct ppp_channel;
>
> @@ -32,7 +31,6 @@
> int (*start_xmit)(struct ppp_channel *, struct sk_buff *);
> /* Handle an ioctl call that has come in via /dev/ppp. */
> int (*ioctl)(struct ppp_channel *, unsigned int, unsigned long);
> -
> };
>
> struct ppp_channel {
> @@ -78,16 +76,6 @@
> * in the start_xmit and ioctl routines for the channel by the time
> * that ppp_unregister_channel returns.
> */
> -
> -/* The following are temporary compatibility stuff */
> -ssize_t ppp_channel_read(struct ppp_channel *chan, struct file *file,
> - char *buf, size_t count);
> -ssize_t ppp_channel_write(struct ppp_channel *chan, const char *buf,
> - size_t count);
> -unsigned int ppp_channel_poll(struct ppp_channel *chan, struct file *file,
> - poll_table *wait);
> -int ppp_channel_ioctl(struct ppp_channel *chan, unsigned int cmd,
> - unsigned long arg);
>
> #endif /* __KERNEL__ */
> #endif
I met 'unresolved symbol sk_chk_filter ...' after applying this patch
and rebooting.( with CONFIG_PPP_FILTER=y )
There shoud be folling lines in linux/net/netsyms.c or so:
#ifdef CONFIG_PPP_FILTER
EXPORT_SYMBOL(sk_chk_filter);
#endif
--
"Where there is a will, there is a way." [EMAIL PROTECTED]
For the future of you and me!hitel: jinbo21
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] PPP update against 2.4.4-pre5
On Fri, 20 Apr 2001, Paul Mackerras wrote:
Brown-paper bag time...
The patch I sent earlier didn't include the accompanying changes to
if_ppp.h and ppp_channel.h. Here they are.
Paul.
diff -urN linux/include/linux/if_ppp.h pmac/include/linux/if_ppp.h
--- linux/include/linux/if_ppp.h Tue Mar 28 04:28:55 2000
+++ pmac/include/linux/if_ppp.h Mon Mar 5 12:16:15 2001
@@ -1,4 +1,4 @@
-/* $Id: if_ppp.h,v 1.19 1999/03/31 06:07:57 paulus Exp $ */
+/* $Id: if_ppp.h,v 1.21 2000/03/27 06:03:36 paulus Exp $ */
/*
* if_ppp.h - Point-to-Point Protocol definitions.
@@ -21,7 +21,7 @@
*/
/*
- * ==FILEVERSION 2324==
+ * ==FILEVERSION 2724==
*
* NOTE TO MAINTAINERS:
* If you modify this file at all, please set the above date.
@@ -130,6 +130,8 @@
#define PPPIOCSCOMPRESS _IOW('t', 77, struct ppp_option_data)
#define PPPIOCGNPMODE_IOWR('t', 76, struct npioctl) /* get NP mode */
#define PPPIOCSNPMODE_IOW('t', 75, struct npioctl) /* set NP mode */
+#define PPPIOCSPASS _IOW('t', 71, struct sock_fprog) /* set pass filter */
+#define PPPIOCSACTIVE_IOW('t', 70, struct sock_fprog) /* set active filt */
#define PPPIOCGDEBUG _IOR('t', 65, int) /* Read debug level */
#define PPPIOCSDEBUG _IOW('t', 64, int) /* Set debug level */
#define PPPIOCGIDLE _IOR('t', 63, struct ppp_idle) /* get idle time */
diff -urN linux/include/linux/ppp_channel.h pmac/include/linux/ppp_channel.h
--- linux/include/linux/ppp_channel.h Mon Apr 2 02:20:35 2001
+++ pmac/include/linux/ppp_channel.h Thu Apr 19 19:16:39 2001
@@ -22,7 +22,6 @@
#include linux/list.h
#include linux/skbuff.h
#include linux/poll.h
-#include asm/atomic.h
struct ppp_channel;
@@ -32,7 +31,6 @@
int (*start_xmit)(struct ppp_channel *, struct sk_buff *);
/* Handle an ioctl call that has come in via /dev/ppp. */
int (*ioctl)(struct ppp_channel *, unsigned int, unsigned long);
-
};
struct ppp_channel {
@@ -78,16 +76,6 @@
* in the start_xmit and ioctl routines for the channel by the time
* that ppp_unregister_channel returns.
*/
-
-/* The following are temporary compatibility stuff */
-ssize_t ppp_channel_read(struct ppp_channel *chan, struct file *file,
- char *buf, size_t count);
-ssize_t ppp_channel_write(struct ppp_channel *chan, const char *buf,
- size_t count);
-unsigned int ppp_channel_poll(struct ppp_channel *chan, struct file *file,
- poll_table *wait);
-int ppp_channel_ioctl(struct ppp_channel *chan, unsigned int cmd,
- unsigned long arg);
#endif /* __KERNEL__ */
#endif
I met 'unresolved symbol sk_chk_filter ...' after applying this patch
and rebooting.( with CONFIG_PPP_FILTER=y )
There shoud be folling lines in linux/net/netsyms.c or so:
#ifdef CONFIG_PPP_FILTER
EXPORT_SYMBOL(sk_chk_filter);
#endif
--
"Where there is a will, there is a way." [EMAIL PROTECTED]
For the future of you and me!hitel: jinbo21
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
a patch about iovirt in 2.4.3-ac6
1. I could avoid warnings about '__io_virt_debug' while performing 'make modudles_install' and successfuly load modules with folowing patch: --- linux/kernel/ksyms.c.orig Mon Apr 16 02:26:35 2001 +++ linux/kernel/ksyms.cSun Apr 15 21:34:51 2001 @@ -56,6 +56,10 @@ #include #endif +#ifdef CONFIG_DEBUG_IOVIRT +#include +#endif + extern void set_device_ro(kdev_t dev,int flag); extern void *sys_call_table; @@ -536,3 +540,6 @@ EXPORT_SYMBOL(tasklist_lock); EXPORT_SYMBOL(pidhash); +#ifdef CONFIG_DEBUG_IOVIRT +EXPORT_SYMBOL(__io_virt_debug); +#endif 2. BTW, cs46xx driver (module) of 2.4.3-ac6 doesn't work well with CONFIG_INPUT_CS461X set. If it were set, since 'cs46xx' is dependent on 'gameport' instead of 'ac97_codec' module while being loaded, I couldn't listen any sound. The workaround with this problem was to unset CONFIG_INPUT_CS461X. * Hardware My laptop is IBM ThinkPad 600X(26459EJ, US keyboard, PIII 500, DVD ROM drive, etc.) * Result of ver_linux Linux mobile.nowhere.net 2.4.3-ac6 #6 Sun Apr 15 21:42:36 KST 2001 i686 unknown Gnu C 2.95.3 Gnu make 3.79.1 binutils 2.11.90.0.5 util-linux 2.11a mount 2.11a modutils 2.4.5 e2fsprogs 1.19 reiserfsprogs 3.x.0b pcmcia-cs 3.1.25 PPP2.4.0 Linux C Library2.2.3 Dynamic linker (ldd) 2.2.3 Procps 2.0.7 Net-tools 1.59 Console-tools 0.3.3 Sh-utils 2.0 Modules Loaded nfs lockd sunrpc smapi superio thinkpad ide-cd cdrom parport_pc lp parport tulip_cb cb_enabler ds i82365 pcmcia_core iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables cs46xx soundcore ac97_codec uhci usbcore nls_euc-kr nls_cp949 vfat fat md * Kernel configuration # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_TOSHIBA=m CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_SMP is not set CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # # General setup # CONFIG_NET=y # CONFIG_VISWS is not set CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_PM=y CONFIG_ACPI=y CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_APM_DO_ENABLE=y CONFIG_APM_CPU_IDLE=y CONFIG_APM_DISPLAY_BLANK=y # CONFIG_APM_RTC_IS_GMT is not set CONFIG_APM_ALLOW_INTS=y # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # Memory Technology Devices (MTD) # CONFIG_MTD=m # CONFIG_MTD_DEBUG is not set # # Disk-On-Chip Device Drivers # CONFIG_MTD_DOC1000=m CONFIG_MTD_DOC2000=m CONFIG_MTD_DOC2001=m CONFIG_MTD_DOCPROBE=m CONFIG_MTD_DOCPROBE_ADDRESS= CONFIG_MTD_DOCPROBE_HIGH=y CONFIG_MTD_DOCPROBE_55AA=y # # RAM/ROM Device Drivers # CONFIG_MTD_SLRAM=m CONFIG_MTD_PMC551=m # CONFIG_MTD_PMC551_BUGFIX is not set # CONFIG_MTD_PMC551_DEBUG is not set CONFIG_MTD_MTDRAM=m CONFIG_MTDRAM_TOTAL_SIZE=4096 CONFIG_MTDRAM_ERASE_SIZE=128 # # Linearly Mapped Flash Device Drivers # CONFIG_MTD_CFI=m CONFIG_MTD_CFI_INTELEXT=m CONFIG_MTD_CFI_AMDSTD=m CONFIG_MTD_RAM=m CONFIG_MTD_ROM=m # CONFIG_MTD_JEDEC is not set CONFIG_MTD_PHYSMAP=m CONFIG_MTD_PHYSMAP_START=800 CONFIG_MTD_PHYSMAP_LEN=400 CONFIG_MTD_PHYSMAP_BUSWIDTH=2 # # Drivers for chip mappings # # CONFIG_MTD_MIXMEM is not set CONFIG_MTD_NORA=m # CONFIG_MTD_OCTAGON is not set CONFIG_MTD_PNC2000=m CONFIG_MTD_RPXLITE=m # CONFIG_MTD_VMAX is not set # # User modules and translation layers for MTD devices # CONFIG_MTD_CHAR=m CONFIG_MTD_BLOCK=m CONFIG_FTL=m CONFIG_NFTL=m CONFIG_NFTL_RW=y # #
a patch about iovirt in 2.4.3-ac6
1. I could avoid warnings about '__io_virt_debug' while performing 'make modudles_install' and successfuly load modules with folowing patch: --- linux/kernel/ksyms.c.orig Mon Apr 16 02:26:35 2001 +++ linux/kernel/ksyms.cSun Apr 15 21:34:51 2001 @@ -56,6 +56,10 @@ #include linux/kmod.h #endif +#ifdef CONFIG_DEBUG_IOVIRT +#include asm/io.h +#endif + extern void set_device_ro(kdev_t dev,int flag); extern void *sys_call_table; @@ -536,3 +540,6 @@ EXPORT_SYMBOL(tasklist_lock); EXPORT_SYMBOL(pidhash); +#ifdef CONFIG_DEBUG_IOVIRT +EXPORT_SYMBOL(__io_virt_debug); +#endif 2. BTW, cs46xx driver (module) of 2.4.3-ac6 doesn't work well with CONFIG_INPUT_CS461X set. If it were set, since 'cs46xx' is dependent on 'gameport' instead of 'ac97_codec' module while being loaded, I couldn't listen any sound. The workaround with this problem was to unset CONFIG_INPUT_CS461X. * Hardware My laptop is IBM ThinkPad 600X(26459EJ, US keyboard, PIII 500, DVD ROM drive, etc.) * Result of ver_linux Linux mobile.nowhere.net 2.4.3-ac6 #6 Sun Apr 15 21:42:36 KST 2001 i686 unknown Gnu C 2.95.3 Gnu make 3.79.1 binutils 2.11.90.0.5 util-linux 2.11a mount 2.11a modutils 2.4.5 e2fsprogs 1.19 reiserfsprogs 3.x.0b pcmcia-cs 3.1.25 PPP2.4.0 Linux C Library2.2.3 Dynamic linker (ldd) 2.2.3 Procps 2.0.7 Net-tools 1.59 Console-tools 0.3.3 Sh-utils 2.0 Modules Loaded nfs lockd sunrpc smapi superio thinkpad ide-cd cdrom parport_pc lp parport tulip_cb cb_enabler ds i82365 pcmcia_core iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables cs46xx soundcore ac97_codec uhci usbcore nls_euc-kr nls_cp949 vfat fat md * Kernel configuration # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_TOSHIBA=m CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_SMP is not set CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y # # General setup # CONFIG_NET=y # CONFIG_VISWS is not set CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_PM=y CONFIG_ACPI=y CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_APM_DO_ENABLE=y CONFIG_APM_CPU_IDLE=y CONFIG_APM_DISPLAY_BLANK=y # CONFIG_APM_RTC_IS_GMT is not set CONFIG_APM_ALLOW_INTS=y # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # Memory Technology Devices (MTD) # CONFIG_MTD=m # CONFIG_MTD_DEBUG is not set # # Disk-On-Chip Device Drivers # CONFIG_MTD_DOC1000=m CONFIG_MTD_DOC2000=m CONFIG_MTD_DOC2001=m CONFIG_MTD_DOCPROBE=m CONFIG_MTD_DOCPROBE_ADDRESS= CONFIG_MTD_DOCPROBE_HIGH=y CONFIG_MTD_DOCPROBE_55AA=y # # RAM/ROM Device Drivers # CONFIG_MTD_SLRAM=m CONFIG_MTD_PMC551=m # CONFIG_MTD_PMC551_BUGFIX is not set # CONFIG_MTD_PMC551_DEBUG is not set CONFIG_MTD_MTDRAM=m CONFIG_MTDRAM_TOTAL_SIZE=4096 CONFIG_MTDRAM_ERASE_SIZE=128 # # Linearly Mapped Flash Device Drivers # CONFIG_MTD_CFI=m CONFIG_MTD_CFI_INTELEXT=m CONFIG_MTD_CFI_AMDSTD=m CONFIG_MTD_RAM=m CONFIG_MTD_ROM=m # CONFIG_MTD_JEDEC is not set CONFIG_MTD_PHYSMAP=m CONFIG_MTD_PHYSMAP_START=800 CONFIG_MTD_PHYSMAP_LEN=400 CONFIG_MTD_PHYSMAP_BUSWIDTH=2 # # Drivers for chip mappings # # CONFIG_MTD_MIXMEM is not set CONFIG_MTD_NORA=m # CONFIG_MTD_OCTAGON is not set CONFIG_MTD_PNC2000=m CONFIG_MTD_RPXLITE=m # CONFIG_MTD_VMAX is not set # # User modules and translation layers for MTD devices # CONFIG_MTD_CHAR=m CONFIG_MTD_BLOCK=m CONFIG_FTL=m CONFIG_NFTL=m
2.4.2-ac18 and lvm_0.9
I met following errors errors when compiling lvm_0.9(lvm-0.9 in latest Rawhide) with gcc-2.95.3-test5 under kernel-2.4.2-ac18 and glibc-2.2.2. make[1]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools' make[2]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools/lib' make[3]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools/lib' gcc -c -pipe -D_GNU_SOURCE -O2 -march=i686 -mcpu=i686 -pipe -Wall \ -I../../tools/lib -I../../tools -o basename.o basename.c In file included from /usr/include/linux/prefetch.h:13, from /usr/include/linux/list.h:6, from ../../tools/lib/lvm.h:98, from ../../tools/lib/liblvm.h:90, from basename.c:34: /usr/include/asm/processor.h:47: parse error before `u16' /usr/include/asm/processor.h:47: warning: no semicolon at end of struct \ or union /usr/include/asm/processor.h:56: parse error before `}' make[3]: *** [basename.o] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/LVM/0.9/tools/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/redhat/BUILD/LVM/0.9/tools/lib' make[2]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools/man8' make[3]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools/man8' make[3]: Leaving directory `/usr/src/redhat/BUILD/LVM/0.9/tools/man8' make[2]: Leaving directory `/usr/src/redhat/BUILD/LVM/0.9/tools/man8' make[2]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools' gcc -c -pipe -D_GNU_SOURCE -O2 -march=i686 -mcpu=i686 -pipe -Wall \ -I../tools/lib -I../tools -o e2fsadm.o e2fsadm.c In file included from /usr/include/linux/prefetch.h:13, from /usr/include/linux/list.h:6, from ../tools/lib/lvm.h:98, from ../tools/lib/liblvm.h:90, from ../tools/lvm_user.h:44, from e2fsadm.c:45: /usr/include/asm/processor.h:47: parse error before `u16' /usr/include/asm/processor.h:47: warning: no semicolon at end of \ struct or union /usr/include/asm/processor.h:56: parse error before `}' make[2]: *** [e2fsadm.o] Error 1 This is true to 2.4.2-20, too. After applying folling patch to kernel source, the compile process of lvm-0.9 went through flawlessly. I guess it is a typo introduced into 2.4.2-ac18 or so. --- linux/include/asm/processor.h.orig Tue Mar 13 03:55:41 2001 +++ linux/include/asm/processor.h Tue Mar 13 03:52:16 2001 @@ -44,7 +44,7 @@ charx86_model_id[64]; int x86_cache_size; /* in KB - valid for CPUS which support this call */ - u16 clockmul;/* Clock multiplier */ + __u16 clockmul;/* Clock multiplier */ int fdiv_bug; int f00f_bug; int coma_bug; -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.2-ac18 and lvm_0.9
I met following errors errors when compiling lvm_0.9(lvm-0.9 in latest Rawhide) with gcc-2.95.3-test5 under kernel-2.4.2-ac18 and glibc-2.2.2. make[1]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools' make[2]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools/lib' make[3]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools/lib' gcc -c -pipe -D_GNU_SOURCE -O2 -march=i686 -mcpu=i686 -pipe -Wall \ -I../../tools/lib -I../../tools -o basename.o basename.c In file included from /usr/include/linux/prefetch.h:13, from /usr/include/linux/list.h:6, from ../../tools/lib/lvm.h:98, from ../../tools/lib/liblvm.h:90, from basename.c:34: /usr/include/asm/processor.h:47: parse error before `u16' /usr/include/asm/processor.h:47: warning: no semicolon at end of struct \ or union /usr/include/asm/processor.h:56: parse error before `}' make[3]: *** [basename.o] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/LVM/0.9/tools/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/redhat/BUILD/LVM/0.9/tools/lib' make[2]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools/man8' make[3]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools/man8' make[3]: Leaving directory `/usr/src/redhat/BUILD/LVM/0.9/tools/man8' make[2]: Leaving directory `/usr/src/redhat/BUILD/LVM/0.9/tools/man8' make[2]: Entering directory `/usr/src/redhat/BUILD/LVM/0.9/tools' gcc -c -pipe -D_GNU_SOURCE -O2 -march=i686 -mcpu=i686 -pipe -Wall \ -I../tools/lib -I../tools -o e2fsadm.o e2fsadm.c In file included from /usr/include/linux/prefetch.h:13, from /usr/include/linux/list.h:6, from ../tools/lib/lvm.h:98, from ../tools/lib/liblvm.h:90, from ../tools/lvm_user.h:44, from e2fsadm.c:45: /usr/include/asm/processor.h:47: parse error before `u16' /usr/include/asm/processor.h:47: warning: no semicolon at end of \ struct or union /usr/include/asm/processor.h:56: parse error before `}' make[2]: *** [e2fsadm.o] Error 1 This is true to 2.4.2-20, too. After applying folling patch to kernel source, the compile process of lvm-0.9 went through flawlessly. I guess it is a typo introduced into 2.4.2-ac18 or so. --- linux/include/asm/processor.h.orig Tue Mar 13 03:55:41 2001 +++ linux/include/asm/processor.h Tue Mar 13 03:52:16 2001 @@ -44,7 +44,7 @@ charx86_model_id[64]; int x86_cache_size; /* in KB - valid for CPUS which support this call */ - u16 clockmul;/* Clock multiplier */ + __u16 clockmul;/* Clock multiplier */ int fdiv_bug; int f00f_bug; int coma_bug; -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ignore
Is there any event lately in vger kernel-list? I haven't been being received mails from it since Dec 17. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
ignore
Is there any event lately in vger kernel-list? I haven't been being received mails from it since Dec 17. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000, Klaus Naumann wrote: > Byeong-ryeol Kim wrote: > > > > On Thu, 26 Oct 2000, Klaus Naumann wrote: > > > > > I was having some little trouble with the QLOGIC Fibre Channel SCSI > > > cards. > > > The issue is, that I have a box with an internal SCSI controller/disk > > > and a QLOGIC card which is connected to an external RAID. The probelm > > > is, that the internal disk is my root disk but is the second in the > > > chain (sdb) after bootup. This gives a lot of problems, because it's > > > impossible to get the system to boot (LILO isn't working). > > > Since I've modified the hosts.c it's working perfectly (at least the > > > order is better now). Patch is attached. > > > Can anyone give a comment on that please ? > > > > > > Hello, > > Your patch would be good, but there is another simple method. > > Did you happen to make the BIOS of Qlogic FC adapter enable to > > boot the machine? > > If so, while POST, timely hit 'Ctrl + Q', and disable boot > > ability in BIOS setting of it. > > No, I have the bios of the controller disabled. > The problem with that is that on boot up (for lilo) the internal disk > is disk number one. But when I'm in the system and want to install lilo > it's disk number two - that's what lilo is complaining about on boot up. > (By spewing out an L and a 01 01 01 01 and so on). > Activating the bios of the QLOGIC (to make the internal disk appear > to be the 2nd one on bootup) didn't solve the problem too - I simply > got a message saying I should insert a system disk ;) Aha, I forgot to describe about making qlogic drivers as a module. While I had been setting and testing SAN switch(Brocade, Gadzoox), RAID with Qlogic 2100(or 2200A), I had the same experience that you described in the previous mail, and solved the problem by patching drivers/scsi/hosts.c as you did. It was a good solution. But, I became aware of the convenience and flexibility of modular drivers(or initrd) in this case. Because, I thought, whenever I do the same test or benchmarking, rebooting the system each is terrible. In that method, I experienced no problem such that you described in the previous E-mail. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000, Klaus Naumann wrote: > I was having some little trouble with the QLOGIC Fibre Channel SCSI > cards. > The issue is, that I have a box with an internal SCSI controller/disk > and a QLOGIC card which is connected to an external RAID. The probelm > is, that the internal disk is my root disk but is the second in the > chain (sdb) after bootup. This gives a lot of problems, because it's > impossible to get the system to boot (LILO isn't working). > Since I've modified the hosts.c it's working perfectly (at least the > order is better now). Patch is attached. > Can anyone give a comment on that please ? Hello, Your patch would be good, but there is another simple method. Did you happen to make the BIOS of Qlogic FC adapter enable to boot the machine? If so, while POST, timely hit 'Ctrl + Q', and disable boot ability in BIOS setting of it. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000, Klaus Naumann wrote: I was having some little trouble with the QLOGIC Fibre Channel SCSI cards. The issue is, that I have a box with an internal SCSI controller/disk and a QLOGIC card which is connected to an external RAID. The probelm is, that the internal disk is my root disk but is the second in the chain (sdb) after bootup. This gives a lot of problems, because it's impossible to get the system to boot (LILO isn't working). Since I've modified the hosts.c it's working perfectly (at least the order is better now). Patch is attached. Can anyone give a comment on that please ? Hello, Your patch would be good, but there is another simple method. Did you happen to make the BIOS of Qlogic FC adapter enable to boot the machine? If so, while POST, timely hit 'Ctrl + Q', and disable boot ability in BIOS setting of it. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000, Klaus Naumann wrote: Byeong-ryeol Kim wrote: On Thu, 26 Oct 2000, Klaus Naumann wrote: I was having some little trouble with the QLOGIC Fibre Channel SCSI cards. The issue is, that I have a box with an internal SCSI controller/disk and a QLOGIC card which is connected to an external RAID. The probelm is, that the internal disk is my root disk but is the second in the chain (sdb) after bootup. This gives a lot of problems, because it's impossible to get the system to boot (LILO isn't working). Since I've modified the hosts.c it's working perfectly (at least the order is better now). Patch is attached. Can anyone give a comment on that please ? Hello, Your patch would be good, but there is another simple method. Did you happen to make the BIOS of Qlogic FC adapter enable to boot the machine? If so, while POST, timely hit 'Ctrl + Q', and disable boot ability in BIOS setting of it. No, I have the bios of the controller disabled. The problem with that is that on boot up (for lilo) the internal disk is disk number one. But when I'm in the system and want to install lilo it's disk number two - that's what lilo is complaining about on boot up. (By spewing out an L and a 01 01 01 01 and so on). Activating the bios of the QLOGIC (to make the internal disk appear to be the 2nd one on bootup) didn't solve the problem too - I simply got a message saying I should insert a system disk ;) Aha, I forgot to describe about making qlogic drivers as a module. While I had been setting and testing SAN switch(Brocade, Gadzoox), RAID with Qlogic 2100(or 2200A), I had the same experience that you described in the previous mail, and solved the problem by patching drivers/scsi/hosts.c as you did. It was a good solution. But, I became aware of the convenience and flexibility of modular drivers(or initrd) in this case. Because, I thought, whenever I do the same test or benchmarking, rebooting the system each is terrible. In that method, I experienced no problem such that you described in the previous E-mail. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
