Package: src:linux
Version: 6.12.13-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I wanted to use the power LED on this laptop for HDD activity, saw triggers can
do this...
* What exactly
Package: firmware-iwlwifi
Version: 20190114-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
fresh install.
* What exactly did you do (or not do) that was effective (or
ineffective)?
downloaded and tested kernel and firwmare from backports, reinstalled
firmw
hey are supporting Xen HVM right
now.
So, there's no need for an uncompressed/gzipped kernel anymore and the
default one boots just fine. Although I'm still curious regarding the
possibility of booting an uncompressed kernel on
native/full-virtualization, I guess this does not makes sense.
I'm really thankful for you support and inclination to help us on the matter.
Very best regards,
Tiago.
--
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil
th on VirtualBox and
Xen on Oracle Cloud. In VirtualBox, I got the error pasted on my first
message. In Oracle Cloud I have no access to the boot logs to confirm
if it happens to be exactly the same.
--
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil
rosoft portable executable
18356 0x47B4 xz compressed data
3108600 0x2F6EF8xz compressed data
Not sure about what bytes "0-18355" means. Maybe a false-positive?
If I run it with "-e", it get two files ("47B4.tar" and "2F6EF8.tar&qu
this,
because there is more than one report of successfully booting
uncompressed kernels[4][5].
- Is "extract-linux" stripping some essential information (the script
looks for an offset to start the decompression process) from the
kernel image that is needed to boot it later? If so, is there a
I have justed booted into most recent jessie kernel with sysvinit and
it is working fine, with no more errors on the logs. It seems there is
a problem somewhere between the kernel and systemd.
Tiago
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of
Hi Ben,
Thanks for answering.
Ben Hutchings writes:
> Control: tag -1 moreinfo
>
> On Thu, 2015-03-12 at 08:57 -0400, Tiago Saboga wrote:
>> Package: src:linux
>> Version: 3.16.7-ckt7-1
>> Severity: critical
>> Justification: breaks the whole system
>&g
Package: linux-headers-3.16-1-amd64
Version: 3.16.2-2
Severity: normal
Hi,
I'm having the following issue when building virtualbox driver:
kmk -C vboxdrv clean
kmk: Entering directory `/usr/src/modules/virtualbox/vboxdrv'
kmk KBUILD_VERBOSE= SUBDIRS=/usr/src/modules/virtualbox/vboxdrv
SRCROOT=/u
the resume file never got generated.
Thanks for your work,
Tiago
[1] - http://www.debian.org/releases/stable/i386/apds03.html.en
-- Package-specific info:
-- initramfs sizes
-rw--- 1 root root 13M Feb 4 23:08 /boot/initrd.img-2.6.32-5-686
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4
Sorry, my bad. I thought it was already in stable, instead it is in
stable-proposed. Thank you!
--
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/1305280184.9411.5.ca
I see most kernels are fixed, including linux-image-2.6.32-5-xen-686.
But linux-image-2.6.32-5-xen-amd64 is missing (currently in version
2.6.32-31)! Do you plan to fix it? Thanks.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
Package: linux-image-2.6.14-2-686
Version: 2.6.14-7
Severity: normal
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686
Locale
13 matches
Mail list logo
