Feisty Herd 4 does not boot on ASUS P5W DH Deluxe

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.

Problem persists with Feisty Herd 3.

Did you check with Herd4 ?

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.

Thanks for your bug report. If you have another version of Ubuntu successfully running on your system could you please add the full output of 'lspci -vv' and 'lspci -vvn' as attachments to your bug report? Thanks in advance.

Using a small screwdriver I physically removed the ASUS WLAN card from my machine. This solved the problem and I am booting fine ;)

I have an Abit AB9 Pro which has an 965 express chipset. I have the same issue with the installer dropping to the initramfs shell on herd 5 (i386). Herd 4 (i386) on the other hand did boot after 10 minutes bu the keyboard and mouse (both USB) didnt work.

I tried herd 3 on x86_64 and no go also.

herd4/5 both work fine on my 32 bit laptop.

This is shaping up to be a crap release for core 2 duo owners !

I can confirm this behaviour when booting the feisty-desktop-i386.iso of Herd 5, altough the bootmessages are different on my system (see attachment). Specs:

- ASUS P5W DH Deluxe Mainboard
- Intel Core 2 Duo E6600 CPU

This motherboard contains a jMicron chip for IDE devices. I've seen some postings on launchpad regarding problems with this chip. My system uses the jMicron IDE connection for my DVD/CD drive, so maybe these issues are related?

I had the same issues on a different motherboard:

- ASUS M2N-SLI Deluxe Motherboard

- Amd Athlon(tm) 64 X2 Dual Core Processor 3600+

Also this motherboard contains a jMicron chip for IDE devices and I solve the boot problem by disabling the jMicron controller item from the BIOS that is set by default to [IDE]. I hope that this temporary solution help...

I guess I have the same problem on a Asus P5B Deluxe mainboard with Intel Intel Core 2 Duo

installation with Ubuntu 7.04 Beta i386 alternate

after installation, the system hangs for a while during the boot process (perhaps 2 minutes), then continues, saying /dev/disk/by-uuid/xxxx does not exist (the root filesystem); I replaced the UUID by /dev/sda8 in /etc/fstab, now it believes, /dev/sda8 does not exist

after this, the system stops responding; I must hard-reset it

the importance of this bug should be raised

ubuntu 6.10 and fedora 7 test 2 both work fine on the same system

I have the same problem on a Asus P5B-5 (Core 2 Duo) when I try to boot 7.04 Beta

maybe also check:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/95533

and

https://bugs.launchpad.net/ubuntu/+bug/97306

Just tried the latest build (http://cdimage.ubuntu.com/daily-live/20070409/). Still doesn't work but some things have changed.

In this new version the livecd tries to read the 3.5" disk drive constantly while booting from the CD. I didn't observe this in previous versions. Putting some random disk in the drive or disabling the drive in BIOS doesn't fix it however.

I've attached a new image of monitor output while booting the live cd. This output is displayed when removing 'splash' and 'quiet' from the boot parameters. Note that this picture was taken when the floppy drive was disabled in BIOS. Also, some time after the output in the picture, other stuff is displayed regarding USB devices. Didn't seem related to this bug however, as there were no observable error messages in that part.

Some info about my setup:
one western digital drive attached via SATA, BIOS set to AHCI
one liteon dvd ram drive attached via IDE (using the jMicron IDE port)

Hope this helps.

I can confirm this sort of problem with the March 23 builds of feisty desktop and alternative, as well as 6.10(!).

I'll be trying a daily build of feisty alternative as well as trying to find the appropriate hex wrench to use to remove the WIFI.

Ooh I lied. 6.10 has a different problem. Sorry sorry.

I tested the 32 bits version of the final feisty LiveCD (thanks to ship-it !) on my Asustek P5B Deluxe motherboard and my IDE CD-ROM. It does not boot.

I copied the LiveCD to an USB key (replacing isolinux with syslinux) and it does boot. Therefore I believe that the problem is not in the kernel. My theory is as follows:

 - this motherboard has a i965P chipset with a ICH8 southbridge
 - this southbridge has no IDE ports (only SATA)
 - the motherboard has an additional IDE controller:

02:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)

 - my IDE CD-ROM is attached to this jmicron controller
 - therefore the CD will not be able to boot if the jmicron controller is not loaded

Could the people concerned with this bug tell us if they test the Live CD with an IDE or SATA CD-ROM ?

I cannot test myself because I lack the proper hardware (I will probably buy one next month).

Testing with Ubuntu Gutsy Tribe-1 would also be interesting to see if that issue is fixed in the kernel to come (as it seems to be kernel/module related)

Tested with daily Gutsy image (amd64) today and it works fine.

HI there,

I also have this bug, but i don;t want to get rid of wifi :)
uname -a
Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux
kubuntu 7.10 beta

i use SATA DVD-RW, and i get "irq 23: nobody cared.."
more details i wrote on Bug #123617

Tested today with final Gutsy 64bit ISO. It works fine as long as I remove "splash quiet" from the kernel commandline.

When I keep the kernel commandline as-is the screen stays black after GRUB is done.

@Sebastian: have a look at https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/147623/ for this issue.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I do not have the exact hardware anymore.

However, with my current hardware

 - ASUS P5W DH Deluxe Mainboard
 - Intel Core 2 Duo E6600 CPU
 - MSI NX8800GTS-T2D640E-HD-OC Graphics Card

Alpha 4 of Intrepid boots perfectly and the desktop of the Live CD starts up in the native resolution of my screen (1920x1200).

Thanks Sebastian,

It's likely this was hardware specific, but since it appears to be resolved with your newest hardware I'm going to close this report. If anyone here who was having issues have the same graphics card with Sebastian originally had and can reproduce this error with the latest 2.6.27 kernel. feel free to reopen this report. If you have a different graphics card, please open a new report as it is helpful to the development teams if bug reports target one specific issue against a specific set of hardware. Thanks.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.