Problems mounting digital camera on FC3
by Keven Ring
I posted this to fedora-list a couple of days ago, but have not had any
responses. Given past successes with getting problems solved there, I
am going to assume that either noone else has this problem, or no one
has any ideas what is different, and how to get it to work.
That being said, I have a Nikon D70 digital camera that I am trying to
mount on a freshly installed FC3. When I plug the camera in, and turn
it on, I get the following messages in /var/log/messages (editted for
brevity):
Nov 9 14:31:14 localhost kernel: usb 2-1: new full speed USB device
using address 8
Nov 9 14:31:14 localhost kernel: scsi3 : SCSI emulation for USB Mass
Storage devices
Nov 9 14:31:14 localhost kernel: Vendor: NIKON Model:
D70 Rev: 1.01
Nov 9 14:31:14 localhost kernel: Type:
Direct-Access ANSI SCSI revision: 02
Nov 9 14:31:18 localhost kernel: sda: Spinning up disk......ready
Nov 9 14:31:18 localhost kernel: SCSI device sda: 3999745 512-byte hdwr
sectors (2048 MB)
Nov 9 14:31:18 localhost kernel: sda: Write Protect is off
Nov 9 14:31:18 localhost kernel: sda: assuming drive cache: write through
Nov 9 14:31:18 localhost kernel: sda:end_request: I/O error, dev sda,
sector 3999744
Nov 9 14:31:18 localhost kernel: Buffer I/O error on device sda,
logical block 3999744
Nov 9 14:31:18 localhost kernel: end_request: I/O error, dev sda,
sector 3999744
Nov 9 14:31:18 localhost kernel: Buffer I/O error on device sda,
logical block 3999744
Nov 9 14:31:18 localhost kernel: sda1
Nov 9 14:31:18 localhost kernel: Attached scsi removable disk sda at
scsi3, channel 0, id 0, lun 0
Nov 9 14:31:18 localhost scsi.agent[20673]: disk at
/devices/pci0000:00/0000:00:1f.4/usb2/2-1/2-1:1.0/host3/3:0:0:0
Nov 9 14:31:19 localhost kernel: end_request: I/O error, dev sda,
sector 63
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 0
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 1
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 2
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 3
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 4
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 5
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 6
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 7
Nov 9 14:31:19 localhost kernel: end_request: I/O error, dev sda,
sector 575
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 512
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 513
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 514
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 515
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 516
Nov 9 14:31:19 localhost kernel: Buffer I/O error on device sda1,
logical block 517
....
This continues for some while.
If I were just looking at this, I might assume that the CF card
(actually, a microdrive) was improperly formatted, or that there were
other problems reading the card.
However, using the same exact computer, but booting into a stock FC1, I
have no problems (although I have to mount /dev/sda1 myself).
Note, I have not been able to successfully mount the camera in either
FC2 or FC3, suggesting a problem with the 2.6 kernel (could be a red
herring, but...).
Any recommendations on how to proceed or test would be greatly
appreciated. I can provide additional information, as requested (eg,
FC1 /var/log/messages, lsmod, etc).
Tonight, I am going to try and build a stock 2.6 kernel, and see if that
helps, hinders, or continues with the same results.
TIA
--
Keven Ring | "Oh no, Not Again..."
The MITRE Corporation | Bowl of Petunias -
7515 Colshire Drive | The Hitchhikers Guide to the Galaxy
McLean VA 22102-7508 |
PH: (703)883-7026 |
19 years, 6 months
the media check problem
by Dennis Bjorklund
I've been doing some tests to see what works and what does not in
the context of the media check problem. A lot of us have to turn of
dma in order for the media check to work.
This is my current thoughts that I would love to get some comments
about from someone who knows the kernel.
1) It's the read ahead that causes the problem. If one use
hdparm and set the read ahead to 0 on the device, then I have
no problem to verify a cd using dd.
2) When I mount the cd then I can check the md5sum of every file and it is
correct no matter what read ahead is set to.
When a filesystem is mounted we know the exact size of the track. Does
the filesystem layer pass on that information to the block device so
it knows it should not read past the end (even when doing read
ahead)?
If it doesn't, then why doesn't it read past the end when the
fs is mounted?
3) Given that it does work as I guess in point 2, then shouldn't the
read ahead on a cdrom device be 0 until we know the max size to
prevent it from reading past the end? Before we know the end then
it's dangerous to read ahead and we should just read what is asked
for.
4) When DMA is turned off then we read block by block and when we hit
and error the previous blocks are already read in and valid. With DMA
it looks like we tell the drive to read lots of blocks, and then when
it breaks we signal back an error directly and the valid blocks in
the beginning of the DMA request are also lost.
5) Does the read ahead buy us much extra speed when installing? Could it
be set to 0 by anaconda for everyone in order to help those of us
where it is a problem.
6) Is read ahead the problem for everyone or is it just something
that makes it work on my hardware.
My next step should be to read the kernel source to verify the above. So
far it's just guesses based on my intuition of how this is implemented. I
want to present it here first and see what people have to say about it
before I spend days (or weeks) trying to understand the block and ide code
in the kernel.
Maybe someone like Alan Cox (but not limited to him!) will look at this
and say it's stupid, and then I don't need to read the code :-)
--
/Dennis Björklund
19 years, 6 months
Stateless Linux
by Jason Powers
Been lucky enough to have a little time to try this out. We've been
trying to get LTSP running here since about March, and it's not really
flying beyond basic use.
So when I saw this project I grabbed the files and set up a box, the
configuration is not only easy compared to LTSP, but I learned a lot
about that process by doing this (LTSP also requires TFTP, LDAP, DHCPD,
etc). I have the most recent build as of now.
I'm still working on getting my first snapshot to export, but it's a lot
easier to check the work when you install phpldapadmin on the same
system: you can see each item as it's created, and check to make sure
it's all correct. Merely running the tests doesn't always catch typos
and such. phpla is pretty easy to install, I untarred it into
/var/www/html and renamed it phpla so I could just browse it. I've been
using a lot of LAMP tools lately, sometimes just seeing the same info a
different way helps a lot.
Anyway I'm here to mention an oddity in the documentation for Stateless.
On this page:
http://fedora.redhat.com/docs/stateless/sn-snapshot-setup.html
it says to use the following command:
stateless-snapshooter --new --protosystem DemoSystem
since it's just a toy I'm actually using the name DemoSystem. However,
the --new and --protosystem had to be replaced with -n -p before it
would work. The error tells you very plainly that those are the
available switches. for some reason --list works just fine, as does -l.
I haven't made any changes to the server, it's as plain as you can get
it fresh off the download mirror. Anyway broken flags are just a minor
thing but I couldn't find an email to send this to so the devel list
seemed as safe a place as any.
On to the next step...
jason
19 years, 6 months
Stateless Linux Question
by Christopher Hotchkiss
Hey guys,
I have been setting up a stateless linux install recently, and I have
a question regarding the caching clients. On step six of the install
guide (http://fedora.redhat.com/docs/stateless/sn-caching-clients.html),
it states "Locate a bootstrap CD for the client OS you wish to install
and mount it at /mnt/cdrom." Would this be a Fedora Core 3 CD1? Or is
there another cd I should be using? Is it possible to generate a
caching install from a snapshot I've made in the previous steps?
--
Christopher Hotchkiss
(813)960-9273
http://www.post227.org
19 years, 6 months
Multicast DNS & the ".local" domain
by Felipe Alfaro Solana
Short question: Does Fedora Core 3 support multicast DNS name
resolution for the ".local" domain?
Long: I can resolv my Linux hostname from my Mac OS X computer, but my
Linux box can't resolve my Mac OS X hostname.
Looking at the network traffic, Mac OS X name queries for the ".local"
domain do send mDNS traffic to the multicast mDNS address. Linux
queries for the ".local" domain go against my ISP DNS server.
19 years, 6 months
Status of fedora.us "Extras" and apt?
by Alex Lancaster
I was wondering if anybody knows the status of the fedora.us repo.
The base os and updates seems to be up at:
http://download.fedora.us/fedora/fedora/3/i386/
but there are no extras package, not even a version of apt built to be
able to apt-get the base os and update packages from the repository.
Nary a mention on the fedora.us website or wiki, I don't even know
there is a plan to build extras packages via fedora.us, perhaps
migration to the new Redhat build system for extras that's been
suggested is imminent, is in the works.
I know it's only been 4 or 5 days since fc3 release, but I'm worried
that no information on fedora.us about when and if a rebuild is
planned might lead users to conclude that it has been abandoned,
especially given that other 3rd party repos: freshrpms, dag etc., and
even livna (which depends of fedora.us) are up and running.
Anyway, I filed a couple of bugs on bugzilla.fedora.us:
http://bugzilla.fedora.us/show_bug.cgi?id=2273 (for apt rebuild)
http://bugzilla.fedora.us/show_bug.cgi?id=2274 (for website update)
Cheers,
Alex
19 years, 6 months
Problem with compiling packages
by Amitabha Roy
Hello:
I have a rather run of the mill Fedora box running FC3 which for some reason
refuses to compile large projects. For example, lets say I check
out CVS emacs, run configure and make, it starts the compilation process,
runs for a while and then either the machine freezes (and I have to
restart the machine)
or it just reboots.
The same thing happens when I try to recompile kdemultimedia
according to the advice in
http://www.holovaty.com/linux/fedorafaq/kde_mp3.html
I do not know whether this a gcc leak or what it is.
There is no log of what exactly causes this as far as I can see.
Can someone please suggest ways I can debug this ?
Or some way to hunt down the culprit ?
Amitabha
19 years, 6 months
Proposing inclusion of a new package
by Andy Jeffries
Hi all,
I created a bug regarding trying to get my application distributed with
Fedora Core, but apparently that's not the way it gets done with Fedora
(it is with Gentoo).
The application is gPHPEdit and I've just released version 0.9.50. To
see what it's about go here:
http://www.gphpedit.org/features.phtml
And to see what's new in the latest version go here:
http://www.gphpedit.org/whats-new-0.9.50.phtml
Anyway, if someone fancies either going ahead and including it in the
distro or pointing me to the procedure for getting it included (or
telling me to get lost for whatever reason), feel free to let me know.
Cheers,
Andy
19 years, 6 months
root::0:0:root:/root:/bin/bash !?!
by Arnaud Abélard
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I just noticed that the default /etc/passwd file installed by the
package setup-2.5.33-1.noarch.rpm (on a FC2, i don't know about FC1 and
FC3 yet) contains the line root::0:0:root:/root:/bin/bash.
This means that root is a passwdless account but nevetheless useable,
with a valid shell. When installing the package in a chroot, for a
vserver, uml, or whatever this creates a very serious security hazard!
I know this is not normally a problem, because anaconda will force the
user to set a password. But the package isn't always installed by
anaconda during a normal installation from a media. In the case of a
manual relocated installation on the purpose to create a chroot
environment this is a real problem.
Arnaud Abélard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBk7mpu1PiD4+WtDcRAm4AAJ9TyawfST/xTQfGJvXLlra6mliuRACeN/Gd
X3jSXzbkn6v0hRq4IXzcNIs=
=5YYj
-----END PGP SIGNATURE-----
19 years, 6 months
problem with font
by Jason Kim
Hi all,
I've just downloaded FC3 and installed it.
Interestingly, my Xlib program doesn't work with FC3.
Instead I got the message, "Error: cannot find the font".
I'm using the"lucidasans-18" in my program.
I've read FC3 release notes, and found some changes in the font system.
But it is over my head.
What cause this problem and how can I fix it.
Jason
19 years, 6 months