Skip to main content

Linux kernel 2.6.20.3 编译成功!

几经波折,终于把Linux内核搞定了。

起因是原先ubuntu带的内核版本较低, 决定升级,可是发现安装后modules 有59M。 启动后lsmod
再一看,俺的神呀, 刷刷地, 竟然有两屏。 另外新内核把我的ide硬盘人成了sda, grub里还要改革选项(一开始不知道,怎么也不能启动), 于是决定自己编译一下。

不过过程并不顺利, 一个是我机器的配置, 是近10年前的笔记本, 编译一次内核要将近两个小时。 另外就是我没经验。

现在想想,可能一共得编译了十几次。 中间闹了很多笑话。比如一开始删的模块比较少, 编译完能启动, 但是modules仍有29M, 硬盘还是sda, 后来有狠心删了一次, 这回好了, modules小多了,硬盘也变回hda了, 可是initramfs mount根时说'no such device' , 有时则是 kernel panic。 我在这个问题上就折腾了好久。还有一次是配置文件搞错了,一下编译了很多模块, 中间吃掉硬盘1G多, 告诉我‘no space left’。。。

中间配置了好几次, 一般都是把ubuntu默认的config拷过来并在此基础上修改。 今天终于成功了, 最后kernel是2M左右, modules一共5M多。 感觉上还能删一些, 不过不用了。

经过几次配置,我对kernel倒是有了进一步了解, 至少对其大概架构有了个印象。若不是我机器如此之慢, 编译过程应该也是很有趣的。现在残留的问题是有关声卡的,应该很容易解决。不过到现在我仍不清楚为什么一开始新内核会认成sda, 也听说一些同学有类似情况。

另外,在编译过程中参考了http://lamp.linux.gov.cn/Linux/kernel_options.html,很有帮助, 对作者表示感谢!

Comments

Popular posts from this blog

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...