Opened 13 years ago
Last modified 3 years ago
#7619 assigned bug
Hang on rocket icon: Toshiba Satellite 2615DVD
| Reported by: | umccullough | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Servers/app_server | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
My Toshiba Satellite 2615DVD/6.0 hangs on the Rocket icon during boot. it seems perhaps related to the VESA driver and/or app_server, as there's a section in the serial debug output that says:
Finding best mode failed
After the vesa driver loads.
Full log will be attached. After it hung for a while, I dropped to KDL and executed teams, threads, and sems to see if there's anything useful in the output.
Serial log is from hrev41826
Attachments (2)
Change History (12)
by , 13 years ago
| Attachment: | satellite_r41826.log added |
|---|
comment:1 by , 13 years ago
It seems I forgot to update the serial log text file with the KDL output before attaching - oops.
Let me know if there's any KDL output that would be useful, or any tracing I should enable?
comment:3 by , 11 years ago
Seems to happen on latest hrev45651 nightly as well - I'll hook up another serial cable and see if there's anything new in the syslog.
comment:4 by , 11 years ago
I hooked this laptop to an external display (since the internal screen is only 800x600), and specified to use 1024x768@16bpp in the failsafe video modes - and it worked!
So, does app_server refuse to work in 800x600 resolutions?
follow-up: 6 comment:5 by , 11 years ago
It shouldn't, at least. The message you see in the syslog comes from: http://code.metager.de/source/xref/haiku/src/servers/app/Screen.cpp#92
And is called from: http://code.metager.de/source/xref/haiku/src/servers/app/VirtualScreen.cpp#113
Since you only see the message once, it looks like the second call succeeds. I take it also does not work with failsafe video mode of 800x600x16 on the internal screen?
Does the machine really hang, or can you talk to it via the network?
comment:6 by , 11 years ago
Replying to axeld:
Since you only see the message once, it looks like the second call succeeds. I take it also does not work with failsafe video mode of 800x600x16 on the internal screen?
Oh :) - it does actually boot to a desktop when forced to either 800x600x16 or 800x600x32. The latter seems to take several minutes from the rocket icon before it shows a blue background. (probably why I assumed it had failed before)
If I don't specify a mode manually, it never seems to get to a desktop at all, even after sitting overnight.
Does the machine really hang, or can you talk to it via the network?
Yeah, I believe it is still technically running, just without a desktop - I see the activity light on my USB ethernet adapter blinking (no built-in ethernet on this one).
On a side note, there is something fundamentally wrong with Haiku on this machine - it runs amazingly slow (only 430mhz P3 Celeron, but it's still not running properly). Haiku doesn't seem to keep proper time on this machine either. I timed how long it took for 10 seconds to tick off the system clock with Haiku running, and it was ~72 seconds wall time.
I'm guessing there's some kind of timer issue at work here.
comment:7 by , 11 years ago
Setting aside the performance problem - is there something that I can check to see why it doesn't choose the proper mode automatically, but works when i force it?
comment:8 by , 11 years ago
We'll need a bit more debug output in the app_server for this. Please try with hrev45716 or newer.
comment:9 by , 7 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
Serial log