Hi all, I have a Intel Original DH55TC mobo, i3 540 proc, 2 GB RAM and NVIDIA 8600GT Graphics card. I want to Learn and convert Linux to my Primary OS, and somehow OPENSUSE just attracted me so much I just cannot go off it. The problem is it just wont install. Every time I start I get these errors
!!!Help please!!!
On 05/31/2011 12:06 PM, cosmicbc wrote:
>
> [image: http://image.susepaste.org/15132098]
which openSUSE version, and from what kind of media are you trying to
install from?
did you get it from software.opensuse.org or somewhere else? (where??)
did you boot from that disk and do this: http://tinyurl.com/2ebcf27
if you did not, do it now…and if it fails then you must get a
perfect disk, see the Download Help link on the download page
oh, tell us: did that motherboard come in a box with a penguin on
it…or just broken flying window? *
this cite
http://www.intel.com/support/motherboards/desktop/dh55tc/sb/CS-031186.htm?wapkw=(DH55TC)
shows success in installation by some distros, but no kernel more recent
than 2.6.33, while openSUSE 11.4 is born with 2.6.37
so, check the disk, check your BIOS settings (if you have fiddled with
the speed or voltage you need to fall back to ‘normal’, and then try
again…
you might also try the Firmware Test on the install disk (right below
Check Installation Media)…
and let us hear from you again…
–
dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255
*
On 2011-05-31 12:06, cosmicbc wrote:
>
> Hi all, I have a Intel Original DH55TC mobo, i3 540 proc, 2 GB RAM and
> NVIDIA 8600GT Graphics card. I want to Learn and convert Linux to my
> Primary OS, and somehow OPENSUSE just attracted me so much I just cannot
> go off it. The problem is it just wont install. Every time I start I
> get these errors
>
> [image: http://image.susepaste.org/15132098]
That’s a bug. Open a bugzilla and attach the full kernel trace dump. The
photo only show the end of it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
I can’t see the whole thing, so I don’t really know what’s going on… but you can always try to pass ‘nomodeset’ to the kernel boot parameters and see if you get the same error. Somehow I look at KMS and see a big boom there…
On 2011-05-31 15:36, ketheriel wrote:
> I can’t see the whole thing, so I don’t really know what’s going on…
There is an “— end trace … ]—” in the photo. That’s the kernel
dumping the info for a bug report, so please report it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
That’s nice and all (the bug reporting part), but I’ve seen this on Intel chipsets caused by KMS enabled, as it wouldn’t be that surprising to happen also on overclocked machines. A bit of information would be welcoming… This one of the cases where detail do make miracles…
Same here, seen it too on Intel chipsets. On most occasions ‘nomodeset’ does the job.
On 2011-05-31 22:36, ketheriel wrote:
>
> That’s nice and all (the bug reporting part), but I’ve seen this on
> Intel chipsets caused by KMS enabled, as it wouldn’t be that surprising
> to happen also on overclocked machines. A bit of information would be
> welcoming… This one of the cases where detail do make miracles…
Absolutely.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Hi eyeryone! thanks for the response. Yesterday I struggled again with my problem and have found out that the real prob was my NVIDIA 8600GT graphics card. I removed the card ant tried again like ten times and DIDNOT get any errors. so the problem really was my Graphics card. Also I think the kernel is not able to use or access the RAM of my graphics card. Now I’m just curious how do i tell the kernel to avoid that particular step. Thanks
Hi eyeryone! thanks for the response. Yesterday I struggled again with my problem and have found out that the real prob was my NVIDIA 8600GT graphics card. I removed the card ant tried again like ten times and DIDNOT get any errors. so the problem really was my Graphics card. Also I think the kernel is not able to use or access the RAM of my graphics card. Now I’m just curious how do i tell the kernel to avoid that particular step. Thanks
NOTE: I am really new in this vast world of LINUX, so if you all could be little more non technical and not use short-forms like (KMS etc) i could grab your responses even better. Thank you
On 06/01/2011 09:36 AM, cosmicbc wrote:
>
> Hi eyeryone! thanks for the response.
you never responded to my initial post, and i see you also ignored
Carlos’ request to log the bug you found…
it is highly unlikely i want to help you if you intend to ignore your
helpers…
but, just because i’m a really really nice and friendly guy i will point
you to these pages, which may not be at all helpful, a fact i can’t know
for sure but would at least have had a chance to guess a potential
remedy if i had some answers and could be confident you had a good
install disk:
http://tinyurl.com/23mgej6
http://en.opensuse.org/SDB:NVIDIA_drivers
http://tinyurl.com/37v9y7m
and, if you don’t understand KMS (or anything else) either ask, or dig
out the answer yourself, like this http://tinyurl.com/3rhjtmp
this whole linux thing is for fun, for learning, for freedom, for
helping each other AND yourself.
–
dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255
agp_backend_intiiallize
agp_add_bridge
agp_intel_probe
local_pci_probe
pci_device_probe
really_probe
_driver_attach+0x79/0x80
bus_for_each_dev+0x4b/0x70
driver_attach+0x60/0x20
dos_add_driver+0x227/0x300
driver register+0x5f/0x100
_pci_register_driver+0x3d/0xb0
do_one initcall+0x33/0x170
kernel init+0x133/0x1cd
kernel_thread_helper+0x6/0x10
NOTE: yesterday i again tried to boot from my suse dvd and used the option " $ modprobe nouveau " and it worked and i installed suse successfully. but from today morning i got the above error.
On 2011-06-02 13:36, cosmicbc wrote:
>
> in response to robin_listas: i dont know how to retrive the “kernel
> dumping the info for a bug report” but i have written down what could
> see in the screen
Insufficient.
If the system starts, it will be in the log. If the system does not start,
then either make a video, or dump via serial port to another computer.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
I’m confused by the logic.
it will be in the log
What log, the PC was running from an optical medium. I doubt any logs were written to his DVD
dump via serial port
That motherboard, like most these days, doesn’t even have a serial port.
I’m very disappointed by the tone of the all the responses to this “Puzzled Penguin’s” very first post. I say this with the greatest respect for the responders, each of whom has been very helpful to me at one time or another. Perhaps you’re all just having a bad day, so I’ll humbly suggest that we take a deep breath and start over.
On 2011-06-02 15:06, caprus wrote:
>
> I’m confused by the logic.
>> it will be in the log
> What log, the PC was running from an optical medium. I doubt any logs
> were written to his DVD
They are in RAM, where they can be read (a file in the installation
ramdisk) and copied to another disk. Plus, some of the files are copied to
the HD automatically (if the installation succeeds, that is). It is just a
question of grepping for a file with that message, and hopping to be lucky.
>> dump via serial port
> That motherboard, like most these days, doesn’t even have a serial
> port.
Mine has, and is a modern one 
There are quite a few MB that do have the serial port connector, but it is
seldom connected to the box. My box doesn’t have the socket, I had to make
do. It is not in “fashion”, so the installers just ignore the serial port
unless requested.
Yes, you are right that it is difficult - but that is what the developers
provided for debugging the kernel while booting. It is what there is. An
usb port would be nicer nowdays, but the devs have not provided for it.
The problem is that the poster found a real bug, something that we, users,
can not solve. But he can help others not finding that bug again by
reporting it to the devs. Yes, it is difficult to do it. Life is not easy.
Linux is a community effort, every one helps. >:-)
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2011-06-03 22:03, Carlos E. R. wrote:
> On 2011-06-02 15:06, caprus wrote:
> The problem is that the poster found a real bug, something that we, users,
> can not solve. But he can help others not finding that bug again by
> reporting it to the devs. Yes, it is difficult to do it. Life is not easy.
> Linux is a community effort, every one helps. >:-)
But yes, I was too harsh. Sorry.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)