no irq handler for vector в чем проблема

11.08.202302.07.2023 admin 0 Comments

Debian User Forums

[SOLVED] Error msg in terminal: «No irq handler for vector»

#1 Post by robgeek » 2013-07-19 23:12

Re: Big problem with Debian kernel.

#2 Post by bw123 » 2013-07-19 23:35

Re: Big problem with Debian kernel.

#3 Post by robgeek » 2013-07-20 00:28

Advanced
PCIPnP
Plug & Play O/S’ [No]
Resources Controlled By [AUTO]
*IRQ Resources «nothing here, and the color of this option is gray.»
Assign IRQ For VGA [DISABLED] «Like you said to do.»

** PCI Express relative itens **
Maximum Payload Size [409 6]

Re: Big problem with Debian kernel.

#4 Post by robgeek » 2013-07-20 15:01

Re: Big problem with Debian kernel.

#5 Post by cynwulf » 2013-07-20 15:41

Re: Big problem with Debian kernel.

#6 Post by robgeek » 2013-07-20 18:17

It seems to me that i have to add «pci=nomsi,noaer» into the boot code, but where is «syslinux.cfg» file?
How can i do that?

Re: Big problem with Debian kernel.

#7 Post by robgeek » 2013-07-22 16:02

Re: Big problem with Debian kernel.

#8 Post by cynwulf » 2013-07-22 20:16

Re: Big problem with Debian kernel.

#9 Post by robgeek » 2013-07-22 22:16

Re: Big problem with Debian kernel.

#10 Post by Randicus » 2013-07-22 22:32

Re: Big problem with Debian kernel.

#11 Post by robgeek » 2013-07-24 17:24

Re: Big problem with Debian kernel.

#12 Post by cynwulf » 2013-07-25 08:06

You don’t need to worry about syslinux.

Just boot the system, when the grub menu appears hit the letter ‘e’ to edit the line

Move the cursor to the end of the line (usually after «ro») and type the options «pci=nomsi,noaer», without the quotes, there.

Then do CTRL+x to boot from that kernel. If that does the trick you can look into doing a permanent edit to the grub configuration.

Re: Big problem with Debian kernel.

#13 Post by fsmithred » 2013-07-25 09:23

Re: Big problem with Debian kernel.

#14 Post by robgeek » 2013-07-26 19:30

Guys. Problem fixed! Thank you very, very much!
After 3 years with this annoying problem finally he wont piss me off again.

I oppened /etc/default/grub and i added ( pci=nomsi,noaer ) between the quote marks in GRUB_CMDLINE_LINUX=»» line.

And finally, in terminal: update-grub

Well, actually i have no idea what i did, but it worked.

Re: [SOLVED] Error msg in terminal: «No irq handler for vect

#15 Post by Tom Booth » 2018-11-12 03:34

Anyway, I get the same, or similar «No IRQ handler for vector» error every time I boot up ANY Linux distro. I’m using Easy2Boot mutiboot from USBs.

There is a pause at this error, often for quite a long time, then the boot will eventually continue successfully. It is only slightly annoying. Mostly I was just wondering what might be causing it and if there might be some cure, Just to speed up boot time if nothing else, it seems to cause a substantial delay.

Источник

Arch Linux

You are not logged in.

#1 2020-06-01 20:41:49

Error message during boot: do_IRQ: 1.55 No irq handler for vector

I’m getting an error message during boot which is slightly annoying as I’m trying to run silent boot on my HTPC. The message says

From what I can tell, this is an «emergency» level item, so setting the loglevel kernel parameter doesn’t fix this (and I can’t imagine it’s good practice to hide emergency level items in any case).

I don’t think it’s causing any particular issues on my system as I can boot in fine but I would like to get to the bottom of this.

I’ve seen a couple of posts on this forum with a similar issue but the one marked [solved] suggested using «acpi=noirq» as a kernel parameter. I tried that and it didn’t change the outcome.

Some relevant information about my system:

Any tips on how to resolve this would be greatly appreciated.

#2 2020-06-03 21:31:34

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

I’ve tried to do some more digging on this but not sure if I’m getting anywhere.

Based on a particular google result, I recompiled the kernel with the «CONFIG_GENERIC_IRQ_DEBUGFS» kernel option enabled (first time doing that so good learning experience!) and then searched the debugfs for this particular vector:

No mention of Vector 55. No idea where to go from here. Does anyone have any ideas?

#3 2020-06-03 22:28:52

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Does adding the kernel parameter nomsi have any effect?

#4 2020-06-04 05:25:38

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Does adding the kernel parameter nomsi have any effect?

Thanks loqs. I assume you mean:

which I saw in a couple of posts. If so, yes, I tried it as I had a similar line my lspci (see bottom of this post) and it didn’t stop the error message.

I tried it before the custom kernel so I’ve just retried it again to see if there was any change to the irqs outputs. The main difference was that it reduced the number of them:

dmesg output from this boot: http://ix.io/2oeD

Here’s the lspci output (when booting with pci=nomsi) which shows the similar lines to the post suggesting this as a fix:

A couple of differences to that post, my board isn’t using a VIA chipset and I have the line:

I don’t know how important the +/- is after the Enable.

#5 2020-06-05 07:49:08

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

I’ve also tried latest linux kernel (5.6.15.arch1-1) but still get the same message.

In terms of debugging this, is it worth unplugging devices (USB devices, TV Tuner PCI card) to see if that stops the messages and, if so, reconnecting one by one to see which triggers this error?

On the plus side, it doesn’t seem to cause any issue to my system so far although, admittedly, it’s not doing much at the moment (just booting to login prompt) as I’m gradually installing the bits I need for the HTPC.

#6 2020-06-05 16:57:11

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Turns out, this isn’t quite true. From another thread on LKML it looks like the error was previously reported as

and, indeed, if I search dmesg on my HTPC (on Xubuntu 16.04 kernel: 4.4.0-131-generic #157-Ubuntu) I do have that exact line

Interestingly, that message is loglevel 7 on 4.4.0-131

but is now loglevel 0 on latest kernels. That’s quite an escalation.

So, I suspect there’s no quick fix for the message and it’s safe to ignore. I’d just prefer not to see it at all.

Last edited by elParaguayo (2020-06-05 16:57:54)

#7 2020-06-05 18:13:15

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

You could try the proposed patch from https://lkml.org/lkml/2019/3/7/212

#8 2020-06-05 18:13:21

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

There is an F5 version available, but i doubt it will help.

#9 2020-06-05 18:37:19

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

You could try the proposed patch from https://lkml.org/lkml/2019/3/7/212

Yes, although that post says the patch didn’t work so I wouldn’t hold out much hope. Also, it took about 5 hours to compile the kernel last time so I’m not desperate to do it again but no harm in trying.

There is an F5 version available, but i doubt it will help.

I doubt it too! It’s about 9 years old and this issue is still around. I’m also not desperate to update the BIOS unless I really have to.

#10 2020-06-05 18:44:38

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Also, it took about 5 hours to compile the kernel last time so I’m not desperate to do it again but no harm in trying.

Have you enabled parallel compilation? To reduce the compile time?

#11 2020-06-05 19:26:45

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Also, it took about 5 hours to compile the kernel last time so I’m not desperate to do it again but no harm in trying.

Have you enabled parallel compilation? To reduce the compile time?

Sadly, yes. I used the nproc line from that link. Not sure how long it would have taken without it.

It’s fine, I can always leave it running overnight.

#12 2020-06-06 09:10:26

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

The message was still there on boot.

I can hide it if I change loglevel kernel parameter to 0 but that, for some reason, stops plymouth working (when the error message was on the screen, you could see the resolution change before plymouth started but that’s not happening now). I’ll have a little play with the parameters but may start a new thread on that.

However, for this particular issue, it feels like we’ve gone as far as we can. Appreciate the support.

#13 2020-06-06 14:13:34

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

You could contact upstream see if they have any other suggestions for resolving the issue in the kernel or if it is just considered a firmware bug.

#14 2020-06-24 12:06:10

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Although I am a Manjaro user I want to mention here that just today this issue popped up with the BIOS upgrade that I did today. I installed new beta BIOS 7C37v193(Beta version) for my MSI MPG X570 GAMING EDGE WIFI board. I did not have any errors or issues with the previous beta 7C37v192(Beta version) which I was running for several weeks now.

This new BIOS 7C37v193(Beta version) is coming with «Updated AMD AGESA ComboAm4v2PI 1.0.0.2» as the only change and the messages I get with that are:

I seee this with kernel 5.4.48 and 5.7.5 with a Ryzen 7 3700X.

kernel command line parameter «pci=nomsi,noaer» does not help. It is not booting with nomsi and noaer alone makes no difference.

#15 2020-06-24 20:40:53

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

This new BIOS 7C37v193(Beta version) is coming with «Updated AMD AGESA ComboAm4v2PI 1.0.0.2» as the only change and the messages I get with that are:

I seee this with kernel 5.4.48 and 5.7.5 with a Ryzen 7 3700X.

kernel command line parameter «pci=nomsi,noaer» does not help. It is not booting with nomsi and noaer alone makes no difference.

Don’t mean to hijack the thread, but I just updated bios on my MSI x570 MB (with Ryzen 3800X) to version 7C35v196(beta) and started to get the same errors (was running previous beta for a couple of weeks without this error present, but with random crashes due to mce microcode errors and thought that I would try this new version).

Источник

Arch Linux

You are not logged in.

#1 2020-06-01 20:41:49

Error message during boot: do_IRQ: 1.55 No irq handler for vector

I’m getting an error message during boot which is slightly annoying as I’m trying to run silent boot on my HTPC. The message says

I don’t think it’s causing any particular issues on my system as I can boot in fine but I would like to get to the bottom of this.

I’ve seen a couple of posts on this forum with a similar issue but the one marked [solved] suggested using «acpi=noirq» as a kernel parameter. I tried that and it didn’t change the outcome.

Some relevant information about my system:

Any tips on how to resolve this would be greatly appreciated.

#2 2020-06-03 21:31:34

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

I’ve tried to do some more digging on this but not sure if I’m getting anywhere.

No mention of Vector 55. No idea where to go from here. Does anyone have any ideas?

#3 2020-06-03 22:28:52

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Does adding the kernel parameter nomsi have any effect?

#4 2020-06-04 05:25:38

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Does adding the kernel parameter nomsi have any effect?

Thanks loqs. I assume you mean:

which I saw in a couple of posts. If so, yes, I tried it as I had a similar line my lspci (see bottom of this post) and it didn’t stop the error message.

I tried it before the custom kernel so I’ve just retried it again to see if there was any change to the irqs outputs. The main difference was that it reduced the number of them:

dmesg output from this boot: http://ix.io/2oeD

Here’s the lspci output (when booting with pci=nomsi) which shows the similar lines to the post suggesting this as a fix:

A couple of differences to that post, my board isn’t using a VIA chipset and I have the line:

I don’t know how important the +/- is after the Enable.

#5 2020-06-05 07:49:08

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

I’ve also tried latest linux kernel (5.6.15.arch1-1) but still get the same message.

In terms of debugging this, is it worth unplugging devices (USB devices, TV Tuner PCI card) to see if that stops the messages and, if so, reconnecting one by one to see which triggers this error?

#6 2020-06-05 16:57:11

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Turns out, this isn’t quite true. From another thread on LKML it looks like the error was previously reported as

and, indeed, if I search dmesg on my HTPC (on Xubuntu 16.04 kernel: 4.4.0-131-generic #157-Ubuntu) I do have that exact line

Interestingly, that message is loglevel 7 on 4.4.0-131

but is now loglevel 0 on latest kernels. That’s quite an escalation.

So, I suspect there’s no quick fix for the message and it’s safe to ignore. I’d just prefer not to see it at all.

Last edited by elParaguayo (2020-06-05 16:57:54)

#7 2020-06-05 18:13:15

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

You could try the proposed patch from https://lkml.org/lkml/2019/3/7/212

#8 2020-06-05 18:13:21

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

There is an F5 version available, but i doubt it will help.

#9 2020-06-05 18:37:19

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

You could try the proposed patch from https://lkml.org/lkml/2019/3/7/212

There is an F5 version available, but i doubt it will help.

I doubt it too! It’s about 9 years old and this issue is still around. I’m also not desperate to update the BIOS unless I really have to.

#10 2020-06-05 18:44:38

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Also, it took about 5 hours to compile the kernel last time so I’m not desperate to do it again but no harm in trying.

Have you enabled parallel compilation? To reduce the compile time?

#11 2020-06-05 19:26:45

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

Also, it took about 5 hours to compile the kernel last time so I’m not desperate to do it again but no harm in trying.

Have you enabled parallel compilation? To reduce the compile time?

Sadly, yes. I used the nproc line from that link. Not sure how long it would have taken without it.

It’s fine, I can always leave it running overnight.

#12 2020-06-06 09:10:26

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

The message was still there on boot.

However, for this particular issue, it feels like we’ve gone as far as we can. Appreciate the support.

#13 2020-06-06 14:13:34

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

You could contact upstream see if they have any other suggestions for resolving the issue in the kernel or if it is just considered a firmware bug.

#14 2020-06-24 12:06:10

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

This new BIOS 7C37v193(Beta version) is coming with «Updated AMD AGESA ComboAm4v2PI 1.0.0.2» as the only change and the messages I get with that are:

I seee this with kernel 5.4.48 and 5.7.5 with a Ryzen 7 3700X.

kernel command line parameter «pci=nomsi,noaer» does not help. It is not booting with nomsi and noaer alone makes no difference.

#15 2020-06-24 20:40:53

Re: Error message during boot: do_IRQ: 1.55 No irq handler for vector

This new BIOS 7C37v193(Beta version) is coming with «Updated AMD AGESA ComboAm4v2PI 1.0.0.2» as the only change and the messages I get with that are:

I seee this with kernel 5.4.48 and 5.7.5 with a Ryzen 7 3700X.

kernel command line parameter «pci=nomsi,noaer» does not help. It is not booting with nomsi and noaer alone makes no difference.

Источник

Дефектные обновления [Core, Extra, Community, Multilib]

vasek
Появилось после очередного обновления или было давно?

Да как появилось ядро 4.15, так и пишет с того времени.
На работу не влияет, но смущает.

vasek
насколько помню, вроде у тебя не Intel, а значит отношения к тебе не имеет.

На работе AMD am2+, четыре ядра, на нём вылетает эта строка.
Дома AMD am3+, восемь ядер, этого сообщения нет.

kernel: do_IRQ: 0.55 No irq handler for vector

RusWolf
Да как появилось ядро 4.15, так и пишет с того времени.
На работу не влияет, но смущает.

Меня тоже. На LTS такого нет.

noaer: [PCIE] If the PCIEAER kernel config parameter is enabled, this kernel boot option can be used to disable the use of PCIE advanced error reporting.
nomsi: [MSI] If the PCI_MSI kernel config parameter is enabled, this kernel boot option can be used to disable the use of MSI interrupts system-wide.

Тогда забей. У меня периодически появляются такие сообщения, не влияющие на работу, и потом сами собой исчезающие после обновлений. Но уже месяца 2 как чисто и ничего не выскакивает.
Как то занялся этим вопросом и пришел к следующему:
вновь появляющиеся сообщения после обновления ядра, не влияющие на работу системы, появляются по следующим причинам
1. В новые ядра включается все больше новых аппаратных функций, которые не всегда полностью поддерживаются на старом железе, а потому и выскакивают всякого рода уведомляющие сообщения.
2. Разработчики ядра добавляют новые функции и при этом специально увеличивают логирование сообщений, что помогает отслеживать ошибки и избежать конфликтов с другими приложениями и системным программным обеспечением. После отработки или закрытия багов вывод таких сообщений удаляют.

akorop
mc в urxvt полностью перестал реагировать на мышь. В смысле, по клику не меняется положение курсора ни в панелях, ни в редакторе; по колесу не скроллируется, по двойному клику не входит в каталог в панелях и т.д.

Источник

Thread: No irq handler for vector

Thread Tools

Display

I’ve been working on getting an older desktop up and running (putting together the hardware).

I’m not quite sure what information might be helpful but I’ll take a shot.

Mobo: An old amberine board

RAM: 2.5 GB PC 3200 ddr sdram (2 X 1 GB + 2 X 256 MB)

Hard Drives: Master = WD 80 GB IDE drive; Slave = Maxtor Diamondmax 10, 100 GB IDE.

Optical Drives: Master = cd read/ write, IDE; Slave = DVD ROM (Philips brand)

These drives, the RAM, the two fans (CPU fan and the one on the back of the case) are currently the only things plugged into the mobo (plus the power supply to the mobo and this one other, square plug on the mobo).

In bios set up I see that all RAM sticks are recognized, CPU is recognized, and all four drives are recognized. I inserted the Ubuntu 10.04 LTS CD to see if I could run live and I get the following message, at which point the whole system hangs.

Does anyone know what’s going on? If you need more info just let me know what you need and I’ll get it for you.

Oh, by the way, I know for a fact that, that CD is fine. It’s the one I used to install 10.04 on this machine (my laptop) that I’m typing to you now. I’ve also run it live before in other machines. The disc isn’t scratched or dirty or anything (I checked).

Any help greatly appreciated. Been wrestling with that machine for a week.
—————————

To start out I had both hard drives on one channel and both optical drives on the other. On each channel there was a master and a slave. Then I got to wondering if that was the right way to go about it. I tried going down to just one drive and setting it up so there is one hard drive on one channel and a hard drive and an optical drive on the other. Nothing I do seems to work. This second configuration doesn’t really make sense because then you have two hard drives both set to master but what alse is there? I’m confused on how to set this up.

I’ve attached two pictures of the output I get when trying to run Ubuntu 10.04 live in that machine. The first one is from the first configurations and the second is from the second configuration.

Does anyone have any advice on the right way to set this up?

The Western Digital drive is a WD800. It’s jumpers have setting for whether a slave is present or whether the drive is by itself. I was careful to pay attention to this.

As far as optical drives go, I have 4 of them stacked up on the table in front of me. I don’t really care which one I use as long as it does what what I need it to within the system. One of them is a DVD ROM. Two of them are CD read/ write drives. The last one is a CD drive but I’m not entirely sure it isn’t just ROM.

The optical drives I have are:

Philips Model no: CDD4801/81
HP C4465-56000
Toshiba Model no: SD-M1002
Teac CD-524EA
—————————

Here is a link to the product specs for that machine.

I think I must have been a little tired when I wrote that o/p last night. I should be more specific about what is left that is original and not.

* The Orig equip that’s still part of machine:

It is a Maxtor Diamondmax 10

Western Digital 80 GB drive (WD800)
2 GB PC 3200 ddr sdram @400 MHz (2 X 1 GB)

It needs to have some optical drive of the ones I have

I have a bunch of expansion cards and one of them is a wireless NIC. At the very least I would like to have that wireless NIC in there eventually.

Right now I’m just trying to get a basic setup going. Not worrying about the card reader or media dock or expansion cards of any kind. Just thinking about hard drives and optical drives.
————————-

The output shown in the code box in the o/p was before I tried 2 other configurations. The two other configs result/ output is what’s shown in the pictures.

Re: No irq handler for vector

Is your boot order set to boot from cdrom first as you should be able to boot into the Live cd without ANY hard drives connected.

Try it.. Switch the computer off at the wall and just pull out the *molex’s to the hard drives

Boot into BIOS so it auto recognises no drives.. Save out and it’ll reboot, hopefully from the cdrom

If that’s successful you know you have a hard drive clash

btw. a single beep means a successful POST ( Power On Self Test)

*Molex’s are the power plugs to the drives. You don’t need to pull the IDE leads out to disable the drive, Just the power.
When you re-insert the molex plugs they are keyed but you can still push em in the wrong way.. If you do that then the blue smoke Genie escapes

Red lead on Molex always goes facing IDE lead

Is your boot order set to boot from cdrom first as you should be able to boot into the Live cd without ANY hard drives connected.

Try it.. Switch the computer off at the wall and just pull out the *molex’s to the hard drives

Boot into BIOS so it auto recognises no drives.. Save out and it’ll reboot, hopefully from the cdrom

If that’s successful you know you have a hard drive clash

btw. a single beep means a successful POST ( Power On Self Test)

Red lead on Molex always goes facing IDE lead

Thanks for showing up. The way I’ve gone about booting from disc is to enter the boot menu using the esc key. After reading your post though I wonder if I haven’t created a problem by something(s) I did before in bios setup. When I was adding drives in the beginning I would plug one in, boot up, go into setup then I’d ‘save and exit’ each time until all drives were added. After that, some changes were made by swapping out drives or the order of drives (master/slave or what channel they were on). I wonder if saving to bios like that messed me up because now it expects a certain thing and it isn’t like that any longer.

Also, somewhere in between there, is bios supposed to automatically boot from cd rom? I thought the default setting was to boot from the HD unless you tell it otherwise in setup or enter the boot menu and select the cd drive to boot from.

Thanks in advance for your help.
———————

I have another dumb question too but don’t know how else I would find out if I don’t ask.

I noticed the power plugs are numbered but have been wondering if it matters which one goes to which drive or what order they are in.

Re: No irq handler for vector

No question is stupid.

No.. Don’t plug the drives in yet (after doing all that)

I want to eliminate any possibility of hard drive clash.. so boot without them connected (boot from the live cd)

No it doesn’t matter what power plugs (Except for the main Motherboard connector) go where.. If it fits and is the right way round.. It’s good to go

Make sure you plug in the «square four» connector near the cpu if it has one too

No question is stupid.

No.. Don’t plug the drives in yet (after doing all that)

I want to eliminate any possibility of hard drive clash.. so boot without them connected (boot from the live cd)

No it doesn’t matter what power plugs (Except for the main Motherboard connector) go where.. If it fits and is the right way round.. It’s good to go

Make sure you plug in the «square four» connector near the cpu if it has one too

Well, how can it boot from a drive that isn’t plugged in?

I wonder if we are on the same page with a certain term «drive». When I say «drive» what I mean is any drive including hard drives and optical drives.

Re: No irq handler for vector

Leave the hard drives unpowered and only connect ONE cdrom

It should boot from optical (cdrom)

I’m trying to test your hardware

Don’t want to «edit» while someone may be reading.

And what about this thing of the channels and what drives to include on what channels. I understand this is maybe a later point than what we’re talking about but this has been a confusion for me.

Ideally, would want the two hard drives, the DVD ROM drive and a CD read/ write drive (that makes 4). There are 2 channels. That raises the question of whether to combine both hard drives on one channel and both optical drives on one channel or to have it with a hard drive and an optical drive on each channel.

The reason I think of this now, at this stage is that to boot from cd rom that drive is gonna have to be plugged into one or the other channels right? And it’s going to have to have some jumper setting as well. Should this not be on my mind from the beginning?

Brother. I’m not trying to test your patience. I get what we’re trying to do here. It’s me. It’s that there are like 4 things in play when it comes to this stuff. Which are important at this stage (testing the hardware) and which aren’t I don’t know. You have: channels (two of them) you have jumpers, with 4 drives and 2 channels you have to make jumper decisions. Even if I am only plugging in the one, cd rom, drive right now, does it matter to make a decision on where to set the jumper and what channel for it to be on based on where you want it to end up in the end (when all drives are connected in the end). I don’t understand if this is important right now or not. What I’m really trying to get my mind around is what I would ‘physically’ be doing. I think I understand clearly but I’ve seen this computer (and I think it safe to say all computers) be very finicky about stupid little details like this. If I think I understand but don’t and I end up doing it differently in some way, the result may not be positive and then your time get’s wasted and we go through all kinds of talking back and forth and end up finding out there was some stupid mistake I made because I didn’t understand correctly to begin with. It isn’t the result or what we’re trying to do that I’m questioning, it’s the ‘precise’ way to achieve that result.

What I think you mean, what I think needs to happen (If I’m understanding correctly) is this:

> 1 unplug ALL drives (hard drives and disc drives) from the power plug but not the ide, flat, cable.
> 2 power up the machine and enter bios setup
> 3 check to see that there are no drives being recognized; and, if so, «save and exit»
> 4 power off the machine
> 5 plug the power plug only into the cd rom drive and no other drives
> 6 power up the machine

Problem: at this point there will be no cd in the drive. Either I will need to have inserted the cd at some point before beginning all the above or I will need to hit the pause button (something that, for all I know, interrupts what we’re trying to do somehow).

I have to assume that it doesn’t matter what channel that cd rom drive is on. After all the plugs on the mobo are colored differently and intuition would say that any difference is supposed to mean there is a difference. I wouldn’t know though.

This is the newbie experience. In a way, we are like a computer. If the knowledge isn’t there, since we are humans and not computers, we can make and assumption rather than just and error output. The computer won’t do that though. It’ll take my assumption; at best, give me an error output, at worst, wreck a drive or two.

Please Swagman, please understand me. This would be easy for you because you’ve already dealt with these petty little questions and know the answers. I only need to learn them once, then I’ll remember forever.

I’m going forward with:

Insert the cd first, then power off, then the steps I listed out above. I hope that’s right and doesn’t make needless effort or confusion.

Источник