Howdy During my first stumbling step with SuSE i ran into some NIC problem that Marshall kindly unfolded for me. He among other things told me to have a look at the possibility of a irq conflict. Well everything started to work so it was put off for later. Now i have had a look at the startup sequence, and it is not a pretty site ;-) Here is what shows in bios boot up. Bus | Dev | Fun | Dev Class | Irq 0 1 1 Sm Buss 9 0 2 0 Usb 1,1 5 0 2 1 Usb 1,1 11 0 2 2 Usb 2,0 9 0 4 0 Net card 9 0 9 0 IDE 14 0 13 0 IEEE 1394 Host 5 1 10 0 Multimedia 11 1 10 1 Input NA 1 10 2 IEEE 1394 Host 11 1 11 0 Net card 9 1 13 0 Mass Storage 11 3 0 0 Display 11 ACPI 9 Not a pretty site at all. Below is what Windooze thinks about it. (ISA) 0 System Timer (ISA) 1 Keyboard (ISA) 2 NOT USED (ISA) 3 Comm 2 (ISA) 4 Comm 1 (ISA) 5 NOT USED (ISA) 6 Standard Disk (ISA) 7 NOT USED (ISA) 8 Sys CMOS (ISA) 9 ACPI (ISA) 10 MPU-401 Midi (ISA) 11 NOT USED (ISA) 12 PS/2 Mouse (ISA) 13 Numeric Data Processor (ISA) 14 Pri IDE (ISA) 15 Sec IDE (PCI) 9 Nvidia nForce PCI System Management (PCI) 16 Intel Pro 1000 Nic (PCI) 18 Creative Audigy zs (PCI) 18 Silicon Image SATA Link Controller (PCI) 19 Nvidia GeForce FX5600 (PCI) 19 OHCI-compatible IEEE 1394-Host (PCI) 20 Standard Enhanced PCI to USB Host Controller (PCI) 21 nVidia nForce MCP Nic (PCI) 21 Standard Open HCD Usb Host (PCI) 22 OHCI-compatible IEEE 1394-Host (PCI) 22 Standard Open HCD Usb Host It looks like a mess ... Only the Sound & Video are cards the rest is on the mobo. Sense the irq's differ between boot and win. I presume i got it in plug and play mod in bios.The problem us i can only change the irq of the outside cards in bios, not the on board stuff. I'm thinking of playing around with the settings in bios to see if i can get things going. Questions. 1. If i change irq and SuSE don t like it. Is it enough to change it back or is there a possibility to ruin the installation. 2. Any suggestions on what to do to separate the irq's. 3. If i switch off one of the usb and one of the ieee, what happens to SuSE when it does not find them tough they was installed. 4. Is there a simple way to see in SuSE what the irq's are. I locked at HWINFO but then i have to do it for all devices. Is there a place to See all irq's given. 5. I've only seen ISA 1-15 before, never PCI 9-22. How does SuSE handle it. Or is it M$ handling only. Phiew T hank's every one on list for all the interesting writing. It's so much to read and try out that it's hard to get time to wright :-) //Andy
Unless you have an ISA card, which is an impossibility since it's obviously a newer motherboard with USB 2.0 and Firewire and they don't come with ISA slots anymore. You only have PCI bus, which shares IRQ's and conflicts don't occur. Don't mix with the settings in the BIOS, except to tell it to leave the configuration to the Operating System. PS. "If it ain't broken, don't fix it". On Monday 24 November 2003 10:27, Anders Lundin wrote:
Howdy During my first stumbling step with SuSE i ran into some NIC problem that Marshall kindly unfolded for me. He among other things told me to have a look at the possibility of a irq conflict. Well everything started to work so it was put off for later. Now i have had a look at the startup sequence, and it is not a pretty site ;-) Here is what shows in bios boot up.
Bus | Dev | Fun | Dev Class | Irq 0 1 1 Sm Buss 9 0 2 0 Usb 1,1 5 0 2 1 Usb 1,1 11 0 2 2 Usb 2,0 9 0 4 0 Net card 9 0 9 0 IDE 14 0 13 0 IEEE 1394 Host 5 1 10 0 Multimedia 11 1 10 1 Input NA 1 10 2 IEEE 1394 Host 11 1 11 0 Net card 9 1 13 0 Mass Storage 11 3 0 0 Display 11 ACPI 9
Not a pretty site at all. Below is what Windooze thinks about it.
(ISA) 0 System Timer (ISA) 1 Keyboard (ISA) 2 NOT USED (ISA) 3 Comm 2 (ISA) 4 Comm 1 (ISA) 5 NOT USED (ISA) 6 Standard Disk (ISA) 7 NOT USED (ISA) 8 Sys CMOS (ISA) 9 ACPI (ISA) 10 MPU-401 Midi (ISA) 11 NOT USED (ISA) 12 PS/2 Mouse (ISA) 13 Numeric Data Processor (ISA) 14 Pri IDE (ISA) 15 Sec IDE (PCI) 9 Nvidia nForce PCI System Management (PCI) 16 Intel Pro 1000 Nic (PCI) 18 Creative Audigy zs (PCI) 18 Silicon Image SATA Link Controller (PCI) 19 Nvidia GeForce FX5600 (PCI) 19 OHCI-compatible IEEE 1394-Host (PCI) 20 Standard Enhanced PCI to USB Host Controller (PCI) 21 nVidia nForce MCP Nic (PCI) 21 Standard Open HCD Usb Host (PCI) 22 OHCI-compatible IEEE 1394-Host (PCI) 22 Standard Open HCD Usb Host
It looks like a mess ... Only the Sound & Video are cards the rest is on the mobo.
Sense the irq's differ between boot and win. I presume i got it in plug and play mod in bios.The problem us i can only change the irq of the outside cards in bios, not the on board stuff. I'm thinking of playing around with the settings in bios to see if i can get things going. Questions. 1. If i change irq and SuSE don t like it. Is it enough to change it back or is there a possibility to ruin the installation.
2. Any suggestions on what to do to separate the irq's.
3. If i switch off one of the usb and one of the ieee, what happens to SuSE when it does not find them tough they was installed.
4. Is there a simple way to see in SuSE what the irq's are. I locked at HWINFO but then i have to do it for all devices. Is there a place to See all irq's given. 5. I've only seen ISA 1-15 before, never PCI 9-22. How does SuSE handle it. Or is it M$ handling only.
Phiew
T hank's every one on list for all the interesting writing. It's so much to read and try out that it's hard to get time to wright :-) //Andy
occur. Don't mix with the settings in the BIOS, except to tell it to leave the configuration to the Operating System. Maybe someone else can correct me if I am wrong but when I had this
Örn Hansen wrote: problem over a year ago, I even contacted the writer of the NIC driver. He told me that sharing would work but only if the BIOS was set to NO for PnP operating system. Perhaps things have changed since then but Linux did not handle PnP like Windows 9x so the BIOS had to do it. When I changed to BIOS management instead of OS management, my problem was solved and the two net cards were able to share an interrupt. Damon REgister
On Monday 24 November 2003 16:49, Damon Register wrote:
Maybe someone else can correct me if I am wrong but when I had this problem over a year ago, I even contacted the writer of the NIC driver. He told me that sharing would work but only if the BIOS was set to NO for PnP operating system. Perhaps things have changed since then but Linux did not handle PnP like Windows 9x so the BIOS had to do it. When I changed to BIOS management instead of OS management, my problem was solved and the two net cards were able to share an interrupt.
The only difference I've seen, with interrupt asignement is with cards that are ISA cards. If you have one of these, you used to go to the BIOS and assign that IRQ as a legendary/ISA interrupt (meaning the BIOS would not assign it to a PCI device). So, that such devices could use the preconfigured resource tables they had. And, personally I've never encountered this, but it's also stated that some of the first PCI NIC's suffered similar problems when IRQ's were concerned as the old ISA cards. So, my guess is, that it was because of such a card that you needed to mark it as non-PnP. But Linux has, to my knowledge, always assigned PCI Irq's on its own and separately from the BIOS.
<snip>
Bus | Dev | Fun | Dev Class | Irq 0 1 1 Sm Buss 9 0 2 0 Usb 1,1 5 0 2 1 Usb 1,1 11 0 2 2 Usb 2,0 9 0 4 0 Net card 9 0 9 0 IDE 14 0 13 0 IEEE 1394 Host 5 1 10 0 Multimedia 11 1 10 1 Input NA 1 10 2 IEEE 1394 Host 11 1 11 0 Net card 9 1 13 0 Mass Storage 11 3 0 0 Display 11 ACPI 9
Not a pretty site at all. Below is what Windooze thinks about it.
(ISA) 0 System Timer (ISA) 1 Keyboard (ISA) 2 NOT USED (ISA) 3 Comm 2 (ISA) 4 Comm 1 (ISA) 5 NOT USED (ISA) 6 Standard Disk (ISA) 7 NOT USED (ISA) 8 Sys CMOS (ISA) 9 ACPI (ISA) 10 MPU-401 Midi (ISA) 11 NOT USED (ISA) 12 PS/2 Mouse (ISA) 13 Numeric Data Processor (ISA) 14 Pri IDE (ISA) 15 Sec IDE (PCI) 9 Nvidia nForce PCI System Management (PCI) 16 Intel Pro 1000 Nic (PCI) 18 Creative Audigy zs (PCI) 18 Silicon Image SATA Link Controller (PCI) 19 Nvidia GeForce FX5600 (PCI) 19 OHCI-compatible IEEE 1394-Host (PCI) 20 Standard Enhanced PCI to USB Host Controller (PCI) 21 nVidia nForce MCP Nic (PCI) 21 Standard Open HCD Usb Host (PCI) 22 OHCI-compatible IEEE 1394-Host (PCI) 22 Standard Open HCD Usb Host
It looks like a mess ...
<a little more snippage>
Questions. 1. If i change irq and SuSE don t like it. Is it enough to change it back or is there a possibility to ruin the installation.
From what little that I know, you can change it and not ruin the install. Although you may have to edit the necessary files by hand.
2. Any suggestions on what to do to separate the irq's.
Some items will work sharing the same interrupt. Some will not. I would try and have everything on it's own IRQ if possible. You can start by looking in your motherboard's documentation. This may help you assign IRQ's to the PCI slots on the board.
3. If i switch off one of the usb and one of the ieee, what happens to SuSE when it does not find them tough they was installed.
They will not be able to be used. SuSE may (emphasize the word may) even not show it as a device attached to the system. It depends on how much automation is in SuSE 9. (Still do not have it yet. Trying to get the boss *wife* to allow me to get it)
4. Is there a simple way to see in SuSE what the irq's are. I locked at HWINFO but then i have to do it for all devices. Is there a place to See all irq's given.
Yep try "cat /proc/interrupts" without the quotes.
5. I've only seen ISA 1-15 before, never PCI 9-22. How does SuSE handle it. Or is it M$ handling only.
Windows is just telling you what bus the IRQ is on.
T hank's every one on list for all the interesting writing. It's so much to read and try out that it's hard to get time to wright :-)
Yes there is alot to digest on this list. You can learn alot by just reading what others issues are and seeing how members here solve them. -- Marshall "Nothing is impossible, we just do not have all the answers to make the impossible, possible."
On Monday 24 November 2003 12:56, Marshall Heartley wrote:
Some items will work sharing the same interrupt. Some will not. I would try and have everything on it's own IRQ if possible. You can start by looking in your motherboard's documentation. This may help you assign IRQ's to the PCI slots on the board.
3. If i switch off one of the usb and one of the ieee, what happens to SuSE when it does not find them tough they was installed.
They will not be able to be used. SuSE may (emphasize the word may) even not show it as a device attached to the system. It depends on how much automation is in SuSE 9. (Still do not have it yet. Trying to get the boss *wife* to allow me to get it)
The PC has only 15 interupts, nothing more. Of which, a few are already taken and cannot be shared by any other source. A few are assigned to legendary devices, like 3.4,5,7. Which leaves you with just a few interupts that you have to share with 22 sources. If you can distribute 9 interupts individually among 22 sources, your a math genius. Unless you have an older mainboard, an old ISA or one of the first PCI cards, or Microchannel card >:) ... the OS, weather Windows, Linux or Mac OS will take care of assigning resources. Iff, you are so unlucky to have an old NIC that has no other ability but to use resources already assigned, it's much cheaper, simpler and gives less a headache to go and buy a new NIC for $6.95. My 2¢ worth.
The PC has only 15 interupts, nothing more. Of which, a few are already taken and cannot be shared by any other source. A few are assigned to legendary devices, like 3.4,5,7. Which leaves you with just a few interupts that you have to share with 22 sources. If you can distribute 9 interupts individually among 22 sources, your a math genius.
I am not a math genius. I just suggested that if he could do that, it would be preferred. I do know that the computers only have 14 interrupts even though they show you 15. 2 and 9 are the same thing. Some mobo's like mine will allow you to change some of the interrupts.
Unless you have an older mainboard, an old ISA or one of the first PCI cards, or Microchannel card >:) ... the OS, weather Windows, Linux or Mac OS will take care of assigning resources. Iff, you are so unlucky to have an old NIC that has no other ability but to use resources already assigned, it's much cheaper, simpler and gives less a headache to go and buy a new NIC for $6.95.
I do agree that if the network interface resources cannot be changed, then it is better to buy a new one and try it. I had that same exact issue just yesterday when trying to upgrade my NIC card. -- Marshall "Nothing is impossible, we just do not have all the answers to make the impossible, possible."
On Monday 24 November 2003 15:07, Marshall Heartley wrote:
I am not a math genius. I just suggested that if he could do that, it would be preferred. I do know that the computers only have 14 interrupts even though they show you 15. 2 and 9 are the same thing. Some mobo's like mine will allow you to change some of the interrupts.
Your right, there are only 14 of them. 2 and 9 are the same, and Zero is a non-assignable one. The output in the message, was from a brand-new mobo, too new to cause problems and the question too general, to be one. Has an FX5600 (High end graphics card), Serial ATA, USB 1.1/2.0 and Firewire, and probably came with XP Pro pre-installed. Being that new, it's probably got a built in NIC, either 3COM or RealTek. You get the picture.
Örn Hansen wrote:
The output in the message, was from a brand-new mobo, too new to cause problems and the question too general, to be one. Has an FX5600 (High end graphics card), Serial ATA, USB 1.1/2.0 and Firewire, and probably came with XP Pro pre-installed. Being that new, it's probably got a built in NIC, either 3COM or RealTek.
You get the picture.
Almost right. The box is built from scratch. Nothing pre installed. Both NIC's are built in. One is nVidia 10/100 & one is intel 1000. The old mobo was also only pci. but i don't recall anything BUT isa in winmanager. If you say SuSE handles assigning GOD by it self i have to trust you on that. It just makes me itchy to see that many shares on one irq. //Andy
On Monday 24 November 2003 18:31, Anders Lundin wrote:
Almost right. The box is built from scratch. Nothing pre installed. Both NIC's are built in. One is nVidia 10/100 & one is intel 1000. The old mobo was also only pci. but i don't recall anything BUT isa in winmanager. If you say SuSE handles assigning GOD by it self i have to trust you on that. It just makes me itchy to see that many shares on one irq.
Thank God the headaches of the old times are in the past ... install and enjoy walking into the future. No more dbase II, III, or IV. No Foxpro, or Access ... SQL is not just for IBM Mainframes. No more cobol, no more CICS ... Oh, what a wonderful world! ;-)
Hi list, I've installed the latest SuSE 9 and wants to use vmware gsx on this server. When I install vmware it prompts me when it wants to overwrite the vmon.c files. I choose no here and I get this error: Version mismatch with vmmon module: expecting 42.0, got 52.0. You have an incorrect version of the `vmmon' kernel module. Try reinstalling VMware GSX Server. Have anyone installed vmware gsx server on SuSE 9 successfully? -- Trond
participants (5)
-
Anders Lundin -
Damon Register -
Marshall Heartley -
Trond Kringstad -
Örn Hansen