https://bugzilla.novell.com/show_bug.cgi?id=673845
https://bugzilla.novell.com/show_bug.cgi?id=673845#c31
--- Comment #31 from Silviu Marin-Caea 2011-08-04 12:28:47 UTC ---
Ok, to sum up what we know, because some information is new:
There is a problem with some kernel modules not being loaded automatically.
- module lp, this affects printing on parallel printers
- the module for floppy drives
- there is a report for module usbserial for USB modems. I negate this, just
tried with this device: Bus 001 Device 004: ID 19d2:0033 ONDA Communication
S.p.A.. It's actually Product: ZTE CDMA Technologies MSM. After issuing an
usb_modeswitch command, the usbserial module was loaded automatically.
So, for the lp module, the solution from comment #19 (adding lp to
/etc/sysconfig/kernel:MODULES_LOADED_ON_BOOT) seems to be accepted as the right
one, or at least is uncontested, so far. However, Johannes Meixner explained
in comment #9 and here http://lists.opensuse.org/opensuse/2011-08/msg00058.html
why YaST is not the right piece of software to do that.
So, the question is now: if YaST isn't, what is? I think we all agree that
this is not something the user should have to do manually. So how can this be
done automatically?
How come modules parport, parport_pc and ppdev get to be loaded automatically
and lp not? What mechanism loads parport, parport_pc and ppdev? Can't lp be
added in there as well? Wouldn't this be a better solution that comment #19?
We need a comment from a kernel guru to clarify these things.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.