[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Fwd: Re: X11 doesn't work]

Ste
Here's what I have up to now.  If you look through you may sort yours
out.  I may need to remove my FX card!

pal.
--- Begin Message --- 
Dr Gavin Seddon a écrit :

Hi,
Although I am familiar with Debian I am new to hppa.  I have installed
Sarge on my visualize but I cannot startx.  I had a look through my
installed lists and it appears the xserver can be installed with
xserver-common.  This asks a series of q's about the hardware.  I had a
look in 'dmesg' and /proc/pci and have seen the monitor is recognised as
a lcd device, even though it is a 21" sgi.  The graphics is A4977A
vusualize EG.  Not an option, should I use vga?

Normally I would boot onto the Knoppix cd and cp /etc/X11/config-4 to my
hard disc.  But I no longer have this facility.  Also, my mouse and kb
are usb which is not an option in the xserver setup.

How do I go about installing and configuring/running X?
Thanks.
GS.


http://www.fr.parisc-linux.org/faq/graphics-howto.html
--> no vga but fbdev .
try
dpkg-reconfigure xserver-xfree86

what do you have under :
/var/log/XFree86.0.log

regards,
Pierrick

--- End Message ---
--- Begin Message --- 
On Thu, Dec 16, 2004 at 04:33:55PM +0000, Dr Gavin Seddon wrote:
> The graphics is A4977A vusualize EG.

Good. That should work.

> How do I go about installing and configuring/running X?

Please post the /var/log/XFree86.0.log
after you run "startx" or "xinit".


Typically the resolution or color depth don't exactly match
what STI is reporting at boot time. Use "fbset -i" to determine
those parameters. This email might help you:
	http://lists.parisc-linux.org/pipermail/parisc-linux/2003-January/019040.html

grant


> Thanks.
> GS.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-hppa-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


-- 
To UNSUBSCRIBE, email to debian-hppa-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

--- End Message ---
--- Begin Message --- 
On Thu, Dec 16, 2004 at 04:33:55PM +0000, Dr Gavin Seddon wrote:
> How do I go about installing and configuring/running X?
> Thanks.

Make sure the package x-window-system-core is installed. VisEG is
a framebuffer, providing no acceleration, so you'll want to use the
"fbdev" X module, and make sure you're using stifb for your console.

Cheers,
	Kyle


-- 
To UNSUBSCRIBE, email to debian-hppa-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

--- End Message ---
--- Begin Message --- 
Dr Gavin Seddon a écrit :

Hi,
Although I am familiar with Debian I am new to hppa.  I have installed
Sarge on my visualize but I cannot startx.  I had a look through my
installed lists and it appears the xserver can be installed with
xserver-common.  This asks a series of q's about the hardware.  I had a
look in 'dmesg' and /proc/pci and have seen the monitor is recognised as
a lcd device, even though it is a 21" sgi.  The graphics is A4977A
vusualize EG.  Not an option, should I use vga?

Normally I would boot onto the Knoppix cd and cp /etc/X11/config-4 to my
hard disc.  But I no longer have this facility.  Also, my mouse and kb
are usb which is not an option in the xserver setup.

How do I go about installing and configuring/running X?
Thanks.
GS.


http://www.fr.parisc-linux.org/faq/graphics-howto.html
--> no vga but fbdev .
try
dpkg-reconfigure xserver-xfree86

what do you have under :
/var/log/XFree86.0.log

regards,
Pierrick

--- End Message ---
--- Begin Message --- 
On Thu, Dec 16, 2004 at 04:33:55PM +0000, Dr Gavin Seddon wrote:
> How do I go about installing and configuring/running X?
> Thanks.

Make sure the package x-window-system-core is installed. VisEG is
a framebuffer, providing no acceleration, so you'll want to use the
"fbdev" X module, and make sure you're using stifb for your console.

Cheers,
	Kyle

--- End Message ---
--- Begin Message --- 
On Thu, Dec 16, 2004 at 04:33:55PM +0000, Dr Gavin Seddon wrote:
> The graphics is A4977A vusualize EG.

Good. That should work.

> How do I go about installing and configuring/running X?

Please post the /var/log/XFree86.0.log
after you run "startx" or "xinit".


Typically the resolution or color depth don't exactly match
what STI is reporting at boot time. Use "fbset -i" to determine
those parameters. This email might help you:
	http://lists.parisc-linux.org/pipermail/parisc-linux/2003-January/019040.html

grant


> Thanks.
> GS.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-hppa-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

--- End Message ---
--- Begin Message --- 
Hi,
>
>Hi, 
>Wow, what a response!  I will post the logs as soon as I have inst. the
>other stuff.  I just noticed I had not inst xfonts-xxxdpi, doing this
>now.  Then I'll have to finish this later, I have to go out.
>
>Thanks again.
>
If I remember well, to be sure you have installed all the needed debs, use:

apt-get install x-window-system x-window-system-core

I don't remember, but I read in some manual/howto/..

Regards

SteX

-- 
GPG Key = D52DF829   --   Stex    -- <stefano.melchior@openlabs.it>
http://www.openlabs.it/~stex - Keyserver http://keyserver.kjsl.com
Registered user #324592 on the Linux Counter, http://counter.li.org

--- End Message ---
--- Begin Message --- 
Hi,
>
>Hi, 
>Wow, what a response!  I will post the logs as soon as I have inst. the
>other stuff.  I just noticed I had not inst xfonts-xxxdpi, doing this
>now.  Then I'll have to finish this later, I have to go out.
>
>Thanks again.
>
If I remember well, to be sure you have installed all the needed debs, use:

apt-get install x-window-system x-window-system-core

I don't remember, but I read in some manual/howto/..

Regards

SteX

-- 
GPG Key = D52DF829   --   Stex    -- <stefano.melchior@openlabs.it>
http://www.openlabs.it/~stex - Keyserver http://keyserver.kjsl.com
Registered user #324592 on the Linux Counter, http://counter.li.org

--- End Message ---
--- Begin Message --- 
Hi,

> (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument
> (EE) FBDEV(0): Mode init failed

do you have the fbset product installed ?

# fbset -i
?

not sure we can find a lot of info on www.google.com/linux
but i don't know axectly the problem.

I have quitly the same problem on one of my system.
not exactly the same FBIOPUT_ error... i am stiil looking for the solution.

best regards,
Pierrick


Dr Gavin Seddon a écrit :

On Thu, 2004-12-16 at 15:51, Pierrick HERVE wrote:


Dr Gavin Seddon a écrit :


Hi,
Although I am familiar with Debian I am new to hppa.  I have installed
Sarge on my visualize but I cannot startx.  I had a look through my
installed lists and it appears the xserver can be installed with
xserver-common.  This asks a series of q's about the hardware.  I had a
look in 'dmesg' and /proc/pci and have seen the monitor is recognised as
a lcd device, even though it is a 21" sgi.  The graphics is A4977A
vusualize EG.  Not an option, should I use vga?

Normally I would boot onto the Knoppix cd and cp /etc/X11/config-4 to my
hard disc.  But I no longer have this facility.  Also, my mouse and kb
are usb which is not an option in the xserver setup.

How do I go about installing and configuring/running X?
Thanks.
GS.


http://www.fr.parisc-linux.org/faq/graphics-howto.html
--> no vga but fbdev .
try
dpkg-reconfigure xserver-xfree86

what do you have under :
/var/log/XFree86.0.log

regards,
Pierrick

log attached.


Cheers.

GS


------------------------------------------------------------------------


This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org.  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-8 20040928144904 root@sarti.debian.org)
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.26-64 parisc64 [ELF] Build Date: 28 September 2004 
	Before reporting problems, check http://www.XFree86.Org/
	to make sure that you have the latest version.
OS Kernel: Linux version 2.4.27-32-smp (root@mkhppa3) (gcc version 3.3.4 (Debian 1:3.3.4-9)) #1 SMP Mon Aug 30 00:39:29 CEST 2004 Markers: (--) probed, (**) from config file, (==) default setting, 
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Fri Dec 17 15:03:30 2004
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Generic Monitor"
(**) |   |-->Device "Generic Video Card"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc104"
(**) XKB: model: "pc104"
(**) Option "XkbLayout" "uk"
(**) XKB: layout: "uk"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/CID" does not exist.
	Entry deleted from font path.
(**) FontPath set to "unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(--) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:0c:0: chip 1011,0019 card 103c,104f rev 41 class 02,00,00 hdr 00
(II) PCI: 00:0d:0: chip 11d4,1889 card 11d4,1889 rev 00 class 04,01,00 hdr 00
(II) PCI: 00:0e:0: chip 100b,0002 card 0000,0000 rev 03 class 01,01,8a hdr 80
(II) PCI: 00:0e:1: chip 100b,000e card 0000,0000 rev 01 class 06,80,00 hdr 80
(II) PCI: 00:0e:2: chip 100b,0012 card 0000,0000 rev 02 class 0c,03,10 hdr 80
(II) PCI: 00:0f:0: chip 1000,000b card 1000,1000 rev 04 class 01,00,00 hdr 80
(II) PCI: 00:0f:1: chip 1000,000b card 1000,1000 rev 04 class 01,00,00 hdr 80
(II) PCI: 02:03:0: chip 103c,1005 card 0000,0000 rev 03 class 03,80,00 hdr 00
(II) PCI: 03:02:0: chip 103c,1008 card 0000,0000 rev 02 class 03,80,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
	[0] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Host-to-PCI bridge:
(II) Bus 2: bridge is at (0:0:0), (2,2,0), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 2 I/O range:
	[0] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 2 non-prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 2 prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Host-to-PCI bridge:
(II) Bus 3: bridge is at (0:0:0), (3,3,0), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 3 I/O range:
	[0] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 3 non-prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 3 prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(!!) More than one possible primary device found
(--) PCI: (2:3:0) Hewlett-Packard Company A4977A Visualize EG rev 3, Mem @ 0xf8000000/25, BIOS @ 0xf6000000/16
(--) PCI: (3:2:0) Hewlett-Packard Company Visualize FX4 rev 2, Mem @ 0xfa000000/25, BIOS @ 0xf7000000/21
(II) Addressable bus resource ranges are
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
	[1] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
	[0] -1	0	0xffffffff - 0xffffffff (0x1) MX[B]
	[1] -1	0	0x00000000 - 0x00000000 (0x1) MX[B]
	[2] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[3] -1	0	0x00000000 - 0x00000000 (0x1) IX[B]
(II) Active PCI resource ranges:
	[0] -1	0	0xf4000000 - 0xf4001fff (0x2000) MX[B]
	[1] -1	0	0xf4004000 - 0xf40043ff (0x400) MX[B]
	[2] -1	0	0xf4002000 - 0xf4003fff (0x2000) MX[B]
	[3] -1	0	0xf4005000 - 0xf40053ff (0x400) MX[B]
	[4] -1	0	0xf4006000 - 0xf4006fff (0x1000) MX[B]
	[5] -1	0	0xf4007000 - 0xf4007fff (0x1000) MX[B]
	[6] -1	0	0xf4009000 - 0xf400900f (0x10) MX[B]
	[7] -1	0	0xf400a000 - 0xf400a00f (0x10) MX[B]
	[8] -1	0	0xf400b000 - 0xf400b00f (0x10) MX[B]
	[9] -1	0	0xf400c000 - 0xf400c1ff (0x200) MX[B]
	[10] -1	0	0xf4008000 - 0xf40083ff (0x400) MX[B]
	[11] -1	0	0xf7000000 - 0xf71fffff (0x200000) MX[B](B)
	[12] -1	0	0xfa000000 - 0xfbffffff (0x2000000) MX[B](B)
	[13] -1	0	0xf6000000 - 0xf600ffff (0x10000) MX[B](B)
	[14] -1	0	0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
	[15] -1	0	0x00000800 - 0x000008ff (0x100) IX[B]
	[16] -1	0	0x00000900 - 0x000009ff (0x100) IX[B]
	[17] -1	0	0x00000a00 - 0x00000a0f (0x10) IX[B]
	[18] -1	0	0x00000b00 - 0x00000b00 (0x1) IX[B]
	[19] -1	0	0x00000d00 - 0x00000d00 (0x1) IX[B]
	[20] -1	0	0x00000e00 - 0x00000e00 (0x1) IX[B]
	[21] -1	0	0x00000f00 - 0x00000f00 (0x1) IX[B]
	[22] -1	0	0x00001000 - 0x0000107f (0x80) IX[B]
(II) Active PCI resource ranges after removing overlaps:
	[0] -1	0	0xf4000000 - 0xf4001fff (0x2000) MX[B]
	[1] -1	0	0xf4004000 - 0xf40043ff (0x400) MX[B]
	[2] -1	0	0xf4002000 - 0xf4003fff (0x2000) MX[B]
	[3] -1	0	0xf4005000 - 0xf40053ff (0x400) MX[B]
	[4] -1	0	0xf4006000 - 0xf4006fff (0x1000) MX[B]
	[5] -1	0	0xf4007000 - 0xf4007fff (0x1000) MX[B]
	[6] -1	0	0xf4009000 - 0xf400900f (0x10) MX[B]
	[7] -1	0	0xf400a000 - 0xf400a00f (0x10) MX[B]
	[8] -1	0	0xf400b000 - 0xf400b00f (0x10) MX[B]
	[9] -1	0	0xf400c000 - 0xf400c1ff (0x200) MX[B]
	[10] -1	0	0xf4008000 - 0xf40083ff (0x400) MX[B]
	[11] -1	0	0xf7000000 - 0xf71fffff (0x200000) MX[B](B)
	[12] -1	0	0xfa000000 - 0xfbffffff (0x2000000) MX[B](B)
	[13] -1	0	0xf6000000 - 0xf600ffff (0x10000) MX[B](B)
	[14] -1	0	0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
	[15] -1	0	0x00000800 - 0x000008ff (0x100) IX[B]
	[16] -1	0	0x00000900 - 0x000009ff (0x100) IX[B]
	[17] -1	0	0x00000a00 - 0x00000a0f (0x10) IX[B]
	[18] -1	0	0x00000b00 - 0x00000b00 (0x1) IX[B]
	[19] -1	0	0x00000d00 - 0x00000d00 (0x1) IX[B]
	[20] -1	0	0x00000e00 - 0x00000e00 (0x1) IX[B]
	[21] -1	0	0x00000f00 - 0x00000f00 (0x1) IX[B]
	[22] -1	0	0x00001000 - 0x0000107f (0x80) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
	[0] -1	0	0xffffffff - 0xffffffff (0x1) MX[B]
	[1] -1	0	0x00000000 - 0x00000000 (0x1) MX[B]
	[2] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[3] -1	0	0x00000000 - 0x00000000 (0x1) IX[B]
(II) All system resource ranges:
	[0] -1	0	0xffffffff - 0xffffffff (0x1) MX[B]
	[1] -1	0	0x00000000 - 0x00000000 (0x1) MX[B]
	[2] -1	0	0xf4000000 - 0xf4001fff (0x2000) MX[B]
	[3] -1	0	0xf4004000 - 0xf40043ff (0x400) MX[B]
	[4] -1	0	0xf4002000 - 0xf4003fff (0x2000) MX[B]
	[5] -1	0	0xf4005000 - 0xf40053ff (0x400) MX[B]
	[6] -1	0	0xf4006000 - 0xf4006fff (0x1000) MX[B]
	[7] -1	0	0xf4007000 - 0xf4007fff (0x1000) MX[B]
	[8] -1	0	0xf4009000 - 0xf400900f (0x10) MX[B]
	[9] -1	0	0xf400a000 - 0xf400a00f (0x10) MX[B]
	[10] -1	0	0xf400b000 - 0xf400b00f (0x10) MX[B]
	[11] -1	0	0xf400c000 - 0xf400c1ff (0x200) MX[B]
	[12] -1	0	0xf4008000 - 0xf40083ff (0x400) MX[B]
	[13] -1	0	0xf7000000 - 0xf71fffff (0x200000) MX[B](B)
	[14] -1	0	0xfa000000 - 0xfbffffff (0x2000000) MX[B](B)
	[15] -1	0	0xf6000000 - 0xf600ffff (0x10000) MX[B](B)
	[16] -1	0	0xf8000000 - 0xf9ffffff (0x2000000) MX[B](B)
	[17] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[18] -1	0	0x00000000 - 0x00000000 (0x1) IX[B]
	[19] -1	0	0x00000800 - 0x000008ff (0x100) IX[B]
	[20] -1	0	0x00000900 - 0x000009ff (0x100) IX[B]
	[21] -1	0	0x00000a00 - 0x00000a0f (0x10) IX[B]
	[22] -1	0	0x00000b00 - 0x00000b00 (0x1) IX[B]
	[23] -1	0	0x00000d00 - 0x00000d00 (0x1) IX[B]
	[24] -1	0	0x00000e00 - 0x00000e00 (0x1) IX[B]
	[25] -1	0	0x00000f00 - 0x00000f00 (0x1) IX[B]
	[26] -1	0	0x00001000 - 0x0000107f (0x80) IX[B]
(II) ATI: ATI driver (version 6.5.5) for chipset: ati
(II) R128: Driver for ATI Rage 128 chipsets:
	ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP),
	ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP),
	ATI Rage 128 Pro GL PA (AGP?), ATI Rage 128 Pro GL PB (AGP?),
	ATI Rage 128 Pro GL PC (AGP?), ATI Rage 128 Pro GL PD (PCI),
	ATI Rage 128 Pro GL PE (AGP?), ATI Rage 128 Pro GL PF (AGP),
	ATI Rage 128 Pro VR PG (AGP?), ATI Rage 128 Pro VR PH (AGP?),
	ATI Rage 128 Pro VR PI (AGP?), ATI Rage 128 Pro VR PJ (AGP?),
	ATI Rage 128 Pro VR PK (AGP?), ATI Rage 128 Pro VR PL (AGP?),
	ATI Rage 128 Pro VR PM (AGP?), ATI Rage 128 Pro VR PN (AGP?),
	ATI Rage 128 Pro VR PO (AGP?), ATI Rage 128 Pro VR PP (PCI),
	ATI Rage 128 Pro VR PQ (AGP?), ATI Rage 128 Pro VR PR (PCI),
	ATI Rage 128 Pro VR PS (AGP?), ATI Rage 128 Pro VR PT (AGP?),
	ATI Rage 128 Pro VR PU (AGP?), ATI Rage 128 Pro VR PV (AGP?),
	ATI Rage 128 Pro VR PW (AGP?), ATI Rage 128 Pro VR PX (AGP?),
	ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP),
	ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI),
	ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (AGP?),
	ATI Rage 128 4X SF (AGP?), ATI Rage 128 4X SG (AGP?),
	ATI Rage 128 4X SH (AGP?), ATI Rage 128 4X SK (AGP?),
	ATI Rage 128 4X SL (AGP?), ATI Rage 128 4X SM (AGP),
	ATI Rage 128 4X SN (AGP?), ATI Rage 128 Pro ULTRA TF (AGP),
	ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP),
	ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?),
	ATI Rage 128 Pro ULTRA TU (AGP?)
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
	ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
	ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI),
	ATI Radeon Mobility M7 LW (AGP),
	ATI Mobility FireGL 7800 M7 LX (AGP),
	ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
	ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336,
	ATI Radeon IGP330/340/350 (A4) 4137,
	ATI Radeon IGP330M/340M/350M (U2) 4337,
	ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP 4437,
	ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
	ATI Radeon 9100 QM (AGP), ATI Radeon 8500 AIW BB (AGP),
	ATI Radeon 8500 AIW BC (AGP), ATI Radeon 7500 QW (AGP/PCI),
	ATI Radeon 7500 QX (AGP/PCI), ATI Radeon 9000/PRO If (AGP/PCI),
	ATI Radeon 9000 Ig (AGP/PCI), ATI FireGL Mobility 9000 (M9) Ld (AGP),
	ATI Radeon Mobility 9000 (M9) Lf (AGP),
	ATI Radeon Mobility 9000 (M9) Lg (AGP),
	ATI Radeon 9100 IGP (A5) 5834,
	ATI Radeon Mobility 9100 IGP (U3) 5835,
	ATI Radeon 9200PRO 5960 (AGP), ATI Radeon 9200 5961 (AGP),
	ATI Radeon 9200 5962 (AGP), ATI Radeon 9200SE 5964 (AGP),
	ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
	ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Radeon 9500 AD (AGP),
	ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
	ATI FireGL Z1 AG (AGP), ATI Radeon 9700 Pro ND (AGP),
	ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AGP),
	ATI FireGL X1 NG (AGP), ATI Radeon 9600 AP (AGP),
	ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
	ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP),
	ATI FireGL RV360 AV (AGP), ATI Radeon Mobility 9600 (M10) NP (AGP),
	ATI Radeon Mobility 9600 (M10) NQ (AGP),
	ATI Radeon Mobility 9600 (M11) NR (AGP),
	ATI Radeon Mobility 9600 (M10) NS (AGP),
	ATI FireGL Mobility T2 (M10) NT (AGP),
	ATI FireGL Mobility T2 (M11) NV (AGP), ATI Radeon 9800SE AH (AGP),
	ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
	ATI FireGL X2 AK (AGP), ATI Radeon 9800PRO NH (AGP),
	ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP),
	ATI Radeon 9800XT NJ (AGP)
(II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
	mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI, mgag400,
	mgag550
(II) GLINT: driver for 3Dlabs chipsets: gamma, gamma2, ti_pm2, ti_pm, r4,
	pm4, pm3, pm2v, pm2, pm, 300sx, 500tx, mx, delta
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
	Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
	Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
	GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
	GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
	Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
	GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
	GeForce4 420 Go 32M, GeForce4 460 Go, GeForce4 440 Go 64M,
	GeForce4 410 Go 16M, Quadro4 500 GoGL, Quadro4 550 XGL, Quadro4 NVS,
	GeForce4 MX 440 with AGP8X, GeForce4 MX 440SE with AGP8X,
	GeForce4 MX 420 with AGP8X, GeForce4 448 Go, GeForce4 488 Go,
	Quadro4 580 XGL, Quadro4 280 NVS, Quadro4 380 XGL,
	GeForce4 MX Integrated GPU, GeForce3, GeForce3 Ti 200,
	GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600, GeForce4 Ti 4400,
	0x0252, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
	Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
	GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
	Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
	GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
	GeForce FX 5600 Ultra, GeForce FX 5600, 0x0313, GeForce FX 5600SE,
	0x0316, 0x0317, GeForce FX Go5600, GeForce FX Go5650,
	Quadro FX Go700, 0x031D, 0x031E, 0x031F, GeForce FX 5200,
	GeForce FX 5200 Ultra, GeForce FX 5200, GeForce FX 5200SE,
	GeForce FX Go5200, GeForce FX Go5250, GeForce FX Go5200 32M/64M,
	0x0329, Quadro NVS 280 PCI, Quadro FX 500, GeForce FX Go5300,
	GeForce FX Go5100, 0x032F, GeForce FX 5900 Ultra, GeForce FX 5900,
	GeForce FX 5900XT, GeForce FX 5950 Ultra, 0x0334, Quadro FX 3000,
	GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
	GeForce FX 5700VE, 0x0345, GeForce FX Go5700, GeForce FX Go5700,
	0x0349, 0x034B, Quadro FX Go1000, Quadro FX 1100, 0x034F
(II) S3: driver (version 0.3.5 for S3 chipset: 964-0, 964-1, 968,
	Trio32/64, Aurora64V+, Trio64V2/DX or /GX
(II) S3VIRGE: driver (version 1.8.6) for S3 ViRGE chipsets: virge, 86C325,
	virge vx, 86C988, virge dx, virge gx, 86C375, 86C385, virge gx2,
	86C357, virge mx, 86C260, virge mx+, 86C280, trio 3d, 86C365,
	trio 3d/2x, 86C362, 86C368
(II) SIS: driver for SiS chipsets: SIS5597/5598, SIS530/620,
	SIS6326/AGP/DVD, SIS300/305, SIS630/730, SIS540, SIS315, SIS315H,
	SIS315PRO, SIS550, SIS650/M650/651/740, SIS330(Xabre),
	SIS660/661FX/M661FX/M661MX/741/741GX/M741/760/M760, SIS340
(II) SAVAGE: driver (version 1.1.27t) for S3 Savage chipsets: Savage4,
	Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX,
	Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133,
	ProSavage PN133, ProSavage KN133, SuperSavage/MX 128,
	SuperSavage/MX 64, SuperSavage/MX 64C, SuperSavage/IX 128,
	SuperSavage/IX 128, SuperSavage/IX 64, SuperSavage/IX 64,
	SuperSavage/IXC 64, SuperSavage/IXC 64, ProSavage DDR,
	ProSavage DDR-K
(II) TRIDENT: driver for Trident chipsets: tvga9000, tvga9000i, tvga8900c,
	tvga8900d, tvga9200cxr, tgui9400cxi, cyber9320, cyber9388, cyber9397,
	cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4, tgui9420dgi,
	tgui9440agi, tgui9660, tgui9680, providia9682, providia9685,
	cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d, cyberbladei7,
	cyberbladei7d, cyberbladei1, cyberbladei1d, cyberbladeAi1,
	cyberbladeAi1d, bladeXP, cyberbladeXPAi1
(II) CHIPS: Driver for Chips and Technologies chipsets: ct65520, ct65525,
	ct65530, ct65535, ct65540, ct65545, ct65546, ct65548, ct65550,
	ct65554, ct65555, ct68554, ct69000, ct69030, ct64200, ct64300
(II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee,
	3dfx Voodoo3, 3dfx Voodoo5
(II) FBDEV: driver for framebuffer: fbdev
(II) VGA: Generic VGA driver (version 4.0) for chipsets: generic
(II) v4l driver for Video4Linux
(II) Primary Device is: (II) FBDEV(0): using default device 
(II) Running in FRAMEBUFFER Mode
(**) FBDEV(0): Depth 24, (--) framebuffer bpp 32
(==) FBDEV(0): RGB weight 888
(==) FBDEV(0): Default visual is TrueColor
(==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) FBDEV(0): Hardware:  (vidmem: 16384k)
(II) FBDEV(0): Checking Modes against framebuffer device...
(II) FBDEV(0): 	mode "800x600" ok
(II) FBDEV(0): 	mode "640x480" ok
(II) FBDEV(0): Checking Modes against monitor...
(--) FBDEV(0): Virtual size is 800x600 (pitch 800)
(**) FBDEV(0):  Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
(II) FBDEV(0): Modeline "800x600"   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync
(**) FBDEV(0):  Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
(II) FBDEV(0): Modeline "640x480"   25.20  640 656 752 800  480 490 492 525 -hsync -vsync
(++) FBDEV(0): DPI set to (100, 100)
(**) FBDEV(0): Using "Shadow Framebuffer"
(--) Depth 24 pixmap format is 32 bpp
(EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument
(EE) FBDEV(0): Mode init failed

Fatal server error:
AddScreen/ScreenInit failed for driver 0


When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to submit@bugs.debian.org.

--- End Message ---
--- Begin Message --- 
On Fri, Dec 17, 2004 at 03:54:22PM +0000, Dr Gavin Seddon wrote:
> > Typically the resolution or color depth don't exactly match
> > what STI is reporting at boot time. Use "fbset -i" to determine
> > those parameters. This email might help you:
> > 	http://lists.parisc-linux.org/pipermail/parisc-linux/2003-January/019040.html

Yeah - you want to read the above email and adjust the XF86Config-4 file.

I've also updated the graphics FAQ:
	http://www.parisc-linux.org/faq/graphics-howto.html

grant

--- End Message ---
--- Begin Message --- on my system I had to reboot to make it work. well for the moment the Xserver does not crash but the mouse is not mapped... 


Name : stifb   is the difference.

my kernel is 2.6.8-1-32  (unstable)


# fbset -i

mode "1280x1024"
    geometry 1280 1024 1280 1024 8
    timings 0 0 0 0 0 0 0
    rgba 8/0,8/0,8/0,0/0
endmode

Frame buffer device information:
    Name        : stifb
    Address     : 0xf9000000
    Size        : 2097152
    Type        : PACKED PIXELS
    Visual      : PSEUDOCOLOR
    XPanStep    : 0
    YPanStep    : 0
    YWrapStep   : 0
    LineLength  : 2048
    MMIO Address: 0xf8100000
    MMIO Size   : 4194304
    Accelerator : No

have a good week-end
Pierrick


Dr Gavin Seddon a écrit :

On Fri, 2004-12-17 at 15:53, Pierrick HERVE wrote:


Hi,

> (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument
> (EE) FBDEV(0): Mode init failed

do you have the fbset product installed ?

# fbset -i
?

not sure we can find a lot of info on www.google.com/linux
but i don't know axectly the problem.

I have quitly the same problem on one of my system.
not exactly the same FBIOPUT_ error... i am stiil looking for the solution.

best regards,
Pierrick



Hi,
Attached is a script of the output:

Cheers.
GS



------------------------------------------------------------------------

Script started on Fri 17 Dec 2004 17:38:22 GMT
samson:~# fbset -i

mode "1024x768"
    geometry 1024 768 1024 768 8
    timings 0 0 0 0 0 0 0
    rgba 8/0,8/0,8/0,0/0
endmode

Frame buffer device information:
Name : Address : 0xf9000000 
    Size        : 16777216
    Type        : PACKED PIXELS
    Visual      : PSEUDOCOLOR
    XPanStep    : 0
    YPanStep    : 0
    YWrapStep   : 0
    LineLength  : 2048
    MMIO Address: 0xf8100000
    MMIO Size   : 4194304
    Accelerator : No
samson:~# Script done on Fri 17 Dec 2004 17:38:41 GMT

--- End Message ---
--- Begin Message --- 
On Sat, Dec 18, 2004 at 04:24:34PM +0000, Dr Gavin Seddon wrote:
> > 	http://www.parisc-linux.org/faq/graphics-howto.html
>
> I did as instructed.  After my penguin on boot I see 'stifb:unsupported
> gfx card'

Did you have two gfx cards installed?
If you only have one then like the driver says, it's not supported.
I thought the penguin on boot was an indicator the card was supported.

>  and when I startx I get 'AddScreen/ScreenInit failed for
> driver 0'.  Need I alter XF86Config-4 to a different monitor?  At the
> moment it is set to 'generic'.

The Section "Screen" will reference a "Device". The corresponding
Section "Device" should be where one indicates which device one meant.
I've never tried to to setup multiple cards and don't know what
card specifier looks like. I suppose it's either a /dev name or
a PCI device (same format as lspci provides).

Anyone else help with this?

thanks,
grant

--- End Message ---
Reply to: