I just did:-
yum install gallery2
It installed with no errors.
The trouble is I now have no clue as to what to do next. What do I
have to do next, I can't see any *obvious* pages to browse to get it
Yes, I do have apache installed and running, and PHP, and mySql.
I am having trouble getting Fedora 9 (x86_64 live cd) to read my SD
card using a built-in Ricoh MMC reader on an HP 8510 laptop (Core 2
Duo). I get mmcblk0 and mmcblk0p1 in /dev but any attempt to read the
card fails. I see an icon in Nautilus but after opening it and a brief
pause I get an error "Can't read superblock". Also, any attempt to
inspect the device in parted or fdisk also fail. They both complain
about lables but I'm not sure if they are talking about filesystem
labels or volume lables. I can't see why the latter would cause an
issue. I tried the mklabel command in parted setting it to msdos but
it couldn't complete... I'm in Windows XP right now and it's reading
Along those lines, is it possible to get the UUID of a disk from windows?
I've just installed Fedora 9 on my laptop, and unfortunately a few
things are getting worse in Fedora.
Network management has always been awkward on Fedora and with Fedora 9
it's getting much worse.
1. I have always edited the config files directly to get things
working. And still have to ( it's just a straight forward wireless
2. NetworkManager is now the default on install, BUT...
2.1 NetworkManager does not give you a wireless connection when no
user is logged in.
2.1.1 How am I going to run any network service, NTP, NFS,
httpd, etc..... without a network?
2.1.2 How am I going to remotely administer my machines?
2.2 NetworkManager does not give you the ability to configure system
wide networking services or policy.
2.3 NetworkManager does not have any decent documentation.
3. Try using WPA and DHCP at the same time. It's never worked in this
or any previous Fedora. Yes, NM will do it, but that's no good because
of the previously stated problems. the network service won't do it
because it tries to run DHCP immediately after bringing up the
interfaces...It SHOULD wait until wpa_supplicant has run and the
interface is available for traffic before kicking off DHCP...
GDM was functional, well behaved and stable in Fedora 8. I used it to
log into other F8 machines locked away in difficult to get at racks.
Fedora 9 has effectively removed that ability by shipping a GDM with
gdmsetup. How many users depend on that functionality? I did, and
won't be able to upgrade to F9 for any other machines.
Use the fedora website/wiki to collect information about use cases.
Find out what people depend on. Use that to provide a guarantee that
functionality and usefulness won't go backwards. If it was ever setup,
I'd tell you everything I do with my machines.
so far the installation of FC6 has gone relatively smoothly albeit some
additional learning and bumps due to the 64 bit architecture of this
The mother board is an Intel DG965RYCK which uses Intel's 965 express
chipset. Based upon what I've been able to find on the web, Intel has
released the drivers for this chipset to OSS, although there have been
issues as to what Intel actually released and how complete they might be.
Regardless I unable to run mplayer (or Realplayer) for that matter
without the display first freezing then going black followed by garbage
along the bottom of the screen. A Control-Alt-Backspace does not stop X
from running. The only way to recover the machine from this point is to
reboot the system. I am still able to connect from a remote system, its
just the display that has become unstable.
lspci -v shows the following for the graphics adapter
00:02.0 VGA compatible controller: Intel Corporation Integrated
Graphics Controller (rev 02) (prog-if 00 [VGA])
Subsystem: Intel Corporation Unknown device 514d
Flags: bus master, fast devsel, latency 0, IRQ 177
Memory at 50200000 (32-bit, non-prefetchable) [size=1M]
Memory at 40000000 (64-bit, prefetchable) [size=256M]
I/O ports at 3110 [size=8]
Capabilities:  Message Signalled Interrupts: 64bit-
Capabilities: [d0] Power Management version 2
suggestions would be appreciated.
Was gdmsetup removed from Fedora 9? I'm trying to figure out how to
Thomas E. Casartello, Jr.
Department of Information Technology
Westfield State College
Red Hat Certified Technician (RHCT)
I am having problems with NetworkManager and wireless network. When I
installed Fedora 9 NetworkManager was working fine and able to connect
to wireless networks. However, after I did the first update suggested by
the OS, NetworkManager stopped being able to recognize wireless
networks. I formatted and installed Fedora 9 twice to confirm the
problem. I could not however identify which update is causing this
problem. Anybody having the same problem? Thanks.
this is somehow off-topic, but hopefully someone here has been through
I just bought a shiny new Core 2 Duo machine (Intel DG33BU mobo), with
a nice 250G SATA disk. Fedora 7 installation went surprisingly well
(and fast), only problem was that onboard NIC was not recognized, but
upgrading the kernel offline fixed this. Everything is amazingly fast
BUT... I need this machine to dual-boot to Windows XP (still addicted
to some Windows-only games =( ). XP setup CD hangs just after showing
"examining hardware configuration" or something like that. It doesn't
really hangs, it just switches to a blank screen and sits there
forever (I already left it there for more than 15min to no avail).
Keyboard is responsive and HD led stays on. CTRL+ALT+DEL reboots as
I talked to IT guys at work and they told me they've been through this
already lots of times, it seems XP is unable to properly recognize the
disk when only Linux is installed on it (?!?), and only solution would
be to reformat the whole thing and install XP first.
Is that true?
My system is configured as:
~ fdisk -l /dev/sda
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 10467 83971755 8e Linux LVM
HD specs are:
~ hdparm -I /dev/sda
ATA device, with non-removable media
Model Number: SAMSUNG SP2504C
Serial Number: S09QJ1SP208120
Firmware Revision: VT100-50
GRUB is installed on MBR. All remaining space is sitting there,
waiting for XP to take over... =/
Anyone knows of a workaround? Should I try to create an additional
partition on the empty space and format it as VFAT hoping this would
make Windoze less stupid? Or am I doomed to remove all partitions and
start from scratch, starting with XP?
I've just installed F9 in my Vmware workstation 6 but I couldn't
change my defualt 800x600 resolution to 1024x768. Is VMware causing this
problem? Any Idea.
Registered Linux User# 441709.
I am trying to get a Canon LBP2900 laser printer working under F9.
Alas, the driver is (apparently) closed and not included in the Caps
package, which might be a reason to avoid this printer, but be that as
it may, one can download a Linux driver easily enough from Canon:
These are the latest RPMs:
2007-12-03 08:49 cndrvcups-capt-1.60-1.i386.rpm
2007-12-03 08:49 cndrvcups-common-1.60-1.i386.rpm
Once installed, CAPS automatically recognizes the printer and selects
what appears to be the correct driver:
Canon LBP2900 CAPT ver.1.5
Likewise, the printer shows up properly in dmesg:
usb 1-4: new high speed USB device using ehci_hcd and address 26
usb 1-4: configuration #1 chosen from 1 choice
usblp1: USB Bidirectional printer dev 26 if 0 alt 0 proto 2 vid 0x04A9
usb 1-4: New USB device found, idVendor=04a9, idProduct=2676
usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4: Product: Canon CAPT USB Device
usb 1-4: Manufacturer: Canon
usb 1-4: SerialNumber: 0000A380HGkZ
but if I try a test page, nothing happens. The only indication that
something is wrong is this error message repeatedly displayed in dmesg:
usblp1: error -32 reading printer status
Any ideas what is going on here?