[Cooker] [Bug 3328] [harddrake] INSMOD error after running harddrake at boot

2003-03-19 Thread tvignaud
http://qa.mandrakesoft.com/show_bug.cgi?id=3328

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||WONTFIX



--- Additional Comments From [EMAIL PROTECTED]  2003-03-19 10:35 ---
just a warning of the floppy detection. 
 
harddrake ask detect_devices to list all availlable floppy drives, which in turn needs 
floppy 
module to be loaded. 
 
hance the message 



--- 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: 
On screen message given after upgrading to latest harddrake does not happen on
original release of RC2, on screen message is:

"Hint: Insmod errors can be caused by incorrect module parameters, including IO
or IRQ parameters. You may find more information in SYSLOG or DMESG once you
have logged in"



[Cooker] [Bug 3328] [harddrake] INSMOD error after running harddrake at boot

2003-03-16 Thread andy.dewhurst
http://qa.mandrakesoft.com/show_bug.cgi?id=3328





--- Additional Comments From [EMAIL PROTECTED]  2003-03-16 17:19 ---
There is nothing in syslog but if you remove the > /dev/nul from the detection process 
you get 
on screen: 
 
/lib/modules/2.4.21-0.11mdk/kernel/drivers/block/floppy.o.gz: init_module: No such 
device 
modprobe: insmod /lib/modules/2.4.21-0.11mdk/kernel/drivers/block/floppy.o.gz failed 
modprobe: insmod floppy failed 
 
 
Why is it trying to insmod a device that isn't in the machine? The machine is a 
floppyless 
workstation. 



--- 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: 
On screen message given after upgrading to latest harddrake does not happen on
original release of RC2, on screen message is:

"Hint: Insmod errors can be caused by incorrect module parameters, including IO
or IRQ parameters. You may find more information in SYSLOG or DMESG once you
have logged in"



[Cooker] [Bug 3328] [harddrake] INSMOD error after running harddrake at boot

2003-03-15 Thread tmb
http://qa.mandrakesoft.com/show_bug.cgi?id=3328





--- Additional Comments From [EMAIL PROTECTED]  2003-03-15 10:20 ---
Viestissä Lauantai 15. Maaliskuuta 2003 10:05, andy.dewhurst kirjoitti:

So what is in the syslog?
(the error message stated syslog _or_ dmesg ...)

thomas




--- 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: 
On screen message given after upgrading to latest harddrake does not happen on
original release of RC2, on screen message is:

"Hint: Insmod errors can be caused by incorrect module parameters, including IO
or IRQ parameters. You may find more information in SYSLOG or DMESG once you
have logged in"



[Cooker] [Bug 3328] [harddrake] INSMOD error after running harddrake at boot

2003-03-15 Thread andy.dewhurst
http://qa.mandrakesoft.com/show_bug.cgi?id=3328





--- Additional Comments From [EMAIL PROTECTED]  2003-03-15 09:05 ---
exactly, there is nothing mentioned in dmesg, The kernel version is the one 
supplied with RC2.  



--- 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: 
On screen message given after upgrading to latest harddrake does not happen on
original release of RC2, on screen message is:

"Hint: Insmod errors can be caused by incorrect module parameters, including IO
or IRQ parameters. You may find more information in SYSLOG or DMESG once you
have logged in"



[Cooker] [Bug 3328] [harddrake] INSMOD error after running harddrake at boot

2003-03-14 Thread tmb
http://qa.mandrakesoft.com/show_bug.cgi?id=3328





--- Additional Comments From [EMAIL PROTECTED]  2003-03-15 04:49 ---
What kernel version? 
 
what insmod error? 
 
dmesg does not show any insmod error...!!! 



--- 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: 
On screen message given after upgrading to latest harddrake does not happen on
original release of RC2, on screen message is:

"Hint: Insmod errors can be caused by incorrect module parameters, including IO
or IRQ parameters. You may find more information in SYSLOG or DMESG once you
have logged in"



[Cooker] [Bug 3328] [harddrake] INSMOD error after running harddrake at boot

2003-03-14 Thread andy.dewhurst
http://qa.mandrakesoft.com/show_bug.cgi?id=3328





--- Additional Comments From [EMAIL PROTECTED]  2003-03-14 20:22 ---
Created an attachment (id=361)
 --> (http://qa.mandrakesoft.com/attachment.cgi?id=361&action=view)
DMESG output 

Attached DMESG output



--- 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: 
On screen message given after upgrading to latest harddrake does not happen on
original release of RC2, on screen message is:

"Hint: Insmod errors can be caused by incorrect module parameters, including IO
or IRQ parameters. You may find more information in SYSLOG or DMESG once you
have logged in"