Re: No cdrom device

[Charlie]

 On Thu, 29 Dec 2011 13:01:54 -0500 "edj...@gmail.com edj...@gmail.com"
 suggested this:

>On Thursday, December 29, 2011 11:39:45 AM Vincent Lefevre wrote:
>> > 
>> > No, it wasn't a hardware problem.  After much travail with udev,
>> > modprobe, interrupts, etc. and leariing more about dmesg output
>> > than I care to know, I thought - well, no sr0?  Then make one!
>> > 
>> > touch /dev/sr0
>> > chown root:disk /dev/sr0
>> > chmod 660 /dev/sr0
>> 
>> You shouldn't need to do that manually. There's something broken
>> on your system.
>
>Perhaps, but the device survives reboots,  so -- if all is well, then
>it is. 

After an upgrade a couple of weeks ago, had to change the
cdrom's from /dev/scd* to /dev/sr*

Have no idea why? However, leaving them as /dev/scd* they weren't
recognised.

Charlie
-- 

Registered Linux User:- 329524
***

In prosperity our friends know us; in adversity we know our friends.
 Churton Collins

***
Debian GNU/Linux - just the best way to create magic
___


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111230075308.06233acd@taowild

Re: No cdrom device

[edjabr]

On Thursday, December 29, 2011 11:39:45 AM Vincent Lefevre wrote:
> > 
> > No, it wasn't a hardware problem.  After much travail with udev,
> > modprobe, interrupts, etc. and leariing more about dmesg output than I
> > care to know, I thought - well, no sr0?  Then make one!
> > 
> > touch /dev/sr0
> > chown root:disk /dev/sr0
> > chmod 660 /dev/sr0
> 
> You shouldn't need to do that manually. There's something broken
> on your system.

Perhaps, but the device survives reboots,  so -- if all is well, then it is. 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201112291301.54809.edj...@gmail.com

Re: No cdrom device

[Vincent Lefevre]

On 2011-12-29 11:10:52 -0500, edj...@gmail.com wrote:
> On Wednesday, December 28, 2011 11:37:15 PM Bill Marcum wrote:
> > In gmane.linux.debian.user, you wrote:
> > > lshw output in my case has no *cdrom entry at all.  I rebooted, opened
> > > the tray manually, inserted a Knoppix disk and set the BIOS to boot off
> > > the cdrom drive.  No luck - booted from the hard drive.
> > 
> > That sounds like a hardware problem with the cdrom drive.
> 
> No, it wasn't a hardware problem.  After much travail with udev, modprobe, 
> interrupts, etc. and leariing more about dmesg output than I care to know, I 
> thought - well, no sr0?  Then make one!
> 
> touch /dev/sr0
> chown root:disk /dev/sr0
> chmod 660 /dev/sr0

You shouldn't need to do that manually. There's something broken
on your system.

-- 
Vincent Lefèvre  - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111229163945.gr5...@xvii.vinc17.org

Re: No cdrom device

[edjabr]

On Wednesday, December 28, 2011 11:37:15 PM Bill Marcum wrote:
> In gmane.linux.debian.user, you wrote:
> > lshw output in my case has no *cdrom entry at all.  I rebooted, opened
> > the tray manually, inserted a Knoppix disk and set the BIOS to boot off
> > the cdrom drive.  No luck - booted from the hard drive.
> 
> That sounds like a hardware problem with the cdrom drive.

No, it wasn't a hardware problem.  After much travail with udev, modprobe, 
interrupts, etc. and leariing more about dmesg output than I care to know, I 
thought - well, no sr0?  Then make one!

touch /dev/sr0
chown root:disk /dev/sr0
chmod 660 /dev/sr0

And that was that.  Sometimes the simplest, most obvious solution is the one 
that eludes us the most.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201112291110.53653.edj...@gmail.com

Re: No cdrom device

[Bill Marcum]

In gmane.linux.debian.user, you wrote:
>
> lshw output in my case has no *cdrom entry at all.  I rebooted, opened the 
> tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom 
> drive.  No luck - booted from the hard drive.  
>
That sounds like a hardware problem with the cdrom drive.

> Also,modprobe sr_modgave me sg0 in /dev (?).  mount /dev/sg0 
> /mnt/cdrom  gave  mount: /dev/sg0 is not a block device
>
>  This is getting  wierder and wierder.
>
>


-- 
"Never believe the attribution of a quotation you find on the Internet."
(George Bernard Shaw)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/E1Rg7jv-0005eG-Cy@lat.local

Re: No cdrom device

[Vincent Lefevre]

On 2011-12-24 09:58:43 -0600, Hugo Vanwoerkom wrote:
> On 12/23/2011 06:32 PM, Vincent Lefevre wrote:
> >Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).
> 
> I believe that was after a udev update. It showed up in the changelog.

Indeed:

udev (175-1) unstable; urgency=low
[...]
  * 50-udev-default.rules: removed the obsolete scd%n symlinks.
[...]
 -- Marco d'Itri   Fri, 18 Nov 2011 03:05:39 +0100

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111224163610.ga5...@xvii.vinc17.org

Re: No cdrom device

[Hugo Vanwoerkom]

On 12/23/2011 06:32 PM, Vincent Lefevre wrote:

On 2011-12-23 18:30:25 -0500, Wayne Topa wrote:

On 12/23/2011 03:38 PM, Wayne Topa wrote:

On 12/23/2011 12:18 PM, Ed Jabbour wrote:

CDROM tray will not respond to "eject":

[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block
device
eject: tried to use `/dev/scd0' as device name but it is no block device
eject: unable to find or open device for: `cdrom'
=


Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).



I believe that was after a udev update. It showed up in the changelog.

Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/jd4srj$h58$1...@dough.gmane.org

Re: No cdrom device

[Vincent Lefevre]

On 2011-12-23 20:14:32 -0500, Ed Jabbour wrote:
> On Friday, December 23, 2011 7:32:22 PM Vincent Lefevre wrote:
> >Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).
> 
> Why do I still get error msgs referring to scd0??

Perhaps because it is mentioned in /etc/fstab?

> > Running lshw *as root* says which /dev files can be used.
> > In my case:
> > 
> >*-cdrom
> > description: DVD-RAM writer
> > product: DVD+-RW TS-U633A
> > vendor: TSSTcorp
> > physical id: 1
> > bus info: scsi@1:0.0.0
> > logical name: /dev/cdrom
> > logical name: /dev/cdrw
> > logical name: /dev/dvd
> > logical name: /dev/dvdrw
> > logical name: /dev/sr0
> > version: D300
> > capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
> > configuration: ansiversion=5 status=nodisc
> > 
> > I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced
> > by something else.
> 
> lshw output in my case has no *cdrom entry at all.

Note: I recall that lshw must be run as root (if I run lshw as a
normal user, I don't get a *-cdrom entry either). Otherwise perhaps
your drive is not recognized.

> I rebooted, opened the tray manually, inserted a Knoppix disk and
> set the BIOS to boot off the cdrom drive. No luck - booted from the
> hard drive.
> 
> Also,modprobe sr_modgave me sg0 in /dev (?).  mount /dev/sg0 
> /mnt/cdrom  gave  mount: /dev/sg0 is not a block device
> 
>  This is getting  wierder and wierder.

Here I don't need "modprobe sr_mod". It is loaded automatically.

-- 
Vincent Lefèvre  - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111224114154.gf15...@xvii.vinc17.org

Re: No cdrom device

[Ed Jabbour]

On Friday, December 23, 2011 7:32:22 PM Vincent Lefevre wrote:

>Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).

Why do I still get error msgs referring to scd0??

> Running lshw *as root* says which /dev files can be used.
> In my case:
> 
>*-cdrom
> description: DVD-RAM writer
> product: DVD+-RW TS-U633A
> vendor: TSSTcorp
> physical id: 1
> bus info: scsi@1:0.0.0
> logical name: /dev/cdrom
> logical name: /dev/cdrw
> logical name: /dev/dvd
> logical name: /dev/dvdrw
> logical name: /dev/sr0
> version: D300
> capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
> configuration: ansiversion=5 status=nodisc
> 
> I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced
> by something else.

lshw output in my case has no *cdrom entry at all.  I rebooted, opened the 
tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom 
drive.  No luck - booted from the hard drive.  

Also,modprobe sr_modgave me sg0 in /dev (?).  mount /dev/sg0 
/mnt/cdrom  gave  mount: /dev/sg0 is not a block device

 This is getting  wierder and wierder.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201112232014.32945.e...@att.net

Re: No cdrom device

[Vincent Lefevre]

On 2011-12-23 18:30:25 -0500, Wayne Topa wrote:
> On 12/23/2011 03:38 PM, Wayne Topa wrote:
> >On 12/23/2011 12:18 PM, Ed Jabbour wrote:
> >>CDROM tray will not respond to "eject":
> >>
> >>[Fri Dec 23] edj:~$ eject
> >>eject: tried to use `/media/cdrom0' as device name but it is no block
> >>device
> >>eject: tried to use `/dev/scd0' as device name but it is no block device
> >>eject: unable to find or open device for: `cdrom'
> >>=

Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).

> >~$ dmesg |grep -A2 -B2 cdrom
> >[ 2.592157] sd 2:0:0:0: [sda] Attached SCSI disk
> >[ 2.640560] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2
> >cdda tray
> >[ 2.640634] cdrom: Uniform CD-ROM driver Revision: 3.20
> >[ 2.640848] sr 0:0:0:0: Attached scsi CD-ROM sr0
> >[ 2.704036] usb 4-1: new full speed USB device number 2 using ohci_hcd
> >
> >Which shows my cdrom is /dev/sd0
> 
> Woops ^^^ /dev/sr0  sorry
> >
> >I eject with:
> >eject /dev/sr0
> >
> >or with this line in my /etc/fstab
> >/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
> >
> >eject /media/cdrom0

Running lshw *as root* says which /dev files can be used.
In my case:

   *-cdrom
description: DVD-RAM writer
product: DVD+-RW TS-U633A
vendor: TSSTcorp
physical id: 1
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/dvd
logical name: /dev/dvdrw
logical name: /dev/sr0
version: D300
capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: ansiversion=5 status=nodisc

I've chosen to use /dev/cdrom in case /dev/sr0 would be replaced
by something else.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111224003222.ge15...@xvii.vinc17.org

Re: No cdrom device

[Wayne Topa]

On 12/23/2011 03:38 PM, Wayne Topa wrote:

On 12/23/2011 12:18 PM, Ed Jabbour wrote:

CDROM tray will not respond to "eject":

[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block
device
eject: tried to use `/dev/scd0' as device name but it is no block device
eject: unable to find or open device for: `cdrom'
=

Perhaps related, dmesg reveals:
==
6.720030] ata1: link is slow to respond, please be patient (ready=0)
[ 11.704028] ata1: device not ready (errno=-16), forcing hardreset
[ 16.900028] ata1: link is slow to respond, please be patient (ready=0)
[ 21.716029] ata1: SRST failed (errno=-16)
[ 26.912027] ata1: link is slow to respond, please be patient (ready=0)
[ 31.728027] ata1: SRST failed (errno=-16)
[ 36.924030] ata1: link is slow to respond, please be patient (ready=0)
[ 66.772029] ata1: SRST failed (errno=-16)
[ 71.800028] ata1: SRST failed (errno=-16)
[ 71.811047] ata1: reset failed, giving up
[ 71.811185] ata2: port disabled--ignoring
=

modprobe cdrom sr_mod:
==
FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686-
pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown
parameter (see dmesg)

728.919036] cdrom: Unknown parameter `sr_mod'
===

Nor will the tray open manually, except that it does if on reboot, I
push the
button before GRUB takes over. Running testing with the 3.1.0-1-686-pae
kernel, although the problem persists no matter which kernel I boot into.

Any advice, pointers, etc. appreciated.


Locate your cdrom with:

$dmesg |grep -A2 B2 cdrom

Which in my case returns;

~$ dmesg |grep -A2 -B2 cdrom
[ 2.592157] sd 2:0:0:0: [sda] Attached SCSI disk
[ 2.640560] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2
cdda tray
[ 2.640634] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.640848] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 2.704036] usb 4-1: new full speed USB device number 2 using ohci_hcd

Which shows my cdrom is /dev/sd0


Woops ^^^ /dev/sr0  sorry


I eject with:
eject /dev/sr0

or with this line in my /etc/fstab
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

eject /media/cdrom0

HTH

WT











--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4ef50f11.2000...@gmail.com

Re: No cdrom device

[Wayne Topa]

On 12/23/2011 12:18 PM, Ed Jabbour wrote:

CDROM tray will not respond to "eject":

[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block device
eject: tried to use `/dev/scd0' as device name but it is no block device
eject: unable to find or open device for: `cdrom'
=

Perhaps related, dmesg reveals:
==
6.720030] ata1: link is slow to respond, please be patient (ready=0)
[   11.704028] ata1: device not ready (errno=-16), forcing hardreset
[   16.900028] ata1: link is slow to respond, please be patient (ready=0)
[   21.716029] ata1: SRST failed (errno=-16)
[   26.912027] ata1: link is slow to respond, please be patient (ready=0)
[   31.728027] ata1: SRST failed (errno=-16)
[   36.924030] ata1: link is slow to respond, please be patient (ready=0)
[   66.772029] ata1: SRST failed (errno=-16)
[   71.800028] ata1: SRST failed (errno=-16)
[   71.811047] ata1: reset failed, giving up
[   71.811185] ata2: port disabled--ignoring
=

modprobe cdrom sr_mod:
==
FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686-
pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown
parameter (see dmesg)

728.919036] cdrom: Unknown parameter `sr_mod'
===

Nor will the tray open manually, except that it does if on reboot, I push the
button before GRUB takes over.   Running testing with the 3.1.0-1-686-pae
kernel, although the problem persists no matter which kernel I boot into.

Any advice, pointers, etc. appreciated.


Locate your cdrom with:

$dmesg |grep -A2 B2 cdrom

Which in my case returns;

~$ dmesg |grep -A2 -B2 cdrom
[2.592157] sd 2:0:0:0: [sda] Attached SCSI disk
[2.640560] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw 
xa/form2 cdda tray

[2.640634] cdrom: Uniform CD-ROM driver Revision: 3.20
[2.640848] sr 0:0:0:0: Attached scsi CD-ROM sr0
[2.704036] usb 4-1: new full speed USB device number 2 using ohci_hcd

Which shows my cdrom is /dev/sd0

I eject with:
eject /dev/sr0

or with this line in my /etc/fstab
/dev/sr0   /media/cdrom0   udf,iso9660 user,noauto 0   0

eject /media/cdrom0

HTH

WT









--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4ef4e6b1@gmail.com

Re: No cdrom device

[Raf Czlonka]

On Fri, Dec 23, 2011 at 05:18:47PM GMT, Ed Jabbour wrote:
> CDROM tray will not respond to "eject":
> 
> [Fri Dec 23] edj:~$ eject
> eject: tried to use `/media/cdrom0' as device name but it is no block device
> eject: tried to use `/dev/scd0' as device name but it is no block device
> eject: unable to find or open device for: `cdrom'
> =

Which device is you optical drive?

> Perhaps related, dmesg reveals:
> ==
> 6.720030] ata1: link is slow to respond, please be patient (ready=0)
> [   11.704028] ata1: device not ready (errno=-16), forcing hardreset
> [   16.900028] ata1: link is slow to respond, please be patient (ready=0)
> [   21.716029] ata1: SRST failed (errno=-16)
> [   26.912027] ata1: link is slow to respond, please be patient (ready=0)
> [   31.728027] ata1: SRST failed (errno=-16)
> [   36.924030] ata1: link is slow to respond, please be patient (ready=0)
> [   66.772029] ata1: SRST failed (errno=-16)
> [   71.800028] ata1: SRST failed (errno=-16)
> [   71.811047] ata1: reset failed, giving up
> [   71.811185] ata2: port disabled--ignoring
> =

Might be related, see below.

> modprobe cdrom sr_mod:
> ==
> FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686-
> pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown 
> parameter (see dmesg)

You're trying to load two modules (cdrom and sr_mod) and modprobe treats
the second one as a parameter to the first one.
You should load modules one by one.

> 728.919036] cdrom: Unknown parameter `sr_mod'

Which part of the above message is not clear? ;^)

> Nor will the tray open manually, except that it does if on reboot, I push the 
> button before GRUB takes over.   Running testing with the 3.1.0-1-686-pae  
> kernel, although the problem persists no matter which kernel I boot into.
> 
> Any advice, pointers, etc. appreciated.

The above dmesg messages might point to faulty drive or cable.
Does the optical drive work at all, e.g. under another OS?

Regards,
-- 
Raf


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111223174823.ga18...@linuxstuff.pl

No cdrom device

[Ed Jabbour]

CDROM tray will not respond to "eject":

[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block device
eject: tried to use `/dev/scd0' as device name but it is no block device
eject: unable to find or open device for: `cdrom'
=

Perhaps related, dmesg reveals:
==
6.720030] ata1: link is slow to respond, please be patient (ready=0)
[   11.704028] ata1: device not ready (errno=-16), forcing hardreset
[   16.900028] ata1: link is slow to respond, please be patient (ready=0)
[   21.716029] ata1: SRST failed (errno=-16)
[   26.912027] ata1: link is slow to respond, please be patient (ready=0)
[   31.728027] ata1: SRST failed (errno=-16)
[   36.924030] ata1: link is slow to respond, please be patient (ready=0)
[   66.772029] ata1: SRST failed (errno=-16)
[   71.800028] ata1: SRST failed (errno=-16)
[   71.811047] ata1: reset failed, giving up
[   71.811185] ata2: port disabled--ignoring
=

modprobe cdrom sr_mod:
==
FATAL: Error inserting cdrom (/lib/modules/3.1.0-1-686-
pae/kernel/drivers/cdrom/cdrom.ko): Unknown symbol in module, or unknown 
parameter (see dmesg)

728.919036] cdrom: Unknown parameter `sr_mod'
===

Nor will the tray open manually, except that it does if on reboot, I push the 
button before GRUB takes over.   Running testing with the 3.1.0-1-686-pae  
kernel, although the problem persists no matter which kernel I boot into.

Any advice, pointers, etc. appreciated.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201112231218.47633.e...@att.net

Re: floppy install on 486dx/33 w/ no CDROM

[FGL]

On Tue, Nov 20, 2001 at 12:12:05PM -0500, [EMAIL PROTECTED] wrote:
> 
> I have done a base installation from floppies.  Is there a
> step-by-step somewhere for dialing up my ISP from a 
> console, and then proceeding with the installation from
> debian.org??

Very simple. You need to have ppp installed. As root run pppconfig
and create a provider profile by answering the questions about the
phone number to dial, the serial port to use, etc.

Assuming that you named your provider 'abc', you get online by
typing

pon abc

on the command line. To proceed with the rest of the installation
use the command

dselect

and go through the numbered menu items in sequence.

After leaving dselect, get offline with the command

poff

FGL

Re: floppy install on 486dx/33 w/ no CDROM

[mdt1]

 To:
   
  debian 

 > I installed my first Debian (2.1) with floppies back in 1999.

Congratulations!!  I am now trying also, on a laptop.

> For installing the rest of the programs you want, that might be a
good 
> idea, but there are other means to get them into your box, ppp or >
>ethernet
> comes to mind.

> good luck,

> Hans Ekbrand

I have done a base installation from floppies.  Is there a
step-by-step somewhere for dialing up my ISP from a 
console, and then proceeding with the installation from
debian.org??

Thanks in advance,

dave

Re: floppy install on 486dx/33 w/ no CDROM

[Hans Ekbrand]

On Mon, Nov 19, 2001 at 01:34:55PM -0800, Chris Nestor wrote:
> I'm trying to do an install on a 486dx/33 w/ no CDROM, using 3.5" floppies.  
> I did a rawrite2 of resc1440.bin to boot and repartition.  When it came time 
> for the kernel
> install, I can't find the requisite files.  It asks for a rescue floppy, 
> which I thought this was, but the installer is asking for other media.  I 
> have read of a drivers floppy (drv1440.bin) and some base file floppies 
> (base14-1.bin, ...14-2.bin, etc. on thru 14-7.bin), but can't find them on 
> the CD which accompanied the O'Reilly GNU/Linux book I picked up.  This is 
> kernel 2.0.36, which I realize is kinda old, but so is my system.  I just 
> want a dedicated linux box that I can poke around on and get command happy, 
> and all for now.  
> 

I installed my first Debian (2.1) with floppies back in 1999.

The drivers floppy contains kernel-modules that you may or may not need,
depending on your hardware. Get it.

The base floppies contains the most essential files in a Debian GNU/Linux
system. Get them.

> I went to the Debian.org site, tried an ftp site, but got messages saying I 
> didn't have "permission".  

The number of base floppies (7) and the kernel version (2.0.36) indicates
that you are trying to install Debian 2.1 (slink), but the standard mirrors
don't keep slink anymore, and the archives (for info on the archives see 
http://www.debian.org/distrib/archive), do not respond (they never
do for me, it seems).

But there is still hope, I found slink still alive at

http://ftp2.de.debian.org/debian-archive/dists/slink/main/disks-i386/2.1.12-1999-12-09/

> I guess I could go and get a CDROM and try an install that way, but don't 
> think the BIOS is up to that (AMI circa 1993).
> 

For installing the rest of the programs you want, that might be a good 
idea, but there are other means to get them into your box, ppp or ethernet
comes to mind.

good luck,

Hans Ekbrand

floppy install on 486dx/33 w/ no CDROM

[Chris Nestor]

I'm trying to do an install on a 486dx/33 w/ no 
CDROM, using 3.5" floppies.  I did a rawrite2 of resc1440.bin to boot and 
repartition.  When it came time for the kernel
install, I can't find the requisite files.  It 
asks for a rescue floppy, which I thought this was, but the installer is asking 
for other media.  I have read of a drivers floppy (drv1440.bin) and some 
base file floppies (base14-1.bin, ...14-2.bin, etc. on thru 14-7.bin), but can't 
find them on the CD which accompanied the O'Reilly GNU/Linux book I picked 
up.  This is kernel 2.0.36, which I realize is kinda old, but so is my 
system.  I just want a dedicated linux box that I can poke around on and 
get command happy, and all for now.  
 
I went to the Debian.org site, tried an ftp site, 
but got messages saying I didn't have "permission".  
 
I guess I could go and get a CDROM and try an 
install that way, but don't think the BIOS is up to that (AMI circa 
1993).
 
Trolling about for ideas,
Chris Nestor
[EMAIL PROTECTED]

Re: debian from scratch? no CDROM. How to?

[Ian Stuart]

On Monday 12 February 2001  5:26 pm, Robert Cymbala wrote:
> Two educational guides come to mind:
>
> 1.
> Go to  http://www.linuxdoc.org/LDP/
> Choose the "lfs" folder
> Choose the "LFS" folder
>
> This book describes the process of creating your own Linux system from
> scratch from an already installed Linux distribution, using nothing
> but the sources of software that are needed.
>
> 2.
> http://www.netspace.net.au/~gok/power2bash/
>
> Welcome to the home page of From Power Up To Bash Prompt. The current
> version is 0.9, and was uploaded on 5 November 2000.
3)

Download the boot-floppies :)

-- 
   --==**==--
Ian Stuart - EdINA, DataLibrary, University computing services.
-
Truth is what you believe it to be.
  I cannot force my facts on you, only make you believe my beliefs.
-
http://lucas.ucs.ed.ac.uk/

Re: debian from scratch? no CDROM. How to?

[Robert Cymbala]

Two educational guides come to mind:

1.
Go to  http://www.linuxdoc.org/LDP/
Choose the "lfs" folder
Choose the "LFS" folder

This book describes the process of creating your own Linux system from
scratch from an already installed Linux distribution, using nothing
but the sources of software that are needed.

2.
http://www.netspace.net.au/~gok/power2bash/

Welcome to the home page of From Power Up To Bash Prompt. The current
version is 0.9, and was uploaded on 5 November 2000.

---
I'd love to have the time to go through those real thoroughly...
---


--- [EMAIL PROTECTED] wrote:
> For my own education, I would like to start with a minimal linux
> ...
> Is there a step-by-step written for newbies about how to get started with 
> recover operation??
> 
> TIA,
> 
> dave



=
---

__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

debian from scratch? no CDROM. How to?

[DTi4565459]

For my own education, I would like to start with a minimal linux like 
CClinux.  Then add a terminal (like the old Win3.1 terminal) so I can dial to 
ISP. 

Then lynx to the Debian ftp site.   And then start to build a system that 
would include X, KDE, a dial-up networking connection, and finally Netscape.  

I know, your first thought is why doesn't the newbie get an easy install 
CDROM.  Well, I've done that on some desktops; but I want to do it now on a 
laptop where the ext PCMCIA CDROM keeps crashing the kernel.  At one time the 
external EXP CDROM was working, but recently there is some kind of packet 
error that hangs Debian Linux in the middle of boot from hard drive.  Is 
there a way to start boot from lilo with instruction NOT to try to mount the 
cdrom (i think it was treating it as /dev/hdc)?  Presently, I have 
reinstalled from rescue and root floppies, plus 3 module floppies, and 11 
base floppies.  But, even this system won't boot because of CDROM errors.  
Even if I pull PCMCIA card out, still hangs.  So, it looks like I've got to 
go back to booting a single floppy like CClinux.  That will work.  But, I 
can't figure out how to reach the file system that was installed with the 
Debian install.

Is there a step-by-step written for newbies about how to get started with 
recover operation??

TIA,

dave

Re: OT: no cdrom audio from sound card line out

[Jürgen A. Erhard]

Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> "Mark" =3D=3D Mark Schiltz <[EMAIL PROTECTED]> writes:

Mark> On Mon, 18 Sep 2000, David Z. Maze wrote:
>> Mark Schiltz <[EMAIL PROTECTED]> writes:
MS> I think I have tried everything, maybe my sound card is not fully
MS> supported? I have a motherboard with built-in soundpro
MS> (CMI8330). The sound is working with the exception of the cd
MS> audio. I know the cd is working because I can use the phone plug
MS> on the face of the cdrom.
>>=20
>> Two thoughts:
>>=20
>> (1) Is there a cable inside the computer connecting the CD-ROM to the
>> sound card?

Mark> Yes

>> (2) Run a Linux mixer program.  Is the CD audio volume non-zero?  Is
>> the master volume non-zero?

Mark> I have tried many different mixers.

Mark> This is a dual boot machine and cd audio works in the other (W98)=
 system.
Mark> I guess I should just get a new sound card.

What do you use to start the CD playing?  I found out my newly
installed SCSI CD was not properly supported by cdtool and
dcd... cdtool's cdplay can't start it, whereas dcd can... but dcd
doesn't show it playing when it actually does, whereas cdtool's cdinfo
shows it as playing.

Weird.  Maybe it's the same with your stuff... try different players
(if you haven't already).

HTH,

Bye, J

--=20
J=FCrgen A. Erhard[EMAIL PROTECTED]   phone: (GERMANY) 0721 27326
  My WebHome: http://members.tripod.com/Juergen_Erhard
  Linux - Free PC Unix (http://www.linux.org)
Comes in two sizes: huge and Oh-My-God.


pgpTDDomgwF1F.pgp
Description: PGP signature

Re: OT: no cdrom audio from sound card line out

[Mike Werner]

Mark Schiltz wrote:
> I think I have tried everything, maybe my sound card is not fully supported? I
> have a motherboard with built-in soundpro (CMI8330). The sound is working with
> the exception of the cd audio. I know the cd is working because I can use the
> phone plug on the face of the cdrom.
> 
> Any Ideas?

This might sound like a dumb sugesstion, but did you double check the cable
that goes from the CD drive to the soundcard?  I forgot all about that cable
once - took me most of a week before I thought to check it.  The cable was
still sitting in my parts box.  Another time I had a bad cable - one of the
leads was broken internally.

Second thing I would do is fire up a mixer-type program and see what the CD
audio level is set to.  It just might be set all the way down.  The Ensoniq
Soundscape I have in this machine was a bit of a pain in the ass that way
for a while.
-- 
Mike Werner  KA8YSD   | He that is slow to believe anything and
  | everything is of great understanding,
'91 GS500E| for belief in one false principle is the
Morgantown WV | beginning of all unwisdom.



pgpgltASPPBSd.pgp
Description: PGP signature

Re: OT: no cdrom audio from sound card line out

[Mark Schiltz]

On Mon, 18 Sep 2000, David Z. Maze wrote:
> Mark Schiltz <[EMAIL PROTECTED]> writes:
> MS> I think I have tried everything, maybe my sound card is not fully
> MS> supported? I have a motherboard with built-in soundpro
> MS> (CMI8330). The sound is working with the exception of the cd
> MS> audio. I know the cd is working because I can use the phone plug
> MS> on the face of the cdrom.
> 
> Two thoughts:
> 
> (1) Is there a cable inside the computer connecting the CD-ROM to the
> sound card?

Yes

> (2) Run a Linux mixer program.  Is the CD audio volume non-zero?  Is
> the master volume non-zero?

I have tried many different mixers.

This is a dual boot machine and cd audio works in the other (W98) system.
I guess I should just get a new sound card.

-- 
I'm here to paint but I've forgotten my brush...
You got beer?

Mark Schiltz

Re: OT: no cdrom audio from sound card line out

[David Z. Maze]

Mark Schiltz <[EMAIL PROTECTED]> writes:
MS> I think I have tried everything, maybe my sound card is not fully
MS> supported? I have a motherboard with built-in soundpro
MS> (CMI8330). The sound is working with the exception of the cd
MS> audio. I know the cd is working because I can use the phone plug
MS> on the face of the cdrom.

Two thoughts:

(1) Is there a cable inside the computer connecting the CD-ROM to the
sound card?

(2) Run a Linux mixer program.  Is the CD audio volume non-zero?  Is
the master volume non-zero?

-- 
David Maze [EMAIL PROTECTED]  http://www.mit.edu/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
-- Abra Mitchell

OT: no cdrom audio from sound card line out

[Mark Schiltz]

I think I have tried everything, maybe my sound card is not fully supported? I
have a motherboard with built-in soundpro (CMI8330). The sound is working with
the exception of the cd audio. I know the cd is working because I can use the
phone plug on the face of the cdrom.

Any Ideas?

 -- 
I'm here to paint but I've forgotten my brush...
You got beer?

Mark Schiltz

no cdrom

[Elaina Tillinghast]

Any hints for the stpid?

I have the linux central official debain 2.0binary i36 cd with kernel
2.0.34. It boots. When I get to the "install kernel..." option, it
can't find the cd and hints that I should try iinsmod. "insmod cdrom"
doesn't work. I've added a /cdrom directory and "mount -t iso9660
/dev/scd0 /cdrom" doesn't. My cd was found as /dev/scd0 before trying
to put the new version on. 

I went around in circles trying to mount my cd or get the insmod to
find a module when somehow the cd mounted and I could proceed. The
base2 image on the cd is bad. I now seem unable to reproduce the
mounting miracle. I had intended to dd the files to floppy and I hope
to find a valid base2 somewhere. 

Elaina

no cdrom

[Chris Tipney]

Thanks to all those who answered my call on the missing CDROM, I followed
the advice and it now works fine - briallant! It must have been an easy
question everyone came up with the same answer!

Cheers,

Chris Tipney
Hungerford, Berkshire, England

Re: no CDROM

[William Chow]

On Thu, 6 Mar 1997, Chris Tipney wrote:

> Dear all,
> 
> I have just finished installing Debian fron the CD that came with Linux
> World issue 1 it works fine but doesn't find my Aztech IDE CDROM drive.
> 
> During boot the following lines appear...
> 
> hdb: CDA286031 SE, ATAPI CDROM drive
> ide0 at 0x1f0-0x1f7, 0x3f6 on IRQ14
Uh, what do think the two lines mean? An IDE CDROM hangs off the IDE
controller, so hdb is your cdrom.

> 
> The boot up then goes through various CDROM types withput finding one present.
That's cuz it's already been detected. These CDROMs aren't IDE, they're
proprietary CDROM types used on older systems. 
> 
> My system is Pentium 120 using DPT scsi with Debian on it's own drive
> (/dev/sdb1 and /dev/sdb2). I have disabled all mention of IDE hard drives in
> the BIOS. 
> 
> I am able to 'mount' a file system of type 'proc' on /dev/hda but I'm not
> sure of what this means - yet. (this is my first real try at Unix etc).
You have to mount the cdrom on /dev/hdb to access it. Then you can use
dselect to point at it. Debian should've automatically configured your
cd-rom to be mounted during bootup, but it is being detected.

> 
> I need access to the CD to install the packages.
> 
> Any help gratefully received,
> 
> Regards,
> 
> Chris 
> 
> 
> 
> 

Re: no CDROM

[Heikki Vatiainen]

Hi,

I'm not sure I correctly understood everything so please correct me if I'm 
wrong:

 o You have made the six install floppies
 o You used one of the floppies to boot 
 o The base system got installed and the computer was rebooted
 o You now want to install the rest of the system but haven't used the dselect
   program which helps you to select and install the rest of the packages

If this is true, login as user 'root' and type 'dselect'. This will ask for 
the install media, cdrom for you, I used ftp, and mount the cdrom for you.

For the boot lines, here's what I have:

hdd: FX810T4, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15

You can try mounting your cdrom by first making the mount directory 'mkdir 
/mnt/cdrom' and then issuing command 'mount -t iso9660 /dev/hdb /mnt/cdrom'. 
Now if you cd to /mnt/cdrom you should be able to access the files on your 
cdrom. See also the Debian FAQ which tells about dselect and installing from a 
CD-ROM http://www.debian.org/FAQ/. http://www.buoy.com/debian/guide.html has 
the info for beginners about the dselect program.

I'm not sure what you mean by mounting 'proc' file system on /dev/hda since 
the 'proc' file system is not a real filesystem but a pseudo filesystem which 
contains files that actually contain information on your system. The files in 
the 'proc' file system do _not_ take any space on the disk.

I have no idea how Debian was distributed with the Linux World, I made my 
install by ftp.

Please feel free to mail me, but please elaborate more your current situation.

Chris Tipney wrote:
> Dear all,
> 
> I have just finished installing Debian fron the CD that came with Linux
> World issue 1 it works fine but doesn't find my Aztech IDE CDROM drive.
> 
> During boot the following lines appear...
> 
> hdb: CDA286031 SE, ATAPI CDROM drive
> ide0 at 0x1f0-0x1f7, 0x3f6 on IRQ14
> 
> The boot up then goes through various CDROM types withput finding one present.
> 
> My system is Pentium 120 using DPT scsi with Debian on it's own drive
> (/dev/sdb1 and /dev/sdb2). I have disabled all mention of IDE hard drives in
> the BIOS. 
> 
> I am able to 'mount' a file system of type 'proc' on /dev/hda but I'm not
> sure of what this means - yet. (this is my first real try at Unix etc).
> 
> I need access to the CD to install the packages.

// Heikki
-- 
Heikki Vatiainen  * [EMAIL PROTECTED]
Tampere University of Technology  * Tampere, Finland

no CDROM

[Chris Tipney]

Dear all,

I have just finished installing Debian fron the CD that came with Linux
World issue 1 it works fine but doesn't find my Aztech IDE CDROM drive.

During boot the following lines appear...

hdb: CDA286031 SE, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7, 0x3f6 on IRQ14

The boot up then goes through various CDROM types withput finding one present.

My system is Pentium 120 using DPT scsi with Debian on it's own drive
(/dev/sdb1 and /dev/sdb2). I have disabled all mention of IDE hard drives in
the BIOS. 

I am able to 'mount' a file system of type 'proc' on /dev/hda but I'm not
sure of what this means - yet. (this is my first real try at Unix etc).

I need access to the CD to install the packages.

Any help gratefully received,

Regards,

Chris