Problems with serial ata
by Pedro Fernandes Macedo
As I just bought my first serial ata disk , I'm having lockup problems
on my two fedora installations (FC2t1 and FC1).
The hardware I'm using is a Asus A7N8X-Deluxe motherboard (Silicon sata
chip) , using a seagate disk (not configured as raid). The OS is
installed on a parallel ata disk and has worked for a long time without
problems. The problem happens when I remove "hde=noprobe" from the boot
line to detect the serial ata disk (it is being recognized as hde).
The system locks and no messages appear on /var/log/messages . On the
other O$, it works perfectly...
This locks happen on FC2t1 and on FC1 (both fully updated). The problem
happens with full system load or even if the system is sitting idle...
Any ideas? I'm gonna make more tests , this time with smartd disabled
and see if I can pinpoint the cause of the problems...
--
Pedro Macedo
20 years, 2 months
GPG Keys
by William Sullivan
Where can I find a collection of gpg keys for FC2 T1, I am using apt
with Indiana and California mirrors. I remember running accrossed a
site with a lot of GPG keys a week or so ago but I don't remember how I
found it or what site it was. Thanks
20 years, 2 months
Re: HP zv5000z AMD64 Development Install fails
by Brian Stretch
-----Original Message-----
From: "Lewt @ Linux Warcry" <lewt(a)warcry.com>
Brian Stretch wrote:
>> I was able to get FC1 AMD64 to install on this HP zv5000z Athlon 64
>> nForce3 chipset notebook, but it locked up on reboot with the capslock
>> light blinking, possibly didn't read the GeForce 440 Go vidcard right?
>> The lockup was right about the time it ought to switch to X. I did a
>> graphical install, no need for textmode, though the screen did go
>> out-of-sync for a few seconds at the tail end of the shutdown-to-reboot.
>>
>> The AMD64 devel tree from today and yesterday didn't get very
>> far. I tried a NFS install from a local mirror of the duke mirror. Fedora
>> says "no valid devices were found on which to create new file systems"
>> after I select manual partitioning with Disk Druid. Then it reboots.
>> I tried acpi=off selinux=0 just for laughs, no diff. Anyone have any
>> ideas before I bugzilla this?
>>
>> It can't detect the "mouse" either, which is an ALPS keypad, and I
>> didn't see an option to manually select it like I could with FC1.
>
> try running acpi=off in your grub..
Found it! HP hasn't patched K8 Errata #93 in their BIOS yet.
Adding idle=poll is the workaround.
http://lists.suse.com/archive/suse-amd64/2003-Dec/0031.html
Also, video goes out of sync after X shuts down and FC1 drops to text
mode for the remainder of the shutdown sequence. It's back in sync
when the machine boots again.
That gets FC1 up and running, but the development tree is still no-go.
Anyone?
20 years, 2 months
X Windows appears to lock up
by Thomas Molina
I've got this problem where the X Windows system appears to malfunction
after some indeterminite time under Fedora Core 2 test 1. Unless I am
doing something wrong it probably needs putting in bugzilla, but my
observations to this point are rather amorphous so I will describe it and
solicit suggestions on how to proceed for further data gathering I can put
into bugzilla.
I have the screensaver set to blank after five minutes, cycle after five
minutes, and lock the screen after zero minutes. This gives me a random
screensaver which cycles between random patterns every five minutes and
locks the screen as soon as it kicks in, which is excatly what I want. If
I watch, it cycles, blanks, and locks as expected. However, after some
indeterminite time greater than one hour and less than six hours X goes
away and refuses to come back. I say greater than one hour and less than
six hours because I have watched it for an hour at a time and saw it act
normally, but if I leave it operating overnight X is locked up when I get
up in the morning.
When I say locked up I mean I see a blank screen with no graphics, no
mouse cursor, and no ability to kill X from that screen. Ctrl+Alt+Bkspc
does not kill the X Server, and Ctrl+Alt+Fx doesn't switch to other
virtual consoles. However, everything else is unaffected. The mailserver
is functioning normally, nfs shares are served out, and I can telnet in
with no problem. I just can't kill X, nor switch to another console to
kill it. I can telnet in and kill -9 it or, if I have previously switched
to another console, I can kill -9 it there.
There does not appear to be anything relevant in /var/log/messages, nor in
XFree86.0.log. It has happened with all the Fedora Core 2 test kernels,
as well as with the stock Linus 2.6 kernels. It does not happen with
Fedora Core 1 under any conditions.
So there you have it. I have a description of a problem, but not a lot of
hard data or debugging material. It seems I may have missed something,
but I am not sure what. It also seems to be an X problem, but that is not
conclusive. Otherwise it wouold have happened in Core 1 or behaviour
would have changed with the switch to x11-org.
Can someone suggest something I have missed or some way to gather more
data for bugzilla?
20 years, 2 months
Unable to align partition
by gplou@centrenad.com
When installing core 2 test 1 the installer tell me about a problem with
my partion "Unable to align..." If I ignore it, disk druid show my windows
xp disk with some weird cylinder number and partition. Thats fine with me
because I want to install to an other disk anyway. When I do that Fedora
installation go fine but the installer write that broken partition over
the old working one and I endup with my system not booting anymore. I
think the installer shouldnt rewrite partition if you are not modifing
them.
I tought the problem was due to the partition I made from windows XP or
something but every other distro I try install fine with no such problem.
I got 2 computer with basicly the same setup and both get the error with
fedora. Last nigh I gave an other try to it with the development boot.iso
and a ftp install to the development tree and the same problem occur
again.
I did some googleing and search on the list but I couldnt find anyone else
with the same problem and playing with my bios setting didnt help. Any
idea? thx.
--
Guillaume
20 years, 2 months
Invisible fonts under GTK apps.
by Kevin Sullivan
I am currently running yarrow (2.4.22-1.2115.nptl) on a fresh
installation. I did not do an upgrade. I have been using apt and
freshrpms but I don't think that has anything to do with my
problem. It would seem that all of the dialog boxes in GTK
applications have invisible fonts(ripperX, audacity). If I highlight
the text I can read it but it is not visible otherwise. All other apps
seem to work just fine. I am using kde but I also have the problem
with gnome. I have played with xfontsel, xset and font handling in kde
but no help.
Any ideas?
Thanks,
Kevin Sullivan
20 years, 2 months
2.6 kernel 2.6.4-1.290 reboots on unsuspend
by Camilo Mesias
Hi,
I'm seeing problems with the new kernel 2.6.4-1.290.
My machine has issues with ACPI so I am using APM for now. I can get a
reasonably working system with APM, but ACPI doesn't report battery
levels at all.
The real problem is that the machine reboots when it comes out of being
suspended. I wondered if anything had changed in the kernels recently
causing this behaviour? I think the original 2.6 kernel from the FC2
test 1 isos worked normally.
If it is the kernel kapmd, is there some way to disable or tune it's
behaviour? I am running the user space apmd (apmd-3.0.2-20) but if I
kill that before suspending, it doesn't help.
Any ideas?
-Cam
20 years, 2 months