Kernel 5.4.0-1012.12 fixes the issue.
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880607
Title:
Raspberry Pi 4
A buddy is running a Pi 4 with the official 20.04 Pi image (freshly set
up) and with the 1011 kernel WITHOUT ISSUES. His config looks like this:
cmdline.txt:
root=LABEL=writable rootfstype=ext4 rootwait console=serial0,115200
console=tty1 net.ifnames=0 dwc_otg.lpm_enable=0 elevator=deadline
My cmdline.txt:
root=LABEL=rpi4-root rootfstype=ext4 rootwait verbose nosplash
console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 net.ifnames=0
dwc_otg.lpm_enable=0 dwc_otg.fiq_fix_enable=1 fsck.repair=yes
My config.txt:
[pi4]
# Route interrupts to ARM cores using legacy interrupt
Downgrading to 5.4.0-1008-raspi fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880607
Title:
Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
To manage notifications
** Attachment added: "ubuntu-bug linux-raspi (gzipped)"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+attachment/5376655/+files/apport.linux-raspi.2ccw0izb.apport.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After upgrading my Raspberry Pi 4 from Eoan to Focal (arm64), it now
runs awfully slow with dmesg showing loots of these warnings:
[ 3821.602211] [ cut here ]
[ 3821.603018] WARNING: CPU: 2 PID: 25391 at drivers/mmc/host/sdhci.c:1101
Public bug reported:
During upgrade on a Raspberry Pi 3 (armhf) from disco to eoan, the
upgrade of dma failed.
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: dma 0.11-2
ProcVersionSignature: Ubuntu 5.0.0-1025.26-raspi2 5.0.21
Uname: Linux 5.0.0-1025-raspi2 armv7l
ApportVersion:
Public bug reported:
Starting projectM is fine and it comes up with the default
visualisation, menu works, etc.. But as soon as you try to change to ANY
other preset, it crashes with either
free(): double free detected in tcache 2
or
double free or corruption (fasttop)
It seems to be
This was fixed in #1847163.
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843207
Title:
Doesn't boot on Raspberry Pi 4
THANK YOU!!
I just made it boot (without u-boot ATM) with all 4GB RAM enabled. And
my problem was my own stupidity. Several weeks ago, when researching why
it wouldn't boot, I somewhere found the boot param
"modprobe.blacklist=sdhci_iproc" which I added to my command.txt.
Without that module, the
> I'd *guess* that's a limitation due to u-boot, but I'll try and find
> time to test the kernel alone to confirm that. Obviously it's
> something we'll want to sort out fairly quickly but I suspect it'll
> have to be post-release at this point.
For me, the Raspberry never leaves the rainbow
> Which release of Ubuntu are we talking about here?
This is a clone of my RPi3 system (disco, IIRC it started out as bionic)
that was upgraded to eoan (on the Pi3).
btw: I've upgraded(?) the EEPROM to the July version
(https://static.raspberrypi.org/files/rpi-boot-eeprom-
I'm booting my Pis without u-boot with this in my config.txt:
[pi4]
enable_gic=1
armstub=armstub8-gic.bin
total_mem=1024
[all]
kernel=vmlinuz
initramfs initrd.img followkernel
arm_64bit=1
gpu_mem=32
dtparam=eee=off
This exact setup works fine on my Pi 3B+
The DTB is also missing from the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843207
Title:
Doesn't boot on Raspberry Pi 4
To manage notifications about this bug go to:
Public bug reported:
linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to
missing kernel modules for the new hardware components. It would be nice
if these got included. Also it only boots the kernel when the Pi is
configured for 1GB RAM or less. (Then gets stuck on missing root
With 1.1.1b-1ubuntu2.3 it's a bit different. The system doesn't seem to
freeze anymore, but network traffic stops working. Happend about 1-2
hours after a fresh reboot (after applying updates). It still answered
to PINGs, but no other network traffic. Neither SSH, nor HTTP/HTTPS or
XMPP. After
Public bug reported:
Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco
arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41
CEST. About 12:36 the system froze. I was able to reset the system at
around 17:17. It froze again at around 17:55. Reset it again 19:09,
I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've
also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager
still autoconnects just fine after boot. The configuration looks
identical on both machines.
--
You received this bug notification because you are a member
The thing is: In the previous version, flash-kernel ignored if mkimage
was missing and just continued normally without throwing any error or
even showing any warning. Which is the behaviour I'd prefer.
The new version aborts and throws an error although there's no need to
run mkimage on my system
Public bug reported:
After updating flash-kernel from 3.90ubuntu3 to 3.90ubuntu3.18.10.1,
dpkg aborted with this error:
Processing triggers for flash-kernel (3.90ubuntu3.18.10.1) ...
Using DTB: bcm2710-rpi-3-b-plus.dtb
Installing
Public bug reported:
The current version of vte2.91 is 0.54.1 which breaks SCOSC/SCORC ANSI
codes for saving the cursor position and returning to it. (Aka. SCP and
RCP)
This is fixed in 0.54.2 as per
https://gitlab.gnome.org/GNOME/vte/issues/48 . Please update package for
cosmic.
** Affects:
Public bug reported:
The Raspberry Pi firmware can boot a Linux kernel perfectly fine with
these settings in config.txt:
kernel=vmlinuz
initramfs initrd.img followkernel
(Note that the space between "initramfs" and "initrd.img" is
intentional!)
So there's no actual need to use u-boot anymore.
Can we omit this u-boot dependency, please? The Raspberry firmware can
boot Linux kernels perfectly fine all on its own without the need of
u-boot. There's absolutely no need to add this additional layer of
potential problems, e.g. bug #1791466 .
--
You received this bug notification because you
This might be related to bug #1791466
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
To manage notifications about this bug go
Public bug reported:
When dist-upgrading from artful to bionic, the upgrade of dma failed
with:
Setting up dma (0.11-1build1) ...
dpkg: error processing package dma (--configure):
installed dma package post-installation script subprocess returned error exit
status 128
Only after temporarily
This might be related to this one: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=847659
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791471
Title:
Upgrading from 0.11-1 (artful) to
** Also affects: u-boot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791466
Title:
RPi3: fdt_addr_r conflicts with scriptaddr from u-boot-rpi
Public bug reported:
u-boot-rpi_2016.03+dfsg1-6ubuntu2 (armhf) loads the boot.scr to
0x0200 but the bootscr.rpi3 also expects the FDT to be at this
address.
Changing the bootscr.rpi3 (and /boot/firmware/config.txt) to have the
FDT at 0x02008000 and running flash-kernel afterwards makes the
Same here while upgrading my Raspberry Pi 2 (armhf) from 17.10 to 18.04.
Upgrader finished with "Upgrade complete" but left hundreds of packages
in their old versions. I had to fix that with aptitude and now it's
actually finishing the upgrade.
--
You received this bug notification because you
@Andrea:
@include common-auth
auth optional pam_gnome_keyring.so
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password
@Andrea: Yes, no "switch to greeter" for me anymore. But still I get the
LightDM lock screen (with working password field) instead of GDM3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
A few reboots later, I'm now able to unlock the notebook from the
LightDM lockscreen. There's no "switch to greeter" anymore, but a real
password entry field which works. However, I still don't know why I had
the GDM3 lockscreen before.
--
You received this bug notification because you are a
I see this during bootup with a fresh install of artful on a HP Spectre
x360 13-4104ng notebook. For me it's setkeycodes e057 and code 0xd7,
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After a reboot, with nothing else changed, media keys are no worky
again. So it's NOT the Commands plugin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727842
Title:
Volume and Mute buttons on
After enabling it and disabling it again, the media keys work now for
some reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727842
Title:
Volume and Mute buttons on keyboard not doing
My Commands plugin was already disabled and the media keys still don't
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727842
Title:
Volume and Mute buttons on keyboard not doing anything in
Just for the record: I had Ubuntu 17.10 (upgraded from 17.04 which was
upgraded from 16.10) running on my HP Spectre x360 just fine with GDM3
and Unity and when the screensaver kicked in or I locked the screen, it
turned to the GDM3 greeter.
A few days ago, I cleared my SSD and installed 17.10
Today I was able to get media keys working about every 3rd restart of
unity-settings-daemon. I've saved 2 logs of each state. I suspect it has
to do with the order the plugins are loaded.
** Attachment added: "mylogs.zip"
Ah, I gave up after about 8 attempts without any luck - wanted to try
some more today. Glad you did it first. :)
After cleaning up different port numbers and IDs, the only obvious
difference between your logs seems to be something about the color-
plugin.
I've attached the cleaned logs.
**
This is after waiting a few minutes at the GDM logon screen. I also
tested the media keys in GDM and they worked. But they DON'T work in
Unity.
https://pastebin.ubuntu.com/26222796/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I found a pattern: When I login immediately after GDM comes up,
the hotkeys seem to work. When I wait a bit at the user selection and
THEN login, the hotkeys DON'T work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't know what happened, but yesterday, all hotkeys worked for some
reason. After shutting down the PC over night and booting it up today
with no changes made - they DON'T work again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1726930 ***
https://bugs.launchpad.net/bugs/1726930
** This bug has been marked a duplicate of bug 1726930
System fails to start (boot) on battery due to read-only root file-system
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
After upgrade to 17.10, my volume up/down and mute buttons/keys don't
change anything.
They keys get recognised in keyboard configuration as "Audio lower
volume" and "Audio raise volume" and "Audio mute". But pressing them
doesn't do anything.
Inside applications, the other
This bug reappeared (with cifs/smb mounts in fstab) after upgrade to
17.10 "artful" for me. The fix in #5 worked just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share
Confirmed on a hp Spectre x360 13-4104ng.
On battery power, the system DOESN'T boot up.
With the charger connected, the system boots up just fine.
See https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458 for my
apport logs.
--
You received this bug notification because you are a
Yes, this seems to be a duplicate of your bug.
On battery power, the system DOESN'T boot up.
With the charger connected, the system boots up just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The change in the fstab seems to have worked only once. Today, it
doesn't boot again (with the changed fstab). I've tried switching from
UEFI to Legacy mode without luck, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I changed my fstab from
UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1
to
UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 rw,errors=remount-ro 0
1
and it now boots fine again. I don't know why that is necessary now and
why the update didn't notify me or made the change
Public bug reported:
After not touching my notebook since 30th September (where I did the
dist-upgrade to artful and installed all available updates), I did all
available updates today (20th October) and the system didn't boot after
that.
The last message I see is "Reached target Bluetooth".
For the record: I upgraded to zesty and with kernel 4.10.0-1004
everything works fine, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic when using rtlwifi since
4.8.0-1035 seems to fix the problem. (Didn't check -1034.) Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
To
The error message is:
Preparing to unpack .../bash_4.4-2ubuntu1_amd64.deb ...
Unpacking bash (4.4-2ubuntu1) over (4.3-15ubuntu1) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu15) ...
update-initramfs: deferring update (trigger activated)
dpkg: dependency
Did anybody check the current kernel from zesty? I'm thinking about
upgrading, but don't want to render the thing unbootable because there's
no working kernel left.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This seems to be the same problem as described in bug #1636262, only
this time it happened during upgrade from 16.10 to 17.04. The setup
process (do-release-upgrade -d) aborted and I had to finish it manually.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package:
Problem still exists with 4.8.0-1033.37.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
To manage notifications about this
Possible duplicate: bug #1667160
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666421
Title:
kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
To manage notifications about this bug go to:
A workaround seems to be using https://github.com/dz0ny/rt8192cu instead
of the rtlwifi driver.
Bug also reported for the Orange Pi here: https://github.com/orangepi-
xunlong/orangepi_h3_linux/pull/1
Also related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666421
** Summary changed:
Same problem with 4.8.0-1032.
** Summary changed:
- Kernel panic with 4.8.0-1025 through -1031 on RasPi 2
+ Kernel panic since 4.8.0-1025 on RasPi 2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still no worky with kernel 4.8.0-1031.
** Attachment added: "Kernel panic with kernel 4.8.0-1031"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4849159/+files/vlcsnap-2017-03-28-21h33m24s240.png
** Summary changed:
- Kernel panic with 4.8.0-1025, -1026 and -1028
I just got the update to kernel 4.8.0-1031.35 ... will test later today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2
To
** Also affects: linux-meta-raspi2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-meta-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Kernel panic with 4.8.0-1025 and -1026 on RasPi 2
+ Kernel panic with 4.8.0-1025, -1026 and -1028 on RasPi 2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
** Attachment added: "vlcsnap-2017-03-09-23h36m39s986.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4834940/+files/vlcsnap-2017-03-09-23h36m39s986.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested today with the -1028 kernel. The problem IS STILL THERE.
This time, I made a video of the problem:
https://www.youtube.com/watch?v=H_PxSXsgVQU
The error part starts with:
Unable to handle kernel NULL pointer dereference at virtual address 0034
pgd = afcfc000
[0034] *pgd=
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825134/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825135/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825139/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825140/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
Title:
NOTE: The apport I sent was created with the WORKING 1024 kernel. IT IS
NOT from the here mentioned -1025 or -1026 kernel as there I can barely
login until the kernel panics.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825137/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825136/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825138/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1667160/+attachment/4825141/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667160
apport information
** Tags added: apport-collected yakkety
** Description changed:
I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
there's a RTL2838 DVB-T USB stick attached to monitor airplane
Public bug reported:
I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
there's a RTL2838 DVB-T USB stick attached to monitor airplane positions
for Flightradar24.
After updateing the kernel from 4.8.0-1024,
** Attachment added: "Screenshot of kernel panic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667160/+attachment/4824869/+files/IMG_20170223_0030047.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just got access to that Raspberry Pi 3 again. I saw that the expected
fdt address now changed to 0x02008000 in the boot script.
In the config.txt, it was set as:
# set extended DT area
device_tree_address=0x100
device_tree_end=0x8000
So I changed it to:
# set extended DT area
I don't have access to the RasPi3 at the moment (due to the changing MAC
screwing with DHCP and port forwardings). I'll see what I can do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652504
Title:
Could the missing fdt at 0x0200 be the reason, the RasPi now has a
different MAC address on each and every boot? Because I noticed this
after I got the boot process working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also the official flash-kernel_3.0~rc.4ubuntu64_armhf.deb sets the fdt
address to 0x100 whereas 3.0~rc.4ubuntu64.1.1 from yakkety-updates sets
it to 0x0200. So it seems to be a regression in that package.
Downgrading to 3.0~rc.4ubuntu64 and running "sudo flash-kernel" works.
(Don't know why it
Upon further inspection: The flash-kernel from the rpi3 PPA
https://launchpad.net/~ubuntu-raspi2/+archive/ubuntu/ppa-rpi3 is only
published for Xenial and there, the boot script sets the fdt address to
0x100 instead of 0x200. And that works without explicitly loading
the fdt.
So it seems I
Downgrading the kernel or recently upgraded packages flash-kernel or
linux-firmware-raspi2 didn't work for me. But you can fix this
temporarily by editing /usr/share/flash-kernel/bootscript/bootscr.rpi3
and adding the line
fatload mmc 0:1 ${fdt_addr_r} bcm2710-rpi-3-b.dtb
after the line
It seems the FDT isn't loaded properly. I can boot the system if I load
the FDT manually and do the remaining steps from the boot.scr manually:
fatload mmc 0:1 0x0200 bcm2710-rpi-3-b.dtb
fdt addr 0x0200
fatload mmc 0:1 0x0100 vmlinuz
fatload mmc 0:1 0x0210
The actual problem happens earlier in the process than depicted in the
screenshot above:
Found U-Boot script /boot.scr
reading /boot.scr
412 bytes read in 13 ms (30.3 KiB/s)
## Executing script at 0200
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address
Same here. The update to 1021 breaks the boot and the only way to
recover is to rename all *.bak files back so it boots the older kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The version of dma coming with Xenial is 0.9-1 and puts a Tab character
between sender name and stamp in the From line. This causes a "You have
new mail." message on login, but running "mail" (from mailutils) gives
"No mail for $USER.".
Changing all those tabs to spaces
I have this problem in Ubuntu 15.10 and Guake Terminal 0.8.4 (from the
WebUpd8 PPA, as recommended on their homepage).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506166
Title:
Bracketed paste
I'm on Vivid Beta 1 now and still no gear icon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/918657
Title:
unity-greeter_0.2.0-0ubuntu2 breaks desktop-selector
To manage notifications about this
Public bug reported:
After installing the moc package (2.5.0~alpha4+svn20120224-1ubuntu1)
incl. all dependencies, I get this when trying to run it:
$ moc
moc: could not find a Qt installation of ''
** Affects: moc (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Steve, turns out, there already was such a bug report:
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1066484/comments/11
Regarding the CIFS mounts: Today, I changed the auto cifs mounts during
startup to noauto,user mounts, which get mounted by my user using a script
after
While trying to catch a samba related bug, Steve Langasek pointed me to
this NM bug. The screenshot shows the nm-dispatcher.action: Caught
signal 15, shutting down... message.
Steve's comment
(https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631/comments/191):
Markus, your screenshot
Steve, turns out, there already was such a bug report:
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1066484/comments/11
Regarding the CIFS mounts: Today, I changed the auto cifs mounts during
startup to noauto,user mounts, which get mounted by my user using a script
after
Here's a screenshot of the last few lines visible before my notebook
shuts down. It's 13.04 as of May 27th.
** Attachment added: Shutdown messages
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631/+attachment/3688214/+files/IMG_20130527_192438.jpg
--
You received this bug
Public bug reported:
I've set my CONCURRENCY_LEVEL variable to 8 to use all CPU cores of the
i7. This works fine when compiling programs from the command line. But
whenever dkms needs to compile something, like e.g. the vboxdrv, it only
uses one single core (can be seen with htop) and thus takes
The problem is still there on a fresh Raring installation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are
The problem is still there on a fresh Raring installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
Just for the record: Had this problem today with the current 12.10
64-bit installer on a Lenovo E530. The installer was booted via EFI from
USB stick.
Removing the ubi-webcam.py didn't work. But I noticed a dd process
taking ~10% CPU although the installer showed that all files were
already
After booting my Acer Revo R3610 with linux-image:amd64 3.5.0.24.30,
vbetool dpms off (and other commands) also produces the Real mode
call failed error. It worked fine with kernel 3.5.0.21.32. Don't know
about the versions in-between.
--
You received this bug notification because you are a
Bug still appears in 12.10 (guake 0.4.3-3). A workaround is to edit
/usr/bin/guake and change line 821 to
width = 97
(May vary depending on your screen width.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 150 matches
Mail list logo
