|
|
|
|
|||||
|
Maintained by Francis F. Steen, Communication Studies, University of California Los Angeles |
|||||||
|
Gubbio's new kernel On 25 May 2002, I got lm_sensors 2.6.3 from http://www2.lm-sensors.nu/~lm78/download.html; see FAQ. I copied my 2.4.16 linux kernel source from /home/steen/mnt/giant/src/linux-2.4.16
to /usr/src/linux and recompiled it to get the i2c part, needed for the
hardware monitoring. First build I first rebuilt the 2.4.16p kernel on 25 May 2002, in effect modifying my previous and working setup. Instructions: http://www.desktop-linux.net/kernel.htm I relied on my notes at 2001-12-29_Kernel.html You could have done make mrproper first! It removes old dependency files. "If you want to carry your existing configuration to a new version with minimal work, use "make oldconfig", which will only ask you for the answers to new questions." I could have done this, but wanted to make some changes.
Now, since the processor support was for PII rather than my current PIII, it could be that my upgrade will work better now. I should also be able to set up a firewall. The i2o devices are to support motherboard monitoring with lm_monitor (they need them as modules only).
No problems reported
At the end of the compiling process I got this:
I may have done one or two things as modules -- not sure about this, and couldn't tell from the printout! Anyway, I went through the motions: If you configured any of the parts of the kernel as `modules', you will have to do "make modules" followed by "make modules_install". Read Documentation/modules.txt for more information. For example, an explanation of how to use the modules is included there. I then copied bzImage from /usr/src/linux/arch/i386/boot -- it is 1195589 large, or 1.2MB -- to /boot and renamed it kernel-2.4.16p2 I then copied the system map /usr/src/linux/System.map to /boot and renamed it System.map-2.4.16p2 This could be a big problem -- the kernel may need the system map to be called System.map-2.4.16, as the current system map is called. To safeguard the previous kernel, I therefore renamed the current (30 December 2001) system map System.map-2.4.16p and the new one should probably become System.map-2.4.16 -- but for the moment I left it as System.map-2.4.16p2. Instructions for mounting lilo on a floppy: http://www.geocities.com/ariyahidayat/essays/linux_in_floppy.htm In the end I decided to just use YaST2, as I have before. I went to YaST Control Center and chose Bootloader configuration. In YaST's lilo editor, I removed "disableapic" since this is now enabled, but I left hdd=ide-scsi -- make sure this should really be hdd! The root is /dev/hdc7 and the initrd is /boot/initrd. The video mode was set to 788, which is 800x600x64k -- I set it to 791, which is 1024x768x64k. See http://www.linux-quebec.org/archives/aide/msg15636.html for a list of the modes. The floppy drive is at /dev/fd0 and is defined as boot. You should make a copy of this floppy! I wrote the new values to a new floppy rather than to the old one, so the old is my security backup that will only boot the 30 December 2001 kernel (and the other exiting options). I then ran lilo, just to be on the safe side, and got
That should do it. I couldn't mount the floppy, but gave it a try anyway. To be super safe I changed the name of the system map from 2.4.16p2 to 2.4.16. The system boots fine, but I get errors about modprobe -- I later discover this is because I selected the kernel to probe for modules at startup. I also got other funny error messages in xconsole, though performance seemed fine. Second build On 26 May 2002, I made a new kernel, and got some new errors relating to the configuration. I guess I'm not a big fan of YaST2. Useful list of commands -- http://www.ss64.demon.co.uk/bash/ The error message screen is called xconsole and can be started by running this command. I decided to stop using XFS, the x-font server, as it doesn't really seem to be required -- see /etc/X11/fs/config, where it's labeled a security risk. I set START_XFS="no" in rc.config. I also set START_SMB="no" -- this could be the cause of the "netbios-ssn/tcp (2): bind: Address already in use" error message I get hundreds of, as samba is also started in inetd. In /etc/inittab I set initial runlevel to 3 -- SuSE had set it to 5. I'm looking for where modules are managed. I found /etc/modules.conf and used
to find the lines from the modprobe errors:
I found the following on SuSE - http://sdb.suse.de/en/sdb/html/thallma_kde2_mixer.html:
Pretty stupid, eh? I tried that; the same could likely be accomplised by adding this to /etc/conf.modules:
Here is a long mail on making Soundblaster work. These are remaining errors:
The file file://localhost/usr/src/linux/Documentation/devices.txt has a full list of all the devices -- 10-134 = /dev/apm_bios Advanced Power Management BIOS, which I've not asked for, and 116 is the Advanced Linux Sound Driver (ALSA). So this means the module for ALSA is missing, as is the APM BIOS -- I obviously don't need either, and should find a way to switch off modules. Notes from modules.conf: I found alias char-major-116 snd, but I didn't find 10-134, so this may not be the right place after all. Here is the stuff that looks specific to my configuration:
Still, this doesn't seem to match my error messages. When I typed modprobe I got this:
I went to /lib/modules to look -- there's not much. It looks like the only thing I did as a module this time is ip6table_filter -- pretty marginal. In SuSE's kernel there are what looks like hundreds of modules, but my grep is not pulling up anything even there. For what happens at bootup, see /etc/init.d/ and the README file there -- the rest are all shell scripts.
I added AllowedAddresses = 128.97.184; to lisarc -- the syntax may be wrong. Various Try testparm to get your samba settings. Errors before the new kernel:
My attempt to mount the floppy:
Font errors:
A typical session -- this is from /var/log/messages
Here we go after the new kernel:
These problems were largely corrected by a second build, except that I never fixed the mtrr problem. Linux Loadable Kernel Module HOWTO: http://www.tldp.org/HOWTO/Module-HOWTO/ So I rebuilt the kernel, since I believed I had included APM by mistake. Now, after doing a make mrproper, I discovered to my dismay that I had lost all previous selections. I also discovered that what I need for the hardware monitoring is i2c, not 12o -- a little nearsighted there! But it horrifies me to think I may have left a vital component out -- this may not be a workable kernel. Instead of using SuSE, I just edited /etc/lilo.config this time, and then ran lilo -- this looks fine, and all you need is a bootable floppy, which I already have. It doesn't seem to contain much. The Linux Kernel HOWTO: http://www.tldp.org/HOWTO/Kernel-HOWTO.html. Samba double-loading is a weird one -- it goes away if I nix it from rc.config and leave it in inetd.conf. It won't start on its own that way, but I just start it manually with rcsamba start and it works fine. Didn't get any help from the otherwise excellent Using Samba: http://ieee.uwaterloo.ca/UsingSamba/index.html. Samba -- after nixing it from rc.config, but keeping it in inetd, it didn't start on its own. I started it with this command:
Using this method, I finally got rid of the error messages. More on the video modes at startup -- file://localhost/usr/src/linux/Documentation/fb/vesafb.txt You can use 0x317 for the 1024x768 format -- or you can use the decimal version, which is perhaps what you have now. Try video=vesa:ywrap Using framebuffer devices on Intel platforms: http://www.tldp.org/HOWTO/Framebuffer-HOWTO-5.html This second build works great and has very few error messages -- just the mtrr. Some guy had a script to fix this on 5 Jan 2001 on the linux kernel discussion board; I wrote to ask about it but the mail bounced. I attempted to run this kernel on cyberspace, in the wee hours, but found to my not-surprise that nothing worked: in fact, this kernel lacks cyberspace's network card driver, video card driver, and sound card driver. I was intending to give cyberspace the kernelspace NFS. Third build My third build, on 27 May 2002, was simple and painless: I simply turned
the i2c components into modules and copied everything as usual -- that
is to say, the bzImage, the System.map, and for larks, the .configure
file. I also did make modules and make modules_install of course; the
i2c are the only modules. This looks quite successful, and I made the lm-sensors work too. Fourth build On 30 May 2002 I rebuilt the kernel, hoping to make fdisk -l work -- there's some subtle problem. Help on modules: http://www.lysator.liu.se/~forsberg/linux/chapter3.html#MODULES depmod -a I made a disk for partitioning the drive using GNU parted; see help. However, I couldn't make it resize the hdc7 partition. See recovering from corrupt filesystem (local guide). Details. Fifth build On 3 June 2002 I added some bits regarding the scsi emulator and make the CDRW finally work! This was 2.4.16m4. I made some final tweaks and arrived at a successful build, 2.4.16m5.
|
|
|
|
|
|||||
|
Maintained by Francis F. Steen, Communication Studies, University of California Los Angeles |
|||||||
