Rpmbuild question

[Thomas E Dukes]

Hello,

I have never rebuilt a src package and am not really sure how to do this.  I
read the man page but I can't seem to figure it out.

I want to rebuild the proftpt src rpm from pbone.net with mysql support.
The package indicates 2 rebuild options:

Available rpmbuild rebuild options :
--without : tls
--with : ldap mysql postgresql

I have installed the source rpm and tried running rpmbuild -ba --with : ldap
mysql postgresql from /usr/src/redhat/SPECS but that doesn't work.

Can I get a little help here?  I have tried numerous times with all kind of
different combinations and still no go.

TIA

[Paul Howarth]

Thomas E. Dukes wrote:
> Hello,
>
> I have never rebuilt a src package and am not really sure how to do this.  I
> read the man page but I can't seem to figure it out.
>
> I want to rebuild the proftpt src rpm from pbone.net with mysql support.
> The package indicates 2 rebuild options:
>
> Available rpmbuild rebuild options :
> --without : tls
> --with : ldap mysql postgresql
>
> I have installed the source rpm and tried running rpmbuild -ba --with : ldap
> mysql postgresql from /usr/src/redhat/SPECS but that doesn't work.
>
> Can I get a little help here?  I have tried numerous times with all kind of
> different combinations and still no go.

Try:

rpmbuild --rebuild --with mysql proftpd.src.rpm
or
rpmbuild --rebuild --with mysql --with ldap proftpd.src.rpm
etc.

Cheers, Paul.

[Dag Wieers]

On Thu, 26 Aug 2004, Thomas E. Dukes wrote:
> I have never rebuilt a src package and am not really sure how to do this.  I
> read the man page but I can't seem to figure it out.
>
> I want to rebuild the proftpt src rpm from pbone.net with mysql support.
> The package indicates 2 rebuild options:
>
> Available rpmbuild rebuild options :
> --without : tls
> --with : ldap mysql postgresql
>
> I have installed the source rpm and tried running rpmbuild -ba --with : ldap
> mysql postgresql from /usr/src/redhat/SPECS but that doesn't work.
>
> Can I get a little help here?  I have tried numerous times with all kind of
> different combinations and still no go.

Ok, based on your feedback I noticed it is Matthias (freshrpms) his 
proftpd package :) Try something like this:

rpmbuild --rebuild --with ldap --with mysql --with postgresql proftpd*.src.rpm

That should work.

--   dag wieers,  [e-mail],  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]

[Thomas E Dukes]

> Ok, based on your feedback I noticed it is Matthias 
> (freshrpms) his proftpd package :) Try something like this:
>
> rpmbuild --rebuild --with ldap --with mysql --with 
> postgresql proftpd*.src.rpm
>
> That should work.

No, actually it was your src.rpm I'm trying to rebuild.  That got it.
Thanks!!

[Thomas E Dukes]

Oooops, one more question.  :-)

If I just rebuilt the source rpm, then I guess I need to build a binary
package after I install the newly rebuilt source package, right?

TIA
> Ok, based on your feedback I noticed it is Matthias 
> (freshrpms) his proftpd package :) Try something like this:
>
> rpmbuild --rebuild --with ldap --with mysql --with 
> postgresql proftpd*.src.rpm
>
> That should work.

[Paul Howarth]

Thomas E. Dukes wrote:
> Oooops, one more question.  :-)
>
> If I just rebuilt the source rpm, then I guess I need to build a binary
> package after I install the newly rebuilt source package, right?

Nope; if you "rpmbuild --rebuild" a src.rpm package you'll just get the binary 
packages built on your system, no new src.rpm. It would be equivalent to 
"rpmbuild -bb specfile". If you do "rpmbuild -ba specfile" you'll get a new 
src.rpm but unless you've edited the specfile, it won't have any significant 
differences to the src.rpm you started with.

Cheers, Paul.

[Thomas E Dukes]

OK,

I thought I had this worked out but its not building a binary rpm.  I thinks
its bombing out.

Here's the message:

/usr/bin/ld: cannot find -lmysqlclient
collect2: ld returned 1 exit status
make: *** [proftpd] Error 1
Error: Bad exit status from /var/tmp/rpm-tmp.22654 (%build)

User machbuild does not exist - using root
Group machbuild does not exist - using root
 (repeats about 6 times)

Bad exit status from /var/tmp/rpm-tmp.22654 (%build)

I don't think it can find mysqlclient but I may be wrong.  I located it at
/usr/lib/mysql

TIA

[Paul Howarth]

Thomas E. Dukes wrote:
> I thought I had this worked out but its not building a binary rpm.  I thinks
> its bombing out.
>
> Here's the message:
>
> /usr/bin/ld: cannot find -lmysqlclient
> collect2: ld returned 1 exit status
> make: *** [proftpd] Error 1
> Error: Bad exit status from /var/tmp/rpm-tmp.22654 (%build)

It can't find libmysqlclient; it's part of the mysql-devel package but it puts 
it /usr/lib/mysql rather than /usr/lib. Try setting the LDFLAGS environment 
variable before doing the rpmbuild:

export LDFLAGS=-L/usr/lib/mysql
rpmbuild ...
> User machbuild does not exist - using root
> Group machbuild does not exist - using root
>  (repeats about 6 times)

These are normal. The src.rpm was built by someone with username machbuild. 
Nothing to worry about there.

Paul.

[Michael Schwendt]

On Thu, 26 Aug 2004 10:32:49 -0400, Thomas E. Dukes wrote:
> OK,
>
> I thought I had this worked out but its not building a binary rpm.  I thinks
> its bombing out.
>
> Here's the message:
>
> /usr/bin/ld: cannot find -lmysqlclient
> collect2: ld returned 1 exit status
> make: *** [proftpd] Error 1
> Error: Bad exit status from /var/tmp/rpm-tmp.22654 (%build)
>
> User machbuild does not exist - using root
> Group machbuild does not exist - using root
>  (repeats about 6 times)
>
> Bad exit status from /var/tmp/rpm-tmp.22654 (%build)
>
> I don't think it can find mysqlclient but I may be wrong.  I located it at
> /usr/lib/mysql

"mysql-devel" not installed. It contains /usr/lib/mysql/libmysqlclient.so

[Thomas E Dukes]

> Thomas E. Dukes wrote:
> > I thought I had this worked out but its not building a
>
> binary rpm.  I
> > thinks its bombing out.
> >
> > Here's the message:
> >
> > /usr/bin/ld: cannot find -lmysqlclient
> > collect2: ld returned 1 exit status
> > make: *** [proftpd] Error 1
> > Error: Bad exit status from /var/tmp/rpm-tmp.22654 (%build)
>
> It can't find libmysqlclient; it's part of the mysql-devel 
> package but it puts it /usr/lib/mysql rather than /usr/lib. 
> Try setting the LDFLAGS environment variable before doing the 
> rpmbuild:
>
> export LDFLAGS=-L/usr/lib/mysql
> rpmbuild ...
> > User machbuild does not exist - using root Group machbuild does not 
> > exist - using root  (repeats about 6 times)
>
> These are normal. The src.rpm was built by someone with 
> username machbuild. 
> Nothing to worry about there.

Thanks again for the help!  That solved one problem but I now have a new
one.  :-(

The last few lines:

Modules/mod_sql.o(.data+0x3c0):/usr/src/redhat/BUILD/proftpd-1.2.9/modules/m
od_sql.c:400 first defined here
Collect2: ld returned 1 exit status
Make: *** [profptd] Error 1
Error: Bad exit status from /var/tmp/rpm-tmp.32603 (%build)

Don't have a clue about this one.

TIA

[Paul Howarth]

Thomas E. Dukes wrote:
> Thanks again for the help!  That solved one problem but I now have a new
> one.  :-(
>
> The last few lines:
>
> Modules/mod_sql.o(.data+0x3c0):/usr/src/redhat/BUILD/proftpd-1.2.9/modules/m
> od_sql.c:400 first defined here
> Collect2: ld returned 1 exit status
> Make: *** [profptd] Error 1
> Error: Bad exit status from /var/tmp/rpm-tmp.32603 (%build)
>
> Don't have a clue about this one.

I've just tried this with my own proftpd RPM. I found that if I specified the 
sql_mysql module without also specifying the sql module (first) then I got the 
same problem.

So I needed:

rpmbuild --rebuild --with mod_sql --with mod_sql_mysql proftpd.src.rpm

You might want to look for a similar option in your spec file.

I've now fixed my own RPM so that it automatically includes mod_sql if the 
mysql or postgres backends are selected. You can get the SRPM (1.2.10rc3) from:

http://www.city-fan.org/ftp/contrib/misc/

if you're interested. The binary RPMs don't have SQL support so you won't want 
those.

Cheers, Paul.

[Thomas E Dukes]

On Thu, 2004-08-26 at 11:44, Paul Howarth wrote:
> Thomas E. Dukes wrote:
> > Thanks again for the help!  That solved one problem but I now have a new
> > one.  :-(
> >
> > The last few lines:
> >
> > Modules/mod_sql.o(.data+0x3c0):/usr/src/redhat/BUILD/proftpd-1.2.9/modules/m
> > od_sql.c:400 first defined here
> > Collect2: ld returned 1 exit status
> > Make: *** [profptd] Error 1
> > Error: Bad exit status from /var/tmp/rpm-tmp.32603 (%build)
> >
> > Don't have a clue about this one.
>
> I've just tried this with my own proftpd RPM. I found that if I specified the 
> sql_mysql module without also specifying the sql module (first) then I got the 
> same problem.
>
> So I needed:
>
> rpmbuild --rebuild --with mod_sql --with mod_sql_mysql proftpd.src.rpm
>
> You might want to look for a similar option in your spec file.
>
> I've now fixed my own RPM so that it automatically includes mod_sql if the 
> mysql or postgres backends are selected. You can get the SRPM (1.2.10rc3) from:
>
> http://www.city-fan.org/ftp/contrib/misc/
>
> if you're interested. The binary RPMs don't have SQL support so you won't want 
> those.
>
> Cheers, Paul.

Thanks for all the help, Paul.  That worked!!

Thanks!!

[Dag Wieers]

On Thu, 26 Aug 2004, Thomas E. Dukes wrote:
> > Ok, based on your feedback I noticed it is Matthias 
> > (freshrpms) his proftpd package :) Try something like this:
> >
> > rpmbuild --rebuild --with ldap --with mysql --with 
> > postgresql proftpd*.src.rpm
> >
> > That should work.
>
> No, actually it was your src.rpm I'm trying to rebuild.  That got it.
> Thanks!!

It really is Matthias his package (the SPEC files also reflects that), but 
I just provide it for some older and some other distributions and archs.

Not that it matters though, but he earns the credit for his work.

--   dag wieers,  [e-mail],  http://dag.wieers.com/   -- 
[Any errors in spelling, tact or fact are transmission errors]

[Dag Wieers]

On Thu, 26 Aug 2004, Thomas E. Dukes wrote:
> OK,
>
> I thought I had this worked out but its not building a binary rpm.  I thinks
> its bombing out.
>
> Here's the message:
>
> /usr/bin/ld: cannot find -lmysqlclient
> collect2: ld returned 1 exit status
> make: *** [proftpd] Error 1
> Error: Bad exit status from /var/tmp/rpm-tmp.22654 (%build)
>
> User machbuild does not exist - using root
> Group machbuild does not exist - using root
>  (repeats about 6 times)
>
> Bad exit status from /var/tmp/rpm-tmp.22654 (%build)
>
> I don't think it can find mysqlclient but I may be wrong.  I located it at
> /usr/lib/mysql

Is it possible that you used --nodeps to have it continue ? Because the 
SPEC file actually already takes care of it:

%{?_with_mysql:Requires: mysql}
    %{?_with_mysql:BuildRequires: mysql-devel, zlib-devel}

This will make sure that if you specify --with mysql, it will fail if you 
don't have the BuildRequires installed.

If you want to learn to build or rebuild packages, please take a look and 
try to understand the contents of the SPEC file. It really isn't hard and 
it will save you quite a lot of time trying to get things done :)

Kind regards,
--   dag wieers,  [e-mail],  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]

[Bob Holtzman]

On Thu, 26 Aug 2004, Paul Howarth wrote:
> Thomas E. Dukes wrote:
> > Oooops, one more question.  :-)
> >
> > If I just rebuilt the source rpm, then I guess I need to build a binary
> > package after I install the newly rebuilt source package, right?
>
> Nope; if you "rpmbuild --rebuild" a src.rpm package you'll just get the binary 
> packages built on your system, no new src.rpm. It would be equivalent to 
> "rpmbuild -bb specfile". If you do "rpmbuild -ba specfile" you'll get a new 
> src.rpm but unless you've edited the specfile, it won't have any significant 
> differences to the src.rpm you started with.

I assume that, since rpmbuild is run against the src.rpm file, the src.rpm 
file doesn't get installed thereby splitting off the .spec file. Is this 
correct?

[Thomas E Dukes]

Hi Dag,

I finally got it to rebuild BUT, proftpd (with mysql support) is a little
tougher to config than I imagined.  I'm back to vsftpd.  :-(

I'll keep working at it.

I have used several of your binary rpm's and have had no problems.  Thanks
for you contributions!!!
> It really is Matthias his package (the SPEC files also 
> reflects that), but I just provide it for some older and some 
> other distributions and archs.
>
> Not that it matters though, but he earns the credit for his work.
>
> --   dag wieers,  [e-mail],  http://dag.wieers.com/   -- 
> [Any errors in spelling, tact or fact are transmission errors]
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

[Paul Howarth]

On Fri, 2004-08-27 at 02:03, Bob Holtzman wrote:
> On Thu, 26 Aug 2004, Paul Howarth wrote:
> > Thomas E. Dukes wrote:
> > > Oooops, one more question.  :-)
> > >
> > > If I just rebuilt the source rpm, then I guess I need to build a binary
> > > package after I install the newly rebuilt source package, right?
> >
> > Nope; if you "rpmbuild --rebuild" a src.rpm package you'll just get the binary 
> > packages built on your system, no new src.rpm. It would be equivalent to 
> > "rpmbuild -bb specfile". If you do "rpmbuild -ba specfile" you'll get a new 
> > src.rpm but unless you've edited the specfile, it won't have any significant 
> > differences to the src.rpm you started with.
>
> I assume that, since rpmbuild is run against the src.rpm file, the src.rpm 
> file doesn't get installed thereby splitting off the .spec file. Is this 
> correct?

The src.rpm gets installed, then built, then removed. If the build fails
the installed src.rpm (i.e. spec, sources, part-built package) is left
in your build area and you can look at the spec file etc. to try to
figure out what went wrong.

Paul.

[Paul Howarth]

On Fri, 2004-08-27 at 01:42, Dag Wieers wrote:
> Is it possible that you used --nodeps to have it continue ? Because the 
> SPEC file actually already takes care of it:
>
> %{?_with_mysql:Requires: mysql}
>    %{?_with_mysql:BuildRequires: mysql-devel, zlib-devel}
>
> This will make sure that if you specify --with mysql, it will fail if you 
> don't have the BuildRequires installed.

He did have mysql-devel installed; building with mysql on FC2 requires
passing --with-libraries=%{_libdir}/mysql and also ensuring that mod_sql
is selected in addition to mod_sql_mysql. Those seemed to be the
problems that he came across.

Paul.

[Dag Wieers]

On Fri, 27 Aug 2004, Paul Howarth wrote:
> On Fri, 2004-08-27 at 01:42, Dag Wieers wrote:
> > Is it possible that you used --nodeps to have it continue ? Because the 
> > SPEC file actually already takes care of it:
> >
> > %{?_with_mysql:Requires: mysql}
> >    %{?_with_mysql:BuildRequires: mysql-devel, zlib-devel}
> >
> > This will make sure that if you specify --with mysql, it will fail if you 
> > don't have the BuildRequires installed.
>
> He did have mysql-devel installed; building with mysql on FC2 requires
> passing --with-libraries=%{_libdir}/mysql and also ensuring that mod_sql
> is selected in addition to mod_sql_mysql. Those seemed to be the
> problems that he came across.

Well, I didn't mention it because it actually is there too. Look at:

http://dag.wieers.com/packages/proftpd/proftpd.spec

You'll see:

%{?_with_mysql:--with-libraries="%{_libdir}/mysql"} \
    %{?_with_postgresql:--with-libraries="%{_libdir}"} \
    --with-modules=mod_readme:mod_auth_pam%{?_with_ldap::mod_ldap}%{?_with_mysql::mod_sql:mod_sql_mysql}%{?_with_postgresql::mod_sql:mod_sql_postgres}%{!?_without_tls::mod_tls}

So it is well designed to handle all the situations and what has happened 
should not have happened, unless he did --nodeps. Or did I miss something ?

Kind regards,
--   dag wieers,  [e-mail],  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]

[Paul Howarth]

On Tue, 2004-08-31 at 01:15, Dag Wieers wrote:
> On Fri, 27 Aug 2004, Paul Howarth wrote:
> > He did have mysql-devel installed; building with mysql on FC2 requires
> > passing --with-libraries=%{_libdir}/mysql and also ensuring that mod_sql
> > is selected in addition to mod_sql_mysql. Those seemed to be the
> > problems that he came across.
>
> Well, I didn't mention it because it actually is there too. Look at:
>
> http://dag.wieers.com/packages/proftpd/proftpd.spec
>
> You'll see:
>
> %{?_with_mysql:--with-libraries="%{_libdir}/mysql"} \
>    %{?_with_postgresql:--with-libraries="%{_libdir}"} \
>    --with-modules=mod_readme:mod_auth_pam%{?_with_ldap::mod_ldap}%{?_with_mysql::mod_sql:mod_sql_mysql}%{?_with_postgresql::mod_sql:mod_sql_postgres}%{!?_without_tls::mod_tls}
>
> So it is well designed to handle all the situations and what has happened 
> should not have happened, unless he did --nodeps. Or did I miss something ?

Well that all looks fine so I don't know what was happening. Somehow
he'd got it looking for but not finding the mysql libraries. I wonder if
he'd edited the spec file?

Paul.

[Thomas E Dukes]

Hello,
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Paul Howarth
> Sent: Tuesday, August 31, 2004 3:24 AM
> To: For users of Fedora Core releases
> Subject: RE: Rpmbuild question
>
> On Tue, 2004-08-31 at 01:15, Dag Wieers wrote:
> > On Fri, 27 Aug 2004, Paul Howarth wrote:
> > > He did have mysql-devel installed; building with mysql on FC2 
> > > requires passing --with-libraries=%{_libdir}/mysql and
>
> also ensuring
> > > that mod_sql is selected in addition to mod_sql_mysql.
>
> Those seemed
> > > to be the problems that he came across.
> >
> > Well, I didn't mention it because it actually is there too. Look at:
> >
> > http://dag.wieers.com/packages/proftpd/proftpd.spec
> >
> > You'll see:
> >
> > %{?_with_mysql:--with-libraries="%{_libdir}/mysql"} \
> >    %{?_with_postgresql:--with-libraries="%{_libdir}"} \
>
> --with-modules=mod_readme:mod_auth_pam%{?_with_ldap::mod_ldap}%{?_with
> >
>
> _mysql::mod_sql:mod_sql_mysql}%{?_with_postgresql::mod_sql:mod_sql_pos
> > tgres}%{!?_without_tls::mod_tls}
> >
> > So it is well designed to handle all the situations and what has 
> > happened should not have happened, unless he did --nodeps.
>
> Or did I miss something ?

No, I didn't use --nodeps.  I did as Paul suggessted:
rpmbuild --rebuild --with mod_sql --with mod_sql_mysql
proftpd-1.2.10-0.rc3.2.src.rpm
> Well that all looks fine so I don't know what was happening. 
> Somehow he'd got it looking for but not finding the mysql 
> libraries. I wonder if he'd edited the spec file?

No, I didn't touch the spec file.  I would'nt have know what to edit.

It rebuilt but I was unable to get proftpd setup so I went back to vsftpd.
I tried to setup up a db as in the example but could not get the tables to
create.  I finally changed a few things and created a db that was similar.
Then, I figured I'd have to manually insert all ftp users into the db. Then
I wondered could some users (virtual host) be authenticated using mysql and
others in a different virtual host by PAM or whatever vsftpd is using.

I was getting over my head fast so I just went back to vsftpd.

I do appreciate the help from both of you!!

Thanks!!

[Paul Howarth]

Hi Thomas,

Thomas E. Dukes wrote:
> No, I didn't use --nodeps.  I did as Paul suggessted:
> rpmbuild --rebuild --with mod_sql --with mod_sql_mysql
> proftpd-1.2.10-0.rc3.2.src.rpm

That one's my RPM though, not Dag's. Do you recall what you did to try to 
build the first RPM your downloaded?

Paul.

[Thomas E Dukes]

Hi Paul,

First I tried rpmbuild -ba --with : ldap mysql postgresql (several ways),
then after posting to the list I tried something like rpmbuild --rebuild
--with : ldap mysql postgresql (serveral more times), then finally the way
you suggested.

Thanks!!
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Paul Howarth
> Sent: Tuesday, August 31, 2004 8:55 AM
> To: For users of Fedora Core releases
> Subject: Re: Rpmbuild question
>
> Hi Thomas,
>
> Thomas E. Dukes wrote:
> > No, I didn't use --nodeps.  I did as Paul suggessted:
> > rpmbuild --rebuild --with mod_sql --with mod_sql_mysql 
> > proftpd-1.2.10-0.rc3.2.src.rpm
>
> That one's my RPM though, not Dag's. Do you recall what you 
> did to try to build the first RPM your downloaded?
>
> Paul.
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

Modules question

[Thomas E Dukes]

Hello,

About a year ago, I installed an ide CDRW.  I added the following lines to
modules.conf:

options ide-cd ignore=hdb
pre-install sg     modprobe ide-scsi # load ide-scsi before sg
pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
pre-install ide-scsi modprobe ide-cd # load ide-cd   before ide-scsi

Since upgrading from RH 9 to FC 2, I now get "fatal error" at boot up for sg
module. What is the sg module?  The reason I ask is that under RH 9, I
always got an error about sound.  My mother board does not have sound nor do
I have a sound card.  So I'm sure that's why I got the sound error under RH
9.

Is the sg module for sound?  If so, can I comment it out without affecting
the operation of the CDRW?

TIA

Modules question

[Michael Schwendt]

On Sat, 4 Sep 2004 08:29:48 -0400, Thomas E. Dukes wrote:
> About a year ago, I installed an ide CDRW.  I added the following lines to
> modules.conf:
>
> options ide-cd ignore=hdb
> pre-install sg     modprobe ide-scsi # load ide-scsi before sg
> pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
> pre-install ide-scsi modprobe ide-cd # load ide-cd   before ide-scsi
>
> Since upgrading from RH 9 to FC 2, I now get "fatal error" at boot up for sg
> module. What is the sg module?

SCSI generic
> The reason I ask is that under RH 9, I
> always got an error about sound.

Unrelated.
> My mother board does not have sound nor do
> I have a sound card.  So I'm sure that's why I got the sound error under RH
> 9.

What error? modprobe warnings in system log file can be ignored and
switched off via /etc/modprobe.conf
> Is the sg module for sound?  If so, can I comment it out without affecting
> the operation of the CDRW?

The ATAPI CD-ROM SCSI-emulation entries you've created are not needed in
Fedora Core 1 and in particular not needed in Fedora Core 2. FC1 uses
a kernel command-line parameter (hdb=ide-scsi) in /boot/grub/grub.conf,
and FC2 no longer uses SCSI-emulation for your CDRW.

Btw, your message appears as a reply to

Subject: RE: Rpmbuild question
  In-Reply-To:

because you replied to an existing thread. Please avoid that in the
future.

Modules question

[Paul Howarth]

On Sat, 2004-09-04 at 13:29, Thomas E. Dukes wrote:
> Hello,
>
> About a year ago, I installed an ide CDRW.  I added the following lines to
> modules.conf:
>
> options ide-cd ignore=hdb
> pre-install sg     modprobe ide-scsi # load ide-scsi before sg
> pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
> pre-install ide-scsi modprobe ide-cd # load ide-cd   before ide-scsi
>
> Since upgrading from RH 9 to FC 2, I now get "fatal error" at boot up for sg
> module. What is the sg module?  The reason I ask is that under RH 9, I
> always got an error about sound.  My mother board does not have sound nor do
> I have a sound card.  So I'm sure that's why I got the sound error under RH
> 9.
>
> Is the sg module for sound?  If so, can I comment it out without affecting
> the operation of the CDRW?

"sg" is "scsi generic", commonly used for things like scanners.

2.6 kernels, unlike 2.4 kernels, do not require ide-scsi to burn to
ATAPI CD writers. The 2.6 kernel also uses modprobe.conf rather than
modules.conf; you shouldn't need any of the lines above in your
modprobe.conf file.

Paul.

Modules question

[Thomas E Dukes]

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Paul Howarth
> Sent: Saturday, September 04, 2004 8:42 AM
> To: For users of Fedora Core releases
> Subject: Re: Modules question
>
> On Sat, 2004-09-04 at 13:29, Thomas E. Dukes wrote:
> > Hello,
> >
> > About a year ago, I installed an ide CDRW.  I added the following 
> > lines to
> > modules.conf:
> >
> > options ide-cd ignore=hdb
> > pre-install sg     modprobe ide-scsi # load ide-scsi before sg
> > pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
> > pre-install ide-scsi modprobe ide-cd # load ide-cd   before ide-scsi
> >
> > Since upgrading from RH 9 to FC 2, I now get "fatal error"
>
> at boot up
> > for sg module. What is the sg module?  The reason I ask is
>
> that under
> > RH 9, I always got an error about sound.  My mother board does not 
> > have sound nor do I have a sound card.  So I'm sure that's
>
> why I got
> > the sound error under RH 9.
> >
> > Is the sg module for sound?  If so, can I comment it out without 
> > affecting the operation of the CDRW?
>
> "sg" is "scsi generic", commonly used for things like scanners.
>
> 2.6 kernels, unlike 2.4 kernels, do not require ide-scsi to 
> burn to ATAPI CD writers. The 2.6 kernel also uses 
> modprobe.conf rather than modules.conf; you shouldn't need 
> any of the lines above in your modprobe.conf file.

Hi Paul,

Thanks.

So I don't need the modules.conf file at all?

In modprobe.conf they are a different.  I didn't add these, they were
already there.

options ide-cd ignore=hdb # tell the ide-cd module to ignore hdb
alias scd0 sr_mod
install ide-scsi { modprobe ide-cd # load ide-cd before ide-scsi; } ;
/sbin/modprobe --first-time --ignore-install ide-scsi
install sg { modprobe ide-scsi # load ide-scsi before sg; } ; /sbin/modprobe
--first-time --ignore-install sg
install sr_mod { modprobe ide-scsi # load ide-scsi before sr_mod; } ;
/sbin/modprobe --first-time --ignore-install sr_mod

So, these are OK to delete or comment out?

Thanks

Modules question

[Thomas E Dukes]

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Michael Schwendt
> Sent: Saturday, September 04, 2004 8:42 AM
> To: For users of Fedora Core releases
> Subject: Re: Modules question
>
> On Sat, 4 Sep 2004 08:29:48 -0400, Thomas E. Dukes wrote:
> > About a year ago, I installed an ide CDRW.  I added the following 
> > lines to
> > modules.conf:
> >
> > options ide-cd ignore=hdb
> > pre-install sg     modprobe ide-scsi # load ide-scsi before sg
> > pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
> > pre-install ide-scsi modprobe ide-cd # load ide-cd   before ide-scsi
> >
> > Since upgrading from RH 9 to FC 2, I now get "fatal error"
>
> at boot up
> > for sg module. What is the sg module?
>
> SCSI generic
> > The reason I ask is that under RH 9, I always got an error about 
> > sound.
>
> Unrelated.
> > My mother board does not have sound nor do I have a sound card.  So 
> > I'm sure that's why I got the sound error under RH 9.
>
> What error? modprobe warnings in system log file can be 
> ignored and switched off via /etc/modprobe.conf
> > Is the sg module for sound?  If so, can I comment it out without 
> > affecting the operation of the CDRW?
>
> The ATAPI CD-ROM SCSI-emulation entries you've created are 
> not needed in Fedora Core 1 and in particular not needed in 
> Fedora Core 2. FC1 uses a kernel command-line parameter 
> (hdb=ide-scsi) in /boot/grub/grub.conf, and FC2 no longer 
> uses SCSI-emulation for your CDRW.
>
> Btw, your message appears as a reply to
>
> Subject: RE: Rpmbuild question
>   In-Reply-To: 
>
> because you replied to an existing thread. Please avoid that 
> in the future.

Sorry, I was in need for the email address for the list.

Modules question

[Paul Howarth]

On Sat, 2004-09-04 at 13:58, Thomas E. Dukes wrote:
> So I don't need the modules.conf file at all?

I'd keep it around for now in case you need to boot into a 2.4 kernel
for some reason.
> In modprobe.conf they are a different.  I didn't add these, they were
> already there.

I think the FC2 installer probably just copied the modules.conf entries
across to the modprobe.conf file when you did the upgrade from RH9.
> options ide-cd ignore=hdb # tell the ide-cd module to ignore hdb
> alias scd0 sr_mod
> install ide-scsi { modprobe ide-cd # load ide-cd before ide-scsi; } ;
> /sbin/modprobe --first-time --ignore-install ide-scsi
> install sg { modprobe ide-scsi # load ide-scsi before sg; } ; /sbin/modprobe
> --first-time --ignore-install sg
> install sr_mod { modprobe ide-scsi # load ide-scsi before sr_mod; } ;
> /sbin/modprobe --first-time --ignore-install sr_mod
>
> So, these are OK to delete or comment out?

Try commenting them all out and see what happens.

Are there any other entries in your modprobe.conf file? They may be
responsible for the sound-related messages you got.

Paul.

Modules question

[Michael Schwendt]

On Sat, 4 Sep 2004 08:59:45 -0400, Thomas E. Dukes wrote:
> > Btw, your message appears as a reply to
> >
> > Subject: RE: Rpmbuild question
> >   In-Reply-To: 
> >
> > because you replied to an existing thread. Please avoid that 
> > in the future.
>
> Sorry, I was in need for the email address for the list.

Cut'n'paste it, or put it into your addressbook. Whether you believe it or
not, some subscribers won't see your message when it is a reply to an
arbitrary thread, because they collapse threads and don't expect new
topics to appear in threads they are not interested in. ;)

Modules question

[Thomas E Dukes]

> Try commenting them all out and see what happens.
>
> Are there any other entries in your modprobe.conf file? They 
> may be responsible for the sound-related messages you got.

Here's the full modprobe.conf:

# Note: for use under 2.4, changes must also be made to modules.conf!
alias parport_lowlevel parport_pc
alias eth0 tulip
alias usb-controller uhci-hcd
options 3c509 irq=10
options ide-cd ignore=hdb # tell the ide-cd module to ignore hdb
alias scd0 sr_mod
install char-major-97 /bin/true
install ide-scsi { modprobe ide-cd # load ide-cd before ide-scsi; } ;
/sbin/modprobe --first-time --ignore-install ide-scsi
install sg { modprobe ide-scsi # load ide-scsi before sg; } ; /sbin/modprobe
--first-time --ignore-install sg
install sr_mod { modprobe ide-scsi # load ide-scsi before sr_mod; } ;
/sbin/modprobe --first-time --ignore-install sr_mod

The error in RH 9 was only seen when it shutting down.  Something about
modprobe sound mixer as far as I can remember.  I haven't seen it in FC 2.
Just thought the two, sg and sound, might be related.

Modules question

[Thomas E Dukes]

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Thomas E. Dukes
> Sent: Saturday, September 04, 2004 9:40 AM
> To: 'For users of Fedora Core releases'
> Subject: RE: Modules question
> > Try commenting them all out and see what happens.
> >
> > Are there any other entries in your modprobe.conf file? They may be 
> > responsible for the sound-related messages you got.
>
> Here's the full modprobe.conf:
>
> # Note: for use under 2.4, changes must also be made to modules.conf!
> alias parport_lowlevel parport_pc
> alias eth0 tulip
> alias usb-controller uhci-hcd
> options 3c509 irq=10
> options ide-cd ignore=hdb # tell the ide-cd module to ignore 
> hdb alias scd0 sr_mod install char-major-97 /bin/true install 
> ide-scsi { modprobe ide-cd # load ide-cd before ide-scsi; } ; 
> /sbin/modprobe --first-time --ignore-install ide-scsi install 
> sg { modprobe ide-scsi # load ide-scsi before sg; } ; 
> /sbin/modprobe --first-time --ignore-install sg install 
> sr_mod { modprobe ide-scsi # load ide-scsi before sr_mod; } ; 
> /sbin/modprobe --first-time --ignore-install sr_mod
>
> The error in RH 9 was only seen when it shutting down.  
> Something about modprobe sound mixer as far as I can 
> remember.  I haven't seen it in FC 2.
> Just thought the two, sg and sound, might be related.

OK, I commented the lines out and that took care of the "fatal error" at
boot up.

I don't know if you can help me with this one but what stirred this thread
is I use mondorecuse for backing up my system.

Its been about 2 weeks since I upgrade from RH 9 to FC 2 and I have decided
to stay with FC 2.

I am trying to perform a full backup but mondo is reporting that there is a
kernel 2.6 ide-scsi module broken.  I just re-started the backup and got the
same error after commenting the lines out in modprobe.conf.

Do I have a symlink broken somewhere.  I can re-install the "package" if I
knew which one contained the ide-scsi modules.  Any idea?

Thanks!!

Modules question

[Mike Burger]

On Sat, 4 Sep 2004, Michael Schwendt wrote:
> On Sat, 4 Sep 2004 08:29:48 -0400, Thomas E. Dukes wrote:
>
> The ATAPI CD-ROM SCSI-emulation entries you've created are not needed in
> Fedora Core 1 and in particular not needed in Fedora Core 2. FC1 uses
> a kernel command-line parameter (hdb=ide-scsi) in /boot/grub/grub.conf,
> and FC2 no longer uses SCSI-emulation for your CDRW.

FWIW, it can (and does, if configured so), and if you're using X-CD-Roast 
to burn CDs, it's still the preferred method.

Modules question

[Paul Howarth]

On Sat, 2004-09-04 at 14:54, Thomas E. Dukes wrote:
> OK, I commented the lines out and that took care of the "fatal error" at
> boot up.
>
> I don't know if you can help me with this one but what stirred this thread
> is I use mondorecuse for backing up my system.
>
> Its been about 2 weeks since I upgrade from RH 9 to FC 2 and I have decided
> to stay with FC 2.
>
> I am trying to perform a full backup but mondo is reporting that there is a
> kernel 2.6 ide-scsi module broken.  I just re-started the backup and got the
> same error after commenting the lines out in modprobe.conf.

Might be worth asking over at http://forum.mondorescue.org/
> Do I have a symlink broken somewhere.  I can re-install the "package" if I
> knew which one contained the ide-scsi modules.  Any idea?

Kernel modules are part of the RPM for the associated kernel.

$ rpm -qf /lib/modules/2.6.8-1.521/kernel/drivers/scsi/ide-scsi.ko
kernel-2.6.8-1.521

Paul.

Modules question

[Thomas E Dukes]

> Might be worth asking over at http://forum.mondorescue.org/
> > Do I have a symlink broken somewhere.  I can re-install the
>
> "package"
> > if I knew which one contained the ide-scsi modules.  Any idea?
>
> Kernel modules are part of the RPM for the associated kernel.
>
> $ rpm -qf /lib/modules/2.6.8-1.521/kernel/drivers/scsi/ide-scsi.ko
> kernel-2.6.8-1.521

Hi Paul,

I subscribe to that list too.  I posted earlier but I haven't gotten a
reply.  Actually, I have only seen my post.  Must not be a lot of traffic on
it today.  I'll try the forum.

Thanks!!

Modules question

[Thomas E Dukes]

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Paul Howarth
> Sent: Saturday, September 04, 2004 9:14 AM
> To: For users of Fedora Core releases
> Subject: RE: Modules question
>
> On Sat, 2004-09-04 at 13:58, Thomas E. Dukes wrote:
> > So I don't need the modules.conf file at all?
>
> I'd keep it around for now in case you need to boot into a 
> 2.4 kernel for some reason.

Apparently the 2.6 kernel has problems with the ide-scsi module.  What/how
can I install a 2.4 kernel?  Can I / Should I use a FC 1 2.4 kernel or can I
go back to the latest RH 9 kernel.  I don't want to wipe out the 2.6 but I
am having problems backing up my system.

What would be the best way to do this?  Can I do this?

TIA

Modules question

[Jeff Vian]

On Sat, 2004-09-04 at 07:29, Thomas E. Dukes wrote:
> Hello,
>
> About a year ago, I installed an ide CDRW.  I added the following lines to
> modules.conf:
>
> options ide-cd ignore=hdb
> pre-install sg     modprobe ide-scsi # load ide-scsi before sg
> pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
> pre-install ide-scsi modprobe ide-cd # load ide-cd   before ide-scsi

modprobe ide-scsi handles all that in the  proper sequence.
> Since upgrading from RH 9 to FC 2, I now get "fatal error" at boot up for sg
> module. What is the sg module?  The reason I ask is that under RH 9, I
> always got an error about sound.  My mother board does not have sound nor do
> I have a sound card.  So I'm sure that's why I got the sound error under RH
> 9.
>
> Is the sg module for sound?  If so, can I comment it out without affecting
> the operation of the CDRW?

The sg module is the raw scsi device.

the module ide-scsi is not needed nor recommended for use with FC2.  The
2.6 kernel is able to use the ATAPI device for cd burning.

Modules question

[Tom Mitchell]

On Sat, Sep 04, 2004 at 08:29:48AM -0400, Thomas E. Dukes wrote:
>
> About a year ago, I installed an ide CDRW.  I added the following
> lines to modules.conf:
> options ide-cd ignore=hdb
> pre-install sg     modprobe ide-scsi # load ide-scsi before sg
> pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
> pre-install ide-scsi modprobe ide-cd # load ide-cd   before ide-scsi
> Since upgrading from RH 9 to FC 2, I now get "fatal error" at boot

Two key changes RH9 to FC2 may apply here.

First the older SCSI emulation layer that has been required by IDE CDROM
burner software and other devices is no longer separate.

Another is that  /etc/modules.conf has been replaced by 
/etc/modprobe.conf (when the 2.6 kernels arrived).

A onetime conversion would have been done by a conversion script that
does not seem to get things like this and USB right.

Of interest the SCSI command set design is rich enough that it is used
by a lot of devices that are connected by physical layers that are not
SCSI.  This command set .vs. physical layer thing might cause some
people confusion.

As other replied to this thread just comment out and later delete  those
"sc and scsi" lines as they are probably unnecessary.

Any major kernel update could rename, discard, reorganize, replace
merge or extract functionality... as you have found.