Re: [Cooker] rtl8139 on the network boot disk
On Wednesday 31 January 2001 17:39, you wrote: > > Ummm try turning off PnP OS in your BIOS--reliable as a rain > > dance but what > > do you have to lose? > > Last night I tried both on and off, to no avail. And I installed Win98SE > and the card works in that, so I know it's not bad hardware. So I've > narrowed it down to IRQs (which I thought didn't matter any more in this > brave new world of PCI, but what do I know?). I ripped out the sound card, > just in case, leaving the network card, video card (Matrox Millennium II), > and a Voodoo 1 card. And, I figured out, USB. It's not a card, but it was > using an IRQ. The same IRQ as my NIC. (Different I/O range, but same IRQ) > No matter what I did, no matter how I changed it in Windows (using the > handy-dandy Device Manager), it always set the IRQ of my NIC and the IRQ > for the USB to the same thing. That's probably due to the whole "IRQ > routing" thing I know nothing about, right? So I looked around in the BIOS > and found an entry "Assign IRQ to USB". I set that to disabled. But it > didn't solve my problem. It did, however generate different output during > the bootup. (Now, work with me here, I was reading it as fast as I could as > it scrolled by, but this should be close.) > > Either way, with "IRQ for USB" enabled or disabled, I get this: > > <4> Unknown bridge resource 0: assuming transparent > <4> Unknown bridge resource 1: assuming transparent > <4> Unknown bridge resource 2: assuming transparent > <4> PCI: Using IRQ router PIIX (8086/7110) at 00:07.0 > > If I disable "IRQ for USB", I also get this, : > > <4> PCI: Found IRQ 10 for device 00:07.2 > <4> PCI: The same IRQ used for device 00:09.0 > > Does any of that make sense to anyone? Cause I'm pretty sure it relates to > my problem, but being a Java programmer by trade, not a kernel hacker, I'm > a bit stumped. :-) > > Eaon > > p.s. This may be getting way beyond a cooker problem, and if it is, feel > free to tell me to junk the whole thing and do something different. ;-) I think you are on the right track... Assign the USB to an unused IRQ and try swapping slots (some PCI slots will handle only certain interrupts, but since interrupts can be shared, everything should be OK, right? ...Wrong, espcially with NICs). It should not be necessary to pull cards. Question. Is the NIC in the slot next to where you would have an agp video card? If so, it tries to share an interrupt with AGP... Doesn't work very well--activate network and screen blanks. This is true only of some AGPs--RAGE IIC and Intel EtherPro 10/100 were infamous for this. Civileme
RE: [Cooker] rtl8139 on the network boot disk
> Ummm try turning off PnP OS in your BIOS--reliable as a rain > dance but what > do you have to lose? Last night I tried both on and off, to no avail. And I installed Win98SE and the card works in that, so I know it's not bad hardware. So I've narrowed it down to IRQs (which I thought didn't matter any more in this brave new world of PCI, but what do I know?). I ripped out the sound card, just in case, leaving the network card, video card (Matrox Millennium II), and a Voodoo 1 card. And, I figured out, USB. It's not a card, but it was using an IRQ. The same IRQ as my NIC. (Different I/O range, but same IRQ) No matter what I did, no matter how I changed it in Windows (using the handy-dandy Device Manager), it always set the IRQ of my NIC and the IRQ for the USB to the same thing. That's probably due to the whole "IRQ routing" thing I know nothing about, right? So I looked around in the BIOS and found an entry "Assign IRQ to USB". I set that to disabled. But it didn't solve my problem. It did, however generate different output during the bootup. (Now, work with me here, I was reading it as fast as I could as it scrolled by, but this should be close.) Either way, with "IRQ for USB" enabled or disabled, I get this: <4> Unknown bridge resource 0: assuming transparent <4> Unknown bridge resource 1: assuming transparent <4> Unknown bridge resource 2: assuming transparent <4> PCI: Using IRQ router PIIX (8086/7110) at 00:07.0 If I disable "IRQ for USB", I also get this, : <4> PCI: Found IRQ 10 for device 00:07.2 <4> PCI: The same IRQ used for device 00:09.0 Does any of that make sense to anyone? Cause I'm pretty sure it relates to my problem, but being a Java programmer by trade, not a kernel hacker, I'm a bit stumped. :-) Eaon p.s. This may be getting way beyond a cooker problem, and if it is, feel free to tell me to junk the whole thing and do something different. ;-)
Re: [Cooker] rtl8139 on the network boot disk
"Eaon" <[EMAIL PROTECTED]> writes: > Well, it didn't work. I fmirror'd when I got home last night, and saw a new > network.img come down, so I tried that with 8139too.o. No go. I then tried > compiling rtl8139.o on my existing 7.2 system and adding it through expert > mode, and that failed too. So that leaves me with: a) It needs some > parameters to the module that I don't now, or b) it's an IRQ conflict - how > do I deal with that? Parameters that I don't know, probably, or c) it's a > hardware problem, and I've got bigger fish to fry, as it were. I think > tonight I'll install Win(bloze)98 and see if its fab-o nifty plug and pray > can find the card (how's that for asking to be flamed). If it can't either, > then I know I've got a hardware problem. If it can, then it's (a) or (b). > But it's looking less and less like a software issue, and more like a quirk > of my system. My best guess was to go with the kernel 2.4 and the fact that there is no more rtl8139.o in it.. -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] rtl8139 on the network boot disk
On Tuesday 30 January 2001 17:20, you wrote: > Well, it didn't work. I fmirror'd when I got home last night, and saw a > new network.img come down, so I tried that with 8139too.o. No go. I then > tried compiling rtl8139.o on my existing 7.2 system and adding it through > expert mode, and that failed too. So that leaves me with: a) It needs some > parameters to the module that I don't now, or b) it's an IRQ conflict - how > do I deal with that? Parameters that I don't know, probably, or c) it's a > hardware problem, and I've got bigger fish to fry, as it were. I think > tonight I'll install Win(bloze)98 and see if its fab-o nifty plug and pray > can find the card (how's that for asking to be flamed). If it can't > either, then I know I've got a hardware problem. If it can, then it's (a) > or (b). But it's looking less and less like a software issue, and more like > a quirk of my system. > > Eaon Ummm try turning off PnP OS in your BIOS--reliable as a rain dance but what do you have to lose? Civileme > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, January 30, 2001 5:33 AM > > To: [EMAIL PROTECTED] > > Cc: Eaon > > Subject: Re: [Cooker] rtl8139 on the network boot disk > > > > "Eaon" <[EMAIL PROTECTED]> writes: > > > Well, actually, I did try that one, mainly because it looked so > > > > promising > > > > > (the magic number "8139" and all). It didn't work. So then I got > > > frustrated and went down the entire list and tried each and every > > > module listed, all to no good effect. :-) Is it picky about the I/O > > > > address or > > > > > anything (I'm pretty sure the BIOS is set to "Plug and play OS > > > > = NO" - would > > > > > that matter?). I dunno, I'm just guessing there. Maybe I've > > > > actually found > > > > > a bug. Wouldn't that be exciting for me. > > > > If it's a PCI card, apart from a IRQ/DMA conflict everything should run > > fine.. > > > > > Anyway, the thread titled "install hd.img for BusLogic" has a > > > > reference to > > > > > using expert mode to choose extra modules (quoting Guillaume > > > Cottenceau: "Copy it on an ext2-filesystem'ed floppy, type "expert" at > > > boot > > > > time and put > > > > > this floppy as an additional modules floppy."). Silly me, not > > > > being so full > > > > > of myself as to consider myself an expert (I always choose expert or > > > "custom" when install M$ stuff, why not Linux stuff). :-) > > > > I'll see what I > > > > > can make of that tonight (build rtl8139.o on my 7.2 box and > > > > insert it using > > > > > expert mode). > > > > Be careful, this is done at very early stage, so you have to manually > > provide all potential modules requirements to each modules (f.ex. > > advansys.o requires scsi_mod.o). > > > > Also, in expert mode, no PCI autoprobing is done. > > > > > > > > -- > > Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
RE: [Cooker] rtl8139 on the network boot disk
Well, it didn't work. I fmirror'd when I got home last night, and saw a new network.img come down, so I tried that with 8139too.o. No go. I then tried compiling rtl8139.o on my existing 7.2 system and adding it through expert mode, and that failed too. So that leaves me with: a) It needs some parameters to the module that I don't now, or b) it's an IRQ conflict - how do I deal with that? Parameters that I don't know, probably, or c) it's a hardware problem, and I've got bigger fish to fry, as it were. I think tonight I'll install Win(bloze)98 and see if its fab-o nifty plug and pray can find the card (how's that for asking to be flamed). If it can't either, then I know I've got a hardware problem. If it can, then it's (a) or (b). But it's looking less and less like a software issue, and more like a quirk of my system. Eaon > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 30, 2001 5:33 AM > To: [EMAIL PROTECTED] > Cc: Eaon > Subject: Re: [Cooker] rtl8139 on the network boot disk > > > "Eaon" <[EMAIL PROTECTED]> writes: > > > Well, actually, I did try that one, mainly because it looked so > promising > > (the magic number "8139" and all). It didn't work. So then I got > > frustrated and went down the entire list and tried each and every module > > listed, all to no good effect. :-) Is it picky about the I/O > address or > > anything (I'm pretty sure the BIOS is set to "Plug and play OS > = NO" - would > > that matter?). I dunno, I'm just guessing there. Maybe I've > actually found > > a bug. Wouldn't that be exciting for me. > > If it's a PCI card, apart from a IRQ/DMA conflict everything should run > fine.. > > > > Anyway, the thread titled "install hd.img for BusLogic" has a > reference to > > using expert mode to choose extra modules (quoting Guillaume Cottenceau: > > "Copy it on an ext2-filesystem'ed floppy, type "expert" at boot > time and put > > this floppy as an additional modules floppy."). Silly me, not > being so full > > of myself as to consider myself an expert (I always choose expert or > > "custom" when install M$ stuff, why not Linux stuff). :-) > I'll see what I > > can make of that tonight (build rtl8139.o on my 7.2 box and > insert it using > > expert mode). > > Be careful, this is done at very early stage, so you have to manually > provide all potential modules requirements to each modules (f.ex. > advansys.o requires scsi_mod.o). > > Also, in expert mode, no PCI autoprobing is done. > > > > -- > Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] rtl8139 on the network boot disk
"Eaon" <[EMAIL PROTECTED]> writes: > Well, actually, I did try that one, mainly because it looked so promising > (the magic number "8139" and all). It didn't work. So then I got > frustrated and went down the entire list and tried each and every module > listed, all to no good effect. :-) Is it picky about the I/O address or > anything (I'm pretty sure the BIOS is set to "Plug and play OS = NO" - would > that matter?). I dunno, I'm just guessing there. Maybe I've actually found > a bug. Wouldn't that be exciting for me. If it's a PCI card, apart from a IRQ/DMA conflict everything should run fine.. > Anyway, the thread titled "install hd.img for BusLogic" has a reference to > using expert mode to choose extra modules (quoting Guillaume Cottenceau: > "Copy it on an ext2-filesystem'ed floppy, type "expert" at boot time and put > this floppy as an additional modules floppy."). Silly me, not being so full > of myself as to consider myself an expert (I always choose expert or > "custom" when install M$ stuff, why not Linux stuff). :-) I'll see what I > can make of that tonight (build rtl8139.o on my 7.2 box and insert it using > expert mode). Be careful, this is done at very early stage, so you have to manually provide all potential modules requirements to each modules (f.ex. advansys.o requires scsi_mod.o). Also, in expert mode, no PCI autoprobing is done. -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
RE: [Cooker] rtl8139 on the network boot disk
Well, actually, I did try that one, mainly because it looked so promising (the magic number "8139" and all). It didn't work. So then I got frustrated and went down the entire list and tried each and every module listed, all to no good effect. :-) Is it picky about the I/O address or anything (I'm pretty sure the BIOS is set to "Plug and play OS = NO" - would that matter?). I dunno, I'm just guessing there. Maybe I've actually found a bug. Wouldn't that be exciting for me. Anyway, the thread titled "install hd.img for BusLogic" has a reference to using expert mode to choose extra modules (quoting Guillaume Cottenceau: "Copy it on an ext2-filesystem'ed floppy, type "expert" at boot time and put this floppy as an additional modules floppy."). Silly me, not being so full of myself as to consider myself an expert (I always choose expert or "custom" when install M$ stuff, why not Linux stuff). :-) I'll see what I can make of that tonight (build rtl8139.o on my 7.2 box and insert it using expert mode). I will also try 8139too.o again, just to make sure I'm not lying about it not working. ;-) Eaon > -Original Message- > From: Robin Cook [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 29, 2001 4:06 PM > To: Eaon > Cc: [EMAIL PROTECTED] > Subject: Re: [Cooker] rtl8139 on the network boot disk > > > Hello Eaon, > > The module you are looking for is 8139too.o in the 2.4.0 kernels. > > Monday, January 29, 2001, 10:23:28 AM, you wrote: > > E> Second try - sent this last week and it never went through - > was something > E> broken perhaps? Or I got censored for being an idiot, who knows. ;-) > > > E> Ok, go easy on me. I've just recently put on the chef's hat > and entered the > E> kitchen. But alas, I'm stuck at the door. > > E> I've mirrored cooker to a working machine running 7.2. I want > to set up > E> over the network (NFS) to another machine, so I created the > network boot > E> disk. But the system I'm going to install on has a DLink > DFE-538TX card, > E> which uses rtl8139.o. It's not in the list of available > modules (though > E> it's a decent card for the price, working for me on other machines - it > E> should work). How do I a) add it to the list or b) get some > nice person to > E> see to it that the driver is on the next version of that disk? > > E> Or, inspiration strikes, could I ALT-F? to somewhere and > insmod it manually? > E> ATL-F3 and ALT-F4 have no prompt at which to type, so I'm not > seeing this as > E> a possibility, but perhaps... > > E> Eaon > > -- > Best regards, > Robinmailto:[EMAIL PROTECTED] > >
Re: [Cooker] rtl8139 on the network boot disk
Hello Eaon, The module you are looking for is 8139too.o in the 2.4.0 kernels. Monday, January 29, 2001, 10:23:28 AM, you wrote: E> Second try - sent this last week and it never went through - was something E> broken perhaps? Or I got censored for being an idiot, who knows. ;-) E> Ok, go easy on me. I've just recently put on the chef's hat and entered the E> kitchen. But alas, I'm stuck at the door. E> I've mirrored cooker to a working machine running 7.2. I want to set up E> over the network (NFS) to another machine, so I created the network boot E> disk. But the system I'm going to install on has a DLink DFE-538TX card, E> which uses rtl8139.o. It's not in the list of available modules (though E> it's a decent card for the price, working for me on other machines - it E> should work). How do I a) add it to the list or b) get some nice person to E> see to it that the driver is on the next version of that disk? E> Or, inspiration strikes, could I ALT-F? to somewhere and insmod it manually? E> ATL-F3 and ALT-F4 have no prompt at which to type, so I'm not seeing this as E> a possibility, but perhaps... E> Eaon -- Best regards, Robinmailto:[EMAIL PROTECTED]
