** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270656
Title:
Ubuntu 14.04 boots to blank console
To manage notifications abou
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
Seems fixed now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270656
Title:
Ubuntu 14.04 boots to blank console
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
As far as I remember we changed CONFIG_DRM_VMWGFX_FBCON to 'y ' now. Generally
it is getting more complicated nowadays. Grub2 initializes some framebuffer
graphics mode (unless console mode is enforced in /etc/default/grub), hands
this fb over to plymouth and that hands things over to X. And som
With my laptop the problem is gone using my self compiled kernel or the latest
one from Ubuntu. It is there using some older kernels. I had to carefully
adjust "vga=xxx" to switch to the very same mode than gfxpayload set to
1280x800@32. Took some time and playing around until it worked as expec
Looks like since the later updates the bug seems gone -- at least for vmwares
graphics drivers.
On an other system running on real hardware the bug seems gone too.
I'll check later today on my laptop -- hopefully it is history there
too!
--
You received this bug notification because you are a m
I fear the problem here might be in reality more than one and we should
get them into separate reports to make it simpler to work on them. The
symptom and maybe the overall problem might be the same but each
graphics type will need to be addressed individually. This report was
initially about vmwgf
I have the same problem. On hardware.
LTS 14.04
GeForce GTX 750
If I enter grub menu choose "Advanced Options For Ubuntu"
Then doing nothing and normally load the system resulting ctrl+alt+F0-F6
becomes working and I see login prompt on text consoles.
Text consoles worked before with the same ubun
I had the same problem, but I fixed it by commenting these lines:
# if ([ "$ubuntu_recovery" = 0 ] || [ x$type != xrecovery ]) && \
# ([ "x$GRUB_GFXPAYLOAD_LINUX" != x ] || [ "$gfxpayload_dynamic" = 1 ]);
then
# echo " gfxmode \$linux_gfx_mode" | sed "s/^/$submenu_indentation/"
# fi
Not sure which errors are gone now. The line related to drm and vmwgfx are like
the previous no blacklisting and no setting fbdev dmesg to me. Again repeating
the resolution and FIFO line and not replacing the framebuffer.
How the user-space tools would influence the kernel boot I cannot explain.
Since today a new version of open-vm-tools is available. I've tested
again with this new version. Some of the errors seen with the old
version are gone now.
** Attachment added: "New version of open-vm-tools"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3955154/+fil
With this kernel-option I'll get a console prompt, but various kernel
log lines are never prinited on screen.
Printing stops at about "[ 54.811735] [drm] DMA map mode: Using
physical TTM page addresses." and then starts again after a screen size
change at about "[ 57.317174] intel_rapl: domain
Ok so with those there seems to be some resolution lines which get
repeated three times with the Ubuntu kernel (which is odd) and compared
to the self-compiled kernel there seems to be no action to replace the
framebuffer.
Could you try to boot the Ubuntu kernel with "vmwgfx.enable_fbdev=1"
added
** Attachment added: "dmesg-log from Ubuntu-Kernel, no driver blacklisted"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954637/+files/dmsg-201401221500.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "dmesg-log from my own kernel, no driver blacklisted"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954635/+files/dmsg-201401221526.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
My fault: picked the wrong dmesg-files …!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270656
Title:
Ubuntu 14.04 boots to blank console
To manage notifications about this bug go to:
https://bugs
Blacklisting simple-framebuffer for the Ubuntu kernel will have no
effect because it is built-in. But I am interested in the two dmesg's
without any blacklisting to compare the output. Somehow those labelled
as own kernel seem to be from a boot with the normal Ubuntu kernel, too.
Just the wrong dme
** Attachment added: "blacklist simple-framebuffer -- own kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954417/+files/dmsg-201401221500.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Attachment added: "blacklist simple-framebuffer"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954402/+files/dmsg-201401221458.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Attachment added: "blacklisted vmwgfx"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954400/+files/dmsg-201401221456.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Attachment added: "none blacklisted"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954403/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_037.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Attachment added: "blacklisted vmwgfx"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954399/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_035.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "none blacklisted -- own kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954405/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_035.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Attachment added: "none blacklisted -- own kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954406/+files/dmsg-201401221456.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Attachment added: "none blacklisted"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954404/+files/dmsg-201401221500.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Attachment added: "blacklist simple-framebuffer"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954401/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_036.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "blacklist simple-framebuffer -- own kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954416/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_037.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "blacklist vmwgfx -- own kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954415/+files/dmsg-201401221458.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Attachment added: "blacklist vmwgfx -- own kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3954414/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_036.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
There are slightly differences in character display depending on which
driver is blacklisted.
With my own kernel I could recognize changes in character display while
booting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
It would explain it when this caused the old framebuffer displayed but
not updated and the new one updated but not displayed. Anyway, the
Ubuntu supplied kernel is quite close to upstream, so its rather some
config difference.
Please could you retry with the latest 3.13.0-5 Ubuntu kernel and add
t
#12: yes this is true, but does not explain why this leads to "blank
console" using the ubuntu supplied kernel and not using one self
compiled from plain vanilla sources. I've tested since: 3.12.8,
3.13.0-rc8 and 3.13. All show the same result: working console at
expected 800x600.
The ubuntu suppl
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270656
Title:
Ubuntu 14.04 boots to blank console
To manage notifications about this bu
The apport data from comment #11 shows a virtual machine on VMWare.
Looking at the first dmesg log, there seems to be some kind of resource
conflict between the simple-framebuffer driver and vmwgfx. For testing
you could probably try to create a file like /etc/modprobe.d/blacklist-
testing.conf wit
apport-collect fails to login to launchpad after allowing to access on
my behalf see:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1270717
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270656
** Attachment added: ""apport-bug linux"-run output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3952531/+files/apport.linux-image-3.13.0-4-generic.aasrvt.apport
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notific
** Attachment added: "Console using plain vanilla kernel 3.13.0-rc8"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+attachment/3952528/+files/NC158_u1404-x86_64%20-%20VMware%20Workstation_024.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
This doesn't seem to be related to util-linux.
** Package changed: util-linux (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270656
Title:
Ubuntu 14.04 boots to blank co
** Attachment added: "Config used to compile plain vanilla kernel 3.13.0-rc8"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1270656/+attachment/3952396/+files/3.13.0-rc8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Attachment added: "Config used to compile plain vanilla kernel 3.12.8 from
kernel.org"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1270656/+attachment/3952389/+files/3.12.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Had the chance to test on a system not providing 640x480 any more. Only
800x600 and higher are available. Such a system is unusable: even
without any vga setting grub is shown, but later, after switching back
to 640x480 nothing is drawn any more on screen!
--
You received this bug notification be
Tested with different vga parameters -- all the same: blank console, but
switched to the given size: 800x600.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270656
Title:
Ubuntu 14.04 boots to blank
/etc/defaults/grub:
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=2
GRU
43 matches
Mail list logo
