[Sussex] Now able to 'c' thanks

Steve Dobson steve.dobson at krasnegar.demon.co.uk
Sun Dec 1 07:49:00 UTC 2002


Angelo

On Sat, Nov 30, 2002 at 11:07:57PM +0000, Angelo Servini wrote:
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.19-x1/kernel/drivers/usb/gt6801.o

Without more details it looks like you're kernel and modules haven't
been compiled together.  Change directory to the kernel source and
run:
  # make clean && make dep && make bzImage && make modules
  # rm -rf /lib/modules/2.4.19-x1
  # make module_install
and then install the new kernel in the normal way & reboot.

> (ps I also had to type the above.  the '>'  pipe does not work as I 
> suspect that make outputs to stderr? not stdio? and console does not 
> allow cut'n'paste)

'>' is a short cut for '1>' which is redirect stdout.  '2>' is the
redirect for stderr.  If you want stdout & stderr to go to the same
place then try '2>&1' which redirects stderr to stdout.  You can then
redirect stdout to where you want.  i.e.
  # modprobe gt6801 2>&1 > /tmp/modprobe.log

Be warned thou' if you're on the console and the error is being logged
to the system logger then some of output may not be from the command 
but from the system logger in which case the above will not trap it.

Steve




More information about the Sussex mailing list