Re: Can't get xorg working on iBook - Help please!
On Wed, Dec 31, 2008 at 10:37 AM, Michel Dänzer <daenzer@debian.org> wrote:
> On Tue, 2008-12-30 at 18:00 -0700, Bob Lounsbury wrote:
>> On Mon, Dec 29, 2008 at 1:42 AM, Michel Dänzer <daenzer@debian.org> wrote:
>> > On Sat, 2008-12-27 at 11:15 -0700, Bob Lounsbury wrote:
>> >> On Sat, Dec 27, 2008 at 2:06 AM, Michel Dänzer <daenzer@debian.org> wrote:
>> >> > On Fri, 2008-12-26 at 10:27 -0700, Bob Lounsbury wrote:
>> >> >> Has anyone experienced the error in the attached Xorg.0.log file? I've
>> >> >> also attached my xorg.conf. I've tried all sorts of changes to the
>> >> >> xorg.conf, but nothing works.
>> >> >
>> >> > [...]
>> >> >
>> >> >> (**) R128(0): Using framebuffer device
>> >> >> (II) Loading sub module "fbdevhw"
>> >> >> (II) LoadModule: "fbdevhw"
>> >> >>
>> >> >> (II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so
>> >> >> (II) Module fbdevhw: vendor="X.Org Foundation"
>> >> >> compiled for 1.5.2, module version = 0.0.2
>> >> >> ABI class: X.Org Video Driver, version 4.1
>> >> >> (WW) open /dev/fb2: No such file or directory
>> >> >> (WW) open /dev/fb3: No such file or directory
>> >> >> (WW) open /dev/fb4: No such file or directory
>> >> >> (WW) open /dev/fb5: No such file or directory
>> >> >> (WW) open /dev/fb6: No such file or directory
>> >> >> (WW) open /dev/fb7: No such file or directory
>> >> >> (EE) Unable to find a valid framebuffer device
>> >> >> (EE) R128(0): Failed to open framebuffer device, consult warnings and/or errors above for possible reasons
>> >> >> (you may have to look at the server log to see warnings)
>> >> >
>> >> > This is probably because you're using OFfb rather than aty128fb (what
>> >> > does /proc/fb contain?) in console. Either fix that, or try without
>> >> > Option "UseFBDev", though IIRC that may be tricky to get working with
>> >> > the r128 driver on Apple laptops.
>> >>
>> >> Sorry, I'm pretty new to linux, I don't know what 'using OFfb rather
>> >> than aty128fb' means.
>> >
>> > The /proc/fb contents in your other post show that you actually are
>> > using aty128fb... I took a look at the failing X server code, it looks
>> > like it may have a bug which causes it to fail to recognize the
>> > correlation between the PCI device and the framebuffer device. What does
>> >
>> > find /sys -name \*fb0
>> >
>> > say?
>>
>> /sys/devices/pci0000:00/0000:00:10.0/graphics:fb0
>
> Okay, it looks like this is due to a bad X server change which was
> unfortunately backported to the 1.5 release. I've contacted the author
> of the change and we'll hopefully come up with a fix soon.
>
>
>> >> If I set the option to false rather than true then I get the
>> >> attached error message.
>> >
>> > Option "NoInt10"
>> >
>> > may get you past this, but as I said, it might be tricky to get the r128
>> > driver working without UseFBDev on an Apple laptop.
>>
>> I tried this option and I didn't get any error messages and X seemed
>> to start with the typical X mouse. There were a few of warnings, but
>> no errors (I attached the log). However, now when I try to run
>> 'gnome-session' as a normal user I get:
>>
>> ** (gnome-session:3719): WARNING**: Cannot open display
>
> Looks like the $DISPLAY environment variable isn't set properly. It's
> probably easier if you use a display manager like gdm or at least start
> gnome-session together with X using something like startx or
>
> xinit $(which gnome-session)
>
>
> --
> Earthling Michel Dänzer | http://www.vmware.com
> Libre software enthusiast | Debian, X and DRI developer
>
Just wanted to report that X and gnome are working, although it is
very old qt looking and is being displayed at 1360x768 rather than
1024x768 as I have specified in the xorg.conf.
I assume the old qt looks are due to the NoInt10 option?
Thanks for the help!
/Bob
Reply to: