bterm vs. creator 3d
It appears there may be kernel bugs causing bterm problems.
- Forwarded message from Daniel Jacobowitz [EMAIL PROTECTED] -
Date: Sun, 25 Apr 2004 10:21:00 -0400
From: Daniel Jacobowitz [EMAIL PROTECTED]
To: Blars Blarson [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#245620: A little patch to help debug
On Sat, Apr 24, 2004 at 11:26:26PM -0700, Blars Blarson wrote:
(gdb) print fb_fix
$1 = {id = Creator 3D\000\000\000\000\000, smem_start = 0,
smem_len = 1310720, type = 0, type_aux = 0, visual = 2, xpanstep = 0,
ypanstep = 0, ywrapstep = 0, line_length = 8192, mmio_start = 0,
mmio_len = 0, accel = 11, reserved = {0, 0, 0}}
(gdb) print fb_var
$2 = {xres = 1152, yres = 864, xres_virtual = 1280, yres_virtual = 1024,
xoffset = 0, yoffset = 0, bits_per_pixel = 32, grayscale = 0, red = {
offset = 0, length = 8, msb_right = 0}, green = {offset = 8, length = 8,
msb_right = 0}, blue = {offset = 16, length = 8, msb_right = 0}, transp =
{
offset = 0, length = 0, msb_right = 0}, nonstd = 0, activate = 0,
height = 4294967295, width = 4294967295, accel_flags = 1, pixclock = 1,
left_margin = 0, right_margin = 0, upper_margin = 0, lower_margin = 0,
hsync_len = 0, vsync_len = 0, sync = 0, vmode = 0, rotate = 0, reserved = {
0, 0, 0, 0, 0}}
(gdb) print bogl_frame_len
$3 = 1310720
xres_virtual = 1280
yres_virtual = 1024
bits_per_pixel = 32
Minimum memory you need for such a framebuffer is 1280 * 1024 * 4 =
5242880 bytes.
smem_len = 1310720
line_length = 8192
With that line length you'd need 8192 * 1024 = 8388608 (8MB).
So why does smem_len == 1024 * 1280? I think your kernel is lying.
Looking at the 2.6 Creator3D driver, I don't see where it initializes
smem_len. I can't see how xres_virtual and yres_virtual get larger
than xres/yres either.
Oh, you're using 2.4, let me look at the 2.4 driver. I see how you get
margins now. And it says:
type-fb_depth = depth = (fbtype == FBTYPE_SUN2BW) ? 1 : 8;
i.e. the 2.4 driver does not appear to support 32 bit. That's in
sbusfb.c, which then calls an init function in creatorfb.c, which
changes the depth to 24 and the bpp to 32 - but smem_len is never
changed. Thus the mapping is too small.
I don't think this bug has anything to do with bogl. Have you tried
any other framebuffer graphics application on this kernel? Excluding
X, which tends to ignore the kernel's information anyway.
Maybe debian-sparc knows more.
It fills a block with red left to right accross the top of the screen
for the first several calls of bogl_tcfb_text until xx exceeds 320
where it is off of the screen. It loops back again and the red gets
brighter. The red on the left third of the screen is brighter than
the right, and it's bombing out before the screen is half full of red.
The (white) text that was on the screen when it started stays on.
This certainly sounds like something is lying about the framebuffer
parameters.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
- End forwarded message -
--
Blars Blarson [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
[newbie] Install/Boot problem
Hi All, I have installed woody via 'net boot'. All went well, but I can't boot from the hard disk. System: SPARCstation 20 32Mb RAM No floopy or CDROM drive Issues that make me suspicious include: o I used the 's' parameter in fdisk to partition this disk. This gave me: sda1 / sda2 swap sda3 Whole Disk o SILO refused to install. o I don't know very much about OpenBOOT or SPARCstations. All suggestions welcome ;-) Everard
Bug#245620: ok, but..
Is the bug really that we don't change smem_len? AFAICS, most other fb drivers don't change fix-smem_len at all. I'm relatively new to framebuffer code in general, so any clue will be appreciated. I considered replicating the stuff that changes fb_size and smem_len in sbusfb.c in creatorfb.c but that doesn't sound quite right (although it might work.) Also I don't happen to have a Creator3d card, much less an actual Ultra machine (will change soon) so I'm stabbing in the dark here. -- Joshua Kwan signature.asc Description: Digital signature
Re: [newbie] Install/Boot problem
On Sunday 25 April 2004 16:37, Everard Brown wrote: Hi All, I have installed woody via 'net boot'. All went well, but I can't boot from the hard disk. System: SPARCstation 20 32Mb RAM No floopy or CDROM drive Issues that make me suspicious include: o I used the 's' parameter in fdisk to partition this disk. This gave me: sda1 / sda2 swap sda3 Whole Disk o SILO refused to install. sda1 (the partition containing /boot) probably extends past the first 1GB of disk space. On SparcStation 20s, the partition that contains /boot must completely reside in the first 1GB of disk space (due to OpenBOOT bugs/restrictions) Pat -- Purdue University ITAP/RCS--- http://www.itap.purdue.edu/rcs/ The Computer Refuge --- http://computer-refuge.org
Re: [newbie] Install/Boot problem
Hi Pat,
Thanks for the quick reply ;-)
On Monday 26 Apr 2004 12:05 am, Patrick Finnegan wrote:
On Sunday 25 April 2004 16:37, Everard Brown wrote:
Hi All,
I have installed woody via 'net boot'. All went well, but I can't
boot from the hard disk.
System: SPARCstation 20
32Mb RAM
No floopy or CDROM drive
Issues that make me suspicious include:
o I used the 's' parameter in fdisk to partition this disk. This gave
me: sda1 /
sda2 swap
sda3 Whole Disk
o SILO refused to install.
sda1 (the partition containing /boot) probably extends past the first
1GB of disk space. On SparcStation 20s, the partition that
contains /boot must completely reside in the first 1GB of disk space
(due to OpenBOOT bugs/restrictions)
That sounds a very likely cause of my problem, but when I try to create the
Sun disk label ('s' option in fdisk) that is always the default.
Can anyone suggest how I might acheive a partitioning scheme which would be
acceptable to the install program?
I already tried to split the space allocated to sda1, but I couldn't get the
unused part of the partition back.
I'll have a more detailed look at the fdisk options...
All suggestions are still very welcome.
Everard
2.6.x kernel for Sparc?
I didn't see this in apt... Is there a 2.6.x kernel image available for Sparc (I have a Sparc 5). Thanks Eric
Re: [newbie] Install/Boot problem
On Sunday 25 April 2004 18:39, Everard Brown wrote:
That sounds a very likely cause of my problem, but when I try to
create the Sun disk label ('s' option in fdisk) that is always the
default.
Can anyone suggest how I might acheive a partitioning scheme which
would be acceptable to the install program?
Use d to delete sda1 and sda2, and then use n to create new ones.
Make sure you use t to change the type of the swap partition to type
82 (Linux Swap).
I already tried to split the space allocated to sda1, but I couldn't
get the unused part of the partition back.
I'll have a more detailed look at the fdisk options...
m gets you a list of commands in fdisk.
Pat
--
Purdue University ITAP/RCS--- http://www.itap.purdue.edu/rcs/
The Computer Refuge --- http://computer-refuge.org
Re: 2.6.x kernel for Sparc?
On Sun, Apr 25, 2004 at 08:23:39PM -0400, Eric Nichols wrote: I didn't see this in apt... Is there a 2.6.x kernel image available for Sparc (I have a Sparc 5). Right now 2.6.x on sparc32 is a shot in the dark. Things are coming along, but don't expect too much. Someone may have deb's available independently. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/
