[Cooker] [Bug 4639] [Installation] printer-utils rpm not found

2003-08-14 Thread [larssj]
http://qa.mandrakesoft.com/show_bug.cgi?id=4639


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Additional Comments From [EMAIL PROTECTED]  2003-10-08 01:44 ---
Same problem by the new installation of 9.2 Beta 2. The system can't do a full
boot -- failes because of missing usbmouse!!!  

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
During the summary process of the installation (done as an upgrade from Cooker Beta 
1, the system install aborts with a repeating error message printer-utils rpm not 
found. 
At this point, I can only click OK repeatedly and cannot break out of this sgtep. 
Resetting the system brings back a working setup but it feels like the install is not 
complete.



[Cooker] [Bug 4561] [printer-utils] missing package

2003-08-11 Thread [larssj]
http://qa.mandrakesoft.com/show_bug.cgi?id=4561


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Additional Comments From [EMAIL PROTECTED]  2003-10-08 16:16 ---
Same problem by the new installation of 9.2 Beta 2 but the system can't do a
full boot because I use a usb keyboard usb-mouse! 

It failes to find the usb modules before it dose rc.sysinit: Finding module
dependencies:  succeeded !!!  

/var/log/message:
---
...
Aug  9 23:50:27 localhost rc.sysinit: Setting hostname localhost:  succeeded 
Aug  9 23:50:27 localhost modprobe: insmod:  
Aug  9 23:50:27 localhost modprobe:
/lib/modules/2.4.21-6mdk/kernel/drivers/usb/usbcore.o: No such file or directory 
Aug  9 23:50:27 localhost modprobe: modprobe: insmod
/lib/modules/2.4.21-6mdk/kernel/drivers/usb/usbcore.o failed 
Aug  9 23:50:27 localhost modprobe: modprobe: insmod usb-uhci failed 
Aug  9 23:50:27 localhost usb: Initializing USB controller (usb-uhci):  failed 
Aug  9 23:50:27 localhost modprobe: insmod:
/lib/modules/2.4.21-6mdk/kernel/drivers/usb/usbcore.o: No such file or directory 
Aug  9 23:50:27 localhost modprobe: modprobe: insmod
/lib/modules/2.4.21-6mdk/kernel/drivers/usb/usbcore.o failed 
Aug  9 23:50:27 localhost modprobe: modprobe: insmod usb-ohci failed 
Aug  9 23:50:27 localhost usb: Initializing USB controller (usb-ohci):  failed 
Aug  9 23:50:27 localhost modprobe: insmod:  
Aug  9 23:50:27 localhost modprobe:
/lib/modules/2.4.21-6mdk/kernel/drivers/usb/usbcore.o: No such file or directory 
Aug  9 23:50:27 localhost modprobe: modprobe: insmod
/lib/modules/2.4.21-6mdk/kernel/drivers/usb/usbcore.o failed 
Aug  9 23:50:27 localhost modprobe: modprobe: insmod ehci-hcd failed 
Aug  9 23:50:27 localhost usb: Initializing USB controller (ehci-hcd):  failed 
Aug  9 23:50:32 localhost rc.sysinit: Remounting root filesystem in read-write
mode:  succeeded 
Aug  9 23:50:32 localhost rc.sysinit: Activating swap partitions:  succeeded 
Aug  9 23:50:44 localhost rc.sysinit: Finding module dependencies:  succeeded 
...


Shall the modules alway be gzipped?
 -- the usb keyboard module is expected to be *.o not *.o.gz !! 

Then shall the usb-keyboard and root filesystem remount rc.sysinit: Remounting
root filesystem in read-write mode:  succeeded be moved after rc.sysinit:
Finding module dependencies:  succeeded -- you need keyboard to do fsck!


-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date: 
description: 
I have downloaded and burned three sets of mdk 9.2 beta 2 and get to the
post-install configuration screen during which I am simply notified that an
error occurred can't find printer-utils.rpm and installation halts and goes
into and endless loop; at this juncture the only out is a reset.  The system
does boot up normally and you can fix the printer installation and screen
settings by going into the Mandrake Control Center