Today's karmic-desktop.iso image file boots just fine.
--
Karmic desktop CD fails to boot because of different squashfs versions
https://bugs.launchpad.net/bugs/375352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
RE: Goldy wrote ..
Please stop spamming this bug report! Your ranting is complete nonsense given
that Ubuntu 9.10 (which is -not- Ubuntu 9.05) is at an early alpha stage. Btw,
it is still possible to install from the alternate install media which is what
I have done successfully. If you want
Public bug reported:
Binary package hint: squashfs-tools
The AMD64 desktop snapshot of Ubuntu 9.10 as of 2009-05-12 fails to boot
because the squashfs versions of the live image [3.1] and that of the
kernel [4.0] are different. During boot, the kernel complains
"SQUASHFS error: Major/Minor m
Issue fixed for current daily-live spin including vim-
gnome-7.2.079-1ubuntu4. I suppose it was a PA or GNOME issue but the
important thing is that it is settled now.
--
vim-gnome freezing from any GTK event at Jaunty
https://bugs.launchpad.net/bugs/308713
You received this bug notification becau
- I have observed the same issue for snapshot of the Ubuntu 9.04 desktop
spin as of 2009-01-20.
- The same issue occurs on current Fedora 10, see
https://bugzilla.redhat.com/show_bug.cgi?id=463908 .
consequently, this bug should already have occured in Ubuntu 8.10
based upon GNOME 2.24.x.
Issue was already solved in Gutsy. A current live CD works nicely, too. Package
info:
- kernel 2.6.27-2-generic
- X.Org 1.4.99.906 (1.5.0 RC 6)
I suggest to close this bug as being solved.
--
drmMap libGL error on "SuperSavage/IXC 64" and "Xorg 7.2"
https://bugs.launchpad.net/bugs/88905
You rece
For recent releases including Ubuntu 8.0.4.1 LTS, desktop effects refused to be
enabled at all. Today, I have booted the current Intrepid live CD on my old
system sporting an R100 QD [Radeon 7200], and actually, desktop effects can be
enabled now. The whole screen [EMAIL PROTECTED] is used corre
This issue is still present for Ubuntu 8.0.4.1 LTS (Hardy Heron). I have read
elsewhere that NM requires a recent version of wireless extensions not
supported by the current ACX driver (v0.3.36).
I am using a D-Link DWL-G520+ rev. A3, and after disabling NM, I am able to
bring up wlan0 with dhcl
*** This bug is a duplicate of bug 66679 ***
https://bugs.launchpad.net/bugs/66679
Public bug reported:
Binary package hint: xfce4-cpu-freq-plugin
Release: Ubuntu 8.04
Package: xfce4-cpu-freq-plugin-0.0.1-0ubuntu2
The "Properties" dialog of XFCE4 CPU frequency plugin allows to check
"Show C
System still crashes shortly after booting the AMD64 live CD as of
2008-03-19. Adding vga=792 to the boot line cures the problem.
--
Feisty crashes after grub, before boot process, if usplash is enabled (amd64)
https://bugs.launchpad.net/bugs/8
You received this bug notification because you a
Current Hardy/AMD64 live CDs [e.g. of 2007-12-31] crash my system, too.
Directly after validating the boot options, the screen goes blank, and after a
few seconds, the system simply starts over again.
The mainboard is a Tyan S2865AG2NRF [chipset NForce4 Ultra] equipped with an
ATI X800 GT PCIe g
For a fully updated Gutsy system as of 2007-10-15, I still have these
artifacts [see attached screenshot]. The graphics device is an onboard
"Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics
Device [8086:2562] (rev 03)".
** Attachment added: "White border compiz artifacts o
I have tested ACX111 support with yesterday's Gutsy live CD, and the
driver works well with my DWL-G520+ adapter.
NM doesn't pick up the network. However, it's possible to set up a WLAN
connection in the 'old fashioned' way although this requires some
tweaking. In a first time, the adapter doesn't
Where are the error messages that you are talking about? The 'dmesg'
output doesn't look complete. In my case, error messages appear after
the 'NET: Registered protocol family ..' line and read:
[ 823.768203] wlan0: association FAILED: peer sent Status Code 18
(Assoc denied: requesting STA doesnt
No activity does not mean that the issue has been settled. As a matter
of fact, 3D effects do not get enabled on my 'Radeon 7200' board because
of the reasons outlined above. I do not know of any distribution which
has fixed this issue ('Fedora' clearly hasn't).
I had posted earlier that adding a
Public bug reported:
Binary package hint: xserver-xorg-video-ati
For ATI driver version 6.7.191 and later, X crashes when a single CRT is
connected to an R100 based video adapter. The monitor powers off, and
the system needs to be shut down/rebooted by means of ctrl-alt-del. A
backtrace appears a
*** This bug is a duplicate of bug 118539 ***
https://bugs.launchpad.net/bugs/118539
It turns out that master bug #118539 is effectively resolved by using
the current snapshot
http://www.hauke-m.de/fileadmin/acx/acx-20070610.tar.bz2
after copying the firmware file to /lib/firmware/`una
*** This bug is a duplicate of bug 118539 ***
https://bugs.launchpad.net/bugs/118539
As I had pointed out in Bug #118539, this issue is essentially solved
and was due to ACX sources from early 2007 which do not take into
account the new mac80211 wireless stack of the 2.6.22 kernel whereas
snap
Using the current "Fedora" development tree, that's hard to tell for me. Here,
"hotplug" is not used at all. What I can state is that on my sytem, the
firmware can be found at "/lib/firmware/tiacx111c16". You might want to try
copying your firmware file to this location or have a look at the "ho
*** This bug is a duplicate of bug 118539 ***
https://bugs.launchpad.net/bugs/118539
Driver snapshot "acx-20070101" is not compatible with the new "mac80211"
wireless stack of kernel version 2.6.22.x and later. However, there is a
modified version by Hauke available at
http://www.hauke-m.
Driver snapshot "acx-20070101" is not compatible with the new "mac80211"
wireless stack of kernel version 2.6.22.x and later. However, there is a
modified version by Hauke available at
http://www.hauke-m.de/fileadmin/acx/acx-20070610.tar.bz2 .
This one builds and works nicely for me up to the
** Attachment added: "lspci -vvnn output file for 2.6.22-9-generic and an
acx111 based WLAN card"
http://launchpadlibrarian.net/8706646/lspci-vvnn-2.6.22-9-generic.log
--
modprobe acx on Kubuntu gusty fail
https://bugs.launchpad.net/bugs/127521
You received this bug notification because you
Same here for a D-Link DWL-G520+ WLAN card based upon the ACX111
controller for kernel version 2.6.22-9-generic. Has the Ubuntu driver
already been updapted to the mac80211 compatible snapshot available at
http://www.hauke-m.de/fileadmin/acx/acx-20070610.tar.bz2 ?
If not, this might be the re
I also have trouble using a 'D-Link DWL-G520+' card with 'feisty'. The
kernel spawns messages like the following over and over again:
'[ 387.488260] wlan0: association FAILED: peer sent Status Code 18 (Assoc
denied
: requesting STA doesnt support all data rates in basic set)'
However, ther
@aquo: I recommend you to install the current development kernel
2.6.22-7 from the Gutsy tree in addition to 2.6.20-15/16. For that one
the drm problem has been clearly fixed upstream.
--
drmMap libGL error on "SuperSavage/IXC 64" and "Xorg 7.2"
https://bugs.launchpad.net/bugs/88905
You received
I have the same problem with a "Radeon 7200" [R100] card for the current
"daily-live" image. The screen is completely unresponsive then, and I actually
need to kill the "X" server, because the screen is completely messed up, and
the desktop does not even fall back to "non-compiz" mode.
In my cas
Issue fixed for me by kernel "2.6.22-rc3-git6".
--
drmMap libGL error on "SuperSavage/IXC 64" and "Xorg 7.2"
https://bugs.launchpad.net/bugs/88905
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-
@ catchit:
This bug is not for you **unless** you observe the already well-known "libGL
error: drmMap of framebuffer failed .." when executing "glxgears/glxinfo",
preferably after setting "LIBGL_DEBUG" to "verbose". Since you do not seem to
encounter this message, you have benn bitten by a dif
@ Tom Shaw :
I am running an "IBM ThinkPad T23" connected to an external monitor at "[EMAIL
PROTECTED]" with hardware rendering up and running which is clearly possible
for this model sporting 16 MB of video memory.
--
No hardware rendering for "SuperSavage/IXC 64" and "Xorg 7.2"
https://bugs.l
@ Tom Shaw :
The hint concerning the video memory was already given in comment 17. The
important thing to retain is that in this case, already "Xorg.0.log" reports
that direct rendering is disabled due to insufficient video memory! In
"catchit's" case, however, this seems to be ok, whereas "glxi
@ Carbonfish:
As I have pointed out several comments above, the procedure is for
instance described here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393266;msg=37;att=0
The current "git" tree is fully functional. So, just go ahead!
--
No hardware rendering for "SuperSavage/IXC 64" an
>It seems that the "savage_dri.so" file was not in the
>expected path after "depmod -a" was executed, so it
>couldn't be loaded.
The "depmod" command has nothing to do with the "Xorg" driver module
"savage_dri.so". It only ensures that new kernel modules "drm.ko" and
"savage.ko" do get used instea
@catchit
What model is your notebook exactly? Is direct rendering supported by
the "X" server as reported in "Xorg.0.log"? Did you ever manage to get
direct rendering work for previous releases? Do you still obtain the
error message:
...
libGL error: drmMap of framebuffer failed (Invalid argumen
** Attachment removed: "DRM snapshot 07-02-25"
http://librarian.launchpad.net/7385621/linux-core.tar.bz2
** Attachment added: "freedesktop DRM snapshot as of 07-02-25."
http://librarian.launchpad.net/7385659/drm.tar.bz2
--
No hardware rendering for "SuperSavage/IXC 64" and "Xorg 7.2"
htt
Simply unpack the attachment, go to "linux-core" and type 'make
DRM_MODULES="savage"' to build "drm.ko" and "savage.ko" or simply type
"make" to build all the kernel modules. Make sure to load the new
modules "drm.ko" and "savage.ko" before the "X" server starts or simply
replace the original ones
No, this is not a new "Ubuntu" bug. It also happens on "Fedora". I am
sorry that I completely forgot about that issue that I encounter myself
when using the current tree. I am using an older snapshot that compiles
correctly. Try to checkout the "DRM" branch as of about 2 months ago.
That one should
The procedure is for instance described here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393266;msg=37;att=0
--
No hardware rendering for "SuperSavage/IXC 64" and "Xorg 7.2"
https://bugs.launchpad.net/bugs/88905
You received this bug notification because you are a member of Ubuntu
Bugs
This is a duplicate of bug #88905. There you also find the reference to
the upstream bug http://bugzilla.kernel.org/show_bug.cgi?id=7767 that I
had reported back in January 2007.
--
Regression in savage DRM support
https://bugs.launchpad.net/bugs/99251
You received this bug notification because y
Still broken in kernel "2.6.20-12-generic". This probably won't work out
for "feisty" final ...
--
No hardware rendering for "SuperSavage/IXC 64" and "Xorg 7.2"
https://launchpad.net/bugs/88905
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
Public bug reported:
Binary package hint: kernel-image-2.6.20-9-generic-di
Hardware rendering is broken for "SuperSavage/IXC 64" and "Xorg 7.2" in
the current "feisty" tree. On my "IBM ThinkPad T23", "glxinfo" now
reports:
...
libGL error: drmMap of framebuffer failed (Invalid argument)
libGL er
40 matches
Mail list logo
