During boot-up, and just after the setting the clock line, noticed the
following line:
modeprobe: FATAL: module char_10_135 not found
First noticed this a few revisions ago. The contents of directory
/lib/modules/2.6.0-test3-bk8/kernel/drivers/char:
agp/ genrtc.ko hw_random.ko lp.ko rtc.ko
hmm, long shot, but perhaps this bug is related to not auto-loading
module lp?
Russ
On Wed, Aug 20, 2003 at 05:54:15PM -0700, Russell Whitaker wrote:
>
> During boot-up, and just after the setting the clock line, noticed the
> following line:
>
> modeprobe: FATAL: module char_10_135 not found
>
> First noticed this a few revisions ago. The contents of directory
> /lib/modules/2.6.0-test3-bk8/kernel/drivers/char:
>
> agp/ genrtc.ko hw_random.ko lp.ko rtc.ko
>
> hmm, long shot, but perhaps this bug is related to not auto-loading
> module lp?
Minor 135 is rtc.
Do you have module-init-tools installed?
> Russ
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
On Saturday 30 Aug 2003 11:08, Adrian Bunk wrote:
> Minor 135 is rtc.
Indeed. If it's any help, my rtc's working fine under 2.6.0 (test-4) with...
alias char-major-10-135 rtc
...in my /etc/modprobe.conf.
M
--
"It's the small gaps between the rain that count,
and learning how to live amongst them."
-- Jeff Noon
On Sat, 30 Aug 2003, Adrian Bunk wrote:
> On Wed, Aug 20, 2003 at 05:54:15PM -0700, Russell Whitaker wrote:
> >
> > During boot-up, and just after the setting the clock line, noticed the
> > following line:
> >
> > modeprobe: FATAL: module char_10_135 not found
> >
> > First noticed this a few revisions ago. The contents of directory
> > /lib/modules/2.6.0-test3-bk8/kernel/drivers/char:
> >
> > agp/ genrtc.ko hw_random.ko lp.ko rtc.ko
> >
> > hmm, long shot, but perhaps this bug is related to not auto-loading
> > module lp?
>
> Minor 135 is rtc.
>
> Do you have module-init-tools installed?
>
module-init-tools 0.9.13-pre 2
That was the latest version I could find on Aug 3rd. Please let me know
if there is a later version I should try.
Thanks,
Russ
On Sat, 30 Aug 2003, Russell Whitaker wrote:
>module-init-tools 0.9.13-pre 2
>
>That was the latest version I could find on Aug 3rd. Please let me know
>if there is a later version I should try.
Check the order of calls during boot. In most cases, the rtc will be
required before modules are setup -- /proc/sys/kernel/modprobe isn't
set yet.
--Ricky
On Tue, 2 Sep 2003, Ricky Beam wrote:
> On Sat, 30 Aug 2003, Russell Whitaker wrote:
> >module-init-tools 0.9.13-pre 2
> >
> >That was the latest version I could find on Aug 3rd. Please let me know
> >if there is a later version I should try.
>
> Check the order of calls during boot. In most cases, the rtc will be
> required before modules are setup -- /proc/sys/kernel/modprobe isn't
> set yet.
**update** Had written the following and then updated to 2.6.0-test4-bk8
and found the module_char_10_135 problem has gone away.
Thanks,
Russ
Had changed "Enhanced Real Time Clock" from module to built-in so next
itteration will change it back and check it out. In the meanwhile here's
a recap of what I've done:
Started with a Slackware 9.0 installation, booting kernel 2.4.xx.
Custom kernel, these (amoung others) are modules: lp, floppy, and
"Enhanced Real Time Clock". Have this line in fstab so can mount floppy
as user:
/dev/fd0 /mnt/floppy auto noauto,user
Everything works as expected. Then kernel-2.6 came out. So I "cp /vmlinuz
/vmlinuz.4", changed lilo's first entry to lin6, adding 2nd entry lin4,
installed lilo, edited lilo.config to change the 2nd vmlinuz to vmlinuz.4
and recycled lilo.