Some of my fonts looks weirdly scrambled:
Why could that be? freetype-freworld?
Thanks in advance...
Rodolfo Alcazar - rodolfo.alcazar(a)padep.org.bo
otbits.blogspot.com / counter.li.org: #367962
"Das Fernsehen ist eine Infektion der Seele."
- Federico Fellini
I have two white vertical bar type objects in my system tray on KDE4
(F9)...one fairly thin, the other about twice the thickness.
If I hover over them or right click on them, I get nothing.
Does anyone know what they represent?
I have updated my desktop using the 64-bit desktop of F9 from F7. My
wireless is described by:
00:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset
Subsystem: Netgear MA311 802.11b wireless adapter
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at e9005000 (32-bit, prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: hostap_pci
Kernel modules: orinoco_pci, hostap_pci
Under F7 the wireless connected without any issues.
The I'm using plain old WEP on the access point. When I attempt to connect
the first NM pip turns green immediately but the second pip never does.
Eventually I'm asked for the WEP key. Entering it again does no good. I've
used system-config-network to statically enter the WEP key and specify the
SSID. Nothing works. I've never been able to connect under F9.
I notice that I'm never asked to unlock the keyring as I was under F5 and
F7. Are there any other suggestions as to what I can try?
I am trying to get my Palm M130 working with F9 using libusb. When I
start the hotsync, /var/log/messages shows this:
May 19 11:32:41 localhost kernel: hub 1-0:1.0: unable to enumerate USB device on port 3
May 19 11:32:41 localhost kernel: usb 3-1: new full speed USB device using ohci_hcd and address 16
May 19 11:32:41 localhost kernel: usb 3-1: configuration #1 chosen from 1 choice
May 19 11:32:41 localhost kernel: usb 3-1: New USB device found, idVendor=0830, idProduct=0050
May 19 11:32:41 localhost kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
May 19 11:32:41 localhost kernel: usb 3-1: Product: <FF><F7><9F>
May 19 11:32:41 localhost kernel: usb 3-1: Manufacturer: Palm, Inc.
May 19 11:32:41 localhost kernel: usb 3-1: SerialNumber: PalmSN12345678
May 19 11:33:54 localhost kernel: usb 3-1: USB disconnect, address 16
The "address 16" on the second and last lines increments each time I try
it, otherwise it is identical every time.
I also get the following in /proc/bus/usb/devices:
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 16 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=0830 ProdID=0050 Rev= 1.00
S: Manufacturer=Palm, Inc.
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
and I get a corresponding entry in /proc/bus/usb/003 (in this
However, "pilot-xfer -p usb: -l" just sits there saying "Listening for
incoming connection on usb:..." forever.
Is there anything special I need to do to configure this? Any
troubleshooting ideas? Or should I just give up on libusb and use visor?
There are several things about Fedora 9 that bug me.
First, SELinux is configured, with no ability to opt-out, as was the
case in Fedora 8. Second, the "automatic login for a designated user"
has been removed.
Both of these are clearly security-related, but where is it written
that Fedora needs to force us to "be good". Strikes me that the folks
who do these things need to ask what the users want. Or was I asleep
when the discussion raged on the list?
Third, not security related but emblemantic of the same mindset, I
suspect, is the introduction, again by default with no opt-out, of
UUIDs. I understand that this is thought to be a Good Idea (tm) for
those users who use bleeding-edge software on their multi-system
networks, but for the rest of us, its just a pain, and makes life more
complicated for those of us that administer our own laptops.
Now I feel better.
I just installed F9 on my shiny new box.
The install went fine.
When it spit the DVD out and ebooted the video was awful.
The screen apppers to be tearing/sparkly.
I had to guess with the Tab key/mouse and Enter to get a user added and go into X.
Once there the video is still broken.
I tried system-config-display.
It says I am running st 640x480 and millions of colors.
The size drop-down menu just shows 640x480, the colors millions/thousands.
It seems to be much higher display than that though.
Too tall for the screen, cannot "mouse down" even near the bottom.
I looked in /etc/X11 xorg.conf and it says "vesa"
I googled and could not find a fix (had to use this old system)
The card is ID as Radeon HD 3450, the box says ASUS EAH3450.
It is a fanless 256M PCI Express 2.0 "HDCP compliant" card.
The install display was quite nice and I would be happy to see that resolution again.
The box barcode read:EAH3450/HTP/256M/A
I am using the 15 pin vga output not the DVi-I
Death before Decaf!!!
*I would like to know if anyone is having problems getting their wireless
connection to actually connect in Fedora 9 using Network Manager?*
I just installed Fedora 9 on my laptop (Thinkpad R40). I did not do the 76
updates yet, but out-of-the-box, my wireless won't connect. The LAN
connects just fine, but not wireless. It's great that network manager does
an auto broadcast, now. I put in my WEP information, which I
triple-checked, but it says the connection has disconnected. I even tried
it on WEPless access points and the same thing happens.
*Skill-set:* I am a linux noob so I do not fully understand all the terms
or concepts yet. I am a Windows power-user, but as you all know that
doesn't mean squat with a REAL operating system. Thanks for your help.
"..Grace to you and peace from Him who is and who was and who is to come.."
I have a PC that is failing intermittently. What are the best choice for
attempting to pinpoint a hardware fault - in terms of either fedora
packaged or other open sourcesoftware ?
Perhaps there is something that can both perform one of and 'to death'
tests of various PC components, and components in combination, and also
provide peak workload for all subsystems at once, in an attempt to
generate a slow to occur failure.
I know about memtest, and read-only disk tests from fsck. Any others ?