Re: Installing with new Installer-Image
- To: Finn Thain <fthain@telegraphics.com.au>
- Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, Stefan Niestegge <beetle@abbuc.de>, Michael Schmitz <schmitzmic@gmail.com>, Debian m68k <debian-68k@lists.debian.org>
- Subject: Re: Installing with new Installer-Image
- From: Geert Uytterhoeven <geert@linux-m68k.org>
- Date: Fri, 6 Oct 2017 16:00:28 +0200
- Message-id: <[🔎] CAMuHMdX=waPGvwUNL9qKB3hdbvkZf8umFrjPGKo03nC-autv2A@mail.gmail.com>
- In-reply-to: <[🔎] alpine.LNX.2.00.1710070034320.3@nippy.intranet>
- References: <f9c4e93e-342d-9cd2-e7f3-92829c6f5810@abbuc.de> <CAMuHMdX2xj+tDuCmu-FRAdQR6PUbuak9L-dkbhvJvDaRJRc5wg@mail.gmail.com> <ee989a28-910c-a282-a5a5-2a961b988738@abbuc.de> <CAMuHMdVZXBcFw1qiOA9BxzUFptbtrCaL9YAbpDohpe=F7U6Wjw@mail.gmail.com> <cc30e0c3-ee0e-7203-1925-3f6513a670f1@abbuc.de> <9f38b115-7049-90d5-6fc3-454c0853168e@physik.fu-berlin.de> <bb23d5ab-7ef3-5439-8f39-f63590c652dc@abbuc.de> <df39c716-ddd0-3437-b6c0-7f97b3a5fcd3@physik.fu-berlin.de> <50fdf12b-6dec-837a-23f4-7d65011d64b8@abbuc.de> <alpine.LNX.2.00.1709191336340.3@nippy.intranet> <f3787adb-9035-1883-0777-cdaf76766839@physik.fu-berlin.de> <alpine.LNX.2.00.1709201129150.3@nippy.intranet> <28a59acd-f4cf-6d7a-e70c-6d77b279e3d8@physik.fu-berlin.de> <CAMuHMdU8k=U+ZAZCcgL06uF5SY494V5HzZOb7GVe15p-J8wzng@mail.gmail.com> <alpine.LNX.2.00.1709211249370.3@nippy.intranet> <1af17ead-1f73-b6ac-a10e-21c67e50cc4a@physik.fu-berlin.de> <CAMuHMdVfNK5zGQx_pPXuZSs8D22DfCuoSJpjc56dtAQug_0fnw@mail.gmail.com> <[🔎] alpine.LNX.2.00.1710070034320.3@nippy.intranet>
On Fri, Oct 6, 2017 at 3:34 PM, Finn Thain <fthain@telegraphics.com.au> wrote:
> Sat, 7 Oct 2017 00:34:48 +1100 (AEDT)n Fri, 22 Sep 2017, Geert Uytterhoeven wrote:
>> > You don't need access to hardware. You can test the kernel just fine
>> > on Aranym. All you need is a simple root filesystem and an initrd
>> > which I can provide. In fact, you can just use the kernel and initrd
>> > from the debian-installer distribution:
>>
>> Correct.
>> And the Falcon IDE driver still works fine when not a module...
>>
>> >> https://people.debian.org/~glaubitz/debian-cd/debian-installer-images_20170828_m68k.tar.gz
>> >
>> > Use the common kernel and the initrd for the CD-ROM installation.
>> >
>
> There are some modules missing from the initrd. I copied all of the
> modules from the ISO to the initrd and now I can run 'depmod' and
> 'modprobe falconide' and all the device nodes get created automatically.
>
> The only problem is, when I access the CD-ROM (/dev/hdb) I get an oops.
> This happens with 'dd' and with 'mount'. No idea why. Maybe some problem
> with my aranym config (?)
> [ 508.810000] cdrom: Uniform CD-ROM driver Revision: 3.20
> [ 630.060000] Unable to handle kernel access at virtual address 416e6461
> [ 630.060000] Oops: 00000000
> [ 630.060000] Modules linked in: ide_cd_mod cdrom ide_gd_mod falconide ide_core evdev mac_hid atari_scsi
> [ 630.060000] PC: [<001693ba>] memset+0x2e/0x94
I guess that's the memset in ide_cdrom_prep_fs()?
> [ 630.060000] SR: 2704 SP: 1b93dc98 a2: 1b8ca000
> [ 630.060000] d0: 00000000 d1: 00000010 d2: 416e6461 d3: 00000008
> [ 630.060000] d4: 00000000 d5: 1b93c000 a0: 416e6461 a1: ffffffe0
> [ 630.060000] Process dd (pid: 2374, task=1b8ca000)
> [ 630.060000] Frame format=7 eff addr=416e6461 ssw=0425 faddr=416e6461
Looks like a complete bogus address. And it's "Anda" in ASCII.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Reply to: