Booting stops somehere in the bootscript

[ekdahl]

It worked before Begeistert and graphic card and memory upgrade. I'm not exactly sure where it stops, but the screen is blue and mouse pointer is visible. Deskbar and Terminal doesn't appear though. The red light on the mouse is never lit. Neither F12 nor Ctrl Alt Del works. Safe mode works. How should I proceed?

[euan]

syslog from euan

[euan]

I've been seeing the same symptoms for a while too. However it now happens pretty much all the time on my Amd X2 system. Syslog attached. KDL was available, didn't know where to look, so had a general browse around. can't seem to figure out what word kdl hangman things co?e is. coke? core? code? cope? cote? coye? cole? coze? coxe? cove? cobe? cone? come??? anyways, hope the syslog is useful...

[ekdahl]

I might add that I also have an Athlon 64 x2, if that's relevant.

[mmlr]

Replying to ekdahl:

I might add that I also have an Athlon 64 x2, if that's relevant.

It might be relevant. Does this also happen when you disable SMP from the boot menu? I'm currently investigating the SMP issues that make Haiku unusable on a Quad core and there might just be something that also affects dual core AMD systems.

[mmlr]

Could you please try with r23721 or newer? This might just have fixed such freezes on SMP systems.

[ekdahl]

Replying to mmlr:

Could you please try with r23721 or newer? This might just have fixed such freezes on SMP systems.

It boots now! Thank you!

Too bad that the mouse doesn't work. I'll open another ticket for that.

[euan]

Replying to mmlr:

Could you please try with r23721 or newer? This might just have fixed such freezes on SMP systems.

Thanks very much. I hope to test this tomorrow evening when I'm home. Hopefully this will also fix #1711

Cheers!

[euan]

no change tested with mmlr's patches up to today's [23742] :(

[hunnia]

This may be related to the above ticket. I have an amd64 computer with sata drives and usb mouse. Installed on sda the newest snapshot. If I boot I get the screen, mouse pointer but no tracker. In the save mode I do get into the haiku shell, in which lot of commands work, but more complicated commands give: "Cannot initialize global fonts." If I disable USB in the BIOS the problem still exist. When I am in the empty screen with the mouse pointer, Ctrl-Alt-Enter does NOT open the Team Monitor. F12 enters kernel debug. Executing teams display (Here I write only the last word of each line) : syslo, waitfor, sh, regis, debug, net_s and app_s. a back trace indicate that I am in an idle tread. Vector 0x21 error code 0x0

I do have a single core AMD64. For testing I use a PS2 Mouse. Downloading the newest haiku (28 Jan), I found for my pleasure that the bootup printout, uses "more" and can be controlled from the keyboard. All drivers and drives seem to be detected correctly. The following few lines look interesting (Before we go to graphics mode.

AGP: found 2 AGP devices

load driver() ....graphics/nvidia vesa : init_hardware()

init_driver() publish_devices find_device

loaded driver ....graphics/vesa via: init_hardware() failed: General system error vesa: vesa_init() completed successfully vesa: acc: vesa.accelerant

Could the General system error cause the problem?

[euan]

No it just returns that to say that driver doesn't support your graphics card.

[korli]

from Lengyel Sándor: I got haiku working on my virtual box. If on the virtual box I change t the boot script, so that in the safe mode it starts the app_server instead of the fake_app_server, and I select the safe mode, I get to the (safe-mode) shell just like I do normally. (Using the fake_app_server.)

If I do the same on my Haiku which is installed on my hard drive and select

safe mode, I will get a black screen in place of the shell. Could it mean that MY problem is with the application server?

[hunnia]

Well in my case I did locate the problem. I do not know whether it is the #1723 biug. It is not the application server. Going to a safe video mode my screen does not go black and slowly altering the script for the safe mode I found the line which cause the problem. The boot up hangs (with a blue screen and a cursor) at waitfor_input_server_event_loop_ line When I comment out this line, in the boot script, I get a perfect screen with tracker, icons and all. (But of course the system is unusable.

[ekdahl]

It works for me (I submitted the bug) when I remove the ehci driver, so #1726 is the same bug but more descriptive for my problem.

[hunnia]

Replying to ekdahl:

It works for me (I submitted the bug) when I remove the ehci driver, so #1726 is the same bug but more descriptive for my problem.

I downloaded the latest image, r24101, removed ehci from the ...../busses directory and still failed. I still have to comment out waitfor_input_server_event_loop_ to make it somewhat work.

[hunnia]

Using the 2008 Aug 2 image on a Haiku partition boot up end executing the tracker is now successfull. So as far as I (hunnia) is concerned the problem get solved and if all agrees, the ticket can be closed.