public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: n00bsys0p <n00b@n00bsys0p.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Possible bug in via-velocity on 3.0+
Date: Tue, 18 Oct 2011 17:01:19 +0100	[thread overview]
Message-ID: <j7k7sf$vbf$1@dough.gmane.org> (raw)

Hi,

I've been trying to get a custom 3.0 kernel to boot via PXE on a VIA 
EPIA EN15000G, and have run into a problem where once the thin client 
starts to load the kernel, the entire screen turns into a mosaic of 
random colours and characters.

I've tested this serving a 2.6.35.8 kernel (configured identically to 
the 3.0) to the thin client where the master and client are both fitted 
with EPIA EN1500G, and it works perfectly. Also, I tried swapping the 
master's motherboard to a Gigabyte GA-D525TUD (Realtek LAN chip), and it 
succeeded in serving the 3.0 kernel to an EN15000G without a fault.

In all test cases, the master was using a 3.0 kernel.

Through this testing, I surmise that it is something to do with the LAN 
driver which is used, as this is the only thing I can see to have 
changed between the two running systems. Could it be accidentally 
overwriting the video RAM or something along those lines?

Here's a link to a photo of what the screen looks like when it goes 
wrong: 
https://lh3.googleusercontent.com/-sXFP41oaF9U/TpyMFg89CqI/AAAAAAAAA-I/PBrltIm0cB4/s720/PXEFail.jpg

Anyway, hope there's someone here who knows what might be happening here!

Alex


             reply	other threads:[~2011-10-18 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 16:01 n00bsys0p [this message]
2011-10-18 16:15 ` Possible bug in via-velocity on 3.0+ Bjorn Helgaas
2011-10-19 10:14   ` n00b
2011-10-19 15:14     ` Bjorn Helgaas
2011-10-19 15:47       ` n00b
2011-10-26 18:32         ` Bjorn Helgaas
2011-10-26 21:51           ` n00b

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='j7k7sf$vbf$1@dough.gmane.org' \
    --to=n00b@n00bsys0p.co.uk \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox