On Tue, 2003-09-30 at 15:56, Charles Curley wrote: > On Tue, Sep 30, 2003 at 09:18:28AM +0200, Nils Philippsen wrote: [...] > > It's a pity that cups tries to randomly probe stuff like USB at all when > > I only have one locally attached parallel printer. I finally filed a > > separate report for it: > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=105986 > > I agree. I have no USB devices attached to my system, and no printers > of any flavor. I had defined no printers at the time, and only looked > into the problem when I had problems trying to use a network printer. > > However, it didn't take cups two whole minutes to decide it couldn't > find the missing module. > > I took another look at my boot messages, and I see a lot of messages > like: > > Sep 29 10:26:15 issola modprobe: modprobe: Can't locate module block-major-34 > > with different numbers attached. What is "block-major-*"? Something > the USB system generates as needed? It means "something is accessing a block device with major number 34 and I cannot associate any drivers with it" -- you can lookup known device major/minor numbers in /usr/src/linux-2.4/Documentation/devices.txt. In your case: [...] 34 char Z8530 HDLC driver 0 = /dev/scc0 First Z8530, first port [...] block Fourth IDE hard disk/CD-ROM interface 0 = /dev/hdg Master: whole disk (or CD-ROM) 64 = /dev/hdh Slave: whole disk (or CD-ROM) Partitions are handled the same way as for the first interface (see major number 3). [...] > Nils, did you get your printer to work even with this problem? Yes, no problem when cups is running. Nils -- Nils Philippsen / Red Hat / nphilipp@xxxxxxxxxx "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- B. Franklin, 1759 PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
Attachment:
signature.asc
Description: This is a digitally signed message part
