Re: Camera panasonic-TZ18
by Patrick Dupre
Hello,
After a very long time I was able to mount it from /dev/sdb1 and copy
my files. Not very convenient!
Any idea? It work fine from another machine (fedora 18).
Regards.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 8 months
Re: Camera panasonic-TZ18
by Patrick Dupre
Thank,
Here it is
The camera says connexion to PC in progress, and it takes a very long time before it disappears.
In addition, if I try to add the camera manually from digikam, there is not model showing up.
It looks like that I need to install some drivers.
Aug 1 01:00:02 sophocle systemd-udevd[11100]: inotify_add_watch(7, /dev/sdb, 10) failed: No such file or directory
Aug 1 01:00:07 sophocle kernel: [11896.611096] usb 1-6: new high-speed USB device number 7 using ehci-pci
Aug 1 01:00:07 sophocle kernel: [11896.728118] usb 1-6: New USB device found, idVendor=04da, idProduct=2372
Aug 1 01:00:07 sophocle kernel: [11896.728127] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 1 01:00:07 sophocle kernel: [11896.728131] usb 1-6: Product: DMC-TZ18
Aug 1 01:00:07 sophocle kernel: [11896.728135] usb 1-6: Manufacturer: Panasonic
Aug 1 01:00:07 sophocle kernel: [11896.728138] usb 1-6: SerialNumber: 0000000000000000006F1302150801
Aug 1 01:00:07 sophocle kernel: [11896.728801] usb-storage 1-6:1.0: USB Mass Storage device detected
Aug 1 01:00:07 sophocle kernel: [11896.733248] usb-storage 1-6:1.0: Quirks match for vid 04da pid 2372: 90
Aug 1 01:00:07 sophocle kernel: [11896.735270] scsi5 : usb-storage 1-6:1.0
Aug 1 01:00:07 sophocle mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6"
Aug 1 01:00:07 sophocle mtp-probe: bus: 1, device: 7 was not an MTP device
Aug 1 01:00:08 sophocle kernel: [11897.738193] scsi 5:0:0:0: Direct-Access MATSHITA DMC-TZ18 0110 PQ: 0 ANSI: 2
Aug 1 01:00:08 sophocle kernel: [11897.738800] sd 5:0:0:0: Attached scsi generic sg2 type 0
Aug 1 01:00:08 sophocle kernel: [11897.740008] sd 5:0:0:0: [sdb] Adjusting the sector count from its reported value: 15523840
Aug 1 01:00:08 sophocle kernel: [11897.740054] sd 5:0:0:0: [sdb] 15523839 512-byte logical blocks: (7.94 GB/7.40 GiB)
Aug 1 01:00:08 sophocle kernel: [11897.741035] sd 5:0:0:0: [sdb] Write Protect is on
Aug 1 01:00:08 sophocle kernel: [11897.741890] sd 5:0:0:0: [sdb] No Caching mode page present
Aug 1 01:00:08 sophocle kernel: [11897.741898] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Aug 1 01:00:38 sophocle kernel: [11928.101092] usb 1-6: reset high-speed USB device number 7 using ehci-pci
Aug 1 01:01:09 sophocle kernel: [11959.109182] usb 1-6: reset high-speed USB device number 7 using ehci-pci
Aug 1 01:01:41 sophocle kernel: [11990.213151] usb 1-6: reset high-speed USB device number 7 using ehci-pci
Aug 1 01:02:11 sophocle kernel: [12021.189094] usb 1-6: reset high-speed USB device number 7 using ehci-pci
Aug 1 01:02:12 sophocle kernel: [12021.312222] sd 5:0:0:0: [sdb] Adjusting the sector count from its reported value: 15523840
Aug 1 01:02:12 sophocle kernel: [12021.313518] sd 5:0:0:0: [sdb] No Caching mode page present
Aug 1 01:02:12 sophocle kernel: [12021.313525] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Aug 1 01:02:42 sophocle kernel: [12052.165207] usb 1-6: reset high-speed USB device number 7 using ehci-pci
Aug 1 01:03:13 sophocle kernel: [12083.141074] usb 1-6: reset high-speed USB device number 7 using ehci-pci
Aug 1 01:03:44 sophocle kernel: [12114.117204] usb 1-6: reset high-speed USB device number 7 using ehci-pci
Aug 1 01:04:15 sophocle kernel: [12145.157208] usb 1-6: reset high-speed USB device number 7 using ehci-pci
> ----- Original Message -----
> From: Ed Greshko
> Sent: 08/01/13 01:02 AM
> To: Community support for Fedora users
> Subject: Re: Camera panasonic-TZ18
>
> On 08/01/13 06:55, Patrick Dupre wrote:
> > I connected my camera panasonic DMC-TZ18
> > Bus 001 Device 005: ID 04da:2372 Panasonic (Matsushita) Lumix Camera (Storage mode)
> >
> > but it does not seem to be seen by the computer.
> > no camera been by digicam or shotwell.
> > Do I need to install some drivers?
>
> Watch /var/log/messages as you plug it in. Sounds as if it may be to be accessed as a USB drive.
>
> --
> Getting tired of non-Fedora discussions and self-serving posts
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 8 months
howto do test update
by Neal Becker
I see emacs has been updated to 24.3. I'm pretty sure I don't want it. I have
built/installed 24.3 earlier, and found some problems. Specifically, tramp
doesn't seem to work (hangs), and I need it.
Any thoughts on how I might be able to do a yum update, and then backout if I
don't like it?
I know yum has history rollback - but that would depend on being able to find
the earlier 24.2 rpms. Which are probably gone. Which I find rather annoying.
10 years, 8 months
F19 Disc Chundering
by Jonathan Allen
All,
Having just installed F19 on a new mcahine, the disc keeps makeing 'reset'
noises and puts this in /var/log/messages:
Jul 30 18:58:38 brush kernel: [ 3538.326082] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jul 30 18:58:38 brush kernel: [ 3538.326098] sr 3:0:0:0: CDB:
Jul 30 18:58:38 brush kernel: [ 3538.326102] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
Jul 30 18:58:38 brush kernel: [ 3538.326123] ata4.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
Jul 30 18:58:38 brush kernel: [ 3538.326123] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jul 30 18:58:38 brush kernel: [ 3538.326129] ata4.00: status: { DRDY }
Jul 30 18:58:38 brush kernel: [ 3538.326139] ata4: hard resetting link
Jul 30 18:58:38 brush kernel: [ 3538.989992] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 30 18:58:38 brush kernel: [ 3539.007104] ata4.00: configured for PIO0
Jul 30 18:58:38 brush kernel: [ 3539.022994] ata4: EH complete
This happens about every 30 seconds. Any idea what is going on?
Jonathan
10 years, 8 months
The state of blu-ray burning in linux is terrible
by Richard Shaw
DISCLAIMER: Yes I'm whining, but hopefully someone who wants to user their
BD writer will find this useful...
Well I thought I would try to make my first blu-ray movie from some home
movies instead of down converting them to DVD like I have been... Only to
find out not only is it currently laborious process, it's actually
technically impossible for FOSS.
The laborious part is trying to get it into the right format (x264 with
very specific settings and separate audio file), but even if you manage
that part, there's no UDF 2.5 write support in linux. If you're lucky, you
BD player may not care.
No problem, I'll worry about that later, I'll just burn a backup of my
pictures that were getting to hard to backup on DVD's....
Put in disc... Check!
Detected in Brasero... Check!
"copy" into new data project... Check!
BURN!
ejects immediately with no helpful error message...
... skip some time spent googling only to get really mad about the whole
cdrkit vs. cdrtools debacle...
... skip spending time getting cdrtools 3.01 to build ...
I'm still working on getting the kinks out of that... conflicts with
several cdrkit packages (genisoimage, wodim, icedax)
Ok! Last resort, do it the PITA way...
$ dd if=/dev/zero of=/bdimage.udf bs=2048 count=12219392
$ mkudffs bdimage.udf
# sudo mount -t udf -o loop bdimage /mnt/disc
currently copying files into the image file... HOPEFULLY brasero will at
least burn the image...
Richard
10 years, 8 months
BTRFS using LZO compression over NFS.
by Gary Artim
question: why does my compression rate change based on the *clients*
kernel (i think)?
situation: testing using btrfs with lzo, when I run with equal kernels
on the server and client I get the same compression (on a 11GB:1.2GB).
When I run on a client with a 2.6.x kernel I get (11GB:6GB), same
file, all nfs4. btw, I dont get the same speed, 11GB file, server to
server, 16secs on btrfs/lzo; 11GB file, client to server 2mins on
btrfs/lzo over NFS.
has anyone tried or can explain?
server: 3.9.9-201.fc18.x86_64
client (in question): 2.6.31.6-2.caos
client (get same compression): 3.9.9-201.fc18.x86_64 or 3.9.9-302.fc19.x86_64
thanks for any enlightening thoughts!
10 years, 8 months
Re: VirtualBox wont run -
by Reindl Harald
Am 31.07.2013 19:54, schrieb Steven Stern:
>>> Reindl: This depends on which repo VirtualBox is installed from.
>>> If installed from the repo on VirtualBox.org, then it *does*
>>> install a file in /etc/init.d and one manages it through calls to
>>> "service", which appropriately run the script with the right
>>> parameters, including "setup"
>>
>> what do you not realize in the fact that /sbin/service is a wrapper
>> to systemctl?
>>
> Yes, I do. But the syntax is a whole lot easier for "service"
the syntax is *exactly* the same, only action and service-name are reverse
translate this to "service" (hint: it is impossible)
systemctl restart dbmail-imapd.service dbmail-lmtpd.service dbmail-pop3d.service dbmail-timsieved.service
and if the services you restart have dependencies to each other (After=/Before=)
it will happen in the correct order while you have to type "service name restart"
in the right order and multiple times
10 years, 8 months
RE: VirtualBox wont run -
by Alan Gagne
> Am 31.07.2013 16:45, schrieb Bob Goodwin ~ Zuni:
> >/ I awoke around 03:00 and tried whatever new suggestions had come in at that time as well as rebooting, all to no
> />/ avail.
> />/
> />/ However, systemctl setup vboxdrv.service still does not run:
> />/
> />/ [root at box10 <https://admin.fedoraproject.org/mailman/listinfo/users> bobg]# /sbin/service vboxdrv setup
> />/ Redirecting to /bin/systemctl setup vboxdrv.service
> />/ Unknown operation 'setup'.
> />/
> />/ Thanks to all for the help. That help is invaluable to many of us and is what keeps people coming back to Fedora!
> /
> /etc/init.d/vboxdrv setup
>
> you *must not* use systemctl or service which is a wrapper for systemctl
> the times where a service can have whatever actions are gone with systemd
Not entirely true with regards to using service. This is on my F19 box.
[root@dw-agagne ~]# uname -r
3.10.3-300.fc19.x86_64
[dw-agagne ~]# service vboxdrv
Usage: /etc/init.d/vboxdrv
{start|stop|stop_vms|restart|force-reload|status|setup}
[dw-agagne ~]# service vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modulesError! There are no
instances of module: vboxhost
4.2.16 located in the DKMS tree.
Error! There are no instances of module: vboxhost
4.2.16 located in the DKMS tree.
[ OK ]
Trying to register the VirtualBox kernel modules using DKMS[ OK ]
Starting VirtualBox kernel modules [ OK ]
[dw-agagne ~]# service vboxdrv status
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are
loaded.
Where Bob has a problem with vboxdrv is that it does not exist.
It appears he has gotten virtualbox from the rpmfusion repo.
vboxdrv comes with what is packaged from the virtualbox.org repo.
[dw-agagne ~]# yum repolist
Loaded plugins: langpacks, refresh-packagekit
repo id repo
name status
adobe-linux-i386 Adobe Systems
Incorporated 17
adobe-linux-x86_64 Adobe Systems
Incorporated 2
fedora/19/x86_64 Fedora 19 -
x86_64 36,253
google-chrome google-chrome 3
rpmfusion-free/19/x86_64 RPM Fusion for Fedora 19 -
Free 462
rpmfusion-free-updates/19/x86_64 RPM Fusion for Fedora 19 - Free
- Updates 96
rpmfusion-nonfree/19/x86_64 RPM Fusion for Fedora 19 -
Nonfree 219
rpmfusion-nonfree-updates/19/x86_64 RPM Fusion for Fedora 19 -
Nonfree - Updates 90
updates/19/x86_64 Fedora 19 - x86_64 -
Updates 9,730
virtualbox/19/x86_64
[dw-agagne ~]# yum provides "*/vboxdrv"
VirtualBox-4.2-4.2.8_83876_fedora18-1.x86_64 : Oracle VM VirtualBox
Repo : virtualbox
Matched from:
Filename : /etc/rc.d/init.d/vboxdrv
Filename : /usr/share/virtualbox/src/vboxhost/vboxdrv
Alan
10 years, 8 months
Disable PCI devices via systemd
by Raman Gupta
I have an Intel motherboard sound card, and twoHDMI audio sound cards
provided by each of my ATI video cards:
# lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation Patsburg High Definition Audio
Controller (rev 05)
01:00.1 Audio device: ATI Technologies Inc Device aaa0
02:00.1 Audio device: ATI Technologies Inc Device aaa0
I don't have anything plugged into the ATI HDMI ports so I want to
disable those devices, as I get annoying error messages in KDE at
startup time and periodically in /var/log/messages. For example:
[ 13.018758] ALSA sound/pci/hda/hda_eld.c:334 HDMI: ELD buf size is
0, force 128
[ 13.018772] ALSA sound/pci/hda/hda_eld.c:351 HDMI: invalid ELD data
byte 0
I cannot blacklist the module, because the "snd_hda_intel" module that
drives the Intel sound card on my motherboardalso recognizes the ATI
cards, according to lspci-v.
The following solution does workperfectly:
# echo 1 > /sys/devices/pci0000:00/0000:00:02.0/0000:01:00.1/remove
# echo 1 > /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.1/remove
In the old days, the above two lines would go into rc.local. What is
the systemd way to not create those devices? Or is there an alternate
approach to turn off the HDMI sound cards on the ATI cards?
Regards,
Raman
10 years, 8 months
yum expected to work in rescue mode on install DVD?
by Richard Shaw
After a failed fedup upgrade from F18 to 19 I was left with a broken
system...
No problem, I figured, I would just boot a F19 install DVD and go into
rescue mode and fix things using "yum --installroot=..."
After booting into rescue mode I tried running yum, and the program seems
to be there, but it complained about not being able to import the yummain
module.
Is yum expected to work in rescue mode? I would think so...
I ended up using rpm directly and hunting down the dependencies one at a
time until I had a working yum in the chroot.
Thanks,
Richard
10 years, 8 months
