[parisc-linux] Startup problem X

[parisc-linux] Startup problem X

[JOERGENSEN,RUNAR (HP-Norway,ex1)]

Greetings

I'm having X startup problems with a C200 (Raven/U+)
and 20" Color monitor (1280x1024, A4331D). I'm using=20
the framebuffer driver ("fbdev"), but I never get passed the=20
"Shadow framebuffer" part. X crashes complaining
about: FBIOPUT_VSCREENINFO: invalid argument
AddScreen/ScreenInit failed for driver 0

I would have loved to share some logs, but this unit=20
is not on net...yet.=20

I've looked around and tried a couple of different=20
Xf86config files. Does anyone have a sample config=20
file to share with the above setup?=20

XFree86 version: 4.1.0.1
OS: Linux 2.4.9-pa79 parisc64 [ELF]=20

Regards,
Runar J=F8rgensen=20

Re: [parisc-linux] Startup problem X

[Grant Grundler]

"JOERGENSEN,RUNAR (HP-Norway,ex1)" wrote:
> I'm having X startup problems with a C200 (Raven/U+)
...
> about: FBIOPUT_VSCREENINFO: invalid argument
> AddScreen/ScreenInit failed for driver 0
...
> XFree86 version: 4.1.0.1
> OS: Linux 2.4.9-pa79 parisc64 [ELF] 

Try a 32-bit kernel.
64-bit kernel might want an ioctl "wrapper" which hasn't been written.
Newer kernels are available on ftp://ftp.parisc-linux.org/kernels/32

grant

Re: [parisc-linux] Startup problem X

[Grant Grundler]

"JOERGENSEN,RUNAR (HP-Norway,ex1)" wrote:
> I'm a bit confused because I though we installed
> the 32bit version. In fact, when we boot we get
> thew following kernel: /boot/vmlinux-2.4.9-32.
> When I do a "file" on /boot/vmlinux-2.4.9-32,
> I get 32bit ELF executable.

Look at /etc/palo.conf and see what vmlinux it points to.
That's the one that's getting loaded/run.
By default you should have gotten a 32-bit kernel.
I doubt the syscall wrapper is the issue.

Newer 2.4.16 kernels are available from ftp.parisc-linux.org/kernels/32.
I suggest grabbing one of those.

> The OS line I presented was picked from what
> "XFree86 -version" reports.

eg. Build Operating System: Linux 2.4.13 i686 [ELF] 

"uname -m" will tell you which vmlinux you are running on *now*.
Not which one the XF86 binaries where built on.

> A mismatch in the image itself?

not likely.
Sounds like you have the original, mostly working kernel still.
Just try a newer one.

grant