Re: Linux 2.6.13-rc2 (build error with no CONFIG_HOTPLUG_PCI)
Linus Torvalds wrote: Ok, -rc3 is pretty small, with the bulk of the diff being some defconfig updates, and cleanup of xtensa (notably removal of another copy of zlib). Greg Kroah-Hartman: PCI: clean up dynamic pci id logic PCI: Fix up PCI routing in parent bridge Without CONFIG_HOTPLUG and CONFIG_HOTPLUG_PCI, I got this: CC drivers/pci/pci-driver.o drivers/pci/pci-driver.c: In function `pci_match_device': drivers/pci/pci-driver.c:156: error: dereferencing pointer to incomplete type drivers/pci/pci-driver.c:156: warning: type defaults to `int' in declaration of `type name' drivers/pci/pci-driver.c:156: error: request for member `node' in something not a structure or union drivers/pci/pci-driver.c:156: warning: type defaults to `int' in declaration of `__mptr' drivers/pci/pci-driver.c:156: warning: initialization from incompatible pointer type [snipped similar errors/warnings] make[2]: *** [drivers/pci/pci-driver.o] Error 1 make[1]: *** [drivers/pci] Error 2 make: *** [drivers] Error 2 Setting CONFIG_HOTPLUG=y and CONFIG_HOTPLUG_PCI=y allowed 2.6.13-rc2 to build/boot/run. Steven -- This e-mail contains no programmatic content requiring independent ADC review. - 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.6.13-rc2 (build error with no CONFIG_HOTPLUG_PCI)
Linus Torvalds wrote: Ok, -rc3 is pretty small, with the bulk of the diff being some defconfig updates, and cleanup of xtensa (notably removal of another copy of zlib). Greg Kroah-Hartman: PCI: clean up dynamic pci id logic PCI: Fix up PCI routing in parent bridge Without CONFIG_HOTPLUG and CONFIG_HOTPLUG_PCI, I got this: CC drivers/pci/pci-driver.o drivers/pci/pci-driver.c: In function `pci_match_device': drivers/pci/pci-driver.c:156: error: dereferencing pointer to incomplete type drivers/pci/pci-driver.c:156: warning: type defaults to `int' in declaration of `type name' drivers/pci/pci-driver.c:156: error: request for member `node' in something not a structure or union drivers/pci/pci-driver.c:156: warning: type defaults to `int' in declaration of `__mptr' drivers/pci/pci-driver.c:156: warning: initialization from incompatible pointer type [snipped similar errors/warnings] make[2]: *** [drivers/pci/pci-driver.o] Error 1 make[1]: *** [drivers/pci] Error 2 make: *** [drivers] Error 2 Setting CONFIG_HOTPLUG=y and CONFIG_HOTPLUG_PCI=y allowed 2.6.13-rc2 to build/boot/run. Steven -- This e-mail contains no programmatic content requiring independent ADC review. - 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: 2.6.12-rc3 compile error in aic7xxx_osm.c
Martin J. Bligh wrote: drivers/scsi/aic7xxx/aic7xxx_osm.c: In function `ahc_linux_init': drivers/scsi/aic7xxx/aic7xxx_osm.c:3608: parse error before `int' drivers/scsi/aic7xxx/aic7xxx_osm.c:3609: `rc' undeclared (first use in this function) drivers/scsi/aic7xxx/aic7xxx_osm.c:3609: (Each undeclared identifier is reported only once drivers/scsi/aic7xxx/aic7xxx_osm.c:3609: for each function it appears in.) drivers/scsi/aic7xxx/aic7xxx_osm.c: At top level: drivers/scsi/aic7xxx/aic7xxx_osm.c:744: warning: `ahc_linux_detect' defined but not used Looks fixed in Linus' current tree: -- commit 858eaca169ed5e7b1b14eebb889323e75a02af0e tree 385e241e0cc18794b8d8b70095181e2578bee14c parent a2755a80f40e5794ddc20e00f781af9d6320fafb author James Bottomley <[EMAIL PROTECTED]> Thu, 21 Apr 2005 21:35:45 -0700 committer Linus Torvalds <[EMAIL PROTECTED]> Thu, 21 Apr 2005 21:35:45 -0700 [PATCH] Fix aic7xxx_osm.c compile with older gcc's My version of gcc doesn't warn about this error (declaration in the middle of a set of statements). The fix is simple (this also corrects return code; for init functions it should be zero or error). -- Steven - 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: 2.6.12-rc3 compile error in aic7xxx_osm.c
Martin J. Bligh wrote: drivers/scsi/aic7xxx/aic7xxx_osm.c: In function `ahc_linux_init': drivers/scsi/aic7xxx/aic7xxx_osm.c:3608: parse error before `int' drivers/scsi/aic7xxx/aic7xxx_osm.c:3609: `rc' undeclared (first use in this function) drivers/scsi/aic7xxx/aic7xxx_osm.c:3609: (Each undeclared identifier is reported only once drivers/scsi/aic7xxx/aic7xxx_osm.c:3609: for each function it appears in.) drivers/scsi/aic7xxx/aic7xxx_osm.c: At top level: drivers/scsi/aic7xxx/aic7xxx_osm.c:744: warning: `ahc_linux_detect' defined but not used Looks fixed in Linus' current tree: -- commit 858eaca169ed5e7b1b14eebb889323e75a02af0e tree 385e241e0cc18794b8d8b70095181e2578bee14c parent a2755a80f40e5794ddc20e00f781af9d6320fafb author James Bottomley [EMAIL PROTECTED] Thu, 21 Apr 2005 21:35:45 -0700 committer Linus Torvalds [EMAIL PROTECTED] Thu, 21 Apr 2005 21:35:45 -0700 [PATCH] Fix aic7xxx_osm.c compile with older gcc's My version of gcc doesn't warn about this error (declaration in the middle of a set of statements). The fix is simple (this also corrects return code; for init functions it should be zero or error). -- Steven - 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: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
On Tuesday 19 April 2005 05:38 pm, Linus Torvalds wrote: > > On Tue, 19 Apr 2005, Steven Cole wrote: > > > > I wasn't complaining about the 4 minutes, just the lack of feedback > > during the majority of that time. And most of it was after the last > > patching file message. > > That should be exactly the thing that the new "read-tree -m" fixes. > > Before, when you read in a new tree (which is what you do when you update > to somebody elses version), git would throw all the cached information > away, and so you'd end up doing a "checkout-cache -f -a" that re-wrote > every single checked-out file, followed by "update-cache --refresh" that > then re-created the cache for every single file. > > With the new read-tree, the same sequence (assuming you have the "-m" > flag to tell read-tree to merge the cache information) will now only write > out and re-check the files that actually changed due to the update or > merge. > > So that last phase should go from minutes to seconds - instead of checking > 17,000+ files, you'd end up checking maybe a few hundred for most "normal" > updates. > > For example, updating all the way from the git root (ie plain 2.6.12-rc2) > to the current head, only 577 files have changed, and the rest (16,740) > should never be touched at all. > > You can see why doing just the 577 instead of the full 17,317 might speed > things up a bit ;) > > Linus Cool. Petr, I hope this works like this with your tools tomorrow. > > PS. Of course, right now it probably does make sense to waste some time > occasionally, and run "fsck-cache $(cat .git/HEAD)" every once in a while. > Just in case.. > > Sounds like a good thing to schedule for $WEEHOUR. Steven - 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: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
On Tuesday 19 April 2005 04:38 pm, Linus Torvalds wrote: > > On Tue, 19 Apr 2005, Steven Cole wrote: > > > > But perhaps a progress bar right about here might be > > a good thing for the terminally impatient. > > > > real3m54.909s > > user0m14.835s > > sys 0m10.587s > > > > 4 minutes might be long enough to cause some folks to lose hope. > > Well, the real operations took only 15 seconds. What kind of horribe > person are you, that you don't have all of the kernel in your disk cache > already? Shame on you. > > Or was the 4 minutes for downloading all the objest too? Yes, I was using a very recent version of the pasky tools, I had created the repo this morning with git init YOUR_RSYC_URL_FOR_LINUX-2.6. I did time git pull origin and watched the fur fly. Then, the flurry of patching file blah messages, followed by a rather pregnant pause after the last patching message. I wasn't complaining about the 4 minutes, just the lack of feedback during the majority of that time. And most of it was after the last patching file message. > > Anyway, it looks like you are using pasky's scripts, and the old > "patch-based" upgrade at that. You certainly will _not_ see the > > [many files patched] > patching file mm/mmap.c > .. > > if you use a real git merge. That's probable be the real problem here. > > Real merges have no patches taking place _anywhere_. And they take about > half a second. Doing an "update" of your tree should _literally_ boil down > to > > # > # "repo" needs to point to the repo we update from > # > rsync -avz --ignore-existing $repo/objects/. .git/objects/. > rsync -L $repo/HEAD .git/NEW_HEAD || exit 1 > read-tree -m $(cat .git/NEW_HEAD) || exit 1 > checkout-cache -f -a > update-cache --refresh > mv .git/NEW_HEAD .git/HEAD > > and if it does anything else, it's literally broken. Btw, the above does > need my "read-tree -m" thing which I committed today. > > (CAREFUL: the above is not a good script, because it _will_ just overwrite > all your old contents with the stuff you updated to. You should thus not > actually use something like this, but a "git update" should literally end > up doing the above operations in the end, and just add proper checking). > > And if that takes 4 minutes, you've got problems. > > Just say no to patches. > > Linus > > PS: If you want a clean tree without any old files or anything else, for > that matter, you can then do a "show-files -z --others | xargs -0 rm", but > be careful: that will blow away _anything_ that wasn't revision controlled > with git. So don't blame me if your pr0n collection is gone afterwards. > OK. I may try some of this tomorrow from work, where I have a fat pipe. I'm on dialup from home, and I suspect not very many folks want to hear the sad tale of how long it takes to get the kernel over 56k dialup. Steven - 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: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Linus Torvalds wrote: On Tue, 19 Apr 2005, Greg KH wrote: Nice, it looks like the merge of this tree, and my usb tree worked just fine. Yup, it all seems to work out. [many files patched] patching file mm/mmap.c patching file net/bridge/br_sysfs_if.c patching file scripts/ver_linux --^ Hey, that's my patch! Last...and least. But perhaps a progress bar right about here might be a good thing for the terminally impatient. real3m54.909s user0m14.835s sys 0m10.587s 4 minutes might be long enough to cause some folks to lose hope. Steven - 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: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Linus Torvalds wrote: On Tue, 19 Apr 2005, Greg KH wrote: Nice, it looks like the merge of this tree, and my usb tree worked just fine. Yup, it all seems to work out. [many files patched] patching file mm/mmap.c patching file net/bridge/br_sysfs_if.c patching file scripts/ver_linux --^ Hey, that's my patch! Last...and least. But perhaps a progress bar right about here might be a good thing for the terminally impatient. real3m54.909s user0m14.835s sys 0m10.587s 4 minutes might be long enough to cause some folks to lose hope. Steven - 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: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
On Tuesday 19 April 2005 04:38 pm, Linus Torvalds wrote: On Tue, 19 Apr 2005, Steven Cole wrote: But perhaps a progress bar right about here might be a good thing for the terminally impatient. real3m54.909s user0m14.835s sys 0m10.587s 4 minutes might be long enough to cause some folks to lose hope. Well, the real operations took only 15 seconds. What kind of horribe person are you, that you don't have all of the kernel in your disk cache already? Shame on you. Or was the 4 minutes for downloading all the objest too? Yes, I was using a very recent version of the pasky tools, I had created the repo this morning with git init YOUR_RSYC_URL_FOR_LINUX-2.6. I did time git pull origin and watched the fur fly. Then, the flurry of patching file blah messages, followed by a rather pregnant pause after the last patching message. I wasn't complaining about the 4 minutes, just the lack of feedback during the majority of that time. And most of it was after the last patching file message. Anyway, it looks like you are using pasky's scripts, and the old patch-based upgrade at that. You certainly will _not_ see the [many files patched] patching file mm/mmap.c .. if you use a real git merge. That's probable be the real problem here. Real merges have no patches taking place _anywhere_. And they take about half a second. Doing an update of your tree should _literally_ boil down to # # repo needs to point to the repo we update from # rsync -avz --ignore-existing $repo/objects/. .git/objects/. rsync -L $repo/HEAD .git/NEW_HEAD || exit 1 read-tree -m $(cat .git/NEW_HEAD) || exit 1 checkout-cache -f -a update-cache --refresh mv .git/NEW_HEAD .git/HEAD and if it does anything else, it's literally broken. Btw, the above does need my read-tree -m thing which I committed today. (CAREFUL: the above is not a good script, because it _will_ just overwrite all your old contents with the stuff you updated to. You should thus not actually use something like this, but a git update should literally end up doing the above operations in the end, and just add proper checking). And if that takes 4 minutes, you've got problems. Just say no to patches. Linus PS: If you want a clean tree without any old files or anything else, for that matter, you can then do a show-files -z --others | xargs -0 rm, but be careful: that will blow away _anything_ that wasn't revision controlled with git. So don't blame me if your pr0n collection is gone afterwards. OK. I may try some of this tomorrow from work, where I have a fat pipe. I'm on dialup from home, and I suspect not very many folks want to hear the sad tale of how long it takes to get the kernel over 56k dialup. Steven - 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: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
On Tuesday 19 April 2005 05:38 pm, Linus Torvalds wrote: On Tue, 19 Apr 2005, Steven Cole wrote: I wasn't complaining about the 4 minutes, just the lack of feedback during the majority of that time. And most of it was after the last patching file message. That should be exactly the thing that the new read-tree -m fixes. Before, when you read in a new tree (which is what you do when you update to somebody elses version), git would throw all the cached information away, and so you'd end up doing a checkout-cache -f -a that re-wrote every single checked-out file, followed by update-cache --refresh that then re-created the cache for every single file. With the new read-tree, the same sequence (assuming you have the -m flag to tell read-tree to merge the cache information) will now only write out and re-check the files that actually changed due to the update or merge. So that last phase should go from minutes to seconds - instead of checking 17,000+ files, you'd end up checking maybe a few hundred for most normal updates. For example, updating all the way from the git root (ie plain 2.6.12-rc2) to the current head, only 577 files have changed, and the rest (16,740) should never be touched at all. You can see why doing just the 577 instead of the full 17,317 might speed things up a bit ;) Linus Cool. Petr, I hope this works like this with your tools tomorrow. PS. Of course, right now it probably does make sense to waste some time occasionally, and run fsck-cache $(cat .git/HEAD) every once in a while. Just in case.. Sounds like a good thing to schedule for $WEEHOUR. Steven - 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.6.12-rc2 oops PREEMPT DEBUG_PAGEALLOC sysenter_past_esp+0x3/0x75
I got around to booting 2.6.12-rc2 here at home last night, and got several (12) oops. Here is a typical one. They all have the same trace, but occured on differing processes. [18008.409586] <1>Unable to handle kernel paging request at virtual address c2166000 [24538.187178] printing eip: [24538.187188] c0102b5c [24538.187195] *pde = 7067 [24538.187203] *pte = 02166000 [24538.187214] Oops: [#4] [24538.187220] PREEMPT DEBUG_PAGEALLOC [24538.187239] CPU:0 [24538.187244] EIP:0060:[]Not tainted VLI [24538.187251] EFLAGS: 00010046 (2.6.12-rc2) [24538.187274] EIP is at restore_all+0x4/0x18 [24538.187286] eax: 0282 ebx: 0006 ecx: edx: 0001 [24538.187302] esi: 081530d8 edi: 0817f428 ebp: c2164000 esp: c2165fc8 [24538.187315] ds: 007b es: 007b ss: 0068 [24538.187328] Process kppp (pid: 7305, threadinfo=c2164000 task=cb69db10) [24538.187338] Stack: 0006 541b bfb6d950 081530d8 0817f428 bfb6d928 0036 c010007b [24538.187366]007b ff00 c0102a9a 0060 0282 007b [24538.187387] Call Trace: [24538.187396] [] sysenter_past_esp+0x3/0x75 Prior to that, I'd been running 2.6.12-rc1 without these problems. Apologies in advance if I don't respond for additional information right away. I'll be away from the computer for a while today. Anticipating one question: [EMAIL PROTECTED] testing-2.6]$ grep PREEMPT .config CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_DEBUG_PREEMPT is not set Steven - 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.6.12-rc2 oops PREEMPT DEBUG_PAGEALLOC sysenter_past_esp+0x3/0x75
I got around to booting 2.6.12-rc2 here at home last night, and got several (12) oops. Here is a typical one. They all have the same trace, but occured on differing processes. [18008.409586] 1Unable to handle kernel paging request at virtual address c2166000 [24538.187178] printing eip: [24538.187188] c0102b5c [24538.187195] *pde = 7067 [24538.187203] *pte = 02166000 [24538.187214] Oops: [#4] [24538.187220] PREEMPT DEBUG_PAGEALLOC [24538.187239] CPU:0 [24538.187244] EIP:0060:[c0102b5c]Not tainted VLI [24538.187251] EFLAGS: 00010046 (2.6.12-rc2) [24538.187274] EIP is at restore_all+0x4/0x18 [24538.187286] eax: 0282 ebx: 0006 ecx: edx: 0001 [24538.187302] esi: 081530d8 edi: 0817f428 ebp: c2164000 esp: c2165fc8 [24538.187315] ds: 007b es: 007b ss: 0068 [24538.187328] Process kppp (pid: 7305, threadinfo=c2164000 task=cb69db10) [24538.187338] Stack: 0006 541b bfb6d950 081530d8 0817f428 bfb6d928 0036 c010007b [24538.187366]007b ff00 c0102a9a 0060 0282 007b [24538.187387] Call Trace: [24538.187396] [c0102a9a] sysenter_past_esp+0x3/0x75 Prior to that, I'd been running 2.6.12-rc1 without these problems. Apologies in advance if I don't respond for additional information right away. I'll be away from the computer for a while today. Anticipating one question: [EMAIL PROTECTED] testing-2.6]$ grep PREEMPT .config CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_DEBUG_PREEMPT is not set Steven - 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: 2.6.12-rc2-mm1: ACPI=y, ACPI_BOOT=n problems
Andrew Morton wrote: Steven Cole <[EMAIL PROTECTED]> wrote: arch/i386/kernel/setup.c: In function 'setup_arch': arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init' arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init' diff -puN include/linux/acpi.h~no-acpi-build-fix include/linux/acpi.h --- 25/include/linux/acpi.h~no-acpi-build-fix 2005-04-05 00:14:46.0 -0700 +++ 25-akpm/include/linux/acpi.h2005-04-05 00:23:39.0 -0700 @@ -418,16 +418,6 @@ extern int sbf_port ; [patch snipped] Yes, that worked with no CONFIG_ACPI. Thanks. On a slightly offtopic note, I'm now using this gcc: gcc (GCC) 4.0.0 20050308 (Red Hat 4.0.0-0.32) I don't have any quantitative data at hand, this seems SLW. I guess that's progress. But it slows down testing somewhat. Steven - 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: 2.6.12-rc2-mm1: ACPI=y, ACPI_BOOT=n problems
Andrew Morton wrote: Steven Cole [EMAIL PROTECTED] wrote: arch/i386/kernel/setup.c: In function 'setup_arch': arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init' arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init' diff -puN include/linux/acpi.h~no-acpi-build-fix include/linux/acpi.h --- 25/include/linux/acpi.h~no-acpi-build-fix 2005-04-05 00:14:46.0 -0700 +++ 25-akpm/include/linux/acpi.h2005-04-05 00:23:39.0 -0700 @@ -418,16 +418,6 @@ extern int sbf_port ; [patch snipped] Yes, that worked with no CONFIG_ACPI. Thanks. On a slightly offtopic note, I'm now using this gcc: gcc (GCC) 4.0.0 20050308 (Red Hat 4.0.0-0.32) I don't have any quantitative data at hand, this seems SLW. I guess that's progress. But it slows down testing somewhat. Steven - 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: 2.6.12-rc2-mm1: ACPI=y, ACPI_BOOT=n problems
Adrian Bunk wrote: On Wed, Apr 06, 2005 at 12:32:52AM +1200, Reuben Farrelly wrote: Hi again At 12:14 a.m. 6/04/2005, Adrian Bunk wrote: On Tue, Apr 05, 2005 at 08:34:11PM +1200, Reuben Farrelly wrote: Hi, Hi Reuben, ... Hrm. Something changed between the last -mm release which compiled through, and this one.. ... LD .tmp_vmlinux1 arch/i386/kernel/built-in.o(.init.text+0x1823): In function `setup_arch': : undefined reference to `acpi_boot_table_init' arch/i386/kernel/built-in.o(.init.text+0x1828): In function `setup_arch': : undefined reference to `acpi_boot_init' make: *** [.tmp_vmlinux1] Error 1 [EMAIL PROTECTED] linux-2.6]# Backing out bk-acpi.patch works around it.. Please send your .config . Have just figured out that it seems to be caused by having ACPI disabled in .config, once I re-enabled ACPI the build problem went away. Config attached anyway, I imagine the problem is quite reproduceable.. Ah, this was the working .config . fter setting CONFIG_ACPI=n I started seeing different but most likely related problems. @Len: ACPI=y and ACPI_BOOT=n seems to be a legal configuration (with X86_HT=y), but it breaks into pieces if you try the compilation. Here is some additional and hopefully helpful information. Without CONFIG_ACPI=y, I first got: arch/i386/kernel/setup.c: In function 'setup_arch': arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init' arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init' and then at the end: arch/i386/kernel/built-in.o(.init.text+0x1b81): In function `setup_arch': : undefined reference to `acpi_boot_table_init' arch/i386/kernel/built-in.o(.init.text+0x1b86): In function `setup_arch': : undefined reference to `acpi_boot_init' make: *** [.tmp_vmlinux1] Error 1 With these set linux-2.6.12-rc2-mm1 built OK. [EMAIL PROTECTED] linux-2.6.12-rc2-mm1]$ grep ^CONFIG_ACPI .config CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_BLACKLIST_YEAR=0 CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y Steven - 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: 2.6.12-rc2-mm1: ACPI=y, ACPI_BOOT=n problems
Adrian Bunk wrote: On Wed, Apr 06, 2005 at 12:32:52AM +1200, Reuben Farrelly wrote: Hi again At 12:14 a.m. 6/04/2005, Adrian Bunk wrote: On Tue, Apr 05, 2005 at 08:34:11PM +1200, Reuben Farrelly wrote: Hi, Hi Reuben, ... Hrm. Something changed between the last -mm release which compiled through, and this one.. ... LD .tmp_vmlinux1 arch/i386/kernel/built-in.o(.init.text+0x1823): In function `setup_arch': : undefined reference to `acpi_boot_table_init' arch/i386/kernel/built-in.o(.init.text+0x1828): In function `setup_arch': : undefined reference to `acpi_boot_init' make: *** [.tmp_vmlinux1] Error 1 [EMAIL PROTECTED] linux-2.6]# Backing out bk-acpi.patch works around it.. Please send your .config . Have just figured out that it seems to be caused by having ACPI disabled in .config, once I re-enabled ACPI the build problem went away. Config attached anyway, I imagine the problem is quite reproduceable.. Ah, this was the working .config . fter setting CONFIG_ACPI=n I started seeing different but most likely related problems. @Len: ACPI=y and ACPI_BOOT=n seems to be a legal configuration (with X86_HT=y), but it breaks into pieces if you try the compilation. Here is some additional and hopefully helpful information. Without CONFIG_ACPI=y, I first got: arch/i386/kernel/setup.c: In function 'setup_arch': arch/i386/kernel/setup.c:1571: warning: implicit declaration of function 'acpi_boot_table_init' arch/i386/kernel/setup.c:1572: warning: implicit declaration of function 'acpi_boot_init' and then at the end: arch/i386/kernel/built-in.o(.init.text+0x1b81): In function `setup_arch': : undefined reference to `acpi_boot_table_init' arch/i386/kernel/built-in.o(.init.text+0x1b86): In function `setup_arch': : undefined reference to `acpi_boot_init' make: *** [.tmp_vmlinux1] Error 1 With these set linux-2.6.12-rc2-mm1 built OK. [EMAIL PROTECTED] linux-2.6.12-rc2-mm1]$ grep ^CONFIG_ACPI .config CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_BLACKLIST_YEAR=0 CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y Steven - 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/
[PATCH] Clarify -rc definition in Documentation/feature-list-2.6.txt
Gentlehackers, The day to clarify the real definition of "-rc" is finally here. Steven --- linux-2.6.12-rc1-mm4/Documentation/feature-list-2.6.txt.orig 2005-04-01 07:56:23.0 -0700 +++ linux-2.6.12-rc1-mm4/Documentation/feature-list-2.6.txt 2005-04-01 07:59:21.0 -0700 @@ -23,16 +23,21 @@ Applying patches. ~ - In 2.4 and previous kernels, the recommended way to apply patches was to use a command line such as ... gzip -cd patchXX.gz | patch -p0 In 2.6, Linus started adding an extra path element to the diffs, so using -p1 in the untarred 'to be patched' directory is necessary. +Release Candidates +~ +- In 2.4 and previous kernels, -rc meant "release candidate". + In 2.6, -rc means "really churning", so even more testing is desired. + Known gotchas. ~~ Certain known bugs are being reported over and over. Here are the workarounds. - Blank screen after decompressing kernel? Make sure your .config has CONFIG_INPUT=y CONFIG_VT=y - 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/
[PATCH] Clarify -rc definition in Documentation/feature-list-2.6.txt
Gentlehackers, The day to clarify the real definition of -rc is finally here. Steven --- linux-2.6.12-rc1-mm4/Documentation/feature-list-2.6.txt.orig 2005-04-01 07:56:23.0 -0700 +++ linux-2.6.12-rc1-mm4/Documentation/feature-list-2.6.txt 2005-04-01 07:59:21.0 -0700 @@ -23,16 +23,21 @@ Applying patches. ~ - In 2.4 and previous kernels, the recommended way to apply patches was to use a command line such as ... gzip -cd patchXX.gz | patch -p0 In 2.6, Linus started adding an extra path element to the diffs, so using -p1 in the untarred 'to be patched' directory is necessary. +Release Candidates +~ +- In 2.4 and previous kernels, -rc meant release candidate. + In 2.6, -rc means really churning, so even more testing is desired. + Known gotchas. ~~ Certain known bugs are being reported over and over. Here are the workarounds. - Blank screen after decompressing kernel? Make sure your .config has CONFIG_INPUT=y CONFIG_VT=y - 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/
[PATCH] 2.6.12-rc1-mm3 Fix ver_linux script for no udev utils.
Without the attached patch, the ver_linux script gives
the following if udev utils are not present.
./scripts/ver_linux: line 90: udevinfo: command not found
The patch causes ver_linux to be silent in the case of
no udevinfo command.
Steven
TSPA (Technical data or Software Publicly Available)
Signed-off-by: Steven Cole <[EMAIL PROTECTED]>
--- linux-2.6.12-rc1-mm3/scripts/ver_linux.orig 2005-03-29 08:52:35.0
-0700
+++ linux-2.6.12-rc1-mm3/scripts/ver_linux 2005-03-29 09:04:37.0
-0700
@@ -87,7 +87,7 @@
expr --v 2>&1 | awk 'NR==1{print "Sh-utils ", $NF}'
-udevinfo -V | awk '{print "udev ", $3}'
+udevinfo -V 2>&1 | grep version | awk '{print "udev ", $3}'
if [ -e /proc/modules ]; then
X=`cat /proc/modules | sed -e "s/ .*$//"`
[PATCH] 2.6.12-rc1-mm3 Fix ver_linux script for no udev utils.
Without the attached patch, the ver_linux script gives
the following if udev utils are not present.
./scripts/ver_linux: line 90: udevinfo: command not found
The patch causes ver_linux to be silent in the case of
no udevinfo command.
Steven
TSPA (Technical data or Software Publicly Available)
Signed-off-by: Steven Cole [EMAIL PROTECTED]
--- linux-2.6.12-rc1-mm3/scripts/ver_linux.orig 2005-03-29 08:52:35.0
-0700
+++ linux-2.6.12-rc1-mm3/scripts/ver_linux 2005-03-29 09:04:37.0
-0700
@@ -87,7 +87,7 @@
expr --v 21 | awk 'NR==1{print Sh-utils , $NF}'
-udevinfo -V | awk '{print udev , $3}'
+udevinfo -V 21 | grep version | awk '{print udev , $3}'
if [ -e /proc/modules ]; then
X=`cat /proc/modules | sed -e s/ .*$//`
Re: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
Andrew Morton wrote: Andrew Morton <[EMAIL PROTECTED]> wrote: It's the new rock-ridge bounds checking. Try this, please? OK, you caught me just as I was headed out the door. ;) The patch fixed it for me. Wheee. [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm3-GX110 [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.9G 335M 97% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 97M 1.7G 6% /var /dev/hdc iso96602.9M 2.9M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 2578 -rw-rw-rw- 1 501 501 2639360 Aug 7 2003 snmp-opc server 30.msi [EMAIL PROTECTED] steven]# dmesg | tail [ 49.932278] EXT3 FS on hda8, internal journal [ 49.932292] EXT3-fs: mounted filesystem with ordered data mode. [ 49.966250] kjournald starting. Commit interval 5 seconds [ 49.966659] EXT3 FS on hda6, internal journal [ 49.99] EXT3-fs: mounted filesystem with ordered data mode. [ 49.994929] kjournald starting. Commit interval 5 seconds [ 49.995334] EXT3 FS on hda7, internal journal [ 49.995345] EXT3-fs: mounted filesystem with ordered data mode. [ 57.117794] PCI: Found IRQ 5 for device :01:0c.0 [ 123.944869] ISO 9660 Extensions: IEEE_P1282 Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
Andrew Morton wrote: Steven Cole <[EMAIL PROTECTED]> wrote: I found a few more minutes to test two more kernels. The problem first occured with 2.6.12-rc1-mm2: 2.6.12-rc1 reads the cd-rom OK as reported earlier 2.6.12-rc1-mm1 also reads the cd-rom OK 2.6.12-rc1-mm2 broken same as -mm3 described as above 2.6.12-rc1-mm3 broken as reported earlier Are you really really sure about that? -mm3 included both the bk-ide-dev tree and the isofs changes. 2.6.12-rc1-mm2 had neither. Just to be really really sure, I repeated the tests. I even checked that the image/label combination in /etc/lilo.conf was what I intended, but the uname -r should show what's what. Same results, -mm2 broken, and -mm1 reads the disk. I even tried other CD's just to make sure I didn't have something weird. Same results. OK, thanks. It would be interesting to copy a CD to hard disk (under -mm1) and see if it works OK with the loopback driver. Also, boot into -mm2 and do a `cmp' of the cdrom with the image which is on hard-disk. This should help us work out whether it's isofs, the driver, the VFS or whatever. - It seems that I've run out of time here today. If this is still an issue after the weekend, I'll do the above tests. Until then, Happy Easter. Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
Andrew Morton wrote: Steven Cole <[EMAIL PROTECTED]> wrote: > [ 49.198779] EXT3-fs: mounted filesystem with ordered data mode. > [ 56.310394] PCI: Found IRQ 5 for device :01:0c.0 > [ 222.804956] rock: directory entry would overflow storage > [ 222.804978] rock: sig=0x5245, size=8, remaining=0 > [ 235.551953] rock: directory entry would overflow storage > [ 235.551969] rock: sig=0x5850, size=36, remaining=34 > [ 235.551976] rock: directory entry would overflow storage > [ 235.551981] rock: sig=0x5850, size=36, remaining=34 > > Sorry, I don't have the time to do further troubleshooting, but I > hope this is enough information. The .config for this machine was > posted earlier in another thread here: > http://marc.theaimsgroup.com/?l=linux-kernel=67720523853=2 > > Steven I found a few more minutes to test two more kernels. The problem first occured with 2.6.12-rc1-mm2: 2.6.12-rc1 reads the cd-rom OK as reported earlier 2.6.12-rc1-mm1 also reads the cd-rom OK 2.6.12-rc1-mm2 broken same as -mm3 described as above 2.6.12-rc1-mm3 broken as reported earlier Are you really really sure about that? -mm3 included both the bk-ide-dev tree and the isofs changes. 2.6.12-rc1-mm2 had neither. Just to be really really sure, I repeated the tests. I even checked that the image/label combination in /etc/lilo.conf was what I intended, but the uname -r should show what's what. Same results, -mm2 broken, and -mm1 reads the disk. I even tried other CD's just to make sure I didn't have something weird. Same results. [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm2-GX110 [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.5G 818M 91% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso96602.9M 2.9M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 0 [EMAIL PROTECTED] steven]# dmesg | tail [ 51.205871] EXT3 FS on hda6, internal journal [ 51.205880] EXT3-fs: mounted filesystem with ordered data mode. [ 51.234132] kjournald starting. Commit interval 5 seconds [ 51.234544] EXT3 FS on hda7, internal journal [ 51.234553] EXT3-fs: mounted filesystem with ordered data mode. [ 58.357329] PCI: Found IRQ 5 for device :01:0c.0 [ 146.301026] rock: directory entry would overflow storage [ 146.301044] rock: sig=0x5245, size=8, remaining=0 [ 158.388397] rock: directory entry would overflow storage [ 158.388415] rock: sig=0x5850, size=36, remaining=34 [EMAIL PROTECTED] steven]# Machine rebooted here. [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm1-GX110 [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.5G 818M 91% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso96602.9M 2.9M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 2578 -rw-rw-rw- 1 501 501 2639360 Aug 7 2003 snmp-opc server 30.msi [EMAIL PROTECTED] steven]# dmesg | tail [ 50.267382] EXT3 FS on hda8, internal journal [ 50.267395] EXT3-fs: mounted filesystem with ordered data mode. [ 50.301423] kjournald starting. Commit interval 5 seconds [ 50.301763] EXT3 FS on hda6, internal journal [ 50.301774] EXT3-fs: mounted filesystem with ordered data mode. [ 50.330087] kjournald starting. Commit interval 5 seconds [ 50.330503] EXT3 FS on hda7, internal journal [ 50.330516] EXT3-fs: mounted filesystem with ordered data mode. [ 57.453061] PCI: Found IRQ 5 for device :01:0c.0 [ 187.450836] ISO 9660 Extensions: IEEE_P1282 [EMAIL PROTECTED] steven]# Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
Steven Cole wrote: I'm having trouble reading from the cd-rom with 2.6.12-rc1-mm3. Kernel 2.6.12-rc1 behaves normally: [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.2G 1.1G 88% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 37859 -rw-r--r-- 1 501 501 38673949 Mar 25 07:41 linux-2429tar.gz -rw-r--r-- 1 501 50192317 Mar 25 07:43 patch-2430-rc1.bz2 [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-GX110 Snipped from dmesg: [ 51.440018] EXT3-fs: mounted filesystem with ordered data mode. [ 58.585093] PCI: Found IRQ 5 for device :01:0c.0 [ 232.333180] ISO 9660 Extensions: IEEE_P1282 Kernel 2.6.12-rc1-mm3 does not: (same CD left in device) [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.2G 1.1G 88% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 0 [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm3-GX110 Snipped from dmesg: [ 49.198779] EXT3-fs: mounted filesystem with ordered data mode. [ 56.310394] PCI: Found IRQ 5 for device :01:0c.0 [ 222.804956] rock: directory entry would overflow storage [ 222.804978] rock: sig=0x5245, size=8, remaining=0 [ 235.551953] rock: directory entry would overflow storage [ 235.551969] rock: sig=0x5850, size=36, remaining=34 [ 235.551976] rock: directory entry would overflow storage [ 235.551981] rock: sig=0x5850, size=36, remaining=34 Sorry, I don't have the time to do further troubleshooting, but I hope this is enough information. The .config for this machine was posted earlier in another thread here: http://marc.theaimsgroup.com/?l=linux-kernel=67720523853=2 Steven I found a few more minutes to test two more kernels. The problem first occured with 2.6.12-rc1-mm2: 2.6.12-rc1 reads the cd-rom OK as reported earlier 2.6.12-rc1-mm1 also reads the cd-rom OK 2.6.12-rc1-mm2 broken same as -mm3 described as above 2.6.12-rc1-mm3 broken as reported earlier Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
I'm having trouble reading from the cd-rom with 2.6.12-rc1-mm3. Kernel 2.6.12-rc1 behaves normally: [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.2G 1.1G 88% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 37859 -rw-r--r-- 1 501 501 38673949 Mar 25 07:41 linux-2429tar.gz -rw-r--r-- 1 501 50192317 Mar 25 07:43 patch-2430-rc1.bz2 [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-GX110 Snipped from dmesg: [ 51.440018] EXT3-fs: mounted filesystem with ordered data mode. [ 58.585093] PCI: Found IRQ 5 for device :01:0c.0 [ 232.333180] ISO 9660 Extensions: IEEE_P1282 Kernel 2.6.12-rc1-mm3 does not: (same CD left in device) [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.2G 1.1G 88% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 0 [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm3-GX110 Snipped from dmesg: [ 49.198779] EXT3-fs: mounted filesystem with ordered data mode. [ 56.310394] PCI: Found IRQ 5 for device :01:0c.0 [ 222.804956] rock: directory entry would overflow storage [ 222.804978] rock: sig=0x5245, size=8, remaining=0 [ 235.551953] rock: directory entry would overflow storage [ 235.551969] rock: sig=0x5850, size=36, remaining=34 [ 235.551976] rock: directory entry would overflow storage [ 235.551981] rock: sig=0x5850, size=36, remaining=34 Sorry, I don't have the time to do further troubleshooting, but I hope this is enough information. The .config for this machine was posted earlier in another thread here: http://marc.theaimsgroup.com/?l=linux-kernel=67720523853=2 Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
I'm having trouble reading from the cd-rom with 2.6.12-rc1-mm3. Kernel 2.6.12-rc1 behaves normally: [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.2G 1.1G 88% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 37859 -rw-r--r-- 1 501 501 38673949 Mar 25 07:41 linux-2429tar.gz -rw-r--r-- 1 501 50192317 Mar 25 07:43 patch-2430-rc1.bz2 [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-GX110 Snipped from dmesg: [ 51.440018] EXT3-fs: mounted filesystem with ordered data mode. [ 58.585093] PCI: Found IRQ 5 for device :01:0c.0 [ 232.333180] ISO 9660 Extensions: IEEE_P1282 Kernel 2.6.12-rc1-mm3 does not: (same CD left in device) [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.2G 1.1G 88% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 0 [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm3-GX110 Snipped from dmesg: [ 49.198779] EXT3-fs: mounted filesystem with ordered data mode. [ 56.310394] PCI: Found IRQ 5 for device :01:0c.0 [ 222.804956] rock: directory entry would overflow storage [ 222.804978] rock: sig=0x5245, size=8, remaining=0 [ 235.551953] rock: directory entry would overflow storage [ 235.551969] rock: sig=0x5850, size=36, remaining=34 [ 235.551976] rock: directory entry would overflow storage [ 235.551981] rock: sig=0x5850, size=36, remaining=34 Sorry, I don't have the time to do further troubleshooting, but I hope this is enough information. The .config for this machine was posted earlier in another thread here: http://marc.theaimsgroup.com/?l=linux-kernelm=67720523853w=2 Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
Steven Cole wrote: I'm having trouble reading from the cd-rom with 2.6.12-rc1-mm3. Kernel 2.6.12-rc1 behaves normally: [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.2G 1.1G 88% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 37859 -rw-r--r-- 1 501 501 38673949 Mar 25 07:41 linux-2429tar.gz -rw-r--r-- 1 501 50192317 Mar 25 07:43 patch-2430-rc1.bz2 [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-GX110 Snipped from dmesg: [ 51.440018] EXT3-fs: mounted filesystem with ordered data mode. [ 58.585093] PCI: Found IRQ 5 for device :01:0c.0 [ 232.333180] ISO 9660 Extensions: IEEE_P1282 Kernel 2.6.12-rc1-mm3 does not: (same CD left in device) [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.2G 1.1G 88% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso9660 38M 38M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 0 [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm3-GX110 Snipped from dmesg: [ 49.198779] EXT3-fs: mounted filesystem with ordered data mode. [ 56.310394] PCI: Found IRQ 5 for device :01:0c.0 [ 222.804956] rock: directory entry would overflow storage [ 222.804978] rock: sig=0x5245, size=8, remaining=0 [ 235.551953] rock: directory entry would overflow storage [ 235.551969] rock: sig=0x5850, size=36, remaining=34 [ 235.551976] rock: directory entry would overflow storage [ 235.551981] rock: sig=0x5850, size=36, remaining=34 Sorry, I don't have the time to do further troubleshooting, but I hope this is enough information. The .config for this machine was posted earlier in another thread here: http://marc.theaimsgroup.com/?l=linux-kernelm=67720523853w=2 Steven I found a few more minutes to test two more kernels. The problem first occured with 2.6.12-rc1-mm2: 2.6.12-rc1 reads the cd-rom OK as reported earlier 2.6.12-rc1-mm1 also reads the cd-rom OK 2.6.12-rc1-mm2 broken same as -mm3 described as above 2.6.12-rc1-mm3 broken as reported earlier Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
Andrew Morton wrote: Steven Cole [EMAIL PROTECTED] wrote: [ 49.198779] EXT3-fs: mounted filesystem with ordered data mode. [ 56.310394] PCI: Found IRQ 5 for device :01:0c.0 [ 222.804956] rock: directory entry would overflow storage [ 222.804978] rock: sig=0x5245, size=8, remaining=0 [ 235.551953] rock: directory entry would overflow storage [ 235.551969] rock: sig=0x5850, size=36, remaining=34 [ 235.551976] rock: directory entry would overflow storage [ 235.551981] rock: sig=0x5850, size=36, remaining=34 Sorry, I don't have the time to do further troubleshooting, but I hope this is enough information. The .config for this machine was posted earlier in another thread here: http://marc.theaimsgroup.com/?l=linux-kernelm=67720523853w=2 Steven I found a few more minutes to test two more kernels. The problem first occured with 2.6.12-rc1-mm2: 2.6.12-rc1 reads the cd-rom OK as reported earlier 2.6.12-rc1-mm1 also reads the cd-rom OK 2.6.12-rc1-mm2 broken same as -mm3 described as above 2.6.12-rc1-mm3 broken as reported earlier Are you really really sure about that? -mm3 included both the bk-ide-dev tree and the isofs changes. 2.6.12-rc1-mm2 had neither. Just to be really really sure, I repeated the tests. I even checked that the image/label combination in /etc/lilo.conf was what I intended, but the uname -r should show what's what. Same results, -mm2 broken, and -mm1 reads the disk. I even tried other CD's just to make sure I didn't have something weird. Same results. [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm2-GX110 [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.5G 818M 91% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso96602.9M 2.9M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 0 [EMAIL PROTECTED] steven]# dmesg | tail [ 51.205871] EXT3 FS on hda6, internal journal [ 51.205880] EXT3-fs: mounted filesystem with ordered data mode. [ 51.234132] kjournald starting. Commit interval 5 seconds [ 51.234544] EXT3 FS on hda7, internal journal [ 51.234553] EXT3-fs: mounted filesystem with ordered data mode. [ 58.357329] PCI: Found IRQ 5 for device :01:0c.0 [ 146.301026] rock: directory entry would overflow storage [ 146.301044] rock: sig=0x5245, size=8, remaining=0 [ 158.388397] rock: directory entry would overflow storage [ 158.388415] rock: sig=0x5850, size=36, remaining=34 [EMAIL PROTECTED] steven]# Machine rebooted here. [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm1-GX110 [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.5G 818M 91% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 96M 1.7G 6% /var /dev/hdc iso96602.9M 2.9M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 2578 -rw-rw-rw- 1 501 501 2639360 Aug 7 2003 snmp-opc server 30.msi [EMAIL PROTECTED] steven]# dmesg | tail [ 50.267382] EXT3 FS on hda8, internal journal [ 50.267395] EXT3-fs: mounted filesystem with ordered data mode. [ 50.301423] kjournald starting. Commit interval 5 seconds [ 50.301763] EXT3 FS on hda6, internal journal [ 50.301774] EXT3-fs: mounted filesystem with ordered data mode. [ 50.330087] kjournald starting. Commit interval 5 seconds [ 50.330503] EXT3 FS on hda7, internal journal [ 50.330516] EXT3-fs: mounted filesystem with ordered data mode. [ 57.453061] PCI: Found IRQ 5 for device :01:0c.0 [ 187.450836] ISO 9660 Extensions: IEEE_P1282 [EMAIL PROTECTED] steven]# Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
Andrew Morton wrote: Steven Cole [EMAIL PROTECTED] wrote: I found a few more minutes to test two more kernels. The problem first occured with 2.6.12-rc1-mm2: 2.6.12-rc1 reads the cd-rom OK as reported earlier 2.6.12-rc1-mm1 also reads the cd-rom OK 2.6.12-rc1-mm2 broken same as -mm3 described as above 2.6.12-rc1-mm3 broken as reported earlier Are you really really sure about that? -mm3 included both the bk-ide-dev tree and the isofs changes. 2.6.12-rc1-mm2 had neither. Just to be really really sure, I repeated the tests. I even checked that the image/label combination in /etc/lilo.conf was what I intended, but the uname -r should show what's what. Same results, -mm2 broken, and -mm1 reads the disk. I even tried other CD's just to make sure I didn't have something weird. Same results. OK, thanks. It would be interesting to copy a CD to hard disk (under -mm1) and see if it works OK with the loopback driver. Also, boot into -mm2 and do a `cmp' of the cdrom with the image which is on hard-disk. This should help us work out whether it's isofs, the driver, the VFS or whatever. - It seems that I've run out of time here today. If this is still an issue after the weekend, I'll do the above tests. Until then, Happy Easter. Steven - 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: 2.6.12-rc1-mm3 (cannot read cd-rom, 2.6.12-rc1 is OK)
Andrew Morton wrote: Andrew Morton [EMAIL PROTECTED] wrote: It's the new rock-ridge bounds checking. Try this, please? OK, you caught me just as I was headed out the door. ;) The patch fixed it for me. Wheee. [EMAIL PROTECTED] steven]# uname -r 2.6.12-rc1-mm3-GX110 [EMAIL PROTECTED] steven]# mount /dev/hdc /mnt/cdrom mount: block device /dev/hdc is write-protected, mounting read-only [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 96M 193M 34% / /dev/hda9 reiserfs8.3G 7.9G 335M 97% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.5G 5.5G 22% /usr /dev/hda7 ext31.9G 97M 1.7G 6% /var /dev/hdc iso96602.9M 2.9M 0 100% /mnt/cdrom [EMAIL PROTECTED] steven]# ls -l /mnt/cdrom total 2578 -rw-rw-rw- 1 501 501 2639360 Aug 7 2003 snmp-opc server 30.msi [EMAIL PROTECTED] steven]# dmesg | tail [ 49.932278] EXT3 FS on hda8, internal journal [ 49.932292] EXT3-fs: mounted filesystem with ordered data mode. [ 49.966250] kjournald starting. Commit interval 5 seconds [ 49.966659] EXT3 FS on hda6, internal journal [ 49.99] EXT3-fs: mounted filesystem with ordered data mode. [ 49.994929] kjournald starting. Commit interval 5 seconds [ 49.995334] EXT3 FS on hda7, internal journal [ 49.995345] EXT3-fs: mounted filesystem with ordered data mode. [ 57.117794] PCI: Found IRQ 5 for device :01:0c.0 [ 123.944869] ISO 9660 Extensions: IEEE_P1282 Steven - 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: 2.6.12-rc1-mm2 (patch to fix build error In function `zft_init')
Steven Cole wrote:
I'm getting the following build error with 2.6.12-rc1-mm2:
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x4323): In function `zft_init':
: undefined reference to `class_device_creat'
make: *** [.tmp_vmlinux1] Error 1
I glanced at the code, and this little patch fixes the problem:
Steven
Signed-off by: Steven Cole <[EMAIL PROTECTED]>
--- linux-2.6.12-rc1-mm2/drivers/char/ftape/zftape/zftape-init.c.orig
2005-03-24 08:43:30.0 -0700
+++ linux-2.6.12-rc1-mm2/drivers/char/ftape/zftape/zftape-init.c
2005-03-24 08:43:56.0 -0700
@@ -331,7 +331,7 @@
zft_class = class_create(THIS_MODULE, "zft");
for (i = 0; i < 4; i++) {
- class_device_creat(zft_class, MKDEV(QIC117_TAPE_MAJOR, i),
NULL, "qft%i", i);
+ class_device_create(zft_class, MKDEV(QIC117_TAPE_MAJOR, i),
NULL, "qft%i", i);
devfs_mk_cdev(MKDEV(QIC117_TAPE_MAJOR, i),
S_IFCHR | S_IRUSR | S_IWUSR,
"qft%i", i);
Re: 2.6.12-rc1-mm2 (build error In function `zft_init')
I'm getting the following build error with 2.6.12-rc1-mm2: CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o(.init.text+0x4323): In function `zft_init': : undefined reference to `class_device_creat' make: *** [.tmp_vmlinux1] Error 1 2.6.12-rc1-mm1 built and is running just fine. I used the -rc1-mm1 .config, did make oldconfig, make bzImage. Here is the .config: [EMAIL PROTECTED] linux-2.6.12-rc1-mm2]$ grep ^CONFIG .config CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAR_PAGES=y CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="-GX110" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KALLSYMS=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 CONFIG_BASE_SMALL=0 CONFIG_X86_PC=y CONFIG_MPENTIUMIII=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_P4THERMAL=y CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_EDD=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_PHYSICAL_START=0x10 CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_LEGACY_PROC=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=32000 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_AOE_PARTITIONS=16 CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_IP_TCPDIAG=y CONFIG_XFRM=y CONFIG_NETDEVICES=y CONFIG_NET_ETHERNET=y CONFIG_MII=y CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=y CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_LIBPS2=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_FTAPE=y CONFIG_ZFTAPE=y CONFIG_ZFT_DFLT_BLK_SZ=10240 CONFIG_ZFT_COMPRESSOR=y CONFIG_FT_NR_BUFFERS=3 CONFIG_FT_PROC_FS=y CONFIG_FT_NORMAL_DEBUG=y CONFIG_FT_STD_FDC=y CONFIG_FT_FDC_THR=8 CONFIG_FT_FDC_MAX_RATE=2000 CONFIG_FT_ALPHA_CLOCK=0 CONFIG_AGP=y CONFIG_AGP_INTEL=y CONFIG_VIDEO_DEV=y CONFIG_VIDEO_SELECT=y CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_REISER4_FS=y CONFIG_REISERFS_FS=y CONFIG_DNOTIFY=y CONFIG_ISO9660_FS=y CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=y CONFIG_NTFS_RW=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y CONFIG_DEVFS_FS=y CONFIG_TMPFS=y CONFIG_RAMFS=y CONFIG_PARTITION_ADVANCED=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_UTF8=y CONFIG_PRINTK_TIME=y CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_DEBUG_BUGVERBOSE=y CONFIG_FRAME_POINTER=y CONFIG_EARLY_PRINTK=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_SECURITY=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_CAPABILITIES=y CONFIG_CRC_CCITT=y CONFIG_CRC32=y CONFIG_LIBCRC32C=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_PC=y Steven - 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: 2.6.12-rc1-mm2 (build error In function `zft_init')
I'm getting the following build error with 2.6.12-rc1-mm2: CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o(.init.text+0x4323): In function `zft_init': : undefined reference to `class_device_creat' make: *** [.tmp_vmlinux1] Error 1 2.6.12-rc1-mm1 built and is running just fine. I used the -rc1-mm1 .config, did make oldconfig, make bzImage. Here is the .config: [EMAIL PROTECTED] linux-2.6.12-rc1-mm2]$ grep ^CONFIG .config CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAR_PAGES=y CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION=-GX110 CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KALLSYMS=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 CONFIG_BASE_SMALL=0 CONFIG_X86_PC=y CONFIG_MPENTIUMIII=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_P4THERMAL=y CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_EDD=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_PHYSICAL_START=0x10 CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_LEGACY_PROC=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=32000 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_AOE_PARTITIONS=16 CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_IP_TCPDIAG=y CONFIG_XFRM=y CONFIG_NETDEVICES=y CONFIG_NET_ETHERNET=y CONFIG_MII=y CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=y CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_LIBPS2=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_FTAPE=y CONFIG_ZFTAPE=y CONFIG_ZFT_DFLT_BLK_SZ=10240 CONFIG_ZFT_COMPRESSOR=y CONFIG_FT_NR_BUFFERS=3 CONFIG_FT_PROC_FS=y CONFIG_FT_NORMAL_DEBUG=y CONFIG_FT_STD_FDC=y CONFIG_FT_FDC_THR=8 CONFIG_FT_FDC_MAX_RATE=2000 CONFIG_FT_ALPHA_CLOCK=0 CONFIG_AGP=y CONFIG_AGP_INTEL=y CONFIG_VIDEO_DEV=y CONFIG_VIDEO_SELECT=y CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_REISER4_FS=y CONFIG_REISERFS_FS=y CONFIG_DNOTIFY=y CONFIG_ISO9660_FS=y CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 CONFIG_NTFS_FS=y CONFIG_NTFS_RW=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y CONFIG_DEVFS_FS=y CONFIG_TMPFS=y CONFIG_RAMFS=y CONFIG_PARTITION_ADVANCED=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT=iso8859-1 CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_UTF8=y CONFIG_PRINTK_TIME=y CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_DEBUG_BUGVERBOSE=y CONFIG_FRAME_POINTER=y CONFIG_EARLY_PRINTK=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_SECURITY=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_CAPABILITIES=y CONFIG_CRC_CCITT=y CONFIG_CRC32=y CONFIG_LIBCRC32C=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_PC=y Steven - 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: 2.6.12-rc1-mm2 (patch to fix build error In function `zft_init')
Steven Cole wrote:
I'm getting the following build error with 2.6.12-rc1-mm2:
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x4323): In function `zft_init':
: undefined reference to `class_device_creat'
make: *** [.tmp_vmlinux1] Error 1
I glanced at the code, and this little patch fixes the problem:
Steven
Signed-off by: Steven Cole [EMAIL PROTECTED]
--- linux-2.6.12-rc1-mm2/drivers/char/ftape/zftape/zftape-init.c.orig
2005-03-24 08:43:30.0 -0700
+++ linux-2.6.12-rc1-mm2/drivers/char/ftape/zftape/zftape-init.c
2005-03-24 08:43:56.0 -0700
@@ -331,7 +331,7 @@
zft_class = class_create(THIS_MODULE, zft);
for (i = 0; i 4; i++) {
- class_device_creat(zft_class, MKDEV(QIC117_TAPE_MAJOR, i),
NULL, qft%i, i);
+ class_device_create(zft_class, MKDEV(QIC117_TAPE_MAJOR, i),
NULL, qft%i, i);
devfs_mk_cdev(MKDEV(QIC117_TAPE_MAJOR, i),
S_IFCHR | S_IRUSR | S_IWUSR,
qft%i, i);
Re: Problem with PPPD on dialup with 2.6.11-bk1 and later; 2.6.11 is OK
On Friday 11 March 2005 01:13 pm, Bill Davidsen wrote: > Stephen Hemminger wrote: > >>Stephen Hemminger also wrote: (Someting's busted with serial in 2.6.11 > >>latest) > >> > >>>Some checkin since 2.6.11 has caused the serial driver to > >>>drop characters. Console output is chopped and messages are garbled. > >>>Even the shell prompt gets truncated. > > > > > >>Searching lkml archive, I found: > >>http://marc.theaimsgroup.com/?l=linux-kernel=111031501416334=2 > >> > >>I also found that reverting that patch made the problem go away for > >>2.6.11-bk1. > > > > > > > > Yes, this patch is the problem. A fix showed up today. > > Current kernels work fine, thanks. > > Could someone who has the patch broken out send it to -stable? Serial > not working is a non-trivial issue given the number of people who use > dialup either full time or as a fallback connection. > The fix is in: http://linus.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]|src/|src/drivers|src/drivers/serial|related/drivers/serial/8250.c Since the breakage which this fix is for didn't appear until after 2.6.11, a patch to 2.6.11.x is not required. Steven - 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: Problem with PPPD on dialup with 2.6.11-bk1 and later; 2.6.11 is OK
On Friday 11 March 2005 01:13 pm, Bill Davidsen wrote: Stephen Hemminger wrote: Stephen Hemminger also wrote: (Someting's busted with serial in 2.6.11 latest) Some checkin since 2.6.11 has caused the serial driver to drop characters. Console output is chopped and messages are garbled. Even the shell prompt gets truncated. Searching lkml archive, I found: http://marc.theaimsgroup.com/?l=linux-kernelm=111031501416334w=2 I also found that reverting that patch made the problem go away for 2.6.11-bk1. Yes, this patch is the problem. A fix showed up today. Current kernels work fine, thanks. Could someone who has the patch broken out send it to -stable? Serial not working is a non-trivial issue given the number of people who use dialup either full time or as a fallback connection. The fix is in: http://linus.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]|src/|src/drivers|src/drivers/serial|related/drivers/serial/8250.c Since the breakage which this fix is for didn't appear until after 2.6.11, a patch to 2.6.11.x is not required. Steven - 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: Someting's busted with serial in 2.6.11 latest
On Thursday 10 March 2005 03:59 pm, Russell King wrote: > On Thu, Mar 10, 2005 at 03:40:11PM -0700, Steven Cole wrote: > > I'll test current bk tonight, but I don't see any recent fix to > > drivers/serial/8250.c when browsing linux.bkbits.net/linux-2.6. > > Ok, so Stephen's bug is already fixed. After testing the latest bk, if > you find your bug isn't resolved, please try to isolate the change by > applying this patch. If this doesn't resolve it, then your change of > behaviour hasn't been caused by changes to 8250.c, but must be down to > some other part of the kernel. OK, latest 2.6.11-bk works just fine. Although I thought I had a failure with a fairly recent snapshot, I must have had a version before the fix. Sorry for any confusion. FWIW, the failing kernels reported: ttyS0 at I/O 0x3f8 (irq = 4) is a XScale But now, all is fine. Thanks. Steven - 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: Someting's busted with serial in 2.6.11 latest
On Thursday 10 March 2005 03:59 pm, Russell King wrote:
> On Thu, Mar 10, 2005 at 03:40:11PM -0700, Steven Cole wrote:
> > I'll test current bk tonight, but I don't see any recent fix to
> > drivers/serial/8250.c when browsing linux.bkbits.net/linux-2.6.
>
> Ok, so Stephen's bug is already fixed. After testing the latest bk, if
> you find your bug isn't resolved, please try to isolate the change by
> applying this patch. If this doesn't resolve it, then your change of
> behaviour hasn't been caused by changes to 8250.c, but must be down to
> some other part of the kernel.
>
> = linux-2.6-rmk/drivers/serial/8250.c 1.97 vs 1.95 =
> --- 1.97/drivers/serial/8250.c2005-03-08 10:04:55 +00:00
> +++ 1.95/drivers/serial/8250.c2005-02-28 16:05:18 +00:00
> @@ -642,7 +642,6 @@
> static void autoconfig_16550a(struct uart_8250_port *up)
> {
> unsigned char status1, status2;
> - unsigned int iersave;
>
> up->port.type = PORT_16550A;
> up->capabilities |= UART_CAP_FIFO;
> @@ -729,7 +728,6 @@
> serial_outp(up, UART_FCR, UART_FCR_ENABLE_FIFO | UART_FCR7_64BYTE);
> status2 = serial_in(up, UART_IIR) >> 5;
> serial_outp(up, UART_FCR, UART_FCR_ENABLE_FIFO);
> - serial_outp(up, UART_LCR, 0);
>
> DEBUG_AUTOCONF("iir1=%d iir2=%d ", status1, status2);
>
> @@ -738,40 +736,6 @@
> up->capabilities |= UART_CAP_AFE | UART_CAP_SLEEP;
> return;
> }
> -
> - /*
> - * Try writing and reading the UART_IER_UUE bit (b6).
> - * If it works, this is probably one of the Xscale platform's
> - * internal UARTs.
> - * We're going to explicitly set the UUE bit to 0 before
> - * trying to write and read a 1 just to make sure it's not
> - * already a 1 and maybe locked there before we even start start.
> - */
> - iersave = serial_in(up, UART_IER);
> - serial_outp(up, UART_IER, iersave & ~UART_IER_UUE);
> - if (!(serial_in(up, UART_IER) & UART_IER_UUE)) {
> - /*
> - * OK it's in a known zero state, try writing and reading
> - * without disturbing the current state of the other bits.
> - */
> - serial_outp(up, UART_IER, iersave | UART_IER_UUE);
> - if (serial_in(up, UART_IER) & UART_IER_UUE) {
> - /*
> - * It's an Xscale.
> - * We'll leave the UART_IER_UUE bit set to 1 (enabled).
> - */
> - DEBUG_AUTOCONF("Xscale ");
> - up->port.type = PORT_XSCALE;
> - return;
> - }
> - } else {
> - /*
> - * If we got here we couldn't force the IER_UUE bit to 0.
> - * Log it and continue.
> - */
> - DEBUG_AUTOCONF("Couldn't force IER_UUE to 0 ");
> - }
> - serial_outp(up, UART_IER, iersave);
> }
>
> /*
>
>
I am currently doing a bk pull from linux.bkbits.net/linux-2.6, and can test
the above
patch if dialup via a serial modem breaks again, but I think I already know the
answer.
I first noticed this _after_ the last one-line change to drivers/serial/8250.c.
Last night, after establishing that 2.6.11-bk1 was the earliest kernel to have
the problem,
and reverting the Xscale patch fixed it, I tried with last night's bk-current.
It also failed as previously described, and worked with the Xscale patch
reverted.
Here is a snippet from dmesg from my current kernel (with Xscale reverted)
working
on dialup.via serial modem.
[ 43.034336] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 43.034520] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 43.034616] Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
[ 43.034924] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 43.038087] pnp: Device 00:01.00 activated.
[ 43.038329] ttyS1 at I/O 0x2f8 (irq = 10) is a 16550A
For completeness, here is the patch I applied with patch -p1 -R:
Steven
diff -Nru a/drivers/serial/8250.c b/drivers/serial/8250.c
--- a/drivers/serial/8250.c 2005-02-28 08:05:18 -08:00
+++ b/drivers/serial/8250.c 2005-01-24 08:00:57 -08:00
@@ -642,6 +642,7 @@
static void autoconfig_16550a(struct uart_8250_port *up)
{
unsigned char status1, status2;
+ unsigned int iersave;
up->port.type = PORT_16550A;
up->capabilities |= UART_CAP_FIFO;
@@ -736,6 +737,40 @@
up->capabilities |= UART_CAP_AFE | UART_CAP_SLEEP;
return;
}
+
+ /*
+ * Try writing and reading the UART_IER_UUE bit (b6).
+ * If it works, this is probably one of the Xscale platform's
+ * internal UARTs.
+ * We're going to explicitly set the U
Re: Someting's busted with serial in 2.6.11 latest
Russell King wrote: On Wed, Mar 09, 2005 at 03:50:49PM -0800, Stephen Hemminger wrote: Some checkin since 2.6.11 has caused the serial driver to drop characters. Console output is chopped and messages are garbled. Even the shell prompt gets truncated. There was a problem with 2.6.11-bk1 which should now be resolved. Is this still true of the latest bk kernel? Also, seeing the kernel messages may provide some hint. Here is a post I made perhaps relevant to this. http://marc.theaimsgroup.com/?l=linux-kernel=111042402103071=2 I'll test current bk tonight, but I don't see any recent fix to drivers/serial/8250.c when browsing linux.bkbits.net/linux-2.6. Steven - 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: Someting's busted with serial in 2.6.11 latest
Russell King wrote: On Wed, Mar 09, 2005 at 03:50:49PM -0800, Stephen Hemminger wrote: Some checkin since 2.6.11 has caused the serial driver to drop characters. Console output is chopped and messages are garbled. Even the shell prompt gets truncated. There was a problem with 2.6.11-bk1 which should now be resolved. Is this still true of the latest bk kernel? Also, seeing the kernel messages may provide some hint. Here is a post I made perhaps relevant to this. http://marc.theaimsgroup.com/?l=linux-kernelm=111042402103071w=2 I'll test current bk tonight, but I don't see any recent fix to drivers/serial/8250.c when browsing linux.bkbits.net/linux-2.6. Steven - 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: Someting's busted with serial in 2.6.11 latest
On Thursday 10 March 2005 03:59 pm, Russell King wrote:
On Thu, Mar 10, 2005 at 03:40:11PM -0700, Steven Cole wrote:
I'll test current bk tonight, but I don't see any recent fix to
drivers/serial/8250.c when browsing linux.bkbits.net/linux-2.6.
Ok, so Stephen's bug is already fixed. After testing the latest bk, if
you find your bug isn't resolved, please try to isolate the change by
applying this patch. If this doesn't resolve it, then your change of
behaviour hasn't been caused by changes to 8250.c, but must be down to
some other part of the kernel.
= linux-2.6-rmk/drivers/serial/8250.c 1.97 vs 1.95 =
--- 1.97/drivers/serial/8250.c2005-03-08 10:04:55 +00:00
+++ 1.95/drivers/serial/8250.c2005-02-28 16:05:18 +00:00
@@ -642,7 +642,6 @@
static void autoconfig_16550a(struct uart_8250_port *up)
{
unsigned char status1, status2;
- unsigned int iersave;
up-port.type = PORT_16550A;
up-capabilities |= UART_CAP_FIFO;
@@ -729,7 +728,6 @@
serial_outp(up, UART_FCR, UART_FCR_ENABLE_FIFO | UART_FCR7_64BYTE);
status2 = serial_in(up, UART_IIR) 5;
serial_outp(up, UART_FCR, UART_FCR_ENABLE_FIFO);
- serial_outp(up, UART_LCR, 0);
DEBUG_AUTOCONF(iir1=%d iir2=%d , status1, status2);
@@ -738,40 +736,6 @@
up-capabilities |= UART_CAP_AFE | UART_CAP_SLEEP;
return;
}
-
- /*
- * Try writing and reading the UART_IER_UUE bit (b6).
- * If it works, this is probably one of the Xscale platform's
- * internal UARTs.
- * We're going to explicitly set the UUE bit to 0 before
- * trying to write and read a 1 just to make sure it's not
- * already a 1 and maybe locked there before we even start start.
- */
- iersave = serial_in(up, UART_IER);
- serial_outp(up, UART_IER, iersave ~UART_IER_UUE);
- if (!(serial_in(up, UART_IER) UART_IER_UUE)) {
- /*
- * OK it's in a known zero state, try writing and reading
- * without disturbing the current state of the other bits.
- */
- serial_outp(up, UART_IER, iersave | UART_IER_UUE);
- if (serial_in(up, UART_IER) UART_IER_UUE) {
- /*
- * It's an Xscale.
- * We'll leave the UART_IER_UUE bit set to 1 (enabled).
- */
- DEBUG_AUTOCONF(Xscale );
- up-port.type = PORT_XSCALE;
- return;
- }
- } else {
- /*
- * If we got here we couldn't force the IER_UUE bit to 0.
- * Log it and continue.
- */
- DEBUG_AUTOCONF(Couldn't force IER_UUE to 0 );
- }
- serial_outp(up, UART_IER, iersave);
}
/*
I am currently doing a bk pull from linux.bkbits.net/linux-2.6, and can test
the above
patch if dialup via a serial modem breaks again, but I think I already know the
answer.
I first noticed this _after_ the last one-line change to drivers/serial/8250.c.
Last night, after establishing that 2.6.11-bk1 was the earliest kernel to have
the problem,
and reverting the Xscale patch fixed it, I tried with last night's bk-current.
It also failed as previously described, and worked with the Xscale patch
reverted.
Here is a snippet from dmesg from my current kernel (with Xscale reverted)
working
on dialup.via serial modem.
[ 43.034336] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 43.034520] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 43.034616] Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
[ 43.034924] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 43.038087] pnp: Device 00:01.00 activated.
[ 43.038329] ttyS1 at I/O 0x2f8 (irq = 10) is a 16550A
For completeness, here is the patch I applied with patch -p1 -R:
Steven
diff -Nru a/drivers/serial/8250.c b/drivers/serial/8250.c
--- a/drivers/serial/8250.c 2005-02-28 08:05:18 -08:00
+++ b/drivers/serial/8250.c 2005-01-24 08:00:57 -08:00
@@ -642,6 +642,7 @@
static void autoconfig_16550a(struct uart_8250_port *up)
{
unsigned char status1, status2;
+ unsigned int iersave;
up-port.type = PORT_16550A;
up-capabilities |= UART_CAP_FIFO;
@@ -736,6 +737,40 @@
up-capabilities |= UART_CAP_AFE | UART_CAP_SLEEP;
return;
}
+
+ /*
+ * Try writing and reading the UART_IER_UUE bit (b6).
+ * If it works, this is probably one of the Xscale platform's
+ * internal UARTs.
+ * We're going to explicitly set the UUE bit to 0 before
+ * trying to write and read a 1 just to make sure it's not
+ * already a 1 and maybe locked there before we even start start.
+ */
+ iersave = serial_in(up, UART_IER);
+ serial_outp(up, UART_IER, iersave ~UART_IER_UUE);
+ if (!(serial_in(up, UART_IER) UART_IER_UUE)) {
+ /*
+ * OK it's in a known zero state, try writing and reading
+ * without disturbing the current
Re: Someting's busted with serial in 2.6.11 latest
On Thursday 10 March 2005 03:59 pm, Russell King wrote: On Thu, Mar 10, 2005 at 03:40:11PM -0700, Steven Cole wrote: I'll test current bk tonight, but I don't see any recent fix to drivers/serial/8250.c when browsing linux.bkbits.net/linux-2.6. Ok, so Stephen's bug is already fixed. After testing the latest bk, if you find your bug isn't resolved, please try to isolate the change by applying this patch. If this doesn't resolve it, then your change of behaviour hasn't been caused by changes to 8250.c, but must be down to some other part of the kernel. OK, latest 2.6.11-bk works just fine. Although I thought I had a failure with a fairly recent snapshot, I must have had a version before the fix. Sorry for any confusion. FWIW, the failing kernels reported: ttyS0 at I/O 0x3f8 (irq = 4) is a XScale But now, all is fine. Thanks. Steven - 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: Problem with PPPD on dialup with 2.6.11-bk1 and later; 2.6.11 is OK
Today at 04:57:37 pm, I wrote: >Earlier today, I reported "PPPD fails on recent 2.6.11-bk". I've narrowed >the problem down to between 2.6.11 and 2.6.11-bk1. > >I get this with 2.6.11-bk1: (two attempts) > >Mar 9 16:34:32 spc pppd[1142]: pppd 2.4.1 started by steven, uid 501 >Mar 9 16:34:32 spc pppd[1142]: Using interface ppp0 >Mar 9 16:34:32 spc pppd[1142]: Connect: ppp0 <--> /dev/ttyS1 >Mar 9 16:34:56 spc pppd[1142]: Hangup (SIGHUP) >Mar 9 16:34:56 spc pppd[1142]: Modem hangup >Mar 9 16:34:56 spc pppd[1142]: Connection terminated. >Mar 9 16:34:56 spc pppd[1142]: Exit. Searching lkml archive, I found: http://marc.theaimsgroup.com/?l=linux-kernel=111031501416334=2 I also found that reverting that patch made the problem go away for 2.6.11-bk1. The bookmarkable link for this changeset is here: http://linus.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]|[EMAIL PROTECTED] Stephen Hemminger also wrote: (Someting's busted with serial in 2.6.11 latest) >Some checkin since 2.6.11 has caused the serial driver to >drop characters. Console output is chopped and messages are garbled. >Even the shell prompt gets truncated. Hope this helps, Steven - 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/
Problem with PPPD on dialup with 2.6.11-bk1 and later; 2.6.11 is OK
Earlier today, I reported "PPPD fails on recent 2.6.11-bk". I've narrowed the problem down to between 2.6.11 and 2.6.11-bk1. I get this with 2.6.11-bk1: (two attempts) Mar 9 16:34:32 spc pppd[1142]: pppd 2.4.1 started by steven, uid 501 Mar 9 16:34:32 spc pppd[1142]: Using interface ppp0 Mar 9 16:34:32 spc pppd[1142]: Connect: ppp0 <--> /dev/ttyS1 Mar 9 16:34:56 spc pppd[1142]: Hangup (SIGHUP) Mar 9 16:34:56 spc pppd[1142]: Modem hangup Mar 9 16:34:56 spc pppd[1142]: Connection terminated. Mar 9 16:34:56 spc pppd[1142]: Exit. Mar 9 16:35:44 spc pppd[1143]: pppd 2.4.1 started by steven, uid 501 Mar 9 16:35:44 spc pppd[1143]: Using interface ppp0 Mar 9 16:35:44 spc pppd[1143]: Connect: ppp0 <--> /dev/ttyS1 Mar 9 16:36:08 spc pppd[1143]: Hangup (SIGHUP) Mar 9 16:36:08 spc pppd[1143]: Modem hangup Mar 9 16:36:08 spc pppd[1143]: Connection terminated. Mar 9 16:36:08 spc pppd[1143]: Exit. 2.6.11 works fine: Mar 9 16:40:03 spc pppd[1106]: pppd 2.4.1 started by steven, uid 501 Mar 9 16:40:03 spc pppd[1106]: Using interface ppp0 Mar 9 16:40:03 spc pppd[1106]: Connect: ppp0 <--> /dev/ttyS1 Mar 9 16:40:03 spc pppd[1106]: kernel does not support PPP filtering Mar 9 16:40:04 spc pppd[1106]: local IP address 216.31.65.65 Mar 9 16:40:04 spc pppd[1106]: remote IP address 216.31.65.1 Mar 9 16:40:04 spc pppd[1106]: primary DNS address 216.234.192.92 Mar 9 16:40:04 spc pppd[1106]: secondary DNS address 216.234.213.130 Steven - 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: current linus bk, error mounting root
Jon Smirl wrote: On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote: Jon Smirl wrote: Something in the last 24hrs in linus bk broke my ability to mount root: Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root Switchroot: mount failed 22 umount /initrd/dev failed: 2 If I back off a day everything works again. Root is on Intel ICH5 SATA drive. dmesg output? Can you verify that -bk4 works, and -bk5 breaks? bk4 works. I don't have a serial port hooked up so there is no way to get dmesg, but I don't see anything obvious on the screen scrolling by. I'll check bk5 next. It would be much more convenient if the bkN releases were tagged in Linus bk. Yes, and name them -preN instead. ;) I had a slightly different problem mounting root with an earlier -mm, which was fixed by setting CONFIG_BASE_FULL=y. I saw that option enter the Linus tree recently, so that might be something you could try. Steven - 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/
PPPD fails on recent 2.6.11-bk
Last night, I did a bk pull from linux.bkbits.net/linux-2.6, built and rebooted, and the pppd (version 2.4.2) failed to start after the modem at the ISP end answered. I usually keep the kernel fairly up-to-date with bk, and I'm certain that 2.6.11-vanilla ran pppd just fine a few days earlier. I rebooted to an older kernel (2.6.6) and pppd ran OK. I retested with the 2.6.11-plus kernel, and it was still broken. Due to my slow connection (56k) and slow machine, I wasn't able to further narrow down when this failure was introduced, but I may be able to do that tonight on my home machine. Sorry, I don't have the time or hardware to work on this during the day. If anyone can test a recent 2.6.11-bk-current kernel with pppd on dialup, that would be helpful. Steven - 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/
PPPD fails on recent 2.6.11-bk
Last night, I did a bk pull from linux.bkbits.net/linux-2.6, built and rebooted, and the pppd (version 2.4.2) failed to start after the modem at the ISP end answered. I usually keep the kernel fairly up-to-date with bk, and I'm certain that 2.6.11-vanilla ran pppd just fine a few days earlier. I rebooted to an older kernel (2.6.6) and pppd ran OK. I retested with the 2.6.11-plus kernel, and it was still broken. Due to my slow connection (56k) and slow machine, I wasn't able to further narrow down when this failure was introduced, but I may be able to do that tonight on my home machine. Sorry, I don't have the time or hardware to work on this during the day. If anyone can test a recent 2.6.11-bk-current kernel with pppd on dialup, that would be helpful. Steven - 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: current linus bk, error mounting root
Jon Smirl wrote: On Wed, 09 Mar 2005 12:16:44 -0500, Jeff Garzik [EMAIL PROTECTED] wrote: Jon Smirl wrote: Something in the last 24hrs in linus bk broke my ability to mount root: Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root Switchroot: mount failed 22 umount /initrd/dev failed: 2 If I back off a day everything works again. Root is on Intel ICH5 SATA drive. dmesg output? Can you verify that -bk4 works, and -bk5 breaks? bk4 works. I don't have a serial port hooked up so there is no way to get dmesg, but I don't see anything obvious on the screen scrolling by. I'll check bk5 next. It would be much more convenient if the bkN releases were tagged in Linus bk. Yes, and name them -preN instead. ;) I had a slightly different problem mounting root with an earlier -mm, which was fixed by setting CONFIG_BASE_FULL=y. I saw that option enter the Linus tree recently, so that might be something you could try. Steven - 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/
Problem with PPPD on dialup with 2.6.11-bk1 and later; 2.6.11 is OK
Earlier today, I reported PPPD fails on recent 2.6.11-bk. I've narrowed the problem down to between 2.6.11 and 2.6.11-bk1. I get this with 2.6.11-bk1: (two attempts) Mar 9 16:34:32 spc pppd[1142]: pppd 2.4.1 started by steven, uid 501 Mar 9 16:34:32 spc pppd[1142]: Using interface ppp0 Mar 9 16:34:32 spc pppd[1142]: Connect: ppp0 -- /dev/ttyS1 Mar 9 16:34:56 spc pppd[1142]: Hangup (SIGHUP) Mar 9 16:34:56 spc pppd[1142]: Modem hangup Mar 9 16:34:56 spc pppd[1142]: Connection terminated. Mar 9 16:34:56 spc pppd[1142]: Exit. Mar 9 16:35:44 spc pppd[1143]: pppd 2.4.1 started by steven, uid 501 Mar 9 16:35:44 spc pppd[1143]: Using interface ppp0 Mar 9 16:35:44 spc pppd[1143]: Connect: ppp0 -- /dev/ttyS1 Mar 9 16:36:08 spc pppd[1143]: Hangup (SIGHUP) Mar 9 16:36:08 spc pppd[1143]: Modem hangup Mar 9 16:36:08 spc pppd[1143]: Connection terminated. Mar 9 16:36:08 spc pppd[1143]: Exit. 2.6.11 works fine: Mar 9 16:40:03 spc pppd[1106]: pppd 2.4.1 started by steven, uid 501 Mar 9 16:40:03 spc pppd[1106]: Using interface ppp0 Mar 9 16:40:03 spc pppd[1106]: Connect: ppp0 -- /dev/ttyS1 Mar 9 16:40:03 spc pppd[1106]: kernel does not support PPP filtering Mar 9 16:40:04 spc pppd[1106]: local IP address 216.31.65.65 Mar 9 16:40:04 spc pppd[1106]: remote IP address 216.31.65.1 Mar 9 16:40:04 spc pppd[1106]: primary DNS address 216.234.192.92 Mar 9 16:40:04 spc pppd[1106]: secondary DNS address 216.234.213.130 Steven - 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: Problem with PPPD on dialup with 2.6.11-bk1 and later; 2.6.11 is OK
Today at 04:57:37 pm, I wrote: Earlier today, I reported PPPD fails on recent 2.6.11-bk. I've narrowed the problem down to between 2.6.11 and 2.6.11-bk1. I get this with 2.6.11-bk1: (two attempts) Mar 9 16:34:32 spc pppd[1142]: pppd 2.4.1 started by steven, uid 501 Mar 9 16:34:32 spc pppd[1142]: Using interface ppp0 Mar 9 16:34:32 spc pppd[1142]: Connect: ppp0 -- /dev/ttyS1 Mar 9 16:34:56 spc pppd[1142]: Hangup (SIGHUP) Mar 9 16:34:56 spc pppd[1142]: Modem hangup Mar 9 16:34:56 spc pppd[1142]: Connection terminated. Mar 9 16:34:56 spc pppd[1142]: Exit. Searching lkml archive, I found: http://marc.theaimsgroup.com/?l=linux-kernelm=111031501416334w=2 I also found that reverting that patch made the problem go away for 2.6.11-bk1. The bookmarkable link for this changeset is here: http://linus.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]|[EMAIL PROTECTED] Stephen Hemminger also wrote: (Someting's busted with serial in 2.6.11 latest) Some checkin since 2.6.11 has caused the serial driver to drop characters. Console output is chopped and messages are garbled. Even the shell prompt gets truncated. Hope this helps, Steven - 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: RFD: Kernel release numbering
Jeff Garzik wrote: Linus Torvalds wrote: I've long since decided that there's no point to making "-pre". What's the difference between a "-pre" and a daily -bk snapshot? Really? Several non-BK developers use the first -rc1 as a merge point. Others simply trust that _Linus_ has a lot more smarts than an automated script, about deciding when a good testing point should occur. Holy Penguin Pee has value, they feel. So when I do a release, it _is_ an -rc. The fact that people have trouble understanding this is not _my_ fault. If you want people to start testing, a good first step would be understanding why this is so. Users have been trained that -rc means "serious bugfixes only". You are trying to re-train them. That just won't work. When you do an -rc1 or -rc2, it is not serious bugfixes only. _Especially_ rc1. rc1 is in no way "bugfixes only." Non-BK developers just treat the first couple -rc's as a merge point, while the rest of us BK developers have already gone into "send bugfixes only" mode. You are fighting an uphill battle against user perceptions and training. Jeff Here's an idea which might just be too simple, but here it is anyway: Modifiy the bk snapshot scripts to name the 2.6.x series snapshots as -PREy instead of -BKy. That way, the general population of users will see the -bk snapshots as -pre releases. According to Linus, pre == bk. So, name them as such. Linus, wait for at least two weeks before releasing the first -rc. That way, the bulk on the thundering herd of patches will be hopefully be merged by then. And users will have 2.6.x-PRE[1..14] to test. The hard part for the kernel.org script writer might be to disable the -bk/-pre snapshot once the first -rc is out. Since your _intent_ is that an -rc really be an -rc, make it so. It shouldn't take more than a release or two to train the maintainers that the post-2.6.11 -rc's are _really_ release candidates. Steven - 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: RFD: Kernel release numbering
Jeff Garzik wrote: Linus Torvalds wrote: I've long since decided that there's no point to making -pre. What's the difference between a -pre and a daily -bk snapshot? Really? Several non-BK developers use the first -rc1 as a merge point. Others simply trust that _Linus_ has a lot more smarts than an automated script, about deciding when a good testing point should occur. Holy Penguin Pee has value, they feel. So when I do a release, it _is_ an -rc. The fact that people have trouble understanding this is not _my_ fault. If you want people to start testing, a good first step would be understanding why this is so. Users have been trained that -rc means serious bugfixes only. You are trying to re-train them. That just won't work. When you do an -rc1 or -rc2, it is not serious bugfixes only. _Especially_ rc1. rc1 is in no way bugfixes only. Non-BK developers just treat the first couple -rc's as a merge point, while the rest of us BK developers have already gone into send bugfixes only mode. You are fighting an uphill battle against user perceptions and training. Jeff Here's an idea which might just be too simple, but here it is anyway: Modifiy the bk snapshot scripts to name the 2.6.x series snapshots as -PREy instead of -BKy. That way, the general population of users will see the -bk snapshots as -pre releases. According to Linus, pre == bk. So, name them as such. Linus, wait for at least two weeks before releasing the first -rc. That way, the bulk on the thundering herd of patches will be hopefully be merged by then. And users will have 2.6.x-PRE[1..14] to test. The hard part for the kernel.org script writer might be to disable the -bk/-pre snapshot once the first -rc is out. Since your _intent_ is that an -rc really be an -rc, make it so. It shouldn't take more than a release or two to train the maintainers that the post-2.6.11 -rc's are _really_ release candidates. Steven - 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: 2.6.11-rc4-mm1 (VFS: Cannot open root device "301")
Matt Mackall wrote:
On Wed, Feb 23, 2005 at 03:10:38PM -0700, Steven Cole wrote:
Andrew Morton wrote:
Steven Cole <[EMAIL PROTECTED]> wrote:
I am having trouble getting recent -mm kernels to boot on my test box.
For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
VFS: Cannot open root device "301" or unknown-block(3,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(3,1)
[snipped]
Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
then retest.
Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
missing.
Can you retry CONFIG_BASE_FULL=n with Andrew's patch?
You may need to boot back into a sane kernel for LILO to operate properly.
--- 25/drivers/ide/ide-probe.c~ide_init_disk-fix Wed Feb 23 16:24:44 2005
+++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
@@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unregister_region)
void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
{
ide_hwif_t *hwif = drive->hwif;
- unsigned int unit = drive->select.all & (1 << 4);
+ unsigned int unit = (drive->select.all >> 4) & 1;
disk->major = hwif->major;
disk->first_minor = unit << PARTN_BITS;
Andrew's above patch fixes the hdb->hdq insanity, but I still need
CONFIG_BASE_FULL=y. I tried unsetting CONFIG_BASE_FULL, and again
got the "VFS: Cannot open root device" message (with akpm's patch).
Steven
-
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: 2.6.11-rc4-mm1 (VFS: Cannot open root device "301")
Matt Mackall wrote:
On Wed, Feb 23, 2005 at 03:10:38PM -0700, Steven Cole wrote:
Andrew Morton wrote:
Steven Cole <[EMAIL PROTECTED]> wrote:
I am having trouble getting recent -mm kernels to boot on my test box.
For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
VFS: Cannot open root device "301" or unknown-block(3,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(3,1)
[snipped]
Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
then retest.
Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
missing.
Can you retry CONFIG_BASE_FULL=n with Andrew's patch?
You may need to boot back into a sane kernel for LILO to operate properly.
--- 25/drivers/ide/ide-probe.c~ide_init_disk-fix Wed Feb 23 16:24:44 2005
+++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
@@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unregister_region)
void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
{
ide_hwif_t *hwif = drive->hwif;
- unsigned int unit = drive->select.all & (1 << 4);
+ unsigned int unit = (drive->select.all >> 4) & 1;
disk->major = hwif->major;
disk->first_minor = unit << PARTN_BITS;
Andrew's above patch fixes the hdb->hdq insanity, but I still need
CONFIG_BASE_FULL=y. I tried unsetting CONFIG_BASE_FULL, and again
got the "VFS: Cannot open root device" message (with akpm's patch).
Steven
-
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: 2.6.11-rc4-mm1 (VFS: Cannot open root device 301)
Matt Mackall wrote:
On Wed, Feb 23, 2005 at 03:10:38PM -0700, Steven Cole wrote:
Andrew Morton wrote:
Steven Cole [EMAIL PROTECTED] wrote:
I am having trouble getting recent -mm kernels to boot on my test box.
For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
VFS: Cannot open root device 301 or unknown-block(3,1)
Please append a correct root= boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(3,1)
[snipped]
Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
then retest.
Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
missing.
Can you retry CONFIG_BASE_FULL=n with Andrew's patch?
You may need to boot back into a sane kernel for LILO to operate properly.
--- 25/drivers/ide/ide-probe.c~ide_init_disk-fix Wed Feb 23 16:24:44 2005
+++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
@@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unregister_region)
void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
{
ide_hwif_t *hwif = drive-hwif;
- unsigned int unit = drive-select.all (1 4);
+ unsigned int unit = (drive-select.all 4) 1;
disk-major = hwif-major;
disk-first_minor = unit PARTN_BITS;
Andrew's above patch fixes the hdb-hdq insanity, but I still need
CONFIG_BASE_FULL=y. I tried unsetting CONFIG_BASE_FULL, and again
got the VFS: Cannot open root device message (with akpm's patch).
Steven
-
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: 2.6.11-rc4-mm1 (VFS: Cannot open root device 301)
Matt Mackall wrote:
On Wed, Feb 23, 2005 at 03:10:38PM -0700, Steven Cole wrote:
Andrew Morton wrote:
Steven Cole [EMAIL PROTECTED] wrote:
I am having trouble getting recent -mm kernels to boot on my test box.
For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
VFS: Cannot open root device 301 or unknown-block(3,1)
Please append a correct root= boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(3,1)
[snipped]
Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
then retest.
Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
missing.
Can you retry CONFIG_BASE_FULL=n with Andrew's patch?
You may need to boot back into a sane kernel for LILO to operate properly.
--- 25/drivers/ide/ide-probe.c~ide_init_disk-fix Wed Feb 23 16:24:44 2005
+++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
@@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unregister_region)
void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
{
ide_hwif_t *hwif = drive-hwif;
- unsigned int unit = drive-select.all (1 4);
+ unsigned int unit = (drive-select.all 4) 1;
disk-major = hwif-major;
disk-first_minor = unit PARTN_BITS;
Andrew's above patch fixes the hdb-hdq insanity, but I still need
CONFIG_BASE_FULL=y. I tried unsetting CONFIG_BASE_FULL, and again
got the VFS: Cannot open root device message (with akpm's patch).
Steven
-
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: 2.6.11-rc4-mm1 (VFS: Cannot open root device "301")
Steven Cole wrote: Andrew Morton wrote: Steven Cole <[EMAIL PROTECTED]> wrote: I am having trouble getting recent -mm kernels to boot on my test box. For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following: VFS: Cannot open root device "301" or unknown-block(3,1) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1) [snipped] Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0, then retest. Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be missing. [EMAIL PROTECTED] steven]# uname -r 2.6.11-rc4-mm1-GX110 [EMAIL PROTECTED] steven]# mount -t reiser4 /dev/hdb1 /reiser4_testing mount: special device /dev/hdb1 does not exist Reading another post (and looking in /dev), I tried hdq: [EMAIL PROTECTED] steven]# mount -t reiser4 /dev/hdq1 /reiser4_testing [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 75M 214M 26% / /dev/hda9 reiserfs8.3G 3.9G 4.4G 48% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.7G 5.4G 24% /usr /dev/hda7 ext31.9G 86M 1.7G 5% /var /dev/hdq1 reiser4 18G 217M 18G 2% /reiser4_testing Snipped from dmesg: hda: ST320423A, ATA DISK drive hdb: WDC WD200BB-75AUA1, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: SONY CD-RW CRX160E, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 128KiB hda: 40011300 sectors (20485 MB) w/512KiB Cache, CHS=39693/16/63, UDMA(66) hda: cache flushes not supported /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 > hdb: max request size: 128KiB hdb: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(66) hdb: cache flushes not supported /dev/ide/host0/bus0/target1/lun0: p1 Steven (Replying to myself) I decided to fix 2.6.11-rc3-mm1 with CONFIG_BASE_FULL=y and see if the hdb/hdq confusion existed with that earlier kernel, but when I ran lilo, I got a "Fatal: cache_add: LILO internal error" message. [EMAIL PROTECTED] steven]# /sbin/lilo -v LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2004 John Coffman Released 17-Nov-2004, and compiled at 20:03:17 on Jan 15 2005 Reading boot sector from /dev/hda Fatal: cache_add: LILO internal error This box is still running 2.6.11-rc4-mm1 from above, and was booted with append="root=0301" accidentally left in lilo.conf from earlier testing. Steven - 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: 2.6.11-rc4-mm1 (VFS: Cannot open root device "301")
Andrew Morton wrote: Steven Cole <[EMAIL PROTECTED]> wrote: I am having trouble getting recent -mm kernels to boot on my test box. For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following: VFS: Cannot open root device "301" or unknown-block(3,1) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1) [snipped] Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0, then retest. Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be missing. [EMAIL PROTECTED] steven]# uname -r 2.6.11-rc4-mm1-GX110 [EMAIL PROTECTED] steven]# mount -t reiser4 /dev/hdb1 /reiser4_testing mount: special device /dev/hdb1 does not exist Reading another post (and looking in /dev), I tried hdq: [EMAIL PROTECTED] steven]# mount -t reiser4 /dev/hdq1 /reiser4_testing [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 75M 214M 26% / /dev/hda9 reiserfs8.3G 3.9G 4.4G 48% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.7G 5.4G 24% /usr /dev/hda7 ext31.9G 86M 1.7G 5% /var /dev/hdq1 reiser4 18G 217M 18G 2% /reiser4_testing Snipped from dmesg: hda: ST320423A, ATA DISK drive hdb: WDC WD200BB-75AUA1, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: SONY CD-RW CRX160E, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 128KiB hda: 40011300 sectors (20485 MB) w/512KiB Cache, CHS=39693/16/63, UDMA(66) hda: cache flushes not supported /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 > hdb: max request size: 128KiB hdb: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(66) hdb: cache flushes not supported /dev/ide/host0/bus0/target1/lun0: p1 Steven - 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: 2.6.11-rc4-mm1 (VFS: Cannot open root device "301")
Andrew Morton wrote: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/ - Various fixes and updates all over the place. Things seem to have slowed down a bit. I am having trouble getting recent -mm kernels to boot on my test box. For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following: VFS: Cannot open root device "301" or unknown-block(3,1) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1) 2.6.11-rc2-mm1 boots fine, and so do plain -rc3 and -rc4. I copied a working .config from an earlier kernel(-rc3), and ran make oldconfig, answering most of the new questions 'n'. I did try appending root=0301 (which worked last year after similar symptoms, but that didn't help this time). The root fs is ext3, which is compiled in. Any help appreciated. Steven Output of grep ^CONFIG .config: CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCALVERSION="-GX110" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_BASE_SMALL=1 CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 CONFIG_X86_PC=y CONFIG_MPENTIUMIII=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_P4THERMAL=y CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_EDD=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_PHYSICAL_START=0x10 CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_LEGACY_PROC=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=32000 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_XFRM=y CONFIG_NETDEVICES=y CONFIG_NET_ETHERNET=y CONFIG_MII=y CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=y CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_LIBPS2=y CONFIG_SOUND_GAMEPORT=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_FTAPE=y CONFIG_ZFTAPE=y CONFIG_ZFT_DFLT_BLK_SZ=10240 CONFIG_ZFT_COMPRESSOR=y CONFIG_FT_NR_BUFFERS=3 CONFIG_FT_PROC_FS=y CONFIG_FT_NORMAL_DEBUG=y CONFIG_FT_STD_FDC=y CONFIG_FT_FDC_THR=8 CONFIG_FT_FDC_MAX_RATE=2000 CONFIG_FT_ALPHA_CLOCK=0 CONFIG_AGP=y CONFIG_AGP_INTEL=y CONFIG_VIDEO_DEV=y CONFIG_VIDEO_SELECT=y CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_REISER4_FS=y CONFIG_REISERFS_FS=y CONFIG_ISO9660_FS=y CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=y CONFIG_NTFS_RW=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y CONFIG_DEVFS_FS=y CONFIG_TMPFS=y CONFIG_RAMFS=y CONFIG_PARTITION_ADVANCED=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_UTF8=y CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_FRAME_POINTER=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_SECURITY=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_CAPABILITIES=y CONFIG_CRC_CCITT=y CONFIG_CRC32=y CONFIG_LIBCRC32C=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at
Re: 2.6.11-rc4-mm1 (VFS: Cannot open root device 301)
Andrew Morton wrote: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/ - Various fixes and updates all over the place. Things seem to have slowed down a bit. I am having trouble getting recent -mm kernels to boot on my test box. For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following: VFS: Cannot open root device 301 or unknown-block(3,1) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1) 2.6.11-rc2-mm1 boots fine, and so do plain -rc3 and -rc4. I copied a working .config from an earlier kernel(-rc3), and ran make oldconfig, answering most of the new questions 'n'. I did try appending root=0301 (which worked last year after similar symptoms, but that didn't help this time). The root fs is ext3, which is compiled in. Any help appreciated. Steven Output of grep ^CONFIG .config: CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCALVERSION=-GX110 CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_BASE_SMALL=1 CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 CONFIG_X86_PC=y CONFIG_MPENTIUMIII=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_P4THERMAL=y CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_EDD=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_PHYSICAL_START=0x10 CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_LEGACY_PROC=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=32000 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_XFRM=y CONFIG_NETDEVICES=y CONFIG_NET_ETHERNET=y CONFIG_MII=y CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=y CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_LIBPS2=y CONFIG_SOUND_GAMEPORT=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_FTAPE=y CONFIG_ZFTAPE=y CONFIG_ZFT_DFLT_BLK_SZ=10240 CONFIG_ZFT_COMPRESSOR=y CONFIG_FT_NR_BUFFERS=3 CONFIG_FT_PROC_FS=y CONFIG_FT_NORMAL_DEBUG=y CONFIG_FT_STD_FDC=y CONFIG_FT_FDC_THR=8 CONFIG_FT_FDC_MAX_RATE=2000 CONFIG_FT_ALPHA_CLOCK=0 CONFIG_AGP=y CONFIG_AGP_INTEL=y CONFIG_VIDEO_DEV=y CONFIG_VIDEO_SELECT=y CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_REISER4_FS=y CONFIG_REISERFS_FS=y CONFIG_ISO9660_FS=y CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 CONFIG_NTFS_FS=y CONFIG_NTFS_RW=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y CONFIG_DEVFS_FS=y CONFIG_TMPFS=y CONFIG_RAMFS=y CONFIG_PARTITION_ADVANCED=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT=iso8859-1 CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_UTF8=y CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_FRAME_POINTER=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_SECURITY=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_CAPABILITIES=y CONFIG_CRC_CCITT=y CONFIG_CRC32=y CONFIG_LIBCRC32C=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at
Re: 2.6.11-rc4-mm1 (VFS: Cannot open root device 301)
Andrew Morton wrote: Steven Cole [EMAIL PROTECTED] wrote: I am having trouble getting recent -mm kernels to boot on my test box. For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following: VFS: Cannot open root device 301 or unknown-block(3,1) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1) [snipped] Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0, then retest. Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be missing. [EMAIL PROTECTED] steven]# uname -r 2.6.11-rc4-mm1-GX110 [EMAIL PROTECTED] steven]# mount -t reiser4 /dev/hdb1 /reiser4_testing mount: special device /dev/hdb1 does not exist Reading another post (and looking in /dev), I tried hdq: [EMAIL PROTECTED] steven]# mount -t reiser4 /dev/hdq1 /reiser4_testing [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 75M 214M 26% / /dev/hda9 reiserfs8.3G 3.9G 4.4G 48% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.7G 5.4G 24% /usr /dev/hda7 ext31.9G 86M 1.7G 5% /var /dev/hdq1 reiser4 18G 217M 18G 2% /reiser4_testing Snipped from dmesg: hda: ST320423A, ATA DISK drive hdb: WDC WD200BB-75AUA1, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: SONY CD-RW CRX160E, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 128KiB hda: 40011300 sectors (20485 MB) w/512KiB Cache, CHS=39693/16/63, UDMA(66) hda: cache flushes not supported /dev/ide/host0/bus0/target0/lun0: p1 p2 p5 p6 p7 p8 p9 hdb: max request size: 128KiB hdb: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(66) hdb: cache flushes not supported /dev/ide/host0/bus0/target1/lun0: p1 Steven - 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: 2.6.11-rc4-mm1 (VFS: Cannot open root device 301)
Steven Cole wrote: Andrew Morton wrote: Steven Cole [EMAIL PROTECTED] wrote: I am having trouble getting recent -mm kernels to boot on my test box. For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following: VFS: Cannot open root device 301 or unknown-block(3,1) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1) [snipped] Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0, then retest. Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be missing. [EMAIL PROTECTED] steven]# uname -r 2.6.11-rc4-mm1-GX110 [EMAIL PROTECTED] steven]# mount -t reiser4 /dev/hdb1 /reiser4_testing mount: special device /dev/hdb1 does not exist Reading another post (and looking in /dev), I tried hdq: [EMAIL PROTECTED] steven]# mount -t reiser4 /dev/hdq1 /reiser4_testing [EMAIL PROTECTED] steven]# df -T FilesystemTypeSize Used Avail Use% Mounted on /dev/hda1 ext3304M 75M 214M 26% / /dev/hda9 reiserfs8.3G 3.9G 4.4G 48% /home /dev/hda8 ext3464M 8.1M 432M 2% /tmp /dev/hda6 ext37.4G 1.7G 5.4G 24% /usr /dev/hda7 ext31.9G 86M 1.7G 5% /var /dev/hdq1 reiser4 18G 217M 18G 2% /reiser4_testing Snipped from dmesg: hda: ST320423A, ATA DISK drive hdb: WDC WD200BB-75AUA1, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: SONY CD-RW CRX160E, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 128KiB hda: 40011300 sectors (20485 MB) w/512KiB Cache, CHS=39693/16/63, UDMA(66) hda: cache flushes not supported /dev/ide/host0/bus0/target0/lun0: p1 p2 p5 p6 p7 p8 p9 hdb: max request size: 128KiB hdb: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(66) hdb: cache flushes not supported /dev/ide/host0/bus0/target1/lun0: p1 Steven (Replying to myself) I decided to fix 2.6.11-rc3-mm1 with CONFIG_BASE_FULL=y and see if the hdb/hdq confusion existed with that earlier kernel, but when I ran lilo, I got a Fatal: cache_add: LILO internal error message. [EMAIL PROTECTED] steven]# /sbin/lilo -v LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2004 John Coffman Released 17-Nov-2004, and compiled at 20:03:17 on Jan 15 2005 Reading boot sector from /dev/hda Fatal: cache_add: LILO internal error This box is still running 2.6.11-rc4-mm1 from above, and was booted with append=root=0301 accidentally left in lilo.conf from earlier testing. Steven - 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: 2.4.6-ac1 will not build, 2.4.6 ok
On Friday 06 July 2001 16:35, Tom Diehl wrote:
> Hi all,
> This is my first bug report so please go easy on me if I screw it up.
> The kernel 2.4.6-ac1
> The build machine AMD k6-2-350 with 128Megs of memory
> I get the following errors when I try to build ac1. It builds ok when
> just building 2.4.6 with the same config file run through make old_config,
> so I guess this is some kind of problem with ac1.
I posted a patch for this a few hours after 2.4.6-ac1 became available, but
there have been problems with lkml archive servers in the interim, so here
is my patch again. If you look in drivers/parport/parport_pc.c, you'll see that
the new code is bracketed by:
#if defined (CONFIG_PNPBIOS) || defined (CONFIG_PNPBIOS_MODULE)
new stuff for 2.4.6-ac1
#endif
Steven
--- linux-2.4.6-ac1/drivers/parport/parport_pc.c.original    Wed Jul  4 15:22:28
2001
+++ linux/drivers/parport/parport_pc.c  Wed Jul  4 15:26:03 2001
@@Â -2828,12 +2828,14 @@
    detect_and_report_smsc ();
 #endif
Â
+#if defined (CONFIG_PNPBIOS) || defined (CONFIG_PNPBIOS_MODULE)
    dev=NULL;
    while ((dev=pnpbios_find_device("PNP0400",dev)))
        count+=init_pnp040x(dev);
    dev=NULL;
     while ((dev=pnpbios_find_device("PNP0401",dev)))
         count+=init_pnp040x(dev);
+#endif
Â
    /* Onboard SuperIO chipsets that show themselves on the PCI bus. */
    count += parport_pc_init_superio (autoirq, autodma);
-
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: 2.4.6-ac1 will not build, 2.4.6 ok
On Friday 06 July 2001 16:35, Tom Diehl wrote: Hi all, This is my first bug report so please go easy on me if I screw it up. The kernel 2.4.6-ac1 The build machine AMD k6-2-350 with 128Megs of memory I get the following errors when I try to build ac1. It builds ok when just building 2.4.6 with the same config file run through make old_config, so I guess this is some kind of problem with ac1. I posted a patch for this a few hours after 2.4.6-ac1 became available, but there have been problems with lkml archive servers in the interim, so here is my patch again. If you look in drivers/parport/parport_pc.c, you'll see that the new code is bracketed by: #if defined (CONFIG_PNPBIOS) || defined (CONFIG_PNPBIOS_MODULE) new stuff for 2.4.6-ac1 #endif Steven --- linux-2.4.6-ac1/drivers/parport/parport_pc.c.original    Wed Jul  4 15:22:28 2001 +++ linux/drivers/parport/parport_pc.c  Wed Jul  4 15:26:03 2001 @@ -2828,12 +2828,14 @@     detect_and_report_smsc ();  #endif  +#if defined (CONFIG_PNPBIOS) || defined (CONFIG_PNPBIOS_MODULE)     dev=NULL;     while ((dev=pnpbios_find_device(PNP0400,dev)))         count+=init_pnp040x(dev);     dev=NULL;      while ((dev=pnpbios_find_device(PNP0401,dev)))          count+=init_pnp040x(dev); +#endif      /* Onboard SuperIO chipsets that show themselves on the PCI bus. */     count += parport_pc_init_superio (autoirq, autodma); - 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/
[PATCH] 2.4.6-ac1 fix error in drivers/parport/parport_pc.c
I got this error building 2.4.6-ac1.
drivers/parport/driver.o: In function `parport_pc_find_ports':
drivers/parport/driver.o(.text.init+0x3f2): undefined reference to `init_pnp040x'
drivers/parport/driver.o(.text.init+0x400): undefined reference to
`pnpbios_find_device'
drivers/parport/driver.o(.text.init+0x412): undefined reference to `init_pnp040x'
drivers/parport/driver.o(.text.init+0x420): undefined reference to
`pnpbios_find_device'
make: *** [vmlinux] Error 1
My access to lkml archives is temporarily gone (marc.theaimsgroup.com is down
and other archive sites aren't very current), so please forgive me if someone else
has already posted this fix.
Here is a patch which may be correct. It worked for me.
Steven
--- linux-2.4.6-ac1/drivers/parport/parport_pc.c.original Wed Jul 4 15:22:28
2001
+++ linux/drivers/parport/parport_pc.c Wed Jul 4 15:26:03 2001
@@ -2828,12 +2828,14 @@
detect_and_report_smsc ();
#endif
+#if defined (CONFIG_PNPBIOS) || defined (CONFIG_PNPBIOS_MODULE)
dev=NULL;
while ((dev=pnpbios_find_device("PNP0400",dev)))
count+=init_pnp040x(dev);
dev=NULL;
while ((dev=pnpbios_find_device("PNP0401",dev)))
count+=init_pnp040x(dev);
+#endif
/* Onboard SuperIO chipsets that show themselves on the PCI bus. */
count += parport_pc_init_superio (autoirq, autodma);
-
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/
[PATCH] 2.4.6-ac1 fix error in drivers/parport/parport_pc.c
I got this error building 2.4.6-ac1. drivers/parport/driver.o: In function `parport_pc_find_ports': drivers/parport/driver.o(.text.init+0x3f2): undefined reference to `init_pnp040x' drivers/parport/driver.o(.text.init+0x400): undefined reference to `pnpbios_find_device' drivers/parport/driver.o(.text.init+0x412): undefined reference to `init_pnp040x' drivers/parport/driver.o(.text.init+0x420): undefined reference to `pnpbios_find_device' make: *** [vmlinux] Error 1 My access to lkml archives is temporarily gone (marc.theaimsgroup.com is down and other archive sites aren't very current), so please forgive me if someone else has already posted this fix. Here is a patch which may be correct. It worked for me. Steven --- linux-2.4.6-ac1/drivers/parport/parport_pc.c.original Wed Jul 4 15:22:28 2001 +++ linux/drivers/parport/parport_pc.c Wed Jul 4 15:26:03 2001 @@ -2828,12 +2828,14 @@ detect_and_report_smsc (); #endif +#if defined (CONFIG_PNPBIOS) || defined (CONFIG_PNPBIOS_MODULE) dev=NULL; while ((dev=pnpbios_find_device(PNP0400,dev))) count+=init_pnp040x(dev); dev=NULL; while ((dev=pnpbios_find_device(PNP0401,dev))) count+=init_pnp040x(dev); +#endif /* Onboard SuperIO chipsets that show themselves on the PCI bus. */ count += parport_pc_init_superio (autoirq, autodma); - 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: 2.4.5-ac20 problems with drivers/net/Config.in and make xconfig
On Thursday 28 June 2001 20:18, Keith Owens wrote: > On Thu, 28 Jun 2001 10:05:58 -0600, > > Steven Cole <[EMAIL PROTECTED]> wrote: > >[root@spc linux]# make xconfig > >./tkparse < ../arch/i386/config.in >> kconfig.tk > >make[1]: *** [kconfig.tk] Error 139 > >make[1]: Leaving directory `/usr/src/linux-2.4.5-ac20/scripts' > > Sigh. I wish people making big changes to config files would check > that the change works for all the variants of make *config. > > Index: 5.52/drivers/net/Config.in > --- 5.52/drivers/net/Config.in Fri, 29 Jun 2001 11:39:55 +1000 kaos > (linux-2.4/l/c/9_Config.in 1.1.2.2.1.4.1.12 644) +++ > 5.52(w)/drivers/net/Config.in Fri, 29 Jun 2001 12:14:23 +1000 kaos > (linux-2.4/l/c/9_Config.in 1.1.2.2.1.4.1.12 644) @@ -16,7 +16,7 @@ if [ > "$CONFIG_EXPERIMENTAL" = "y" ]; the > fi > > if [ "$CONFIG_ISAPNP" = "y" ]; then > - tristate 'General Instruments Surfboard 1000' CONFIG_NET_SB1000 > $CONFIG_ISAPNP + tristate 'General Instruments Surfboard 1000' > CONFIG_NET_SB1000 fi > > # > @@ -204,7 +204,6 @@ bool 'Ethernet (10 or 100Mbit)' CONFIG_N >dep_tristate 'D-Link DE600 pocket adapter support' CONFIG_DE600 > $CONFIG_ISA dep_tristate 'D-Link DE620 pocket adapter support' > CONFIG_DE620 $CONFIG_ISA fi > -fi > > endmenu Here is a variant of Keith's patch. The free-floating "fi" at line 207 was the result of a deleted line "if [ "$CONFIG_NET_ETHERNET" = "y" ]; then". The indentation was the major clue. This patch was made against 2.4.5-ac21. Steven --- linux/drivers/net/Config.in.originalFri Jun 29 07:17:57 2001 +++ linux/drivers/net/Config.in Fri Jun 29 07:23:02 2001 @@ -16,7 +16,7 @@ fi if [ "$CONFIG_ISAPNP" = "y" ]; then - tristate 'General Instruments Surfboard 1000' CONFIG_NET_SB1000 $CONFIG_ISAPNP + tristate 'General Instruments Surfboard 1000' CONFIG_NET_SB1000 fi # @@ -27,6 +27,7 @@ comment 'Ethernet (10 or 100Mbit)' bool 'Ethernet (10 or 100Mbit)' CONFIG_NET_ETHERNET +if [ "$CONFIG_NET_ETHERNET" = "y" ]; then if [ "$CONFIG_ARM" = "y" ]; then dep_bool ' ARM EBSA110 AM79C961A support' CONFIG_ARM_AM79C961A $CONFIG_ARCH_EBSA110 if [ "$CONFIG_ARCH_ACORN" = "y" ]; then - 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: 2.4.5-ac20 problems with drivers/net/Config.in and make xconfig
On Thursday 28 June 2001 20:18, Keith Owens wrote: On Thu, 28 Jun 2001 10:05:58 -0600, Steven Cole [EMAIL PROTECTED] wrote: [root@spc linux]# make xconfig ./tkparse ../arch/i386/config.in kconfig.tk make[1]: *** [kconfig.tk] Error 139 make[1]: Leaving directory `/usr/src/linux-2.4.5-ac20/scripts' Sigh. I wish people making big changes to config files would check that the change works for all the variants of make *config. Index: 5.52/drivers/net/Config.in --- 5.52/drivers/net/Config.in Fri, 29 Jun 2001 11:39:55 +1000 kaos (linux-2.4/l/c/9_Config.in 1.1.2.2.1.4.1.12 644) +++ 5.52(w)/drivers/net/Config.in Fri, 29 Jun 2001 12:14:23 +1000 kaos (linux-2.4/l/c/9_Config.in 1.1.2.2.1.4.1.12 644) @@ -16,7 +16,7 @@ if [ $CONFIG_EXPERIMENTAL = y ]; the fi if [ $CONFIG_ISAPNP = y ]; then - tristate 'General Instruments Surfboard 1000' CONFIG_NET_SB1000 $CONFIG_ISAPNP + tristate 'General Instruments Surfboard 1000' CONFIG_NET_SB1000 fi # @@ -204,7 +204,6 @@ bool 'Ethernet (10 or 100Mbit)' CONFIG_N dep_tristate 'D-Link DE600 pocket adapter support' CONFIG_DE600 $CONFIG_ISA dep_tristate 'D-Link DE620 pocket adapter support' CONFIG_DE620 $CONFIG_ISA fi -fi endmenu Here is a variant of Keith's patch. The free-floating fi at line 207 was the result of a deleted line if [ $CONFIG_NET_ETHERNET = y ]; then. The indentation was the major clue. This patch was made against 2.4.5-ac21. Steven --- linux/drivers/net/Config.in.originalFri Jun 29 07:17:57 2001 +++ linux/drivers/net/Config.in Fri Jun 29 07:23:02 2001 @@ -16,7 +16,7 @@ fi if [ $CONFIG_ISAPNP = y ]; then - tristate 'General Instruments Surfboard 1000' CONFIG_NET_SB1000 $CONFIG_ISAPNP + tristate 'General Instruments Surfboard 1000' CONFIG_NET_SB1000 fi # @@ -27,6 +27,7 @@ comment 'Ethernet (10 or 100Mbit)' bool 'Ethernet (10 or 100Mbit)' CONFIG_NET_ETHERNET +if [ $CONFIG_NET_ETHERNET = y ]; then if [ $CONFIG_ARM = y ]; then dep_bool ' ARM EBSA110 AM79C961A support' CONFIG_ARM_AM79C961A $CONFIG_ARCH_EBSA110 if [ $CONFIG_ARCH_ACORN = y ]; then - 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.5-ac20 five more undocumented symbols
Hello all, In addition to the 14 new CONFIG symbols without help texts which 2.4.6-pre6 introduced, 2.4.5-ac20 has 5 more, for a total of 19 in -ac20. Here are the five new symbols in 2.4.5-ac20 which don't have Configure.help texts and likely should have. If you're the owner of these, please provide the appropriate help texts for Configure.help. Or, if they don't need no steenking help texts, please let ESR and me know that too. Thanks in advance, Steven CONFIG_FB_ATY_CT_VAIO_LCD CONFIG_MTD_CFI_BE_BYTE_SWAP CONFIG_MTD_CFI_LART_BIT_SWAP CONFIG_MTD_CFI_LE_BYTE_SWAP CONFIG_MTD_CFI_VIRTUAL_ER - 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.5-ac20 problems with drivers/net/Config.in and make xconfig
I got this familiar error with make xconfig and 2.4.5-ac20 (same as 2.4.6-pre6) drivers/net/Config.in: 149: can't handle dep_bool/dep_mbool/dep_tristate condition make[1]: *** [kconfig.tk] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.5-ac20/scripts' make: *** [xconfig] Error 2 I applied this patch written by Keith Owens (thanks Keith): --- linux/drivers/net/Config.in.originalThu Jun 28 09:52:02 2001 +++ linux/drivers/net/Config.in Thu Jun 28 09:52:25 2001 @@ -146,7 +146,11 @@ tristate ' NE/2 (ne2000 MCA version) support' CONFIG_NE2_MCA tristate ' IBM LAN Adapter/A support' CONFIG_IBMLANA fi - dep_bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI + if [ "$CONFIG_ISA" = "y" -o "$CONFIG_EISA" = "y" -o "$CONFIG_PCI" = "y" ]; then + bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI + else + define_bool CONFIG_NET_PCI n + fi if [ "$CONFIG_NET_PCI" = "y" ]; then dep_tristate 'AMD PCnet32 PCI support' CONFIG_PCNET32 $CONFIG_PCI dep_tristate 'Adaptec Starfire support (EXPERIMENTAL)' CONFIG_ADAPTEC_STARFIRE $CONFIG_PCI $CONFIG_EXPERIMENTAL And then I got: [root@spc linux]# make xconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts kconfig.tk make[1]: Entering directory `/usr/src/linux-2.4.5-ac20/scripts' cat header.tk >> ./kconfig.tk ./tkparse < ../arch/i386/config.in >> kconfig.tk make[1]: *** [kconfig.tk] Error 139 make[1]: Leaving directory `/usr/src/linux-2.4.5-ac20/scripts' make: *** [xconfig] Error 2 So, I used the old reliable make menuconfig, and it worked OK and 2.4.5-ac20 built successfully. Steven - 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: 2.4.6-pre6 cs46xx build error with CONFIG_SOUND_FUSION=m
On Thursday 28 June 2001 09:33, Alan Cox wrote: > > With CONFIG_SOUND_FUSION=m, I get the following error for 2.4.6-pre6 > > during make modules: > > > > I've got a number of older 2.4.[3,4,5] kernels, so I'll go back and try > > to figure out when the change occured, but this is the first time I've > > seen this particular build error. > > I've fixed the build bug in ac20.. just uploading now At the suggestion of Frank Davis, I tried 2.4.5-ac19, and it built just fine for me with CONFIG_SOUND_FUSION=m, and sound is also working with 2.4.5-ac19. I don't see -ac20 yet, but will try it later today with CONFIG_SOUND_FUSION=m and CONFIG_SOUND_FUSION=y. Thanks, Steven - 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.6-pre6 cs46xx build error with CONFIG_SOUND_FUSION=m
With CONFIG_SOUND_FUSION=m, I get the following error for 2.4.6-pre6 during make modules: cs46xx.c:386: conflicting types for `cs46xx_suspend_tbl' cs46xxpm-24.h:39: previous declaration of `cs46xx_suspend_tbl' cs46xx.c:387: conflicting types for `cs46xx_resume_tbl' cs46xxpm-24.h:40: previous declaration of `cs46xx_resume_tbl' cs46xx.c:5617: warning: initialization from incompatible pointer type cs46xx.c:5618: warning: initialization from incompatible pointer type cs46xx.c:5693: conflicting types for `cs46xx_suspend_tbl' cs46xx.c:386: previous declaration of `cs46xx_suspend_tbl' cs46xx.c:5702: conflicting types for `cs46xx_resume_tbl' cs46xx.c:387: previous declaration of `cs46xx_resume_tbl' make[2]: *** [cs46xx.o] Error 1 With CONFIG_SOUND_FUSION=y, 2.4.6-pre6 builds without errors, but the sound doesn't work while running 2.4.6-pre6. The sound does work with 2.4.3-20mdksmp as shipped with LM 8.0. I've got a number of older 2.4.[3,4,5] kernels, so I'll go back and try to figure out when the change occured, but this is the first time I've seen this particular build error. Steven - 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/
Fourteen new undocumented symbols in 2.4.6-pre6
Hello all, 2.4.6-pre6 introduces 14 new undocumented symbols. Would the owners please provide help texts for the following: CONFIG_CPU_SUBTYPE_SH7751 CONFIG_CPU_SUBTYPE_ST40STB1 CONFIG_HD64465_IOBASE CONFIG_MAPLE_KEYBOARD CONFIG_MAPLE_MOUSE CONFIG_SH_7751_SOLUTION_ENGINE CONFIG_SH_BIGSUR CONFIG_SH_CAT68701 CONFIG_SH_SH2000 CONFIG_SH_STB1_HARP CONFIG_SH_STB1_OVERDRIVE CONFIG_ST40_LMI_MEMORY CONFIG_TULIP_MMIO CONFIG_TULIP_MWI The SuperH ones are just items in a choice menu, so they can be one-liners. Thanks in advance, Steven - 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.6-pre6 cs46xx build error with CONFIG_SOUND_FUSION=m
With CONFIG_SOUND_FUSION=m, I get the following error for 2.4.6-pre6 during make modules: cs46xx.c:386: conflicting types for `cs46xx_suspend_tbl' cs46xxpm-24.h:39: previous declaration of `cs46xx_suspend_tbl' cs46xx.c:387: conflicting types for `cs46xx_resume_tbl' cs46xxpm-24.h:40: previous declaration of `cs46xx_resume_tbl' cs46xx.c:5617: warning: initialization from incompatible pointer type cs46xx.c:5618: warning: initialization from incompatible pointer type cs46xx.c:5693: conflicting types for `cs46xx_suspend_tbl' cs46xx.c:386: previous declaration of `cs46xx_suspend_tbl' cs46xx.c:5702: conflicting types for `cs46xx_resume_tbl' cs46xx.c:387: previous declaration of `cs46xx_resume_tbl' make[2]: *** [cs46xx.o] Error 1 With CONFIG_SOUND_FUSION=y, 2.4.6-pre6 builds without errors, but the sound doesn't work while running 2.4.6-pre6. The sound does work with 2.4.3-20mdksmp as shipped with LM 8.0. I've got a number of older 2.4.[3,4,5] kernels, so I'll go back and try to figure out when the change occured, but this is the first time I've seen this particular build error. Steven - 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.5-ac20 five more undocumented symbols
Hello all, In addition to the 14 new CONFIG symbols without help texts which 2.4.6-pre6 introduced, 2.4.5-ac20 has 5 more, for a total of 19 in -ac20. Here are the five new symbols in 2.4.5-ac20 which don't have Configure.help texts and likely should have. If you're the owner of these, please provide the appropriate help texts for Configure.help. Or, if they don't need no steenking help texts, please let ESR and me know that too. Thanks in advance, Steven CONFIG_FB_ATY_CT_VAIO_LCD CONFIG_MTD_CFI_BE_BYTE_SWAP CONFIG_MTD_CFI_LART_BIT_SWAP CONFIG_MTD_CFI_LE_BYTE_SWAP CONFIG_MTD_CFI_VIRTUAL_ER - 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: 2.4.6-pre6 cs46xx build error with CONFIG_SOUND_FUSION=m
On Thursday 28 June 2001 09:33, Alan Cox wrote: With CONFIG_SOUND_FUSION=m, I get the following error for 2.4.6-pre6 during make modules: I've got a number of older 2.4.[3,4,5] kernels, so I'll go back and try to figure out when the change occured, but this is the first time I've seen this particular build error. I've fixed the build bug in ac20.. just uploading now At the suggestion of Frank Davis, I tried 2.4.5-ac19, and it built just fine for me with CONFIG_SOUND_FUSION=m, and sound is also working with 2.4.5-ac19. I don't see -ac20 yet, but will try it later today with CONFIG_SOUND_FUSION=m and CONFIG_SOUND_FUSION=y. Thanks, Steven - 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.5-ac20 problems with drivers/net/Config.in and make xconfig
I got this familiar error with make xconfig and 2.4.5-ac20 (same as 2.4.6-pre6) drivers/net/Config.in: 149: can't handle dep_bool/dep_mbool/dep_tristate condition make[1]: *** [kconfig.tk] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.5-ac20/scripts' make: *** [xconfig] Error 2 I applied this patch written by Keith Owens (thanks Keith): --- linux/drivers/net/Config.in.originalThu Jun 28 09:52:02 2001 +++ linux/drivers/net/Config.in Thu Jun 28 09:52:25 2001 @@ -146,7 +146,11 @@ tristate ' NE/2 (ne2000 MCA version) support' CONFIG_NE2_MCA tristate ' IBM LAN Adapter/A support' CONFIG_IBMLANA fi - dep_bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI + if [ $CONFIG_ISA = y -o $CONFIG_EISA = y -o $CONFIG_PCI = y ]; then + bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI + else + define_bool CONFIG_NET_PCI n + fi if [ $CONFIG_NET_PCI = y ]; then dep_tristate 'AMD PCnet32 PCI support' CONFIG_PCNET32 $CONFIG_PCI dep_tristate 'Adaptec Starfire support (EXPERIMENTAL)' CONFIG_ADAPTEC_STARFIRE $CONFIG_PCI $CONFIG_EXPERIMENTAL And then I got: [root@spc linux]# make xconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts kconfig.tk make[1]: Entering directory `/usr/src/linux-2.4.5-ac20/scripts' cat header.tk ./kconfig.tk ./tkparse ../arch/i386/config.in kconfig.tk make[1]: *** [kconfig.tk] Error 139 make[1]: Leaving directory `/usr/src/linux-2.4.5-ac20/scripts' make: *** [xconfig] Error 2 So, I used the old reliable make menuconfig, and it worked OK and 2.4.5-ac20 built successfully. Steven - 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/
[PATCH] 2.4.6-pre6 fix drivers/net/Config.in error
I got this error for 2.4.6-pre6 for make xconfig drivers/net/Config.in: 145: can't handle dep_bool/dep_mbool/dep_tristate condition make[1]: *** [kconfig.tk] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.6-pre6/scripts' make: *** [xconfig] Error 2 This may be the proper fix. Steven --- linux/drivers/net/Config.in.originalWed Jun 27 20:39:50 2001 +++ linux/drivers/net/Config.in Wed Jun 27 20:41:28 2001 @@ -142,7 +142,7 @@ tristate ' NE/2 (ne2000 MCA version) support' CONFIG_NE2_MCA tristate ' IBM LAN Adapter/A support' CONFIG_IBMLANA fi - dep_bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI + dep_bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI $CONFIG_PCI if [ "$CONFIG_NET_PCI" = "y" ]; then dep_tristate 'AMD PCnet32 PCI support' CONFIG_PCNET32 $CONFIG_PCI dep_tristate 'Adaptec Starfire support (EXPERIMENTAL)' CONFIG_ADAPTEC_STARFIRE $CONFIG_PCI $CONFIG_EXPERIMENTAL - 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/
[PATCH] 2.4.6-pre6 fix drivers/net/Config.in error
I got this error for 2.4.6-pre6 for make xconfig drivers/net/Config.in: 145: can't handle dep_bool/dep_mbool/dep_tristate condition make[1]: *** [kconfig.tk] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.6-pre6/scripts' make: *** [xconfig] Error 2 This may be the proper fix. Steven --- linux/drivers/net/Config.in.originalWed Jun 27 20:39:50 2001 +++ linux/drivers/net/Config.in Wed Jun 27 20:41:28 2001 @@ -142,7 +142,7 @@ tristate ' NE/2 (ne2000 MCA version) support' CONFIG_NE2_MCA tristate ' IBM LAN Adapter/A support' CONFIG_IBMLANA fi - dep_bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI + dep_bool ' EISA, VLB, PCI and on board controllers' CONFIG_NET_PCI $CONFIG_PCI if [ $CONFIG_NET_PCI = y ]; then dep_tristate 'AMD PCnet32 PCI support' CONFIG_PCNET32 $CONFIG_PCI dep_tristate 'Adaptec Starfire support (EXPERIMENTAL)' CONFIG_ADAPTEC_STARFIRE $CONFIG_PCI $CONFIG_EXPERIMENTAL - 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/
[PATCH] 2.4.5-ac7 fix for rivers/net/wireless/Config.in problem
I got the following error from make xconfig: drivers/net/wireless/Config.in: 5: can't handle dep_bool/dep_mbool/dep_tristate condition make[1]: *** [kconfig.tk] Error 1 Here is a little micro patch to change the dep_tristate into a plain vanilla tristate. Steven --- linux/drivers/net/wireless/Config.in.ac7Sat Jun 2 21:27:18 2001 +++ linux/drivers/net/wireless/Config.inSat Jun 2 21:32:59 2001 @@ -2,7 +2,7 @@ # Wireless LAN device configuration # -dep_tristate ' Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards' CONFIG_AIRO + tristate ' Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards' CONFIG_AIRO if [ "$CONFIG_ALL_PPC" = "y" ]; then tristate ' Apple Airport support (built-in)' CONFIG_APPLE_AIRPORT - 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/
[PATCH] 2.4.5-ac7 fix for rivers/net/wireless/Config.in problem
I got the following error from make xconfig: drivers/net/wireless/Config.in: 5: can't handle dep_bool/dep_mbool/dep_tristate condition make[1]: *** [kconfig.tk] Error 1 Here is a little micro patch to change the dep_tristate into a plain vanilla tristate. Steven --- linux/drivers/net/wireless/Config.in.ac7Sat Jun 2 21:27:18 2001 +++ linux/drivers/net/wireless/Config.inSat Jun 2 21:32:59 2001 @@ -2,7 +2,7 @@ # Wireless LAN device configuration # -dep_tristate ' Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards' CONFIG_AIRO + tristate ' Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards' CONFIG_AIRO if [ $CONFIG_ALL_PPC = y ]; then tristate ' Apple Airport support (built-in)' CONFIG_APPLE_AIRPORT - 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: [kbuild-devel] Re: CML2 design philosophy heads-up
On Monday 21 May 2001 10:01, Tom Rini wrote: > On Mon, May 21, 2001 at 09:58:04AM -0600, Steven Cole wrote: > > On Monday 21 May 2001 09:36, Tom Rini wrote: > > > Which brings up another point, RedHat (7.1?) and Debian/woody both have > > > the option of having python2 around. Anyone know about mandrake? My > > > point is that some dists are already dealing with python2. > > > > Hi Tom, > > I use Linux-Mandrake 8.0 now, and python2 is installed by default for a > > development workstation installation. I asked Mandrakesoft to also > > install the tkinter package (which was not installed by default in > > release candidate 1), and it appeared in LM 8.0 final, so if you like to > > use make xconfig with CML2, you can. > > Could you please send this to linux-kernel as well? :) At Tom's request, posting to lkml. Steven - 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: [kbuild-devel] Re: CML2 design philosophy heads-up
On Monday 21 May 2001 10:01, Tom Rini wrote: On Mon, May 21, 2001 at 09:58:04AM -0600, Steven Cole wrote: On Monday 21 May 2001 09:36, Tom Rini wrote: Which brings up another point, RedHat (7.1?) and Debian/woody both have the option of having python2 around. Anyone know about mandrake? My point is that some dists are already dealing with python2. Hi Tom, I use Linux-Mandrake 8.0 now, and python2 is installed by default for a development workstation installation. I asked Mandrakesoft to also install the tkinter package (which was not installed by default in release candidate 1), and it appeared in LM 8.0 final, so if you like to use make xconfig with CML2, you can. Could you please send this to linux-kernel as well? :) At Tom's request, posting to lkml. Steven - 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: [kbuild-devel] Re: CML2 design philosophy heads-up
On Friday 18 May 2001 09:19, Jes Sorensen wrote: > Replacing the code does not require changing the style of the config > files. Thats a major problem with CML2, you introduce a new 'let me do > everything for you' tool that relies on a programming language that is > not being shipped by any major vendor nor does it look like they are > planning to do it anytime soon. And even if they start doing so, this Actually, Linux-Mandrake 8.0 ships with Python 2.0, but your next point is a very good one: > is a totally unreasonable requirement, you *must* to make it possible > to compile kernels on older distributions without requiring people to > update half of their system. On some architectures, the majority of > the users are still on glibc 2.0 and other old versions of > tools. Telling them to install an updated gcc for kernel compilation > is a necessary evil, which can easily be done without disturbing the > rest of the system. Updating the system's python installation is not a > reasonable request. Nobody disagrees that the Makefiles needs a > redesign, however that doesn't mean everything else has to be > redisigned in a totally incompatible manner. I didn't have trouble installing python 2.0 before LM 8.0 did that for me, but I was probably just lucky. I've seen some reports by other people who did have difficulty upgrading python. If the python installation difficulties are a real obstacle, perhaps that is what needs to be fixed. Steven - 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: [kbuild-devel] Re: CML2 design philosophy heads-up
On Friday 18 May 2001 09:19, Jes Sorensen wrote: Replacing the code does not require changing the style of the config files. Thats a major problem with CML2, you introduce a new 'let me do everything for you' tool that relies on a programming language that is not being shipped by any major vendor nor does it look like they are planning to do it anytime soon. And even if they start doing so, this Actually, Linux-Mandrake 8.0 ships with Python 2.0, but your next point is a very good one: is a totally unreasonable requirement, you *must* to make it possible to compile kernels on older distributions without requiring people to update half of their system. On some architectures, the majority of the users are still on glibc 2.0 and other old versions of tools. Telling them to install an updated gcc for kernel compilation is a necessary evil, which can easily be done without disturbing the rest of the system. Updating the system's python installation is not a reasonable request. Nobody disagrees that the Makefiles needs a redesign, however that doesn't mean everything else has to be redisigned in a totally incompatible manner. I didn't have trouble installing python 2.0 before LM 8.0 did that for me, but I was probably just lucky. I've seen some reports by other people who did have difficulty upgrading python. If the python installation difficulties are a real obstacle, perhaps that is what needs to be fixed. Steven - 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.4-ac4 build error with CONFIG_USB=y
With CONFIG_USB=y, I got the following error building 2.4.4-ac4: drivers/usb/usbdrv.o: In function `uhci_alloc_td': drivers/usb/usbdrv.o(.text+0x57b7): undefined reference to `pci_pool_alloc' drivers/usb/usbdrv.o: In function `uhci_free_td': drivers/usb/usbdrv.o(.text+0x5a41): undefined reference to `pci_pool_free' drivers/usb/usbdrv.o: In function `uhci_alloc_qh': drivers/usb/usbdrv.o(.text+0x5a67): undefined reference to `pci_pool_alloc' drivers/usb/usbdrv.o: In function `uhci_free_qh': drivers/usb/usbdrv.o(.text+0x5ad1): undefined reference to `pci_pool_free' drivers/usb/usbdrv.o: In function `alloc_uhci': drivers/usb/usbdrv.o(.text+0x88c7): undefined reference to `pci_pool_create' drivers/usb/usbdrv.o(.text+0x88f6): undefined reference to `pci_pool_create' drivers/usb/usbdrv.o(.text+0x8c22): undefined reference to `pci_pool_destroy' drivers/usb/usbdrv.o(.text+0x8c2c): undefined reference to `pci_pool_destroy' drivers/usb/usbdrv.o: In function `release_uhci': drivers/usb/usbdrv.o(.text+0x8ce6): undefined reference to `pci_pool_destroy' drivers/usb/usbdrv.o(.text+0x8cfb): undefined reference to `pci_pool_destroy' make: *** [vmlinux] Error 1 Undefining CONFIG_USB gave me a clean build. Steven - 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.4-ac4 build error with CONFIG_USB=y
With CONFIG_USB=y, I got the following error building 2.4.4-ac4: drivers/usb/usbdrv.o: In function `uhci_alloc_td': drivers/usb/usbdrv.o(.text+0x57b7): undefined reference to `pci_pool_alloc' drivers/usb/usbdrv.o: In function `uhci_free_td': drivers/usb/usbdrv.o(.text+0x5a41): undefined reference to `pci_pool_free' drivers/usb/usbdrv.o: In function `uhci_alloc_qh': drivers/usb/usbdrv.o(.text+0x5a67): undefined reference to `pci_pool_alloc' drivers/usb/usbdrv.o: In function `uhci_free_qh': drivers/usb/usbdrv.o(.text+0x5ad1): undefined reference to `pci_pool_free' drivers/usb/usbdrv.o: In function `alloc_uhci': drivers/usb/usbdrv.o(.text+0x88c7): undefined reference to `pci_pool_create' drivers/usb/usbdrv.o(.text+0x88f6): undefined reference to `pci_pool_create' drivers/usb/usbdrv.o(.text+0x8c22): undefined reference to `pci_pool_destroy' drivers/usb/usbdrv.o(.text+0x8c2c): undefined reference to `pci_pool_destroy' drivers/usb/usbdrv.o: In function `release_uhci': drivers/usb/usbdrv.o(.text+0x8ce6): undefined reference to `pci_pool_destroy' drivers/usb/usbdrv.o(.text+0x8cfb): undefined reference to `pci_pool_destroy' make: *** [vmlinux] Error 1 Undefining CONFIG_USB gave me a clean build. Steven - 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.3-ac11 request for help texts for recenty introduced config options
As of kernel 2.4.3-ac11, there are 464 config options which have no help text in Configure.help. Here is the list of these items which have been introduced after 2.4.3-ac1. Each group is incremental, versus 2.4.3-ac[n-1]. If you see one of your options here, please consider generating a patch for Configure.help, or send me the information and I'll do the rest. A status of "acknowledged" means that the item is being worked on by the person named or their designate. Thank you to the maintainers who have responded. Thanks in advance, Steven 2.4.3-ac11 none 2.4.3-ac10 CONFIG_E1355_FB_BASE CONFIG_E1355_REG_BASE CONFIG_ETRAX_CSP0_LEDS CONFIG_ETRAX_DEBUG_PORT0 CONFIG_ETRAX_DEBUG_PORT1 CONFIG_ETRAX_DEBUG_PORT2 CONFIG_ETRAX_DEBUG_PORT3 CONFIG_ETRAX_DEBUG_PORT_NULL CONFIG_ETRAX_I2C_EEPROM_16KB CONFIG_ETRAX_I2C_EEPROM_2KB CONFIG_ETRAX_I2C_EEPROM_8KB CONFIG_ETRAX_IDE_CSP0_8_RESET CONFIG_ETRAX_LED10Y CONFIG_ETRAX_LED11Y CONFIG_ETRAX_LED12R CONFIG_ETRAX_LED4G CONFIG_ETRAX_LED4R CONFIG_ETRAX_LED5G CONFIG_ETRAX_LED5R CONFIG_ETRAX_LED6G CONFIG_ETRAX_LED6R CONFIG_ETRAX_LED7G CONFIG_ETRAX_LED7R CONFIG_ETRAX_LED8Y CONFIG_ETRAX_LED9Y CONFIG_ETRAX_PARALLEL_PORT0 CONFIG_ETRAX_PARALLEL_PORT1 CONFIG_ETRAX_PARPORT CONFIG_ETRAX_RESCUE_SER0 CONFIG_ETRAX_RESCUE_SER1 CONFIG_ETRAX_RESCUE_SER2 CONFIG_ETRAX_RESCUE_SER3 CONFIG_ETRAX_RS485_ON_PA_BIT CONFIG_ETRAX_SDRAM CONFIG_FB_DC CONFIG_FB_E1355 2.4.3-ac9 none 2.4.3-ac8 none 2.4.3-ac7 CONFIG_BBC_I2C 2.4.3-ac6 CONFIG_AIC7XXX_BUILD_FIRMWARE 2.4.3-ac5 CONFIG_IA64_EFIVARS acknowledgedMatt Domsch CONFIG_ITANIUM CONFIG_MCKINLEY CONFIG_MCKINLEY_A0_SPECIFIC CONFIG_MCKINLEY_ASTEP_SPECIFIC 2.4.3-ac4 CONFIG_ARCH_CLPS711X CONFIG_ARCH_P720T CONFIG_ARM_THUMB CONFIG_CPU_ARM1020 CONFIG_CPU_ARM610 acknowledgedRussell King CONFIG_CPU_ARM710 acknowledgedRussell King CONFIG_CPU_ARM720T acknowledgedRussell King CONFIG_CPU_ARM920T acknowledgedRussell King CONFIG_CPU_SA110acknowledgedRussell King CONFIG_DASD_DIAG CONFIG_DEBUG_CLPS711X_UART2 CONFIG_DEBUGSYM CONFIG_GCOV CONFIG_GPROF CONFIG_HOSTFS CONFIG_NET_UM_ETH CONFIG_NET_UMN CONFIG_SA1100_PANGOLIN CONFIG_SA1100_SHERMAN CONFIG_SSL 2.4.3-ac3 none 2.4.3-ac2 CONFIG_GEMINI - 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.3-ac11 request for help texts for recenty introduced config options
As of kernel 2.4.3-ac11, there are 464 config options which have no help text in Configure.help. Here is the list of these items which have been introduced after 2.4.3-ac1. Each group is incremental, versus 2.4.3-ac[n-1]. If you see one of your options here, please consider generating a patch for Configure.help, or send me the information and I'll do the rest. A status of "acknowledged" means that the item is being worked on by the person named or their designate. Thank you to the maintainers who have responded. Thanks in advance, Steven 2.4.3-ac11 none 2.4.3-ac10 CONFIG_E1355_FB_BASE CONFIG_E1355_REG_BASE CONFIG_ETRAX_CSP0_LEDS CONFIG_ETRAX_DEBUG_PORT0 CONFIG_ETRAX_DEBUG_PORT1 CONFIG_ETRAX_DEBUG_PORT2 CONFIG_ETRAX_DEBUG_PORT3 CONFIG_ETRAX_DEBUG_PORT_NULL CONFIG_ETRAX_I2C_EEPROM_16KB CONFIG_ETRAX_I2C_EEPROM_2KB CONFIG_ETRAX_I2C_EEPROM_8KB CONFIG_ETRAX_IDE_CSP0_8_RESET CONFIG_ETRAX_LED10Y CONFIG_ETRAX_LED11Y CONFIG_ETRAX_LED12R CONFIG_ETRAX_LED4G CONFIG_ETRAX_LED4R CONFIG_ETRAX_LED5G CONFIG_ETRAX_LED5R CONFIG_ETRAX_LED6G CONFIG_ETRAX_LED6R CONFIG_ETRAX_LED7G CONFIG_ETRAX_LED7R CONFIG_ETRAX_LED8Y CONFIG_ETRAX_LED9Y CONFIG_ETRAX_PARALLEL_PORT0 CONFIG_ETRAX_PARALLEL_PORT1 CONFIG_ETRAX_PARPORT CONFIG_ETRAX_RESCUE_SER0 CONFIG_ETRAX_RESCUE_SER1 CONFIG_ETRAX_RESCUE_SER2 CONFIG_ETRAX_RESCUE_SER3 CONFIG_ETRAX_RS485_ON_PA_BIT CONFIG_ETRAX_SDRAM CONFIG_FB_DC CONFIG_FB_E1355 2.4.3-ac9 none 2.4.3-ac8 none 2.4.3-ac7 CONFIG_BBC_I2C 2.4.3-ac6 CONFIG_AIC7XXX_BUILD_FIRMWARE 2.4.3-ac5 CONFIG_IA64_EFIVARS acknowledgedMatt Domsch CONFIG_ITANIUM CONFIG_MCKINLEY CONFIG_MCKINLEY_A0_SPECIFIC CONFIG_MCKINLEY_ASTEP_SPECIFIC 2.4.3-ac4 CONFIG_ARCH_CLPS711X CONFIG_ARCH_P720T CONFIG_ARM_THUMB CONFIG_CPU_ARM1020 CONFIG_CPU_ARM610 acknowledgedRussell King CONFIG_CPU_ARM710 acknowledgedRussell King CONFIG_CPU_ARM720T acknowledgedRussell King CONFIG_CPU_ARM920T acknowledgedRussell King CONFIG_CPU_SA110acknowledgedRussell King CONFIG_DASD_DIAG CONFIG_DEBUG_CLPS711X_UART2 CONFIG_DEBUGSYM CONFIG_GCOV CONFIG_GPROF CONFIG_HOSTFS CONFIG_NET_UM_ETH CONFIG_NET_UMN CONFIG_SA1100_PANGOLIN CONFIG_SA1100_SHERMAN CONFIG_SSL 2.4.3-ac3 none 2.4.3-ac2 CONFIG_GEMINI - 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: Configure.help maintainer change
Axel Boldt wrote: >Eric has worked on Configure.help for some time now and I haven't, >so he will take over official maintenance of that file. I've also been fixing up Configure.help for a while now, and helped Eric recently with his huge update patch for Configure.help. I'd like to be listed as a co-maintainer of Configure.help, along with ESR. Steven Here is an alternative patch, against 2.4.3-ac10: --- linux/MAINTAINERS.ac10 Thu Apr 19 21:54:37 2001 +++ linux/MAINTAINERS Thu Apr 19 22:00:06 2001 @@ -280,8 +280,10 @@ S: Maintained CONFIGURE.HELP -P: Axel Boldt -M: [EMAIL PROTECTED] +P: Eric S. Raymond +M: Eric S. Raymond <[EMAIL PROTECTED]> +P: Steven P. Cole +M: Steven P. Cole <[EMAIL PROTECTED]> S: Maintained COSA/SRP SYNC SERIAL DRIVER --- linux/Documentation/Configure.help.ac10 Thu Apr 19 22:01:20 2001 +++ linux/Documentation/Configure.help Thu Apr 19 22:02:58 2001 @@ -1,4 +1,5 @@ -# Maintained by Axel Boldt ([EMAIL PROTECTED]) +# Maintained by Eric S. Raymond <[EMAIL PROTECTED]> +# and by Steven P. Cole <[EMAIL PROTECTED]> # # This version of the Linux kernel configuration help texts # corresponds to the kernel versions 2.4.x. - 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: Configure.help maintainer change
Axel Boldt wrote: Eric has worked on Configure.help for some time now and I haven't, so he will take over official maintenance of that file. I've also been fixing up Configure.help for a while now, and helped Eric recently with his huge update patch for Configure.help. I'd like to be listed as a co-maintainer of Configure.help, along with ESR. Steven Here is an alternative patch, against 2.4.3-ac10: --- linux/MAINTAINERS.ac10 Thu Apr 19 21:54:37 2001 +++ linux/MAINTAINERS Thu Apr 19 22:00:06 2001 @@ -280,8 +280,10 @@ S: Maintained CONFIGURE.HELP -P: Axel Boldt -M: [EMAIL PROTECTED] +P: Eric S. Raymond +M: Eric S. Raymond [EMAIL PROTECTED] +P: Steven P. Cole +M: Steven P. Cole [EMAIL PROTECTED] S: Maintained COSA/SRP SYNC SERIAL DRIVER --- linux/Documentation/Configure.help.ac10 Thu Apr 19 22:01:20 2001 +++ linux/Documentation/Configure.help Thu Apr 19 22:02:58 2001 @@ -1,4 +1,5 @@ -# Maintained by Axel Boldt ([EMAIL PROTECTED]) +# Maintained by Eric S. Raymond [EMAIL PROTECTED] +# and by Steven P. Cole [EMAIL PROTECTED] # # This version of the Linux kernel configuration help texts # corresponds to the kernel versions 2.4.x. - 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.3-ac8 build error with CONFIG_DEBUG_KERNEL not set
I got the following with CONFIG_DEBUG_KERNEL not set: kernel/kernel.o(__ksymtab+0xc80): undefined reference to `handle_sysrq' kernel/kernel.o(__ksymtab+0xc88): undefined reference to `__handle_sysrq_nolock' kernel/kernel.o(__ksymtab+0xc90): undefined reference to `__sysrq_lock_table' kernel/kernel.o(__ksymtab+0xc98): undefined reference to `__sysrq_unlock_table' kernel/kernel.o(__ksymtab+0xca0): undefined reference to `__sysrq_get_key_op' kernel/kernel.o(__ksymtab+0xca8): undefined reference to `__sysrq_put_key_op' make: *** [vmlinux] Error 1 However, with CONFIG_DEBUG_KERNEL and CONFIG_MAGIC_SYSRQ set to y, I got a clean build. Steven - 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: [kbuild-devel] CML2 1.1.4 is available
On Tuesday 17 April 2001 12:13, Eric S. Raymond wrote: > The latest version is always available at http://www.tuxedo.org/~esr/cml2/ > > Release 1.1.4: Tue Apr 17 14:02:17 EDT 2001 > * Tom Rini's patches for the ARM port tree. > * Correct handling of booleans when trits are disabled. > * `nohelp' tie symbol introduced. > * Code audited with PyChecker. > > The fact that most of the arguments about recent releases have to do with > color selection in the UI tells me that the UI is just about good enough. > The sluggishness complaints seem to have subsided as well. > > So let's try to shift our attention to auditing and fixing the rules files, > shall we? Using CML2 1.1.4 to make xconfig for 2.4.4-pre3: I hope this falls into one of the above categories, but now with CONFIG_MODULES set to y, I don't see any of the y m n choices colored in with the usual magenta. This is true on all menus. The label text is green for those set to y, but this hasn't been 100% reliable in the past. On the other hand, with CONFIG_MODULES set to n, your fix seems to have worked. So, one step forward, one step back. Steven - 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.3-ac8 build error with CONFIG_DEBUG_KERNEL not set
I got the following with CONFIG_DEBUG_KERNEL not set: kernel/kernel.o(__ksymtab+0xc80): undefined reference to `handle_sysrq' kernel/kernel.o(__ksymtab+0xc88): undefined reference to `__handle_sysrq_nolock' kernel/kernel.o(__ksymtab+0xc90): undefined reference to `__sysrq_lock_table' kernel/kernel.o(__ksymtab+0xc98): undefined reference to `__sysrq_unlock_table' kernel/kernel.o(__ksymtab+0xca0): undefined reference to `__sysrq_get_key_op' kernel/kernel.o(__ksymtab+0xca8): undefined reference to `__sysrq_put_key_op' make: *** [vmlinux] Error 1 However, with CONFIG_DEBUG_KERNEL and CONFIG_MAGIC_SYSRQ set to y, I got a clean build. Steven - 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: [kbuild-devel] CML2 1.1.4 is available
On Tuesday 17 April 2001 12:13, Eric S. Raymond wrote: The latest version is always available at http://www.tuxedo.org/~esr/cml2/ Release 1.1.4: Tue Apr 17 14:02:17 EDT 2001 * Tom Rini's patches for the ARM port tree. * Correct handling of booleans when trits are disabled. * `nohelp' tie symbol introduced. * Code audited with PyChecker. The fact that most of the arguments about recent releases have to do with color selection in the UI tells me that the UI is just about good enough. The sluggishness complaints seem to have subsided as well. So let's try to shift our attention to auditing and fixing the rules files, shall we? Using CML2 1.1.4 to make xconfig for 2.4.4-pre3: I hope this falls into one of the above categories, but now with CONFIG_MODULES set to y, I don't see any of the y m n choices colored in with the usual magenta. This is true on all menus. The label text is green for those set to y, but this hasn't been 100% reliable in the past. On the other hand, with CONFIG_MODULES set to n, your fix seems to have worked. So, one step forward, one step back. Steven - 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: [kbuild-devel] CML2 1.1.3 is available
On Monday 16 April 2001 16:06, Eric S. Raymond wrote: > Steven Cole <[EMAIL PROTECTED]>: > > Whoops, I just tried out 1.1.3 using make xconfig, and now all the > > option labels are dark green, not just the ones set to y. > > That's because they're set in your .config, dude! Well, lets look at a snippet of the .config: # CONFIG_BINFMT_SOM is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_SMP is not set I just re-installed CML2 1.1.2, and it shows those options as you would expect, that is the ones set to y are green, and the "not set" ones are black. Well, except CONFIG_BINFMT_ELF which is black. Toggling it to n and then to y makes it green. Re-installing CML2 1.1.3, I see all those options as green. I can send you my whole .config if that would be useful. Steven - 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: [kbuild-devel] CML2 1.1.3 is available
On Monday 16 April 2001 15:42, Eric S. Raymond wrote: > CML2 NEWS > > The latest version is always available at http://www.tuxedo.org/~esr/cml2/ > > Release 1.1.3: > * Freeze color changed from cyan to blue. > * Tom Rini's network-configuration patches. > * Better detection of set variables to be colored green. > * Minor resize and scrolling fixes in menuconfig. > * Fixed a rather nasty bug involving side-effect computation > that showed up if you set, unset, and reset a symbol in a > choices menu. > * In non-choice menus, select bar is now advanced after [ymn]. > > Point release -- bug fixes and UI cleanups. Whoops, I just tried out 1.1.3 using make xconfig, and now all the option labels are dark green, not just the ones set to y. Thanks for changing the freeze color to blue. That is much more readable against the silver background for make xconfig. Steven - 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: [kbuild-devel] CML2 1.1.3 is available
On Monday 16 April 2001 15:42, Eric S. Raymond wrote: CML2 NEWS The latest version is always available at http://www.tuxedo.org/~esr/cml2/ Release 1.1.3: * Freeze color changed from cyan to blue. * Tom Rini's network-configuration patches. * Better detection of set variables to be colored green. * Minor resize and scrolling fixes in menuconfig. * Fixed a rather nasty bug involving side-effect computation that showed up if you set, unset, and reset a symbol in a choices menu. * In non-choice menus, select bar is now advanced after [ymn]. Point release -- bug fixes and UI cleanups. Whoops, I just tried out 1.1.3 using make xconfig, and now all the option labels are dark green, not just the ones set to y. Thanks for changing the freeze color to blue. That is much more readable against the silver background for make xconfig. Steven - 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: [kbuild-devel] CML2 1.1.3 is available
On Monday 16 April 2001 16:06, Eric S. Raymond wrote: Steven Cole [EMAIL PROTECTED]: Whoops, I just tried out 1.1.3 using make xconfig, and now all the option labels are dark green, not just the ones set to y. That's because they're set in your .config, dude! Well, lets look at a snippet of the .config: # CONFIG_BINFMT_SOM is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_SMP is not set I just re-installed CML2 1.1.2, and it shows those options as you would expect, that is the ones set to y are green, and the "not set" ones are black. Well, except CONFIG_BINFMT_ELF which is black. Toggling it to n and then to y makes it green. Re-installing CML2 1.1.3, I see all those options as green. I can send you my whole .config if that would be useful. Steven - 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: [kbuild-devel] CML2 1.1.2 is available
On Sunday 15 April 2001 12:33, Eric S. Raymond wrote: > The latest version is always available at http://www.tuxedo.org/~esr/cml2/ > > Release 1.1.2: Sun Apr 15 14:26:07 EDT 2001 > * Synchronized with 2.4.4-pre3. > * Screen flicker in menuconfig is gone. > * KEY_HOME and KEY_END now go to top or bottom of menu. > * Zack Weinberg's patch reorganizing the block devices menus. > > The screen flicker fix should also speed up general responsiveness. Good, and many thanks for changing bright green to dark green for make xconfig. That's much better! However, the label "Processor type (X86)" is still in cyan, and makes my poor old tired eyes even more tired. A nice dark blue would be much appreciated. Steven - 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/
