Show Posts
1
Debian / [new] Kernel 2.6.24.4 With Cpufreq
« on: September 10, 2008, 05:07:55 pm »
Hey Man,
Thanks for getting back to me! Having taken your (slightly hard) advice, I've gone back thru the posts and read more. I should have done before but sometimes I get lost on this board layout for some reason. Doh!
I'd kinda surfed and assumed that the posts recently related to Wifi mainly, and didn't really understand the stack discussed could hit all network hardware. I'm totally new to this having given up on Angstrom, and Titchy, while seeming sexy doesn't work for me yet (probably more reading issues!)
Now I've basically just cleared out the Z internal disk again and untarred the rootfs again and dropped in the previous version of the 'modules' build. Then Re-flashed (just to be sure) and it's alive! I'm only tinkering at the moment, but this is a lot more useful than GPE or OPIE on the Angstrom distros which is what caught my eye initially. My dm9601 works sweet, and all is good.
I did slighty bork it earlier, but maybe I'm just unlucky. I'm based in Spain and had real problems connecting to armel-debs.applieddata.net, so I tweaked the sources.list to use mirrors.eu.kernel.org. That seemed to work until I did a dist-upgrade, at which point I got major problems with libts arguing about 1.0-0 and 0.0-0. I'll have a look more on this one, but at the mo I'm just reinstalling the default, and will avoid dist-upgrade for now!
In the meantime, thanks for your advice, I appreciate it, and I'm glad I got it sorted before the LHC sucks us all into a Black Hole. That would have really pissed me off, the Zau still being useless and dying on the same day!! Also, Happy National Day from Gibraltar (The Country I work in) ((Sometimes!))
Bon
Thanks for getting back to me! Having taken your (slightly hard) advice, I've gone back thru the posts and read more. I should have done before but sometimes I get lost on this board layout for some reason. Doh!
I'd kinda surfed and assumed that the posts recently related to Wifi mainly, and didn't really understand the stack discussed could hit all network hardware. I'm totally new to this having given up on Angstrom, and Titchy, while seeming sexy doesn't work for me yet (probably more reading issues!)
Now I've basically just cleared out the Z internal disk again and untarred the rootfs again and dropped in the previous version of the 'modules' build. Then Re-flashed (just to be sure) and it's alive! I'm only tinkering at the moment, but this is a lot more useful than GPE or OPIE on the Angstrom distros which is what caught my eye initially. My dm9601 works sweet, and all is good.
I did slighty bork it earlier, but maybe I'm just unlucky. I'm based in Spain and had real problems connecting to armel-debs.applieddata.net, so I tweaked the sources.list to use mirrors.eu.kernel.org. That seemed to work until I did a dist-upgrade, at which point I got major problems with libts arguing about 1.0-0 and 0.0-0. I'll have a look more on this one, but at the mo I'm just reinstalling the default, and will avoid dist-upgrade for now!
In the meantime, thanks for your advice, I appreciate it, and I'm glad I got it sorted before the LHC sucks us all into a Black Hole. That would have really pissed me off, the Zau still being useless and dying on the same day!! Also, Happy National Day from Gibraltar (The Country I work in) ((Sometimes!))
Bon
Quote from: xamindar
I would recommend just unpacking the module pack from before august 6th (the old modules) from that same page into your modules directory, that should get them working and still leave the iptables ones there. I haven't tried the iptables modules so no idea if they even work.