Tired of Running Haiku Under VMs

21

[quote=umccullough]Starting with your last question:

Now, i’m looking in there, and I see a legacy_sata driver being installed. When I go look at this driver, it has a whole list of PCI ids that it supports.

I looked up your motherboard, and it appears to have an nforce4 chipset - the legacy_sata driver only supports a few NF2/3 chips - so I have a feeling you’re out of luck until the AHCI driver is completed :frowning: It’s always hard to get modern hardware working with alternative OSes :frowning: I’m not entirely sure though - so if you can get the vendor/device IDs for your SATA controller, you can verify them against the list in src/add-ons/kernel/busses/ide/legacy_sata/legacy_sata.c
[/quote]

I have a MSI K9NGM2 (http://global.msi.com.tw/index.php?func=proddesc&prod_no=257&maincat_no=1) which has a NVIDIA nForce 430 southbridge and that works very well with the legacy_sata driver. nForce 4 and 5 (and the earlier ones also of course) doesn’t support AHCI and should use the legacy_sata driver, I’m not sure about the 6 series.

22

Oh well. I don’t have another machine, so I can’t get a logfile, and my BIOS has no legacy_mode. Looks like I’m out of luck.

I’ve seen some progress on the AHCI driver on the frontpage of this website. I can only hope it gets done ASAP so that I can finally use the OS.

23

Your hardware is not AHCI compliant. You need the legacy_sata driver, which is already included in the image. You don’t need to use legacy mode, as the driver should support your sata controller.

24

AHCI works only on many ( but not all ) “newer” sata controllers.

Normally your motherboard manual would say if your board supports AHCI. I believe that AHCI is not supported by your motherboard.

You’re stuck with getting the legacy_sata driver working for you.

Only certain legacy ( Nvidia ) sata controllers are supported with legacy sata driver. To see if yours is, do the following ( in Windows XP ):

Getting the Vendor & Device ID ( for Sata Controller ):

  1. Start->Control Panel->System
  2. Click “Hardware” Tab, click “Device Manager”
  3. Double Click “SCSI & RAID Controllers”
  4. Double Click on your SATA Controller
  5. Click “Details” Tab
  6. Provide the info you get here

ie: PCI\VEN_1095&DEV_3112
Silicon Image 3112 SATA Controller
From above: Vendor id=0x1095, Device id=0x3112

Device & vendor ids can be used to verify if legacy sata driver supports your sata controller.

Fredrik, would you mind giving your vendor & device ids for your sata controller also, for comparison?

PS, you can also get vendor & device ids from Linux too.

25

Sure, my vendor id is of course 0x10de since it’s nvidia, and the device id is 0x0266. You can see that it’s supported in http://svn.berlios.de/viewcvs/haiku/haiku/trunk/src/add-ons/kernel/busses/ide/legacy_sata/legacy_sata.c?rev=21951&view=markup

26

My apologies, I haven’t done much research on nForce SATA controllers… (which is ironic since I have two different mobos with this).

I just looked up my Gigabyte GA-M55plus-S3G board and it also has the nvidia 0x0266/0x0267 (MCP51) devid controller…

My ECS GeForce6100SM-M board (currently in RAID configuration) has 0x03F6 (MCP61)

Unfortunately I can’t test either of these soon :frowning:

27

Cool guys.

It looks like your sata controllers are supported ( or should be ) by the legacy sata driver.

Urias, hopefully you can test out one of those motherboards. The one of interest would be the ECS board. Because it has newer (MCP61) controller?

Ankur, if you could give your vendor id ( should be 0x10de for Nvidia ) & device id then we can find out if your sata controller is supported.

The best way to know if your hardware works, in Haiku, is always to give the brand, model, vendor id and device id. This way it can be matched up to Haiku source code.

Later,

28

I’ve got the ECS GeForce6100SM-M myself, and it’s able to boot Haiku fine. Though so far not much else works other than the video.

29

How do I get the vendor ID and stuff under Linux? KInfoCenter doesn’t help much.

EDIT : I just heard about some 137gig limit. I have a 250GB HDD with Haiku on (Linux name) sda9 (total 10 partitions, 25gigs each). Can this be a problem?

30

Thanks Michael. Good to hear that sata & video are working for you.

Ankur,
Ok, under Linux ( I had to boot into Fedora to check this ):

Type ( easy way ):
"lspci -nn | grep -i SATA "

My result ( copy yours like I’ve done below ):
01:0d.0 Mass storage controller [0180]: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller [1095:3112] (rev 02)

Notice at the end it says: " [1095:3112] ", 1095 is the Vendor ID, 3112 is the Device ID.

Your Vendor id should be 10de because that identifies Nvidia

OR you can do ( hard way ):
“lspci -nn” and search through to find your SATA controller.

BeOS had the hard drive limit because at the time Be Inc. did not realize that drive sizes would get bigger than 137GB in the future. Haiku does not have drive limit issue.

31

You know this for sure? Haiku uses the same boot block as R5 did - and this boot block has the offset to the partition start in it… I speculate that possibly a partition starting above the 137gb limit may actually be unable to boot.

Now, on the other hand, Haiku probably supports accessing a disk beyond 137gb, but booting from a partition starting beyond 137gb is a different issue.

Please let us know if you’ve successfully booted haiku from a partition beyond the first 137gb of the disk - I’d like to know for sure that this works… and I haven’t had time to test it myself :frowning:

32

Good call Urias. I was thinking about Haiku supporting a drive bigger than 137GB in size ( which it should ). I can not say if Haiku will boot a partition that is over the 137GB limit - may or may not.

So, that could be an issue. But first thing is to find out the hardware Ankur has to see if it is even supported by Haiku. If so, then can move onto the other issues like this, etc.

33

Correct, but I think he was referencing another forum post - I just wanted to make sure it wasn’t being discounted here :wink:

http://haiku-os.org/community/forum/installing_haiku_to_a_partition_from_linux#comment-7863

Actually, I just realized my statement that “Haiku uses the same boot block as R5” may be inaccurate… perhaps it appears that way because I formatted the specific partition from R5 rather than using the tools provided in the Haiku repository… I will check this.

34

Here’s the SATA stuff :

00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0054] (rev f3) 00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0055] (rev f3)

Did I mention that my sda9 is actually is under an extended partition? Is that a problem?

35

Your device ids 0x0054, 0x0055 should both be supported by the legacy sata controller because they are both listed in there.

from legacy sata driver:
#define PCI_vendor_NVIDIA 0x10de
[snip]
#define PCI_device_CK804S1 0x0054
#define PCI_device_CK804S2 0x0055
[snip]

Sata driver is unlikely to be the problem. Some other things to check out:

  1. Could be because your partition is over 137GB mark or
  2. Partition is extended instead of primary or
  3. Is your partition bfs formatted?

Try hitting [SPACEBAR] quickly when booting & it’ll take you to safe mode. Check Console Debugging & that’ll make the booting more verbose & you can see what error you are given.

36

[quote=General Maximus]Here’s the SATA stuff :

00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0054] (rev f3) 00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0055] (rev f3)

Did I mention that my sda9 is actually is under an extended partition? Is that a problem?[/quote]

I boot Haiku from an extended partition, but it is a PATA system. The legacy_sata driver is very new, so it is possible your system shows up a bug in it. If you file a bug at http://dev.haiku-os.org with any information you can get then it will be seen by the people who may be able to help.

37

I got the new Image.
Installed it from zeta onto a bootable partition using cp -a * /HaikuTest
Boot goes fine but I only see a blank blue screen with cursor.
When try safe mode with console output and safe video mode, I get in the haiku shell successfully.
Commands seem to work fine.
/var/log has no log file in it, So I cannot see what is the problem.
I have a Sata drive, but obviously shell works.
I usually use a usb mouse, but I have problem with a PS2 mouse also.

4 months ago I did have tacker up.

Any ideas?

38

I haven’t tried a recent build in some weeks - so maybe some recent changes have rendered something “unstable”…

I assume that since you are running Zeta on this same machine, you have a decent amount of RAM… (at least 128mb)

Perhaps some of the new VM changes are causing an issue with app_server, Tracker, etc?

39

In today’s xxx66/67 revisions I have the same phenomenon on a PATA system that previously worked fine. Either everything looks normal but I cannot launch any preferences or applications, or I see only the Terminal window and the blue background (no desktop icons, no menu/tracker). RAM is 512 MB. Shutting down or restarting doesn’t work either.

40

Yes, I have a giga byte of memory. :slight_smile: