Bug 41154 - 2.4.3-5 - unresolved symbol in toshiba.o
Summary: 2.4.3-5 - unresolved symbol in toshiba.o
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel
Version: 1.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-17 21:34 UTC by Alexei Podtelezhnikov
Modified: 2007-04-18 16:33 UTC (History)
0 users

Clone Of:
Last Closed: 2001-05-21 06:48:02 UTC

Attachments (Terms of Use)

Description Alexei Podtelezhnikov 2001-05-17 21:34:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.3-5 i686)

Description of problem:
While checking module dependencies athlon variant of the kernel 2.4.3-5
complains about unresolved symbols in toshiba.o.  Not sure if i686 does
that too. 

Also, my Viper chipset has been blacklisted for usb-uhci.o which fails to
load and complains about it. I hope this is no mistake, because that never
happened with 2.4.2-2 and earlier.

How reproducible:

Steps to Reproduce:
1. Booting 2.4.3-5.athlon on Viper chipset 

Additional info:

Comment 1 Arjan van de Ven 2001-05-18 07:47:25 UTC
Regarding the toshiba module: That module is disabled in the .config of the
athlon kernel, and should therefore not be in the RPM. Could you see with

rpm -qf <filename>

which rpm owns that file ?

Regarding the chipset blacklist: AMD has confirmed the chip doesn't work and
corrupts data if used.

Comment 2 Alexei Podtelezhnikov 2001-05-21 06:47:57 UTC
I assume toshiba.o wasn't removed during update from i686 type to athlon one of 
the same 2.4.3-5. I used rpm -Uvh --ignorearch --force. This was the only 
option combination which worked. Without --force I just received tons on errors 
and failure. It's too bad that such switching between kernels is so painful.

BTW, I think it makes sense to use /lib/modules/2.4.3-5.athlon 
and /lib/modules/2.4.3-5.i686 to avoid conflicts and allow people to have both 
versions at the same time.

Note You need to log in before you can comment on or make changes to this bug.