Re: removing /etc/hotplug.d/ support
Horms writes... > There are some architectures where 2.4 has been abandonded uptream, > and these are being removed from the arcive > powerpc (ok, thats one, not some) hppa is as well. It is still useful to have the 2.4 kernel-images in the archive since they are still more stable on some machines. Maybe willy/kyle/thibault can comment more. -- Matt Taggart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
On Thu, 2005-08-25 at 06:25 +0200, Martin Schulze wrote:
> dann frazier wrote:
> > On Wed, 2005-08-24 at 20:30 +0200, Martin Schulze wrote:
> > > dann frazier wrote:
> > > > On Tue, 2005-08-23 at 15:22 -0600, dann frazier wrote:
> > > > > We're getting closer. Please check this for accuracy:
> > > > > http://wiki.debian.net/?DebianKernelSargeUpdateStatus
> > > > >
> > > > > I can try to do hppa this afternoon; any word on m68k, mips & s390?
> > > >
> > > > Security Team,
> > > > Is there a way we can take advantage of your autobuilder setup for
> > > > lagging archs?
> > >
> > > Only when the source package is in the security queue accompanied
> > > with a binary package the buildds for missing architectures should
> > > try it on their respective architectures.
> >
> > Joey,
> > Can we go ahead and start uploading packages for the archs we've
> > completed?
>
> Could you send me a {list,set} of patches and descriptions that were
> fixed by these kernels?
Sure.
svn cat
svn://svn.debian.org/svn/kernel/tags/kernel-2.4/source/kernel-source-2.4.27-2.4.27/2.4.27-10sarge1/debian/patches/series/2.4.27-10sarge1
svn cat
svn://svn.debian.org/svn/kernel/tags/kernel/source/kernel-source-2.6.8-2.6.8/2.6.8-16sarge1/debian/patches/series/2.6.8-16sarge1
You svn co those tags to fetch the patches. Both the changelog and the
patche files themselves contain descriptions/CAN IDs.
--
dann frazier <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: compiling 2.6.12 with the debian patch
Processing commands for [EMAIL PROTECTED]: > tag 324583 +pending Bug#324583: linux-patch-debian-2.6.12: missing default version numbers in unpatch/apply script break make-kpkg There were no tags set. Tags added: pending > tag 324583 +patch Bug#324583: linux-patch-debian-2.6.12: missing default version numbers in unpatch/apply script break make-kpkg Tags were: pending Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324583: compiling 2.6.12 with the debian patch
tag 324583 +pending tag 324583 +patch thanks Hi, I have put the attched patch into SVN which should resolve this problem. It should appear in the next relase, likely 2.6.12-6 Thanks Index: debian/rules.real === --- debian/rules.real (revision 4051) +++ debian/rules.real (working copy) @@ -262,8 +262,8 @@ dh_installdirs $(DH_OPTIONS) $(pbase)/apply $(pbase)/debian $(pbase)/unpatch dh_install $(DH_OPTIONS) debian/patches-debian/* $(pbase)/debian # Install the debian patches - sed 's/@version@/$(release)/g' debian/bin/apply > $(pfull)/apply/debian - sed 's/@upstream@/$(version)/g' debian/bin/unpatch > $(pfull)/unpatch/debian + sed 's/@version@/$(SOURCE_VERSION)/g' debian/bin/apply > $(pfull)/apply/debian + sed 's/@upstream@/$(VERSION)/g' debian/bin/unpatch > $(pfull)/unpatch/debian chmod 755 $(pfull)/apply/debian $(pfull)/unpatch/debian chmod 644 $(pfull)/debian/*.patch bzip2 -9 $(pfull)/debian/*.patch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
dann frazier wrote:
> On Wed, 2005-08-24 at 20:30 +0200, Martin Schulze wrote:
> > dann frazier wrote:
> > > On Tue, 2005-08-23 at 15:22 -0600, dann frazier wrote:
> > > > We're getting closer. Please check this for accuracy:
> > > > http://wiki.debian.net/?DebianKernelSargeUpdateStatus
> > > >
> > > > I can try to do hppa this afternoon; any word on m68k, mips & s390?
> > >
> > > Security Team,
> > > Is there a way we can take advantage of your autobuilder setup for
> > > lagging archs?
> >
> > Only when the source package is in the security queue accompanied
> > with a binary package the buildds for missing architectures should
> > try it on their respective architectures.
>
> Joey,
> Can we go ahead and start uploading packages for the archs we've
> completed?
Could you send me a {list,set} of patches and descriptions that were
fixed by these kernels?
>
> And, if we can't find folks to build on these other archs, can we
> release a first pass advisory to get the completed ones out to users and
> followup later? ISTR this happening for woody.
For woody, I have a whole bunch of updates. I've tested them on the
2.4.18 kernel, so they can be ported to 2.4.16, .17 and .19, but that's
like 30 patches unfortunately. A volunteer for this would be welcome.
Regards,
Joey
--
The MS-DOS filesystem is nice for removable media. -- H. Peter Anvin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: removing /etc/hotplug.d/ support
On Wed, Aug 24, 2005 at 04:59:01PM -0700, Steve Langasek wrote: > On Thu, Aug 25, 2005 at 01:01:10AM +0200, Marco d'Itri wrote: > > On Aug 24, martin f krafft <[EMAIL PROTECTED]> wrote: > > > > > udev has also been the hotplug multiplexer for some time now. > > > Yeah. Horrible. Will udev become an editor and MTA too, maybe after > > > etch? > > No. But since it had to deal with most events, applying the same process > > to the others was a natural extension of its design. > > > > > 2.4 kernels will not be supported in etch, > > > I don't think this is an authoritative statement. At the moment, > > > some architectures do not work with 2.6. > > It's an educated guess. I consulted some of the interested maintainers > > and followed the debian-kernel list, and so far there is no sign that > > 2.4 will be supported (and if 2.6 will not be fixed on architectures > > like sparc32, too bad for them). > > Although being able to ship just one kernel for all our ports in etch is > everyone's first choice, the release team has not made any decision yet to > exclude 2.4 kernels from etch if they're needed for a particular arch or > subarch. Given that the kernel team is still rolling new 2.4 updates in > unstable, and d-i still defaults to 2.4 on a majority of archs, I think it > is premature to drop hotplug support for 2.4 at this point. > > It would certainly be a big help to the release team in making this decision > if the kernel team would begin to drop 2.4 kernels as early as possible in > the release cycle for those architectures where they believe they are no > longer needed. Together with working out which ports are actually viable > for etch under the new requirements (which of course first requires fully > specifying those requirements), we should be able to get a clear picture in > a couple of months of just what the kernel requirements are for etch. There are some architectures where 2.4 is required, its because of these that it seems that we are stuck with 2.4 for Etch. alpha (installer), m68k (2.6 only works on amiga), s390 (installer), mips, mipsel There are some architectures where 2.4 has been abandonded uptream, and these are being removed from the arcive powerpc (ok, thats one, not some) There are some architectures, like i386, which are pretty well maintained upstream for 2.4, so it seems reasonable to keep them, as we need 2.4 because of the first group, and its not a whole lot of extra effort - if it is lets get rid of them. I'm aware of the udev issue, I'm happy for that to be a catalyst for canning 2.4 where possible. But what about the arches that need 2.4. Does that mean we have to backport udev anyway? I might add, that right now I'm doing the bulk of 2.4 maintenance, and my current plan is to just keep patching 2.4.27, the sarge kernel, and eventually, once all the current teething problems are ironed out with the single-source 2.6 package, use that framework to produce a new 2.4.X, probably .35 or so by then. Also, I only have powerpc (not supported by 2.4) and i386 hardware at my disposal, so it would be very convenient for me to keep 2.4.27 around for i386. Though I'm not really concerend about being able to install 2.4.27, just have something to test, so I guess that doesn't have to be a package that appears in Debian. But if I'm building the things, it seems like it might as well. Finally, the lists above are probably incomplete, please jump in with additional information if you have it. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Ubuntu reboot: kernel panic-: VFS: unable to mount root fs on unknown block(0,0)
On Thu, 2005-08-25 at 07:42 +0800, weiyun lv wrote: > Ubuntu reboot: kernel panic-not syncing: VFS: unable to mount root fs on > unknown block(0,0) hey weiyun, This list is a Debian list. Though related to Debian[1], the Ubuntu distribution has a number of differences. I suggest asking your question in an Ubuntu forum, such as one of the mailing lists here: http://www.ubuntulinux.org/community/lists [1] http://www.ubuntulinux.org/ubuntu/relationship/document_view -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#324550: Needs dependency fix [linux-image-2.6.12-1-686: install fails with "cannot stat `(0xffffe000)': No such file or directory"]
At Wed, 24 Aug 2005 11:30:30 -0400, Theodore Ts'o wrote: > Actually, to be completely correct, the right value should be > "Conflicts: e2fsprogs (< 1.35-7)", as linux-gate.so started being > filtered in e2fsprogs 1.35-7. OK, I changed from (<= 1.37-2sarge1) to (<< 1.35-7). Thanks! Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: removing /etc/hotplug.d/ support
On Thu, Aug 25, 2005 at 01:01:10AM +0200, Marco d'Itri wrote: > On Aug 24, martin f krafft <[EMAIL PROTECTED]> wrote: > > > udev has also been the hotplug multiplexer for some time now. > > Yeah. Horrible. Will udev become an editor and MTA too, maybe after > > etch? > No. But since it had to deal with most events, applying the same process > to the others was a natural extension of its design. > > > 2.4 kernels will not be supported in etch, > > I don't think this is an authoritative statement. At the moment, > > some architectures do not work with 2.6. > It's an educated guess. I consulted some of the interested maintainers > and followed the debian-kernel list, and so far there is no sign that > 2.4 will be supported (and if 2.6 will not be fixed on architectures > like sparc32, too bad for them). Although being able to ship just one kernel for all our ports in etch is everyone's first choice, the release team has not made any decision yet to exclude 2.4 kernels from etch if they're needed for a particular arch or subarch. Given that the kernel team is still rolling new 2.4 updates in unstable, and d-i still defaults to 2.4 on a majority of archs, I think it is premature to drop hotplug support for 2.4 at this point. It would certainly be a big help to the release team in making this decision if the kernel team would begin to drop 2.4 kernels as early as possible in the release cycle for those architectures where they believe they are no longer needed. Together with working out which ports are actually viable for etch under the new requirements (which of course first requires fully specifying those requirements), we should be able to get a clear picture in a couple of months of just what the kernel requirements are for etch. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Ubuntu reboot: kernel panic-: VFS: unable to mount root fs on unknown block(0,0)
Ubuntu reboot: kernel panic-not syncing: VFS: unable to mount root fs on unknown block(0,0) hello, I am a newbie and I met some problem which has puzzled me for a whole week: 1. install Ubuntu 5.04(I use ext2, for the second time ext3 as the file system), and gcc etc. no problem here. 2. download kernel source 2.6.10 from kernel.org 3. reconfig the kernel, only enable kernel-hacking options. (for the second time also ext3 file system) 4. make bzImage; make modules; make modules_install; make install. no error message given. 5. updata menu.lst and reboot. *> it gives above error message. 5-1. I tried to use mkinitrd and added to the menu.lst too, but it doesn't work. And here I feel quiet unclear, some people say you need it, some say you don't need it and you should even delete it in menu.lst. So, what can I do now, and the kernel-compiling is somewhat time-consuming. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
On Wed, Aug 24, 2005 at 04:50:35PM -0600, dann frazier wrote: > > This is a stable-security update. Horms has also created packages for > an unstable update of 2.4.27, but that's a separate topic. > Unfortunately it sounds like we cannot upload a source package and have > the autobuilders do it - would you be able to do an m68k in a pristine > sarge environment? Yes, I could, but it would take a lot longer than cross-compiling plus I'll be travelling for a few days, among other things I'll be trying to get two faster m68k machines running for debian. But even if I could get the cross-compiling 2.4.27 working again I could not upload much before next tuesday. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
On Thu, 2005-08-25 at 00:36 +0200, Christian T. Steigies wrote: > On Tue, Aug 23, 2005 at 03:22:02PM -0600, dann frazier wrote: > > We're getting closer. Please check this for accuracy: > > http://wiki.debian.net/?DebianKernelSargeUpdateStatus > > > > I can try to do hppa this afternoon; any word on m68k, mips & s390? > > I am having problems getting a cross-compiler for gcc-2.95 working for m68k, > gcc-3.3 can not compile 2.4.27 for m68k. I can upload a new patch package > (needed only for a patch to pick gcc-2.95 as default compiler instead of now > gcc-3.3), but for the images I can only provide a source package right now, > which would have to be built by the autobuilders. This would be all for > unstable? I haven't seen any mention of stable/sarge in the 2.4.27 packages. > > A sarge update would not need a new kernel-patch-m68k package, just a > rebuild of the kernel-image-m68k package using the new kernel-source. This is a stable-security update. Horms has also created packages for an unstable update of 2.4.27, but that's a separate topic. Unfortunately it sounds like we cannot upload a source package and have the autobuilders do it - would you be able to do an m68k in a pristine sarge environment? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
On Tue, Aug 23, 2005 at 03:22:02PM -0600, dann frazier wrote: > We're getting closer. Please check this for accuracy: > http://wiki.debian.net/?DebianKernelSargeUpdateStatus > > I can try to do hppa this afternoon; any word on m68k, mips & s390? I am having problems getting a cross-compiler for gcc-2.95 working for m68k, gcc-3.3 can not compile 2.4.27 for m68k. I can upload a new patch package (needed only for a patch to pick gcc-2.95 as default compiler instead of now gcc-3.3), but for the images I can only provide a source package right now, which would have to be built by the autobuilders. This would be all for unstable? I haven't seen any mention of stable/sarge in the 2.4.27 packages. A sarge update would not need a new kernel-patch-m68k package, just a rebuild of the kernel-image-m68k package using the new kernel-source. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
On Wed, 2005-08-24 at 20:30 +0200, Martin Schulze wrote: > dann frazier wrote: > > On Tue, 2005-08-23 at 15:22 -0600, dann frazier wrote: > > > We're getting closer. Please check this for accuracy: > > > http://wiki.debian.net/?DebianKernelSargeUpdateStatus > > > > > > I can try to do hppa this afternoon; any word on m68k, mips & s390? > > > > Security Team, > > Is there a way we can take advantage of your autobuilder setup for > > lagging archs? > > Only when the source package is in the security queue accompanied > with a binary package the buildds for missing architectures should > try it on their respective architectures. Joey, Can we go ahead and start uploading packages for the archs we've completed? And, if we can't find folks to build on these other archs, can we release a first pass advisory to get the completed ones out to users and followup later? ISTR this happening for woody. Sorry for asking so many questions - hopefully we'll all know exactly what to do for the next time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323724: Dual G5 turns off after a while
On Wed, Aug 24, 2005 at 12:37:09PM -0700, Shyamal Prasad wrote: > "Sven" == Sven Luther <[EMAIL PROTECTED]> writes: > > Sven> On Tue, Aug 23, 2005 at 07:02:15PM -0700, Shyamal Prasad > > >> and, yes, I'm booting via with yaboot. I'm really stumped on > >> why this kernel is not booting my machine when it works for > >> Daniel (who also has a PowerMac7,3). Am I missing something > >> obvious? > > Sven> So, what are you really booting ? > > Hi Sven, > > I am booting vmlinux-2.12-1-powerpc64 (installed from the sid deb file > with its initrd). > > Sven> Did you run ybin and such, > > Actually I do not usually because I should not need to (I have the > symbolic links set up so I can simply move them to point at the right > images). But, just to be sure, I just tried it again and it changes > nothing. > > Sven> did you try the stuff Benjamin Herrenschmidt suggested to > Sven> Paul's bug report (#323724) ? > Sven> Have a look at : > Sven> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323724 > > Actually I'm having the same problem that Paul reported, except on a > PowerMac 7,3 (970FX). The boot fails at the exact same point. I can > try benh's suggestion but it will take some time (need to install the > biarch toolchain and recompile kernel), and it was more about > isolating the place where the fault happens, right? Yes, please do, the biarch toolchain is in sid, so you just have to install those, and you probably want to do this anyway. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
On Wed, 2005-08-24 at 20:30 +0200, Martin Schulze wrote: > dann frazier wrote: > > On Tue, 2005-08-23 at 15:22 -0600, dann frazier wrote: > > > We're getting closer. Please check this for accuracy: > > > http://wiki.debian.net/?DebianKernelSargeUpdateStatus > > > > > > I can try to do hppa this afternoon; any word on m68k, mips & s390? > > > > Security Team, > > Is there a way we can take advantage of your autobuilder setup for > > lagging archs? > > Only when the source package is in the security queue accompanied > with a binary package the buildds for missing architectures should > try it on their respective architectures. Bummer. Obviously that doesn't help since these packages only build on one arch. Oh well; at least this should work in etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#285017: marked as done (kernel-image-2.4.27-1-686: upgrading from v2 to v6 slows down my modem)
[ please do _not_ drop peoples of the cc list. i agree [EMAIL PROTECTED] was mistakenly on that list. ] On Wed, Aug 24, 2005 at 04:02:51PM -0400, A. Costa wrote: > On Wed, 24 Aug 2005 20:36:24 +0200 > maximilian attems <[EMAIL PROTECTED]> wrote: > > > an expired tag that would close bugs one month later after tagging if the > > bug reporter doesn't reappear would be on my highest wishlist now the bts > > gets even nicer. > > But suppose the maintainer is away for a while? Reporter X sends in > a report, Maintainer Y doesn't even reply for 6 months. So the BTS > closes it, so Y never sees it. > > Or suppose the _reporter_ was away for a while, or dies? X writes a > good report, a week later is eaten by sharks, two weeks after Y > replies, gets no reply for two weeks then closes it. already done quite a lot of bug sorting. a list of open bugs tagged wontfix is not a happy place. nor a list of bugs tagged moreinfo without any substantial feedback by its submitters. for the second ones such a slow die mode would be perfect. anyway this is not the place to discuss that. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#322086: ali5451 details
My laptop is a Sony Vaio PCG-FREV37. I don't know how it's wired on the inside; there appear to be three external connections (from the symbols, I think they're a line-out, a mic-in, and headphone/speaker-out; I've only tried the headphone jack). There's also a built-in speaker that normally is active when external speakers aren't plugged in. "amixer scontents" says: - cut here -- Simple mixer control 'Master',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 28 [90%] [on] Front Right: Playback 28 [90%] [on] Simple mixer control 'Master Mono',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 31 Mono: Playback 25 [81%] [on] Simple mixer control 'Headphone',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 24 [77%] [on] Front Right: Playback 24 [77%] [on] Simple mixer control 'Headphone Jack Sense',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'PCM',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 29 [94%] [on] Front Right: Playback 29 [94%] [on] Simple mixer control 'Line',0 Capabilities: pvolume pswitch cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 26 [84%] [on] Capture [off] Front Right: Playback 26 [84%] [on] Capture [off] Simple mixer control 'Line Jack Sense',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'CD',0 Capabilities: pvolume pswitch cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 25 [81%] [on] Capture [off] Front Right: Playback 25 [81%] [on] Capture [off] Simple mixer control 'Mic',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Mono Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Playback 28 [90%] [on] Front Left: Capture [on] Front Right: Capture [on] Simple mixer control 'Mic Boost (+20dB)',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'Mic Select',0 Capabilities: Mono: Simple mixer control 'Video',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Front Left - Front Right Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'Phone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Mono Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Playback 18 [58%] [on] Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'Aux',0 Capabilities: pvolume pswitch cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 31 Front Left: Playback 27 [87%] [on] Capture [off] Front Right: Playback 27 [87%] [on] Capture [off] Simple mixer control 'Mono Output Select',0 Capabilities: Mono: Simple mixer control 'Capture',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 15 Front Left: Capture 0 [0%] [on] Front Right: Capture 0 [0%] [on] Simple mixer control 'Mix',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Front Left - Front Right Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'Mix Mono',0 Capabilities: cswitch cswitch-joined cswitch-exclusive Capture exclusive group: 0 Capture channels: Front Left - Front Right Front Left: Capture [off] Front Right: Capture [off] Simple mixer control 'External Amplifier',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'Stereo Mic',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] --- cut here - and now for something really weird: unplugging the external speakers resulted in the internal speakers making noises where I used to get silence. Then, when I flicked the headphone jack sense a few more times and/or plugged/unplugged the speakers a few times, the internal sound output stopped again. Daniel -- /--- Daniel Bu
Bug#285017: marked as done (kernel-image-2.4.27-1-686: upgrading from v2 to v6 slows down my modem)
On Wed, 24 Aug 2005 20:36:24 +0200 maximilian attems <[EMAIL PROTECTED]> wrote: > an expired tag that would close bugs one month later after tagging if the > bug reporter doesn't reappear would be on my highest wishlist now the bts > gets even nicer. But suppose the maintainer is away for a while? Reporter X sends in a report, Maintainer Y doesn't even reply for 6 months. So the BTS closes it, so Y never sees it. Or suppose the _reporter_ was away for a while, or dies? X writes a good report, a week later is eaten by sharks, two weeks after Y replies, gets no reply for two weeks then closes it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Move report to correct package
Processing commands for [EMAIL PROTECTED]: > reassign 319986 linux-2.6 Bug#319986: linux-image-2.6.12-1-powerpc64 fails on dual G5 PowerMac7,3 Bug reassigned from package `kernel' to `linux-2.6'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323724: Dual G5 turns off after a while
"Sven" == Sven Luther <[EMAIL PROTECTED]> writes: Sven> On Tue, Aug 23, 2005 at 07:02:15PM -0700, Shyamal Prasad >> and, yes, I'm booting via with yaboot. I'm really stumped on >> why this kernel is not booting my machine when it works for >> Daniel (who also has a PowerMac7,3). Am I missing something >> obvious? Sven> So, what are you really booting ? Hi Sven, I am booting vmlinux-2.12-1-powerpc64 (installed from the sid deb file with its initrd). Sven> Did you run ybin and such, Actually I do not usually because I should not need to (I have the symbolic links set up so I can simply move them to point at the right images). But, just to be sure, I just tried it again and it changes nothing. Sven> did you try the stuff Benjamin Herrenschmidt suggested to Sven> Paul's bug report (#323724) ? Sven> Have a look at : Sven> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323724 Actually I'm having the same problem that Paul reported, except on a PowerMac 7,3 (970FX). The boot fails at the exact same point. I can try benh's suggestion but it will take some time (need to install the biarch toolchain and recompile kernel), and it was more about isolating the place where the fault happens, right? Sven> Maybe you could try : set panic_timeout in the yaboot kernel Sven> options as Bastian suggested before though Actually my PowerMac7,3 does not seem to reboot by itself in a big hurry (but I've never waited that long to find out). I usually have enough time to look over the kernel output and reset the power. Sven> Also, please write to bug report #323724 in futur, and not Sven> to the mailing list. Will do. Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
seinfeld dvds
Hello, I am interested in purchasing your set of Seinfeld DVD's to get all the 180 episodes and 9 seasons. Is this legit - I want to make sure I do not get scammed and receive nothing in return? What proof or guarantee do I have that you will come through and provide the item at hand? Do you ship to Virginia...? What price is the entire set. Can I use a DVD remote for scene selections and episode selection..? Also, is this truly DVD quality or VHS quality or VCD or what kind? Will these dvds all work in normal standard DVD players...? Sorry for overloading so many questions but please let me know ASAP so i can purchase the product. I really appreciate your response and look forward to doing business with you now and more in the future. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#285017: marked as done (kernel-image-2.4.27-1-686: upgrading from v2 to v6 slows down my modem)
On Tue, 16 Aug 2005, Horms wrote: > reopen 285017 > thanks > > Hi Maximilian, > > its still a bug in the 2.4.27 package. It may or may not be fixable. > And the patch may or may not be appropriate for Sarge. development wise 2.4 is long dead. therefor i'm not sure if it's sane to archive all it's bugs. i don't see much of use. users wont navigating through the unsorted obscure list of kernel packages that may affect them. either way i wont touch the 2.4 side of the bts. respect your engangement. > My current preference for handling problems like this, > is firstly to encourage the user to use a more up to date kernel. > Secondly downgrading feature requests (which this isn't) to > wishlist. And lastly ascertianing what if a fix exists, > and if so either adding it to SVN or marking the bug as +wontfix > accordingly. +wontfix is also my prefered option for bugs that > we think are too hard. as said above i don't see much gain in such a work. > While I don't like clutter in the BTS, I think closing bugs just > opens the door for duplicates to be subsequently filed, and > I'm not sure that helps anyone. > > On a related note, your work cleaning out bugs for 2.6.10, 11 and > other soon to be removed from the archive kernels is excellent. > I am really pleased about the way that is going. Its something > that has needed to be done for a while. thanks for the notice! :) anyway i'll try to allocate some timeslice for that from time to time. i have quite an horror for the pile of the kernel metapackage bug. as those are stable users, you can't help much for those. but ill try to also sort them. an expired tag that would close bugs one month later after tagging if the bug reporter doesn't reappear would be on my highest wishlist now the bts gets even nicer. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
dann frazier wrote: > On Tue, 2005-08-23 at 15:22 -0600, dann frazier wrote: > > We're getting closer. Please check this for accuracy: > > http://wiki.debian.net/?DebianKernelSargeUpdateStatus > > > > I can try to do hppa this afternoon; any word on m68k, mips & s390? > > Security Team, > Is there a way we can take advantage of your autobuilder setup for > lagging archs? Only when the source package is in the security queue accompanied with a binary package the buildds for missing architectures should try it on their respective architectures. Regards, Joey -- It's time to close the windows. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: status of first round of sarge kernel updates
On Tue, 2005-08-23 at 15:22 -0600, dann frazier wrote: > We're getting closer. Please check this for accuracy: > http://wiki.debian.net/?DebianKernelSargeUpdateStatus > > I can try to do hppa this afternoon; any word on m68k, mips & s390? Security Team, Is there a way we can take advantage of your autobuilder setup for lagging archs? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#324550: Needs dependency fix [linux-image-2.6.12-1-686: install fails with "cannot stat `(0xffffe000)': No such file or directory"]
On Wed, Aug 24, 2005 at 05:52:32PM +0900, GOTO Masanori wrote: > Thinking about this issue, I agree with Ted's opinion - we don't > probably need to consider about cross-release. However, actually this > problem was caused by glibc, and such change made old e2fsprogs > unusable. It's a bit hard to decide, but in this case I choose to add > "Conflicts: e2fsprogs (<= 1.37-2sarge1)". Ted, is this version <= > 1.37-2sarge1 correct value? Actually, to be completely correct, the right value should be "Conflicts: e2fsprogs (< 1.35-7)", as linux-gate.so started being filtered in e2fsprogs 1.35-7. (I wrote 1.37-5 in a previous message, but that was a typo; my apologies for any confusion that may have engendered.) - Ted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[PATCH 2/2] Debian mkinitrd: initrd for automatically loading dump capture kernel
The following patch provides feature to generate special initrd for
regular kernel which can load the dump capture kernel while booting.
--- mkinitrd.orig 2005-08-24 18:55:49.0 +0530
+++ mkinitrd2005-08-24 18:55:44.0 +0530
@@ -101,6 +101,8 @@ Options:
-r root Override ROOT setting in mkinitrd.conf.
-c dump_device Copy dump to this device
-f dump_dev_fs Filesystem on the dump device
+ -i initrd Capture kernel's initrd
+ -v kernel_image Capture kernel (vmlinux only for now)
See mkinitrd(8) for further details.
EOF
@@ -1213,6 +1215,9 @@ gendir() {
/sbin/pivot_root /bin/cat /bin/mknod \
/usr/sbin/chroot /bin/uname \
$([ $kdump_capture -eq 1 ] && find /bin /sbin -name dd
&& find /bin /sbin -name reboot) \
+ $([ $auto_kdump -eq 1 ] && for i in `find / -noleaf
-type f -name kexec`; do
+ echo $i; break;
+ done ) \
`command -v stat` $readlink \
`cat "$@" exe`
do
@@ -1289,6 +1294,12 @@ gendir() {
> etc/mtab
+ if [ $auto_kdump -eq 1 ]; then
+ cp $capture_initrd capture_initrd
+ cp $capture_kernel capture_kernel
+ fi
+
+
if [ $kdump_capture -eq 1 -a ! -b "${dump_dev#/}" ]; then
dump_maj=$(ls -l $dump_dev | cut -d " " -f 6 | cut -d "," -f 1)
dump_min=$(ls -l $dump_dev | cut -d " " -f 7)
@@ -1323,6 +1334,13 @@ umount /dump
echo Rebooting the system
reboot -f" >> script
fi
+
+ if [ "$auto_kdump" -eq 1 ]; then
+ echo "mount -t sysfs sys /sys
+echo Kexec loading the capture kernel
+`find . -name kexec` -p capture_kernel --args-linux --crash-dump
--initrd="capture_initrd" --append='root=$device init 1'
+echo Kexec loading done ">> script
+ fi
}
ORIGDIR=`pwd`
@@ -1331,11 +1349,12 @@ PROG="$0"
dump_dev=""
dump_fs=""
kdump_capture=0
+auto_kdump=0
CONFDIR=/etc/mkinitrd
unset keep croot cmkimage out || :
-while getopts "d:km:o:r:c:f:" flag; do
+while getopts "d:km:o:r:c:f:i:v:" flag; do
case $flag in
d)
CONFDIR="$OPTARG"
@@ -1364,6 +1383,12 @@ while getopts "d:km:o:r:c:f:" flag; do
f)
dump_fs=$OPTARG
;;
+ i)
+ capture_initrd=$OPTARG
+ ;;
+ v)
+ capture_kernel=$OPTARG
+ ;;
*)
usage
;;
@@ -1389,6 +1414,36 @@ else
kdump_capture=1
fi
+if [ $kdump_capture -eq 0 ]; then
+ if [ -z "$capture_initrd" -a -z "$capture_kernel" ]; then
+ auto_kdump=0
+ elif [ ! -z "$capture_initrd" -a -z "$capture_kernel" ]; then
+ echo 'Please specify the capture kernel'
+ usage
+ exit 1
+ elif [ -z "$capture_initrd" -a ! -z "$capture_kernel" ]; then
+ echo " Please specify the capture kernel's initrd "
+ usage
+ exit 1
+ else
+ if [ ! -e "$capture_initrd" ]; then
+ echo Capture kernel initrd "$capture_initrd" does not
exist...Aborting
+ exit 1
+ fi
+ if [ ! -e "$capture_kernel" ]; then
+ echo Capture kernel image "$capture_kernel" does not
exist...Aborting
+ exit 1
+ else
+ if [ $(file $capture_kernel | cut -d " " -f 2) != "ELF"
]; then
+ echo Capture kernel image "$capture_kernel" is
not an ELF \
+ executable...Aborting
+ exit 1
+ fi
+ fi
+ auto_kdump=1
+ fi
+fi
+
VERSION=$1
[ $# -gt 0 ] || unset VERSION
case $VERSION in
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[PATCH 1/2] Debian mkinitrd: initrd for automatically saving kdump
The following patch implements the feature to generate a special
initrd to automatically save the kdump.
--- mkinitrd.orig 2005-08-24 18:21:04.0 +0530
+++ mkinitrd2005-08-24 18:22:17.0 +0530
@@ -99,6 +99,8 @@ Options:
-m command Set the command to make an initrd image.
-o outfile Write to outfile.
-r root Override ROOT setting in mkinitrd.conf.
+ -c dump_device Copy dump to this device
+ -f dump_dev_fs Filesystem on the dump device
See mkinitrd(8) for further details.
EOF
@@ -1121,8 +1123,11 @@ gendir() {
echo 'unix 2> /dev/null'
echo '. swsusp 2> /dev/null' >&7
} >&3
- [ -z "$ROOT" ] || probe
+ [ -z "$ROOT" -o $kdump_capture -eq 1 ] || probe
+ if [ $kdump_capture -eq 1 ]; then
+ getroot $dump_dev
+ fi
exec 3>&- 4>&- 5>&- 6>&-
mkdir initrd
@@ -1207,6 +1212,7 @@ gendir() {
/bin/mount /bin/umount \
/sbin/pivot_root /bin/cat /bin/mknod \
/usr/sbin/chroot /bin/uname \
+ $([ $kdump_capture -eq 1 ] && find /bin /sbin -name dd
&& find /bin /sbin -name reboot) \
`command -v stat` $readlink \
`cat "$@" exe`
do
@@ -1279,10 +1285,17 @@ gendir() {
esac
cd initrd
- mkdir -p dev2 devfs etc keyscripts mnt proc scripts sys tmp var
+ mkdir -p dev2 devfs etc keyscripts mnt proc scripts sys tmp var `[
$kdump_capture -eq 1 ] && echo 'dump'`
> etc/mtab
+ if [ $kdump_capture -eq 1 -a ! -b "${dump_dev#/}" ]; then
+dump_maj=$(ls -l $dump_dev | cut -d " " -f 6 | cut -d "," -f 1)
+dump_min=$(ls -l $dump_dev | cut -d " " -f 7)
+ dev_type=$(ls -l $dump_dev | cut -c 1)
+ mknod "${dump_dev#/}" $dev_type $dump_maj $dump_min
+ DEVLINKS="$DEVLINKS ${dump_dev#/dev/}"
+ fi
devices=
for i in \
cciss ida ide scsi md mapper $DEVLINKS
@@ -1301,15 +1314,28 @@ gendir() {
fi
INITRDDIR=$dir/initrd MODULEDIR=$MODULEDIR VERSION=$VERSION \
run-parts "$CONFDIR"/scripts
+
+ if [ $kdump_capture -eq 1 ]; then
+ echo "mount -t $dump_fs $dump_dev /dump
+echo Copying the dump
+dd if=/proc/vmcore of=/dump/dumpfile
+umount /dump
+echo Rebooting the system
+reboot -f" >> script
+ fi
}
ORIGDIR=`pwd`
PROG="$0"
+dump_dev=""
+dump_fs=""
+kdump_capture=0
+
CONFDIR=/etc/mkinitrd
unset keep croot cmkimage out || :
-while getopts "d:km:o:r:" flag; do
+while getopts "d:km:o:r:c:f:" flag; do
case $flag in
d)
CONFDIR="$OPTARG"
@@ -1332,6 +1358,12 @@ while getopts "d:km:o:r:" flag; do
r)
croot=$OPTARG
;;
+ c)
+ dump_dev=$OPTARG
+ ;;
+ f)
+ dump_fs=$OPTARG
+ ;;
*)
usage
;;
@@ -1343,6 +1375,20 @@ if ! [ $out ] || [ $# -gt 1 ]; then
usage
fi
+if [ -z "$dump_dev" -a -z "$dump_fs" ]; then
+ kdump_capture=0
+elif [ -z "$dump_dev" -a ! -z "$dump_fs" ]; then
+ echo 'Please specify a dump device'
+ usage
+ exit 1
+elif [ ! -z "$dump_dev" -a -z "$dump_fs" ]; then
+ echo 'Please specify a filesystem for the dump device'
+ usage
+ exit 1
+else
+ kdump_capture=1
+fi
+
VERSION=$1
[ $# -gt 0 ] || unset VERSION
case $VERSION in
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[PATCH 0/2] Debian mkinitrd: Integrate kdump
Hi The following set of patches made on mkinitrd (from initrd-tools package:version 0.1.82), would enable the integration of kdump with Debian. For more details about the kexec based kdump solution please refer to Documentation/kdump/kdump.txt in the kernel source tree. This first patch (to be applied on the mkinitrd), would enable the generation of the initrd for the dump capture kernel. Usage: mkinitrd -c -f -o The second patch would enable the user to generate the initrd for the first or the regular kernel. This initrd will package the second kernel or the dump capture kernel along with its initrd, the kexec-tools user space application (needed to load the dump capture kernel). Usage: mkinitrd -i -v -o The user would then need to boot to the first kernel with this initrd. Incase of a panic/crash, the system will automatically boot to the capture kernel. The capture kernel's initrd will copy the dump and reboot the system back to regular kernel. This is a series patch set. Pls apply as follows on the mkinitrd: 1. capture_initrd.patch 2. first_initrd.patch Please let me know your comments. Thanks Rachita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling 2.6.12 with the debian patch
On Wed, 2005-08-24 at 18:06 +0900, Horms wrote: > This does seem to be a bug to me, as although the patches are already > applied, asking them to apply should just result in a noop, not the > script dying. Agreed. It should either be smart enough to figure out what to do, or print a reasonable error message when it has not been passed a kernel-tree revision. -- dann frazier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: dangling symlinux in 2.6.8
Processing commands for [EMAIL PROTECTED]: > reassign 323999 kernel-image-2.6.8-i386 Bug#323999: Dangling Symlink in /lib/modules/2.6.8-2-386/source in kernel-image-2.6.8-16 Bug reassigned from package `kernel-image-2.6.8-i386' to `kernel-image-2.6.8-i386'. > reassign 270577 kernel-image-2.6.8-i386 Bug#270577: kernel-image-2.6.8-1-k7: Source symlink points to builder's home directory Warning: Unknown package 'minor' Bug reassigned from package `minor' to `kernel-image-2.6.8-i386'. > reassign 268971 kernel-image-2.6.8-i386 Bug#268971: kernel-image-2.6.8-1-686-smp: dangling link Warning: Unknown package 'minor' Bug reassigned from package `minor' to `kernel-image-2.6.8-i386'. > severity 323999 minor Bug#323999: Dangling Symlink in /lib/modules/2.6.8-2-386/source in kernel-image-2.6.8-16 Severity set to `minor'. > severity 270577 minor Bug#270577: kernel-image-2.6.8-1-k7: Source symlink points to builder's home directory Severity set to `minor'. > severity 268971 minor Bug#268971: kernel-image-2.6.8-1-686-smp: dangling link Severity set to `minor'. > merge 323999 270577 268971 Bug#268971: kernel-image-2.6.8-1-686-smp: dangling link Bug#270577: kernel-image-2.6.8-1-k7: Source symlink points to builder's home directory Bug#323999: Dangling Symlink in /lib/modules/2.6.8-2-386/source in kernel-image-2.6.8-16 Merged 268971 270577 323999. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#302523: kernel-image-2.6.11-9-amd64-k8: module dm_mod locks my IDE disks
> Output of dmsetup? I guess that you are interested in "dmsetup ls", right? After I fix my system by removing the dm_mod module and manually mounting my 2 PATA drives, I get: # dmsetup ls /proc/misc: No entry for device-mapper found Is device-mapper driver missing from kernel? Failure to communicate with kernel device-mapper driver. /proc/misc: No entry for device-mapper found Is device-mapper driver missing from kernel? Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.01.04 (2005-08-02)(compat) and kernel driver Command failed # modprobe dm_mod # dmsetup ls No devices found In fact I guess that you are interested in the dmsetup output right after the boot, when the dm_mod module still locks my PATA drives. Unfortunately I cannot afford to reboot this machine now. I will do it when kernel 2.6.13 is out. -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Error while using mkinitrd of the initrd-tools (0.1.82) package
Hi
Following the change in the 'module_exists()' in the
latest version of mkinitrd, I encounter the following
error when I use mkinitrd to build an initrd.
find: /lib/modules/2.6.13-rc5/kernel/drivers/ide: No such
file or directory
My kernel has ide built in the kernel. The problem, I
suspect, lies in the print_ide_modules() call which assigns
none to $IDE_CORE and further calls print_module with
'drivers/ide/ide-disk'. The module_exists() then complains
as it does not find any /lib/modules/2.6.13-rc5/kernel/drivers/ide
directory.
Could probably have a check to see whether the required directory
exists before calling print_module() as follows:
--- mkinitrd.orig 2005-08-24 13:35:57.0 +0530
+++ mkinitrd2005-08-24 13:39:58.0 +0530
@@ -469,7 +469,9 @@ print_ide_modules() {
;;
*)
IDE_CORE=none
- print_module drivers/ide/ide-disk
+ if [ -d $MODULEDIR/kernel/drivers/ide ]; then
+ print_module drivers/ide/ide-disk
+ fi
return
;;
esac
Thanks
Rachita.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284477: Bug#302001: Merge bugs?
tag 302001 + upstream thanks On Wed, Aug 03, 2005 at 11:55:21AM +0200, Martin Stigge wrote: > Horms schrieb: > >>>Is there any chance that any of the interested parties could test > >>>a) 2.4.12 from unstable and b) an unpatched kernel from kernel.org? > >> > >>I'll try an unpatched kernel on an affected machine within the next 10 > >>days. > >> > >>Are you sure there is an 2.4.12 in unstable? > > > >Sorry I ment 2.6.12, its at > >ftp://ftp.debian.org/debian/pool/main/l/linux-2.6/ > > What worked so far is a self-compiled Debian patched 2.6.11 with > ACPI_SLEEP and X86_UP_IOAPIC disabled, but the precompiled 2.6.11-2-686 > didn't. What also worked (on one of the machines, the others are in > production-use, I can't test very much there) is the precompiled > 2.6.12-1-686 with kernel-option "noapic", and without that, the clock > went crazy again - which is a) from above. (!) These were my tests so > far -- I'll try a vanilla 2.6.12.3 within the next days (b from above). > > >>What's special to this kernel? I also tried kernel-image-2.4.27-2-686 > >>from sarge, where the problem seemed to be gone - but some of the > >>affected systems where somehow instable using this kernel (random > >>lockups within 3-6 days). > > > >There is nothing particularly special about 2.6.12, I just think it > >would be good to check if it has been fixed upstream. > > It's not. Thanks, I'm tagging this as upstream accordinly, but unfortunately I'm not sure what else to do with it. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#302001: Merge bugs?
On Wed, Jul 27, 2005 at 08:26:21AM -0300, Rafael Ávila de Espíndola wrote: > On Wednesday 27 July 2005 04:22, Horms wrote: > > Agreed, this mail should merge them. > > > > I had a quick look around, and it seems that most/all of the > > reports of this bug are from Debian users. Which could mean > > a number of things, but it does make me wonder if it is > > caused by one of the patches applied to the Debian Kernel. > If I recall correctly the bug was also present on Gentoo. The bug I reported > in the kernel bugzilla was in vanilla 2.6.8. Thanks, that is valuable information, at least we know its not been introduced by Debian. -- Horms
Processed: Re: Bug#302001: Merge bugs?
Processing commands for [EMAIL PROTECTED]: > tag 302001 + upstream Bug#302001: kernel-image-2.6.8-2-686: clock breaks after inserting uhci-hcd module There were no tags set. Bug#284477: kernel-image-2.6.8-1-686: IBM ThinkCentre sometimes goes to extremely sluggish state Bug#298301: system clock loops with 2.6.8 Tags added: upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: dangling symlinux in 2.6.8
Processing commands for [EMAIL PROTECTED]: > reassign 323999 kernel-image-2.6.8-i386 Bug#323999: Dangling Symlink in /lib/modules/2.6.8-2-386/source in kernel-image-2.6.8-16 Bug reassigned from package `kernel-image-2.6.8-i386' to `kernel-image-2.6.8-i386'. > reassign 270577 kernel-image-2.6.8-i386 Bug#270577: kernel-image-2.6.8-1-k7: Source symlink points to builder's home directory Bug reassigned from package `kernel-image-2.6.8-2-k7' to `kernel-image-2.6.8-i386'. > reassign 268971 kernel-image-2.6.8-i386 Bug#268971: kernel-image-2.6.8-1-686-smp: dangling link Bug reassigned from package `kernel-image-2.6.8-2-686-smp' to `kernel-image-2.6.8-i386'. > severity 323999 minor Bug#323999: Dangling Symlink in /lib/modules/2.6.8-2-386/source in kernel-image-2.6.8-16 Severity set to `minor'. > reassign 270577 minor Bug#270577: kernel-image-2.6.8-1-k7: Source symlink points to builder's home directory Warning: Unknown package 'minor' Bug reassigned from package `kernel-image-2.6.8-i386' to `minor'. > reassign 268971 minor Bug#268971: kernel-image-2.6.8-1-686-smp: dangling link Warning: Unknown package 'minor' Bug reassigned from package `kernel-image-2.6.8-i386' to `minor'. > merge 323999 270577 268971 Bug#268971: kernel-image-2.6.8-1-686-smp: dangling link Bug#270577: kernel-image-2.6.8-1-k7: Source symlink points to builder's home directory Bug#323999: Dangling Symlink in /lib/modules/2.6.8-2-386/source in kernel-image-2.6.8-16 Mismatch - only Bugs in same state can be merged: Values for `package' don't match: #268971 has `minor'; #323999 has `kernel-image-2.6.8-i386' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324583: linux-patch-debian-2.6.12: missing default version numbers in unpatch/apply script break make-kpkg
On Mon, Aug 22, 2005 at 11:00:46PM +0200, Sven Hartge wrote: > Package: linux-patch-debian-2.6.12 > Version: 2.6.12-5 > Severity: important > > > Somehow the @upstream@ and @version@ macros didn't get expanded in > debian/bin/unpatch and debian/bin/apply which causes Thanks, I was looking into a simmilar report on debian-kernel and noticed the same thing. I believe that I have a fix for it and it should go in the next release. I'll send an update here once I have had a chance to test my fix. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#282751: marked as done (kernel-image-2.6.8-i386: updating kernel 2.6.8 from -5 to -9: no initrd symlink)
Your message dated Wed, 24 Aug 2005 18:38:04 +0900 with message-id <[EMAIL PROTECTED]> and subject line Re; kernel-image-2.6.8-i386: updating kernel 2.6.8 from -5 to -9: no initrd symlink has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 24 Nov 2004 08:19:51 + >From [EMAIL PROTECTED] Wed Nov 24 00:19:50 2004 Return-path: <[EMAIL PROTECTED]> Received: from m127.net81-67-100.noos.fr (act.irishseb.dyndns.org) [81.67.100.127] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CWsNS-0006O6-00; Wed, 24 Nov 2004 00:19:50 -0800 Received: from sleibt by act.irishseb.dyndns.org with local (Exim 3.36 #1 (Debian)) id 1CWsMx-0001Yk-00; Wed, 24 Nov 2004 09:19:19 +0100 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Sebastien LITAIZE <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-image-2.6.8-i386: updating kernel 2.6.8 from -5 to -9: no initrd symlink X-Mailer: reportbug 3.2 Date: Wed, 24 Nov 2004 09:19:19 +0100 Message-Id: <[EMAIL PROTECTED]> Sender: SLeiBt <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,DATING,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel-image-2.6.8-i386 Severity: normal Hi!, Just did an upgrade, kernel 2.6.8 went from -5 to -9, but when lilo runs it complains, rightly so as the symlink to initrd is missing from /. A simple ln -s boot/initrd.img-2.6.8-1-686-smp initrd.img then re-running lilo seems to be OK (I can't reboot right now to be very sure...). I had the same thing on a machine running 2.6.8 -386 which is why I'm reporting this here. Regards, Sebastien -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) --- Received: (at 282751-done) by bugs.debian.org; 24 Aug 2005 09:51:10 + >From [EMAIL PROTECTED] Wed Aug 24 02:51:09 2005 Return-path: <[EMAIL PROTECTED]> Received: from koto.vergenet.net [210.128.90.7] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E7ruX-0004ie-00; Wed, 24 Aug 2005 02:51:09 -0700 Received: by koto.vergenet.net (Postfix, from userid 7100) id 518E934003; Wed, 24 Aug 2005 18:51:08 +0900 (JST) Date: Wed, 24 Aug 2005 18:38:04 +0900 From: Horms <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re; kernel-image-2.6.8-i386: updating kernel 2.6.8 from -5 to -9: no initrd symlink Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Cluestick: seven User-Agent: Mutt/1.5.9i Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 I do not believe the current release (-16) has this problem. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324817: marked as done (linux-source-2.6.12: permission denied when doing 'make menuconfig')
Your message dated Wed, 24 Aug 2005 11:48:07 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#324817: linux-source-2.6.12: permission denied when doing 'make menuconfig' has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 24 Aug 2005 08:31:19 + >From [EMAIL PROTECTED] Wed Aug 24 01:31:19 2005 Return-path: <[EMAIL PROTECTED]> Received: from mtagate1.uk.ibm.com [195.212.29.134] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1E7qfH-0002Rj-00; Wed, 24 Aug 2005 01:31:19 -0700 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate1.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j7O8UMA2259064 for <[EMAIL PROTECTED]>; Wed, 24 Aug 2005 08:30:23 GMT Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j7O8ULsL283464 for <[EMAIL PROTECTED]>; Wed, 24 Aug 2005 09:30:21 +0100 Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id j7O8ULeH017078 for <[EMAIL PROTECTED]>; Wed, 24 Aug 2005 09:30:21 +0100 Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j7O8UJqN017020; Wed, 24 Aug 2005 09:30:19 +0100 Received: from localhost.localdomain (sig-9-145-248-159.de.ibm.com [9.145.248.159]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id KAA65704; Wed, 24 Aug 2005 10:30:18 +0200 Message-Id: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" From: Chris Vanden Berghe <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: linux-source-2.6.12: permission denied when doing 'make menuconfig' X-Mailer: reportbug 3.16 Date: Wed, 24 Aug 2005 10:30:15 +0200 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mtagate1.uk.ibm.com id j7O8UMA2259064 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: linux-source-2.6.12 Version: 2.6.12-5 Severity: normal I get a permission denied error when trying to run 'make menuconfig' on a= clean kernel source: [EMAIL PROTECTED]:/mnt/hd2/usr/src$ sudo apt-get install linux-source-2.6.12 Reading package lists... Done Building dependency tree... Done Suggested packages: libncurses-dev libqt3-mt-dev The following NEW packages will be installed: linux-source-2.6.12 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 0B/36,5MB of archives. After unpacking 36,5MB of additional disk space will be used. Reading package fields... Done Reading package status... Done Retrieving bug reports... Done Selecting previously deselected package linux-source-2.6.12. (Reading database ... 155438 files and directories currently installed.) Unpacking linux-source-2.6.12 (from .../linux-source-2.6.12_2.6.12-5_all.= deb) ... Setting up linux-source-2.6.12 (2.6.12-5) ... [EMAIL PROTECTED]:/usr/src$ tar xvjf linux-source-2.6.12.tar.bz2 [EMAIL PROTECTED]:/mnt/hd2/usr/src$ ln -s linux-source-2.6.12 linux [EMAIL PROTECTED]:/mnt/hd2/usr/src$ cd linux [EMAIL PROTECTED]:/mnt/hd2/usr/src/linux$ make menuconfig HOSTCC scripts/basic/fixdep scripts/basic/fixdep.c: In function =E2=80=98parse_config_file=E2=80=99: scripts/basic/fixdep.c:245: warning: pointer targets in passing argument = 1 of =E2=80=98use_config=E2=80=99 differ in signedness scripts/basic/fixdep.c: In function =E2=80=98parse_dep_file=E2=80=99: scripts/basic/fixdep.c:299: warning: pointer targets in passing argument = 1 of =E2=80=98__builtin_strchr=E2=80=99 differ in signedness scripts/basic/fixdep.c:299: warning: pointer targets in assignment differ= in signedness /bin/sh: scripts/basic/fixdep: Permission denied make[1]: *** [scripts/basic/fixdep] Error 1 make: *** [scripts_basic] Error 2 [EMAIL PROTECTED]:/mnt/hd2/usr/src/linux$ groups vbc adm disk lp dialout cdrom floppy audio src video plugdev staff games = thinkpad nvram camera scanner [EMAIL PROTECTED]:/mnt/hd2/usr/src/linux$ sudo make menucon
Re: compiling 2.6.12 with the debian patch
On Fri, Aug 19, 2005 at 11:00:47AM -0600, dann frazier wrote: > On Fri, 2005-08-19 at 16:36 +0300, Teemu Ikonen wrote: > > Hi all, > > > > For a few recent versions of the Debian patch I've been getting the > > following when trying to compile the 2.6.12 kernel > > (linux-source-2.6.12-5) with > > "make-kpkg --added-patches debian kernel_image": > > > > test -f applied_patches && rm -f applied_patches > > make: [stamp-debian] Error 1 (ignored) > > for patch in /usr/src/kernel-patches/all/2.6.12/apply/debian ; do > > \ > > if test -x $patch; then\ > > if $patch; then \ > > echo "Patch $patch processed fine"; \ > > echo "$patch" >> applied_patches; \ > > else \ > >echo "Patch $patch failed."; \ > >echo "Hit return to Continue"; \ > >read ans; \ > > fi; \ > > fi; \ > > done > > E: Can't patch to nonexistent revision (wait until 2006) > > Patch /usr/src/kernel-patches/all/2.6.12/apply/debian failed. > > Hit return to Continue FYI: Sven Hartge has opened a bug for this in the BTS, #324583 -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324817: linux-source-2.6.12: permission denied when doing 'make menuconfig'
On Wed, Aug 24, 2005 at 10:30:15AM +0200, Chris Vanden Berghe wrote: > I get a permission denied error when trying to run 'make menuconfig' on a > clean kernel source: [as user] > /bin/sh: scripts/basic/fixdep: Permission denied [as root] > /bin/sh: scripts/basic/fixdep: Permission denied You don't showed if scripts/basic/fixdep is executable (which gcc always set for the executable output), so I expect that you have the filesystem mounted with noexec or similar. Bastian -- Star Trek Lives! signature.asc Description: Digital signature
Bug#324817: linux-source-2.6.12: permission denied when doing 'make menuconfig'
On Wed, Aug 24, 2005 at 10:30:15AM +0200, Chris Vanden Berghe wrote: > Package: linux-source-2.6.12 > Version: 2.6.12-5 > Severity: normal > > > I get a permission denied error when trying to run 'make menuconfig' on a > clean kernel source: Bizzare. Could you see if scripts/basic/fixdep exists, and if so, what permissions it has. It should be executable. Also, the following might shed some light on what is going on if its a compile problem: make V=1 menuconfig Another idea that springs to mind is that /mnt/hd2/usr/src is in a partition mounted noexec. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324817: linux-source-2.6.12: permission denied when doing 'make menuconfig'
On Wed, Aug 24, 2005 at 10:30:15AM +0200, Chris Vanden Berghe wrote: > Package: linux-source-2.6.12 > Version: 2.6.12-5 > Severity: normal > > > I get a permission denied error when trying to run 'make menuconfig' on a > clean kernel source: Well, it is obvious that the stuff in /usr/src should be owned by root, and that you should extract your tree in some other directory where you are allowed to mess with. On a debian system, anything outside of /home/ and /usr/local should be reserved to only the packaging system, and i guess only /home/ should have permissions. [1]. Try : cd ~ tar xvjf /usr/src/linux-source-2.6.12.tar.bz2 ln -s linux-source-2.6.12 linux cd linux make menuconfig [1] : Well, that is the theory, but i guess this will be enough to give you enough information to solve your problem given your own system setup. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: compiling 2.6.12 with the debian patch
On Fri, Aug 19, 2005 at 11:00:47AM -0600, dann frazier wrote: > On Fri, 2005-08-19 at 16:36 +0300, Teemu Ikonen wrote: > > Hi all, > > > > For a few recent versions of the Debian patch I've been getting the > > following when trying to compile the 2.6.12 kernel > > (linux-source-2.6.12-5) with > > "make-kpkg --added-patches debian kernel_image": > > > > test -f applied_patches && rm -f applied_patches > > make: [stamp-debian] Error 1 (ignored) > > for patch in /usr/src/kernel-patches/all/2.6.12/apply/debian ; do > > \ > > if test -x $patch; then\ > > if $patch; then \ > > echo "Patch $patch processed fine"; \ > > echo "$patch" >> applied_patches; \ > > else \ > >echo "Patch $patch failed."; \ > >echo "Hit return to Continue"; \ > >read ans; \ > > fi; \ > > fi; \ > > done > > E: Can't patch to nonexistent revision (wait until 2006) > > Patch /usr/src/kernel-patches/all/2.6.12/apply/debian failed. > > Hit return to Continue > > The linux-source tarball already contains the debian patches. See > http://wiki.debian.net/?DebianKernelTree and > http://wiki.debian.net/?DebianKernelSource for details. This does seem to be a bug to me, as although the patches are already applied, asking them to apply should just result in a noop, not the script dying. I think that I have isolated the problem, and I will try and get it fixed for the next release. The easiest work around, as Dann suggested, is to just ommit debian from --added-patches for now. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#324550: Needs dependency fix [linux-image-2.6.12-1-686: install fails with "cannot stat `(0xffffe000)': No such file or directory"]
At Wed, 24 Aug 2005 12:46:34 +0900, Horms wrote: > On Tue, Aug 23, 2005 at 08:17:58AM -0400, Theodore Ts'o wrote: > > On Tue, Aug 23, 2005 at 07:49:23PM +0900, Simon Horman [Horms] wrote: > > > long time no see. It seems that the problem is indeed fixed if you get > > > the sarge (or later) versions of e2fsprogs and glibc. However, some > > > people don't have that, and its causing some breakage for those people. > > > Would it be possible for you to add the conflicts that Ted suggested to > > > the next glibc release. This would seem like a nice way to make the > > > problem go away for everyone. > > > > Hmm, OK. This is how I understand the problem. > > > > If you are using the sarge versions of e2fsprogs (1.37-2sarge1) and > > libc6 (2.3.2), you're fine. > > > > If you are using the latest unstable versions of e2fsprogs (1.38-1 or > > the just uploaded 1.38-2) and glibc (2.3.5) you're also fine. > > > > The problem comes if you are using the sarge (1.37-2sarge1) version of > > e2fsprogs (or any version of e2fsprogs before 1.37-5) and an unstable > > version of glibc which is newer than 2.3.4, due to the change in what > > ldd outputs (the linux-gate.so entry). > > > > Since we can't retroactively fix e2fsprogs (although I suppose I am > > trying to get an updated 1.37-2sarge2 into the next stable update, I > > could try to convince the release managers to let me get an additional > > conflicts added, or to get the linux-gate.so filtering added to > > -2sarge2), the only way to fix this is to add the conflicts line to > > libc6. Thanks to Simon and Ted with the detailed explanation, I understand what the problem is. > > On the other hand, do we have to support these kinds of wierd > > cross-release dependencies? I have in the past updated to an unstable > > version of libc on a stable system, for various sordid reasons, but I > > always considered it something hazardous that might break things. I > > don't know that supporting a mix-and-match between stable and unstable > > is something we have to do, and if it means adding extra hair into > > libc6's dependencies that in practice may not get removed for a long > > time, is it worth doing? > > I'm not sure that kind of mixing and matching is really > supported, in the sense that if a new version exists, the > recommended solution is always to upgrade. > > I think your idea is worthwile, as people do mix and match, > but I'll also understand if Goto-san doesn't wan the > extra cruft in control - it will become irrelevant over time. > > I'm going to reassign this bug to libc6, Goto-san can close > it from there in whatever way he sees fit. Thinking about this issue, I agree with Ted's opinion - we don't probably need to consider about cross-release. However, actually this problem was caused by glibc, and such change made old e2fsprogs unusable. It's a bit hard to decide, but in this case I choose to add "Conflicts: e2fsprogs (<= 1.37-2sarge1)". Ted, is this version <= 1.37-2sarge1 correct value? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324817: linux-source-2.6.12: permission denied when doing 'make menuconfig'
Package: linux-source-2.6.12 Version: 2.6.12-5 Severity: normal I get a permission denied error when trying to run 'make menuconfig' on a clean kernel source: [EMAIL PROTECTED]:/mnt/hd2/usr/src$ sudo apt-get install linux-source-2.6.12 Reading package lists... Done Building dependency tree... Done Suggested packages: libncurses-dev libqt3-mt-dev The following NEW packages will be installed: linux-source-2.6.12 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 0B/36,5MB of archives. After unpacking 36,5MB of additional disk space will be used. Reading package fields... Done Reading package status... Done Retrieving bug reports... Done Selecting previously deselected package linux-source-2.6.12. (Reading database ... 155438 files and directories currently installed.) Unpacking linux-source-2.6.12 (from .../linux-source-2.6.12_2.6.12-5_all.deb) ... Setting up linux-source-2.6.12 (2.6.12-5) ... [EMAIL PROTECTED]:/usr/src$ tar xvjf linux-source-2.6.12.tar.bz2 [EMAIL PROTECTED]:/mnt/hd2/usr/src$ ln -s linux-source-2.6.12 linux [EMAIL PROTECTED]:/mnt/hd2/usr/src$ cd linux [EMAIL PROTECTED]:/mnt/hd2/usr/src/linux$ make menuconfig HOSTCC scripts/basic/fixdep scripts/basic/fixdep.c: In function ‘parse_config_file’: scripts/basic/fixdep.c:245: warning: pointer targets in passing argument 1 of ‘use_config’ differ in signedness scripts/basic/fixdep.c: In function ‘parse_dep_file’: scripts/basic/fixdep.c:299: warning: pointer targets in passing argument 1 of ‘__builtin_strchr’ differ in signedness scripts/basic/fixdep.c:299: warning: pointer targets in assignment differ in signedness /bin/sh: scripts/basic/fixdep: Permission denied make[1]: *** [scripts/basic/fixdep] Error 1 make: *** [scripts_basic] Error 2 [EMAIL PROTECTED]:/mnt/hd2/usr/src/linux$ groups vbc adm disk lp dialout cdrom floppy audio src video plugdev staff games thinkpad nvram camera scanner [EMAIL PROTECTED]:/mnt/hd2/usr/src/linux$ sudo make menuconfig HOSTCC scripts/basic/fixdep scripts/basic/fixdep.c: In function ‘parse_config_file’: scripts/basic/fixdep.c:245: warning: pointer targets in passing argument 1 of ‘use_config’ differ in signedness scripts/basic/fixdep.c: In function ‘parse_dep_file’: scripts/basic/fixdep.c:299: warning: pointer targets in passing argument 1 of ‘__builtin_strchr’ differ in signedness scripts/basic/fixdep.c:299: warning: pointer targets in assignment differ in signedness /bin/sh: scripts/basic/fixdep: Permission denied make[1]: *** [scripts/basic/fixdep] Error 1 make: *** [scripts_basic] Error 2 Cheers, Chris. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.t41-4 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-source-2.6.12 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-8high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities Versions of packages linux-source-2.6.12 recommends: ii gcc 4:4.0.1-3 The GNU C compiler ii libc6-dev [libc-dev] 2.3.5-4GNU C Library: Development Librari ii make 3.80-11The GNU version of the "make" util -- no debconf information
Bug#323757: Appears to be duplicate of #323702
> On Sun, Aug 21, 2005 at 11:39:59PM -0400, Barry Hawkins wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > After searching through the debian-kernel list archive, this report > > appears to be a duplicate of #323702. I won't merge them as the > > debian-kernel team may prefer to do that themselves based on their > > judgement. For those who need a fix for this issue soon, follow the > > workaround mentioned in #323702, purging and reinstalling your > > linux-headers packages. > > Indeed, it does seem to be the same bug, I am merging them. > > Also, the bug seems to be as fixed as it is ever going to be. > Its a packaging glitch, is been fixed, and there is a work > around for people who had the broken package. Unstable is... unstable. Thank you very much for taking the time to investigate this and point me to the solution. I feel a bti ashamed not having done it myself. So, once again, thanks a lot. -- Alexandre Fayolle signature.asc Description: Digital signature
