Re: module cdu31a fails on insert
From: [EMAIL PROTECTED] (renald loignon) May I ask, in all seriousness, and without a trace of sarcasm, where in the world (BUT preferably in the Debian installation instructions) one is expected to find this information? I was used to the old cdu31a=0xPORT,IRQ syntax from the boot prompt, or as an append=... line in /etc/lilo.conf I don't see that it is documented at all outside of the kernel source. And if you think that this is a serious problem in Debian, it is. And it's not going to be helped unless more people like you volunteer to work on the documentation. Is there any chance you have checked the bootparm-howto? http://sunsite.unc.edu/mdw ?? If it is not in there, I would suggest that would be the best place for it. -- Todd Fries .. [EMAIL PROTECTED]
Re: module cdu31a fails on insert
Todd Is there any chance you have checked the bootparm-howto? Todd Todd http://sunsite.unc.edu/mdw ?? If you install Debian's doc-linux package, they are also at /usr/doc/HOWTO/* As the doc-linux package is updated monthly with the upstream HOWTOs, you should always look for the newest one in unstable/binary-all/doc. Safe to install on any system as it's only text. Hard to put a bug into that :-) -- Dirk Eddelbuttel http://qed.econ.queensu.ca/~edd
Re: module cdu31a fails on insert
Susan: I'm getting confused. Isn't the purpose of /usr/lib/module_help/arguments to document the arguments that can be given to a module when it is activated? I don't think the cdu31a information is in there - we must have missed it when we created modconf. Also, not everyone uses modconf, which is the only thing that displays the module_help files. We don't have a person who follows the kernel and keeps an accurate list of module arguments. Also, Lars took on modconf when I had too much to do, but he was less than enthusiastic about it. We could use another volunteer to be the module mayven. Thanks Bruce
Re: module cdu31a fails on insert
Bruce Perens: We don't have a person who follows the kernel and keeps an accurate list of module arguments. Also, Lars took on modconf when I had too much to do, but he was less than enthusiastic about it. We could use another volunteer to be the module mayven. Ilucius ([EMAIL PROTECTED]) took it from me, but I'm not sure if we bothered to tell anyone. (Ilucius, perhaps you can confirm this.) -- Rural sizes win [EMAIL PROTECTED] http://www.iki.fi/liw/ Please don't Cc: me when replying to my message on a mailing list. pgpQLHOsAAaAZ.pgp Description: PGP signature
Re: module cdu31a fails on insert
On Tue, 20 Aug 1996, Lars Wirzenius wrote: Bruce Perens: We don't have a person who follows the kernel and keeps an accurate list of module arguments. Also, Lars took on modconf when I had too much to do, but he was less than enthusiastic about it. We could use another volunteer to be the module mayven. Ilucius ([EMAIL PROTECTED]) took it from me, but I'm not sure if we bothered to tell anyone. (Ilucius, perhaps you can confirm this.) Yep, your right. I neglected to inform anyone. (face red in shame) I've been playing around with this architecture independence stuff that I COMPLETELY forgot about it. But, since I'll be without a modem for a few days, I'll take the time to scan the kernel source for any additions/differences. Leland __ Y_ a_ m_ b_ o_ | The leanest, meanest, fightinest sweet tater on Earth! oo o oo o o | o o o | [EMAIL PROTECTED] o ooo o | -- -- -- -- -- -- | http://www.millcomm.com/~llucius (maybe one day)
Re: module cdu31a fails on insert
Susan: I'm getting confused. Isn't the purpose of /usr/lib/module_help/arguments to document the arguments that can be given to a module when it is activated? I don't think the cdu31a information is in there - we must have missed it when we created modconf. Also, not everyone uses modconf, which is the only thing that displays the module_help files. We don't have a person who follows the kernel and keeps an accurate list of module arguments. Also, Lars took on modconf when I had too much to do, but he was less than enthusiastic about it. We could use another volunteer to be the module mayven. I hear you Bruce. I most certainly do not wish to put down the fine efforts that you and the rest of the Debian group are putting in. Also, I consider it quite likely that I will eventually get involved (again) in some non-profit group or other having to do with computer software and/or the Internet. (In fact, been there, done that, if you will give some consideration to some 5 years of involvement in Fidonet at many levels). Honesty, whether I join the Linux camp or another will depend on the success of my current efforts to bootstrap myself into this community. For now, most of my on-line interactions are done with Eudora for Windows (email), Free Agent (news) , WsFTP and Netscape for Windows. Thus, as a example of obstacle to my progression, I cannot easily grab a set of HTMLized FAQs from the Net for local perusal because they use long filenames. Also, I am constrained to getting the msdos-i386 branch of the distribution sites, even though dselect seems to be somewhat reluctant to use these DOS filenames... And if I start seriously considering the purchase of a CD copy of the distribution, to give dselect the long filenames it prefers, I have to face a non-documented module argument... taking on the whining voice of Gilda Radner's Roseanne Roseannadanna When it's not one thing, it's another... ;-))) Hey, don't let me spoil your fun. Whenever I point out a flaw in the Debian distribution, I do it in the spirit of providing useful feedback, and with no malice whatsoever. Consider it my first level of contribution to your fine work. Hopefully, in the fullness of time I will feel confident and knowledgeable enough to participate in more significant ways. In the meantime, I'm still here, so despite my setbacks, I haven't given up Regards, renald
Re: module cdu31a fails on insert
Lars: Ilucius ([EMAIL PROTECTED]) took it from me From: llucius [EMAIL PROTECTED] Yep, your right. I neglected to inform anyone. (face red in shame) I've been playing around with this architecture independence stuff that I COMPLETELY forgot about it. Leland, of course I'm happy to get any work you do on this now. You are also one of the lead programmers on the 68k port, and you are a lead programmer on the issue of architecture independence for Debian. One of our problems is that a few key volunteers do a _lot_ of stuff, and tasks should be distributed better so that those key people can continue to have lives and health :-) So I won't frown if you eventually find someone else to take on the job of tracking modules. Thanks Bruce
Re: module cdu31a fails on insert
From: [EMAIL PROTECTED] (renald loignon) May I ask, in all seriousness, and without a trace of sarcasm, where in the world (BUT preferably in the Debian installation instructions) one is expected to find this information? I was used to the old cdu31a=0xPORT,IRQ syntax from the boot prompt, or as an append=... line in /etc/lilo.conf I don't see that it is documented at all outside of the kernel source. And if you think that this is a serious problem in Debian, it is. And it's not going to be helped unless more people like you volunteer to work on the documentation. Thanks Bruce -- Clinton isn't perfect, but I like him a lot more than Dole. Please register to vote, and vote for Democrats. Bruce Perens AB6YM [EMAIL PROTECTED]http://www.hams.com/
Re: module cdu31a fails on insert
Bruce Perens wrote: From: [EMAIL PROTECTED] (renald loignon) May I ask, in all seriousness, and without a trace of sarcasm, where in the world (BUT preferably in the Debian installation instructions) one is expected to find this information? I was used to the old cdu31a=0xPORT,IRQ syntax from the boot prompt, or as an append=... line in /etc/lilo.conf I don't see that it is documented at all outside of the kernel source. I'm getting confused. Isn't the purpose of /usr/lib/module_help/arguments to document the arguments that can be given to a module when it is activated? ?, Susan Kleinmann
module cdu31a fails on insert
I am installing debian 1.1.1 from the August Pacific Hi Tech CD on my Gateway 200 PS-60. Things go OK until I try to add the cdu31a module to support the CDU33A CDROM drive in the Gateway: it fails to insert. The drive is defaulted onto 0x340; when I try to add a parameter to the module insertion it either fails the same way or gives me an invalid parameter message. So perhaps I am providing the parameter in the wrong format (could not find any documentation with the distribution on the format of module parameters) - or something else is wrong. Everything works OK using Slackware 3.0 kernel 1.2.13 with cdu31a support in the kernel. Thanks, Michael Laing
Re: module cdu31a fails on insert
From: [EMAIL PROTECTED] Things go OK until I try to add the cdu31a module to support the CDU33A CDROM drive in the Gateway: it fails to insert. The drive is defaulted onto 0x340; when I try to add a parameter to the module insertion it either fails the same way or gives me an invalid parameter message. Use the argument cdu31a_port=0x340 when you install the module. It also understands cdu31a_irx=N. Bruce -- Clinton isn't perfect, but I like him a lot more than Dole. Please register to vote, and vote for Democrats. Bruce Perens AB6YM [EMAIL PROTECTED]http://www.hams.com/
Re: module cdu31a fails on insert
Hi Michael! On Sun, 18 Aug 1996 [EMAIL PROTECTED] wrote: The drive is defaulted onto 0x340; when I try to add a parameter to the module insertion it either fails the same way or gives me an invalid parameter message. Have you tried with the following parameter? cdu31a_port=0x340 Bye Good Luck! Pablo B.
Re: module cdu31a fails on insert
Use the argument cdu31a_port=0x340 when you install the module. It also understands cdu31a_irx=N. May I ask, in all seriousness, and without a trace of sarcasm, where in the world (BUT preferably in the Debian installation instructions) one is expected to find this information? I was used to the old cdu31a=0xPORT,IRQ syntax from the boot prompt, or as an append=... line in /etc/lilo.conf
