** Tags added: metabug
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
@strabes
To extract the usplash.conf file from the initramfs, follow these steps:
1. open a terminal
2. run this command: mkdir tmp; cd tmp; gzip -cd /boot/initrd.img-$(uname -r) |
cpio -im; cp -a etc/usplash.conf ..; cd ..; rm -rf tmp
(best is to paste this line in your terminal, if you retype
Confirming on xserver-xorg-video-ati, based on the fact that debbugs
#445100 suggest that some Debian ATI driver version fix this problem.
** Also affects: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status:
In Debian bug number 445100, it is said:
You nailed that one, Brice. The problem goes away with
xserver-xorg-video-ati/experimental 1:6.7.194-1.
** Bug watch added: Debian Bug tracker #445100
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445100
** Also affects: xserver-xorg-video-ati
@interbird:
Thanks for your reply. I ran the commands and both files are identical,
but my shutdown usplash is still a small, very dark greyscale version of
the normal usplash image. Is there any other information you know that
might apply to this problem? Thanks again.
--
tty[1-6] are active
I've tried both:
1. sudo vi /etc/initramfs-tools/modules and add fbcon and vesafb
fbcon
vesafb
2. sudo update-initramfs -u
3. sudo vi /etc/modprobe.d/blacklist-framebuffer
change the line blacklist vesafb to # blacklist vesafb
4. reboot and everything is fine
and:
1. sudo nano
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I do have a VERY different workaround, that let me suggest the real bug
is with xserver-xorg-video-intel.
Everytime I set my /etc/X11/xorg.conf file to use 'i810' driver, my TTY[1-6]
works fine.
And when I set Xorg to use 'intel' driver, my TTY[1-6] goes away.
As I reported in duplicate of this
@interbird:
May I ask how to edit the /etc/usplash which is used for shut down? I
have apparently edited the one used for bootup by simply running sudo
nano /etc/usplash. I don't exactly understand the difference between the
two. If you could point me to a website with this kind of information
This is how I got my Dell Inspiron E1705/9400 with ATI Mobility Radeon
X1400 working:
Undo all the other things you did with vesafb. The /etc/initramfs-
tools/modules and /etc/modprobe.d/blacklist-framebuffer files should be
their defaults (vesafb should be commented out again.)
sudo nano
@strabes
At boot-time the splash-screen takes it's resolution from /etc/usplash.conf,
*which is in the initramfs image* !
At boot the root-filesystem is changed from the initramfs to the real-root.
Your system is on the real-root.
On shutdown, the splash-screen takes it's resolution, again, from
errata:
#1
s/Which is different/Which could be different/
#2
What's a link to a link without a link...
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers
(thx, caravel)
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You
thinkpad Z60m (intel vga) framebuffer working with:
kernel: 2.6.22-14-generic
grub options: # defoptions=nosplash vga=791
sudo nano /etc/modprobe.d/blacklist-framebuffer
change the line blacklist vesafb to # blacklist vesafb
sudo vi /etc/initramfs-tools/modules and add fbcon and vesafb
sudo
1. sudo nano /etc/modprobe.d/blacklist-framebuffer
* change the line blacklist vesafb to # blacklist vesafb and I
uncommented nvidiafb (if somebody has another card just choose your's)
2. sudo nano /etc/initramfs-tools/modules and add fbcon and vesafb and nvidiafb
(the same as above, if other
Should I take that to mean, comment out (with #) blacklist nvidiafb (I
have an old nvidia Geforce card) so that it is NOT blacklisted?
I took this to say that vesafb and nvidiafb are the only ones in my file
WITH a # so as not blacklisted. Right?
--
tty[1-6] are active but display nothing in
i would recommend not to comment out nvidiafb.
there are issues known and what you really want is vesafb.
leaving nvidiafb in the blacklist is goood.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a
Hmm. With only vesafb it is not working,
at least with me.
Regards.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Same here, I needed to include nvidiafb (with a PCX5300 card).
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
wright,
than do it without 4.:
1. sudo gedit /etc/initramfs-tools/modules
add following lines:
fbcon
vesafb
2. sudo update-initramfs -u
3. sudo gedit /etc/modprobe.d/blacklist-framebuffer
change the line blacklist vesafb to # blacklist vesafb
5. sudo gedit /boot/grub/menu.lst
this line
Never Mind said...
I've got a Nvidia FX 5200
sudo nano /etc/modprobe.d/blacklist-framebuffer
change the line blacklist vesafb to # blacklist vesafb
sudo vi /etc/initramfs-tools/modules and add fbcon and -- nidiafb
sudo update-initramfs -u -k all
It works for me ;)
Before I saw your
are you test Nvidia chip with just add vesafb but not nvidiafb to
/etc/initramfs-tools/modules
if you have time, PLs take a test, Thank you.
wait for your report. :)
On Mon, Nov 12, 2007 at 04:00:26PM -, darthanubis wrote:
Authentication-Results: mx.google.com; spf=pass (google.com: best
hi, i have the same,
since gutsy, switching to vt by pressing ctrl+alt+F1-6 results in black screen.
removing vga=791 does not change a thing.
nvidia go6600
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you
thanks 1000 times to John Yates!!and all of you!!!
this worked for me perfectly:
ubuntu gutsy framebufer fix for switching to VT:
1. sudo gedit /etc/initramfs-tools/modules
add following lines:
fbcon
vesafb
2. sudo update-initramfs -u
3. sudo gedit /etc/modprobe.d/blacklist-framebuffer
I don't know who John Yates is (I don't see a posting with that name
here), but what's the use of step 4? You already added fbcon to /etc
/initramfs-tools/modules in step 1.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug
@Goodness
Can you send your initrd image to the email-address in the script?
I'll try it on my system to see what's wrong with it.
Please also include the out put of the lspci -v and lmod commands.
*Before you modprobe vesafb; thus when your Ctrl-Alt-Fn terminals are blank*
You can use: lspci -v
Hello,
first, i make a backup of my complete installation before i start the
test with the skript
now i test the skript, at last the version #4.
i think my sytem like not to load vesafb at booting.
i do following:
back to standardfiles /etc/modules, /etc/modprobe.d/blacklist-framebuffer and
@Goodness
The pushd and popd commands could not be found on your system.
I did not realize they are not installed by default, sorry for that.
Here is a fixed script.
Hope this one works for you.
@angel1127
The vesafb should work with any vesa 2.0 compliant videocard.
It is only used for the
@Shriramana Sharma
In my former post I meant: vga=792 uses 24-bpp.
So try vga=791 and please see if this new script fixes the cpio error you had.
** Attachment added: Script to fix gutsy initrd.img to load vesafb
unconditionally #4
http://launchpadlibrarian.net/10301766/fix-gutsy-initramfs
@Shriramana Sharma
vga=791 (0x318) uses 24-bpp which could be the problem.
Try vga=791 (0x317) which uses 16-bpp.
Here is some info (look at the table under section 5.3):
http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html
If that doesn't work, I'm currently on IRC and willing to help you.
Server:
@interbird:
I'm on en_IN so by doing export LANG=en_US prior to running the script
the script worked, and I even got the vga=792 screen until X started.
After X started, however, Ctrl+Alt+F1 etc give me a junk display.
So:
1) you may consider temporarily storing the LANG environment value into
Goodness wrote on 2007-11-0
i have a problem, i can not load vesafb with modified /etc/initramfs-
tools/modules.
i modified /etc/initramfs-tools/modules:
fbcon
vesafb
and commented out in /etc/modprobe.d/blacklist-framebuffer is:
blacklist-vesafb
sudo update-initramfs -u
When i start the
@Shriramana Sharma
You are right, I was wondering why pushd and popd were not found.
I changed the symlink from dash to bash on my system months ago due to more
strange behaviour from dash.
(I upgraded feisty to gutsy which left my symlink to bash untouched)
I too quickly tried to determine
interbird, please change:
#!/bin/sh
to
#!/bin/bash
in the script. That's the problem. You are telling the system to
interpret the script using sh which on Ubuntu is a symlink to dash which
does not support all of bash's features. (I learnt that the hard way.)
pushd and popd are bash built-ins.
Are the kernel maintainers still actively looking at this? A kernel
update is in order, methinks.
@interbird:
I tried changing 792 to 791 but to no avail. Even changing the xorg.conf depth
setting did not help. I still get the junk display when I do Ctrl+Alt+Fn.
--
tty[1-6] are active but
@angel1127
Vesa is a videocard independant standard to access higher resolutions than
standard vga (640x480x16).
Almost any recent videocard supports this.
You can read what vesa is here:
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
$kernel-source/Documentation/fb/vesafb.txt is correct in
@interbird
I view vesafb readme under kernel 2.6.23 source. it seems to used to
intel boxs.
i do know about what chips support vesa 2.0. is where any list?
Thank you.
interbird 写道:
@Goodness
The pushd and popd commands could not be found on your system.
I did not realize they are not
Hello,
i have a problem, i can not load vesafb with modified /etc/initramfs-
tools/modules.
I modified /etc/initramfs-tools/modules:
fbcon
vesafb
and commented out in /etc/modprobe.d/blacklist-framebuffer is:
blacklist-vesafb
sudo update-initramfs -u
When i start the system comes a black
@Goodness
Maybe this script fixes it for you.
** Attachment added: Fix gutsy initrd.img to load vesafb unconditionally
http://launchpadlibrarian.net/10292550/fix-gutsy-initramfs
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug
its just can used to fix chip of intel which use vesafb.
for a fresh to linux, they may use this to all ubuntu.
so i think, if you write script to fix, Pls give a error or warning when
non intel chip.
or write a script to fix common chips.
THX.
interbird 写道:
@Goodness
Maybe this script fixes
@ interbird
thanks for your help, but there is a problem with the skript:
./fix-gutsy-initramfs: 29: pushd: not found
cp: Aufruf von stat für „initrd.img-2.6.22-14-generic“ nicht möglich: No such
file or directory
gzip: initrd.img-2.6.22-14-generic.gz: No such file or directory
Sounds nice. Will try it when I get home tonight.
But what about non-nVidia systems? I am having the same problems on an
Intel system (with a 82915G video chip).
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because
This is in response to caravel's comments:
My hardware is similar. Nvidia GeForce 8400M GS, Intel Core 2 Duo. I
also have Gutsy amd64 desktop installed.
I was intrigued that you were able to get a console with native
1440x900, and gave your method a try. It was not successful.
But I was able
@caravel
Just tried your solution on the nVidia system. It works. Not without the
vesafb. In that case the monitor and video card are not recognised, and I get
the Gnome window at 800x600 in the center of my 1280x1024 monitor. tty1-6
looked ok, but could not switch back to tty7 (just a
@caravel
Did the same on the Intel system, with intelfb instead of nvidiafb.
Everything seemed to be ok, until I tried to switch back from tty1 to
tty7. tty7 was just black. It did work however, because the key sequence
alt-F1, S, A, alt-H restarted the system (keys are for the Dutch
locale).
Just correcting myself:
9. to allow module loading, I commented two blacklist lines in this file:
$ sudo nano /etc/modprobe.d/blacklist-framebuffer
# blacklist nvidiafb
# blacklist vesafb
* if anyone had the time to try without vesafb, that would be great
Cheers
--
tty[1-6] are active but
Bug confirmed on fresh 7.10 final installation
$ uname -sr
Linux 2.6.22-14-generic
$ lspci | grep 'VGA'
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated
Graphics Device (rev 02)
but can neither confirme John Yate's fix nor loading it manually.
Black ttys untill gdm
** Tags added: hardy-kernel-candidate
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Sridhar Dhanapalan wrote:
The solution outlined in fanatic's last post has made my console visible.
I didn't have to use any vga settings in grub.
I should add that this has seemingly messed up my bootsplash. It is
now of a lower resolution, and is offset to the right to the point where
I have had this bug for a long time in Feisty and now in
Gutsyinstead of a black screen I received verticle colored lines
filling the whole screen.
I have HP dv8000 with AMD with ATI X200M
The bug only exists when I use fglrx drivers.
I employed the solution of Kai (way above: radeonfb,
the commands below also solved the issue, however resolution isn't perfect
sudo modprobe vga16fb
sudo modprobe fbcon
just waiting for the bug fix and so far working with the temp fix. many
thanks to all pointing that out. It drove me crazy many days ago.
--
tty[1-6] are active but display
Best results I got so far:
- used startupmanager to set resolution to 1280x1024 (could do this manually,
but wanted to try this way);
- manually removed vga=794 setting from boot parameters in /boot/grub/menu.lst;
- no changes to the default modules list or blacklists.
I now have a proper
@ardchoille
I actually used mc as root to add the module-names and then posted the
append-commands without checking if they worked.
And you are right, they don't work; shame on me.
Your comment reminds me again to always double-check before posting.
Thanks !
--
tty[1-6] are active but display
So... I know i'm rather new to this whole scene, but the issue i'm
having is related, though slightly different. Instead of just plain
black tty's, my screen cycles through colors. And only when i'm using
nvidia-glx-new drivers. When i use the nvidia-glx ones (after i get them
working,) I get to
Loading the vga16fb and fbcon modules gets the ttys working again for
me, although their display isn't perfectely centered on screen plus no
Login: prompt appears when switching to them (entering the login works
nevertheless).
Kernel version is 2.6.22-14-generic.
--
tty[1-6] are active but
Bug also confirmed on final gutsy upgrade on my computer.
The following commands solve the problem (i added the 2 modules in my
/etc/modules file).
sudo modprobe vga16fb
sudo modprobe fbcon
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received
This bug almost made Xubuntu uninstallable on my machine (reformat and
clean install) since the installer did not recognize my hardware
properly, and not all of the options that I passed to the installer were
honored by it. And since Xfce-terminal has a bug too (crashes GDM) and
I could not bring
ASUS F3SC-AS218E here, with GeForce 8400M. I was testing all Tribes
and RC of Ubuntu Gutsy and recently I installed it from official ISO.
I have nvidia-glx-new driver installed by Restricted Drivers Manager
and I have obviously noticed problems with black virtual terminals.
Since this notebook
For me this worked :
sudo echo fbcon /etc/modules
sudo echo vesafb /etc/modules
sudo update-initramfs -v -u -k $(uname -r)
The screen will remain blank for some time until the drivers are loaded.
To have them loaded earlier-on initrd has to be modified.
Some info of my machine:
grub menu.list
The solution outlined in fanatic's last post has made my console
visible. I didn't have to use any vga settings in grub.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I should add that this has seemingly messed up my bootsplash. It is now
of a lower resolution, and is offset to the right to the point where
half of it is on the right edge of the screen and the rest is wrapped
around onto the left. I've experimented with a few different resolutions
in
use vga=791 will effect your gnome UI.
you take care look at UI color and other. you will find.
interbird 写道:
For me this worked :
sudo echo fbcon /etc/modules
sudo echo vesafb /etc/modules
sudo update-initramfs -v -u -k $(uname -r)
The screen will remain blank for some time until the
interbird wrote ..
For me this worked :
sudo echo fbcon /etc/modules
sudo echo vesafb /etc/modules
interbird, you might want to cat /etc/modules and see if the expected
text was actually written to that file because those two commands
shouldn't have worked as you expected them to. The
I can reproduce this bug on an ATi card (Radeon Xpress 1100) using
fglrx. I can also fix the bug by adding vesafb and fbcon to /etc
/initramfs-tools/modules, and commenting out the relevant lines in
/etc/modprobe.d/blacklist-framebuffer. As a result of this the splash
image does not display
I did a fresh install of Gutsy on my AMD/nVidia system. I can access tty1-6
now, but the font is huge. I am using the nvidia-glx-new restricted drivers,
which were installed via the Restricted Manager.
I will try to change the resolution to get a smaller font in the tty's, and see
if that
*** solved here ***
using El Chupacabras instructions.
vga=791 is working fine.
Thank you!
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
No luck here. I've tried all the suggestions made above. I've got a Dell
Inspiron 9400 laptop with Nvidia GeForce Go 7900GS graphics.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
---solved here too
I used El Chupacabras instructions as well. I have added a vga=791 in my
menu.lst and I edited my /etc/initramfs-tools/modules to look like:
fbcon
vsafb
vga16fb
I changed /etc/modprobe.d/blacklist-framebuffer
blacklist vesafb - #blacklist vesafb
blacklist
I confirm the problem here on my Acer Aspire 5680 Laptop.
I've installed Ubuntu Gutsy and set up the boot with startup-manager.
My tty consoles on f1-6 are invisible, with the flashing cursor on top-left
corner, but working. If I log in, it logs me in (I verified from X just after).
--
tty[1-6]
Tried to change the resolution to 1280x1024 by editing usplash.conf and adding
vga=794 to the kernel boot parameters, and generating a new initrd image.
During boot the Ubuntu logo screen disappeared, and was replaced by a black
screen with a flashing cursor in the upper left corner. After a
ardchoille,
Sorry for the accusation. You're not to blaim, I overreacted in the heat of the
moment.
Real problem here is that just users are the ones that respond here. Nothing
from the official Ubuntu side. Why can't they at least inform us about the
status of the bug?
Workarounds reported
gwi, no hard feeling.. and you have a very good point. There should be a
standard process to this, since this is a critical bug. Someone from the
dev team should be assigned as PR for the bug to come in and say
something to the effect of
we're working on the bug at the moment and will get back to
I just noticed the date when this bug was first reported:
Bug #129910, first reported on 2007-08-02 by Miguel Martinez
That's over two months ago. Maybe this is one of those situations where
the dev team isn't interested in fixing the bug.
--
tty[1-6] are active but display nothing in Gutsy
Hi, i have AMD Athlon 2000+ and Nvidia 6200 graphic card. I have
installed Gutsy and have the same problem with tty. I have nvidia-glx-
new drivers installed and with that drivers it is impossible to make tty
work in gutsy, nvidia-glx drivers work fine but then you can't enable
your visual
I am experiencing the problem on two different systems: one (AMD
Athlon64 X2) with nVidia restricted drivers, and one (Intel Pentium IV)
with the i810 non-restricted drivers. So the restricted drivers are not
the (only) cause of this bug.
--
tty[1-6] are active but display nothing in Gutsy
gwi have you tried to remove vesafb from blacklist-framebuffer on that
system with i810. Maybe that will work, and if you are using nvidia-glx-
new restricted drivers try nvidia-glx non-restricted. That worked on my
system, but nvidia-glx does not support visual effects or 3D.
--
tty[1-6] are
I can reproduce this on one system using an NVIDIA card and nvidia-glx
drivers, one system using an NVIDIA card and nvidia-glx-new drivers, and
one laptop (Acer Travelmate 4000) with an ATI card and no proprietary
drivers.
--
tty[1-6] are active but display nothing in Gutsy
The original problem (black screen on tty[1-6]) is not related to nvidia
or other hardware and is caused by a change in /scripts/init-
top/framebuffer from Feisty to Gutsy:
--- initrd.feisty/scripts/init-top/framebuffer 2007-02-07 10:52:34.0
+0100
+++ initrd/scripts/init-top/framebuffer
I'm no expert, but I have to disagree for the following reasons:
1) I cannot find -b anywhere in my /usr/share/initramfs-tools/scripts
/init-top/framebuffer file
2) My /etc/modprobe.d/blacklist-framebuffer file still contain the lines
blacklist vesafb and blacklist vga16fb
3)
As Massimo Dal Zotto wrote, the original problem (black screen on
tty[1-6]) is not related to nvidia or other hardware. The problem
exists for non-NVidia users as well, such as mga and intel.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You
Thanks ardchoille, this:
sudo apt-get install nvidia-glx sudo nvidia-glx-config enable sudo
dpkg-reconfigure xserver-xorg
really fucked up my system. Ended with a message that my config was corrupt and
I should recheck the MD5sum?
Result: display adapter: no longer recognised, monitor: no
gwl i had the same problem, had to reinstall gutsy and it fixed the problem,
try backing up your files and re-install
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have experienced this problem on a clean install of 7.10. Graphics
are provided by an old nvidia gforce mx2 card. TTYs 1-6 showed up
following the initial install and following the restricted drivers
install using the new GUI module. They disappeared after I added
vga=791 to my boot options.
gwi wrote:
Thanks ardchoille, this:
sudo apt-get install nvidia-glx sudo nvidia-glx-config enable ..
gwi,
I'm sorry it made further problems with your system. However, in all fairness,
what I suggested was the proper way to install nvidia drivers on a fresh
install without using the
The same problem occurred for me with a RV280 [Radeon 9200 PRO] chip.
Removing vga=791 from /boot/grub/menu.lst fixed the problem.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Why do you add vesafb to your /etc/initramfs-tools/modules instead of the
nvidiafb?
As far as I know vesafb is for intel chips.
Try the following:
sudo vi /etc/initramfs-tools/modules and add fbcon and nvidiafb
sudo update-initramfs -u -k all
--
tty[1-6] are active but display nothing in
Thank you for trying Thomas Sommer, but it didn't work.
I can't live without my tty's. If xorg breaks, I have no alternative but
to reinstall Kubuntu. At least in Feisty, I was able to use screen +
mutt + irssi + elinks + bash + mc in tty 1-6 and was able to continue
work and not have to worry
My tty return back, i lost it after last update kernel. today i test
update-initramfs -u -k all.
then restart it, tty return.
so i think its because default kernel all black all framebuffer, so you
need to update by your configure files
/etc/modprobe.d/blacklist-framebuffer
I have fixed it on the following:
Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub
Interface (rev 03)
I followed satkata's instructions from
https://bugs.launchpad.net/ubuntu/+bug/152089 1st comment:
1. sudo vi /etc/initramfs-tools/modules and add fbcon and vesafb
so my
I have an ATI Radeon 9600 card, and Kai's fix (
sudo mcedit /etc/initramfs-tools/modules
fbcon
radeonfb
sudo update-initramfs -u -k all -v
sudo mcedit /etc/modprobe.d/blacklist-framebuffer
#blacklist radeonfb
sudo modprobe radeonfb
)
Lets me see the shutdown messages, but I still get
I got it!!! I also commented out blacklist vesafb in /etc/modprobe.d
/blacklist-framebuffer, and now it works! I'm using the
2.6.22-14-generic kernal.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a
Got no luck with the workaround here.
using vga=0x318
[EMAIL PROTECTED] [4|~/thunderbird-maddler] $ uname -a
Linux aubergine 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce Go
7600] (rev a1)
--
tty[1-6]
@ Thomas Sommer: nvidiafb is fine if you are using nv video driver,
but it conflicts with the nvidia-glx-new proprietary driver. Since
vesafb works well with nvidia video cards, that's the suggested choice
to use.
--
tty[1-6] are active but display nothing in Gutsy
Changing my previous comment, for my nvidia card the nvidiafb driver is
not needed, a wrong testing procedure made me think that. Vesafb is more
than enough as Jean has noted.
So the suggestions by NeverMind, satkata and Absorbed are basically the
same and worked as is for me without needing
On 10/21/07, Salva Ferrer [EMAIL PROTECTED] wrote:
Changing my previous comment, for my nvidia card the nvidiafb driver is
not needed, a wrong testing procedure made me think that. Vesafb is more
than enough as Jean has noted.
My card (GeForcde 7300 LE) was not working with vesafb and it is
I had the same problem with no tty's, all I did to fix it was reinstall
gutsy and restore my packages with aptoncd and my /home partition took 20
minutes to fix this problem that way
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug
1.) I edited my /etc/initramfs-tools to look like:
fbcon
vsafb
vga16fb
2.) I changed /etc/modprobe.d
blacklist vesafb - #blacklist vesafb
blacklist vga16fb - #blacklist vga16fb
3.) sudo update-initramfs -u
I have an Nvidia GeForce 7600 GS, and this worked for me.
Try enabling vga16fb if no
I'm sorry, but the vsafb is supposed to be vesafb.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
My kernel is 2.6.22-14-386 , I tried removing vesafb from blacklisted
modules and modprobe it / added it to initramfs modules , but this
problem still persist. When I modprobe vesafb and fbcon, tty[1-6] gives
black screen, When I boot my system without vesafb, It gives only
flashing _. It's very
Try removing vga16fb from the blacklist,
and adding it along with vesafb and fbcon to the initramfs modules.
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I've followed recommendations exactly, and variations thereof, with both
Matrox and Intel chips. In no case has lsmod ever shown vesafb as having
been loaded by the time init completes. Only when I modprobe vesafb
manually do I get working framebuffer consoles.
--
tty[1-6] are active but display
1 - 100 of 208 matches
Mail list logo
