Bug 441465 - Install has no X on PS3
Install has no X on PS3
Product: Fedora
Classification: Fedora
Component: rhpxl (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks: F9Blocker
  Show dependency treegraph
Reported: 2008-04-08 05:12 EDT by David Woodhouse
Modified: 2008-04-09 13:29 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-09 13:29:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Woodhouse 2008-04-08 05:12:05 EDT
Today's installer finds no graphics device on PS3. This was working a week or
two ago.
Comment 1 David Woodhouse 2008-04-08 06:14:25 EDT
I suspect this is due to the du-kudzufication of rhpxl? kudzu has special cases
for virtual framebuffer devices, such as the PS3 and Xen.

The PS3 framebuffer shows up in HAL like this:

udi = '/org/freedesktop/Hal/devices/ps3_system_bus_ioc0_01'
  info.linux.driver = 'ps3fb'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'PS3 Device (ioc0_01)'  (string)
  info.subsystem = 'ps3_system_bus'  (string)
  info.udi = '/org/freedesktop/Hal/devices/ps3_system_bus_ioc0_01'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'ps3_system_bus'  (string)
  linux.sysfs_path = '/sys/devices/ps3_system/ioc0_01'  (string)
  ps3_system_bus.id = 'ioc0_01'  (string)

You probably don't want to rely on that though; if you don't find any other
video cards and if /dev/fb0 exists, just use it.
Comment 2 Adam Jackson 2008-04-08 16:31:14 EDT
Fix for this (I hope) built as rhpxl 1.4.  Please test, and reopen if this isn't
Comment 3 David Woodhouse 2008-04-09 08:21:11 EDT
I'm not sure that checking all HAL devices for 'info.linux.driver' ends with
'fb' is really the best way to achieve this. In some cases, the framebuffer
device might not be known to HAL -- it's just a coincidence that it is on the
PS3. I suspect it isn't for Xen framebuffer. It would be better to look for
/dev/fb0 or in /proc/fb, surely?

Also, X doesn't seem to be working anyway (with no xorg.conf)...
(EE) Unable to locate/open config file
Primary device is not PCI
[New Thread 0xf7fed000 (LWP 23934)]
---Type <return> to continue, or q <return> to quit---

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf7fed000 (LWP 23934)]
0x10084128 in chooseVideoDriver ()
(gdb) bt
#0  0x10084128 in chooseVideoDriver ()
#1  0x100849c4 in xf86AutoConfig ()
#2  0x10065c88 in InitOutput ()
#3  0x10022158 in main ()

Comment 4 David Woodhouse 2008-04-09 10:54:33 EDT
[root@dyn-253 ~]# system-config-display
Traceback (most recent call last):
  File "/usr/share/system-config-display/xconf.py", line 293, in <module>
    vc = rhpxl.videocard.VideoCardInfo()
  File "/usr/lib/python2.5/site-packages/rhpxl/videocard.py", line 183, in __init__
    fdevs = [x for x in devs if
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in __call__
  File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 607, in
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchProperty: No property
info.linux.driver on device with id /org/freedesktop/Hal/devices/computer_alsa_timer
Comment 5 Adam Jackson 2008-04-09 13:29:39 EDT
Re-fixed in rhpxl 1.5.  The segv when running without a config file should be
resolved in xserver, afaik.

Note You need to log in before you can comment on or make changes to this bug.