View previous topic :: View next topic |
Author |
Message |
theghost1990 n00b
Joined: 20 Feb 2008 Posts: 12
|
Posted: Fri Mar 07, 2008 1:31 pm Post subject: HPPA: stifb: 'A1262A' (id: 0x35acda30) not supported |
|
|
hi,
i've have problems with my HP C3700 and Xorg and other parts....
My 1st problem is this part of output from dmesg:
STI GSC/PCI core graphics driver Version 0.9a
STI PCI graphic ROM found at f7000000 (2048 kB), fb at fa000000 (32 MB)
id 35acda30-9a02587, conforms to spec rev. 8.0d
graphics card name: A1262A
sticon: Initializing STI text console.
Console: switching to colour STI console 128x48
stifb: 'A1262A' (id: 0x35acda30) not supported.
Generic RTC Driver v1.07
this card hasn't a support from the Frambufferdriver but i need the Framebuffer for Xorg.....
an the other Porblem is b0 i have this message:
INIT: id "b0" respawning too fast: disabled for 5 minuntes |
|
Back to top |
|
|
ddc Guru
Joined: 29 Aug 2006 Posts: 522
|
Posted: Fri Mar 07, 2008 7:41 pm Post subject: |
|
|
the STI with X ? we want too
but the only solution is to add a matrox or a voodoo2/3 video board
trust me, it is the best solution, they work great with X |
|
Back to top |
|
|
bombsquad n00b
Joined: 28 Aug 2007 Posts: 12 Location: Coventry, United Kingdom
|
Posted: Wed Jun 11, 2008 1:29 pm Post subject: |
|
|
Alternate video cards are a good plan. The one you have got in there at present is probably an older fx board - I have an fx4 and that isn't supported either, but my _really_ old crappy 24bit framebuffer card does work - it's just slow.
As for the b0 thing: this is related to the various places you can have your console on PA-RISC machines.
The best one would be the STI framebuffer (stifb) which as you can see is not supported on your machine hence the first error message.
There's the STI text console (sticon) which works on more cards and seems to be alright for your machine; probably the one you see on your display =)
Finally there is the 'PDC software console' or a serial console.
The tty device for the PDC console is /dev/ttyB0 and the entry in /etc/inittab that describes it is called 'b0' - it would appear that init can't start a login prompt on your ttyB0, which probably means it isn't built-in to your kernel or the device node is missing from /dev - so it fails, constantly, and then init gets pissed off and stops restarting it for a while. Commenting out the line starting with b0 in /etc/inittab should be fine for you. |
|
Back to top |
|
|
|