12288 2 amdgpu,ext4
--
Eric Valette
On 14/05/2024 23:39, Tom Overlund wrote:
It's actually upstream. I ran the same:
$ make bindeb-pkg
on the upstream source as I did on the Debian source, and yes, it gave me .deb
packages.
Here's the repo for the upstream script that was part of the problem:
https://github.com/torvalds/lin
As title says, this is a bug in debian additionnal scripts to build the
packages, not upstream.
Using upstream code works but does not produce package and knowing
exacltly the minimal kernel setup for debian is not obvious.
Once you have a working .deb you can probably reuse the .config.
--
It has been a month and nobody did care on 6.6. I bet I may be identical
for 6.7.
NB : I reported other bugs as the localmodconfig options do not include
many rather basic options (ISO 9660, usb disks, ...).
This one can be fixed by adding the relevant config options...
-- eric
On 15/04/2024 11:32, Diederik de Haas wrote:
On Monday, 15 April 2024 10:41:55 CEST Eric Valette wrote:
Why is there no 6.6 up-to-date kernel pushed in testing as well? Do you
plan to wait until 6.6 enter stable? When?
Nothing gets 'pushed' to Testing. Packages *transition* to Te
apt-cache policy linux-image-amd64
linux-image-amd64:
Installé : 6.6.15-2
Candidat : 6.7.9-2
Table de version :
6.7.9-2 500
500 http://ftp.de.debian.org/debian unstable/main amd64 Packages
*** 6.6.15-2 500
500 http://ftp.de.debian.org/debian testing/main amd64 Packages
1
Package: linux-source-6.6
Version: 6.6.15-2
Severity: normal
After using make localmodconfig I discovered that USB keys cannot be mounted,
nor ISO images.
I think theses are basics that shoul be enabled like other stuffs.
-- System Information:
Debian Release: trixie/sid
APT prefers stable-
Package: linux-source-6.6
Version: 6.6.15-2
Severity: minor
I never installed pahole before... It is not in the list of required package.
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'unstab
On 10/03/2024 12:25, Bastian Blank wrote:
Control: severity -1 important
Yes, the kernel included Debian package support can't handle compressed
modules in various ways. Just disable them for now.
OK. Will try.
Maybe doc should be updated until it is fixed.
It however means that you can
Package: linux-source-6.6
Version: 6.6.15-2
Severity: grave
Justification: renders package unusable
As I wanted:
1) to stay on long term kernel 6.6 branch,
2) 6.7.x has been uploaded to unstable already,
3) I would like to enable NTFS3, and AMD TEE
I decided I will try to recompile
As I wanted:
1) to stay on long term kernel 6.6 branch,
2) 6.7.x has been uploaded to unstable already,
3) I would like to enable NTFS3, and AMD TEE
I decided I will try to recompile the kernel myself first (I have MOK
keys already registered and used to manually sign so
The unsigned version is available, so are the linux-libc-dev package.
I know the autosign transition is ongoing but as the build is
successful why not produce a signed version?
-- eric
On 06/08/2023 00:08, Hans van Kranenburg wrote:
Hi Eric,
I think I can help answering this one. It's a good question.
Thanks for taking the time to answer and sorry for this mailing list
polution but debian-kernel-maint mailing list is long dead.
On 8/5/23 10:43, Eric Valette wrote
Hi Debian kernel maintainers,
I have a question regarding the way kernel versions are selected for the
stable tree. First, I am a very long Debian user and have been building
my own kernel for years, managing self signed kernel and modules for
secure boot and my Debian version is always a unst
Package: linux-image-6.3.0-1-amd64
Version: 6.3.7-1
Severity: normal
Tags: patch
tvheadend does not work with this kernel. 6.1.27 does.
The patch and the probme is also found by other
https://bbs.archlinux.org/viewtopic.php?id=286421
-- System Information:
Debian Release: trixie/sid
APT p
Package: linux-image-amd64
Version: 6.3.7-1
Severity: normal
Tags: patch
tvheadend does not work with this kernel. 6.1.27 does.
The patch and the probme is also found by other
https://bbs.archlinux.org/viewtopic.php?id=286421
-- System Information:
Debian Release: trixie/sid
APT prefers stab
On 16/02/2022 22:36, Eric Valette wrote:
On 16/02/2022 21:01, Eric Valette wrote:
On 16/02/2022 20:58, Alex Deucher wrote:
On Wed, Feb 16, 2022 at 2:56 PM Eric Valette
wrote:
Here is the dmesg. For bisecting, I'm not home and the Intrenet
connection is just too slow.
In order to h
On 20/02/2022 16:48, Dominique Dumont wrote:
On Monday, 14 February 2022 22:52:27 CET Alex Deucher wrote:
Does the system actually suspend?
Not really. The screens looks like it's going to suspend, but it does come
back after 10s or so. The light mounted in the middle of the power button does
On 16/02/2022 21:01, Eric Valette wrote:
On 16/02/2022 20:58, Alex Deucher wrote:
On Wed, Feb 16, 2022 at 2:56 PM Eric Valette
wrote:
Here is the dmesg. For bisecting, I'm not home and the Intrenet
connection is just too slow.
In order to help a bit, I started to build kernel wit
On Tue, 15 Feb 2022 15:42:27 -0500 Alex Deucher
wrote:
What chip is this? Can you provide the full dmesg output?
Its a a renoir chip with a second gpu : [Radeon RX 5500/5500M / Pro 5500M].
Processor Information
Socket Designation: FP6
Type: Central Processor
Family:
On 15/02/2022 19:14, Eric Valette wrote:
Since I upgraded from 5.10 (own compiled kernel or debian kernel) to
5.15 (own compiled from same config or debian kernel) and even 5.16
kernel from debian, I get this behavior :
1) First suspend and resume works,
2) But later suspendend
Since I upgraded from 5.10 (own compiled kernel or debian kernel) to
5.15 (own compiled from same config or debian kernel) and even 5.16
kernel from debian, I get this behavior :
1) First suspend and resume works,
2) But later suspendend always fails. I have kernel exce
On 21/10/2016 16:36, Ben Hutchings wrote:
On Fri, 2016-10-21 at 12:40 +0300, Konstantin Demin wrote:
I disagree: you fix debian code but upstream kernel is also affected.
I wanted to compile the upstream 4.4.26 for the COW fixe and cannot.
Please revert.
It is absolutely supported (so long
On 10/21/2016 11:40 AM, Konstantin Demin wrote:
I disagree: you fix debian code but upstream kernel is also affected.
I wanted to compile the upstream 4.4.26 for the COW fixe and cannot.
Please revert.
$ rmadison linux
linux | 4.5.5-1 | unstable| source
lin
On 10/21/2016 11:18 AM, Debian Bug Tracking System wrote:
Processing control commands:
reassign -1 src:linux
Bug #841500 [gcc-6] gcc-6: Unable to compile upstream kernel with previous
.config
Bug reassigned from package 'gcc-6' to 'src:linux'.
No longer marked as found in versions gcc-6/6.2.0
I never use debian kernel and connaot compile upstream kernel with gcc-6
now.
--eric
On 30/06/2016 22:00, Eric Valette wrote:
On 30/06/2016 21:46, Martin Pitt wrote:
Hello Eric,
Eric Valette [2016-06-30 21:33 +0200]:
I have an initrd on this machine so this is something else
OK, I owe you an apology then, sorry. In #771652 you didn't yet, so I
just assumed that was
And yes the proposed patches works I use them for two weeks now. Still
not in 3.1 RC :-(
-- eric
--
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/4e5a7817.2020..
On 04/01/2010 13:00, Martin Michlmayr wrote:
Eric,
Here are instructions to fix your DNS-323. I've tested them on my
machine.
Thanks. My DNS323 is up and running with its mtd again. Hope I was
nearly the only one.
BTW I used a modified flash-kernel script to generate the images and I
thin
On 27/12/2009 10:20, Martin Michlmayr wrote:
You like crying over spilt milk, don't you?
Probably as you like breaking other hardware inadvertently...
We support a lot of NAS
devices and I cannot test every single change on every device.
You should. You cannot rely on every single users ha
On 26/12/2009 18:59, Martin Michlmayr wrote:
Except I can no more update my kernel because it use the mtdblock
devices => the bug is not fixed for me as it requires more than
providing a correct kernel. You need also to provide a way to reflash
it.
We told you already - you need a serial cons
On 26/12/2009 17:18, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the linux-2.6 package:
#562205: linux-image-2.6.32-trunk-orion5x: Not more mtd device => impossible
to flash new kernel
It has been closed by Ben Hutching
On 25/12/2009 17:54, Martin Michlmayr wrote:
* Eric Valette [2009-12-24 18:08]:
Reading flash-kernel, I can probably rewrite it to skip the mtd check
but I would rather be sure that this will be understood by uboot
rather using kermit and uboot command rather than writing it directly
to mtd
On 24/12/2009 16:14, Martin Michlmayr wrote:
- use the serial console (as documented on my web page).
Just in case as I do not want to make a full reinstall. I have in /boot
initrd.img-2.6.31-1-orion5x and vmlinuz-2.6.31-1-orion5x that works as
it flashed the .32-1. How can I recreate corr
On 24/12/2009 16:47, Eric Valette wrote:
If loading the module doesn't work, I see
two possibilities to recover your machine:
- maybe you can use kexec to execute a good kernel and then write it
to flash.
What is the correct procedure and what kernel is supposed to work?
kexec -l
On 24/12/2009 16:14, Martin Michlmayr wrote:
* Eric Valette [2009-12-24 00:11]:
Yes it is on a DNS 323. But how will this be fixed? Is it possible to
recreate the mtd devices after having flashed a kernel without proper
in kernel support? Or will you find a way to upload the drivers via
Found in version should be 2.6.32-1 not 2.6.32-2. Its the 2.6.32-1
kernel that has problem.
Besides, If anyone can guaranty I will be able to fix my problem OK for
normal, but so far, I'm still skeptical: without the mdt devices, I
cannot flash any new kernel version.
Modprobing the correct
On 24/12/2009 00:16, Eric Valette wrote:
modprobe cfi_cmdset_0002
Correction: I reinstalled the
linux-image-2.6.32-trunk-orion5x_2.6.32-1_armel.deb (of course the flash
part failed but the modules where back in sync with kernel config) and
loaded the modules. But it did not recreate any
On 23/12/2009 23:25, Martin Michlmayr wrote:
* Eric Valette [2009-12-23 22:07]:
Is there any method to recreate mdt devices by hand so that I can get
back a new mtd enabled kernel?
Try:
modprobe cfi_cmdset_0002
I already did before posting but it does not work. No error message but
On 23/12/2009 22:09, Martin Michlmayr wrote:
* Eric Valette [2009-12-23 21:05]:
The previous kernel has probably a bug as I have /proc/mtd empty and
no /dev/mtdblks! I will never be able to update a kernel unless I
mange to get access to the flash again!
Is this on a D-Link DNS-323? If so
Package: linux-2.6
Version: 2.6.32-2
Severity: critical
Justification: breaks unrelated software
The previous kernel has probably a bug as I have /proc/mtd empty and no
/dev/mtdblks! I will never be able to update a kernel unless
I mange to get access to the flash again!
-- Package-specific info
You may find usefull to know that by default in 2.6, the sound is
disabled. You need alsamixer/alsamixergui to set the volume.
--
__
/ ` Eric Valette
/-- __ o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace
Tel: +33 (0)2 99 85
42 matches
Mail list logo
