Linux-Hardware Digest #579, Volume #12 Thu, 30 Mar 00 16:13:09 EST
Contents:
37.5 GB and Linux ("Bill")
Re: Infra-red transceiver Project ? (Robie Basak)
Re: cdrom drives? (Dances With Crows)
Re: 37.5 GB and Linux ([EMAIL PROTECTED])
Re: Dual processor (Dances With Crows)
Re: Problem Modem (Dave Eikel)
Re: Infra-red transceiver Project ? (Georg Lukas)
Re: Dual processor (jwk)
Re: My serial port ttyS3 doesn't work ([EMAIL PROTECTED])
Brainless modems ("Powerkiter")
raid help (Andy Harrison)
raid help (Andy Harrison)
NIC disappeared (Jonah)
cd writer trouble: CDRW works. CDR doesn't. (jonnyc)
Asus CU-WE i810E with Linux (James Ho)
----------------------------------------------------------------------------
From: "Bill" <[EMAIL PROTECTED]>
Subject: 37.5 GB and Linux
Date: Thu, 30 Mar 2000 12:38:55 -0600
I have an IBM 37.5 GB hard disk and I'm trying to duel boot Windows 98 SE
and Linux. In the oversize disk HOWTO
(http://www.linuxdoc.org/HOWTO/Large-Disk-HOWTO-12.html#ss12.1), it mentions
that a distribution running the 2.2.14 kernel will survive the insane 33.8
GB Linux booting limit. Does this mean that I can successfully install
RedHat Linux 6.2 (the new RedHat with the Linux 2.2.14 kernel) on hard drive
with partitions like:
========
| Windoze (GBs 1-19)
| |
| |
| |
=========
| RH 6.2 (20-37.5)
| |
| |
| |
=========
Note: I can't seem to duel boot the RH 6.1 and Windoze. I've had many
problems each and every time I try it and I've had to delete all partitions
on my drive and install Windoze using its own CDROM disc and its simple
fdisk.
------------------------------
From: [EMAIL PROTECTED] (Robie Basak)
Subject: Re: Infra-red transceiver Project ?
Reply-To: [EMAIL PROTECTED]
Date: 30 Mar 2000 18:40:17 GMT
http://fsinfo.cs.uni-sb.de/~columbus/lirc/index.html
Robie.
On Wed, 29 Mar 2000 19:04:26 GMT, Andre-John Mas said:
>Hi,
>Does anyone know of any projects that would show me how to add
>an infra-red transceiver to a PC and how I could program it under
>Linux to respond to TV-controller type device?
>Andre
>--
>http://www.bigfoot.com/~ajmas/
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
--
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: cdrom drives?
Date: 30 Mar 2000 14:17:31 EST
Reply-To: [EMAIL PROTECTED]
On Thu, 30 Mar 2000 17:54:59 GMT, Steve Maughan
<<[EMAIL PROTECTED]>> shouted forth into the ether:
>My old 6X CD drive is finally giving up on me so I'm looking at getting
>a new cd-rom drive (i'm a student and I can't afford a DVD drive at such
>short notice).
>
>I assume that all of the following drives are ATAPI compliant and work
>under linux: what I want to know is how well do they work under linux
>and more importantly, which one can anyone recommend/unrecommend...
>
>The drives are:
> Aopen IDE 48X (CD940E)
> Asustek IDE 40X (CD-S400 40)
> Creative Labs IDE 52X
> Teac IDE 40X (CD-540E)
40x drives are noisy as hell, and often slower than drives that run 24x
since the 40x drives seem to spend about 30 seconds spun up before they
spin down to save power. Then, of course, they take 5 or 6 seconds to
spin up again... royal pain for normal use/access patterns.
Unless you have unusual requirements (like you're an extreme audiophile)
then CD-ROMs are basically a commodity item. Get a 24x or so that's a
step or 2 up from the cheapest available; you'll save a few bucks and
it'll hold you until you get a DVD and/or CD-RW.
--
Matt G / Dances With Crows \###| Programmers are playwrights
There is no Darkness in Eternity \##| Computers are lousy actors
But only Light too dim for us to see \#| Lusers are vicious drama critics
(Unless, of course, you're working with NT)\| BOFHen burn down theatres.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: 37.5 GB and Linux
Date: Thu, 30 Mar 2000 19:11:38 GMT
In article <P9NE4.119$d6.2256@uchinews>,
"Bill" <[EMAIL PROTECTED]> wrote:
> I have an IBM 37.5 GB hard disk and I'm trying to duel boot Windows 98
SE
> and Linux. In the oversize disk HOWTO
> (http://www.linuxdoc.org/HOWTO/Large-Disk-HOWTO-12.html#ss12.1), it
mentions
> that a distribution running the 2.2.14 kernel will survive the insane
33.8
> GB Linux booting limit. Does this mean that I can successfully install
> RedHat Linux 6.2 (the new RedHat with the Linux 2.2.14 kernel) on hard
drive
> with partitions like:
> --------
> | Windoze (GBs 1-19)
> | |
> | |
> | |
> ---------
> | RH 6.2 (20-37.5)
> | |
> | |
> | |
> ---------
>
> Note: I can't seem to duel boot the RH 6.1 and Windoze. I've had many
> problems each and every time I try it and I've had to delete all
partitions
> on my drive and install Windoze using its own CDROM disc and its
simple
> fdisk.
What I did on the 30G drive that came with my system was use Partition
Magic and put the ext2 partition *in front of* the Windoze partition.
Dual boot works just fine with Mandrake 7.x
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Dual processor
Date: 30 Mar 2000 14:22:42 EST
Reply-To: [EMAIL PROTECTED]
On Thu, 30 Mar 2000 20:06:55 +0200, Tom Haeck
<<8c052g$iq1$[EMAIL PROTECTED]>> shouted forth into the ether:
>Hello everybody,
>
>I have a CPU-board with 2 x PIII-500. I installed SUSE 6.2 on it. It was
>installed, and the CPU monitor in KDE only showed me one CPU. So I concluded
>that the basic installation of SUSE doesn't use the 2nd processor (Is this
Unless there's an option for "Install kernel with SMP support" during the
installation process, no. Most people still have uniprocessor machines,
and an SMP kernel runs slower on a UP machine, so SuSE went with UP as the
default. RedHat went with SMP as the default.
>So, I recompiled my Kernel, but still I can see only 1 CPU in the
>CPU-monitor. How can I be sure that Linux uses the 2 processors? And what
>must I do in order to make them work?
Compile the kernel with SMP support. You did that, right?
There are a whole bunch of different applications that report CPU load in
a window or whatever; some of these lack multi-processor support. If you
do a "cat /proc/cpuinfo" and see only one CPU, only one is being used.
If two show up, they're both being used. Simple, eh?
--
Matt G / Dances With Crows \###| Programmers are playwrights
There is no Darkness in Eternity \##| Computers are lousy actors
But only Light too dim for us to see \#| Lusers are vicious drama critics
(Unless, of course, you're working with NT)\| BOFHen burn down theatres.
------------------------------
From: Dave Eikel <[EMAIL PROTECTED]>
Subject: Re: Problem Modem
Date: Thu, 30 Mar 2000 19:47:06 GMT
Most PCI modems are Windows only modems and you may need to replace
yours. Look at the modem card itself and see if it has any jumpers on
it.
If it does not, then you are basically hosed.
"Pablo Gonz=E1lez =C1lvarez" wrote:
> =
> I have a problem to configurate a PCI rockwell modem 56K.
------------------------------
From: Georg Lukas <[EMAIL PROTECTED]>
Subject: Re: Infra-red transceiver Project ?
Date: Thu, 30 Mar 2000 21:55:59 +0200
Hi,
I'm owner of a notebook with a builtin IrDA port. Is there a way to use
it to send/receive remote control messages to controll the PC remotely
or to "magically" switch the TV channel?
I'm searching for any kind of ressources...
Georg Lukas
------------------------------
From: [EMAIL PROTECTED] (jwk)
Subject: Re: Dual processor
Date: 30 Mar 2000 20:08:08 GMT
Reply-To: [EMAIL PROTECTED]
On Thu, 30 Mar 2000 20:06:55 +0200, Tom Haeck
<[EMAIL PROTECTED]> wrote:
>Hello everybody,
>
>I have a CPU-board with 2 x PIII-500. I installed SUSE 6.2 on it. It was
>installed, and the CPU monitor in KDE only showed me one CPU. So I concluded
>that the basic installation of SUSE doesn't use the 2nd processor (Is this
>so?).
>So, I recompiled my Kernel, but still I can see only 1 CPU in the
>CPU-monitor. How can I be sure that Linux uses the 2 processors? And what
>must I do in order to make them work?
>
>Thanks in advance,
>
>TH
>
Recompile the kernel, and set Symmetric multi-processing support to TRUE
in the second chapter of the menu.
Then make sure you install your new kernel, and reboot.
Then type cat /proc/cpuinfo and see:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 560.800991
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 mmx fxsr xmm
bogomips : 1117.39
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 560.800991
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 mmx fxsr xmm
bogomips : 1120.67
Good luck,
Jurriaan
--
proof by example:
The author gives only the case n = 2 and suggests that it
contains most of the ideas of the general proof.
Linux 2.2.15pre14 SMP 4 users load av: 0.00 0.00 0.00
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.redhat
Subject: Re: My serial port ttyS3 doesn't work
Date: Thu, 30 Mar 2000 20:09:25 GMT
>>[EMAIL PROTECTED] wrote:
>>>
>>>
>>> I have been trying for some time without success to
>>> get my "ttyS3" port to work. I'm stumped. Can
>>> anyone help me? Here are some details...
In article <[EMAIL PROTECTED]>,
John McDowell <[EMAIL PROTECTED]> wrote:
>
> If you can set your modem to Com 1, IRQ 4/ 03f8-03FF, ttyS00 will
> work.......at least it did in my 2 Linux machines. If the modem has
> jumpers, this is a piece of cake. Set to 16550A
>
> ttyS01 is Com 2, IRQ 3/orf8 and ttS02 is Com 3, IRQ 4/03e8
>
> Good Luck,
> Fuzz
>
My modem and my ttyS0 already work.
My objective is to unfreeze ttyS3.
Thanks anyway,
rkarmo
PS: I can not set my modem to Com 1, IRQ 4/ 03f8-03FF.
My modem does not have jumpers, nor a 16550A UART.
Or did you mean to connect the serial cable to COM1?
Setting my modem to ttyS0 would interfere with my serial mouse, anyway.
I think COM2 is not "orf8".
My ttyS devices have no 0's (except in the bootup messages).
and finally my COM3 is "ttyS2", not "ttS02".
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "Powerkiter" <[EMAIL PROTECTED]>
Subject: Brainless modems
Date: Thu, 30 Mar 2000 22:22:39 +0200
Will I see the day when LINUX supports softmodems or braindead modems as I
often read.
TIA
Powerkiter
------------------------------
From: Andy Harrison <[EMAIL PROTECTED]>
Subject: raid help
Date: Thu, 30 Mar 2000 15:25:33 -0500
Have big trouble with my server here. Anyone have any
advice?
This unit was working perfectly fine. I powered it
off, transported it to the office, and powered it back on.
I was very careful and the machine did not get dropped,
shaken, bumped, or severely jarred in any way.
Don't even know what the "bad magic" error means...
sdc, sdd, sde, sdf drives are all in one external chassis,
while sdg and sdh are in individual external chassis. sda
and sdb are internal.
Here's the log clipping from booting up:
================
Mar 30 20:06:00 nachoz kernel: scsi : detected 1 SCSI cdrom 8 SCSI disks total.
Mar 30 20:06:00 nachoz kernel: esp0: target 6 asynchronous
Mar 30 20:06:00 nachoz kernel: Uniform CDROM driver Revision: 2.56
Mar 30 20:06:00 nachoz kernel: esp0: target 0 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp0: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdb: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdc: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 2 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdd: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 3 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sde: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 4 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdf: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp2: target 0 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdg: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp2: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdh: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: Partition check:
Mar 30 20:06:00 nachoz kernel: sda: sda1 sda3
Mar 30 20:06:00 nachoz kernel: sdb: sdb1 sdb2 sdb3
Mar 30 20:06:00 nachoz kernel: sdc: sdc1 sdc3
Mar 30 20:06:00 nachoz kernel: sdd:Dev 08:30 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sde:Dev 08:40 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdf:Dev 08:50 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdg:Dev 08:60 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdh: sdh1 sdh3
================
If I try running the following, I get:
# e2fsck /dev/sdg
e2fsck 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdg
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
My raidtab is as follows:
================
#
# compatible (old) RAID0 setup:
#
raiddev /dev/md1
raid-level 0
nr-raid-disks 3
#persistent-superblock 1
persistent-superblock 0
chunk-size 32
device /dev/sdh1
raid-disk 0
device /dev/sdb2
raid-disk 1
device /dev/sdg1
raid-disk 2
raiddev /dev/md2
raid-level 0
nr-raid-disks 4
#persistent-superblock 1
persistent-superblock 0
chunk-size 32
device /dev/sdc1
raid-disk 0
device /dev/sdd1
raid-disk 1
device /dev/sde1
raid-disk 2
device /dev/sdf1
raid-disk 3
================
# cat /proc/mdstat
Personalities :
read_ahead not set
unused devices: <none>
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: TOSHIBA Model: XM-5401TASUN4XCD Rev: 1036
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 03 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
# more /proc/scsi/esp/*
::::::::::::::
0
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0062ff8
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 0 1 6 ]
Target # config3 Sync Capabilities Disconnect Wide
0 000000c3 [0f,04] yes yes
1 000000c3 [0f,04] yes yes
6 00000081 [0f,04] yes no
::::::::::::::
1
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0078cbc
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 1 2 3 4 ]
Target # config3 Sync Capabilities Disconnect Wide
1 000000c3 [0f,04] yes yes
2 000000c3 [0f,04] yes yes
3 000000c3 [0f,04] yes yes
4 000000c3 [0f,04] yes yes
::::::::::::::
2
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0085aec
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 0 1 ]
Target # config3 Sync Capabilities Disconnect Wide
0 000000c3 [0f,04] yes yes
1 000000c3 [0f,04] yes yes
--
Andy Harrison
Time Warner Cable of Maine
Road Runner Associate Systems Administrator
[EMAIL PROTECTED]
ICQ: 1467660 AIM: AndyHarrisonRR
------------------------------
From: Andy Harrison <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,linux.redhat.sparc
Subject: raid help
Date: Thu, 30 Mar 2000 15:29:31 -0500
Having big trouble with my server here. Anyone have any
advice?
This unit was working perfectly fine. I powered it
off, transported it to the office, and powered it back on.
I was very careful and the machine did not get dropped,
shaken, bumped, or severely jarred in any way.
Don't even know what the "bad magic" error means...
sdc, sdd, sde, sdf drives are all in one external chassis,
while sdg and sdh are in individual external chassis. sda
and sdb are internal.
(Running rh6.1 on a sparc u2)
Here's the log clipping from booting up:
================
Mar 30 20:06:00 nachoz kernel: scsi : detected 1 SCSI cdrom 8 SCSI disks total.
Mar 30 20:06:00 nachoz kernel: esp0: target 6 asynchronous
Mar 30 20:06:00 nachoz kernel: Uniform CDROM driver Revision: 2.56
Mar 30 20:06:00 nachoz kernel: esp0: target 0 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp0: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdb: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdc: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 2 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdd: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 3 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sde: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp1: target 4 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdf: hdwr sector= 512 bytes. Sectors=
8386733 [4095 MB] [4.1 GB]
Mar 30 20:06:00 nachoz kernel: esp2: target 0 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdg: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: esp2: target 1 [period 100ns offset 15 20.00MHz
FAST-WIDE SCSI-II]
Mar 30 20:06:00 nachoz kernel: SCSI device sdh: hdwr sector= 512 bytes. Sectors=
4194995 [2048 MB] [2.0 GB]
Mar 30 20:06:00 nachoz kernel: Partition check:
Mar 30 20:06:00 nachoz kernel: sda: sda1 sda3
Mar 30 20:06:00 nachoz kernel: sdb: sdb1 sdb2 sdb3
Mar 30 20:06:00 nachoz kernel: sdc: sdc1 sdc3
Mar 30 20:06:00 nachoz kernel: sdd:Dev 08:30 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sde:Dev 08:40 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdf:Dev 08:50 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdg:Dev 08:60 Sun disklabel: bad magic 0000
Mar 30 20:06:01 nachoz kernel: unknown partition table
Mar 30 20:06:01 nachoz kernel: sdh: sdh1 sdh3
================
If I try running the following, I get:
# e2fsck /dev/sdg
e2fsck 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdg
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
My raidtab is as follows:
================
#
# compatible (old) RAID0 setup:
#
raiddev /dev/md1
raid-level 0
nr-raid-disks 3
#persistent-superblock 1
persistent-superblock 0
chunk-size 32
device /dev/sdh1
raid-disk 0
device /dev/sdb2
raid-disk 1
device /dev/sdg1
raid-disk 2
raiddev /dev/md2
raid-level 0
nr-raid-disks 4
#persistent-superblock 1
persistent-superblock 0
chunk-size 32
device /dev/sdc1
raid-disk 0
device /dev/sdd1
raid-disk 1
device /dev/sde1
raid-disk 2
device /dev/sdf1
raid-disk 3
================
# cat /proc/mdstat
Personalities :
read_ahead not set
unused devices: <none>
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: TOSHIBA Model: XM-5401TASUN4XCD Rev: 1036
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 03 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 04 Lun: 00
Vendor: SEAGATE Model: ST15230W SUN4.2G Rev: 0738
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
# more /proc/scsi/esp/*
::::::::::::::
0
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0062ff8
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 0 1 6 ]
Target # config3 Sync Capabilities Disconnect Wide
0 000000c3 [0f,04] yes yes
1 000000c3 [0f,04] yes yes
6 00000081 [0f,04] yes no
::::::::::::::
1
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0078cbc
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 1 2 3 4 ]
Target # config3 Sync Capabilities Disconnect Wide
1 000000c3 [0f,04] yes yes
2 000000c3 [0f,04] yes yes
3 000000c3 [0f,04] yes yes
4 000000c3 [0f,04] yes yes
::::::::::::::
2
::::::::::::::
Sparc ESP Host Adapter:
PROM node f0085aec
PROM name SUNW,fas
ESP Model Happy Meal FAS
DMA Revision Rev HME/FAS
Live Targets [ 0 1 ]
Target # config3 Sync Capabilities Disconnect Wide
0 000000c3 [0f,04] yes yes
1 000000c3 [0f,04] yes yes
--
Andy Harrison
Time Warner Cable of Maine
Road Runner Associate Systems Administrator
[EMAIL PROTECTED]
ICQ: 1467660 AIM: AndyHarrisonRR
------------------------------
From: Jonah <[EMAIL PROTECTED]>
Subject: NIC disappeared
Date: Thu, 30 Mar 2000 20:30:24 GMT
I have a RH6.1 machine that I am trying to make into a firewall. I had a
kernel that allowed me to use 2 NIC's but after building a rule set I found
that ip masq probably wasn't turned on. So I decided to upgrade and
rebuild it. Now 1 of my NIC's has disappeared. what was eth0 is now
unreachable and eth1 is now eth0. I've done teh /sbin/modprobe ne io=0x300
( the address of the eth0 I want) and once that is complete and I perform
teh ifup eth0 I check the card by executing the ifconfig command and I see
that the card at 0x260 was loaded into eth0 and that the device eth1
doesn't exist...
kind of long winded, but I'm in a hurry... I need to get this done as soon
as I can and I believe it should be working once this setback is overcome.
Jonah
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: jonnyc <[EMAIL PROTECTED]>
Subject: cd writer trouble: CDRW works. CDR doesn't.
Date: Thu, 30 Mar 2000 20:31:23 GMT
Hi -
I'm having a funky problem with my HP7200 external cd writer on a
RH6.1/win98 dual boot machine:
data CDRs burned under win98 work perfectly (haven't had a failure yet).
data CDRs burned under RH6.1 FAIL completely (burn ok, but won't mount).
data CDRWs burned under RH6.1 work perfectly.
That's right, if run the same burn script on a CDR and a CDRW the CDRW
comes out fine, but the CDR doesn't. I know the CDR media is ok because
I've burned a dozen of them under Windows. But all four that I've tried
under Linux won't mount.
Anyone have any suggestions? Do I need to set any "media" switches in
cdrecord?
Regards - Jon
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: James Ho <[EMAIL PROTECTED]>
Subject: Asus CU-WE i810E with Linux
Date: Thu, 30 Mar 2000 22:08:43 +1000
Hi there.
Can anyone tell me if All-In-One motherboard are any good to Linux?
Does Linux supports it well? Or is there any difference with normal
motherboards?
The model I am particularly interested is Asus CU-WE i810E. Its spec
can be found from
http://www.asus.com.tw/products/motherboard/pentiumpro/cuwe/index.html
Thanks heaps.
James.
Fatal Error: Found [MS-Windows] System -> Repartitioning Disk for Linux...
------------------------------
** 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
******************************
