Here are my results with Herd 4:
With the same setup as before I get the same error.
When I remove the USB cable that connects my screen's card reader / hub,
the boot process continues up to the point where the on-board wireless
chip is initialized. Then the kernel segfaults.
** Attachment added
Did you check with Herd4 ?
--
Feisty Herd 2 does not boot on Core 2 Duo
https://launchpad.net/bugs/81596
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: casper (Ubuntu)
Status: Needs Info => Confirmed
--
Feisty Herd 2 does not boot on Core 2 Duo
https://launchpad.net/bugs/81596
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Problem persists with Feisty Herd 3.
--
Feisty Herd 2 does not boot on Core 2 Duo
https://launchpad.net/bugs/81596
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: Ubuntu
Sourcepackagename: None => casper
--
Feisty Herd 2 does not boot on Core 2 Duo
https://launchpad.net/bugs/81596
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "Screenshot of boot messages"
http://librarian.launchpad.net/5929642/Screenshot.JPG
--
Feisty Herd 2 does not boot on Core 2 Duo
https://launchpad.net/bugs/81596
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
Can you edit the kernel command line from the boot menu and remove the
splash parameter, it will let you able to see the boot messages, give
the last ones you see.
** Changed in: Ubuntu
Status: Unconfirmed => Needs Info
--
Feisty Herd 2 does not boot on Core 2 Duo
https://launchpad.net/bu
