Hi,
im trying to install 11.1 64-bit on my D945GCLF2 (atom 330). (Intel® Desktop Board D945GCLF2 - Overview)
Just after pressing install and the kernel loads, the green “load opensuse-screen” shows for a second and then it gets Kernel Panic (not syncing: attempted to kill init!).
I’ve tried to disable the onboard lan, usb ports and hyperthreading but no difference.
However, the 32-bit version loads without problem.
Anyone with the same problem? =)
ansbar wrote:
>
> Hi,
>
> im trying to install 11.1 64-bit on my D945GCLF2 (atom 330). (‘Intel®
> Desktop Board D945GCLF2 - Overview’ (http://tinyurl.com/44zo4v))
> Just after pressing install and the kernel loads, the green “load
> opensuse-screen” shows for a second and then it gets Kernel Panic (not
> syncing: attempted to kill init!).
>
> I’ve tried to disable the onboard lan, usb ports and hyperthreading
> but no difference.
>
> However, the 32-bit version loads without problem.
>
> Anyone with the same problem? =)
>
>
Have you tried the failsafe option?
If so what are the results?
If it boots in failsafe then it is probably one of the settings like acpi=off etc… just put those one at a time on the normal boot line at the boot screen to see which.
–
Mark…
Nil illegitimi carborundum
Hi, sorry forgot to add that.
I’ve tried installing it with boot options:
ide=nodma apm=off acpi=off noresume edd=off x11failsafe vga=0x31a
and also with the options kernel: safe settings and Video mode: text mode
Is there any other way to set failsafe?
Anyway, it still gives med the kernel panic…
This is just to confirm the result reported originally by
ansbar. I get a similar result in an attempt to install
11.1 onto a D945GCLF2 Intel dual-core Atom platform which
currently has 11.0 installed on it. The 11.0 installed
without problems and has been running nicely. A
description of my experience is as follows:
Boot platform with openSUSE-11.1-x86_64.iso DVD in drive.
At the splash screen, choose to install from DVD.
Progress bar notifier indicates loading kernel from DVD.
Upon completion of kernel load step, the splash screen
disappears, replaced by a text output screen containing,
in part, the following kernel oops:
BUG: unable to handle kernel paging request at ffffffff80209000
IP: <ffffffff802460bc>] on_each_cpu+0x0/0x30
PGD 203067 PUD 207063 PMD 3da20163 PTE 209161
Oops: 0003 [1] SMP
— standard Oops register dump —
— standard Oops call trace —
— other Oops miscellaneous information —
kernel not syncing: attempted to kill init!
At this point, in order to regain control over the
system I find I must disconnect mains power.
I tried selecting safe kernel mode and disabling other
features as allowed by the installation interface, all
with exactly the same result. Also got same result
when attempting to test memory, firmware or verify DVD.
One final observation: I was able to install 11.1 from
this same DVD onto VmWare, running on my Mac Pro (Intel),
and it appears to have installed correctly. So this
indicates to me that at least the DVD is not the source
of the problem. I would bet the problem is related to
the D945GCLF2 hardware interacting with the 11.1 kernel.
Hope there’s someone out there with the knowledge to
fix this. Thanks.
johndi0308 wrote:
> This is just to confirm the result reported originally by
> ansbar. I get a similar result in an attempt to install
> 11.1 onto a D945GCLF2 Intel dual-core Atom platform which
> currently has 11.0 installed on it. The 11.0 installed
> without problems and has been running nicely. A
> description of my experience is as follows:
>
> 1. Boot platform with openSUSE-11.1-x86_64.iso DVD in drive.
> 2. At the splash screen, choose to install from DVD.
> 3. Progress bar notifier indicates loading kernel from DVD.
> 4. Upon completion of kernel load step, the splash screen
> disappears, replaced by a text output screen containing,
> in part, the following kernel oops:
>
> BUG: unable to handle kernel paging request at ffffffff80209000
> IP: <ffffffff802460bc>] on_each_cpu+0x0/0x30
> PGD 203067 PUD 207063 PMD 3da20163 PTE 209161
> Oops: 0003 [1] SMP
>
> — standard Oops register dump —
> — standard Oops call trace —
> — other Oops miscellaneous information —
>
> kernel not syncing: attempted to kill init!
>
> At this point, in order to regain control over the
> system I find I must disconnect mains power.
>
> I tried selecting safe kernel mode and disabling other
> features as allowed by the installation interface, all
> with exactly the same result. Also got same result
> when attempting to test memory, firmware or verify DVD.
>
> One final observation: I was able to install 11.1 from
> this same DVD onto VmWare, running on my Mac Pro (Intel),
> and it appears to have installed correctly. So this
> indicates to me that at least the DVD is not the source
> of the problem. I would bet the problem is related to
> the D945GCLF2 hardware interacting with the 11.1 kernel.
>
> Hope there’s someone out there with the knowledge to
> fix this. Thanks.
I had a problem booting the Live CD on one of my machines, but the NET install
CD worked. I found it with -RC1, but openSUSE decided to ignore the problem as
the release date was too close. Please try the NET disk. If it also fails to
boot, then your problem is different than mine, and it may be a kernel bug and
this error report should be posted to the Linux Kernel Mailing List
linux-kernel@vger.kernel.org. Someone there should be able to fix it.
Larry
Larry -
I made up a NET CD, booted to the splash screen.
Attempting to either do a “check installation media”
or a net install resulted in kernel oopses. Therefore,
all my experience thus far tells me that on a D945GCLF2
board (Intel i945P/G dual-core processor, 133 MHz, 1G DDRII memory)
any operation that loads and starts up the kernel almost
immediately results in a kernel oops. Depending upon which
operation is selected at the splash screen, the call trace
looks different. I’m sorry that I’m not set up to dump the
total kernel oops output so I know I’m not being as helpful
as one would wish.
I will post this onto the Kernel mailing list as you suggest
and hope someone will look at it.
“Glad” to hear im not alone with this problem. Please update this thread if you find any solution.
Could you attach full capture of the oops (e.g. by camera)?
Same motherboard, same problem (2GB of ram though). Opensuse 11.0 works fine though.
To all:
Roland (devzero@web.de) suggested I review the following
thread, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/279186
which implied that what I was experiencing was not a bug
within the openSUSE 11.1 release at all, but instead a
bug in the bios version as shipped on my D945GCLF2 board.
I interrupted my bios during the boot process and found
that I had bios version 0099. I went to the Intel
download center (Download Software, Drivers and Utilities) and
got the iso image of version 0122 and burned it into a
bootable CD (LF94510J.86A.0122.2008.1117.0113).
It took a couple of tries to boot the CD and successfully
apply the bios upgrade to version 0122. But once this
was done I was able to do a standard install of 11.1
(automatic, accept all suggested defaults) and now I
appear to be running 11.1 (64 bit) with no problems.
So as far as I am concerned this bug is solved by the
bios upgrade. Thanks to all who offered suggestions.
John
I can confirm that this solution is working. I used the 0137 version.
Thanks for the help!
Hi, there!
I also experienced a kernel panic when trying to install the OpenSuSE 11.1 [x86-64] on my new Shuttle X27D with an Intel Atom 330.
The manual of the Shuttle X27D is not all too verbose, so I cannot say much about the chipset or Bios yet. (But I might find out whatever may be important. It’s just that I don’t have it at hand right now…)
When I boot the Install DVD of OpenSuSE [x86-64] and chose “Install” without changing any option, I run into the following error:
BUG: unable to handle kernel paging request at ffffffff80209000
IP: <ffffffff80246bc>] on_each_cpu+0x0/0x30
PGD 203067 PUD 207063 PMD 7dfc6163 PTE 209161
Oops: 003 [1] SMP
last sysfs file:
CPU 0
Modules linked in:
supported: Yes
Pid: 1, comm: swapper Not tainted 2.6.27.7-default #1
…]
Call Trace:
<ffffffff80229f1b>] change_page_attrset_clr+0x130/0x1e4
<ffffffff8022752b>] mark_rodata_ro+0x65/0x78
<ffffffff80209130>] init_post+0x13/0x183
<ffffffff808eb930>] kernel_init+0xe6/0xea
<ffffffff8020d7b9>] child_rip+0xa/0x11
Code: 25 00 00 00 00 48 89 da 48 87 10 e8 a7 e0 00 00 85 c0 74 e3 65 48 8b 04 25 00 00 00 00 48 c7 00 00 00 00 00 31 c0 41 5a 5b 5d c3 <41> 55 49 89 fd 41 54 49 89 f4 53 e8 dd c0 01 00 89 c3 fa 0f 1f
RIP <ffffffff802460bc>] on_each_cpu+0x0/0x30
RSP <ffff8807d419d78>
CR2: fffffff80209000
---[end trace 49212d7546df107a]---
Kernel panic - not syncing: Attempted to kill init!
I tried to update my BIOS to the latest version provided by Shuttle.com, which itself was successful. Unfortunately that didn’t help anything.
I also tried the hint posted here to use the the network installation. But that didn’t help either…
On some webpage I read that the network device of the Shuttle causes kernel panic on MacOS, so I disabled it in the BIOS. Unforunately that didn’t help either. Only the error changed slightly a bit:
BUG: unable to handle kernel paging request at 00000000006f1000
IP: <ffffffff8020d420>] apic_timer_interrupt+0x0/0x90
PGD 0
Oops: 0002 [1] SMP
last sysfs file:
CPU 0
Modules linked in:
Supported: Yes
Pid: 1, comm: swapper Not tainted 2.6.27.7-default #1
…]
Call Trace:
<ffffffff8022886e>] __phys_addr+0x1e/0x2e
<ffffffff80229b42>] __change_page_attr+0x13b/0x25d
<ffffffff80229c81>] __change_page_attr_set_clr+0x1d/0x53
<ffffffff80229d65>] cpa_process_alias+0xae/0x134
<ffffffff80229c92>] __change_page_attr_set_clr+0x2e/0x53
<ffffffff80229ea7>] change_page_attrset_clr+0xbc/0x1e4
<ffffffff8022752b>] mark_rodata_ro+0x65/0x78
<ffffffff80209130>] init_post+0x13/0x183
<ffffffff808eb930>] kernel_init+0xe6/0xea
<ffffffff8020d7b9>] child_rip+0xa/0x11
Code: 44 00 00 65 ff 04 25 20 00 00 00 65 48 0f 44 24 25 28 00 00 00 55 e8 e6 21 01 00 e9 19 f6 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 <68> 10 ff ff ff fc 48 83 ec 48 48 89 7c 24 40 48 48 89 74 24 38 48
RIP <ffffffff8020d420>] apic_timer_interrupt+0x0/0x90
RSP <ffff88007d419d28>
CR2: 00000000006f1000
---[end trace 41d930af09f92734 ]---
Kernel panic - not syncing: Attempted to kill init!
I should finally note that the kernel panic did **NOT **occur when trying to install OpenSuSE 11.0 [x86-64] or OpenSuSE 11.1 [i586]
I would post your panic messages, etc. on the Linux Kernel Mailing List
(linux-kernel@vger.kernel.org). One of the gurus will know what that oops means.
Larry
thanks for the hint!
will do so, when i’m at home.
sorry for dumping the whole kernel messages into this forum here. hope you don’t mind… 