Flickering screen with kernel 2.6.32
by Alberto Ferrante
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thanks for your reply Dale,
>> I run Fedora 12 on my IBM T60 laptop and with the last two kernel
>> releases (the two 2.6.32 ones) I have a strange problem. All is fine on
>> the laptop screen. Thought, when I connect the computer to the docking
>> station the images on the external screen are flickering. To be precise,
>> the image is stable in a small section located in the center of the
>> screen, but it is not in all the other parts. The T60 has an ATI graphic
>> card and I am using the radeon driver provided in the kernel. All works
>> fine with previous kernels (at the moment I am using the
>> 2.6.31.12-174.2.22.fc12.i686 release).
>>
>
> Have you tested with and without nomodeset?
> cat /proc/cmdline
Actually using nomodeset solves the problem, thanks for suggesting this!!
> What video card?
> lspci | grep -i video
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility
X1400
> What ati drivers?
The radeon drivers provided in the kernel (radeon kernel module, radeon
xorg driver).
Thanks again!
Best,
Alberto
- --
Alberto Ferrante, Ph.D.
Personal Home Page: http://www.alari.ch/people/alberto
Public key: http://www.alari.ch/people/alberto/key-alari-dti.txt
Advanced Learning and Research Institute [http://www.ALaRI.ch]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (GNU/Linux)
iQIcBAEBCAAGBQJLvZBdAAoJEGwAj6ArCn4k0BsP/i4EK2ic0CQb79Kb4j+Fb7tb
OY45U5uFsY447i821TcVqFFETkyTTRW8QkryWdcxPBrSZ/jp4QlhniIC4jYUvNGm
WdIeBi+F+wQSn+tGTdR7zYll/cTgfzpel8eVgFi+m73fx7tsRSg8OZCNqKoqf75L
3Hd1rPTKA3KnZRWSxAmKfioXcg806vTqzXiBodeDkg6s1mCvEyBW6s0ABdguUdqt
zaQC94XtYtvtqUNWcBwFAFp4nmAnEdhiO2FJ1ri8QmvN5/io7g5pFmLoAYnWXpvB
zrZ2bh9Py+Mk6M6Tl1gO+AO2xymC8rDnxBQdbtf1JUpoyDO0pfkQ3Mop/RTc5OAh
rVG0Y5aQ6Bcb6T+bYI9q4y+e0DPzM/+8ZN0oGsHU2hy7I7eIF4R4SUzA+C1Pvtgj
4Zvuv3A1h5qnFkY+aYTPgRvzAvKW2wHmMg5+zR6vWmwlNeGFuJxOxPR/LuJDs2d4
USvkZh7mRJ3J8lS445zFrkaxdkIPNmGo6koP4/HT5d0n7ay5z+I6/edl3C90t1KX
l0ArPmcjVPD5gbB449gqSR1izyu7LF2uMSO2HJzYBm+Hrv5rb8+g658F7D0TB4WJ
FdKgf6oFkq1dLj7B3bO/a6WKGpbiuqf6dDEBhxH1mrv9VteD0rY0V4ZYVwePoIUX
otu2gBPR6pSOV1zPnc26
=PeNi
-----END PGP SIGNATURE-----
14 years, 1 month
CD burning problems
by Alberto Ferrante
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thanks for your reply Fred,
>> with Fedra 12, since the advent of kernel 2.6.32 I have a strange
>> problem with both my CD burners (a Plextor and an Asus): I can burn CDs
>> (apparently) without any problem, but those CDs are unreadable.
>> I am currently using Brasero as K3B had the same problem even with
>> previous releases of the kernel!
> Thoughts, though:
> --try the burned media on other computers: are they readable there?
No in general, but one of them strangely appears to be readable on my
laptop that also runs Fedora 12.
> --will the system read media burned on other computers? using the
> same brand of media? using k3b on the other computers?
Definitely yes! And I can read them on the PC where I have problems. I
can even read CDs I previously burned on this PC.
> --try a different drive in the same computer
Both my CD burners (an Asus and a Plextor) have the same problem.
> --have you changed brands of media? Once upon a time I had a CDRW drive
> that only worked on some kinds/brands of media, and I had one batch
> of media it would burn fine but couldn't read after burning it while
> other drives could. (needless to say, that drive is long-since gone.)
I have been using exactly the same media (Verbatim) for a long time, and
I cannot see a reason why media coming from the same 50-CD package were
OK 2 months ago and they are not now. Furthermore, burning CD images
seems to work fine (but I haven't tried that in the last days).
As soon as I find some time, I'd like trying to burn a CD from the
command line.
Thanks again for your reply.
Best,
Alberto
- --
Home page: http://www.alari.ch/people/alberto/personal
Photo galleries : http://albertoferrante.name
Public key: http://www.alari.ch/people/alberto/pubkey.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (GNU/Linux)
iQIcBAEBCAAGBQJLvZIeAAoJEGwAj6ArCn4k6McP/3aXfb6WoWwJd4pq4lSgAw+y
tT2fZZr5SAEs4olNPLZMxxCn+qEwIHqWAwlHRYNMg+aj4/unReSfI93nXAAIk/yG
xjtMQoTZ6eKYnFr7BJY1AkwD2uDLJpTNO9TkdB3vjucO5bHOxGOb+4aCgB0cysLd
ruz8q1e3FDDRwoZiJKU1/3DqMCcYNVLFbRu8Z8d6VEnPrfz9m0mjsnp6gzUPxdaJ
Ot9KSWzQpvmy3tdnZcVj6T4FNQK7IYJcaM4HAxbPYS35JBiGsTCMdTPmpkryxHml
Q9dhYf8B7pXfHgyIaQVRsREFmt/XraYyLgnkV5ysu8mMUFIxilm7sBGUg92gApC4
Cd8i6T2eIa+JGN1teCXAAHcZknkKUeR6llVCEKOLSw8RACF/iN/5457M71rRh0qe
oebSqjclPACmUOZerm25XE1T/B/biBRyoqC7hrj40PPOVbJgZqMi4P8/Ovbo1Ap7
O79b2Fm0ugaWgCdh3zy78ug13Td763K6N0WAnYJdsMpuzmXPo0Q7S3f9kykdBaWW
ofD6CrOtlHbz4zygra17gJ+NzvMHrH7THnQAxv1tYZ1W5IK2Vc8a4n15GXjLv1ZM
O/TZ8mqfAuaV5fbo1As/wU/v5uiccyhIuYJtRsYdDMvIcHL5SR9yJudNEHvyfBa5
MLplkiP6dLHKrZFa9svE
=iuKi
-----END PGP SIGNATURE-----
14 years, 1 month
Kernel Oops right after boot
by Andrew Junev
Hello All,
While trying to fix cd-rom automount issue, I noticed my kernel makes
several Oops'es right after boot. I do not notice any strange behavior
whatsoever. It's just these lines in the /var/log/messages that make
me think something is wrong:
2010-04-06T23:33:59.461793+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:33:59.461891+04:00 frontend1 abrtd: Directory 'kerneloops-1270582439-1' creation detected
2010-04-06T23:34:05.996433+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:34:06.030973+04:00 frontend1 abrtd: Crash is in database already (dup of /var/cache/abrt/kerneloops-1270580900-1)
2010-04-06T23:34:06.031042+04:00 frontend1 abrtd: Deleting crash kerneloops-1270582439-1 (dup of kerneloops-1270580900-1), sending dbus signal
2010-04-06T23:35:59.112531+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:35:59.112582+04:00 frontend1 abrtd: Directory 'kerneloops-1270582559-1' creation detected
2010-04-06T23:35:59.206403+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:35:59.210845+04:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1270582559-1, processing
2010-04-06T23:35:59.503073+04:00 frontend1 abrtd: Registered Action plugin 'RunApp'
2010-04-06T23:35:59.503133+04:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1270582559-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
2010-04-06T23:36:18.187097+04:00 frontend1 ntpd[1165]: synchronized to 90.156.233.43, stratum 3
2010-04-06T23:36:18.187128+04:00 frontend1 ntpd[1165]: time reset +0.697205 s
2010-04-06T23:36:18.187142+04:00 frontend1 ntpd[1165]: kernel time sync status change 2001
2010-04-06T23:37:59.810046+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:37:59.810164+04:00 frontend1 abrtd: Directory 'kerneloops-1270582679-1' creation detected
2010-04-06T23:37:59.896992+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:37:59.901369+04:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1270582679-1, processing
2010-04-06T23:37:59.901413+04:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1270582679-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
2010-04-06T23:40:00.018233+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:40:00.018286+04:00 frontend1 abrtd: Directory 'kerneloops-1270582800-1' creation detected
2010-04-06T23:40:00.106862+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:40:00.385884+04:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1270582800-1, processing
2010-04-06T23:40:00.385984+04:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1270582800-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
2010-04-06T23:41:57.269786+04:00 frontend1 ntpd[1165]: synchronized to 212.192.253.168, stratum 2
2010-04-06T23:42:00.112898+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:42:00.112990+04:00 frontend1 abrtd: Directory 'kerneloops-1270582920-1' creation detected
2010-04-06T23:42:00.204395+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:42:00.208968+04:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1270582920-1, processing
2010-04-06T23:42:00.208986+04:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1270582920-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
I think it all started when I replaced the motherboard. I mentioned
some time ago in this mailing list that my new motherboard (MSI
P43T-C51) didn't work in Linux with my old video adapter (NVidia 8600GT).
As I couldn't find a solution, I just put an older 7600GS to be able
to use the machine. So I used the system in this configuration as a
MythTV frontend and had no troubles at all (except for the recently
disappeared automount, but I tend to think it's caused by a human
factor perhaps I changed something related to automount, just can't
figure out what it is).
Originally I was using proprietary NVidia driver. Today I switched
back to Nouveau, but Oopses are still there - no difference at all...
I kindly ask for your help in getting to know what actually
causes these oopses. I'd like to have that fixed, if that is at all
possible.
Dmesg output is attached (hope my message won't be too large).
--
Best regards,
Andrew
14 years, 1 month
RE: Looking for a monitor driver
by Leslie S Satenstein
Monday, April 5,
2010 8:10 AM
From:
"Tim"
<ignored_mailbox(a)yahoo.com.au>
To:
"Community support for Fedora users"
<users(a)lists.fedoraproject.org>
Dave Higton:
>
You're lucky with your CRTs. The ones I've seen that were a few
>
years old, had bad screen burn, plus a nasty colour cast as one
>
of the electron guns had lost emission. I was glad to have my
>
last CRT monitor replaced here (by an LCD) because it had bad
>
Moiré patterning, which could only be cure by defocussing it
>
badly.
>
> Having used CRTs and LCDs, I would never go back
to CRT without
> a fight. Fortunately LCDs are (a) so cheap (I
don't understand
> your comment about outrageously overpriced
LCDs), (b) the only
> type commonly available.
I've got CRT
monitors, here, of 1980s vintage, still with excellent
pictures. Of
course, I've seen also seen bad ones, cheap and nasty
monitors which
were always crappy, from the word go. And middling ones
which
deteriorated in short order. But I'm certainly not going to say
that
"CRT monitors are bad" simply because the bad ones were. Only a
few
years ago I gave away a valve CRT monitor from the 1960s which still
had
a razor sharp image.
I've seen plenty of bad LCDs. Everything
from: Only the highest
resolution ones don't look like you're
staring at a fluorescent tube
through flywire. Glaringly obvious
dead pixels, or even a whole third
of the screen all magenta. The
colour response being quite crap
(something that standard TV LCDs go
to all sorts of tricks to try and
get around). Very limited angle of
view without getting strange
distortions - thankfully that's getting
better, but it's still not
there.
While it was still possible
to buy both types, it was common to see that
LCDs two or three times
the price of a CRT looked worse than the CRT.
The cheap ones really
looked crap. Shops stopped setting up side by
side comparisons,
because even the untrained eye could see the
difference. To get what
I will accept as a decent picture, on an LCD,
I'd have to pay three
times as much as what I consider acceptable.
It's the "Emperor's
new clothes" all over again.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't
send private replies to my address, the mailbox is ignored. I
read
messages from the public lists.
I have this counter comment. I use a NEC Multisync e1100, and the only advantage I see offered by an LCD monitor is the width. To have a LCD monitor that gives me a full 11inch vertical letter size or A4 size as 1-1 on the screen puts the LCD monitor out of my budget range.
I can purchase great quality (exchange) CRT monitor from computer shops for about $50 to $60. (I can buy a used P4 working system for the same price).
The CRT monitor I have can provide fine hue adjustment, and very close color match to my laser printer output. I cannot say the same for the LCD monitors that I have used. It also has very fast response time, but my use is not for gaming, so I don't care.
The negative side of CRT is the big weight and footprint.
Leslie
14 years, 1 month
Boot Failed: wrong # of devices in RAID set
by CharlesAndLiz
Hi,
> I installed Fedora 12 and performed the normal updates. Now I can't
> reboot and get the following console error message.
>
> ERROR: via: wrong # of devices in RAID set "via_cbcff jdief" [1/2] on
> /dev/sda
> ERROR: removing inconsistent RAID set "via_cbcff jdief"
> ERROR: no RAID set found
> No root device found
> Boot has failed, sleeping forever.
>
> Rebooting multiple times does not help as in other posts.
>
> Any suggestions?
>
> francis9
>
14 years, 1 month
Strange 'ls' listing
by Jeff Kittle
Has anyone noticed that the ls command tacks on '.' Character at the end of
each permission string , example:
total 124
drwxr-xr-x. 2 root root 4096 2009-08-25 13:06 srv
drwxr-xr-x. 2 root root 4096 2009-08-25 13:06 opt
drwxr-xr-x. 2 root root 4096 2009-08-25 13:06 mnt
drwxr-xr-x. 2 root root 4096 2009-08-25 13:06 media
drwx------. 2 root root 16384 2010-04-05 02:30 lost+found
drwxr-xr-x. 3 root root 4096 2010-04-05 02:32 db
drwxr-xr-x. 15 root root 4096 2010-04-05 02:37 usr
dr-xr-xr-x. 9 root root 4096 2010-04-05 02:41 lib
dr-xr-xr-x. 5 root root 4096 2010-04-05 02:44 boot
drwxr-xr-x. 22 root root 4096 2010-04-05 02:46 var
drwx------. 3 root root 4096 2010-04-05 02:48 .dbus
dr-xr-x---. 4 root root 4096 2010-04-05 02:52 root
dr-xr-xr-x. 9 root root 12288 2010-04-06 03:39 lib64
dr-xr-xr-x. 2 root root 4096 2010-04-06 03:39 bin
dr-xr-xr-x. 2 root root 12288 2010-04-06 03:39 sbin
drwxrwxrwx. 3 root root 4096 2010-04-06 19:52 backup
dr-xr-xr-x. 153 root root 0 2010-04-07 00:38 proc
drwxr-xr-x. 13 root root 0 2010-04-07 00:38 sys
drwxr-xr-x. 7 root root 0 2010-04-07 00:38 selinux
-rw-r--r--. 1 root root 0 2010-04-07 00:38 .autofsck
dr-xr-xr-x. 26 root root 4096 2010-04-07 00:38 ..
dr-xr-xr-x. 26 root root 4096 2010-04-07 00:38 .
drwxr-xr-x. 4 root root 4096 2010-04-07 00:50 home
drwxr-xr-x. 18 root root 4280 2010-04-07 20:19 dev
drwxr-xr-x. 111 root root 12288 2010-04-07 20:19 etc
drwxrwxrwx. 7 jeff jeff 4096 2010-04-07 22:42 jeff
drwxrwxrwt. 8 root root 4096 2010-04-07 22:55 tmp
Pretty much screws up WInSCP unless I change the protocol from 'SCP' to
'SFTP'
14 years, 1 month
Audacity
by Michael Miles
Ok this is really weird.
I install Audacity and everything is fine (English)
I open preferences -do nothing then close prefs and all is in German
Can't change it back
Uninstall it and reinstall
Same thing English then German
Does anyone have the same problem?
1.3.11-01 beta x86_64
14 years, 1 month
Severe problems with radeonHD 3470 and dual head conf
by Peter Boy
Hi,
I bought a new box with an ATI Radeon HD 3470 (it is one of the rare
graphic boards with 2 DVI and passive cooling).
Installing F12 it automatically configures xinerama mode (better
spanning) as desired. But:
- Using a VGA adapter and VGA connection the second screen uses
a thinner, hard to read font and just a few different colors
(e.g. light grey will become white).
- Using DVI connectors directly the second monitor does not
receive a signal at all, allthough xrandr reports both monitors
connected and xorg.log reads the monitors specifications (and
does not report any error).
If I switch the monitors, the same effect. So it is not caused by the
monitor itself or the cable.
Any advice how to resolve it greatly appreciated.
Thanks in advance
Peter
14 years, 1 month
fedora 12 ping doesn't respect /etc/nsswitch.conf?
by Kevin Martin
Trying to ping a host that should resolv (via /etc/hosts) to an
particular IP address and via DNS to a different address, I find that
ping picks up the second address, not the first. My /etc/nsswitch.conf
specifically lists "hosts: files dns" but an strace of the ping clearly
shows that it's not even looking at /etc/nsswitch.conf. When did this
change?
Kevin
14 years, 1 month
fedora 12 named not updating pid file?
by Kevin Martin
I'm seeing where 1) /var/named/chroot/var/run/named.pid file is not
getting updated with the new pid upon a restart of named and 2) where
files in /var/named are getting owned by root upon yum updates and I
have to go "chown -R" the /var/named directory to the correct ownership
every time (this has been broken for a long fime). Is anybody else
seeing these issues and are there/will there be fixes for them?
Thanks.
Kevin
14 years, 1 month