[Bug 518623] Re: [KM400] Black screen after boot, no text console possible
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, especially for older IGPs like CLE266. However you can likely make it work with some module parameters as described in viafb.txt: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/fb/viafb.txt;h=f3e046a6a987a685910bafc171c2cc9cf243df1b;hb=HEAD If you also hit some acceleration bugs that where fixed in 2.6.33 you can use viafb_accel=0 This bug is similiar/identical to this one I think https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-via/+bug/538430 I do not object blacklisting viafb for this release as there exists also an even more serious problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539020 However blacklisting vga16fb sounds like a bad idea but that's not something I work on. (but even balcklisting it wouldn't be that much of a problem but it really should simply work) Perhaps it would be a good idea to do one seperate bugreport only for the vga16fb bug which gives a more verbose description of what the screen looks like? -- [KM400] Black screen after boot, no text console possible https://bugs.launchpad.net/bugs/518623 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 558569] Re: Unable start as live cd Lucid Beta 2
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 IGP works for some people - the crash happens very early (even when the module refuses to work) but seems to also happen if it would likely work (with the vmalloc option) I can think only of one code area, the I2C code, that could cause this as the rest are fairly simple PCI commands. Maybe the manufacturers of your boards did some strange things as is done in OLPC (where this just causes half a minute delay). But maybe I'm just missing something obvious here. However debugging this and finding the right fix will be something that takes a while (and a lot of help from people who experience this bug). There is a slight chance (although relatively low) that this will be fixed in 2.6.35-rc2 as Jon posted some changes to the I2C code (not explicitly labled as fixes so don't expect too much). It also could be helpful if somebody would test Harald's old tree, located at http://git.gnumonks.org/cgi-bin/gitweb.cgi?p=linux-2.6-via.git;a=shortlog;h=refs/heads/via-viafb but I do not expect it to work any better (although it did sometimes in the past). If I knew that this does not work I could ask him for help as he has better connections to VIA and is more experienced than me. So if you want to give it a try this might be a starting point https://wiki.ubuntu.com/KernelTeam/KnowledgeBase I won't provide any help in compiling and installing your own test kernel as my advice would likely lead to screwing your system up. Sorry that I can't be a big help but there is not much I can do without knowing what exactly goes wrong and therefore prefer to concentrate on the things I can actually do without too much guesswork. -- Unable start as live cd Lucid Beta 2 https://bugs.launchpad.net/bugs/558569 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539020] Re: Lucid Beta 1 installation CD gives blank screen and freezes
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 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539020] Re: Lucid Beta 1 installation CD gives blank screen and freezes
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 just dug in my inbox and found the relevant bug report where the VGA hardware looks identical to yours: http://marc.info/?l=linux-fbdev&m=126131088208675&w=2 Sadly the thread was interupted (reply-all problem) and the potential freeze was reported later as a sidenote. -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539020] Re: Lucid Beta 1 installation CD gives blank screen and freezes
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 Fedora is doing who make the module completly unusable as far as I know) -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539020] Re: Lucid Beta 1 installation CD gives blank screen and freezes
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 do you use? (if any) And the hardware you have (VN896). That's all. Framebuffer drivers are pretty standalone. For communication do what you like: Either here (if nobody objects) or mail the results to me or (as the module shouldn't have any grave modifications) to linux-fb...@vger.kernel.org -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539020] Re: Lucid Beta 1 installation CD gives blank screen and freezes
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. Okay as I don't see a way to propagate the boot options to viafb could you please blacklist it for now and test whether sudo modprobe viafb viafb_accel=0 behaves different? This will tell us whether this is a hardware acceleration problem (most likely) or not. I need only the result for one of those 2.6.32 or later kernels. Sorry but I need to locate the problem somehow. Thanks. -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539020] Re: Lucid Beta 1 installation CD gives blank screen and freezes
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 callbacks suppressed [ 32.255737] vmap allocation for size 134221824 failed: use vmalloc= to increase size. [ 32.255742] ioremap failed [ 32.255770] viafb: probe of :01:00.0 failed with error -12 This means that viafb itself refuses to work as it can't map the framebuffer (128MB, is this correct?). I'm really puzzled how a module that itself refuses to do anything can cause any harm to (escpecially freeze) your machine. So the best I can suggest as the next step would be to add the boot option "vmalloc=268435456" to reserve 256MB for remapping and see whether the behaviour of 2.6.33 changes, meaning (a) whether the warning in the syslog vanishes (the different kernel version shouldn't make a difference but you can check if you like) (b) whether viafb still freezes your PC -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539020] Re: Lucid Beta 1 installation CD gives blank screen and freezes
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_accel=0) some other (less critical) hardware acceleration issues are http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8a3a95c32f612068be8dae74fa5fc4cf2db1592e http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0b94190e1e60f96962b82d35729d7d44cf298ef8 Sorry for the trouble but viafb is currently undergoing heavy changes and as only a few people test -mm (resulting in only a very limited variety of VIA boards getting tested) and the datasheets are not as good as they could be these issues can't be avoided at the moment. -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538430] Re: Ubuntu 10.04 alpha 3 boot corrupts screen on VIA VX800 graphics (A110 netbook)
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 device setup is inside viafb and as far as I know in all free drivers a chaos at least. Maybe openchrome assumes that the current setting is correct which is probably not the worst choice but should be avoided if possible. That said its probably a bug in viafb and in openchrome with viafb making the additional assumption that the output device is on VGA/CRT/primary output which is often correct but sometimes wrong. On the long term the whole output device setup mess has to be cleaned up but whether this is possible and how long it will take depends heavily on VIA and won't be finished under a year, I fear. -- Ubuntu 10.04 alpha 3 boot corrupts screen on VIA VX800 graphics (A110 netbook) https://bugs.launchpad.net/bugs/538430 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538430] Re: Ubuntu 10.04 alpha 3 boot corrupts screen on VIA VX800 graphics (A110 netbook)
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 problem for X as I'm only using the framebuffer driver (with -fbdev if X is needed). -- Ubuntu 10.04 alpha 3 boot corrupts screen on VIA VX800 graphics (A110 netbook) https://bugs.launchpad.net/bugs/538430 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 558569] Re: Unable start as live cd Lucid Beta 2
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 correctly during boot process (removing "quiet splash"?). I suggest you look for another bug report that looks like the issue you have or to open one if none exists. For the issue discussed here: Thanks to Leo it was possible to narrow it down to the I2C area. As it does not look like a general issue (some of these IGPs do work) I assume that something on the board where it occurs is wired differently. I do not push the (debug) patch to mainline because it can cause regressions and would forbid any auto-detection (of available resolutions and the like). I am trying to improve the code to auto-detect where devices are connected and plan to query only connected devices via I2C (and hope that this will automatically solve this issue) but that takes a while especially as there exists nearly no documentation for older chipsets. -- Unable start as live cd Lucid Beta 2 https://bugs.launchpad.net/bugs/558569 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
