Bug#1052714: firmware-amd-graphics: Missing firmware for AMD Radeon RX 7000 series cards
I'd like to ping this issue. Just installed a RX 7700 XT and needed to manually download a bunch of firmware files from the upstream repo to get it to work. I am on unstable, Is there anything a user (me) can do to help here? What is needed to get this package up to date? I saw a little update in the git repo, but it does not look like an update to a newer linux-firmware version? Regards Andre
Bug#939986: (no subject)
Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=205005
Bug#939986: (no subject)
salsa is down, but assuming net/wireless/nl80211.c is unpatched, it's
running into this:
/* a self-managed-reg device must have a private regdom */
if (WARN_ON(!regdom && self_managed)) {
nlmsg_free(msg);
return -EINVAL;
}
Any ideas?
Bug#939986: (no subject)
previous post was with 5.3~rc5-1~exp2, so it happens there too. with 5.2.0-2-amd64 it's the same though: [3.938929] [ cut here ] [3.938979] WARNING: CPU: 1 PID: 551 at net/wireless/nl80211.c:6859 nl80211_get_reg_do+0x1fc/0x210 [cfg80211] [3.938980] Modules linked in: cmac bnep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic ghash_clmulni_intel ledtrig_audio binfmt_misc arc4 nls_ascii btusb nls_cp437 btrtl btbcm btintel vfat bluetooth fat snd_soc_skl iwlmvm i915 snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi mac80211 snd_soc_core snd_compress aesni_intel snd_hda_intel snd_hda_codec iwlwifi aes_x86_64 uvcvideo crypto_simd snd_hda_core cryptd drbg glue_helper rtsx_usb_ms videobuf2_vmalloc drm_kms_helper snd_hwdep videobuf2_memops videobuf2_v4l2 intel_cstate videobuf2_common snd_pcm intel_uncore memstick ansi_cprng videodev drm cfg80211 efi_pstore intel_rapl_perf snd_timer ecdh_generic ecc iTCO_wdt iTCO_vendor_support media sg watchdog evdev joydev i2c_algo_bit intel_pch_thermal snd soundcore ideapad_laptop sparse_keymap serio_raw efivars pcspkr [3.939007] intel_wmi_thunderbolt rfkill battery pcc_cpufreq acpi_pad ac button sunrpc efivarfs ip_tables x_tables autofs4 ext4 rtsx_usb_sdmmc mmc_core crc16 rtsx_usb mbcache mfd_core jbd2 crc32c_generic sr_mod cdrom sd_mod xhci_pci xhci_hcd ahci libahci libata crc32c_intel psmouse usbcore r8169 scsi_mod realtek libphy i2c_i801 usb_common wmi video [3.939023] CPU: 1 PID: 551 Comm: wpa_supplicant Tainted: GW 5.2.0-2-amd64 #1 Debian 5.2.9-2 [3.939024] Hardware name: LENOVO 80RJ/Lenovo B71-80, BIOS 0RCN35WW 12/03/2015 [3.939043] RIP: 0010:nl80211_get_reg_do+0x1fc/0x210 [cfg80211] [3.939045] Code: ff 48 89 ef e8 c5 a5 2d de b8 a6 ff ff ff eb 89 eb ef b8 97 ff ff ff eb 80 e8 70 04 d7 dd 48 c7 c7 08 18 95 c0 e8 b2 81 dd dd <0f> 0b 48 89 ef e8 9a a5 2d de b8 ea ff ff ff e9 5b ff ff ff 0f 1f [3.939046] RSP: 0018:a59781dc3ac8 EFLAGS: 00010246 [3.939047] RAX: 0024 RBX: RCX: [3.939048] RDX: RSI: 9a7ba2297688 RDI: 9a7ba2297688 [3.939049] RBP: 9a7b9e5f4a00 R08: 0364 R09: 0004 [3.939050] R10: R11: 0001 R12: a59781dc3b50 [3.939051] R13: 9a7b9e07f014 R14: 0001 R15: 9a7b9d7a4300 [3.939052] FS: 7fb70bc70800() GS:9a7ba228() knlGS: [3.939053] CS: 0010 DS: ES: CR0: 80050033 [3.939054] CR2: 55f02b69a038 CR3: 0004596bc005 CR4: 003606e0 [3.939055] Call Trace: [3.939060] ? _cond_resched+0x15/0x30 [3.939064] genl_family_rcv_msg+0x1d2/0x410 [3.939067] ? __alloc_pages_nodemask+0x163/0x310 [3.939069] genl_rcv_msg+0x47/0x8c [3.939071] ? __kmalloc_node_track_caller+0x1cb/0x290 [3.939073] ? genl_family_rcv_msg+0x410/0x410 [3.939074] netlink_rcv_skb+0x49/0x110 [3.939076] genl_rcv+0x24/0x40 [3.939077] netlink_unicast+0x17e/0x200 [3.939079] netlink_sendmsg+0x204/0x3d0 [3.939082] sock_sendmsg+0x4c/0x50 [3.939084] ___sys_sendmsg+0x29f/0x300 [3.939085] ? ___sys_recvmsg+0x16c/0x200 [3.939088] ? mem_cgroup_commit_charge+0x80/0x4d0 [3.939089] ? mem_cgroup_try_charge+0x86/0x190 [3.939092] ? __handle_mm_fault+0xa98/0x1280 [3.939094] __sys_sendmsg+0x57/0xa0 [3.939097] do_syscall_64+0x53/0x130 [3.939099] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [3.939101] RIP: 0033:0x7fb70bfc2744 [3.939102] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 48 8d 05 99 3c 0c 00 8b 00 85 c0 75 13 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 89 54 24 1c 48 89 [3.939103] RSP: 002b:7fff96501ff8 EFLAGS: 0246 ORIG_RAX: 002e [3.939105] RAX: ffda RBX: 55f02b663480 RCX: 7fb70bfc2744 [3.939106] RDX: RSI: 7fff96502030 RDI: 0004 [3.939106] RBP: 55f02b693f00 R08: 0004 R09: 55f02b697dc0 [3.939107] R10: 7fff96502104 R11: 0246 R12: 55f02b663390 [3.939108] R13: 7fff96502030 R14: 7fff96502160 R15: 7fff96502104 [3.939110] ---[ end trace 260d0e5afec60bed ]---
Bug#939986: (no subject)
reopen 939986 I get the very same crash :( [3.877660] [ cut here ] [3.877711] WARNING: CPU: 1 PID: 551 at net/wireless/nl80211.c:6865 nl80211_get_reg_do+0x1fc/0x210 [cfg80211] [3.877712] Modules linked in: cmac bnep intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi ghash_clmulni_intel snd_hda_codec_conexant snd_hda_codec_generic ledtrig_audio snd_soc_skl binfmt_misc iwlmvm snd_soc_skl_ipc snd_soc_sst_ipc btusb snd_soc_sst_dsp btrtl btbcm snd_hda_ext_core btintel nls_ascii nls_cp437 uvcvideo snd_soc_acpi_intel_match mac80211 videobuf2_vmalloc bluetooth vfat videobuf2_memops aesni_intel snd_soc_acpi i915 fat libarc4 videobuf2_v4l2 aes_x86_64 crypto_simd snd_soc_core snd_compress cryptd glue_helper snd_hda_intel iwlwifi intel_cstate videobuf2_common snd_hda_codec drbg drm_kms_helper efi_pstore videodev snd_hda_core intel_uncore snd_hwdep mc ansi_cprng drm cfg80211 snd_pcm intel_rapl_perf rtsx_usb_ms memstick snd_timer iTCO_wdt iTCO_vendor_support evdev snd ecdh_generic joydev sg pcspkr watchdog serio_raw ecc efivars intel_wmi_thunderbolt intel_pch_thermal [3.877740] soundcore i2c_algo_bit ideapad_laptop sparse_keymap rfkill battery acpi_pad ac button sunrpc efivarfs ip_tables x_tables autofs4 rtsx_usb_sdmmc mmc_core ext4 rtsx_usb mfd_core crc16 mbcache jbd2 crc32c_generic sr_mod cdrom sd_mod xhci_pci xhci_hcd ahci libahci libata r8169 usbcore crc32c_intel realtek libphy scsi_mod psmouse usb_common i2c_i801 wmi video [3.877758] CPU: 1 PID: 551 Comm: wpa_supplicant Tainted: GW 5.3.0-rc5-amd64 #1 Debian 5.3~rc5-1~exp2 [3.877759] Hardware name: LENOVO 80RJ/Lenovo B71-80, BIOS 0RCN35WW 12/03/2015 [3.89] RIP: 0010:nl80211_get_reg_do+0x1fc/0x210 [cfg80211] [3.877780] Code: ff 48 89 ef e8 75 d6 86 fb b8 a6 ff ff ff eb 89 eb ef b8 97 ff ff ff eb 80 e8 30 71 2f fb 48 c7 c7 a8 b8 7c c0 e8 52 ee 35 fb <0f> 0b 48 89 ef e8 4a d6 86 fb b8 ea ff ff ff e9 5b ff ff ff 0f 1f [3.877781] RSP: 0018:b22d0051bac0 EFLAGS: 00010246 [3.877783] RAX: 0024 RBX: RCX: [3.877784] RDX: RSI: 8a2762297688 RDI: 8a2762297688 [3.877785] RBP: 8a2759715f00 R08: 0364 R09: 0004 [3.877785] R10: R11: 0001 R12: b22d0051bb48 [3.877786] R13: 8a2759b02014 R14: 0001 R15: 8a275a6d0300 [3.877788] FS: 7f47d4411800() GS:8a276228() knlGS: [3.877789] CS: 0010 DS: ES: CR0: 80050033 [3.877790] CR2: 5645fc5b4038 CR3: 00045a4e0005 CR4: 003606e0 [3.877791] Call Trace: [3.877796] ? _cond_resched+0x15/0x30 [3.877800] genl_family_rcv_msg+0x1d2/0x410 [3.877803] ? __alloc_pages_nodemask+0x163/0x310 [3.877806] genl_rcv_msg+0x47/0x90 [3.877808] ? __kmalloc_node_track_caller+0x1b5/0x2f0 [3.877810] ? genl_family_rcv_msg+0x410/0x410 [3.877812] netlink_rcv_skb+0x49/0x110 [3.877815] genl_rcv+0x24/0x40 [3.877816] netlink_unicast+0x17e/0x200 [3.877819] netlink_sendmsg+0x210/0x3d0 [3.877822] sock_sendmsg+0x5b/0x60 [3.877824] ___sys_sendmsg+0x29f/0x320 [3.877826] ? ___sys_recvmsg+0x16c/0x200 [3.877829] ? mem_cgroup_commit_charge+0x61/0x4c0 [3.877831] ? mem_cgroup_try_charge+0x6a/0x190 [3.877833] ? __handle_mm_fault+0xa92/0x1280 [3.877836] ? __cgroup_bpf_run_filter_setsockopt+0xba/0x2e0 [3.877837] __sys_sendmsg+0x57/0xa0 [3.877841] do_syscall_64+0x53/0x130 [3.877844] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [3.877846] RIP: 0033:0x7f47d4763744 [3.877847] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 48 8d 05 99 3c 0c 00 8b 00 85 c0 75 13 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 89 54 24 1c 48 89 [3.877848] RSP: 002b:7fff1c3915d8 EFLAGS: 0246 ORIG_RAX: 002e [3.877850] RAX: ffda RBX: 5645fc57d480 RCX: 7f47d4763744 [3.877851] RDX: RSI: 7fff1c391610 RDI: 0004 [3.877851] RBP: 5645fc5adf00 R08: 0004 R09: 5645fc5b1dc0 [3.877852] R10: 7fff1c3916e4 R11: 0246 R12: 5645fc57d390 [3.877853] R13: 7fff1c391610 R14: 7fff1c391740 R15: 7fff1c3916e4 [3.877858] ---[ end trace 3f3d716d44a8ac03 ]---
Bug#920809: [src:linux] Please enable CONFIG_CAN_PEAK_PCIEFD as module
Hi again. I created a patch (attached) against the current master of https://salsa.debian.org/kernel-team/linux If you prefer git as a source then here's a pull-request for the same repository: The following changes since commit 03e2a159aaa286ed569e561f5e9a1804a0ccf03c: Update to 4.20.5 (2019-01-28 16:15:01 +0100) are available in the Git repository at: https://git.nautsch.de/git/nautsch/linux-debian.git master for you to fetch changes up to 33b8506cc7b3a616ad9d6f2b7f55ebdbc7193f88: enable CAN_PEAK_PCIEFD (2019-02-05 09:21:58 +0100) Andre Naujoks (1): enable CAN_PEAK_PCIEFD debian/config/config | 5 + 1 file changed, 5 insertions(+) Regards Andre From 33b8506cc7b3a616ad9d6f2b7f55ebdbc7193f88 Mon Sep 17 00:00:00 2001 From: Andre Naujoks Date: Tue, 5 Feb 2019 09:21:58 +0100 Subject: [PATCH] enable CAN_PEAK_PCIEFD --- debian/config/config | 5 + 1 file changed, 5 insertions(+) diff --git a/debian/config/config b/debian/config/config index a92295d9b44a..68f77c424d6d 100644 --- a/debian/config/config +++ b/debian/config/config @@ -2897,6 +2897,11 @@ CONFIG_CAN_CALC_BITTIMING=y ## # CONFIG_CAN_M_CAN is not set +## +## file: drivers/net/can/peak_canfd/Kconfig +## +CONFIG_CAN_PEAK_PCIEFD=m + ## ## file: drivers/net/can/sja1000/Kconfig ## -- 2.20.1
Bug#920809: [src:linux] Please enable CONFIG_CAN_PEAK_PCIEFD as module
Package: src:linux Version: 4.19.16-1 Severity: normal --- Please enter the report below this line. --- Hi. Would it be possible to enable CONFIG_CAN_PEAK_PCIEFD as a kernel module in upcoming kernels? It is a device driver for a PCI express CAN Bus adapter. Thanks in advance Regards Andre --- System information. --- Architecture: Kernel: Linux 4.19.0-2-amd64 Debian Release: buster/sid 500 unstable-debug debug.mirrors.debian.org 500 unstable deb.debian.org 1 experimental-debug deb.debian.org 1 experimentaldeb.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#917939: please enable CONFIG_ARM_ARMADA_37XX_CPUFREQ for arm64
On Sat, 19 Jan 2019 17:04:43 +0900 Hideki Yamane wrote: Hi, On Tue, 1 Jan 2019 10:27:00 +0100 Andre Heider wrote: > Source: linux > Version: 4.19.12-1 > Severity: wishlist > > Hi, > > this option is missing for cpu frequency scaling on e.g. my espressobin. arch/arm64/configs/defconfig seems to have it in 4.19.12-1 to me. $ grep CONFIG_ARM_ARMADA_37XX_CPUFREQ -r ./ ./arch/arm64/configs/defconfig:CONFIG_ARM_ARMADA_37XX_CPUFREQ=y ./drivers/cpufreq/Makefile:obj-$(CONFIG_ARM_ARMADA_37XX_CPUFREQ)+= armada-37xx-cpufreq.o Yes, that's the upstream defconfig, it's just missing for Debian. Could we please get that option? Pretty please? :)
Bug#917939: please enable CONFIG_ARM_ARMADA_37XX_CPUFREQ for arm64
Source: linux Version: 4.19.12-1 Severity: wishlist Hi, this option is missing for cpu frequency scaling on e.g. my espressobin. According to [0], 4.19 should be ready for cpufreq on this platform. The mentioned AVS support doesn't seem to have an additional config knob, or at least I didn't see one. [0] https://elinux.org/Marvell_EBU:Mainline_Linux Thanks! Andre
Bug#888817: arm64: please enable CONFIG_PCI_TEGRA
Source: linux Version: 4.14.0-3-arm64 Severity: wishlist Hi, this is for the tegra pcie controller, as found on e.g. the jetson tx1: https://elinux.org/Jetson_TX1 Thanks, Andre
Bug#886983: arm64: please enable CONFIG_I2C_PXA
Source: linux Version: 4.14.0-3-arm64 Severity: wishlist Hi, this is for the i2c host controller on mvebu, like espressobin. Thanks, Andre
Bug#869028: linux-image-4.12.0-trunk: Please enable CONFIG_IOSCHED_BFQ
Source: linux Version: 4.12.0-trunk Severity: wishlist Hi, new blq-mq i/o scheduler in 4.12, please enable. Thanks, Andre
Bug#836255: DTBs are no longer bundled
Source: linux Version: 4.7.0-1-armmp-lpae Severity: important Hi, starting with 4.7 the DTBs are not part of the package anymore: # dpkg -L linux-image-4.5.0-2-armmp-lpae|grep dtb|wc -l 349 # dpkg -L linux-image-4.6.0-1-armmp-lpae|grep dtb|wc -l 363 # dpkg -L linux-image-4.7.0-1-armmp-lpae|grep dtb|wc -l 0 which in return makes flash-kernel fail, and the kernel can not be properly booted (on devices depending on flash-kernel).
Bug#823493: Cubieboard2 also affected
Hi, there's finally a v4.5 fix available, see [0]: > v4 fixes for 4.5 are here: > > https://patchwork.ozlabs.org/patch/598195/ (revert) > https://patchwork.ozlabs.org/patch/598196/ Those two didn't make it to v4.5.5, but please incude these, stmmac is broken for 5 debian kernel releases already. Thanks, Andre [0] https://www.spinics.net/lists/netdev/msg369626.html
Bug#818174: Please enable powerplay for amdgpu
Source: linux Version: 4.5~rc7-1~exp1 Severity: wishlist Hi, powerplay is the power management for the amdgpu driver. On top of the config switch this feature used to be hidden behind an additional kernel module parameter. As of v4.5 it looks like it's enabled per default for the families 'tonga' and 'fiji', but need to be enabled via the kernel cmdline for 'carrizo' and 'stoney', see [0]. Please enable CONFIG_DRM_AMD_POWERPLAY. Thanks, Andre [0] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c?id=refs/tags/v4.5#n95
Bug#808623: Please enable new sunxi drivers
Source: linux Version: 4.4~rc5-1~exp1 Severity: wishlist Hi, 4.4 mainline merged new sunxi drivers, two not yet enabled: * CAN controller (CONFIG_CAN_SUN4I) * Audio codec (CONFIG_SND_SUN4I_CODEC) Please enable. Thanks, Andre
Bug#808625: Module sun4i-ss fails to load
Source: linux Version: 4.4~rc5-1~exp1 Severity: bug Hi, the new module fails to load: [ 13.879728] sun4i-ss 1c15000.crypto-engine: no reset control found [ 13.887548] sun4i-ss 1c15000.crypto-engine: Die ID 0 [ 13.892618] sun4i-ss 1c15000.crypto-engine: Fail to register md5 [ 13.898809] sun4i-ss: probe of 1c15000.crypto-engine failed with error -22 There's an upstream bug about it [0], and while the fix didn't yet land in master nor stable, it is currently found in next [1]. Thanks, Andre [0] https://bugzilla.kernel.org/show_bug.cgi?id=107281 [1] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f9ea86604e3ba64edd2817795798168fbb3c1a6
Bug#808623:
And another driver not yet enabled: "X-Powers AXP20X power button driver" (CONFIG_INPUT_AXP20X_PEK), which was merged for 4.0 already
Bug#804856: Please enable new sunxi drivers
Source: linux Version: 4.3-1~exp1 Severity: wishlist Hi, 4.3 mainline merged new sunxi drivers, two not yet enabled: * the USB OTG controller (CONFIG_USB_MUSB_SUNXI) * support for the Security System crypto accelerator (CONFIG_CRYPTO_DEV_SUN4I_SS) Please enable. Thanks, Andre
Bug#784688: Thousands of "xen:balloon: Cannot add additional memory (-17) messages" despite dom0 ballooning disabled
Hello, I'm seeing the same. After a fresh boot before starting any guests xl shows: root@tank0:~# xl list 0 NameID Mem VCPUs State Time(s) Domain-0 0 4096 8 r- 8.4 I did run "xl mem-set 0 4096" then started an guest. This produced a load of the "xen:balloon: Cannot add additional memory (-17)" messages. xl now shows: root@tank0:~# xl list 0 NameID Mem VCPUs State Time(s) Domain-0 0 4094 8 r- 24.4 Runnig "xl mem-set 0 4094" after the guest had started seems to have stopped the messages for the moment. (not running mem-set at this point continued to produce the messages in some frequent irregular intervalls) Xen options are "dom0_mem=4096M,max:4096M" . Dom0 linux kernel options are "mem=4096" . xl.conf got autoballoon="off" . Have a nice day, Andre
Bug#792388:
I noticed the commit, thx Ian! I only own a beaglebone black, so not all drivers are of interest there, but unless there's a reason not to: please enable. Hah, I also own a couple of other devices unrelated to sunxi, but what I really meant is my cubieboard 2 :P -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAHsu+b9qhcgqNFdh+Nm=6kw5upR=3j9qzvcjjrqno-fhsnd...@mail.gmail.com
Bug#792388: Please enable the latest sunxi drivers for armmp(-lpae)
Source: linux Version: 4.1.2-1~exp1 Severity: wishlist Hi, there're a couple of new mainline drivers missing for sunxi: MTD_NAND_SUNXI EEPROM_SUNXI_SID KEYBOARD_SUN4I_LRADC SERIO_SUN4I_PS2 I2C_SUN6I_P2WI SPI_SUN4I IR_SUNXI RTC_DRV_SUN6I DMA_SUN6I PWM_SUN4I PHY_SUN9I_USB I only own a beaglebone black, so not all drivers are of interest there, but unless there's a reason not to: please enable. Thanks, Andre -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cahsu+b9octrad3kzmejakunhbrk_k60fm058tnlai69qni2...@mail.gmail.com
Bug#781548: Support for HP SmartArray Gen9 Cards
Package: linux-image-3.2.0-4-amd64
Version: 3.2.65-1+deb7u2
Hi,
nowadays wheezy kernel cant boot on Gen9 HP Servers because of the new PCI
ids of Smart Array Cards, the patch attached solves the problem
supporting the new Gen9 Cards
HTH
diff -uNr a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
--- a/drivers/scsi/hpsa.c 2014-12-14 16:24:02.0 +
+++ b/drivers/scsi/hpsa.c 2015-03-26 22:19:29.907717557 +
@@ -107,6 +107,19 @@
{PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSH, 0x103C, 0x1926},
{PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSH, 0x103C, 0x1928},
{PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSF, 0x103C, 0x334d},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSH, 0x103C, 0x1929},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21BD},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21BE},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21BF},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C0},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C1},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C2},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C3},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C4},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C5},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C7},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C8},
+ {PCI_VENDOR_ID_HP, PCI_DEVICE_ID_HP_CISSI, 0x103C, 0x21C9},
{PCI_VENDOR_ID_HP, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
PCI_CLASS_STORAGE_RAID 8, 0x 8, 0},
{0,}
@@ -142,6 +155,18 @@
{0x1926103C, Smart Array, SA5_access},
{0x1928103C, Smart Array, SA5_access},
{0x334d103C, Smart Array P822se, SA5_access},
+{0x21BD103C, Smart Array, SA5_access},
+{0x21BE103C, Smart Array, SA5_access},
+{0x21BF103C, Smart Array, SA5_access},
+{0x21C0103C, Smart Array, SA5_access},
+{0x21C1103C, Smart Array, SA5_access},
+{0x21C2103C, Smart Array, SA5_access},
+{0x21C3103C, Smart Array, SA5_access},
+{0x21C4103C, Smart Array, SA5_access},
+{0x21C5103C, Smart Array, SA5_access},
+{0x21C7103C, Smart Array, SA5_access},
+{0x21C8103C, Smart Array, SA5_access},
+{0x21C9103C, Smart Array, SA5_access},
{0x103C, Unknown Smart Array, SA5_access},
};
diff -uNr a/include/linux/pci_ids.h b/include/linux/pci_ids.h
--- a/include/linux/pci_ids.h 2014-12-14 16:24:02.0 +
+++ b/include/linux/pci_ids.h 2015-03-26 22:19:01.498077026 +
@@ -753,6 +753,7 @@
#define PCI_DEVICE_ID_HP_CISSE 0x323a
#define PCI_DEVICE_ID_HP_CISSF 0x323b
#define PCI_DEVICE_ID_HP_CISSH 0x323c
+#define PCI_DEVICE_ID_HP_CISSI 0x3239
#define PCI_DEVICE_ID_HP_ZX2_IOC 0x4031
#define PCI_VENDOR_ID_PCTECH 0x1042
Bug#594697: Xen 4/Linux 2.6.32-5-xen (Squeeze testing): Bridged PV Guests Crash Upon Autostart
Original-Nachricht Datum: Sat, 28 Aug 2010 14:50:24 +0100 Von: Ian Campbell i...@hellion.org.uk An: andr...@gmx.net, 594...@bugs.debian.org Betreff: Re: Bug#594697: Xen 4/Linux 2.6.32-5-xen (Squeeze testing): Bridged PV Guests Crash Upon Autostart On Sat, 2010-08-28 at 15:27 +0200, andr...@gmx.net wrote: Package: linux-image-2.6.32-5-xen-amd64/xen-hypervisor-4.0-amd64/udev Version: 2.6.32-5/4.0.1-rc5/160 The curent Squeeze Xen versions do not work with the current Squeeze udev version. Paravirtualised guests do not autostart. In other words, after creating DomUs with xen-create-image and xm create, if you reboot Dom0, all DomUs will crash and consume maximum CPU time due to known Xen bug #1612. This is a significant limitation, since a system will never automatically reboot to its previous state. According to Xen bug #1612, one solution would be to significantly upgrade to a newer kernel version, or to otherwise path the kernel accordingly. The other solution would be to revert back to udev 151. See http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612 for reference. Thank you for all the work you do! I believe the fix for this is in the 2.6.32-21 kernel currently present in Sid. Ian. Thank you for pointing this out. I was able to install Sid-Xen (linux-image-*-xen, xen-tools, xen-utils) on top of a non-Xen Squeeze. Problem solved. Will Squeeze use 2.6.32.21, too? -- GMX DSL SOMMER-SPECIAL: Surf Phone Flat 16.000 für nur 19,99 ¿/mtl.!* http://portal.gmx.net/de/go/dsl -- 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/20100829173726.288...@gmx.net
Bug#594697: Xen 4/Linux 2.6.32-5-xen (Squeeze testing): Bridged PV Guests Crash Upon Autostart
Package: linux-image-2.6.32-5-xen-amd64/xen-hypervisor-4.0-amd64/udev Version: 2.6.32-5/4.0.1-rc5/160 The curent Squeeze Xen versions do not work with the current Squeeze udev version. Paravirtualised guests do not autostart. In other words, after creating DomUs with xen-create-image and xm create, if you reboot Dom0, all DomUs will crash and consume maximum CPU time due to known Xen bug #1612. This is a significant limitation, since a system will never automatically reboot to its previous state. According to Xen bug #1612, one solution would be to significantly upgrade to a newer kernel version, or to otherwise path the kernel accordingly. The other solution would be to revert back to udev 151. See http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612 for reference. Thank you for all the work you do! -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- 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/20100828132754.24...@gmx.net
Bug#582481: [pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
Hi, if it is a bug in udev, why does the system start with the old initramfs? Greetings, Andre Pawlowski --- Die Schriftsteller können nicht so schnell schreiben, wie die Regierungen Kriege machen, denn das Schreiben verlangt Denkarbeit. -Bertolt Brecht On 05/22/2010 01:13 PM, Jonas Meurer wrote: hey, On 21/05/2010 maximilian attems wrote: On Fri, 21 May 2010, Andre Pawlowski wrote: This bugreport was written with the initrd.img-2.6.32-trunk-amd64.bak before updating yesterday to initramfs-tools 0.94.4. I have an encrytped lvm which contains every partition except /boot. It was created by the Debian squeeze setup when I installed the system. Today I tried to boot the system with the new initramfs-tools and after I entered the password I get this message: kernel-provided name 'dm-0' and NAME='/mapper/sda2_crypt' disagree, please use SYMLINK+= or change the kernel to provide the proper name This bug appears after I upgraded libudev0 udev insserv groff-base initramfs-tools libglib2.0-0 libglib2.0-dev libglib2.0-data libgps19 libgudev-1.0-0 libjack0 libschroedinger-1.0-0 libwebkit-1.0-common libwebkit-1.0-2 xserver-xorg-video-intel xterm because I only changed the initrd.img and after that I could boot the system again I think it is a bug in initramfs-tools. no we dont set udev symlinks, so it is either a crytsetup or an udev bug. i strongly believe it's a udev bug. the same warnings appear on my system since last udev upgrade. the apear both at cryptdisks and lvm initscript invokation. didn't have time to further investigate it though. greetings, jonas -- 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/4bfb6428.5050...@h4des.org
Bug#582481: [pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
Today I could copy all the output the error does. Here is what the system shows when I boot with the new initrd.img-2.6.32-trunk-amd64: Loading, please wait... Volume group laptop-vg not found Skipping volume group laptop-vg Unable to find LVM volume laptop-vg/root Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: udevd-work[422]: kernel-provided name 'dm-0' and NAME= 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or change the kernel to provide the proper name udevd-work[422]: kernel-provided name 'dm-0' and NAME= 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or change the kernel to provide the proper name No key available with this passphrase cryptsetup: cryptsetup failed, bad password or options? Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: Ok, now the output when I use the initrd.img-2.6.32-trunk-amd64.bak: Loading, please wait... Volume group laptop-vg not found Skipping volume group hantuch-vg Unable to find LVM volume laptop-vg/root Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: Key slot 0 unlocked [normal booting output follows] The system is up to date with the newest squeeze packets. Regards Andre Pawlowski --- Warum fallen wir? Damit wir lernen können, uns wieder aufzurappeln. -Batman Begins (Thomas Wayne) On 05/25/2010 08:59 AM, maximilian attems wrote: tags 582481 moreinfo stop On Tue, May 25, 2010 at 07:46:16AM +0200, Andre Pawlowski wrote: Hi, if it is a bug in udev, why does the system start with the old initramfs? dude you have not provided the error message or presumed failure of the new initramfs!? how about telling that as a start. can you still reproduce it with latest initramfs-tools? thanks. -- 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/4bfbaff0.40...@h4des.org
Bug#582481: [pkg-cryptsetup-devel] Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
I've found it. It wasn't an error in the initramfs-tools. The idea came to me when I logged on to a system via RDP. I use a german keyboard and a us layout. The layout changed with the new initramfs-tools and so the keys I entered where wrong. It's definitely no bug. I'm sorry for causing troubles. At the moment I worked with the new initrd image. Thanks Andre Pawlowski --- Vorstellungskraft ist wichtiger als Wissen, denn Wissen ist Begrenzt. -Albert Einstein On 05/25/2010 01:22 PM, Jonas Meurer wrote: hey andre, On 25/05/2010 Andre Pawlowski wrote: Today I could copy all the output the error does. thanks, let's see ... Here is what the system shows when I boot with the new initrd.img-2.6.32-trunk-amd64: Loading, please wait... Volume group laptop-vg not found Skipping volume group laptop-vg Unable to find LVM volume laptop-vg/root Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: udevd-work[422]: kernel-provided name 'dm-0' and NAME= 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or change the kernel to provide the proper name udevd-work[422]: kernel-provided name 'dm-0' and NAME= 'mapper/temporary-cryptsetup-414' disagree, please use SYMLINK+= or change the kernel to provide the proper name No key available with this passphrase cryptsetup: cryptsetup failed, bad password or options? Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: did you try to submit the correct passphrase at all? as already written, these udevd-work messages are just warnings, they shouldn't have any impact on the functionality after all. in fact, they appear on my system as well since last udev upgrade. but unlocking the disk still works. Ok, now the output when I use the initrd.img-2.6.32-trunk-amd64.bak: Loading, please wait... Volume group laptop-vg not found Skipping volume group hantuch-vg Unable to find LVM volume laptop-vg/root Unlocking the disk /dev/disk/by-uuid/e7bf2609-7a87-447c-9827-694bc164debb (sda2_crypt) Enter passphrase: Key slot 0 unlocked [normal booting output follows] The system is up to date with the newest squeeze packets. so unlocking the disk works with old initramfs, while it fails with the new initramfs (ignoring the udev warnings)? or does it work with the new initramfs as well, despite cluttering the passphrase prompt with udev warnings? in the former case you most probably spotted another bug (or misconfigured your system), in the latter case this bugreport should be reassigned to package dmsetup, where the respective udev rules need to be updated. greetings, jonas -- 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/4bfbfeab.4090...@h4des.org
Bug#582481: initramfs-tools: System won't boot anymore if it was encrypted by debian squeeze setup
Package: initramfs-tools Version: 0.94.4 Severity: important This bugreport was written with the initrd.img-2.6.32-trunk-amd64.bak before updating yesterday to initramfs-tools 0.94.4. I have an encrytped lvm which contains every partition except /boot. It was created by the Debian squeeze setup when I installed the system. Today I tried to boot the system with the new initramfs-tools and after I entered the password I get this message: kernel-provided name 'dm-0' and NAME='/mapper/sda2_crypt' disagree, please use SYMLINK+= or change the kernel to provide the proper name This bug appears after I upgraded libudev0 udev insserv groff-base initramfs-tools libglib2.0-0 libglib2.0-dev libglib2.0-data libgps19 libgudev-1.0-0 libjack0 libschroedinger-1.0-0 libwebkit-1.0-common libwebkit-1.0-2 xserver-xorg-video-intel xterm because I only changed the initrd.img and after that I could boot the system again I think it is a bug in initramfs-tools. -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.32-trunk-amd64 root=/dev/mapper/handtuch--vg-root ro quiet -- /proc/filesystems ext4 fuseblk -- lsmod Module Size Used by nf_conntrack_ipv4 9817 2 nf_defrag_ipv4 1139 1 nf_conntrack_ipv4 xt_state1303 2 nf_conntrack 46359 2 nf_conntrack_ipv4,xt_state xt_tcpudp 2319 2 iptable_filter 2258 1 ip_tables 13899 1 iptable_filter x_tables 12813 3 xt_state,xt_tcpudp,ip_tables vboxnetadp 4225 0 vboxnetflt 9978 0 vboxdrv 1710854 2 vboxnetadp,vboxnetflt fuse 50078 1 loop 11767 0 firewire_sbp2 11450 0 snd_hda_codec_conexant21789 1 joydev 8411 0 snd_hda_intel 18147 0 arc41274 2 ecb 1841 2 snd_hda_codec 54212 2 snd_hda_codec_conexant,snd_hda_intel snd_hwdep 5364 1 snd_hda_codec snd_pcm_oss32399 0 snd_mixer_oss 12606 1 snd_pcm_oss iwlagn 71452 0 iwlcore77494 1 iwlagn snd_pcm60615 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi4208 0 snd_rawmidi15291 1 snd_seq_midi snd_seq_midi_event 4628 1 snd_seq_midi snd_seq42769 2 snd_seq_midi,snd_seq_midi_event mac80211 135407 2 iwlagn,iwlcore snd_timer 15502 2 snd_pcm,snd_seq pcmcia 19426 0 uvcvideo 51663 0 cfg80211 101253 3 iwlagn,iwlcore,mac80211 videodev 29977 1 uvcvideo thinkpad_acpi 50043 0 yenta_socket 19051 1 v4l1_compat11442 2 uvcvideo,videodev rsrc_nonstatic 7294 1 yenta_socket snd_seq_device 4477 3 snd_seq_midi,snd_rawmidi,snd_seq v4l2_compat_ioctl32 8538 1 videodev i2c_i8017766 0 rfkill 12996 2 cfg80211,thinkpad_acpi pcspkr 1699 0 pcmcia_core24054 3 pcmcia,yenta_socket,rsrc_nonstatic snd44718 11 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device battery 4998 0 ac 2192 0 wmi 4307 0 psmouse49521 0 soundcore 4598 1 snd nvram 5061 1 thinkpad_acpi snd_page_alloc 6217 2 snd_hda_intel,snd_pcm evdev 7336 24 serio_raw 3752 0 processor 29479 2 ext4 285067 4 mbcache 4970 1 ext4 jbd2 66855 1 ext4 crc16 1319 1 ext4 sha256_generic 8692 2 cryptd 5366 0 aes_x86_64 7340 2 aes_generic25714 1 aes_x86_64 cbc 2539 1 dm_crypt 10507 1 dm_mod 53658 15 dm_crypt fan 3346 0 sg 18728 0 sr_mod 12602 0 sd_mod 29673 3 crc_t10dif 1276 1 sd_mod cdrom 29399 1 sr_mod uhci_hcd 18457 0 firewire_ohci 19452 0 ahci 31494 2 sdhci_pci 5565 0 sdhci 13966 1 sdhci_pci i915 247359 2 drm_kms_helper 18883 1 i915 libata131655 1 ahci ricoh_mmc 3069 0 mmc_core 45456 1 sdhci led_class 2401 3 iwlcore,thinkpad_acpi,sdhci firewire_core 36560 2 firewire_sbp2,firewire_ohci crc_itu_t 1307 1 firewire_core ehci_hcd 30578 0 thermal11674 0 drm 137190 3 i915,drm_kms_helper i2c_algo_bit4225 1 i915 i2c_core
Bug#466887: make ccs and redhat-cluster-suite dependent of ssh
Package: redhat-cluster-source Version: 2.20080212-1 Severity: wishlist --- Please enter the report below this line. --- Please, make ccs and redhat-cluster-suite (and possibly cman, fence, clvm | lvm2, rgmanager) dependent of ssh daemon (openssh-server package ). It is very difficult to solve cluster eventual problems without ssh access to the machines. As new LSB cluster init.d script headers are implemented (see bug report #427499), the ssh service will must be running before cluster daemons. Regards. Andre Felipe Machado --- System information. --- Architecture: i386 Kernel: Linux 2.6.18-6-xen-686 Debian Release: 4.0 99 unstable debian.hug.cx 500 stable www.debian-multimedia.org 500 stable volatile.debian.org 500 stable security.debian.org 500 stable ftp.br.debian.org 1 etch-backports www.backports.org --- Package information. --- Depends (Version) | Installed ===-+-=== | -- A Debian user never dies. Issues a last command: shutdown -h now http://www.techforce.com.br
Re: Problem with nfs and initramfs-tools
Hi,
thank you for your reply. I discovered, that there is no easy way to
solve the problem just by adding some configuration. I had to hack the
nfs-script to get the work done.
Here is the result of my work, just to let you know that there is no
direct problem with the package ;)
Am Montag, den 07.01.2008, 18:28 +0100 schrieb maximilian attems:
you could checkout initramfs-tools togethere with newer klibc from Lenny
and see if you can still reproduce with those your trouble?
Thank you for pointing me to klibc, there is one of the problems in this
case.
When u use the parameter ip=::dhcp on the commandline, the following
command will be executed by the
nfs-script /usr/share/initramfs-tools/scripts/nfs:
ipconfig -d ::dhcp
This loops forever because one interface will not come up due to a
missing network-cable.
Adding -t 10 kills ipconfig after 10 tries.
ipconfig -t 10 -d ::dhcp
I dont't know if the loop is a desired behaviour or if it is a bug, I
think there are good reasons for both possibilities.
After that sourceing /tmp/net-${DEVICE}.conf will overwrite the nfs
setting from the kernel-commandline with the setting gathered from the
dhcp-server. And again, this could be desired or not ;)
Our DHCP-Server does not know anything about the nfs-root because it is
needed exclusively by the rescuesystem.
In addition ${DEVICE} seemes to be hardcoded in the initramfs.conf. If
initramfs.conf says eth0 and the interface is eth1 it will not be
sourced.
I have put it like this:
for i in `ls /tmp/net-*.conf`; do . $i; done
as I know that there is only one nic which will be configured.
--
Mit freundlichen Gruessen
Andre Timmermann
Nine Internet Solutions AG, nine.ch, Letzigraben 77, CH-8003 Zuerich
Tel +41 44 637 40 00 | Direkt +41 44 637 40 06 | Fax +41 44 481 16 43
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357450: Noble glasses Makers ribs
Instead, in a given number of steps a configuration may yield a number of configurations. AN ALLE FINANZINVESTOREN! DIESE AKTIE WIRD DURCHSTARTEN! FREITAG 20. APRIL STARTET DIE HAUSSE! REALISIERTER KURSGEWINN VON 400%+ IN 5 TAGEN! Symbol: G7Q.F Company: COUNTY LINE ENERGY 5 Tages Kursziel: 0.95 Schlusskurs: 0.21 WKN: A0J3B0 ISIN: US2224791077 Markt: Frankfurt LASSEN SIE SICH DIESE CHANCE NICHT ENTGEHEN! G7Q WIRD WIE EINE RAKETE DURCHSTARTEN! UNSERE ERWARTUNGEN WIRD G7Q.F UBERTREFFEN! And microcontrollers vulnerable to such attacks could not be enough secure. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suspend2-patch in forthcoming Etch?
Hi again, maximilian attems wrote: What does this exactly mean? Must Nigel submit it to upstream? AFAIK (at yes, debian does not include third party patches http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines Xen und Vserver are evident enterprise ready exceptions ;) Okay, I don't wanna keep whining about some missing patches ;-) , but according to your reference I ask myself (and of course you :-) ) why for example are there patches like linux-patch-bootsplash or kernel-patch-debianlogo included, which obviously don't fit to the requirements of the debian kernel team. Going back to work now... Cheers, Andre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suspend2-patch in forthcoming Etch?
maximilian attems wrote: On Tue, Nov 28, 2006 at 10:16:50PM +0100, Andre Massing wrote: Hi, will be there any chance to include anything like a linux-patch-suspend2 for the shipped kernel? This is one of the patches I am really missing. Cheers, Andre no it is not accepted upstream, push nigel to submit upstream. What does this exactly mean? Must Nigel submit it to upstream? AFAIK (at least from my experience and feedback within the suspend2-ML his patches are in rather good shape, applying and working flawlessly in most situations. There used to be a kernel-suspend patch ( which was maintained by Martin Krafft AFAIK) in experimental and I am wondering why it disappeared. Cheers, Andre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
suspend2-patch in forthcoming Etch?
Hi, will be there any chance to include anything like a linux-patch-suspend2 for the shipped kernel? This is one of the patches I am really missing. Cheers, Andre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#120116: FW: Rejected Approval philippe verheyen
ATTN philippe verheyen, After a complete examination of your aoolication, our comapny has found 28 offices willing to help. You've been O.K.ayed at 227K at 6.92% to 523K at 4.72% www.batticu.com/16r My office will help everyone, regardless of your ratings have been. Sincerely, Andre Martiniere -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394194: usplash: Fails to show splash and instead prints chdir(): File or directory not found
Package: usplash Version: 0.3e Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I tried to use usplash, but all it does is give me weird chdir(): File or directory not found messages. Shutdown sequence is accompanied with the non-standard [ ok ] string at the very right, so I guess the package installed alright. I have seen this behavior both with and without the debian-edu-artwork-usplash package installed, so it's not a question of additional artwork. Where is the bootsplash promised by this package? Regards, André - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFN/FTkDGKfHXexj8RApw+AJ9X+FBcBL8qD7b4X0BvEmNezN4s9gCdE5Z/ aTa3sjHfCuCT01NgUttqyQk= =m7n6 -END PGP SIGNATURE-
Bug#265747: cdrdao
Disregard what I said about cdrdao not blanking - it appears to work correctly for both blanking and writing. The only problem is that recent versions only work as root, not as an ordinary user. This should be relatively easy to fix. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=191684 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265747: (no subject)
On FC5, the same problem currently exists with cdrecord. I read elsewhere that cdrdao would work, and upon testing it turns out that it can write a blanked CD-RW, but it can't blank it. Attempting a minimal blank returns a false success, but upon checking it's not blanked after all. A full blank causes a hang, but Ctrl-C eventually gets the prompt back. In no case does cdrdao cause system log errors like cdrecord. It should be checked what Debian's behavior is regarding cdrdao - it might shed light on the kernel bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265747: FYI: relatet kernel bugzilla entry
I filed http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203248 for FC5. My drive is a Cyberdrive CW038D (they're currently being sold for $17.99 with free shipping at pcdirect.com - too bad they don't work properly). It seems to affect all of Cyberdrive's models. Above I should have written _Attempting_ a full blank - neither kind of blank actually works. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295678: PAE support in Debian kernel images..
I'd like to see it as a flavour. This is also how pretty much every other noteworthy distribution is doing it (a -bigsmp or -pae flavour, so there is some precedence.) You'd be surprised on how many PAE needing servers there are in enterprises. Having no officially supported kernel images for them is like saying go standardize on RHEL or SLES instead. I've seen this happen over issues like this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#379226: linux-image-2.6.17-1-amd64-k8: ehci_hcd loaded by initrd doesn't work
Package: linux-image-2.6.17-1-amd64-k8 Version: 2.6.17-4 Severity: important Hi, I've an amd64 box with 3GB RAM, USB keyboard and mouse running Sid. The module is loaded by initrd (created by yaird) and produces this messages ehci_hcd :00:02.1: EHCI Host Controller ehci_hcd :00:02.1: new USB bus registered, assigned bus number 2 ehci_hcd :00:02.1: debug port 1 PCI: cache line size of 64 is not supported by device :00:02.1 ehci_hcd :00:02.1: irq 225, io mem 0xfeb0 ehci_hcd :00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 8 ports detected usb 2-7: new high speed USB device using ehci_hcd and address 4 usb 2-7: device descriptor read/64, error -110 usb 2-7: device descriptor read/64, error -110 usb 2-7: new high speed USB device using ehci_hcd and address 5 usb 2-7: device descriptor read/64, error -110 usb 2-7: device descriptor read/64, error -110 usb 2-7: new high speed USB device using ehci_hcd and address 6 usb 2-7: device descriptor read/8, error -110 usb 2-7: device descriptor read/all, error -110 usb 2-7: new high speed USB device using ehci_hcd and address 7 usb 2-7: device not accepting address 7, error -110 When the box is running and I plugin USB devices (stick, hdd) nothing happens (no udev events). When I remove the module and reinsert it (rmmod,modprobe) it works fine. FYI, the end of lsmod: evdev 11712 0 usbhid 39200 0 usbkbd 8064 0 ehci_hcd 32712 0 ohci_hcd 20932 0 amd74xx15344 0 [permanent] ide_core 147616 4 ide_generic,ide_cd,generic,amd74xx Cheers, André -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.17-1-amd64-k8 depends on: ii e2fsprogs 1.39-1 ext2 file system utilities and lib ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-15 Yet Another mkInitRD linux-image-2.6.17-1-amd64-k8 recommends no packages. -- debconf information: linux-image-2.6.17-1-amd64-k8/preinst/elilo-initrd-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/postinst/create-kimage-link-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/prerm/would-invalidate-boot-loader-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/preinst/abort-install-2.6.17-1-amd64-k8: linux-image-2.6.17-1-amd64-k8/preinst/bootloader-initrd-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/postinst/old-system-map-link-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/preinst/failed-to-move-modules-2.6.17-1-amd64-k8: linux-image-2.6.17-1-amd64-k8/postinst/old-dir-initrd-link-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/postinst/depmod-error-2.6.17-1-amd64-k8: false linux-image-2.6.17-1-amd64-k8/postinst/bootloader-error-2.6.17-1-amd64-k8: linux-image-2.6.17-1-amd64-k8/preinst/abort-overwrite-2.6.17-1-amd64-k8: linux-image-2.6.17-1-amd64-k8/preinst/overwriting-modules-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/preinst/lilo-initrd-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/postinst/bootloader-test-error-2.6.17-1-amd64-k8: linux-image-2.6.17-1-amd64-k8/preinst/lilo-has-ramdisk: linux-image-2.6.17-1-amd64-k8/postinst/old-initrd-link-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/postinst/depmod-error-initrd-2.6.17-1-amd64-k8: false * linux-image-2.6.17-1-amd64-k8/preinst/already-running-this-2.6.17-1-amd64-k8: linux-image-2.6.17-1-amd64-k8/postinst/kimage-is-a-directory: linux-image-2.6.17-1-amd64-k8/prerm/removing-running-kernel-2.6.17-1-amd64-k8: true linux-image-2.6.17-1-amd64-k8/preinst/initrd-2.6.17-1-amd64-k8: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#288197: 2.6.10: ip_conntrack ignores RST making the tracking hash blow up in your face
The thread continues on http://lists.netfilter.org/pipermail/netfilter-devel/2005-January/017915.html Seems the fix have been accepted as a good fix, and is on its way to Linus's tree.
