0.8.4-4 should be making its way out to the Debian archives shortly.
Probably won't make it into wheezy but it seems to be a non-issue in
wheezy currently and pre-emptively fixes an FTBFS in wheezy+1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
It built fine on amd64 in a current sid pbuilder prior to upload to
Debian. I'll try and find time to take a look at this on an Ubuntu/amd64
box and work out what's going on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Changed in: blcr (Ubuntu)
Assignee: (unassigned) => Alan Woodland (awoodland)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/804943
Title:
blcr kernel module failed to build with kernel
2.6.39+ support currently has two known issues:
https://hpcrdm.lbl.gov/pipermail/checkpoint/2011-October/000334.html
I think they're both things I should be able to handle although the BKL
removal has the potential to introduce some hard to debug problems. All
going well though it might be possibl
There's an updated package currently awaiting build in my PPA that adds
support for kernels up to and including 2.6.38 (i.e. Natty) -
https://launchpad.net/~awoodland/+archive/blcr/+sourcepub/1980069
/+listing-archive-extra
It passed all the tests it should on my test machine and is an official
up
No news yet and the patch in testing only goes to 2.6.35 right now. I have a
suspicion the timing will match the next debian freeze so an ubuntu specific
patch to break the dependency change probably makes most sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
On 21 April 2011 17:17, pablomme wrote:
> Could somebody please change the openmpi-bin package dependency on
> openmpi-checkpoint from "recommends" to "suggests", to stop the flood of
> duplicates? This is what most commonly pulls blcr-dkms, which is non
> functional since kernel 2.6.35 and its fa
Turns out this driver is actually pretty redundant (for me at least)
since 2.6.29 anyway - gspca_stv06xx seems to support all of the hardware
that I have which used to use qc-usb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Patch added: "Patch to look in generated/ instead of linux/ for auto
generated headers"
https://bugs.launchpad.net/bugs/706321/+attachment/1803209/+files/qc-usb-2.6.35.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
Linux kernels > 2.6.32 moved several include files that are generated
automatically from linux/* to generated/*. This patch causes qc-usb-
source to look in the appropriate place (and hence build again) on these
kernels.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: q
That would be quite a sensible fix to stem the tide of bug reports in
Ubuntu. 0.8.2-14 should fix this for kernels upto and including 2.6.34,
however I've not yet managed to fix builds for 2.6.35, so this would be
worth having still.
--
package blcr-dkms does not support 2.6.33 or more recent ker
libcr0 will behave sanely if the kernel modules are not available. The
extent of this is to return appropriate error codes from API calls
though, rather than actually being useful, hence the recommends there.
I originally took the view that most MPI "users" were probably sysadmins
setting up clust
I am testing packages with support for kernels < 2.6.35 now. 2.6.35
support is probably someway off still. Since as I understand it the
forthcoming release will be using 2.6.35 it probably makes sense to make
this change on Ubuntu.
Alan
--
package blcr-dkms does not support 2.6.33 or more recent
*** This bug is a duplicate of bug 572012 ***
https://bugs.launchpad.net/bugs/572012
** This bug has been marked a duplicate of bug 572012
package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module
failed to build
--
package blcr-dkms 0.8.2-10 failed to install/upgrade: blc
*** This bug is a duplicate of bug 572012 ***
https://bugs.launchpad.net/bugs/572012
** This bug has been marked a duplicate of bug 572012
package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module
failed to build
--
package blcr-dkms 0.8.2-10 failed to install/upgrade: blc
*** This bug is a duplicate of bug 555729 ***
https://bugs.launchpad.net/bugs/555729
** This bug has been marked a duplicate of bug 555729
package blcr-dkms does not support 2.6.33 or more recent kernels
--
package blcr-dkms 0.8.2-13 failed to install/upgrade: blcr kernel module failed
t
*** This bug is a duplicate of bug 572012 ***
https://bugs.launchpad.net/bugs/572012
** This bug has been marked a duplicate of bug 572012
package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module
failed to build
--
package blcr-dkms 0.8.2-10 failed to install/upgrade: blc
*** This bug is a duplicate of bug 572012 ***
https://bugs.launchpad.net/bugs/572012
** This bug has been marked a duplicate of bug 572012
package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module
failed to build
--
package blcr-dkms 0.8.2-10 failed to install/upgrade: blc
It looks like you're trying to build for a kernel that's not currently
installed.
Alan
--
package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed
to build
https://bugs.launchpad.net/bugs/586875
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Summary changed:
- package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module
failed to build
+ package blcr-dkms does not support 2.6.33 or more recent kernels
--
package blcr-dkms does not support 2.6.33 or more recent kernels
https://bugs.launchpad.net/bugs/555729
You receiv
This is also reported in Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573112
** Bug watch added: Debian Bug tracker #573112
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573112
--
package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed
to build
https://
ailed to build
** Changed in: blcr (Ubuntu)
Status: New => In Progress
** Changed in: blcr (Ubuntu)
Assignee: (unassigned) => Alan Woodland (awoodland)
--
package blcr-dkms 0.8.2-11 failed to install/upgrade: blcr kernel module failed
to build
https://bugs.launchpad.net/bugs
>From the log it looks like you're trying to build for a kernel which
doesn't have the System.map installed - BLCR needs this in order to be
able to build.
Alan
--
package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed
to build
https://bugs.launchpad.net/bugs/572012
You
** Changed in: blcr (Ubuntu)
Status: New => In Progress
** Changed in: blcr (Ubuntu)
Assignee: (unassigned) => Alan Woodland (awoodland)
--
package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed
to build
https://bugs.launchpad.net/bugs/555729
You re
Hi, blcr is currently known to not work with kernel 2.6.33 or newer.
Upstream and I are working on a patch for this but it's non trivial.
Alan
On 4/5/10, Scott Lockwood wrote:
> Public bug reported:
>
> 1)
> Description: Ubuntu lucid (development branch)
> Release: 10.04
>
> 2)
> blcr-dkms
Public bug reported:
Changes:
blcr (0.8.2-10) unstable; urgency=low
.
* Add patch from Paul Hargrove that fixes builds on linux-rt
- Fixes build dkms build failure with linux-rt kernels.
- Required autoreconf run
LP: #534175
* Bump to standards version 3.8.4, no changes n
** Changed in: blcr (Ubuntu)
Status: In Progress => Fix Committed
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed
to build against linux-rt kernel
https://bugs.launchpad.net/bugs/534175
You received this bug notification because you are a member of Ubuntu
Of course when I said -lp I really meant -rt...
New version has just been uploaded to Debian/Unstable. Will request
getting it pulled into Lucid later today.
Alan
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed
to build against linux-rt kernel
https://bugs.lau
It was the Ubuntu freeze I was unsure about. I'm preparing -10 now with
the patch for -lp kernels. I've checked up and there shouldn't be a
problem for getting the fix pulled across from Debian. Once that hits
testing and lucid I'll do another revision which adds an extra package
with the testsuite
** Changed in: blcr (Ubuntu)
Status: New => Invalid
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed
to build - Segmentation fault (core dumped)
https://bugs.launchpad.net/bugs/531255
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: blcr (Ubuntu)
Status: New => In Progress
** Changed in: blcr (Ubuntu)
Assignee: (unassigned) => Alan Woodland (awoodland)
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed
to build against linux-rt kernel
https://bugs.launchp
I will definitely wait for an ack on the functionality of the resulting
patch. Seems odd that it would end up missing those macros.
If it works manually it should work with DKMS, all the bits do (in a
slightly odd way) is call configure for the appropriate kernel and make,
dressed up like a non-au
apt-get source linux-image-2.6.28-3-rt
(Oddly this package is at version 2.6.31-9.152)
linux-rt appears to be a meta-package which depends upon the latest
linux-image-X-rt. I've never looked at the -rt packages until today.
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel mod
>From a quick look just now it looks like it should be possible to add
support for this branch. I don't have enough time to develop and test
this right now though, but I'll forward the report upstream.
Alan
--
package blcr-dkms 0.8.2-9 failed to install/upgrade: blcr kernel module failed
to bui
BLCR can in theory build against almost any standard 2.6.X kernel. I
have no idea what -rt changes internally though. Do you have a
config.log from the failed configure attempt that you could attach to
this report?
As for nvidia modules not getting built because of this I'd say that was
a bug with
The odd thing is when it fails disabling NM, using wpa_supplicant
manually and then re-enabling NM causes NM to work again (reliably too)
--
wpa_supplicant wifi connection gets disconnected with tls_connection_handshake
https://bugs.launchpad.net/bugs/338362
You received this bug notification bec
The fix for this in 0.8.2-9 has hit testing now, so as soon as that gets
pulled across...
--
fails to build on armel/lucid
https://bugs.launchpad.net/bugs/503185
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
2010/1/18 Dave Martin :
> I managed to build the kernel modules against the linux-fsl-imx51
> headers and install them; make check then ran, using the configure args
> you suggest (I added --prefix=/usr --mandir=/usr/share/man for
> consistency with the package build proper, but I doubt this affect
2010/1/18 Dave Martin :
> I get a successful build, but I'm not sure how to run the testsuite.
> Any ideas?
Testsuite needs to be built separately using:
./configure --with-installed-libcr --with-installed-modules && make
check IIRC. There's a bug in the current release which prevents
--with-insta
2010/1/5 Paul H. Hargrove :
> Alan,
>
> I believe you are mistaken in reading the comments to imply "we
> shouldn['t] be using __kernel_cmpxchg on newer kernels anyway". That
> feature became available in 2.6.12 and before that there was no way to
> perform an atomic operation from user code w/
Hi,
I noticed today that BLCR is failing to build on armel on Ubuntu. This
problem is reported in [1]. It would seem that ARMv7 no longer
includes swp/swpne instructions. It's relatively trivial to
conditionally replace this with appropriate ldrex/strex instructions
instead though. Before I produc
Further research indicates that SWP has been deprecated and subsequently
dropped from the instruction set in newer arm processors:
http://www.doulos.com/knowhow/arm/Hints_and_Tips/Implementing_Semaphores/
I'll see about putting together a patch with upstream to correct this.
--
fails to build o
Am I correct in thinking armel for Ubuntu is targeting a different arm
varient than armel in Debian then? Any arm gurus know of an easy
workaround?
It builds fine on armel Debian:
https://buildd.debian.org/fetch.cgi?pkg=blcr;ver=0.8.2-7;arch=armel;stamp=1261371421
--
fails to build on armel/lu
Looks like you're missing the linux-headers-`uname -r` package perhaps?
--
package blcr-dkms 0.8.2-7 failed to install/upgrade: blcr kernel module failed
to build
https://bugs.launchpad.net/bugs/502261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I have the same problem on an acer aspire 751. Changing
/etc/modprobe.d/alsa-base.conf from the default:
options snd-hda-intel power_save=10 power_save_controller=N
to:
options snd-hda-intel model=acer
Seems to make the error go away.
--
snd-hda-intel: spurious response messages in dmesg - ca
45 matches
Mail list logo
