#7940 closed bug (fixed)
Dell Inspiron M5030, install medium will not boot.
Reported by: | BURGINABC | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | - General | Version: | R1/alpha3 |
Keywords: | install boot | Cc: | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
Specs of computer: 64-bit AMD Athlon II dual-core processor. 4GB RAM, Ati Mobility radeon graphics card with 256 MB graphics memory.
It showed the splash screen, a few of the icons lit up, and then the disc stopped spinning, the loading process just stopped completely. It wasn't the disc's fault, the disc installed successfully to an old pentium 4 desktop soon afterward.
Attachments (2)
Change History (16)
comment:1 by , 13 years ago
comment:3 by , 13 years ago
Platform: | x86-64 → x86 |
---|
The "Platform" field is supposed to refer to the Haiku platform, not the target architecture. ATM that isn't all that interesting, but once the x86-64 port is working it will be.
At any rate, please attach the syslog, if possible.
comment:4 by , 13 years ago
syslog? I'm sorry, but I don't know what that is. Is that what bash gives you when you input the "dmesg" command? or is it something else?
As for which splashscreen icon it stopped on, I tried it again and it made it to the third icon.
comment:5 by , 13 years ago
There's some info in http://dev.haiku-os.org/wiki/ReportingBugs -- basically you access it from the bootloader or (easier) from another OS that can read BFS, and attach it to this ticket page.
comment:6 by , 13 years ago
I read the wiki article and...
If the syslog is supposed to be stored in the Be File System, than that means it doesn't exist. the install disc never came close to the part where you format a partition as BFS, as it never left the splash screen. The little partition I made in preparation for Haiku is still unformatted as yet, since my version of GParted doesn't seem to be able to create BFS.
Sorry...
comment:7 by , 13 years ago
Not necessarily: the boot loader keeps an in-memory syslog buffer up until it finds a disk to write it back to ; if you can soft reboot your machine (aka, some way that does not involve powering off) after it hangs, you can enter the boot loader again immediately after reboot by holding left shift immediately after the BIOS finishes and the CD boot starts. From there you can go to the debug options menu, where there will be an option to write that syslog to a FAT32 USB stick if you have one plugged in at time of boot.
comment:8 by , 13 years ago
sorry... but as far as I know, my only option when it hangs on the splashscreen is a hard shutdown. if it's possible to soft reboot from there on my machine, I don't know how...
sorry if my bug report is a dead end...
comment:9 by , 13 years ago
IMHO, the phenomenon is similar as the issue on AMD C1E with no ARAT platform. I suggest try the patch in #8111
comment:10 by , 13 years ago
The patch is applied in hrev44025. Please test with nightly that has this change.
comment:11 by , 11 years ago
With a recent nightly mine sometimes gets through all of the startup icons and then goes to a split black and white screen. One left have one color the right half another. If I press left space during boot and pick failsafe video mode it then only goes to the disks icon and then bails after a minute or two saying it couldn't find any boot partitions. Note that I have installed a 1TB hard drive on this laptop and the Haiku partitions are slated to be the 2nd 3rd and 4th partitons, with each of the 4 partitions being about 250GB in size. So all of the Haiku parttions start past the 200GB mark, if that matters.
by , 10 years ago
comment:13 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I think I got Haiku R1B1 to boot from and install from a DVD on my M5030. But I can't recheck it at this time since it died a few weeks ago. Let's close this for now as probably fixed.
comment:14 by , 5 years ago
Milestone: | R1 → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Note that when I tagged it as x86-64, I was referring to the processor, not the build of haiku. the build of haiku was 32 bit. however, x86-64 processors are supposed to be backwards compatible with 32-bit OS, so I wouldn't think that that would be the problem...