This does not sound like the issue discussed here. As far as I
understand Ubuntu blacklisted viafb and therefore no issues you
currently experience can be related to it. Your issue sounds like you
can at least figure out where characters are. It would be interesting
whether anything is shown correc
Leo adding vmalloc=268435456 to the line with "quite splash" was what I wanted,
thanks. But your syslog missed any reference to viafb even the startup message
(probably it didn't get written to disk prior to freeze) so I didn't see
anything in there.
Anyway by using the fact that
- the very same
No, the upstream changes in viafb won't help the problem you are experiencing
and it is unknown whether viafb and/or openchrome (which should not rely on the
output configuration to be correct) will ever be fixed as this would require an
amount of documentation that is not yet released by VIA, e
Thanks. It's odd to hear that it breaks totally for you but works for another
with the same IGP. I'm nearing despair. However I just found something
suspicious in the syslog you attached:
[ 32.198735] VIA Graphics Intergration Chipset framebuffer 2.4 initializing
[ 32.255733] __ratelimit: 3 c
Hi Leo,
thanks a lot for your work. So this
1. seems to be a completly new issue that was not known before
2. there is not even a way (to my knowledge) to prevent this as the boot
options don't get propagated until module load time
so blacklisting it for the release looks like the best option.
I fully agree that we shouldn't welcome a new user (or any user) with a
non-booting linux.
Upstream
Well I don't need that much info at all:
Does it work? (or in what way does it not work)
If yes, are there any remaining issues?
What's the kernel version you're trying?
What module/boot parameters
If you want something that helps during boot try (not sure whether it works,
but might worth a try)
video=viafb:off
or (if it's just a hardware acceleration problem)
video=viafb:viafb_accel=0
Blacklisting, well I could live with it as it still allows to use viafb
if wanted (so better than what Fe
Hi,
perhaps I should have added that my main objective is to fix the freeze. That
viafb sometimes requires a bunch of parameters for correct operation as
described in viafb.txt is a known issue I'm trying to fix on the long term (but
that proves quite difficult without much support from VIA)
I
That's bad, I really thought it would work.
Well if everything fails could you please also try the latest kernel you
suggested last time
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc3-karmic/
This would at last reveal whether this is a known/fixed bug or a completly new
one.
--
Lucid
I'm wondering why video=viafb makes a difference for you as normally this gets
autoloaded or doesn't react at all.
Does it work correctly if you add something like this instead?
video=viafb:viafb_active_dev=DVI,viafb_mode=800x480
Yeah, it might sound odd that its called 'DVI' but the whole output
Just a word from the viafb maintainer:
This sounds like a known problem, fixed by
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=97922b5462fa543484831d42ab0fe4562b9373fc
(or alternatively by disabling hardware acceleration in viafb via the module
parameter viafb_ac
This happens as VGA is not the output connected to your hardware. You'll likely
see the correct screen if you plug in a monitor to the VGA port of the netbook.
viafb will work if you give it the options (as explained in viafb.txt)
viafb_active_dev=DVI viafb_mode=800x480
I don't know how to fix the
12 matches
Mail list logo
