Ubuntu Edgy build is (still) not bootable w/ jMicron Controller

Bug #66747 reported by dgamble
12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Low
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.17

Please reference Bug #57502: "JMicron PATA/SATA Controller does not work". Support for the jMicron controller was recently added to the Edgy builds. A number of users have reported success with that fix, but a number of other users have also reported that is produces a different problem instead.

On both the 2006-10-16 Desktop and Alternate Edgy builds, booting on a P965 Neo (w/ jMicron controller), E6400 Core 2 Duo processor, yields the following error:

-------8<--------------------
Decompressing Linux...done.
Booting the kernel.

[ 28.165756] PCI: JMB36x: Enabling dual function on 0000:02:00.0
[ 28.185749] PCI: Cannot allocate resource region 0 of device 0000:02:00.0
[ 28.185782] PCI: Cannot allocate resource region 0 of device 0000:02:00.0
[ 28.185814] PCI: Cannot allocate resource region 0 of device 0000:02:00.0
[ 28.185845] PCI: Cannot allocate resource region 0 of device 0000:02:00.0
[ 28.186495] PCI: Error while updating region 0000:02:00.0/0 (0000b000 != 00000000)
[ 28.186531] PCI: Error while updating region 0000:02:00.0/0 (0000b000 != 00000000)

kernel direct mapping tables up to 100000000 @ 8000-8000
-------8<--------------------

No combination of kernel switches or BIOS toggles appear to have any effect. The machine works fine with my original Windows XP Home CD. A large number of users in Bug #57502 have reported the same problem.

I am unsure if this issue is the same problem as that original report or not, but the bug owner is no longer responding, so this seems like the best way to proceed to get this fixed (I apologize if not). The last note from the owner indicated that some changes to SOME of the CD builds needed to be done, however Edgy is due to be released shortly and still NO builds at all appear to work.

Revision history for this message
Anders (andersja+launchpad-net) wrote :

Can confirm this is still a pb with the install from the edgy liveCD of 16 Oct.

I have a Gigabyte GA-965P-DS3, P965, Socket-775 motherboard (https://www.komplett.co.uk/k/ki.asp?sku=323508) and a Intel Core 2 Duo E6300 1.86GHz Socket LGA775 processor. See also error messages posted on Bug #57502

Revision history for this message
kaz (ubuntu-tvetc) wrote :

And for the record (I too already reported this in Bug #57502), I can confirm this problem with the Edgy Eft x86 daily 20061017.1.

I have a Foxconn P9657AA-8EKRS2H, P965, Socket-775 motherboard (http://www.foxconnchannel.com/EN-US/Product/motherboard_detail.aspx?ID=en-gb0000194) and an Intel Core 2 Duo E6600 CPU.

Revision history for this message
Anders (andersja+launchpad-net) wrote :

3 different reporters corroborate this bug report. Setting status to 'Confirmed'

Changed in linux-source-2.6.17:
status: Unconfirmed → Confirmed
Revision history for this message
Alex (alexc-lp-deactivatedaccount) wrote :

I also have a similar problem with this hardware:

Intel Core 2 Duo E6600
Abit AB9
1xIDE DVD RW - Slave
1X80GB Maxtor IDE Hard Drive - Master
2X SATA 2 Western Digital Hard Drives

At first I could not even load the Final Release Edgy LiveCD as I kept getting "Error loading boot CD" errors which then told me to reboot, or it would get stuck at 8% while loading the Kernel. After reading around on ubuntuforums.org I read about disabling things like USB, so I did this and then I could boot the LiveCD. I managed to install Edgy perfectly with no problems.

However, when I was told to restart my PC did not restart correctly - it ejected my CD which is normal, but then it didn't shutdown. It just hung there with a little bit of the progress bar left with no hard drive activity at all. I had to do a hard restart in the end.

After I did the hard restart, GRUB loads fine but I do see some errors flash quickly on the page which appears after, they go too fast for me to see but they look very similar to the ones in the first post of this bug report. I then get shown usplash with the smallest bit of progress bar showing, but nothing loads and there is no hard drive activity.

Revision history for this message
Anders (andersja+launchpad-net) wrote :

When the boot screen hangs, try Ctrl+F1 or Ctrl+Alt+F1 to read the output? If you get anything, check with the output above?

Also, check that you've taken all the steps listed in the comments section on Bug #57502 (e.g. set your controller type to RAID - may not be valid for you if you)

Revision history for this message
cuby (cuby) wrote :

This can be related to the PATA probleme with Jmicron. see bug #126113: https://bugs.launchpad.net/ubuntu/+bug/126113

Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
mangar (mycrapaccount-deactivatedaccount) wrote :

Ubuntu Hardy alpha at the 14/3/2008, when using msi neo p965 with jmicron chip, in not bootable
unless boot parameter "splash" is removed, and "irqpoll' is added.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux-source-2.6.17:
status: Confirmed → Invalid
Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Ralph Janke (txwikinger) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

Changed in linux:
importance: Undecided → Low
status: Incomplete → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.