LinuxQuestions.org - AntiX kernel panic during installation init

- antiX / MX Linux (https://www.linuxquestions.org/questions/antix-mx-linux-127/)

- - AntiX kernel panic during installation init (https://www.linuxquestions.org/questions/antix-mx-linux-127/antix-kernel-panic-during-installation-init-4175710527/)

AntiX kernel panic during installation init

Selected boot failure screen text:

Code:

traps: init[1] trap invalid opcode ip:80a1d0e sp:bf80c700 error:0[5.522618] in busybox[8048000+83000]

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

CPU: 0 PID: 1 Comm: init Not tainted 4.9.0-279-antix.1-486-smp #1

Hardware name: MiTAC 5114VU/VP4-686A, BIOS 6.00 PG 09/03/2000

Some machine info booted to Knoppix CD:

Code:

# inxi -Cayz

CPU:

  Info: model: AMD-K6 3D bits: 32 type: UP arch: K6-2 family: 5 model-id: 8

    stepping: 0xC (12) microcode: N/A

  Topology: cpus: 1x cores: 1 smt: N/A cache: L1: 64 KiB L2: 512 KiB

    note: check

  Speed (MHz): 550 min/max: N/A base/boost: 550/733 volts: 3.3 V

    ext-clock: 100 MHz core: 1: 550 bogomips: 1100

# inxi -Iayz

Info:

  Processes: 70 Uptime: 33m wakeups: 0 Memory: 237.3 MiB

  used: 60.5 MiB (25.5%) Init: SysVinit v: 2.88 runlevel: 2 default: 5

  tool: service Compilers: gcc: 4.6.1 alt: 4.6 Packages: note: see --pkg

  apt: 1261 lib: 599 Shell: Bash v: 4.1.5 running-in: tty 3 inxi: 3.3.14

Onboard video sharing system RAM accounts for the <256M of RAM.

What I did was fully prep the disk with formatted partitions and Grub installed. My hope was to get installation started without burning anything, which I commonly do with other distros by loading the NET installation versions of kernel and initrd with Grub, and installation parameters splash=0 disable=lx vga=791 noresume. Grub loaded kernel and initrd easily enough, but 5.5 seconds later, the kernel panic resulted. A follow-up try with video=1440x900 instead of vga=791 produced a similar panic, and exit code=0x00000004, but in 80x25 mode, so all lines but one before "Call Trace" scrolled away.

Is this due to lack of needed configuration, an expected problem with a K6/2, or something else? None of my searches turned up installing AntiX without booting directly from installation media. USB boot is not possible. PC does have CD drive, so I could burn the NET .iso to CD, but would rather have Grub start the party. :)

Quote:

Originally Posted by mrmazda (Post 6344530)

Selected boot failure screen text:[code]traps: init[1] trap invalid opcode ip:80a1d0e sp:bf80c700 error:0[5.522618] in busybox[8048000+83000]

"Invalid opcode" means the executable (BusyBox in this case) contains an instruction your CPU doesn't understand.

32-bit Knoppix is supposedly compiled for a 486 target, so the K6-2 ought to work just fine. I suggest you run memtest86+ to rule out hardware issues.

The PC ran WinXP OK until its HD died. It's what I used to use to setup my Logitech Harmony remote. All the preparations I did running Knoppix 6.7.1 with 3.0.4 kernel. Memtest86 v4.20 I included in the initial Grub menu as the default. I ran it before booting the AntiX kernel, and multiple clean passes since. It's a creepy slow process, main memory at a breathtaking 181 MB/s, 0.72% the speed of my Kaby Lake's DDR4. :p

I ran Plop Boot manager to boot on usb 1.1 . It is like watching paint dry though. On boot up and running. On older gear.

For K6 or K7 cpu.

I'd maybe rethink things. Being a die hard antiX user . I posted this a while back
https://www.antixforum.com/forums/to...us-like-k-cpu/

Edit; I checksum my iso downloads to save me headaches later on.

It does sound like hardware fatigue.
Often occurs right when you start changing things.
If not, maybe this is a problem:

Quote:

Originally Posted by mrmazda (Post 6344530)

Onboard video sharing system RAM accounts for the <256M of RAM.

I tried burning the NET .iso to CDRW. It failed to boot. So I wasted a CD-R. Grub works, but kernel panic with exit code 0x00000004 came after 6.4s, with the details scrolled off top of screen in 800x600 mode. Retry in 1024x768 reproduced OP panic data.

Puppy I don't like, having used it more than I would have if something else was as easy to download and burn ready to run DFSee, which is the only partitioner I've used for partition management for more than two decades. It's what DFSee .isos are provided with.

I tried installing several old knoppix versions, 4.0.2, 5.0.1, 5.1.1, 6.0.1, 6.4.4, 6.7.1 & 7.2.1. All the older ones errored in one way or another running knoppix-installer or knx-hdinstall, while the newer ones don't have an installer I could identify.

Next I tried Debian. I had to go back to Wheezy/7 to find an installer kernel that didn't halt for lack of CMOV. Now that it's running it should be easier to setup testing of others on remaining partitions reserved for the purpose, possibly including a bug report it could be used to follow up on on the AntiX kernel panic.

Code:

# inxi -SIy

System:

  Host: m5114 Kernel: 3.2.0-4-486 arch: i586 bits: 32 Console: tty 3

    Distro: Debian GNU/Linux 7 (wheezy)

Info:

  Processes: 56 Uptime: 4h 22m Memory: 241 MiB used: 43.9 MiB (18.2%)

  Init: SysVinit runlevel: 3 Shell: Bash inxi: 3.3.14

The antiX kernel does not support your AMD-K6 CPU.

I have a K6-III somewhere I could install when I find it. Is it unsupported too?