I did finally get the 4.17.11 kernel to compile so that my large drives
are visible now, but I had to use a 'shotgun' approach in including as
many SCSI/SATA/etc variables as possible.
I do intend on comparing the non-functioning config for 4.17.11 against
both the functioning config, as well
On Wed 01 Aug 2018 at 23:37:33 (-0600), Taren wrote:
> I'm running Stretch, with kernel 4.9.0.7, and am trying to compile a
> new kernel (preferably 4.17.11) into which I can boot.
> The kernel builds successfully, but whenever I try booting into the
> new kernel, I end up in emergency mode, with t
Correction:
The kernel version I'm using (which sees my 2.7T drives) is 4.9.0-7-amd,
not 4.9.0.7.
I can provide the .config file for 4.17.11, if needed.
On 08/01/2018 11:37 PM, Taren wrote:
I'm running Stretch, with kernel 4.9.0.7, and am trying to compile a
new kernel (preferably 4.17.11)
Hi,
>>"Johann" == Johann Spies <[EMAIL PROTECTED]> writes:
Johann> I am trying to compile a kernel with
Johann> make-kpkg --revision=custom.1.0 kernel_image
Johann> dpkg-deb - error: (upstream) version (`scsi') doesn't contain any
digits
Johann> dpkg-deb: 1 errors in control file
[EMAIL PROTECTED] wrote:
>
> > After intalling, the system is OK (I think).
> >
> > Today I recompile the kernel 2.0.29 and here is when problems arose:
> >
> > When I boot whith new kernel, I see that during booting procces the
> > kernel try setup my NE2000 network card TWO TIMES: the frist one
Hi,
Are there any stamp-* files in the top level directory? Please
try
# make-kpkg clean
# make-kpkg -r custom.A kernel_image
and see if that works. If not, please capture the output
(using script maybe) and also the listing produced by ls -als and
please file a bug report
In message <[EMAIL PROTECTED]> you wrote:
>--Multipart_Sat_Mar__8_19:17:27_1997-1
>Content-Type: text/plain; charset=US-ASCII
>
>> "Elie" == Elie Rosenblum <[EMAIL PROTECTED]> writes:
>
...
>>>
>>> Well, I know of this fatal sig 11 thing, but, $%!"#$"#$%"%", it
>>> worked before on
> "Elie" == Elie Rosenblum <[EMAIL PROTECTED]> writes:
Elie> On Sun, 9 Mar 1997, Alexander Koch wrote:
>> I tried to compile a new kernel on my own (just the old way)
>> and I am afraid i messed some things up...
>>
>> What does have to be a module? Even the SCSI controlle
On Sun, 9 Mar 1997, Alexander Koch wrote:
> I tried to compile a new kernel on my own (just the old way) and I am afraid
> i messed some things up...
>
> What does have to be a module? Even the SCSI controller? (I guess not)
>
> And, besides - after installing debian on my system I get segfaults
Hi,
Firstly: It was a problem with kernel sources not expecting
the suddenly POSIX compliant expr in shell utils, not with
make-kpkg. (/usr/doc/kernel-package.Problems.gz in newer
kernel-packages dissects this in detail).
Secondly, sure, this is Unix. You can always do things
m
On Mon, 24 Feb 1997, Michael Banys wrote:
>
> Does anyone know how to fix this problem? It's completely baffling me...
>
I don't know of a way to make it perfect, but, the following is a
fix. in the drivers/sound directory, copy Config.std to Config.in and
then do make config or oldconfig (no
Hi,
This is a know bug with the *kernel sources* (not make-kpkg as
has been suggested). Actually, this problem is an artifact of expr
becomming suddenly POSIX compliant, much to the consternation of the
kernel configure scripts.
The fix is to apply the following patch to your
On Mon, 24 Feb 1997, Michael Banys wrote:
> So I go through make config and everything is just fine ... until it comes
> to the sound. When it reaches the soundblaster I/O, no matter what I type
> in, it reports: "Sorry, no help available for this option yet," and then
> just goes right back to t
> Well, I am trying to compile a custom kernel, which I've done
> numerous times on my old system, using make-kpkg. So I go through
> make config and everything is just fine ... until it comes to the
> sound. When it reaches the soundblaster I/O, no matter what I type
> in, it reports: "Sorry, no h
14 matches
Mail list logo
