On Tue, Feb 08, 2022 at 12:01:22PM +0100, Julian Andres Klode wrote:
> It's worth pointing out that in Ubuntu, the generated MOK key
> is for module signing only (extended key usage 1.3.6.1.4.1.2312.16.1.2),
> kernels signed with it will NOT be bootable.
Why should these be separate keys? There's
On Mon, Feb 07, 2022 at 09:33:46PM +0900, Masahiro Yamada wrote:
> Added "Ben Hutchings "
>
> On Wed, Jan 5, 2022 at 3:13 AM Matthew Wilcox wrote:
> >
> > On Wed, Jan 05, 2022 at 12:39:57AM +0900, Masahiro Yamada wrote:
> > > > +vmlinux=$($MAKE -s -f
On Wed, Jan 05, 2022 at 12:39:57AM +0900, Masahiro Yamada wrote:
> +CC the maintainers of CERTIFICATE HANDLING
> M: David Howells
> M: David Woodhouse
> L: keyri...@vger.kernel.org
Davids, can one of you respond to this?
> On Sat, Dec 18, 2021 at 12:11 PM Matthew
On Wed, Jan 05, 2022 at 12:39:57AM +0900, Masahiro Yamada wrote:
> > +vmlinux=$($MAKE -s -f $srctree/Makefile image_name)
> > +key=
> > +if is_enabled CONFIG_EFI_STUB && is_enabled CONFIG_MODULE_SIG; then
> > + cert=$(grep ^CONFIG_MODULE_SIG_KEY= include/config/auto.conf | cut
> > -d\" -f2)
If the config file specifies a signing key, use it to sign
the kernel so that machines with SecureBoot enabled can boot.
See https://wiki.debian.org/SecureBoot
Signed-off-by: Matthew Wilcox (Oracle)
---
v2:
- Handle private keys stored in the pem file as well as adjacent to the
certificate
On Thu, Nov 04, 2021 at 06:28:40PM +0900, Masahiro Yamada wrote:
> On Thu, Oct 14, 2021 at 6:47 PM Ard Biesheuvel wrote:
> >
> > On Wed, 13 Oct 2021 at 22:07, Matthew Wilcox (Oracle)
> > wrote:
> > >
> > > If the config file specifies a signing key,
If the config file specifies a signing key, use it to sign
the kernel so that machines with SecureBoot enabled can boot.
See https://wiki.debian.org/SecureBoot
Signed-off-by: Matthew Wilcox (Oracle)
---
scripts/package/builddeb | 10 +-
1 file changed, 9 insertions(+), 1 deletion
On Thu, May 06, 2021 at 02:01:53PM +0200, Ard Biesheuvel wrote:
> On Thu, 6 May 2021 at 14:00, Matthew Wilcox (Oracle)
> wrote:
> >
> > If the config file specifies a signing key, use it to sign
> > the kernel so that machines with SecureBoot enabled can boot.
> &g
If the config file specifies a signing key, use it to sign
the kernel so that machines with SecureBoot enabled can boot.
See https://wiki.debian.org/SecureBoot
Signed-off-by: Matthew Wilcox (Oracle)
---
scripts/package/builddeb | 10 +-
1 file changed, 9 insertions(+), 1 deletion
Package: initramfs-tools
Version: 0.98.8
In /usr/share/initramfs-tools/hook-functions, xhci-hcd is spelled
simply xhci. It was renamed to xhci-hcd in 2.6.34-rc2.
Please update this script.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
his I2C bus is not acessible by the operating system (as far as I know).
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possi
On Tue, May 08, 2007 at 12:43:26AM +0300, Eddy Petri??or wrote:
> On 08/05/07, Geert Stappers <[EMAIL PROTECTED]> wrote:
> >reassign 422713 pciutils
> >tags 422713 d-i
>
> Probably I would have assigned this to the kernel than to pciutils.
>
> (OTOH, taking into account that (probably) due to thi
Package: linux-image-2.6.17-2-parisc
Version: 2.6.17-6
I found about 4 different ways to deadlock the current implementation of
rwlocks on parisc. I've committed a patch to our git tree which should
improve the situation, although it's obviously not had a lot of testing
yet, and is subject to bei
On Fri, Oct 28, 2005 at 05:34:06PM +0900, Horms wrote:
> Also, can someone look into HPPA, or point me at which patch to use?
> http://packages.vergenet.net/testing/linux-2.6-2.6.14/linux-2.6_2.6.14-1-hppa.log.gz
I know I *said* not to use the -pa0 kernel, but it's booted fine for me
on a K460 and
On Thu, Oct 27, 2005 at 02:39:24PM +0900, Horms wrote:
> On Wed, Oct 26, 2005 at 10:52:02PM -0600, Matthew Wilcox wrote:
> > On Thu, Oct 27, 2005 at 01:35:14PM +0900, Horms wrote:
> > > That looks a lot like the error I was seeing last week.
> > > Is anyone looking into
On Thu, Oct 27, 2005 at 01:35:14PM +0900, Horms wrote:
> That looks a lot like the error I was seeing last week.
> Is anyone looking into it?
It's fixed in CVS.
I blame the person who took a snapshot before we went to -pa1 ;-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "un
On Tue, Sep 27, 2005 at 08:52:26AM -0700, Christoph Lameter wrote:
> On Mon, 26 Sep 2005, dann frazier wrote:
>
> > The biggest headache with maintaining the ia64 kernel has probably been
> > with the non-SMP flavours. Generic/non-SMP configs seem to not get much
> > attention upstream. This mak
On Fri, May 06, 2005 at 10:42:25AM +0200, Nico Golde wrote:
> Hi,
> why the debian kernel-packages don't provide the config file
> via /proc?
It's in /boot instead
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of th
On Mon, Apr 04, 2005 at 10:51:30AM -0700, Greg KH wrote:
> Then let's see some acts. We (lkml) are not the ones with the percieved
> problem, or the ones discussing it.
Actually, there are some legitimate problems with some of the files in
the Linux source base. Last time this came up, the Aceni
On Thu, Mar 24, 2005 at 04:31:24AM -0500, Andres Salomon wrote:
> The way that arch/subarch specific patches are handled needs to be thought
> out. There are architectures that are close to linus kernels, and there
> are those that aren't. The preferred way to do things is to have
> something sim
On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote:
> As many of you may know on some machines users will need to install
> a current kernel before they will be able to upgrade woody to sarge
> (or better: glibc of woody to glibc of sarge). I've tried to use the
> available informati
On Wed, Mar 23, 2005 at 04:09:42PM +0100, Frank Lichtenheld wrote:
> How big is the chance that we will have another ABI change during
> sarge's lifetime (100%?). So it can't hurd to figure out the problems
> with that now independently of our decision in this matter...
Absolutely. It's bound to
On Tue, Mar 22, 2005 at 03:47:51PM -0500, Kyle McMartin wrote:
> This is basically a call for suggestions for what I should backmerge
> to 2.6.8 from recent CVS. I will go through the parisc-linux-cvs archive
> again and try to pull what I can see, but I'd like a bit of help.
In case it wasn't alr
On Tue, Mar 22, 2005 at 09:06:19AM -0300, Humberto Massa wrote:
> And I believe that the Vancouver proposal, if implemented as intended up
> to now, will not only affect what Debian really *is*, but in some ways
> will *destroy* what Debian is.
Debian has already decided to destroy what it is by g
On Mon, Mar 21, 2005 at 04:08:19PM +0100, Sven Luther wrote:
> Thanks. Maybe i should resign from my debian duties then since i am not
> wanted. Do you volunteer to take over my packages ? Please handle parted for
> which i am searching a co-maintainer since > 6 month, and take over the
> powerpc k
On Mon, Mar 21, 2005 at 03:20:29PM +0100, Sven Luther wrote:
> > Anyway, regarding kernels: I can imagine sometimes, especially with the
> > backlog we have currently, a swift processing of some kernel package
> > might be warranted and help Sarge. If there is such a case, it would
> > help if some
On Mon, Mar 14, 2005 at 09:16:46AM -, linay long wrote:
> I am new to debugging linux kernel. I have an mpc8540 based board with
> BDI2000. Now I am trying to debug Linux kernel.u-boot is the bootloader.The
> steps I followed listed below.The problem I am facing is
debian-kernel really isn't
On Mon, Feb 14, 2005 at 01:09:43PM -0500, Joey Hess wrote:
> Matthew Wilcox wrote:
> > I think de4x5 should be a driver of last resort. Tulip should always
> > be preferred to drive a given piece of hardware. I wouldn't shed any
> > tears if we stopped shipping de4x5 by
On Mon, Feb 14, 2005 at 06:21:24PM +0100, Marco d'Itri wrote:
> reassign 294867 kernel-image-2.6.8-i386
> thanks
>
> If a driver hangs the system when loaded, it is a good hint of a kernel
> bug.
I think de4x5 should be a driver of last resort. Tulip should always
be preferred to drive a given p
On Wed, Feb 02, 2005 at 07:43:36AM +0100, Christian Perrier wrote:
> So, please please please, people who will attend this meeting, only
> focus on that one topic and have all your discussions driven by it and
> only it.
Unfortunately, your comments seemed to get held up in your mailsystem,
so did
On Mon, Jan 31, 2005 at 05:20:56PM +0100, Petter Reinholdtsen wrote:
> [Matthew Wilcox]
> > I will not subject myself to the whims of Rob Levin.
>
> Why do you believe others are interested in your conflict with some
> (to me at least) unknown person Rob Levin?
He runs
On Mon, Jan 31, 2005 at 04:12:06PM +0100, maximilian attems wrote:
> arch Maintainer please attend, to have your opinion voiced.
I will only attend if the meeting is hosted on a different IRC network.
I will not subject myself to the whims of Rob Levin.
--
"Next the statesmen will invent cheap l
On Fri, Jan 07, 2005 at 02:32:19PM -0500, Andres Salomon wrote:
> 3) 2.4/2.6 random poolsize sysctl handler integer overflow
> 4) 2.6 scsi ioctl integer overflow and information leak
Fix for this one:
http://linux.bkbits.net:8080/linux-2.5/[EMAIL PROTECTED]
> 5) 2.2/2.4/2.6 moxa serial driver bss
On Sun, Jan 09, 2005 at 08:33:51PM +0100, Marc Haber wrote:
> Actually, the kernel of my dreams is more near to the vanilla
> kernel.org kernel, so I'd like to be able to throw out patches that
> you need to apply because of your _much_ broader user base.
>
> otoh, I would like to run a 2.6.10 ker
On Thu, Jan 06, 2005 at 06:08:29PM +0100, Robin Bultot wrote:
> BUT when I rebooted in 2.6.9 I get an error:
> VFS: Cannot open root device "hde3" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
>
> My motherboa
On Mon, Dec 13, 2004 at 12:15:57PM -0500, Christopher Priest wrote:
> Is this helpful
> http://web.archive.org/web/2711071330/sanjose.alteon.com/license-agree.shtml
Not really. That licence doesn't allow Debian to distribute whatever
it is that's being licenced. There's only permission for p
On Mon, Dec 13, 2004 at 03:04:34PM +, HÃ¥vard Dahle wrote:
> I am sorry. As it turns out, this is now resolved, and I suspect that eth1394
> never was the culprit.
>
> I am not sure what was the real fix. I am tracking debian sid, and updates to
> discover (I think) made the problem go away.
On Mon, Dec 13, 2004 at 04:17:17PM +0900, Horms wrote:
> On Wed, Dec 08, 2004 at 06:29:34PM +0000, Matthew Wilcox wrote:
> > On Wed, Dec 08, 2004 at 07:26:40PM +0100, Paul Akkermans wrote:
> > > Hello everyone,
> >
> > HEY! RETARD!! This is the third time this we
On Sun, Dec 12, 2004 at 03:17:31PM -0500, Nathanael Nerode wrote:
> Warning: long. CC'ed to debian-legal in case anyone there knows anything more.
How about cc'ing the author of the driver? He might know the answer.
> The source for the acenic driver is in fact in the source package for
> the k
On Wed, Dec 08, 2004 at 07:26:40PM +0100, Paul Akkermans wrote:
> Hello everyone,
HEY! RETARD!! This is the third time this week you've posted to
debian-kernel. This is the third time I'm telling you to fuck off.
I was polite before. But now you've made me angry. GO AWAY.
--
"Next the state
On Tue, Dec 07, 2004 at 09:51:30PM +0100, Paul Akkermans wrote:
> Hi group,
>
> I have a compicated question. I am analysing the input core. My question is
> if it is so that the functions and procedures which are defined and exported
> in input.c can be overridden in other modules (other than i
On Sat, Dec 04, 2004 at 01:01:33PM -0500, Kyle McMartin wrote:
> * ACENIC firwmare, driver disabled:
> . drivers/net/acenic_firmware.h
>
> So there's a good reason why you're unable to use these cards.
ITYM "good reason to switch to Ubuntu, Gentoo or Fedora". HTH.
--
"Next the statesmen will i
On Sat, Dec 04, 2004 at 12:18:01PM -0500, Joey Hess wrote:
> Discover says to use the acenic driver for these, but it does not seem
> to be available in the 2.4 or 2.6 kernels for hppa or i386. I do see the
> driver the the kernel source so please turn it on.
I thought the anti-firmware fanatics h
On Fri, Dec 03, 2004 at 02:57:24PM +0100, Paul Akkermans wrote:
> I am analysing the input layer of the kernel 2.6.7 and I came across this
> function and I have no idea what it is for. Can anybody help me?
I suggest you ask kernelnewbies at
http://www.kernelnewbies.org/mailinglist.php3
This lis
On Wed, Oct 06, 2004 at 11:33:38PM +0530, Rishi wrote:
> After re-booting... the top program shows only one CPU.
press '1'.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and w
On Fri, Oct 01, 2004 at 03:36:36PM -0600, Jim Cromie wrote:
> having /proc/config.gz available would be a nice default,
> Ive been having some difficulty building a working kernel,
> and the kernel-image-2.6.8.1-k7 works. It would be handy
> as a starting point.
What's wrong with /boot/config?
-
On Wed, Sep 22, 2004 at 06:25:23PM +0900, Horms wrote:
> On Sun, Sep 19, 2004 at 09:21:12AM +0200, Robert Millan wrote:
> > On Fri, Sep 17, 2004 at 08:38:56AM +0200, Christoph Hellwig wrote:
> > > tags 272029 +upstream
> > > thanks
> > >
> > > Please get feature-patches merged upstream before bugg
On Thu, Sep 16, 2004 at 08:34:38PM +0200, Jens Schmalzing wrote:
> Sorry. I got the message completely wrong. I really was:
>
> | PCI: Enabling device :00:0c.0 ( -> 0003)
> | sym.0.12.0: MMIO base address disabled.
OK, so that's entirely different. That happens if we read 0 directly
fr
On Thu, Sep 16, 2004 at 04:22:54PM +0200, Jens Schmalzing wrote:
> > As upstream maintainer, I'd like more information about it please ...
>
> > - How does it "not work properly"? Does it hang on first access to
> >the chip, or does it suffer data corruption?
>
> It outputs a "can't map PCI
On Thu, Sep 16, 2004 at 11:51:31AM +0200, Jens Schmalzing wrote:
> I recently encountered a machine (a Thinkpad 860) with a NCR 53C810
> SCSI controller that would not work properly unless the config option
> CONFIG_SCSI_SYM53C8XX_IOMAPPED was set. Under these circumstances,
> installation was a r
On Mon, Sep 13, 2004 at 11:10:11PM +0200, maks attems wrote:
> Use the CPUFreq governor 'userspace' as default. This allows
> you to set the CPU frequency manually or when an userspace
> - programm shall be able to set the CPU dynamically without having
> + programme sh
On Mon, Sep 06, 2004 at 05:39:20PM +0200, eolyte wrote:
> It seems that only the devices that are plugged before the uhci_hcd module is
> loaded are detected. These are working properly, but if I plug another device
> after, it doesn't even appear in /proc/bus/usb/devices, and idem if i
> unplug
On Sun, Sep 05, 2004 at 11:53:13PM -0500, [EMAIL PROTECTED] wrote:
> Hello All
>
> I am a recent convert to Debian. have installed Debian in my old machine
> i386 machine at 300 Mhz with 256 MB RAM.and 30GB HDD.
> It connects to the internet via a router. I would like to know if there is
> a
On Fri, Aug 20, 2004 at 05:15:36PM -0700, Mike Fedyk wrote:
> Matthew Wilcox wrote:
> >32-bit PCI cards should work without problems in 64-bit slots, though.
> >
> That's what I thought, but I have an Adaptec 2940UW card that causes
> instability reliably in 64bit pci
On Fri, Aug 20, 2004 at 02:29:50PM -0700, Mike Fedyk wrote:
> Hi,
>
> Sorry for the premature bug report, but it looks like the problem was
> caused by a 32-bit PCI SCSI card in a 64-bit slot.
32-bit PCI cards should work without problems in 64-bit slots, though.
--
"Next the statesmen will in
On Fri, Aug 13, 2004 at 03:22:14PM +0200, Christoph Hellwig wrote:
> On Tue, Aug 03, 2004 at 11:12:20AM -0600, dann frazier wrote:
> > The only ones that aren't already upstream, afaict, are:
> > sym53c8xx_revert.patch - The new domain validation stuff mysteriously
> >
On Sun, Jul 11, 2004 at 01:04:59PM +0200, Bastian Blank wrote:
> On Sun, Jul 11, 2004 at 11:43:57AM +0200, Christoph Hellwig wrote:
> > CONFIG_SYN_COOKIES
> >
> > Syn cookies are bad idea in these day's internet, no need to
> > waste space for support.
>
> Err, you want to make any machin
On Mon, Jul 05, 2004 at 10:29:34PM +0200, Kim wrote:
> eax: 014c ebx: c130aaf0 ecx: 1000 edx: 0001038f
Single bit set.
> Does anyone know what this is?
Bad RAM. Run memtest86 to confirm, but you've got all the classic
symptoms of a
On Sun, Jun 27, 2004 at 01:27:09PM +0200, Alexander Reinholdt wrote:
> Configuring the kernel sources fails with an compiler error:
>
> dustpuppy:/usr/src/kernel-source-2.6.6# make menuconfig
> HOSTCC scripts/basic/fixdep
> cc1: internal compiler error: Speicherzugriffsfehler
> Please submit a fu
On Fri, Jun 18, 2004 at 09:02:25AM -0400, Brian Thomas Sniffen wrote:
> I would be much more convinced if I saw an argument from the
> GPL-incompatible-firmware-is-OK side as to why the GPL prohibits
> distributing linkages of GPL'd and GPL-incompatible code.
The interpretation favoured by kernel
On Thu, Jun 17, 2004 at 06:03:16PM +, Jim Marhaus wrote:
> Traditionally people have erred on the side of caution in interpreting free
> licenses, following the wishes of the copyright holder and looking to the
> license's author for guidance. In this case the FSF indicates the binary
> firmwar
On Tue, Jun 15, 2004 at 09:01:52PM -0500, Joe Wreschnig wrote:
> At best that solves a third of the problem.
It solves the problem at hand -- that Debian has no permission to
distribute the file. You can now go back to wanking about firmware all
you like. I shan't bother with that.
--
"Next th
On Tue, Jun 15, 2004 at 05:51:03PM -0500, Joe Wreschnig wrote:
> On Tue, 2004-06-15 at 14:38, Andreas Schuldei wrote:
> > * Nathanael Nerode ([EMAIL PROTECTED]) [040615 21:27]:
> > > I request that the people planning to take over kernel maintenance comment
> > > ASAP on their plans regarding this
On Mon, Jun 14, 2004 at 12:57:15PM -0400, Nathanael Nerode wrote:
> I ask because such a file is present in Debian's Linux kernel sources and
> there seems to have been no attempt to remove it, despite the upload of
> new versions since the bug report.
>
> drivers/usb/misc/emi26_fw.h:
>
> * The
On Sun, Jun 13, 2004 at 06:35:40PM -0700, William Lee Irwin III wrote:
> Please, no debates on the firmware subject.
>
> Here is the current blacklist of tainted files that need to be
> sanitized and/or removed from virgin mainline.
Why is drivers/scsi/qlogicisp_asm.c not on this list?
--
"Next
Try booting with "pci=noacpi". I bet the devices will show up in
lspci then. There's a known bug with broken BIOSes.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will d
On Sun, May 30, 2004 at 05:37:05PM +0200, Goswin von Brederlow wrote:
> Christoph Hellwig <[EMAIL PROTECTED]> writes:
> > No, theres lots of code in kernelspace that assumes a partitioned disk
> > has a block of minors. Use a volume manager instead of traditional
> > partitions if you need more th
67 matches
Mail list logo