Hi guys,

I just tried compiling my own kernel, which did not boot.

The main issues I noted was that I did not choose the correct framebuffer driver/device, as there was no decent video modes, and my harddrive was not recognized.

My hardware is an Asus v1v laptop. 320gb sata hdd, 4gb ram, core 2 duo cpu, screen is 1680x1050 on a radeon 3650 video card. I have not enabled modules as I simply don't need them, and have patched my kernel with RSBAC, so the RSBAC options can all be safely ignored.

I have made my .config available at http://pastebin.com/m4ccc5b8b and was hoping someone could guide me to the issues I have missed out. Specifically, what I have out to get my sata hdd recognized, and which framebuffer I should use for my radeon 3650.

Cheers for any assistance on this issue.

It's been a while since I've used slackware, but I do remember joys and madness of compiling one's own kernel, the hours scouring module descriptions, compiling, booting, rebooting a safe kernel, wondering if this would be the module to break it..

Anyhow, I last used Slack 11 I think, and I never did get my Radeon 7000 working quite right with anything beyond the standard framebuffer modules.

In my experience, don't set CONFIG_FB_RADEON=y. Instead, you should set CONFIG_FB_VESA=y and CONFIG_FB_RADEON=m or n. It's Ok when you normally work under X in the most cases. Don't set variables by hand but make use of "make menuconfig" or "make xconfig". Good Luck~

Can you pastebin your lspci -v output?

Great advice ... I just finished a new kernel compile today. I remember the days of first learning to compile a kernel. And my biggest issues where Video & Sata detection. I keep all modules to a minimum, with the exception of sound.

Also double check your Filesystems, and double check to make sure you have the necessary FS support.

Also use grissiom's suggestions with the framebuffer. I never use the built framebuffer modules. I always use the VESA.

Hmm, I will probably end up working more in the console than in X, and so want to be able to use my full native resolution, of 1680x1050. VESA does not support this, and apparently the radeon driver does not either...although surely it should?

I don't use modules, so would rather find out the correct driver to use and have it work..

Not at the moment, or for a while just yet.., I'll save a copy the next time I try again, but what are you looking for? If you can give me a hint as to what I may have missed, I can try recompiling and testing and hopefully save a bit of time.

Hmm, I've compiled many a kernel. Just not on this particular hardware. The reason I want to try and make use of my radeon framebuffer, is to be able to use my native 1680x1050 resolution, which vesa does not support, at least by default.

My filesystems are fine..just using a very simple EXT3 system.

What hardware are you using? I come up a resolution:

1) try a 2.6.31 kernel.
2) if it not work with your configuration, enable DRM_RADEON_KMS and FB_VESA and disable FB_RADEON, report a bug in buazilla.kernel.org

I should have mentioned, but I am using the latest .31 kernel.

Anyway, I got everything else working and it now boots, I just needed AHCI_SATA enabled. Something that was not obvious to me at the time.

However, I still cannot get my radeon framebuffer working. I would be fine with vesa, but want to be able to use my console it my native resolution, which vesa does not support.

I can still post my new .config if anyone wants...

edit: Was just doing some research, and will try booting with video=radeonfb:1680x1050-32@60

Hopefully, it shall be amazing.

Hard to say anything, as your .config on pastebin is not complete, as it seems...

Whenever I want to try a new kernel or simply tune one existing, I take a Slackware config as a basis and make only a few changes at a time.

e.g. to install 2.6.31 on Slackware64-13.0 I installed the source in /usr/src, cd to it, issued zcat /proc/config.gz > .config, ran make oldconfig, answered the questions for new drivers, added only built-in support for my root fs (reiserfs), then ran make && make modules && make modules_install and it did the trick.

More details here.

I used to strip down my kernels removing a lot of drivers I didn't need but I ceased to do that: I spent a lot of time only to shorten compilation time; better do something else while it runs.

Only my

I don't know if you can get any resolutions outside of X beyond what you see in /etc/lilo.conf in the vga= option list. I could be wrong about this though...

Out of curiosity, why would you say my .config is incomplete? I can confirm it is 100% complete.

As above, I now have it working and booting, and the only change was to enable ahci_sata.

I generally prefer to only compile in the exact drivers I need, which results in a small, lean and mean and fast kernel, perfect for my needs.

I would not rely on the slackware generic config. Everything works and will be supported, but this is because everything is a module. Useful for compatibility and for a distribution, but not so much for a specific configuration.

Yeah, you definitely can. If you have a look around, there are quite a few people booting happily with 1680x1050..., and I used to run 1450x900 without a problem.

Just an idea, but can you see what resolutions are supported by looking in your /var/log/Xorg.0.log?

Sorry I was wrong (at first I didn't see the File Systems section).

Yes, I saw your post above after posting mine.

Granted, that's_your_choice

If everything works, look what modules your system need and trim your kernel. Why monolithic?