Linux-Hardware Digest #836, Volume #14           Mon, 28 May 01 13:13:06 EDT

Contents:
  Re: Back up in Linux ("Les Mikesell")
  Suport for the Epox 8KTA3? (Frank)
  CD-ROM problems with kernel s.4.x (Filipe Bonjour)
  Re: How could I make a raw copy of a disk ? ("Martin.Knoblauch")
  Linux compatible components?Corel? (Nicholas Scott)
  Re: Suport for the Epox 8KTA3? (Thomas Rasmussen)
  Re: Linux compatible components?Corel? (Frank Miller)
  Re: Please read... (Daniel Hanke)
  Re: Montego snd worked in 6.2 but not 7.1?? (Liam Watts)
  Re: How could I make a raw copy of a disk ? ("Mark Robson")

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

From: "Les Mikesell" <[EMAIL PROTECTED]>
Crossposted-To: 
alt.os.linux,alt.os.linux.mandrake,comp.os.linux.advocacy,comp.windows.x.kde,tw.bbs.comp.linux
Subject: Re: Back up in Linux
Date: Mon, 28 May 2001 15:17:42 GMT


"Aaron R. Kulkis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> >
> > Tar is actually better than dump at dealing with an active filesystem
> > but neither will handle the case where multiple files must be saved
> > as a snapshot of a consistent state.   What we need is kernel support
> > to freeze the 'real' filesystem while letting the system continue to
work
> > with changes staying in the buffers or paging out to swap if necessary -
and
> > of course, a way for the backup utility to read the frozen copy.
>
> Everything I've seen always says to get a PERFECT level 0, go to
> single user mode (init S)  and remount the root filesystem read-only.

That's fine if you don't need the machine to be doing anything - but if
that is the case why bother to back it up?   One workable but expensive
trick is to use a NetApp for an NFS-mounted filesystem and rsh
the dumps from there.  The NetApp will do it's snapshot thing and
send a dump of the snapshot even as the real filesystem continues
to change.

      Les Mikesell
       [EMAIL PROTECTED]




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

From: [EMAIL PROTECTED] (Frank)
Subject: Suport for the Epox 8KTA3?
Date: Mon, 28 May 2001 15:18:37 GMT

I have tried to find information wheter the Epox 8KA3 with KT133A is
supported by Linux, but I found nothing.
Can anybody tell me if it is supported and how well it works.

Frank van Dam

[EMAIL PROTECTED]

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

From: Filipe Bonjour <[EMAIL PROTECTED]>
Subject: CD-ROM problems with kernel s.4.x
Date: Mon, 28 May 2001 12:17:31 -0300

Hi,

I recently switched from kernel 2.2 (RH 6.2) to kernel 2.4 (RH 7.1) and
I've been having problems readinc CDs. The kernel shipped with RH 7.1 is
2.4.2-2 and I've tried 2.4.4 as well, without success. Here is what I
get
when I try to read some files:

===========

hdb: status error: status 0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: status error: status 0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
hdb: tray open
nd_request: I/O error, dev 03:40 (hdb), sector 643492
hdb: status error: status 0x58 { DriveReady SeekComplete DataRequest
Error }
hdb: status error: status 0x24
hdb: drive not ready for command
cp reading `helpport.tar.gz': Input/output error

============

I must admit my CD-ROM is rather old, it's a Creative 24x, so maybe
that's
the problem... Here's what I get from the files in /proc/ide/ide0/hdb:

capacity: 0
driver:   ide-cdrom version 4.59
identify: 
media:    cdrom
model:    CREATIVE CD2422E
settings: 
name                    value           min             max             mode
----                    -----           ---             ---             ----
breada_readahead        4               0               127            
rw
current_speed           34              0               69             
rw
dsc_overlap             1               0               1              
rw
file_readahead          0               0               2097151        
rw
ide_scsi                0               0               1              
rw
init_speed              12              0               69             
rw
io_32bit                1               0               3              
rw
keepsettings            0               0               1              
rw
max_kb_per_request      127             1               127            
rw
nice1                   1               0               1              
rw
number                  1               0               3              
rw
pio_mode                write-only      0               255            
w
slow                    0               0               1              
rw
unmaskirq               1               0               1              
rw
using_dma               1               0               1              
rw

=================

Has anyone experienced the same problem? Any help would be appreciated!

TIA,

Fil

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

From: "Martin.Knoblauch" <[EMAIL PROTECTED]>
Subject: Re: How could I make a raw copy of a disk ?
Date: Mon, 28 May 2001 17:36:38 +0200

This is a multi-part message in MIME format.
==============36838D197958D0AA988FAD26
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"A. GUILLEVIC" wrote:
> 
> Hello,
> 
> We'll implement around 30 Linux boxes in our company and I'd like if a small
> software to make raw diskcopy exists ? I tried with dd, which works fine, but
> too slowly (around 3 hours and a half to copy a 9 Gb IDE drive). All PCs are
> shipped with ULTRA-ATA 66 disk drives. Did I do something wrong with dd or
> is it really that slow ?
> 
>                        Thanks in advance for your help.

 try playing with the "bs" option of "dd". Also, if possible, place the
disks on different controllers. SCSI should handle a single controller
case pretty well, but I am not sure about IDE/ATA.

Martin
-- 
==================================================================
Martin Knoblauch         |    email:  [EMAIL PROTECTED]
TeraPort GmbH            |    Phone:  +49-89-510857-309
C+ITS                    |    Fax:    +49-89-510857-111
http://www.teraport.de   |    Mobile: +49-170-4904759
==============36838D197958D0AA988FAD26
Content-Type: text/x-vcard; charset=us-ascii;
 name="Martin.Knoblauch.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Martin.Knoblauch
Content-Disposition: attachment;
 filename="Martin.Knoblauch.vcf"

begin:vcard 
n:Knoblauch;Martin
tel;cell:+49-170-4904759
tel;fax:+49-89-510857-111
tel;work:+49-89-510857-309
x-mozilla-html:FALSE
url:http://www.teraport.de
org:TeraPort GmbH;C+ITS
adr:;;Garmischer Straße 4;München;Bayern;D-80339;Germany
version:2.1
email;internet:[EMAIL PROTECTED]
title:Senior System Engineer
x-mozilla-cpt:;-7008
fn:Martin Knoblauch
end:vcard

==============36838D197958D0AA988FAD26==


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

From: Nicholas Scott <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Linux compatible components?Corel?
Date: Mon, 28 May 2001 11:55:01 -0400

I recently built a machine and installed removable hardrive trays.  One
of my thoughts was to be able to remove the drive with the Windows OS an
insert another with Linux. However, before I dive into the linux world I
was wondering if I had any components that were not hospitable to Linux.
I'd appreciate any info regarding problem and fixes for any of the
parts. Below is a list of my system components.  In Addition, I use
Corel Draw and understand that Corel products are available for Linux.
In fact Corel produces a version of Linux.  Answers? Suggestions?

DFI AK74-EC Mobo ATA100, On-board sound (currently disabled)
VIA KT133a
BIOS Version Award Modular BIOS v6.00PG
256 Micron ram
Western Digital 30 gig 7200 ATA100 HD
NEC Zip 100 internal Zip drive
NEC NR 7700a 12x CD-RW
AMD Duron Processor 650 Mhz
3D Prophet SE
Standard 3 1/2 Floppy
Adaptec AIC-7850 PCI SCSI Controller
Creative SB Live! Value
Zoom Internal 56K LT Voice Faxmodem
Alcatel SpeedTouch(tm) USB ADSL PPPoA






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

From: Thomas Rasmussen <[EMAIL PROTECTED]>
Subject: Re: Suport for the Epox 8KTA3?
Date: 28 May 2001 18:13:29 +0200

>>>>> "Frank" == Frank  <[EMAIL PROTECTED]> writes:

 Frank> I have tried to find information wheter the Epox 8KA3 with
 Frank> KT133A is supported by Linux, but I found nothing.  Can
 Frank> anybody tell me if it is supported and how well it works.

I have the 8KTA3+ (Raid controller) and it works fine for me. I'm
currently not using the HPT370 but the kernel finds it and probes
without any problems, so I would think that it is working without any
problems. I'm not using the onboard audio either, but I have read that
alsa is supporting it without problems too.

My setup is as follows:
Epox 8KTA3+ with Athlon Thunderbird 1GHz and 256MB RAM
IBM UDMA66 20GB harddrive
Debian Woody with kernel 2.4.3
and some other small stuff.

I have found no problems with the motherboard other than the fan is
quite noicy :-)

If you wan't some specific information, you are welcome to email me as
I probably would miss your posting here :-)

/Thomas

-- 
/"\  | "To alcohol! The cause of - and solution to - 
\ /  | all of life's problems!" -- Homer Simpson
 x   |                   
/ \ <-- (ASCII Ribbon Campain against html emails and postings!)

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

From: Frank Miller <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Linux compatible components?Corel?
Date: Mon, 28 May 2001 16:35:29 GMT

Nicholas Scott wrote:
> 
> I recently built a machine and installed removable hardrive trays.  One
> of my thoughts was to be able to remove the drive with the Windows OS an
> insert another with Linux. However, before I dive into the linux world I
> was wondering if I had any components that were not hospitable to Linux.
> I'd appreciate any info regarding problem and fixes for any of the
> parts. Below is a list of my system components.  In Addition, I use
> Corel Draw and understand that Corel products are available for Linux.
> In fact Corel produces a version of Linux.  Answers? Suggestions?
> 
> DFI AK74-EC Mobo ATA100, On-board sound (currently disabled)
> VIA KT133a
> BIOS Version Award Modular BIOS v6.00PG
> 256 Micron ram
> Western Digital 30 gig 7200 ATA100 HD
> NEC Zip 100 internal Zip drive
> NEC NR 7700a 12x CD-RW
> AMD Duron Processor 650 Mhz
> 3D Prophet SE
> Standard 3 1/2 Floppy
> Adaptec AIC-7850 PCI SCSI Controller
> Creative SB Live! Value
> Zoom Internal 56K LT Voice Faxmodem
> Alcatel SpeedTouch(tm) USB ADSL PPPoA

Forget Corel.  I tried it when it first came out.  Version 1. worked
"sott of".  Version 1.1 was a disaster.  I bought WordPerfect for Linux
and it sets in a box because, again it worked "almost".  The
wordprocessor didn't work correctly under Corel or Redhat.


I am using Mandrake and love it.

Frank

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

From: Daniel Hanke <[EMAIL PROTECTED]>
Subject: Re: Please read...
Date: Mon, 28 May 2001 16:31:27 GMT

Ok Daniel,

LinuX drivers can be compiled in the kernel or can be compiled as a kind=
=20
of =84kernel dll=93 called =84module=93. A compiled-in-driver is loaded =
at boot=20
time, a module can be loaded by invoking =84insmod <module_name>.o=93 (Y=
ou=20
have to be root). Modules can also be installed automagically by adding =

an entry in /etc/modules.conf. The format of this file is described in=20=

its manual page (=84man modules.conf=93). But for the first time the bes=
t way=20
is to use =84insmod=93 (if You have the .o file).
The message =84couldn't execute /usr/bin/kdesu=93 means, that a) You're =

trying to install the driver without being root, b) the program =84kdesu=
=93=20
(it makes You being root) insn't installed. You can a) get root by=20
opening a Terminal and typing =84su=93 b) trying to locate the kdesu pac=
kage=20
and install it.
LinuX is a very big system and for newcomers it's the best to read a goo=
d=20
LinuX book. Look at www.linux.org/books for a book, or look at Your=20
installation disks. My SuSE Linux has some very good books in the=20
books.rpm package (grab it at=20
ftp://ftp.suse.com/pub/suse/i386/7.1/suse/doc3/books.rpm=20
). They are in Postscript or TeX/DVI format.

Have fun ...
        Daniel

P.S.: To get help under LinuX You can type =84apropos <keyword>=93 (that=
=20
gives You a list of commands) or =84man <command>=93 at the console.

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

From: Liam Watts <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.redhat,comp.os.linux.help,comp.os.linux.setup
Subject: Re: Montego snd worked in 6.2 but not 7.1??
Date: Mon, 28 May 2001 16:38:21 GMT

I found that thread on Sourceforge...great tips! Pretty detailed.
I did the
rpm -q kernel-source
and got "kernel-source-2.4.2-2" so evidently the source code is installed.
So then I make the path in /usr/src:
"ln -s linux-2.4.2 linux" in the /usr/src directory, and all went well.
So I tried "make install20" again, and got a list of errors, but this time
they were all "...from incompatible pointer type" errors.

Any ideas? That thread on the Sourcefiorge doesn't address that error.

Thanks for your help!

Liam

mark dynarski wrote:

> I ran into the same issue when I upgraded from 6.2 to RH 7.0.  The
> Sourceforge site that maintains the Aureal drivers had a thread about the
> issue.  The solution was to install the 7.0 kernel source from the install
> CD-ROM.  RH does not load the source by default and the module needs some
> of the source to compile correctly.
>
> Hope this helps,
> Mark D
>
> Liam Watts wrote:
>
> > As the subject states, I have a Turtle Beach Montego 3D (Aureal Vortex I
> > AU8820) sound card. In the 3 years I've been playing off and on with
> > Linux I've never been able to get it to work.
> > That is until I found the driver pack au88xx.1.0.5.tar.gz from
> > linux.org. It installed perfectly in my RH 6.2!!
> >
> > Well, I wiped and installed RH7.1.  I'd have thought better support, but
> > when I "make install20" I get the string of info I'll paste at the end
> > here, and it doesn't work.
> >
> > Can anyone give me any pointers here with this?
> >
> > Thanks!
> > Liam
> >
> > [root@X a au88xx-1.0.5]# make install20
> > make install AUCHIP=AU8820
> > make[1]: Entering directory `/tmp/au88xx-1.0.5'
> > cc -D__KERNEL__ -DMODULE -DAU8820 -O -Wall -pipe -m486
> > -I/usr/src/linux/include
> > -O2 -fomit-frame-pointer   -c -o vortex.o vortex.c
> > In file included from vortex.c:50:
> > /usr/include/linux/modversions.h:1:2: #error Modules should never use
> > kernel-hea
> > ders system headers,
> > /usr/include/linux/modversions.h:2:2: #error but headers from an
> > appropriate ker
> > nel-source
> > In file included from vortex.c:67:
> > /usr/include/asm/spinlock.h:26: conflicting types for `spinlock_t'
> > /usr/include/linux/spinlock.h:55: previous declaration of `spinlock_t'
> > /usr/include/asm/spinlock.h:68: parse error before `{'
> > /usr/include/asm/spinlock.h:78: parse error before `void'
> > /usr/include/asm/spinlock.h:93: parse error before `do'
> > /usr/include/asm/spinlock.h:121: conflicting types for `rwlock_t'
> > /usr/include/linux/spinlock.h:118: previous declaration of `rwlock_t'
> > /usr/include/asm/spinlock.h:146: parse error before `void'
> > /usr/include/asm/spinlock.h:155: parse error before `void'
> > vortex.c:277: warning: initialization from incompatible pointer type
> > vortex.c:278: warning: initialization from incompatible pointer type
> > vortex.c:279: warning: initialization from incompatible pointer type
> > vortex.c:281: warning: initialization from incompatible pointer type
> > vortex.c:282: warning: initialization from incompatible pointer type
> > vortex.c:283: warning: initialization from incompatible pointer type
> > vortex.c:284: warning: initialization from incompatible pointer type
> > vortex.c:287: warning: initialization from incompatible pointer type
> > vortex.c:289: warning: initialization from incompatible pointer type
> > vortex.c:294: warning: initialization from incompatible pointer type
> > vortex.c:296: warning: initialization from incompatible pointer type
> > vortex.c:299: warning: initialization from incompatible pointer type
> > vortex.c:301: warning: initialization from incompatible pointer type
> > vortex.c:302: warning: initialization from incompatible pointer type
> > vortex.c:303: warning: initialization from incompatible pointer type
> > vortex.c:305: warning: initialization from incompatible pointer type
> > vortex.c:306: warning: initialization from incompatible pointer type
> > vortex.c:308: warning: initialization from incompatible pointer type
> > vortex.c:311: warning: initialization from incompatible pointer type
> > vortex.c:314: warning: initialization from incompatible pointer type
> > vortex.c:320: warning: initialization from incompatible pointer type
> > vortex.c:323: warning: initialization from incompatible pointer type
> > vortex.c: In function `scan_id':
> > vortex.c:485: structure has no member named `base_address'
> > vortex.c:486: structure has no member named `base_address'
> > vortex.c: In function `add_device':
> > vortex.c:513: warning: implicit declaration of function `init_waitqueue'
> >
> > vortex.c: In function `alloc_core':
> > vortex.c:696: structure has no member named `base_address'
> > vortex.c:698: structure has no member named `base_address'
> > vortex.c: In function `au_audio_read':
> > vortex.c:794: warning: passing arg 1 of `interruptible_sleep_on' from
> > incompatib
> > le pointer type
> > vortex.c: In function `au_audio_write':
> > vortex.c:857: warning: passing arg 1 of `interruptible_sleep_on' from
> > incompatib
> > le pointer type
> > vortex.c: In function `au_audio_ioctl':
> > vortex.c:943: warning: implicit declaration of function `get_user_ret'
> > vortex.c:897: warning: `val' might be used uninitialized in this
> > function
> > vortex.c: In function `au_audio_mmap':
> > vortex.c:1114: structure has no member named `vm_offset'
> > vortex.c: In function `drain_playback':
> > vortex.c:1224: warning: passing arg 1 of `interruptible_sleep_on' from
> > incompati
> > ble pointer type
> > vortex.c: In function `get_frags':
> > vortex.c:1333: warning: implicit declaration of function `MAP_NR'
> > vortex.c: In function `au_handle_timer':
> > vortex.c:1581: warning: passing arg 1 of `__wake_up' from incompatible
> > pointer t
> > ype
> > vortex.c:1611: warning: passing arg 1 of `__wake_up' from incompatible
> > pointer t
> > ype
> > vortex.c: In function `au_mixer_ioctl':
> > vortex.c:1628: warning: `val' might be used uninitialized in this
> > function
> > vortex.c: In function `au_midi_read':
> > vortex.c:2001: warning: passing arg 1 of `interruptible_sleep_on' from
> > incompati
> > ble pointer type
> > vortex.c: In function `au_midi_write':
> > vortex.c:2050: warning: passing arg 1 of `interruptible_sleep_
> > ble pointer type
> > vortex.c: In function `au_midi_poll':
> > vortex.c:2079: warning: passing arg 2 of `poll_wait' from inco
> > ype
> > vortex.c:2081: warning: passing arg 2 of `poll_wait' from inco
> > ype
> > vortex.c: In function `au_handle_midi':
> > vortex.c:2121: warning: passing arg 1 of `__wake_up' from inco
> > ype
> > vortex.c:2132: warning: passing arg 1 of `__wake_up' from inco
> > ype
> > vortex.c: In function `sound_proc_get_info':
> > vortex.c:2267: structure has no member named `base_address'
> > make[1]: *** [vortex.o] Error 1
> > make[1]: Leaving directory `/tmp/au88xx-1.0.5'
> > make: *** [install20] Error 2
> > [root@x au88xx-1.0.5]#
> >
> >
> >


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

From: "Mark Robson" <[EMAIL PROTECTED]>
Subject: Re: How could I make a raw copy of a disk ?
Date: Mon, 28 May 2001 17:49:36 +0100

In article <[EMAIL PROTECTED]>, "A.
GUILLEVIC" <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> We'll implement around 30 Linux boxes in our company and I'd like if a
> small software to make raw diskcopy exists ? I tried with dd, which
> works fine, but too slowly (around 3 hours and a half to copy a 9 Gb IDE
> drive). All PCs are shipped with ULTRA-ATA 66 disk drives. Did I do
> something wrong with dd or is it really that slow ?

dd is as fast or slow as the hardware.

Make sure you've set up the discs with DMA-mode turned on - which isn't
the default in <2.4 kernels (AFAIK) - this makes up to a factor of 10
difference (read the hdparm man page)

Failing that, you could try making a copy of the source disc, then
gzipping it - then it would have less data to read from the source disc
so less I/O

AFAIK, you can also use normal disc mirroring software - like Norton
Ghost or whatever - with the normal limitations. In my experience
however, this is unlikely to be faster than what you're describing.

Most of these programs support ext2 these days

Cheers
        Mark

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


** 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 by posting to comp.os.linux.hardware.

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