here I talk
New Debian/Ubuntu kernel package released: 2.6.30.1-shinedown
This new Debian/Ubuntu kernel package based on kernel version 2.6.30.1 and it comes with all the major bug fixed and improvements plus there is the latest version of acerhdf module (0.5.14) and it includes also the coretemp fix for Intel Atom CPU’s.
The name of this new release, Shinedown, comes from one of my favorite rock bands, but has no special meaning to it, so you can ignore it if you want to. 
Also to be able to know whats new in this release, you should check out http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.30.1.
I wont explain again the installation method, I suppose most of you know it or you can check the previous post of mine to see how to install a kernel. The packages can be found at http://dl.robertalks.com/kernel/2.6.30.1-shinedown/. Please download it, install it and test it, also don’t forget to let me know if there are any problems or bugs in it.
For development or other disto build please check out and download the full kernel source code from: http://dl.robertalks.com/kernel/2.6.30.1-shinedown/source/.
Good luck and have a nice weekend!
Thanks, man. I’m going to try to compile this kernel for ArchLinux!
Great kernel! Only issue I had was that I had to change the configuration so that the framebuffer driver was compiled into the kernel, rather than as a module.
Without doing that, X would work fine, but the console would be totally blank, and any attempt to ctrl-fn would garble the display. I have a laptop, and from what I’ve read intelfb needs to be compiled into the kernel to work with non-CRT displays.
Thanks!
Well I have also Intel graphics on my laptop, but didn’t have any issues with the frame buffer… Maybe you got some different graphics card, who knows!
Robert,
Very weird! It’s possible that I messed up the module installation or something, but everything else seems to work. And not being able to access the console was not a problem I’d ever had before. Changing the framebuffer driver so it was built into the kernel fixed things, but it took a bit of research to figure it out.
This was what finally tipped me off:
http://www.xfree86.org/~dawes/intelfb.html
“If you have a non-CRT display (e.g., laptop LCD panel, or an external LCD panel connected via a DVI connector) active when the driver is loaded, it will refuse to load. To use the driver with non-CRT devices, the driver needs to be built in to the kernel, and the “vga=XXX” boot option used to program the video mode via the video BIOS at boot time.”
Not a problem at all, in the long run. Your kernel seems to work great, better than any of the others I used from the Arch Linux User Repository. The fan control seems to work now, when it threw error messages before. That alone is nice. Thanks again!
Terrence
Oh, I should add that I’m not using an initrd. Your kernel doesn’t need one, correct?
Well as I know initrd should be used and usually not because of the graphics card, but because of the disks, if you have SCSI or SATA you need initrd, but if it works without then ok. Regarding the framebuffer, its only related to intel 8XX version and as I know on Atom netbooks there is no 8XX version, but 9XX graphics adapter. Anyway, using it with whatever you need to make it work good that is the point, if for you it worked the way you did it, I think it should be just fine.
Robert,
The lack of initrd was probably the issue, then. I’m assuming that if I’d configured one appropriately it would have loaded whatever drivers needed for the console to show up properly.
The Arch Linux kernels specifically designed for the Acer don’t use initrds, which is why I thought yours probably didn’t need one. When I had problems, I did try making one, but I think Arch’s default mkinitcpio.conf (I don’t know the equivalent file in debian/ubuntu) may need some tweaking to work with this kernel in particular. Booting with the image it generated didn’t solve the frame buffer issue.
Actually, this is the point at which my experience entirely breaks down. From what you’re saying, it shouldn’t have worked at all without the initrd. Yet it does!
Computers can be mysterious sometimes, heh. Thanks again! If I had time and expertise, I’d ask your permission to write a package file and include your kernel in the Arch User Repository. From what I can tell, it’s the most up-to-date kernel for the Acer available.
Best,
Terrence
First of all, you are welcome and second, you can create the initrd using mkinitrd, which should be included in almost any distro out there. Now how Arch works and does the things I’m not really sure, I never used Arch. I prefer CentOS/Redhat or Ubuntu/Debian, for me they seems mature enough and work quite well. Good luck in the future and if you have some other issue let me know.
I got an error everytime I try to build something (by using make) when running your kernel. It goes something like this:
/usr/src/linux-headers-2.6.30.1-shinedown/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.30.1-shinedown/arch/x86/Makefile_32.cpu: No such file or directory
make[1]: *** No rule to make target `/usr/src/linux-headers-2.6.30.1-shinedown/arch/x86/Makefile_32.cpu’. Stop.
I also got some kind of warning when installed the deb that could be related to this:
Hmm. There is a symbolic link /lib/modules/2.6.30.1-shinedown/build
However, I can not read it: No existe el fichero ó directorio
Therefore, I am deleting /lib/modules/2.6.30.1-shinedown/build
Hmm. The package shipped with a symbolic link /lib/modules/2.6.30.1-shinedown/source
However, I can not read the target: No existe el fichero ó directorio
Therefore, I am deleting /lib/modules/2.6.30.1-shinedown/source
That’s it. Besides that, It’s a pretty good work you’re doing here. Keep up!
Hi, you have to go to /usr/src/linux-headers-2.6.30.1-shinedown and run the following:
cp -a /boot/config-$(uname -r) /usr/src/linux-headers-2.6.30.1-shinedown
make menuconfig
make modules
The it will create the necesary files. The warnings can be ignored.
Thank you, man. That did the trick. Great kernel, by the way.
Good! Im happy I can help!
Type your comment here
I am followed your instructions above and now running ur compiled kernel. But the problem is with virtual box 3.0.2 which doesnt run. it asked me to re-setup the kernel driver (which it sud hav done itself) and asked me to run “/etc/init.d/vboxdrv setup” and i did as said but i get error as
$ cat /var/log/vbox-install.log
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.30.1-shinedown/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
/usr/src/linux-headers-2.6.30.1-shinedown/arch/x86/Makefile:41: /usr/src/linux-headers-2.6.30.1-shinedown/arch/x86/Makefile_32.cpu: No such file or directory
make[1]: *** No rule to make target `/usr/src/linux-headers-2.6.30.1-shinedown/arch/x86/Makefile_32.cpu’. Stop.
make: *** [vboxdrv] Error 2
I tried your above quoted method which worked for Mike but poor me.. didnt work for me
do you hav any idea? I even checked manually to see whether that file is there but didnt fine Makefile_32.cpu in that location but i saw only Kconfig.cpu.. dunno wot’s wrong???
wait!! do i need to download “linux-source-2.6.30.1-shinedown_1_all.deb ” package as well??? it was bigger size 58M so i didnt download
When i used 2.6.30 from ubuntu kernel repo, the “linux-headers-2.6.30-020630_2.6.30-020630_all.deb” package was only 8.8MiB …. so was wondering abt that..
Thanks for your time…
Yes, you need to download and install linux-source-2.6.30.1-shinedown_1_all.deb so everything work. After you download the source, install it then you can follow the instructions from Mike.
thanks for the reply, but i did that few mins back but didnt help. when i install that source deb it added a linux-source-2.6.30.1-shinedown_1.tar.bz2 in /urs/src directory :S
Any idea or suggestions..
Yes sure, to go /usr/src, tar -zjvf linux-source-2.6.30.1-shinedown_1.tar.bz2
then:
ln -s /usr/src/linux-2.6.30.1-shinedown /usr/src/linux
ln -s /usr/src/linux /lib/modules/2.6.30.1-shinedown/source
cd /usr/src/linux
cp -a /boot/config-$(uname -r) /usr/src/linux/.config
make menuconfig
make modules
and it should work!
Thank your for your help. I tried as u suggested and i corrected few typos u made, like instead of ‘tar -zjvf..’ it sud hav been ‘tar -xjvf..’ isnt it? then i corrected the directory names also and finally got it started. Everything seemed fine and compiled but after i reboot there is no change.
I activated sony memorystick module but it still doesnt work. And I still can’t start my virtual box. virtual box kernel modules still cant be compiled..
I guess i hav to stick to 2.6.30 to work with virtual box
Well sorry anyway, for most people it works, but there is always some problems. Maybe next time gonna have more luck!