[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Begin: Mounting root file system ... /init: line 221: arithmetic syntax error



On 9/5/25 13:11, John Paul Adrian Glaubitz wrote:
Hi Dennis,

On Sep 5, 2025, at 6:40 PM, Dennis Clarke <dclarke@blastwave.org> wrote:


Well, this is interesting :


[   23.462584] This architecture does not have kernel memory protection.
[   23.636642] Run /init as init process
Loading, please wait...
/scripts/init-top/udev: line 14: can't create /sys/kernel/uevent_helper: Permission denied
Begin: Loading essential drivers ... [   24.311877] SCSI subsystem initialized
[   24.842426] pata_ali 0000:00:0d.0: enabling device (0004 -> 0005)
[   25.012970] scsi host0: pata_ali
[   25.105325] scsi host1: pata_ali
[   25.193444] ata1: PATA max UDMA/66 cmd 0x1fe02010200 ctl 0x1fe02010218 bmdma 0x1fe02010220 irq 12 lpm-pol 0
[   25.321678] ata2: PATA max UDMA/66 cmd 0x1fe02010210 ctl 0x1fe02010208 bmdma 0x1fe02010228 irq 12 lpm-pol 0
[   25.759898] ata1.00: ATA-5: ST340016A, 3.10, max UDMA/100
[   25.830961] ata1.00: 78165360 sectors, multi 0: LBA
[   26.050457] scsi 0:0:0:0: Direct-Access     ATA      ST340016A 3.10 PQ: 0 ANSI: 5
[   26.935164] ata2.00: ATA-6: ST340014A, 8.01, max UDMA/100
[   27.006267] ata2.00: 78165360 sectors, multi 0: LBA48
[   27.607854] scsi 1:0:0:0: Direct-Access     ATA      ST340014A 8.01 PQ: 0 ANSI: 5
modprobe: module tulip.ko not found in modules.dep
modprobe: module auth_rpcgss.ko not found in modules.dep
modprobe: module dmfe.ko not found in modules.dep
modprobe: module flash.ko not found in modules.dep
modprobe: module lockd.ko not found in modules.dep
modprobe: module loop.ko not found in modules.dep
modprobe: module nfs.ko not found in modules.dep
modprobe: module nfs_acl.ko not found in modules.dep
modprobe: module nfsd.ko not found in modules.dep
[   29.496486] sd 0:0:0:0: [sda] 78165360 512-byte logical blocks: (40.0 GB/37.3 GiB)
[   29.597089] sd 1:0:0:0: [sdb] 78165360 512-byte logical blocks: (40.0 GB/37.3 GiB)
[   29.771089] sd 1:0:0:0: [sdb] Write Protect is off
[   29.834362] sd 0:0:0:0: [sda] Write Protect is off
[   29.897614] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   30.016830] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   30.136138] sd 1:0:0:0: [sdb] Preferred minimum I/O size 512 bytes
[   30.217751] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[   30.340686]  sda: sda1 sda2 sda3 sda4
[   30.391482] sd 0:0:0:0: [sda] Attached SCSI disk
[   33.940513]  sdb: sdb1 sdb2 sdb3 sdb4
[   33.991486] sd 1:0:0:0: [sdb] Attached SCSI disk
modprobe: module sg.ko not found in modules.dep
modprobe: module sunrpc.ko not found in modules.dep
modprobe: [   34.183107] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[   34.288481] CPU: 0 UID: 0 PID: 1 Comm: init Not tainted 6.12.3-sparc64-smp #1  Debian 6.12.3-1+sparc64
[   34.410847] Call Trace:
[   34.442944] [<0000000000ef8e70>] dump_stack+0x8/0x18
[   34.508199] [<0000000000eeb430>] panic+0xf4/0x398
[   34.570023] [<0000000000474574>] do_exit+0xab4/0xac0
[   34.635274] [<0000000000474744>] do_group_exit+0x24/0xa0
[   34.705101] [<00000000004747dc>] sys_exit_group+0x1c/0x40
[   34.776069] [<0000000000406214>] linux_sparc_syscall32+0x34/0x60
[   34.855064] Press Stop-A (L1-A) from sun keyboard or send break
[   34.855064] twice on console to return to the boot prom
[   35.001455] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 ]---
module usbcore.ko not found in modules.dep
modprobe: module platform:f0069d48 not found in modules.dep
modprobe: module platform:root not found in modules.dep
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... /init: line 221: arithmetic syntax error
~
Type  'go' to resume
ok power-off

lom>
LOM event: +0h32m20s host power off
lom>

I would suggest to create sparc64 sid chroot with the debootstrap command I suggested in my previous mails.

Just make sure to install qemu-user before running it with »--arch=sparc64« on your x86_64 machine.


I have no idea how to do these things. I am guessing the qemu-user stuff
 is for some cross compile procedure ?


Then tar that directory up, transfer it to the SPARC and unpack it into the root directory of the second hard drive

Then point the root partition in silo.conf to the newly generated sid sparc64 partition.

That sounds cool ... if I can get there.

--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken


Reply to: