Linux-Hardware Digest #844, Volume #10           Sun, 25 Jul 99 13:13:30 EDT

Contents:
  Re: NEC SuperScript 1800 w/PostScript level 2 (Daniel Buettner)
  Logitech Trackman Marble FX? ("Peter A. Koren")
  STB Velocity 3D Black Screen & Mouse Pointer (Mario Cosenza)
  Re: How do I change SCSI cards in Red Hat 6.0? (Jon Bloom)
  cdrecord error (Matt Garman)
  Re: Modem Question (Abdullah Ramazanoglu)
  Advice on Linux and LS-120 drive? ("Steve Snyder")

----------------------------------------------------------------------------

From: Daniel Buettner <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux
Subject: Re: NEC SuperScript 1800 w/PostScript level 2
Date: 20 Jul 1999 15:18:00 GMT

Carlos Wexler <[EMAIL PROTECTED]> wrote:
> Hi everyone!
>
> I am looking to buy a postscript laser printer and found a printer with
> very nice specifications for a nice price:  
>
> NEC SuperScript 1800 (about $770 at PCConnection)
> ====================
> 1200dpi (not that I can see the difference w/r/t 600...) 
> 17 ppm (manufacturer's claims...)
> PCL5/6 and PostScript Level 2 (additional ~$110)
> Duplex  (nice feature! lets save some trees...)
>
> Claims to be compatible with Windoze/DOS and Mac (with the PS kit and an
> optional mac interface)
>
> Will it work with Linux?  It should, right?  After all it is PostScript...
I see no reason why it wouldn't work.  Since it says it works with DOS,
you can be fairly certain that it is a "real" printer.

> But will I know the escape sequences to make it print either in duplex or
> simplex mode?
Depending on how "nice" the printer is, you can probably set this feature
on its control panel.  I have a Lexmark Optra that I use under linux.  To
configure paper source/paper size I use the printer's control panel, since
I have no software to control this under linux.  With this printer, any of
the settings available in the properties dialog in windows can also be 
manually set with the control panel on the printer.  But I don't know how
featureful the NEC is if you don't use their software.


> How reliable are NEC printers? (I was going to get an HP 2100 w/PS for
> about the same price, but no duplexing)
I have never used an NEC printer, so I can't say for certain.  The printer
I have, a Lexmark Optra 1620, is available for about the same price as well.

It is 1200 dpi
16ppm (although I think that is only for 600dpi and 1200dpi 
       "quality" -- true 1200 dpi is slower, but I just use 600dpi)
PCL mumble
PS level 2 

It doesn't come with duplexing capabilities, but an add-on module can
be ordered from Lexmark, if it is that important.  I have had no
problems with this printer (other than windows re-detecting it all the
time, since I installed the PS drivers under windows but windows thinks
it should really be a PCL printer).


HTH,
-- 
~
~
~
"Daniel Buettner" line 4 of 4 --100%--

------------------------------

From: "Peter A. Koren" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Logitech Trackman Marble FX?
Date: Sun, 25 Jul 1999 10:24:31 -0500

Is the Logitech Trackman Marble FX supported under Linux? I am
considering this one because it "seems" to be comfortable to use for at
least the short while I got to try it in a store.

Thanks,

Peter Koren

--
remove the .zap-this from the email address to reach me.




------------------------------

From: Mario Cosenza <[EMAIL PROTECTED]>
Subject: STB Velocity 3D Black Screen & Mouse Pointer
Date: Sun, 25 Jul 1999 15:19:01 GMT

Using the X SVGA driver I can only get a black screen and a mouse
pointer when I set the resolution higher than 320x200. Everything else
works (if I click blindly) I just can't see.

VGA16 is the only other driver that works (but it's ugly). I have tried
S3 & S3V also with no luck.

Any ideas?

Oh yeah, I've got the following...

STB Velocity 3D (Virge VX) (from Gateway 2000, are these cards
'stripped' down?)
RedHat 6.0
XFree86-3.3.3.1-52 (the update after the RedHat 6.0 release)

Thanks.


------------------------------

From: Jon Bloom <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: How do I change SCSI cards in Red Hat 6.0?
Date: Sun, 25 Jul 1999 11:20:08 -0400

David Koretzky wrote:
> 
> Anthony Valentine wrote:
> >
> > I currently use and Advansys SCSI card (which works fine) but I woulf
> > like to upgrade it to an Adaptec  2940UW.  The aic7xxx.o module supports
> > the Adaptec card, but I cannot get Red Hat to load this module on boot.
> 
> You have to recompile the kernel with support for the Adaptec as a
> module.

No, the kernel distributed with RH 6.0 already has that and the other
needed support. (I wish people would stop telling newbies to recompile
their kernel when the newbie has specified use of a distro that already
has the needed kernel config. Why chase someone away from Linux by
making things seem harder than they are?)

[Snipped accurate description of making/using initrd.]

Jon
--
Jon Bloom, KE3Z
[EMAIL PROTECTED]
Electronic Publications Manager (Software, CD-ROMs and Web site)

------------------------------

From: [EMAIL PROTECTED] (Matt Garman)
Crossposted-To: comp.os.linux.misc
Subject: cdrecord error
Date: 25 Jul 1999 05:35:57 GMT
Reply-To: [EMAIL PROTECTED]

Hello:

I'm using Debian 2.1 Linux, trying to burn CDs using cdrecord v1.6
(the Debian packaged one) and a internal Plextor PlexWriter 4/12 SCSI
cd burner.

Initially, it worked perfectly, always.  Recently, though, it's been
coming up with random errors.  These errors may not come up on a dummy 
write, but will happen when I try to do the actual burn.  Sometimes
the errors show up on the dummy burn, too.

Here is a script output of me doing a few dummy burns:

Script started on Sat Jul 24 23:47:51 1999
sh-2.01# nice -n -20 cdrecod rd -v speed=4 dev=0,4,0 -audio -dummy *.wav
Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling
TOC Type: 0 = CD-DA
scsidev: '0,4,0'
scsibus: 0 target: 4 lun: 0
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   : SYNC LINKED 
Vendor_info    : 'PLEXTOR '
Identifikation : 'CD-R   PX-R412C '
Revision       : '1.04'
Device seems to be: Generic mmc CD-R.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : SWABAUDIO
Track 01: audio  53 MB (05:18.02) no preemp
Track 02: audio  38 MB (03:49.20) no preemp
Track 03: audio  80 MB (07:56.21) no preemp
Track 04: audio  47 MB (04:43.72) no preemp
Track 05: audio  54 MB (05:21.96) no preemp
Total size:     275 MB (27:17.12) = 122784 sectors
Lout start:     275 MB (27:19/09) = 122784 sectors
ATIP info from disk:
  Indicated writing power: 4
  Is unrestricted
  Is not erasable
  ATIP start of lead in:  -11580 (97:27/45)
  ATIP start of lead out: 333226 (74:05/01)
Disk type: Phthalocyanine or similar
Manufacturer: Kodak Japan Limited
Blocks total: 333226 Blocks remaining: 21988
cdrecord: WARNING: Data may not fit on current disk.
Starting to write CD at speed 4 in dummy mode for single session.
Last chance to quit, starting dummy write in 9 seconds.
Waiting for reader process to fill input-buffer ... input-buffer ready.
Starting new track at sector: 311238
Track 01:   0 of  53 MB written.
Track 01:   1 of  53 MB written (fifo
99%).
Track 01:   2 of  53 MB written (fifo  99%).
Track 01:   3 of
53 MB written (fifo 100%).
Track 01:   4 of  53 MB written (fifo
99%).
Track 01:   5 of  53 MB written (fifo  99%).
Track 01:   6 of
53 MB written (fifo 100%).
Track 01:   7 of  53 MB written (fifo
100%).
Track 01:   8 of  53 MB written (fifo 100%).
Track 01:   9 of
53 MB written (fifo 100%).
Track 01:  10 of  53 MB written (fifo
100%).
Track 01:  11 of  53 MB written (fifo  99%).
Track 01:  12 of
53 MB written (fifo 100%).
Track 01:  13 of  53 MB written (fifo
100%).
Track 01:  14 of  53 MB written (fifo  99%).
Track 01:  15 of
53 MB written (fifo 100%).
Track 01:  16 of  53 MB written (fifo
99%).
Track 01:  17 of  53 MB written (fifo  99%).
Track 01:  18 of
53 MB written (fifo 100%).
Track 01:  19 of  53 MB written (fifo
100%).
Track 01:  20 of  53 MB written (fifo 100%).
Track 01:  21 of
53 MB written (fifo 100%).
Track 01:  22 of  53 MB written (fifo
100%).
Track 01:  23 of  53 MB written (fifo 100%).
Track 01:  24 of
53 MB written (fifo 100%).
Track 01:  25 of  53 MB written (fifo
100%).
Track 01:  26 of  53 MB written (fifo 100%).
Track 01:  27 of
53 MB written (fifo 100%).
Track 01:  28 of  53 MB written (fifo
100%).
Track 01:  29 of  53 MB written (fifo 100%).
Track 01:  30 of
53 MB written (fifo 100%).
Track 01:  31 of  53 MB written (fifo
100%).
Track 01:  32 of  53 MB written (fifo  99%).
Track 01:  33 of
53 MB written (fifo 100%).
Track 01:  34 of  53 MB written (fifo
100%).
Track 01:  35 of  53 MB written (fifo  99%).
Track 01:  36 of
53 MB written (fifo 100%).
Track 01:  37 of  53 MB written (fifo
99%).
Track 01:  38 of  53 MB written (fifo 100%).
Track 01:  39 of
53 MB written (fifo  99%).
Track 01:  40 of  53 MB written (fifo
99%).
Track 01:  41 of  53 MB written (fifo 100%).
Track 01:  42 of
53 MB written (fifo 100%).
Track 01:  43 of  53 MB written (fifo
100%).
Track 01:  44 of  53 MB written (fifo  99%).
Track 01:  45 of
53 MB written (fifo 100%).
Track 01:  46 of  53 MB written (fifo
99%).
Track 01:  47 of  53 MB written (fifo 100%).
Track 01:  48 of
53 MB written (fifo 100%).
Track 01:  49 of  53 MB written (fifo
100%).
cdrecord: Success. write_g1: scsi sendcmd: retryable error
CDB:  2A 00 00 05 15 A5 00 00 0D 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 0A 00 00
Sense Key: 0x9 Vendor Unique, Segment 0
Sense Code: 0x80 Qual 0x0A (limited laser life) [No matching qualifier] Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.002s timeout 40s

write track data: error after 51704016 bytes
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
Writing  time:   80.402s
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
cdrecord: Success. close track/session: scsi sendcmd: retryable error
CDB:  5B 00 02 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 01 00 00
Sense Key: 0x9 Vendor Unique, Segment 0
Sense Code: 0x80 Qual 0x01 (limited laser life) [No matching qualifier] Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.001s timeout 480s
Fixating time:    0.003s
cdrecord: fifo had 1819 puts and 1692 gets.
cdrecord: fifo was 0 times empty and 1094 times full, min fill was 96%.
sh-2.01# nice -n -20 cdrecord -v speed=4 dev=0,4,0 -audio -dummy *.wav
Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling
TOC Type: 0 = CD-DA
scsidev: '0,4,0'
scsibus: 0 target: 4 lun: 0
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   : SYNC LINKED 
Vendor_info    : 'PLEXTOR '
Identifikation : 'CD-R   PX-R412C '
Revision       : '1.04'
Device seems to be: Generic mmc CD-R.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : SWABAUDIO
Track 01: audio  53 MB (05:18.02) no preemp
Track 02: audio  38 MB (03:49.20) no preemp
Track 03: audio  80 MB (07:56.21) no preemp
Track 04: audio  47 MB (04:43.72) no preemp
Track 05: audio  54 MB (05:21.96) no preemp
Total size:     275 MB (27:17.12) = 122784 sectors
Lout start:     275 MB (27:19/09) = 122784 sectors
ATIP info from disk:
  Indicated writing power: 4
  Is unrestricted
  Is not erasable
  ATIP start of lead in:  -11580 (97:27/45)
  ATIP start of lead out: 333226 (74:05/01)
Disk type: Phthalocyanine or similar
Manufacturer: Kodak Japan Limited
Blocks total: 333226 Blocks remaining: 21988
cdrecord: WARNING: Data may not fit on current disk.
Starting to write CD at speed 4 in dummy mode for single session.
Last chance to quit, starting dummy write in 9 seconds.
Waiting for reader process to fill input-buffer ... input-buffer ready.
Starting new track at sector: 311238
Track 01:   0 of  53 MB written.
Track 01:   1 of  53 MB written (fifo
99%).
Track 01:   2 of  53 MB written (fifo  99%).
Track 01:   3 of
...
53 MB written (fifo 100%).
Track 01:  49 of  53 MB written (fifo
100%).
cdrecord: Success. write_g1: scsi sendcmd: retryable error
CDB:  2A 00 00 05 15 A5 00 00 0D 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 0A 00 00
Sense Key: 0x9 Vendor Unique, Segment 0
Sense Code: 0x80 Qual 0x0A (limited laser life) [No matching qualifier] Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.002s timeout 40s

write track data: error after 51704016 bytes
Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
Writing  time:   80.362s
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
cdrecord: Success. close track/session: scsi sendcmd: retryable error
CDB:  5B 00 02 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 01 00 00
Sense Key: 0x9 Vendor Unique, Segment 0
Sense Code: 0x80 Qual 0x01 (limited laser life) [No matching qualifier] Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.000s timeout 480s
Fixating time:    0.002s
cdrecord: fifo had 1819 puts and 1692 gets.
cdrecord: fifo was 0 times empty and 931 times full, min fill was 97%.
sh-2.01# nice -n -20 cdrecord -v speed=4 dev=0,4,0 -audio -dummy *.wav
Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling
TOC Type: 0 = CD-DA
scsidev: '0,4,0'
scsibus: 0 target: 4 lun: 0
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   : SYNC LINKED 
Vendor_info    : 'PLEXTOR '
Identifikation : 'CD-R   PX-R412C '
Revision       : '1.04'
Device seems to be: Generic mmc CD-R.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : SWABAUDIO
Track 01: audio  53 MB (05:18.02) no preemp
Track 02: audio  38 MB (03:49.20) no preemp
Track 03: audio  80 MB (07:56.21) no preemp
Track 04: audio  47 MB (04:43.72) no preemp
Track 05: audio  54 MB (05:21.96) no preemp
Total size:     275 MB (27:17.12) = 122784 sectors
Lout start:     275 MB (27:19/09) = 122784 sectors
ATIP info from disk:
  Indicated writing power: 4
  Is unrestricted
  Is not erasable
  ATIP start of lead in:  -11580 (97:27/45)
  ATIP start of lead out: 333226 (74:05/01)
Disk type: Phthalocyanine or similar
Manufacturer: Kodak Japan Limited
Blocks total: 333226 Blocks remaining: 333226
Starting to write CD at speed 4 in dummy mode for single session.
Last chance to quit, starting dummy write in 9 seconds.
Waiting for reader process to fill input-buffer ... input-buffer ready.
Starting new track at sector: 0
Track 01:   0 of  53 MB written.
Track 01:   1 of  53 MB written (fifo
99%).
Track 01:   2 of  53 MB written (fifo  99%).
Track 01:   3 of
53 MB written (fifo 100%).
Track 01:   4 of  53 MB written (fifo
...
99%).
Track 01:  50 of  53 MB written (fifo 100%).
Track 01:  51 of
53 MB written (fifo 100%).
Track 01:  52 of  53 MB written (fifo
100%).
Track 01:  53 of  53 MB written (fifo  99%).
Track 01: Total bytes read/written: 56099904/56099904 (23852 sectors).
Starting new track at sector: 24004
Track 02:   0 of  38 MB written.
Track 02:   1 of  38 MB written (fifo
99%).
Track 02:   2 of  38 MB written (fifo  99%).
Track 02:   3 of
38 MB written (fifo  98%).
Track 02:   4 of  38 MB written (fifo
...
38 MB written (fifo 100%).
Track 02:  34 of  38 MB written (fifo
100%).
Track 02:  35 of  38 MB written (fifo  98%).
Track 02:  36 of
38 MB written (fifo 100%).
Track 02:  37 of  38 MB written (fifo 100%).
Track 02:  38 of  38 MB
written (fifo 100%).
Track 02: Total bytes read/written: 40430880/40430880 (17190 sectors).
Starting new track at sector: 41346
Track 03:   0 of  80 MB written.
Track 03:   1 of  80 MB written (fifo
99%).
Track 03:   2 of  80 MB written (fifo  99%).
Track 03:   3 of
80 MB written (fifo  98%).
Track 03:   4 of  80 MB written (fifo
...
99%).
Track 03:  77 of  80 MB written (fifo 100%).
Track 03:  78 of
80 MB written (fifo 100%).
Track 03:  79 of  80 MB written (fifo
100%).
Track 03:  80 of  80 MB written (fifo 100%).
Track 03: Total bytes read/written: 84004032/84004032 (35716 sectors).
Starting new track at sector: 77214
Track 04:   0 of  47 MB written.
Track 04:   1 of  47 MB written (fifo
99%).
Track 04:   2 of  47 MB written (fifo 100%).
Track 04:   3 of
47 MB written (fifo 100%).
Track 04:   4 of  47 MB written (fifo
100%).
Track 04:   5 of  47 MB written (fifo 100%).
Track 04:   6 of
...
47 MB written (fifo  99%).
Track 04:  43 of  47 MB written (fifo
100%).
Track 04:  44 of  47 MB written (fifo  99%).
Track 04:  45 of
47 MB written (fifo 100%).
Track 04:  46 of  47 MB written (fifo
100%).
Track 04:  47 of  47 MB written (fifo 100%).
Track 04: Total bytes read/written: 50048208/50048208 (21279 sectors).
Starting new track at sector: 98645
Track 05:   0 of  54 MB written.
Track 05:   1 of  54 MB written (fifo
99%).
Track 05:   2 of  54 MB written (fifo  99%).
Track 05:   3 of
...
54 MB written (fifo 100%).
Track 05:  52 of  54 MB written (fifo
100%).
Track 05:  53 of  54 MB written (fifo 100%).
Track 05:  54 of  54 MB written (fifo 100%).
Track 05: Total bytes read/written: 56793744/56793744 (24147 sectors).
Writing  time:  435.019s
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
cdrecord: Success. close track/session: scsi sendcmd: retryable error
CDB:  5B 00 02 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 01 00 00
Sense Key: 0x9 Vendor Unique, Segment 0
Sense Code: 0x80 Qual 0x01 (limited laser life) [No matching qualifier] Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.000s timeout 480s
Fixating time:    0.003s
cdrecord: fifo had 9401 puts and 9401 gets.
cdrecord: fifo was 0 times empty and 5666 times full, min fill was 91%.
sh-2.01# exit

Script done on Sun Jul 25 00:27:08 1999

-- 
Matt Garman, [EMAIL PROTECTED]
"And through the window in the wall
 Come streaming in on sunlight wings
 A million bright ambassadors of morning." 
        --Pink Floyd, "Echoes"

------------------------------

From: Abdullah Ramazanoglu <[EMAIL PROTECTED]>
Subject: Re: Modem Question
Date: Sun, 25 Jul 1999 18:39:48 +0300

You must SUID root the binaries "pppd" and kppp". The locations of these
may depend on your distro, but following commands (issued as root)
should do the job:

chmod u+s `which pppd`
chmod u+s `which kppp`

It is explained under Help button of main kppp dial window. As
explained, this method is somewhat a quick and dirty method in terms of
security. Instead, it is better to leave pppd and kppp as is and
manually change the attributes of each and every resource that these
binaries use. OTOH if it's a single user home machine, IMO there's no
need to be that strict. I do use SUID pppd / kppp binaries at home. 

Note that, if you use linuxconf, it is somewhat over-clever in detecting
which binaries should have what attributes; and at each time you Quit
from linuxconf it asks whether it should activate the changes. One of
those changes is reverting pppd to its original form. You must NOT let
linuxconf do that.

Hope this helps,
Abdullah


Stephen Kowski wrote:
> 
> When I log in as my user (not root) and try to use the KPP Dialer to use modem to
> connect to ISP I get this error message:
> PPD is not properly installed!
> The ppd binary must be installed with SUID bit set.  Contact your system admin.
> I click ok there and get in and it does find and configure  my modem...  I have no
> clue from here...
> 
> Steve
> 
> Kevin Theobald wrote:
> 
> > "Steve Kowski" <[EMAIL PROTECTED]> writes:
> >
> > > I am a newbie to Linux.  I have it running on my IBM ThinkPad 380ED.
> >
> > That's quite a feat for a "newbie" given everything I've heard about
> > Linux on laptops!
> >
> > > Everything runs great and I am actually using linux more than Windoze.  I do
> > > have one question.  The only way for me to dial out on my modem right now is
> > > that I must log in as Root.  My "normal" user can't use the modem.  Any
> > > suggestions?  Do i need to Chown a certain file? Help is always appreciated.
> >
> > Well, there could be lots of reasons, depending on what modem tool
> > you're using.  Either a device file needs to be writable by everyone
> > ("chmod 777 <device-name>"), or your modem program must be run "setuid
> > root" (which means when you start it, it runs as the root user so it
> > can access devices mere mortals can't).  I don't know much about these
> > tools myself.  Check any manuals (e.g., "man xxx" where xxx is the
> > name of your modem program).  Also, some programs take -d as a switch
> > which prints out debugging info, which may give a clue.
> >
> > --
> > ------------------------------------------------------------------------------
> > | Kevin B. Theobald, Ph.D. - Computer Architecture and Parallel Systems Lab. |
> > | Department of Electrical and Computer Engineering, University of Delaware  |
> > ------------------------------------------------------------------------------
> > | I think history has proven over and over again that once a company has a   |
> > | lock on a market, product quality and innovation decline -- and prices     |
> > | rise.  Are you going to be part of the problem or part of the solution?    |
> > |                                                                            |
> > |                                       Robert B. Denny, Chicago Tribune     |
> > |                                  http://solo.dc3.com/editorial/102298.html |
> > ------------------------------------------------------------------------------

-- 
Abdullah Ramazanoðlu    [ aramazanoglu AT demirbank DOT com DOT tr ]

------------------------------

From: "Steve Snyder" <[EMAIL PROTECTED]>
Reply-To: "Steve Snyder" <[EMAIL PROTECTED]>
Subject: Advice on Linux and LS-120 drive?
Date: Sun, 25 Jul 1999 16:04:50 GMT

I've got RH 6.0 installed on a system with an LS-120 drive.  Because
all the other storage devices are SCSI, this drive is identified as
/dev/hda.  I've got a few questions regarding Linux's view of the
LS-120 drive.

1. When I run LILO to install a new kernel onto my SCSI hard disk 
(/dev/sda3), it issues a lot of complaints about /dev/hda (the 
LS-120 drive) as well.  LILO does what it's supposed to, and I have no
trouble with booting off the hard disk.  I am troubled though by the 
screen full of warnings.  LILO complains that /dev/hda has 2 sizes, 
128MB and 0MB.  Hmm.  Why should it care about /dev/hda at all when 
I'm handling /dev/sda3?

2. Ideally, I want the LS-120 to be treated like a big floppy.  Linux,
though, seems to want to treat it like a hard disk.  The distinction
is the use of partitions.  I'd rather not have partitions at all, while
Linux wants to write the filesystem and files to a specific partition
number (e.g.  /dev/hda1).  Since the drive is accessed via the device
driver ide_floppy.o, the system is presumably aware that the device is
not a fixed hard disk.  Is there a way I can do without partitions
altogether?

Thank you.

***** Steve Snyder *****




------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.hardware) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Hardware Digest
******************************

Reply via email to