Re: [OT] Cannot save BIOS settings
by Tod Merley
> Date: Thu, 23 Feb 2006 16:51:28 -0500
> From: "James He" <icrazy(a)gmail.com>
> Subject: [OT] Cannot save BIOS settings
> To: fedora-list(a)redhat.com
> Message-ID:
> <fd0f51b90602231351h361b635cx4da7fce0941a8534(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi, all!
>
> This might be off-topic, but since we are running FC on this machine,
> so maybe you can help.
>
> I replaced a bad motherboard with a new one for one computer and the
> computer started to be working again. The only problem now is that I
> am not able to save the BIOS(Phoenix) setting on that computer, that
> is to say, the default setting will always come back automatically.
> This is not acceptable, for we need to boot the computer from network,
> but the default booting sequence prefers to boot from hard disk, on
> which we do have a bootable operating system.
>
> The BIOS reset jumper is in its normal place, and I even changed the
> battery on the motherboard to see how it goes -- the problem remained.
>
> Thanks in advance!
>
> --
> Best regards,
>
> James He
Hi James!
I would be doing the following:
0. Making sure I am using the proper procedure to save the settings as I
leave the CMOS setup program. Some have the ability to exit without saving
permitting the use of the settings one time only. I would make sure that I
save and exit. I would also look at any CMOS security settings just in case.
1. Reading the MB manual with specific attention concerning how the CMOS is
powered and controlled. I often find these PDF on the web if they are not
in hand.
2. Measuring the actual CMOS battery voltages - with a volt meter out of
box and with a simulated load if I could figure out with that was (if it
holds with a 1K resistor my guess is that it is fine). I would also look
into measuring it as it feeds the CMOS on the MB (very carefully of
course!!).
3. Taking some time to clean and look at very closely the battery holder and
associated parts.
4. I would try removing or changing the CMOS jumper you mention and also
take a good look it it's integrity and clean the posts as well and try
another jumper.
5. If all this did not clear the problem, considering another MB.
Good Hunting!
Tod
18 years, 4 months
Upgrading from FC5T3 to FC5 final
by Bill Dealey
If I install FC5T3 on my machine now, will I have do a reinstall/upgrade
when the final release of FC5 is available or will I be able to upgrade
to the full FC5 via yum updates?
18 years, 4 months
Hard drive cable question -
by bobgoodwin
Does it matter which forty pin connector plugs into the master and slave
drives?
I have come to the realization after struggling with some problems that
there are a lot more wires in the ribbon cable than there are connector
pins.
I now see that Maxtor designates the connector at the end of the cable
as the "master" and the one just below it as the "slave." I presently
have only one drive jumpered as master with FC4 running on it and it
;doesn't seem to care which data cable connector is attached to it, but
when I put in the second drive, jumpered as "slave" the computer won't
boot. I decided the drive was bad but now I'm wondering? It may be the
wrong connectors plugged into the drives.
I thought "cable select" cables had wires obviously crossed in the
ribbon cable but that may not be true with this 80 wire ribbon?
Can someone clear this up for me.
Thanks.
Bob Goodwin Zuni, Virginia
18 years, 4 months
[OT] Cannot save BIOS settings
by James He
Hi, all!
This might be off-topic, but since we are running FC on this machine,
so maybe you can help.
I replaced a bad motherboard with a new one for one computer and the
computer started to be working again. The only problem now is that I
am not able to save the BIOS(Phoenix) setting on that computer, that
is to say, the default setting will always come back automatically.
This is not acceptable, for we need to boot the computer from network,
but the default booting sequence prefers to boot from hard disk, on
which we do have a bootable operating system.
The BIOS reset jumper is in its normal place, and I even changed the
battery on the motherboard to see how it goes -- the problem remained.
Thanks in advance!
--
Best regards,
James He
18 years, 4 months
FC5 Release?
by Ali Helmy
Hey mates,
Can anyone give me a good close estimate as to when FC5 is going to
released? As a final release, not a test one
Thank You
--
A. Helmy
18 years, 4 months
desktop problem
by Rick Lim
Hi there,
I have done something to my desktop that I don't know how to fix,
when I minimise an application it does not show up on the task bar, does anyone
know how to fix this???
TIA
18 years, 4 months
FC4, ssh, kerberos 5 and TGT passing
by Tony Heaton
Hello,
I searched the archives, and didn't find anything on this. I have
installed FC4, ssh-1.99-OpenSSH_4.2 and krb 1.4.1-5. The only thing
that is not working is tgt passing. I kinit on box A then ssh to box B.
When I do a klist on box B, there is no ticket. Any help would be
appreciated.
Thanks
--
Tony Heaton
theaton(a)lanl.gov
- "If you do nothing, they'll win"
18 years, 4 months
crond question
by Luc MAIGNAN
Hi,
to prevent crond to stop (this has arrived !!!), I wanted to launch it
via inittab and respawn option like this :
cron:2345:respawn:/usr/bin/crond
This doesn't work : I have errors in messages "crond is responding too
fast : disabled for 5 mn"
Is there any way to do this ?
Best regards
18 years, 4 months
Re: Modem ttyS14?
by ron
>> ron wrote:
>> hello,
>>
>>I s there some way to set the pci device to another setting other than
>> ttyS14? I am experimenting with some live cds and they do not include
>> ttyS14 in their modem setups.
>>
>> My fedora core dmesg says:
>>
>> ttyS14 at I/O 0xa000 (irq = 3) is a 16550
>>
>> usually adding a sym link modem in /dev with:
>>
>> ln -sf /dev/ttyS14 /dev/modem
>>
>> works.
>>
> Mikkel wrote:
> I think you are stuck making the symlink. The problem is that the
> driver for the PCI I/O card is setting the port to ttyS14, so it
> is the driver that would need to be changed. If you were not using
> live CDs, you could create a udev rule, but this is not really an
> option for live CDs. (You could also use setserial to change the
> device.)
Mikkel,
Thanks,
# setserial <space> /dev/ttyS4 <space> port <space> 0xa000 <space> irq
<space> 3 <space> uart <space> 16550A <space> spd_vhi
worked for me. Your correct the driver is setting the device.
Kernel 2.6.11-11_FC3AS/SMP
Model Marquis-1814T
I can recommend this company:
ASL Labs:
Marquis K814T
http://www.aslab.com/products/workstations/marquisk814_spec.html
http://www.aslab.com/products/workstations/marquisk814.html
jpeg
http://www.aslab.com/images/products/ATX_side_view.jpg
http://www.aslab.com/images/products/front_view_hotswap.jpg
http://www.aslab.com/images/products/side_view.jpg
Marquis K814T Specifications.
Motherboard:
ASUS A8N-E ATX motherboard
CPU:
AMD(r) Athlon(r) 64 or Athlon 64 FX processor, .13 or .09 micron, 512K
or 1M L2 cache, 800mhz or 1Ghz HyperTransport Link, Socket 939
64-bit integer registers, 128-bit SSE/SSE2 registeres
48-bit virtual addresses, 40-bit physical addresses
AMD 64-bit x86 instruction set extensions
Chipset:
Nvidia(r) nForce 4 Ultra
Memory Subsystem:
Four DIMM banks supporting up to 4GB1 PC-3200 ECC unbuffered SDRAM
memory, single or dual channel (128-bit) memory access
Note: 128-bit memory access requires even number of memory modules.
-ron-
18 years, 4 months
Removable media handling in KDE on FC4
by Jason L Tibbitts III
I'm looking at putting FC4 on selected desktops here and I'm
investigating how it handles USB sticks and the like. (Most of the
machines are running FC3 and everyone uses KDE.)
So I logged in as a test user and inserted a USB stick. I was pleased
to see the window appear asking what should be done with it. So I
opened it in a window, looked around and closed the window. Now what?
The device is mounted; unplugging it would be bad. There's no desktop
icon indicating that it's mounted (and none indicating an unmounted
device either). Yes, desktop behavior is set to display mounted and
unmounted removable media.
If you look in the file manager and click on the right combination of
tabs, the USB device shows up as a hard disk named sda1 and can be
unmounted from there. Unfortunately my users will never comprehend
that.
My guess is that this has something to do with the missing HAL support
in KDE. Is there any way to improve things? Should I look to
KDE-Redhat's packages?
- J<
18 years, 4 months
