On Wed, Dec 11, 2019 at 03:18:06PM +0100, Karoly Balogh (Charlie/SGR) wrote:
> Hi,
>
> On Wed, 11 Dec 2019, Geert Uytterhoeven wrote:
>
> > > (BTW, if any kernel developer wants to take a look, I can make the A1200
> > > or the A4000 remotely accessible, via a Raspberry Pi. Serial console, and
>
Hi,
On Wed, 11 Dec 2019, Geert Uytterhoeven wrote:
> > (BTW, if any kernel developer wants to take a look, I can make the A1200
> > or the A4000 remotely accessible, via a Raspberry Pi. Serial console, and
> > hardware-reset for the Amiga via RPi GPIO. On boot it would just fetch a
> > new
Hi Charlie,
On Wed, Dec 11, 2019 at 2:36 PM Karoly Balogh (Charlie/SGR)
wrote:
> (BTW, if any kernel developer wants to take a look, I can make the A1200
> or the A4000 remotely accessible, via a Raspberry Pi. Serial console, and
> hardware-reset for the Amiga via RPi GPIO. On boot it would just
Hi,
On Tue, 10 Dec 2019, John Paul Adrian Glaubitz wrote:
> > (Ps: are these tests/sharing this kind of info is useful? I stop spamming
> > if no one is really interested.)
>
> Absolutely. Please keep reporting such issues as you see them.
OK, so just a quick update, the effort to get a
CC linux-ide, as people there may be more familiar with the quirks and
caveats of SD2IDE adapters
On Tue, Dec 10, 2019 at 3:56 PM Karoly Balogh (Charlie/SGR)
wrote:
> On Mon, 9 Dec 2019, Karoly Balogh (Charlie/SGR) wrote:
> > > It would be interesting to know if other people with A1200s have
> >
Hi!
On 12/10/19 3:56 PM, Karoly Balogh (Charlie/SGR) wrote:
> If I try to boot the kernel from an actual 2,5" HDD (Samsung 40GB,
> relatively recent), none of the enumeration problems seem to be happening,
> and both the IDE driver and the PATA driver shows the partitions on the
> HDD properly,
Hi,
On Mon, 9 Dec 2019, Karoly Balogh (Charlie/SGR) wrote:
> > It would be interesting to know if other people with A1200s have
> > issues with IDE or not
>
> Sorry for bumping this thread after a few months, I just wanted to
> report that I recently built a mainline 4.19.87 kernel with GCC
Hi,
On Tue, 25 Jun 2019, Geert Uytterhoeven wrote:
> While I first thought this was an IDE drive issue (we had issues with
> some WDC models a long time ago, which didn't show up on PC, as PCs
> don't use shared interrupts), this looks like an issue with the A1200
> GAYLE-specific interrupt
Hi Szymon,
On Mon, Jun 24, 2019 at 7:06 PM Szymon Bieganski wrote:
> On 6/24/19 4:27 AM, Michael Schmitz wrote:
> > The screenshot you sent by separate mail does show _IDE_IRQ high
> > (inactive)? Suggests it's not the hda drive flooding the system with
> > interrupts (which we pretty much knew
Hi Michael,
On Mon, Jun 24, 2019 at 4:28 AM Michael Schmitz wrote:
> On 23/06/19 10:26 PM, Szymon Bieganski wrote:
> > On 6/21/19 10:49 PM, Michael Schmitz wrote:
> >> Looks to me as though the master drive present causes a probe for a
> >> slave drive to abort. That could have ramifications for
Hi Szymon,
On 23/06/19 10:26 PM, Szymon Bieganski wrote:
Michael,
On 6/21/19 10:49 PM, Michael Schmitz wrote:
Looks like the probe for hdb does not time out (that would have taken
either of the 'return 1' paths). So it's either return code 0 or 2. 0
would have called do_identify() which we
Michael,
On 6/21/19 10:49 PM, Michael Schmitz wrote:
> Looks like the probe for hdb does not time out (that would have taken
> either of the 'return 1' paths). So it's either return code 0 or 2. 0
> would have called do_identify() which we should have seen, or 2 (drive
> aborted probe).
>
See
Szymon,
Am 22.06.2019 um 04:37 schrieb Szymon Bieganski:
On 6/19/19 1:42 AM, Michael Schmitz wrote:
Does the heartbeat LED keep flashing past this point? I wonder whether
there's an interrupt still pending on the IDE interface that wasn't
cleared when the probe for hdb timed out.
Keeps
Hi Geert,
On 6/19/19 9:25 AM, Geert Uytterhoeven wrote:
> Does it make a difference if you remove the PCMCIA Ethernet card?
> PCMCIA and IDE share interrupts through Gayle.
>
Not at all. Kernel stall the same way with or without pcmcia card. LED
keeps blinking the same, but slightly faster rate.
Hi Szymon,
On Tue, Jun 18, 2019 at 9:50 PM Szymon Bieganski wrote:
> On 6/18/19 8:56 AM, Geert Uytterhoeven wrote:
> > Can you sprinkle some debug prints
> > printk("%s:%u\n", __func__, __LINE__);
> >
> > in ide_probe_port() and probe_for_drive() (drivers/ide/ide-probe.c) and
> > retry?
>
Hi Michael,
On Wed, Jun 19, 2019 at 2:09 AM Michael Schmitz wrote:
> On 18/06/19 6:56 PM, Geert Uytterhoeven wrote:
> > On Mon, Jun 17, 2019 at 11:22 PM Michael Schmitz
> > wrote:
> >> On 15/06/19 11:15 AM, Finn Thain wrote:
> >>> On Wed, 12 Jun 2019, Szymon Bieganski wrote:
> Here is the
Hi Geert,
On 18/06/19 6:56 PM, Geert Uytterhoeven wrote:
Hi Michael,
On Mon, Jun 17, 2019 at 11:22 PM Michael Schmitz wrote:
On 15/06/19 11:15 AM, Finn Thain wrote:
On Wed, 12 Jun 2019, Szymon Bieganski wrote:
Here is the end of dmesg (full log in attachment) when kernel stalls,
just as
Szymon,
On 19/06/19 7:50 AM, Szymon Bieganski wrote:
Hello Geert,
On 6/18/19 8:56 AM, Geert Uytterhoeven wrote:
Can you sprinkle some debug prints
printk("%s:%u\n", __func__, __LINE__);
in ide_probe_port() and probe_for_drive() (drivers/ide/ide-probe.c) and retry?
I've recompiled with
Hi Geert,
On 18/06/19 6:56 PM, Geert Uytterhoeven wrote:
Not sure whether the 'probing with STATUS instead of ALTSTATUS' message
is normal for the A1200. Geert might remember that sort of detail.
That comes from drivers/ide/ide-probe.c:ide_dev_read_id().
Looking at the code, it may be caused
Hi Finn,
On 18/06/19 11:51 AM, Finn Thain wrote:
On Tue, 18 Jun 2019, Michael Schmitz wrote:
On 15/06/19 11:15 AM, Finn Thain wrote:
On Wed, 12 Jun 2019, Szymon Bieganski wrote:
Here is the end of dmesg (full log in attachment) when kernel stalls,
just as before:
Hello Geert,
On 6/18/19 8:56 AM, Geert Uytterhoeven wrote:
> Can you sprinkle some debug prints
> printk("%s:%u\n", __func__, __LINE__);
>
> in ide_probe_port() and probe_for_drive() (drivers/ide/ide-probe.c) and retry?
>
I've recompiled with addition of these extra lines, and found out that
Hi Michael,
On Mon, Jun 17, 2019 at 11:22 PM Michael Schmitz wrote:
> On 15/06/19 11:15 AM, Finn Thain wrote:
> > On Wed, 12 Jun 2019, Szymon Bieganski wrote:
> >> Here is the end of dmesg (full log in attachment) when kernel stalls,
> >> just as before:
> >>
> >>
> >>
>
On Tue, 18 Jun 2019, Michael Schmitz wrote:
> On 15/06/19 11:15 AM, Finn Thain wrote:
> > On Wed, 12 Jun 2019, Szymon Bieganski wrote:
> >
> > > Here is the end of dmesg (full log in attachment) when kernel stalls,
> > > just as before:
> > >
> > >
> > >
> > > [
Hi Szymon,
On 15/06/19 11:15 AM, Finn Thain wrote:
On Wed, 12 Jun 2019, Szymon Bieganski wrote:
Here is the end of dmesg (full log in attachment) when kernel stalls,
just as before:
[ 122.43] This architecture does not have kernel memory protection.
[
On Wed, 12 Jun 2019, Szymon Bieganski wrote:
>
> Here is the end of dmesg (full log in attachment) when kernel stalls,
> just as before:
>
>
>
> [ 122.43] This architecture does not have kernel memory protection.
> [ 122.44] Run /init as init process
> [
Hi Michael,
I did try to boot with "initcall_debug ignore_loglevel", as you suggested:
[ 0.00] Kernel command line: loglevel=7 initcall_debug
init=/bin/bash root=/dev/ram console=tty0 console=ttyS0,9600n8
video=amifb:pal-lace modprobe.blacklist=amiflop debug
Hi, again,
On 6/7/19 1:27 AM, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 6/6/19 11:22 PM, Szymon Bieganski wrote:
>> stock 1D4 Amiga 1200 with Apollo 040 CPU card, recent Elbox FastATA IDE
>> controller with 40G IDE HDD and PCMCIA network card. All components
>> causes no problems with other
Hi Geert!
On 6/7/19 9:00 AM, Geert Uytterhoeven wrote:
>> openSUSE sets it though:
>>
>> glaubitz@suse-laptop:~> grep CONFIG_UEVENT_HELPER /boot/config-$(uname -r)
>> CONFIG_UEVENT_HELPER=y
>> CONFIG_UEVENT_HELPER_PATH=""
>> glaubitz@suse-laptop:~>
>>
>> Should it be set?
>
> No, please don't
Hi Adrian,
On Fri, Jun 7, 2019 at 8:54 AM John Paul Adrian Glaubitz
wrote:
> On 6/7/19 8:35 AM, Geert Uytterhoeven wrote:
> > BTW, do these kernels have CONFIG_UEVENT_HELPER and/or
> > CONFIG_UEVENT_HELPER_PATH set?
>
> No, we haven't:
>
> root@pacman:~# grep CONFIG_UEVENT_HELPER
Hi!
On 6/6/19 11:22 PM, Szymon Bieganski wrote:
> Unfortunately I am facing strange problem that might be related to some
> specific hardware configuration, and therefore would like to consult
> with the experienced users if my problems might be caused by either
> software or hardware. Relevant
Hello!
First of all thank you all for your efforts to revive the Debian ports
for m68k. I myself as a Debian fan, would love to make use of my
retro-rig with my favorite linux distro beside AmigaOS and NetBSD.
Unfortunately I am facing strange problem that might be related to some
specific
31 matches
Mail list logo
