search

sebanc / brunch

Boot ChromeOS on x86_64 PC - Supports Intel CPU/GPU from 8th gen or AMD Ryzen
GNU General Public License v3.0
3.7k stars 393 forks source link

Crosh shell not opening - illegal Instruction (core dumped) #1362

Open joeyoropesa-dev opened 2 years ago

joeyoropesa-dev commented 2 years ago

When I try to open Crosh shell with keyboard, crosh shell constantly close itself. After that when I try run crosh shell from terminal (Ctrl + Alt + F2) I get this error:

illegal instruction (core dumped)

I have latest Brunch and ChromeOS version so - is this bug by Brunch or by Chrome OS. And if this bug by Brunch framework, can this problem be solved. My Chrome OS image is rammus type. I don't have installed anything on my device (Android, Crostini - nothing)

/var/log/messages says: 2022-01-02T10:10:00.694175Z INFO kernel: [ 2515.077547] traps: crosh[9981] trap invalid opcode ip:59d35b93c4d9 sp:7ffeb42c8600 error:0 in crosh[59d35b844000+1e3000] 2022-01-02T10:10:01.196282Z WARNING crash_reporter[9984]: [user] Received crash notification for crosh[9981] sig 4, user 0 group 0 (handling) 2022-01-02T10:10:01.197404Z INFO crash_reporter[9984]: State of crashed process [9981]: S (sleeping) 2022-01-02T10:10:01.198684Z INFO crash_reporter[9984]: Accessing crash dir '/var/spool/crash' via symlinked handle '/proc/self/fd/11' 2022-01-02T10:10:01.219384Z WARNING crash_reporter[9984]: exec name 'crosh' not found in log file 2022-01-02T10:10:01.303526Z INFO crash_reporter[9984]: Stored minidump to /var/spool/crash/crosh.20220102.111001.28129.9981.dmp 2022-01-02T10:10:01.303882Z INFO crash_reporter[9984]: Finishing crash. Meta file: /proc/self/fd/11/crosh.20220102.111001.28129.9981.meta

tejasraman commented 2 years ago

Best I can think of is that Brunch is sending illegal(unsupported) instructions to your CPU. What exactly is your CPU model? Maybe try a different recovery image, "syndra" or "syndra" might work? - FYI I'm not sebanc, and it could be something else

tejasraman commented 2 years ago

I meant "syndra" or "caroline" - just to try :)

joeyoropesa-dev commented 2 years ago

Best I can think of is that Brunch is sending illegal(unsupported) instructions to your CPU. What exactly is your CPU model? Maybe try a different recovery image, "syndra" or "syndra" might work? - FYI I'm not sebanc, and it could be something else

Processor: Intel(R) Celeron(R) CPU B820 @ 1.70GHz

tejasraman commented 2 years ago

That's Sandy Bridge. There shouldn't be problems with Sandy Bridge, but a "fairly recent" Celeron is recommended. You could try "nami" recovery image, or use "caroline" (try caroline first). It may just be that the rammus image is using unsupported instruction sets. Try these two and get back to me if they don;'t work :) Here is the caroline image: https://cros.tech/device/caroline and the nami one: https://cros.tech/device/nami

joeyoropesa-dev commented 2 years ago

FYI, the Brunch page says that Baytrail or later is needed - you have the older "Sandy Bridge". You could try a different recovery ("nami" or "caroline") and if they work, you could try "samus" (if you're OK with a release of Chrome OS from June 2021) - that has a higher chance, but is now end of life.

Is "nami" image supported by Google and my CPU?

tejasraman commented 2 years ago

Yes, the “nami” image is supported until 2025 (rammus hits EOL in 2026 - a year after nami) but nami should have better support for your CPU. This is an honestly weird error, and usually, these weird errors on seemingly supported CPUs (this is the actual Sandy Bridge architecture) can be solved using a different recovery.

tejasraman commented 2 years ago

FYI, the Brunch page says that Baytrail or later is needed - you have the older "Sandy Bridge". You could try a different recovery ("nami" or "caroline") and if they don’t work, you could try "samus" (if you're OK with a release of Chrome OS from June 2021) - that has a higher chance, but is now end of life - sorry for the confusion with this comment

joeyoropesa-dev commented 2 years ago

Yes, the “nami” image is supported until 2025 (rammus hits EOL in 2026 - a year after nami) but nami should have better support for your CPU. This is an honestly weird error, and usually, these weird errors on seemingly supported CPUs (this is the actual Sandy Bridge architecture) can be solved using a different recovery.

On stable and beta version, crosh problem is resolved but in dev - the problem is the same. Maybe, if I change the kernel in the brunch settings for booting this image - i can use crosh on the dev version too.

tejasraman commented 2 years ago

Ohhhh… you are on ChromeOS Dev builds. You usually need brunch-unstable to use dev builds (it contains the latest Brunch code). Do you have the Brunch PWA installed on your Brunch laptop?

tejasraman commented 2 years ago

That’s how you change from brunch-stable to brunch-unstable(brunch dev releases)

joeyoropesa-dev commented 2 years ago

Ohhhh… you are on ChromeOS Dev builds. You usually need brunch-unstable to use dev builds (it contains the latest Brunch code). Do you have the Brunch PWA installed on your Brunch laptop?

I'm using Brunch Unstable (the latest version for Unstable builds)

Brunch PWA is installed

(Now on kernel 5.15 - dev channel and crosh works but when I choose to boot to the Brunch settings, my device is booting to the chrome os normally. When I choose to boot Chrome OS normally, doesn't boot at all - can't find chromeos.img - can't mount /dev/sda7: no such device)

tejasraman commented 2 years ago

Maybe a messed up grub config. Press E on the Brunch option and see what is going on. Tell me what shows up in the grub editor.

joeyoropesa-dev commented 2 years ago

Maybe a messed up grub config. Press E on the Brunch option and see what is going on. Tell me what shows up in the grub editor.

Fixed. When I changed brunch kernel from 5.15 to 5.10, it's working now normally

tejasraman commented 2 years ago

Great thanks!

ganeshambalakkara commented 2 years ago

I'm too having the same problem crosh closes as soon as i press Ctrl+Alt+T. After that when I try run crosh shell from terminal (Ctrl + Alt + F2) I get this error: illegal instruction (core dumped)

ganeshambalakkara commented 2 years ago

@admin-elvistrujanovic Can please help me how u solved this issue

tejasraman commented 2 years ago

Don't use kernel 5.15

ganeshambalakkara commented 2 years ago

I'm using kernel 5.4 only still

ganeshambalakkara commented 2 years ago

@admin-elvistrujanovic I'm using kernel 5.4 only still

tejasraman commented 2 years ago

What is your computer? On May 23, 2022, 1:03 PM -0600, ganeshambalakkara @.***>, wrote:

@admin-elvistrujanovic I'm using kernel 5.4 only still — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

ganeshambalakkara commented 2 years ago

@admin-elvistrujanovic Mine is hp elitebook 8460p 320GB hardisk 4gb DDR2 ram with integrated graphics intel i5

tejasraman commented 2 years ago

DDR2 on a laptop that was only compatible with DDR3?

This laptop should work with Rammus, and it seems that your hardware is similar to of @admin-elvistrujanovic. (You both have 2nd gen Intel CPUs wi5 HD3000 graphics)

FYI I am NOT @admin-elvistrujanovic.

What he did to fix it was using kernel 5.10 on his system, but I want more info. What is your brunch version, chrome OS version, and recovery image?

ganeshambalakkara commented 2 years ago

@tejasraman brunch version r100 chromeos 100 rammus ,ddr3 4gb ram

tejasraman commented 2 years ago

Warning: Don't update to r101 on your model Try kernel 5.10

ganeshambalakkara commented 2 years ago

@tejasraman would i be able to update to another version?

tejasraman commented 2 years ago

Not until @sebanc fixes the Mesa driver issue. Try kernel 5.10 in Brunch config, do not upgrade to r101

soupCodez commented 2 years ago

I have this same issue

tejasraman commented 2 years ago

Hello @soupCodez ! We need some more context to deal with this. Could you please tell me

(Ya, that was a bit generic, sorry - but I can't really do much until I know info)

tejasraman commented 2 years ago

@soupCodez are you still having this issue?

dhomas1 commented 2 years ago

Hello there!

I am still having this problem. I am on Brunch r103 with the image for Rammus on ChromeOS v103. My hardware is an HP Probook 67470b that uses a Core i5 3rd gen processor. I am using Kernel 5.10, but I had the same behaviour with kernel 5.4 and 5.15.

I have Brunch installed on my USB key using the instructions from Github (not any other video instructions). When I get to the part where I want to install it to the HDD, I cannot open crosh.

Troubleshooting steps I've tried:

Any help would be welcome. Thank you!

tejasraman commented 2 years ago

Hi @dhomas1 Seems you're very thorough in your troubleshooting (great job!) but there is something wrong (it seems).

0: (yes I added this later 😂😂😂) Are you using a ChromeOS USB key to install onto the HDD? This is a procedure I could never do without some error - mainly grub related but who knows? My recommendation is to make an Ubuntu USB and install it from the USB with sebanc's instructions.

  1. Are you using bios or EFI?
  2. Have you reinstalled CrOS even once?
  3. Android is unrelated - try Android init fix or enabling VT-D (virtualization) in BIOS setup

installing Chrome OS v104 with Brunch r103 (I didn't think this would work :) )

It works most of the time 😉

disabling nX in BIOS

NX is something most modern OSes need

dhomas1 commented 2 years ago

@tejasraman Thanks for the tips!

0: I've been using a ChromeOS USB key, using the instructions here: https://github.com/sebanc/brunch/blob/master/install-with-windows.md

I'll try using Ubuntu instead.

1: I've set up the image without the MBR patch. My Boot mode is set to "UEFI Hybrid (with CSM)", though I can set it up to "UEFI Native (without CSM)" to see if it helps.

2: I've installed and reinstalled CrOS multiple times, though I've only used the Rammus image (not sure which other image would be compatible with my hardware).

3: I've set up the Android init fix, but my apps all still seem to crash.

I said I'd disabled nX (No eXecute), but in reality it was "Data Execution Prevention" that I'd disabled. In any case, it didn't change the outcome.

I'll try the changes and report back. Thanks for the advice!

tejasraman commented 2 years ago

Use it without the BIOS patch for better boot times and less problems. The BIOS patch IMO is nothing but trouble. CSM is ok but don't use the patch.

You can use balenaEtcher to burn Ubuntu onto a USB.

You could try the nami image (1 year less of CrOS updates, but it is slightly older so... )

tejasraman commented 2 years ago

Hi @dhomas1 ! I can provide you with an (up to date) video tutorial if you want.

Tejas

tejasraman commented 2 years ago

@dhomas1 have you managed to get it working?

Not-Dhanraj commented 2 years ago

hey there @tejasraman . Can you suggest brunch type for Intel(R) Celeron(R) CPU B830 ? It would be amazing if you could also include a tutorial. Thanks.

tejasraman commented 2 years ago

@Not-Dhanraj The best image I can give you is Caroline.

I'll give you a tutorial but I need to know if you're using windows or Linux.

(Edit: read your GH page. Arch? Don't use the btw line on me 🤣)

Currently using fedora KDE but I have a partition with endeavorOS (Sway) and I can tell you what to do from there.

Tejas

tejasraman commented 2 years ago

If you see #1677 I'm not sure if your celeron will work however it might. If you could try Caroline + brunch 107-unstablehttps://github.com/sebanc/brunch-unstable/releases/tag/r107-unstable-20221029) that might work.

You can read the official docs. If you want singleboot I can help but dualboot is a mixed bag (especially when it comes to fedora)

Not-Dhanraj commented 2 years ago

I don't intend to use btw line anyways lamo😂 I use it cause it is pretty lightweight on my b830 laptop. Tried debian/fedora xfce as well but arch felt smooth so going with it. Haven't updated/turned it on from months now i need to chroot and update everything 😂

Not-Dhanraj commented 2 years ago

If you see #1677 I'm not sure if your celeron will work however it might. If you could try Caroline + brunch 107-unstablehttps://github.com/sebanc/brunch-unstable/releases/tag/r107-unstable-20221029) that might work.

You can read the official docs. If you want singleboot I can help but dualboot is a mixed bag (especially when it comes to fedora)

Yeah, i want singleboot. If it'll work i'll upgrade to a 150 gig ssd. Are you sure that unstable might not be unstable? 🤔 Can it work with stable?

tejasraman commented 2 years ago

I mean it will but unstable is never unstable. I wanted to replicate my Sandy bridge setup but stable should work.

Single boot :) I can help

(BTW I don't use Arch)

tejasraman commented 2 years ago

I'll give you a tutorial in any form you want.

Not-Dhanraj commented 2 years ago

I'll give you a tutorial in any form you want.

Video tutorial would be amazing 😅

tejasraman commented 2 years ago

Will do! Want me to do it on arch?

Not-Dhanraj commented 2 years ago

Will do! Want me to do it on arch?

Do it with whatever you have right now, or whatever you are comfortable with😁

tejasraman commented 2 years ago

I have an arch partition on my main PC. I'll film it today or tomorrow and send it in to you.

Not-Dhanraj commented 2 years ago

Thanks!

tejasraman commented 2 years ago

I'm still trying to make this into a video tutorial but here is a text tutorial:

PS the computer needs EFI support for this to work.

If you want to try the legacy bios patch download the "mbr_support.tar.gz" from the main brunch repo and extract it into the same folder as the other two right before the last step.

Not-Dhanraj commented 2 years ago

Don't worry abour legacy bios, the laptop in which i am trying to install chrome os supports EFI.

tejasraman commented 2 years ago

Great... The only Sandy bridge laptop I have is a MacBook with EFI so I never tested the patch.

Did the guide work for you?

Edit: The reason I mentioned it was that most Windows Sandy Bridge laptops had Windows 7 (no EFI).