On Tue, 14 Mar 2023 19:38:49 +1300
Michael Schmitz wrote:
> replacing 'm68k' by one of the officially supported architectures (I
> used 'amd64') will give a working URL. This does contain a workaround
> to shut up the new warning:
[...]
> I suspect there has never been any firmware distributed f
Just started getting this:
Reading package lists... Done
N: Repository 'Debian bookworm' changed its 'non-free component' value from
'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at:
https://www.debian.org/releases/bookworm/m68
Hi Michael,
> that's apparently been corrected in later versions. Commit
> ca831f29f8f25c97182e726429b38c0802200c8f (in from 5.17).
>
> I doubt this would lead to different code generated.
>
> Which was the first broken version you tried? That would narrow down
> the search range considerably..
FYI:
Just caught this trying a re-compile of kernel 5.15.2 from kernel org,
under debbootstrap/sbuild and qemu-system-m68k both produce this issue:
CC mm/process_vm_access.o
CC mm/page_alloc.o
mm/page_alloc.c: In function ‘mem_init_print_info’:
mm/page_alloc.c:8163:27: warning: com
Hi Adrian,
On Tue, 21 Feb 2023 15:50:52 +0100
John Paul Adrian Glaubitz wrote:
> Will try earlier kernels until I found the one where the breakage was
> introduced. Currently known latest kernel to work is 5.10.5.
From my testing last year trying to boot my Amiga 3000, the break
happens sometim
Hi Geert,
> While the non-working case in your next email has
> "ramdisk dest is 0x0f7f6794" and a matching
> "initrd: 0f7f6794 - 1000".
> /me confused even more...
Just did a fresh test with both, powered down between tests..
Kernel 5.15/intrid 5.15:
https://amiga.vk3heg.net/wp-content
Hi Geert,
On Fri, 9 Sep 2022 09:34:21 +0200
Geert Uytterhoeven wrote:
> I think we really need to see the output of "amiboot -d",
> for both the good and the bad cases.
https://amiga.vk3heg.net/wp-content/uploads/2022/09/PXL_20220910_004939673-scaled.jpg
Kernel/Intrd: 5.19
>>
Hi Geert.
> I think we really need to see the output of "amiboot -d",
> for both the good and the bad cases.
I had amiboot like so:
amiboot -d -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
root=/dev/sda2 fb=false
Didn't see anything different, in the output except for this at the
start o
Here's a test of kernel 5.16, intrid 5.16. It exited to busybox saying
it couldn’t find /dev/sda2 (root fs)
[0.00] Linux version 5.16.0-6-m68k (debian-ker...@lists.debian.org)
(gcc-11 (Debian 11.2.0-19) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1
Debian 5.16.1
Hi Finn,
On Fri, 9 Sep 2022 11:36:49 +1000 (AEST)
Finn Thain wrote:
> You mean, you tried kernel 5.15 with initrd 5.19? The question is,
> "did it oops?". Having seen the results below, I suspect that it
> didn't oops, despite the large initrd.
ohh.. here's a successful boot with vmlinux-5.15.0
Hi Guys.
As requested.
Finn I also tried kernel 5.19 with intrid 5.15..
Still only Kernel/Intrid 5.15-02 is the one that boots.
command line was always (With only kernel/intred changes):
amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
root=/dev/sda2 fb=false debug=mem
Kernel 5.1
Hi Finn,
On 2022-09-08 08:19, Finn Thain wrote:
Kernel command line: ignore_loglevel -r initrd.img-5.19.0-1-m68k
root=/dev/sda2 fb=false debug=mem BOOT_IMAGE=vmlinux-5.19.0-1-m68k
Hence Amiboot didn't provide the initrd...
Okay, so the first couple of logs Stephen sent used the correct c
Hi Geert,
amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
root=/dev/sda2 fb=false debug=mem
Are you sure that is what you really used?
Yes, that is what I've been using and works with 5.15
Screen shot of just before I started a new test. I boot the Amiga with
no startup-seque
Hi Finn,
On Wed, 7 Sep 2022 11:59:17 +1000 (AEST)
Finn Thain wrote:
> > Here are three debugs. mixing the kernel/intrid's...
>
> What happens if you boot the 5.19 kernel/initrd pair with
> "root=/dev/sda2" omitted from the kernel parameters?
>
> It looks like the oops from the 5.18 build
Hi Geert,
On Tue, 6 Sep 2022 09:40:27 +0200
Geert Uytterhoeven wrote:
> > 5.18.16-1 (2022-08-10) [0.00] printk: debug: ignoring
> > loglevel setting. [0.00] printk: console [debug0] enabled [
> >0.00] Amiga hardware found: [A3000] VIDEO BLITTER AMBER_FF
> > AUDIO FLOPPY A
Hello Ingo,
On Sun, 4 Sep 2022 10:55:40 +0200
Ingo Jürgensmann wrote:
> > 0x0a00-0x0fff] [0.00] Initmem setup
> > node 0 [mem 0x0a00-0x0fff] [0.00]
> > Unable to handle kernel access at virtual address (ptrval)
>
> So, here is the
Hi Finn,
> What happens if you boot the known-good initrd (v5.15) with the
> crashy vmlinux binary (v5.18)?
> The combination won't boot normally but should fail normally (wrong
> modules) and not fail with an oops.
It still crashes, but I can see the process.
Searching for SAVEKMSG magic...
On Sat, 3 Sep 2022 13:10:46 +0200
Ingo Jürgensmann wrote:
> > Amiga 3000
> > Warpengine 68040@40Mhz
> > 128Mb ram on warpengine
>
> Uhm? How do you get the Warpengine with 128MB into an A3000? Usually
> there is not enough space on the Warpengine for 4x 32 MB SIMMs - or
> did you use 2x 64MB one
Hi Adrian,
On Sat, 3 Sep 2022 09:25:13 +0200
John Paul Adrian Glaubitz wrote:
> Might be a wise idea to cross-post this to the Linux/m68k kernel
> mailing list.
Didn't know there was one.
> Also, kernel 5.19.6 is currently being built and should be available
> soonish.
I'll test that when i
Hi Guys,
I have "Debian GNU/Linux bookworm/sid" installed on both Qemu-user and
real hardware.
Amiga 3000
Warpengine 68040@40Mhz
128Mb ram on warpengine
8Mb Fast ram on MB
2Mb Chip ram
X-surf Network card (Original)
Kickstart 3.2
Qemu is working with no issues.
Real hardware issue:
Booting ker
On Mon, 21 Jan 2019 12:48:34 +0100
John Paul Adrian Glaubitz wrote:
> Hello!
>
> I have created updated installation images for Debian Ports,
> please find the updated images below and test them [1].
>
> Feedback welcome.
>
> Adrian
>
> > [1] https://cdimage.debian.org/cdimage/ports/2019-01-2
Update: I have been able to get past the partitioning issues.
I used the 3.1r8 cd to create my partitions & format.
Once I got to the partition error, I switched to the second console.
Mounted the partition on /target and once the menu came up for the
steps I moved onto the install option.
So
On Fri, 7 Sep 2018 11:15:22 +0200
John Paul Adrian Glaubitz wrote:
> On 09/07/2018 11:01 AM, Geert Uytterhoeven wrote:
> > The CV64 driver (and the CV64/3D and Retina/Z3 drivers) were removed
> > in commit e019630e78e3482c ("[PATCH] remove broken video drivers")
> > in v2.6.21.
>
> The plan is
Hello Geert,
On Fri, 7 Sep 2018 11:01:19 +0200
Geert Uytterhoeven wrote:
[...]
> > Cybervision64 with 4mb Ram.
> > Install issues:
>
> The CV64 driver (and the CV64/3D and Retina/Z3 drivers) were removed
> in commit e019630e78e3482c ("[PATCH] remove broken video drivers") in
> v2.6.21.
>
> On
Been on the list lurking for some time, and have made a few posts in the
past.
Read John Paul Adrian Glaubitz's post from 20th July, and downloaded
the iso he listed.
(https://cdimage.debian.org/cdimage/ports/10.0/m68k/iso-cd/)
My config:
Amiga 4000D, 2Mb chip, 4Mb Fast.
Warpengine 68040@40mhz w
On Sunday, May 01, 2011 10:33:34 pm Christian T. Steigies wrote:
> disk as well, especially as it does not seem to be needed. BTW does
> anybody have a spare A2k powersupply (with 220V please) or an idea how to
> modify a "modern" powersupply to replace the one in an A2k? I once read
> some inst
Hi Guys,
would this beast work with Debian M68K?
http://amigakit.leamancomputing.com/catalog/product_info.php?products_id=958
ZorRAM is a new SDRAM Fast Memory expansion for Amiga!
Expand your Amiga 3000, 3000T, 4000 or 4000T with this 128MB or 256MB SDRAM
memory expansion.
Board plugs in
27 matches
Mail list logo
