Every once in a while my Linux install will hang on boot with these two lines as the last lines:

ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15

Anybody know how to fix this?

Could you show us the output a few lines before that. Say about 10 lines or so. Just looking at that it looks like a hard disc problem.

Well, I'll have to wait until it happens again. As I said, it doesn't happen all the time, just once every few days or so. Next time it happens I'll post it, unless there is some sort of log that keeps track of more than just the boot into the system that time. You know of any?

Not sure if this will help...

I'm running SuSE 8.2 and mine also occasionally hangs at boot, however eventually does boot. More often than not I find that it is trying to resolve periphs (usb printer,firewire drive etc.) that have come either partially or all the way disconnected from my PC.

Before next boot I usually make sure everything is snug and it seesm to resolve the prob.

Oh seems like my reply didn't go through. I did write one but it seems it got lost somewhere...

There is an app called dmesg which accesses the kernel ring buffer. You can pipie the output into something to be able to scroll back and forth like so: dmesg |less.

But can I see a boot log for a previous bootup, not the one I had just done to get into my system (When I have the problem, I have to reboot................)

I have been running suse at home and at work for about 1.5 months now. (refugee from unstable mandrake installs)
I have strange bootup failures all the time with suse. It hates USB. If i have something PLUGGED in to a usb port, not even turned on, the machine cant load x and it drops my to the login prompt (x wont start no matter what after this happens). Sometimes it wont boot at all.
The fix that i use is to boot up with the IDE option (forget the actual command right now, but you can see it in the options)
If anybody knows why this fixes it, id be glad to know! (or how to fix it)
Thats my .02

I wonder if that's the problem with mine....... I have a USB flash drive on my keychain, and sometimes I have that plugged in when I boot, but I don't remember if the 2 are connected. I do have a printer in USB, and that doesn't seem to be a problem, and also a keyboard. I'll try it and see if it happens with the USB flash drive inserted.

Yes, make sure to let us know what happens with that. I cant find anything on the net about Suse9 doing this. But we all know that This distro suffers from terrrible usb support, and its well documented.
Also, when you post back here, i would like to know what mobo you have, perhaps the issue is there. (mine is a kr7a-133r). I also use a wireless mouse and keyboard (finally got those "special" keys working thanks to the multimedia keys utility!!!!!!), both usb. It seems to be a problem with the front usb ports alone. Do you plug in there?
/tired/worksucks/ ./configure coffee

My Mobo is the first thing in my profile........... I have a wireless mouse, but a wired keyboard. I use the front USB ports only for the USB flash drive. I tried rebooting with it plugged in, and it booted fine. How come when I don't want it to screw up on boot it does, and when I want it to screw up it doesn't??!!!!!

DOH! I should have actually READ the profile, or your sig. or maybe just read something.

So it didnt hang. Well thats good for you! but bad for me! ( i was hoping to weasel an answer out of this)

Have you done an fsck to make sure everything is kosher with the filesystem? Other than that... i got nothin.

and to answer your question of: "How come when I don't want it to screw up on boot it does, and when I want it to screw up it doesn't?" you should read this:
http://www.theonion.com/onion3636/co...echnology.html
yeah its old, but STILL hilarious.

OK, it finally happened again, and I painstakingly wrote down everything on the screen. The only weird thing is, when I compared it to the normal boot log of when it doesn't do that, the log is EXACTLY the same, word for word, letter for letter, etc....
So I just copied and pasted the normal boot log for that entire screen. Here it is:

NFORCE2: IDE controller at PCI slot 00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100%% native mode: will probe irqs later
AMD_IDE: Bios didn't set cable bits corectly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
AMD_IDE: PCI device 10de:0065 (nVidia Corporation) (rev a2) UDMA100 controller on pci00:09.0
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hdaMA, hdbMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdcMA, hddMA
SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
SiI3112 Serial ATA: chipset revision 2
SiI3112 Serial ATA: not 100%% native mode: will probe irqs later
ide2: MMIO-DMA , BIOS settings: hdeio, hdfio
ide3: MMIO-DMA , BIOS settings: hdgio, hdhio
hda: Maxtor 2B020H1, ATA DISK drive
hdb: Maxtor 53073H4, ATA DISK drive
blk: queue c03eb6c0, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c03eb81c, I/O limit 4095Mb (mask 0xffffffff)
hdc: TDK CDRW5200B, ATAPI CD/DVD-ROM drive
hdd: ATAPI 52X CDROM, ATAPI CD/DVD-ROM drive
hde: Maxtor 6Y120M0, ATA DISK drive
hdg: Maxtor 6Y120M0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15

I hope this helps! I am completely lost

In that case I don't know. I used to get crc errors while uncompressing my kernel image on a particular computer. It happened very occasionally and only on that one box. So it could be one of those unexplained things.