Errror with acroread
by Paul Smith
Dear All
I am getting the following:
$ /usr/bin/acroread
/usr/local/Adobe/Acrobat7.0/Reader/intellinux/bin/acroread: error
while loading shared libraries:
/usr/local/Adobe/Acrobat7.0/Reader/intellinux/lib/libJP2K.so: cannot
restore segment prot after reloc: Permission denied
$
Any ideas?
Paul
18 years, 1 month
mime type editor?
by Riku Seppälä
Hello,
Sorry if this is asked before but I can't find answer. I want to use
amarok for .m3u files as default on every situation, how do I accomplish
that? The easy answer please :) Doubleclicking .m3u file on konqueror
opens amarok now but, firefox still says rhythmbox is default
application for m3u.
Is there any kind on mime-type editor?
Riku
18 years, 1 month
Where is usb-serial.h?
by Mariano López Reta
Hi,
I have just installed FC5 (and I'm really happy with it).
I need to compile a new Ipaq module, but I cannot find usb-serial.h.
Can someone tell me where to find it?
--
Mariano López Reta
Tortuguitas, Buenos Aires, Argentina
Registered Linux user #412032
Count yourself at http://counter.li.org/
18 years, 1 month
Problem with kernels after 2.6.14-1.1656_FC4
by Markus Lindholm
Hi
I have file and db server with FC4 on, plus all the updates except for the
kernel. I have tried all the kernels after 2.6.14-1.1656_FC4 up to
2.6.16-1.2069_FC4, but none of them will boot on this piece of hardware. I
filed a bug report
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180279 some time back.
I didn't think much more about, content with a working 2.6.14-1.1656_FC4 and
confident that the bug would eventually be fixed.
But now that 2.6.16-1.2069_FC4 came out and it still wouldn't boot I started
wondering if there is something more to it. The issue seems to be that none
of the latest kernels can find the root device. Is there some steps that I
would have to take to make the later kernels work? Or try to raise the issue
on some other list or forum?
Any advice would be appreciated.
Markus
It's a ASUS A8N-E motherboard, the root device is on a sata disk behind a
nVidia CK804 controller.
18 years, 1 month
compiling pam_mount for FC5
by Roman Maeder
I couldn't find any rpms for pam_mount-0.12.2 for FC5 and tried to compile
it myself. I didn't get very far, as the "make" output at the end shows.
The file in question is /usr/include/linux/loop.h, which belongs to
glibc-kernheaders-3.0-5.2, so this seems to be up-to-date. Any ideas?
Roman
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./../include -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -DG_DISABLE_DEPRECATED -D_LARGEFILE_SOURCE=1
-D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -D_REENTRANT -Wall -Waggregate-return
-Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wshadow
-Wstrict-prototypes -Winline -pipe -g -O2 -MT mount.lo -MD -MP
-MF .deps/mount.Tpo -c mount.c -fPIC -DPIC -o .libs/mount.o
In file included from mount.c:54:
/usr/include/linux/loop.h:31:2: error: #error "Wrong dev_t in loop.h"
mount.c:75: warning: 'struct loop_info64' declared inside parameter list
mount.c:75: warning: its scope is only this definition or declaration, which
is probably not what you want
mount.c: In function 'already_mounted':
mount.c:184: error: storage size of 'loopdev' isn't known
mount.c:184: warning: unused variable 'loopdev'
mount.c: At top level:
mount.c:944: warning: 'struct loop_info64' declared inside parameter list
mount.c:945: error: conflicting types for 'loop_bk'
mount.c:75: error: previous declaration of 'loop_bk' was here
mount.c:951:6: error: #error
-------------------------------------------------------------------
mount.c:952:6: error: #error Your userspace kernel headers
(/usr/include/linux/) are out of date
mount.c:953:6: error: #error This is NOT a pam-mount bug, but one of your
distribution.
mount.c:954:6: error: #error
-------------------------------------------------------------------
mount.c: In function 'loop_bk':
mount.c:956: error: 'LOOP_GET_STATUS64' undeclared (first use in this
function)
mount.c:956: error: (Each undeclared identifier is reported only once
mount.c:956: error: for each function it appears in.)
mount.c:961: error: dereferencing pointer to incomplete type
make[2]: *** [mount.lo] Error 1
make[2]: Leaving directory `/usr/local/src/pam_mount-0.12.2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/pam_mount-0.12.2'
make: *** [all] Error 2
18 years, 1 month
fc5 installation problem
by harry
Installed FC5 64 from DVD onto AMD Proteus. Installation smooth and
fast. Congratulations on successful installation at end. but on reboot I
was presented with dark blue screen with faint vertical lines. Tried
another monitor but results the same. Anyone give me a clue, Thanks
Harry.
18 years, 1 month
Software Raid 5 (FC5)
by Mark Yarbrough
During install time I was made 10 raid partitions across 5 500GB SATA
drives. The final partition /dev/md8 wouldn't partition format and anaconda
would crash telling me that the partition couldn't be formatted, and
required a reboot. After the 3rd attempt I figured that the partitions are
all the same size so I will just format it when I am in the running
operating system.
I took a look at my partitions using fdisk (take note that all 5 are the
same save the drive number it self) <see paste at bottom>
The partitions are there. /dev/sdX11 is the partition that I am trying to
use. I tried to make the raid partitions to no avail. I looked at
/etc/mdadm.conf and saw that /dev/md8 is there. From my limited
understanding I am under the assumption that the raid is made and all I need
to do is format it. I try to format it and I get the error reporting the
device size to be zero. The partitions are clearly not zero. I am now
stuck. What should I do next?
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sda2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sda3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sda4 41433 60801 155581492+ 5 Extended
/dev/sda5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sda6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sda7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sda8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sda9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sda10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sda11 49846 60796 87963876 fd Linux raid
autodetect
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sdb2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sdb3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sdb4 41433 60801 155581492+ 5 Extended
/dev/sdb5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sdb6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sdb7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sdb8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sdb9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sdb10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sdb11 49846 60796 87963876 fd Linux raid
autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sdc2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sdc3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sdc4 41433 60801 155581492+ 5 Extended
/dev/sdc5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sdc6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sdc7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sdc8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sdc9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sdc10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sdc11 49846 60796 87963876 fd Linux raid
autodetect
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sdd2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sdd3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sdd4 41433 60801 155581492+ 5 Extended
/dev/sdd5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sdd6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sdd7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sdd8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sdd9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sdd10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sdd11 49846 60796 87963876 fd Linux raid
autodetect
Disk /dev/sde: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 * 1 28683 230396166 fd Linux raid
autodetect
/dev/sde2 28684 38882 81923467+ fd Linux raid
autodetect
/dev/sde3 38883 41432 20482875 fd Linux raid
autodetect
/dev/sde4 41433 60801 155581492+ 5 Extended
/dev/sde5 41433 43344 15358108+ fd Linux raid
autodetect
/dev/sde6 43345 45256 15358108+ fd Linux raid
autodetect
/dev/sde7 45257 46658 11261533+ fd Linux raid
autodetect
/dev/sde8 46659 47933 10241406 fd Linux raid
autodetect
/dev/sde9 47934 49208 10241406 fd Linux raid
autodetect
/dev/sde10 49209 49845 5116671 fd Linux raid
autodetect
/dev/sde11 49846 60796 87963876 fd Linux raid
autodetect
# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
ARRAY /dev/md8 level=raid5 num-devices=5
uuid=fc489661:c7e54273:f9a60c82:fb747b29
ARRAY /dev/md6 level=raid5 num-devices=5
uuid=eac1a77f:5278bfcd:4ae75c92:7ecde09b
ARRAY /dev/md3 level=raid5 num-devices=5
uuid=1e94cb1d:f84f5a3b:1e0ff333:408d5bb7
ARRAY /dev/md5 level=raid5 num-devices=5
uuid=f5bfaf8b:8a591cf0:d73b7d31:4c07a93b
ARRAY /dev/md1 level=raid5 num-devices=5
uuid=0bf1a445:323d5326:5a7a92fc:1c346c33
ARRAY /dev/md9 level=raid5 num-devices=5
uuid=f5811eae:cfb21182:41881dcf:739f1bad
ARRAY /dev/md4 level=raid5 num-devices=5
uuid=348c95b9:df7feee6:41713309:a9324496
ARRAY /dev/md0 level=raid5 num-devices=5
uuid=bf7ef721:318d6d4e:b626b349:5f9c7e15
ARRAY /dev/md7 level=raid5 num-devices=5
uuid=a196ca52:c6700579:ff5a0379:9d6c9084
ARRAY /dev/md2 level=raid5 num-devices=5
uuid=5e0d3003:e65e36d0:25158ed3:f81e126d
18 years, 1 month
Re: My Epson scanner now works - without USB 2
by Mike C
On Tuesday 28 Mar 2006 18:29, Jeff Vian wrote:
>I know that the front panel connectors switch from USB 2.0 to USB 1.1 as a
>BIOS setting. I've copied a 100MB file from a USB flash drive and the
>difference is evident.
>Also it's the same USB socket with the same cable that works in one mode and
>not the other.
>Dave F
I don;t know if this is related but I recently upgraded from fc4 to fc5 (clean
install) and found that I had some problems with my Epson CX3200 scanner/printer
connected via a usb port. The printer functions were working fine in fc5.
sane-find-scanner worked, and then scanimage -L gave:
device `epson:libusb:001:002' is a Epson CC-570L flatbed scanner
OK so it did fid the scanner OK.... but running the GIMP and trying to "acquire
-> Xsane:device...." did nothing - just gave no response at all, but running
kooka (all under KDE) found the scanner just fine !!! I was then using kooka to
do scans, but GIMP refused to co-operate.
Subsequently out of desperation I deleted the existing .sane directory in the
user area and tried again - it then worked just fine !
Mike
18 years, 1 month
FC5 RAID 1 - booting off either drive
by Laurence Vanek
Greetings -
To my surprise, fresh install of FC5 with RAID 1 configured at install
time went without a hitch. I have /dev/md0 defined on /boot
partitions. It boots fine with this setup.
I had my FC4 system setup this exact way except I found that I had to
manually install grub on one of the disks to permit booting off either
one if the other is down.
Does anyone know of a way to check for the presence of grub on each
drive (obviously its on hda since it boots presently) to see if this
needs to be done for FC5 also without powering down each drive in turn &
attempting to boot?
18 years, 1 month
