Article View: comp.os.linux.misc
Article #1394Re: after compiling new kernel, network not working
From: Venex
Date: Thu, 06 Jan 2000 00:00
Date: Thu, 06 Jan 2000 00:00
56 lines
2977 bytes
2977 bytes
Kurniadi Asrigo <q8n25@unb.ca> wrote: >(...) >But after the boot finish and I ran dmesg, it seems the soundcard was >initialized and working right, at least to me. This is part of the >dmesg: > >Sound initialization started >Sound initialization complete Until it's working fine, I can see no problem ;-) >and at the end it said: > >sb_card: I/O, IRQ, and DMA are mandatory ><SoundBlaster EMU8000 (RAM512k)> Check out the /etc/conf.modules. There should be a line in there looking something like this 9this is of course just an example): option sb io=0x220 irq=5 dma=1 dma16=5 I think that there is something missing in that line. Just when you type manually "insmod sb", but without the appropriate parameters, you'll get the same error message. >The complete dmesg is attached at end of this e-mail. "Nice hardware you have!" said master Yoda ;-) >If I try insmod, I will get this message: > >sb.o: unresolved symbol unload_uart401_Rsmp_ecfdd9c9 >sb.o: unresolved symbol attach_uart401_Rsmp_45af1327 >sb.o: unresolved symbol uart401intr_Rsmp_6391d066 >sb.o: unresolved symbol probe_uart401_Rsmp_6467f99b > >in /lib/modules/2.2.13/misc I have these files: >sb.o awe_wave.o es1371.o parport_probe.0 uart401.o >uart6850.o > >Does anybody has any idea about the problem? Or any suggestion that I >have to try? S*** happens ;-) It doesn't matter, really. That kind of errors tend to appear sometimes, but they usually are just warnings and have no influence on how the modules work. If your soundcard work it rather means that everything is OK. You have been watching: "Some lame hints from:" -- Calder a.k.a. Venex Best wishes :-)
Technical Details
Message-ID:
<947191089.1607493841@news.tpnet.pl>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4_uc4.2384$%O1.27606@sodalite.nbnet.nb.ca> <slrn875o70.t6s.perrypip@apollo.netservers.com> <3872E7DC.B63160E2@unb.ca> <947103204.1177725770@news.tpnet.pl> <3874A0FD.D93CB766@unb.ca>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 111240,568ae492a31f8483 X-Google-Attributes: gid111240,public X-Google-Thread: 1143c4,568ae492a31f8483 X-Google-Attributes: gid1143c4,public X-Google-Thread: 101801,568ae492a31f8483 X-Google-Attributes: gid101801,public X-Google-Thread: 1103af,568ae492a31f8483 X-Google-Attributes: gid1103af,public X-Google-Thread: 10669a,568ae492a31f8483 X-Google-Attributes: gid10669a,public From: Venex <varth@box43.gnet.pl> Subject: Re: after compiling new kernel, network not working Date: 2000/01/06 Message-ID: <947191089.1607493841@news.tpnet.pl> X-Deja-AN: 569264343 Content-Transfer-Encoding: quoted-printable References: <4_uc4.2384$%O1.27606@sodalite.nbnet.nb.ca> <slrn875o70.t6s.perrypip@apollo.netservers.com> <3872E7DC.B63160E2@unb.ca> <947103204.1177725770@news.tpnet.pl> <3874A0FD.D93CB766@unb.ca> Content-Type: text/plain; charset=iso-8859-1 X-Complaints-To: abuse@tpsa.pl X-Trace: news.tpnet.pl 947195081 212.160.11.122 (Thu, 06 Jan 2000 22:44:41 MET) Organization: TPNET - http://www.tpnet.pl MIME-Version: 1.0 NNTP-Posting-Date: Thu, 06 Jan 2000 22:44:41 MET Newsgroups: comp.os.linux.misc,comp.os.linux.networking,fj.os.linux.networking,linux.dev.kernel,linux.redhat.misc