Linux-Hardware Digest #57, Volume #13 Sat, 17 Jun 00 15:13:04 EDT
Contents:
Re: Compaq Proliant DL-series hardware (Kostis Mentzelos)
Re: Is there support for AAA-131U2 in Linux (Markus Kossmann)
Can't use "setserial" command to setup modem. (James)
RE: Compatibility, pls help (Newbie question) ("turbo")
Re: Lilo Problem (SooperGrover)
Re: CDR and sound card under SUSE linux 6.4 ("Peter T. Breuer")
Re: CDR and sound card under SUSE linux 6.4 (Edward Lee)
Re: Compatibility, pls help (Newbie question) (Dances With Crows)
Re: Dumping Windows (Dances With Crows)
RH6.2 mke2fs crashes on install
Re: Dumping Windows (Hal Burgiss)
Trouble with cdrecord..:< (root)
----------------------------------------------------------------------------
From: Kostis Mentzelos <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: Compaq Proliant DL-series hardware
Date: Sat, 17 Jun 2000 19:04:49 +0300
I have installed SuSE linux 6.3 on compaq ML350
The network card is the same. NC3163. SuSE automatically
load eepro100 driver (intel ether express 10/100).
But I have problems. While the network is working fine
suddenly is going down and I need to restart the server!!!
I have replaced the compaq network card with 3com.
I will know the results next week
Kostis.
------------------------------
From: Markus Kossmann <[EMAIL PROTECTED]>
Subject: Re: Is there support for AAA-131U2 in Linux
Date: Sat, 17 Jun 2000 17:20:23 +0200
Jeff Roberts wrote:
>
> Nikolaj Woel wrote:
> >
> > subj.
> Does anyone know of support for this card?
> It's been out for a while, I would expect that SOMEONE has written a
> driver for it.
Did you read the kernel configuration help for the aic7xxx driver ?
The reason for the lack of support is Adaptec. The don't release any
programming specs for the 7810 used on these cards .
--
Markus Kossmann
[EMAIL PROTECTED]
------------------------------
From: James <[EMAIL PROTECTED]>
Subject: Can't use "setserial" command to setup modem.
Date: Sat, 17 Jun 2000 16:30:06 GMT
Hi,
I have an internal ISA Rockwell modem, I realise it could be a winmodem
although I have my doubts because I used to use Corel linux and it worked
fine.
I am now running Mandrake 7.0 and cannot manage to setup my modem. If I
log in and load Kppp and click connect it will initialise, dial very
slowly and hang up. If I try to reconnect It says "Sorry the modem doesn't
respond."
I also tried to set it up with the "setserial /dev/ttyS2 autoconfig"
command but I get a message saying "Device or resource busy."
I then tried doing it the long way with "setserial" but I did not know
what value to put for "uart" how do I find this out?
How can I get my modem to work? And why does linux think that it is
busy?
My computer;
Cyrix 266
64Mb RAM
Mandrake 7.0
Dual boot with Windows 98
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: "turbo" <[EMAIL PROTECTED]>
Subject: RE: Compatibility, pls help (Newbie question)
Date: Sat, 17 Jun 2000 17:18:22 +0100
Hi
I would like to buy a new computer. The computer I would like to buy is a
Dell Dimension XPS T800. It has a Intel Pentium 111, 128mb, 15Gb IDE hard
disk.
The monitor is a Dell 17' monitor Viewable area) The video adaptor is a 32mb
Nvida m64 TNT X2 video card. The sound card is a Creative labs 64V sound.
Can anyone pls tell me if this computer will be compatible with Redhat 6.2?
I've checked Redhat's web page about compatibility, but I'm not really sure.
Can someone pls help? I'm still a newbie!
Thanks
David
------------------------------
From: [EMAIL PROTECTED] (SooperGrover)
Subject: Re: Lilo Problem
Date: Sat, 17 Jun 2000 17:08:48 GMT
Crossposted-To:
alt.uu.comp.os.linux.questions,comp.os.linux.misc,comp.os.linux.x,nl.comp.os.linux.overig,nl.comp.os.linux.x
On Sat, 17 Jun 2000 13:29:40 +0200, "FROZEN_Steam"
<[EMAIL PROTECTED]> wrote:
|Hello,
|
|I'm having some trouble using lilo.
|
|I've configured lilo on mbr, but when it starts, There's only an 'L' on my
|screen and I can do nothing but hit reset...
It seems you have a problem with your harddrive. LILO should probably
be configured to use linear mode. Read on...
>From the LILO README file comes the following:
When LILO loads itself, it displays the word "LILO". Each letter is
printed before or after performing some specific action. If LILO fails
at some point, the letters printed so far can be used to identify the
problem. This is described in more detail in the technical overview.
Note that some hex digits may be inserted after the first "L" if a
transient disk problem occurs. Unless LILO stops at that point,
generating an endless stream of error codes, such hex digits do not
indicate a severe problem.
(<nothing>) No part of LILO has been loaded. LILO either isn't
installed or the partition on which its boot sector is located isn't
active.
L <error> ... The first stage boot loader has been loaded and
started, but it can't load the second stage boot loader. The two-digit
error codes indicate the type of problem. (See also section "Disk
error codes".) This condition usually indicates a media failure or a
geometry mismatch (e.g. bad disk parameters, see section "Disk
geometry").
LI The first stage boot loader was able to load the second stage
boot loader, but has failed to execute it. This can either be caused
by a geometry mismatch or by moving /boot/boot.b without running the
map installer.
LIL The second stage boot loader has been started, but it can't
load the descriptor table from the map file. This is typically caused
by a media failure or by a geometry mismatch.
LIL? The second stage boot loader has been loaded at an incorrect
address. This is typically caused by a subtle geometry mismatch or by
moving /boot/boot.b without running the map installer.
LIL- The descriptor table is corrupt. This can either be caused
by a geometry mismatch or by moving /boot/map without running the map
installer.
LILO All parts of LILO have been successfully loaded.
Disk error codes
- - - - - - - -
If the BIOS signals an error when LILO is trying to load a boot image,
the respective error code is displayed. The following BIOS error codes
are known:
0x00 "Internal error". This code is generated by the sector read
routine of the LILO boot loader whenever an internal inconsistency is
detected. This might be caused by corrupt files. Try re-building the
map file. Another possible cause for this error are attempts to access
cylinders beyond 1024 while using the LINEAR option. See section "BIOS
restrictions" for more details and for how to solve the problem.
0x01 "Illegal command". This shouldn't happen, but if it does, it
may indicate an attempt to access a disk which is not supported by the
BIOS. See also "Warning: BIOS drive 0x<number> may not be accessible"
in section "Warnings".
0x02 "Address mark not found". This usually indicates a media
problem. Try again several times.
0x03 "Write-protected disk". This should only occur on write
operations.
0x04 "Sector not found". This typically indicates a geometry
mismatch. If you're booting a raw-written disk image, verify whether
it was created for disks with the same geometry as the one you're
using. If you're booting from a SCSI disk or a large IDE disk, you
should check, whether LILO has obtained correct geometry data from the
kernel or whether the geometry definition corresponds to the real disk
geometry. (See section "Disk geometry".) Removing COMPACT may help
too. So may adding LINEAR.
0x06 "Change line active". This should be a transient error. Try
booting a second time.
0x07 "Invalid initialization". The BIOS failed to properly
initialize the disk controller. You should control the BIOS setup
parameters. A warm boot might help too.
0x08 "DMA overrun". This shouldn't happen. Try booting again.
0x09 "DMA attempt across 64k boundary". This shouldn't happen.
Try omitting the COMPACT option.
0x0C "Invalid media". This shouldn't happen and might be caused
by a media error. Try booting again.
0x10 "CRC error". A media error has been detected. Try booting
several times, running the map installer a second time (to put the map
file at some other physical location or to write "good data" over the
bad spot), mapping out the bad sectors/tracks and, if all else fails,
replacing the media.
0x11 "ECC correction successful". A read error occurred, but was
corrected. LILO does not recognize this condition and aborts the load
process anyway. A second load attempt should succeed.
0x20 "Controller error". This shouldn't happen.
0x40 "Seek failure". This might be a media problem. Try booting
again.
0x80 "Disk timeout". The disk or the drive isn't ready. Either
the media is bad or the disk isn't spinning. If you're booting from a
floppy, you might not have closed the drive door. Otherwise, trying to
boot again might help.
0xBB "BIOS error". This shouldn't happen. Try booting again. If
the problem persists, removing the COMPACT option or adding/removing
LINEAR might help.
If the error occurred during a write operation, the error code (two
hex digits) is prefixed with a "W". Although write errors don't affect
the boot process, they might indicate a severe problem, because they
usually imply that LILO has tried to write to an invalid location. If
spurious write errors occur on a system, it might be a good idea to
configure LILO to run read-only (see section "Build-time
configuration").
Generally, invalid geometry and attempts to use more than two disks
without a very modern BIOS may yield misleading error codes. Please
check carefully if /sbin/lilo doesn't emit any warnings. Then try
using the LINEAR option (see section "Global options").
|
|I hava a Gigabyte GA71XE mainboard wth an AMD Athlon 700
|
|Could someone pls help?
|
|Thanx,
|Floris
|
|
--
SooperGrover
A tanned skin indicates the beginning of carcinogen melanoma...
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: CDR and sound card under SUSE linux 6.4
Date: 17 Jun 2000 17:22:07 GMT
Esther Klabbers <[EMAIL PROTECTED]> wrote:
: I don't know what you mean by where is it plugged in. It is an IDE2
What do you mean by "what do you mean by where is it plugged in"? Which
word do you not understand? It is a peripheral. That means it is
connected to the computer by cables that carry information between
it and the rest of the system. Those cables go somewhere. They
could go to a scsi controller. They could go to a special soundcard
socket. They could go to an ide controller. In your case it sounds
like they are plugged in to the second IDE controller, so your cd will
be /dev/hdc or /dev/hdd, depending on whether it is respectively master
or slave on the controller. It will be master (and should be configured
as master) if it is alone on the controller. If there is an IDE disk on
the controller too, then it must and will be configured as slave.
: CD-ROM.
: The error message I get is:
: mount: block device /dev/hdc is write protected, mounting read-only. On
That's not an error message, that's a fact. You can't write to a cdrom!
So everything is working OK.
: my KDE desktop trying to mount the CD-ROM leads to the message:
: mount: the kernel doesn't recognize /dev/cdrom as a block device (maybe
: 'insmod driver'?). However, going to /cdrom does allow me to view the
: contents of the CD-ROM now.
So forget about the message from kde and tell the authors about it so
they can fix it.
: alsa-conf seems to work. It recognizes the sound card as CS4236B. But
: still I don't hear anything.
That IS a crystal. I have one of those on a laptop and it works fine
with alsa drivers.
: Thanks for your trouble so far. Bye the way, the floppy disk has the
: same problem when trying to mount it. It says /dev/fd0 is not a valid
: block device.
Tell us what you did and what the message was. EXACTLY. Anything else is
no good as an error report. It doesn't help you or us.
It sounds like you didn't have a floppy in the drive or you didn't have
mount permissions or your driver wasn't loaded. I can't tell without a
clear and exact description.
Peter
------------------------------
From: Edward Lee <[EMAIL PROTECTED]>
Subject: Re: CDR and sound card under SUSE linux 6.4
Date: Sat, 17 Jun 2000 10:42:27 -0700
Alsa drivers might not be handling the chip properly. On a labtop, your
bios helps. But on add-on cards, try http://linnix.com. Linux 2.4 is
recommeded for the CSC4236. E-mail me if you need more details.
"Peter T. Breuer" wrote:
>
> : alsa-conf seems to work. It recognizes the sound card as CS4236B. But
> : still I don't hear anything.
>
> That IS a crystal. I have one of those on a laptop and it works fine
> with alsa drivers.
>
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Compatibility, pls help (Newbie question)
Date: 17 Jun 2000 14:21:02 EDT
Reply-To: [EMAIL PROTECTED]
On Sat, 17 Jun 2000 17:18:22 +0100, turbo
<<[EMAIL PROTECTED]>> shouted forth into the ether:
>Hi
>I would like to buy a new computer. The computer I would like to buy is a
>Dell Dimension XPS T800. It has a Intel Pentium 111, 128mb, 15Gb IDE hard
^^^
I fall asleep for 2 hours, and Intel jacks the version numbers up beyond
all recognition? Figures. (Hint: It's "3" or "III", or if you're on
Intel's marketing team, it's "!!!".)
>The monitor is a Dell 17' monitor Viewable area) The video adaptor is a 32mb
>Nvida m64 TNT X2 video card. The sound card is a Creative labs 64V sound.
>Can anyone pls tell me if this computer will be compatible with Redhat 6.2?
Processor: fine
Monitor: fine
Hard Drive: fine
Video: probably (you mean "TNT2", don't you? If so, yes.)
Sound: see below
"Creative Labs 64V" means nothing. However, most Creative cards these
days use the ES1370, ES1371, or emu10k chipsets, all of which are
supported. RedHat 6.2 comes with the "sndconfig" utility, which you
should run once you've gone through the install process.
If you want to make your newbie period as short as possible, go to
http://linuxdoc.org/HOWTO/ and http://linuxnewbie.org/ as well as reading
the manual that comes with the RH 6.2 boxed set and possibly getting a
book like _Running Linux_.
--
Matt G / Dances With Crows /\ "Man could not stare too long at the face
\----[this space for rent]-----/ \ of the Computer or her children and still
\There is no Darkness in Eternity \ remain as Man." --David Zindell "So did
But only Light too dim for us to see\ they become Gods, or Usenetters?" --/me
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Dumping Windows
Date: 17 Jun 2000 14:27:05 EDT
Reply-To: [EMAIL PROTECTED]
On Sat, 17 Jun 2000 15:55:40 GMT, Kevin Clark
<<[EMAIL PROTECTED]>> shouted forth into the ether:
>I have linux installed on my slave hard drive hdb (swap, boot, root)
>Windows is installed on my master hard drive hda
>Lilo is installed on MBR on hda
>I want to get rid of windows and make hda a linux drive and still be
>able to boot.
>What are the steps to get this done and what call the new mount? /usr?
>Even tho /usr exists on hdb
0. cfdisk /dev/hda
(create Linux partitions)
1. mke2fs those partitions you created
2. mount one of your new partitions on, say, /mnt/new
3. copy everything from your current /usr to /mnt/new.
4. make sure everything copied over OK.
5. delete everything from /usr
6. umount /mnt/new
7. mount /dev/hdaX /usr
8. If that worked well and did what you wanted, put the following line in
/etc/fstab:
/dev/hdaX /usr defaults 0 2
Then /usr will be mounted automatically at boot time, and it'll be on the
other hard drive.
--
Matt G / Dances With Crows /\ "Man could not stare too long at the face
\----[this space for rent]-----/ \ of the Computer or her children and still
\There is no Darkness in Eternity \ remain as Man." --David Zindell "So did
But only Light too dim for us to see\ they become Gods, or Usenetters?" --/me
------------------------------
From: <.>
Subject: RH6.2 mke2fs crashes on install
Date: Sat, 17 Jun 2000 14:09:41 -0500
Crossposted-To: comp.os.linux.help,comp.os.linux.setup
problem: mke2fs crashes during installation
OS: RedHat6.2
hardware:
ASUS P3B-F (intel 440BX chipset)
intel P3-550E
256Mb ram
Adaptec 2940 + Seagate Cheetah 9.1Gb (also tried with WD 15Gb IDE
drives)
details: when I flip to console during install I can see the output of
mke2fs. it always dies somewhere in "writing inode tables: n/m" (5/66, or
37/227, etc. etc.)
crash dump overview: (this part is always the same, no matter what
partitioning or what drive I'm using.)
Oops: 0000
CPU: 0
EIP: 0010:[<c0125224>]
EFLAGS: 00010206
***
any help would be greatly appreciated. this is all pretty standard
hardware. I originally thought it was the IDE drives, so I went to a nice
scsi. it still bombs, so apparently the problem is something else. perhaps
the memory is bad and I just don't discover it until this point?
also, I tried the suse6.4 install and it fails in the same place (I guess...
I can't see console window, but it says it's formatting HD)
thanks,
michael
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Hal Burgiss)
Subject: Re: Dumping Windows
Reply-To: [EMAIL PROTECTED]
Date: Sat, 17 Jun 2000 19:02:27 GMT
On 17 Jun 2000 14:27:05 EDT, Dances With Crows
<[EMAIL PROTECTED]> wrote:
>
>0. cfdisk /dev/hda
>(create Linux partitions)
>1. mke2fs those partitions you created
>2. mount one of your new partitions on, say, /mnt/new
>3. copy everything from your current /usr to /mnt/new.
Would suggest to use 'cp -a' for this to preserve symlinks, etc. Just in
case the original poster is not aware ...
--
Hal B
[EMAIL PROTECTED]
--
------------------------------
From: root <[EMAIL PROTECTED]>
Subject: Trouble with cdrecord..:<
Date: Sat, 17 Jun 2000 14:06:48 -0500
Hello! I am experiencing a frustrating problem, so 4 or so coasters
later, here i am.
Here is the standard output of a dummy write using gtoaster:
everything "appears" to be normal.to this point, and then.....
fixating CDROM.
Cdrecord 1.8.1 (i586-mandrake-linux-gnu) Copyright (C) 1995-2000 J�rg
Schilling
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Using libscg version 'schily-0.1'
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'HP '
Identifikation : 'CD-Writer+ 7500 '
Revision : '1.0a'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO
Starting to write CD/DVD at speed 2 in dummy mode for single session.
Last chance to quit, starting dummy write in 9 seconds.8
seconds.7 seconds.6 seconds.5
seconds.4 seconds.3 seconds.2
seconds.1 seconds.
CDB: 55 10 00 00 00 00 00 00 10 00
Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 26 00 00 80
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x26 Qual 0x00 (invalid field in parameter list) Fru 0x0
Sense flags: Blk 0 (not valid) error refers to data part, bit ptr 0 (not
valid) field ptr 0
cmd finished after 0.007s timeout 40s
cdrecord: Input/output error. mode select g1: scsi sendcmd: retryable
error
status: 0x2 (CHECK CONDITION)
CD recording process finished.
--
I have two 2.2.16 kernels compiled..one using no scsi modules (all scsi
suupport is compiled into the kernel)
and one where its modulized..
what is interesting is that when i was using 2.2.14 , a similar setup
used the sg.o module..but i havent been able to use that yet despite its
presence in /lib/modules/2.2.16/
ANY suggestions are always welcome :)
Tia,
meany
------------------------------
** 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
******************************
