Subject: Re: Kernel 2.4.4 drivers
From: r may (mayro@earthlink.net)
Date: Sat Jun 30 2001 - 09:36:15 MDT
On Sat, 30 Jun 2001 09:19:41 -0500
"michael" <mlibby@qwest.net> wrote:
>
> I ran through a kernel compile (make xconfig; make dep; make; make modules),
> and I set the USB printer and scanner stuff to Y rather than M. (Should I
> have just set it to M?). Then when I'm done I have a new vmlinux and a new
> System.map, which I renamed, put in /boot, and changed the symlinks to point
> to the new bits. I couldn't find any replacement module-info or zImage files.
>
> But when I restart it still looks like the stock kernel from YDL (the login
> label matches the label on the /boot files), and I have no idea how to check
> to see if my new kernel with the drivers I need is the one that loaded.
>
> I see that the 2.2.19 kernel has all the modules I might need for USB, so I
> suppose I could use that, but... I still want to learn this stuff.
>
> Thanks,
> Michael.
If you want to take your new kernel for a test run you need to copy the vmlinux and System.map files to your /boot directory. You may want to follow the same idea of copying the files with their version numbers as part of their names and then make symlinks to them. As for whether I say Y or M for the drivers I'd say its up to you. I say Y to most everything I use regularly just because I'm lazy about modules (no worries about loading and unloading them). Also I do the make sequence slightly differently, thought there may be more than one way to do things. When I compile my kernels I do: make menuconfig (xconfig is just fine too but I don't always use X) make dep, make vmlinux, make modules, make modules_install (no space). Then I copy stuff to /boot and reboot. I don't know about the module-info file but I haven't seen any problems without it either.
Also if your up to it you may want to edit your yaboot.conf file (if you made a bootstrap partition you need to mount it as an hfs partition) so that when your at the yaboot prompt you can leave the default to linux which probably point to vmlinux in /boot. What you can do is add another section that points to your new kernel and call it somthing like linux-2.4 so that when you type linux-2.4 at the yaboot promt it loads your new kernel. If it loads with no problems great. If it doesn't work you can still boot your old kernel with no problems.
If your going to usr PPP with your new 2.4.x kernel then you'll probably need to recompile "pppd". At least thats the only way I was able to get ppp working with 2.4.x kernels. Make sure your /usr/src/linux points to the your 2.4.x kernel source directory since pppd needs some info from the kernel source.
hope this helps,
- robert
This archive was generated by hypermail 2a24 : Sat Jun 30 2001 - 08:41:50 MDT