Bug#282234: marked as done (kernel-source-2.6.9: VesaFB doesn't work if compiled in statically)
Your message dated Mon, 4 Jul 2005 13:29:12 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#279648: bug still present in 2.6.11 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; 20 Nov 2004 16:42:57 + >From [EMAIL PROTECTED] Sat Nov 20 08:42:57 2004 Return-path: <[EMAIL PROTECTED]> Received: from pop.gmx.de (mail.gmx.net) [213.165.64.20] by spohr.debian.org with smtp (Exim 3.35 1 (Debian)) id 1CVYK8-l1-00; Sat, 20 Nov 2004 08:42:57 -0800 Received: (qmail 24158 invoked by uid 65534); 20 Nov 2004 16:42:24 - Received: from dialin-212-144-026-106.arcor-ip.net (EHLO trabant) (212.144.26.106) by mail.gmx.net (mp020) with SMTP; 20 Nov 2004 17:42:24 +0100 X-Authenticated: #7318305 Received: from felix by trabant with local (Exim 3.36 #1 (Debian)) id 1CVYMo-cK-00; Sat, 20 Nov 2004 17:45:42 +0100 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Felix Kuehling <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: kernel-source-2.6.9: VesaFB doesn't work if compiled in statically X-Mailer: reportbug 2.63 Date: Sat, 20 Nov 2004 17:45:42 +0100 Message-Id: <[EMAIL PROTECTED]> Sender: Felix Kuehling <[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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel-source-2.6.9 Version: 2.6.9-1 Severity: important This is probably related to bug #279648. There are some reports in there that sound like they are actually this bug. VesaFB doesn't work (blank screen) if compiled in statically in version 2.6.9. The same configuration worked with kernel-source-2.6.8. If I compile VesaFB as a module and load it via /etc/modules (I don't use initrd) the display works after the module has been loaded. Is there any more info you need about my kernel or lilo configuration? -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9 Locale: LANG=de_DE, LC_CTYPE=de_DE Versions of packages kernel-source-2.6.9 depends on: ii binutils 2.15-4 The GNU assembler, linker and bina ii bzip2 1.0.2-1A high-quality block-sorting file ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities -- no debconf information --- Received: (at 282234-done) by bugs.debian.org; 4 Jul 2005 04:54:39 + >From [EMAIL PROTECTED] Sun Jul 03 21:54:39 2005 Return-path: <[EMAIL PROTECTED]> Received: from koto.vergenet.net [210.128.90.7] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DpIyd-0004b9-00; Sun, 03 Jul 2005 21:54:39 -0700 Received: by koto.vergenet.net (Postfix, from userid 7100) id 6E3CD3402B; Mon, 4 Jul 2005 13:24:42 +0900 (JST) Date: Mon, 4 Jul 2005 13:29:12 +0900 From: Horms <[EMAIL PROTECTED]> To: Bastian Venthur <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#279648: bug still present in 2.6.11 Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> 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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER, VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 3 reassign 279648 kernel-source-2.6.11 reassign 282234 kernel-source-2.6.11 thanks On Fri, Jul 01, 2005 at 03:16:29PM +0200, Bastian Venthur wrote: > Package: kernel-source-2.6.10 > Followup-For: Bug #279648 > > Hi kernel-team, > > this bug is over 1/2year old and still present in 2.6.11. > > Is it possible to upgrade this bug at least to important (if not grave?) > -- having no display on bootup is in my opinion a really bad bug, and > not everyone knows, that booting with vga=normal
Bug#279648: bug still present in 2.6.11
reassign 279648 kernel-source-2.6.11 reassign 282234 kernel-source-2.6.11 thanks On Fri, Jul 01, 2005 at 03:16:29PM +0200, Bastian Venthur wrote: > Package: kernel-source-2.6.10 > Followup-For: Bug #279648 > > Hi kernel-team, > > this bug is over 1/2year old and still present in 2.6.11. > > Is it possible to upgrade this bug at least to important (if not grave?) > -- having no display on bootup is in my opinion a really bad bug, and > not everyone knows, that booting with vga=normal is a workaround. > > Interesting here is also, that this bug is already localized in one file > (modular-vesafb.dpatch) since over a 1/2 year but not fixed. Is there any > additional information I could give to help fixing this bug? > > Or is there any progress, the (many) submitters should know? > > Related (if not the same) bugs: #282234 #309682 Lets start by cleaning up the bugs. I am closing 309682 as it is a duplicate of 279648. I am also closing 28223 as on examining the kernel-source-2.6.11 source it appears to be fix, if someone has experience to the contrary, please reopen it. And I am reassigning 279648 and 282234 to kernel-source-2.6.11 as it is currently assigned to kernel-source-2.6.9 which has not been suported for quite sime time now. I don't even think it is on d.o anymore. And as to the severity of the bug, I don't believe the guidlines specify age as a parameter for bug seveirty. As for 279648 itself, the bug report seems to indicate that disabling CONFIG_BLK_DEV_UB (a very green piece of code introduced in 2.6.11 bug probably not ready for prime time) resolves the problem, and the current kernel-images (for i386 at least) do just this. Could you take a look in your kernel config and if CONFIG_BLK_DEV_UB is enabled, please disable it. Thanks -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309682: marked as done (console vga mode problem)
Your message dated Mon, 4 Jul 2005 13:29:12 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#279648: bug still present in 2.6.11 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; 18 May 2005 19:53:32 + >From [EMAIL PROTECTED] Wed May 18 12:53:32 2005 Return-path: <[EMAIL PROTECTED]> Received: from master.debian.org [146.82.138.7] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DYUbk-0003A4-00; Wed, 18 May 2005 12:53:32 -0700 Received: from pd9e77b3d.dip.t-dialin.net (localhost.localdomain) [217.231.123.61] by master.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DYUbi-0006Ec-00; Wed, 18 May 2005 14:53:30 -0500 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Bastian Venthur <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: console vga mode problem X-Mailer: reportbug 3.12 Date: Wed, 18 May 2005 21:53:59 +0200 X-Debbugs-Cc: [EMAIL PROTECTED] Message-Id: <[EMAIL PROTECTED]> 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-Status: No, hits=-7.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS, HAS_PACKAGE,OUR_MTA_MSGID,X_DEBBUGS_CC autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.11 Version: 2.6.11-5 Severity: important In this kernel, there is still the bug #279648 (console vga mode problem) present. Since this bug is nearly 1/2 year old, and not present in kernel.org-kernel maybe someone should check the debian-(vesafb?)-patches. I think #282234 has something to to with this bug. Sincerely Bastian -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-laptop Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-source-2.6.11 depends on: ii binutils 2.15-5 The GNU assembler, linker and bina ii bzip2 1.0.2-6high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities -- no debconf information --- Received: (at 309682-done) by bugs.debian.org; 4 Jul 2005 04:54:39 + >From [EMAIL PROTECTED] Sun Jul 03 21:54:39 2005 Return-path: <[EMAIL PROTECTED]> Received: from koto.vergenet.net [210.128.90.7] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DpIyd-0004b9-00; Sun, 03 Jul 2005 21:54:39 -0700 Received: by koto.vergenet.net (Postfix, from userid 7100) id 6E3CD3402B; Mon, 4 Jul 2005 13:24:42 +0900 (JST) Date: Mon, 4 Jul 2005 13:29:12 +0900 From: Horms <[EMAIL PROTECTED]> To: Bastian Venthur <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#279648: bug still present in 2.6.11 Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> 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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER, VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 4 reassign 279648 kernel-source-2.6.11 reassign 282234 kernel-source-2.6.11 thanks On Fri, Jul 01, 2005 at 03:16:29PM +0200, Bastian Venthur wrote: > Package: kernel-source-2.6.10 > Followup-For: Bug #279648 > > Hi kernel-team, > > this bug is over 1/2year old and still present in 2.6.11. > > Is it possible to upgrade this bug at least to important (if not grave?) > -- having no display on bootup is in my opinion a really bad bug, and > not everyone knows, that booting with vga=normal is a workaround. > > Interesting here is also, that this bug is already localized in one file > (modular-vesafb.dpatch) since over a 1/2 year but not fixed. Is there any > additional information I could give to help fixing this bug? > > Or is there any progress, the (many) submitters should know? > > Related (if not
Re: depmod -a after module install
On Sun, Jul 03, 2005 at 10:35:22PM +0300, Tzafrir Cohen wrote: > Hi debian-kernel folks, > > I'm trying to modify the package zaptel-source (generated from source > package zaptel). That package is used to build a kernel modules package > called zaptel-modules- (zaptel-modules hence forth). > > Currently the package zaptel-source has a postinst script that runs: > > if [ "`uname -r`" = "_KVERS_" ]; > depmod -a & > fi > > That script is probably useless for the source package itself, as it has > no kernel modules itself, and the kernel version at the time of its > install is irrelevant to the kernel that will be built later. I moved it > to the postinst script of the gemnerated zaptel-modules package (I > fogure that an appropriate postrm script should be added). > > However I noticed an error in a script that installed that package. I > noticed that this script runs: > > apt-get install zaptel-modules-$kernel > depmod -a > > The error message was from depmod, because the two runs of depmod > aparantly colided. The manual install of depmod could be removed. But > what would have hapanned had I run: > > > apt-get install zaptel-modules-$kernel other-modules-$kernel > > and the package other-modules-$kernel had the same script? Any chance > the same error would occour? > > So what should I do: > > 1. Drop that postinst script. Require more work from the installer > > 2. Keep the script as-is > > 3. run 'depmod -a' with no '&' instead, and possibly further delay >installation? I'd choose option 3. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GCC version change / C++ ABI change
On Mon, Jul 04, 2005 at 03:07:23AM +0200, Matthias Klose wrote: > Junichi Uekawa writes: > > Hi, > > > > > This week, we will change the GCC default versions from 3.3 to 4.0 > > > > Would it break kernel 2.4 builds somehow ? > > No, you can still build using gcc-3.3. I have added this as a build dependancy for all the kernel images that are in the kernel team's svn tree, that is alpha, hppa, i386, ia64, mips, powerpc, s390 and sparc. This should appear in their respective next releases. I have CCed the uploaders of these packages, if you are one of those people and have a reason to undo this change, please do so, I have no ambitions to tread on your toes. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#251023: mkinitrd is already adapted to add the DSDT
On Fri, Jul 01, 2005 at 05:30:36PM +0100, David Goodenough wrote:
> On Friday 01 July 2005 11:42, A Mennucc wrote:
> > hi there
> >
> > I am very interested in patches for custom DSDT support (I own
> > an ASUS notebook which has a broken DSDT, so ACPI suspend does not work;
> > and there is a fixed DSDT in acpi.sf.net that I would love to try);
> >
> > I hope that they would accepted in Debian's shipped kernel
> > (see bug 251023).
> >
> > So I want to point a very important fact: the command /usr/sbin/mkinitrd
> > in Debian Sarge already supports those patches: at the end it
> > sports the lines
> >
> >
> > if [ -e /etc/mkinitrd/DSDT ]; then
> >echo -n "INITRDDSDT123DSDT123" >>${initrd_file}
> >cat /etc/mkinitrd/DSDT >>${initrd_file}
> > fi
> >
> > so the Debian user would just need to put the fixed DSDT in
> > /etc/mkinitrd/DSDT and it would be included in mkinitrd, and
> > (as soon as the patch is accepted in default Debian kernels)
> > it would be loaded at startup: easy and clean.
> >
> > I guess that for the above mkinitrd snippet , we would need the patch
> > http://gaugusch.at/acpi-dsdt-initrd-patches/acpi-dsdt-initrd-patch-v0.7d-2.
> >6.9.patch (for kernel >= 2.6.9 ) and the patch
> > http://gaugusch.at/acpi-dsdt-initrd-patches/acpi-dsdt-initramfs-fix-2.6.10-
> >cleanup.patch (for kernel == 2.6.10 )
> >
> > Unfortunately this last patch fails on the standard kernel in Sarge, that
> > is 2.6.8 ... I will need to look into it ..
> >
> > a.
>
> I agree that this would be useful. When I raised it several months ago
> I was told that this INITRD method was not the prefered route in the
> kernel currently as they prefer the route of statically linking the DSDT
> into the kernel. I think this is daft as most people do not want to get
> involved in building kernels. Actually I think that while this method is
> better than a whole kernel build that really the best solution would be
> to modify the kernel and LILO/GRUB/whatever_boot_loader to take a
> file name for the DSDT and then all that is needed is to create the
> file - much easier for Joe User.
I imagine this followed from not wanting to include the code in question
in the debian kernel, which in turn I would guess boils down to either or
both of the following:
1. The Debian kernel doesn't add patches that aren't upstream.
2. The Debian kernel can only include DFSG free code.
And I imagine the road to finding a solution that doesn't completely
suck for users, has to keep both of these points in mind. On the
other hand, I haven't checked the code in question, and both of
these points may be invalid.
> The problem obviously is that this has to be done VERY early in the
> kernel boot process so no solution is going to be trivial, but it must
> be as easy as possible for Joe User as many laptops have these
> problems.
--
Horms
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GCC version change / C++ ABI change
Junichi Uekawa writes: > Hi, > > > This week, we will change the GCC default versions from 3.3 to 4.0 > > Would it break kernel 2.4 builds somehow ? No, you can still build using gcc-3.3. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GCC version change / C++ ABI change
Thiemo Seufer <[EMAIL PROTECTED]> writes: > Junichi Uekawa wrote: >> Hi, >> >> > This week, we will change the GCC default versions from 3.3 to 4.0 >> >> Would it break kernel 2.4 builds somehow ? >> I've not been quite following; but the thread almost a month ago >> seems to indicate thus: >> http://www.kerneltraffic.org/kernel-traffic/kt20050701_316.html#7 > > Quite likely, yes. 2.4 Kernels would need to Build-Dep on 3.4. But the current versions of 2.4 doesn't get fixed yet? -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#316809: kernel-source-2.6.11: tell where to find the Debian .config
Package: kernel-source-2.6.11 Version: 2.6.11-7 Severity: wishlist I wanted to rebuild a kernel-image package starting with the same .config in the official Debian packages. One way to do this is to install the kernel-image package, which contains it in /boot/config-XXX, but it's annoying to install a huge kernel-image package you're just going to replace. It took me a good while to notice that the .config file is also in the kernel-headers package (obvious in retrospect), in /usr/src/kernel-headers-XXX/.config. That's also a big download for just that file, though I already happened to have it installed. Finally, I discovered that the kernel-image _source_ package is (contrary to intuition) a tiny little thing containing little other than the .configs. I would suggest either copying the .configs into the kernel-source package, or putting clear documentation into the kernel-source package, say in README.Debian: If you want to start with the same kernel .config used in the official Debian kernel-image package, get it from the _source_ package for the relevant kernel-image (don't worry, it's a small download). BTW, the kernel-headers-2.6.11-1 package contains /usr/share/doc/kernel-headers-2.6.11-1/config-2.6.11-1.gz matching /usr/src/kernel-headers-2.6.11-1/.config; however the kernel-headers-2.6.11-1-686 contains no such file in /usr/share/doc. Is that intentional? Andrew -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages kernel-source-2.6.11 depends on: ii binutils 2.15-7 The GNU assembler, linker and bina ii bzip2 1.0.2-7high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities Versions of packages kernel-source-2.6.11 recommends: ii gcc 4:3.3.6-1The GNU C compiler ii libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari ii make3.80-9 The GNU version of the "make" util -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GCC version change / C++ ABI change
Junichi Uekawa wrote: > Hi, > > > This week, we will change the GCC default versions from 3.3 to 4.0 > > Would it break kernel 2.4 builds somehow ? > I've not been quite following; but the thread almost a month ago > seems to indicate thus: > http://www.kerneltraffic.org/kernel-traffic/kt20050701_316.html#7 Quite likely, yes. 2.4 Kernels would need to Build-Dep on 3.4. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GCC version change / C++ ABI change
Hi, > This week, we will change the GCC default versions from 3.3 to 4.0 Would it break kernel 2.4 builds somehow ? I've not been quite following; but the thread almost a month ago seems to indicate thus: http://www.kerneltraffic.org/kernel-traffic/kt20050701_316.html#7 regards, junichi -- Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/ 183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recompile Kernel problem.
There is a --initrd flag you need to pass to make-kpkg to have the initrd built. Regards, satadru -Original Message- From: Jaccon <[EMAIL PROTECTED]> Date: Sunday, Jul 3, 2005 4:59 pm Subject: Recompile Kernel problem. Hi, i have the problem while the recompile the Kernel 2.6.12 in Debian 3.1 Sarge with kernel 2.6.8. The system dont make the initrd file and Lilo dont update the configuration automatic. I use the command. make menuconfig save the configuration make-kpkg -rev .Custom1 kernel_image dpkg -i kernel-2.6.12-Custom1.deb The command its OK ? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Recompile Kernel problem.
Hi, i have the problem while the recompile the Kernel 2.6.12 in Debian 3.1 Sarge with kernel 2.6.8. The system dont make the initrd file and Lilo dont update the configuration automatic. I use the command. make menuconfig save the configuration make-kpkg -rev .Custom1 kernel_image dpkg -i kernel-2.6.12-Custom1.deb The command its OK ? Thanks
depmod -a after module install
Hi debian-kernel folks, I'm trying to modify the package zaptel-source (generated from source package zaptel). That package is used to build a kernel modules package called zaptel-modules- (zaptel-modules hence forth). Currently the package zaptel-source has a postinst script that runs: if [ "`uname -r`" = "_KVERS_" ]; depmod -a & fi That script is probably useless for the source package itself, as it has no kernel modules itself, and the kernel version at the time of its install is irrelevant to the kernel that will be built later. I moved it to the postinst script of the gemnerated zaptel-modules package (I fogure that an appropriate postrm script should be added). However I noticed an error in a script that installed that package. I noticed that this script runs: apt-get install zaptel-modules-$kernel depmod -a The error message was from depmod, because the two runs of depmod aparantly colided. The manual install of depmod could be removed. But what would have hapanned had I run: apt-get install zaptel-modules-$kernel other-modules-$kernel and the package other-modules-$kernel had the same script? Any chance the same error would occour? So what should I do: 1. Drop that postinst script. Require more work from the installer 2. Keep the script as-is 3. run 'depmod -a' with no '&' instead, and possibly further delay installation? Please CC me your reply, TIA. -- Tzafrir Cohen icq#16849755 +972-50-7952406 [EMAIL PROTECTED] http://www.xorcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
No pills, no pumps - Its the Patch
Wanna be more man? Check this dude http://www.siratu.com/ss/ If they give you ruled paper, write the other way. It is feeling and force of imagination that make us eloquent. When all think alike, no one thinks very much. In adversity remember to keep an even mind. Getting old is not for sissies. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#316393: marked as done (setserial does not set closing_wait correctly on kernel 2.6.8)
Processing commands for [EMAIL PROTECTED]: > reopen 316393 Bug#316393: setserial does not set closing_wait correctly on kernel 2.6.8 Bug reopened, originator not changed. > 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]
Re: Bug#316393: setserial does not set closing_wait correctly on kernel 2.6.8
reassign 316393 kernel-source-2.6.8 thanks Hi Dr. Oliver Muth On Sat, Jul 02, 2005 at 08:27:35PM +0200, Dr. Oliver Muth wrote: > Hi Ola, > > I compiled the kernel myself from Debian kernel-source-2.6.8-16. So I > guess this is the package it belongs to. Ok, I see. > Sorry for bothering you with it. No problem. Reassigning to that version now. Regards, // Ola > Best regards > > Oliver > > Am Samstag, den 02.07.2005, 16:27 +0200 schrieb Ola Lundqvist: > > Hello > > > > Looks like a kernel bug to me. To what package should I redirect > > this bug? > > > > Regards, > > > > // Ola > > > > On Thu, Jun 30, 2005 at 07:54:06AM +0200, Dr. Oliver Muth wrote: > > > Package: setserial > > > Version: 2.17-41 > > > Severity: normal > > > > > > Hi! > > > > > > Maybe this is not a bug in setserial but in the 2.6.8 kernel: > > > setserial reports high values for close_delay and closing_wait. > > > When I try to change close_delay to 3000 with setserial, the is 3, > > > with 300 I get 3000. > > > > > > This is what I get from setserial with kernel 2.6.8: > > > /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 > > > Baud_base: 115200, close_delay: 5000, divisor: 0 > > > closing_wait: 37856 > > > Flags: spd_normal skip_test > > > With kernel 2.4.25 I got close_delay=50 and > > > closing_wait=3000. > > > > > > Best regards > > > > > > Oliver > > > > > > -- System Information: > > > Debian Release: 3.1 > > > APT prefers testing > > > APT policy: (500, 'testing') > > > Architecture: i386 (i686) > > > Kernel: Linux 2.6.8 > > > Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) > > > > > > Versions of packages setserial depends on: > > > ii debconf 1.4.30.13Debian configuration > > > management sy > > > ii libc6 2.3.2.ds1-22 GNU C Library: Shared > > > libraries an > > > > > > -- debconf information: > > > setserial/rc-boot-file-removed: > > > setserial/rc-boot-file-renamed: > > > setserial/update-modules-failed: > > > setserial/autosave: true > > > * setserial/autosave-types: autosave once > > > > > > > > > -- > Dr. Oliver Muth <[EMAIL PROTECTED]> > > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering / [EMAIL PROTECTED] Annebergsslingan 37\ | [EMAIL PROTECTED] 654 65 KARLSTAD| | http://www.opal.dhs.org Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#316393: marked as done (setserial does not set closing_wait correctly on kernel 2.6.8)
Your message dated Sun, 3 Jul 2005 16:01:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#316393: setserial does not set closing_wait correctly on kernel 2.6.8 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; 30 Jun 2005 16:56:10 + >From [EMAIL PROTECTED] Thu Jun 30 09:56:10 2005 Return-path: <[EMAIL PROTECTED]> Received: from ak132.nuaccess.net (athlon-9.bjoernsjoe) [213.142.10.132] (Debian-exim) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Do2Kc-00085Q-00; Thu, 30 Jun 2005 09:56:10 -0700 Received: from oliver by athlon-9.bjoernsjoe with local (Exim 4.50) id 1Dnrzy-0001tS-MC for [EMAIL PROTECTED]; Thu, 30 Jun 2005 07:54:06 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Dr. Oliver Muth" <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: setserial does not set closing_wait correctly on kernel 2.6.8 X-Mailer: reportbug 3.8 Date: Thu, 30 Jun 2005 07:54:06 +0200 Message-Id: <[EMAIL PROTECTED]> 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-Status: No, hits=-7.3 required=4.0 tests=BAYES_00,DATE_IN_PAST_06_12, HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: setserial Version: 2.17-41 Severity: normal Hi! Maybe this is not a bug in setserial but in the 2.6.8 kernel: setserial reports high values for close_delay and closing_wait. When I try to change close_delay to 3000 with setserial, the is 3, with 300 I get 3000. This is what I get from setserial with kernel 2.6.8: /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 Baud_base: 115200, close_delay: 5000, divisor: 0 closing_wait: 37856 Flags: spd_normal skip_test With kernel 2.4.25 I got close_delay=50 and closing_wait=3000. Best regards Oliver -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages setserial depends on: ii debconf 1.4.30.13Debian configuration management sy ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- debconf information: setserial/rc-boot-file-removed: setserial/rc-boot-file-renamed: setserial/update-modules-failed: setserial/autosave: true * setserial/autosave-types: autosave once --- Received: (at 316393-done) by bugs.debian.org; 3 Jul 2005 13:59:15 + >From [EMAIL PROTECTED] Sun Jul 03 06:59:15 2005 Return-path: <[EMAIL PROTECTED]> Received: from c-adt-5.ataco.se (bixbite.opalsys.net) [213.115.168.248] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Dp507-0005gx-00; Sun, 03 Jul 2005 06:59:15 -0700 Received: from ola by bixbite.opalsys.net with local (Exim 4.50) id 1Dp51r-0008GW-0f; Sun, 03 Jul 2005 16:01:03 +0200 Date: Sun, 3 Jul 2005 16:01:02 +0200 From: Ola Lundqvist <[EMAIL PROTECTED]> To: "Dr. Oliver Muth" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#316393: setserial does not set closing_wait correctly on kernel 2.6.8 Message-ID: <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <[EMAIL PROTECTED]> 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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER, VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: X-CrossAssassin-Score: 2 reassign 316393 kernel-source-2.6.8 thanks Hi Dr. Oliver Muth On Sat, Jul 02, 2005 at 08:27:35PM +0200, Dr. Oliver Muth wrote: > Hi Ola, > > I compiled the kernel myself from Debian kernel-source-2.6.8-16. So I > guess this is the package it belongs to. Ok, I see. > Sorry for bothering you with it. No problem. Reassigning to that version now. Regards, // Ola > Best regards > > Oliver > > Am Samstag, den 02.07.2005, 16:27 +0200 schrieb Ola Lundqvist: >
Processed: Re: Bug#316393: setserial does not set closing_wait correctly on kernel 2.6.8
Processing commands for [EMAIL PROTECTED]: > reassign 316393 kernel-source-2.6.8 Bug#316393: setserial does not set closing_wait correctly on kernel 2.6.8 Bug reassigned from package `setserial' to `kernel-source-2.6.8'. > 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]
Now, it's finally possible for you to enlarge your penis
New Penis Enlargement Patches! http://www.siratu.com/ss/ The murals in restaurants are on par with the food in museums. Do what you can, with what you have, where you are. A precedent embalms a principle. You're never too old to become younger. The trouble with computers, of course, is that they're very sophisticated idiots. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#67718: Cheap Software-Upgrades-educational bargains-oem-Software Buyer's Guide.
Name-brand software at low, low, low, low prices http://gcy.jq5gmijcyb18y2j.canellaih.info What I dream of is an art of balance. If you tell a lie -- tell a big one. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
