Juanito


Group: Members
Posts: 1601
Joined: Sep. 2005 |
 |
Posted: Feb. 06 2007,13:49 |
 |
Quote (WDef @ Feb. 06 2007,11:17) | Broken means broken. You can compile the kernel but not the modules (setting eg CONFIG_M686 gets around this). There was a patch to fix this for CONFIG_M386=y. This is why you don't see anyone posting that they sucessfully rebuilt dsl's 2.4.26 kernel for 386 with modules (I've rebuilt these for 686). |
I was wondering if this was what you meant - after a long time and a lot of help from the DSL forum regulars, I managed to rebuild 2.4.26 kernel modules and use them in DSL - see http://damnsmalllinux.org/cgi-bin....p;st=70 page 15.
As you say, the trick was to modify the drmP.h file - after this things worked and I used the bluetooth and cpufreq modules thus created in DSL.
If you think it might be useful, I could post the drmP.h file
|