Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: More Module Mayhem
- To: tlug@example.com
- Subject: Re: More Module Mayhem
- From: twistedhammer@example.com
- Date: Sat, 2 Jun 2001 13:47:42 -0800
- Content-transfer-encoding: 7BIT
- Content-type: text/plain; charset=US-ASCII
- In-reply-to: <Pine.LNX.4.33.0106021954010.1692-100000@example.com>
- Priority: normal
- Reply-to: twiistedhammer@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <d0_cvB.A.RUG.A6VG7@example.com>
- Resent-Sender: tlug-request@example.com
It sounds like the init script that failed had brought up some of the parport_pc's dependencies. Thus the parport_pc module loaded fine. insmod has no knowledge of dependencies. Instead try 'modprobe parport_pc'. modprobe is a wrapper program for insmod that examines the output of 'depmod -a'. you might want to run 'lsmod' before and after modprobe to see which modules are being loaded. James Gibson On 2 Jun 2001, at 20:24, Dennis McMurchy wrote: <snip> > I got one error message about the parport_pc module apparently not > being loaded, so I tried a manual '/sbin/insmod parport_pc'. This > worked just fine. It produced the message: > > Using /lib/modules/2.4.2-2/kernel/drivers/parport/parport_pc.o > > and made the printer usable from a virtual Win. I was delighted at > how simple it all was. > > However, when I did the same thing later on this afternoon, I got a > whole slew of error messages about unresolved symbols: > > <root@example.com:/home/denis>$ /sbin/insmod parport_pc > Using /lib/modules/2.4.2-2/kernel/drivers/parport/parport_pc.o > /lib/modules/2.4.2-2/kernel/drivers/parport/parport_pc.o: unresolved > symbol parp ort_ieee1284_epp_read_data_R7091445d > /lib/modules/2.4.2-2/kernel/drivers/parport/parport_pc.o: unresolved > symbol parp ort_ieee1284_epp_write_data_R02d3216f > /lib/modules/2.4.2-2/kernel/drivers/parport/parport_pc.o: unresolved > symbol parp ort_ieee1284_read_byte_R71b59e1e > /lib/modules/2.4.2-2/kernel/drivers/parport/parport_pc.o: unresolved > symbol parp ort_ieee1284_epp_read_addr_R0754aa65...etc, etc, etc > > I'm not aware that I've changed anything that would affect the > modules. > What on earth could have happened? And, more importantly, what can I > do to fix this? I have had a look at the manpages, of course, for > 'insmod', 'depmod', and 'modprobe' - not for the first time - but > without finding any inspiration there. > > Hope someone out there has the magic bullet. > > Cheers, Dennis > -- > Dennis McMurchy, > Sointula, B.C. / Tojinmachi, Fukuoka > Canada Japan > > > ---------------------------------------------------------------------- > - Next Technical Meeting: Sat, May 12 13:30- Next Nomikai Meeting: > Fri, June (TBA) 19:30- Tengu Tokyo Eki Mae > ---------------------------------------------------------------------- > - more info: http://www.tlug.gr.jp Sponsor: Global Online > Japan James Gibson twistedhammer@example.com
- Follow-Ups:
- Re: More Module Mayhem [Mastered]
- From: Dennis McMurchy <denismcm@example.com>
- References:
- More Module Mayhem
- From: Dennis McMurchy <denismcm@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: CD-ROM drive
- Next by Date: Re: More Module Mayhem [Mastered]
- Prev by thread: More Module Mayhem
- Next by thread: Re: More Module Mayhem [Mastered]
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links