RAGE XL Framebuffer
by Yanick Quirion
Hi all
I know that is not a specific question about Fedora, but I can't find answer on the kernel mailing list.
Is somebody having server with integrated ATI RAGE XL video card? Is it possible to patch the kernel to support this video card? If I add VGA=791 in my grub.conf, I will have a resolution of 1024x768 which is good, but the display is very slow (especially when the screen is scrolling). If I use I this: "video=aty128fb:1024x768@70" it will not work. I'm using kernel 2.4.22 but I will try 2.6.0-test11 today.
If somebody has a patch, a link or anything else that can help me, it will be appreciated.
Thanks for your help.
Regards,
-----------
Yanick Quirion
Administrateur Réseau/Network Manager
NEOKIMIA INC.
Institut de Pharmacologie de Sherbrooke
3e étage (Édifice Z5)
3001 12e avenue Nord
Sherbrooke, Québec
CANADA
J1H 5N4
Tél.: +1 819 820-6040
Direct: +1 819 820-6855
Fax.: +1 819 820-6841
email: Yanick.Quirion(a)neokimia.com
9 years
Soundblaster
by Antonio Montagnani
I have two similar PC (old Pentium but workin fine)
In Pc no.1 I upgraded from RH8 to Fedora and it went fine: Soundblaster
is working fine
In Pc no.2 I made a fresh installation but in redhat-sound-config Fedora
doesn't see any card, that was working on Redhat 9 after soundconfig...
Where is the trick?? I assume that my Sounblaster is an old 16...but
fine on a router/firewall.
Tnx
Antonio
9 years
WiFi permanently disappeared after booting test kernel
by Mike Fleetwood
Hi,
On my netbook I booted a test kernel 3.8.0-rc4+ I compiled. Now after
booting back into my regular Fedora kernel 3.6.11-5.fc17.i686.PAE my
wifi network device remains permanently disappeared. No wifi networks
displayed in Network Manager gui. Also the Network Manager syslog
messages make it look like the device has completely disappeared.
Suggestions for restoring wifi welcome.
Thanks
Mike
Fragment of Network Manager syslog messages when working before
--8<--
Jan 18 23:01:53 edge NetworkManager[479]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill2: found WiFi
radio killswitch (at
/sys/devices/pci0000:00/0000:00:1c.3/0000:01:00.0/ieee80211/phy0/rfkill2)
(driver ath9k)
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill0: found WiFi
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill0)
(platform driver eeepc)
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill4: found WWAN
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill4)
(platform driver eeepc)
Jan 18 23:01:53 edge NetworkManager[479]: <info> WiFi enabled by radio
killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> Networking is enabled
by state file
...
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): using
nl80211 for WiFi device control
Jan 18 23:01:53 edge NetworkManager[479]: <warn> (wlan0): driver
supports Access Point (AP) mode
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): new 802.11
WiFi device (driver: 'ath9k' ifindex: 3)
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): exported as
/org/freedesktop/NetworkManager/Devices/1
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): now managed
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): bringing up device.
...
Jan 18 23:01:59 edge NetworkManager[479]: <info> Activation (wlan0)
successful, device activated.
Jan 18 23:01:59 edge NetworkManager[479]: <info> Activation (wlan0)
Stage 5 of 5 (IPv4 Commit) complete.
Fragment of Network Manager syslog messages when broken after
--8<--
Jan 28 18:43:26 edge NetworkManager[466]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 28 18:43:26 edge NetworkManager[466]: <info> rfkill0: found WiFi
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill0)
(platform driver eeepc)
Jan 28 18:43:26 edge NetworkManager[466]: <info> rfkill2: found WWAN
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill2)
(platform driver eeepc)
Jan 28 18:43:26 edge NetworkManager[466]: <info> WiFi disabled by
radio killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> Networking is enabled
by state file
No (wlan0) related NetworkManager syslog messages afterwards at all.
9 years, 9 months
What happened to floppy drive support?
by n2xssvv.g02gfr12930
I've been using a floppy boot disk as reserve if my HD boot fails, But
it appears floppy support as now been removed. Why? Then how can I
create an emergency media that is flexible enough to be updated as required?
JB
10 years, 11 months
no printout, but no other hint of error. F18.
by William Mattison
Hi,
When I try to print anything out, I get no printout. Even a test page does not come out. But no indication of trouble shows up on the monitor, and no indication of trouble on the printer's display. I did download and install the driver. cups gives no hint of trouble that I recognize. If I restart the system and boot up with Windows 7 home, I do get printouts.
The printer is a Xerox WorkCentre 6015ni, I'm using Fedora-18, 64-bit, and the printer is connected to the system via usb bus. This is a stand-alone home desktop.
I'm neither trained nor experienced in sys. admin. I've exhausted the help I can get from the printer's manual (media and web site). Any help you can give will be appreciated.
Bill.
11 years
Runlevel 3 after fedup
by ellis＠spinics.net
After upgrade from 17 to 18 with fedup and installing all the updates I was
unable to login as any user other than root. When I tried I was greeted with
the message: "System is booting up".
After beating my head against the wall I finally tried booting to runlevel
5 instead of 3. That fixed the issue. But booting to runlevel 3 and switching
to 5 doesn't work.
Possibly a problem with systemd?
--
http://yosemitenews.info/
11 years, 1 month
Unrelieved black popups and message boxes
by Temlakos
Everyone:
I asked this before under a different heading, and no one answered.
I get a large volume of e-mail, and very often I interact with a site
that brings up a lot of message boxes, "suggestion boxes" (for
auto-filling from a few keystroke clues), and bringing up apps after
they were minimized to the system tray or the task bar. Now why is it
that, after maybe two hours of operation, those popups come up and are
totally black? The only way to solve the problem, that I have found, is
to shut down. And even then, I can't even see what I'm doing, but have
to guess where the icons are for executing a controlled shutdown. (I can
always bring up a command-line login screen, log in as root, and then
shut down. But that doesn't seem to solve the problem for the next session.)
And when I log back on, everything's fine--until it starts happening
again, after several more window draws.
What could be causing this? Where do I even look for error logs and the
like?
I never had this problem in any other version of Fedora. I'm having it
now, and it's driving me nuts.
For the record, I used the "upgrading from F17 to F18 using yum" method.
I even used the elaborate script that walks you through rpmnew and
rpmsave reconciliation. And I've kept up with every system update since
then. Actually, the problem began about three kernel updates back.
Temlakos
11 years, 1 month
Problem with cron
by Joe Zeff
I have my computers registered with the Linux Counter, and my main
desktop machine is supposed to update its status once a week, using a
cron job:
# added by lico-update.sh version 0.3.14
58 11 * * 4 /home/joe/bin/lico-update.sh -m
The permissions on the script are right, and if run manually, it works.
This worked fine under Fedora 16, but doesn't now that I'm running F
17. Does anybody know what's happened, or how to find out?
11 years, 2 months
Samba 4
by Gabriel VLASIU
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi!
Maybe someone can help me with samba 4 (F18).
In previous version (samba 3/F17) I had this definition for a share:
[xxx]
path = /xxx
browseable = yes
writable = yes
; writable = no
printable = no
public = yes
guest only = yes
guest ok = yes
create mask = 0664
directory mask = 0775
force group = xxx
The important thing here is "create mask". I do not want all files created
by users to be executable in linux.
The same definition work in samba 4 with the exception of running windoze
.exe files from the share. In windoze, there is no read & exec permissions
associated with the file. Only read for everyone and read/write for unix
user/group. I can manually set the exec flag (from linux or windoze) but
this has to be made every time someone copy an executable file.
Any chance to revert to the behavior from samba 3?
Thank you.
Sincerely,
Gabriel
- --
// Gabriel VLASIU
//
// OpenGPG-KeyID : 44952F15
// OpenGPG-Fingerprint: 4AC5 7C26 2FE9 02DA 4906 24B2 D32B 7ED7 4495 2F15
// OpenGPG-URL : http://www.vlasiu.net/public.key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
iQIcBAEBCgAGBQJRCntGAAoJENMrftdElS8VccwP/1Bn7zfctWYW86LES/0kE0J/
nig6I927ekX2d+UwUBffUmFgL/G9Pfh4drX7Lrh/HakT/MBerUxZa79URF3v7mLS
OmX00areoAHBc1wBo39xHLujNKwwifr4fdgLLFt3hsA0iL6R71l6eDz9tzk7SUPA
zpdo6bx9mqX95TdmDHR/q+2Z5ab39hP5AkIRWZwa8jQiSHKn5RN4MyWsTtpFnCkR
fM88zmDq72NGXJD9oApd9LLvZbw08rILI7na6IXIcFg+HTowM0IhozPUdqfPtYf9
FgmQP7vg1J38U8Lw7P4n+5/eei/+h0YdMHs1N864aYumNz+Ts+2KU1RLyzr9ZIUg
YkcQ6V60WA5Esy2c7p87/TgL+5bRa4pqMhghLXcoBAxRbaqFOY7i2fbb8/+JfU1y
lJq5z08M0RXDV0dSwKix1iuGd5cfSfoFroC8J9SXttMZcPwoDVIz5L/arWFFGByo
f9m5XD5fPMxOY8vIkGbO62oYhH66gIIelvQXT8g7TiTWgIeTXdOigYEeZQye43Fk
Sst9nS/JUpZcXSq8qIErh/WD4nvAOzUg3p0IgwHpmqxIndDNrVD1aol3mooKuv94
gzZWQEU1Z0Tfm5NnS5qrsiU3RnwgkI8qya5xHVFIhzMTUP7ickWNA1myRdBWXDt0
gc7W1TxMJY3xZ2u1Bngx
=uDBh
-----END PGP SIGNATURE-----
11 years, 2 months
