Results 31 to 39 of 39
Thanks for helping hazel. I've been through more kernel compiles in the last two days than during the whole previous time I've spent with Linux trying various configurations to no ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-09-2010 #31
Thanks for helping hazel. I've been through more kernel compiles in the last two days than during the whole previous time I've spent with Linux trying various configurations to no avail. Then I tried using the .config made from make defconfig and edited for file systems and hardware. To my delight, this worked. I never really knew just how bloated Ubuntu configured kernels were until now. With the standard CRUX .config, it's hard to find many things turned on. With Ubuntu, it's hard to find many things turned off!
- 10-09-2010 #32
So far I've never had to use defconfig. I always use my previous config file from /boot and just look at the options that are flagged NEW. I intend to do the same initially for this upgrade. If that doesn't work and I get the same sort of problems you've had, plan B is to use the config file that I worked out for Debian testing (2.6.32). make defconfig is definitely plan C."I'm just a little old lady; don't try to dazzle me with jargon!"
- 10-09-2010 #33
What's so puzzling is the old .config worked perfectly under 2.5 with kernel 2.6.35, yet using the exact same .config with 2.6.35 in 2.7 gives the problem with partitions not showing up in /dev. I ran into problems trying to get 2.6 installed on this machine and had to give up because I didn't have the time then to resolve it. The two issues must be related. I'll continue to try and pin it down but still don't have a clue where the difference is.
- 10-09-2010 #34
- 10-09-2010 #35
this. I created the ext4 partition using gparted running on Arch so huge_file must have been enabled. So in Arch I just ranCode:
tune2fs -O ^huge_file /dev/sda15
@Dapper Dan - I suggest you compare old and new .config files using meld or something similar ... diff will give you a list to work with or vimdiff should give equivalent functions to meld (I just find meld easier to use for updates).
Last edited by Jonathan183; 10-09-2010 at 11:19 PM. Reason: correct vim ref
- 10-09-2010 #36
1. detect hardware, file system(s) and partitions.
2. Use the collected information to create a custom .config.
3. Compile the kernel for the user's particular setup.
All unnecessary drivers, modules and support would be left out leaving the user with a lean and clean kernel. I'm not smart enough to figure out how to make such a distro but it seems to me it would be possible to do.
- 10-09-2010 #37
- 10-10-2010 #38
Dan, I have 2.7 installed and booting on my lappy.
Had to do a dance with the kernel for the last couple of days... but I decided to reinstall earlier tonight, added SCSI support along with my SATA drivers, and got right up and going! FWIW... I formatted to ext4.
- 10-10-2010 #39