given the first release of android 2.0, has anyone out there
successfully installed that on a 64-bit fedora? specifically, fedora
11 or (hopefully equivalently) fedora 12 beta.
i'm just about to give it a shot, but it would be nice to know that
someone else has already done it and identified any glitches hidden in
the install instructions:
based on a quick perusal, it would seem that open jdk is now
compatible (whereas it didn't used to be), and one still has to
install the minimal packages for 32-bit compatibility. in any event,
if someone else has already done this, that would be awesome.
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Has anyone had a total failure to run kmod-nvidia with an 8300 GS graphics
card in f11?
used to run with the kmod-nvidia-PAE installed from rpmfusion just fine in
f10 with no issues at all.
When I installed (clean) the new f11 system on this machine (in fact two
machines with this card both have identical issues), the install was fine, I
then yum updated to the latest kernel and, as per my normal upgrade
procedure, then yum installed kmod-nvidia-PAE from rpmfusion. This process
worked without issue on two other machines which have nvidia graphics cards
(but not the 8300 card). On rebooting, the boot began as normal (text
kms/plymouth with the blue/white running line on the bottom of the screen),
but as soon as x should start - it didn't. There was a blank screen with a
flashing cursor at top right only. I removed the kmod-nvidia package, and
xorg.conf and ran without it until yesterday.
After updating the system to the new kernel yesterday I booted to the new
kernel 18.104.22.168-90.fc11.i686.PAE - which was fine and tried yum install
kmod-nvidia-PAE (which is the correct version of kmod-nvidia for this card
and kernel I believe) and rebooted - same as the original problem - after
the plymouth non-graphical boot, blank screen with flashing cursor - except
that some seconds later a couple of lines of text appeared on the screen
related to selinux audit. I removed kmod-mvidia and am running without it
again - this morning in the syslog there are lines:
audit(1256631766.417:29202): auid=4294967295 ses=4294967295
subj=system_u:system_r:readahead_t:s0 op=remove rule key=(null) list=2 res=1
However I am not sure this is directly related to the kmod-nvidia-PAE or
Anyway I wonder if anyone else has had a problem with this card and an
inability to use kmod-nvidia? If so is there a known workaround?
Thanks for any replies.
View this message in context: http://www.nabble.com/F11-Nvidia-8300-GS-and-kmod-nvidia-PAE-fail-tp26091...
Sent from the Fedora List mailing list archive at Nabble.com.
when trying to copy a certain file, i get the message:
cp: reading 'file' : Input/output error
i took the volume it was on offline, & did a forced
e2fsck. same thing.
smartctl -H tells me the drive 'passes' .
i can change the name with mv, no problem there.
are there any other (non-destructive) steps i can take?
Do What Thou Wilt
The Whole of
Is there a HOWTO around on how to use an Epson perfection 2480 USB
scanner on Fedora 11 x86_64 ?
So far sane-find-scanner (run as root) returns two devices:
found USB scanner (vendor=0x146a [Knobloch-GmbH],
product=0x0003 [fischertechnik Robo RF Data Link (Knobloch GmbH)])
found USB scanner (vendor=0x04b8 [EPSON],
product=0x0121 [EPSON Scanner])
I hope that the first one does not confuse the system. It is *not* a scanner.
Then scanimage -L returns:
device `snapscan:libusb:001:002' is a EPSON EPSON Scanner flatbed scanner
And when I try something like:
scanimage -d 'snapscan:libusb:001:002'
[snapscan] Cannot open firmware file /usr/share/sane/snapscan/your-firmwarefile.bin.
[snapscan] Edit the firmware file entry in snapscan.conf.
scanimage: open of device snapscan:libusb:001:002 failed: Invalid argument
I have no idea what this is about.
Any help welcomed.
It looks like environment variables set in .bash_profile are visible
to applications started in gnome but not via a shell. For example
evolution knows when I modify LC_COLLATE.
But how? Here's the invocation chain from login down to evolution -- no
1710 ? Ss 0:00 /usr/sbin/gdm-binary -nodaemon
14284 ? S 0:00 \_ /usr/libexec/gdm-simple-slave --display-id /org/gnome/Disp
14285 tty7 Ss+ 0:43 \_ /usr/bin/Xorg :0 -br -verbose -auth /var/run/gdm/auth-
14366 ? S 0:00 \_ pam: gdm-password
14413 ? Ssl 0:00 \_ gnome-session
14523 ? Sl 0:00 \_ metacity
14536 ? S 0:00 \_ gnome-panel
14537 ? S 0:00 \_ nautilus
14542 ? S 0:00 \_ /bin/sh /usr/lib64/firefox-3.5.4/run-mozilla.s
14651 ? Sl 0:41 | \_ /usr/lib64/firefox-3.5.4/firefox
14543 ? Sl 0:17 \_ evolution
What am I missing?
Thanks - jon
I installed Fedora 11 on a DiskOnKey. I booted from this DiskONKey
successfully on the machine
on which I made the installation. However, when I tried on two
different machines, it failed, and it reached the
grub command line. On a third machine it reached a line containing the
word GRUB only.
I wonder - is there a way to install Fedora 11 on a DiskOnKey so that
it will boot from any machine (which is capable of booting from USB )?
Note: I had made my trials on motherboards after verifying that these
motherboards **do** support boot from
USB disk on key.
This is the grub.conf on the USB DiskOnKey:
title Fedora (22.214.171.124-167.fc11.x86_64)
kernel /boot/vmlinuz-126.96.36.199-167.fc11.x86_64 ro root=UUID=e73e50db-2420
-4792-a347-3e15ed38c5b9 rhgb quiet
I was trying to read an online tool catalogue, and noticed a PDF button at the
bottom of the webpage. Clicked on it, and it opened the dialog box to
download. What has been downloaded though is a .php script (27.3MB).
The properties shows that it contains a pdf document, but I've no idea how to
run it, open it, or whatever needs to be done, to get to see the PDF.
Any suggestions folks.
My truly ancient Epson C82 finally refused to respond to the head cleaning
paddles yesterday, so I went out and got a new Epson NX515 combo scanner &
It signs on as: (Fedora 10, kernel 2.6.32-rc5)
Oct 23 20:27:15 coyote kernel: [598891.940960] usb 1-4: new high speed USB device using ehci_hcd and address 16
Oct 23 20:27:15 coyote kernel: [598892.079434] usb 1-4: New USB device found, idVendor=04b8, idProduct=0856
Oct 23 20:27:15 coyote kernel: [598892.079437] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 23 20:27:15 coyote kernel: [598892.079440] usb 1-4: Product: USB2.0 MFP(Hi-Speed)
Oct 23 20:27:15 coyote kernel: [598892.079442] usb 1-4: Manufacturer: EPSON
Oct 23 20:27:15 coyote kernel: [598892.079444] usb 1-4: SerialNumber: 4C454C593037313524
Oct 23 20:27:15 coyote kernel: [598892.079540] usb 1-4: configuration #1 chosen from 1 choice
Oct 23 20:27:15 coyote kernel: [598892.087345] usblp2: USB Bidirectional printer dev 16 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0856
Oct 23 20:27:15 coyote kernel: [598892.088576] scsi10 : SCSI emulation for USB Mass Storage devices
Oct 23 20:27:20 coyote kernel: [598897.090894] scsi 10:0:0:0: Direct-Access EPSON Storage 1.00 PQ: 0 ANSI: 2
Oct 23 20:27:20 coyote kernel: [598897.091362] sd 10:0:0:0: Attached scsi generic sg9 type 0
Oct 23 20:27:20 coyote kernel: [598897.101631] sd 10:0:0:0: [sdi] Attached SCSI removable disk
Oct 23 20:27:23 coyote hal_lpadmin: File "/usr/libexec/hal_lpadmin", line 717, in main#012 h = HalLpAdmin()
Oct 23 20:27:23 coyote hal_lpadmin: File "/usr/libexec/hal_lpadmin", line 686, in __init__#012 self.addPrinter()
Oct 23 20:27:23 coyote hal_lpadmin: File "/usr/libexec/hal_lpadmin", line 700, in addPrinter#012 printer.add()
Oct 23 20:27:23 coyote hal_lpadmin: File "/usr/libexec/hal_lpadmin", line 541, in add#012 location=os.uname ())
Oct 23 20:27:23 coyote hal_lpadmin: IPPError: (1025, 'client-error-forbidden')
which appears that the scanner, ahh, wait, its got a card reader in it too,
in addition to ethernet and bluetooth. So that explains /dev/sg9 and /dev/sgi.
So there are two problems, which do not prevent it from being used for all
sorts of utility printing.
Problem 1 is that the newest Epson/gutenprint drivers are for the NX400
series, so the maximum useable resolution is 1440x720, whereas it can go
as high as 5760x2880. I would like to be able to get to 2880x2880 for photo work.
Problem 2 is that the scanner doesn't even check in as shown above.
OTOH, I also have an Epson 1250u that works flawlessly, but it would be nice
to get rid of one rather high occupancy item here in the coyote.den.
The current xsane device dialog skips it, going directly to the Epson 1250u,
so xsane isn't seeing it, and while I have kooka according to the menu's, it
doesn't come when called.
Has anyone a clue to pass along?
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
No man is an island, but some of us are long peninsulas.
I have installed F11 on an Asus Eee PC 1101HA which has the GMA 500 chipset.
After running yum for updates, I now have two kernels installed:
For the GMA 500, I installed the following:
Oct 28 00:28:57 Installed: psb-firmware-0.30-4.fc11.noarch
Oct 28 00:28:58 Installed: xpsb-glx-0.18-5.fc11.i686
Oct 28 00:28:58 Installed: libdrm-poulsbo-2.3.0-10.fc11.i586
Oct 28 00:29:46 Installed: rhpxl-1.12-2.fc11.i586
Oct 28 00:29:48 Installed: system-config-display-1.1.3-2.fc11.noarch
Oct 28 00:29:48 Installed: livna-config-display-0.0.23-1.fc11.noarch
Oct 28 00:29:48 Installed: kmod-psb-4.41.1-10.fc11.2.i586
Oct 28 00:29:51 Installed:
Oct 28 00:29:58 Installed: xorg-x11-drv-psb-0.31.0-15.fc11.i586
If I boot the original kernel, X boots OK, only the startup complains about
not finding "psb.ko". Ok, that makes sense; I only have the 2.6.30 version
installed. But if I boot the latest kernel, the boot process hangs at some
point after "Starting UDEV..." (no error message is displayed).
There are a few lines in the system log but they don't tell me much:
Oct 28 01:13:05 pollux kernel: psb 0000:00:02.0: PCI INT A -> GSI 22 (level,
low) -> IRQ 22
Oct 28 01:13:05 pollux kernel: [drm] psb - 5.0.1.0046
Oct 28 01:13:05 pollux kernel: [drm:psb_do_init] *ERROR* Debug is 0x00000000
Oct 28 01:13:05 pollux kernel: psb 0000:00:02.0: firmware: requesting
Oct 28 01:13:05 pollux kernel: fbcon: psbfb (fb0) is primary device
Oct 28 01:13:05 pollux kernel: [drm] fb0: psbfb frame buffer device
Oct 28 01:13:05 pollux kernel: [drm] Initialized psb 4.41.1 20090416 on
Can anyone give me some pointers on how to determine what is going wrong
here? The Xorg log isn't much help. Also, is there a way of forcing the boot
process to stick with text-only? Booting at run level 3 doesn't seem to do
View this message in context: http://www.nabble.com/Intel-GMA-500-problems-on-Eee-tp26087610p26087610.html
Sent from the Fedora List mailing list archive at Nabble.com.
I try to access the boot menu, where you can choose a kernel and,
whatever key I press, I can't stop the countdown and access the boot
I checked /boot/grub/grub.conf and I have hiddenmenu in it. But the
back-up, /boot/grub/grub.conf~ dates back to August and has hiddenmenu
in it too. Since I accessed the boot menu since August, I suppose this
is not the problem.