linuxStudent11

[Log in to get rid of this advertisement]

This situation is looking hopeless.

As I expected, my bios cannot find the dvd out on the USB. And I have no DVD directly internal. The Fedora installation manual refers ambiguously (and tantalizingly) to booting from a harddrive (what I WANT to do) but nowhere does it tell me what the first step is. Do I need to to set the MBR for that partition to the ISO? I was told the iso is not an executable. It says I must enter the full pathname of the ISO. See http://docs.fedoraproject.org/instal...harddrive.html
Enter into WHAT??? Why can't I just be told what I want to know?

I don't want to boot off of my USB since I must load several new tools, make room, etc. And I think my old bios is dumb about USB at startup.

I could try a network load. But this seems like overkill. What is so bloody esoteric about just loading from a file?

billymayday

Are you able to boot anything from USB? The issue is that, as I unserstand things, you need to be able to boot up the Fedora installer before you can use these options. One option would be to boot from a USB key, but I don't think a floppy will work (I'll have a look on the net).

How did you get Fedora 8 installed?

Dumb question - will a USB CD boot (It can't hurt to ask)?

billymayday

THis is a bit old, but it may work. Mote that you are going to have to get yourself some non-LVM space

http://www.cs.cmu.edu/~colohan/docs/fedora_upgrade.html

linuxStudent11

Thanks for trying so hard...

I finally bit the bullet and spent my bucks (I have very few these daze) on a clearance sale old internal ATAPI-IDE DVD reader...didn't know such things were sold...for only $20 USD.
(sheesh, times are tough. You'd think an MS in AI w/thesis would be employable.)

I'm GUESSING this will solve my problem...the hw problem I mean.

FC8 went in with an equally old CD reader ... now disconnected and gone.
Now if FC5 has drivers for this thing...brand name "LiteOn"(?)...sez Microsoft Windows required...and if anyone believes that I've got some beach-front property on Mars I need to sell.

linuxStudent11

Thanks to BillyMayday and CRC123 I'm now

FEDORA CORE 9!!! ON THE AIR!!!

I guess there's just no easy way around (easier than) loading from DVD/CD.

BTW: Seems to be plenty of glitches during load and post-installation fixing.

I ran across this at the end of yum update:
ERROR:dbus.connection:Unable to set arguments () according to signature u's': <type 'exceptions.TypeError'>: More items found in D-Bus signature than in Python arguments
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in <module>
yummain.user_main(sys.argv[1:], exit_code=True)
File "/usr/share/yum-cli/yummain.py", line 241, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 193, in main
base.doTransaction()
File "/usr/share/yum-cli/cli.py", line 432, in doTransaction
self.runTransaction(cb=cb)
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 790, in runTransaction
self.plugins.run('posttrans')
File "/usr/lib/python2.5/site-packages/yum/plugins.py", line 175, in run
func(conduitcls(self, self.base, conf, **kwargs))
File "/usr/lib/yum-plugins/refresh-packagekit.py", line 37, in posttrans_hook
packagekit_iface.StateHasChanged('posttrans')
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 597, in call_blocking
message.append(signature=signature, *args)
TypeError: More items found in D-Bus signature than in Python arguments

Also, my xemacs seems to know nothing about dired. When I click the dired button, it says that symbol is void.

When I first came up, fonts were seriously aliased into jaggies on the menus. But the second login, everything got magically fixed.

Also, my NIC card started out deactivated with a strange DHCP bug failure report. So I clicked deactivate. Then I clicked activate. Then it reported failure again. But then it magically connected to our local switch. Everything's been fine since.

Also, the media check screen during installation was flakey. When it finished the check, I clicked "continue" (or was it "skip") to return to the install path. It gave me a modal error dialog that said "OK" in text in the upper left with a single OK button as my only possible response...no other comments. So I clicked "OK" and it returned me to the screen to "Test" or "Skip". When I clicked "Skip" I got the same modal box again...ad infinitum. No biggie, I'd just begun the install, so I restarted.

I hope these bug reports are useful. I haven't got bugzilla going yet.

billymayday

Glad you're up and running!