Re: Kernel Images for Xenomai
Hi, thanks for interest in working on this! On 01/15/2014 12:25 PM, Leopold Palomo-Avellaneda wrote: I ask it to the debian kernel maintainers with the lack of knowledge that what it implies, because for example: - xenomai doesn't work in all architectures than debian. - it has patches for previous versions of the linux provided by debian. - who maintain it? However, I think that we can have interested people to work on that, and could be affordable. One of the biggest obstacles is the release schedules of Debian and Xenomai projects, and I can't expect either of them to follow the other. This implies that Debian typically includes an outdated version of Xenomai in its stable version even though I include the respective latest Xenomai release always immediately into Debian unstable. In addition, kernels supported by official Xenomai patches also typically differ from the ones that Debian ships. Since Debian synchronizes quite well now with kernel.org stable branches, there is at least a good chance to synchronize in this second regard. Roland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d67a90.6050...@antcom.de
Re: Kernel Images for Xenomai
On 01/15/2014 01:16 PM, Gilles Chanteperdrix wrote: In addition, kernels supported by official Xenomai patches also typically differ from the ones that Debian ships. Since Debian synchronizes quite well now with kernel.org stable branches, there is at least a good chance to synchronize in this second regard. Since Leopold is talking about generating patched linux images, does it really matter if they do not use the same versions as the ones used by Debian? Yes, if it's included in Debian stable, we would need to trust someone who steps up to support the respective package (i.e. its over time aging version) for security updates for years. When it's only in backports, there is no such hard restriction. Roland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d68347.6000...@antcom.de
Bug#725492: linux-source: deb file contains data.tar.gz instead of data.tar
Hi, I'm now also hit by this issue (some packages at debian-ports.org can't be built due to build-dep linux-source-3.11 not being listed in Packages). I asked on #debian-ftp a while back and was advised to use -Zgzip -z0 which is accepted but has the problem you're reporting. (The dpkg documentation now says this is equivalent to -Znone, but obviously that's not quite true!) The difference seems to be that -Znone results in a data.tar (rejected by lintian) and -Zgzip -z0 results in the same file but called data.tar.gz. The latter is actally not a gzip file and clearly breaks apt-ftparchive. A workaround would be to ignore gunzip errors in apt (apt-ftparchive) and retry data.tar.gz as data.tar. But this would be rather ugly. However, a file called data.tar.gz which isn't really gz is misleading. Maybe you can consider -z1 instead of -z0? (gzip -0 isn't really supported). Thanks in advance, Roland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a05e1a.6070...@antcom.de
Re: powerpcspe kernel-wedge configuration
On 06/05/2013 03:13 AM, Ben Hutchings wrote: linux/3.9.4-1 again failed to build again on powerpcspe, this time using the same kernel-wedge configuration as for powerpc. It's missing a few expected modules, which look Mac-specific and presumably have correctly been disabled for this architecture. I remember that in previous versions, we removed those modules for powerpcspe, for exactly this reason. Maybe it would be best if we just remove debian/installer/powerpcspe until you're ready to work on installer support? Fine with me, also. :-) As long as the rest of the build works... ;-) Thanks, Roland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51aee72f.6020...@antcom.de
Bug#708662: linux: FTBFS on powerpcspe due to duplicate module llc at kernel-wedge
Source: linux Version: 3.8.13-1 Severity: wishlist Tags: patch sid User: debian-powerpc...@breakpoint.cc Usertags: powerpcspe Hi, linux FTBFS on powerpcspe: ... dh_prep kernel-wedge install-files 3.8-2 install -D -m 644 debian/linux-image-3.8-2-powerpcspe/boot/vmlinux-3.8-2-powerpcspe debian/kernel-image-3.8-2-powerpcspe-di/boot/vmlinux install -d debian/kernel-image-3.8-2-powerpcspe-di/lib/modules/3.8-2-powerpcspe install -m 644 debian/linux-image-3.8-2-powerpcspe/lib/modules/3.8-2-powerpcspe/modules.builtin debian/linux-image-3.8-2-powerpcspe/lib/modules/3.8-2-powerpcspe/modules.order debian/kernel-image-3.8-2-powerpcspe-di/lib/modules/3.8-2-powerpcspe/ install -D -m 644 debian/linux-image-3.8-2-powerpcspe/boot/System.map-3.8-2-powerpcspe debian/kernel-image-3.8-2-powerpcspe-di/boot/System.map install -d debian/kernel-image-3.8-2-powerpcspe-di/usr/lib cp -a debian/linux-image-3.8-2-powerpcspe/usr/lib/linux-image-3.8-2-powerpcspe debian/kernel-image-3.8-2-powerpcspe-di/usr/lib/linux-image-3.8-2-powerpcspe kernel-wedge copy-modules 3.8-2 powerpcspe 3.8-2-powerpcspe kernel-wedge find-dups 3.8-2-powerpcspe some modules are in more than one package debian/nic-modules-3.8-2-powerpcspe-di lib/modules/3.8-2-powerpcspe/kernel/net/llc/llc.ko debian/nic-extra-modules-3.8-2-powerpcspe-di lib/modules/3.8-2-powerpcspe/kernel/net/llc/llc.ko command exited with status 1 make[2]: *** [install-udeb_powerpcspe] Error 2 ... This is fixed on powerpc already (see #708510), but not for powerpcspe. See attached patch: Basically, same solution: Add llc to debian/installer/powerpcspe/modules/powerpcspe/nic-shared-modules. Thanks in advance, Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.8.0 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash --- debian/installer/powerpcspe/modules/powerpcspe/nic-shared-modules.orig 2013-05-17 16:35:13.450702528 +0200 +++ debian/installer/powerpcspe/modules/powerpcspe/nic-shared-modules 2013-05-17 16:35:35.890711212 +0200 @@ -1 +1,2 @@ #include nic-shared-modules +llc
Bug#708510: linux: FTBFS on powerpc due to duplicate module llc at kernel-wedge
Source: linux Version: 3.8.12-1 Severity: important User: debian-powerpc...@breakpoint.cc Usertags: powerpcspe Hi, linux FTBFS on powerpc: ... some modules are in more than one package debian/nic-modules-3.8-1-powerpc-di lib/modules/3.8-1-powerpc/kernel/net/llc/llc.ko debian/nic-extra-modules-3.8-1-powerpc-di lib/modules/3.8-1-powerpc/kernel/net/llc/llc.ko command exited with status 1 make[2]: *** [install-udeb_powerpc] Error 2 ... This is because llc is pulled indirectly (via module dependency?) into both nic-modules and nic-extra-modules, although it is not listed in the modules files in debian/installer/* directly. Platform-specific, though, since it only happens on powerpc (and powerpcspe). I could confirm this by removing all modules from debian/installer/modules/nic-extra-modules except hamachi. (On powerpcspe, this issue surfaces when #708336 and #708094 are fixed.) Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.8.0 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130516075443.3846.69365.report...@spe1.antcom.de
Bug#708336: linux: FTBFS on powerpcspe due to missing module tms380tr
Source: linux Version: 3.8.12-1 Severity: wishlist Tags: sid patch User: debian-powerpc...@breakpoint.cc Usertags: powerpcspe Hi, linux FTBFS on powerpcspe[1] like this: ... dh_prep kernel-wedge install-files 3.8-1 install -D -m 644 debian/linux-image-3.8-1-powerpcspe/boot/vmlinux-3.8-1-powerpcspe debian/kernel-image-3.8-1-powerpcspe-di/boot/vmlinux install -d debian/kernel-image-3.8-1-powerpcspe-di/lib/modules/3.8-1-powerpcspe install -m 644 debian/linux-image-3.8-1-powerpcspe/lib/modules/3.8-1-powerpcspe/modules.builtin debian/linux-image-3.8-1-powerpcspe/lib/modules/3.8-1-powerpcspe/modules.order debian/kernel-image-3.8-1-powerpcspe-di/lib/modules/3.8-1-powerpcspe/ install -D -m 644 debian/linux-image-3.8-1-powerpcspe/boot/System.map-3.8-1-powerpcspe debian/kernel-image-3.8-1-powerpcspe-di/boot/System.map install -d debian/kernel-image-3.8-1-powerpcspe-di/usr/lib cp -a debian/linux-image-3.8-1-powerpcspe/usr/lib/linux-image-3.8-1-powerpcspe debian/kernel-image-3.8-1-powerpcspe-di/usr/lib/linux-image-3.8-1-powerpcspe kernel-wedge copy-modules 3.8-1 powerpcspe 3.8-1-powerpcspe missing module tms380tr command exited with status 1 make[2]: *** [install-udeb_powerpcspe] Error 2 make[1]: *** [binary-arch_powerpcspe] Error 2 ... This is due to a module referenced in the di module lists which is not available anymore in 3.8. Attaching a patch that fixes this. The module is now only referenced by powerpcspe. (The issue surfaces when #708094 is fixed.) Thanks in advance, Roland [1] http://wiki.debian.org/PowerPCSPEPort -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.8.0 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash --- debian/installer/powerpcspe/modules/powerpcspe/nic-extra-modules.orig 2013-05-14 16:01:10.836962816 +0200 +++ debian/installer/powerpcspe/modules/powerpcspe/nic-extra-modules 2013-05-14 16:01:22.068972821 +0200 @@ -1,3 +1,2 @@ #include nic-extra-modules -tms380tr --- debian/installer/powerpcspe/modules/powerpcspe-powerpcspe-miboot/nic-extra-modules.orig 2013-05-14 16:01:41.624968756 +0200 +++ debian/installer/powerpcspe/modules/powerpcspe-powerpcspe-miboot/nic-extra-modules 2013-05-14 16:01:55.000968207 +0200 @@ -11,7 +11,6 @@ abyss lanstreamer olympic -tms380tr tmspci de2104x dmfe
Bug#708094: linux: FTBFS on powerpcspe due to missing mkimage
Hi Ben, you wrote: Please provide a patch to disable building the unwanted file. I'm attaching a patch that disables the cited target and some further individual ones of the respective MPC boards which also lead to similar errors (mkimage missing for building cuImage.* etc.). Roland Description: Prevent building uImage with missing mkimage On some powerpc platforms, CONFIG_DEFAULT_UIMAGE is selected automatically, which leads to uImage being built automatically with mkimage. This tool is not available in linux's build-dependencies, and the file is not strictly necessary, so we are omitting this step in the build process, Debian-specific. Author: Roland Stigge sti...@antcom.de Bug-Debian: http://bugs.debian.org/708094 Index: linux-3.8.12/arch/powerpc/boot/Makefile === --- linux-3.8.12.orig/arch/powerpc/boot/Makefile 2013-05-13 21:05:41.0 +0200 +++ linux-3.8.12/arch/powerpc/boot/Makefile 2013-05-14 07:48:26.434286772 +0200 @@ -204,7 +204,6 @@ image-$(CONFIG_PPC_PMAC) += zImage.pmac image-$(CONFIG_PPC_HOLLY) += dtbImage.holly image-$(CONFIG_PPC_PRPMC2800) += dtbImage.prpmc2800 -image-$(CONFIG_DEFAULT_UIMAGE) += uImage image-$(CONFIG_EPAPR_BOOT) += zImage.epapr # @@ -262,23 +261,6 @@ image-$(CONFIG_MPC836x_MDS) += cuImage.mpc836x_mds image-$(CONFIG_ASP834x) += dtbImage.asp834x-redboot -# Board ports in arch/powerpc/platform/85xx/Kconfig -image-$(CONFIG_MPC8540_ADS) += cuImage.mpc8540ads -image-$(CONFIG_MPC8560_ADS) += cuImage.mpc8560ads -image-$(CONFIG_MPC85xx_CDS) += cuImage.mpc8541cds \ - cuImage.mpc8548cds_32b \ - cuImage.mpc8555cds -image-$(CONFIG_MPC85xx_MDS) += cuImage.mpc8568mds -image-$(CONFIG_MPC85xx_DS) += cuImage.mpc8544ds \ - cuImage.mpc8572ds -image-$(CONFIG_TQM8540) += cuImage.tqm8540 -image-$(CONFIG_TQM8541) += cuImage.tqm8541 -image-$(CONFIG_TQM8548) += cuImage.tqm8548 -image-$(CONFIG_TQM8555) += cuImage.tqm8555 -image-$(CONFIG_TQM8560) += cuImage.tqm8560 -image-$(CONFIG_SBC8548) += cuImage.sbc8548 -image-$(CONFIG_KSI8560) += cuImage.ksi8560 - # Board ports in arch/powerpc/platform/embedded6xx/Kconfig image-$(CONFIG_STORCENTER) += cuImage.storcenter image-$(CONFIG_MPC7448HPC2) += cuImage.mpc7448hpc2
Bug#708094: linux: FTBFS on powerpcspe due to missing mkimage
Source: linux Version: 3.8.12-1 Severity: wishlist Tags: sid User: debian-powerpc...@breakpoint.cc Usertags: powerpcspe Hi, on powerpcspe[1], linux currently FTBFS like this: ... HOSTCC arch/powerpc/boot/mktree WRAParch/powerpc/boot/uImage INFO: Uncompressed kernel (size 0x5d1000) overlaps the address of the wrapper(0x40) INFO: Fixing the link_address of wrapper to (0x60) mkimage command not found - U-Boot images will not be built make[6]: *** [arch/powerpc/boot/uImage] Error 1 ... This is because the platforms CONFIG_MPC85xx activated in our powerpcspe config select CONFIG_DEFAULT_UIMAGE which leads to mkimage (for uImage creation) to be called. Adding Build-Depends: u-boot-tools fixes this. Limiting to [powerpcspe] would be fine for now, IMO. Thanks in advance, Roland [1] http://wiki.debian.org/PowerPCSPEPort -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.8.0 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130513070127.31588.17225.report...@spe2.antcom.de
Bug#708094: linux: FTBFS on powerpcspe due to missing mkimage
Hi, On 05/13/2013 03:40 PM, Ben Hutchings wrote: On Mon, 2013-05-13 at 09:01 +0200, Roland Stigge wrote: Source: linux Version: 3.8.12-1 Severity: wishlist Tags: sid User: debian-powerpc...@breakpoint.cc Usertags: powerpcspe Hi, on powerpcspe[1], linux currently FTBFS like this: ... HOSTCC arch/powerpc/boot/mktree WRAParch/powerpc/boot/uImage INFO: Uncompressed kernel (size 0x5d1000) overlaps the address of the wrapper(0x40) INFO: Fixing the link_address of wrapper to (0x60) mkimage command not found - U-Boot images will not be built make[6]: *** [arch/powerpc/boot/uImage] Error 1 ... This is because the platforms CONFIG_MPC85xx activated in our powerpcspe config select CONFIG_DEFAULT_UIMAGE which leads to mkimage (for uImage creation) to be called. Adding Build-Depends: u-boot-tools fixes this. Limiting to [powerpcspe] would be fine for now, IMO. On many ARM platforms, u-boot images are generated by flash-kernel at installation time. Shouldn't this platform be handled in the same way? Thank you for the quick response! You are right - the uImage generated in the above step is not directly used on boot (without flashing separately on typical PowerPCSPE boards). I'm working on a solution for this, separately. However, the powerpc specific option CONFIG_DEFAULT_UIMAGE always tries to build uImage at (Debian package) linux build time, see arch/powerpc/boot/Makefile:207: image-$(CONFIG_DEFAULT_UIMAGE) += uImage So can we add u-boot-tools as build-dep for powerpcspe? Or do you have a different suggestion for making the default package linux build? Thanks in advance, Roland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5190fff4.1040...@antcom.de
Bug#693042: linux: please support arch powerpcspe
On 12/11/12 17:48, Bastian Blank wrote: On Mon, Nov 12, 2012 at 05:19:36PM +0100, Roland Stigge wrote: On 12/11/12 13:35, Bastian Blank wrote: On Mon, Nov 12, 2012 at 01:24:06PM +0100, Roland Stigge wrote: I'm attaching a patch that supports powerpcspe [1] in linux. This is a follow-up for http://bugs.debian.org/593340 Please provide a patch that re-uses the existing config files. I will not accept full configs any longer. Are there any tools recommended for generating this, or should I just omit CONFIG_ options from the new config that are already included in the generic config? This config should only include settings relevant for the cpu selection. I reduced the config (debian/config/powerpcspe/config*) to only cpu selection. Unfortunately, this seems to be not enough config, even if automatically merged with debian/config/config: Some driver modules that are expected later on, are not built. As an example: 8139too is missing at kernel-wedge time: kernel-wedge copy-modules 3.2.0-4 powerpcspe 3.2.0-4-powerpcspe ... missing module 8139too Looking at the other archs' configs, I find CONFIG_8139TOO=m in them, e.g. debian/config/powerpc/config. So should I activate the missing modules in powerpcspe's config also, even if it's not strictly CPU specific? Or add it all to debian/config/config? Thanks in advance, Roland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50a21727.1030...@antcom.de
Bug#693042: linux: please support arch powerpcspe
On 12/11/12 13:35, Bastian Blank wrote: On Mon, Nov 12, 2012 at 01:24:06PM +0100, Roland Stigge wrote: I'm attaching a patch that supports powerpcspe [1] in linux. This is a follow-up for http://bugs.debian.org/593340 Please provide a patch that re-uses the existing config files. I will not accept full configs any longer. Thanks for the note! Are there any tools recommended for generating this, or should I just omit CONFIG_ options from the new config that are already included in the generic config? Thanks in advance! Roland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50a12198.9050...@antcom.de
Bug#622361: linux-base: Please enable option BATMAN_ADV
Package: linux-base Version: 3.2 Severity: wishlist Hi, please add OPTION_BATMAN_ADV as a kernel module in linux-image-* Thanks! bye, Roland -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-base depends on: ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii libuuid-perl 0.02-4 Perl extension for using UUID inte ii udev 167-1 /dev/ and hotplug management daemo ii util-linux2.17.2-9.1 Miscellaneous system utilities linux-base recommends no packages. linux-base suggests no packages. -- debconf information: linux-base/disk-id-manual-boot-loader: linux-base/disk-id-update-failed: * linux-base/disk-id-manual: * linux-base/disk-id-convert-plan-no-relabel: true linux-base/do-bootloader-default-changed: * linux-base/disk-id-convert-plan: true * linux-base/disk-id-convert-auto: true -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110412135711.24189.30688.report...@rst-pc1.lan.work-microwave.de
Bug#620059: #620059: nfs-kernel: Starting NFS kernel daemon: nfsd mountd failed!
Hi, replacing portmap with rpcbind worked for me, since portmap doesn't support IPv6 currently (see #563545). Thanks for reporting. bye, Roland -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d934f52.3000...@debian.org
Bug#288273: kernel-image-2.6.8-1-sparc64: ieee1394 disk problem on sparc (SunBlade
Hi, sorry for the delay. maximilian attems wrote: sparc fixes went into upstream, you may want to test trunk linux-images 2.6.24-rc6, see apt lines wiki.debian.org/DebianKernel thanks for feedback. I tried it with the current default Debian kernel 2.4.24. Now, it looks like this on switching on the device: firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: Unsolicited response (source ffc0, tlabel 5) firewire_core: Unsolicited response (source ffc0, tlabel f) firewire_core: Unsolicited response (source ffc0, tlabel 10) firewire_core: Unsolicited response (source ffc0, tlabel 11) firewire_core: Unsolicited response (source ffc0, tlabel 12) firewire_core: Unsolicited response (source ffc0, tlabel 13) firewire_core: Unsolicited response (source ffc0, tlabel 14) firewire_core: giving up on config rom for node id ffc0 bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288273: kernel-image-2.6.8-1-sparc64: ieee1394 disk problem on sparc (SunBlade 1000)
reopen 288273 thanks Hi, I just checked it on the SPARC machine, with the following result: = firewire_core: giving up on config rom for node id ffc1 firewire_core: BM lock failed, making local node (ffc0) root. firewire_core: phy config: card 0, new root=ffc0, gap_count=5 /[EMAIL PROTECTED],70: PCI discard timeout error asserted. /[EMAIL PROTECTED],70: PCI bus error, PCI_STATUS[22a0] firewire_core: Unsolicited response (source ffc1, tlabel 0) firewire_core: BM lock failed, making local node (ffc0) root. firewire_core: phy config: card 0, new root=ffc0, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 /[EMAIL PROTECTED],70: PCI discard timeout error asserted. /[EMAIL PROTECTED],70: PCI bus error, PCI_STATUS[22a0] /[EMAIL PROTECTED],70: PCI discard timeout error asserted. /[EMAIL PROTECTED],70: PCI bus error, PCI_STATUS[22a0] firewire_core: Unsolicited response (source ffc1, tlabel 0) firewire_core: BM lock failed, making local node (ffc0) root. firewire_core: phy config: card 0, new root=ffc0, gap_count=5 /[EMAIL PROTECTED],70: PCI discard timeout error asserted. /[EMAIL PROTECTED],70: PCI bus error, PCI_STATUS[22a0] firewire_core: Unsolicited response (source ffc1, tlabel 0) firewire_core: BM lock failed, making local node (ffc0) root. firewire_core: phy config: card 0, new root=ffc0, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 /[EMAIL PROTECTED],70: PCI discard timeout error asserted. /[EMAIL PROTECTED],70: PCI bus error, PCI_STATUS[22a0] firewire_core: phy config: card 0, new root=ffc1, gap_count=5 /[EMAIL PROTECTED],70: PCI discard timeout error asserted. [...] = Turning on the firewire external HDD (hot-plug), I can make the system lock up. I also checked that the i386 config still works: = firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 scsi3 : SBP-2 IEEE-1394 firewire_core: created new fw device fw1 (4 config rom retries) firewire_sbp2: logged in to sbp2 unit fw1.0 (0 retries) firewire_sbp2: - management_agent_address:0xf001 firewire_sbp2: - command_block_agent_address: 0xf0010020 firewire_sbp2: - status write address:0x0001 scsi 3:0:0:0: Direct-Access-RBC WDC WD20 00JB-00GVA0 PQ: 0 ANSI: 4 sd 3:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 11 00 00 00 sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 3:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 11 00 00 00 sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sd 3:0:0:0: [sdb] Attached SCSI disk sd 3:0:0:0: Attached scsi generic sg2 type 14 = (All using latest stock Debian kernels 2.6.22) I hope I will have the time for further investigation soon. Feel free to tell me what to look for to speed up this process. Thanks, bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395181: missing dependency on libdevmapper1.01
maximilian attems wrote: initrd-tools is dead. you want to use initramfs-tools. OK, then better leave this one unfixed to keep the package RC-buggy and let someone kick it out of Debian... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395181: missing dependency on libdevmapper1.01
Hi,
you can either do this:
===
diff -ruN initrd-tools-0.1.84.1.orig/mkinitrd initrd-tools-0.1.84.1/mkinitrd
--- initrd-tools-0.1.84.1.orig/mkinitrd 2006-04-24 01:08:14.0 +0200
+++ initrd-tools-0.1.84.1/mkinitrd 2006-11-02 17:23:11.0 +0100
@@ -384,7 +384,7 @@
EOF
{
echo /sbin/cryptsetup
- echo /lib/libdevmapper.so.1.01
+ echo /lib/libdevmapper.so.*
echo /lib/libpopt.so.0
} 6
}
===
... or hard code it again (/lib/libdevmapper.so.1.02) and next time get
a new bug for free!
(This is not the first time this happens: See #266591 et al.)
bye,
Roland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378225: Dell Laptop does not resume from suspend-to-RAM
Hi, I'm not 100% sure, but according to the symptoms on my site, the problem seems to be fixed in 2.6.18: I had the same problem with 2.6.17 and Dell Latitude X1 as described in all of the above listed bug reports. With Debian's stock 2.6.18, it's gone. :-) Please retest and close the bugs if appropriate (or give a note otherwise). Thanks, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#258979: kernel-image-2.6.*: debsums checksum mismatch
block 258979 by 261019 thanks Hi, I created a patch for kernel-package that until now didn't create md5sums on package creation resulting in apt creating them on package installation, followed by depmod -a invalidating them. See #261019. bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
#330191: klibc 1.1.1-4 FTBFS on sparc
Hi, now that linux-headers-2.6.12-1-* is not available in sid anymore, I tried it with linux-headers-2.6.14-2-* (-sparc64 in this case). Besides the fact that the proper asm - asm-sparc64 symlink was missing, the 2.6.14-2-* package is configured for SPARC32 and therefore doesn't provide 64 bit options like page size etc. that is needed by klibc (build). Is this a bug or a feature? ;-) Thanks. bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337774: linux-2.6: Identd service currently broken by default
Package: linux-2.6 Severity: important Hi, I came across this problem by using ident identification with PostgreSQL in Debian. The default identd in Debian, pidentd, currently utilizes NETLINK (with a patch to upstream code[1]) for connection identification. Therefore, kernel support is needed. While CONFIG_IP_TCPDIAG is currently configured as a module by default (checked on i386 and sparc64), this one is not loaded automatically. This causes identd service to be broken by default: [EMAIL PROTECTED]:~$ telnet atari 113 Trying 192.168.5.99... Connected to atari. Escape character is '^]'. 22,36660 22 , 36660 : ERROR : NO-USER With the module tcp_diag loaded manually on the server, it works: [EMAIL PROTECTED]:~$ telnet atari 113 Trying 192.168.5.99... Connected to atari. Escape character is '^]'. 22,36660 22 , 36660 : USERID : UNIX :root The package pidentd solved this problem by just mentioning it in the README.Debian[2]. I'm currently seeing some possible solutions to solve this problem: (a) Make the module tcp_diag being loaded automatically on demand (preferred) (b) Set CONFIG_IP_TCPDIAG=y (c) Change pidentd, reassigning the bug (questionable) Thanks, Roland [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=208290 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305926 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-sparc64, also tested with 2.6.14 on i386 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329879: iptables error on sun450
Hi, is this related to http://lists.debian.org/debian-sparc/2005/10/msg00073.html or rather not? bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288273: kernel-image-2.6.8-1-sparc64: ieee1394 disk problem on sparc (SunBlade 1000)
Package: kernel Severity: normal Hi, I've got an external usb/ieee1394 drive that works on my Intel machine with options sbp2 serialize_io=1. On UltraSPARC (SunBlade 1000), only USB (1.x) works. With firewire, I get the following in the kern.log: = Jan 2 20:20:27 localhost kernel: ieee1394: Error parsing configrom for node 0-00:1023 Jan 2 20:20:27 localhost kernel: ieee1394: Node changed: 0-00:1023 - 0-01:1023 Jan 2 20:20:36 localhost kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0030e00e8200fe6f] Jan 2 20:20:36 localhost kernel: ieee1394: unsolicited response packet received - no tlabel match Jan 2 20:20:36 localhost kernel: sbp2: $Rev: 1219 $ Ben Collins [EMAIL PROTECTED] Jan 2 20:20:36 localhost kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1) Jan 2 20:20:36 localhost kernel: scsi3 : SCSI emulation for IEEE-1394 SBP-2 Devices Jan 2 20:20:37 localhost kernel: ieee1394: sbp2: Logged into SBP-2 device Jan 2 20:20:37 localhost kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048] Jan 2 20:20:37 localhost kernel: Vendor: WDC WD20 Model: 00JB-00GVA0 Rev: Jan 2 20:20:37 localhost kernel: Type: Direct-Access ANSI SCSI revision: 06 Jan 2 20:20:37 localhost kernel: SCSI device sdc: 390721968 512-byte hdwr sectors (200050 MB) Jan 2 20:20:37 localhost kernel: SCSI device sdc: drive cache: write through Jan 2 20:20:38 localhost kernel: /dev/scsi/host3/bus0/target0/lun0: p1 Jan 2 20:20:38 localhost kernel: Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0 Jan 2 20:21:13 localhost kernel: VFS: Can't find ext3 filesystem on dev sdc1. = and on the console: = sonny:~# mount -t ext3 /dev/sdc1 /mnt/temp mount: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so sonny:~# = I tried with and without options sbp2 serialize_io=1. Additional info: = # lspci :00:00.0 Host bridge: Sun Microsystems Computer Corp. Schizo PCI Bus Module :00:04.0 SCSI storage controller: QLogic Corp. QLA2200 64-bit Fibre Channel Adapter (rev 05) 0001:00:00.0 Host bridge: Sun Microsystems Computer Corp. Schizo PCI Bus Module 0001:00:05.0 Bridge: Sun Microsystems Computer Corp. RIO EBUS (rev 01) 0001:00:05.1 Ethernet controller: Sun Microsystems Computer Corp. RIO GEM (rev 01) 0001:00:05.2 FireWire (IEEE 1394): Sun Microsystems Computer Corp. RIO 1394 (rev 01) 0001:00:05.3 USB Controller: Sun Microsystems Computer Corp. RIO USB (rev 01) 0001:00:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 37) 0001:00:06.1 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 37) # lsmod Module Size Used by usb_storage67024 1 sbp2 25544 0 ipv6 291512 16 evdev 11840 0 eth139422992 0 ohci_hcd 21528 0 sungem 34264 0 sungem_phy 9600 1 sungem ohci1394 39896 0 ieee1394 400408 3 sbp2,eth1394,ohci1394 bbc13296 0 ext3 141472 3 jbd60784 1 ext3 sd_mod 21312 6 qlogicfc 176864 3 sym53c8xx 90816 0 scsi_transport_spi 15552 1 sym53c8xx scsi_mod 94136 6 usb_storage,sbp2,sd_mod,qlogicfc,sym53c8xx,scsi_transport_spi = I'm using the default Debian kernel, as you can see below. Please tell me if you need further info. Thanks in advance. bye, Roland -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: sparc (sparc64) Kernel: Linux 2.6.8-1-sparc64 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Bug#288273: kernel-image-2.6.8-1-sparc64: ieee1394 disk problem on sparc (SunBlade 1000)
On the working i386 setup, it looks like this: Jan 2 20:59:28 atari kernel: ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting... Jan 2 20:59:30 atari kernel: ieee1394: Error parsing configrom for node 0-00:1023 Jan 2 20:59:30 atari kernel: ieee1394: Node changed: 0-00:1023 - 0-01:1023 Jan 2 20:59:38 atari kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0030e00e8200fe6f] Jan 2 20:59:38 atari kernel: ieee1394: unsolicited response packet received - no tlabel match Jan 2 20:59:38 atari kernel: sbp2: $Rev: 1219 $ Ben Collins [EMAIL PROTECTED] Jan 2 20:59:38 atari kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1) Jan 2 20:59:38 atari kernel: scsi2 : SCSI emulation for IEEE-1394 SBP-2 Devices Jan 2 20:59:39 atari kernel: ieee1394: sbp2: Logged into SBP-2 device Jan 2 20:59:39 atari kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048] Jan 2 20:59:39 atari kernel: Vendor: WDC WD20 Model: 00JB-00GVA0 Rev: Jan 2 20:59:39 atari kernel: Type: Direct-Access ANSI SCSI revision: 06 Jan 2 20:59:39 atari kernel: Attached scsi generic sg0 at scsi2, channel 0, id 0, lun 0, type 0 Jan 2 20:59:40 atari kernel: SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB) Jan 2 20:59:40 atari kernel: SCSI device sda: drive cache: write through Jan 2 20:59:40 atari kernel: /dev/scsi/host2/bus0/target0/lun0: p1 Jan 2 20:59:40 atari kernel: Attached scsi disk sda at scsi2, channel 0, id 0, lun 0 Jan 2 21:00:26 atari kernel: kjournald starting. Commit interval 5 seconds Jan 2 21:00:26 atari kernel: EXT3 FS on sda1, internal journal Jan 2 21:00:26 atari kernel: EXT3-fs: mounted filesystem with ordered data mode. Not much different, except the sg0 message. bye, Roland --
Potential netfilter problems?
Hi, FYI: https://coredump.buug.de/pipermail/buug-l/2004-October/000906.html (and follow-ups; sorry, German-only) suggests that there are potential problems with 2.6.9 and netfilter. Is this relevant to us? (Haven't tried yet, just forwarded.) bye, Roland
Bug#245668: [Alsa-devel] Re: Bug#245668: kernel-source-2.6.5: intel8x0: IEC958 output not working anymore
Hi, On Fri, 2004-09-03 at 14:43, Clemens Ladisch wrote: intel8x0: IEC958 digital output (S/PDIF) is said not work since kernel 2.6.4. lsmod: snd_intel8x0 34824 0 i810_audio 33812 0 Don't load the ALSA and OSS drivers at the same time. I don't. This is fixed in the current Debian setup. But the problem in question persists. Does aplay something.wav work? Does aplay -D spdif something.wav work? If not, what happens? $ aplay pub/mi1.wav Playing WAVE 'pub/mi1.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono $ aplay -D spdif pub/mi1.wav Playing WAVE 'pub/mi1.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono aplay: set_params:837: Channels count non available $ The first invocation plays the file, the second returns immediately with the above message. bye, Roland
Bug#240812: Debian #240812 - tg3 problems with NFS
On Thu, 2004-08-19 at 19:29, David S. Miller wrote: Maybe it's checksum offload related. Try: ethtool -K $(DEVICE_NAME) rx off tx off sg off tso off Does that make the problem go away? No.
Bug#245668: [Alsa-devel] Re: Bug#245668: kernel-source-2.6.5: intel8x0: IEC958 output not working anymore
On Fri, 2004-09-03 at 16:23, Takashi Iwai wrote: Does aplay something.wav work? Does aplay -D spdif something.wav work? If not, what happens? $ aplay pub/mi1.wav Playing WAVE 'pub/mi1.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono $ aplay -D spdif pub/mi1.wav Playing WAVE 'pub/mi1.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono aplay: set_params:837: Channels count non available use -D plug:spdif It's nearly like the very first version. Digital output is like muted. When I played around I noticed that gnome-alsamixer segfaults when I _uncheck_ IEC958 during the playback: Thread 1 (Thread 1088226208 (LWP 4234)): #0 0x408ebf1f in snd_mixer_elem_get_type () from /usr/lib/libasound.so.2 #1 0x08050175 in gam_toggle_set_state () #2 0x0804ff50 in gam_toggle_get_type () #3 0x40812121 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #4 0x407fdc20 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #5 0x40811c25 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #6 0x40810be7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #7 0x40810ee4 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #8 0x404b3665 in gtk_toggle_button_toggled () from /usr/lib/libgtk-x11-2.0.so.0 #9 0x404b3a12 in gtk_toggle_button_get_inconsistent () from /usr/lib/libgtk-x11-2.0.so.0 #10 0x40812121 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #11 0x407fdfb7 in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #12 0x407fdc20 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #13 0x4081144e in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #14 0x40810be7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #15 0x40810ee4 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #16 0x4034e215 in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0 #17 0x404b350e in gtk_toggle_button_set_active () from /usr/lib/libgtk-x11-2.0.so.0 #18 0x0804ff50 in gam_toggle_get_type () #19 0x40812121 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #20 0x407fdc20 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #21 0x40811c25 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #22 0x40810be7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #23 0x40810ee4 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #24 0x404b3665 in gtk_toggle_button_toggled () from /usr/lib/libgtk-x11-2.0.so.0 #25 0x404b3a12 in gtk_toggle_button_get_inconsistent () from /usr/lib/libgtk-x11-2.0.so.0 #26 0x40812121 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 [...] from /usr/lib/libgtk-x11-2.0.so.0 #14698 0x40812121 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #14699 0x407fdfb7 in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #14700 0x407fdc20 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 ---Type return to continue, or q return to quit--- #14701 0x4081144e in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #14702 0x40810be7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #14703 0x40810ee4 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #14704 0x4034e215 in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0 #14705 0x404b350e in gtk_toggle_button_set_active () from /usr/lib/libgtk-x11-2.0.so.0 #14706 0x0804ff50 in gam_toggle_get_type () #14707 0x40812121 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #14708 0x407fdc20 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #14709 0x40811c25 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #14710 0x40810be7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #14711 0x40810ee4 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #14712 0x404b3665 in gtk_toggle_button_toggled () from /usr/lib/libgtk-x11-2.0.so.0 #14713 0x404b3a12 in gtk_toggle_button_get_inconsistent () from /usr/lib/libgtk-x11-2.0.so.0 #14714 0x40812121 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #14715 0x407fdfb7 in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #14716 0x407fdc20 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #14717 0x4081144e in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #14718 0x40810be7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 ---Type return to continue, or q return to quit--- #14719 0x40810ee4 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #14720 0x4034e215 in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0 #14721 0x404b350e in gtk_toggle_button_set_active () from /usr/lib/libgtk-x11-2.0.so.0 #14722 0x0804ff50 in gam_toggle_get_type () #14723 0x40812121 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 Stack overflow? This doesn't occur without the -D [...] option. bye, Roland
Re: How to prevent modules from being loaded
On Tue, 2004-08-31 at 13:00, Sven Luther wrote: a while ago, I asked the kernel maintainer how to prevent modules from being loaded since now we have hotplug etc. that loads everything that sticks to the kernel. Using hotplug or discover* blacklists? I'm using hotplug. Adding snd or snd_intel8x0 to /etc/hotplug/blacklist or /etc/hotplug/blacklist.d/local doesn't help here. All the snd modules are loaded after bootup as before. Like said, there are three things involved here : discover* There's no discover* on this machine. So no danger from this direction. Right? hotplug Done. magic also module loading. Which magic do you mean? Please teach me some. :) Thanks. bye, Roland
Re: How to prevent modules from being loaded
On Tue, 2004-08-31 at 15:06, Sven Luther wrote: There's no discover* on this machine. So no danger from this direction. Right? Discover is part of the base system though. debootstrap doesn't install it, so what do you mean with this? Sure, it installs discover1. Where? atari:/usr/lib/debootstrap# grep -r discover * atari:/usr/lib/debootstrap# atari:/home/ernie/temp# debootstrap sid sid ftp://sbo/debmirror/debian/ [...] atari:/home/ernie/temp# chroot sid atari:/# dpkg -l '*discover*' No packages found matching *discover*. atari:/# What does this mean?
How to prevent modules from being loaded
Hi, a while ago, I asked the kernel maintainer how to prevent modules from being loaded since now we have hotplug etc. that loads everything that sticks to the kernel. He taught me to set an alias to some nonexistent device. An ugly hack, but it worked. Now, not even this works for me: alias snd xxx leads to snd being loaded at boot time, but later I get: # modprobe snd FATAL: Module xxx not found. # So I need a new solution. Any idea? Thanks. bye, Roland
Bug#245668: kernel-source-2.6.5: intel8x0: IEC958 output not working anymore
On Sun, 2004-08-29 at 15:00, maks attems wrote: bug could be already closed as concerning self-compiled. please retry with current stock debian kernel-images for 2.6.8 and report back. The problem persists. bye, Roland
