Re: new kernel, new problems

2003-02-26 Thread Simon Tod
 --- Russell Shaw [EMAIL PROTECTED] wrote: 
Simon Tod wrote:
  So why can't modprobe find any of the modules - if
  indeed that's the problem - cause they're
 certainly
  where they're supposed to be.
  
  Looking through the output of
  
  ~$ depmod
  ~$ modprobe -a \*
  
  again suggests to me that it's some sort of
 dependency
  or configuration problem... the same comment
 appears
  again and again in the output
  
  Hint: insmod errors can be caused by incorrect
 module
  parameters, including invalid IO or IRQ
 parameters.
  
  What's that all about?!
  
  
   --- Russell Shaw [EMAIL PROTECTED] wrote: 
  Simon Tod wrote:
  
 Surely I don't need to do make modules and
 make
 modules_install when I'm not compiling a kernel,
 
 just
 
 installing a pre-built one 2.4.20-686 (and the
 corresponding kernel-pcmcia-modules file)!? The
 
 output
 
 of
 
 ~$ depmod
 ~$ modprobe -a \*
 
 gives me the lengthy output in the attached file.
 
 How
 
 does this help?
 
 Can you verify this module is actually here?:
 
   
 /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o
 
 What does uname -a show?
 Don't top-post.
 
 


~$uname -a

Linux orient 2.4.20-686 #1 Mon Jan 13 22:22:30 EST
2003 i686 Pentium III (Coppermine) GenuineIntel
GNU/Linux

so there doesn't look like there's anything wrong with
that!?

 -- 
 To UNSUBSCRIBE, email to
 [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
  

=
---
Simon Tod
[EMAIL PROTECTED]

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: new kernel, new problems

2003-02-25 Thread Simon Tod
Surely I don't need to do make modules and make
modules_install when I'm not compiling a kernel, just
installing a pre-built one 2.4.20-686 (and the
corresponding kernel-pcmcia-modules file)!? The output
of

~$ depmod
~$ modprobe -a \*

gives me the lengthy output in the attached file. How
does this help?


 --- Russell Shaw [EMAIL PROTECTED] wrote: 
Simon Tod wrote:
 
 Thanks. Got the cpu speed bit solved.
 
 Looking through the PCMCIA HowTo I've checked to
 see
 that /etc/pcmica/config, /etc/default/pcmcia and
 /etc/init.d/pcmica are the same under both kernels.
 
 My new kernel is missing the line
 
 serial_cs   4384   0  (unused)
 
 from lsmod.
   
 
 
 Try:
 depmod
 modprobe -a \*
 
 If that fixes the problem, maybe you should add
 the missing modules to /etc/modules.
 Did you do make modules, make modules_install
 when doing the kernel?
 
 
 -- 
 To UNSUBSCRIBE, email to
 [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
  

=
---
Simon Tod
[EMAIL PROTECTED]

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


=
---
Simon Tod
[EMAIL PROTECTED]

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: new kernel, new problems

2003-02-25 Thread Simon Tod
Surely I don't need to do make modules and make
modules_install when I'm not compiling a kernel, just
installing a pre-built one 2.4.20-686 (and the
corresponding kernel-pcmcia-modules file)!? The output
of

~$ depmod
~$ modprobe -a \*

gives me the lengthy output in the attached file. How
does this help?


Opps. Forgot to attach the file last time :-0

 --- Russell Shaw [EMAIL PROTECTED] wrote: 
Simon Tod wrote:
 
 Thanks. Got the cpu speed bit solved.
 
 Looking through the PCMCIA HowTo I've checked to
 see
 that /etc/pcmica/config, /etc/default/pcmcia and
 /etc/init.d/pcmica are the same under both kernels.
 
 My new kernel is missing the line
 
 serial_cs   4384   0  (unused)
 
 from lsmod.
   
 
 
 Try:
 depmod
 modprobe -a \*
 
 If that fixes the problem, maybe you should add
 the missing modules to /etc/modules.
 Did you do make modules, make modules_install
 when doing the kernel?
 
 
 -- 
 To UNSUBSCRIBE, email to
 [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
  

=
---
Simon Tod
[EMAIL PROTECTED]

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


=
---
Simon Tod
[EMAIL PROTECTED]

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.comWarning: loading /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o will taint the 
kernel: no license
  See http://www.tux.org/lkml/#export-tainted for information about tainted modules
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: init_module: No such device
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: insmod 
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o failed
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO 
or IRQ parameters.
  You may find more information in syslog or the output from dmesg
Warning: loading /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o will taint the 
kernel: no license
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: init_module: No such device
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: insmod 
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o failed
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO 
or IRQ parameters.
  You may find more information in syslog or the output from dmesg
Warning: loading /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o will taint the 
kernel: no license
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: init_module: No such device
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: insmod 
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o failed
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO 
or IRQ parameters.
  You may find more information in syslog or the output from dmesg
Warning: loading /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o will taint the 
kernel: no license
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: init_module: No such device
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: insmod 
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o failed
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO 
or IRQ parameters.
  You may find more information in syslog or the output from dmesg
Warning: loading /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o will taint the 
kernel: no license
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: init_module: No such device
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: insmod 
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o failed
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO 
or IRQ parameters.
  You may find more information in syslog or the output from dmesg
Warning: loading /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o will taint the 
kernel: no license
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: init_module: No such device
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: insmod 
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o failed
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO 
or IRQ parameters.
  You may find more information in syslog or the output from dmesg
Warning: loading /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o will taint the 
kernel: no license
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: init_module: No such device
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o: insmod 
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o failed
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO 
or IRQ parameters.
  You may find more information in syslog or the output from dmesg
Warning: loading 

Re: new kernel, new problems

2003-02-25 Thread Russell Shaw
Simon Tod wrote:
Surely I don't need to do make modules and make
modules_install when I'm not compiling a kernel, just
installing a pre-built one 2.4.20-686 (and the
corresponding kernel-pcmcia-modules file)!? The output
of
~$ depmod
~$ modprobe -a \*
gives me the lengthy output in the attached file. How
does this help?
Can you verify this module is actually here?:

  /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: new kernel, new problems

2003-02-25 Thread Simon Tod
So why can't modprobe find any of the modules - if
indeed that's the problem - cause they're certainly
where they're supposed to be.

Looking through the output of

~$ depmod
~$ modprobe -a \*

again suggests to me that it's some sort of dependency
or configuration problem... the same comment appears
again and again in the output

Hint: insmod errors can be caused by incorrect module
parameters, including invalid IO or IRQ parameters.

What's that all about?!


 --- Russell Shaw [EMAIL PROTECTED] wrote: 
Simon Tod wrote:
  Surely I don't need to do make modules and make
  modules_install when I'm not compiling a kernel,
 just
  installing a pre-built one 2.4.20-686 (and the
  corresponding kernel-pcmcia-modules file)!? The
 output
  of
  
  ~$ depmod
  ~$ modprobe -a \*
  
  gives me the lengthy output in the attached file.
 How
  does this help?
 
 Can you verify this module is actually here?:
 
   
 /lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o
 
 
 -- 
 To UNSUBSCRIBE, email to
 [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
  

=
---
Simon Tod
[EMAIL PROTECTED]

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: new kernel, new problems

2003-02-25 Thread Russell Shaw
Simon Tod wrote:
So why can't modprobe find any of the modules - if
indeed that's the problem - cause they're certainly
where they're supposed to be.
Looking through the output of

~$ depmod
~$ modprobe -a \*
again suggests to me that it's some sort of dependency
or configuration problem... the same comment appears
again and again in the output
Hint: insmod errors can be caused by incorrect module
parameters, including invalid IO or IRQ parameters.
What's that all about?!

 --- Russell Shaw [EMAIL PROTECTED] wrote: 
Simon Tod wrote:
Surely I don't need to do make modules and make
modules_install when I'm not compiling a kernel,
just

installing a pre-built one 2.4.20-686 (and the
corresponding kernel-pcmcia-modules file)!? The
output

of

~$ depmod
~$ modprobe -a \*
gives me the lengthy output in the attached file.
How

does this help?
Can you verify this module is actually here?:

 
/lib/modules/2.4.20-686/kernel/drivers/acpi/acpi.o
What does uname -a show?
Don't top-post.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



RE: new kernel, new problems

2003-02-19 Thread Simon Tod
Thanks. Got the cpu speed bit solved.

Looking through the PCMCIA HowTo I've checked to see
that /etc/pcmica/config, /etc/default/pcmcia and
/etc/init.d/pcmica are the same under both kernels.

My new kernel is missing the line

serial_cs   4384   0  (unused)

from lsmod.

Under the kernel 2.4.20-686 the output of
/proc/devices is

Character devices:
  1 mem
  2 pty/m%d
  3 pty/s%d
  4 tts/%d
  5 cua/%d
  7 vcs
 10 misc
 13 input
 14 sound
 29 fb
128 ptm
136 pts/%d
162 raw

Block devices:
  1 ramdisk
  3 ide0

while under 2.4.19 it's

Character devices:
  1 mem
  2 pty
  3 ttyp
  4 ttyS
  5 cua
  7 vcs
 10 misc
 14 sound
 29 fb
108 ppp
128 ptm
136 pts
162 raw
180 usb
203 cpu/cpuid
226 drm
254 pcmcia

Block devices:
  2 fd
  3 ide0
  7 loop
 43 nbd

There seem to be a whole bunch of devices missing in
the new kernel.

An attempt to start serial_cs with modprobe illicited
the response

/lib/modules/2.4.20-686/kernel/drivers/pcmcia/ds.o:
insmod
/lib/modules/2.4.20-686/kernel/drivers/pcmcia/ds.o
failed
/lib/modules/2.4.20-686/kernel/drivers/pcmcia/ds.o:
insmod serial_cs failed
Hint: insmod errors can be caused by incorrect module
parameters, including invalid IO or IRQ parameters.
  You may find more information in syslog or the
output from dmesg

while insmod serial_cs gave me

Using
/lib/modules/2.4.20-686/kernel/drivers/char/pcmcia/serial_cs.o
/lib/modules/2.4.20-686/kernel/drivers/char/pcmcia/serial_cs.o:
unresolved symbol register_pccard_driver_R583d4ed2
/lib/modules/2.4.20-686/kernel/drivers/char/pcmcia/serial_cs.o:
unresolved symbol unregister_pccard_driver_Rdb348cd2

So now I'm stumped. Where do I go from here to get the
pcmcia modem up and running? 

 --- Narins, Josh [EMAIL PROTECTED] wrote: 
I have a 1000 Mhz that was originally recognized as
 667Mhz
 
 Look for these files
 
  /proc/cpufreq
  /proc/sys/cpu/0/{speed|speed-min|speed-max}
 
 if you have those, all you have to do is 
 
  cat /proc/sys/cpu/0/speed-max 
 /proc/sys/cpu/0/speed
 
 check the results with 
 
  cat /proc/cpufreq
 
 If you have multiple processors, you should find
 them under
 /proc/sys/cpu/[0-9]+
 
 by the way, you can also cat speed, speed-min and
 speed-max
 
 
 
  -Original Message-
  From: Simon Tod [mailto:[EMAIL PROTECTED]] 
  Sent: Tuesday, February 18, 2003 3:16 PM
  To: [EMAIL PROTECTED]
  Subject: new kernel, new problems
  
  
  Having installed kernel-image-2.4.20-686 and
  kernel-pcmcia-modules-2.4.20-686 to rid myself of
 a
  couple of problems I was having with my old kernel
  (2.4.19), I've now picked up a couple of new
 problems.
  
  1) A failure to get the pcmcia modem running - I
  notice there is a pcmcia entry in /proc/devices
 under
  the old kernel but not the new one. How can I
 track
  down the relavent info in the old kernel that I
 can
  use in the new one to the modem up again?
  
  2) Reading /var/log/dmesg when booting under the
 new
  kernel, it claims to detect a 700 MHz processor
 while
  the old kernel gets it right at 1000 MHz. WTF?
  
  Thanks in advance.
   
  
  =
  ---
  Simon Tod
  [EMAIL PROTECTED]
  
  __
  Do You Yahoo!?
  Everything you'll ever need on one web page
  from News and Sport to Email and Music Charts
  http://uk.my.yahoo.com
  
  
  -- 
  To UNSUBSCRIBE, email to
 [EMAIL PROTECTED] 
  with a subject of unsubscribe. Trouble? Contact 
  [EMAIL PROTECTED]
  
  
 

--
 This message is intended only for the personal and
 confidential use of the designated recipient(s)
 named above.  If you are not the intended recipient
 of this message you are hereby notified that any
 review, dissemination, distribution or copying of
 this message is strictly prohibited.  This
 communication is for information purposes only and
 should not be regarded as an offer to sell or as a
 solicitation of an offer to buy any financial
 product, an official confirmation of any
 transaction, or as an official statement of Lehman
 Brothers.  Email transmission cannot be guaranteed
 to be secure or error-free.  Therefore, we do not
 represent that this information is complete or
 accurate and it should not be relied upon as such. 
 All information is subject to change without notice.
 
  

=
---
Simon Tod
[EMAIL PROTECTED]

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Re: new kernel, new problems

2003-02-19 Thread Russell Shaw
Simon Tod wrote:


Thanks. Got the cpu speed bit solved.

Looking through the PCMCIA HowTo I've checked to see
that /etc/pcmica/config, /etc/default/pcmcia and
/etc/init.d/pcmica are the same under both kernels.

My new kernel is missing the line

serial_cs   4384   0  (unused)

from lsmod.
 


Try:
depmod
modprobe -a \*

If that fixes the problem, maybe you should add
the missing modules to /etc/modules.
Did you do make modules, make modules_install
when doing the kernel?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



new kernel, new problems

2003-02-18 Thread Simon Tod
Having installed kernel-image-2.4.20-686 and
kernel-pcmcia-modules-2.4.20-686 to rid myself of a
couple of problems I was having with my old kernel
(2.4.19), I've now picked up a couple of new problems.

1) A failure to get the pcmcia modem running - I
notice there is a pcmcia entry in /proc/devices under
the old kernel but not the new one. How can I track
down the relavent info in the old kernel that I can
use in the new one to the modem up again?

2) Reading /var/log/dmesg when booting under the new
kernel, it claims to detect a 700 MHz processor while
the old kernel gets it right at 1000 MHz. WTF?

Thanks in advance.
 

=
---
Simon Tod
[EMAIL PROTECTED]

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




RE: new kernel, new problems

2003-02-18 Thread Narins, Josh
I have a 1000 Mhz that was originally recognized as 667Mhz

Look for these files

 /proc/cpufreq
 /proc/sys/cpu/0/{speed|speed-min|speed-max}

if you have those, all you have to do is 

 cat /proc/sys/cpu/0/speed-max  /proc/sys/cpu/0/speed

check the results with 

 cat /proc/cpufreq

If you have multiple processors, you should find them under
/proc/sys/cpu/[0-9]+

by the way, you can also cat speed, speed-min and speed-max



 -Original Message-
 From: Simon Tod [mailto:[EMAIL PROTECTED]] 
 Sent: Tuesday, February 18, 2003 3:16 PM
 To: [EMAIL PROTECTED]
 Subject: new kernel, new problems
 
 
 Having installed kernel-image-2.4.20-686 and
 kernel-pcmcia-modules-2.4.20-686 to rid myself of a
 couple of problems I was having with my old kernel
 (2.4.19), I've now picked up a couple of new problems.
 
 1) A failure to get the pcmcia modem running - I
 notice there is a pcmcia entry in /proc/devices under
 the old kernel but not the new one. How can I track
 down the relavent info in the old kernel that I can
 use in the new one to the modem up again?
 
 2) Reading /var/log/dmesg when booting under the new
 kernel, it claims to detect a 700 MHz processor while
 the old kernel gets it right at 1000 MHz. WTF?
 
 Thanks in advance.
  
 
 =
 ---
 Simon Tod
 [EMAIL PROTECTED]
 
 __
 Do You Yahoo!?
 Everything you'll ever need on one web page
 from News and Sport to Email and Music Charts
 http://uk.my.yahoo.com
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact 
 [EMAIL PROTECTED]
 
 

--
This message is intended only for the personal and confidential use of the designated 
recipient(s) named above.  If you are not the intended recipient of this message you 
are hereby notified that any review, dissemination, distribution or copying of this 
message is strictly prohibited.  This communication is for information purposes only 
and should not be regarded as an offer to sell or as a solicitation of an offer to buy 
any financial product, an official confirmation of any transaction, or as an official 
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or 
error-free.  Therefore, we do not represent that this information is complete or 
accurate and it should not be relied upon as such.  All information is subject to 
change without notice.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]