Bind
by linuxserver
Hello, I am trying to use the GUI DNS configuration tool and it says it
updates the named.conf file, but when I look at the named.conf in etc it
is not updated. Any one know what I am missing
Thanks
Richard Tracy
20 years, 3 months
USB Devices not working
by Khürt Williams
I can not get my USB devices to work under Fedora Core 1. I am trying
to get my Sony DSC-S70 digital camer to be recognised by the system to
no avail. Other USB devices fail to be recognised as well. My USB
drive is not recognised.
Here is the output from syslog when the Sony DSC-S70 is connected.
Jan 31 10:45:22 cypher kernel: hub.c: new USB device 00:07.2-1, assigned
address 4
Jan 31 10:45:25 cypher usb.agent[5456]: missing kernel or user mode
driver usb-storage
Jan 31 10:45:25 cypher kernel: SCSI device sda: 253696 512-byte hdwr
sectors (130 MB)
Jan 31 10:45:25 cypher kernel: sda: Write Protect is off
Jan 31 10:45:25 cypher kernel: sda: sda1
Jan 31 10:45:25 cypher kernel: inserting floppy driver for
2.4.22-1.2149.nptl
Jan 31 10:45:28 cypher kernel: floppy0: no floppy controllers found
Jan 31 10:45:28 cypher insmod:
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/block/floppy.o:
init_module: No such device
Jan 31 10:45:28 cypher insmod: Hint: insmod errors can be caused by
incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output
from dmesg
Jan 31 10:45:28 cypher insmod:
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/block/floppy.o: insmod
block-major-2 failed
Jan 31 10:45:30 cypher devlabel: devlabel service started/restarted
and when the camera is disconnected.
Jan 31 10:54:05 cypher kernel: usb.c: USB disconnect on device 00:07.2-1
address 4
Jan 31 10:54:05 cypher kernel: sda: Unit Not Ready, sense:
Jan 31 10:54:05 cypher kernel: Info fld=0xa00 (nonstd), Current 00:00:
sense key Not Ready
Jan 31 10:54:05 cypher kernel: sda : READ CAPACITY failed.
Jan 31 10:54:05 cypher kernel: sda : status = 1, message = 00, host = 0,
driver = 08
Jan 31 10:54:05 cypher kernel: Info fld=0xa00 (nonstd), Current sd00:00:
sense key Not Ready
Jan 31 10:54:05 cypher kernel: sda : block size assumed to be 512 bytes,
disk size 1GB.
Jan 31 10:54:05 cypher kernel: sda: test WP failed, assume Write Enabled
Jan 31 10:54:05 cypher kernel: sda: I/O error: dev 08:00, sector 0
Jan 31 10:54:05 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:54:05 cypher kernel: unable to read partition table
Jan 31 10:54:05 cypher kernel: sda: Unit Not Ready, sense:
Jan 31 10:54:05 cypher kernel: Info fld=0xa00 (nonstd), Current 00:00:
sense key Not Ready
Jan 31 10:54:05 cypher kernel: sda : READ CAPACITY failed.
Jan 31 10:54:05 cypher kernel: sda : status = 1, message = 00, host = 0,
driver = 08
Jan 31 10:54:05 cypher kernel: Info fld=0xa00 (nonstd), Current sd00:00:
sense key Not Ready
Jan 31 10:54:05 cypher kernel: sda : block size assumed to be 512 bytes,
disk size 1GB.
Jan 31 10:54:05 cypher kernel: sda: test WP failed, assume Write Enabled
Jan 31 10:54:05 cypher kernel: sda: I/O error: dev 08:00, sector 0
Jan 31 10:54:05 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:54:05 cypher kernel: unable to read partition table
Jan 31 10:54:05 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:54:05 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:54:06 cypher kernel: sda: Unit Not Ready, sense:
Jan 31 10:54:06 cypher kernel: Info fld=0xa00 (nonstd), Current 00:00:
sense key Not Ready
Jan 31 10:54:06 cypher kernel: sda : READ CAPACITY failed.
Jan 31 10:54:06 cypher kernel: sda : status = 1, message = 00, host = 0,
driver = 08
Jan 31 10:54:06 cypher kernel: Info fld=0xa00 (nonstd), Current sd00:00:
sense key Not Ready
Jan 31 10:54:06 cypher kernel: sda : block size assumed to be 512 bytes,
disk size 1GB.
Jan 31 10:54:06 cypher kernel: sda: test WP failed, assume Write Enabled
Jan 31 10:54:06 cypher kernel: sda: I/O error: dev 08:00, sector 0
Jan 31 10:54:06 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:54:06 cypher kernel: unable to read partition table
Jan 31 10:54:06 cypher devlabel: devlabel service started/restarted
Jan 31 10:54:07 cypher kernel: sda: Unit Not Ready, sense:
Jan 31 10:54:07 cypher kernel: Info fld=0xa00 (nonstd), Current 00:00:
sense key Not Ready
Jan 31 10:54:07 cypher kernel: sda : READ CAPACITY failed.
Jan 31 10:54:07 cypher kernel: sda : status = 1, message = 00, host = 0,
driver = 08
Jan 31 10:54:07 cypher kernel: Info fld=0xa00 (nonstd), Current sd00:00:
sense key Not Ready
Jan 31 10:54:07 cypher kernel: sda : block size assumed to be 512 bytes,
disk size 1GB.
Jan 31 10:54:07 cypher kernel: sda: test WP failed, assume Write Enabled
Jan 31 10:54:07 cypher kernel: sda: I/O error: dev 08:00, sector 0
Jan 31 10:54:07 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:54:07 cypher kernel: unable to read partition table
Jan 31 10:54:07 cypher kernel: inserting floppy driver for
2.4.22-1.2149.nptl
Jan 31 10:54:10 cypher kernel: floppy0: no floppy controllers found
Jan 31 10:54:10 cypher insmod:
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/block/floppy.o:
init_module: No such device
Jan 31 10:54:10 cypher insmod: Hint: insmod errors can be caused by
incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output
from dmesg
Jan 31 10:54:10 cypher insmod:
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/block/floppy.o: insmod
block-major-2 failed
USB drive
Jan 31 10:55:19 cypher kernel: hub.c: new USB device 00:07.2-2, assigned
address 5
Jan 31 10:55:19 cypher kernel: scsi1 : SCSI emulation for USB Mass
Storage devices
Jan 31 10:55:19 cypher kernel: usb-uhci.c: interrupt, status 3, frame# 1900
Jan 31 10:55:19 cypher kernel: Vendor: HITACHI_ Model:
DK23DA-20 Rev: 00J2
Jan 31 10:55:19 cypher kernel: Type:
Direct-Access ANSI SCSI revision: 02
Jan 31 10:55:19 cypher kernel: Attached scsi disk sdb at scsi1, channel
0, id 0, lun 0
Jan 31 10:55:19 cypher kernel: SCSI device sdb: 39070081 512-byte hdwr
sectors (20004 MB)
Jan 31 10:55:19 cypher kernel: sdb: sdb1 sdb2
Jan 31 10:55:22 cypher usb.agent[6891]: missing kernel or user mode
driver usb-storage
Jan 31 10:55:22 cypher kernel: sda: Unit Not Ready, sense:
Jan 31 10:55:22 cypher kernel: Info fld=0xa00 (nonstd), Current 00:00:
sense key Not Ready
Jan 31 10:55:22 cypher kernel: sda : READ CAPACITY failed.
Jan 31 10:55:22 cypher kernel: sda : status = 1, message = 00, host = 0,
driver = 08
Jan 31 10:55:22 cypher kernel: Info fld=0xa00 (nonstd), Current sd00:00:
sense key Not Ready
Jan 31 10:55:22 cypher kernel: sda : block size assumed to be 512 bytes,
disk size 1GB.
Jan 31 10:55:22 cypher kernel: sda: test WP failed, assume Write Enabled
Jan 31 10:55:22 cypher kernel: sda: I/O error: dev 08:00, sector 0
Jan 31 10:55:22 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:55:22 cypher kernel: unable to read partition table
Jan 31 10:55:22 cypher kernel: inserting floppy driver for
2.4.22-1.2149.nptl
Jan 31 10:55:25 cypher kernel: floppy0: no floppy controllers found
Jan 31 10:55:25 cypher insmod:
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/block/floppy.o:
init_module: No such device
Jan 31 10:55:25 cypher insmod: Hint: insmod errors can be caused by
incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output
from dmesg
Jan 31 10:55:25 cypher insmod:
/lib/modules/2.4.22-1.2149.nptl/kernel/drivers/block/floppy.o: insmod
block-major-2 failed
Jan 31 10:55:26 cypher kernel: sda: Unit Not Ready, sense:
Jan 31 10:55:26 cypher kernel: Info fld=0xa00 (nonstd), Current 00:00:
sense key Not Ready
Jan 31 10:55:26 cypher kernel: sda : READ CAPACITY failed.
Jan 31 10:55:26 cypher kernel: sda : status = 1, message = 00, host = 0,
driver = 08
Jan 31 10:55:26 cypher kernel: Info fld=0xa00 (nonstd), Current sd00:00:
sense key Not Ready
Jan 31 10:55:26 cypher kernel: sda : block size assumed to be 512 bytes,
disk size 1GB.
Jan 31 10:55:26 cypher kernel: sda: test WP failed, assume Write Enabled
Jan 31 10:55:26 cypher kernel: sda: I/O error: dev 08:00, sector 0
Jan 31 10:55:26 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:55:26 cypher kernel: unable to read partition table
Jan 31 10:55:26 cypher kernel: usb-uhci.c: interrupt, status 3, frame# 391
Jan 31 10:55:27 cypher kernel: sda: Unit Not Ready, sense:
Jan 31 10:55:27 cypher kernel: Info fld=0xa00 (nonstd), Current 00:00:
sense key Not Ready
Jan 31 10:55:27 cypher kernel: sda : READ CAPACITY failed.
Jan 31 10:55:27 cypher kernel: sda : status = 1, message = 00, host = 0,
driver = 08
Jan 31 10:55:27 cypher kernel: Info fld=0xa00 (nonstd), Current sd00:00:
sense key Not Ready
Jan 31 10:55:27 cypher kernel: sda : block size assumed to be 512 bytes,
disk size 1GB.
Jan 31 10:55:27 cypher kernel: sda: test WP failed, assume Write Enabled
Jan 31 10:55:27 cypher kernel: sda: I/O error: dev 08:00, sector 0
Jan 31 10:55:27 cypher kernel: I/O error: dev 08:00, sector 0
Jan 31 10:55:27 cypher kernel: unable to read partition table
Jan 31 10:55:28 cypher devlabel: devlabel service started/restarted
20 years, 3 months
Re: Random System Crashes
by Mike Chepesky
>Mike Chepesky wrote:
>
> > Hello,
> >
> > I'm new to Linux, and I've just downloaded and installed the Fedora
> > Core. Installation and configuration went smoothly, and I can work in
> > the GNOME environment normally. However, it seems that every 1/2 hour
> > or so, even in the middle of working on something, I get a crash. The
> > computer is still on (i.e. I can still eject the CD-ROM drive, the
> > power light is on), but my monitor turns off (as if it's gone into
> > power-saving mode) and no keystrokes or mouse clicks will revive it
> > (not even Ctrl-Alt-Del).
> >
> > I have the latest Linux kernel (as provided by the automatic updater),
> > and everything else works just fine. Any suggestions??
>
>Can you post the output of uname -r ?
>
>I had a problem with the 2.4.22-1.2140.nptl kernel with my Athlon XP and
>nforce2 chipset. I looked in /var/log/messages and did not see any
>errors, the monitor did not show a sync signal (like it's in suspend),
>and the system was locked up hard (no response from Ctrl-Alt-F1,
>Ctrl-Alt-Backspace, Ctrl-Alt-Delete), and I could not ping the machine.
>This happened several times within an hour and a half. Seems like it
>happened when I was browsing or downloading from the network. I went
>back to the -2135 kernel, and my machine has been more stable, but
>recently has locked up while running a screensaver. I just upgraded to
>the 2149 kernel, and disabled a lot of the screensavers, so I will wait
>and see what happens. It looks like I was seeing the same problem you
>were seeing when I was on the 2140 athlon kernel.
>
>Are you using alsa drivers, or the OSS drivers that come with FC1?
I'm using the 2.4.22-1.2149.nptl kernel (output from uname -r). Your problem
is in fact identical to mine. I've been using it for the past couple of
hours, and nothing strange has happened, so we will see. Perhaps disabling
screensavers is a good idea...
I'm using the drivers that came with FC1, btw.
Mike
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fj...
20 years, 3 months
Postfix is totally fsck'd...
by Lorenzo Prince
I am guessing this has taken place over the last couple of days. I first saw
that I was getting fewer messages than usual. This was not a problem, because I
just thought that fewer people were sending messages. Well, the problem got
worse. I now stopped receiving messages through fetchmail which I know should
come every day without fail. Then it started taking a long time to receive my
cron messages. I didn't receive a message yesterday that I should have gotten in
the afternoon, and naturally, I thought it was the server that sent it, (maybe
something to do with this latest virus slowing down the server. So I started
sending test messages through the local server. I sent about 5 tests and lost
all of them. I then checked the maillog
grep postfix /var/log/maillog |less
and according to the log, someone has found my postfix and is trying to use it as
a relay to try to send hundreds or possibly thousands of messages to what looks
like an alphabetical list of AOL users. The problem is that Postfix seems to
actually be relaying these messages and then picking up the bounces from AOL and
relaying them back to the sender who has an empty from address. I don't
understand, however, how or why this is happening, as I have postfix configured
to only accept local relays, and the log is saying the messages are coming from a
remote sender. When I do the relay test at mail-abuse.org, it tells me that my
system appears to reject relay attempts. I ended up having to switch my MTA to
Sendmail, because Postfix is so backed up to the point that my system takes
almost 5 minutes to boot, and messages delivered from local users to local users
aren't even getting through anymore. What can I do to solve the Postfix problem?
What can I do to stop this relaying even though Postfix is configured not to
relay from remote connections at all? I started using postfix when I heard that
sendmail had a history of insecurity. Is this better now? Should I just start
using sendmail instead of Postfix?
Thanks for any help
PRINCE
20 years, 3 months
Disk Layout/Partitioning Practices
by Ron Herardian
Hello,
When installing everything and allowing for future updates and packages I am using the following disk layout:
Mount Point Size
/boot 100MB
/ 500MB
/usr 4GB
/var 2GB
swap 2x physical RAM, e.g., 1GB
/home TBD, e.g., 1GB per user
/opt TBD/catchall [3rd party servers will be installed here]
I want to have enough space on required partitions but not waste space on infrequently modified filesystems where add-on packages will probably not go.
I'd like to get an idea what other folks are doing in terms of disk layouts. What are the best practices?
Ron
--
Global System Services Corporation (GSS)
650 Castro Street, Suite 120, Number 268, Mountain View, CA 94041, USA
+1 (650) 965-8669 phone, +1 (650) 965-8679 fax, +1 (650) 283-5241 mobile
rherardi(a)gssnet.com, http://www.gssnet.com
"The best way to predict your future is to create it." - Stephen Covey
20 years, 3 months
[OT] setting up Bochs to run WinXP
by Lorenzo Prince
Hi. I just saw the posting about Bochs and thought I'd give it a try. I
downloaded and installed the RPM but I can't seem to get it to find WinXP, which
is installed on /dev/hda3. Does anyone know how to get this setup so that it
will boot /dev/hda3 and run WinXP for me so I don't have to reboot the system?
Thanks,
PRINCE
20 years, 3 months
rhythmbox error
by Joe Klemmer
Just for kicks I wanted to try out Rhythmbox. Unfortunately whenever I
try to play anything I get a pop-up error message saying, "Failed to
create mad element; check your installation". OC, it doesn't tell me
what needs to be checked in my installation. Anyone have any ideas?
--
Akebono vs Godzilla! Coming soon to a theater near you.
20 years, 3 months
hello
by Dave Jones
The message cannot be represented in 7-bit ASCII encoding and has been sent as a binary attachment.
20 years, 3 months
Greetings from new member
by Manuel Portillo
Hi everyone,
I just wanted to introduce myself and ask if any of you speak Spanish.
My name is Manuel Portillo and I am the Director of an organization that
work to help Latinos utilize alternative information technology, both in
English and in Spanish.
I am a new Linux user though; and I would appreciate any help you can
offer me to learn how to install new software (packages) in my Fedora
installation.
Thank you so much for your help. You can email me directly at
Sinfronteras(a)comcast.net or please respond through this list.
20 years, 3 months