Bug#278729: kernel-image-2.6-k7: kernel-image-2.6*-k7* and 2.6*-686* should
In article [EMAIL PROTECTED] you wrote: On Tue, 8 Nov 2005 15:34:48 +0100, Sven Luther wrote [typo corrected]: You can now, just need to add Recommends: blah to the arch/arch/defines entry. Now the capability has been added, any chance you could pop this extra line in? I'd be happy to do it myself, but of course I can't. Richard. I will put the follwing into svn which should effect the change. -- Horms Index: debian/arch/i386/defines === --- debian/arch/i386/defines(revision 4929) +++ debian/arch/i386/defines(working copy) @@ -12,16 +12,20 @@ [686] class: PPro/Celeron/PII/PIII/P4 longclass: Pentium Pro/Celeron/Pentium II/Pentium III/Pentium 4 +recommends: libc6-i686 [686-smp] class: PPro/Celeron/PII/PIII/P4 SMP longclass: multi-processor Pentium Pro/Celeron/Pentium II/Pentium III/Pentium 4 +recommends: libc6-i686 [k7] class: AMD K7 longclass: 32bit AMD Duron/Athlon/AthlonXP +recommends: libc6-i686 [k7-smp] class: AMD K7 SMP longclass: 32-bit multi-processor AMD Duron/Athlon/AthlonXP +recommends: libc6-i686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340774: udev: unable to register OSS PCM device 0:0 for snd-intel8x0 with dxr3 card installed
In article [EMAIL PROTECTED] you wrote: reassign 340774 linux-2.6 thanks On Nov 25, AdamW [EMAIL PROTECTED] wrote: I've got a problem with oss emulation from alsa with dxr3 card installed in my system. Udev loads drivers for dxr3 first and then is unable to register OSS PCM device 0:0 When I remove dxr3 drivers (em8300, bt865) everything is ok. It would be grateful if you could fix this problem. I think that it would be enough if udev could load sound drivers first, however, I do not know how t do it. udev does not and will not enforce this kind of drivers ordering. This looks like a kernel bug. I understand, but with hotplug there is no problem with alsa oss emulation even if drivers for sound card are loaded first. It happens only when I use udev istead of hotplug I believe that what Marco is saying is that, while the ordering of loading the modules may be important, as does indeed seem to be the case here, its not up to udev to set that ordering, it is handled entirely by the kernel. So it seems that Alsa needs to be enhanced so either the ordering isn't required, or it has some way to load oss pcm first. With this in mind, could you please log a bug against ALSA and report any bugs back here (unfortunately bugzilla doesn't play well with the debian BTS). James Courtier-Dutton recently posted (to another bug) about how he would like ALSA bugs handled. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338606;msg=15 Thanks -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340836: linux-image-2.6.14-2-686: module ieee80211_crypt_tkip and ieee80211_crypt_ccmp are broken
In article [EMAIL PROTECTED] you wrote: Package: linux-image-2.6.14-2-686 Version: 2.6.14-3 Severity: important Hi, When ieee80211_crypt_tkip is loaded I have this in kern.log and TKIP auth doesn't work: Nov 26 10:41:36 localhost vmunix: ieee80211_crypt: registered algorithm 'NULL' Latest ieee80211-source give the same result. There is a known problem with the ieee80211 in Linus' tree being out of date. Its slowly being discussed on debian-kernel. http://lists.debian.org/debian-kernel/2005/11/msg01215.html -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319789: marked as done (kernel-image-2.6.11-1-k7: Does not detect builtin MPU of via82C686)
Your message dated Wed, 30 Nov 2005 17:26:52 +0900 (JST) with message-id [EMAIL PROTECTED] and subject line Bug#319789: No success 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 19:32:33 + From [EMAIL PROTECTED] Sun Jul 24 12:32:33 2005 Return-path: [EMAIL PROTECTED] Received: from piraten.student.lu.se [130.235.208.46] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1DwmDB-0005yb-00; Sun, 24 Jul 2005 12:32:33 -0700 Received: from d304.par.afb.lu.se (d304.par.afb.lu.se [194.47.217.44]) by piraten.student.lu.se (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Sun, 24 Jul 2005 21:32:31 +0200 (MEST) Received: from vincent by d304.par.afb.lu.se with local (Exim 4.52) id 1DwmD9-0001OJ-6l; Sun, 24 Jul 2005 21:32:31 +0200 Date: Sun, 24 Jul 2005 21:32:30 +0200 From: =?utf-8?q?Vincent_L=C3=B6nngren?= [EMAIL PROTECTED] Subject: kernel-image-2.6.11-1-k7: Does not detect builtin MPU of via82C686 To: Debian Bug Tracking System [EMAIL PROTECTED] Message-id: [EMAIL PROTECTED] MIME-version: 1.0 X-Mailer: reportbug 3.15 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT 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=-6.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS, HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-7 Severity: normal The module snd_via82xx is supposed to detect the builtin MPU of VIA82C686 units. It does so under kernel-image-2.6.8-2-k7, but not kernel-image-2.6.8-1-k7. I haven't been able to get it working with a custom kernel or by passing options (like mpu_port=330) to the module, either. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.11 Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Versions of packages kernel-image-2.6.11-1-k7 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 kernel-image-2.6.11-1-k7 recommends no packages. -- no debconf information --- Received: (at 319789-done) by bugs.debian.org; 30 Nov 2005 08:27:26 + From [EMAIL PROTECTED] Wed Nov 30 00:27:26 2005 Return-path: [EMAIL PROTECTED] Received: from koto.vergenet.net ([210.128.90.7]) by spohr.debian.org with esmtp (Exim 4.50) id 1EhNJE-000493-0K for [EMAIL PROTECTED]; Wed, 30 Nov 2005 00:27:26 -0800 Received: by koto.vergenet.net (Postfix, from userid 7100) id 5847934029; Wed, 30 Nov 2005 17:26:52 +0900 (JST) From: Horms [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#319789: No success In-Reply-To: [EMAIL PROTECTED] X-Newsgroups: gmane.linux.debian.devel.kernel User-Agent: tin/1.7.10-20050815 (Grimsay) (UNIX) (Linux/2.6.12.6-xen0 (i686)) Message-Id: [EMAIL PROTECTED] Date: Wed, 30 Nov 2005 17:26:52 +0900 (JST) 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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 In article [EMAIL PROTECTED] you wrote: I've been e-mail corresponding with Takashi Iwai with no success. It seems I'm the only one experiencing this, and I can't make it go away by fiddling with the bios settings or passing arguments to the modules. Maybe it's something very peculiar about my hardware, although it's strange that it works under kernels up to 2.6.8. Anyway, since I'm the only one experiencing this and I'm not in dire need of an MPU, maybe the bug should be closed? It sounds likely its a hardware problem. I'm going ahead and closing it as you suggest. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
Mikhail Gusarov [EMAIL PROTECTED] wrote: You ([EMAIL PROTECTED]) wrote: H If you know more, please add your knowledge below. [skip] 2.6.14-2 still enables the outdated ieee80211 :( Fixing this is simply a matter of disabling CONFIG_IEEE80211. This will allow to use ipw2200 (ipw2100 also) drivers built using module-assistant as before. The complete list of changes needed to turn off ieee80211 seems to be: # CONFIG_HOSTAP is not set # CONFIG_IPW2100 is not set # CONFIG_IPW2200 is not set # CONFIG_IEEE80211_CRYPT_TKIP is not set # CONFIG_IEEE80211_CRYPT_WEP is not set # CONFIG_IEEE80211_CRYPT_CCMP is not set # CONFIG_IEEE80211 is not set Or in other words HOSTAP and IPW2100, IPW2200 and HOSTAP (Prism) also needs to be disabled. Is the latter acceptable collateral dammage? I was under the impression that upstream had recently updated ieee80211. Is it still out of date in 2.6.14 ? Below is a patch that effects the change in the current 2.6.14 tree. Note that it probably will not apply cleanly as soon as any other changes are made to the configs due to some quirks in the way that split config. Note also that it consolodates some spurious arm and m68k configs for these options into the global config. Index: a/debian/arch/arm/config.s3c2410 === --- a/debian/arch/arm/config.s3c2410(revision 4929) +++ a/debian/arch/arm/config.s3c2410(working copy) @@ -279,11 +279,7 @@ # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set -CONFIG_IEEE80211=m # CONFIG_IEEE80211_DEBUG is not set -CONFIG_IEEE80211_CRYPT_WEP=m -CONFIG_IEEE80211_CRYPT_CCMP=m -CONFIG_IEEE80211_CRYPT_TKIP=m # # Device Drivers Index: a/debian/arch/arm/config.footbridge === --- a/debian/arch/arm/config.footbridge (revision 4929) +++ a/debian/arch/arm/config.footbridge (working copy) @@ -305,11 +305,7 @@ # CONFIG_VLSI_FIR is not set # CONFIG_VIA_FIR is not set # CONFIG_BT is not set -CONFIG_IEEE80211=m # CONFIG_IEEE80211_DEBUG is not set -CONFIG_IEEE80211_CRYPT_WEP=m -CONFIG_IEEE80211_CRYPT_CCMP=m -CONFIG_IEEE80211_CRYPT_TKIP=m # # Device Drivers @@ -687,7 +683,6 @@ # # CONFIG_NET_RADIO is not set # CONFIG_IPW_DEBUG is not set -CONFIG_IPW2200=m # # Wan interfaces Index: a/debian/arch/arm/config.ixp4xx === --- a/debian/arch/arm/config.ixp4xx (revision 4929) +++ a/debian/arch/arm/config.ixp4xx (working copy) @@ -437,11 +437,7 @@ # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set -CONFIG_IEEE80211=m # CONFIG_IEEE80211_DEBUG is not set -CONFIG_IEEE80211_CRYPT_WEP=m -CONFIG_IEEE80211_CRYPT_CCMP=m -CONFIG_IEEE80211_CRYPT_TKIP=m # # Device Drivers @@ -856,10 +852,8 @@ # # Wireless 802.11b ISA/PCI cards support # -CONFIG_IPW2100=m CONFIG_IPW2100_MONITOR=y # CONFIG_IPW_DEBUG is not set -CONFIG_IPW2200=m CONFIG_HERMES=y # CONFIG_PLX_HERMES is not set # CONFIG_TMD_HERMES is not set @@ -871,7 +865,6 @@ # Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support # # CONFIG_PRISM54 is not set -CONFIG_HOSTAP=m CONFIG_HOSTAP_FIRMWARE=y CONFIG_HOSTAP_PLX=m CONFIG_HOSTAP_PCI=m Index: a/debian/arch/arm/config.rpc === --- a/debian/arch/arm/config.rpc(revision 4929) +++ a/debian/arch/arm/config.rpc(working copy) @@ -251,11 +251,7 @@ # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set -CONFIG_IEEE80211=m # CONFIG_IEEE80211_DEBUG is not set -CONFIG_IEEE80211_CRYPT_WEP=m -CONFIG_IEEE80211_CRYPT_CCMP=m -CONFIG_IEEE80211_CRYPT_TKIP=m # # Device Drivers Index: a/debian/arch/m68k/config === --- a/debian/arch/m68k/config (revision 4929) +++ a/debian/arch/m68k/config (working copy) @@ -344,7 +344,3 @@ CONFIG_LIBCRC32C=m CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m -CONFIG_IEEE80211_CRYPT_CCMP=n -CONFIG_IEEE80211_CRYPT_TKIP=n -CONFIG_IEEE80211_CRYPT_WEP=n -CONFIG_IEEE80211=n Index: a/debian/arch/config === --- a/debian/arch/config(revision 4929) +++ a/debian/arch/config(working copy) @@ -585,7 +585,6 @@ CONFIG_USB_NET_AX8817X=m CONFIG_USB_YEALINK=m CONFIG_FUSE_FS=m -CONFIG_IEEE80211_CRYPT_CCMP=m CONFIG_PHYCONTROL=y # CONFIG_IPW_DEBUG is not set # CONFIG_EV64360 is not set @@ -601,7 +600,6 @@ CONFIG_INET_TCP_DIAG=m CONFIG_RAID_ATTRS=m CONFIG_USB_NET_CDCETHER=m -CONFIG_IPW2100=m CONFIG_DVB_USB_VP702X=m CONFIG_VIDEO_SAA6588=m CONFIG_CHELSIO_T1=m @@ -631,7 +629,6 @@ CONFIG_DRM_SAVAGE=m CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_PHYLIB=m -CONFIG_IEEE80211_CRYPT_TKIP=m CONFIG_MARVELL_PHY=m CONFIG_SCSI_SATA_MV=m CONFIG_SND_GENERIC_DRIVER=y @@ -645,7 +642,6 @@ CONFIG_IP6_NF_TARGET_REJECT=m #
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wed, Nov 30, 2005 at 06:51:44AM +, Horms wrote: Mikhail Gusarov [EMAIL PROTECTED] wrote: You ([EMAIL PROTECTED]) wrote: H If you know more, please add your knowledge below. [skip] 2.6.14-2 still enables the outdated ieee80211 :( Fixing this is simply a matter of disabling CONFIG_IEEE80211. This will allow to use ipw2200 (ipw2100 also) drivers built using module-assistant as before. The complete list of changes needed to turn off ieee80211 seems to be: # CONFIG_HOSTAP is not set # CONFIG_IPW2100 is not set # CONFIG_IPW2200 is not set # CONFIG_IEEE80211_CRYPT_TKIP is not set # CONFIG_IEEE80211_CRYPT_WEP is not set # CONFIG_IEEE80211_CRYPT_CCMP is not set # CONFIG_IEEE80211 is not set Or in other words HOSTAP and IPW2100, IPW2200 and HOSTAP (Prism) also needs to be disabled. Is the latter acceptable collateral dammage? I was under the impression that upstream had recently updated ieee80211. Is it still out of date in 2.6.14 ? yes. 2.6.15 ipw2XXX are fine and with up2date ieee80211 stack. there we should really enable those. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wed, Nov 30, 2005 at 10:09:54AM +0100, Maximilian Attems wrote: On Wed, Nov 30, 2005 at 06:51:44AM +, Horms wrote: Mikhail Gusarov [EMAIL PROTECTED] wrote: You ([EMAIL PROTECTED]) wrote: H If you know more, please add your knowledge below. [skip] 2.6.14-2 still enables the outdated ieee80211 :( Fixing this is simply a matter of disabling CONFIG_IEEE80211. This will allow to use ipw2200 (ipw2100 also) drivers built using module-assistant as before. The complete list of changes needed to turn off ieee80211 seems to be: # CONFIG_HOSTAP is not set # CONFIG_IPW2100 is not set # CONFIG_IPW2200 is not set # CONFIG_IEEE80211_CRYPT_TKIP is not set # CONFIG_IEEE80211_CRYPT_WEP is not set # CONFIG_IEEE80211_CRYPT_CCMP is not set # CONFIG_IEEE80211 is not set Or in other words HOSTAP and IPW2100, IPW2200 and HOSTAP (Prism) also needs to be disabled. Is the latter acceptable collateral dammage? I was under the impression that upstream had recently updated ieee80211. Is it still out of date in 2.6.14 ? yes. 2.6.15 ipw2XXX are fine and with up2date ieee80211 stack. there we should really enable those. Ok, so I should just go ahead and put my patch into the 2.6.14 branch? Or should we leave it as 2.6.15 probably isn't that far away... maybe -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.4.27-12 for Sid
Joey Hess [EMAIL PROTECTED] wrote: [-- text/plain, encoding quoted-printable, charset: us-ascii, 15 lines --] Horms wrote: Holger kindly reminded me on IRC yesterday that its been a long time since a new 2.4.27 was uploaded into Sarge. He pointed out that there are a number of valuable fixes in SVN. Is there any reason why you're sticking with 2.4.27+patches rather than following the 2.4 series upstream? Seems to this uninformed observer like it might be less work to follow upstream since it's limited to security fixes, serious bug fixes, and driver backports, assuming merging with it isn't too much work. Well, the main reasons are: 1) The patches are actually coming in at a very slow rate so keeping 2.4.27 up to date hasn't proved to be a great burden (though the same would be true of 2.4.32) 2) The merge takes time. 3) Currently maintaining 2.4.27 for sid also maintains it for sarge, two birds, one stone. Thats not to say that they are good reasons. But they are the reasons. To be quite honest, I would be very happy if someone would take over looking after 2.4. And update it to 2.4.32 and the new packaging infastructure that is now used for linux-2.6 in sid/etch. At the time that I started working on 2.4 packaging, 2.4 was slated as a viable kernel for a significant userbase for sarge. Looking forward, it is my belif that by the time we hit etch, 2.4 will only be for niche users, older hardware and arches that don't have 2.6. I think those users are very worthy reasons to keep 2.4, at least on arches that need it. But I'm finding it hard to get excited about doing it myself. Holger mentioned he would be interested in looking into it. He also mentioned that his coding skills are a little weak. Personally I don't think that is mich of a problem. What is needed is someone who is patient, can work with people to find answers, can do simple merging of patches and in short, manage package releases. In my time working on the kernel team I have spend much, much, much more time doing those things than the occasional like of code I write as a bugfix. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341378: kernel 2.6.12 and 2.6.14 crash on boot loading usb drivers on a sis chipset
Package: kernel Severity: critical Justification: breaks the whole system -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) With new udev (I reported to udev maintainer but it says it's a kernel problem) the kernel doesn't' boot anymore making a mess of usb tree as described in the log file I attached below. the only way is to deinnstall udev and use old hotplug Nov 30 10:51:26 localhost kernel: VFS: Mounted root (cramfs filesystem) readonly. Nov 30 10:51:26 localhost kernel: Freeing unused kernel memory: 180k freed Nov 30 10:51:26 localhost kernel: input: AT Translated Set 2 keyboard on isa0060/serio0 Nov 30 10:51:26 localhost kernel: Capability LSM initialized Nov 30 10:51:26 localhost kernel: NET: Registered protocol family 1 Nov 30 10:51:26 localhost kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Nov 30 10:51:26 localhost kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Nov 30 10:51:26 localhost kernel: SIS5513: IDE controller at PCI slot :00:02.5 Nov 30 10:51:26 localhost kernel: PCI: Found IRQ 11 for device :00:02.5 Nov 30 10:51:26 localhost kernel: SIS5513: chipset revision 0 Nov 30 10:51:26 localhost kernel: SIS5513: not 100%% native mode: will probe irqs later Nov 30 10:51:26 localhost kernel: SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller Nov 30 10:51:26 localhost kernel: ide0: BM-DMA at 0x9400-0x9407, BIOS settings: hda:DMA, hdb:pio Nov 30 10:51:26 localhost kernel: ide1: BM-DMA at 0x9408-0x940f, BIOS settings: hdc:DMA, hdd:pio Nov 30 10:51:26 localhost kernel: Probing IDE interface ide0... Nov 30 10:51:26 localhost kernel: hda: Maxtor 6Y080L0, ATA DISK drive Nov 30 10:51:26 localhost kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Nov 30 10:51:26 localhost kernel: Probing IDE interface ide1... Nov 30 10:51:26 localhost kernel: hdc: CD-224E, ATAPI CD/DVD-ROM drive Nov 30 10:51:26 localhost kernel: ide1 at 0x170-0x177,0x376 on irq 15 Nov 30 10:51:26 localhost kernel: Probing IDE interface ide2... Nov 30 10:51:26 localhost kernel: Probing IDE interface ide3... Nov 30 10:51:26 localhost kernel: Probing IDE interface ide4... Nov 30 10:51:26 localhost kernel: Probing IDE interface ide5... Nov 30 10:51:26 localhost kernel: hda: max request size: 128KiB Nov 30 10:51:26 localhost kernel: hda: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100) Nov 30 10:51:26 localhost kernel: hda: cache flushes supported Nov 30 10:51:26 localhost kernel: /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p5 p6 p4 Nov 30 10:51:26 localhost kernel: EXT3-fs: INFO: recovery required on readonly filesystem. Nov 30 10:51:26 localhost kernel: EXT3-fs: write access will be enabled during recovery. Nov 30 10:51:26 localhost kernel: kjournald starting. Commit interval 5 seconds Nov 30 10:51:26 localhost kernel: EXT3-fs: recovery complete. Nov 30 10:51:26 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 30 10:51:26 localhost kernel: hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) Nov 30 10:51:26 localhost kernel: Uniform CD-ROM driver Revision: 3.20 Nov 30 10:51:26 localhost kernel: input: PC Speaker Nov 30 10:51:26 localhost kernel: Real Time Clock Driver v1.12 Nov 30 10:51:26 localhost kernel: parport: PnPBIOS parport detected. Nov 30 10:51:26 localhost kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] Nov 30 10:51:26 localhost kernel: Floppy drive(s): fd0 is 1.44M Nov 30 10:51:26 localhost kernel: mice: PS/2 mouse device common for all mice Nov 30 10:51:26 localhost kernel: FDC 0 is a post-1991 82077 Nov 30 10:51:26 localhost kernel: Linux agpgart interface v0.101 (c) Dave Jones Nov 30 10:51:26 localhost kernel: agpgart: Detected SiS 650 chipset Nov 30 10:51:26 localhost kernel: agpgart: AGP aperture is 64M @ 0xe800 Nov 30 10:51:26 localhost kernel: usbcore: registered new driver usbfs Nov 30 10:51:26 localhost kernel: usbcore: registered new driver hub Nov 30 10:51:26 localhost kernel: i2c-sis96x version 1.0.0 Nov 30 10:51:26 localhost kernel: sis96x_smbus :00:02.1: SiS96x SMBus base address: 0x8100 Nov 30 10:51:26 localhost kernel: PCI: setting IRQ 11 as level-triggered Nov 30 10:51:26 localhost kernel: PCI: Assigned IRQ 11 for device :00:03.3 Nov 30 10:51:26 localhost kernel: ehci_hcd :00:03.3: Silicon Integrated Systems [SiS] USB 2.0 Controller Nov 30 10:51:26 localhost kernel: ehci_hcd :00:03.3: new USB bus registered, assigned bus number 1 Nov 30 10:51:26 localhost kernel: ehci_hcd :00:03.3: irq 11, io mem 0xec004000 Nov 30 10:51:26 localhost kernel: PCI: cache line size of 128 is not supported by device :00:03.3 Nov 30 10:51:27 localhost kernel: ehci_hcd :00:03.3: USB 2.0 initialized, EHCI 1.00,
Re: Bug#341035: kernel-source-2.6.8: [PATCH] CH Products USB yoke and pedals recognized but frozen by SET_IDLE
Vassilii Khachaturov [EMAIL PROTECTED] wrote: Package: kernel-source-2.6.8 Version: 2.6.8-16 Severity: normal Tags: patch The devices Bus 004 Device 003: ID 068e:00ff CH Products, Inc. Flight Sim Yoke Bus 004 Device 002: ID 068e:00f2 CH Products, Inc. Flight Sim Pedals on my machine get recognized but they don't work. cat'ting the relevant /dev/input/js* devices reports some initial data, but no axis or button input on any of them produces any change. flightgear/fgjs/js_demo don't show any input either. Following the tip at http://www.qbik.ch/usb/devices/showdev.php?id=587 by Alex Perry, I made the following patch that works perfectly on my system. A better approach would probably be a configure option if somebody does need that extra SET_IDLE call. I'm not x-posting to lkml since 2.6.8 is an ancient source (2.6.14 exists today), but since we only have 2.6.8 in debian archive as of today, I want it available for other Debian users that might want to solve the same problem. Just a slight clarification, 2.6.8 and 2.4.27 are the kernels for Sarge. More recent kernels are available in Sid (unstable) and Etch (currently testing), and occasionally experimental. There is also a backport of 2.4.12 for Sarge floating about: http://packages.vergenet.net/sarge-backports/ --- drivers/usb/input/hid-core.c.orig 2005-11-27 23:53:11.838499336 +0200 +++ drivers/usb/input/hid-core.c2005-11-27 23:53:05.533457848 +0200 @@ -1309,9 +1309,14 @@ void hid_init_reports(struct hid_device * bugfree devices and will cause a worst-case extra delay of * 1ms for buggy ones. */ +#if 0 /* vassilii: disabled tipped by Alex Perry's report for an equivalent + * change of older (2001) source. This allows the USB CH Products + * yoke and pedals to work correctly. + */ usb_control_msg(hid-dev, usb_sndctrlpipe(hid-dev, 0), HID_REQ_SET_IDLE, USB_TYPE_CLASS | USB_RECIP_INTERFACE, (1 8), hid-ifnum, NULL, 0, HZ * USB_CTRL_SET_TIMEOUT); +#endif report_enum = hid-report_enum + HID_INPUT_REPORT; list = report_enum-report_list.next; That seems fine enough to me. Do you know of any side effects of using this patch. Or do you considere it a candidate for inclusion in a Sarge update. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote: On Wed, Nov 30, 2005 at 10:09:54AM +0100, Maximilian Attems wrote: On Wed, Nov 30, 2005 at 06:51:44AM +, Horms wrote: Mikhail Gusarov [EMAIL PROTECTED] wrote: You ([EMAIL PROTECTED]) wrote: H If you know more, please add your knowledge below. [skip] 2.6.14-2 still enables the outdated ieee80211 :( Fixing this is simply a matter of disabling CONFIG_IEEE80211. This will allow to use ipw2200 (ipw2100 also) drivers built using module-assistant as before. The complete list of changes needed to turn off ieee80211 seems to be: # CONFIG_HOSTAP is not set # CONFIG_IPW2100 is not set # CONFIG_IPW2200 is not set # CONFIG_IEEE80211_CRYPT_TKIP is not set # CONFIG_IEEE80211_CRYPT_WEP is not set # CONFIG_IEEE80211_CRYPT_CCMP is not set # CONFIG_IEEE80211 is not set Or in other words HOSTAP and IPW2100, IPW2200 and HOSTAP (Prism) also needs to be disabled. Is the latter acceptable collateral dammage? I was under the impression that upstream had recently updated ieee80211. Is it still out of date in 2.6.14 ? yes. 2.6.15 ipw2XXX are fine and with up2date ieee80211 stack. there we should really enable those. Ok, so I should just go ahead and put my patch into the 2.6.14 branch? Or should we leave it as 2.6.15 probably isn't that far away... maybe depends if d-i will base itself on 2.6.14 for next beta than it's maybe nicer to have those ancient than nothing. there are still some -rc expected, maybe we get a christmas present? ;) -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341378: kernel 2.6.12 and 2.6.14 crash on boot loading usb drivers on a sis chipset
On Wed, Nov 30, 2005 at 11:05:26AM +0100, giorgiove wrote: Package: kernel Severity: critical Justification: breaks the whole system hmm as it works for others that severity seems midly exagerated, leave it to other d-kernel maintainer. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) With new udev (I reported to udev maintainer but it says it's a kernel problem) the kernel doesn't' boot anymore making a mess of usb tree as described in the log file I attached below. the only way is to deinnstall udev and use old hotplug please send in: working dmesg after boot, lspci output. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wednesday 30 November 2005 11:44, Maximilian Attems wrote: On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote: Ok, so I should just go ahead and put my patch into the 2.6.14 branch? Or should we leave it as 2.6.15 probably isn't that far away... maybe depends if d-i will base itself on 2.6.14 for next beta than it's maybe nicer to have those ancient than nothing. We will use whatever is in testing at the time of the release. So it depends very much on when 2.6.15 will be uploaded (and even if 2.6.14 will have moved to testing before then). Are there major changes from .14 to .15? If not, we should be able to change over to .15 relatively fast. My preliminary target for d-i beta2 is 2nd half of January. We'll need at least .14 in testing for the release. Cheers, FJP P.S. Expect an RC for 2.6.14-4 from me. From dmesg in vmware: kernel BUG at mm/slab.c:1807! invalid operand: [#1] pgp2Nf92jooKD.pgp Description: PGP signature
Bug#341392: linux-2.6: kernel BUG at mm/slab.c:1807!
Package: linux-2.6
Version: 2.6.14-4
Severity: serious
The following error happens on Debian Installer boot in vmware (386 kernel).
This problem was not present in -3.
The system does come up after the error, but it looks so basic (memory
management AFAICT) that I've set RC severity anyway.
Feel free to adjust if you disagree.
Cheers,
FJP
ACPI: Processor [CPU0] (supports 8 throttling states)
kmem_cache_create: duplicate cache UNIX
[ cut here ]
kernel BUG at mm/slab.c:1807!
invalid operand: [#1]
Modules linked in: unix thermal processor fan pcnet32 mii uhci_hcd usbcore
CPU:0
EIP:0060:[c013c552]Not tainted VLI
EFLAGS: 00010202 (2.6.14-2-386)
EIP is at kmem_cache_create+0x4ea/0x64c
eax: 002b ebx: c9c26b4c ecx: c02f8080 edx: 206b
esi: c0303829 edi: ca86fde9 ebp: c9c26980 esp: c988ff38
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 1605, threadinfo=c988e000 task=c98c8a70)
Stack: c02ba8f8 ca86fde4 000a c9a957a0 c9c2699c ff80 0080 c000
0080 ca870080 ca86fd60 0804e154 ca86fde4 c02410d2 ca86fde4 015c
2000 ca804000 ca870080 0804e190 0804e154
Call Trace:
[c02410d2] proto_register+0x56/0x1b4
[ca804000] af_unix_init+0x0/0x5f [unix]
[ca80400d] af_unix_init+0xd/0x5f [unix]
[c012e8a1] sys_init_module+0x99/0x16c
[c01030dd] syscall_call+0x7/0xb
Code: c9 fc ff ff 55 e8 0f 0e 00 00 59 e9 a9 fd ff ff 90 ff 74 24 30 68 f8 a8
2b c0 e8 6e b3
fd ff ff 05 4c 16 39 c0 0f 8e cb 15 00 00 0f 0b 0f 07 0d a0 2b c0 58 5a e9
d7 fd ff ff b8
00 e0 ff ff 21
6usbcore: registered new driver usbkbd
drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
pgpy5gbrlqwu8.pgp
Description: PGP signature
Bug#341393: linux-image-2.6.14-2-686 does not boot on HP Compaq nx8220 Laptop
Package: linux-image-2.6.14-2-686 The mentioned kernel does not boot. It says, that IRQ routing is not possible. acpi=off and pci=routeirq have no effect. MfG, Stefan Sonnenberg-Carstens NRW.BANK IT-Handel Department: 101-79310 Herzogstraße 15 D - 40217 Düsseldorf Tel.: +49211 826 3211 EMail: [EMAIL PROTECTED] Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided.
Re: Bug#332381: This problem has broader implications
Micah Anderson [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Although the original report says, After 250 days, the jiffies overflow and ipt_recent do not work anymore and is for 2.4, I've actually found that the code included in 2.6.8 (and probably any kernel version that includes ipt_recent) causes unexpected issues related to the jiffies as well, other than the 250 days issue. If you have rules that block based on ipt_recent you will find that they will block much too early at odd times. For example, I have a rule that will DROP ssh connections if there have been more than 6 seen in the last 60 seconds, but (seemingly) randomly I will get DROPped on the first connection. Lets be quite clear, the ip_recent code is in dire need of a rewrite. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341035: kernel-source-2.6.8: [PATCH] CH Products USB yoke and pedals recognized but frozen by SET_IDLE
I have changed my pinning policy to prefer testing over stable: APT policy: (950, 'testing'), (500, 'stable'), (300, 'unstable') and ran a full apt-get dist-upgrade. Having then downgraded freeglut back to the stable's 2.2.0 version and forbidding the current testing release of the 2.4.0 one, I recompiled flightgear, and it worked on Debian testing as well, also seeing the joystick, with the 2.6.14 kernel (sorry for my previous ignorance on this bug thread about the new kernel packaging scheme that had lead me to miss the post 2.6.8 kernel packages in the Debian archive). The funny thing is that (just for fun) I have retested the older (2.6.8) kernel, even after complete power down (with the power cord removed to make sure), and now I see that the CH Products yoke and pedals DO work with my computer (/dev/input/js[01]). Perhaps some change was introduced in the user-level USB utilities (and/or hotplug) that masked (or augmented, if you prefer it this way) the default kernel behaviour. You may reassign the present bug to some other package if you know to which one :-) Hence, I didn't work any further on the issue (my plan was to hunt down if an equivalent patch was needed to a later kernel, and creating a kernel config option to mask this patch for those who are afraid of it). Fly safe (even if in the virtual reality), Vassilii -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341104: linux-patch-debian-2.6.14: dropping EXTRAVERSION from official kernel patches
On Tue, Nov 29, 2005 at 05:03:11PM +0100, Sven Luther wrote:
2) I got a number of crashes (total freeze) with such kernel. The
personnal best is less than 5 minutes :-{. A 2.6.14.3 pristine
(linux patches - no debian patches) does not exhibit this
behaviour, AFAIK (currently stress testing it - no problems)
Could you please try the debian 2.6.14-4 linux-image kernels please ?
1) Crashes seems to result from bad initial defaults at the ACPI
THRM zone. Solved by setting more conservative values
2) I finally figure out how to generate exactly the right
kernel-version and kernel-package:
kernel-package name is determined once during configure, and must
be set with the --rev switch (2.6.14-4)
kernel-version is set at compile time (kernel-image) with the
--append-to-version switch.
So, maybe the kernel compilation procedure should be make a bit
more explicit about this configure -- kernel-image steps ?
Best regards
Pascal
--
Dr. ir. Pascal Dupuis
K. U. Leuven, ESAT/ELECTA (formerly ELEN): http://www.esat.kuleuven.ac.be/
Kasteelpark Arenberg, 10; B-3001 Leuven-Heverlee, Belgium
Tel. +32-16-32 10 21 -- Fax +32-16-32 19 85
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wed, Nov 30, 2005 at 12:49:28PM +0100, Frans Pop wrote: On Wednesday 30 November 2005 11:44, Maximilian Attems wrote: On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote: Ok, so I should just go ahead and put my patch into the 2.6.14 branch? Or should we leave it as 2.6.15 probably isn't that far away... maybe depends if d-i will base itself on 2.6.14 for next beta than it's maybe nicer to have those ancient than nothing. We will use whatever is in testing at the time of the release. So it depends very much on when 2.6.15 will be uploaded (and even if 2.6.14 will have moved to testing before then). Are there major changes from .14 to .15? If not, we should be able to change over to .15 relatively fast. better ntfs support, up2date ipw2XXX, vfs support shared subtree, fbcon console rotation + usual bunch of fixes and driver upgrades. no acpi change. My preliminary target for d-i beta2 is 2nd half of January. We'll need at least .14 in testing for the release. .15 should come around christmas, so it should be early enough for all archs to focus on. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341393: linux-image-2.6.14-2-686 does not boot on HP Compaq nx8220 Laptop
tags 341393 moreinfo stop On Wed, Nov 30, 2005 at 01:27:45PM +0100, [EMAIL PROTECTED] wrote: Package: linux-image-2.6.14-2-686 The mentioned kernel does not boot. It says, that IRQ routing is not possible. acpi=off and pci=routeirq have no effect. what's the last error message? can you paste log? Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided. wtf your message is public, keep away such strange footers. won't help your much. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#341393: linux-image-2.6.14-2-686 does not boot on HP Compaq nx8220 Laptop
Processing commands for [EMAIL PROTECTED]: tags 341393 moreinfo Bug#341393: linux-image-2.6.14-2-686 does not boot on HP Compaq nx8220 Laptop 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]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wednesday 30 November 2005 16:06, Maximilian Attems wrote: better ntfs support, up2date ipw2XXX, vfs support shared subtree, fbcon console rotation + usual bunch of fixes and driver upgrades. no acpi change. Nothing that should give us problems I think. Thanks. FB console rotation could be nice to play with :-) .15 should come around christmas, so it should be early enough for all archs to focus on. If it gets into Debian as quickly as .14 and does not draw the number of RC bugs that .14 seems to do, we should be fine. pgpdojiR6kZtk.pgp Description: PGP signature
Re: [kernel] r4856 - dists/trunk/linux-2.6/debian/bin
On Mon, 21 Nov 2005, Frederik Schüler wrote:
Author: fschueler-guest
Date: Mon Nov 21 07:59:55 2005
New Revision: 4856
Modified:
dists/trunk/linux-2.6/debian/bin/install-header
Log:
Comment out include/asm symlink deletion in the generic per-arch
linux-headers package. This symlink was present in headers packages before
2.6.14-1.
Modified: dists/trunk/linux-2.6/debian/bin/install-header
==
--- dists/trunk/linux-2.6/debian/bin/install-header (original)
+++ dists/trunk/linux-2.6/debian/bin/install-header Mon Nov 21 07:59:55 2005
@@ -15,7 +15,7 @@
# we'll want to drop this bit of code. The asm-* directories should remain.
DIRS=generic $(for i in $KERNEL_HEADER_DIRS; do echo -n '|' $i; done)
-rm -f include/asm
+#rm -f include/asm
eval
for i in include/asm-*; do
case \${i#include/asm-} in
can we put that patch in?
would unbreak klibc.
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#341393: linux-image-2.6.14-2-686 does not boot on HP Compaq nx8220 Laptop
On Wednesday 30 November 2005 17:01, Maximilian Attems wrote: [annoying footer blurb] wtf your message is public, keep away such strange footers. won't help your much. Ppl sending from corporate mail accounts mostly cannot control such footers. They are added by the mail servers after the fact. OTOH, they should probably not use such accounts for this purpose anyway as their employers probably won't be happy with the spam it attracts. pgpo8WwOOOlsd.pgp Description: PGP signature
Bug#332824: fixed udev - fixed initramfs-tools?
please retest with latest initramfs-tools in unstable aka version 0.41. it needs latest udev 0.76-3 too. the various seen timing bugs should be fixed thanks to newer udev. please add feedback to your bug report. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336317: fixed udev - fixed initramfs-tools?
please retest with latest initramfs-tools in unstable aka version 0.41. it needs latest udev 0.76-3 too. the various seen timing bugs should be fixed thanks to newer udev. please add feedback to your bug report. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337033: fixed udev - fixed initramfs-tools?
please retest with latest initramfs-tools in unstable aka version 0.41. it needs latest udev 0.76-3 too. the various seen timing bugs should be fixed thanks to newer udev. please add feedback to your bug report. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337045: fixed initramfs-tools?
please retest with latest initramfs-tools in unstable aka version 0.41. it needs latest udev 0.76-3 too. the various seen timing bugs should be fixed thanks to newer udev. please add feedback to your bug report. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338406: fixed initramfs-tools?
please retest with latest initramfs-tools in unstable aka version 0.41. it needs latest udev 0.76-3 too. the various seen timing bugs should be fixed thanks to newer udev. please add feedback to your bug report. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341035: kernel-source-2.6.8: [PATCH] CH Products USB yoke and pedals recognized but frozen by SET_IDLE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 30 Nov 2005 15:45:48 +0200 (IST) Vassilii Khachaturov [EMAIL PROTECTED] wrote: The funny thing is that (just for fun) I have retested the older (2.6.8) kernel, even after complete power down (with the power cord removed to make sure), and now I see that the CH Products yoke and pedals DO work with my computer (/dev/input/js[01]). Perhaps some change was introduced in the user-level USB utilities (and/or hotplug) that masked (or augmented, if you prefer it this way) the default kernel behaviour. Beware that your initial ramdisk for 2.6.8 was probably generated while still running Sarge, so the devices are possily created _before_ booting into Etch. Try backing up your old, working initial ramdisk for 2.6.8 and run dpkg-reconfigure for your 2.6.8 package. This should gerenate a new initial ramdisk similar to the one used for 2.6.14, and comparisons makes more sense. Oh, and when running dpkg-reconfigure then pay attention to the output revealing what ramdisk tool is used. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDjexkn7DbMsAkQLgRAu6jAJ9Ut5N8wu64neC64hXb8ez3P8niuwCfa8lU un24BN5HAPzmO9JolZ36bLA= =F/pn -END PGP SIGNATURE-
Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working
Horms wrote: In article [EMAIL PROTECTED] you wrote: I think I need to write a canned response for 2.6.8 bugs: As upstream kernel development moves at a rapid pace its virtually impossible to backport other than trivial fixes. Without spending a lot of time investingating your problem, would it be possible to see if the 2.6.12 backport to sarge, a significantly newer kernel, helps your immediate problem. http://packages.vergenet.net/sarge-backports/ Absolutely. I'll give it a try and let you know the results. --dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working
Dan Aronson wrote: Horms wrote: In article [EMAIL PROTECTED] you wrote: [...] would it be possible to see if the 2.6.12 backport to sarge, a significantly newer kernel, helps your immediate problem. http://packages.vergenet.net/sarge-backports/ Absolutely. I'll give it a try and let you know the results. Uh, which deb files should I try to install? --dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working
Seems to be a BIOS bug that backported 2.6.12 gets past. Fine solution for me. --dan ehci_hcd :02:0d.3: ALi Corporation USB 2.0 Controller ehci_hcd :02:0d.3: debug port 1 ehci_hcd :02:0d.3: BIOS handoff failed (112, 1010001) ehci_hcd :02:0d.3: continuing after BIOS bug... ehci_hcd :02:0d.3: new USB bus registered, assigned bus number 5 ehci_hcd :02:0d.3: irq 209, io mem 0x4070 ehci_hcd :02:0d.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 Horms wrote: In article [EMAIL PROTECTED] you wrote: Package: kernel-image-2.6.8-2-386 Version: 2.6.8-16 Severity: important I recently bouch a compusa brand usb 2.0 2 port card (model pci-usbali5273-2p-2). It doesn't work, the ehci module reports: ehci_hcd :02:0d.3: ALi Corporation USB 2.0 Controller ehci_hcd :02:0d.3: BIOS handoff failed (112, 1010001) ehci_hcd :02:0d.3: can't reset ehci_hcd :02:0d.3: init :02:0d.3 fail, -95 ehci_hcd: probe of :02:0d.3 failed with error -95 I think I need to write a canned response for 2.6.8 bugs: As upstream kernel development moves at a rapid pace its virtually impossible to backport other than trivial fixes. Without spending a lot of time investingating your problem, would it be possible to see if the 2.6.12 backport to sarge, a significantly newer kernel, helps your immediate problem. http://packages.vergenet.net/sarge-backports/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wed, Nov 30, 2005 at 12:49:28PM +0100, Frans Pop wrote: On Wednesday 30 November 2005 11:44, Maximilian Attems wrote: On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote: Ok, so I should just go ahead and put my patch into the 2.6.14 branch? Or should we leave it as 2.6.15 probably isn't that far away... maybe depends if d-i will base itself on 2.6.14 for next beta than it's maybe nicer to have those ancient than nothing. We will use whatever is in testing at the time of the release. So it depends very much on when 2.6.15 will be uploaded (and even if 2.6.14 will have moved to testing before then). Are there major changes from .14 to .15? If not, we should be able to change over to .15 relatively fast. .15 will bring a non-negligible amount of change to powerpc, going from ARCH=ppc|ppc64 to ARCH=powerpc, which may entail modifications in the boot-wrapper and kernel with builtin initrds, and maybe some subarch being broken or partially broken. But we are/will be working on the -rc releases in experimental, so hopefully this will work out fast, apus may only be there a couple of weeks after the .15 release though. My preliminary target for d-i beta2 is 2nd half of January. We'll need at least .14 in testing for the release. Should be nice, i think. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341378: kernel 2.6.12 and 2.6.14 crash on boot loading usb drivers on a sis chipset
severity 341378 important thanks On Wed, Nov 30, 2005 at 11:39:41AM +0100, Maximilian Attems wrote: On Wed, Nov 30, 2005 at 11:05:26AM +0100, giorgiove wrote: Package: kernel Severity: critical Justification: breaks the whole system hmm as it works for others that severity seems midly exagerated, leave it to other d-kernel maintainer. Indeed, lowering it. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) With new udev (I reported to udev maintainer but it says it's a kernel problem) the kernel doesn't' boot anymore making a mess of usb tree as described in the log file I attached below. the only way is to deinnstall udev and use old hotplug please send in: working dmesg after boot, lspci output. Oh, this is udev breakage, clearly not critical then. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#341378: kernel 2.6.12 and 2.6.14 crash on boot loading usb drivers on a sis chipset
Processing commands for [EMAIL PROTECTED]: severity 341378 important Bug#341378: kernel 2.6.12 and 2.6.14 crash on boot loading usb drivers on a sis chipset Severity set to `important'. 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#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working
Horms, I don't know why I didn't see it yesterday when I looked, but this seems to be the same bug as 316848. Sorry for making you reply again. I'll be even more careful next time. --dan Horms wrote: In article [EMAIL PROTECTED] you wrote: Package: kernel-image-2.6.8-2-386 Version: 2.6.8-16 Severity: important I recently bouch a compusa brand usb 2.0 2 port card (model pci-usbali5273-2p-2). It doesn't work, the ehci module reports: ehci_hcd :02:0d.3: ALi Corporation USB 2.0 Controller ehci_hcd :02:0d.3: BIOS handoff failed (112, 1010001) ehci_hcd :02:0d.3: can't reset ehci_hcd :02:0d.3: init :02:0d.3 fail, -95 ehci_hcd: probe of :02:0d.3 failed with error -95 I think I need to write a canned response for 2.6.8 bugs: As upstream kernel development moves at a rapid pace its virtually impossible to backport other than trivial fixes. Without spending a lot of time investingating your problem, would it be possible to see if the 2.6.12 backport to sarge, a significantly newer kernel, helps your immediate problem. http://packages.vergenet.net/sarge-backports/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
USB devices dead after APM suspend on kernel 2.6.14-2-686
Hi, I have Debian sid, kernel 2.6.14-2-686, installed on a Fujitsu Lifebook E342 laptop. When it comes back from APM suspend, the USB devices (a 4-port hub and a mouse) are not brought up, and lsusb (or any access to /proc/bus/usb) hangs. This doesn't happen with a 2.6.8-2-686 kernel which I also have installed. If my memory serves me right, this problem started with 2.6.14 kernels. Could anybody give me a hand on how to properly configure APM/USB so that suspend works as expected on a 2.6.14-2-686 kernel ? I've googled a lot around this theme but confess my inability and ignorance to resolve the problem. I'm unsure of what info would be important to analyze this problem. Please tell me if something else is necessary. Thanks a lot Paulo From /var/log/syslog after APM suspend: Nov 29 02:46:07 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) Nov 29 02:46:08 localhost kernel: usb 1-1.4: no poweroff yet, suspending instead Nov 29 02:46:08 localhost kernel: usb 1-1: no poweroff yet, suspending instead Nov 29 02:46:08 localhost kernel: usb usb1: no poweroff yet, suspending instead Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:07.2 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:07.2 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:13.0 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:13.1 Nov 29 02:46:25 localhost kernel: eth0: lost link beat Nov 29 02:46:25 localhost kernel: usb 1-1: USB disconnect, address 4 Nov 29 02:46:25 localhost kernel: usb 1-1.4: USB disconnect, address 6 Nov 29 02:46:26 localhost kernel: eth0: found link beat Nov 29 02:46:26 localhost kernel: eth0: autonegotiation complete: 100baseT-FD selected uname -a: Linux cortazar 2.6.14-2-686 #1 Sat Nov 26 13:10:11 UTC 2005 i686 GNU/Linux lsusb: Bus 001 Device 003: ID 045e:0084 Microsoft Corp. Bus 001 Device 002: ID 05e3:0660 Genesys Logic, Inc. USB 2.0 Hub Bus 001 Device 001: ID : lspci: :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) :00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:10.0 Communication controller: Agere Systems 56k WinModem (rev 01) :00:13.0 CardBus bridge: Texas Instruments PCI1221 :00:13.1 CardBus bridge: Texas Instruments PCI1221 :00:14.0 VGA compatible controller: Trident Microsystems Cyber 9388 (rev d3) dpkg -l udev: ii udev 0.076-3/dev/ and hotplug management daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341498: does not find valid filesystem label from fstab LABEL= option
Package: yaird Version: 0.0.11-12 Severity: normal Sending manually via KMail as I missed switching report bug SMTP server from master.debian.org to bugs.debian.org as indicated in the changelog of latest reportbug package. Hello, yaird doesn't seem to work with a label for the root filesystem: Richte linux-image-2.6.14-2-686 ein (2.6.14-4) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: label 'debian' not found (/etc/fstab:6) (fatal) Failed to create initrd image. dpkg: Fehler beim Bearbeiten von linux-image-2.6.14-2-686 (--configure): Unterprozess post-installation script gab den Fehlerwert 2 zurück Fehler traten auf beim Bearbeiten von: linux-image-2.6.14-2-686 E: Sub-process /usr/bin/dpkg returned an error code (1) The offending line in /etc/fstab is: LABEL=debian / xfs defaults0 1 This line works perfectly fine since ages and also worked with previous mkinitrd tool. The label seems to be fine: [EMAIL PROTECTED]:/ - xfs_admin -l /dev/hda5 label = debian As soon as I replace the offending line in /etc/fstab by /dev/hda5 / xfs defaults0 1 yaird seems to work correctly. This bug may or may not be related to: bug #337168 and bug #337415. I reported it cause for me it seems to be a different problem as yaird seems to get the label name correctly (no / that is reduced to ), but it still doesn't find the label. Regards, Martin -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14.2-tp23 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages yaird depends on: ii cpio 2.6-9 GNU cpio -- a program to manage ar ii dash 0.5.2-8 The Debian Almquist Shell ii libc62.3.5-8 GNU C Library: Shared libraries an ii libhtml-template-perl2.6-2 HTML::Template : A module for usin ii libparse-recdescent-perl 1.94.free-1 Generates recursive-descent parser ii perl 5.8.7-7 Larry Wall's Practical Extraction yaird recommends no packages. -- no debconf information -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
Bug#340344: yaird: Fail to create initrd on s390/s390x
On Wed, Nov 23, 2005 at 12:00:31AM +0100, Ivan Warren wrote: # yaird -o /tmp/a 2.6.14-2-s390x yaird error: unsupported device required: dasda (fatal) Could you post .. Most certainly... Thanks, that helps. After looking at your output and a debian kernel for s390 it seems that the kernel uses a module mapping table similar to that used for usb and pci; the modules listed in that table match closely with what you describe in your note. Perhaps you could test the version that is now in the development tree? Instructions: apt_get install bzr http_proxy=http://whatever.domain:port/ export http_proxy bzr get http://www.xs4all.nl/~ekonijn/yaird.bzr/ cd yaird.bzr sh bootstrap.sh ./configure --prefix=$HOME/local make install cd $HOME/local/etc ln -s Debian.cfg Templates.cfg cd /tmp sudo $HOME/local/sbin/yaird -v -o junk.img You're the first one to use this temporary, throw-away, bazaar-NG repository, so you may find suprises. Let me know if you need a tarball instead of this repository. The code is untested and will probably break. If this happens and the cause is not immediately obvious, could you add a load of Base::debug statements to Ccw*.pm and post the diffs and output? Note that the repository also contains EVMS support and ide-generic stuff; the differences are a bit much for a patch. Lets get this working first, sort out the packaging afterwards ... Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wednesday 30 November 2005 21:04, Sven Luther wrote: Are there major changes from .14 to .15? If not, we should be able to change over to .15 relatively fast. .15 will bring a non-negligible amount of change to powerpc, going from ARCH=ppc|ppc64 to ARCH=powerpc, which may entail modifications in the boot-wrapper and kernel with builtin initrds, and maybe some subarch being broken or partially broken. But we are/will be working on the -rc releases in experimental, so hopefully this will work out fast, apus may only be there a couple of weeks after the .15 release though. Well, to be honest I'm not too worried about ppc as it has good support. Please keep d-boot informed if anything really unexpected crops up. pgp3hYI63qhM4.pgp Description: PGP signature
Bug#341498: does not find valid filesystem label from fstab LABEL= option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 30 Nov 2005 23:40:04 +0100 Martin Steigerwald [EMAIL PROTECTED] wrote: The offending line in /etc/fstab is: LABEL=debian / xfs defaults0 1 This bug may or may not be related to: bug #337168 and bug #337415. Sounds like #337065 - could you please check... - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDji66n7DbMsAkQLgRAloJAJ0Y44WVXP2uWA/eU9hNrfPSyjVuGgCgo9oJ 3xJ2khYlkyLjOE23GRL90Ys= =4KMQ -END PGP SIGNATURE-
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Wed, Nov 30, 2005 at 11:58:17PM +0100, Frans Pop wrote: On Wednesday 30 November 2005 21:04, Sven Luther wrote: Are there major changes from .14 to .15? If not, we should be able to change over to .15 relatively fast. .15 will bring a non-negligible amount of change to powerpc, going from ARCH=ppc|ppc64 to ARCH=powerpc, which may entail modifications in the boot-wrapper and kernel with builtin initrds, and maybe some subarch being broken or partially broken. But we are/will be working on the -rc releases in experimental, so hopefully this will work out fast, apus may only be there a couple of weeks after the .15 release though. Well, to be honest I'm not too worried about ppc as it has good support. Yeah, but the change from ARCH=ppc | ARCH=ppc64, to a single re-unified ARCH=powerpc kernel will not go without glitch, especially for the lesser subarches (oldworld, prep, apus come to mind), and may cause some sever disfunction in even the mainline arches, let's hope this will be resolved before the 2.6.15 release though. I know i will already have to do some adaptation on the pegasos for the interrupt handling and the serial port for example. Please keep d-boot informed if anything really unexpected crops up. I will, no problem. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.14 status summary, and upcoming 2.6.15 ...
On Mon, Nov 28, 2005 at 04:12:34AM +0100, Jonas Smedegaard wrote: On Mon, 28 Nov 2005 02:48:01 +0100 Sven Luther [EMAIL PROTECTED] wrote: On Mon, Nov 28, 2005 at 02:23:32AM +0100, Jonas Smedegaard wrote: On Mon, 28 Nov 2005 00:13:50 +0100 Sven Luther [EMAIL PROTECTED] wrote: Yaird only by default supports drivers using sysfs. I suspect that the issue of bug#328534 is a driver module not properly using sysfs. And I guess the workaround is simply to add it manually to /etc/yaird/Default.cfg. But it is pure speculation - I'd really want Erik's opinion. Hmm, long and wandering history in that bug. If I read it correctly, user can boot 2.6.8, then run yaird for 2.6.14. This results in a boot image, booting it ends with complaints about 'sda1 fails to show up'. The SCSI driver for relevant controller has caused problems in recent kernels. This suggests: 1. Yaird believes it can build an image. This happens only if /sys/block/sda1 contains a symlink to something that looks credible as a disk driver in /sys/devices/ 2. Loading the drivers that yaird selects is not enough to get the hardware running to a level where it shows up in /sys/block/sda. Possible explanations: a. Driver has misleading sysfs information, that leads to a module not being loaded. b. Driver only becomes active after an unrelated module is loaded, like old versions of via82cxxx that only work after ide-generic is loaded. c. Driver does something clever that is not recognised by yaird, like /sbin/modprobe to start raid6 support. d. Driver does not work at all. To find out what is the case, start by looking at the /init script in the boot image. Does this contain the modules you want it to contain? The last module before mkbdev sda is suspect: it should be the one that creates the missing /sys/block/sda/dev. What's that last module? So looks like a driver problem, at this point not enough information to be sure the problem is in the sysfs part of the driver, or to trust that it can be made to work by loading extra modules. BTW, also, about ia64 situation, is it possible to use yaird in initrd case still ? I know Eric was disabling this for 0.12, but we are still using 0.11 ? Yaird 0.0.11 is newest release - so it _will_ be removed but _was_ not yet. It is deprecated due to lack of testing. So if someone starts testing it then Erik might get convinced to keep it: Replace /etc/yaird/Templates.cfg with /usr/share/doc/yaird/examples/Debian-initrd.cfg.gz gunzipped should do the trick. Seems to be fixed in lilo in the mean time, so I'll not look into this. Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
On Thu, Dec 01, 2005 at 12:26:25AM +0100, Frans Pop wrote: On Thursday 01 December 2005 00:09, Sven Luther wrote: Yeah, but the change from ARCH=ppc | ARCH=ppc64, to a single re-unified ARCH=powerpc kernel will not go without glitch, especially for the lesser subarches (oldworld, prep, apus come to mind), and may cause some sever disfunction in even the mainline arches, let's hope this will be resolved before the 2.6.15 release though. Getting it in d-i beta2 may be an opportunity to get some testing exposure for lesser arches, so that may be worth considering even if there are some known issues. We could easily make a note about it in the errata. Hehe, i guess i will be able to test most of the lesser arches myself, except apus, and well, oldworld miboot will not work, and benh told me oldworld/bootx is currently broken, altough he hoped to have the fix in time for 2.6.15. Given the major impact on ppc, is it an option for the kernel team to upload 2.6.15 to experimental first, so we keep a little bit more room for maneuvering towards the d-i release? Nope, we will upload the -rc kernels to experimental, but i don't think we should upload the actual released kernels to experimental, those should go into sid, and preferably the day of the release. That said, we have a few weeks, and working on the -rc tree in experimental should help sort out all issues, hopefully. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ancient ieee80211/ipw2200 drivers in recent kernel (2.6.14)
In gmane.linux.debian.devel.kernel Maximilian Attems [EMAIL PROTECTED] wrote: On Wed, Nov 30, 2005 at 12:49:28PM +0100, Frans Pop wrote: On Wednesday 30 November 2005 11:44, Maximilian Attems wrote: On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote: Ok, so I should just go ahead and put my patch into the 2.6.14 branch? Or should we leave it as 2.6.15 probably isn't that far away... maybe depends if d-i will base itself on 2.6.14 for next beta than it's maybe nicer to have those ancient than nothing. We will use whatever is in testing at the time of the release. So it depends very much on when 2.6.15 will be uploaded (and even if 2.6.14 will have moved to testing before then). Are there major changes from .14 to .15? If not, we should be able to change over to .15 relatively fast. Ok, in this case I am inclided to leave things as is in .14, and make changes as required, if any, to .15. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340344: yaird: Fail to create initrd on s390/s390x
The code is untested and will probably break. If this
happens and the cause is
not immediately obvious, could you add a load of Base::debug
statements
to Ccw*.pm and post the diffs and output?
Erik,
Well..
The build went ok.. however, here is what I get :
deb390-1:/tmp# /home/ivan/local/sbin/yaird -v -o junk.img
yaird: goal: template, prologue (/home/ivan/local/etc/yaird/Default.cfg:52)
yaird: action: prologue, {}
yaird: goal: module, fbcon (/home/ivan/local/etc/yaird/Default.cfg:56)
yaird: goal: mountdir, / (/home/ivan/local/etc/yaird/Default.cfg:143)
yaird error: unsupported device required: dasda (fatal)
(that's after removing the input device goals that are irrelevant on that
arch..)
Looks pretty much the same as before..
Now.. Unfortunatelly, I am completelly Perl ignorant - so I wouldn't even
know where to put any debug statement :-(
I'll try to see if I can squeeze more information out of this later on (it's
a bit late !)
However, If you have any idea, I'll be willing to accomodate for any test
you may find usefull.
--Ivan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working
On Wed, Nov 30, 2005 at 12:44:29PM -0800, Dan Aronson wrote: Horms, I don't know why I didn't see it yesterday when I looked, but this seems to be the same bug as 316848. Sorry for making you reply again. I'll be even more careful next time. No problem. Just to clarify. You still see the same bug in 2.6.12? -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working
As I wrote, the in 2.6.12 the driver now reports that there is a BIOS bug, but then recovers and finishes loading, I haven't yet tried a device on it, but it does show up correctly in /proc/bus/usb/devices. --dan Horms wrote: On Wed, Nov 30, 2005 at 12:44:29PM -0800, Dan Aronson wrote: Horms, I don't know why I didn't see it yesterday when I looked, but this seems to be the same bug as 316848. Sorry for making you reply again. I'll be even more careful next time. No problem. Just to clarify. You still see the same bug in 2.6.12? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341329: kernel-image-2.6.8-2-386: usb 2.0 pci card with ali 5273 chip not working
On Wed, Nov 30, 2005 at 06:37:57PM -0800, Dan Aronson wrote: As I wrote, the in 2.6.12 the driver now reports that there is a BIOS bug, but then recovers and finishes loading, I haven't yet tried a device on it, but it does show up correctly in /proc/bus/usb/devices. Thanks -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341519: linux-image-2.6.14-2-686: USB devices dead after resuming from APM suspend
Package: linux-image-2.6.14-2-686 Version: 2.6.14-4 Severity: normal I have up-to-date sid, kernel 2.6.14-2-686, installed on a Fujitsu Lifebook E342 laptop. When it comes back from APM suspend, the USB devices (a 4-port hub and a mouse) are not brought up, and lsusb (or any access to /proc/bus/usb) hangs. This doesn't happen with a 2.6.12-1-686 kernel which I also have installed. Paulo /proc/cmdline: root=/dev/hda1 ro acpi=off From /var/log/syslog after APM suspend: Nov 29 02:46:07 localhost kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) Nov 29 02:46:08 localhost kernel: usb 1-1.4: no poweroff yet, suspending instead Nov 29 02:46:08 localhost kernel: usb 1-1: no poweroff yet, suspending instead Nov 29 02:46:08 localhost kernel: usb usb1: no poweroff yet, suspending instead Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:07.2 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:07.2 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:13.0 Nov 29 02:46:25 localhost kernel: PCI: Found IRQ 9 for device :00:13.1 Nov 29 02:46:25 localhost kernel: eth0: lost link beat Nov 29 02:46:25 localhost kernel: usb 1-1: USB disconnect, address 4 Nov 29 02:46:25 localhost kernel: usb 1-1.4: USB disconnect, address 6 Nov 29 02:46:26 localhost kernel: eth0: found link beat Nov 29 02:46:26 localhost kernel: eth0: autonegotiation complete: 100baseT-FD selected uname -a: Linux cortazar 2.6.14-2-686 #1 Sat Nov 26 13:10:11 UTC 2005 i686 GNU/Linux lsusb: Bus 001 Device 003: ID 045e:0084 Microsoft Corp. Bus 001 Device 002: ID 05e3:0660 Genesys Logic, Inc. USB 2.0 Hub Bus 001 Device 001: ID : lspci: :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) :00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:10.0 Communication controller: Agere Systems 56k WinModem (rev 01) :00:13.0 CardBus bridge: Texas Instruments PCI1221 :00:13.1 CardBus bridge: Texas Instruments PCI1221 :00:14.0 VGA compatible controller: Trident Microsystems Cyber 9388 (rev d3) dpkg -l udev: ii udev 0.076-3/dev/ and hotplug management daemon -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.14-2-686 depends on: ii module-init-tools 3.2-pre9-4 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.11-12 Yet Another mkInitRD linux-image-2.6.14-2-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340344: yaird: Fail to create initrd on s390/s390x
On Thu, Dec 01, 2005 at 02:49:03AM +0100, Ivan Warren wrote:
The build went ok.. however, here is what I get :
deb390-1:/tmp# /home/ivan/local/sbin/yaird -v -o junk.img
yaird: goal: template, prologue (/home/ivan/local/etc/yaird/Default.cfg:52)
yaird: action: prologue, {}
yaird: goal: module, fbcon (/home/ivan/local/etc/yaird/Default.cfg:56)
yaird: goal: mountdir, / (/home/ivan/local/etc/yaird/Default.cfg:143)
yaird error: unsupported device required: dasda (fatal)
Could you test a corrected version?
- cd yaird.bzr
- bzr pull # get update
- grep dasd perl/Plan.pm# oops, that was missing
- make install # rest as before
Thanks,
Erik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341522: Drivers for sbus devices are not included in initrd on sparc
Package: yaird Version: 0.0.11-12 Severity: important Hi, As I've mentioned on d-k, the sbus devices found in some early Ultras are not properly sysfs-trained. As a result, yaird currently fails to include the SCSI driver if the controller is an sbus device. As modifying the drivers may be too complicated, a possible workaround is to always force-include the esp.ko driver (I believe it is the only sbus-based SCSI controller) on sparc. Thanks, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#341516: wpasupplicant: kernel panic on start with hostap driver
Processing commands for [EMAIL PROTECTED]: reassign 341516 kernel Bug#341516: wpasupplicant: kernel panic on start with hostap driver Bug reassigned from package `wpasupplicant' to `kernel'. severity 341516 grave Bug#341516: wpasupplicant: kernel panic on start with hostap driver Severity set to `grave'. 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#341524: yaird: fails to upgrade from linux-2.4 to 2.6
Package: yaird Version: 0.0.11-12 Severity: important Hello, I just upgraded to sid from sarge, and I'm having problems moving to the kernel 2.6. First off, let me mention that the upgrade didn't go as smoothly as planned, which was to be expected nowadays... My packages for kernel-image-2.6 were removed somehow, probably due to the new linux-image kernels. Anyways... Now that I actually try to switch to 2.6, some weird problem doesn't want to let me. I tried this: # aptitude install yaird [...] # tail -1 /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitrd.yaird # : note that I also tried without the above line # aptitude install linux-image-k7 [...] The following NEW packages will be installed: linux-image-2.6-k7 linux-image-2.6.14-2-k7 linux-image-k7 [...] Selecting previously deselected package linux-image-2.6.14-2-k7. (Reading database ... 230480 files and directories currently installed.) Unpacking linux-image-2.6.14-2-k7 (from .../linux-image-2.6.14-2-k7_2.6.14-4_i386.deb) ... You are attempting to install an initrd kernel image (version 2.6.14-2-k7) while running a kernel of version 2.4.27-2-k7, but you have no suitable ramdisk generation tool installed among /usr/sbin/mkinitrd.yaird. This will break the installation, unless a suitable ramdisk generation tool is also being installed right now. Could not find . at /var/lib/dpkg/tmp.ci/preinst line 228. Selecting previously deselected package linux-image-2.6-k7. Unpacking linux-image-2.6-k7 (from .../linux-image-2.6-k7_2.6.14-4_i386.deb) ... Selecting previously deselected package linux-image-k7. Unpacking linux-image-k7 (from .../linux-image-k7_2.6.14-4_i386.deb) ... Setting up linux-image-2.6.14-2-k7 (2.6.14-4) ... Failed to find suitable ramdisk generation tool for kernel version 2.6.14-2-k7 on running kernel 2.4.27-2-k7 in /usr/sbin/mkinitrd.yaird dpkg: error processing linux-image-2.6.14-2-k7 (--configure): subprocess post-installation script returned error exit status 9 dpkg: dependency problems prevent configuration of linux-image-2.6-k7: linux-image-2.6-k7 depends on linux-image-2.6.14-2-k7; however: Package linux-image-2.6.14-2-k7 is not configured yet. dpkg: error processing linux-image-2.6-k7 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-k7: linux-image-k7 depends on linux-image-2.6-k7; however: Package linux-image-2.6-k7 is not configured yet. dpkg: error processing linux-image-k7 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.14-2-k7 linux-image-2.6-k7 linux-image-k7 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.14-2-k7 (2.6.14-4) ... Failed to find suitable ramdisk generation tool for kernel version 2.6.14-2-k7 on running kernel 2.4.27-2-k7 in /usr/sbin/mkinitrd.yaird dpkg: error processing linux-image-2.6.14-2-k7 (--configure): subprocess post-installation script returned error exit status 9 dpkg: dependency problems prevent configuration of linux-image-2.6-k7: linux-image-2.6-k7 depends on linux-image-2.6.14-2-k7; however: Package linux-image-2.6.14-2-k7 is not configured yet. dpkg: error processing linux-image-2.6-k7 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-k7: linux-image-k7 depends on linux-image-2.6-k7; however: Package linux-image-2.6-k7 is not configured yet. dpkg: error processing linux-image-k7 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.14-2-k7 linux-image-2.6-k7 linux-image-k7 Seems to me that yaird doesn't support migration from 2.4 to 2.6.14. It does support anything below 2.6.13 though: # mkinitrd --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.12 echo 1 1 # mkinitrd --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.13 echo 1 # That is after adding the line to kernel-img.conf but i had the same result before. Now, I *was* able to upgrade, using the initramfs-tools package. Maybe the dependency list for linux-image should be reversed for that package, ie. put initramfs before yaird. # /usr/sbin/mkinitramfs --supported-host-version=2.4.27-2-k7 --supported-target-version=2.6.14 echo 1 1 I'm not sure I understand all the implications here, but I leave that all in your wise hands. I can help more if you tell me what to do. :) Thanks, a. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu, Dec 01, 2005 at 01:29:08AM -0500, The Anarcat wrote: Package: yaird Version: 0.0.11-12 Severity: important Hello, I just upgraded to sid from sarge, and I'm having problems moving to the kernel 2.6. First off, let me mention that the upgrade didn't go as smoothly as planned, which was to be expected nowadays... My packages for kernel-image-2.6 were removed somehow, probably due to the new linux-image kernels. Anyways... Now that I actually try to switch to 2.6, some weird problem doesn't want to let me. I tried this: Well, yaird cannot install from a 2.4 kernel, which is why you see this failure. The correct upgrade way using yaird is to first upgrade to the sarge (2.6.8) or etch (2.6.12) 2.6 kernel, and then upgrade to 2.6.14 after a reboot, using yaird, or boot the current 2.6.14 based sid-d-i netinst, once you are at the partitioning step, go to console 2, mount your root partition, chroot into it, mount /proc and /sys, and dpkg-reconfigure linux-image-2.6.14-2-k7. The other alternative is to install initramfs-tools, which knows how to install from a 2.4 kernel. I prefer using yaird myself though. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu Dec 01, 2005 at 07:58:32AM +0100, Sven Luther wrote: Well, yaird cannot install from a 2.4 kernel, which is why you see this failure. The correct upgrade way using yaird is to first upgrade to the sarge (2.6.8) or etch (2.6.12) 2.6 kernel, and then upgrade to 2.6.14 after a reboot, using yaird, or boot the current 2.6.14 based sid-d-i netinst, once you are at the partitioning step, go to console 2, mount your root partition, chroot into it, mount /proc and /sys, and dpkg-reconfigure linux-image-2.6.14-2-k7. The other alternative is to install initramfs-tools, which knows how to install from a 2.4 kernel. I prefer using yaird myself though. Is this what the upgrade path from sarge will look like for etch (assuming here that etch will go up to 2.6.14, or will that not happen at all?). In general, why not simply change the depends to have the whole thing Just Work in the general case? A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341524: yaird: fails to upgrade from linux-2.4 to 2.6
On Thu, Dec 01, 2005 at 02:12:20AM -0500, The Anarcat wrote: On Thu Dec 01, 2005 at 07:58:32AM +0100, Sven Luther wrote: Well, yaird cannot install from a 2.4 kernel, which is why you see this failure. The correct upgrade way using yaird is to first upgrade to the sarge (2.6.8) or etch (2.6.12) 2.6 kernel, and then upgrade to 2.6.14 after a reboot, using yaird, or boot the current 2.6.14 based sid-d-i netinst, once you are at the partitioning step, go to console 2, mount your root partition, chroot into it, mount /proc and /sys, and dpkg-reconfigure linux-image-2.6.14-2-k7. The other alternative is to install initramfs-tools, which knows how to install from a 2.4 kernel. I prefer using yaird myself though. Is this what the upgrade path from sarge will look like for etch (assuming here that etch will go up to 2.6.14, or will that not happen at all?). No, but we are still far from the sarge release (which is scheduled for december 2006, with freeze in july or so), and we probably will have to move to having initramfs-tools the first default for it. Maybe the best idea would be to have yaird as first default as now, but have the dependencies install both, which would guarantee it always works. In general, why not simply change the depends to have the whole thing Just Work in the general case? Well, at 2.6.14 release time, initramfs-tools, and his klibc dependency, had some maturation problems, and is also regularly broken by udev, so for now, yaird, provided it works, is still the more solid solution, and at least it will fail cleanly, and give you an error message or such, while initramfs-tools may or not fail during boot time. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
