CD burning problem
by jery_wang
Hi All,
Here I am, back with another problem. I can't seem to burn CD's with FC3. I've tried the default Gnome burner, k3b and xcdroast, all with no luck. I was beginning to think that it was a hardware problem, but when I booted back to FC2, I was able to burn OK. Running cdrecord --scanbus gives me the following:
[dishawjp@eunix ~]$ cdrecord --scanbus
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus0:
0,0,0 0) 'ATAPI ' 'DVD-ROM 16X ' '582F' Removable CD-ROM
0,1,0 1) 'MSI ' 'CD-RW M$-8348 ' '120D' Removable CD-ROM
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
[dishawjp@eunix ~]$
Which would seem to indicate that cdrecord can find the device. But issuing the following command for cdrecord gives me the following output:
[dishawjp@eunix ~]$ cdrecord -v -eject speed=8 /media/cdrecorder /home/dishawjp/docs/
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'DVD-ROM 16X '
Revision : '582F'
Device seems to be: Generic mmc2 DVD-ROM.
Current: 0x0000
Profile: 0x0010
Profile: 0x0008
cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target.
[dishawjp@eunix ~]$ cdrecord -v -eject speed=8 /dev/cdrecorder /home/dishawjp/pics/other/
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c 1.83 04/05/20 Copyright 1997 J. Schilling').
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'ATAPI '
Identifikation : 'DVD-ROM 16X '
Revision : '582F'
Device seems to be: Generic mmc2 DVD-ROM.
Current: 0x0000
Profile: 0x0010
Profile: 0x0008
cdrecord: Sorry, no CD/DVD-Recorder or unsupported CD/DVD-Recorder found on this target.
I tried both /dev/cdrecorder and /media/cdrecorder and even /dev/hdb as the device in the command with the same results. It appears that the major problem is that it's not finding my cdburner, just my DVD drive. Both drives are ATAPI
Any thoughts on how to get this going? It's not too important for now, but I will want to be able to do backups sometime.
Oh, in case it helps, my fstab is below, it will probably wrap, but maybe give someone a clue anyway:
Code:
@eunix ~]$ more /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/hdd3 swap swap defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/hdb /media/cdrecorder auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/hda /media/cdrom auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
[dishawjp@eunix ~]$
As always, any help greatly appreciated.
Jim
--
This is an email sent via the webforum on http://fcp.homelinux.org
19 years
RE: OT: FC4 and Evolution
by Mark Haney
________________________________
From: fedora-list-bounces(a)redhat.com on behalf of Rahul Sundaram
Sent: Thu 3/3/2005 09:02
To: For users of Fedora Core releases
Subject: Re: OT: FC4 and Evolution
Hi
> >
> That's great. I'm not in a big hurry for it, but I do want to test it
> when it's available so I can prove to my company that it works.
do the testing now so developers can fix any bugs and get an update out properly
Where are the test packages?
--
Regards,
Rahul Sundaram
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
19 years
NEC Chipset cardbus USB2 card not working in high speed mode - any hints?
by Charles E. "Rick" Taylor, IV
System:
-------
Thinkpad X22
Fedora Core 3
Kernel 2.6.9-1.698_FC3
Problem:
--------
I've got a Dynex USB2 cardbus card (NEC chipset) that works at high
speed under Fedora Core 1. However, under Fedora Core 3, I can't get high
speed working - which means I can't use my newer CDRW drive, as it wants
to communicate at a minimum of 8X for burning CDRs.
Here's what happens:
dmesg on card insert -
PCI: Enabling device 0000:03:00.2 (0000 -> 0002)
ehci_hcd 0000:03:00.2: EHCI Host Controller
ehci_hcd 0000:03:00.2: irq 11, pci mem e8964000
ehci_hcd 0000:03:00.2: new USB bus registered, assigned bus number 4
ehci_hcd 0000:03:00.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 5 ports detected
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ohci_hcd 0000:03:00.0: OHCI Host Controller
PCI: Setting latency timer of device 0000:03:00.0 to 64
ohci_hcd 0000:03:00.0: irq 11, pci mem e886a000
ohci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 5
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 3 ports detected
PCI: Enabling device 0000:03:00.1 (0000 -> 0002)
ohci_hcd 0000:03:00.1: OHCI Host Controller
PCI: Setting latency timer of device 0000:03:00.1 to 64
ohci_hcd 0000:03:00.1: irq 11, pci mem e8a3a000
ohci_hcd 0000:03:00.1: new USB bus registered, assigned bus number 6
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
(Looks normal so far, I think...)
Now, plugging in the CD burner:
dmesg
ehci_hcd 0000:03:00.2: fatal error
ehci_hcd 0000:03:00.2: HC died; cleaning up
ohci_hcd 0000:03:00.1: wakeup
usb 6-1: new full speed USB device using address 2
usb 6-1: not running at top speed; connect to a high speed hub
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: IOMEGA Model: CDDVD482416E23-C Rev: 0037
Type: CD-ROM ANSI SCSI revision: 02
USB Mass Storage device found at 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
sr0: scsi3-mmc drive: 24x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
At this point, I can "use" the drive, but only at low speed - meaning I
can't burn anything but CDRW discs (which the drive will burn at 4X).
This drive and card combo works under Fedora Core 1 and will burn at full
speed.
Any hints?
--
--------------------------------------------------------------------
* Charles Taylor <tomalek(a)mindspring.com>
* Chemistry teacher, Linux enthusiast!
--------------------------------------------------------------------
* Web: http://home.mindspring.com/~charletiv/
--------------------------------------------------------------------
19 years
synaptics / alps touchpad
by Jonathan Berry
Hi all,
Does the latest FC3 kernel (770_FC3) have the necessary patches to
work with a synaptics touchpad? That is, does anyone have synaptics
working with the stock FC3 kernel (without re-compiling or anything
like that)?
A seperate question, does anyone know when the 2.6.11 kernel in
testing will be released? I've heard reports that at least vanilla
2.6.11 kernels have the necessary patches to get synaptics working.
My laptop (Compaq R3000Z) has a synaptics touchpad, but a bug in the
BIOS prevents it from being properly recognized. If psmouse is built
as a module (and not built in as in the default config) I can get it
working with "rmmod psmouse && modprobe psmouse" but it only works as
a normal mouse (no special synaptics functions). With a default
kernel, I can also get it to work by rubbing the touchpad enough :).
Both operations seem to reset something in the touchpad that then
allow it to be recognized. There is a BIOS upgrade available which
fixes this, but I am reluctant to apply it since almost everything
works. I have been trying to see if I could get it to work as a
synaptics touchpad without the BIOS upgrade (it's a long shot, but
worth a try), so I'm trying to figure out what all I need to do to get
it working.
One last question. Does anyone know if there is a way to get FC3 to
try to redect the mouse? Such a command would be much more
convienient than rubbing the pad until it works :).
Thanks,
Jonathan
19 years
Up2date on FC3 64bit
by Doug Coats
I just purchased a new computer with the AMD 64bit processor. I installed
FC3 on it yesterday using the 64bit version. When I went to use up2date I
noticed both 32bit and 64bit files for upgrades. Many of the 64bit files
would not install, complaining about conflicts with the 32bit versions that
were already installed. The 32bit versions would not install either. Now
that is when I select only all 32bit or all 64bit files.
What am I supposed to do. Do I need to have both of them installed? Is
this simply a result of not having some of these programs in 64bit at the
time of the release so that they were installed as 32bit versions and now
they are available as 64bit? Do I need to uninstall the 32bit version and
then install the 64bit version? Why in the world is this so complicated?
Would apt or yum treat this differently?
Thanks for your input.
Doug
19 years
Yum 2.2 w/ HTTP proxy fails w/ error "Cannot find a valid baseurl for repo:"
by Mike Fleetwood
Hi,
Recently "yum check-update" and "yum update" has started producing the
error "Cannot find a valid baseurl for repo: ...". Googling suggests
that other occurrences have been caused by network connectivity errors
or miss configured yum repository locations. I am convinced that in my
case it is yum 2.2's inability to successfully download files through a
HTTP proxy that is the problem. To work around the problem I
reinstalled yum 2.1 and upgrade using "yum --exclude=yum update".
Has anybody else had the same experience?
Can anybody suggest how to debug the code? Running "yum -d 9 ..."
doesn't add anything useful.
I have 2 FC3 installations which I update manually using "yum update"
regularly. Both have to use a HTTP proxy (different ones) to access
the Internet and both have the same problem.
HTTP proxy setting:
[root@bridge ~]# env | grep HTTP
HTTP_PROXY=http://rockover:8080/
Here is yum 2.1 working:
[root@bridge ~]# rpm -q yum
yum-2.1.12-0.fc3
[root@bridge ~]# yum update
Setting up Update Process
Setting up Repo: base
repomd.xml 100% |=========================| 1.1 kB 00:00
Setting up Repo: updates-released
repomd.xml 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
base : ################################################## 2622/2622
updates-re: ################################################## 742/742
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package yum.noarch 0:2.2.0-0.fc3 set to be updated
--> Running transaction check
Dependencies Resolved
Transaction Listing:
Update: yum.noarch 0:2.2.0-0.fc3
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Updating: yum 100 % done 1/2
Completing update for yum - 2/2
Updated: yum.noarch 0:2.2.0-0.fc3
Complete!
And here is yum 2.2 failing:
[root@bridge ~]# rpm -q yum
yum-2.2.0-0.fc3
[root@bridge ~]# yum update
Setting up Update Process
Setting up Repos
base 100% |=========================| 1.1 kB 00:00
Cannot find a valid baseurl for repo: updates-released
Thanks for your attention,
Mike
--
__ __ _ _ ___ ____ _ ___ ___ _ ___ ___ _
| \/ (_| | _ / _ \ | ___| | / _ \/ _ \| |_ _ _ _/ \/ \ _| |
| |\/| | | |/ | ___| | _| | |_| __| ___| __| \/ \/| O | O / _ |
|_| |_|_|_|\_\\___| |_| |____\___|\___||____\_/^\_/\___/\___/\___|
19 years
Boot from ICH6R Intel Software SATA Raid?
by Keith G. Robertson-Turner
Hi all,
Well I'm back after a long absence, mainly work related, but also due to
a hardware upgrade that has effectively left me Linux-less ... specifically:
Gigabyte GA-8ANXP-D mobo
2 x WD Raptor 74GB RAID0 (Boot + OS)
2 x Maxtor 400GB RAID0 (Data + Scratch)
All running off an Intel 82801FR SATA Raid Controller (ICH6R)
2 x Plextor 712SA SATA DVD+-RW
Both running off a Silicon Image 3114 SATA Raid Controller
Currently I have WinXP occupying half of the first raid volume, and I
wish to dual boot with FC3 (or FC4 later).
All my attempts at installing a multitude of different Linux distros on
this setup have failed (can't find disks), however FC3 seems to have
come the closest to succeeding.
From research, this is what I need AFAICT:
libata (ata_piix)
ataraid (iswraid)
dmraid
Working from memory, and IIRC, the first two are present and loaded
correctly during setup.
However, anaconda does not seem to be running dmraid to activate the
raid volume, and indeed when I jump to the console to run dmraid
manually, it is not available (not part of the stage2.img).
Another issue is the DVD drives. I haven't actually got around to
installing the Maxtor drives yet (still awaiting delivery) and so the
DVD drives are currently attached to the ICH6R. This works fine for
Windows, but all the Linux distros I've tried so far puke at stage2
because of (to paraphrase) "I can't find the disc I booted from" type
errors. Currently I'm circumventing the problem with a USB drive.
So, my questions:
1) ... Has anyone actually succeeded in setting up a similar configuration?
2) ... How can I get access to dmraid during setup?
3) ... Will this actually work, given access to dmraid, or are the
drivers (ata_piix, iswraid) still not fully functional?
4) ... Will FC4 be prepped and ready for this type of install?
5) ... Are there any "Live" distros that include dmraid (Knoppix doesn't
- AFAICT)?
7) ... What kernel parameters do I need to pass, to enable the SATA DVD
drives to work properly, or is it the case that this doesn't work yet?
6) ... Any other suggestions?
I don't want to get sidetracked by the alternatives (3ware, PATA,
raidtools, mdadm, etc.), I am fully aware of them. I just want to
concentrate on getting this configuration to work, regardless of whether
or not it is "doing things the hard way". It has to be done sooner or
later, for the sake of Fedora, and GNU/Linux in general.
If I can get a running system up, then I'll be quite happy to act as a
beta tester, write a FAQ/tutorial, and even help with packaging (if
necessary).
I haven't had a working Linux system for some time, and I'm anxious to
get back to working on Tripwire, amongst other things.
If it comes down to it, I can always resurrect the dinosaur from cold
storage, in order to get a working Linux system, but space is limited;
it was beginning to pack up (SCSI controller dying); it's dog slow, pig
ugly, noisy; huge; and the very reason I bought a new system in the
first place. I'd really rather just ditch it.
TIA,
-
Regards,
K.
19 years
A few quick newbie questions...
by jery_wang
Using a 200GIG WD harddrive and VIA EPIA M10000 mini-ITX motherboard with 512 megs of RAM....
#1 - I do the install, no problems as far as I can tell, then it has to do a reboot. It gets to where it is then asking for a "username" in the middle of the screen. I don't have a username. At some point during the install it forces me to put in an admin name or something, but that user/pass doesn't work. Is there a way during the install to tell it "hey, no freaking user/pass on this computer"?
#2 - Want to do a dual boot between XP and Linux. Do I partition the harddrive first, then install XP, then install Linux?
This is all new ground to me (Linux and dual booting). While I'm not a computer dunce, these two "issues" has me stumped. Please use small words and pretty pictures.
Many thanks!
Pencilneck blah blah blah
--
This is an email sent via the webforum on http://fcp.homelinux.org
19 years
Does FC3 issue halt to Athlon XP cpus when idle?
by Steve Bergman
I know that at one time the kernel did not issue a halt instruction to
athlon cpus due to some sort of bug that caused some athlons not to wake
up again.
Is this still true on, e.g., an Athlon XP 2100+ with the current FC3 kernel?
Thanks,
Steve
19 years
