On Mon, 26 Jun 2017, Thorsten Glaser wrote:
> >> I think you ran into this issue:
> >>
> >> > https://patchwork.kernel.org/patch/8098441/
>
> I use NatFeat disc only, though, not the ncr controller.
There is no working ncr controller provided by aranym, just a stub for
one, sufficient to fool c
Finn Thain dixit:
>On Mon, 26 Jun 2017, John Paul Adrian Glaubitz wrote:
>> Which can be worked-around by adding
>> "initcall_blacklist=atari_scsi_driver_init" to the kernel command line.
>> The buildd "mama" is running 4.11 with that work around.
Looks like it:
Linux ara5.mirbsd.org 4.9.0-3-m68k
On Mon, 26 Jun 2017, John Paul Adrian Glaubitz wrote:
> On 06/26/2017 12:29 AM, Thorsten Glaser wrote:
> > I cannot boot Linux 4.9, but 4.1 still works. (I think 4.3 also
> > failed, but I had autoremoved that already.)
>
> I think you ran into this issue:
>
> > https://patchwork.kernel.org/pat
On 06/26/2017 12:29 AM, Thorsten Glaser wrote:
> I cannot boot Linux 4.9, but 4.1 still works. (I think 4.3 also failed,
> but I had autoremoved that already.)
I think you ran into this issue:
> https://patchwork.kernel.org/patch/8098441/
Which can be worked-around by adding
"initcall_blacklist
Package: src:linux
Version: 4.9.30-2
Severity: important
I cannot boot Linux 4.9, but 4.1 still works. (I think 4.3 also failed,
but I had autoremoved that already.)
ARAnyM console log for failed build:
-cutting here may damage your screen surface-
ARAnyM 1.0.2
Using config file: 'buildd
5 matches
Mail list logo
