Fedora Installation Options - Page 13

SamTzu · #**181** 30th July 2007, 11:21 AM

Its good that you bothered to send this info.
This is the only way the community can keep up-to-date on the constant bugs that plague us.
Unfortunately FC seems to be more prone to bugs that its rivals. I personally think upgrade cycle is too fast and beta testing is rushed.
I too am tired of finding bugs that keep returning again and again because of this.

SamTzu

PS. Did you try doing the "Check Disk" on FC7 DVD?
Please insert disk 2. LOL

earth · #**182** 30th July 2007, 04:24 PM

SamTzu, thanks for your post! Since I posted last week about the unsuccessful boot of live cd FC7 for my Dell Dimension 4600C, your post reminded me to try the FC7 live cd with another old system I'm running right now. FC7 live cd booted sucessfuly, and I'm posting here from the FC7 live cd. Here's some interesting technical information for you and the FC compilers: Upon boot I got this message:
"ACPI: BIOS age (1997) fails cutoff (1999) acpi=force is required to enable ACPI; Red Hat nash version 6.0.9 starting . . ." then this machine successfully booted from the fc7 live cd, and I'm going to try a harddisk install later on. FYI, here's the Detected Hardware information for this machine:

1. Hard Disk -- hda

Identification
Vendor: ‎Western Digital Corp.

Model: ‎WD205AA

Media class: ‎hd

Bus identification
Vendor ID: ‎0x0000

Device ID: ‎0x0000

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Connection
Bus: ‎ide

Channel: ‎primary

Device
Old device file: ‎/dev/hda

Partitions
Primary partitions: ‎2 (hda1, hda3)

Extended partitions: ‎3 (hda5, hda6, hda7)

Misc
Geometry: ‎2494/255/63 (CHS)

Disk controller: ‎0

2. CD burner -- hdc

Identification
Disk identifier: ‎TDK CDRW241040B

Media class: ‎cdrom

Bus identification
Vendor ID: ‎0x0000

Device ID: ‎0x0000

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Connection
Bus: ‎ide

Channel: ‎secondary

Device
Old device file: ‎/dev/hdc

Misc
Drive capacity: ‎burner

Disk controller: ‎0

3. AGP controllers

Identification
Vendor: ‎VIA Technologies Inc.

Description: ‎VT8371 [KX133]

Media class: ‎BRIDGE_HOST

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎0

PCI function #: ‎0

Vendor ID: ‎0x1106

Device ID: ‎0x0391

Sub vendor ID: ‎0xffff

Sub device ID: ‎0xffff

Misc
Module: ‎via-agp

4. Video Card

Identification
Vendor: ‎ATI Technologies Inc.

Description: ‎Rage 128 GL AGP 1x/2x

Media class: ‎DISPLAY_VGA

Connection
Bus: ‎PCI

Bus PCI #: ‎1

PCI device #: ‎0

PCI function #: ‎0

Vendor ID: ‎0x1002

Device ID: ‎0x5246

Sub vendor ID: ‎0x1002

Sub device ID: ‎0x0008

Misc
Module: ‎Card:ATI Rage 128 TVout

5. Soundcard

Identification
Vendor: ‎VIA Technologies Inc.

Description: ‎VT82C686 [Apollo Super AC97/Audio]

Media class: ‎MULTIMEDIA_AUDIO

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎7

PCI function #: ‎5

Vendor ID: ‎0x1106

Device ID: ‎0x3058

Sub vendor ID: ‎0x11d4

Sub device ID: ‎0x5348

Driver
Module: ‎snd-via82xx

Alternative drivers: ‎via82cxxx_audio

6. Processsors

Identification
Processor ID: ‎1

Vendor: ‎AuthenticAMD

Model name: ‎AMD Athlon(tm) Processor

Cpuid family: ‎6

Model: ‎2

Model stepping: ‎1

Connection
Vendor ID: ‎0x0000

Device ID: ‎0x0000

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Performances
Frequency (MHz): ‎601.395

Cache size: ‎512 KB

Bogomips: ‎1204.34

Bugs
Fdiv bug: ‎No

Coma bug: ‎No

F00f bug: ‎No

Halt bug: ‎No

FPU
Is FPU present: ‎Yes

Whether the FPU has an irq vector: ‎Yes

Misc
Cpuid level: ‎1

Flags: ‎fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow up

Write protection: ‎Yes

7. Ethernet card

Identification
Vendor: ‎Realtek Semiconductor

Description: ‎RTL-8139

Media class: ‎NETWORK_ETHERNET

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎15

PCI function #: ‎0

Vendor ID: ‎0x10ec

Device ID: ‎0x8139

Sub vendor ID: ‎0xffff

Sub device ID: ‎0xffff

Misc
Module: ‎8139too

8. Memory

L1 Cache

Connection
Vendor ID: ‎0x0000

Device ID: ‎0x0000

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Misc
Name: ‎L1 Cache

Installed size: ‎128 KB

Type: ‎Cache

L2 Cache

Connection
Vendor ID: ‎0x0000

Device ID: ‎0x0000

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Misc
Name: ‎L2 Cache

Installed size: ‎512 KB

Type: ‎Cache

Memory Module Dimm 1

Connection
Vendor ID: ‎0x0000

Device ID: ‎0x0000

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Misc
Name: ‎DIMM1

Speed: ‎Unknown

Installed size: ‎128 MB (Single-bank Connection)

Enabled Size: ‎128 MB (Single-bank Connection)

Type: ‎Memory Module

Bank connections: ‎0 1

Dimm 2

Connection
Vendor ID: ‎0x0000

Device ID: ‎0x0000

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Misc
Name: ‎DIMM2

Speed: ‎Unknown

Installed size: ‎128 MB (Single-bank Connection)

Enabled Size: ‎128 MB (Single-bank Connection)

Type: ‎Memory Module

Bank connections: ‎2 3

9. IDE/ATA controllers

Identification
Vendor: ‎VIA Technologies Inc.

Description: ‎VT82C586 IDE [Apollo]

Media class: ‎STORAGE_IDE

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎7

PCI function #: ‎1

Vendor ID: ‎0x1106

Device ID: ‎0x0571

Sub vendor ID: ‎0xffff

Sub device ID: ‎0xffff

Misc
Module: ‎via82cxxx

10. USB controllers (2)

Identification
Vendor: ‎VIA Technologies Inc.

Description: ‎VT82C586B USB

Media class: ‎SERIAL_USB

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎7

PCI function #: ‎3

Vendor ID: ‎0x1106

Device ID: ‎0x3038

Sub vendor ID: ‎0x0925

Sub device ID: ‎0x1234

Misc
Module: ‎uhci-hcd

11. SMBus controllers

Identification
Vendor: ‎VIA Technologies Inc.

Description: ‎VT82C686 [Apollo Super ACPI]

Media class: ‎SERIAL_SMBUS

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎7

PCI function #: ‎4

Vendor ID: ‎0x1106

Device ID: ‎0x3057

Sub vendor ID: ‎0xffff

Sub device ID: ‎0xffff

Misc
Module: ‎i2c-viapro

12. Bridges and system controllers

Identification
Vendor: ‎VIA Technologies Inc.

Description: ‎VT8371 [PCI-PCI Bridge]

Media class: ‎BRIDGE_PCI

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎1

PCI function #: ‎0

Vendor ID: ‎0x1106

Device ID: ‎0x8391

Sub vendor ID: ‎0xffff

Sub device ID: ‎0xffff

Identification
Vendor: ‎VIA Technologies Inc.

Description: ‎VT82C686 [Apollo Super]

Media class: ‎BRIDGE_ISA

Connection
Bus: ‎PCI

Bus PCI #: ‎0

PCI device #: ‎7

PCI function #: ‎0

Vendor ID: ‎0x1106

Device ID: ‎0x0686

Sub vendor ID: ‎0xffff

Sub device ID: ‎0xffff

13. Keyboard

Identification
Vendor: ‎

Description: ‎AT Translated Set 2 keyboard

Connection
Bus: ‎isa

Vendor ID: ‎0x0001

Device ID: ‎0x0001

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Misc
Module: ‎kbd

14. Mouse

Connection
Bus: ‎isa

Vendor ID: ‎0x0002

Device ID: ‎0x0006

Sub vendor ID: ‎0x0000

Sub device ID: ‎0x0000

Features
Emulated wheel: ‎No

Misc
Vendor: ‎

Description: ‎ImExPS/2 Logitech Explorer Mouse

Module: ‎mouse0

I'm very pleased that this old system booted up the FC7, which makes me think that Dell computers may have other issues booting from live cd's, not necessarily a bug in the FC7 distro itself, (although it's true that PCLOS live cd did boot from the Dimension 4600c, indicating that's it is possible). Thanks again, SamTzu!

earth · #**183** 30th July 2007, 04:31 PM

Another point of interest -- none of the live cd's would boot from this machine until I added another 128mb memory module. I did install SUSE on the machine with only the original 128mb memory, because SUSE used a hda swap partition to make the installation but otherwise would not have installed. The extra 128 mb memory made this machine into a viable live cd & install machine! It makes me wonder if my Dell Dimension 4600C would run more live distros if it had more memory than its original 256. I'm not going to upgrade it though because another family member took it over with windows xp running very well on 256mb's.

lsatenstein · #**184** 30th July 2007, 06:35 PM

The problem with all linux distributions is that the technology changes are driving the linux changes. And since new technologies come out almost weekly, linux distributions have to do likewise.

Sometimes, it is the bios on the mother board that is out of date. For example when a dvd cannot be read at boot time, it could be that the problem is with dma or some bios parameter. Boot with the nodma option and things could work out.

I too wish that there was more testing between releases. One day flash works, and the next, it is broken. However I was able to repair my problem, and I hope that this board can help you get your fc7 system installed.

Fc7, once installed, is the most stable of the Fedora installations to date. I have not had any requirement to do a reinstall.

earth · #**185** 31st July 2007, 12:49 AM

Quote:

Originally Posted by lsatenstein

The problem with all linux distributions is that the technology changes are driving the linux changes. And since new technologies come out almost weekly, linux distributions have to do likewise.

Sometimes, it is the bios on the mother board that is out of date. For example when a dvd cannot be read at boot time, it could be that the problem is with dma or some bios parameter. Boot with the nodma option and things could work out.

I too wish that there was more testing between releases. One day flash works, and the next, it is broken. However I was able to repair my problem, and I hope that this board can help you get your fc7 system installed.

Fc7, once installed, is the most stable of the Fedora installations to date. I have not had any requirement to do a reinstall.

I successfully installed FC7 this afternoon, and updated it from the database. I also ordered a 256mb module from Crucial Technology ($33.00) for this old computer, a GA-7VM model that I picked up for $40 last week, but with only 128mb dram. I understand the problem of new technologies, but the challenge (for me) is to use Linux with older machines. I thought the FC7 install was well designed and very intuitive in its partitioning of my hd.

Peter_APIIT · #**186** 31st July 2007, 04:28 AM

Why don't try to install Livecd. This is much easier to do so.

I hope this help.

SamTzu · #**187** 31st July 2007, 05:23 PM

Thats not the point.

The point is that if the BASIC options in the DVD release do not work and force you to reboot your machine because the media test goes in to a perpetual loop then I got to ask - why bother making the DVD version?

Sam

samogite · #**188** 11th August 2007, 02:15 PM

Hi there

I'm newbie with some linux skills (used it couple years ago, have basic skills). Decided to switch to linux.

I'm looking for mentor to help me go through few problems I have.

First, I have one hard drive and Windows XP Pro on it. I need to have it on my PC.

Installed Fedora 7 on an unpartitioned part of hard drive. During installation I wasn't sure about changing anything in MBR so I didn't install GRUB at that stage. Of course, I cannot boot my Fedora. Tried installing GRUB useing Fedora installation DVD, but no luck. It says something about not being able to install something and restarts.

Is there anyone who could help me? Private messages are welcome. Links are welcome.

Let me know if there is anything I can give here more (information) before you can help me.

Thanks in advance.

SamTzu · #**189** 12th August 2007, 08:52 AM

Fedora might be too "Pro" OS for beginners. By far the easiest Linux at the moment is PCLinuxOS.
Everything in it just seems to work. Very simple.

Sam

PS. Remember KISS? "Keep It Simple Stupid."

brr872002 · #**190** 13th August 2007, 08:24 AM

Installed Fedora 7 two PCs in office one in home PC without burning the FC7_DVD.iso in to a DVD media one of the through local net work or from fat32 partition .
Simply open dvd.iso in window machine using WINRAR burn /images/ boot.iso in CD and boot give media option local Hard Drive/ IP add of local server PC 192.168.XXX.XXX
In case of vintage PCS always use kernel option ide=nodma

samogite · #**191** 17th August 2007, 12:03 PM

Quote:

Originally Posted by SamTzu

Fedora might be too "Pro" OS for beginners. By far the easiest Linux at the moment is PCLinuxOS.
Everything in it just seems to work. Very simple.

Sam

PS. Remember KISS? "Keep It Simple Stupid."

2 SamTzu:

thanks for response, but I have Fedora up and running and I'm really happy with it.

I had to reinstall Fedora and let it modify my MBR. It automaticly added my Windows XP OS on booting OS list - so that solved my problem.

isra_mv · #**192** 20th August 2007, 04:59 AM

hi. this is my first post in this community.
my problem: i downloaded the fedora 7 kde live-cd. my notebook has an ati x700. when the cd executes the x server, the screen turns black, and i can only use the text mode consoles. i've had always this problem with ati video cards, except with kubuntu 7.04, and the last time i installed fc6 in text mode and after the installation i fixed it, but now i don't know how to install fedora 7 from the live-cd. i ran the os in text console, login as root and tried typing:
# anaconda --text
but it says that i didn't specified the instalation mode

please, tell me how to use anaconda, or where should i execute it.

Brotherred · #**193** 22nd August 2007, 05:00 AM

I am wondering if this is the place to ask a question about upgrading the OS with out reinstalling. How do you do that? I heard that you use Anaconda but how is that done? I did not see that option in listed in the commands above.

isra_mv · #**194** 22nd August 2007, 07:24 PM

I found the answer.
Brotherred, I asked it here because the thread is about the options for installing Fedora with Anaconda, and that was what I needed. And actually, the option is in the list, but not as I needed with the live-cd
Once the OS starts, in a text console, type:
# anaconda --method=livecd:///dev/live-osimg --text
I didn't use "--text" because anaconda checks the graphic card and when finds a problem, automatically runs in text mode.

Staffy · #**195** 24th August 2007, 11:08 AM

Hi can any one give me some advise or send me to a link on the correct method to installing fedora7 as a duel boot option in conjunction to windows XP for dummies

I realy dont want to install the fedora7 blind folded
Thanks inadvance