f. With the patch, it should be able to handle any valid
kernel composite device number.
Respectfully submitted,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscri
; then
in the parse_numeric function. Problem solved. And yes, I realize that using
disk labels or uuids is the recommended way to specify the root file system
these
days. But that's another story, as I mentioned earlier.
Respectfully yours,
--
.''`. Stephen Powell
case you're interested.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
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.o
them seem to have
a colon in them. I suggest the following code to replace the above:
case "${modalias}" in
""|*:*)
:
;;
*)
force_load "${modalias}"
;;
esa
Control: tags -1 patch
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
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/119
id=0b991f5cdcd6201e5401f83ca3a672343c3bfc49
I have personally tested the fixes, and they work for me on my z890.
Respectfully submitted,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with
=a313bdc5310dd807655d3ca3eb2219cd65dfe45a
--
.''`. Stephen Powell
: :' :
`. `'`
`-
On Thu, 27 Aug 2015 18:06:49 -0400 (EDT), Ben Hutchings wrote:
>
> On Wed, 2015-08-26 at 21:33 -0400, Stephen Powell wrote:
>>
>> The Linux kernel in jessie fails to build from source for
>> the combination ARCH=s390, CONFIG_SMP=n, and CONFIG_DYNAMIC_DEBUG=y.
>> Co
Forwarding the below message to the relevant Debian Bug Log
- Forwarded Message -
From: Luis Henriques
To: Sebastian Ott
Cc: Martin Schwidefsky , Stephen Powell
, Luis Henriques ,
kernel-t...@lists.ubuntu.com
Sent: Thu, 03 Sep 2015 06:38:07 -0400 (EDT)
Subject: [3.16.y-ckt stable
Forwarding to the Debian bug log
- Forwarded Message -
From: Luis Henriques
To: linux-ker...@vger.kernel.org, sta...@vger.kernel.org,
kernel-t...@lists.ubuntu.com
Cc: Sebastian Ott , Martin Schwidefsky
, Stephen Powell , Luis Henriques
Sent: Fri, 04 Sep 2015 09:08:33 -0400 (EDT
file is renamed to the expected naming convention (*_s390x.deb).
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
nder
"Kernel Hacking".) Then I issued
make KDEB_PKGVERSION=3.14.4-1 KBUILD_PKG_ROOTCMD=fakeroot \
INSTALL_MOD_STRIP=1 KBUILD_DEBARCH=s390x deb-pkg
as a non-root user. It built a kernel image package just the way I wanted it.
--
.''`. Stephen Powell
: :' :
submitted to kernel.org soon, if it hasn't been already.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
n
> that has happened.
The patch is now official.
Here is a link to the official git commit at kernel.org:
https://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h=features&id=26d766c60f4ea08cd14f0f3435a6db3d6cc2ae96
--
.''`. Stephen Powell
: :' :
`. `
have tested, and it fixes the problem. Here's a link to the
official upstream git commit at kernel.org:
https://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/commit/?h=features&id=e512d56c799517f33b301d81e9a5e0ebf30c2d1e
--
.''`. Stephen Powell
: :
the next higher multiple of 8. Is this correct?
I have no idea. What I do know is that the current algorithm doesn't work for
me, but the above does. For now. Will it continue to work in the future?
I don't know.
--
.''`. Stephen Powell
: :' :
`. `'
ant to, with
any boot loader.
Let me know what you think.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
hat says
... root=806 ...
(the leading zero is suppressed). Chances are, the user is not directly
specifying the root device as a hexadecimal number anywhere. The boot
loader makes this substitution. lilo has done this forever, and zipl
was patterned after lilo.
--
.''
lation.
The kernel command line sees
... root=UUID=055d446a-977d-4aa6-877d-62c716f5e85a ...
which gets you around the problem for now.
Respectfully submitted,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@
ually made it into a future stable point release.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
with no apparent ill effects.
However, you might want to look things over to see if anything
needs to be changed in the code logic as well.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.o
On Sat, 18 Dec 2010 19:59:00 -0500 (EST), Stephen Powell wrote:
>
> This is a bug report for drivers/s390/block/dasd_eckd.c in the
> Linux kernel source code. The device table indicates that a
> combination of a 3880 storage control unit and a 3390 DASD device
> type is valid. Th
bug report can be found at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607416
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
The real-time preemption patches for kernel 3.11 do not appear to be present
in linux-source-3.11. What happened to them?
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of &q
On Sun, 24 Nov 2013 23:25:41 -0500 (EST), Ben Hutchings wrote:
>
> On Sun, 2013-11-24 at 20:29 -0500, Stephen Powell wrote:
>>
>> The real-time preemption patches for kernel 3.11 do not appear to be present
>> in linux-source-3.11. What happened to them?
>
> The
to be the common denominator. I don't
even know where to start. I may as well turn my computer off until
I can find a stable kernel. If there's anything I can do to help,
please let me know.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUB
vives long enough for
me to login as root and issue these two commands before it crashes.
But once I get that far, I haven't had any problems since. I now
think 736892 really is a bug, and that it is the cause of the kernel
crashes I have been experiencing.
--
.''`. Stephe
716703 ]---
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
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/2027073877.834564.1391741777992.javamail.r...@md01.wow.synacor.com
On Fri, 07 Feb 2014 05:49:55 -0500 (EST), Ben Hutchings wrote:
> Stephen Powell wrote:
>> [38587.355263] BUG: unable to handle kernel paging request at
>> 081c
>
> Looks like a bit flip to me (0 turned to 0x800 and then treated
> as a real pointer). D
n all systems with
non-ECC memory
from now on. Thanks for the tip!
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas
On Sat, 01 Feb 2014 14:54:32 -0500 (EST), Stephen Powell wrote:
>
> I may have found the problem. This problem may be related to Debian bug
> number 736892.
As it turned out, Debian bug number 736892 was an unrelated problem.
My real problem was faulty memory (RAM). Ben, I know
#CP VINPUT VMSG 1
as opposed to letting a timeout occur and letting the default kernel
boot via a timeout. I don't know why that matters, but that has been
my experience.
I will be more than happy to assist in debugging this.
--
.''`. Stephen Powell
: :'
CPGIR450W CP entered; disabled wait PSW 00020001 8000 0001DE26
I have backed out to a 2.6.32 kernel until the problem is resolved. The 2.6.38
kernel is obviously unusable for me.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email
nion bug
number 620126 in package sysconfig-hardware for the same bug in another
package.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
handled. I will run the upstream
vanilla kernel source until a Debian package containing the fix is
available. Thanks, Jonathan.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of &q
On Thu, 14 Apr 2011 21:48:56 -0400 (EDT), Stephen Powell wrote:
>
> The problem appears to be fixed in the latest vanilla upstream kernel
> source, which at the time of this writing is 2.6.39-rc3.
> ...
Oops! I spoke too soon. I checked the server before I went to bed
last night
hours now,
which is definitely a good sign. Without this patch, I've not been able
to keep a 2.6.38 s390x kernel up for more than a few hours. Unfortunately,
since I can't reproduce the problem on demand, I cannot say with 100%
certainty that the problem is fixed, but it looks good and
On Tue, 19 Apr 2011 02:34:01 -0400 (EDT), Heiko Carstens wrote:
> Stephen Powell wrote:
>> I installed linux-image-2.6.38-2-s390x version 2.6.38-3 on my up-to-date
>> Wheezy
>> system today. It runs in a virtual machine under z/VM 5.4.0 running in an
>> LPAR
>>
I ask sta...@kernel.org to port the whole commit?
(It may have dependencies on previous commits and get complicated rather
quickly.) Or do I ask them to cherry pick that one-line change in
drivers/s390/block/dasd_eckd.c? I could use some advice here.
--
.''`. Stephen Powell
; Date: Thu Feb 17 13:13:55 2011 +0100
>
> [S390] dasd: correct device table
>
> The 3880 storage control unit supports a 3380 device
> type, but not a 3390 device type.
>
> Reported-by: Stephen Powell
> Signed-off-by: Stefan Haberland
> Signed
On Sun, 24 Apr 2011 19:52:47 -0400 (EDT), Greg KH wrote:
> On Sat, Apr 23, 2011 at 09:10:19AM -0400, Stephen Powell wrote:
>> On Fri, 22 Apr 2011 23:09:50 -0400 (EDT), Jonathan Nieder wrote:
>>>
>>> If you run "git log dd30ac3 --grep='dasd: correct device t
,sg
usbcore 108302 3 ehci_hcd,uhci_hcd
usb_common 12338 1 usbcore
Obviously not all of these need to be in the initial RAM file system.
When using MODULES=most, everything works fine.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
-
tabs,
inserting unwanted line breaks, etc. Therefore, to preserve the patch
unaltered, I provided a link instead.
I have tested the patch on my system, and it works fine. The patch is
applied to /usr/share/initramfs-tools/hook-functions.
--
.''`. Step
ccur if the user
specifies a block special file name or a symbolic link to a block special
file name.
For more information, see my LILO web page:
http://users.wowway.com/~zlinuxman/lilo.htm
I hope this helps.
--
.''`. Stephen Powell
: :' :
`. `'`
risk. But if you do try it, please report
your results.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
an the complete string is numeric
or is
the null string.) But these are not regular expressions, these are shell
patterns.
As a shell pattern, [0-9]* means "a single numeric digit at the beginning of the
string followed by zero or more arbitrary characters". Your patch solves t
wowway.com/~zlinuxman/parse_numeric.patch
I have used a link to it, rather than include the patch inline, since
my e-mail client has the nasty habit of expanding tabs, inserting unwanted
line breaks, etc.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIB
hat you have not encountered. Have you tried the patch? (You will of
course need to rebuild the initial RAM file system after applying the
patch.)
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debia
re using the "root" kernel boot
parameter in a non-standard way, in which case you are on your own.
There is a legitimate bug in the parse_numeric function which has
been discovered as the result of your bug report, and it appears to
me that this proposed patch fixes that problem. But adding su
tools assumes also. If those assumptions
ever become a problem, lilo will probably specify the root file system
in a different way rather than continuing to use a hexadecimal number.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to de
ill. If you want
to enhance the code to correctly handle the full 16-hex-digit composite
device number, go ahead. As you say, it's trivial. And that would
once again make you the author of the final patch, which is fine.
--
.''`. Stephen Powell
: :' :
`. `'`
author or the Debian
package maintainer for kernel-package (i.e. Manoj). It seems to
work for me and for my purposes, but I do not warrant the patch
to be free from defects. Take this with as many grains of salt
as you think it's worth.
P.S. kernel-package is also incompatible with make 3.8
far all my changes have been to generic KMS code and are not
nouveau-specific.
I'd rather wait to publish my fixes until I have everything working
correctly. The trouble is I haven't had much time to work on it lately.
--
.''`. Stephen Powell
: :' :
`. `'
l fix:
http://users.wowway.com/~zlinuxman/kernel/interlace.diff
I used kernel 2.6.38 as my code base.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe".
alternatives that I haven't thought of. What are your
thoughts?
P.S. For this initial post I have CC-ed debian-boot and debian-devel, as
there may be interested parties on that list that are not subscribed
to debian-kernel, but it is my intention that the discussion take place
on debian-ke
, but it's just one of a long
> list of tasks.
I didn't start this thread as criticism. As a matter of fact, I am
amazed at the prolific productivity of the kernel team. I don't know
how you find time to do all that you do. But I didn't want to wait
until the last minute to
On Wed, 20 Jul 2011 09:25:37 -0400 (EDT), Ben Hutchings wrote:
> On Wed, 2011-07-20 at 07:39 -0400 (EDT), Stephen Powell wrote:
>> On Wed, 20 Jul 2011 04:52:59 -0400 (EDT), Ben Hutchings wrote:
>>>
>>> Hook scripts will just perpetuate the use of the undocument
n,
I may stop recommending it.
Any further communication regarding this issue should be posted to debian-user,
since the kernel team does not support kernel-package.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
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/1733626537.566900.1330134799559.javamail.r...@md01.wow.synacor.com
-
tainting kernel
The kernel does boot; but the kernel gets tainted, which disables lock
debugging.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
On Mon, May 23, 2016, at 22:16, Ben Hutchings wrote:
> On Mon, 2016-05-23 at 21:06 -0400, Stephen Powell wrote:
>>
>> The following message is received at boot time when booting the stock Debian
>> kernel
>> version 4.5.3-2 on the s390x architecture:
>>
>&g
, I don't. dpt_i2o is working just fine for me.
All's well that ends well!
Regards,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
other error checking corner cases.
Respectfully submitted,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--- a/functions 2016-01-21 18:33:59.0 -0500
+++ b/functions 2016-03-24 08:09:11.0 -0400
@@ -128,14 +128,28 @@
# lilo compatibility
parse
;
> Ben.
>
Interesting. I wasn't aware of that. Thank you for calling my attention
to it. Under the circumstances, wishlist is fine.
Regards,
--
.''`. Stephen Powell
: :' :
`. `'`
`-
Hello Debian kernel team.
I am an IBM mainframe systems programmer. I support
and maintain the z/VM operating system at my
installation which provides the virtualization that
allows multiple virtual Linux servers to share the
same LPAR (mainframe partition). I would like to make
an appeal for th
> It is enabled in the current Debian kernel images
for
> 2.6.24 and above.
> However it is not enabled in the Etch 2.6.18. 2.6.24
> is currently in
> proposed-updates and will reach stable in the next
> days (hopefully).
Thanks!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
Package: linux-image-2.6.26-2-s390
Version: 2.6.26-15
Severity: critical
This particular Linux kernel image will not boot on a virtual machine in ESA
mode under z/VM. I have not tried other platforms (LPAR, for example).
Here is the boot log:
--
Booting default (debian)...
[0.
> Can you boot the old kernel and unpack the initramfs to see if the
> needed modules got added? See the DEBUG section of initramfs-tools(8)
> for a command to do the unpacking.
As you know, the initial RAM file system is not included with the kernel
image package but is built dynamically during k
I just tried re-building the initial RAM file system for the 2.6.26-1-s390
kernel image, rerunning zipl, and rebooting.
It came up fine. It does not appear to be a problem with the build process for
the initial RAM file system.
If it is, it is a build problem which is specific to the new kernel
By the way, I have another server that runs the 64-bit version of the kernel
image (linux-image-2.6.26-2-s390x), and it works fine.
Either the bug affects only the 31-bit version of the kernel, or there is an
environmental difference of some kind.
I have found an environmental difference between the two servers, one of which
runs linux-image-2.6.26-2-s390x (and will boot)
and the other of which runs linux-image-2.6.26-2-s390 (and will not boot). The
s390x server has only one virtual CPU.
The s390 server has two virtual CPUs. I changed th
Correction. The s390 server did not have two virtual CPUs. It had a *LIMIT*
of two virtual CPUs. In other words, its CP directory entry contained
MACH XA 2
This statement creates only one virtual CPU, but allows a second one to be
defined, if desired, by means of the
CP DEFINE CPU
command.
> Could http://bugs.debian.org/511334 be related to your problem? There's a
> link to patch in one of the last messages.
> See especially messages #57 and #65.
It's possible that they may be related. The difference, though, is that the user
in problem number 511334 was running in a virtual machi
Actually, I decided to go ahead and do the plan I had outlined, just for grins,
while I was waiting on an answer.
If it didn't work, and Frans said "yes, do that", I could then say it didn't
work right away and save time.
But it did work!
Here is what I did, as close as I can remember it. I was
Package: linux-image-2.6.26-2-686
Version: 2.6.26-15
Severity: normal
I have two laptops. One is an IBM ThinkPad 390E running Debian Etch
(kernel linux-image-2.6.18-6-686). The other is an IBM ThinkPad 600
running Debian Lenny (kernel linux-image-2.6.26-2-686).
I have a 16-bit PC Card 10/100 Eth
If you need more information on my system and how it is set up, please
see http://www.wowway.com/~zlinuxman/tp600.htm.
I tried installing linux-image-2.6.29-bpo.2-686 from lenny-backports to
see if the latest linux kernel would fix the problem, but it does not.
The symptom is the same. The card is recognized and configured,
but I/O does not work. Therefore, DHCP configuration fails.
Here is the output of "lspcmci
The latest kernel update, revision 2.6.26-15lenny2, still does not
contain the fix for this problem.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
In the process of collecting additional supporting data, I have
stumbled upon the problem. As mentioned
earlier, there are two laptops involved here. One runs
Etch (kernel 2.6.18) and the other runs Lenny (kernel 2.6.26).
The Compaq Netelligent 10/100 PC Card adapter works in the Etch
machine an
> Yes, 15lenny2 was a security update. This fix is queued for 2.6.26-16
> which should be included in Debian 5.0.2.
Well, I guess that makes sense; since the kernel that is packaged with
the Debian installer needs to be replaced too. Even s390x kernels,
which are not affected by this bug, are in
I had a similar problem installing Lenny on an IBM ThinkPad 600 Model 2645-51U,
which also has a built-in Crystal Semiconductor CS4237B sound chip. You
might want to check out my web site, http://www.wowway.com/~zlinuxman/tp600.htm,
to see how I handled the problem. One thing in particular that I
Dear Mr. Hansen,
I am not a member of the Debian Kernel Team, or any other team for that matter.
I am just an ordinary end user. But I noticed the message
Clocksource tsc unstable (delta = -244351700 ns)
in the kernel log file and wondered if that might be part of your problem.
You yourself hav
> perhaps this means the severity should be lowered
I can't speak to that. I'm not a member of the Debian kernel team. I'm just
an ordinary
end user who happened to notice a reference to the same kind of sound chip that
I have
and thought I might be able to help.
The problem, as I see it, is
When I closed this bug report, it appeared that my Compaq Netelligent
10/100 PC Card Ethernet adapter WOULD work with Ethernet cables which
have no soft plastic boot protecting the hard plastic hook, but WOULD
NOT work with cables which have boots. Subsequent testing, however,
has disproved this.
Package: linux-image-2.6.26-2-s390x
Version: 2.6.26-19
X-Debbugs-CC: debian-s...@lists.debian.org
This bug report applies to the s390 and s390x Linux kernel architectures only.
I am reasonably certain that this is not a Debian-specific bug but
applies to all distributions. Nevertheless, since I a
I have come up with a patch that seems to solve my problem.
The mdsk_init_io internal subroutine of drivers/s390/block/dasd_diag.c
currently looks like this:
--
/* Initialize block I/O to DIAG device using the specified blocksize and
* block offset. On success, return zero and set end_
>
> However ...
>
> This fix also creates (or more likely exposes) another problem. When this fix
> is on, devices which are manually taken offline immediately come online again!
> I had this problem once before in an earlier kernel, but the problem
> eventually
> went away with maintenance.
>
Maybe I'm re-inventing the wheel here, but I have recently collected and
organized
my notes on custom kernel building in Debian and have put them on the web at the
following URL: http://www.wowway.com/~zlinuxman/Kernel.htm
Maybe it will be useful to somebody. If there is anything incorrect on th
On Mon, Nov 16 2009, Manoj Srivastava wrote:
> I like that, and would like to be able to incorporate this HOWTO
> in the kernel-package package. What license are you distributing the
> document under? If it is a free license, I would like it to be in the
> kernel-package docs for Squeeze.
I'm
> first of all you shall build your linux-2.6 in ~/src/
> no compellent reason to do it in /usr/src
> second you shall use make deb-pkg no need to use kernel-package
> on a recent linux-2.6 tarball (>= 2.6.31). it will just produce
> the linux-image.
Thank you for your feedback. In response to
> here the pointer to the historic mail from linus, quite dated already
> http://lkml.indiana.edu/hypermail/linux/kernel/0007.3/0587.html
Thanks. I have read the e-mail. I am not a C programmer, despite managing
to hack out a kernel patch for dasd_diag.c. But I do know other programming
langu
> I would like to suggest addressing the building of out-of-tree modules
> as well. This is kind of a moving target, as Debian does not currently
> offer a way to build deb packages from out-of-tree modules which have
> been (prematurely, IMO) converted to DKMS.
I'm afraid that's beyond my area o
>>
>> I'm afraid that's beyond my area of recent experience. The last time I built
>> an out-of-tree module was back in the days when the ALSA drivers were
>> not part of the kernel source tree, and I was using Woody, I think,
>> with a 2.4 kernel. But make-pkpg could do that back then, and I wou
An official fix has now been published for this problem by upstream
development for kernel 2.6.33. See
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=22825ab7693fd29769518a0d25ba43c01a50092a
Please consider backporting it to 2.6.32 so that when Squeeze freezes, t
Hello upstream kernel team!
A fix was recently published for drivers/s390/block/dasd_diag.c to fix a problem
with an inability to get read-only minidisks online to Linux via the dasd_diag
driver. This fix was published for kernel release 2.6.33. (See
http://git.kernel.org/?p=linux/kernel/git/tor
On 2010-01-04 at 14:52:19 -0800, Greg KH wrote:
> On Mon, Dec 21, 2009 at 10:26:38AM -0500, Stephen Powell wrote:
> > Hello upstream kernel team!
> >
> > A fix was recently published for drivers/s390/block/dasd_diag.c to fix a
> > problem
> > with an inability
o from the Debian installer menu
that's their call, as far as I am concerned. I just don't want to see
lilo removed from the distribution.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.deb
kernel maintainer scripts to invoke the bootloader. See also, for example,
linux-image-2.6.26-2-s390.postinst, where zipl is assigned as the bootloader
on line 38. This really is an "open and shut case", if only I can the kernel
people to actually look at it! Please l
On Tue, 08 Jun 2010 07:39:58 -0400 (EDT), Vincent Danjean wrote:
> On 07/06/2010 17:37, Stephen Powell wrote:
>> But for a kernel install or reconfigure, it is the responsibility of the
>> kernel maintainer scripts to invoke the bootloader. See also, for example,
>> linu
On Tue, 15 Jun 2010 23:25:45 -0400 (EDT), Ben Hutchings wrote:
> On Tue, 2010-06-08 at 09:43 -0400, Stephen Powell wrote:
>>
>>do_bootloader = yes
>>
>> in /etc/kernel-img.conf means "run the historic boot loader for this
>> platform".
>> Fo
On Thu, 17 Jun 2010 18:11:04 -0400 (EDT), Ben Hutchings wrote:
> On Thu, Jun 17, 2010 at 12:33:58PM -0400, Stephen Powell wrote:
>> [...]
>> I can maybe accept your proposal for Squeeze. But for Lenny, I believe
>> that the maintainer scripts should be changed back they
1 - 100 of 146 matches
Mail list logo