Opened 18 years ago

Last modified 18 years ago

#238 closed bug

physical vmware haiku boot works - in native mode the bootloader cannot find a device — at Version 6

Reported by: backupwww@… Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc: diver
Blocked By: Blocking:
Platform: All

Description (last modified by axeld)

Motherboard:

CPU Type: Mobile Intel Pentium IIIE, 500 MHz (5 x 100) Motherboard Name: BM 26458PG Motherboard Chipset: Intel 82440BX/ZX System Memory: 256 MB (SDRAM) BIOS Type: IBM (11/30/99) Video Adapter: NeoMagic MagicGraph256ZX driver (4091 KB)

SAMSUNG MP0402H (40 GB, 5400 RPM, Ultra-ATA/100)

C: (FAT32) 9529 MB

then some logical devices in an extended partition haiku got

$ makebootable -full /haiku Using full mode bootsector /dev/disk/ide/ata/0/master/0/0_5 successfully made bootable. $

/haiku space is about 10000MB

/dev/disk/ide/ata/0/master/0/0_4 is used for beos and after /haiku at the moment there is unused space. Maybe a big bfs or fat32 partition will follow.

if i install a second beos or zeta on /haiku partition, they all will boot!

HAIKU boots too, but not natve. The only way is to use vmware which I configured using the whole physical hdd device. BeOS bootman starts and I can choose between win2k, beos and haiku. All will run. Choosing haiku I see the fastest BeOS in vmware. :)

In native mode, the HAIKU bootloader doesn't find an boot device. I can scan for a device but it doesn't help. The only way is to restart. Then the notebook boots again and I can do my choice in bootman again.

At the moment I could not find my 2.5 USB adapter to install HAIKU on a new whole hdd for testing. I will search it.

My HAIKU build was rev16537_raw.tar.bz2 (others before cause the same problem)

On my desktop pc I have a native running HAIKU

nick #haiku is b3w

Change History (6)

comment:1 by diver, 18 years ago

Summary: physical vmware haiku boot works - in native mode the bootloader cannot find a device physical vmware haiku boot works - in native mode the bootloader cannot find a device

comment:2 by diver, 18 years ago

Cc: diver added

comment:3 by diver, 18 years ago

Does it still happens?

comment:4 by backupwww@…, 18 years ago

yes it does!

i hope i get back my hdd adapters this weekend

to test it with a full formated hdd consiting of one whole bfs partition

comment:5 by backupwww@…, 18 years ago

I installed HAIKU on a new blank hdd. First I tested it with BeOS R5 Pro and BeOS boots. I delete the BeOS files and copied HAIKU on it. HAIKU does not boot.

HAIKU Boot Loader says Select boot volume (Current: None)

comment:6 by axeld, 18 years ago

Description: modified (diff)
Platform: All

Bug #874 is a duplicate of this bug, and provides additional info.

Note: See TracTickets for help on using tickets.