OpenSUSE 13.1 installs and runs fine so there is an issue with how
Debian and/or Ubuntu is doing things here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Title:
Ubuntu 13.10 + 14.04 Catast
** Description changed:
System Specs:
ASUS Sabertooth 990FX (with the latest BIOS)
AMD FX-8120
AMD Radeon HD 7950
240GB Seagate SSD (20GiB / partition)
2TB WD HDD (/home)
+
+ The same issues are present both with GPT UEFI and simple MBR non-UEFI
+ installs.
I have installed Ub
** Project changed: efibootmgr => efibootmgr (Ubuntu)
** Changed in: efibootmgr (Ubuntu)
Status: New => Confirmed
** Also affects: systemd
Importance: Undecided
Status: New
** Description changed:
System Specs:
ASUS Sabertooth 990FX (with the latest BIOS)
AMD FX-8120
** Description changed:
System Specs:
ASUS Sabertooth 990FX (with the latest BIOS)
AMD FX-8120
AMD Radeon HD 7950
240GB Seagate SSD (20GiB / partition)
2TB WD HDD (/home)
I have installed Ubuntu 14.04 three times and each met the same fate.
- The first time you boot into the sy
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: efibootmgr (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Title:
** Description changed:
System Specs:
ASUS Sabertooth 990FX (with the latest BIOS)
AMD FX-8120
AMD Radeon HD 7950
240GB Seagate SSD (20GiB / partition)
2TB WD HDD (/home)
I have installed Ubuntu 14.04 three times and each met the same fate.
The first time you boot into the sy
** Description changed:
System Specs:
ASUS Sabertooth 990FX (with the latest BIOS)
AMD FX-8120
AMD Radeon HD 7950
240GB Seagate SSD (20GiB / partition)
2TB WD HDD (/home)
I have installed Ubuntu 14.04 three times and each met the same fate.
- The first time you boot into the sy
and upon trying to boot into Ubuntu 14.04, the systemd-udevd errors
still prevent me to boot as usual.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Title:
Ubuntu 13.10 + 14.04 Catastrophic
and as always, not a single kern.log, syslog, or anything relevant is
capture so the only thing you have to see, in regards to the stack
traces, are the screenshots I provided earlier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Currently in the Ubuntu 14.04 daily live ISO. As usual, it installs fine
with no errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Title:
Ubuntu 13.10 + 14.04 Catastrophic Random Kernel
The issue with Xubuntu 13.10 seems to be related to this bug:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/879858
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Title:
Ubuntu 13.10 +
Ubuntu 14.04 already has the latest mainline kernel, and Ubuntu 13.04
works perfectly fine with every kernel from 3.8 to 3.12.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Title:
Ubuntu 13.
If possible, can you test the latest mainline kernel to see if this bug
is already fixed upstream? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't see any mentions of systemd-udevd or kthreadd in these logs like
I took in my screenshots (of which I don't remember seeing issues with
efibootmgr) so the bug with Xubuntu may or may not be related to the
issue I'm having here, although I would assume there is some sort of
connection someho
Once again it has crashed at the same spot
Nov 15 11:13:27 xubuntu ubiquity: Setting up grub-efi-amd64-signed
(1.22.1+2.00-19ubuntu2.1) ...
Nov 15 11:14:29 xubuntu kernel: [ 1035.084269] CPU: 7 PID: 15508 Comm:
efibootmgr Tainted: GF D 3.11.0-12-generic #19-Ubuntu
Nov 15 11:14:29 xubunt
I'm currently on a live session of an Xubuntu 13.10 64-bit flash drive
which I was attempting to install over my Ubuntu 14.04 partition and
when it got to the installing grub2 portion it crashed and now I have a
log I can provide.
** Tags added: apport-collected
** Description changed:
System
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909417/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Titl
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909418/+files/syslog
** Attachment removed: "ProcEnviron.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909416/+files/ProcEnviron.txt
-
I notice that Raring does not have a file named systemd-udevd in
/lib/systemd but Saucy/Trusting do. Therefore, the systemd-udevd thing
is a new addition to Ubuntu starting with Saucy. It's the only thing I
can think of that could be causing issues.
--
You received this bug notification because y
Now that I think about it, I use the Oibaf PPA on Raring which includes
linux-firmware 1.117 but Raring has always worked fine; so surely it
can't be a firmware bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Attachment added: "screenshots.7z"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909165/+files/screenshots.7z
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
There are some screenshots. I can't get any output from a regular boot
since my monitor then says 'No Display' so I have to use recovery mode
to show the error messages. I reinstalled Ubuntu 14.04 and set those
boot options; and as usual the first time I boot into Ubuntu 13.10/14.04
it works fine.
Copying with a digital photo isn't that great since the error messages
are so long that you can't see the entire error. You can't write it down
either because the errors occur quickly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Can you follow the "Boot options" instructions on the following wiki to
enable additional output on boot:
https://wiki.ubuntu.com/DebuggingKernelBoot
As mentioned on the wiki, it would be great if you can attach a log file
which may have captured any messages you see. If you are unable to
capture
Perhaps this is a bug with systemd-udev? after all, one of the errors I
get is 'systemd-udevd tainted'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Title:
Ubuntu 13.10 + 14.04 Catastrophic
After replacing all of the firmware files in Trusty with Raring's, it
still crashes. I'm not sure what else could be causing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250321
Title:
Ubuntu 1
I tried booting with no devices connected to my system (not even a mouse
or keyboard) and got the same results.
Boot #1: Boots then monitor says there is no display
Boot Recovery #1: Boots fine
Boot #2: Boots to desktop then immediately hangs (this time with icons in panel)
Boot Recovery #2 Instan
27 matches
Mail list logo