No DVI after pacman -Syu

[wapiserv]

Hello,

i installed my new beagleboard xM with the default arch installation instruction.
Everything works well until i tried to update my arch with "pacman -Syu"
There was anew kernel version and some udev stuff with the update.

The board comes up after a reboot, i can login with ssh, but cant use the DVI output now. No screen.
Can someone help me.

Thanks.

[ggeorgan]

It seems this is a more general problem. It has been raised in another thread in this present forum. I have replicated this same finding in my installation, too. Apparently, pacman update is not really working for this platform.

[WarheadsSE]

I'd say it's not pacman, but the newer kernel, and the changes it brings with it.

[ggeorgan]

It is quite possible. The point of using arch is to have a rolling distribution. Keeping up with updates can only be done, if a significant number of users are there. It would appear that the critical number of (suitably qualified) users is not there yet for this platform and for this distro. Better to look at it all as an educational opportunity.

[pepedog]

You probably got an older kernel you can rollback to, using pacman -U, in /var/lib/cache/pacman
Then alter pacman.conf to stop kernel updates until this is fixed

[WarheadsSE]

Also, I hate to break it to you, but not all of our devs have all of the devices. Hell, I have 1 GFN & 5 oxnas's.

It's the kernel sources that broke these, so it's an upstream issue as far as I can tell.

[ggeorgan]

Why rollback, if one can avoid upgrading to a new kernel in the first place ? All one needs is proper warning, such as one finds in this forum. Of course, in another thread, one is urged to update to a newer kernel for performance. In that same thread there is a warning about the serial port not quite working. In fact, it gets stuck at the point at which ssh gets started and does not manage to end up in the command prompt like it does in Angstrom. Perhaps that' s a feature though, to force one to use ssh.
It would seem that, besides the small number of suitably qualified users, ARM devices are not quite similar enough to one another to allow relatively problem-free porting of software solutions from one to another. Hence developers end up getting overwhelmed.

[WarheadsSE]

A lot of it honestly has to do with the way the platforms work, and the poor support from originating manufacturers.

http://www.theinquirer.net/inquirer/new ... s-torvalds
http://www.theinquirer.net/inquirer/new ... con-europe

[android]

This issue seems to be preventing any graphical output from the beagleboard platform.

Is there any resolution?

For my application, hardware acceleration isn't necessary, but X is.

Is there anyway to get graphical output on omap currently?

On boot there is this:
$this->bbcode_second_pass_code('', 'omapfb omapfb: no driver for display')

And on attempting to startx:
$this->bbcode_second_pass_code('', '(EE) open /dev/fb0: No such file or directory')

Are there any clues into the origin of this issue?

Thank You...

johnea

[kmihelich]

Not quite sure why the fb device isn't there, make sure you're on the latest kernel. Install xf86-video-omapfb for the omapfb xorg driver.