DD, I see that no logs in /var/log
folder are being updated
What should be my next step to get proper error messages and
investigate further?
Thanks in advance,
Aurélien
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2039786/+subs
Hi All,
I'm sorry i didn't found time to send my work but now it's done.
Please find the ALC298 python scripts and the brightness management of the
Samsung galaxy book 12 on my github:
https://github.com/Teetoow/SamsungGalaxyBook12
I'm not sure it will solve problem for other ALC298 soundcards
Hi all,
I finally got time to work on the soundcard of the Galaxy Book 12 (SM-W720). I
finally found the solution in order to get it working under linux after a lot
of work on the verbs I got from qemu two years ago.
I already can have sound from a script I'll send to you this weekend.
I'm
@PowerKiki
I'm really sorry for the delay. My computer crashed and I needed to repair it..
I just finished...
After a year I reinstalled the latest kernel but the problem seems to persist.
Here is the result of the alsa-info.sh:
Hi,
I have a Samsung galaxy book and encounter the same problem with my ALC298
sound card. I tried everything you did but it didn't work with mine. In fact I
even cannot hear something with the earphones.
I also tried to check the verbs used under windows (throught qemu) and it seems
they are
I tried an Avantree Leaf bluetooth transmitter with my Plantronics
Blackbeat Pro 2 and I don't have any improvement. In call mode, the
sound is still mono with the same (bad) quality that switching the sound
profile to HSP/HFP. Why there is no difference?
--
You received this bug notification
I'm also interested by such Bluetooth adapter, which one do you
recommend between the Avantree Leaf and 1Mii b10?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor
damned I did all this job for nothing... I didn't see the patch but
seems it's exactly I encountered and the solution I found it seems that
it fixes the issue right!
However as I said I also enabled the use of confidence field which
really improve the use of the keyboard of this computer. IT
I just found time in order to debug this problem. I found a "bug" in the
hid-multitouch driver. I also enabled the confidence management provided
by this touchpad in order to avoid pointer movements when we are using
the keyboard.
I'll try to submit this patch to the kernel developers team.
**
It kind of works but takes forever to start due to crng initialization.
(Forever like I didn’t wait and ended up pressing some random keys to get
things moving after more than a minute.)
[6.163871] 8139cp :00:03.0 ens3: link up, 100Mbps, full-duplex, lpa
0x05E1
[ 97.338260] random:
I can confirm 4.15.0-23.26~lp1777242 is installing and booting fine.
Thanks for your quick feedbacks. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777242
Title:
4.15.0-23-generic
Hmm, I had missed that :
$ sudo update-initramfs -u -k 4.15.0-23-generic
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
modinfo: ERROR: could not get modinfo from 'qxl': Exec format error
depmod: ERROR: failed to load symbols from
Kernel log says:
Failed to execute /init (error -2)
Kernel panic - not syncing: No working init found. Try passing init= option to
kernel. [...]
** Attachment added: "Capture d’écran depuis 2018-06-16 15-54-05.png"
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1777242/+attachment/5153305/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
Apport info is obviously from the booting kernel, I’ll try to also get
some useful information from the panic in the VT.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1777242
Public bug reported:
Trying to boot bionic with 4.15.0-23-generic fails with a kernel panic in qemu
on an Debian amd64 host.
The version of qemu is the current in Debian Testing: 2.12+dfsg-3.
Booting with 4.15.0-22-generic works fine.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1777242/+attachment/5153304/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
The attachment...
** Attachment added: "sosreport-potassium-20180507142110.tar.xz"
https://bugs.launchpad.net/ubuntu-certification/+bug/1767832/+attachment/5135442/+files/sosreport-potassium-20180507142110.tar.xz
--
You received this bug notification because you are a member of Kernel
Hi,
Sorry I just chose the wrong package.. As you may know ASUS does not provide
support for Linux for this laptop...
You will find attached to this message the result of sosreport --batch.
Please let me know if I can do something in order to help you.
Regards
--
You received this bug
Ok I troubleshot this problem.
Apparently, it came from the package `connman`, an Intel utility to
manage wlan and bluetooth that I installed wrongly since it's intended
for embedded systems.
Removing it solved all my problems.
** Package changed: bluez (Ubuntu) => connman (Ubuntu)
** Changed
Yes it looks like the same bug (at least for the GUI part), and it's a
Thinkpad as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1762603
Title:
bluetooth keeps turning off
Same bug on Ubuntu 18.04 / Thinkpad P51.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1738838
Title:
Bluetooth icon shows "Off" and the only option given below it is "Turn
Off"
I mean reboots.
So, on boot, the airplane mode is turned on by default (for an unknwon
reason).
The rfkill output is attached above. I have to trigger several `sudo
rfkill unblock all` to actually have them unlocked (in command line).
But then, the GUI still shows the bluetooth switch as OFF.
Also I have tried with blueman instead, with and without acpi-calls-
dkms, tp-smapi-dkms, tlp installed, the issue remains.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1762603
Title:
Public bug reported:
the bluetooth worked well right after install. After a few reboots, it's
impossible to keep it on and to connect devices.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux
Public bug reported:
My laptop is an ASUS UX302LG with kernel 3.13.0-5-generic on Ubuntu
Trusty 14.04. When I boot, the screen is switched on but remains black.
I connected another screen which works fine (VGA or HDMI) but I'm not
able to use the primary screen.
I tested the kernel
Alberto Aguirre :
I submitted the ticket
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274425
With kernel 3.13.0-5.20 (Ubuntu 14.04), the command sudo xrandr --output eDP1
--mode 1680x1050 does nothing.
With kernels drm-intel-nightly/2014-01-23-trusty and
Ok, I will send it on my next reboot.
For information, I was unable to suspend the laptop because it was awakening
some seconds later.
I made it working by using the following script (/etc/pm/sleep.d/20_zenbook) :
case ${1} in
hibernate|suspend)
# Unbind ehci_hcd for first device
I have an Asus UX302LG with Ubuntu 14.04 and I connected another screen to be
able to wor.
Today, I installed the kernel drm-intel-nightly/2014-01-23-trusty
(http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2014-01-23-trusty/)
and it seems to work well.
--
You received this bug
It works with development release :
[ 290.176136] usb 1-3: new high-speed USB device number 4 using ehci-pci
[ 290.311030] usb 1-3: New USB device found, idVendor=12d1, idProduct=1446
[ 290.311040] usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 290.311047] usb 1-3:
30 matches
Mail list logo
