Re: 2.6.12 upload
On Thu, Jul 21, 2005 at 11:04:07AM +0200, Goswin von Brederlow wrote: Horms [EMAIL PROTECTED] writes: On Wed, Jul 20, 2005 at 10:17:00AM +0200, Goswin von Brederlow wrote: Thiemo Seufer [EMAIL PROTECTED] writes: Andres Salomon wrote: [snip] It is IMHO not realistic to expect the rest of the world to wait for some obscure subarchitecture. Who said we're going to wait for some obscure subarchitecture? We're going to keep working on kernels until we freeze for etch, at which point the subarchitectures have a limit amount of time to catch up. The problem is the ongoing development in unstable. It is e.g. not possible to build debian-installer for that subarch and upload it if its kernel isn't already/still in unstable. Thiemo Actualy there are 2 problems: 1. Slow archs will keep the kernel-source from migrating to testing. That is if those archs are still testing blockers. I think this can seriously harm the amount of testing the kernel gets. Suelry this is a broader problem realating to buildds in general, if they aren't fast enough, they need more resources. We can help this to some extent by trying to cut down on the number of flavours floating around, especially on slower arches. However, the kernel is by no means the largest package in Debian (I believe OpenOffice.Org builds in arm take a full week) and this doesn't seem to be a major problem in Debian at large. No. I don't mean that m68k will take so long to compile. Well, it does, but it will get there in time for medium or low uploads. Critical uploads might stress it though. But an extra day delay isn't too bad. But what if the kernel FTBFS on mips? It needs to be looked into, the mips patch needs to be updated, tested, merged and a new source needs to be uploaded. If the looking into and fixing takes 3 month then that will be 3 month without a new kernel in etch. Yes, that is a problematic scenario. But if such a problem occurs, and it really is holding up the kernel for all arches, surely some time can be found to fix patch at the time. 2. Each kernel-image-di-arch source needs the right kernel-image version and source for its architecture to be present in the archive to be GPL compliant. This is only a problem for the archive software to keep track of. Someone has to write code for this. The D-I build should be using only the linux-kernel-di udebs if I'm not mistaken. As long as they are available D-I should keep building. Or did I miss something and the linux-kernel-di packages will disapear into the main kernel-source package? Firstly, I don't agree that this is neccessary for GPL compliance in any way whatsoever, however I do accept that some people believe that it is. To keep those people happy, kernel-images should depend on kernel-tree-X.Y.Z-N and everything works just fine - that is, the kernel-image can be reproduced verbatim ecen if the kernel source package increases N. You've got the wrong packages. The DI kernel udebs (linux-kernel-di-arch source) takes the kernel-image deb, splits it up into kernel and several groups of modules and builds udebs. There is no Depends there and can't be to keep the kernel-image debs available. kernel-image-di-arch ---source--- linux-kernel-di | magic | \/ kernel-tree-X.Y.Z-N ---depends--- kernel-image | \/ kernel sources The 'magic' part is the problem. I don't follow why there is a problem with linux-kernel-di depending on kernel-tree-X.Y.Z-N. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319175: kernel-image-2.4.27-2-686-smp: after 'apt-get upgrade' the kernel-image-2.4.27-2-686 don't boot anymore
On Tue, Jul 05, 2005 at 03:34:57PM +0200, Marlon Nerling wrote: Package: kernel-image-2.4.27-2-686-smp Severity: important -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Nice Day, I make a normal 'monthly or so' upgrade of a server running sarge. At upgrade from kernel-image-2.4.27-2-686-smp_2.4.27-8_i386 to kernel-image-2.4.27-2-686-smp_2.4.27-10_i386.deb : [EMAIL PROTECTED]:/# apt-get install kernel-image-2.4.27-2-686-smp Reading Package Lists... Done Building Dependency Tree... Done Suggested packages: kernel-doc-2.4.27 kernel-pcmcia-modules-2.4.27-2-686-smp The following packages will be upgraded: kernel-image-2.4.27-2-686-smp 1 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. Need to get 0B/12.7MB of archives. After unpacking 8192B of additional disk space will be used. (Reading database ... 45043 files and directories currently installed.) Preparing to replace kernel-image-2.4.27-2-686-smp 2.4.27-8 (using .../kernel-image-2.4.27-2-686-smp_2.4.27-10_i386.deb) ... The directory /lib/modules/2.4.27-2-686-smp still exists. Continuing as directed. Unpacking replacement kernel-image-2.4.27-2-686-smp ... Setting up kernel-image-2.4.27-2-686-smp (2.4.27-10) ... You are attempting to install a kernel version that is the same as the version you are currently running (version 2.4.27-2-686-smp). The modules list is quite likely to have been changed, and the modules dependency file /lib/modules/2.4.27-2-686-smp/modules.dep needs to be re-built. It can not be built correctly right now, since the module list for the running kernel are likely to be different from the kernel installed. I am creating a new modules.dep file, but that may not be correct. It shall be regenerated correctly at next reboot. I repeat: you have to reboot in order for the modules file to be created correctly. Until you reboot, it may be impossible to load some modules. Reboot as soon as this install is finished (Do not reboot right now, since you may not be able to boot back up until installation is over, but boot immediately after). I can not stress that too much. You need to reboot soon. Please Hit return to continue. depmod: *** Unresolved symbols in /lib/modules/2.4.27-2-686-smp/updates/alsa/snd-pdaudiocf.o depmod: *** Unresolved symbols in /lib/modules/2.4.27-2-686-smp/updates/alsa/snd-vx-cs.o depmod: *** Unresolved symbols in /lib/modules/2.4.27-2-686-smp/updates/alsa/snd-vxp440.o depmod: *** Unresolved symbols in /lib/modules/2.4.27-2-686-smp/updates/alsa/snd-vxpocket.o /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe I think that the problem is the alsa modules you have need to be recompiled against the new kernel. I'm not sure if you got these from a package or compiled them by hand, nor do I have any first-hand experience with 2.4 + alsa, but in any case they seem to be out of date and I think that is the root of your problem. Can you try updating or removing them? failed FATAL: Module DAC960.o not found. FATAL: Module cciss.o not found. FATAL: Module cpqarray.o not found. FATAL: Module floppy.o not found. FATAL: Module loop.o not found. FATAL: Module nbd.o not found. FATAL: Module ps2esdi.o not found. FATAL: Module sx8.o not found. FATAL: Module umem.o not found. FATAL: Module xd.o not found. FATAL: Module ide_detect.o not found. FATAL: Module ide_cd.o not found. FATAL: Module ide_core.o not found. FATAL: Module ide_floppy.o not found. FATAL: Module ide_disk.o not found. FATAL: Module ide_pnp.o not found. FATAL: Module ide_tape.o not found. FATAL: Module pdc202xx_new.o not found. FATAL: Module adma100.o not found. FATAL: Module aec62xx.o not found. FATAL: Module alim15x3.o not found. FATAL: Module amd74xx.o not found. FATAL: Module atiixp.o not found. FATAL: Module cmd640.o not found. FATAL: Module cmd64x.o not found. FATAL: Module cs5530.o not found. FATAL: Module cy82c693.o not found. FATAL: Module generic.o not
Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with = 48mb RAM
On Tue, Jul 26, 2005 at 03:19:25AM +0100, Luke Kenneth Casson Leighton wrote: On Mon, Jul 25, 2005 at 05:52:54PM -0700, Steve Langasek wrote: On Tue, Jul 26, 2005 at 12:45:48AM +0100, Luke Kenneth Casson Leighton wrote: On Mon, Jul 25, 2005 at 03:51:22PM -0700, Matt Taggart wrote: for this P120 (whatever) i have *shudder* had to use a 2.2.10-compact-pci kernel. there exists a kernel-image-2.4.18-bf2.4 (which i might try at some point). Uh, 2.4.18-bf2.4 was built solely for use with the woody installer, and is only available in oldstable. If you're considering using it as the kernel on a newly-installed system, only as a drastic desperation measure, as you can see it is a step up from what the machine is _presently_ running... And why are the 2.4 kernel packages in sarge not a better option? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
PS/2 barcode scanner shows no output, kernel 2.6 (atkbd.c)
Hi. I tried to use a barcode scanner (Labau LS300 PS/2) under Debian 3.1 but it failed. When using Debian's kernel 2.6.8 (2.6.8-2-686-smp) I don't get any useful output of the scanner except of the following messages in /var/log/kern.log. Jul 25 08:13:45 debian kernel: atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed. Jul 25 08:13:46 debian kernel: input: AT Translated Set 2 keyboard on isa0060/serio0 Jul 25 08:14:08 debian kernel: input: AT Translated Set 2 keyboard on isa0060/serio0 Jul 25 08:14:37 debian last message repeated 2 times A compiled Kernel 2.6.12.3 doesn't work either. But after booting Debian's kernel 2.4.27 (2.4.27-2-686-smp) the appropriate scan values are printed to the screen as expected. When scanning barcodes while Linux keylogger (lkl) is running each value is saved successfully in lkl's logfile. If DEBUG_ATKBD is set in /usr/src/linux/drivers/input/keyboard/atkbd.c and I scan a barcode I get some more output in /var/log/kern.log but nothing useful (for me). Jul 25 08:55:30 debian kernel: atkbd.c: Received aa flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received fe flags 03 Jul 25 08:55:30 debian kernel: atkbd.c: Received b8 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 9d flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received e0 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 9d flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 05 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 85 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 02 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 82 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 07 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 87 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 0b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 8b flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 05 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 85 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 07 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 87 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 05 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 85 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 06 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 86 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 1c flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 9c flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received aa flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received b6 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received b8 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received e0 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received b8 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 9d flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received e0 flags 00 Jul 25 08:55:30 debian kernel: atkbd.c: Received 9d flags 00 Seems to be a problem of kernel 2.6 in general because it works with kernel 2.4. Is there a workaround or kernel option to allow the use of ps/2 barcode scanners with kernel 2.6? Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319823: Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with = 48mb RAM
My firewall/mail gateway/shell host for 2-3 people is an old P90 with 40 mb of ram. It works well with Debian and I see no reason to upgrade the hardware. Woody installer worked perfectly back in the days and dist-upgrade to Sarge did too. I bet there are tons of home/small office gateways with this kind of hardware, which may have not seen the Sarge or even Woody installers since 'apt-get dist-upgrade' to a newer release works so well. According to Sarge manuals 32 MB of memory is the minimum http://www.debian.org/releases/stable/i386/ch02s05.html.en so 48 MB should be enough. The default kernel choice is 2.4, so linux26 can have stricter requirements. Those requirements will have to be written down before the next release if 2.4 is dropped, so perhaps someone could know them already. IMO, older installers available from ftp://ftp.debian.org/debian-archive and mirrors can be used for machines with less than currently required amount of RAM memory. (With smaller disk space its a totally different issue, Sarge requires a minimum of 110 MB with normal installer and without hacks.) After installing Woody for example, an 'apt-get dist-upgrade' via network or CDs to Sarge works (ok, some glitches exist but it mostly works). As dist-upgrades are supposed to work only from the previous release, then perhaps a user with 8 MB of RAM could install Slink which requires 4 MB of ram http://www.debian.org/releases/slink/i386/ch-hardware-req.en.html#s2.3 and dist-upgrade with swap enabled via potato and woody to sarge. This of course requires that CPU (i486?), drivers (does ISA bus still work? One old Gravis Ultrasound worked with little tweaking on 2.6.x) and disk space work with all of the releases. (Actually that sounds like an interesting hack for someone and documenting it for Debian installation manual would be great. And I've been around only since late Woody so this might just sound easier than it actually is...) So from my, x86-Debian-user point of view, newer installers don't have to work on the old-but-stil-usable-for-my-needs machines if there is a documented path for running latest Debian stable on it. To me, documentation is sufficient if an 'apt-get dist-upgrade' like upgrade from previous release is supported -- and it is. -Mikko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
#312457 - Enable CONFIG_AUDIT in kernel configuration, it's needed for SELinux
2.6.12 is already out, with CONFIG_AUDIT disabled. Any change to get this enabled soon? Best regards PS. Keep my in CC, not subscribed -- Isaac Clerencia at Warp Networks, http://www.warp.es Work: [EMAIL PROTECTED] | Debian: [EMAIL PROTECTED] pgpa5fDgpAupI.pgp Description: PGP signature
Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with = 48mb RAM
On Tuesday 26 July 2005 02:06, Steve Langasek wrote: I believe Joey Hess is the person who has the best handle on what the actual minimum requirements are for installing sarge. Joey, do you have anything we could add to the sarge release notes for this, if it's not already in there? The drop of subarchs (including real 386) is listed in the Release Notes. The minimum hardware requirements for installing Sarge are listed in the Installation Guide. pgpJnNRvfAt4N.pgp Description: PGP signature
Bug#319457: kernel-image-2.6.8-2-k7: DVD Burning with ide-scsi : oops the kernel, hangs ide-scsi
On Tue, Jul 26, 2005 at 10:44:49AM +0200, A Mennucc wrote: (I am sending this to cdrecord / dvdrecord / gcombust mantainers as well: please read below) On Mon, Jul 25, 2005 at 06:30:25PM +0900, Horms wrote: tag 319457 +wontfix thanks On Fri, Jul 22, 2005 at 10:38:47AM +0200, A Mennucc wrote: Package: kernel-image-2.6.8-2-k7 Version: 2.6.8-16 Severity: important I just bought a DVD Burner; I wanted to burn stuff, so I loaded ide-scsi (since this was the way to go some years ago - I did not know that now is deprecated) ; the command $ dvdrecord dev=1,0,0 -v -dummy -dao debian-31r0a-i386-binary-1.iso segfaulted, and its fork started printing: dvdrecord: No such device or address. Cannot send SCSI cmd via ioctl Moreover the kernel oopsed (NULL pointer dereference) and then the module ide-scsi seems dead (cannot remove it, does not respond); see dmesg in attachment Don't use ide-scsi, ever! two options: 1) If idescsi should never be used, then idescsi should not be built into the kernel (by setting BLK_DEV_IDESCSI to no) Yes, I agree entirely. However, I was asked to leave it in so as not to break anything that happens to work using it. So its there for 2.6.8. 2) If idescsi is shipped, then it should not ever oops by NULL point dereferencing. Your tag 'wontfix' is nonsense: any option of the above that you choose, you find a a bug in the current kernel that must be fixed in future revisions. I disagree. I think there is some value in leaving this driver in as it does work for some people. Think of it as a transition process. In any case, its there for sarge, so its too late. I certainly would like to see it disabled for the Etch kernel. Can dvdrecord use ide devices directly? When starting cdrecord using ATAPI interface it prints Warning: Using ATA Packet interface. Warning: The related Linux kernel interface code seems to be unmaintained. Warning: There is absolutely NO DMA, operations thus are slow. This seems to suggest that idescsi should be used instead. Currently /usr/share/doc/cdrecord/README.ATAPI.setup says Usually you would not want to use ide-scsi with kernel 2.6 It does not say : Do not ever use it Moreover gcombust does not support ATAPI in its interface Any tool that uses it should have a bug filed against it. If so please do that. I'm marking this as wontfix and leaving it open so it can act as a reference for others. I think that kernel people and the mantainer of cdrecord/dvdrecord should reach an agreement on this issue. (Translation: I am just a poor user, please sort this out between mantainers). Yes, I agree. If idescsi should not be used, then the documents of cdrecord/dvdrecord should be adjusted. Moreover gcombust needs some refurbishment to be able to use ATAPI. Yes, I agree. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with = 48mb RAM
On Tue, Jul 26, 2005 at 12:45:48AM +0100, Luke Kenneth Casson Leighton wrote: On Mon, Jul 25, 2005 at 03:51:22PM -0700, Matt Taggart wrote: It would probably be a good idea to record what ought to work in any given release and maybe have an ongoing idea what it should be. The answer might be architecture specific? ISTR either the d-i team or apt/dpkg/aptitude trying to get sarge systems with 32mb working towards the end of the release. if you really want to try that out, without messing with older hardware, try usin XEN. No need to mess with older hardware *or* Xen. Use the mem=32M (etc.) kernel parameter. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 upload
Horms [EMAIL PROTECTED] writes: On Thu, Jul 21, 2005 at 11:04:07AM +0200, Goswin von Brederlow wrote: The DI kernel udebs (linux-kernel-di-arch source) takes the kernel-image deb, splits it up into kernel and several groups of modules and builds udebs. There is no Depends there and can't be to keep the kernel-image debs available. kernel-image-di-arch ---source--- linux-kernel-di | magic | \/ kernel-tree-X.Y.Z-N ---depends--- kernel-image | \/ kernel sources The 'magic' part is the problem. I don't follow why there is a problem with linux-kernel-di depending on kernel-tree-X.Y.Z-N. -- Horms The problem is that the DAK will update linux-2.6, kernel-tree-x.y.z-n and kernel-image packages without any regards to linux-kernel-di. They will become out of sync and end up without source - GPL violation. In the old setup kernel-source-2.6.8 will remain until removed manualy and linux-kernel-di has that as source. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 upload
On Tue, Jul 26, 2005 at 03:26:04PM +0200, Goswin von Brederlow wrote: Horms [EMAIL PROTECTED] writes: On Thu, Jul 21, 2005 at 11:04:07AM +0200, Goswin von Brederlow wrote: The DI kernel udebs (linux-kernel-di-arch source) takes the kernel-image deb, splits it up into kernel and several groups of modules and builds udebs. There is no Depends there and can't be to keep the kernel-image debs available. kernel-image-di-arch ---source--- linux-kernel-di | magic | \/ kernel-tree-X.Y.Z-N ---depends--- kernel-image | \/ kernel sources The 'magic' part is the problem. I don't follow why there is a problem with linux-kernel-di depending on kernel-tree-X.Y.Z-N. -- Horms The problem is that the DAK will update linux-2.6, kernel-tree-x.y.z-n and kernel-image packages without any regards to linux-kernel-di. They will become out of sync and end up without source - GPL violation. In the old setup kernel-source-2.6.8 will remain until removed manualy and linux-kernel-di has that as source. But kernel-source-x.y.z.N provides kernel-tree-x.y.z-n for 1 = n = N Surely this resolves the problem some people percieve with regards to the GPL. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 upload
On Tue, Jul 26, 2005 at 03:26:04PM +0200, Goswin von Brederlow wrote: Horms [EMAIL PROTECTED] writes: On Thu, Jul 21, 2005 at 11:04:07AM +0200, Goswin von Brederlow wrote: The DI kernel udebs (linux-kernel-di-arch source) takes the kernel-image deb, splits it up into kernel and several groups of modules and builds udebs. There is no Depends there and can't be to keep the kernel-image debs available. kernel-image-di-arch ---source--- linux-kernel-di | magic | \/ kernel-tree-X.Y.Z-N ---depends--- kernel-image | \/ kernel sources The 'magic' part is the problem. I don't follow why there is a problem with linux-kernel-di depending on kernel-tree-X.Y.Z-N. -- Horms The problem is that the DAK will update linux-2.6, kernel-tree-x.y.z-n and kernel-image packages without any regards to linux-kernel-di. They will become out of sync and end up without source - GPL violation. In the old setup kernel-source-2.6.8 will remain until removed manualy and linux-kernel-di has that as source. I'd like to see the magic moved into the kernel packaging. Right now the magic is performed using the kernel-wedge package and config files from http://svn.debian.org/wsvn/d-i/trunk/packages/kernel/?rev=0sc=0. Really it's just creating udebs with the kernel and specific modules. -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: 2.6.12 upload
Horms [EMAIL PROTECTED] writes: On Tue, Jul 26, 2005 at 03:26:04PM +0200, Goswin von Brederlow wrote: Horms [EMAIL PROTECTED] writes: On Thu, Jul 21, 2005 at 11:04:07AM +0200, Goswin von Brederlow wrote: The DI kernel udebs (linux-kernel-di-arch source) takes the kernel-image deb, splits it up into kernel and several groups of modules and builds udebs. There is no Depends there and can't be to keep the kernel-image debs available. kernel-image-di-arch ---source--- linux-kernel-di | magic | \/ kernel-tree-X.Y.Z-N ---depends--- kernel-image | \/ kernel sources The 'magic' part is the problem. I don't follow why there is a problem with linux-kernel-di depending on kernel-tree-X.Y.Z-N. -- Horms The problem is that the DAK will update linux-2.6, kernel-tree-x.y.z-n and kernel-image packages without any regards to linux-kernel-di. They will become out of sync and end up without source - GPL violation. In the old setup kernel-source-2.6.8 will remain until removed manualy and linux-kernel-di has that as source. But kernel-source-x.y.z.N provides kernel-tree-x.y.z-n for 1 = n = N Surely this resolves the problem some people percieve with regards to the GPL. No. Since linux-2.6 source means kernel-tree-x.y.(z+1)-1 will replace kernel-tree-x.y.z-n now. You would have to provide 1 = z = Z, 1 = n = N for it to still work. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320042: conflicting files with kernel-doc-2.6.11
Package: linux-doc-2.6.12 Version: 2.6.12-1 Severity: important dpkg reports that /usr/share/man/man9/wanbook.9 is also in kernel-doc-2.6.11 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 upload
On Tue, Jul 26, 2005 at 06:24:43PM +0200, Goswin von Brederlow wrote: Stephen R Marenka [EMAIL PROTECTED] writes: Really it's just creating udebs with the kernel and specific modules. That would solve a lot of problems, including the GPL one. The debs and udebs would update at the same time each time. On the other hand it would mean D-I has to change the version more often but that should grep the Packages file to find the current version for daily builds imho. daily builds aren't that big of a deal. If one fails because of a kernel change, you update the config and build it manually or the next day. This is already what happens with a change in the build-deps (at least, if you're not watching closely enough). -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: 2.6.12 upload
Stephen R Marenka [EMAIL PROTECTED] writes: On Tue, Jul 26, 2005 at 06:24:43PM +0200, Goswin von Brederlow wrote: Stephen R Marenka [EMAIL PROTECTED] writes: Really it's just creating udebs with the kernel and specific modules. That would solve a lot of problems, including the GPL one. The debs and udebs would update at the same time each time. On the other hand it would mean D-I has to change the version more often but that should grep the Packages file to find the current version for daily builds imho. daily builds aren't that big of a deal. If one fails because of a kernel change, you update the config and build it manually or the next day. This is already what happens with a change in the build-deps (at least, if you're not watching closely enough). But why bother? Just add KERNEL_VERSION=$(grep-dctrl -P linux-kernel-di-$(ARCH) -n -s Version Packages) and let it figure it out automatically. :) Or something to the same effect. Mfg Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309961: irq 18: nobody cared!
as this seems the same machine concerned by another bug. did you try newer 2.6.12 from unstable? are you overclocking? try to boot with the noacpi or noapic kernel parameter. thanks for your feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307909: kernel-image-2.6.11-1-686: cpufreq broken for Pentium M
tags 307909 moreinfo stop any update on the matter? can you try latest 2.6.12 from unstable. in case it doesn't cure please post it's dmesg as well the dmesg of the working 2.6.8. thanks for you feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308941: kernel-image-2.6.11-1-k7: cpio error installing package
tags 308941 moreinfo stop any progress on that matter? your box seems badly broken. please send the ouput of those commands: dpkg -l cpio cpio --version ls -l /lib/ld-linux.so.2 -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#304095: kernel-image-2.6.11: Getting loads of ERROR Removing module 'xxxxx' at the end of kernel loading
tags 304095 moreinfo reassign 304095 initrd-tools stop which version of initrd-tools are you using? anyway the replacement - initramfs-tools- is in preparation. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312973: kernel-image-2.6.11-1-686: system clock drifts ahead of hardware clock
can you please test the 2.6.12 linux image in unstable? does the bug still occurs? -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312320: kernel-image-2.6.11-1-k7: Firewire hard freeze on moderate load
did you try if an upgrade to latest 2.6.12 from unstable helps? thanks for your feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#304095: kernel-image-2.6.11: Getting loads of ERROR Removing module 'xxxxx' at the end of kernel loading
Maximilian Attems wrote: tags 304095 moreinfo reassign 304095 initrd-tools stop which version of initrd-tools are you using? anyway the replacement - initramfs-tools- is in preparation. Don't get this anymore :-). Was solved in one of the upgrades. I thought this bug was already closed. Jaap -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303550: kernel-image-2.6.11-1-686: irq11 makes eth0 problems
please try out latest 2.6.12 image from unstable and report back how it works? thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: kernel-image-2.6.11: Getting loads of ERROR Removing module 'xxxxx' at the end of kernel loading
Processing commands for [EMAIL PROTECTED]: tags 304095 moreinfo Bug#304095: kernel-image-2.6.11: Getting loads of ERROR Removing module 'x' at the end of kernel loading There were no tags set. Tags added: moreinfo reassign 304095 initrd-tools Bug#304095: kernel-image-2.6.11: Getting loads of ERROR Removing module 'x' at the end of kernel loading Bug reassigned from package `kernel-image-2.6.11-1-686' to `initrd-tools'. 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]
Processed: Re: kerlnel-image-2.6.11-1-686: psmouse.c: Explorer mouse lost synchronization
Processing commands for [EMAIL PROTECTED]: reassign 305025 gpm Bug#305025: kerlnel-image-2.6.11-1-686: psmouse.c: Explorer mouse lost synchronization Bug reassigned from package `kernel-image-2.6.11-1-686' to `gpm'. 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: Re: kernel-image-2.6.11-1-686: ALSA mixer controls not working
Processing commands for [EMAIL PROTECTED]: reassign 305187 alsa-base Bug#305187: kernel-image-2.6.11-1-686: ALSA mixer controls not working Bug reassigned from package `kernel-image-2.6.11-1-686' to `alsa-base'. 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]
Processed: Re: kernel-image-2.6.11-1-k7: cpio error installing package
Processing commands for [EMAIL PROTECTED]: tags 308941 moreinfo Bug#308941: kernel-image-2.6.11-1-k7: cpio error installing package There were no tags set. Tags added: moreinfo 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]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: tags 310931 moreinfo Bug#310931: kacpid hogs CPU on HP/Compaq nx6110 There were no tags set. Tags added: moreinfo 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]
Processed: Re: kernel-image-2.6.11-1-686: Extra ide probes hang some systems
Processing commands for [EMAIL PROTECTED]: tags 316591 moreinfo Bug#316591: kernel-image-2.6.11-1-686: Extra ide probes hang some systems There were no tags set. Tags added: moreinfo 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]
Processed: Re: kernel-image-2.6.11-1-686: cpufreq broken for Pentium M
Processing commands for [EMAIL PROTECTED]: tags 307909 moreinfo Bug#307909: kernel-image-2.6.11-1-686: cpufreq broken for Pentium M There were no tags set. Tags added: moreinfo 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]
Processed: Re: kernel-image 2.6.11-5 not detecting Zaurus 5500
Processing commands for [EMAIL PROTECTED]: tags 311222 moreinfo Bug#311222: kernel-image 2.6.11-5 not detecting Zaurus 5500 There were no tags set. Tags added: moreinfo 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#308934: marked as done ([kernel package] Missing ethernet module)
Your message dated Tue, 26 Jul 2005 17:50:31 +0200 with message-id [EMAIL PROTECTED] and subject line [kernel package] Missing ethernet module 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 maintonly) by bugs.debian.org; 13 May 2005 11:13:59 + From [EMAIL PROTECTED] Fri May 13 04:13:59 2005 Return-path: [EMAIL PROTECTED] Received: from wproxy.gmail.com [64.233.184.200] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DWY7D-0007SQ-00; Fri, 13 May 2005 04:13:59 -0700 Received: by wproxy.gmail.com with SMTP id 71so230656wra for [EMAIL PROTECTED]; Fri, 13 May 2005 04:13:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Afz6si8cZEdWx+qbfUgkh3XYEV/QHLSceiDEcySPRWU1Ws/PT6jmZ0oUWuSlFrkM6Z+LpxL0dFbddD12ZVErCjuLFdh8bBjjsxpBV4HVh9VTqZkpl6ABGblSlbzRJA9+OdfjQDQDNlcIPoEAOX8pNwilweGNPes/W6BroRcjOI0= Received: by 10.54.24.48 with SMTP id 48mr1747935wrx; Fri, 13 May 2005 04:13:58 -0700 (PDT) Received: by 10.54.50.28 with HTTP; Fri, 13 May 2005 04:13:58 -0700 (PDT) Message-ID: [EMAIL PROTECTED] Date: Fri, 13 May 2005 13:13:58 +0200 From: =?ISO-8859-1?Q?R=E9my_Saissy?= [EMAIL PROTECTED] Reply-To: =?ISO-8859-1?Q?R=E9my_Saissy?= [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [kernel package] Missing ethernet module Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.11-1-686-smp Version: 2.6.11-3 the tg3 module (Broadcom Tigon3 ethernet driver) isn't compiled into this package. Have a nice day --=20 R=E9my Saissy --- Received: (at 308934-done) by bugs.debian.org; 26 Jul 2005 15:51:08 + From [EMAIL PROTECTED] Tue Jul 26 08:51:08 2005 Return-path: [EMAIL PROTECTED] Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1DxRi0-0007ZD-00; Tue, 26 Jul 2005 08:51:08 -0700 Received: by baikonur.stro.at (Postfix, from userid 1001) id AB5775C013; Tue, 26 Jul 2005 17:50:31 +0200 (CEST) Date: Tue, 26 Jul 2005 17:50:31 +0200 From: Maximilian Attems [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [kernel package] Missing ethernet module Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by Amavis (ClamAV) at stro.at 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 please upgrade to latest 2.6.12 from unstable. the firmware got relicensed and thus tigon is reincluded. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#303970: marked as done (kernel-image-2.6.11-1-386: in /lib/modules, source - /home/dilinger/src/kernel/kernel-image/2.6.11-2/kernel-image-2.6.11-i386-2.6.11/install-386)
Your message dated Tue, 26 Jul 2005 17:33:08 +0200 with message-id [EMAIL PROTECTED] and subject line kernel-image-2.6.11-1-386: in /lib/modules, source - /home/dilinger/src/kernel/kernel-image/2.6.11-2/kernel-image-2.6.11-i386-2.6.11/install-386 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; 10 Apr 2005 01:41:00 + From [EMAIL PROTECTED] Sat Apr 09 18:41:00 2005 Return-path: [EMAIL PROTECTED] Received: from smtp1.adl2.internode.on.net [203.16.214.181] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DKRRc-0002JV-00; Sat, 09 Apr 2005 18:41:00 -0700 Received: from localhost (ppp751.adelaide.on.net.au [150.101.76.238]) by smtp1.adl2.internode.on.net (8.12.9/8.12.9) with ESMTP id j3A1euO6064403; Sun, 10 Apr 2005 11:10:58 +0930 (CST) Received: from amarsh04 by localhost with local (Exim 4.50) id 1DKRRW-0006AA-KV; Sun, 10 Apr 2005 11:10:54 +0930 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Arthur Marsh [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: kernel-image-2.6.11-1-386: in /lib/modules, source - /home/dilinger/src/kernel/kernel-image/2.6.11-2/kernel-image-2.6.11-i386-2.6.11/install-386 X-Mailer: reportbug 3.9 Date: Sun, 10 Apr 2005 11:10:53 +0930 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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.11-1-386 Version: 2.6.11-2 Severity: normal /lib/modules/2.6.11-1-386 as installed has the following symbolic link: source - /home/dilinger/src/kernel/kernel-image/2.6.11-2/kernel-image-2.6.11-i386-2.6.11/install-386 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.11-1-386 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages kernel-image-2.6.11-1-386 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.77 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information --- Received: (at 303970-done) by bugs.debian.org; 26 Jul 2005 15:34:04 + From [EMAIL PROTECTED] Tue Jul 26 08:34:04 2005 Return-path: [EMAIL PROTECTED] Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1DxRRU-0008JB-00; Tue, 26 Jul 2005 08:34:04 -0700 Received: by baikonur.stro.at (Postfix, from userid 1001) id 206C05C014; Tue, 26 Jul 2005 17:33:08 +0200 (CEST) Date: Tue, 26 Jul 2005 17:33:08 +0200 From: Maximilian Attems [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: kernel-image-2.6.11-1-386: in /lib/modules, source - /home/dilinger/src/kernel/kernel-image/2.6.11-2/kernel-image-2.6.11-i386-2.6.11/install-386 Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by Amavis (ClamAV) at stro.at 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 the linux-image 2.6.12 is no differently build. reopen and reassign if they are still lying around there. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317096: marked as done (kernel-image-2.6-em64t-p4-smp: kernel panic on xseries 346)
Your message dated Tue, 26 Jul 2005 17:18:55 +0200 with message-id [EMAIL PROTECTED] and subject line kernel panic 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; 6 Jul 2005 09:14:14 + From [EMAIL PROTECTED] Wed Jul 06 02:14:14 2005 Return-path: [EMAIL PROTECTED] Received: from (localhost.localdomain) [212.239.116.31] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Dq5yw-0005fh-00; Wed, 06 Jul 2005 02:14:14 -0700 Received: by localhost.localdomain (Postfix, from userid 1000) id 7FC345F2; Wed, 6 Jul 2005 11:13:41 +0200 (CEST) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Simone Piccardi [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: kernel-image-2.6-em64t-p4-smp: kernel panic on xseries 346 X-Mailer: reportbug 3.8 Date: Wed, 06 Jul 2005 11:13:41 +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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6-em64t-p4-smp Version: 103 Severity: important Using this kernel I got a kernel panic, the last lines are: pivot_root: No such file or directory /sbin/init: 432: cannot open dev/console: No such file Kernel panic: Attempted to kill init! It seems that the serveraid is not recognised. Using the normal 2.6.8-2-686-smp is working fine. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.6-em64t-p4-smp depends on: ii kernel-image-2.6.8-11-em64t-p 2.6.8-14 Linux kernel image for version 2.6 -- no debconf information --- Received: (at 317096-done) by bugs.debian.org; 26 Jul 2005 15:19:36 + From [EMAIL PROTECTED] Tue Jul 26 08:19:36 2005 Return-path: [EMAIL PROTECTED] Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1DxRDU-0001rW-00; Tue, 26 Jul 2005 08:19:36 -0700 Received: by baikonur.stro.at (Postfix, from userid 1001) id 4DF235C010; Tue, 26 Jul 2005 17:18:55 +0200 (CEST) Date: Tue, 26 Jul 2005 17:18:55 +0200 From: Maximilian Attems [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: kernel panic Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by Amavis (ClamAV) at stro.at 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 you didn't respond to the followups. the message you posted is from a missing initrd not passed to the bootloader. i guess you have cured your system since. please reopen if pain subsist. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320053: kernel-image-2.6.8-2-686: Installing it with sarge leads to failing at booting next time
Package: kernel-image-2.6.8-2-686 Severity: critical Justification: breaks the whole system I was installing Sarge on to my new notebook (Acer Extensa 4102 WLMI) with linux26 (so it installs the 2.6.8-2 kernel). Everything goes ok till the next reboot in which Sarge would ask me further questions about the system. After i choose the Sarge install in grub the kernel stops after some time with : modprobe: FATAL: Error inserting pciehp (/lib/modules/2.6.8-2-686/kernel/drivers/pci/hotplug/shpchp.ko): Operation not permitted shpchp: can't be loaded [...] hw_random: can't be loaded [...] Unable to handle kernel NULL pointer dereference at virtual adress 0024 [...] i810_audio: can't be loaded [...] So tried with bootoption pnpbios=off pci=nosort acpi=off apm=off but nothing works.. plz help me with my problem and thx for the great work stefan -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320050: kernel-image-2.6.8-2-686: Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller not working
Package: kernel-image-2.6.8-2-686 Version: 2.6.8-16 Severity: normal Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller is not working. dmesg output after modpobe: ACPI: PCI interrupt :00:14.5[B] - GSI 17 (level, low) - IRQ 193 ATI IXP AC97 controller: probe of :00:14.5 failed with error -13 output of cat /proc/asound/devices: 33: : timer output of alsamixer: alsamixer: function snd_ctl_open failed for default: No such device Thanks Vania -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.6.8-2-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81.1 tools to create initrd image for pii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information
Bug#312973: kernel-image-2.6.11-1-686: system clock drifts ahead of hardware clock
On Tue, 2005-26-07 at 17:27 +0200, Maximilian Attems wrote: can you please test the 2.6.12 linux image in unstable? does the bug still occurs? I never saw it ... I just explained to Chris what AC97 meant. However, I will try the 2.6.12 kernel ... my system has been crashing badly this week. I suspect the radeon driver more than sound now ... -- maks -- --gh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#320033: kernel panic when using ebtables and arp.
Processing commands for [EMAIL PROTECTED]: reassign 320033 kernel Bug#320033: kernel panic when using ebtables and arp. Warning: Unknown package 'kernel-image' Bug reassigned from package `kernel-image' to `kernel'. -- 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: Re: your mail
Processing commands for [EMAIL PROTECTED]: retitle 310931 overheating cpu due to !acpid Bug#310931: kacpid hogs CPU on HP/Compaq nx6110 Changed Bug title. tags 310931 -moreinfo Bug#310931: overheating cpu due to !acpid Tags were: moreinfo Tags removed: moreinfo tags 310931 d-i Bug#310931: overheating cpu due to !acpid There were no tags set. Tags added: d-i severity 310931 wishlist Bug#310931: overheating cpu due to !acpid Severity set to `wishlist'. reassign 310931 tasksel Bug#310931: overheating cpu due to !acpid Bug reassigned from package `kernel-image-2.6.11-1-686' to `tasksel'. 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#304095: marked as done (kernel-image-2.6.11: Getting loads of ERROR Removing module 'xxxxx' at the end of kernel loading)
Your message dated Tue, 26 Jul 2005 21:44:21 +0200 with message-id [EMAIL PROTECTED] and subject line kernel-image-2.6.11: Getting loads of ERROR Removing module 'x' at the end of kernel loading 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; 10 Apr 2005 20:57:28 + From [EMAIL PROTECTED] Sun Apr 10 13:57:28 2005 Return-path: [EMAIL PROTECTED] Received: from smtp1.versatel.nl [62.58.50.88] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1DKjUm-00070I-00; Sun, 10 Apr 2005 13:57:28 -0700 Received: (qmail 27873 invoked by uid 10); 10 Apr 2005 20:56:56 - Message-ID: [EMAIL PROTECTED] Received: (vexira-qq 27855-36850918 invoked from network) 10 Apr 2005 22:56:56 +0200 Received: from unknown (HELO localhost.localdomain) ([81.59.142.150]) (envelope-sender [EMAIL PROTECTED]) by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP for ; 10 Apr 2005 20:56:56 - Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Jaap Haitsma [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: kernel-image-2.6.11: Getting loads of ERROR Removing module 'x' at the end of kernel loading X-Mailer: reportbug 3.9 Date: Sun, 10 Apr 2005 22:56:51 +0200 X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.30.0.2; VDF: 6.30.0.11; host: postbode01.zonnet.nl) 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,HAS_PACKAGE, MSGID_FROM_MTA_HEADER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-image-2.6.11-1-686 Version: 2.6.11-2 Severity: normal File: kernel-image-2.6.11 I get around 10 messages which say something like ERROR Removing module 'x' where is a name of some module just before init starts -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kernel-image-2.6.11-1-686 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.77 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information --- Received: (at 304095-done) by bugs.debian.org; 26 Jul 2005 19:44:21 + From [EMAIL PROTECTED] Tue Jul 26 12:44:21 2005 Return-path: [EMAIL PROTECTED] Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1DxVLg-0004AU-00; Tue, 26 Jul 2005 12:44:21 -0700 Received: from sputnik (stallburg.stro.at [128.131.216.190]) by baikonur.stro.at (Postfix) with ESMTP id A493C5C00F for [EMAIL PROTECTED]; Tue, 26 Jul 2005 21:44:08 +0200 (CEST) Received: from max by sputnik with local (Exim 4.52) id 1DxVLh-00022u-V3 for [EMAIL PROTECTED]; Tue, 26 Jul 2005 21:44:21 +0200 Date: Tue, 26 Jul 2005 21:44:21 +0200 From: maximilian attems [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: kernel-image-2.6.11: Getting loads of ERROR Removing module 'x' at the end of kernel loading Message-ID: [EMAIL PROTECTED] References: [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 X-Virus-Scanned: by Amavis (ClamAV) at stro.at 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 On Tue, 26 Jul 2005, Jaap Haitsma wrote: Maximilian Attems wrote: anyway the replacement - initramfs-tools- is in preparation. Don't get this anymore :-). Was solved in one of the upgrades. I thought this bug was already closed. Jaap ok thanks for the feedback. closing it. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?
Bug#310931: your mail
retitle 310931 overheating cpu due to !acpid tags 310931 -moreinfo tags 310931 d-i severity 310931 wishlist reassign 310931 tasksel thanks On Tue, 26 Jul 2005, Marcin Owsiany wrote: On Tue, Jul 26, 2005 at 05:57:17PM +0200, Maximilian Attems wrote: tags 310931 moreinfo stop any progress on the matter? can you reproduce it with the 2.6.12 linux image from unstable? First of all, the reported situation happened only before I installed acpid package. After that, during regular operation in runlevel 2, when userspace acpid is running, there are no more kacpid CPU hogs. I also got the impression that the CPU fan switches to higher RPM on high CPU utilization only when acpid is running. It might be that in runlevel 1 (i.e. when the user-space acpid is not running), the CPU was constantly overheated, and that in turn caused the kacpid CPU hog. hmm so the bug report isn't exactly against a kernel-image. i'm not sure debian is already preventing the unexerienced user from overheating it's cpu. for now i'll reassign to tasksel so the bug gets on the radar of the debian-installer team. maybe we already install acpid for desktop systems, but maybe that should be paired with some hardware detection of d-i (apm or acpi too old) cc the debian-installer list for feedback. I installed the 2.6.12 package the day before yesterday, so I will try to test this some more in runlevel 1 today, if you want. no thanks i believe you. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 upload
On Tuesday 26 July 2005 20:00, Stephen R Marenka wrote: daily builds aren't that big of a deal. If one fails because of a kernel change, you update the config and build it manually or the next day. This is already what happens with a change in the build-deps (at least, if you're not watching closely enough). Right. The main concern is breaking the latest Beta or RC release by kernel changes. Daily builds are, almost by definition, not a problem. pgpQAxu965JER.pgp Description: PGP signature
Processed: Re: your mail
Processing commands for [EMAIL PROTECTED]: reassign 310931 initrd-tools Bug#310931: overheating cpu due to !acpid Bug reassigned from package `tasksel' to `initrd-tools'. tags 310931 -d-i Bug#310931: overheating cpu due to !acpid Tags were: d-i Tags removed: d-i clone 310931 -1 Bug#310931: overheating cpu due to !acpid Bug 310931 cloned as bug 320094. reassign -1 acpid Bug#320094: overheating cpu due to !acpid Bug reassigned from package `initrd-tools' to `acpid'. 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#320091: kernel-image-2.6.8-2-386: Boot fails with a syntax error in /scripts/ext3-add-journal.sh
Package: kernel-image-2.6.8-2-386 Version: 2.6.8-16 Severity: important I am currently running kernel-image-2.6.8-1-386 on this up-to-date Debian Sarge system. That kernel seems to run fine. I attempted to upgrade to kernel-image-2.6.8-2-386, but it fails to boot and does not appear to even get as far as mounting /. These seem like the relevant messages: /scripts/ext3-add-journal.sh: 27: arith: syntax error: 0x /sbin/init: 426: arith: syntax error: 0x Kernel panic: Attempted to kill init! but I don't know what scrolled out of sight first. Obviously I had to copy them down by hand. Not finding it on the system, I mounted the initrd files and found a script named ext3-add-journal.sh, which I presume is the problem. They are clearly different between the two kernel versions but the syntax error doesn't make any obvious sense just from an inspection of the script. Any help or pointers for further investigation would be appreciated. Dustin -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages kernel-image-2.6.8-2-386 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320053: kernel-image-2.6.8-2-686: Installing it with sarge leads to failing at booting next time
On Tuesday 26 July 2005 19:27, Stefan Esterer wrote: After i choose the Sarge install in grub the kernel stops after some time with : modprobe: FATAL: Error inserting pciehp (/lib/modules/2.6.8-2-686/kernel/drivers/pci/hotplug/shpchp.ko): Operation not permitted shpchp: can't be loaded [...] hw_random: can't be loaded [...] Everything up to here is normal. These modules are not supported by your hardware but do no harm. Just blacklist them for both discover and hotplug and you will be fine. Unable to handle kernel NULL pointer dereference at virtual adress 0024 [...] i810_audio: can't be loaded [...] This one looks very much like a problem I've seen in several installation reports. [1] gives the best summary and status of the problem and has a workaround. Could you check that's the same issue? Basic problem: we really need someone who has the hardware and is willing to test solutions. Could you do that? The first step would be: check if the problem still occur with the 2.6.12 kernel. The second step would be: get in touch with the ALSA people and try to get the problem solved (maybe testing with latest drivers from CVS first). [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298623 Cheers, FJP (P.S. Please give a little bit more of the console output next time; it was just chance that I recognized the issue from the two relevant lines.) pgppWCKbDfrkI.pgp Description: PGP signature
Bug#310931: your mail
On Wednesday 27 July 2005 00:42, Marcin Owsiany wrote: acpid is already installed on all systems with acpi (and 2.6 kernels) by hw-detect. I wonder why it didn't get installed with sarge on my laptop.. Is it installed in expert mode as well? acpi and acpid are scheduled for installation during hw-detect if directory /proc/acpi is present in the installer. This was implemented _after_ the sarge release, so only happens if a daily installer image is used. It happens for any installation method. The syslog should show a message Detected acpi support, installing acpi/acpid.. As /proc/acpi is only present with 2.6 kernels, acpi and acpid are not automatically installed by d-i for installations using a 2.4 kernel. The 'apt-install' script is used in d-i to either directly install a package (if the base system is already setup) or schedule a package for later installation (before that time). In any case, acpid will only be run _after_ the system is rebooted. See hw-detect in svn (or during installation) for the actual code. pgp5VoO2TsEwX.pgp Description: PGP signature
Bug#310931: overheating cpu due to !acpid
On Tue, Jul 26, 2005 at 11:13:47PM +0200, maximilian attems wrote: On Tue, 26 Jul 2005, Marcin Owsiany wrote: Either way, I don't think having acpid installed is enough, as long it starts so late in bootup process. A long fsck run or a similar problem before entering runlevel 2, and the problem appears again :-/ I don't know much about ACPI specification, but maybe it would be possible to make the fans run at maximum speed when kernel boots, until acpid starts (which would then turn them down according to whatever its user-space policy says). well infact acpid can be started pretty early remembered to have seen a fix that propagated even to the initrd-tools in ubuntu for that. Ubuntu loads acpid at the normal time; what we do is load some acpi-related kernel modules from the initrd. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319754: marked as done (kernel-source-2.6.11: missing header files + syntax errors)
Your message dated Tue, 26 Jul 2005 21:34:37 -0400 (EDT) with message-id [EMAIL PROTECTED] and subject line Closing - no bug 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 Jul 2005 15:26:48 + From [EMAIL PROTECTED] Sun Jul 24 08:26:48 2005 Return-path: [EMAIL PROTECTED] Received: from mail.isac.cnr.it [192.167.167.252] (postfix) by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1DwiNL-00055i-00; Sun, 24 Jul 2005 08:26:47 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.isac.cnr.it (Postfix) with ESMTP id C9B48135; Sun, 24 Jul 2005 17:26:42 +0200 (CEST) Received: from mail.isac.cnr.it ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22824-01; Sun, 24 Jul 2005 17:26:38 +0200 (CEST) Received: from arjuna (remote1.bo.isac.cnr.it [192.167.167.186]) by mail.isac.cnr.it (Postfix) with ESMTP id 04F1B133; Sun, 24 Jul 2005 17:26:36 +0200 (CEST) Received: from root by arjuna with local (Exim 3.36 #1 (Debian)) id 1DwiOe-0003k2-00; Sun, 24 Jul 2005 17:28:08 +0200 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: augh62 [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: kernel-source-2.6.11: missing header files + syntax errors X-Mailer: reportbug 3.15 Date: Sun, 24 Jul 2005 17:28:00 +0200 Message-Id: [EMAIL PROTECTED] X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at isac.cnr.it 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: kernel-source-2.6.11 Version: 2.6.11-7 Severity: grave Justification: renders package unusable Here is the output of make menuconfig HOSTCC scripts/basic/fixdep scripts/basic/fixdep.c:105:23: error: sys/types.h: No such file or directory scripts/basic/fixdep.c:106:22: error: sys/stat.h: No such file or directory scripts/basic/fixdep.c:107:22: error: sys/mman.h: No such file or directory In file included from /usr/include/unistd.h:26, from scripts/basic/fixdep.c:108: /usr/include/features.h:295:25: error: sys/cdefs.h: No such file or directory In file included from /usr/include/bits/types.h:31, from /usr/include/unistd.h:186, from scripts/basic/fixdep.c:108: /usr/lib/gcc/i486-linux-gnu/4.0.1/include/stddef.h:214: error: syntax error before 'typedef' In file included from scripts/basic/fixdep.c:108: /usr/include/unistd.h:256: error: syntax error before '__THROW' /usr/include/unistd.h:286: error: syntax error before '__THROW' /usr/include/unistd.h:369: error: syntax error before '__THROW' /usr/include/unistd.h:378: error: syntax error before '__THROW' /usr/include/unistd.h:398: error: syntax error before '__THROW' /usr/include/unistd.h:419: error: syntax error before '__THROW' /usr/include/unistd.h:423: error: syntax error before '__THROW' /usr/include/unistd.h:429: error: syntax error before '__THROW' /usr/include/unistd.h:434: error: syntax error before '__THROW' /usr/include/unistd.h:438: error: syntax error before '__THROW' /usr/include/unistd.h:448: error: syntax error before '__THROW' /usr/include/unistd.h:461: error: syntax error before '__THROW' /usr/include/unistd.h:466: error: syntax error before '__THROW' /usr/include/unistd.h:469: error: syntax error before '__THROW' /usr/include/unistd.h:481: error: syntax error before '__THROW' /usr/include/unistd.h:492: error: syntax error before '__THROW' /usr/include/unistd.h:496: error: syntax error before '__THROW' /usr/include/unistd.h:500: error: syntax error before '__THROW' /usr/include/unistd.h:504: error: syntax error before '__THROW' /usr/include/unistd.h:509: error: syntax error before '__THROW' /usr/include/unistd.h:514: error: syntax error before '__THROW' In file included from scripts/basic/fixdep.c:108: /usr/include/unistd.h:528: error: syntax error before '__THROW' /usr/include/unistd.h:531: error: syntax error before '__THROW' /usr/include/unistd.h:534: error: syntax error before '__THROW' /usr/include/unistd.h:538: error: syntax error before '__THROW' /usr/include/unistd.h:543: error: syntax error before '__THROW' /usr/include/unistd.h:546: error: syntax error before
Re: 2.6.12 upload
On Tue, Jul 26, 2005 at 06:23:05PM +0200, Goswin von Brederlow wrote: Horms [EMAIL PROTECTED] writes: On Tue, Jul 26, 2005 at 03:26:04PM +0200, Goswin von Brederlow wrote: Horms [EMAIL PROTECTED] writes: On Thu, Jul 21, 2005 at 11:04:07AM +0200, Goswin von Brederlow wrote: The DI kernel udebs (linux-kernel-di-arch source) takes the kernel-image deb, splits it up into kernel and several groups of modules and builds udebs. There is no Depends there and can't be to keep the kernel-image debs available. kernel-image-di-arch ---source--- linux-kernel-di | magic | \/ kernel-tree-X.Y.Z-N ---depends--- kernel-image | \/ kernel sources The 'magic' part is the problem. I don't follow why there is a problem with linux-kernel-di depending on kernel-tree-X.Y.Z-N. -- Horms The problem is that the DAK will update linux-2.6, kernel-tree-x.y.z-n and kernel-image packages without any regards to linux-kernel-di. They will become out of sync and end up without source - GPL violation. In the old setup kernel-source-2.6.8 will remain until removed manualy and linux-kernel-di has that as source. But kernel-source-x.y.z.N provides kernel-tree-x.y.z-n for 1 = n = N Surely this resolves the problem some people percieve with regards to the GPL. No. Since linux-2.6 source means kernel-tree-x.y.(z+1)-1 will replace kernel-tree-x.y.z-n now. You would have to provide 1 = z = Z, 1 = n = N for it to still work. Ok, understood. Is there a reason that the dependancy can't be on kernel-tree-x.y.x-N? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Processed: Re: Bug#320033: kernel panic when using ebtables and arp.
reassign 320033 kernel-source-2.6.8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320091: kernel-image-2.6.8-2-386: Boot fails with a syntax error in /scripts/ext3-add-journal.sh
On Tue, Jul 26, 2005 at 03:23:57PM -0700, Dustin Laurence wrote: Package: kernel-image-2.6.8-2-386 Version: 2.6.8-16 Severity: important I am currently running kernel-image-2.6.8-1-386 on this up-to-date Debian Sarge system. That kernel seems to run fine. I attempted to upgrade to kernel-image-2.6.8-2-386, but it fails to boot and does not appear to even get as far as mounting /. These seem like the relevant messages: /scripts/ext3-add-journal.sh: 27: arith: syntax error: 0x /sbin/init: 426: arith: syntax error: 0x Kernel panic: Attempted to kill init! but I don't know what scrolled out of sight first. Obviously I had to copy them down by hand. Not finding it on the system, I mounted the initrd files and found a script named ext3-add-journal.sh, which I presume is the problem. They are clearly different between the two kernel versions but the syntax error doesn't make any obvious sense just from an inspection of the script. Any help or pointers for further investigation would be appreciated. Hi, This sounds like you are seeing two problems. 1. Your root device hasn't been detected properly and 2. The script isn't doing proper error checking Lets focus on problem 1. Could you take a look at what modules are needed to access your root partition using kernel-image-2.6.8-1-386? You should be able to work this out using dmsg and lsmod. Then compare this to the modules that are included in your initrd image and its /loadmodules script. If you can't get anywhere could you send the output of dmsg and lsmod from kernel-image-2.6.8-1-386, and from the initrd image of kernel-image-2.6.8-2-386, find . and the loadmodules script. Thanks -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320053: kernel-image-2.6.8-2-686: Installing it with sarge leads to failing at booting next time
On Tue, Jul 26, 2005 at 07:27:47PM +0200, Stefan Esterer wrote: Package: kernel-image-2.6.8-2-686 Severity: critical Justification: breaks the whole system I was installing Sarge on to my new notebook (Acer Extensa 4102 WLMI) with linux26 (so it installs the 2.6.8-2 kernel). Everything goes ok till the next reboot in which Sarge would ask me further questions about the system. After i choose the Sarge install in grub the kernel stops after some time with : modprobe: FATAL: Error inserting pciehp (/lib/modules/2.6.8-2-686/kernel/drivers/pci/hotplug/shpchp.ko): Operation not permitted shpchp: can't be loaded [...] hw_random: can't be loaded [...] Unable to handle kernel NULL pointer dereference at virtual adress 0024 [...] i810_audio: can't be loaded [...] So tried with bootoption pnpbios=off pci=nosort acpi=off apm=off but nothing works.. This sounds a lot like Bug #296762 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296762 Could you take a look at that and see if it helps, in particular the post from MI [EMAIL PROTECTED] on the 15th of May. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
