Re: Bug#940710: Fails to load pkcs8_key_parser module
Control: reassign -1 linux-image-5.2.0-2-amd64 Control: retitle -1 Please enable CONFIG_PKCS8_PRIVATE_KEY_PARSER Hi Andreas, On Tue, Sep 24, 2019 at 1:32 PM Andreas Henriksson wrote: > Hello Felipe Sateler, > > On Tue, Sep 24, 2019 at 10:03:19AM -0300, Felipe Sateler wrote: > > Control: reopen -1 > [...] > > This causes failed boots on debian by default [...] > > Really? Please share more info! It certainly doesn't for me. > Sorry, I was a bit sloppy in my wording. What I mean is that systemd considers the boot degraded because `systemd-modules-load` fails: % systemctl is-system-running degraded % systemctl --no-legend --failed systemd-modules-load.service loaded failed failed Load Kernel Modules % systemctl --no-legend status systemd-modules-load.service ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-04-11 12:28:36 -04; 5 months 13 days ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 530 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 530 (code=exited, status=1/FAILURE) Apr 11 12:28:36 felipeasus systemd[1]: Starting Load Kernel Modules... Apr 11 12:28:36 felipeasus systemd-modules-load[530]: Failed to find module 'pkcs8_key_parser' Apr 11 12:28:36 felipeasus systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Apr 11 12:28:36 felipeasus systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Apr 11 12:28:36 felipeasus systemd[1]: Failed to start Load Kernel Modules. > (Would also be nice if you reported a dedicated bug report about that > instead of repurposing this.) > Well, the root cause is the same, so I thought I'd just reopen. > > > [...] since the debian kernels don't enable that module: > > > > % grep CONFIG_PKCS8_PRIVATE_KEY_PARSER /boot/config-* > > /boot/config-5.2.0-2-amd64:# CONFIG_PKCS8_PRIVATE_KEY_PARSER is not set > > /boot/config-5.3.0-rc5-amd64:# CONFIG_PKCS8_PRIVATE_KEY_PARSER is not set > > I'm aware that it doesn't (at the moment). AFAIK the usual debian kernel > team policy is to enable things on request, so someone just needs to > request it. Since you're not the first to ask *me* (even though I'm not > on the kernel team) I've already asked on #debian-kernel if they can > enable it while at the same time asking people to please not use me as a > proxy. > I'm sorry you feel like I'm using you as middleman. As I said in the part quoted below, I didn't know if requesting the kernel maintainers to add this option makes sense. I'm happy to request it myself: #941098. > > > > > Since I have no idea what does pkcs8_key_parser do, I don't know if it > > would be best to have linux enable that option or to have iwd not ship > this > > file. > > It is needed if you want to use iwd to connect to wpa enterprise > networks. Thanks for the explanation. This means the best solution (from the iwd POV) is to have the kernel enable the option. I have requested that feature now on #941098. -- Saludos, Felipe Sateler
Bug#941098: linux-image-5.2.0-2-amd64: Please enable CONFIG_PKCS8_PRIVATE_KEY_PARSER
Package: src:linux Version: 5.2.9-2 Severity: wishlist Dear Maintainer, As detailed in #940710, iwd needs this option in order to support enterprise WPA networks. The lack of this module means iwd causes systemd-modules-load to fail at boot. It would be great if it would be enabled. -- Kernel: Linux 5.3.0-rc5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.2.0-2-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.135 ii kmod26-3 ii linux-base 4.6 Versions of packages linux-image-5.2.0-2-amd64 recommends: ii apparmor 2.13.3-5 ii firmware-linux-free 3.4 Versions of packages linux-image-5.2.0-2-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.04-3 pn linux-doc-5.2 Versions of packages linux-image-5.2.0-2-amd64 is related to: ii firmware-amd-graphics 20190717-2 ii firmware-atheros 20190717-2 ii firmware-bnx2 20190717-2 ii firmware-bnx2x20190717-2 ii firmware-brcm8021120190717-2 ii firmware-cavium 20190717-2 ii firmware-intel-sound 20190717-2 ii firmware-intelwimax 20190717-2 ii firmware-ipw2x00 20190717-2 ii firmware-ivtv 20190717-2 ii firmware-iwlwifi 20190717-2 ii firmware-libertas 20190717-2 ii firmware-linux-nonfree20190717-2 ii firmware-misc-nonfree 20190717-2 ii firmware-myricom 20190717-2 ii firmware-netxen 20190717-2 ii firmware-qlogic 20190717-2 ii firmware-realtek 20190717-2 ii firmware-samsung 20190717-2 ii firmware-siano20190717-2 ii firmware-ti-connectivity 20190717-2 pn xen-hypervisor -- no debconf information
Bug#892408: firmware-iwlwifi: please package new upstream version to get firmware-iwlwifi-8265-34
Package: firmware-iwlwifi Version: 20170823-1 Severity: wishlist Hi, The currently packaged snapshot is missing (at least) firmware-iwlwifi-8265-34, which is required for the intel wifi card on my laptop (Dell Latitude 5285) to work. 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) Subsystem: Intel Corporation Wireless 8265 / 8275 Kernel driver in use: iwlwifi Kernel modules: iwlwifi Fetching the file from upstream git repository was enough to make the wifi card work. Saludos -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.130 -- no debconf information -- debsums errors found: debsums: changed file /lib/firmware/intel/ibt-11-5.ddc (from firmware-iwlwifi package) debsums: changed file /lib/firmware/intel/ibt-11-5.sfi (from firmware-iwlwifi package)
Re: Bug#833326: pulseaudio: Lenovo Ideapad 300 - volume of the internal microphone is very low
Control: reassign -1 linux-image-4.6.0-1-amd64 On 10 August 2016 at 14:16, Florent Mazzone wrote: > > Hello Felipe, > > Thanks for your answer. I'm currently using pavucontrol, as soon as I > disable one channel from the microphone (for example the left chanel level > is 0%), the microphone will work normally. I've found on the Ubuntu an issue > that looks similar to the one I've noticed with this laptop ( > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 ). Maybe > the problem is specific to this type of microphone ? So, it looks like that problem indeed. Reassigning to the kernel then, as the problem is there. Please attach the alsa-info as documented at https://wiki.ubuntu.com/Audio/AlsaInfo -- Saludos, Felipe Sateler
Re: Bug#830992: pulseaudio: no sound with snd_hda_codec_realtek ALC880
Control: reassign -1 linux-image-4.6.0-1-686-pae On 14 July 2016 at 12:36, Loris e Anna wrote: > Hi Filipe, > as your request, in attach the verbose log. For some reason, your kernel is not creating a proper alsa device, and ALSA does not appear to know about it. Therefore reassigning to the kernel. -- Saludos, Felipe Sateler
Re: Bug#825507: pulseaudio: system hangs, log message ask me to report bug
efers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) > Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages pulseaudio depends on: > ii adduser 3.114 > ii libasound21.1.0-1 > ii libasound2-plugins1.1.0-1+b1 > ii libc6 2.22-9 > ii libcap2 1:2.25-1 > ii libdbus-1-3 1.10.8-1 > ii libfftw3-single3 3.3.4-2+b1 > ii libgcc1 1:6.1.1-4 > ii libice6 2:1.0.9-1+b1 > ii libltdl7 2.4.6-0.1 > ii liborc-0.4-0 1:0.4.25-1 > ii libpulse0 8.0-2+b2 > ii libsm62:1.2.2-1+b1 > ii libsndfile1 1.0.25-10 > ii libsoxr0 0.1.2-1 > ii libspeexdsp1 1.2~rc1.2-1 > ii libstdc++66.1.1-4 > ii libsystemd0 229-6 > ii libtdb1 1.3.9-1 > ii libudev1 229-6 > ii libwebrtc-audio-processing-0 0.1-3 > ii libx11-6 2:1.6.3-1 > ii libx11-xcb1 2:1.6.3-1 > ii libxcb1 1.11.1-1 > ii libxtst6 2:1.2.2-1+b1 > ii lsb-base 9.20160110 > ii pulseaudio-utils 8.0-2+b2 > ii udev 229-6 > > Versions of packages pulseaudio recommends: > ii pulseaudio-module-x11 8.0-2+b2 > ii rtkit 0.11-4 > > Versions of packages pulseaudio suggests: > pn paman > pn paprefs > ii pavucontrol 3.0-3+b2 > pn pavumeter > > -- no debconf information > > ___ > pkg-pulseaudio-devel mailing list > pkg-pulseaudio-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel -- Saludos, Felipe Sateler
Bug#815787: May be a kernel problem not a pulseaudio one?
Control: retitle: linux-4.4: missing snd-emu10k1 modules On 25 February 2016 at 15:14, Russel Winder wrote: > Hi, > >> The emu10k1 (or emu10k1x) driver (for the sound blaster) is not >> loaded, so this is almost certainly a kernel problem. > > Hummm…. > > |> find /lib -name "*emu10k*" > /lib/modules/4.2.0-1-amd64/kernel/sound/pci/emu10k1 > /lib/modules/4.2.0-1-amd64/kernel/sound/pci/emu10k1/snd-emu10k1x.ko > /lib/modules/4.2.0-1-amd64/kernel/sound/pci/emu10k1/snd-emu10k1- > synth.ko > /lib/modules/4.2.0-1-amd64/kernel/sound/pci/emu10k1/snd-emu10k1.ko > /lib/modules/4.2.0-1-amd64/kernel/drivers/input/gameport/emu10k1-gp.ko > /lib/modules/4.3.0-1-amd64/kernel/sound/pci/emu10k1 > /lib/modules/4.3.0-1-amd64/kernel/sound/pci/emu10k1/snd-emu10k1x.ko > /lib/modules/4.3.0-1-amd64/kernel/sound/pci/emu10k1/snd-emu10k1- > synth.ko > /lib/modules/4.3.0-1-amd64/kernel/sound/pci/emu10k1/snd-emu10k1.ko > /lib/modules/4.3.0-1-amd64/kernel/drivers/input/gameport/emu10k1-gp.ko > /lib/modules/4.4.0-1-amd64/kernel/drivers/input/gameport/emu10k1-gp.ko > > I think we have an answer, the kernel modules are not being packaged. I > should have got here a lot earlier! OK, now we have a root cause. Retitling the bug accordingly. -- Saludos, Felipe Sateler
Re: Bug#815787: May be a kernel problem not a pulseaudio one?
Control: reassign -1 linux-image-4.4.0-1-amd64 On 25 February 2016 at 14:20, Russel Winder wrote: > Hi, > >> >> Thanks, that is useful. > > Splendid. I appreciate it can be a pain having to ask for data, but it > is much easier to send it what is asked for and will be useful than to > try and guess ahead of time and inundate with useless stuff. Yes, moreover, the level of output from pulseaudio verbose mode is too much for normal usage so it cannot be automatically included. > >> The log contains: >> >> module-udev-detect.c: Found 1 cards. >> >> And no trace of the sound blaster. The code suggests that this is >> either because it is no longer in the sound subsystem, or that the >> path does not have an id[1]. > > Sound blaster is definitely still there, witness that it is in the > lspci listing and it works fine in earlier kernels. > > 09:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 > (rev 05) > 09:02.1 Input device controller: Creative Labs SB Live! Game Port (rev > 05) > >> What is the output of: >> >> ls -d /sys/devices/*/*/sound/* > > |> ls -d /sys/devices/*/*/sound/* > ls: cannot access '/sys/devices/*/*/sound/*': No such file or directory > > Which seems a bit terminal. Shall I reboot to 4.3.0 and do the same for > comparison? Second attempt is to do `ls /dev/snd/control*` , and run `udevadm info $controlfile` for each result. But, I somehow missed over the fact that in the initial bug report, one of the attachments shows alsa knows nothing of the sound blaster. If alsa does not know about it, then neither will pulseaudio. This most likely is a problem in the kernel, so I am reassigning there and CCing the kernel list. > >> And for each of those paths, what is the output of: >> >> udevadm info -p $path >> >> ? >> >> Also please attach the output of `lsmod | grep snd` > > |> lsmod | grep snd > snd_hda_codec_hdmi 53248 1 > snd_hda_intel 36864 0 > snd_hda_codec 131072 2 snd_hda_codec_hdmi,snd_hda_intel > snd_hda_core 65536 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel > snd_hwdep 16384 1 snd_hda_codec > snd_pcm 102400 4 > snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core > snd_timer 32768 1 snd_pcm > snd81920 6 > snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel > soundcore 16384 1 snd The emu10k1 (or emu10k1x) driver (for the sound blaster) is not loaded, so this is almost certainly a kernel problem. -- Saludos, Felipe Sateler
Bug#766781: pavucontrol: Input volume cannot be more than 39%
On Wed, Nov 12, 2014 at 1:59 PM, wrote: > Felipe, > > I set "Element mic boost" "volume" to "zero" instead of "0" and it works : I > can increase the input volume level up to 153%. Great that you can have a working setup now. Let us hope the real problem can be solved. > > The link resulting from alsa-info.sh script : > http://www.alsa-project.org/db/?f=047c2acc0b69c594d762f220e8f551f0af0d2a08 I'll leave this to the kernel developers. -- Saludos, Felipe Sateler -- 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/CAAfdZj-ykzyffRas_D=3nogh85nkwosdl6yztag9v35tokw...@mail.gmail.com
Re: Bug#726556: pulseaudio: mic is dead after suspend
Control: reassign -1 linux-image-3.13-1-amd64/3.13.5-1 On Fri, Apr 18, 2014 at 6:32 PM, Stefan Krastanov wrote: > Here are the results: > > 1. > `arecord` while pa is *not* suspended and while the mic is working > fine returns "device is busy" > > ``` > % arecord -vv -fdat -c 2 -D hw:0,0 test.wav > arecord: main:722: audio open error: Device or resource busy > ``` > > 2. > if the mic is working just before issuing the command > `pasuspender -- arecord -vv -fdat -c 2 -D hw:0,0 test.wav` > then `arecord` works and the sound from the mic is recorded > > 3. > if the mic is *not* working just before issuing the command > `pasuspender -- arecord -vv -fdat -c 2 -D hw:0,0 test.wav` > then `arecord` does not record any noise > > 4. > if the mic is working just before issuing the command > `pasuspender -- yes > /dev/null` > and I suspend and resume without killing the process > then the mic is *not* working after the resume, nor after > I kill the process after resuming Then this is almost certainly a kernel bug. I'm reassigning there, as I cannot do much here. Good luck! -- Saludos, Felipe Sateler -- 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/caafdzj-nzgmop3t-8sjjtl+41rgaj8bdpe841tc-hejckkt...@mail.gmail.com
Bug#714471: linux-image-3.9-1-amd64: No sound from internal speakers with hda intel
Package: src:linux Version: 3.9.6-1 Severity: normal Dear linux maintainers, the 3.9 kernel has introduced a regression compared with the 3.8 kernel (and earlier), now my internal speakers produce no sound (playing with the several pulseaudio and alsa mixers produces no results). I have attached the reportbug-generated reports for both 3.9-1 and 3.8-1, and also the alsa-info.sh output for both kernels. If any other information is required, I will happily provide it. -- Saludos, Felipe Sateler report.tgz Description: GNU Zip compressed data
Bug#520232: linux-image-2.6.28-1-amd64: have to load pcspkr to disable the pc speaker
Package: linux-image-2.6.28-1-amd64 Version: 2.6.28-1 Severity: normal Upgrading from 2.6.26 to 2.6.28 the pc speaker started doing annoying beeps when eg, tab-completing. To avoid this I used to blacklist pcspkr, but now it seems I have to load it. In summary: pc speaker on when the pcspkr module unloaded, off when the module is loaded. -- Package-specific info: ** Version: Linux version 2.6.28-1-amd64 (Debian 2.6.28-1) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-4) ) #1 SMP Wed Feb 18 17:16:12 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.28-1-amd64 root=UUID=1a73bf6e-7db2-4013-b64d-0898a5a8d0d7 ro quiet ** Not tainted ** Kernel log: [152778.128284] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b00407) [152778.128330] ahci :00:1f.2: setting latency timer to 64 [152778.128379] i801_smbus :00:1f.3: restoring config space at offset 0xf (was 0x200, writing 0x20a) [152778.128412] i801_smbus :00:1f.3: restoring config space at offset 0x4 (was 0x0, writing 0xfe9fb700) [152778.128423] i801_smbus :00:1f.3: restoring config space at offset 0x1 (was 0x281, writing 0x2800103) [152778.144332] tg3 :09:00.0: restoring config space at offset 0xc (was 0x0, writing 0xfffb) [152778.144391] tg3 :09:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) [152778.144408] tg3 :09:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100106) [152778.160242] firewire_ohci :03:01.0: restoring config space at offset 0xf (was 0x4020100, writing 0x4020105) [152778.160272] firewire_ohci :03:01.0: restoring config space at offset 0x3 (was 0x80, writing 0x804010) [152778.160281] firewire_ohci :03:01.0: restoring config space at offset 0x1 (was 0x210, writing 0x2100106) [152778.256241] sdhci-pci :03:01.1: restoring config space at offset 0xf (was 0x200, writing 0x204) [152778.256269] sdhci-pci :03:01.1: restoring config space at offset 0x4 (was 0x0, writing 0xfe4ff500) [152778.256276] sdhci-pci :03:01.1: restoring config space at offset 0x3 (was 0x80, writing 0x804010) [152778.256285] sdhci-pci :03:01.1: restoring config space at offset 0x1 (was 0x210, writing 0x2100106) [152778.256304] sdhci-pci :03:01.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18 [152778.257325] pci :03:01.2: restoring config space at offset 0xf (was 0x200, writing 0x204) [152778.257346] pci :03:01.2: restoring config space at offset 0x4 (was 0x0, writing 0xfe4ff600) [152778.257351] pci :03:01.2: restoring config space at offset 0x3 (was 0x80, writing 0x804010) [152778.257358] pci :03:01.2: restoring config space at offset 0x1 (was 0x210, writing 0x2100106) [152778.257378] pci :03:01.3: restoring config space at offset 0xf (was 0x200, writing 0x204) [152778.257400] pci :03:01.3: restoring config space at offset 0x4 (was 0x0, writing 0xfe4ff700) [152778.257405] pci :03:01.3: restoring config space at offset 0x3 (was 0x80, writing 0x804010) [152778.257412] pci :03:01.3: restoring config space at offset 0x1 (was 0x210, writing 0x2100106) [152778.448250] ata3: SATA link down (SStatus 0 SControl 300) [152778.568273] sd 0:0:0:0: [sda] Starting disk [152779.009244] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [152779.042671] ata1.00: configured for UDMA/133 [152779.042865] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors: (120 GB/111 GiB) [152779.042890] sd 0:0:0:0: [sda] Write Protect is off [152779.042894] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [152779.042929] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [152779.050687] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [152779.051647] hda: UDMA/33 mode selected [152779.052713] pci :00:02.0: setting latency timer to 64 [152779.300250] pm_op(): usb_dev_resume+0x0/0x5 returns -19 [152779.300253] PM: Device 1-2 failed to resume: error -19 [152779.300261] pm_op(): usb_dev_resume+0x0/0x5 returns -19 [152779.300264] PM: Device 1-2.1 failed to resume: error -19 [152779.300278] pm_op(): usb_dev_resume+0x0/0x5 returns -19 [152779.300281] PM: Device 1-2.2 failed to resume: error -19 [152779.300291] pm_op(): usb_dev_resume+0x0/0x5 returns -19 [152779.300294] PM: Device 1-2.3 failed to resume: error -19 [152779.300932] Restarting tasks ... <6>usb 1-2: USB disconnect, address 29 [152779.338508] usb 1-2.1: USB disconnect, address 30 [152779.338908] usb 1-2.2: USB disconnect, address 31 [152779.339009] done. [152779.393287] usb 1-2.3: USB disconnect, address 32 [152781.388298] tg3 :09:00.0: irq 4346 for MSI/MSI-X [152781.441717] ADDRCONF(NETDEV_UP): eth0: link is not ready [152781.462188] iwl3945 :0c:00.0: enabling device ( -> 0002) [152781.462201] iwl3945 :0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [152781.462276] iwl3945 :0c:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [152
Bug#469727: linux-image-2.6.24-1-amd64: sound doesn't work after suspend to disk with snd-hda-intel
On Tuesday 27 May 2008 08:36:53 maximilian attems wrote: > please try out 2.6.25 from unstable installs just fine in testing. > it has newer alsa if that fails too 2.6.26-rc4 is available here > http://photon.itp.tuwien.ac.at/~mattems/ > > please report back on those. 2.6.25 was a bit flaky for me.. sometimes the soundcard wouldn't come up at boot. 2.6.26-rc4 seems better. I had to blacklist the (new?) snd_pcsp module, dropped the model=5stack argument and things seem to be running smooth. -- Felipe Sateler signature.asc Description: This is a digitally signed message part.
Bug#475131: linux-modules-extra-2.6: Builds fine here
On Sunday 18 May 2008 17:04:28 Daniel Baumann wrote: > Felipe Sateler wrote: > > Works fine here with 2.6.25-1 and 1.5.6-dfsg-7 on an amd64 machine. > > no, it doesn't. first, it's 2.6.25-2 which is of interests (thouhg it's > no difference to 2.6.25-1 wrt/ vbox), second build with lme, not m-a. I'm sorry if the version number is confusing. 2.6.25-1 is what debian/changelog says in the linux-modules-extra source package. I am using the 2.6.25-2 kernel. I did an apt-get source and build-deps linux-modules-extra-2.6 and then (newlines added for clarity): % cat virtualbox-ose/defines [base] arches: i386 amd64 desc: PC virtualization solution longdesc: VirtualBox is a free PC virtualization solution allowing you to run a wide range of PC operating systems on your system. % rm debian/control* % debian/rules debian/control &>/dev/null % dpkg-buildpackage &> build.log % sudo dpkg -i ../virtualbox-ose-modules-2.6.25-2-amd64_2.6.25+1.5.6-dfsg-1_amd64.deb (Reading database ... 184852 files and directories currently installed.) Preparing to replace virtualbox-ose-modules-2.6.25-2-amd64 2.6.25+1.5.6-dfsg-1 (using .../virtualbox-ose-modules-2.6.25-2-amd64_2.6.25+1.5.6-dfsg-1_amd64.deb) ... Unpacking replacement virtualbox-ose-modules-2.6.25-2-amd64 ... Setting up virtualbox-ose-modules-2.6.25-2-amd64 (2.6.25+1.5.6-dfsg-1) ... % sudo modprobe -v vboxdrv insmod /lib/modules/2.6.25-2-amd64/extra/virtualbox-ose/vboxdrv.ko % dmesg|tail [ 8974.290720] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 8992.582962] eth0: no IPv6 routers present [12332.854873] vboxdrv: Trying to deactivate the NMI watchdog permanently... [12332.854879] vboxdrv: Successfully done. [12332.854924] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [12332.854926] vboxdrv: Successfully loaded version 1.5.6_OSE (interface 0x00050002). [15385.072471] vboxdrv: Trying to deactivate the NMI watchdog permanently... [15385.072483] vboxdrv: Successfully done. [15385.072578] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [15385.072583] vboxdrv: Successfully loaded version 1.5.6_OSE (interface 0x00050002). And I can use VirtualBox normally. I just tried the same with a debcheckout and worked as well. -- Felipe Sateler signature.asc Description: This is a digitally signed message part.
Bug#475131: linux-modules-extra-2.6: Builds fine here
Package: linux-modules-extra-2.6 Followup-For: Bug #475131 Works fine here with 2.6.25-1 and 1.5.6-dfsg-7 on an amd64 machine. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#469727: linux-image-2.6.24-1-amd64: sound doesn't work after suspend to disk with snd-hda-intel
Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-4 Severity: normal As the title says. The module is loaded with the options index=0 model=5stack. Reloading the module makes sound work again. Any steps to diagnose this problem? -- Package-specific info: ** Version: Linux version 2.6.24-1-amd64 (Debian 2.6.24-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Mon Feb 11 13:47:43 UTC 2008 ** Command line: BOOT_IMAGE=(hd0,6)/boot/vmlinuz-2.6.24-1-amd64 root=/dev/sda6 ro quiet ** Not tainted ** Kernel log: usb usb4: root hub lost power or was reset PCI: Enabling device :00:1d.2 ( -> 0001) ACPI: PCI Interrupt :00:1d.2[C] -> GSI 22 (level, low) -> IRQ 22 PCI: Setting latency timer of device :00:1d.2 to 64 PM: Writing back config space on device :00:1d.2 at offset f (was 300, writing 307) PM: Writing back config space on device :00:1d.2 at offset 8 (was 1, writing 6f41) usb usb5: root hub lost power or was reset ACPI: PCI Interrupt :00:1d.7[A] -> GSI 20 (level, low) -> IRQ 20 PCI: Setting latency timer of device :00:1d.7 to 64 PM: Writing back config space on device :00:1e.0 at offset 9 (was 100f1, writing 1fff1) PM: Writing back config space on device :00:1e.0 at offset 8 (was 40, writing fe40fe40) PM: Writing back config space on device :00:1e.0 at offset 7 (was 2280e0f0, writing 228000f0) PM: Writing back config space on device :00:1e.0 at offset 1 (was 17, writing 100107) PCI: Setting latency timer of device :00:1e.0 to 64 PM: Writing back config space on device :00:1f.0 at offset 1 (was 217, writing 2100107) PM: Writing back config space on device :00:1f.1 at offset f (was 100, writing 10b) PM: Writing back config space on device :00:1f.1 at offset 1 (was 2880005, writing 285) ACPI: PCI Interrupt :00:1f.1[A] -> GSI 16 (level, low) -> IRQ 16 PM: Writing back config space on device :00:1f.2 at offset f (was 200, writing 20a) PM: Writing back config space on device :00:1f.2 at offset 9 (was 0, writing fe9fb800) PM: Writing back config space on device :00:1f.2 at offset 1 (was 2b0, writing 2b00407) PCI: Setting latency timer of device :00:1f.2 to 64 PM: Writing back config space on device :00:1f.3 at offset f (was 200, writing 20a) PM: Writing back config space on device :00:1f.3 at offset 4 (was 0, writing fe9fb700) PM: Writing back config space on device :00:1f.3 at offset 1 (was 281, writing 2800103) Coming out of suspend... PCI: Enabling device :0c:00.0 ( -> 0002) PM: Writing back config space on device :0c:00.0 at offset f (was 100, writing 10a) PM: Writing back config space on device :0c:00.0 at offset 4 (was 0, writing fe8ff000) PM: Writing back config space on device :0c:00.0 at offset 3 (was 0, writing 10) PM: Writing back config space on device :0c:00.0 at offset 1 (was 12, writing 100506) PM: Writing back config space on device :09:00.0 at offset c (was 0, writing fffb) PM: Writing back config space on device :09:00.0 at offset 3 (was 0, writing 10) PM: Writing back config space on device :09:00.0 at offset 1 (was 10, writing 100506) tg3: eth0: Link is down. PM: Writing back config space on device :03:01.0 at offset f (was 4020100, writing 4020105) PM: Writing back config space on device :03:01.0 at offset 3 (was 80, writing 804010) PM: Writing back config space on device :03:01.0 at offset 1 (was 210, writing 2100106) PM: Writing back config space on device :03:01.1 at offset f (was 200, writing 204) PM: Writing back config space on device :03:01.1 at offset 4 (was 0, writing fe4ff400) PM: Writing back config space on device :03:01.1 at offset 3 (was 80, writing 804010) PM: Writing back config space on device :03:01.1 at offset 1 (was 210, writing 2100106) ACPI: PCI Interrupt :03:01.1[B] -> GSI 18 (level, low) -> IRQ 18 PM: Writing back config space on device :03:01.2 at offset f (was 200, writing 204) PM: Writing back config space on device :03:01.2 at offset 4 (was 0, writing fe4ff600) PM: Writing back config space on device :03:01.2 at offset 3 (was 80, writing 804010) PM: Writing back config space on device :03:01.2 at offset 1 (was 210, writing 2100106) PM: Writing back config space on device :03:01.3 at offset f (was 200, writing 204) PM: Writing back config space on device :03:01.3 at offset 4 (was 0, writing fe4ff700) PM: Writing back config space on device :03:01.3 at offset 3 (was 80, writing 804010) PM: Writing back config space on device :03:01.3 at offset 1 (was 210, writing 2100106) PM: Writing back config space on device :03:01.4 at offset f (was 200, writing 2ff) PM: Writing back config space on device :03:01.4 at offset 4 (was 0, writing ff00) PM: Writing back config space on device :03:01.4 at offset 3 (was 80, writing
Bug#457992: linux-image-2.6.23-1-amd64: Sound works under 2.6.22 but not on 2.6.23 with intel_hda driver
On Thursday 27 December 2007 16:37:30 dann frazier wrote: > On Thu, Dec 27, 2007 at 04:19:49PM -0300, Felipe Sateler wrote: > > There are no obvious errors in 2.6.23 (ie: alsamixer shows the same > > controls, all applications work happily), but there is no sound. > > Please try one of the 2.6.24 snapshots and let us know if it helps. > See http://wiki.debian.org/DebianKernel for snapshot info. Indeed, both rc5 and rc6 work. -- Felipe Sateler signature.asc Description: This is a digitally signed message part.
Bug#457992: linux-image-2.6.23-1-amd64: Sound works under 2.6.22 but not on 2.6.23 with intel_hda driver
Package: linux-image-2.6.23-1-amd64 Version: 2.6.23-2 Severity: important With a Dell Inspiron 1420, the sound driver snd_hda_intel does not work under 2.6.23 while it does under 2.6.22. % cat /etc/modprobe.d/sound alias snd-card-0 snd-hda-intel options snd-hda-intel index=0 model=5stack % lspci| grep -i audio 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) % sudo lspci -v | grep -i -A 9 audio 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) Subsystem: Dell Unknown device 01f3 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [130] Unknown (5) Note that both are stock debian kernels (namely, 2.6.23-2 and 2.6.22-6). There are no obvious errors in 2.6.23 (ie: alsamixer shows the same controls, all applications work happily), but there is no sound. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.23-1-amd64 depends on: ii e2fsprogs1.40.3-1ext2 file system utilities and lib ii initramfs-tools [linux-initr 0.91c tools for generating an initramfs ii module-init-tools3.3-pre11-4 tools for managing Linux kernel mo linux-image-2.6.23-1-amd64 recommends no packages. -- debconf information: linux-image-2.6.23-1-amd64/postinst/depmod-error-2.6.23-1-amd64: false linux-image-2.6.23-1-amd64/postinst/bootloader-error-2.6.23-1-amd64: shared/kernel-image/really-run-bootloader: true linux-image-2.6.23-1-amd64/preinst/abort-install-2.6.23-1-amd64: linux-image-2.6.23-1-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.23-1-amd64/postinst/kimage-is-a-directory: linux-image-2.6.23-1-amd64/preinst/elilo-initrd-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/preinst/bootloader-initrd-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/preinst/lilo-initrd-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/postinst/bootloader-test-error-2.6.23-1-amd64: linux-image-2.6.23-1-amd64/postinst/old-dir-initrd-link-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/postinst/depmod-error-initrd-2.6.23-1-amd64: false linux-image-2.6.23-1-amd64/preinst/overwriting-modules-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/preinst/abort-overwrite-2.6.23-1-amd64: linux-image-2.6.23-1-amd64/preinst/initrd-2.6.23-1-amd64: linux-image-2.6.23-1-amd64/postinst/create-kimage-link-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/postinst/old-system-map-link-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/prerm/removing-running-kernel-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/prerm/would-invalidate-boot-loader-2.6.23-1-amd64: true linux-image-2.6.23-1-amd64/preinst/already-running-this-2.6.23-1-amd64: linux-image-2.6.23-1-amd64/preinst/failed-to-move-modules-2.6.23-1-amd64: linux-image-2.6.23-1-amd64/postinst/old-initrd-link-2.6.23-1-amd64: true -- Felipe Sateler signature.asc Description: This is a digitally signed message part.
Bug#375906: linux-headers-2.6.17-1-k7: Not installable on sid: depends on linux-kbuild-2.6.17 which does not exist
Package: linux-headers-2.6.17-1-k7 Severity: grave Justification: renders package unusable Kernel headers for 2.6.17-1-k7 are not installable because they depend on linux-kbuild-2.6.17, which does not appear to exist anywhere (packages.d.o yields no matches, save a kernel-kbuild-2.6.3 which only exists in the kfreebsd port). -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
