I have a greying homebrew PC, Athlon 1200Mz chip, 30 Gb + 120 Gb HD's, some more-or-less
generic network card, and a Microtek 710S monitor and a DVD drive. I have 256Mb RAM, and the
installer insists on setting up a swap file right away. When I go to install Fedora
off the DVD everything is fine, the graphics look great (the screen resolution appears to be 1024x768),
the packages apparently install OK, everything is fine until I click the Reboot button.
The machine then reboots, loads Fedora and gets to a screen that has some extremely low resolution,
and what appears to be the following list of setup tasks:
Date and Time
The font is immense -- most of the items go off the right hand side of the screen.
There's a caret to the left, and hitting Enter moves it from one line to the next -- until it gets to Hardware
Profile. At that point it hangs. Hitting the reset button just repeats the process. It appears that it's
not recognizing the monitor although as I mentioned, the installer had no problem with it at all. I'm going
to give it one more go this evening, hooking the monitor in directly rather than thru the KVM switch.
Anybody have any ideas? Possible hardware compatibility issues? I've asked around locally but nobody
seems to have any solutions.
Thanks very much,
> -----Messaggio originale-----
> Date: Sat, 29 Mar 2008 22:51:55 -0400
> From: sean darcy <seandarcy2(a)gmail.com>
> Subject: Re: Firewire Stack in F8 Howto Wanted
> To: fedora-list(a)redhat.com
> Message-ID: <fsmv8b$dhi$1(a)ger.gmane.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Albert Graham wrote:
> > Hi,
> > Can any one, point me to a Howto that explains how to use the new
> > Firewire stack in F7/8,
> > I'm trying to get my Mini DV camera to work with via
> Firewire, actually
> > was hoping to use the Camara with ZoneMinder.
> It probably doesn't work with your firewire chip. See
> You'll have to rebuild the kernel, and not use the
> experimental 1394 stack.
Actually, you don't need to rebuild the kernel: you can build only the
and blacklist the new stack.
Take a look in the kwizart and in the ATRPMS repos: if you can't find a
version matching your
kernel, you can always use a srpm and rebuild it with a little editing to
the spec file and the right sources.
I did it for my external FW drives and it works.
Il messaggio e' stato analizzato alla ricerca di virus o
contenuti pericolosi da MailScanner, ed e'
risultato non infetto.
Can anyone give me leads on internet meeting software?
I'm looking for open-source alternatives to our Windows
Linktivity software --
multi-point desktop sharing - we currently can do meetings of up
to 15 participants with one host sharing his desktop to all
control transfer - the host should be able to hand over control
of the meeting to another participant - he should be able to
manipulate the original host's desktop, or, share his
audio and live video sharing for teleconferencing would be a
major plus - our current software is supposed to be able to do
that, but it's so ineffective that we just forget about live
video most of the time, and use telephone conference calls for
the audio portion
any reports on real world use would be greatly appreciated -
packages that work on Redhat derived products, whether CENTOS or
Fedora obviously are my biggest interest
Brunswick, MD, USA
When I first set up Fedora 8, I had some problems getting wlan0 (via
ndiswrapper) working. Now I can prevent wlan0 from being activated, even
when I'm using a wired connection via eth0.
I connect wirelessly at home and wired at the office. When I'm in the
office, I have to turn off NetworkManager (using services), kill
wpa_supplicant and nm-applet, and change config-services-network for
wlan0 so it's not being controlled by NetworkManager. This lets me
activate and use eth0. This works fine for about 30-60 minutes and then
wlan0 gets activated and screws up accessing the network. Then I have to
deactivate wlan0 and eth0, and re-activate eth0 so I can use the network
again. I have to do this over and over.
I have no clue as to why wlan0 is being activated with eth0 already
being activated and I don't know what program is causing this to happen.
I suspect it's something to do with NetworkManager because I never had
this problem before using NM. But I don't know for sure.
How can I prevent wlan0 from being activated???
I tried to install Centos 5.1 on a hard drive, and ran into errors
formatting it. I downloaded and ran the dos version of the Seagate
tools against the disk, which found all sorts of errors, and claimed
that it was running at 253 degrees. This drive has been sitting idle,
but powered on and mounted in a system running FC6 on a different drive.
Looking at /var/log/messages, I see no smart warnings until after I
rebooted into FC6. Prior to the failure I see messages indicating that
the drive is in the smartd database, and that it has been added to the
Shouldn't there have been some indication of problems prior to the
Perhaps you guys might be able to fix something that HP can't...
I have a reasonable laptop with 2Gb RAM (Presario V4004AP) which I had
to install F8 using the text installer last time- graphical stalled.
After the install (which was after I had received the machine back from
a warranty repair for overheating and part failure due to the
overheating issues) the machine lasted a week, then failed post tests.
During the period it was working I had some USB issues, and Gnome made
one complaint of keyboard layout.
I got it back after a mainboard replacement (again), and it lasted
another week (worked like a charm this time) and failed post again.
Couldn't get it to boot at all.
Sent it away again, and this time the tech sent it back NFF- maybe it
wanted a holiday? But when I got it back it did the same thing. I gave
it another kick in the guts, and after 10 secs it did finally pass post
and the bios screen showed up. So I loaded another distro for test
purposes seeing as I had backed up my data before sending it in for
After my testing I put F8 back on but the installer stalled completely
at /sbin/loader- a point that it would pause at for around 3-5mins when
I first started loading fedora on the is laptop. I tried both graphical
and text installers but nogo.
So in my resourcefulness I decided to use the live disk. It booted fine,
and I clicked on the installer- installed ok. Reboot, and the system
seems ok, but some things start to bother me- pirut doesn't work and
won't install, no office packages, etc... Pirut's complaint was it
couldn't create a directory for pixmaps: io error.
Hmmm. So I'm now stuck either trying fix the botched install by the live
disk, or getting the installer to work. What concerns me is if this post
test failure problem is at the root of this, and how do I fix that or
diag it? MB's been replaced twice, post takes 10 secs+ to pass, and odd
fixes come about by pressure on certain parts of the laptop. Kind of
After each repair the tech has thoroughly tested the hardware, and has
run the laptop ragged testing. I pulled the laptop apart before the last
repair to try and find the problem myself, but found nothing- no loose
connections, whatever. Hdd passes every test, during post the hdd light
stays on for some time though.
This is all the info I have now. Any ideas guys? Anymore tests I can put
this thing through?
I was just about to send in a message with pretty much
this title, so I thought I might as well jump in here.
I just finished installing fc8 from the livecd. I was
using fc7, which I "yum upgraded" from fc4 to fc5 to
fc6 to fc7 with minimal problems. I have been using
Linux since slackware .8 (I believe. It came on 25 or
so floppies that I downloaded over a 1200 baud modem)
and I don't ever remember being so frustrated.
I have NetworkManager running at start-up and
NetworkManager-Dispatcher also. Why? I don't know. I
am connected through a DSL modem and eth0, and dhcp
which I previously managed with "system config
network" for a couple of years without problems. I
have no wireless.
My initial problem was that eth0 was not activated on
start-up, NetworkManager was starting eth0 and then
taking it down, according to /var/log/messages.
According to what I read about NetworkManager, it's
first task is to keep wired connections up. I tried I
tried to RTFM and found no useful information, I tried
google, and found no useful information I tried the FC
wiki, and found no useful information.
I tried to see the NetworkManager-info that the docs
mentioned and found out I don't have that. Finally, by
doing a "rpm -ql NetworkManager I found some "nm"
scripts to get it configured. I still had problems so
I tried to "yum remove NetworkManager and dispatcher"
and it, for dependency, removed pidgin, which I want
to message with my daughter. I used pidgin in fc7
without NetworkManager very easily. So I tried "yum
install pidgin. Lo and behold it also installed
Now I have NetworkManager installed and running.
As a paranoid procedure, I usually disable eth0 when
I am not using the computer for a while and then turn
it on when I come back. Now, when I turn it on I get a
segfault in system-config-network
"Determining IP information for eth0 ..
/network-functions line 313 segnentation fault iplink
set dev $/up> dev/null 2&1"
Sorry if I shouldn't have used this title. I just
needed to vent a little (a lot?) I am not quite sure
what to do next, remove NetworkManager (Gosh, I get
tired of typing that) somehow without removing pidgin,
get a new IM program? ( I hate to do that because
configuring pidgin was problematic for me.) Set
Network Manager to not run as a service, turn off the
modem when I leave?
I am probably doing something dumb, it tends to come
with age, but I would appreciate any suggestions.
Having attacked NM (NetworkManager) unmercifully in the past,
I now find myself completely at his (her?) mercy,
as he/she is the only way of connecting one of my current laptop
(with WiFi) to the real world.
For some reason, system-config-network has been getting steadily worse
over the last few months, and now does not work at all.
(At its best it worked about 65% of the time.)
Is anyone successfully using the network service + system-config-network
with Fedora-8 (updated)?
To be more precise, has anyone found themselves NOT connected with WiFi,
and found the problem solved by running system-config-network?
Sorry, John Linville.
Mea maxima culpa.
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
Hi all. I took advantage of the purchase of a new machine to try out
F9 beta. I know this isn't the right list for F9 questions, but this
is mostly about fast user switching, which I think has been around
I am the main user of this computer and am logged in all the time.
Occasionally, someone else will use it, so when I'm not sitting at the
computer, I like it to show gdm/kdm (doesn't matter which really,
currently gdm). In the past, I've changed to an unused VT, logged in,
and started X on :1. Then when I step away from the computer, I run a
script I wrote (tied to a convenient desktop button and xautolock in
case I forget) that changes to the gdm display. Here it is:
# Fire up the screensaver before switching. Using "save" instead of
"lock" gives us a grace period to kill the screensaver without a
password, as defined in the control center.
(sleep 5; dcop kdesktop KScreensaverIface save)&
if [ `fgconsole` -ne 7 ]; then
sudo sh -c ' sudo chvt 7; sleep 30; sudo xset +dpms; sudo xset dpms
force off; sleep 30; sudo xset dpms force off'
It's not perfect in that it assumes gdm is running on vt 7, and this
approach doesn't do anything with device permissions and such. But it
mostly worked well. Note also that my script would turn on my
screensaver and turn off the monitor in short order, which I like.
I'm now trying to accomplish the same thing using the "proper" method,
fast user switching. I'm now using gnome instead of KDE (a story in
itself in F9...), so I do have the user switching applet on my
desktop. What I'm wondering is:
1. Is there some way I can call fast user switching through a script,
like above? I'd like to also turn on the screensaver, etc. Mainly,
I'd like to be able to accomplish the user switch to "Other..." on the
command line using xautolock.
2. This may be more of a test-list question, but when I change to
gdm's vt, DPMS never kicks in. I added these lines to
xset dpms 15 30 45
xset q > /tmp/xsetq.out
As you can see, I sent the output of "xset q" to a file, and DPMS is
DPMS (Energy Star):
Standby: 15 Suspend: 30 Off: 45
DPMS is Enabled
Monitor is On
But it never turns the monitor off. Does anyone know why this is happening?
Sorry for the long post, and thanks for any insights/suggestions/comments!