The kernnels debian is using is too old 2.4.18 & 2.4.20.

To get nforce2 running wiith dma on the ide controler, sata raid on the sil controler, the 3com lan, nvlan, APIC, SMBus & firewire working u need 2.4.21
or newer. 2.6.0test 4 is what I have, & my sata raid 0 works in ata6 mode.

a7n8x dx.
http://home.t-online.de/home/Johanne...rce2linux.html

firewire
http://www.linux1394.org/view_device.php?id=444

yes that's what I think , but I've been unable to boot the installation from 2.4.21 custom kernel:

1º rescue boot diskette works fine
2ª root disk works also
3º when in "install kernel and modules" it asks for the rescue diskette again.
4º and then when I put the rescue floppy again , it keeps saying it's the wrong one.

From here I can't advance.

it's the far I could get in installation

Does that have the nForce2 nvnet LAN driver in it? Given that it's closed source and commercial it's not the sort of thing I'd expect on a Debian CD. If it isn't, then your not going to be able to do much with it (unless you have one of those overpriced nForce2 boards with the otherwise useless second LAN chip on it) as you won't be able to get basic networking up and running.

It boots.There is no debian anything with a nvnet driver.But his problem seems to be that the debian CD doesn't even boot with a nforce2 board.You'll always have to get a kernel plus headers plus gcc on anything debian before you can install the net driver.If you are further hampered (as I am) with a FX graphics card that doesn't even get recognised by the regular xfree driver things become a pain in the butt pretty quick with anything but gentoo at the moment.

bf24 works for me (and 2.4.18 too), look for help in the following forum:

http://www.nforcershq.com/forum/view...2126ab8a49bdcd

It's only for nforce mobos and i get a lot of help there.

Don't the nVidia Linux graphics drivers (version 4496 at least) support FX cards?

The debian cd boots on nforce2! my case:

got the debian cd 1 3.0r1, install with the regular kernel (2.2.x?), no problems at all, and when i finish it compile the modules of nvnet or 3com to the kernell.
With bf24 similar process (except the kernel-source it's not in the debian cd1, i must donwload it).

I don't have to patch anything.
Kernel 2.4.22 has support for the nforce agpgart, or install the new nvidia drivers 26something.

I know about 2.4.22 and the 2.61 nForce drivers, the latter's what I've been running for the last 4 months

Yes - they do,no problem.But you have to have the kernel sources and headers and gcc in place to compile them.To get those you need nvnet running.But for nvnet to run you need the kernel sources and ...
Without network you unfortunately can't download all that stuff.
The xfree driver for nvidia doesn't work with FX cards - thats the reason people that are new to Linux having problems with their RH,Suse,Mdk installs with those cards.

What's stopping you installing Woody (from a CD), compiling nvnet, setting up the NIC, updating to Sid and then installing the nVidia Linux drivers though other than the fact that it's a PITA?

It right in the begginnig , when I boot I choose whatever flavour and then it freezes , in this place:

PCI_IDE: unknown Ide controller on PCI bus0 device 48 .......
PCI_IDE: chipset revision 162
PCI_IDE: not 100% native mode: will probe IRQs later
ide 0: BM-DMA .... .... : BIOS SETTINGS: hda = DMA, hdb = DMA
ide 1: BM-DMA .... .... : BIOS SETTINGS: hdc = DMA, hdd = DMA

In sarge iso (cd1) it also freezes , but now saying:
detected ide-controller linux (something) and then stops .


I am been unable also to make an customized floppy kernel (boot + root) (2.4.21 or 2.4.22) and make it work with debian woody cds or testing iso's.

Beggining to panic ...

TIA

Note: Nic, nvdrivers , etc it's no problem for me, since I can't even get to that fase, this step (when I freeze is the 1st one) .
1-boot cd
2-choose flavour and options
3-and then FREEZE -----

NOTE2 : I'm beggining to suspect that I should change something in bios config, should I ?

That's definately the nForce2 IDE controller, I get that same "chipset revision: 162" bit when I boot Linux on my 8RDA+.

Hmm... if the nForce IDE patch isn't applied (which it isn't, otherwise the IDE controller would be identified as NFORCE2), the controller shouldn't be capable of starting up in DMA mode by default, that could be what's making it freeze. Anyone know of a kernel parameter that can turn this behaviour off?

I really don't get it - I got a nforce motherboard and that boots just fine with the bf2.4 kernel.No patches or anything applied.I would tell you to check with the BIOS but I got no idea what could be wrong there.

I got bf2.4 kernel to boot but no dma, no sata, no firewire, no 3com lan,

U must have 2.4.21+ to get everything working.

I have all that + my sata is sata running raid 0

thear are no reports of this for debian get gentoo

debian is not for new hardware becouse the kernels are just too old.

That's not quite true, patches exist to provide all the relevant functionality for 2.4.20. I'm only running 2.4.20 here (I'm running Gentoo's xfs-sources with the nVidia nForce AGPGART patch applied) and everything bar APIC (not ACPI, that works as near as I can tell) works fine because Gentoo applies all the required patches (except the AGPGART patch, you have to get that from the nVidia drivers) when you emerge the sources.

edit: This is what I get from my 2.4.20 for my nForce2 IDE controller:

I know it's capable of UltraDMA133, theres supposed to be some more fiddling to enable that but as the stuff I have connected to it at the moment is only PIO or UltraDMA66, and the Western Digital HDD I ultimately plan to connect to it is only UltraDMA100, I don't see the point of going to the trouble to enable it.