[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taroon-beta-list
Subject:    RE: S/390 Installation - Device Drivers
From:       "Post, Mark K" <mark.post () eds ! com>
Date:       2003-09-30 15:53:09
Message-ID: 564DE4477544D411AD2C00508BDF0B6A19634C5F () usahm018 ! exmi01 ! exch ! eds ! com
[Download RAW message or body]

If that fixed the problem, then that should report that as a bug.  There's
no reason why the DASD device driver shouldn't be able to handle unformatted
volumes like that.


Mark Post

-----Original Message-----
From: Clark, Ray R [ITS] [mailto:Ray.Clark@mail.sprint.com]
Sent: Tuesday, September 30, 2003 11:49 AM
To: taroon-beta-list@redhat.com
Subject: RE: S/390 Installation - Device Drivers


That's the key, Rob.  Thanks for your help.

-----Original Message-----
From: Rob van der Heij [mailto:rvdheij@iae.nl] 
Sent: Tuesday, September 30, 2003 7:59 AM
To: taroon-beta-list@redhat.com
Subject: Re: S/390 Installation - Device Drivers


Clark, Ray R [ITS] wrote:
> Ya, the /proc/dasd/devices file was a mess before I moved the DASD= 
> line down, but even with it later in the parmfile, I still get the 
> driver errors.

I have not found how the installer detects disks, but it
looks like it cannot handle unformatted disks. If you can format them
with another Linux machine first (or even with the SuSE trial starter
system ;-) that probably helps.

Think I did manage to run dasdfmt on the Red Hat starter system, but it
took some tweaking to get things right.

Rob


--
Taroon-beta-list mailing list
Taroon-beta-list@redhat.com
http://www.redhat.com/mailman/listinfo/taroon-beta-list


--
Taroon-beta-list mailing list
Taroon-beta-list@redhat.com
http://www.redhat.com/mailman/listinfo/taroon-beta-list



[prev in list] [next in list] [prev in thread] [next in thread]