Kernel Panic on new install

[mdavies5]

I installed 3.2 with Cinnamon to a USB stick, no problems. When trying to boot from USB I get a "Kernel Panic - Not Syncing" it then tries and fails again and hangs up. I tried booting into Plop but that just rebooted the machine.
I have a newish Toshiba Satellite pro with Intel graphics 1366 x 768, 12Gb RAm and 120Gb ssd drive.
I formatted a 4Gb USB stick with 1 partition ext4 and the installation finished ok.
My previous experience with Porteus has been on an old desktop, I have not previously used with the Toshiba.

I have read all the cheat codes and tried various option such as no auto, no cd nohd noswap delay=5. The same problem always appears. Any assistance would be appreciated.

[wread]

@mdavies5
Your 000-kernel.xzm and your /boot/syslinux/vmlinuz do not match...

[mdavies5]

Thanks for prompt reply. Both files were from the latest ISO and are dated 24/12/16 10:11;19.
Is there any solution?

[brokenman]

My money is on a hardware problem.

Please check the md5sum of the ISO you downloaded.
Next try a different USB stick.
Next post a screenshot of the more important messages (before/after) the kernel panic message.

Thanks.

[mdavies5]

Hi Brokenman,
MD5 sums match. Tried re-install on Kingston 4b and Toshiba 8Gb sticks. Toshiba would not boot. Kingston boots to menu then shows message. As screen was locked I had to shoot screen with external camera but I do not have access to upload files. Anyway the message was a bunch of hex numbers with some prefixes such as RIP, RSP, CR2. Finishing with "end trace d0bdc5b95217bcaa". After "Kernael Panic" it says "attempting to kill the task" then hangs up.
My Toshiba has UEFI facilties but BIOS is configured to boot without UEFI. Both USB stick shave been used to boot numerous distros, mainly Debian type or Suse.

[Bogomips]

As screen was locked I had to shoot screen with external camera but I do not have access to upload files.

http://forum.porteus.org/viewtopic.php? ... 2bd#p44482

[whitey]

Hi. Just wanted to mention that I've seen something like this too, unfortunately.
Tried to boot new Porteus v3.2.2 via CD on toshiba laptop (satellite c-70 series, i5, 8gb ram);
tried several iso/desktop images (xfce, mate, cinnamon), all 64-bit/x86_64 & passed MD5 checks,
but failed to boot laptop after displaying "kernel panic/unable to sync/attempt to kill process" pattern.
Hope this helps.

[whitey]

Hi, just adding a little more detail to my previous post re multiple-iso(-burned-to-CDs) boot failure on Toshiba laptop.
Laptop bios is set for non-uefi boot.

Porteus CDs (isos) reach initial boot splash screen, but then...
> automatic boot, if allowed, fails
> other quick-select boot options (Always Fresh, Copy To RAM, Text Mode), if attempted, also fail similarly

In each case wording of final message displayed at boot failure reads
" Kernel panic - not syncing: Attempted to kill the idle task! "

[Ed_P]

It's possible your pc is too fast. I believe there is a cheatcode that can be used to slow down the boot process. Unfortunately I don't remember what it is called. Maybe someone who knows what I am talking about can stop in and expand this thought a little further.

[Bogomips]

Can certainly slow it down into stages by, at the boot screen, hitting Tab and then appending debug to the boot options (default syslinux boot). Booting otherwise, append debug to kernel command line. As well as debug there is also delay=t secs. Adding delay=8 will pause boot for 8 secs giving time for slow devices to make themselves known.

[brokenman]

You may also want to try the noapic cheatcode.

[whitey]

Hi, thanks for replying, and thank you for the suggestions...

1) Tried appending debug to default boot string (and to quick-select Always Fresh boot string).
Result: no joy (boot failure displaying " Kernel panic - not syncing: Attempted to kill the idle task! ")

2) Tried appending delay=8 (and other delay values) to default boot string (and to quick-select Always Fresh boot string).
Result: no joy (boot failure displaying " Kernel panic - not syncing: Attempted to kill the idle task! ")
(also, interestingly, different inserted delay values appeared to cause no change in apparent time-to-boot-failure;
in other words, boot failure is happening quickly & appears to occur prior to execution of inserted boot delay)

3) Tried appending noapic to default boot string (and to quick-select Always Fresh boot string).
Result: no joy (boot failure displaying " Kernel panic - not syncing: Attempted to kill the idle task! ")

4) Then, for giggles, attempted to boot Porteus v3.2.2 x86_64 xfce iso via CD on _different but similar_
toshiba laptop (satellite c75, amd a4, 8gb). After rerunning "test suite" described above & in earlier post on
2nd device, able to report that 2nd toshiba laptop failed every attempted boot in exactly the same manner.
In all cases wording of final message displayed at boot failure reads
" Kernel panic - not syncing: Attempted to kill the idle task! "

5) Finally, no longer giggling & instead cursing out toshiba, I tried to boot Porteus v3.2.2 x86_64 xfce iso via CD
on older gateway laptop... AND SUCCESS! The gateway laptop booted Porteus! (not super-fast, but successfully)
(also, not that it matters, but had to use nomodeset boot parameter to solve initial black-screen on boot issue--
as has been required in the past with other linux distros I've booted on this gateway laptop).

So, I guess now I'm wondering... is there anyone out there in the community reading this who's been successful
booting a Porteus 3.2.2 iso/CD on a toshiba satellite (c-series, or any other series) laptop?

[Bogomips]

A bit more info: viewtopic.php?f=54&t=6559

[Blaze]

Try to disable ACPI option and enable Virtualization or Virtual option in BIOS of your laptop.

[whitey]

Hi blaze, thanks for replying.

Re virtualization:
virtualization already enabled ("VT-x only") on 1st toshiba laptop (intel/i5);
virtualization option not available on 2nd toshiba laptop (amd/a4).

Re acpi:
First tried to disable acpi by adding noacpi to boot parameters, but still got boot failure...
but then tried adding acpi=off to boot parameters, and this worked--bypassing boot failure and
allowing init script to run and porteus to boot--on both toshiba laptops!

Again, thank you.