Can't read/mount SD flash memory card in builtin reader.
by Richard Shaw
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
it fine.
Along those lines, is it possible to get the UUID of a disk from windows?
Richard
15 years, 7 months
resize LVM partition
by David Hláčik
Hello guys,
i have removed sda1 partition with Windows , now i have free space on disk
There is
sda1 - now free space
sda2 - /boot
sda3 - LVM
Now i want to resize sda3 to take free space over sda1. Is this possible? as
there is sda2 in way before ...
Is the best solution to just create sda1 with LVM and then resize my volume
group to sda1 also?
Thanks !
David
15 years, 7 months
fedora8 install virtualbox2.0.4:undefined symbol: _ZN7QRegionpLERK5QRect
by gao wenk
[root@Fedora8 share]# VirtualBox
VirtualBox: supR3HardenedMainGetTrustedMain:
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed:
/usr/lib/virtualbox/VirtualBox.so: undefined symbol: _ZN7QRegionpLERK5QRect
why?
fedora8+ VirtualBox-2.0.4_38406_fedora8-1.i386.rpm.
kernel.i686 2.6.23.1-42.fc8
installed
kernel-devel.i686 2.6.23.1-42fc8
installed
kernel-headers.i386 2.6.23.1-42.fc8 installed
gcc.i386 4.1.2-33
installed
gcc-c++.i386 4.1.2-33
installed
gcc-gfortran.i386 4.1.2-33
installed
libgcc.i386 4.1.2-33 installed
qt4.i386 4.3.2-1.fc8
installed
qt4-devel.i386 4.3.2-1.fc8
installed
qt4-doc.i386 4.3.2-1.fc8
installed
qt4-x11.i386 4.3.2-1.fc8 installed
install VirtualBox-2.0.2_36488_fedora8-1.i386.rpm
add root to virtualbox group
/etc/init.d/vboxdrv setup
then,error appears,"_ZN7QRegionpLERK5QRect"
google it,only
http://fixunix.com/suse/532996-sun-virtualbox-opensuse-11-a.html
http://en.opensuse.org/VirtualBox_Installation
just for opensuse.
15 years, 7 months
gnome-keyring not working
by Martín Marqués
I have my Notebook with Fedora 9 and I normally access 3 different
WIFI AP with WPA encryption. The thing is that connection is great
using nm-applet, but the WPA passwords don't get stored in
gnome-keyring. The gnome-keyring daemon is running but each time I
connect to one of the AP I have to give the passphrase to establish a
connection.
Any ideas on what the problem can be. I already tried erasing the
.gnome2/keyring/* files and starting gnome-keyring again.
--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador
15 years, 7 months
Re: ****Re: Data Recovery:
by Craig White
some suggestions...
- that you use keep discussions on the list and not think of me as your
personal support dude.
- that you suggested that you updated to Fedora 9 but that boot options
are Fedora 8 and have to answer my first question about how you updated
from Fedora 8 to Fedora 9 - i.e. the process used because it appears
that it failed. You probably don't realize that when you fail to answer
the first question I asked, I lost a lot of enthusiasm to help.
- let whatever updates do their thing because it does seem as though
you've got something very unfinished installed there and if it were
completely updated, that seems that would be a good thing.
- that you learn to read release notes, especially before doing things
like update an installation because sometimes, they are really
important.
- if after the updates, gnome still fails to give you menus with
applications, someone on the list can tell you how to restore them back
to defaults.
Craig
On Mon, 2008-10-27 at 00:08 +0000, vohnmaxwell(a)bellsouth.net wrote:
>
> After some trial and error and gnashing of teeth, I have finally
> gotten to the point where I can bring up 2 separate terminal sessions
> within the Gnome Gui Desktop. However, I am still not able to click
> on applications, such as FireFox or Yum and have it launch within the
> gui desktop.
>
> I will use the terminal sessions to continue updating Fedora 9 (about
> 500 currently).
>
> Could the possible issue with launching the applictions within the
> desk top be related to the boot options? When I boot and press any
> keep to bypass the default (Xen), the options it displays are for
> Fedora 8 not 9.
>
>
> -------------- Original message from Craig White
> <craigwhite(a)azapple.com>: --------------
>
>
> > On Sun, 2008-10-26 at 13:11 +0000, vohnmaxwell(a)bellsouth.net
> wrote:
> > >
> > > Here a are the steps I've taken and the results.
> > >
> > > 1) Installed Fedora 9
> > > Found that Fedora 9 does not support Xen very well. When
> > > loading, it would encounter a (XEN) Xen is relinquishing
> VGA console
> > > message then hang up. When I would bypass XEN and attempt
> to use one
> > > of the listed Fedora versions, which I would have assumed
> would be
> > > Fedora 9, the list would be for versions of Fedora 8.
> After they
> > > would load, the applications would not run. I would click
> on an
> > > application, say Firefox, and it would not load. Nothing
> would
> > > happen. I would seem that Fedora was confused by having
> some parts
> > > perhaps Fedora 9 and others Fedora 8 and not being
> compatable.
> > ----
> >
> http://docs.fedoraproject.org/release-notes/f9/en_US/sn-Virtualization.html
> >
> > "However, the Xen kernel now lacks Dom0 support. An existing
> Xen
> > host/Dom0 must continue to run Fedora 8. Xen Dom0 support
> will be added
> > back in Fedora 10."
> >
> > This was in the release notes for Fedora 9
> > ----
> > > 2) I tried the Rescue and was confused as to what/how it
> worked.
> > > if said that it put my system to /mnt/sysimage and that I
> could
> > > use the chroot /mnt/sysimage. Well, I am a GUI kind-of-guy
> and I am
> > > clumbsy using anything in command mode.
> > ----
> > I would suggest that you become familiar with it because
> that would
> > appear to be necessary to bring your system back online.
> >
> > boot linux rescue
> > command line stuff...
> >
> > chroot /mnt/sysimage
> > yum update # you really need to update
> > yum update # you will probably need to update again because
> > # the first update will probably just add updates.newkey
> > grub-install /dev/sda
> > ----
> > > 3) when I backed out of the RESCUE and rebooted into one
> of the
> > > Fedora versions (not XEN), it came up with the main screen
> but no
> > > applications, not icons and the title bar at the bootom
> and 2 items
> > > which siad (UNKNOWN). Clicking on these resulted in
> nothing
> > > happening.
> > ----
> > I'm not sure what your intentions are with Xen but it's not
> going to
> > work right for Fedora 9...the release notes do make note of
> that.
> > ----
> > > 4) I then attempted to do a reload of Fedora 9 (update an
> existing
> > > release). This results in just the word GRUB appearing in
> the
> > > upper left of an otherwise blank screen. Nothing happens
> after this.
> > ----
> > try above instructions...should help
> > ----
> > > It this juncture, I am very concerned. I have photos and
> scanned
> > > documents on the drive and want to pull them off before I
> screw things
> > > up more.
> > ----
> > sounds as if they might be on one of the Xen domains but how
> would I
> > know that.
> >
> > It might be best to install the Fedora 10 test at this point
> just to get
> > Xen working again...I am just not aware how well it works
> and what is
> > broken.
> >
> > Craig
> >
15 years, 7 months
configure mount parameters in hotplug
by L
Hi
I often mount USB mannually via line from /etc/fstab
/dev/sdb1 /mnt/USBG vfat noauto,rw,users,shortname=mixed 0 0
is there a way to configure the parameters into hotplug? and let hotplug
handle usb mount. I mainly interesated in get "shortname=mixed" in place.
thanks
Y
15 years, 7 months
Jet Flash filesystem is forced as readonly
by Per Anton Rønning
System log messages:
*** snip ***
Oct 27 11:36:13 localhost kernel: usb 1-2: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Oct 27 11:36:13 localhost kernel: usb 1-2: Product: Mass Storage Device
Oct 27 11:36:13 localhost kernel: usb 1-2: Manufacturer: JetFlash
Oct 27 11:36:13 localhost kernel: usb 1-2: SerialNumber: TCC95547
Oct 27 11:36:18 localhost kernel: scsi 9:0:0:0: Direct-Access
JetFlash TS4GJF185 8.07 PQ: 0 ANSI: 2
Oct 27 11:36:18 localhost kernel: sd 9:0:0:0: [sdb] 7987198 512-byte
hardware sectors (4089 MB)
Oct 27 11:36:18 localhost kernel: sd 9:0:0:0: [sdb] Write Protect is off
Oct 27 11:36:18 localhost kernel: sd 9:0:0:0: [sdb] Assuming drive
cache: write through
Oct 27 11:36:18 localhost kernel: sd 9:0:0:0: [sdb] 7987198 512-byte
hardware sectors (4089 MB)
Oct 27 11:36:18 localhost kernel: sd 9:0:0:0: [sdb] Write Protect is off
Oct 27 11:36:18 localhost kernel: sd 9:0:0:0: [sdb] Assuming drive
cache: write through
Oct 27 11:36:18 localhost kernel: sdb: sdb1
Oct 27 11:36:18 localhost kernel: sd 9:0:0:0: [sdb] Attached SCSI
removable disk
Oct 27 11:36:18 localhost kernel: sd 9:0:0:0: Attached scsi generic sg2
type 0
Oct 27 11:36:19 localhost hald: mounted /dev/sdb1 on behalf of uid 500
Oct 27 11:36:19 localhost gnome-keyring-daemon[2713]: adding removable
location: volume_uuid_7A22_FF86 at /media/disk
Oct 27 11:36:30 localhost kernel: FAT: Filesystem panic (dev sdb1)
Oct 27 11:36:30 localhost kernel: fat_free_clusters: deleting FAT
entry beyond EOF
Oct 27 11:36:30 localhost kernel: File system has been set read-only
*** end snip ***
This has been the case for some days, I have been browsing the internet
to see if someone has a solution to it.
I don't know what has brought this about, but the problem is that that I
use the memory pen for backup purposes, and no write access is denied. I
cannot change this even if I'm root.
I guess it may have something to do with mount options, but I have not
yet found a way to check this i F9, or update it. This may be
elementary, but I fail to find a way to fix it.
BRGDS
PAR
15 years, 7 months
Slow performance in Linux after inserting Powerleap PL-P4/N proc adapter
by Dylan Semler
I recently upgraded an old Dell 8100 by putting in a Powerleap PL-P4/N
processor adapter (socket 423 to socket 478) and upgrading the
processor from a P4 1.33 MHz to a P4 2.6 GHz. Under Windows, there is
a noticeable performance increase. In Linux however, performance is
*horrible*--boot times are especially slow (~10 minutes). It looks
like the kernel recognizes the processor, but it's still reporting
~1.33 MHz.
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 2.60GHz
stepping : 9
cpu MHz : 1296.265
cache size : 512 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts
cid xtpr
bogomips : 2726.08
clflush size : 64
power management:
Can anyone who knows more about this suggest something else to
test/probe to help try and figure this out?
--
Dylan
Type faster. Use Dvorak:
http://dvzine.org
15 years, 7 months
samba insists on using virbr0
by sean darcy
Using f9 updated, with qemu installed, I can't get samba to work.
I think it's because samba keeps using virbr0, rather than eth0.
For instance on the machine with qemu:
nmblookup -d 2 '*'
added interface lo ip=::1 bcast=::1
netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
added interface lo ip=127.0.0.1 bcast=127.255.255.255 netmask=255.0.0.0
added interface eth0 ip=fe80::219:21ff:fe46:d9f9%eth0
bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=10.10.11.180 bcast=10.10.11.255
netmask=255.255.255.0
querying * on 127.255.255.255
Got a positive name query response from 127.0.0.1 ( 192.168.122.1 )
192.168.122.1 *<00>
While on another machine on the same 10.10.11. network:
nmblookup -d 2 '*'
added interface wlan0 ip=fe80::213:2ff:fe36:5cf3%wlan0
bcast=fe80::ffff:ffff:ffff:ffff%wlan0 netmask=ffff:ffff:ffff:ffff::
added interface wlan0 ip=10.10.11.27 bcast=10.10.11.255
netmask=255.255.255.0
querying * on 10.10.11.255
Got a positive name query response from 10.10.11.180 ( 10.10.11.180 )
Got a positive name query response from 10.10.11.252 ( 10.10.11.252 )
Got a positive name query response from 10.10.11.11 ( 10.10.11.11 )
Got a positive name query response from 10.10.11.22 ( 10.10.11.22 )
Got a positive name query response from 10.10.11.151 ( 10.10.11.151 )
Got a positive name query response from 10.10.11.150 ( 10.10.11.150 )
10.10.11.252 *<00>
10.10.11.180 *<00>
10.10.11.151 *<00>
10.10.11.150 *<00>
10.10.11.11 *<00>
10.10.11.22 *<00>
BTW 10.10.11.180 is the machine with qemu.
I'm not able to browse the .180 machine. Having gone through the samba
troubleshooting fault tree, I came on this problem.
Is there a way to keep qemu ( I use it with kvm)?
sean
15 years, 7 months