Bug 48834 - Iomega parallel port Zip-250 not working
Iomega parallel port Zip-250 not working
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-07-11 23:05 EDT by Alan F. Mayer
Modified: 2007-04-18 12:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-06 10:38:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alan F. Mayer 2001-07-11 23:05:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
I did a complete 7.1 install. After install I tried to get my Iomega 
parallel port zip 250 to work. I followed the procedure in canned answer 
#195. I received unresolved symbol errors after doing a "/sbin/modprobe 
ppa". The canned answer says to add several pre-install lines if getting 
unresolved symbol errors. I did this and am still getting unresolved 
symbol errors.

How reproducible:

Steps to Reproduce:
1."/sbin/modprobe ppa"

Actual Results:  I receive about 20 unresolved symbol errors

Expected Results:  mount and use the Iomega zip 250 drive

Additional info:
Comment 1 Phil Knirsch 2001-07-17 07:36:36 EDT
This is definitely a kernel problem, so i'm reassigning it to the kernel package.

One suggestion is to use a newer kernel from rawhide.redhat.com and see if this
problem still happens.

Read ya, Phil
Comment 2 Alan F. Mayer 2001-08-01 19:03:22 EDT
Don't I have the latest kernel after installing 7.1?
Comment 3 Phil Knirsch 2001-08-02 05:31:41 EDT
There are errata and update packages available from us:


or specifically for the kernel:


Or for the most recent (and possibily unstable) packages:


Read ya, Phil

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