[parisc-linux] Re: Boot problem with HPPA 735/125 w/ A1439A CRX

[kurtm22 at netscape.net]

 Hi Helge,

I did what you suggested and built a new kernel from scratch using the 2.6.22
source tar.? I did not comment out the fb_memset() call in stifb.c
prior to the build so I could post the crash results - perhaps
it will provide more insight to what is going on:

sticon: Initializing sti text console
Console: switching to colour STI console 160x64
Backtrace:
??? [<1044e1b0>] stifb_init_fb+0x67c/0x928
??? [<1044e4c4>] stifb_init+0x68/0xf8
??? ? [<1043d4187>] kernel_init+0xfc/0x2c8
??? [<10109c5c>] ret_from_kernel_thread+0x1c/0x24

kernel fault:? code=15? regs=10984200? (addr=f9000000)

.
.
.
.

I can post more of the dump if you need it.? I left the machine 
sitting there as i am writing down what I see on the screen.

--Kurt



 

-----Original Message-----
From: Helge Deller <deller at gmx.de>
To: kurtm22 at netscape.net
Cc: parisc-linux at lists.parisc-linux.org
Sent: Tue, 17 Jul 2007 5:03 pm
Subject: Re: Boot problem with HPPA 735/125 w/ A1439A CRX










Hi Kurt,
CC: parisc-kernel development list

On Tuesday 17 July 2007, kurtm22 at netscape.net wrote:
> You seem to be the maintainer for the stifb.c code for the Debian port
> to hppa. I have a 735/125 w/ 520MB mem and A1439A graphics.

The A1439A seems to be a "CRX24 = CRX+ (24-plane color)" graphics card acording 
to include/asm/grfioctl.h linux kernel header source file.

> I have been unable to boot the 2.6.18-4-parisc and 2.6.8-4-32 kernels.
> Before the system panics, 

Your problem looks similiar to this thread:
http://lists.parisc-linux.org/pipermail/parisc-linux/2004-September/024834.html
(or search for CRX on: http://lists.parisc-linux.org/pipermail/parisc-linux/2004-September/thread.html#24834)
What's the panic message / register dump ?

> there appears to be a line that says "switching to  
> STI color mode (I think).? 

What does it say exactly ?
There are two different strings which can be printed:
a) Console: switching to colour STI console 128x48
b) Console: switching to colour frame buffer device 128x48

The first (a) means it switches to text-only console (sticon), the second (b) is 
printed if the kernel switches to framebuffer mode (stifb).
Only the second one provides /dev/fb0 support and will allow you to use the X 
server.

> So what I am thinking is that there is something 
> up with accessing the hardware through the framebuffer.? 

Yes, might be.
You might want to try a more recent kernel (e.g. build yourself the original 
2.6.22 kernel from kernel.org sources, it should build cleanly on hppa and no 
additional patches are needed).
Looking at the sources, it might be that the fb_memset() call in the function 
rattlerSetupPlanes()  [file: drivers/video/stifb.c] is wrong.
I sadly don't have the hardware to test, but if you compile a kernel, try to 
just delete this fb_memset() call. At least maybe it then maybe doesn't panic 
any more?

Sadly I don't have such a card myself to test.
Anyone wants to send me one ? :-)

> The system has been dist-upgraded to etch from sarge which
> may be why I can boot the 2.4.17-32 kernel but I cannot get X to start:
> -------------------------------------
> X Window System Version 7.1.1
> Release Date: 12 May 2006
> X Protocol Version 11, Revision 0, Release 7.1.1
> Build Operating System: UNKNOWN
> Current Operating System: Linux boss-429 2.4.17-32 #1 Sat Mar 16 17:09:00 MST 
2002 parisc
> Build Date: 03 April 2007
> ??????? Before reporting problems, check http://wiki.x.org
> ??????? to make sure that you have the latest version.
> Module Loader present
> 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/Xorg.0.log", Time: Tue Jul 17 15:44:00 2007
> (==) Using config file: "/etc/X11/xorg.conf"
> (EE) open /dev/fb0: No such device
> (EE) No devices detected.

Read above.
Probably sticon (which does not provide graphics mode) is active.

> This is what the device file looks like:
> /dev/fb0 = crw-rw---- 1 root video 29, 0 Oct? 3? 1999 /dev/fb0

That's ok.

Helge



 


________________________________________________________________________
Check Out the new free AIM(R) Mail -- Unlimited storage and industry-leading spam and email virus protection.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.parisc-linux.org/pipermail/parisc-linux/attachments/20070725/1fcf04c9/attachment.html