Problems updating - YUM - kmod-VirtualBox...
# yum --skip-broken update ... gnome-keyring-sharp i686 1.0.1-0.5.133722svn.fc12 fedora 20 k kmod-nvidia-173xx-2.6.31.6-166.fc12.i686.PAE i686 173.14.22-1.fc12.4 rpmfusion-nonfree-updates 1.8 M Removendo para as dependências: kmod-VirtualBox-OSE-2.6.31.5-127.fc12.i686.PAE i686 3.0.10-1.fc12.4 installed 393 k kmod-nvidia-173xx-2.6.31.5-127.fc12.i686.PAE i686 173.14.22-1.fc12 installed 7.5 M Resumo da transação Instalar 4 Pacote(s) Atualizar 53 Pacote(s) Remover4 Pacote(s) Reinstalar 0 Pacote(s) Desatualizar 0 Pacote(s) Tamanho total: 106 M Correto? [s/N]:s Baixando pacotes: Executando o rpm_check_debug Erro com o rpm_check_debug vs depsolve: kernel-uname-r = 2.6.30.9-96.fc11.i686.PAE is needed by (installed) kmod-VirtualBox-OSE-2.6.30.9-96.fc11.i686.PAE-3.0.10-1.fc11.3.i686 kernel-uname-r = 2.6.30.8-64.fc11.i686.PAE is needed by (installed) kmod-VirtualBox-OSE-2.6.30.8-64.fc11.i686.PAE-3.0.8-1.fc11.i686 kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE is needed by (installed) kmod-VirtualBox-OSE-2.6.30.9-90.fc11.i686.PAE-3.0.10-1.fc11.i686 Concluído! -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
cups/guttenprint color schemes wrong for Epson Stylus CX3500 and other printers
Maybe off topic but, how to correct color schemes for Epson Printers? Default is horrible (excess of red, wrong gamma/brightness, etc). I guess someone must have dealt with that. Best regards CdAB signature.asc Description: OpenPGP digital signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Problems with eclipse KDE (Fedora 11)
!SESSION 2009-09-10 17:53:20.054 --- eclipse.buildId=M20090211-1700 java.version=1.6.0_0 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=pt_BR Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.osgi 4 0 2009-09-10 18:29:07.679 !MESSAGE !STACK 0 java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:131) at java.util.zip.ZipFile.init(ZipFile.java:148) at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAction.java:251) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.basicOpen(ZipBundleFile.java:81) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getZipFile(ZipBundleFile.java:94) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.checkedOpen(ZipBundleFile.java:67) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getEntry(ZipBundleFile.java:239) at org.eclipse.osgi.baseadaptor.BaseData.getEntry(BaseData.java:97) at org.eclipse.osgi.internal.baseadaptor.AdaptorUtil.loadManifestFrom(AdaptorUtil.java:192) at org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.getGeneratedManifest(EclipseStorageHook.java:371) at org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.createCachedManifest(EclipseStorageHook.java:367) at org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.getManifest(EclipseStorageHook.java:472) at org.eclipse.osgi.internal.baseadaptor.BaseStorage.loadManifest(BaseStorage.java:297) at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:82) at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:938) at org.eclipse.osgi.framework.internal.core.Framework$1.run(Framework.java:824) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:905) at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:819) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:215) at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.installBundles(ConfigApplier.java:213) at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:67) at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:124) at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:138) at org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.applyConfiguration(ProfileSynchronizer.java:391) at org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.synchronize(ProfileSynchronizer.java:105) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.synchronize(Activator.java:402) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:161) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321) -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Troubleshooting pendrive ext2fs
Discovered the problem: The pendrive is a counterfeit. VID=1043 PDI=8012 does not correspond to Kingston (iChips ???). Somehow it is capable of storing 16GBytes of data (I recorded a file and then unconnected the pendrive and reconnected it and verified the content via cat $FILE | md5sum /tmp/check.md5... Device readily sent to police, so they'll ask the store how it appeared there. Sorry for the inconvenience. CdAB Em 18-08-2009 19:18, Casimiro de Almeida Barreto escreveu: Hello, I've trouble creating an ext2/ext3/ext4 file system in a 64GBytes pendrive. The device appears at /proc/bus/usb/devices as: T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1043 ProdID=8012 Rev= 1.00 S: Manufacturer=Generic S: Product=Flash Disk C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms It's partioned as: Disk /dev/sdd: 67.1 GB, 67108864512 bytes 64 heads, 32 sectors/track, 64000 cylinders Units = cilindros of 2048 * 512 = 1048576 bytes Disk identifier: 0x4a26a3ed Dispositivo Boot Start End Blocks Id System /dev/sdd1 1 6400065535984 83 Linux And raw partition table data is: Disk /dev/sdd: 64 heads, 32 sectors, 64000 cylinders Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID 1 00 1 10 63 32 1023 32 131071968 83 2 00 0 00 0 00 0 0 00 3 00 0 00 0 00 0 0 00 4 00 0 00 0 00 0 0 00 Disk was formatted with the following command: [r...@localhost ~]# mkfs.ext2 -L kingston -M /media/kingston -O large_file,extent /dev/sdd1 mke2fs 1.41.4 (27-Jan-2009) Filesystem label=kingston OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 4096000 inodes, 16383996 blocks 819199 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 500 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424 Writing inode tables: done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 33 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. And then checked: # fsck -f -v /dev/sdd1 Resulting in: [r...@localhost ~]# fsck -v -f /dev/sdd1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: +(32768--34306) +(65536--66049) +(98304--99842) +(131072--131585) +(163840--165378) +(196608--197121) +(229376--230914) +(262144--262657) +(294912--296450) +(327680--328193) +(360448--360961) +(393216--393729) +(425984--426497) +(458752--459265) +(491520--492033) +(524288--524801) +(557056--557569) +(589824--590337) +(622592--623105) +(655360--655873) +(688128--688641) +(720896--721409) +(753664--754177) +(786432--786945) +(819200--820738) +(851968--852481) +(884736--886274) +(917504--918017) +(950272--950785) +(983040--983553) +(1015808--1016321) +(1048576--1049089) +(1081344--1081857) +(1114112--1114625) +(1146880--1147393) +(1179648--1180161) +(1212416--1212929) +(1245184--1245697) +(1277952--1278465) +(1310720--1311233) +(1343488--1344001) +(1376256--1376769) +(1409024--1409537) +(1441792--1442305) +(1474560--1475073) +(1507328--1507841) +(1540096--1540609) +(1572864--1573377) +(1605632--1607170) +(1638400--1638913) +(1671168--1671681) +(1703936--1704449) +(1736704--1737217) +(1769472--1769985) +(1802240--1802753) +(1835008--1835521) +(1867776--1868289) +(1900544--1901057) +(1933312--1933825) +(1966080--1966593) +(1998848--1999361) +(2031616--2032129) +(2064384--2064897) +(2097152--2097665) +(2129920--2130433) +(2162688--2163201) +(2195456--2195969) +(2228224--2228737) +(2260992--2261505) +(2293760--2294273) +(2326528--2327041) +(2359296--2359809) +(2392064--2392577) +(2424832--2425345) +(2457600--2458113) +(2490368--2490881) +(2523136--2523649) +(2555904--2556417) +(2588672--2589185) +(2621440--2621953) +(2654208--2655746) +(2686976--2687489) +(2719744--2720257) +(2752512--2753025) +(2785280--2785793) +(2818048--2818561) +(2850816--2851329) +(2883584--2884097) +(2916352--2916865) +(2949120--2949633) +(2981888--2982401) +(3014656--3015169) +(3047424--3047937) +(3080192--3080705) +(3112960--3113473) +(3145728--3146241) +(3178496--3179009) +(3211264--3211777) +(3244032--3244545) +(3276800--3277313
Re: Trouble formatting flash disk
Em 18-08-2009 15:13, Eric Sandeen escreveu:
(...)
Could you take this to the linux-ext4 list? It'd be the more
appropriate place for the discussion.
It'd be good to know the details of the errors you see, too.
Thanks,
-Eric
Best regards,
CdAB
Yes, if I know where I can subscribe this list.
Besides, when I format the device as Fat (F16 or F32) it works properly
only if I disable multibyte char encoding for directories (by doing:
LANG=pt_BR.ISO8859-1 and LC_ALL=pt_BR.ISO8859-1. That should be OK but
system should convert file names to proper encoding.
When I format as ext-2 and create a large file, after writing the file I
can't write anything else. If I unmount the fs, I am able to mount again
and even read the file, but I'm not able to write anything else. But if
I fsck it, I'm warned that system was uncleanly unmounted. Several
errors appear (I'll repeat the procedure and log the errors).
Basically what I do is:
# FILE_NAME_PREFIX=`date +%y%m%d%H%M`
# tar cjf - /home /opt /usr/local | gpg -c -a -z0 --cipher-algo=aes256
-o /media/kingston/${FILE_NAME_PREFIX}.asc
# md5sum ${FILE_NAME_PREFIX}.asc ${FILE_NAME_PREFIX}.md5 (this won't
execute - cannot write to device).
But if I do:
# df -m /dev/sdd1
it is still plenty of free memory (64GBytes minus about 10GBytes)...
One thing I was thinking is that this flash memory stores data in blocks
of 512 bytes and minimum ext2 blocking is 1024 bytes...
signature.asc
Description: OpenPGP digital signature
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Troubleshooting pendrive ext2fs
Hello, I've trouble creating an ext2/ext3/ext4 file system in a 64GBytes pendrive. The device appears at /proc/bus/usb/devices as: T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 4 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1043 ProdID=8012 Rev= 1.00 S: Manufacturer=Generic S: Product=Flash Disk C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms It's partioned as: Disk /dev/sdd: 67.1 GB, 67108864512 bytes 64 heads, 32 sectors/track, 64000 cylinders Units = cilindros of 2048 * 512 = 1048576 bytes Disk identifier: 0x4a26a3ed Dispositivo Boot Start End Blocks Id System /dev/sdd1 1 6400065535984 83 Linux And raw partition table data is: Disk /dev/sdd: 64 heads, 32 sectors, 64000 cylinders Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID 1 00 1 10 63 32 1023 32 131071968 83 2 00 0 00 0 00 0 0 00 3 00 0 00 0 00 0 0 00 4 00 0 00 0 00 0 0 00 Disk was formatted with the following command: [r...@localhost ~]# mkfs.ext2 -L kingston -M /media/kingston -O large_file,extent /dev/sdd1 mke2fs 1.41.4 (27-Jan-2009) Filesystem label=kingston OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 4096000 inodes, 16383996 blocks 819199 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 500 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424 Writing inode tables: done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 33 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. And then checked: # fsck -f -v /dev/sdd1 Resulting in: [r...@localhost ~]# fsck -v -f /dev/sdd1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: +(32768--34306) +(65536--66049) +(98304--99842) +(131072--131585) +(163840--165378) +(196608--197121) +(229376--230914) +(262144--262657) +(294912--296450) +(327680--328193) +(360448--360961) +(393216--393729) +(425984--426497) +(458752--459265) +(491520--492033) +(524288--524801) +(557056--557569) +(589824--590337) +(622592--623105) +(655360--655873) +(688128--688641) +(720896--721409) +(753664--754177) +(786432--786945) +(819200--820738) +(851968--852481) +(884736--886274) +(917504--918017) +(950272--950785) +(983040--983553) +(1015808--1016321) +(1048576--1049089) +(1081344--1081857) +(1114112--1114625) +(1146880--1147393) +(1179648--1180161) +(1212416--1212929) +(1245184--1245697) +(1277952--1278465) +(1310720--1311233) +(1343488--1344001) +(1376256--1376769) +(1409024--1409537) +(1441792--1442305) +(1474560--1475073) +(1507328--1507841) +(1540096--1540609) +(1572864--1573377) +(1605632--1607170) +(1638400--1638913) +(1671168--1671681) +(1703936--1704449) +(1736704--1737217) +(1769472--1769985) +(1802240--1802753) +(1835008--1835521) +(1867776--1868289) +(1900544--1901057) +(1933312--1933825) +(1966080--1966593) +(1998848--1999361) +(2031616--2032129) +(2064384--2064897) +(2097152--2097665) +(2129920--2130433) +(2162688--2163201) +(2195456--2195969) +(2228224--2228737) +(2260992--2261505) +(2293760--2294273) +(2326528--2327041) +(2359296--2359809) +(2392064--2392577) +(2424832--2425345) +(2457600--2458113) +(2490368--2490881) +(2523136--2523649) +(2555904--2556417) +(2588672--2589185) +(2621440--2621953) +(2654208--2655746) +(2686976--2687489) +(2719744--2720257) +(2752512--2753025) +(2785280--2785793) +(2818048--2818561) +(2850816--2851329) +(2883584--2884097) +(2916352--2916865) +(2949120--2949633) +(2981888--2982401) +(3014656--3015169) +(3047424--3047937) +(3080192--3080705) +(3112960--3113473) +(3145728--3146241) +(3178496--3179009) +(3211264--3211777) +(3244032--3244545) +(3276800--3277313) +(3309568--3310081) +(3342336--3342849) +(3375104--3375617) +(3407872--3408385) +(3440640--3441153) +(3473408--3473921) +(3506176--3506689) +(3538944--3539457) +(3571712--3572225) +(3604480--3604993) +(3637248--3637761) +(3670016--3670529) +(3702784--3703297) +(3735552--3736065) +(3768320--3768833) +(3801088--3801601) +(3833856--3834369) +(3866624--3867137) +(3899392--3899905) +(3932160--3932673) +(3964928--3965441) +(3997696--3998209) +(4030464--4030977) +(4063232--4063745) +(4096000--4097538) +(4128768--4129281) +(4161536--4162049) +(4194304--4194817) +(4227072--4227585)
Re: PANIC on RPMDB... can't even get version numbers for installed packages...
I did the same procedure as I'd do with M$... 1) Reboot the system 2) ftp download.fedora.redhat.com 3) download glibc* 4) rpm -Uvh --force --nodeps glibc-comm* (yeah... after a reboot rpm works) 5) rm glibc-comm* rpm -Uvh --force --nodeps glibc* And everything comes back to life... Paul Nasrat escreveu: On Tue, 2006-03-07 at 21:24 -0300, Casimiro de Almeida Barreto wrote: After update done 00:23 08/Mar/2006 the following happened (so I can't even get version for packages...): [r...@terra ~]# yum update rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv-open: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30977) error: cannot open Packages database in /var/lib/rpm rpm issue, what steps did you take up to that point? If you experienced any failures what were they? Please back up your rpmdb (/var/lib/rpm) and create a bugzilla, preferably with the history above. Paul
