Hi All,
This bug was reported a while ago but there hasn't been any recent
activity. Just curious if this is still an issue with the latest Hardy
Heron 8.04 Alpha release? http://www.ubuntu.com/testing . Note that
we'll keep this open against the actively developed kernel bug against
2.6.20 thi
On Dec 29, 2007 1:06 PM, carrasclin <[EMAIL PROTECTED]> wrote:
> I'am wondering if this issue has something to do with this other bug
> report I've posted recently https://bugs.launchpad.net/ubuntu/+source
> /module-assistant/+bug/178789
On further inspection, it seems your problems are actually n
On Dec 29, 2007 1:06 PM, carrasclin <[EMAIL PROTECTED]> wrote:
> I'am wondering if this issue has something to do with this other bug
> report I've posted recently https://bugs.launchpad.net/ubuntu/+source
> /module-assistant/+bug/178789
Looks similar. A lot of drivers are affected by this change
I'am wondering if this issue has something to do with this other bug
report I've posted recently https://bugs.launchpad.net/ubuntu/+source
/module-assistant/+bug/178789
By the way I've returned to Official Debian Etch and all this sorts of
problems have gone away. I know this is no the place to ge
> Wateenellende? That is funny :-)
It's quite accurate
> Actually, I think this package might be obsolete. You can download
> the driver from ATI, do some magic with it and it spits out a debian
> package which includes kernel source code for the latest driver. This
> actually worked out of
Wateenellende? That is funny :-)
Actually, I think this package might be obsolete. You can download
the driver from ATI, do some magic with it and it spits out a debian
package which includes kernel source code for the latest driver. This
actually worked out of the box for me.
Google tells me:
Problem still present in gutsy.
Tried to send an email to the maintainer - his email address does not exists
anymore.
Hereby for any maintainer that might stumble upon it.
Hello,
are you still the maintainer for the fglrx-source ? If so, please find
attached a patch which solves some of the pro
to ilustrate that it also happens in the latest restricted modules
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.15 =>
linux-restricted-modules-2.6.20
--
Build of fglrx module fails
https://bugs.launchpad.net/bugs/45563
You received this
Why is there a fglrx kernel module in the linux-restricted-
modules-2.6.17-10-generic package? And how can I build the restricted
modules package myself for my own kernel?
The kernel-source-fglrx is not used to build the standard ubuntu kernel,
so I suppose this package is pretty uninteresting to
Also in the kernel 2.6.20-2-generic with... are they doing something
about that??? why there isn't someone assigned to this bug if it is so
important?? -.-
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Also in the kernel 2.6.20-2-generic with feisty... are they doing
something about that??? why there isn't someone assigned to this bug if
it is so important?? -.-
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Bug still there and it is also in the kernel 2.6.19-7-generic with feisty
see bug 75208
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi. Just reporting that the bug still exists.
I am trying to compile fglrx for dapper's stock kernel (see bug 70225
for reason not using stock binary).
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
Apperantly this bug is a very low priority for the DEVs! Since they
haven't fixed it for more than 4months! And the bug apperantly still
exist in the new release :(
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
it's still not fixed ... in edgy
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Attached my patch to get it going on 2.6.18.
As far as I could determine the changes to fglrx/build_mod/make.sh and
fglrx/build_mod/firegl_public.c are only required for sufficiently new
kernels (where VM_SHM was removed and UTS_RELEASE was moved out of
linux/version.h). For earlier kernels you s
debian/changelog says that "packaging is derieved from nvidia-kernel-source",
and it looks like there's much nvidia stuff that should actually ati specific?
$ grep nvidia debian/* | grep -v changelog:
debian/copyright:Sat, 27 Nov 12:56:49 +. It is heavily based on the
nvidia-kernel packagi
I 2 have tried the official UBUNTU kernel and also the VANILAs and on none of
the kernel this works. And also lots of ppl report the same bahaviour in
UBUNTUFORUMS.ORG.
So the only workarround is to use FGLRX from ATI.COM and instruct FGLRXs
installer to spit out FGLRX-KERNEL-SOURCE. And then U
Just to confirm, I'm also running a custom kernel built from the Ubuntu
2.6.15 source, not a vanilla kernel compile. I only recompiled to patch
in linux-phc (undervolting) and in the process did some basic config
tweaks, but all the Ubuntu patches are in there as with the stock
kernel. I'm sure if
I never spoke about non official kernels. I used always sources from
linux-source-2.6.15 from ubuntu dapper repository.
Try to make the modules with a precompiled kernel with module-assistant. You
will find that it will fail in the same way as with other kernels.
It's a packaging problem, not a
> We all here are using the Debian/Ubuntu way for building the kernel and
> it is not working. So here are the non-ubuntu sources?
No, in your case it could be a real bug - setting the status of this bug
to confirmed.
status Confirmed
** Changed in: linux-restricted-modules-2.6.15 (Ubuntu)
My bad, i refresh the page and i came up with all this posts sorry.
Guido: I'm trying to build a custom kernel and i cant make it work
either so i think at least that should be supported, no?
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs
I'm sorry. But i'm using Ubuntu-sources and i can't build my kernel with the
fglrx module.
We all here are using the Debian/Ubuntu way for building the kernel and
it is not working. So here are the non-ubuntu sources?
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bu
I'm sorry. But i'm using Ubuntu-sources and i can't build my kernel with the
fglrx module.
We all here are using the Debian/Ubuntu way for building the kernel and
it is not working. So here are the non-ubuntu sources?
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bu
> > However, it was not possible to build the module for custom kernels
> > from this.
>
> How's that not using non-ubuntu sources?
Ah ok, now I got you. Yes, you're right, I used a vanilla kernel source
(dapper default kernel is not working at all on my hw). However, I
thought the fglrx-kernel-
I'm sorry. But i'm using Ubuntu-sources and i can't build my kernel with the
fglrx module.
We all here are using the Debian/Ubuntu way for building the kernel and
it is not working. So here are the non-ubuntu sources?
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bu
> However, it was not possible to build the module for custom kernels
> from this.
How's that not using non-ubuntu sources?
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
Nope, we tried to use the fglrx-kernel-source package, which is part of
the "restricted" component. However, it was not possible to build the
module for custom kernels from this. I just mentioned a solution using
the ATI installer that is working for me, but this does not solve the
original problem
Thanks again, Emilio, for the clarification, but only Guido's tip seems
to help me. Still I have to work on it more to see if I can get all
packages installed.
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
@ashrack: please calm down... ubuntu devs have a lot of work to do and
this bug is not very urgent since most of the people using Ubuntu on the
desktop will not need to recompile their kernel at all. However, I
agree, it should be solved "somewhen".
BTW: I managed to get that fglrx module compile
UBUNTU DEVs should care about modules creation. What kind of OS is it
then that I cant build a module for my custom build kernel?ΕΎ
Is there a way to somehow force them or something for them to
respond??!!
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing lis
after you've modified the file, you can run:
sudo module-assistant build fglrx-kernel
it will not extract the tarball another time, because it will find the
sources in /usr/src/modules and will create the package containing the
compiled module.
--
Build of fglrx module fails
https://launchpad.ne
Well, I still can't figure this out. Changing "control. template" allows
me to issue either a "make" or "sh make.sh" command, but once files are
generated, I don't know how to install them. Trying to use module-
assistant just fails like it did before. I even unpacked the tarball,
modified "control
Thanks for the clarification, Emilio
I think you're right that this problem affects the building of maybe any
module against a custom kernel, and isn't a problem with the fglrx
driver.
Also, you may be right about Ubuntu devs not caring about problems with
custom kernels. They should care, howeve
You should download ati-installer, build dapper packages, install only the
fglrx-kernel-source package. The you must decompress fglrx-kernel-source.tar.gz
in /usr/src.
The you have to edit /usr/src/modules/fglrx/debian/control.template to match
this:
Source: fglrx-installer
Section: restricted
P
its almost a month since the first bug report was made for this bug and still
no DEV have answered here.
Do U guys think that they are even aware of this bugs or are they just quietly
waiting for the next FGLRX drivers to come out and "hopefully" they will get it
right. If this is the case it w
Same problem here, and it's up on ubuntuforums, too.
Emisca, could you elaborate on your workaround? How did you change the
version number in your fglrx-kernel-source?
Thanks.
--
Build of fglrx module fails
https://launchpad.net/bugs/45563
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
37 matches
Mail list logo
