From: "Per Øyvind Karlsen" <pkarlsen@mandriva.com>
To: sparclinux@vger.kernel.org
Subject: Re: Problems booting 2.6.18 on SunBlade 100/150
Date: Wed, 07 Jan 2004 06:29:56 +0000 [thread overview]
Message-ID: <200401070729.56891.pkarlsen@mandriva.com> (raw)
Torsdag 19 oktober 2006 08:38, skrev Jim Watson:
> On 19/10/2006, at 5:30 AM, David Miller wrote:
> > Are you sure you're enabling ATYFB video support in your kernel?
> > That's a common error when folks build their own kernels.
>
> Success! I used the later patch [0] and the config file from debian
> 2.6.18-1-sparc64 as mentioned by Jurij[1]
> which includes - hopefully relevant ;)
>
> CONFIG_FB_ATY128=y
> CONFIG_FB_ATY=y
> CONFIG_FB_ATY_CT=y
> # CONFIG_FB_ATY_GENERIC_LCD is not set
> CONFIG_FB_ATY_GX=y
>
> Using LCD Benq FP767 here,
>
> I could only get it it to boot this way:
>
> boot:mylinux18 video=atyfb:off
>
> which is what I need as it also gets rid of those pesky red dots ;)
>
> I am happy to report anything else that might assist...
>
> thanks to David for the patches and thanks to Jurij for guidance,
>
> jim
>
> [0] http://marc.theaimsgroup.com/?l=linux-sparc&m\x116120447318793&w=2
> [1] http://marc.theaimsgroup.com/?l=linux-sparc&m\x116120045100433&w=2
> -
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I'm left puzzled here now, will your display work correctly when disabling
framebuffer with 'video=atyfb:off'? And if you're disabling it, why do you
need to compile support for it?
My experience is that I need atyfb properly working to intialize display,
otherwise it'll boot with not display (openboot screen will stay and no linux
output is displayed, while machine is actually booting and serial can be
used).
Am I missing something here..? (I'm fairly new to sparc, so please have
patience:o)
--
Regards,
Per Øyvind Karlsen
Mandriva
next reply other threads:[~2004-01-07 6:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 6:29 Per Øyvind Karlsen [this message]
2006-10-09 2:29 ` Problems booting 2.6.18 on SunBlade 100/150 Jurij Smakov
2006-10-09 8:21 ` David Miller
2006-10-14 18:49 ` Jurij Smakov
2006-10-15 4:57 ` Jim Watson
2006-10-17 8:17 ` David Miller
2006-10-18 1:56 ` David Miller
2006-10-18 11:50 ` Jim Watson
2006-10-18 12:38 ` Jason Wever
2006-10-18 19:30 ` David Miller
2006-10-18 19:31 ` David Miller
2006-10-18 19:36 ` Per Øyvind Karlsen
2006-10-18 19:38 ` Jurij Smakov
2006-10-18 19:45 ` David Miller
2006-10-18 19:45 ` David Miller
2006-10-18 20:15 ` Per Øyvind Karlsen
2006-10-18 20:28 ` Per Øyvind Karlsen
2006-10-18 20:36 ` David Miller
2006-10-18 20:37 ` David Miller
2006-10-18 20:41 ` Per Øyvind Karlsen
2006-10-18 20:45 ` David Miller
2006-10-19 6:38 ` Jim Watson
2006-10-19 11:18 ` Per Øyvind Karlsen
2006-10-19 11:34 ` Jim Watson
2006-10-19 16:40 ` Jurij Smakov
2006-10-19 23:21 ` Riccardo Tortorici
2006-10-19 23:43 ` Jim Watson
2006-10-20 0:36 ` Riccardo Tortorici
2006-10-20 1:34 ` Jim Watson
2006-10-24 1:19 ` Jason Wever
2006-10-24 23:31 ` Per Øyvind Karlsen
2006-10-24 23:32 ` David Miller
2006-10-24 23:44 ` David Miller
2006-10-25 0:11 ` Per Øyvind Karlsen
2006-10-25 15:23 ` Per Øyvind Karlsen
2006-10-25 20:08 ` Per Øyvind Karlsen
2006-10-26 9:25 ` David Miller
2006-10-26 11:09 ` Per Øyvind Karlsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401070729.56891.pkarlsen@mandriva.com \
--to=pkarlsen@mandriva.com \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.