Re: Bordeaux fails install

[Erick Calder]

I tried your suggestion but get:

"Unable to read package metadata.  This may be due to a missing repodata
directory.  Please ensure that your install tree has been correctly
generated.  Failure: repodata/primary.xml.gz from anaconda: [Errno: 256].
No more mirrors to try."

grr... what next?

>  From: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Reply-To: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Date: Wed, 19 Apr 2006 23:44:31 -0700
>  To: Erick Calder <e(a)arix.com&gt;
>  Cc: <fedora-ppc(a)lists.infradead.org&gt;
>  Subject: Bordeaux fails install
>  
>  Erick Calder writes:
> > I then tried a network install, in case the drive had problems.  I attempted
> > an FTP-based install but with similar results.
>  
>  I've done a half dozen G5 DVD installs of FC5 ppc without significant
>  issues (the only real one is that yaboot doesn't work on a G5 2.0GHz we
>  have.
>  
>  I also have done two network installs, one a fresh install on ppc and
>  the other an ugprade install on i386. For ppc try HTTP to
>  mirrors.kernel.org:fedora/core/4/ppc/os/. In the network installs I just
>  used the rescue CD.
>  
>  -bri

Bordeaux fails install

[Brian D. Carlstrom]

Erick Calder writes:
>  I tried your suggestion but get:
>  
>  "Unable to read package metadata.  This may be due to a missing repodata
>  directory.  Please ensure that your install tree has been correctly
>  generated.  Failure: repodata/primary.xml.gz from anaconda: [Errno: 256].
>  No more mirrors to try."
>  
>  grr... what next? 
Perhaps try the correct URL, which is not what I provided. oops! :)
NOTE I had a 4, not a 5, for the fedora core version. 

I just checked and this is a real file:
    http://mirrors.kernel.org/fedora/core/5/ppc/os/repodata/primary.xml.gz
so you need to enter
   mirrors.kernel.org
   /fedora/core/5/ppc/os
in the installer.

>  
>  > From: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  > Reply-To: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  > Date: Wed, 19 Apr 2006 23:44:31 -0700
>  > To: Erick Calder <e(a)arix.com&gt;
>  > Cc: <fedora-ppc(a)lists.infradead.org&gt;
>  > Subject: Bordeaux fails install
>  > 
>  > Erick Calder writes:
>  >> I then tried a network install, in case the drive had problems.  I attempted
>  >> an FTP-based install but with similar results.
>  > 
>  > I've done a half dozen G5 DVD installs of FC5 ppc without significant
>  > issues (the only real one is that yaboot doesn't work on a G5 2.0GHz we
>  > have.
>  > 
>  > I also have done two network installs, one a fresh install on ppc and
>  > the other an ugprade install on i386. For ppc try HTTP to
>  > mirrors.kernel.org:fedora/core/4/ppc/os/. In the network installs I just
>  > used the rescue CD.
>  > 
>  > -bri
>  
>

Bordeaux fails install

[Erick Calder]

no, I did notice the 4/5 difference and used the correct url... I took a
look with the browser before I entered it into the install process, so I'm
at a loss here...

>  From: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Reply-To: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Date: Fri, 21 Apr 2006 10:51:05 -0700
>  To: Erick Calder <e(a)arix.com&gt;
>  Cc: <fedora-ppc(a)lists.infradead.org&gt;
>  Subject: Re: Bordeaux fails install
>  
>  Erick Calder writes:
> > I tried your suggestion but get:
> > 
> > "Unable to read package metadata.  This may be due to a missing repodata
> > directory.  Please ensure that your install tree has been correctly
> > generated.  Failure: repodata/primary.xml.gz from anaconda: [Errno: 256].
> > No more mirrors to try."
> > 
> > grr... what next?
>  
>  Perhaps try the correct URL, which is not what I provided. oops! :)
>  NOTE I had a 4, not a 5, for the fedora core version.
>  
>  I just checked and this is a real file:
>      http://mirrors.kernel.org/fedora/core/5/ppc/os/repodata/primary.xml.gz
>  so you need to enter
>     mirrors.kernel.org
>     /fedora/core/5/ppc/os
>  in the installer.
>  
> > 
> >> From: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
> >> Reply-To: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
> >> Date: Wed, 19 Apr 2006 23:44:31 -0700
> >> To: Erick Calder <e(a)arix.com&gt;
> >> Cc: <fedora-ppc(a)lists.infradead.org&gt;
> >> Subject: Bordeaux fails install
> >> 
> >> Erick Calder writes:
> >>> I then tried a network install, in case the drive had problems.  I
> >>> attempted
> >>> an FTP-based install but with similar results.
> >> 
> >> I've done a half dozen G5 DVD installs of FC5 ppc without significant
> >> issues (the only real one is that yaboot doesn't work on a G5 2.0GHz we
> >> have.
> >> 
> >> I also have done two network installs, one a fresh install on ppc and
> >> the other an ugprade install on i386. For ppc try HTTP to
> >> mirrors.kernel.org:fedora/core/4/ppc/os/. In the network installs I just
> >> used the rescue CD.
> >> 
> >> -bri
> > 
> >

Bordeaux fails install

[Erick Calder]

my guess was that maybe it had difficulty reaching the mirrors and gave up.
However, I did learn one useful thing, which is the correct layout for a
single-directory that contains the contents of all 5 disks.  I didn't have
it right before, so I fixed that in the laptop and attempted another install
via FTP against my laptop, sadly with similar results as before.

this is making me crazy.  If I verified the checksums of the ISOs I
downloaded, then I know the data is correct, so why does it think stuff is
missing or corrupt?

>  From: Erick Calder <e(a)arix.com&gt;
>  Date: Fri, 21 Apr 2006 20:01:55 -0700
>  To: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Cc: <fedora-ppc(a)lists.infradead.org&gt;
>  Conversation: Bordeaux fails install
>  Subject: Re: Bordeaux fails install
>  
>  no, I did notice the 4/5 difference and used the correct url... I took a
>  look with the browser before I entered it into the install process, so I'm
>  at a loss here...

Bordeaux fails install

[Brian D. Carlstrom]

Erick Calder writes:
>  this is making me crazy.  If I verified the checksums of the ISOs I
>  downloaded, then I know the data is correct, so why does it think stuff is
>  missing or corrupt? 
I recalled this thread from last month on the fedora-test-list. I just
wanted to refer you to it in case it had any helpful information.

-bri

https://www.redhat.com/archives/fedora-test-list/2006-March/msg01631.html

Bordeaux fails install

[Erick Calder]

the article you posted led me to further experimentation and a little
discovery.  it appears that a whole bunch of filenames have gotten
truncated... e.g.

xorg-x11-drv-penmount-1.0.0.5-1
xorg-x11-drv-s3-0.3.5.5-2.ppc.r
xorg-x11-drv-s3virge-1.8.6.5-1.
xorg-x11-drv-savage-2.0.2.3-1.2
xorg-x11-drv-sis-0.8.1.3-1.2.pp
xorg-x11-drv-sisusb-0.7.1.3-1.2
xorg-x11-drv-spaceorb-1.0.0.5-1
xorg-x11-drv-summa-1.0.0.5-1.2.
xorg-x11-drv-tdfx-1.1.1.3-1.3.p
xorg-x11-drv-trident-1.0.1.2-1.
xorg-x11-drv-ur98-1.0.0.5-1.2.p
xorg-x11-drv-vesa-1.0.1.3-1.2.p
xorg-x11-drv-vga-4.0.0.5-2.ppc.
xorg-x11-drv-void-1.0.0.5-1.2.p
xorg-x11-drv-voodoo-1.0.0.5-1.2
xorg-x11-filesystem-7.0-1.noarc
xorg-x11-font-utils-1.0.1-3.ppc
xorg-x11-fonts-base-7.0-3.noarc
xorg-x11-fonts-truetype-7.0-3.n
xorg-x11-server-Xorg-1.0.1-8.pp
xorg-x11-server-utils-1.0.1-1.2
xorg-x11-utils-1.0.1-1.2.ppc.rp
xorg-x11-xauth-1.0.1-1.2.ppc.rp

now, the way I went about this is: after the Bittorrent download I was left
with 6 ISOs.  Double clicking on these (on OSX Panther) causes them to be
mounted... so i'm wondering whether the mount process is failing or if the
ISO contains bad filenames...  could anyone check that or suggest some other
way of extracting the contents of the ISO files?

thx - e

>  From: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Reply-To: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Date: Fri, 21 Apr 2006 20:36:23 -0700
>  To: Erick Calder <e(a)arix.com&gt;
>  Cc: <fedora-ppc(a)lists.infradead.org&gt;
>  Subject: Re: Bordeaux fails install
>  
>  Erick Calder writes:
> > this is making me crazy.  If I verified the checksums of the ISOs I
> > downloaded, then I know the data is correct, so why does it think stuff is
> > missing or corrupt?
>  
>  I recalled this thread from last month on the fedora-test-list. I just
>  wanted to refer you to it in case it had any helpful information.
>  
>  -bri
>  
>  https://www.redhat.com/archives/fedora-test-list/2006-March/msg01631.html

Bordeaux fails install

[Brian D. Carlstrom]

Erick Calder writes:
>  Double clicking on these (on OSX Panther) causes them to be
>  mounted... so i'm wondering whether the mount process is failing or if the
>  ISO contains bad filenames...  could anyone check that or suggest some other
>  way of extracting the contents of the ISO files? 
I've seen this behavior with ISO's mounted by Mac OS X. If I recall the
old Mac OS had something like a 32 character filename length limit,
which is close to what you are seeing. When I hit this problem in the
distance past I just used a Yellow Dog Linux box I had lying around to
work around the issue. Perhaps there is a unix tool available via fink
that would let you extra the ISO. Or perhaps you can use some options
with command line mount to get the right ISO filesystem type.

-bri

Bordeaux fails install

[David Woodhouse]

On Sat, 2006-04-22 at 00:48 -0700, Brian D. Carlstrom wrote:
>  Erick Calder writes:
>   > Double clicking on these (on OSX Panther) causes them to be
>   > mounted... so i'm wondering whether the mount process is failing or if the
>   > ISO contains bad filenames...  could anyone check that or suggest some other
>   > way of extracting the contents of the ISO files?
>  
>  I've seen this behavior with ISO's mounted by Mac OS X. If I recall the
>  old Mac OS had something like a 32 character filename length limit,
>  which is close to what you are seeing.  
$Reasons to _always_ just download or use the install tree directly
instead of mucking around with ISO images++;

-- 
dwmw2

Bordeaux fails install

[Erick Calder]

>  $Reasons to _always_ just download or use the install tree directly
>  instead of mucking around with ISO images++; 
hmm... but if I download the install tree (presumably onto some other
machine), how do I boot the target machine to run the install programme?

-----Original Message-----
From: David Woodhouse [mailto:[e-mail]] 
Sent: Saturday, April 22, 2006 5:18 AM
To: Brian D. Carlstrom
Cc: Erick Calder; fedora-ppc(a)lists.infradead.org
Subject: Re: Bordeaux fails install

On Sat, 2006-04-22 at 00:48 -0700, Brian D. Carlstrom wrote:
>  Erick Calder writes:
>   > Double clicking on these (on OSX Panther) causes them to be
>   > mounted... so i'm wondering whether the mount process is failing or if
the
>   > ISO contains bad filenames...  could anyone check that or
> suggest some 
other
>   > way of extracting the contents of the ISO files?
>  
>  I've seen this behavior with ISO's mounted by Mac OS X. If I recall the
>  old Mac OS had something like a 32 character filename length limit,
>  which is close to what you are seeing.  
$Reasons to _always_ just download or use the install tree directly
instead of mucking around with ISO images++;

-- 
dwmw2

Bordeaux fails install

[Brian D. Carlstrom]

Erick Calder writes:
>  > $Reasons to _always_ just download or use the install tree
> directly
>  > instead of mucking around with ISO images++;
>  
>  hmm... but if I download the install tree (presumably onto some other
>  machine), how do I boot the target machine to run the install programme? 
I thought you downloaded the ISO's and then extracted them on another
machine which was available via FTP. 

I think the other responder is suggesting you download the install tree
using something like rsync to mirrors.kernel.org/fedora/core/5/ppc/os
instead of of using ISOs as an intermediate format.

Since your only problem seems to be that the filesnames were truncated,
you could make a list of RPM's are trucnated based on the file extension
(or lack thereof) and just rename them. Mac OS X has a more reasonable
filename length limit of 255 characters, regardless of their ISO
mounting issues.

-bri

Bordeaux fails install

[Erick Calder]

>  From: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Erick Calder writes:
> > 
> > hmm... but if I download the install tree (presumably onto some other
> > machine), how do I boot the target machine to run the install programme?
>  
>  I thought you downloaded the ISO's and then extracted them on another
>  machine which was available via FTP. 
I did

>  I think the other responder is suggesting you download the install
> tree
>  using something like rsync to mirrors.kernel.org/fedora/core/5/ppc/os
>  instead of of using ISOs as an intermediate format. 
yes, I understand that but my question concerns how to boot.  you see if I
boot from the disc I burnt from the ISO (which is screwed) then the
installer will attempt to install the files it knows to be in disc 1 from
the CD, even though I'm doing a network install - which means that even if I
have the right filenames on the ftp site, it won't read them because it
prefers to read from the CD and thus fails.

Bordeaux fails install

[Brian D. Carlstrom]

Erick Calder writes:
>  you see if I boot from the disc I burnt from the ISO (which is
>  screwed) then the installer will attempt to install the files it
>  knows to be in disc 1 from the CD, even though I'm doing a network
>  install - which means that even if I have the right filenames on the
>  ftp site, it won't read them because it prefers to read from the CD
>  and thus fails. 
I believe you can use the Apple disk utility to burn an ISO (aka disk
image) without extracting it all. It should burn a bit-for-bit copy
without interpreting the contents, preserving the filenames.

In any case, you can burn a rescue CD instead of disc 1. That is what I
did for my network installs, since I wanted to download the minimum ISO
possible.

-bri

Bordeaux fails install

[Erick Calder]

hei everyone,

after a substantially painful process I managed to get Bordeaux installed.
I couldn't upgrade so I had to do a fresh install (grr) but now it's
running.

However, when it boots and I get to the Welcome page I lose mouse and
keyboard.  I have a bluetooth mouse and keyboard which work even at the bios
level (without an OS running) but when FC5 gets to loading the networking I
lose contact with both.

where can I go from here?

>  From: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Reply-To: "Brian D. Carlstrom" <bdc(a)carlstrom.com&gt;
>  Date: Sat, 22 Apr 2006 20:54:52 -0700
>  To: Erick Calder <e(a)arix.com&gt;
>  Cc: 'David Woodhouse' <dwmw2(a)infradead.org&gt;,
> <fedora-ppc(a)lists.infradead.org&gt;
>  Subject: Re: Bordeaux fails install
>  
>  Erick Calder writes:
> > you see if I boot from the disc I burnt from the ISO (which is
> > screwed) then the installer will attempt to install the files it
> > knows to be in disc 1 from the CD, even though I'm doing a network
> > install - which means that even if I have the right filenames on the
> > ftp site, it won't read them because it prefers to read from the CD
> > and thus fails.
>  
>  I believe you can use the Apple disk utility to burn an ISO (aka disk
>  image) without extracting it all. It should burn a bit-for-bit copy
>  without interpreting the contents, preserving the filenames.
>  
>  In any case, you can burn a rescue CD instead of disc 1. That is what I
>  did for my network installs, since I wanted to download the minimum ISO
>  possible.
>  
>  -bri

Bordeaux fails install

[David Woodhouse]

On Sun, 2006-04-30 at 22:50 -0700, Erick Calder wrote:
>  However, when it boots and I get to the Welcome page I lose mouse
> and
>  keyboard.  I have a bluetooth mouse and keyboard which work even at the bios
>  level (without an OS running) but when FC5 gets to loading the networking I
>  lose contact with both.
>  
>  where can I go from here? 
The simple 'fix' is to disable bluetooth services. We have no proper
answer as yet for how Linux is supposed to take over and still handle
the HID devices. If you play with it manually you should probably be
able to get it to work.

-- 
dwmw2

Bordeaux fails install

[Erick Calder]

David Woodhouse
>  On Sun, 2006-04-30 at 22:50 -0700, Erick Calder wrote:
> > where can I go from here?
>
>  The simple 'fix' is to disable bluetooth services. We have no proper
>  answer as yet for how Linux is supposed to take over and still
>  handle the HID devices. 
sounds good.  but how can I disable the bluetooth services?  is
there some parameter I can pass to the yaboot prompt?

>  If you play with it manually you should probably be
>  able to get it to work. 
can you elaborate on this?

Bordeaux fails install

[Pete Graner]

Erick Calder wrote:
>  David Woodhouse
> > On Sun, 2006-04-30 at 22:50 -0700, Erick Calder wrote:
> >> where can I go from here?
> > The simple 'fix' is to disable bluetooth services. We have no proper
> > answer as yet for how Linux is supposed to take over and still
> > handle the HID devices.
>  
>  sounds good.  but how can I disable the bluetooth services?  is
>  there some parameter I can pass to the yaboot prompt? 
chkconfig bluetooth off

If you do that then the step below won't work...

>  
> > If you play with it manually you should probably be
> > able to get it to work.
>  
>  can you elaborate on this? 
/usr/bin/hidd --connect <mac addr of you bt device>

YYMV, I don't have a keyboard just a bt-mouse

Pete
>  
>  _______________________________________________
>  Fedora-ppc mailing list
>  Fedora-ppc(a)lists.infradead.org
>  http://lists.infradead.org/mailman/listinfo/fedora-ppc 

-- 
Pete Graner                                email: <pgraner(a)redhat.com&gt;

Bordeaux fails install

[Luciano Miguel Ferreira Rocha]

On Mon, May 01, 2006 at 02:55:49PM -0400, Pete Graner wrote:
>  Erick Calder wrote:
>  >David Woodhouse
>  >>On Sun, 2006-04-30 at 22:50 -0700, Erick Calder wrote:
>  >>>where can I go from here?
>  >>The simple 'fix' is to disable bluetooth services. We have no proper
>  >>answer as yet for how Linux is supposed to take over and still
>  >>handle the HID devices.
>  >
>  >sounds good.  but how can I disable the bluetooth services?  is
>  >there some parameter I can pass to the yaboot prompt?
>  
>  chkconfig bluetooth off 
Of course, he needs keyboard support for that, so he should boot in
single user mode (parameter 1 or s to yaboot)

-- 
lfr
0/0