This laptop has 1GiB RAM and at BIOS setup I can choose how much of this
1GB I want to give to the video card.
I was giving 128MB.
Tried adding vmalloc=268435456 to the second last line (before quitet
splash) of the boot options. Is it the right place to add it?
Tried adding ... to a new line be
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
I tested with 2.6.33 no acceleration and freezed the same way
--
Lucid Beta 1 installation CD gives blank screen and freezes
https://bugs.launchpad.net/bugs/539020
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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.
> Does it work? (or in what way does it not work)
No. They all halt the in apparently the same way.
> What's the kernel version you're trying?
2.6.32 from Ubuntu Lucid repositories
A patched version of it (v2 by Leann Ogasawara, see the post 38 on LP539020)
i386 files from http://kernel.ubuntu.c
I tested with Lucid.
Without blacklisting viafb it halts the same way:
2.6.32-19
2.6.32-19 (v2)
2.6.34-rc3-lucid/
I added video=viafb:off to the second last line of booting before the
"quiet splash" and it didn't work either.
However the latter was not completely installed:
leoro...@leorolla-la
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
With Karmic, neither one worked:
2.6.32-19
2.6.32-19 (v1)
2.6.32-19 (v2)
They all halt during boot, preety much the same way as with Lucid CD and
2.6.32-16
I will try to test with a Lucid install today. Will also try
2.6.34-rc3-karmic/
--
Lucid Beta 1 installation CD gives blank screen and free
Thanks.
I will try to do these tests as soon as possible.
Normally I wouldn't be able to use this laptop for long periods in the
next couple of days.
I should certainly test it with Karmic.
Will try to install Lucid to an HD partition too, but I don't know if
I will make it. Can also try first
Hi Leo,
So I've made two test kernels. I'd appreciate your feedback on both.
If you'd be able to test these kernels within a Lucid install that'd be
even better.
The first test kernel only has the first patch applied which Florian
suggested might resolve the issue you are facing:
http
Hi Leo,
I've spoken with Florian and I'll build a test kernel with the patches
he's pointed out backported. Please stay tuned.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assig
Thanks for the feedback.
For Ubuntu bugtrack I guess that these patches on the git tree mean that
this is a confirmed bug.
For the linux kernel, I could help testing.
Installing the .deb from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc3-karmic/ is enough?
How do I provide you with
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
1. Lucid kernel (2.6.32-18) on a Karmic install.
I have blacklisted viafb and now it boots and opens gdm.
Without blacklisting viafb it freezes with intense processor and HD activity.
2. Lucid Beta 1 (2.6.32-16) Live Session
I have blacklisted viafb (on another computer, with persistent filesyst
Please, see my post 25 above.
It may be the viafb module in the 2.6.32 kernel
--
Lucid Beta 1 installation CD gives blank screen and freezes
https://bugs.launchpad.net/bugs/539020
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
It's even less likely to be xsplash than Colin suggests, because Lucid
does not have xsplash enabled currently. So that should reduce the
likelihood to about 0. :)
--
Lucid Beta 1 installation CD gives blank screen and freezes
https://bugs.launchpad.net/bugs/539020
You received this bug notifica
Firstly, projects are for use once a bug has been identified by a
developer and is being passed upstream. They are not for use for users
reporting bugs against a distribution, unless those users are explicitly
testing upstream code. That's the difference between "Also affects
project" and "Also a
Hi!
Thanks for helping.
When I disable splash I get the same problem. In my case I suspect the
problem is related to the viafb module that is present on kernel 2.6.32
but not on 2.6.31.
If you can boot disabling splash, I guess your problem is different.
In this case you should file a different
I've been experiencing this bug also with the release beta, and the past
3 daily builds.
It seems that the only place that this bug can originate from is
xsplash, so can I ask why this is not tied to that project? I saw there
was discussion about the inappropriate 'affects', but surely when the
pr
** Description changed:
- I tried to enter the Live session "Try Ubuntu without installing" from a
- live USB.
-
- The screen goes black, the cooler turns on indefinitely (suggesting
- strong cpu activity), and the keyboar locks (I can't turn on/off
- capslock or numlock).
-
+ I tried to enter t
fixed the release tag that I mistakenly put to karmic instead of lucid.
~JFo
** Tags added: lucid
** Tags removed: karmic
--
Lucid Beta 1 installation CD gives blank screen and freezes
https://bugs.launchpad.net/bugs/539020
You received this bug notification because you are a member of Ubuntu
B
Exactly same problems with the Beta 1 release.
Nomodeset doesn't help.
Is it possible to recover log information from the persistent memory
file?
** Summary changed:
- Lucid Alpha 3 installation CD gives blank screen and freezes
+ Lucid Beta 1 installation CD gives blank screen and freezes
**
25 matches
Mail list logo
