From: "Per Øyvind Karlsen" <pkarlsen@mandriva.com>
To: sparclinux@vger.kernel.org
Subject: Re: Problems booting 2.6.18 on SunBlade 100/150
Date: Thu, 19 Oct 2006 11:18:56 +0000 [thread overview]
Message-ID: <200610191318.57642.pkarlsen@mandriva.com> (raw)
In-Reply-To: <200401070729.56891.pkarlsen@mandriva.com>
Torsdag 19 oktober 2006 13:07, skrev Jim Watson:
> On 07/01/2004, at 5:29 PM, Per Øyvind Karlsen wrote:
> > 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)
>
> Hi Per,
>
> i am puzzled too - lets wait and see if anyone provides some
> explanation...
>
> There are two issues here:
>
> (a) i chose to use the debian config file to build a kernel that will
> run - the explanation is that I have no idea what to configure, but
> the debian config is known to work
>
> (b) the kernel that I did build that way, will not run, unless I boot
> with video:atyfb=off
>
> This is on a sunblade100, it may be different on other sparc...you
> need to report what you are using
>
> regrads
>
> jim
Yes, but what I was wondering about is if you got any display at all or were
relying on serial console or something? Is it possible to have display
without framebuffer?
My config etc. were working fine with 2.6.17-rc3, don't know when the atyfb
breakage occured, but in 2.6.17 it was broken...
--
Regards,
Per Øyvind Karlsen
Mandriva
next prev parent reply other threads:[~2006-10-19 11:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 6:29 Problems booting 2.6.18 on SunBlade 100/150 Per Øyvind Karlsen
2006-10-09 2:29 ` 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 [this message]
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=200610191318.57642.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.