[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/518623
Ti
Robert Moerland, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/
update:
In mavreick beta, there is no bug. I have removed viafb from the blacklist.
Splash screen at boot and shutdown/restart are also working.
Not sure if some earlier update to lucid had already fixed it.
--
[KM400] Black screen after boot, no text console possible
https://bugs.launchpad.net
There is the same issue on a desktop computer with "VIA Technologies.
CN896/VN896/P4M900 [Chrome 9 HC]"...
9.10 -> 10.4 upgrage (lucid lynx with kernel 2.6.32-22) has been done, and
after grub computer freezes...
No CLI by Ctrl-Alt-F1/F2/F?..
No GDM (GNOME/LXDE)...
Just reboot by Ctrl-Alt-Del.
My vga16fb problem may be the same one from bug 538893 comment #1, at
least in that the garbage I see in text mode seems to be influenced by
what was on the screen in X. And yes, that's a different bug.
Blacklisting vga16fb is not necessary as long as X works: I get a brief
period of garbage betwee
With the workaround from comment #37 (blacklisting viafb), my boot
process completes without freezing [mentioned in my earlier comments].
[I realize that the following may not be related to this bug. But I have
mentioned it just in case]:
After the boot, I have to do a Ctrl+Alt+Del to get to gdm
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
Confirming workaround by Marien Zwart. After blacklisting both viafb and
vga16fb, I can boot kernel 2.6.32.20 and can use my laptop normally.
Don't know if there are any (major) drawbacks involved with blacklisting
these modules.
--
[KM400] Black screen after boot, no text console possible
https:
As mentioned on the duplicate I just filed: adding "blacklist viafb" and
"blacklist vga16fb" to /etc/modprobe.d/blacklist.conf makes things work
here.
Karmic's kernel (2.6.31-20-generic) also works, but that is because
viafb is not loaded there by default, not because viafb works. If I stop
gdm an
A have same problem with ubuntu 10.4 (2.6.32-20-generic), but kernel
2.6.31-20-generic works fine. I tried change driver to "vesa" or
disabled module dri, glx, but that didn't have any effect. Now, I have
to boot with old kernel.
--
[KM400] Black screen after boot, no text console possible
https:
Same bug for me -- laptop Fujitsu Siemens Amilo Pro v2010, graphics
card: VIA PN800 or PN880 (don't remember which one; I doubt it's
important here), kernel 2.6.23-16-generic. Laptop hangs after fsck with
completely black screen. Interstingly, when I boot into my old Ubuntu
8.10 and immediately re
Hardware: Laptop: MiTac 8615P with chipset: VIA VN896
Software:Ubuntu 10.04, the latest release.
Video driver: 1:0.2.904+svn827-1
My laptop freeze while booting, only a black screen is all I can see.
The Ubuntu boot logo appears the left-down corner of the screen, so
probably the resolution is muc
update:
On my installation, with the latest packages,
1. with kernel 2.6.32-18-generic, the boot still freezes after fsck
message
2. with kernel 2.6.31-19-generic, I get gdm and gnome desktop at low resolution
(800x600) and only other mode shown by xrandr was 640x480.
I manually added a monitor
Adding:
Section "Module"
Disable "dri"
EndSection
to my xorg.conf file didn't make a difference, neither did adding
'Disable "glx"'. I also tried removing the xorg.conf file altogether,
but also that didn't have any visible effect.
@Bartosz: your involvement in this bug, does that mean you
** Summary changed:
- VIA KM400: Black screen after boot, no text console possible
+ [KM400] Black screen after boot, no text console possible
--
[KM400] Black screen after boot, no text console possible
https://bugs.launchpad.net/bugs/518623
You received this bug notification because you are a
15 matches
Mail list logo
