RE: CDROM Boot Hangs But Only Under 6.x

2007-12-28 Thread Ted Mittelstaedt


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Tim Daneliuk
 Sent: Tuesday, December 25, 2007 11:15 PM
 To: FreeBSD Mailing List
 Subject: Re: CDROM Boot Hangs But Only Under 6.x


 Ted Mittelstaedt wrote:
 SNIP


 
  If your MB is new it should work.  Older MB's have problems with
  the new way to boot off an optical cd.  You can try BIOS/CMOS
  updates from the motherbard mfg if they are available.  Sometimes
  even back-flashing to older BIOS fixes it.

 This is a brand new ABIT mobo w/latest bios on board.

 
  3) Reordering/removing memory sticks made no difference.  I am running
  a memory test ATM just to be sure, but so far, the memory
 seems fine.
 
  4) No amount of poking around in the BIOS settings seems to
 help either.
 
  I am starting to suspect the MOBO.  If I stick a couple of cards in the
  two available PCI slots, the system has trouble taking me into the BIOS
  screen.  I have to remove the cards to reliably get into the BIOS
  settings menu.  I wonder if this is one of those situations where there
  are not enough IRQs to go around.
 
 
  If it's a new MB the PCI cards are probably too old/slow to work right.

 I thought that even modern PCI busses would fall back to the old
 speeds.  I've had not trouble with any of my other rather new
 mobos, running, say, old Adaptec controllers.

 
  Another thing to check is if the MB has any overclock settings turned
  on, these will screw up booting, going into BIOS, and some PCI cards.
  Go to BIOS and select reset to factory settings which turns off all
  the go-fast stuff.  And make sure you confirm the CPU speed in BIOS
  with the actual speed stamped on the CPU.

 I've reset the BIOS to the most conservative mode, no overclocking, etc.

 
  Sometimes you just got to stick a floppy disk drive on the thing and
  boot from the 4 boot floppies then do an FTP install.  I have about
  a dozen servers among the collection I manage that are like this -
  some are even newer ones.

 I would *love* to know just where boot is getting lost.  In the case
 of your servers, do you see the same symptoms I am seeing: The
 kernel loading progress prompt gets painted (most of the time,
 sometimes it does not even make it that far) and the booting
 seizes up?


No, they won't even load the boot loader.  The symptoms your describing
are classic for PIO/UDMA negotiation issues.  In other words, the
connection from the atapi controller to the optical drive is being
negotiated by BIOS as UDMA and negotiated by the FreeBSD boot kernel
as UDMA but a bug somewhere is causing the bus to corrupt data.  The
usual fix is to switch to PIO mode.  The only problem with this
is that you have already swapped optical drives, and I'd assume that
at least one of the swaps didn't support UDMA mode (thus forcing
PIO mode) you also said you already checked this, and even if it did
negotiate UDMA it would be UDMA33 not anything faster that would require
the special high speed IDE cables so we can probably rule out a
crap CDROM cable.  Lastly, the default on the ata driver is supposed
to be PIO mode anyway for optical drives.

Ted

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: CDROM Boot Hangs But Only Under 6.x

2007-12-28 Thread Ted Mittelstaedt


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Tim Daneliuk
 Sent: Wednesday, December 26, 2007 1:07 PM
 To: FreeBSD Mailing List
 Subject: Re: CDROM Boot Hangs But Only Under 6.x
 
 
 This was a brand new Abit LG-95Z mobo.  The solution was to return it
 and get an Intel mobo instead.  Problem fixed.

Thanks for letting us know this was a problem board.  I would strongly
request you let Abit know what happened as well.  It is only through
feedback like this that motherboard manufacturers will actually test
their stuff under FreeBSD.

Ted
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-27 Thread David M. Patronis




Not in this case.  As I mentioned in a prior post, I tried booting
with the 7.0-BETA4 ISO and got the exact same results.

Response:

Yes, sorry about that; was in too much of a hurry and missed the later 
posts.


David





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-27 Thread Tim Kellers
I have 18 brand new Gateway towers at work (I can supply the model 
numbers after school restarts next week).  I wanted to clone them using 
dd and an external usb hard drive.  I couldn't boot 6.x or 7.x  CDs on 
any of the boxes, but I was able to install 7 (I didn't try 6.x) on a 
usb stick, set the BIOS to boot from the device and run FreeBSD (and dd) 
from there.


These machines have CDRW/DVDR drives installed.  I've had no problem 
running any content based media from them at all, but I haven't tried 
booting any other media (like WinXP) from them, either.


Tim

David M. Patronis wrote:




Not in this case.  As I mentioned in a prior post, I tried booting
with the 7.0-BETA4 ISO and got the exact same results.

Response:

Yes, sorry about that; was in too much of a hurry and missed the later 
posts.


David





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
[EMAIL PROTECTED]





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-26 Thread NetOpsCenter

[EMAIL PROTECTED] wrote:

On 25/12/2007, Tim Daneliuk [EMAIL PROTECTED] wrote:
  

I am building a new server out of both older and brand new
components.  It is based on a Pentium D 925 and ABIT LG-95Z
mobo.  The DVD-RW is a Lite-On about a year old with very
low hours on it.

So ... here's a fun one:  I can boot and install FreeBSD 4.x (CD)
or Novell SUSE Enterprise Linux Desktop 10 SP1 (DVD) via the
DVD.  But attempting to do this with 6.x (I have tried 6.2R and
6.3-PRE disk #1) causes a hang during boot.  The loader gets
as far as showing the vertical bar that ordinarily spins
to show intitial kernel loading progress and the the machine
just sits there.  There is some further activity on the optical
drive at this point and then the cursor sort of jumps around a bit.

I've not yet tried swapping the optical drive out - though I doubt
this is the problem since I can load the other OSs.  I've tried
removing and moving memory sticks in case this is a flakey
memory problem - no change.  I've tried removing the only
two cards in the machine: 3COM 905C-TX and an Adaptec 2940UW -
no change.

I have one last ditch thing I will try later tonight which is
to force the DVD IDE port into PIO mode and out of DMA mode.
But that's it.  I am stumped.  Ideas anyone?




If it is not hardware, check your bios settings (and mayhap
set back to default or very conservative) (of which the PIO
trick may work).

Also, 7.0 ran extremely well for me back in Sept., you might
try it as an alternative.

HTH

  

Aloha,

I had the same problem with a couple of older mobo's . I ended up 
loading 6.* on a hd on a different machine that I knew worked. I 
physically moved it to the problem box and it Worked.


I think the issue could be the size or the type of HD in my case. Some 
older mobo bios jam up when a HD is more than 60 gig I have found.



~Al Plant - Honolulu, Hawaii -  Phone:  808-284-2740
 + http://hawaiidakine.com + http://freebsdinfo.org + [EMAIL PROTECTED] +
 + http://aloha50.net   - Supporting - FreeBSD 6.* - 7.* +
All that's really worth doing is what we do for others.- Lewis Carrol


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-26 Thread Tim Daneliuk

NetOpsCenter wrote:

[EMAIL PROTECTED] wrote:

On 25/12/2007, Tim Daneliuk [EMAIL PROTECTED] wrote:
 

I am building a new server out of both older and brand new
components.  It is based on a Pentium D 925 and ABIT LG-95Z
mobo.  The DVD-RW is a Lite-On about a year old with very
low hours on it.

So ... here's a fun one:  I can boot and install FreeBSD 4.x (CD)
or Novell SUSE Enterprise Linux Desktop 10 SP1 (DVD) via the
DVD.  But attempting to do this with 6.x (I have tried 6.2R and
6.3-PRE disk #1) causes a hang during boot.  The loader gets
as far as showing the vertical bar that ordinarily spins
to show intitial kernel loading progress and the the machine
just sits there.  There is some further activity on the optical
drive at this point and then the cursor sort of jumps around a bit.

I've not yet tried swapping the optical drive out - though I doubt
this is the problem since I can load the other OSs.  I've tried
removing and moving memory sticks in case this is a flakey
memory problem - no change.  I've tried removing the only
two cards in the machine: 3COM 905C-TX and an Adaptec 2940UW -
no change.

I have one last ditch thing I will try later tonight which is
to force the DVD IDE port into PIO mode and out of DMA mode.
But that's it.  I am stumped.  Ideas anyone?




If it is not hardware, check your bios settings (and mayhap
set back to default or very conservative) (of which the PIO
trick may work).

Also, 7.0 ran extremely well for me back in Sept., you might
try it as an alternative.

HTH

  

Aloha,

I had the same problem with a couple of older mobo's . I ended up 
loading 6.* on a hd on a different machine that I knew worked. I 
physically moved it to the problem box and it Worked.


I think the issue could be the size or the type of HD in my case. Some 
older mobo bios jam up when a HD is more than 60 gig I have found.



~Al Plant - Honolulu, Hawaii -  Phone:  808-284-2740
 + http://hawaiidakine.com + http://freebsdinfo.org + [EMAIL PROTECTED] +
 + http://aloha50.net   - Supporting - FreeBSD 6.* - 7.* +
All that's really worth doing is what we do for others.- Lewis Carrol



This was a brand new Abit LG-95Z mobo.  The solution was to return it
and get an Intel mobo instead.  Problem fixed.
--

Tim Daneliuk [EMAIL PROTECTED]
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-26 Thread Tim Daneliuk

David M. Patronis wrote:

Tim Daneliuk wrote:

[EMAIL PROTECTED] wrote:

On 25/12/2007, Tim Daneliuk [EMAIL PROTECTED] wrote:

I am building a new server out of both older and brand new
components.  It is based on a Pentium D 925 and ABIT LG-95Z
mobo.  The DVD-RW is a Lite-On about a year old with very
low hours on it.

So ... here's a fun one:  I can boot and install FreeBSD 4.x (CD)
or Novell SUSE Enterprise Linux Desktop 10 SP1 (DVD) via the
DVD.  But attempting to do this with 6.x (I have tried 6.2R and
6.3-PRE disk #1) causes a hang during boot.  The loader gets
as far as showing the vertical bar that ordinarily spins
to show intitial kernel loading progress and the the machine
just sits there.  There is some further activity on the optical
drive at this point and then the cursor sort of jumps around a bit.

I've not yet tried swapping the optical drive out - though I doubt
this is the problem since I can load the other OSs.  I've tried
removing and moving memory sticks in case this is a flakey
memory problem - no change.  I've tried removing the only
two cards in the machine: 3COM 905C-TX and an Adaptec 2940UW -
no change.

I have one last ditch thing I will try later tonight which is
to force the DVD IDE port into PIO mode and out of DMA mode.
But that's it.  I am stumped.  Ideas anyone?



If it is not hardware, check your bios settings (and mayhap
set back to default or very conservative) (of which the PIO
trick may work).




I just swapped out the optical drive with a CD-RW - exact same
symptoms.  Fiddling w/BIOS, seems to make no difference, though
I am still poking at it.  I am utterly lost - never seen
very standard hardware like this that FreeBSD could/would not
boot and run on ...

Response:

Its probably an issue with the 6X series. I have experienced something 
similar and just spoke to someone via this list with a similar problem. 
In all cases thus far we were able to install using the 7X series.


David


Not in this case.  As I mentioned in a prior post, I tried booting
with the 7.0-BETA4 ISO and got the exact same results.


--

Tim Daneliuk [EMAIL PROTECTED]
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-26 Thread David M. Patronis

Tim Daneliuk wrote:

[EMAIL PROTECTED] wrote:

On 25/12/2007, Tim Daneliuk [EMAIL PROTECTED] wrote:

I am building a new server out of both older and brand new
components.  It is based on a Pentium D 925 and ABIT LG-95Z
mobo.  The DVD-RW is a Lite-On about a year old with very
low hours on it.

So ... here's a fun one:  I can boot and install FreeBSD 4.x (CD)
or Novell SUSE Enterprise Linux Desktop 10 SP1 (DVD) via the
DVD.  But attempting to do this with 6.x (I have tried 6.2R and
6.3-PRE disk #1) causes a hang during boot.  The loader gets
as far as showing the vertical bar that ordinarily spins
to show intitial kernel loading progress and the the machine
just sits there.  There is some further activity on the optical
drive at this point and then the cursor sort of jumps around a bit.

I've not yet tried swapping the optical drive out - though I doubt
this is the problem since I can load the other OSs.  I've tried
removing and moving memory sticks in case this is a flakey
memory problem - no change.  I've tried removing the only
two cards in the machine: 3COM 905C-TX and an Adaptec 2940UW -
no change.

I have one last ditch thing I will try later tonight which is
to force the DVD IDE port into PIO mode and out of DMA mode.
But that's it.  I am stumped.  Ideas anyone?



If it is not hardware, check your bios settings (and mayhap
set back to default or very conservative) (of which the PIO
trick may work).




I just swapped out the optical drive with a CD-RW - exact same
symptoms.  Fiddling w/BIOS, seems to make no difference, though
I am still poking at it.  I am utterly lost - never seen
very standard hardware like this that FreeBSD could/would not
boot and run on ...

Response:

Its probably an issue with the 6X series. I have experienced something 
similar and just spoke to someone via this list with a similar problem. 
In all cases thus far we were able to install using the 7X series.


David







___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-25 Thread [EMAIL PROTECTED]
On 25/12/2007, Tim Daneliuk [EMAIL PROTECTED] wrote:
 I am building a new server out of both older and brand new
 components.  It is based on a Pentium D 925 and ABIT LG-95Z
 mobo.  The DVD-RW is a Lite-On about a year old with very
 low hours on it.

 So ... here's a fun one:  I can boot and install FreeBSD 4.x (CD)
 or Novell SUSE Enterprise Linux Desktop 10 SP1 (DVD) via the
 DVD.  But attempting to do this with 6.x (I have tried 6.2R and
 6.3-PRE disk #1) causes a hang during boot.  The loader gets
 as far as showing the vertical bar that ordinarily spins
 to show intitial kernel loading progress and the the machine
 just sits there.  There is some further activity on the optical
 drive at this point and then the cursor sort of jumps around a bit.

 I've not yet tried swapping the optical drive out - though I doubt
 this is the problem since I can load the other OSs.  I've tried
 removing and moving memory sticks in case this is a flakey
 memory problem - no change.  I've tried removing the only
 two cards in the machine: 3COM 905C-TX and an Adaptec 2940UW -
 no change.

 I have one last ditch thing I will try later tonight which is
 to force the DVD IDE port into PIO mode and out of DMA mode.
 But that's it.  I am stumped.  Ideas anyone?


If it is not hardware, check your bios settings (and mayhap
set back to default or very conservative) (of which the PIO
trick may work).

Also, 7.0 ran extremely well for me back in Sept., you might
try it as an alternative.

HTH

-- 
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-25 Thread Tim Daneliuk

[EMAIL PROTECTED] wrote:

On 25/12/2007, Tim Daneliuk [EMAIL PROTECTED] wrote:

I am building a new server out of both older and brand new
components.  It is based on a Pentium D 925 and ABIT LG-95Z
mobo.  The DVD-RW is a Lite-On about a year old with very
low hours on it.

So ... here's a fun one:  I can boot and install FreeBSD 4.x (CD)
or Novell SUSE Enterprise Linux Desktop 10 SP1 (DVD) via the
DVD.  But attempting to do this with 6.x (I have tried 6.2R and
6.3-PRE disk #1) causes a hang during boot.  The loader gets
as far as showing the vertical bar that ordinarily spins
to show intitial kernel loading progress and the the machine
just sits there.  There is some further activity on the optical
drive at this point and then the cursor sort of jumps around a bit.

I've not yet tried swapping the optical drive out - though I doubt
this is the problem since I can load the other OSs.  I've tried
removing and moving memory sticks in case this is a flakey
memory problem - no change.  I've tried removing the only
two cards in the machine: 3COM 905C-TX and an Adaptec 2940UW -
no change.

I have one last ditch thing I will try later tonight which is
to force the DVD IDE port into PIO mode and out of DMA mode.
But that's it.  I am stumped.  Ideas anyone?



If it is not hardware, check your bios settings (and mayhap
set back to default or very conservative) (of which the PIO
trick may work).




I just swapped out the optical drive with a CD-RW - exact same
symptoms.  Fiddling w/BIOS, seems to make no difference, though
I am still poking at it.  I am utterly lost - never seen
very standard hardware like this that FreeBSD could/would not
boot and run on ...



--

Tim Daneliuk [EMAIL PROTECTED]
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-25 Thread Tim Daneliuk

[EMAIL PROTECTED] wrote:

On 25/12/2007, Tim Daneliuk [EMAIL PROTECTED] wrote:

I am building a new server out of both older and brand new
components.  It is based on a Pentium D 925 and ABIT LG-95Z
mobo.  The DVD-RW is a Lite-On about a year old with very
low hours on it.

So ... here's a fun one:  I can boot and install FreeBSD 4.x (CD)
or Novell SUSE Enterprise Linux Desktop 10 SP1 (DVD) via the
DVD.  But attempting to do this with 6.x (I have tried 6.2R and
6.3-PRE disk #1) causes a hang during boot.  The loader gets
as far as showing the vertical bar that ordinarily spins
to show intitial kernel loading progress and the the machine
just sits there.  There is some further activity on the optical
drive at this point and then the cursor sort of jumps around a bit.

I've not yet tried swapping the optical drive out - though I doubt
this is the problem since I can load the other OSs.  I've tried
removing and moving memory sticks in case this is a flakey
memory problem - no change.  I've tried removing the only
two cards in the machine: 3COM 905C-TX and an Adaptec 2940UW -
no change.

I have one last ditch thing I will try later tonight which is
to force the DVD IDE port into PIO mode and out of DMA mode.
But that's it.  I am stumped.  Ideas anyone?



If it is not hardware, check your bios settings (and mayhap
set back to default or very conservative) (of which the PIO
trick may work).


Well ... no amount of BIOS fiddling fixes this problem.



Also, 7.0 ran extremely well for me back in Sept., you might
try it as an alternative.



I downloaded 7.0-BETA4 and burned the CD - This exhibits the
exact same boot time behavior as the earlier 6.x releases.

In summary:

1) I can boot 4.x or Linux install CDs.   I cannot boot 6.x or 7.x
   install CD - system hangs at the beginning of loading the kernel
   and the video cursor starts jumping around - presumably because
   the program has lost its way.  (I am assuming that the program
   having trouble is the loader itself, since the kernel is not yet
   loaded at this point.)

2) Changing optical drives made no difference.

3) Reordering/removing memory sticks made no difference.  I am running
   a memory test ATM just to be sure, but so far, the memory seems fine.

4) No amount of poking around in the BIOS settings seems to help either.

I am starting to suspect the MOBO.  If I stick a couple of cards in the
two available PCI slots, the system has trouble taking me into the BIOS
screen.  I have to remove the cards to reliably get into the BIOS
settings menu.  I wonder if this is one of those situations where there
are not enough IRQs to go around.

I remain confused ...

--

Tim Daneliuk [EMAIL PROTECTED]
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: CDROM Boot Hangs But Only Under 6.x

2007-12-25 Thread Ted Mittelstaedt


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Tim Daneliuk
 Sent: Tuesday, December 25, 2007 10:53 PM
 To: FreeBSD Mailing List
 Subject: Re: CDROM Boot Hangs But Only Under 6.x
 
 
 [EMAIL PROTECTED] wrote:
  On 25/12/2007, Tim Daneliuk [EMAIL PROTECTED] wrote:
  I am building a new server out of both older and brand new
  components.  It is based on a Pentium D 925 and ABIT LG-95Z
  mobo.  The DVD-RW is a Lite-On about a year old with very
  low hours on it.
 
  So ... here's a fun one:  I can boot and install FreeBSD 4.x (CD)
  or Novell SUSE Enterprise Linux Desktop 10 SP1 (DVD) via the
  DVD.  But attempting to do this with 6.x (I have tried 6.2R and
  6.3-PRE disk #1) causes a hang during boot.  The loader gets
  as far as showing the vertical bar that ordinarily spins
  to show intitial kernel loading progress and the the machine
  just sits there.  There is some further activity on the optical
  drive at this point and then the cursor sort of jumps around a bit.
 
  I've not yet tried swapping the optical drive out - though I doubt
  this is the problem since I can load the other OSs.  I've tried
  removing and moving memory sticks in case this is a flakey
  memory problem - no change.  I've tried removing the only
  two cards in the machine: 3COM 905C-TX and an Adaptec 2940UW -
  no change.
 
  I have one last ditch thing I will try later tonight which is
  to force the DVD IDE port into PIO mode and out of DMA mode.
  But that's it.  I am stumped.  Ideas anyone?
 
  
  If it is not hardware, check your bios settings (and mayhap
  set back to default or very conservative) (of which the PIO
  trick may work).
 
 Well ... no amount of BIOS fiddling fixes this problem.
 
  
  Also, 7.0 ran extremely well for me back in Sept., you might
  try it as an alternative.
  
 
 I downloaded 7.0-BETA4 and burned the CD - This exhibits the
 exact same boot time behavior as the earlier 6.x releases.
 
 In summary:
 
 1) I can boot 4.x or Linux install CDs.   I cannot boot 6.x or 7.x
 install CD - system hangs at the beginning of loading the kernel
 and the video cursor starts jumping around - presumably because
 the program has lost its way.  (I am assuming that the program
 having trouble is the loader itself, since the kernel is not yet
 loaded at this point.)
 
 2) Changing optical drives made no difference.
 

The boot was changed from 4.x to the later series.  I think it was
changed from floppy emulation boot to cd boot or some such
nonsense.  You can get more info by reading up in the handbook
where it talks about how to create a distribution CD.  One of the
options on the cdburn controls this.

If your MB is new it should work.  Older MB's have problems with
the new way to boot off an optical cd.  You can try BIOS/CMOS
updates from the motherbard mfg if they are available.  Sometimes
even back-flashing to older BIOS fixes it.

 3) Reordering/removing memory sticks made no difference.  I am running
 a memory test ATM just to be sure, but so far, the memory seems fine.
 
 4) No amount of poking around in the BIOS settings seems to help either.
 
 I am starting to suspect the MOBO.  If I stick a couple of cards in the
 two available PCI slots, the system has trouble taking me into the BIOS
 screen.  I have to remove the cards to reliably get into the BIOS
 settings menu.  I wonder if this is one of those situations where there
 are not enough IRQs to go around.
 

If it's a new MB the PCI cards are probably too old/slow to work right.

Another thing to check is if the MB has any overclock settings turned
on, these will screw up booting, going into BIOS, and some PCI cards.
Go to BIOS and select reset to factory settings which turns off all
the go-fast stuff.  And make sure you confirm the CPU speed in BIOS
with the actual speed stamped on the CPU.

Sometimes you just got to stick a floppy disk drive on the thing and
boot from the 4 boot floppies then do an FTP install.  I have about
a dozen servers among the collection I manage that are like this - 
some are even newer ones.

Ted
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Boot Hangs But Only Under 6.x

2007-12-25 Thread Tim Daneliuk

Ted Mittelstaedt wrote:
SNIP




If your MB is new it should work.  Older MB's have problems with
the new way to boot off an optical cd.  You can try BIOS/CMOS
updates from the motherbard mfg if they are available.  Sometimes
even back-flashing to older BIOS fixes it.


This is a brand new ABIT mobo w/latest bios on board.




3) Reordering/removing memory sticks made no difference.  I am running
a memory test ATM just to be sure, but so far, the memory seems fine.

4) No amount of poking around in the BIOS settings seems to help either.

I am starting to suspect the MOBO.  If I stick a couple of cards in the
two available PCI slots, the system has trouble taking me into the BIOS
screen.  I have to remove the cards to reliably get into the BIOS
settings menu.  I wonder if this is one of those situations where there
are not enough IRQs to go around.



If it's a new MB the PCI cards are probably too old/slow to work right.


I thought that even modern PCI busses would fall back to the old
speeds.  I've had not trouble with any of my other rather new
mobos, running, say, old Adaptec controllers.



Another thing to check is if the MB has any overclock settings turned
on, these will screw up booting, going into BIOS, and some PCI cards.
Go to BIOS and select reset to factory settings which turns off all
the go-fast stuff.  And make sure you confirm the CPU speed in BIOS
with the actual speed stamped on the CPU.


I've reset the BIOS to the most conservative mode, no overclocking, etc.



Sometimes you just got to stick a floppy disk drive on the thing and
boot from the 4 boot floppies then do an FTP install.  I have about
a dozen servers among the collection I manage that are like this - 
some are even newer ones.


I would *love* to know just where boot is getting lost.  In the case
of your servers, do you see the same symptoms I am seeing: The
kernel loading progress prompt gets painted (most of the time,
sometimes it does not even make it that far) and the booting
seizes up?

Thanks for your time,

Tim Daneliuk [EMAIL PROTECTED]
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM

2006-07-16 Thread [EMAIL PROTECTED]
On Fri, Jul 14, 2006 06:40 AM, Ivan Levchenko  wrote:
 Hello,

 Could you show the results of:

 dmesg | grep acd
 and
 ls -l /dev/ | grep acd

Here they are:
0-$ dmesg | grep acd
acd0: CD-RW 10X8X32 at ata1-master using PIO4
acd1: CDROM ATAPI CD-ROM DRIVE 40X MAXIMUM at ata1-slave using PIO4
0-$ ls -l /dev/ | grep acd
crw-r-   2 root  operator  117,   0 Jun 12  2001 acd0a
crw-r-   2 root  operator  117,   2 Jun 12  2001 acd0c
crw-r-   2 root  operator  117,   8 Jun 12  2001 acd1a
crw-r-   2 root  operator  117,  10 Jun 12  2001 acd1c
crw-r-   2 root  operator  117,   0 Jun 12  2001 racd0a
crw-r-   2 root  operator  117,   2 Jun 12  2001 racd0c
crw-r-   2 root  operator  117,   8 Jun 12  2001 racd1a
crw-r-   2 root  operator  117,  10 Jun 12  2001 racd1c
0-$ 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM

2006-07-14 Thread [EMAIL PROTECTED]
Here is my latest try on it (where I dropped the 'a' at the end of
'acd0a'):
# mount -t cd9660  /dev/acd0  /cdrom 
cd9660: /dev/acd0: No such file or directory
#

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM

2006-07-14 Thread Ivan Levchenko

Hello,

Could you show the results of:

dmesg | grep acd
and
ls -l /dev/ | grep acd

On 7/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Here is my latest try on it (where I dropped the 'a' at the end of
'acd0a'):
# mount -t cd9660  /dev/acd0  /cdrom
cd9660: /dev/acd0: No such file or directory
#



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM

2006-07-13 Thread Ivan Levchenko

Hello,

Try just mount -t cd9660  /dev/acd0 /cdrom
(without the a)

On 7/12/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

On  Mon, Jul 10, 2006 07:48 PM, Bill Moran  wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

  I can read from my  CDROM  under  Windows 98 , but when I try
 to read from it under  FreeBSD 4.3  I get told that the device is
 busy.  My presumption is that either part of the device driver is
 corrupted, or there is some status data kept long time that is never
 reset but it tells the system that the device is busy.
snip
 You can start by describing _exactly_ what you are doing and the
 _exact_ results.

Here it is (first I show you what was mounted, then the  mount  command):
0-# mount
/dev/ad0s4a on / (ufs, local)
/dev/ad0s4g on /mp1 (ufs, local)
/dev/ad0s4h on /mp2 (ufs, local)
/dev/ad0s4e on /usr (ufs, local)
/dev/ad0s4f on /var (ufs, local)
procfs on /proc (procfs, local)
/dev/fd0 on /a (msdos, local)
0-# mount -t cd9660  /dev/acd0a  /cdrom
cd9660: /dev/acd0a: Device busy


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM

2006-07-12 Thread [EMAIL PROTECTED]
On  Mon, Jul 10, 2006 07:48 PM, Bill Moran  wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

  I can read from my  CDROM  under  Windows 98 , but when I try 
 to read from it under  FreeBSD 4.3  I get told that the device is 
 busy.  My presumption is that either part of the device driver is 
 corrupted, or there is some status data kept long time that is never 
 reset but it tells the system that the device is busy.
snip
 You can start by describing _exactly_ what you are doing and the 
 _exact_ results.

Here it is (first I show you what was mounted, then the  mount  command):
0-# mount
/dev/ad0s4a on / (ufs, local)
/dev/ad0s4g on /mp1 (ufs, local)
/dev/ad0s4h on /mp2 (ufs, local)
/dev/ad0s4e on /usr (ufs, local)
/dev/ad0s4f on /var (ufs, local)
procfs on /proc (procfs, local)
/dev/fd0 on /a (msdos, local)
0-# mount -t cd9660  /dev/acd0a  /cdrom  
cd9660: /dev/acd0a: Device busy


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM

2006-07-10 Thread Bill Moran
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

   I can read from my  CDROM  under  Windows 98 , but when I try 
 to read from it under  FreeBSD 4.3  I get told that the device is busy.
 My presumption is that either part of the device driver is corrupted, 
 or there is some status data kept long time that is never reset but it 
 tells the system that the device is busy.
   What can I do to resolve the difficulty?  If I need a new copy 
 of the device driver, where can I get it (do I need to know the type of
  CDROM  that I have, I believe it is  ATAPI )?

You can start by describing _exactly_ what you are doing and the _exact_
results.

Cut and paste of a session demonstrating the problem would be good.

-- 
Bill Moran

Sometimes I think I'm stupid.  The rest of the time I'm sure of it.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom not found after booting was ok-ver 6.0

2006-04-05 Thread Igor Robul
On Wed, Mar 29, 2006 at 08:02:24PM +0800, uid0 wrote:
 
 IBM Netfinity 5000 with 2 SCSI HDs, SCSI Tape Drive and ATAPI CDrom.
If your CD-ROM is ATA slave, then try changing it to ATA master. If it
is master, then try slave.

I had same looking problem with much cheaper hardware (MSI motherboard
with i815LE chipset and Sony CD-ROM), all worked fine with ASUS CD-ROM,
but had not worked until I changed Sony CD-ROM from master to slave.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM and data on it

2006-03-27 Thread Lowell Gilbert
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:

   I am running FreeBSD 4.3 (see uname -a below) and I have only
   used the CDROM to install new versions of FreeBSD .  Now I
   want to use it for file storage.  What programs must I have to
   be able to read from and write to a CDROM ?  What is the
   structure of information on a CDROM ?  If it is a FreeBSD file
   system, how do I mount the device, or does mount -ing it cause
   it to be considered a file system and that isn't what I want?
   If I want to share a CDROM with MSDOS systems, how would I
   mount it (as an MSDOS file system)?  What about listing the
   files and directories (if any) on it?

Please read the documentation:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html

   Are the programs the same for  FreeBSD 6.0 ?

Yes.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM input/output error

2005-10-21 Thread Jerry McAllister
 
 I can't seem to mount my CD drives, in particular my dvd-cdrw.  I'm
 trying to burn ISO's w/ k3b but can't add the device because of the
 error.  It won't even let me change drive permissions.  What can I do?

I may be wrong on this, but I do not believe you mount a drive
to burn a cd/dvd.  The burner handles it directly.  

You can only mount a CD/DVD if there is a readable disk in the drive.
Then you are sort of mounting the disk, not the drive.
But, if someone else with more knowledge tells you otherwise,
I will stand corrected.

jerry

 Best regards,
 James
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Unknown Transfer Error crashes system

2005-10-13 Thread Wayne Witzke

Lowell Gilbert wrote:

Wayne Witzke [EMAIL PROTECTED] writes:



I'm a little confused...  I thought I had RELENG_5_4.  uname -a says:

FreeBSD wlaptop 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Thu Oct  6
21:18:29 EDT 2005
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WLAPTOP  i386

Isn't this RELENG_5_4?



It was, but some patches have been applied since the release was
made.  I was suggesting RELENG_5, not RELENG_5_4; in other words, the
branch that will eventually become the 5.5 release.


I'll see if I can't figure out how to do this, then.  I had no idea that 
I wasn't running the most current.






Lowell Gilbert wrote:




Is there anything that I can do to capture more information the next
time my computer reboots spontaneously?


Try to get a crash dump.  There's more information on it in the
Handbook.  And some related information on panic analysis (if you can
get it to that point) in the FAQ.



I'll try that, it doens't sound too difficult.  Just so I know, if I
was going to see a kernel panic message, I'd be seeing one before the
computer reboots, right?



I thought that was what you were describing in earlier messages.


I'm *NOT* getting anything of this form (from the FAQ):

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x40
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xf014a7e5
stack pointer   = 0x10:0xf4ed6f24
frame pointer   = 0x10:0xf4ed6f28
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 80 (mount)
interrupt mask  =
trap number = 12
panic: page fault

All I get is the single line error message in the system log:

acd0: unknown transfer phase

and then the computer drops to a POST and reboots.  I see nothing on my 
screen between the error and the POST.


One of the diagnostic steps that the FAQ mentions is to trace the 
instruction pointer.  My assumption was that if the system was going to 
give me a message like that, I'd see it before the POST, but I wanted to 
make sure that I didn't need to be looking for that message in a log 
somewhere, or changing a configuration option somewhere to make the 
system generate an error message of that form, because I definitely 
don't see that before the POST.


Wayne
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Unknown Transfer Error crashes system

2005-10-13 Thread Lowell Gilbert
Wayne Witzke [EMAIL PROTECTED] writes:

 Lowell Gilbert wrote:
  Wayne Witzke [EMAIL PROTECTED] writes:
 
 I'm a little confused...  I thought I had RELENG_5_4.  uname -a says:
 
 FreeBSD wlaptop 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Thu Oct  6
 21:18:29 EDT 2005
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WLAPTOP  i386
 
 Isn't this RELENG_5_4?
  It was, but some patches have been applied since the release was
  made.  I was suggesting RELENG_5, not RELENG_5_4; in other words, the
  branch that will eventually become the 5.5 release.
 
 I'll see if I can't figure out how to do this, then.  I had no idea
 that I wasn't running the most current.

What you are running is the more recent release.  But FreeBSD's
developers have continued to modify code in the six months or so since
then.  

 Lowell Gilbert wrote:
 
 Is there anything that I can do to capture more information the next
 time my computer reboots spontaneously?
 
 Try to get a crash dump.  There's more information on it in the
 Handbook.  And some related information on panic analysis (if you can
 get it to that point) in the FAQ.
 
 
 I'll try that, it doens't sound too difficult.  Just so I know, if I
 was going to see a kernel panic message, I'd be seeing one before the
 computer reboots, right?
  I thought that was what you were describing in earlier messages.
 
 I'm *NOT* getting anything of this form (from the FAQ):
 
   Fatal trap 12: page fault while in kernel mode
   fault virtual address   = 0x40
   fault code  = supervisor read, page not present
   instruction pointer = 0x8:0xf014a7e5
   stack pointer   = 0x10:0xf4ed6f24
   frame pointer   = 0x10:0xf4ed6f28
   code segment= base 0x0, limit 0xf, type 0x1b
   = DPL 0, pres 1, def32 1, gran 1
   processor eflags= interrupt enabled, resume, IOPL = 0
   current process = 80 (mount)
   interrupt mask  =
   trap number = 12
   panic: page fault
 
 All I get is the single line error message in the system log:
 
 acd0: unknown transfer phase
 
 and then the computer drops to a POST and reboots.  I see nothing on
 my screen between the error and the POST.

Ah.  A spontaneous reboot, not a panic.  Sorry I misunderstood.

 One of the diagnostic steps that the FAQ mentions is to trace the
 instruction pointer.  My assumption was that if the system was going
 to give me a message like that, I'd see it before the POST, but I
 wanted to make sure that I didn't need to be looking for that message
 in a log somewhere, or changing a configuration option somewhere to
 make the system generate an error message of that form, because I
 definitely don't see that before the POST.

A debugging kernel may help.  

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Unknown Transfer Error crashes system

2005-10-12 Thread Wayne Witzke

Lowell Gilbert wrote:

Don't top-post, please.

Wayne Witzke [EMAIL PROTECTED] writes:



Lowell Gilbert wrote:


Wayne Witzke [EMAIL PROTECTED] writes:



I've googled the error, but the information was mostly related to cd
burning or errors in different releases from months or years
ago. Nothing recent that I could find.

Does anybody have any idea what's going on and how I can fix whatever it is?


You could talk to the main ATA developer ([EMAIL PROTECTED]), but he
will almost certainly want to know what happens with more recent
code.  Can you try updating your system?





Thank you for your reply!

Are you talking about upgrading to the 6.0-BETA?  Is it a fairly
transparent process, or is it going to require a lot of reconfiguring
and reinstalling?  I'm not sure I have time to update if that's the
case.  I'm working under a deadline at the moment.



RELENG_5 would be an improvement.  It's not necessary, but developers
find it much easier to debug recent code than older versions.  


I'm a little confused...  I thought I had RELENG_5_4.  uname -a says:

FreeBSD wlaptop 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Thu Oct  6 21:18:29 
EDT 2005

 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WLAPTOP  i386

Isn't this RELENG_5_4?





Is there anything that I can do to capture more information the next
time my computer reboots spontaneously?



Try to get a crash dump.  There's more information on it in the
Handbook.  And some related information on panic analysis (if you can
get it to that point) in the FAQ.




I'll try that, it doens't sound too difficult.  Just so I know, if I was 
going to see a kernel panic message, I'd be seeing one before the 
computer reboots, right?


Thank you again!

Wayne
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Unknown Transfer Error crashes system

2005-10-12 Thread Lowell Gilbert
Wayne Witzke [EMAIL PROTECTED] writes:

 I'm a little confused...  I thought I had RELENG_5_4.  uname -a says:
 
 FreeBSD wlaptop 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Thu Oct  6
 21:18:29 EDT 2005
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WLAPTOP  i386
 
 Isn't this RELENG_5_4?

It was, but some patches have been applied since the release was
made.  I was suggesting RELENG_5, not RELENG_5_4; in other words, the
branch that will eventually become the 5.5 release.

 Lowell Gilbert wrote:

 Is there anything that I can do to capture more information the next
 time my computer reboots spontaneously?
  Try to get a crash dump.  There's more information on it in the
  Handbook.  And some related information on panic analysis (if you can
  get it to that point) in the FAQ.
 
 
 I'll try that, it doens't sound too difficult.  Just so I know, if I
 was going to see a kernel panic message, I'd be seeing one before the
 computer reboots, right?

I thought that was what you were describing in earlier messages.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Unknown Transfer Error crashes system

2005-10-11 Thread Wayne Witzke

Thank you for your reply!

Are you talking about upgrading to the 6.0-BETA?  Is it a fairly 
transparent process, or is it going to require a lot of reconfiguring 
and reinstalling?  I'm not sure I have time to update if that's the 
case.  I'm working under a deadline at the moment.


Is there anything that I can do to capture more information the next 
time my computer reboots spontaneously?


Wayne

Lowell Gilbert wrote:

Wayne Witzke [EMAIL PROTECTED] writes:



I've googled the error, but the information was mostly related to cd
burning or errors in different releases from months or years
ago. Nothing recent that I could find.

Does anybody have any idea what's going on and how I can fix whatever it is?



You could talk to the main ATA developer ([EMAIL PROTECTED]), but he
will almost certainly want to know what happens with more recent
code.  Can you try updating your system?




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Unknown Transfer Error crashes system

2005-10-11 Thread Lowell Gilbert
Don't top-post, please.

Wayne Witzke [EMAIL PROTECTED] writes:

 Lowell Gilbert wrote:
  Wayne Witzke [EMAIL PROTECTED] writes:
 
 I've googled the error, but the information was mostly related to cd
 burning or errors in different releases from months or years
 ago. Nothing recent that I could find.
 
 Does anybody have any idea what's going on and how I can fix whatever it is?
  You could talk to the main ATA developer ([EMAIL PROTECTED]), but he
  will almost certainly want to know what happens with more recent
  code.  Can you try updating your system?
 

 Thank you for your reply!
 
 Are you talking about upgrading to the 6.0-BETA?  Is it a fairly
 transparent process, or is it going to require a lot of reconfiguring
 and reinstalling?  I'm not sure I have time to update if that's the
 case.  I'm working under a deadline at the moment.

RELENG_5 would be an improvement.  It's not necessary, but developers
find it much easier to debug recent code than older versions.  

 Is there anything that I can do to capture more information the next
 time my computer reboots spontaneously?

Try to get a crash dump.  There's more information on it in the
Handbook.  And some related information on panic analysis (if you can
get it to that point) in the FAQ.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Unknown Transfer Error crashes system

2005-10-09 Thread Dmitry Mityugov
On 10/9/05, Wayne Witzke [EMAIL PROTECTED] wrote:
 Hello everybody,

 I've just installed FreeBSD on my laptop (decided I wanted a more
 developer-friendly computer).  Aside from what appear to be the standard
 newbie problems, every thing's gone remarkably well, except for this:

 I have a CD-RW/DVD-ROM drive on my laptop.  As a CDROM it had been
 working perfectly well since the initial install about a week and a half
 ago.  It read CDs and DVDs without incident, and did so for hours and
 hours (which it was forced to do because I've been listening to music
 pretty much non-stop since I installed the system).  The burner did not
 work, but after the grueling process of opening up the FreeBSD handbook
 and actually reading how to make it possible to burn CDs, that started
 working as well.  That is, I recompiled the kernel with the atapicam
 module, changed permissions and set up links in the devfs.conf file in
 /etc, and set the suid on cdrecord and cdrdao.  Worked like a charm.
 Burned my first CD, and it was beautiful.  Then I think I went home.

 Yesterday, while not burning any CDs at all, just listening to music
 using kscd while I wrote perl script, my computer suddenly reboots.
...

This's the last day I am reading these archives. I believe you'll have
to find a better OS that suits your needs.

--
Dmitry Mityugov, St. Petersburg, Russia
I ignore all messages with confidentiality statements

We live less by imagination than despite it - Rockwell Kent, N by E
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM Unknown transfer [phase reboots] system

2005-10-09 Thread Wayne Witzke

Dmitry Mityugov wrote:

On 10/9/05, Wayne Witzke [EMAIL PROTECTED] wrote:


Hello everybody,

I've just installed FreeBSD on my laptop (decided I wanted a more
developer-friendly computer).  Aside from what appear to be the standard
newbie problems, every thing's gone remarkably well, except for this:

I have a CD-RW/DVD-ROM drive on my laptop.  As a CDROM it had been
working perfectly well since the initial install about a week and a half
ago.  It read CDs and DVDs without incident, and did so for hours and
hours (which it was forced to do because I've been listening to music
pretty much non-stop since I installed the system).  The burner did not
work, but after the grueling process of opening up the FreeBSD handbook
and actually reading how to make it possible to burn CDs, that started
working as well.  That is, I recompiled the kernel with the atapicam
module, changed permissions and set up links in the devfs.conf file in
/etc, and set the suid on cdrecord and cdrdao.  Worked like a charm.
Burned my first CD, and it was beautiful.  Then I think I went home.

Yesterday, while not burning any CDs at all, just listening to music
using kscd while I wrote perl script, my computer suddenly reboots.


...

This's the last day I am reading these archives. I believe you'll have
to find a better OS that suits your needs.

--
Dmitry Mityugov, St. Petersburg, Russia
I ignore all messages with confidentiality statements

We live less by imagination than despite it - Rockwell Kent, N by E
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]




Mr. Mityugov,

I am certainly sorry if I've offended you in some way.  It seemed to me 
that I asked a perfectly valid question.  I want to know what caused the 
unknown transfer phase on my CDROM and how to prevent it from 
happening again.  I certainly didn't expect that would cause such anger 
that it would warrant a nasty response.


As for whether FreeBSD suits my needs, it most certainly does.  I've 
been an administrator of Unix-like systems for about 7 years, starting 
with Linux systems back in '97 and working my way up to IRIX a few years 
ago.  I've had FreeBSD installed and working on home systems in the 
past, but it's been a while.  Now, my work laptop had crashed (hard disk 
death), and I was tired having to struggle to get Windows to do what I 
wanted it to do and to keep it up and running more then a month at a 
time.  Took 6 months to make Windows work the way I wanted it to, when 
it only took about a week to get FreeBSD working.  In my experience, 
Unix-like systems have *always* been easier to develop on, have always 
been more stable, and are always faster.  The fact that FreeBSD combines 
these properties with the ease of the ports collection plus what I 
thought was a community of involved people willing to help made it the 
obvious choice.


If by suits your needs you meant your need to listen to music, I 
believe that's beside the point.  The fact that acd0 had an unknown 
transfer phase is troubling regardless of the task it was performing at 
the time, especially considering that it was a kernel message.  I will 
almost certainly need to be able to read from my CDROM drive at some 
point in the future for data transfer purposes, and a reboot during such 
a read would at best cause the data transfer to fail, and at worst it 
could corrupt data on the hard drive in an unrecoverable way.


I also apologize that my subject line wasn't 100% accurate.  It should 
have read CDROM Unknown transfer *phase reboots* system.  The word 
error in the subject line was incorrect, and the assertion that it 
caused a crash was just an assumption on my part. I was unable to find a 
memory dump or any information that should have led me to believe it was 
definitely a crash (and I still can't).  Also, it's an assumption on my 
part that the unknown transfer phase rebooted the system, but that was 
the last entry in the log file and I though (and still think) that it's 
the best indicator for what might have gone wrong.  And the word 
reboot may be incorrect as well.  The system didn't go through the 
shutdown process at all, it simply dropped to a POST.


If your objection was to the length of the description in my original 
message, I though it would be prudent to provide as much detail as I 
could about the steps I had gone through with my CDRW/DVDROM drive so 
that those who might be interested in helping would have as much detail 
as I could provide.  I apologize if what I was hoping to be a playful 
tone offended you, but since I tend to enjoy working on operating 
systems like FreeBSD I tend to write in a manner that expresses that 
feeling.  I also apologize that part of my message, and my actual 
question, was at the bottom of the message after the dmesg output.  That 
format was, I realize, not conducive to 

Re: cdrom mount question

2005-07-08 Thread Alejandro Pulver
On Fri, 8 Jul 2005 14:42:22 +
Bryan Maynard [EMAIL PROTECTED] wrote:

 I am not sure which list to post this to, I'll start here. :-) I am
 trying to  play a CD through amaroK in KDE, but when I try to mount
 the disc I get the  following error:
 
 cd9660: /dev/acdo: Operation not permitted
 
 I am not running as root when trying to access the device and I'm sure
 this is  the problem. . . I just don't know how to fix it :-).
 
 Thanks for all your help!
 
 Bryan
 -- 
 Open Source: by the people, for the people.

Hello,

The instructions to allow a normal user to mount devices is in the FAQ:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FLOPPYMOUNT

Best Regards,
Ale
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mount question

2005-07-08 Thread Roland Smith
On Fri, Jul 08, 2005 at 02:42:22PM +, Bryan Maynard wrote:

 I am not sure which list to post this to, I'll start here. :-) I am
 trying to play a CD through amaroK in KDE, but when I try to mount the
 disc I get the following error:

You don't have to mount a music CD.
 
 cd9660: /dev/acdo: Operation not permitted

You do need permission to access the device though.

As root, type 'chmod 666 /dev/acdo'.

To keep this setting after reboot, add the following to /etc/devfs.conf:

perm  acd0  0666


Roland
-- 
R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text.
public key: http://www.xs4all.nl/~rsmith/pubkey.txt


pgptGPZbx4X02.pgp
Description: PGP signature


[Fwd: Re: cdrom mount question]

2005-07-08 Thread Garrett Cooper

On Fri, 8 Jul 2005, Garrett Cooper wrote:

Andreas Davour wrote:


On Fri, 8 Jul 2005, Bryan Maynard wrote:



I am not running as root when trying to access the device and I'm 
sure this is the problem. . . I just don't know how to fix it :-) .



I don't know if I used amaroK or whatever KDE player was in the menu, 
but I just acted like the disc was mounted and it worked. It was a bit 
strange, since I had tried hard to change the protection on the device 
without getting it to work. Maybe the player ran setuid root or 
something, and tried to do magic on its own.


Have amaroK actually complained about the disc not being mounted? If
not, just try without mountinga and you might be lucky.



Audio CDs shouldn't be mounted... If you try and do that you will most 
likely encounter issues with reading the CD. All that you would have to 
do most likely is change the permissions for the device to allow full 
read access to you on a user or group level (ie 0666, 0660 or 
equivalent). Modifying /etc/devfsd.conf to your liking is the best way 
to go to retain changes across boots.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM firewall

2005-06-27 Thread martin hudec
Hello,

On Mon, Jun 27, 2005 at 10:55:42AM +0200 or thereabouts, Frank Bonnet wrote:
 Hi
 
 I'm searching for a CDROM firewall package FreeBSD based
 I know there is several but I can't remember their names.

  It is called m0n0wall, it is based on FreeBSD 4.x.

  Go and grab it from:
  http://www.m0n0.ch/wall/


Cheers,
Martin

-- 
martin hudec


   * 421 907 303 393
   * [EMAIL PROTECTED]
   * http://www.aeternal.net

Nothing travels faster than the speed of light with the possible 
exception of bad news, which obeys its own special laws.

   Douglas Adams, The Hitchhiker's Guide to the Galaxy


pgpg25Omm85dP.pgp
Description: PGP signature


Re: cdrom trouble with wine

2005-03-27 Thread jason henson
jason henson wrote:
I have got to a point where I need some help.  I have got starcraft 
tot install, broodwar to install, and update it.  I can run programs 
from cd in with, like setup.exe, but starcraft still can't read a file 
on the cd.  I have mounted the cd in my home dir, created the right 
wine config file, and even used dd to make an iso that I mounted and 
it still didn't work.  I don't think this game even uses any secure 
rom because a simple disc copy on to a cdr works fine in windows.  
Anyone had a problem like this?

$ wine starcraft.exe
fixme:file:get_default_drive_device auto detection of DOS devices not 
supported on this platform
fixme:ntdll:NtQueryVolumeInformationFile device info not properly 
supported on this platform
err:heap:HEAP_CreateSystemHeap system heap base address 0x8000 not 
available
$

thanks,
Jason

BTW staredit works, but is slugish with out nice.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom image to cdr

2005-02-25 Thread Josh Paetzel
On Friday 25 February 2005 10:13, dick hoogendijk wrote:
 What is the easiest way to copy a complete cdrom with freebsd-4.11?
 Normally I use burncd to burn an iso file to a new cdr, but I never
 copied a complete cdrom to cdr under freebsd. My windows machines
 are down and I need the copy soon. So please forgive me if I'm
 ignorant. Hope the answer is easy ;-)

This is covered in the handbook, but the basic idea is that you mount 
the CD, use mkisofs to create an iso of it and then burn the iso with 
burncd.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html

-- 
Thanks,

Josh Paetzel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom image to cdr

2005-02-25 Thread David Kelly
On Fri, Feb 25, 2005 at 11:02:14AM -0600, Josh Paetzel wrote:
 On Friday 25 February 2005 10:13, dick hoogendijk wrote:
  What is the easiest way to copy a complete cdrom with freebsd-4.11?
  Normally I use burncd to burn an iso file to a new cdr, but I never
  copied a complete cdrom to cdr under freebsd. My windows machines
  are down and I need the copy soon. So please forgive me if I'm
  ignorant. Hope the answer is easy ;-)
 
 This is covered in the handbook, but the basic idea is that you mount 
 the CD, use mkisofs to create an iso of it and then burn the iso with 
 burncd.
 
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html

No, the basic idea mentioned at the above URL is to recover the .iso
file using dd. This usually works. Doesn't work for multisession discs.

I've found some drives report EOM while reading the last block while
others wait until an attempt to read past the last block. Result is that
dd may read some one block short. May be good enough for everything but
verify after write.

/usr/ports/sysutils/cdrdao/ can handle arbitrary disc duplication, altho
I haven't tried it in quite a while.

-- 
David Kelly N4HHE, [EMAIL PROTECTED]

Whom computers would destroy, they must first drive mad.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM of OpenOffice?

2005-01-11 Thread Kris Kennaway
On Tue, Jan 11, 2005 at 10:49:46AM -, John Conover wrote:
 
 Is OpenOffice available for 5.3 on a CDROM?
 
 I'm on a dial up, and its too big.

I think bsdmall sells it, but I don't know.

Kris

pgpZ04mVCnnH0.pgp
Description: PGP signature


Re: CDROM Mounting and Permissions (easy)

2005-01-02 Thread Nikolas Britton
Sergei Gnezdov wrote:
Hi,
I need to mount /dev/acd0 (cdrom) from the standard user account.
Do I have to give the user account write access to /dev/acd0 device or
there is another way I don't know about?
 

http://groups-beta.google.com/group/lucky.freebsd.questions/browse_thread/thread/a4811769719d0538 
(look at the date on the thread :-) )

http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FLOPPYMOUNT
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mounting troubles

2004-12-05 Thread Lucas Holt
I'm not 100% sure about this, but I believe that audio cds use a different 
file system than data cds.  cd9660 is the iso cd format.

On Sun, 5 Dec 2004, Trysch wrote:
hi i am having a problem mounting my cdrom some of the time on freebsd 5.3
my cdrom is also a 28 times burner
if i put in a data disk and type mount -t cd9660 -r /dev/acd0 /cdrom it 
mounts just fine.

however if i put in a regular cd to just listen to not an mp3 disk is tells 
me its an incorrect super block

im on a compaq armada e500
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mounting troubles

2004-12-05 Thread Lowell Gilbert
Trysch [EMAIL PROTECTED] writes:

 hi i am having a problem mounting my cdrom some of the time on freebsd 5.3
 my cdrom is also a 28 times burner
 
 if i put in a data disk and type mount -t cd9660 -r /dev/acd0 /cdrom
 it mounts just fine.
 
 however if i put in a regular cd to just listen to not an mp3 disk is
 tells me its an incorrect super block

Why can I not mount an audio CD?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#MOUNT-AUDIO-CD
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mounting troubles

2004-12-05 Thread Trysch
I've tried every mount command i can find t otry and it wont mount at 
all with music in the cdrom at all

Lucas Holt wrote:
I'm not 100% sure about this, but I believe that audio cds use a 
different file system than data cds.  cd9660 is the iso cd format.

On Sun, 5 Dec 2004, Trysch wrote:
hi i am having a problem mounting my cdrom some of the time on 
freebsd 5.3
my cdrom is also a 28 times burner

if i put in a data disk and type mount -t cd9660 -r /dev/acd0 /cdrom 
it mounts just fine.

however if i put in a regular cd to just listen to not an mp3 disk is 
tells me its an incorrect super block

im on a compaq armada e500
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
[EMAIL PROTECTED]


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mounting troubles

2004-12-05 Thread Adam Fabian
On Sun, Dec 05, 2004 at 11:38:21AM -0700, Trysch wrote:
 however if i put in a regular cd to just listen to not an mp3 disk is
 tells me its an incorrect super block

Audio CDs do not have a filesystem and cannot be mounted.  They can,
however, be read and played with an appropriate program.
-- 
Adam Fabian ([EMAIL PROTECTED])
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom error

2004-09-14 Thread Bill Moran
Petre Bandac [EMAIL PROTECTED] wrote:

 Sep 14 12:34:18 xxl kernel: cd9660: Joliet Extension (Level 1)
 
 Sep 14 12:34:18 xxl kernel: Sep 14 12:34:18 xxl kernel: cd9660: Joliet
 Extension (Level 1)
 
 Sep 14 12:34:26 xxl kernel: acd0: READ_BIG - MEDIUM ERROR asc=0x02
 ascq=0x00 error=0x04
 
 
 and the cdrom doesn't seem to be scratched ... could be my cdrom drive
 which shows signs of old age ?

That's pretty likely.

I've also seen this kind of problem with poor cabling, and with cheap
CDROMs that don't know how to be a slave properly.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDrom problems

2004-06-02 Thread Mark Weinem
On Tue, 25 May 2004, Donald Szatkowski wrote:

 It appears that there are quite a few problems with basic setup and
 cdrom.  Could someone please post a copy of associated files to give
 an example of setup?


1. add vfs.usermount=1 to /etc/sysctl.conf

2. run sysctl vfs.usermount=1

3. add the user to group wheel, adjust the permissions of
   dev/acd0c (FreeBSD 5.x - /dev/acd0) and /dev/cdrom
   if necessary.

For 5.x, make the permissions permanent in /etc/devfs.conf:

perm acd0 0555


Ciao, Mark Weinem
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDrom problems

2004-05-25 Thread Joe Altman
On Tue, May 25, 2004 at 09:25:34AM -0500, Donald Szatkowski wrote:
 It appears that there are quite a few problems with basic setup and cdrom.

What does this mean? Please elaborate: do you mean that setup
beginning with sysinstall is problematic, in that you cannot use your
cdrom drive during sysinstall?

 Could someone please post a copy of associated files to give an example of 
 setup? The kernel.GENERIC is okay for root access to the cdrom, but there are 
 problems allowing general users access.

This appears to be the well-known FAQ about providing access to the CD
drive for non-root users.

Perhaps this will help:

Go to /usr/share/doc/ on your machine, and look for the FAQ
directory. In that document, you will find that chapter nine, question
9.22, is titled How do I let ordinary users mount floppies, CDROMs
and other removable media? Since the document in question is an html
document, you will be able to use a browser.

 Also, could someone address the question of ATAPI compliance of
 devices?

I'm not sure what this means; what question of compliance?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mount problem

2004-03-19 Thread anubis
On Fri, 19 Mar 2004 1:35 am, Chris wrote:
 *This message was transferred with a trial version of
 CommuniGate(tm) Pro*




 In summary: the only way to mount my cdrom after burning an ISO is
 to reboot first.


 Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using
 burncd, then later mount /cdrom to access the files I burned. With
 RC1 and now with 5.2.1-RELEASE, a strange thing happens:

 After a reboot, I can mount /cdrom and access files on the disc.
 But if I re-burn the ISO file, then try to mount /cdrom, I get
 this:

 cd9660: /dev/acd0: Input/output error

 BUT... if I reboot THEN try to access that same disk, it works
 fine.

I had a problem with burncd where I couldnt access the disk after 
burning.  I couldnt eject or mount it.  It required a reboot to get 
it.  I couldnt solve it but I was able to work around it by using 
cdcontrol.  See the man page for all options but breifly you can 
eject and then close the disk by
cdcontrol -f /dev/acd0 eject
cdcontrol -f /dev/acd0 close
I cant remember exactly what I did but I am sure I just ejected by 
software then put back in and it worked fine.  It was as if somehow 
something was holding onto the disk.  I thought it was maybe my 
windows partition getting lonely.






___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mount problem

2004-03-18 Thread Martijn
Hi chris,

You first have to unmount the cdrom before you can mount
a new cd, you can do that by typing:
umount /cdrom

greets, Martijn

On Thursday 18 March 2004 16:35, Chris wrote:
 *This message was transferred with a trial version of CommuniGate(tm) Pro*




 In summary: the only way to mount my cdrom after burning an ISO is to
 reboot first.


 Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd,
 then later mount /cdrom to access the files I burned. With RC1 and now with
 5.2.1-RELEASE, a strange thing happens:

 After a reboot, I can mount /cdrom and access files on the disc. But if I
 re-burn the ISO file, then try to mount /cdrom, I get this:

 cd9660: /dev/acd0: Input/output error

 BUT... if I reboot THEN try to access that same disk, it works fine.

 Thanks,
 Chris


 _
 Email harvesters eat this: [EMAIL PROTECTED]

 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mount problem

2004-03-18 Thread Lowell Gilbert
Chris [EMAIL PROTECTED] writes:

 *This message was transferred with a trial version of CommuniGate(tm) Pro*
 
 
 
 
 In summary: the only way to mount my cdrom after burning an ISO is to reboot first.
 
 
 Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd, then 
 later mount /cdrom to access the files I burned. With RC1 and now with 
 5.2.1-RELEASE, a strange thing happens:
 
 After a reboot, I can mount /cdrom and access files on the disc. But if I re-burn 
 the ISO file, then try to mount /cdrom, I get this: 
 
 cd9660: /dev/acd0: Input/output error
 
 BUT... if I reboot THEN try to access that same disk, it works fine.

Try ejecting and re-loading the disk. 
I've seen some firmware that gets confused easily in these cases...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom mount problem

2004-03-18 Thread Joshua Lokken
* Martijn [EMAIL PROTECTED] [2004-03-18 08:14]:
 Hi chris,
 
 You first have to unmount the cdrom before you can mount
 a new cd, you can do that by typing:
 umount /cdrom
 
 greets, Martijn
 
 On Thursday 18 March 2004 16:35, Chris wrote:
  *This message was transferred with a trial version of CommuniGate(tm) Pro*
 
 
 
 
  In summary: the only way to mount my cdrom after burning an ISO is to
  reboot first.
 
 
  Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd,
  then later mount /cdrom to access the files I burned. With RC1 and now with
  5.2.1-RELEASE, a strange thing happens:
 
  After a reboot, I can mount /cdrom and access files on the disc. But if I
  re-burn the ISO file, then try to mount /cdrom, I get this:
 
  cd9660: /dev/acd0: Input/output error
 
  BUT... if I reboot THEN try to access that same disk, it works fine.
 
  Thanks,
  Chris


Please don't top-post.  I have used burncd since 4.5, and I have
never mounted a CD-R to burn it.  I'm sorry, I have no light to
shed on your problem, just wanted to keep your confusion to a
minimum.  Again, burning a CD-R under FreeBSD with burncd does
NOT involve mounting the drive first.

-- 
Joshua

Beauty is transitory.
Beauty survives.
-- Spock and Kirk, That Which Survives, stardate unknown
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom

2004-02-16 Thread Mardoc Inc.
Thankyou to each of you for your comments re mounting the CDROM.  I have 
now got it working.  As for the age of the OS - newer is not always 
better, I am afraid. Of course this depends on both hardware and 
software, but there is no doubt that the newer hardware (disks etc) are 
far less reliable, despite being able to hold more data. Newer operating 
systems have more bells and whistles, but again, that does not always 
make them better. My most reliable systems are usually my older ones - 
in fact my MOST reliable systems are over 12 years old.

tks

Wayne Hocking

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom

2004-02-16 Thread Kris Kennaway
On Mon, Feb 16, 2004 at 06:54:52AM -0800, Mardoc Inc. wrote:
 
 Thankyou to each of you for your comments re mounting the CDROM.  I have 
 now got it working.  As for the age of the OS - newer is not always 
 better, I am afraid. Of course this depends on both hardware and 
 software, but there is no doubt that the newer hardware (disks etc) are 
 far less reliable, despite being able to hold more data. Newer operating 
 systems have more bells and whistles, but again, that does not always 
 make them better. My most reliable systems are usually my older ones - 
 in fact my MOST reliable systems are over 12 years old.
 

That's all well and good, until you need help to fix a problem with
your old OS.  You're lucky that this one was simple and not an OS bug.

Kris


pgp0.pgp
Description: PGP signature


Re: cdrom

2004-02-15 Thread Kris Kennaway
On Sun, Feb 15, 2004 at 06:58:34PM -0800, Mardoc Inc. wrote:

 I am using FreeBSD 2.2.7-CAM.  My motherboard is a Super P6SNE II, circa 
 1997.

This wasn't ever a supported FreeBSD release, let alone that 2.x
releases have been out of support for years.  However,

 I am trying to read from a CD.  I am currently using a Acer 640-272 CD 
 (40x).
 
 The BIOS recognizes the CD - dmesg gives (approximately - not quite 
 verbatim)
 
 wcd0 unit 1(atapi) ATAPI CD-ROM DRIVE 40x Maximum/NOAP
 removeable drivem iondic,
 wcd0 6890 kB/s, 128 kB cache, audioplay ...
 wcd0 medium type ox11, unlocked
 
 
 
 I have tried to mount it as
 
 mount /dev/wcd0a /cdrom
 
 but I get a message
 
 Incorrect superblock.

This command tells FreeBSD to mount the CD as a UFS filesystem.  It's
possible to make CD images containing UFS filesystems, but it is
unlikely to be what you want; most CDs use the cd9660 filesystem.  Use
mount -t cd9660 instead.

Kris

pgp0.pgp
Description: PGP signature


Re: cdrom

2004-02-15 Thread Eric F Crist
On Sunday 15 February 2004 08:58 pm, Mardoc Inc. wrote:
 To: FreeBSD advisors:

 Re: CDROM

 Dear Sir/Madam

 I am currently using FreeBSD to operate some digitizing  equipment.  I
 cannot upgrade
 to a newer version of FreeBSD because all the current equipment is somewhat
 locked to it.

 I am using FreeBSD 2.2.7-CAM.  My motherboard is a Super P6SNE II, circa
 1997.

 I am trying to read from a CD.  I am currently using a Acer 640-272 CD
 (40x).

 The BIOS recognizes the CD - dmesg gives (approximately - not quite
 verbatim)

 wcd0 unit 1(atapi) ATAPI CD-ROM DRIVE 40x Maximum/NOAP
 removeable drivem iondic,
 wcd0 6890 kB/s, 128 kB cache, audioplay ...
 wcd0 medium type ox11, unlocked



 I have tried to mount it as

 mount /dev/wcd0a /cdrom

 but I get a message

 Incorrect superblock.


 Is there an easy way to mount the CD, or is the message telling me it
 is too difficult, or my CD is too new?? If so, do you know what vintage CD
 I could get to work?

 tks

 Wayne Hocking

 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]


Try the following:

mount -t cd9660 /dev/wcd0c /cdrom

Note the c at the end of the device, instead of the a.  I don't know why, but 
this is what I've got to do.  Perhaps Kris or someone else who knows 
something more than I can explain that part...

HTH
-- 
Eric F Crist
AdTech Integrated Systems, Inc
(612) 998-3588


pgp0.pgp
Description: signature


Re: cdrom

2004-02-13 Thread Dave
On Wed, 11 Feb 2004 22:02:18 +0100, you wrote:

I have an old pc on witch I want to install freebsd, only when the bios 
does not see the cdrom drive. But windows does. It is a normal IDE cdrom 
and set to slave (hard disk primary). Also when I run the installation 
it stops when it has to read the cdrom. Is there a way to manually set 
the cdrom in the bios. or to install it on a other way.

Does the system see the CD drive if you boot from the floppy install
disks?  Some older PCs can't boot from CD but need a driver to be loaded
first.  Even older CD drives use proprietry interfaces which FreeBSD may
not see either, eg the CD is plugged into it's own controller card or a
sound card (some work, some don't)

Dave

-- 
Any speling misteaks are the reult of a bad insallation of mod_spelink.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom

2004-02-13 Thread HOLLOW, CHRISTOPHER
Save yourself the $50 investment in the old hardware and do a network 
installation.  You'll need a floppy drive and a network card.  Create 
the boot floppies and choose FTP installation.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html#INSTALL-FLOPPIES

Yank that old CD-ROM out all together...

Christopher Hollow

Charles Swiger wrote:

On Feb 11, 2004, at 4:02 PM, Wouter Grol wrote:

I have an old pc on witch I want to install freebsd, only when the 
bios does not see the cdrom drive.  But windows does.


Hi--

If the BIOS doesn't recognize the CD-ROM drive, that's generally a 
NO-GO for FreeBSD working with the drive.  You probably have a 
proprietary driver for the device to make it work under Windows.  
However, I think FreeBSD had limited support for some of the old 
pre-ATAPI CD-ROM drives from Mitsumi and Sony (rebranded by 
Creative)...from LINT see:

#
# Miscellaneous hardware:
#
# mcd: Mitsumi CD-ROM using proprietary (non-ATAPI) interface
# scd: Sony CD-ROM using proprietary (non-ATAPI) interface
Is your drive one of these?  Otherwise, it's probably better to spend 
$50 and get a standard CD-ROM drive...

--
Christopher Hollow - Technical Consultant
Infrastructure  Technology Support
Toronto, ON


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom

2004-02-11 Thread Charles Swiger
On Feb 11, 2004, at 4:02 PM, Wouter Grol wrote:
I have an old pc on witch I want to install freebsd, only when the 
bios does not see the cdrom drive.  But windows does.
Hi--

If the BIOS doesn't recognize the CD-ROM drive, that's generally a 
NO-GO for FreeBSD working with the drive.  You probably have a 
proprietary driver for the device to make it work under Windows.  
However, I think FreeBSD had limited support for some of the old 
pre-ATAPI CD-ROM drives from Mitsumi and Sony (rebranded by 
Creative)...from LINT see:

#
# Miscellaneous hardware:
#
# mcd: Mitsumi CD-ROM using proprietary (non-ATAPI) interface
# scd: Sony CD-ROM using proprietary (non-ATAPI) interface
Is your drive one of these?  Otherwise, it's probably better to spend 
$50 and get a standard CD-ROM drive...

--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom eject - by software?

2003-07-26 Thread long cao
/ports/systuils/eject

Utility for ejecting media from CD or optical disk drive.

This is a simple program that eject media from CD or optical disk
drive.  This program work under FreeBSD 2.1.5-RELEASE or later
version.



:)


On Saturday 26 July 2003 07:31 am, Lorin Lund wrote:
 I have a new hand-me-down PC for my FreeBSD box.  After I installed from
 CD (v 4.8)
 I discovered that the eject button does not work on this cd-rom drive.

 Is there any program that will cause the CD to eject?

 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom eject - by software?

2003-07-26 Thread Adam
On Sat, 2003-07-26 at 10:31, Lorin Lund wrote:
 Is there any program that will cause the CD to eject?

Here's how I do it. There's no need for special ports like sysutils/eject.

-$ cat ~/bin/ejectcd.sh 
/usr/local/bin/sudo /sbin/umount -v /cdrom
/usr/sbin/cdcontrol -v -f /dev/acd0 Eject

-- 
Adam [EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom eject - by software?

2003-07-26 Thread Bob Hall
On Sat, Jul 26, 2003 at 08:31:02AM -0600, Lorin Lund wrote:
 I have a new hand-me-down PC for my FreeBSD box.  After I installed from 
 CD (v 4.8)
 I discovered that the eject button does not work on this cd-rom drive.
 
 Is there any program that will cause the CD to eject?

This may be a dumb question, but did you remember to umount before 
hitting the eject button?

Bob Hall
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDRom able to play DVD movies

2003-07-16 Thread ydg
I think ive heard thru the same grapevine as you about such a
contraption. i have no idea if something of this nature exists or not.
and initial logic makes me think [exactly as previously stated] cd
drives, are hardware for cd's. and only dvd's drive has the necessary
extra hardware to read dvd's.
However, what ive heard is there's some kind of tweaked emulation
under windows, which tricks the system into thinking the cdrom drive
is a dvd drive, and the system compensates for the work the drive cant
actually do [perhaps some kind of 'on the fly decode/read']. no idea
if such a beast exists. and with today's prices, its probably easier
to simply buy a dvd drive. :)

yussef

On Tue, 15 Jul 2003 21:58:34-0500
Chris[EMAIL PROTECTED] wrote:

 On Tuesday 15 July 2003 09:54 pm, Neu, Benjamin S. wrote:
  Nope! A cd-rom is built (hardware wise) for CD's not DVD's!
 
 I wanted to be sure - someplace, somewhere I heard, that under
 windows, this could be done. Heh - I musta overheard that from some
 other users in passing - I was sure that wasn't the case, but in a day
 where you can purchase software (windows-wize) to boost your internet
 speed, blah, blah, blah - I just had to ask.
 
 Thanks for confirming what I had expected all along.
 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of Chris
  Sent: Tuesday, July 15, 2003 9:52 PM
  To: [EMAIL PROTECTED]
  Subject: CDRom able to play DVD movies
 
  Hiya -
 
  Is there an app/emulator that will allow my ordinary CD Rom
  reader to play
  store bought DVD movies?
 
 -- 
 
 Best regards,
  Chris
 __
 
 PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363
 
 PGP Mail encouraged / preferred - keys available on common key servers
 __
01010010011101100011011001010111001001011000
 
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
 


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDRom able to play DVD movies

2003-07-16 Thread Frank Knobbe
On Wed, 2003-07-16 at 03:28, [EMAIL PROTECTED] wrote:
 However, what ive heard is there's some kind of tweaked emulation
 under windows, which tricks the system into thinking the cdrom drive
 is a dvd drive, and the system compensates for the work the drive cant
 actually do [perhaps some kind of 'on the fly decode/read']. no idea
 if such a beast exists. and with today's prices, its probably easier
 to simply buy a dvd drive. :)

Sounds to me like you are confusing this software with a software DVD
player/decoder. Most systems should play DVD's through a built-in
hardware decoder and display it on the screen in overlay mode. If you
don't have built-in decoder, you can use software like WinDVD to read
the DVD (still from a DVD drive) and the software does the decoding and
displaying on the screen (which will usually slow the system down bad,
potentially resulting in frame loss).

You still need a DVD drive to read DVD's though. 

Regards,
Frank



signature.asc
Description: This is a digitally signed message part


RE: CDRom able to play DVD movies

2003-07-16 Thread Frank Knobbe
On Wed, 2003-07-16 at 11:44, Neu, Benjamin S. wrote:
 Is there an echo in this mailing list?! :)


Maybe :)  I only kept half of the thread. Sorry for wasting bits

Frank



signature.asc
Description: This is a digitally signed message part


Re: CDRom able to play DVD movies

2003-07-16 Thread Shantanu Mahajan
+-- Chris [freebsd] [15-07-03 21:51 -0500]:
| Hiya -
| 
|   Is there an app/emulator that will allow my ordinary CD Rom reader to play 
| store bought DVD movies?
| 
| -- 
| 
| Best regards,
|  Chris
*no*. and if you are able to do so,
_apply_for_the_patent_immediatlly_ ;-)

Regards,
Shantanu
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: CDRom able to play DVD movies

2003-07-15 Thread Neu, Benjamin S.
Nope! A cd-rom is built (hardware wise) for CD's not DVD's!

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Sent: Tuesday, July 15, 2003 9:52 PM
To: [EMAIL PROTECTED]
Subject: CDRom able to play DVD movies

Hiya -

Is there an app/emulator that will allow my ordinary CD Rom
reader to play 
store bought DVD movies?

-- 

Best regards,
 Chris
__

PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363

PGP Mail encouraged / preferred - keys available on common key servers
__
   01010010011101100011011001010111001001011000


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDRom able to play DVD movies

2003-07-15 Thread Chris
On Tuesday 15 July 2003 09:54 pm, Neu, Benjamin S. wrote:
 Nope! A cd-rom is built (hardware wise) for CD's not DVD's!

I wanted to be sure - someplace, somewhere I heard, that under windows, this 
could be done. Heh - I musta overheard that from some other users in passing 
- I was sure that wasn't the case, but in a day where you can purchase 
software (windows-wize) to boost your internet speed, blah, blah, blah - I 
just had to ask.

Thanks for confirming what I had expected all along.


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Chris
 Sent: Tuesday, July 15, 2003 9:52 PM
 To: [EMAIL PROTECTED]
 Subject: CDRom able to play DVD movies

 Hiya -

   Is there an app/emulator that will allow my ordinary CD Rom
 reader to play
 store bought DVD movies?

-- 

Best regards,
 Chris
__

PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363

PGP Mail encouraged / preferred - keys available on common key servers
__
   01010010011101100011011001010111001001011000


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDRom able to play DVD movies

2003-07-15 Thread Robert Storey
On Tue, 15 Jul 2003 21:58:34 -0500
Chris [EMAIL PROTECTED] wrote:

 On Tuesday 15 July 2003 09:54 pm, Neu, Benjamin S. wrote:
  Nope! A cd-rom is built (hardware wise) for CD's not DVD's!
 
 I wanted to be sure - someplace, somewhere I heard, that under
 windows, this could be done. Heh - I musta overheard that from some
 other users in passing - I was sure that wasn't the case, but in a day
 where you can purchase software (windows-wize) to boost your internet
 speed, blah, blah, blah - I just had to ask.
 
 Thanks for confirming what I had expected all along.
 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of Chris
  Sent: Tuesday, July 15, 2003 9:52 PM
  To: [EMAIL PROTECTED]
  Subject: CDRom able to play DVD movies
 
  Hiya -
 
  Is there an app/emulator that will allow my ordinary CD Rom
  reader to play
  store bought DVD movies?


I think I know the source of your confusion. There is a Windows program
(or probably more than one program by now) which lets you pop a DVD into
your DVD drive, and it converts the files into a format that you can
burn onto CD-R - in other words, it lets you create a pair of VCDs from
a single DVD. And of course, VCDs can be played in a normal CD drive.

regards,
Robert





___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: cdrom-drive opens @ will

2003-06-29 Thread Shantanu Mahajan
+-- Marko Leer [freebsd] [29-06-03 09:51 +0200]:
| Hi all,
| 
| I'm running this 1U server with a cd-RW-rom-drive.
| Every now and then the drive opens. Unfortunately it's a laptop
| sort of drive because it's in a 1U server, so it won't close by
| itself.
| 
| I was wondering if there's any standard proces running on FreeBSD that
| opens it; I haven't monitored it's behaviour closely because I don't
| have permanent access to the box.
| 
| There's no -eject option in any of my cdrecord cmds.
| 
| I'm running FreeBSD 4.8 with a cd0: Slimtype COMBO LSC-24081M 3M35
| Removable CD-ROM SCSI-0 device. McAfee is installed (for MailScanner).
| 
| I suppose it should be possible to lock the drive; the supportteam at
| CW where the box is hosted are getting a bit annoyed [they're
| considering superglue at this point].
| 
| Any suggestions as to why it opens and how this could be prevented
| [other than the Cable and Wireless-solution =:0] greatly appreciated!
| 
| Cheers,
| 
| Marko
| 
| 
| --
I had the similar prob. with my Creative IDE CDROM
drive. It was due to improper power supply to CDROM. The
connector attached to CDROM was faulty. I replaced SMPS
and it solved my problem.

Regards,
Shantanu

-- 
Want to see how much virtual memory you're using? Just type swapinfo to
be shown information about the usage of your swap partitions.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CDROM boot time fsck

2002-10-11 Thread Jerry McAllister

 
 Hello -
 
 I happened to reboot my server last night without a disk in one of the
 cdrom drives.  It caused the startup process to halt, dropping me to a
 shell prompt as it tried to fsck the volume.  Wasn't happy proceeding
 until I fed the drive a disk.  In my environment this is A Bad Thing;
 there may be a disk in there or not, I need the freaking server to come up
 and start running regardless.
 
 I checked my fstab, and the cdroms are listed thusly:
 
 /dev/acd0c  /cdrom  cd9660  ro,auto 0   0
 /dev/acd1c  /cdrom1 cd9660  ro,auto 0   0
 
 Looking at the man page, the last column indicates the fsck type, and 0 is
 supposed to mean that the device doesn't need to be checked during
 startup.  Am I doing something wrong, or is something broken?
 4.6.2-STABLE, BTW.

I think you also want to make it  'noauto'  rather than 'auto'.
With the auto, you are telling it to try and mount the device and
since there is no disk in, it can't.

jerry

 
 KeS
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM boot time fsck

2002-10-11 Thread Kevin Stevens



On Fri, 11 Oct 2002, Jerry McAllister wrote:

  I happened to reboot my server last night without a disk in one of the
  cdrom drives.  It caused the startup process to halt, dropping me to a
  shell prompt as it tried to fsck the volume.  Wasn't happy proceeding
  until I fed the drive a disk.  In my environment this is A Bad Thing;
  there may be a disk in there or not, I need the freaking server to come up
  and start running regardless.
 
  I checked my fstab, and the cdroms are listed thusly:
 
  /dev/acd0c  /cdrom  cd9660  ro,auto 0   0
  /dev/acd1c  /cdrom1 cd9660  ro,auto 0   0
 
  Looking at the man page, the last column indicates the fsck type, and 0 is
  supposed to mean that the device doesn't need to be checked during
  startup.  Am I doing something wrong, or is something broken?
  4.6.2-STABLE, BTW.

 I think you also want to make it  'noauto'  rather than 'auto'.
 With the auto, you are telling it to try and mount the device and
 since there is no disk in, it can't.

Hmm.  I thought of that, but realistically wouldn't you WANT your cdroms
to be automount for just that reason - they're removable media, for
pete's sake.  I'm coming from a Solaris background, where this is handled
completely differently.

I guess I'm looking for the best practice method.

KeS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM boot time fsck

2002-10-11 Thread Kevin Stevens


On Fri, 11 Oct 2002, Cliff Sarginson wrote:

/dev/acd0c  /cdrom  cd9660  ro,auto 0   0
/dev/acd1c  /cdrom1 cd9660  ro,auto 0   0
   
Looking at the man page, the last column indicates the fsck type, and 0 is
supposed to mean that the device doesn't need to be checked during
startup.  Am I doing something wrong, or is something broken?
4.6.2-STABLE, BTW.
  
   I think you also want to make it  'noauto'  rather than 'auto'.
   With the auto, you are telling it to try and mount the device and
   since there is no disk in, it can't.
 
  Hmm.  I thought of that, but realistically wouldn't you WANT your cdroms
  to be automount for just that reason - they're removable media, for
  pete's sake.  I'm coming from a Solaris background, where this is handled
  completely differently.
 
 No,no. Automount makes no sense at all, it means you have to have a
 CD in there, also what if you are using a CD without a filesystem on
 it ? E.g. one you have dd'ed something to.

Ok, then.  Thanks very much for the help, guys!

KeS



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM boot time fsck

2002-10-11 Thread Jerry McAllister

 
 
 On Fri, 11 Oct 2002, Cliff Sarginson wrote:
 
 /dev/acd0c  /cdrom  cd9660  ro,auto 0   0
 /dev/acd1c  /cdrom1 cd9660  ro,auto 0   0

 Looking at the man page, the last column indicates the fsck type, and 0 is
 supposed to mean that the device doesn't need to be checked during
 startup.  Am I doing something wrong, or is something broken?
 4.6.2-STABLE, BTW.
   
I think you also want to make it  'noauto'  rather than 'auto'.
With the auto, you are telling it to try and mount the device and
since there is no disk in, it can't.
  
   Hmm.  I thought of that, but realistically wouldn't you WANT your cdroms
   to be automount for just that reason - they're removable media, for
   pete's sake.  I'm coming from a Solaris background, where this is handled
   completely differently.
  
  No,no. Automount makes no sense at all, it means you have to have a
  CD in there, also what if you are using a CD without a filesystem on
  it ? E.g. one you have dd'ed something to.
 
 Ok, then.  Thanks very much for the help, guys!
 

CDs aren't necessarily mounted to use.  Only if they have a file system
are they mounted.  Otherwise they are read directly in some fashion 
(depending on what they are, data file, music, etc).   If you have auto
there, it means that it will try and mount a file system from that device
to whatever mount point you specify whenever a mount -a is done.   Since
there is often not a Cd with a file system on it in the drive you don't
want it to be auto.   You or your script or whatever you are using needs
to do the mount specifically when you know a Cd with file system is there.

It doesn't mean quite the same thing as autostart when you plug in a CD.

I seem to remember some sort of similar distinction made in Solaris too
though it has been quite a while and they like to have all these GUI
things in Solaris to prevent you from knowing what is going on so it
may not look like it any more.

jerry

 KeS
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM drive(s) suddenly gone

2002-09-18 Thread Kevin Oberman

 From: Weston M. Price [EMAIL PROTECTED]
 Date: Wed, 18 Sep 2002 00:43:01 +
 Sender: [EMAIL PROTECTED]
 
 Excellentmusic cd's work fine. My confusion on the subject sorry. Thanks
 for the help everyone

But nobody actually gave the complete answer, so some people will
continue to have some problems.

You know:
Don't mount music CDs!

You don't know that the device characteristics for ATAPI devices
changed in 4.6 and you need to delete /dev/acd0* and 
cd /dev; ./MAKEDEV acd0

You can check this with 'ls -l /dev/acd*' If the minor modes for the
'c' partition ar not 0 for acd0c and 8 for acd1c, you need to re-make
the devices.

Once this is done, you will be able to use /dev/acd0c as intended.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM drive(s) suddenly gone

2002-09-17 Thread Anish Mistry

On Tuesday 17 September 2002 06:04 pm, Weston M. Price wrote:
 Hello,
   I recently built a new kernel to incorporate sound on my machine. 
Everything 
 seemed to come off without a hitch, no problems whatsoever. I followed the 
 handbook and added a line to my custom kernel. 
 
 device pcm
 
 I purposely left out options PNPBIOS just to make sure everything went all 
 right to begin with
 
 After this I made sure to check everything to make sure all my system 
 functionality remained intactagain, there appeared to be no problems. 
 
 This evening I went to mount one of my cdrom drives and the machine kept 
 giving me a problem saying 
 
 cd9660: /dev/acd0c : Invalid Argument
 
Try mounting /dev/acd0a.  I ran into this problem a while ago.
 I checked /etc/fstab and the entry for both /cdrom and /cdrom1 remained the 
 same as before, they are as follows:
 
 /dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
 /dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0
 
 however, when I took a look a dmesg I found the following:
 
 dmesg | egrep acd
 acd0: CDROM LTN486S at ata1-master PIO4
 acd1: CD-RW HL-DT-ST CD-RW GCE-8240B at ata1-slave PIO4
 
 To tell the truth, really have no idea how this happened. Does anyone have 
any 
 ideas, and more importantly, how do I get the cdrom(s) back? I am running 
 FreeBSD 4.7-PRERELEASE. Thanks for anyhelp anyone can give me. 
 
 Weston
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 
 

-- 
Anish Mistry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM drive(s) suddenly gone

2002-09-17 Thread Weston M. Price

Well, mount /dev/acd0a does not work. Howerver, I did put in a data disk and 
it mounted fine with the command mount /cdrom. However, a music CD will not 
work. Is there some sort of special setting(s) I need to configure to mount 
music CD's? 

Thanks again. 

Weston

On Wednesday 18 September 2002 04:03 am, Anish Mistry wrote:
 On Tuesday 17 September 2002 06:04 pm, Weston M. Price wrote:
  Hello,
  I recently built a new kernel to incorporate sound on my machine.

 Everything

  seemed to come off without a hitch, no problems whatsoever. I followed
  the handbook and added a line to my custom kernel.
 
  device pcm
 
  I purposely left out options PNPBIOS just to make sure everything went
  all right to begin with
 
  After this I made sure to check everything to make sure all my system
  functionality remained intactagain, there appeared to be no problems.
 
  This evening I went to mount one of my cdrom drives and the machine kept
  giving me a problem saying
 
  cd9660: /dev/acd0c : Invalid Argument

 Try mounting /dev/acd0a.  I ran into this problem a while ago.

  I checked /etc/fstab and the entry for both /cdrom and /cdrom1 remained
  the same as before, they are as follows:
 
  /dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
  /dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0
 
  however, when I took a look a dmesg I found the following:
 
  dmesg | egrep acd
  acd0: CDROM LTN486S at ata1-master PIO4
  acd1: CD-RW HL-DT-ST CD-RW GCE-8240B at ata1-slave PIO4
 
  To tell the truth, really have no idea how this happened. Does anyone
  have

 any

  ideas, and more importantly, how do I get the cdrom(s) back? I am running
  FreeBSD 4.7-PRERELEASE. Thanks for anyhelp anyone can give me.
 
  Weston
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM drive(s) suddenly gone

2002-09-17 Thread Weston M. Price

And even weirderwhen I do put in a data cdit is mounted as

/dev/acd0c which according to dmesg doesn't even existsyet it is in the 
/dev directory structure. 

Weston

On Wednesday 18 September 2002 04:03 am, Anish Mistry wrote:
 On Tuesday 17 September 2002 06:04 pm, Weston M. Price wrote:
  Hello,
  I recently built a new kernel to incorporate sound on my machine.

 Everything

  seemed to come off without a hitch, no problems whatsoever. I followed
  the handbook and added a line to my custom kernel.
 
  device pcm
 
  I purposely left out options PNPBIOS just to make sure everything went
  all right to begin with
 
  After this I made sure to check everything to make sure all my system
  functionality remained intactagain, there appeared to be no problems.
 
  This evening I went to mount one of my cdrom drives and the machine kept
  giving me a problem saying
 
  cd9660: /dev/acd0c : Invalid Argument

 Try mounting /dev/acd0a.  I ran into this problem a while ago.

  I checked /etc/fstab and the entry for both /cdrom and /cdrom1 remained
  the same as before, they are as follows:
 
  /dev/acd0c  /cdrom  cd9660  ro,noauto   0   0
  /dev/acd1c  /cdrom1 cd9660  ro,noauto   0   0
 
  however, when I took a look a dmesg I found the following:
 
  dmesg | egrep acd
  acd0: CDROM LTN486S at ata1-master PIO4
  acd1: CD-RW HL-DT-ST CD-RW GCE-8240B at ata1-slave PIO4
 
  To tell the truth, really have no idea how this happened. Does anyone
  have

 any

  ideas, and more importantly, how do I get the cdrom(s) back? I am running
  FreeBSD 4.7-PRERELEASE. Thanks for anyhelp anyone can give me.
 
  Weston
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM drive(s) suddenly gone

2002-09-17 Thread Bob Johnson

On Tuesday 17 September 2002 08:10 pm, Weston M. Price appears to have 
written:
 And even weirderwhen I do put in a data cdit is mounted as

 /dev/acd0c which according to dmesg doesn't even existsyet it is
 in the /dev directory structure.


the c in acd0c says it is the c partition on acd0.  By default, 
the c partition is the entire disk.  So yes, if acd0 exists, acd0c 
exists.  And just because it is in /dev, doesn't mean it actually 
exists.  It just means that if it did exist, you would have a way 
to refer to it.

But you are confusing me.  I thought you couldn't mount your CDs?  
Are you having problems with data CDs, or only music CDs?

 Weston

 On Wednesday 18 September 2002 04:03 am, Anish Mistry wrote:
  On Tuesday 17 September 2002 06:04 pm, Weston M. Price wrote:
   Hello,
 I recently built a new kernel to incorporate sound on my
   machine.
 
  Everything
 
   seemed to come off without a hitch, no problems whatsoever. I
   followed the handbook and added a line to my custom kernel.
  
   device pcm
  
   I purposely left out options PNPBIOS just to make sure everything
   went all right to begin with
  
   After this I made sure to check everything to make sure all my
   system functionality remained intactagain, there appeared to
   be no problems.
  
   This evening I went to mount one of my cdrom drives and the
   machine kept giving me a problem saying
  
   cd9660: /dev/acd0c : Invalid Argument

Maybe something you changed had an effect on your device definitions.  
Try 
   cd /dev   
   sh ./MAKEDEV all

to rebuild all of your devices.

 
  Try mounting /dev/acd0a.  I ran into this problem a while ago.
 
   I checked /etc/fstab and the entry for both /cdrom and /cdrom1
   remained the same as before, they are as follows:
  
   /dev/acd0c  /cdrom  cd9660  ro,noauto   0
 0 /dev/acd1c  /cdrom1 cd9660  ro,noauto
 0   0

the /etc/fstab entry won't change unless you change it.  It doesn't 
get updated automatically.  I assume the mangled lines are caused 
by an email problem?

  
   however, when I took a look a dmesg I found the following:
  
   dmesg | egrep acd
   acd0: CDROM LTN486S at ata1-master PIO4
   acd1: CD-RW HL-DT-ST CD-RW GCE-8240B at ata1-slave PIO4
  
   To tell the truth, really have no idea how this happened. Does
   anyone have

What are you saying happened?  This looks normal to me.  You have 
two CD drives.  Your CDROM gets mounted as /cdrom, and your CD-RW 
gets mounted as /cdrom1

 
  any
 
   ideas, and more importantly, how do I get the cdrom(s) back? I am
   running FreeBSD 4.7-PRERELEASE. Thanks for anyhelp anyone can
   give me.

Start by rebuilding your devices, as above.If you can mount a data 
CD as root, then try it as a normal user.  If that works, then as far as 
I know, how you mount a music CD depends on what program you 
are using to play the music.  It might be expecting a link that isn't 
there, e.g. 
/dev/cdrom may need to point to /dev/acd0


- Bob

  
   Weston


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM drive(s) suddenly gone

2002-09-17 Thread Weston M. Price

No, I literally just got the data cd to work. Howerver, at this point music 
CD's will not mount. 

Weston

On Wednesday 18 September 2002 04:41 am, Bob Johnson wrote:
 On Tuesday 17 September 2002 08:10 pm, Weston M. Price appears to have

 written:
  And even weirderwhen I do put in a data cdit is mounted as
 
  /dev/acd0c which according to dmesg doesn't even existsyet it is
  in the /dev directory structure.

 the c in acd0c says it is the c partition on acd0.  By default,
 the c partition is the entire disk.  So yes, if acd0 exists, acd0c
 exists.  And just because it is in /dev, doesn't mean it actually
 exists.  It just means that if it did exist, you would have a way
 to refer to it.

 But you are confusing me.  I thought you couldn't mount your CDs?
 Are you having problems with data CDs, or only music CDs?

  Weston
 
  On Wednesday 18 September 2002 04:03 am, Anish Mistry wrote:
   On Tuesday 17 September 2002 06:04 pm, Weston M. Price wrote:
Hello,
I recently built a new kernel to incorporate sound on my
machine.
  
   Everything
  
seemed to come off without a hitch, no problems whatsoever. I
followed the handbook and added a line to my custom kernel.
   
device pcm
   
I purposely left out options PNPBIOS just to make sure everything
went all right to begin with
   
After this I made sure to check everything to make sure all my
system functionality remained intactagain, there appeared to
be no problems.
   
This evening I went to mount one of my cdrom drives and the
machine kept giving me a problem saying
   
cd9660: /dev/acd0c : Invalid Argument

 Maybe something you changed had an effect on your device definitions.
 Try
cd /dev
sh ./MAKEDEV all

 to rebuild all of your devices.

   Try mounting /dev/acd0a.  I ran into this problem a while ago.
  
I checked /etc/fstab and the entry for both /cdrom and /cdrom1
remained the same as before, they are as follows:
   
/dev/acd0c  /cdrom  cd9660  ro,noauto   0
  0 /dev/acd1c  /cdrom1 cd9660  ro,noauto
  0   0

 the /etc/fstab entry won't change unless you change it.  It doesn't
 get updated automatically.  I assume the mangled lines are caused
 by an email problem?

however, when I took a look a dmesg I found the following:
   
dmesg | egrep acd
acd0: CDROM LTN486S at ata1-master PIO4
acd1: CD-RW HL-DT-ST CD-RW GCE-8240B at ata1-slave PIO4
   
To tell the truth, really have no idea how this happened. Does
anyone have

 What are you saying happened?  This looks normal to me.  You have
 two CD drives.  Your CDROM gets mounted as /cdrom, and your CD-RW
 gets mounted as /cdrom1

   any
  
ideas, and more importantly, how do I get the cdrom(s) back? I am
running FreeBSD 4.7-PRERELEASE. Thanks for anyhelp anyone can
give me.

 Start by rebuilding your devices, as above.If you can mount a data
 CD as root, then try it as a normal user.  If that works, then as far as
 I know, how you mount a music CD depends on what program you
 are using to play the music.  It might be expecting a link that isn't
 there, e.g.
 /dev/cdrom may need to point to /dev/acd0


 - Bob

Weston

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM drive(s) suddenly gone

2002-09-17 Thread Greg Lane

 And even weirderwhen I do put in a data cdit is mounted as
 
 /dev/acd0c which according to dmesg doesn't even existsyet it is in the 
 /dev directory structure. 

This is the way it is supposed to work. 
The device in dmesg will be acd0, while it will be 
referred to when mounting (as in your fstab) as /dev/acd0c.

In a similar fashion, you will notice that your disk drives are 
detected (if IDE) as ad0, ad1 etc in dmesg, although in 
/etc/fstab they are listed by partition as /dev/ad0s1a etc when 
they are being mounted. 

The additional letter refers to the partition. For the cdrom,
the letter c refers to the whole disk.

Your initial confusion seems to be due to the fact that you were trying 
to mount a music cd. This is not what you do, you play music cd's.
You can use a variety of things to do this, from the basic, 
cdcontrol (see the man page), to the graphical interface
variety, e.g. xcdplayer in the ports. 

If you want to extract the music off the CD as a .wav file, you
don't mount the cd, you use a ripping tool, like cdda2wav (from 
the cdrtools port). 

Hope that makes more sense. 

Cheers,
Greg

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: CDROM drive(s) suddenly gone

2002-09-17 Thread Weston M. Price

Excellentmusic cd's work fine. My confusion on the subject sorry. Thanks 
for the help everyone

Weston

On Wednesday 18 September 2002 04:47 am, Greg Lane wrote:
  And even weirderwhen I do put in a data cdit is mounted as
 
  /dev/acd0c which according to dmesg doesn't even existsyet it is in
  the /dev directory structure.

 This is the way it is supposed to work.
 The device in dmesg will be acd0, while it will be
 referred to when mounting (as in your fstab) as /dev/acd0c.

 In a similar fashion, you will notice that your disk drives are
 detected (if IDE) as ad0, ad1 etc in dmesg, although in
 /etc/fstab they are listed by partition as /dev/ad0s1a etc when
 they are being mounted.

 The additional letter refers to the partition. For the cdrom,
 the letter c refers to the whole disk.

 Your initial confusion seems to be due to the fact that you were trying
 to mount a music cd. This is not what you do, you play music cd's.
 You can use a variety of things to do this, from the basic,
 cdcontrol (see the man page), to the graphical interface
 variety, e.g. xcdplayer in the ports.

 If you want to extract the music off the CD as a .wav file, you
 don't mount the cd, you use a ripping tool, like cdda2wav (from
 the cdrtools port).

 Hope that makes more sense.

 Cheers,
 Greg


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: /cdrom for normal users?

2002-07-19 Thread Brian T . Schellenberger

On Thursday 18 July 2002 02:54 pm, Steve Mazerski wrote:
| On Thursday 18 July 2002 20:09, Daniel Bye wrote:
|  On Thu, Jul 18, 2002 at 07:15:10AM -0700, Balaji, Pavan wrote:
|   By default, cdrom is /dev/acd0c is only mountable by root in FreeBSD.
|   You can make it mountable by normal users by changing the /etc/fstab
|   entry to users,ro,noauto
|  
|   /dev/acd0c  /cdrom  cd9660 users,ro,noauto   0
|   0
| 
|  Hmm, just edited my /etc/fstab to look like this, and I get a different
|  message:
| 
|  cd9660: -o users: option not supported

Right.  That's because you can't do that in FreeBSD.  I wish you could, too.
At least, it's never worked for me.


|  However, google brought me this:
| 
|  http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FLOP
| PY MOUNT

That's ok if you can live with users being able to mount only into their own 
directories, but I found that rather awkward.

I use op (from the ports/packages) to permit ordinary users to mount the 
cdrom.  This is a sort of super sudo command that you use to give limited 
or full access with or without passwords to various commands.

It means that ordinary users would mount with

   op mount /cdrom

rather than just 

   mount /cdrom.

Myself, I alias 

   mount

to 

   op mount

in my ordinary user profile.


-- 
Brian, the man from Babble-On . . . .   [EMAIL PROTECTED] (personal)
http://www.babbleon.org

http://www.eff.org  http://www.programming-freedom.org 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: /cdrom for normal users?

2002-07-18 Thread Balaji, Pavan


By default, cdrom is /dev/acd0c is only mountable by root in FreeBSD. You
can make it mountable by normal users by changing the /etc/fstab entry to
users,ro,noauto

/dev/acd0c  /cdrom  cd9660 users,ro,noauto   0   0

Pavan Balaji,
Intel Corporation

Only the Paranoid Survive  --  Andy Grove


 -Original Message-
 From: Steve Mazerski [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, July 17, 2002 5:14 PM
 To: [EMAIL PROTECTED]
 Subject: /cdrom for normal users?
 
 
 
 Is it the done thing in FreeBSD for normal users to mount CD-ROMs 
 in a local directory rather than /cdrom? 
 
 As a normal user all I get is this:
 
   localuser  mount /cdrom 
   cd9660: /dev/acd0c: Operation not permitted
 
 despite changing the permissions on both the CD-ROM device and /cdrom
 to 660 and ensuring the local user is in the relevant groups
 
 I can mount CD-ROMs in a directory owned by the normal user.
 
 I ask because in Linux, /cdrom is generally useable as a mount point
 by all users. It's not a problem, just wondering.
 
 For reference: 
 
 the relevant line in /etc/fstab:
 
   /dev/acd0c  /cdrom  cd9660  ro,noauto   
 0   0
 
 vfs.usermount is set to 1, and yes, I have read this page:
 
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.htm
l#USER-FLOPPYMOUNT


S.Mazerski


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: /cdrom for normal users?

2002-07-18 Thread Steve Mazerski

On Thursday 18 July 2002 20:09, Daniel Bye wrote:
 On Thu, Jul 18, 2002 at 07:15:10AM -0700, Balaji, Pavan wrote:
  By default, cdrom is /dev/acd0c is only mountable by root in FreeBSD. You
  can make it mountable by normal users by changing the /etc/fstab entry to
  users,ro,noauto
 
  /dev/acd0c  /cdrom  cd9660 users,ro,noauto   0  
  0

 Hmm, just edited my /etc/fstab to look like this, and I get a different
 message:

 cd9660: -o users: option not supported

That's what I got when I borrowed the relevent line from my Linux
/etc/fstab. Being a hopeless beginner I presumed this was a naive
error on my part and discretely forgot to mention it.

 However, google brought me this:

 http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FLOPPY
MOUNT

Thanks, but been there, done that (see my original mail).

So, what's up? At the moment things look like this?

localuser@localhost  uname -a
FreeBSD localhost.local 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Sun Jul 14 
17:14:44 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/KERNEL_1  
i386

(I recompiled the kernel for ext2fs support)

root# sysctl -a | fgrep vfs\.usermount
vfs.usermount: 1

localuser@localhost  ls -ld /cdrom
drwxrwxr-x  2 root  wheel  512 Jul 14 18:10 /cdrom
localuser@localhost  ls -l /dev/acd0c
crw-rw  4 root  operator  117,   0 Jul 14 18:15 /dev/acd0c
localuser@localhost  groups
localuser wheel operator
localuser@localhost  cat /etc/fstab | fgrep cdrom
/dev/acd0c  /cdrom  cd9660  ro,noauto,users 0   0
localuser@localhost  mount /cdrom 
cd9660: -o users: option not supported
localuser@localhost   mount -t cd9660 /dev/acd0c  ~/cdrom 
localuser@localhost   ls ~/cdrom
EULAREADME  RedHat  autorun
GPL RPM-GPG-KEY TRANS.TBL

(well, it was the first one I had to hand ;-)

Any ideas? Just wondering...
(I may of course be overlooking something).

S.Mazerski


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: /cdrom for normal users?

2002-07-18 Thread Adam Weinberger

there is no such parameter passable to mount called users. it needs to
be removed. if you can mount it from the command line, you should make
the fstab line agree with it, and i see no reason why it wouldn't then
work.

keep in mind that in your fstab, you are attempting to mount the CDROM
onto /cdrom. on the command-line, you mounted it onto ~/cdrom. does
localuser have permissions on /cdrom? what are those permissions right
now?

so, in fstab:
/dev/acd0c  /home/localuser/cdrom   cd9660  ro,noauto 0 0

should work fine.

change permissions on /cdrom and i'd assume:
/dev/acd0c  /cdrom  cd9660  ro,noauto 0 0

should work fine.

-Adam


 (07.18.2002 @ 1154 PST): Steve Mazerski said, in 2.1K: 
 On Thursday 18 July 2002 20:09, Daniel Bye wrote:
  On Thu, Jul 18, 2002 at 07:15:10AM -0700, Balaji, Pavan wrote:
   By default, cdrom is /dev/acd0c is only mountable by root in FreeBSD. You
   can make it mountable by normal users by changing the /etc/fstab entry to
   users,ro,noauto
  
   /dev/acd0c  /cdrom  cd9660 users,ro,noauto   0  
   0
 
  Hmm, just edited my /etc/fstab to look like this, and I get a different
  message:
 
  cd9660: -o users: option not supported
 
 That's what I got when I borrowed the relevent line from my Linux
 /etc/fstab. Being a hopeless beginner I presumed this was a naive
 error on my part and discretely forgot to mention it.
 
  However, google brought me this:
 
  http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FLOPPY
 MOUNT
 
 Thanks, but been there, done that (see my original mail).
 
 So, what's up? At the moment things look like this?
 
 localuser@localhost  uname -a
 FreeBSD localhost.local 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Sun Jul 14 
 17:14:44 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/KERNEL_1  
 i386
 
 (I recompiled the kernel for ext2fs support)
 
 root# sysctl -a | fgrep vfs\.usermount
 vfs.usermount: 1
 
 localuser@localhost  ls -ld /cdrom
 drwxrwxr-x  2 root  wheel  512 Jul 14 18:10 /cdrom
 localuser@localhost  ls -l /dev/acd0c
 crw-rw  4 root  operator  117,   0 Jul 14 18:15 /dev/acd0c
 localuser@localhost  groups
 localuser wheel operator
 localuser@localhost  cat /etc/fstab | fgrep cdrom
 /dev/acd0c  /cdrom  cd9660  ro,noauto,users 0   0
 localuser@localhost  mount /cdrom 
 cd9660: -o users: option not supported
 localuser@localhost   mount -t cd9660 /dev/acd0c  ~/cdrom 
 localuser@localhost   ls ~/cdrom
 EULAREADME  RedHat  autorun
 GPL RPM-GPG-KEY TRANS.TBL
 
 (well, it was the first one I had to hand ;-)
 
 Any ideas? Just wondering...
 (I may of course be overlooking something).
 
 S.Mazerski
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 
 end of Re: /cdrom for normal users? from Steve Mazerski 


--
Oh good, my dog found the chainsaw.
-Lilo, Lilo  Stitch
Adam Weinberger
[EMAIL PROTECTED]
http://vectors.cx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: /cdrom for normal users?

2002-07-18 Thread Steve Mazerski

On Thursday 18 July 2002 23:20, Adam Weinberger wrote:
 there is no such parameter passable to mount called users. it needs to
 be removed. if you can mount it from the command line, you should make
 the fstab line agree with it, and i see no reason why it wouldn't then
 work.

 keep in mind that in your fstab, you are attempting to mount the CDROM
 onto /cdrom. on the command-line, you mounted it onto ~/cdrom. does
 localuser have permissions on /cdrom? what are those permissions right
 now?

As posted in the prior mail:

  localuser@localhost  ls -ld /cdrom
  drwxrwxr-x  2 root  wheel  512 Jul 14 18:10 /cdrom
  localuser@localhost  ls -l /dev/acd0c
  crw-rw  4 root  operator  117,   0 Jul 14 18:15 /dev/acd0c
  localuser@localhost  groups
  localuser wheel operator

setting /etc/fstab with

  /dev/acd0c/cdrom  cd9660  ro,noauto 0 0

produces:

localuser@localhost  mount /cdrom
cd9660: /dev/acd0c: Operation not permitted

Am I missing something, or is something missing me? ;-)

S.Mazerski


  (07.18.2002 @ 1154 PST): Steve Mazerski said, in 2.1K: 
 
  On Thursday 18 July 2002 20:09, Daniel Bye wrote:
   On Thu, Jul 18, 2002 at 07:15:10AM -0700, Balaji, Pavan wrote:
By default, cdrom is /dev/acd0c is only mountable by root in FreeBSD.
You can make it mountable by normal users by changing the /etc/fstab
entry to users,ro,noauto
   
/dev/acd0c  /cdrom  cd9660 users,ro,noauto   0
0
  
   Hmm, just edited my /etc/fstab to look like this, and I get a different
   message:
  
   cd9660: -o users: option not supported
 
  That's what I got when I borrowed the relevent line from my Linux
  /etc/fstab. Being a hopeless beginner I presumed this was a naive
  error on my part and discretely forgot to mention it.
 
   However, google brought me this:
  
   http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FL
  OPPY MOUNT
 
  Thanks, but been there, done that (see my original mail).
 
  So, what's up? At the moment things look like this?
 
  localuser@localhost  uname -a
  FreeBSD localhost.local 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Sun Jul 14
  17:14:44 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/KERNEL_1
  i386
 
  (I recompiled the kernel for ext2fs support)
 
  root# sysctl -a | fgrep vfs\.usermount
  vfs.usermount: 1
 
  localuser@localhost  ls -ld /cdrom
  drwxrwxr-x  2 root  wheel  512 Jul 14 18:10 /cdrom
  localuser@localhost  ls -l /dev/acd0c
  crw-rw  4 root  operator  117,   0 Jul 14 18:15 /dev/acd0c
  localuser@localhost  groups
  localuser wheel operator
  localuser@localhost  cat /etc/fstab | fgrep cdrom
  /dev/acd0c  /cdrom  cd9660  ro,noauto,users 0   0
  localuser@localhost  mount /cdrom
  cd9660: -o users: option not supported
  localuser@localhost   mount -t cd9660 /dev/acd0c  ~/cdrom
  localuser@localhost   ls ~/cdrom
  EULAREADME  RedHat  autorun
  GPL RPM-GPG-KEY TRANS.TBL
 
  (well, it was the first one I had to hand ;-)
 
  Any ideas? Just wondering...
  (I may of course be overlooking something).
 
  S.Mazerski
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message
 
  end of Re: /cdrom for normal users? from Steve Mazerski 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: /cdrom for normal users?

2002-07-18 Thread Adam Weinberger

user localhost doesn't have access to read from /dev/acd0c.

-Adam


 (07.18.2002 @ 1245 PST): Steve Mazerski said, in 3.5K: 
 On Thursday 18 July 2002 23:20, Adam Weinberger wrote:
  there is no such parameter passable to mount called users. it needs to
  be removed. if you can mount it from the command line, you should make
  the fstab line agree with it, and i see no reason why it wouldn't then
  work.
 
  keep in mind that in your fstab, you are attempting to mount the CDROM
  onto /cdrom. on the command-line, you mounted it onto ~/cdrom. does
  localuser have permissions on /cdrom? what are those permissions right
  now?
 
 As posted in the prior mail:
 
   localuser@localhost  ls -ld /cdrom
   drwxrwxr-x  2 root  wheel  512 Jul 14 18:10 /cdrom
   localuser@localhost  ls -l /dev/acd0c
   crw-rw  4 root  operator  117,   0 Jul 14 18:15 /dev/acd0c
   localuser@localhost  groups
   localuser wheel operator
 
 setting /etc/fstab with
 
   /dev/acd0c  /cdrom  cd9660  ro,noauto 0 0
 
 produces:
 
 localuser@localhost  mount /cdrom
 cd9660: /dev/acd0c: Operation not permitted
 
 Am I missing something, or is something missing me? ;-)
 
 S.Mazerski
 
 
   (07.18.2002 @ 1154 PST): Steve Mazerski said, in 2.1K: 
  
   On Thursday 18 July 2002 20:09, Daniel Bye wrote:
On Thu, Jul 18, 2002 at 07:15:10AM -0700, Balaji, Pavan wrote:
 By default, cdrom is /dev/acd0c is only mountable by root in FreeBSD.
 You can make it mountable by normal users by changing the /etc/fstab
 entry to users,ro,noauto

 /dev/acd0c  /cdrom  cd9660 users,ro,noauto   0
 0
   
Hmm, just edited my /etc/fstab to look like this, and I get a different
message:
   
cd9660: -o users: option not supported
  
   That's what I got when I borrowed the relevent line from my Linux
   /etc/fstab. Being a hopeless beginner I presumed this was a naive
   error on my part and discretely forgot to mention it.
  
However, google brought me this:
   
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#USER-FL
   OPPY MOUNT
  
   Thanks, but been there, done that (see my original mail).
  
   So, what's up? At the moment things look like this?
  
   localuser@localhost  uname -a
   FreeBSD localhost.local 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Sun Jul 14
   17:14:44 CEST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/KERNEL_1
   i386
  
   (I recompiled the kernel for ext2fs support)
  
   root# sysctl -a | fgrep vfs\.usermount
   vfs.usermount: 1
  
   localuser@localhost  ls -ld /cdrom
   drwxrwxr-x  2 root  wheel  512 Jul 14 18:10 /cdrom
   localuser@localhost  ls -l /dev/acd0c
   crw-rw  4 root  operator  117,   0 Jul 14 18:15 /dev/acd0c
   localuser@localhost  groups
   localuser wheel operator
   localuser@localhost  cat /etc/fstab | fgrep cdrom
   /dev/acd0c  /cdrom  cd9660  ro,noauto,users 0   0
   localuser@localhost  mount /cdrom
   cd9660: -o users: option not supported
   localuser@localhost   mount -t cd9660 /dev/acd0c  ~/cdrom
   localuser@localhost   ls ~/cdrom
   EULAREADME  RedHat  autorun
   GPL RPM-GPG-KEY TRANS.TBL
  
   (well, it was the first one I had to hand ;-)
  
   Any ideas? Just wondering...
   (I may of course be overlooking something).
  
   S.Mazerski
  
  
   To Unsubscribe: send mail to [EMAIL PROTECTED]
   with unsubscribe freebsd-questions in the body of the message
  
   end of Re: /cdrom for normal users? from Steve Mazerski 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 
 end of Re: /cdrom for normal users? from Steve Mazerski 


--
Oh good, my dog found the chainsaw.
-Lilo, Lilo  Stitch
Adam Weinberger
[EMAIL PROTECTED]
http://vectors.cx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: /cdrom for normal users?

2002-07-18 Thread Steve Mazerski

On Friday 19 July 2002 00:15, Adam Weinberger wrote:
 user localhost doesn't have access to read from /dev/acd0c.

 -Adam

user localhost is in group operator, and /dev/acd0c
is readable by group operator:

  localuser@localhost  ls -l /dev/acd0c 
  crw-rw  4 root  operator  117,   0 Jul 14 18:15 /dev/acd0c

If I am missing something fundemental here, please say.

Setting /dev/acd0c to a+rw didn't make any difference.

vfs.usermount is set to 1, the CD-ROM works and I can
mount it in a directory _owned_ by localuser. I can
mount it on /cdrom if I chown it to localuser.


S.Mazerski


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message