Bug 21318
Summary: | Bootup halts on init | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <ws2> |
Component: | SysVinit | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Dale Lovelace <dale> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-11-28 06:38:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2000-11-25 01:18:40 UTC
What happens if you try 'init=/bin/ash.static'? it gets to: VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 64k freed # and then fails. The "#" sign is new. That's not failing - that's a shell prompt. :) Unless you're saying the machine is hung at this point? If it's not hung, what happens if you run: /bin/bash from that shell prompt? It says # /bin/bash Illegal instruction What kind of processor is in the iopener? What most likely happened is that when you installed the drive, the i686 glibc package got installed. This package contains instructions that won't run on less than a PPro. BTW, you can tell what architecture glibc you have by running: rpm -q --qf "%{ARCH}\n" glibc Well that makes sense because I'm pretty sure its a Rise mp6 200Mhz processor (i586). If that's it then what steps do I need to do? Just remove the i686 glibc rpm and install the i586 glibc rpm? i386 glibc RPM actually (there's only an i386 and i686; adding specific i586 optimizations doesn't actually help any), but yes, that's what you'll have to do. You'll also want to check to make sure you aren't running an i686 kernel (although that would be likely to die a lot earlier in the boot sequence...) |