[haiku-bugs] Re: [Haiku] #6042: Booting Haiku R1/alpha2 with Radeon 9800 drops you in kernel debug land
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Mon, 24 May 2010 13:56:10 -0000
#6042: Booting Haiku R1/alpha2 with Radeon 9800 drops you in kernel debug land
--------------------------------------+-------------------------------------
Reporter: mr3d | Owner: euan
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: Drivers/Graphics/radeon | Version: R1/alpha2
Keywords: radeon 9800 kernel debug | Platform: x86
Blockedby: | Patch: 0
Blocking: |
--------------------------------------+-------------------------------------
Comment(by bonefish):
First of all, mr3d please attach at least the KDL output you get --
probably some panic message, ideally with stack trace.
@euan, the last radeon specific output is:
{{{
5589 KERN: Radeon - Radeon_MapDevice: device: 010000
5590 KERN: Radeon - Radeon_MapDevice: old PCI command state: 0x00000087
5591 KERN: Radeon - Radeon_MapDevice: physical address of memory-mapped
I/O: 0xf5000000-0xf500ffff
5592 KERN: add_memory_type_range(1206, 0xf5000000, 0x10000, 0)
[...]
5598 KERN: Radeon - Radeon_GetPLLInfo: ref_clk=2700, ref_div=12,
xclk=33800, min_freq=20000, max_freq=40000 from Legacy BIOS
5599 KERN: Radeon - Radeon_GetConnectorInfoFromBIOS: Port0: DDCType-2,
DACType-1, TMDSType-0, ConnectorType-3
5600 KERN: Radeon - Radeon_GetConnectorInfoFromBIOS: Port1: DDCType-3,
DACType-0, TMDSType--1, ConnectorType-2
5601 KERN: Radeon - Radeon_GetTMDSInfoFromBios: DFP table revision: 4
5602 KERN: Radeon - RADEON_GetAccessibleVRAM: Generation 1 PCI
interface in multifunction mode, accessible memory limited to one aperture
5603 KERN:
5604 KERN: Radeon - Radeon_DetectRAM: Detected total video RAM=131072K,
accesKERN: sible=131072K (PCI BAR=131072K)
5605 KERN: Radeon - Radeon_DetectRAM: 128 MB SDR SGRAM found on 256
wide bus
5606 KERN: Radeon - Radeon_UnmapDevice:
5607 KERN: remove_memory_type_range(1206, 0xf5000000, 0x10000, 0)
[...]
5613 KERN: remove_memory_type_range(1205, 0xc0000, 0x40000, 0)
[...]
5618 KERN: Radeon - probeDevice: found Radeon 9800 Pro NH; ASIC: r350
5619 KERN: Radeon - probeDevice: making /dev/graphics/1002_4E48_010000
5620 KERN: Radeon - Radeon_ProbeDevices: 1 supported devices
5621 KERN: loaded driver /boot/system/add-
ons/kernel/drivers/dev/graphics/radeon
}}}
I.e. it seems everything is unmapped (though device is still published?).
And following that output we get:
{{{
5623 KERN: vesa: init_hardware()
5624 KERN: vesa: init_driver()
5625 KERN: vesa: publish_devices()
5626 KERN: vesa: find_device()
5627 KERN: loaded driver /boot/system/add-
ons/kernel/drivers/dev/graphics/vesa
[...]
5664 KERN: vesa: vesa_init() completed successfully!
5665 KERN: vesa: acc: vesa.accelerant
[...]
5737 KERN: vesa: vbe_set_mode(): BIOS returned 0x014f
5738 KERN: vesa: vesa_set_display_mode(): cannot set mode
[...]
5762 KERN: vesa: vbe_set_mode(): BIOS returned 0x014f
5763 KERN: vesa: vesa_set_display_mode(): cannot set mode
[...]
5787 KERN: vesa: vbe_set_mode(): BIOS returned 0x014f
5788 KERN: vesa: vesa_set_display_mode(): cannot set mode
[...]
5812 KERN: vesa: vbe_set_mode(): BIOS returned 0x014f
5813 KERN: vesa: vesa_set_display_mode(): cannot set mode
}}}
Looks like VESA is being used and something doesn't work correctly.
--
Ticket URL: <http://dev.haiku-os.org/ticket/6042#comment:2>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
