64-bit Installation permanent reboot loop

I’m trying to installing opensuse 11.0 x86_64 on my notebook but always:

  • The DVD start…
  • Exit the Welcome screen…
  • I push on install…
  • Now start the hardware recognition…
  • At about 10% return on the initial screen (?)

NOTES:

  1. My notebook is a Santec N48 equipped with a CPU Intel Core 2 Duo 2.53 GHz P9500.

  2. I tested on the Intel site and is 64-bit CPU.

  3. I have also tried other GNU\Linux distributions but happens the same problem.

  4. The problem does not appear if you try to install a 32-bit distribution.

Thanks for the help,

Ric

Wow; I can’t even find that laptop listed on Google anywhere (except a reference to this post).

Let me argue you should not install 64-bit unless you know exactly why you need it. In Linux, it will usually run slower than 32-bit for almost anything you might be doing on a laptop. I’ve tried various 64-bit versions of Linux and FreeBSD on a dual-core Athlon, and 32-bit is always faster and has fewer problems such as you describe.

I must admit as soon as 64 bits version was out , I
used the 64 bits version .
Did it give problems No.
Is faster 32 bits version ?
Is not only the CPU that makes a PC faster.
Think of the RAM you use with type and how much
The disk controller IDE or SATA .
You’re graphic card and so on.
So in my opinion the CPU is only apart of the story
Dobby9

But really you had installed opensuse 64-bit? How did you do? :confused:

I need 64-bit because I do videoediting and 3D graphics.

This is my hardware: :wink:
SANTECH N48
CPU Intel Core 2 Duo P9500 2.53 GHz (DC, 6Mb, 25W, 64bit)
RAM 4 Gb DDR III 1.066MHz (2x2.048Mb)
HARD DISK 320 Gb 7200RPM Buffer 16Mb S.ATA
DISPLAY 15,4" WSXGA+ 1.680x1.050 Glare Type IPS
VGA nVidia GeForce 9800M GT 512 Mb GDDR3 dedicated

Thanks for the help,

Ric :cool:

But really you had installed opensuse 64-bit? How did you do?

I need 64-bit because I do videoediting and 3D graphics.

This is my hardware:
SANTECH N48
CPU Intel Core 2 Duo P9500 2.53 GHz (DC, 6Mb, 25W, 64bit)
RAM 4 Gb DDR III 1.066MHz (2x2.048Mb)
HARD DISK 320 Gb 7200RPM Buffer 16Mb S.ATA
DISPLAY 15,4" WSXGA+ 1.680x1.050 Glare Type IPS
VGA nVidia GeForce 9800M GT 512 Mb GDDR3 dedicated

Thanks for the help,

Ric

What error messages did you get ?
What did you use the LIVE CD or the DVD ?
Did you do a media check ?
Can you’re disk controller emulate a IDE interface ?
Just to be sure run Memory check.
Try install in verbose mode.
My first impression is if there is a problem that
it is the graphic card or sata driver
Normally I prefer a install media , but in this case
downloading DVD takes a lot more time than the Live CD , so the change that some is going wrong is higher with the DVD
dobby9

At about 10% return on the initial screen

Both

Yes

No

Yes

I can do it? You explain to me how?

I do not know what to do more … :cry:

Ric

I seem to recall you get verbose messages either by selecting it from one of the drop down lists during the initial screen, or you can hit the ESC key as soon as it starts trying to load. You should get a shift from the pretty graphical installer progress to a terminal window with lots of details zipping by. The idea is you may get to see a message with some meaning to you just before it dies.

It is indeed the hitting the Esc key will bring you into the verbose mode
Start with it as soon as possible
Sometimes you have to hit it more than once
Even on a running system it is use full to it now and than.
Hopefully we can find out at what time it goes wrong
dobby9

I have had this problem (64-bit Linux reboots infinitely) with a laptop with this chip - Extreme Notebooks Raptor 560x (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272530). There is a problem with every 64-bit Linux I have tried. The closest I get is with Fedora Core 10, where it installs successfully, but the installed image goes into an infinite reboot. The FC10 live CD also reboots infinitely, leading me to suspect that the installation CD runs as a 32-bit application.

– Bhaskar

Remove some RAM and see if the problem continues if you reduce the RAM from 4GB to 2GB.