I've booted Ubuntu 14.04.5 from the LiveUSB prepared using:
dd if=ubuntu-14.04.5-desktop-amd64.iso of=/dev/sdX bs=4M
and couldn't reproduce the problem with my 1212U.
In case of openSUSE a very similar problem has appeared to be caused by
the tlp package (and its /usr/lib/udev/tlp-usb-udev bash
The workaround with a power management (keeping scanner turned on) is supposed
to be handled by a udev rule. If you check
/etc/udev/rules.d/
there should be a rule with something like:
ENV{libsane_matched}=="yes", RUN+="/bin/sh -c 'if test -e
/sys/$env{DEVPATH}/power/control; then echo on >
We actually did have b43 support for quite a while (in jockey), but as
the quality of the driver got worse and worse over time
I'm sorry to hear that. We got some regressions with 802.11n cards, I've
spent many hours to track them all, and we believe all of them are fixed
(in current and stable
Could someone with Broadcom 802.11ac WiFI do one simple test for me,
please?
1) Remove wl driver temporary:
rmmod wl
2) Try using bcma module:
modprobe bcma
echo 14e4 43b1 /sys/bus/pci/drivers/bcma-pci-bridge/new_id
dmesg | grep bcma
(and provide output of the above dmesg command)
3) That's
Thanks to b3niup we have full info about the hardware now. Broadcom
cards differs by PHY and radio.
In case of 14e4:4365 BCM43142:
* PHY is LCN40 (revision 3)
* RADIO is 0xA065 (revision 0)
Unfortunately there are not specs for LCN40 available, b43 doesn't
support (just like brcmsmac).
I'm not
We can see what 14e4:4365 actually is if someone help me.
Please try the following:
modprobe bcma
echo 14e4 4365 /sys/bus/pci/drivers/bcma-pci-bridge/new_id
dmesg | grep bcma
rmmod bcma
modprobe ssb
echo 14e4 4365 /sys/bus/pci/drivers/b43-pci-bridge/new_id
dmesg | grep ssb
and provide
This bug was fixed in networkmanagement with commit:
commit 68ebd8231f942154cd743d4007b8ab9e8689808b
Author: Lamarque V. Souza lamar...@gmail.com
Date: Mon Sep 12 21:52:11 2011 -0300
Allow DSL connections be associated to ethernet interfaces.
CCBUG: 204170
Upstream bug:
The bug in b43 driver causing DMA errors was fixed in kernel 3.0-rc1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/502433
Title:
Lucid: b43 fatal DMA error on Dell Mini 9
To manage notifications
What about
echo low /sys/class/drm/card0/device/power_profile
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/488152
Title:
[RV710] With ATI restricted driver deactivated, GPU is overheating
--
I guess you call it regression, because your PCI ID was added to ssb.
Yes, we want to auto-load ssb for every SSB-based device. If you want to
use non-official (non-mainline) ndiswrapper, just blacklist native
driver.
What do you expect to be done in this ticket? I can only suggest fixing
There is experimental support for BCM4312 in Ubuntu 10.04 and even
should-be-stable in Ubuntu 10.10. Of couse newer versions (11.04, and
later) will work as well.
For Ubuntu 9.10 and older you need to do one of:
1) install compat-wireless
2) update kernel to 2.6.33 or later
3) install sta AKA wl
This card is LP-PHY type and support for it was introduced in kernel
2.6.32, however 2.6.33 should be more stable.
That means you need Ubuntu 10.10 or newer to get it working (hopefully)
fine with b43.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
[212.940104] phy0 - rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy
aborting.
[213.033671] phy0 - rt2x00pci_regbusy_read: Error - Indirect register access
failed: offset=0x7010 value=0x
This should be fixed by:
commit 08e5310028359de2daaa39cd10e9ca493c51792b
Author: Helmut
@Bartosz: do you think broken Xv can be related to using MMX2 instead of
MMX with new modesetting? It sounds more probably for me than some
modesetting-strict issue.
Stefan: not sure if this patch is worth testing, but you can always try.
Ideally it should fix your broken Xv (and should not break
Here goes log from k3b's svn:
r1049484 | mmalek | 2009-11-15 11:14:05 +0100 (nie) | 3 linie
* Fixed condition when checking if growisofs supports dual-layer DVDs
* Fixed message in above situation
BUG: 214115
This was commited *after* 1.68.0. Will hit 1.69.0 when this will be
released.
--
k3b
We were wrong first about resolving this bug.
Rev 746 fixed some obvious mistake in code, but it still didn't fix problem.
Rev 758 contains real fix for that (like Bartosz mentioned).
Sorry for my previous incorrect info.
--
[P4M900] [HP 2133 MiniNote laptop] Unexpected and unrecoverable
To make it clear:
1) This was bug in openChrome driver
2) We were touching reserved bits of 0x2A register (bug)
3) Bug didn't exist in last release 0.2.903 and we belive it doesn't exist in
current trunk (actually from revision 746 == 25.04.2009)
Great explaination was provided in openChrome's
Oh, now I understand. I downloaded this version of Kubuntu from
http://ubuntu.pl/ which seems to be serious, official Polish page of
Ubuntu. Now I see it's not because on http://kubuntu.org/ there is NOT
any 7.05 version.
It's really stupid from this polish team that they prepare and provide
Public bug reported:
I downloaded and burned Kubuntu7.05.1-desktop-i386-Fulmar.iso. When I
run LiveCD it doesn't detect my hard disk so I am not able to install
this. Problem doesn't exist for Ubuntu 7.04 or openSUSE 10.2. There is
part of my lspci:
00:1f.1 IDE interface: Intel Corporation
** Attachment added: lspci -vvn
http://launchpadlibrarian.net/8219593/lspcivvn.txt
--
Kubuntu doesn't detect SATA hard disk (IDE: ICH5)
https://bugs.launchpad.net/bugs/122691
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: lspci -vv
http://launchpadlibrarian.net/8219591/lspcivv.txt
--
Kubuntu doesn't detect SATA hard disk (IDE: ICH5)
https://bugs.launchpad.net/bugs/122691
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
21 matches
Mail list logo
