** Also affects: xorg-server
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
xf86-video-amd: switching to a vcons fails
https://bugs.launchpad.net/bugs/180742
You received this bug notification because you are a
** Changed in: xserver-xorg-video-amd (Ubuntu)
Status: New = Incomplete
--
Blank or grey chars in font rendering
https://bugs.launchpad.net/bugs/135212
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Gutsy packages are uploaded to my PPA:
https://launchpad.net/~q-funk/+archive
--
xf86-video-amd: switching to a vcons fails
https://bugs.launchpad.net/bugs/180742
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Updated Gutsy packages are uploaded to my PPA:
https://launchpad.net/~q-funk/+archive
--
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Bug watch added: Debian Bug tracker #451089
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451089
** Also affects: xorg-server (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451089
Importance: Unknown
Status: Unknown
--
xf86-video-amd: switching to a vcons
PPA shows that the server fails to build on the
AMD64 platform when the CPUID patch is applied:
https://launchpad.net/~q-funk/+archive/+builds?build_text=build_state=failed
It successfully built on LPIA and i386, though.
--
Martin-Éric Racine
http://q-funk.iki.fi
--
xf86-video-amd: switching
Public bug reported:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
affects ubuntu/flashrom
status new
importance wishlist
subscribe ubuntu-universe-sponsors
Please sync flashrom 0.0+r3073-1 (universe) from Debian unstable (main).
Changelog since current hardy version 0.0+r2769-1:
flashrom
Public bug reported:
Current dependencies are for the old xbase-clients | xmessage. However,
xmessage is provided by x11-utils.
This oversight prevent the removal of basic X packages that duplicate
functionalities offered by equivalent GNOME or KDE packages.
The correct dependency would be
** Summary changed:
- Please sync flashrom 0.0+r3073-1 (universe) from Debian unstable (main).
+ Please sync flashrom 0.0+r3112-2 (universe) from Debian unstable (main).
** Changed in: flashrom (Ubuntu)
Status: Incomplete = Confirmed
--
Please sync flashrom 0.0+r3112-2 (universe) from
The bug was caused by a default pixel depth that was too low. The
default is now 16-bit. An upstream 2.7.7.6 has been released to reflect
this.
I have uploaded it to my PPA and received confirmation that it was
accepted, except that the package has yet to be built by the archive,
for some reason.
As previously reported, DDC works as expected when booting the X server
and AMD driver available in my PPA on hardware booting from a hard-disk.
However, one thing I forgot to point out is that I get really
psychedelic colors, presumably because the maximum color depth is not
correctly detected.
Here is the log I get on the workstation.
** Attachment added: log showing failure to detect 24-bit depth
http://launchpadlibrarian.net/11570562/Xorg.0.log
--
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a
Bryce, since the issue required patching xserver-xorg-core, rather than
xf86-vidoe-amd, would it be appropriate to reassign this bug to source
:xorg-server?
--
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a
Since you used update-manager, it could be a good idea to file the
report against that instead of against upgrade-system.
Reassigning to update-manager.
** Changed in: update-manager (Ubuntu)
Sourcepackagename: upgrade-system = update-manager
--
Problem upgrading from 7.04 to 7.10
In any case, failure to fetch the Packages list of a repository is not a
bug in the update-manager package either. It's a bug in these non-Ubuntu
repositories. Remove them from /etc/apt/sources.list and/or contact the
these sites' administrations to tell them to fix their repository, then
the bug
Bryce, I tried xserver-xorg-core 1.4.1~git20080118-1ubuntu3 on my Hardy
laptop (which uses xserver-xorg-vidoe-siliconmotion). No adverse effect
so far.
--
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: xserver-xorg-video-amd
xserver-xorg-video-amd (2.7.7.6-1) unstable; urgency=low
.
* New upstream release:
+ Default depth raised to 16-bit.
+ Several GCC warning fixes.
*
The change in default display depth actually is of key
NOTE: 1.3 is meant for Gutsy, while 1.4 is meant for the upcoming Hardy
release.
--
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
AMD's Jordan Crouse proposes the following patch.
Scott, can you apply it to the current package and see if it fixes it
for you?
On 17/09/07 14:43 +0300, Martin-Éric Racine wrote:
Greetings everyone,
Can anyone reproduce the following bug?
https://bugs.launchpad.net/ubuntu/+source/xserver
We essentially need to test for two things with this patch:
1) does it solve the crash everyone experiences?
2) does it help X auto-configure itself to the maximum resolution
offered by the display?
--
amd driver fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this
Test packages (Gutsy chroot in pbuilder) are available at
http://q-funk.iki.fi/debian/pool/x/xserver-xorg-video-amd/
The debdiff is attached.
** Attachment added: debdiff_xserver-xorg-video-amd_2.7.7.0-1_2.7.7.0-1ubuntu1
On 11/5/07, Jordan Crouse [EMAIL PROTECTED] wrote:
On 17/09/07 14:43 +0300, Martin-Éric Racine wrote:
Greetings everyone,
Can anyone reproduce the following bug?
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amd/+bug/140051
Patch is attached - just a trivial re
** Changed in: update-manager (Ubuntu)
Sourcepackagename: upgrade-system = update-manager
--
Xubuntu not upgrade to 6,10 bug of update-manager
https://bugs.launchpad.net/bugs/162390
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
It indeed seems to be fixed on Gutsy. Thanks!
--
openoffice.org: impress: presentation mode fails on IceWM
https://bugs.launchpad.net/bugs/88250
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I get the same problem as Will Daniels here. The content of my global
/etc/asound.conf is:
pcm.pulse { type pulse }
ctl.pulse { type pulse }
pcm.!default { type pulse }
ctl.!default { type pulse }
Note that I get the same problem with both Ekiga (whatever is in Gutsy)
and with Skype (1.4 and 2.0
Public bug reported:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
affects ubuntu/xserver-xorg-video-amd
status new
subscribe ubuntu-main-sponsors
Please sync xserver-xorg-video-amd 2.7.7.4-1 (main) from Debian unstable
(main).
Changelog since current hardy version 2.7.7.3-1:
-BEGIN
Hmm... It seems that requestsync failed to fetch the changelog. Here it
is:
xserver-xorg-video-amd (2.7.7.4-1) unstable; urgency=low
.
* New upstream release:
[GX][LX] PreInit fixes to avoid segfaults on X -configure.
.
This is known to work on products with GeodeROM and Insyde
Please note that the Gutsy driver is affected and currently unusable
with LTSP, because DDC probe fails without the above patch and other
changes since 2.7.7.0-1. This needs to be fixed, because this chipset is
used by the vast majority of commercial thin clients designed for LTSP.
--
Please
I have uploaded packages based upon upstream 2.7.7.4 that should fix
this issue for most hardware configurations.
A known exception is hardware booting off General Software BIOS, on
which there are issues with X server 1.3 and newer, more specifically
with the x86emu component of X server, that
xserver-xorg-video-amd (2.7.7.4-1gutsy1) gutsy; urgency=medium
* Reverted 2.7.7.2-2 debian/control changes to produce Gutsy package.
xserver-xorg-video-amd (2.7.7.4-1) unstable; urgency=low
* New upstream release:
[GX][LX] PreInit fixes to avoid segfaults on X -configure.
This is
** Changed in: xserver-xorg-video-amd (Ubuntu)
Status: New = Invalid
--
Laggy and sloppy cursor
https://bugs.launchpad.net/bugs/135211
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Please note that subpixel hinting only works on LCD displays. Just for
reference, can you tell us:
What display are you using? On what Geode-based hardware? Booting using
which BIOS brand and release?
--
Blank or grey chars in font rendering
https://bugs.launchpad.net/bugs/135212
You received
The wishlist you reported does not concern CUPS-PDF at all.
Please note that CUPS-PDF is not an interim solution to anything.
Rather, people have simply found it to be a convenient way to generate
PDF documents. It is specifically intended to replace paper printouts
with PDF documents and to do
All the necessary information was already provided. Reopening.
** Changed in: gtk+2.0 (Ubuntu)
Status: Invalid = Confirmed
--
evince: libgtkprint support is broken
https://bugs.launchpad.net/bugs/135832
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 140051 ***
https://bugs.launchpad.net/bugs/140051
Marc, just for the record, on which thin client device are you trying to
configure this?
--
amd xorg driver not detected for Geode LX video controller
https://bugs.launchpad.net/bugs/156042
You received
Scott reported a few days ago that auto-configuration no longer crashes
(which suggests that Jordan's patch indeed does work), but that X fails
to find the largest available resolution (which suggests a broken DDC
support in X or in this driver.).
--
amd driver fails to autoconfigure
the ability to expand any HOME
value to its correct full path.
--
Martin-Éric Racine
http://q-funk.iki.fi
--
Unable to print to PDF
https://bugs.launchpad.net/bugs/174119
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
of the page you're printing already exists,
it will silently discard the print job
https://bugs.launchpad.net/bugs/161222
You received this bug notification because you are a bug contact for
cups-pdf in ubuntu.
--
Martin-Éric Racine
http://q-funk.iki.fi
--
When printing to PDF, if the name
Yes and I suspect that AppArmor is the cause, since this works fine on
Debian.
On 12/6/07, Tom Haddon [EMAIL PROTECTED] wrote:
The file is not being overwritten or getting a job number appended - it
is being silently dropped...
--
Martin-Éric Racine
http://q-funk.iki.fi
--
When printing
Except that there is no Print Dialog offered by CUPS-PDF. What the user
sees is whichever toolkit some application was built with, sometimes
offering built-in Save To PS capability. It really isn't a CUPS-PDF
issue. This should be reassigned to one of the Xulrunner components.
--
pdf printer
The above configure.in segment is where this starts. I'm suspecting that
other parts of the code need to be modified too.
--
Planner needs transition from libgda2-dev to libgda3-dev
https://bugs.launchpad.net/bugs/182941
You received this bug notification because you are a member of Ubuntu
Bugs,
checking for GDA... configure: error: Package requirements (libgda =
1.0) were not met:
No package 'libgda' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables GDA_CFLAGS
and
I got the above when building with pbuilder, even after autoreconf -v
--install was run. So, the answer is, as Daniel had already pointed out
ages ago, that the upstream code needs to be ported to libgda3; updating
the build-depends is not enough.
--
Planner needs transition from libgda2-dev to
dnl ---
dnl | Database/GDA check |--
dnl ---
AC_ARG_ENABLE(database, [ --enable-database=[no/yes] enable database
support [default=no]], enable_database=$enableval, enable_dat$
if test x$enable_database = xyes ; then
That could work, but it removes the check for libgda-2.0, which is not a
good approach. We would instead need to ADD a check for libgda-3.0.
--
Planner needs transition from libgda2-dev to libgda3-dev
https://bugs.launchpad.net/bugs/182941
You received this bug notification because you are a
Please see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
amd/+bug/140051 for patched drivers (xserver-xorg-core and xserver-xorg-
video-amd) that might solve your issue.
** Summary changed:
- lx800 amd_drv.so(with xorg 1.3) still crashes the screen after ctrl alt BS or
in
This is not a bug. This is a feature: you are trying to build a package
for inclusion in main, using dependencies not available in main; you
need to fetch them from universe. This is a direct result of Ubuntu's
own decision to move libgda2-dev out of main and into universe.
It could also be a
Problems with console switching is a separate issue see
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
amd/+bug/180742 instead.
--
amd driver fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs,
Joe, thank you for reporting on this X.log line. It gets us closer to
finding the exact cause.
Could you attach these items to the bug:
1) The full X.log
2) The output of /usr/share/bug/xserver-xorg-core/script
Also, it would be useful to know the brand of BIOS your ALIX board is
using and
Gideon, just for the record, could you tell us the brand and model of
this GX2 unit?
I'm trying to make a table of all known Geode GX2/LX models on the X.org
wiki, to help the developers track BIOS and hardware vendor -related
issues.
Thanks!
--
xf86-video-amd: switching to a vcons fails
On a Linutop with General Software BIOS (build date: 2007-01-18), DDC
works like a charm and X auto-configuration succeeds too.
Earlier BIOS releases for the Linutop had DDC support disabled and a
serial console instead.
My X.log is attached.
** Attachment added: X.log on a Linutop with General
** Summary changed:
- amd driver fails to autoconfigure
+ xf86-video-amd: fails to autoconfigure
--
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: update-manager (Ubuntu)
Sourcepackagename: upgrade-system = update-manager
--
http://ports.ubuntu.com/ missing from mirrors.cfg
https://bugs.launchpad.net/bugs/184663
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I concur with Pekka.
Here, doing ip addr or ifconfig indeed reported that lo has no IP,
so I inspected /etc/network/interfaces and, sure enough, there was no
stanza for the lo interface. Having fixed this and rebooted, everything
seems back to normal. Kiitoksia, Pekka!
Note that, for some odd
I suspect that AppArmor prevents the overwrite from taking place.
Till: why don't we use SELinux instead of AppArmor? SELinux usage with
CUPS-PDF is fully documented and it works.
--
[Tribe5] cups-pdf do not overwrite existing pdf
https://bugs.launchpad.net/bugs/134671
You received this bug
Guilherme Straioto: you reported that the driver fails on a Brazilian-
made thin client. Could you tell us which brand and version of BIOS is
used to boot it? Thanks!
--
amd driver fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a
Looking at the PDF that Guilherme attached to the bug, it appears that
that Brazilian thin client boots off a General Software BIOS.
--
amd driver fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Jan: did you mean that CUPS should come configured to use the PDF queue
as its default printer?
Fabrizio: this is specified in the configuration file. Note however
that, in practice, AppArmor prevents output to other paths. If you want
to use another output path, you also need to modify AppArmor
There's actually 2 patches against x86emu found in X server = 1.3 that
need to be tested:
http://www.jukie.net/~bart/patches/xorg-server/20080111/0001-X86EMU-
added-blacklist-for-I-O-port-in-0-0xFF-range.patch
and
http://www.jukie.net/~bart/patches/xorg-server/20080111/0001-X86EMU-
I meant confirmation of whether these two x86emu patches fix the bug or
not.
--
amd driver fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: xserver-xorg-video-amd
xserver-xorg-video-amd (2.7.7.5-1) unstable; urgency=low
.
* New upstream release:
+ Basic OLPC support from Bernardo Innocenti and Jordan Crouse.
+ Trivial patch to fix the ZTV module from Martin-Éric Racine
As I recall, Daniel Holbach pointed out earlier that simply updating the
Build-Depends isn't enough to have succesfull gda3 support. The upstream
code itself would need to be upgraded to correctly operate with it. This
is not a trivial task.
--
Planner needs transition from libgda2-dev to
On 1/16/08, Marco Rodrigues [EMAIL PROTECTED] wrote:
Ok.. I've already changed the version check to 1.2.4. I talk with
Oliver, and we also need to check if gda2-postgres in Recommends works
fine.
No. If you upgrade to libgdda3, you also need to upgrade to
gda3-postgres.
--
Martin-Éric
If Daniel can confirm that your patch not only builds cleanly, but also
produces a usable SQL support in Planner, we'll merge it straight into
the Debian package and eliminate the delta between the Debian and Ubuntu
package.
--
Planner needs transition from libgda2-dev to libgda3-dev
I have built Gutsy packages of both xserver-xorg-core and xserver-xorg-
vidoe-amd and uploaded them in my PPA:
https://launchpad.net/%7Eq-funk/+archive
By installing both, GX/LX users should get a functioning driver with DDC
and automatic X configuration. Can subscribers to this bug test this
** Changed in: update-manager (Ubuntu)
Sourcepackagename: upgrade-system = update-manager
--
Cannot sudo.
https://bugs.launchpad.net/bugs/223515
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This seems to be an XFCE4 -specific issue. Reassigning to xfce4
metapackage.
** Changed in: xfce4 (Ubuntu)
Sourcepackagename: numlockx = xfce4
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are
Please note that upstream would be willing to release a new tarball with just
this libDDC patch and autoreconf, calling that 2.9.0.
Would this be acceptable as an SRU for 8.04.1?
The main advantage of upstream applying the patch and running autoreconf
for us is that we'd keep the diff to a
Rolf, I have looked at the whole thread. The point is, it works fine on
GNOME and, according to someone at work, also on KDE. So, yes, it is an
XFCE issue.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification
and setting to confirmed. It looks like we are not
100% sure where and when this can and cannot be reproduced.
Agreed on setting to Confirmed until a positive cause has been found.
--
Martin-Éric Racine
http://q-funk.iki.fi
--
[hardy] numlockx does not turn num lock keyboard light on.
https
On Fri, May 2, 2008 at 10:07 PM, luvr wrote:
Martin-Éric Racine wrote:
Hence why I am veering towards blaming XFCE for skipping the X startup
script.
The issue is that XCFE will not turn the keyboard LED on. You can easily
verify this by running the command numlockx on manually from
into Debian.
Changelog since current intrepid version 2.7-4ubuntu1:
mkelfimage (2.7-5) unstable; urgency=low
* Enabled Arch: lpia.
* W: package-contains-empty-directory usr/share/mkelfImage/elf32-i386/
-- Martin-Éric Racine [EMAIL PROTECTED] Fri, 18 Apr 2008 13:41:52 +0300
-BEGIN PGP
Billy, can you please try the following:
1) add the following lines to /etc/apt/sources.list:
deb http://ppa.launchpad.net/q-funk/ubuntu hardy main
deb-src http://ppa.launchpad.net/q-funk/ubuntu hardy main
2) sudo apt-get install xserver-xorg-video-amd=2.7.7.8-0ubuntu1.
3) Edit
Revised instructions would be:
1) add the following lines to /etc/apt/sources.list:
deb http://ppa.launchpad.net/q-funk/ubuntu hardy main
deb-src http://ppa.launchpad.net/q-funk/ubuntu hardy main
2) sudo apt-get update
3) sudo dpkg -P --force-depends xserver-xorg-video-amd
Billy, just to be safe, can you paste the result of the following
command to this bug:
sudo lspci -v
--
xf86-video-amd: fails to autoconfigure
https://bugs.launchpad.net/bugs/140051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: update-manager (Ubuntu)
Sourcepackagename: upgrade-system = update-manager
--
Upgrade tool fails to recover after kernel panic in mid-upgrade
https://bugs.launchpad.net/bugs/226967
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Billy, thanks for the lspci output.
Could you tell us what brand and model number that laptop is, so that we
can look up the specifications ourselves?
** Changed in: xserver-xorg-video-geode (Ubuntu)
Sourcepackagename: xserver-xorg-video-amd = xserver-xorg-video-geode
--
xf86-video-amd: fails
Jordan of AMD pointed out that, according to your Xorg.log, AmdProbe is
calling xf86MatchDevice and that is failing. The only reasons he can
think of this ever happening is whenever the BIOS has no VSA layer (or
equivalent feature) and no /dev/cpu/0/msr.
Billy, as a test, can you perform the
Steve, I have kept the diff as small as humanely possible. This being
said, fixing both packaging issues and hardware issues within the scope
of the same SRU has not been easy. My apologies if it's still too big
to fit the constraints of an SRU.
One important thing to keep in mind is to avoid
We'd need the updated -all and -geode for the conflict to not happen
during testing.
--
please add geode to driver list in hw/xfree86/common/xf86AutoConfig.c
https://bugs.launchpad.net/bugs/219630
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
-geode is also in sync with the newer Debian 2.10.0-3 in Intrepid.
--
please add geode to driver list in hw/xfree86/common/xf86AutoConfig.c
https://bugs.launchpad.net/bugs/219630
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
unimatrix, exactly which packages did you upgrade and to which versions?
On exactly what thin client hardware (brand name, manufacturer, model)?
--
please add geode to driver list in hw/xfree86/common/xf86AutoConfig.c
https://bugs.launchpad.net/bugs/219630
You received this bug notification
In that case, it's an entirely different issue than the one being discussed
here.
Please file a new bug against package 'xorg' and explain the issue again there.
--
please add geode to driver list in hw/xfree86/common/xf86AutoConfig.c
https://bugs.launchpad.net/bugs/219630
You received this
For NSC, it looks good - although I would have felt safer removing Cyrix
ID numbers.
For GEODE, the Conflicts against NSC has the wrong version. It should be
new NSC with the fixed ID, including the 1: epoch.
--
please add geode to driver list in hw/xfree86/common/xf86AutoConfig.c
NO! Deploying without removing the symbolic link is exactly what we want
to avoid. The symbolic link MUST GO. This is already verified. Let's not
make the same mistake as for 2.1, shall we?
--
please add geode to driver list in hw/xfree86/common/xf86AutoConfig.c
I thought that it had been discussed to oblivion but, much to my
amazement, nobody seems to remember why dropping the symbolic link is
essential:
The symbolic link creates PCI conflicts too, because both the driver and
the one called via the symbolic link claim support for the same chips.
So,
Guys, please don't do this. This has been abundantly tested enough as it
is, by myself and others. The symlink causes too many problems. It was
removed for good reasons. Do NOT re-introduce it!
--
please add geode to driver list in hw/xfree86/common/xf86AutoConfig.c
Steve, no, blacklisting the framebuffer module doesn't fix the issue.
However, if you REALLY insist on keeping the symbolic link, then at
least make it purgeable by putting it in the -amd transitional package,
not in the main -geode package.
--
please add geode to driver list in
Oliver hasn't specified the system on which he tested this, so I cannot
comment on his results.
However, I have tested this on a variety of Geode-based systems by a
variety of vendors and found the exact same behavior on each of them:
that leaving the symbolic link confuses X, while removing it
Oliver, I'm sorry but I haven't observed this behavior you describe on
any of the LX hardware I have access to.
However, removing the symbolic link solved the issue on each and every
LX hardware I tested, while leaving it prevented X from launching, again
on every LX hardware I have access to.
Oliver, please note that now that xserver-xorg-video-all finally Depends
on -geode rather than -amd, it should be possible to build a clean
chroot that will work out of the box, since the symbolic link will not
be present in -geode. Thus, this should finally work OK with the
packages currently in
*** This bug is a duplicate of bug 214119 ***
https://bugs.launchpad.net/bugs/214119
Please note that you must install the updated drivers inside the chroot
that is used to build boot images and then rebuild the image afterwards:
1) sudo chroot /opt/ltsp/i386/
2) mount -t proc proc /proc
3)
in this package, until further notice.
-- Martin-Éric Racine [EMAIL PROTECTED] Thu, 29 May 2008 21:02:18 +0300
xserver-xorg-video-geode (2.9.0-2) unstable; urgency=low
* Moved backward-compatibility symbolic links to AMD package.
* Added a versioned Conflicts/Replaces against 2.9.0-2 to match
While Debian's 2.9.0-3 works for Intrepid, fixing Hardy instead requires
the 2.9.0-3ubuntu2 from my PPA.
--
Please sync xserver-xorg-video-geode 2.9.0-3 (main) from Debian unstable (main).
https://bugs.launchpad.net/bugs/236942
You received this bug notification because you are a member of
What if you try 2.9.0-3ubuntu2 from my PPA? Once you install -geode,
please purge -amd to be sure. Does it help any?
An additional question: what is the hardware on which you get this bug?
Manufacturer? Brand name? Model number?
--
geode driver gives corrupt output
Which kernel are you using? Can you do uname -a from a terminal?
** Changed in: ubuntu
Sourcepackagename: upgrade-system = None
--
Hardy upgrade from Gutsy wireless problem
https://bugs.launchpad.net/bugs/237202
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: ubuntu
Sourcepackagename: upgrade-system = None
--
upgrade fails dapper to edgy
https://bugs.launchpad.net/bugs/236732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Steve, my understanding is that David Bensimon at Canonical has been
testing for various Geode issues. He might be able to answer this.
--
please add geode to driver list in hw/xfree86/common/xf86AutoConfig.c
https://bugs.launchpad.net/bugs/219630
You received this bug notification because you
PS: I forgot to mention that the way Debian and Ubuntu handle PCI ID
matching seems to differ from upstream's intended method in some ways.
Since finding out about this, I have produced two proposed fixes, both
sitting in my PPA:
1) an updated -geode package that uses the Debian/Ubuntu-specific
On Tue, Jun 10, 2008 at 10:13 AM, Martin Pitt wrote:
Martin-Eric, can you please minimal debdiffs with appropriate changelogs
here? I'll sponsor them.
For NSC, that's easy enough, since I started from what's currently in
Hardy.
For GEODE, just to be safe, comparing to which version should I
301 - 400 of 2493 matches
Mail list logo
