Original problem continues with kernel 5.15.0-23, but there is more than
a screenful of fb output in what appears to be 1024x768 mode before
lockup on switch to i915. Xorg is working normally with only one
connected display.
--
You received this bug notification because you are a member of Ubuntu
Problem is worse with kernel 5.15.0-22, while in distros providing
5.16.11+ and 5.17 kernels the problem is gone. Now in 5.15.0-22, no
video ever shows up after the Grub selection is made. The PC apparently
hard locks immediately with black screen when two displays are
connected, even when only one
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562410/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562409/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562408/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Title:
in
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562407/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562406/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/196
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562405/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562404/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562403/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Title:
in
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562402/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562401/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562400/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562399/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Title:
init
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562398/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1961546/+attachment/5562397/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961546
Title:
init f
apport information
** Tags added: apport-collected
** Description changed:
# apt-cache policy linux-image-5.15.0-18-generic
linux-image-5.15.0-18-generic:
Installed: 5.15.0-18.18
Candidate: 5.15.0-18.18
Version table:
*** 5.15.0-18.18 500
500 http://us.archive.ubuntu
Public bug reported:
# apt-cache policy linux-image-5.15.0-18-generic
linux-image-5.15.0-18-generic:
Installed: 5.15.0-18.18
Candidate: 5.15.0-18.18
Version table:
*** 5.15.0-18.18 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
Reporter has history leading up to this report on
https://www.linuxquestions.org/questions/linux-hardware-18/unable-to-
use-twin-monitors-4175702792/ where no solution was found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Broken panning, Bug 77321 , got a downstream fix 5 months ago in
https://bugzilla.opensuse.org/show_bug.cgi?id=771521
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881046
Title:
Panning in a virtual
Broken panning, Bug 77321 , got a downstream fix 5 months ago in
https://bugzilla.opensuse.org/show_bug.cgi?id=771521
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883319
Title:
xrandr --scale restr
(In reply to Michal Suchanek from comment #26)
> This seems to work for me.
Are you sure nothing is setting DPI explicitly or implicitly, such as your DE?
> X.Org version: 1.17.2
> resolution:100x100 dots per inch
> Actual resolution seems to be more like 109 dpi but it's certainly not fixe
Mc exposes the failure, doesn't cause the failure. AFAICT, the failure
is in console-setup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437589
Title:
boxdraw characters corrupt unless unicode_star
I tried to paste console-setup 1.108ubuntu4 from bug.apport into the
package name field during report composition, but it was rejected. I
changed it to simply console-setup, but where that went I have no idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
en_US installation via HTTP onto test system initiated by Grub loading
installation kernel & initrd with 'tasks="standard"' roughly 30 hours
ago, then mc, sddm and selected KDE/KDF packages added via apt*.
DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)"
VERSION
(In reply to comment #53)
> Probably this bug has been marked invalid because there is a mix of two bugs
> here: one is related to panning (which I do not know if it's fixed or no),
> and the other one to mouse constraints when scaling
This bug has not been marked invalid.
> I have X.Org X Serve
(In reply to comment #53)
> Probably this bug has been marked invalid because there is a mix of two bugs
> here: one is related to panning (which I do not know if it's fixed or no),
> and the other one to mouse constraints when scaling
This bug has not been marked invalid.
> I have X.Org X Serve
Since panning at least can work via xrandr, I've forked the failure of
xorg.con* to provide equivalent panning function of xrandr without
arbitrary mouse constraint to bug 77321
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Since panning at least can work via xrandr, I've forked the failure of
xorg.con* to provide equivalent panning function of xrandr without
arbitrary mouse constraint to bug 77321
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Panning works via xrandr (only; not via xorg.con*) also in Kubuntu
12.04's server 1.11.4, while scaling does fail by having the mouse
cursor bound within the screen mode's size.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Panning works via xrandr (only; not via xorg.con*) also in Kubuntu
12.04's server 1.11.4, while scaling does fail by having the mouse
cursor bound within the screen mode's size.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
As the summary is currently written, this bug is INVALID. Panning works
at least as far back as 1.13.2-1.21.1.i586 in openSUSE 12.3
(i865G,rv200), in addition to current 1.15.x and 1.16rc1 servers in
Fedora, Mageia, and openSUSE, but only when xrandr is used to configure
it. Configuration via /etc/
As the summary is currently written, this bug is INVALID. Panning works
at least as far back as 1.13.2-1.21.1.i586 in openSUSE 12.3
(i865G,rv200), in addition to current 1.15.x and 1.16rc1 servers in
Fedora, Mageia, and openSUSE, but only when xrandr is used to configure
it. Configuration via /etc/
For well over a week I've been first testing the success of panning for
various combinations of gfxcard, monitor and fb size in servers prior to
the changes resulting in this bug report and then same for installations
to which I've updated using the 94929 patch applied by Tobias Klausmann
in the op
For well over a week I've been first testing the success of panning for
various combinations of gfxcard, monitor and fb size in servers prior to
the changes resulting in this bug report and then same for installations
to which I've updated using the 94929 patch applied by Tobias Klausmann
in the op
With the g84 on 1080 HDTV, apparently scaling, which I never tried before, is
working too:
$ xrandr --output DVI-I-1 --scale 1.2x1.2
(Assorted X data collected via script):
# grep PRETTY /etc/os-release
PRETTY_NAME="openSUSE 13.2 Milestone 0 (Harlequin) (x86_64)"
# head -n16 /var/log/Xorg.0.log (b
With the g84 on 1080 HDTV, apparently scaling, which I never tried before, is
working too:
$ xrandr --output DVI-I-1 --scale 1.2x1.2
(Assorted X data collected via script):
# grep PRETTY /etc/os-release
PRETTY_NAME="openSUSE 13.2 Milestone 0 (Harlequin) (x86_64)"
# head -n16 /var/log/Xorg.0.log (b
Via xrandr, 94929 patch also tested working apparently OK for:
ATI rv380 VGA & DVI ports 1680x1050 on 1280x1024
Intel G41 VGA & HDMI ports 1680x1050 on 1280x1024
Nouveau G84 DVI port 1680x1050 on 1280x1024. with & without DVI-to-VGA adapter
Nouveau G84 DVI port 2048x1152 & 2560x1600 & 3840x2160 on
Via xrandr, 94929 patch also tested working apparently OK for:
ATI rv380 VGA & DVI ports 1680x1050 on 1280x1024
Intel G41 VGA & HDMI ports 1680x1050 on 1280x1024
Nouveau G84 DVI port 1680x1050 on 1280x1024. with & without DVI-to-VGA adapter
Nouveau G84 DVI port 2048x1152 & 2560x1600 & 3840x2160 on
Comment 43 applies to use of xorg.conf in attempting to produce desired
X configuration, e.g. xorg.conf for Intel gfx containing:
Section "Device"
Identifier "Default Device"
Option "monitor-VGA1" "Default Monitor"
EndSection
Section "Monitor"
Identifier "Default Monitor"
Comment 43 applies to use of xorg.conf in attempting to produce desired
X configuration, e.g. xorg.conf for Intel gfx containing:
Section "Device"
Identifier "Default Device"
Option "monitor-VGA1" "Default Monitor"
EndSection
Section "Monitor"
Identifier "Default Monitor"
Created attachment 96397
Xorg.0.log from i915 host gx280 having used xrandr to produce panning from
94929 patch
This seems to be unusually verbose for the brief time X was running,
with few apps opened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Created attachment 96397
Xorg.0.log from i915 host gx280 having used xrandr to produce panning from
94929 patch
This seems to be unusually verbose for the brief time X was running,
with few apps opened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Created attachment 96204
Xorg.0.log from 92915G host gx280
http://download.opensuse.org/repositories/home:/tobijk:/X11:/XOrg/openSUSE_Factory/i586/
ostensibly has the attachment 94929 patch applied, which I installed on
nv11, rv250 and i915G systems running X.Org X Server 1.15.99.901.
# rpm -q --
Created attachment 96204
Xorg.0.log from 92915G host gx280
http://download.opensuse.org/repositories/home:/tobijk:/X11:/XOrg/openSUSE_Factory/i586/
ostensibly has the attachment 94929 patch applied, which I installed on
nv11, rv250 and i915G systems running X.Org X Server 1.15.99.901.
# rpm -q --
It seems clear that at least analog hardware users who require panning
and want or need to stick to FOSS solutions need to stick to out of
support Xorg versions and/or out of support drivers, and/or ancient
gfxchip technology (e.g. MGA), and/or cheap (and usually slow) hardware
(e.g. # XGI Techno
It seems clear that at least analog hardware users who require panning
and want or need to stick to FOSS solutions need to stick to out of
support Xorg versions and/or out of support drivers, and/or ancient
gfxchip technology (e.g. MGA), and/or cheap (and usually slow) hardware
(e.g. # XGI Techno
More from that IRC conversation:
I'm not asking about making it default, but when screen size can be
detected and resolution is known, what is the problem with dpi?
It worked at some point in the past
it never worked
Ohsix's definition of "never" must be different from the dictionary's.
As ale
If it hasn't happened already, the supply of supported distros that
feature working panning should be exhausted soon. Is there anything non-
programmers can do to facilitate a programmer fixing this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
If it hasn't happened already, the supply of supported distros that
feature working panning should be exhausted soon. Is there anything non-
programmers can do to facilitate a programmer fixing this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
(In reply to comment #31)
> http://download.opensuse.org/repositories/home:/bjoernv:/branches:/openSUSE:/
> 12.2:/Update/standard/
As indicated in downstream https://bugzilla.novell.com/show_bug.cgi?id=771521
these work for me with Intel 865G and NVidia G84.
--
You received this bug notificati
(In reply to comment #31)
> http://download.opensuse.org/repositories/home:/bjoernv:/branches:/openSUSE:/
> 12.2:/Update/standard/
As indicated in downstream https://bugzilla.novell.com/show_bug.cgi?id=771521
these work for me with Intel 865G and NVidia G84.
--
You received this bug notificati
(In reply to comment #77)
> (Chrome already does so, in a misguided attempt to force a constant ratio
> between "px" and "pt" across all websites.
Chrome does because it's built on WebKit, where 96 as the only
possibility is the traditional Macintosh way, which became also the
Internet Explorer d
Created attachment 45751
120 DPI full 1600x1200 desktop screenshot
This demonstrates the current state of elevated actual DTE DPI affairs,
as of the release of openSUSE 11.4 about 5 weeks ago. Video chip is
rv380. Driver is radeon. 120 DPI is achieved exclusively via DisplaySize
in xorg.conf. Note
The bug is marked general, not Intel. Various comments spoke of at least
one other chip prior to my MGA comment 58. Before your comment 58
reached my eyes, I had to put that Intel host aside to work on the MGA
host, so I used that to demonstrate what I wrote in comment 58, that
"always" is incorrec
Created attachment 43320
86 DPI screenshot
What do I win? :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/521877
Title:
[gm45] wrong screen size detected on X200s
To manage notifications about t
Created attachment 43316
Xorg.0.log from server 1.9.3 using 86x86 DPI on i845G
(In reply to comment #57)
> Isn't this bug precisely about X.org *always ignoring* the hardware DPI value
> from the EDID?
There may have been a time when that was the case, but this was filed by
an Intel video user lo
(In reply to comment #55)
> Please use the correct dpi by default.
If it doesn't, it's usually:
1-your distro's fault, or
2-your hardware's fault, or
3-your use of unequal DPI multiple displays, which is a complicated problem for
X to deal with
X automagic configuration will fall back to 96 if
https://bugzilla.novell.com/show_bug.cgi?id=771521 explains how panning
works for me using Radeon but not Intel or Nouveau.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883319
Title:
xrandr --scale
https://bugzilla.novell.com/show_bug.cgi?id=771521 explains how panning
works for me using Radeon but not Intel or Nouveau.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881046
Title:
Panning in a v
FWIW: I don't try to use randr directly to set up panning. I do it
either through xorg.conf or xorg.conf.d/50-monitor.conf because I'm
usually controlling DPI via DisplaySize, limiting VertRefresh to 60 or
75, turning DPMS & DDC off, and turning DefaultModes on. It would be
nice if TargetRefreshRat
FWIW: I don't try to use randr directly to set up panning. I do it
either through xorg.conf or xorg.conf.d/50-monitor.conf because I'm
usually controlling DPI via DisplaySize, limiting VertRefresh to 60 or
75, turning DPMS & DDC off, and turning DefaultModes on. It would be
nice if TargetRefreshRat
For the record, openSUSE Factory (devel) is currently @ 1.12.2, where
panning for me is working OK with radeon/rv200, but not with nouveau or
intel drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
For the record, openSUSE Factory (devel) is currently @ 1.12.2, where
panning for me is working OK with radeon/rv200, but not with nouveau or
intel drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
(In reply to Piyush Soni from comment #557)
> if HTML5 becomes really popular, it might replace Flash
> altogether, removing the need of fixing this bug - but I'm sure Adobe will
> do something to not let that happen so soon...
Adobe already started the process of pushing webmasters to stop using
https://bugzilla.novell.com/show_bug.cgi?id=400552 is the same problem
in openSUSE and http://mail.gnome.org/archives/mc-
devel/2011-May/msg1.html is some mc-devel discussion on the subject.
** Bug watch added: Novell/SUSE Bugzilla #400552
https://bugzilla.novell.com/show_bug.cgi?id=400552
(In reply to comment #8)
> It's not usual that setting DPI to a multiple of 12 can produce more pleasing
> results than prime numbers or multiples of 5. On your display Kyle, 144, a
> multiple of 12 and exactly 1.5 times 96, might work better than 147 or 145.
s/It's not usual/It's not unusual/
--
It's not usual that setting DPI to a multiple of 12 can produce more
pleasing results than prime numbers or multiples of 5. On your display
Kyle, 144, a multiple of 12 and exactly 1.5 times 96, might work better
than 147 or 145.
--
You received this bug notification because you are a member of Ub
Public bug reported:
This seems essentially a continuation of or closely related to
https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/150797
In Lucid when I try vga=0x120 on cmdline I do not get the Intel legacy
native 132 column by 25 row mode. A message flashes on screen and
disappears too
This is worksforme as of 9.10.
--
Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120
https://bugs.launchpad.net/bugs/150797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I installed Epiphany under Karmic Kubuntu. I see no way evident to
directly influence the size of Epiphany web page fonts other than via
its minimum size setting or use of zoom. Epiphany does not respond to
changes in KDE font settings in any way that I can tell. http://fm.no-
ip.com/auth/dpi-scree
I no longer use *buntu on any systems where the standard VESA modes do
not work as expected. It's possible
http://bugzilla.kernel.org/show_bug.cgi?id=7513 may have provided a fix.
The Novell bug noted earlier has been marked fixed as well. I do still
have a working i810 system, so I need to try a 9
The new summary makes my previous comments in this bug inapplicable to
this bug. My disk had a standard partition layout, with all logicals
inside an extended that logically follows 3 primaries.
--
fails to recognise any partitions when primary partition inside extended
partition
https://bugs.la
For framebuffer modes other than 80x25 to function, the GX260 BIOS'
Onboard Video Buffer usually has to be set to 8MB. Leaving it at the
default 1MB usually does not work for the onboard 845G graphics chip.
Now in a fresh install of Kubuntu Intrepid 8.10 from the alternate CD, I
find vga=0x305, vga
*** This bug is a duplicate of bug 118745 ***
https://bugs.launchpad.net/bugs/118745
This is not a bug 118745 duplicate. Nothing about getting X to use an
appropriate DPI will directly change the Firefox behavior. A good fix
for this requires an upstream solution from the folks at mozilla.org.
*** This bug is a duplicate of bug 118745 ***
https://bugs.launchpad.net/bugs/118745
This bug is not a bug 118745 duplicate. Firefox defaults are set in px,
while most of the rest of a normal X desktop are set in pt. The px to pt
relationship does vary with DPI, making this look like a DPI bug
*** This bug is a duplicate of bug 118745 ***
https://bugs.launchpad.net/bugs/118745
This bug is in a sense a DPI issue, but Firefox is behaving as expected,
and this bug is not a duplicate of bug 118745.
Unlike the rest of a typical X desktop, in which font sizes are set and
customized in pt
*** This bug is a duplicate of bug 118745 ***
https://bugs.launchpad.net/bugs/118745
This bug is INVALID, not a dupe of 118745. Firefox is behaving exactly
as expected. When you set a default font size in Firefox you're setting
the size in px, not pt. The expected pt size for a 10px default fo
Leann, the fact that no kernel fix is expected for the foreseeable
future is no reason to WONTFIX. A fix will come from somewhere at some
point. It's just not entirely clear where it will come from, or when.
There has always been a fix available by recompiling the kernel to
restore IDE and preload
That's basically what
https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/150797/comments/1
means IIRC. Newer BIOS may have a 1MB/8MB option while older BIOS have
only .5MB/1MB options. IIRC, my GX150 i815 with Hardy has a BIOS with
.5/1 option set to 1, while my Intel DLVA 845G with Hardy has t
Since my last update, the problem returned, except that the background
color I set in .bashrc is not ignored.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm validity of TEN's comment 8 using 2.6.24-12-generic and
3.0.28a.
--
I/O error on access to SMB shares of OS/2 Warp 4 host mounted in Ubuntu 7.04
https://bugs.launchpad.net/bugs/112839
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Ben Collins wrote "It's way to [sic] unstable,"
That's utter nonsense. In all the years I've been using Linux since
sometime last century, my kernel lines have not had vga= parameters only
briefly when necessary to overcome brokenness such as this. With the
exception of this bug, such periods wit
I upgraded from Gutsy to Hardy and observed no improvement. Then I added
vesafb to /etc/modules. This proved a partial solution. I no longer need
to manually modprobe vesafb, but there's a much too long 25 second delay
between Grub menu selection and observing anything but black on the
screen again
Summary should be changed from "initramfs not generated correctly on
upgrade to Dapper" to "initramfs not generated correctly on dist-
upgrade". This just happened to me going from Gutsy to Hardy. Marking
kernels for reinstallation and applying in Synaptic made system bootable
with Hardy kernels an
Upgrading to the latest kernel didn't help my mga system at all. My
/etc/modprobe.d/blacklist-framebuffer file has no content. No matter
what combination of modules I do or don't include in /etc/initramfs-
tools/modules before doing 'update-initramfs -u -k all', I get entirely
black screen between
FWIW, this bug does not apply to OpenSUSE 10.3, Mandriva 2008, or
Feisty, and I highly doubt it applies to Fedora 8 or any other recent
distro. Apparently the devs think those who rightly expect their fb
consoles to work correctly should use something other than Gutsy or
Hardy, or write their own s
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 receiv
depmod -a didn't change anything for me.
--
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.ubun
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
I tried on another machine with 2.6.22-14-, both 386 & generic, and
Matrox G400. More less the same problem, except that once KDM starts,
trying to switch to tty[1-6] gives me the KDM background image instead
of a black screen, but all during init it's all black.
vesafb does not show up in lsmod o
I just did updates again, and tried as NeverMind suggested in comment
89. As I have Intel 845GL, I did s/nvidiafb/intelfb/. With the default
stanza and vga=788 I still have useless ttys, although there is some
scrambled junk on the top few rows of each instead of entirely black.
This system also h
*** This bug is a duplicate of bug 129910 ***
https://bugs.launchpad.net/bugs/129910
** This bug has been marked a duplicate of bug 129910
tty[1-6] are active but display nothing in Gutsy
--
Bootup splash screen causes problems
https://bugs.launchpad.net/bugs/151490
You received this bug
I tried what MOM2007 recommended without success, and with my i845G with
removed usplash wound up with:
/etc/initramfs-tools/modules:
fbcon
intelfb
vesafb
/etc/modprobe.d/blacklist-framebuffer
...
# blacklist i810fb
# blacklist intelfb
# blacklist vesafb
# blacklist vga16fb
No success, but I se
Looks like another bug 129910 duplicate.
--
framebuffer mode results in black screen starting with kernel 2.6.22-13-generic
https://bugs.launchpad.net/bugs/150638
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
Same problem on 845G. 80x25 is horrible. Please fix this ASAP.
--
Intelfb completely b0rken
https://bugs.launchpad.net/bugs/147606
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.ubunt
Using what hardware? With 2.6.22-14 on my Intel 845G, vga= framebuffer
modes blank the console screens, but video=vesafb has no apparent
effect.
--
framebuffer mode results in black screen starting with kernel 2.6.22-13-generic
https://bugs.launchpad.net/bugs/150638
You received this bug notifica
I've since determined that with 845G a BIOS upgrade may provide support
for standard framebuffer vga= modes.
--
Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120
https://bugs.launchpad.net/bugs/150797
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: usplash
I installed from kubuntu-7.10-beta-alternate this AM, then immediately
upgraded to whatever state is on the mirrors.
On all Intel video chips that I've used (i810, i815, 845G), none of the
common framebuffer vga= modes (785, 788, 791, 0x31a, etc.
It is artificial in the sense that the kernel developers chose to regard
the SCSI partition limit problem of no apparent consequence when
choosing to _replace_ the traditional IDE driver system with a libata
driver system based upon a SCSI foundation. This they did in the face of
ever more gargantu
1 - 100 of 115 matches
Mail list logo
