Page 4 of 5 FirstFirst 12345 LastLast
Results 31 to 40 of 48

Thread: Om on BeagleBoard XM

  1. #31
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    2,359
    Not sure why...all i added was a line to the configurations. Next to the configuration with all the 8's I needed to see what the Surface Type was. If its not 7 but the other configs have a 7 my next question will be what the Color Depth is set to in your xorg config.


    edit:
    Reading through the beagleboard documentation it appears to support 32bit and 16bit just not 24bit color. Some of the instructions configure things for 16bit and some for 24 (which breaks openGL support completely). According to one article I read...for DVI, 1280x720 there is two sets of boot options.

    For 16bit:
    console=ttyS0,115200n8=noinitrd ip=dhcp rw root=/dev/mmcblk0p2 omapfb.mode=dvi:1280720MR-16@60

    For 32bit:
    console=ttyS0,115200n8=noinitrd ip=dhcp rw root=/dev/mmcblk0p2 omapfb.mode=dvi:1280720MR-24@60

    followed by:

    /usr/sbin/fbset.real -depth 32 -rgba 8/16,8/8,8/0,8/24

  2. #32
    Constant Bitrate smp4488's Avatar
    Join Date
    Oct 2007
    Location
    Louisville, KY
    Posts
    125
    Surface type was 97. Im using an HDMI to DVI adapter. Do you want me to try both of the boot options? Ubuntu 10.10 has this new way of handling Xorg config files and i cant find my Xorg.conf. I can place configurations in /usr/share/X11/xorg.conf.d/.

  3. #33
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    2,359
    Quote Originally Posted by smp4488 View Post
    Surface type was 97. Im using an HDMI to DVI adapter. Do you want me to try both of the boot options? Ubuntu 10.10 has this new way of handling Xorg config files and i cant find my Xorg.conf. I can place configurations in /usr/share/X11/xorg.conf.d/.
    I'll make it easy then....first line of the Graphics Explorer will display display depth. I can't find the file either and am not even sure if it gets overridden by the boot options but the API should always work.
    Attached Files Attached Files

  4. #34
    Constant Bitrate smp4488's Avatar
    Join Date
    Oct 2007
    Location
    Louisville, KY
    Posts
    125
    Display Depth: 16 bits

  5. #35
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    2,359
    Quote Originally Posted by smp4488 View Post
    Display Depth: 16 bits
    Alright that explains the problems.... Can you try the boot options for 32bit mode I listed?

    mainly the -16 in your current config needs to be changed to -24 and then that second line needs to be added in underneath

    edit:
    And in case the linux fairy is still watching..... kev does the n900 use 16 or 24/32 bit?

  6. #36
    Constant Bitrate smp4488's Avatar
    Join Date
    Oct 2007
    Location
    Louisville, KY
    Posts
    125
    For some reason i don't think i am running GRUB. I will have to mess with boot settings when i get home.


    Edit:

    Found boot.cmd in /boot/uboot/ and modified it for 32, recompiled uboot and rebooted. GraphicsExplorer still shows 16 bit. When i run fbset my screen becomes all messed up. Its the top half of the screen, split in two with mirror images on each, and a green and purple hue.

  7. #37
    Constant Bitrate smp4488's Avatar
    Join Date
    Oct 2007
    Location
    Louisville, KY
    Posts
    125
    I have Ubuntu booting into 24 and 32 bit modes. The Uboot config files are in /boot/uboot/. Graphics explorer shows 24 and 32. AppCrash log is Failed to create EGL context, error: 12289.

  8. #38
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    2,359
    Possibly fixed in rev 611

  9. #39
    Constant Bitrate smp4488's Avatar
    Join Date
    Oct 2007
    Location
    Louisville, KY
    Posts
    125
    OM Build 611, no app crash or log files.

    Terminal Output:

    Code:
    X Error of failed request:  XI_BadDevice (invalid Device parameter)
      Major opcode of failed request:  141 (XInputExtension)
      Minor opcode of failed request:  48 ()
      Device id in failed request: 0x6
      Serial number of failed request:  21
      Current serial number in output stream:  21

  10. #40
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    2,359
    Any window displayed? If its making it that far i would guess the graphics stuff is all fully working now

Page 4 of 5 FirstFirst 12345 LastLast

Similar Threads

  1. Replies: 42
    Last Post: 12-11-2009, 02:36 PM
  2. Got XM to work, then it took a dump
    By DuDs in forum StreetDeck
    Replies: 3
    Last Post: 05-06-2006, 05:42 PM
  3. XM Channel Changes
    By Chuck in forum Road Runner
    Replies: 2
    Last Post: 04-05-2006, 04:33 AM
  4. XM Satellite Radio to Unveil XM Advanced Services at 2006 Consumer
    By Will Albers in forum General MP3Car Discussion
    Replies: 2
    Last Post: 03-27-2006, 08:49 PM
  5. Using an XM direct as an XMPCR
    By dacndar in forum General Hardware Discussion
    Replies: 20
    Last Post: 10-17-2004, 01:21 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •