November 2004 - Packet Writing - openSUSE Mailing Lists

Linux-2.6.0
by Richard A Downing FBCS 30 Dec '04

30 Dec '04

I was about to update my kernel to the new stable 2.6.0, but notice Jens has added some changes since test11. Is there any reason to suppost the test11 patch wouldn't work? I guess this is just a way of saying 'Can we have a 2.6.0 patch please Peter?' -- Richard A Downing FBCS http://www.freewebs.com/109bean/ Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms.

5 6

Confirm eject problem
by James Blanford 24 Nov '04

24 Nov '04

Howdy folks, I have the same problem with the eject button failing after using the burner in non-packet-writing mode. I prefer to respond with 'cdrecord dev=/dev/hdc -eject' as I find cdrecord's warnings about device names more entertaining than the kernel's warnings about the eject program using deprecated SCSI io controls. Also, Peter might want to make one final patch for 2.6.9-ac5 and beyond, which seems to be the only place to find stability these days. It is a trivial fix. Thanks for all the work. Congratulations on being in the mainstream. - Jim

1 0

Mt Rainier
by Chris Clayton 15 Nov '04

15 Nov '04

Hi folks, I've returned to the problem that's been bugging me for quite a while now - getting a working Mt Rainier (cdmrw) setup on my PC. I started a thread on the kernel mailing list a couple of months ago ( http://marc.theaimsgroup.com/?l=linux-kernel&m=109206600002298&w=2 ), but the outcome seems to be that the problem lies with my Lite-on CD Recorder. Before I spend any more of my hard-earned cash, my question to you good people is, has anyone got a reliable mrw system with a 2.6 kernel and an IDE CD recorder? If so, what recorder are you using please? Thanks in advance. -- Chris

3 6

pktsetup 2.6.8-2 problems
by Christopher Martin 09 Nov '04

09 Nov '04

Hello, I've been using the 2.6.8-2 patch for a while now, and noticed a few things. If packet writing is setup for a drive, the eject button on the drive doesn't work after playing a DVD, or having mounted/unmounted the disc as a non-packet device. The eject command still works (as root). The problem can be fixed, allowing the button to work, by tearing down (and then starting up again, optionally) packet writing on the drive, or else mounting/unmounting the disc as a packet device. However, if all you planned to do was play a DVD, and you normally don't use the eject command, this is a noticeable problem. Also, the current patch has problems working with udev. When the pktcdvd module is loaded, a node is created by udev, /dev/pktcdvd, which should be /dev/pktcdvd/control. Since pktsetup expects /dev/pktcdvd to be a directory, this causes problems. Once this is worked around (by deletion, or being moved), and pktsetup is run to create the nodes for individual drives, say, /dev/pktcdvd/cdrw and /dev/pktcdvd/dvdburner, udev is triggered again and itself creates /dev/pktcdvd0 and /dev/pktcdvd1. Thus each drive now has 2 device nodes. Finally, the permissions of the drive nodes created by pktsetup (640 root.root) don't allow eject to be run by non-root. Would it be good to change the default permissions to 660 root.cdrom (the usual permissions for things like /dev/hdc) thus allowing cdrom group members to eject as well? Should /dev/pktcdvd/control (currently 644 root.root) use these new permissions as well, or is there a good reason for it to be writeable only by root, and readable by anyone? Thanks for all your work on packet writing. Cheers, Christopher Martin

1 0

Re: help to get packet writing working
by M 04 Nov '04

04 Nov '04

> OK-- !!!!!NO where in any instructions I read on making packet > writing work did I see the it said to use cp or drag-n-drop to write to disk. Where is this written???? :) > When I was trying to packet write a year ago, one used cdrwtool -d /dev/hdc -f ../filename to cp file to disk. WHY would I think I was suppose to do some thing different now?????? I think you're thinking of cdrecord which still very much exists and is there for writing an iso image to the disk. you need mkisofs to take the files and create the iso image. There are plenty of GUIs for making this easier. You can't delete using this method though if you use mutisession you can add directories. > Cdrwtool is still in udftools. Although for some reason I dont have man cdrwtool or man mkudffs. > I am using a udftools I installed with ./configure --prefix=/usr. Why would I not have manpages for the above?? You could try ./configure help and see if the man pages can be configured. I use a prebuilt package that puts the man pages in the right place... Debian... > Thank you all for the help...This has not been an easy thing to get working in Linux. No problem. > Maybe this would be a different post but how do I figure out what rev (1.0,1.5 or 2.01) is written on the on the disk????? from the cdrwtool on version: -v version Specify the udf revision to use. Valid revisions are 0x0201, 0x0200, 0x0150, and 0x0102. If omitted, mkudffs udf-version is 0x0150. Don't know if that's what your looking for? -- M

2 1

Re: help to get packet writing working
by gm c 04 Nov '04

04 Nov '04

OK-- !!!!!NO where in any instructions I read on making packet writing work did I see the it said to use cp or drag-n-drop to write to disk. Where is this written???? When I was trying to packet write a year ago, one used cdrwtool -d /dev/hdc -f ../filename to cp file to disk. WHY would I think I was suppose to do some thing different now?????? Cdrwtool is still in udftools. Although for some reason I dont have man cdrwtool or man mkudffs. I am using a udftools I installed with ./configure --prefix=/usr. Why would I not have manpages for the above?? Thank you all for the help...This has not been an easy thing to get working in Linux. Maybe this would be a different post but how do I figure out what rev (1.0,1.5 or 2.01) is written on the on the disk????? mike --- M <martin(a)luminoussheep.net> wrote: > > Hello > > Sorry ,I forgot a couple of times to cc packet-writing@suse. > > also sorry, I now have a /dev/pktcdvd/cdrw. I must not have > checked > > after configuring udftools 0.2.0. > > so far so good... > > > I can cdrwtool -d /dev/hdc -q and get a red light and after some > time > > message setup complete. If I mount disk with mount > /dev/pktcdvd/cdrw > > /cdrwudf -t udf -o rw,noatime I get no error message and can ls > > /cdrwudf and see lost+found. > > even better the disk is ready to use... > > > With disk still mounted, > > if I cdrwtool -d /dev/hdc -f /filename I get error message - > > mode_select: Illegal seek. > > Now why do you want to reformat it now you've mounted it? ;) > All you now need to do is copy files onto it and then unmount it > when you > want to take it away... > It will look just like a directory on a normall filesystem just a > _lot_ > slower. You can copy files onto and delete them from the new mount > point. > e.g. > cp /etc/passwd /cdrwudf > > ... I think we'll skip the rest. > > I think the process is: > 1/ if the disk is new format it with the cdrwtool > 2/ if you haven't setup a packet device configure it with pktsetup > 3/ mount the _packet device_ not the raw device > 4/ copy files onto the new mount point > 5/ umount new mount point > > > Notes: > To add files to a disk you previously unmounted go to step 2/ and > don't > cdrwtool it or you will loose everything on it... > After you have formatted it once, if you want to blank it you could > always > just delete whats on it to reuse, though it might be quicker to > reformat... > > -- > Good luck, > M > > > __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

1 0

Re: help to get packet writing working
by Graham Vincent 03 Nov '04

03 Nov '04

gm c wrote: > Hello > I dont understand the mount command to a path I dont have. That being > /dev/pktcdvd/cdrw. I do have /dev/pktcdvd0,1,2,3. Was pktsetup cdrw > /dev/hdc suppose to make the path?? Yes. If you have the properly patched pktsetup discussed several emails back it will create it for you. If it doesn't you don't have the correct version of pktsetup. Is it possible you have different version in different places on your machine? Send extracts from the logs next time. Graham > mike > > */Graham Vincent <graham(a)gpv.co.nz>/* wrote: > > Hello Mike. > > gm c wrote: > > Hello Graham > > > > I added > > cdr_device=cdrw > > cdrw=ata:1.0.0 > > to /etc/default/cdrecord > > I am not sure if that did anything because I committed out later with > > no change. > > No idea about this - I don't need anything here. > > > > > Then pktsetup cdrw /dev/hdc > > On an new disk I could I could cdrwtool -d /dev/hdc -i and -q. > > I could then mount -t udf /dev/hdc /cdrom -o noatime,rw and see the > > lost+found file. It mounted read only though. > > After umount /cdrom I could cdrwtool -d /dev/hdc -f filename and it > > seemed like it was writing. When I tried to mount to look at files > > copied I got error message cant read superblock etc. > > Why wont this work??? > > I think you're making progress :-) > > From the pktsetup syntax I presume you are using a 2.6.9 kernel for > this? > > After the "pktsetup cdrw /dev/hdc" you should try to mount with: > > "mount /dev/pktcdvd/cdrw /cdrom -t udf -o rw,noatime". > > The mount you are using mounts /dev/hdc but you want to mount the > /dev/pktcdvd/cdrw device which should give you the rw access... > > Take a look at the messages log (/var/log/messages on my FC2 system). It > should give you a fair bit of information on whether you have the right > device mounted. > > Good luck! > > Regards, > > Graham > > p.s. I see some of this traffic escaped being copied to the packet > writing list - my apologies to anyone who missed any of the interesting > bits. > > > > > One of my problems has been the disk I had been using. I could > > cdrwtool -d /dev/hdc -i and see files listed but cdrwtool -d /dev/hdc > > -q would not write to the disk. I tried a different disk which > > cdrwtool -d /dev/hdc -q formated ok. I tried to cdrecord -d /dev/hdc > > -force blank all with no success. Then used windows to format the > > disk and then it would cdrwtool -q. > > > > Mike > > > > > > > > --- Graham Vincent wrote: > > > > > >>Hello Mike. > >> > >>I don't think you are going to have much success changing between > >>the > >>2.4 and 2.6 kernels - both work but there have been significant > >>changes > >>in the access methods written into the kernel. I sugggest you > >>decide > >>which one you want to get working and stick with that (I'd choose > >>2.6.9 > >>if it's compatible with your distribution). > >> > >>the 1.0.0b3 version of udftools should be OK for 2.6.9 If you just > >>run > >>the command "pktsetup" what does it say? On my system I get: > >> > >># pktsetup > >>For pktcdvd < 0.2.0: > >> pktsetup /dev/pktcdvd0 /dev/cdrom setup device > >> pktsetup -d /dev/pktcdvd0 tear down device > >>For pktcdvd >= 0.2.0: > >> pktsetup dev_name /dev/cdrom setup device > >> pktsetup -d dev_name tear down device > >> pktsetup -d major:minor tear down device > >> pktsetup -s show device mappings > >> > >>Note the different syntax. > >> > >>The dmesg you sent me is for a 2.4 boot. It says you have a command > >>line > >>option of hdc=ide-scsi set. Not sure if you are using lilo or grub > >>but > >>check the configuration file. > >> > >>The config-2.6.9 looks OK for packet writing. I've got packet > >>writing > >>configured as a module which may work a bit better than built into > >>the > >>kernel. > >> > >>Summary: 2.4 kernel use scsi emulation. > >>2.6.9 kernel no scsi emulation. > >> > >>Do you have a 2.6.9 kernel that works with your distribution? > >> > >>Regards, > >> > >>Graham > >> > >>gm c wrote: > >> > >>>Hello again > >>>I patched udftools and installed. No difference from what I had > >>>before. Do I have to do something in /etc/defaults/udftools?? The > >>>Instructions in packet-writing.txt show giving the comand > >> > >>cdrwtool -d > >> > >>>/dev/hdc -q before doing pktsetup. Will that work? I do a > >> > >>cdrwtool > >> > >>>-d /dev/hdc -i and get error mesg that dev does not exist. > >>>I am attaching copy of dmesg and config. I am confused about it > >>>showing hdc having attached ide-scsi. I dont have any scsi > >> > >>configured > >> > >>>in this kernel. > >>>mike > >>>--- Graham Vincent wrote: > >>> > >>> > >>> > >>>>Hello Mike. > >>>> > >>>>gm c wrote: > >>>> > >>>> > >>>>>I tried a year ago to get packet writing working with no success > >>>> > >>>>and > >>>> > >>>> > >>>>>am trying again. I read the latest postings, patched kernel > >>>> > >>>>2.4.27 > >>>> > >>>> > >>>>>with patch 2.4.27 and kernel 2.6.9 with patch 2.6.8-2. On 2.4.27 > >>>> > >>>>said > >>>> > >>>> > >>>>>yes to pw on cd/dvd and udf filesystems and yes to scsi > >>>> > >>>>emulation.On > >>>> > >>>> > >>>>>2.6 no scsi emulation and yes to packet-writing. > >>>>>My first try was with k 2.6.9. > >>>>>pksetup /dev/pktcdvd0 /dev/hdc > >>>>>mount -t udf /dev/pktcdvd0 /cdrw > >>>> > >>>>snip... > >>>> > >>>>There have been a few changes to the pktsetup program recently > >> > >>for > >> > >>>>the > >>>>newer 2.6 kernels that require an additional patch and a > >> > >>different > >> > >>>>syntax. > >>>> > >>>>Take a look at the packet-writing.txt file in the > >>>>Documentation/cdrom > >>>>directory of your kernel source tree after applying the 2.6.8-2 > >>>>patch. > >>>>The first section should help a lot :-) > >>>> > >>>>Regards, > >>>> > >>>>Graham > > -- > To unsubscribe, e-mail: packet-writing-unsubscribe(a)suse.com > For additional commands, e-mail: packet-writing-help(a)suse.com > > ------------------------------------------------------------------------ > Do you Yahoo!? > Check out the new Yahoo! Front Page. www.yahoo.com <http://www.yahoo.com> -- Graham Vincent GPV Enterprises Limited PO Box 5001, New Plymouth, New Zealand Ph +64 21 046 8910 Fax +64 6 753 6970 graham(a)gpv.co.nz http://www.gpv.co.nz

2 1

Re: help to get packet writing working
by gm c 02 Nov '04

02 Nov '04

Hello Graham I added cdr_device=cdrw cdrw=ata:1.0.0 to /etc/default/cdrecord I am not sure if that did anything because I committed out later with no change. Then pktsetup cdrw /dev/hdc On an new disk I could I could cdrwtool -d /dev/hdc -i and -q. I could then mount -t udf /dev/hdc /cdrom -o noatime,rw and see the lost+found file. It mounted read only though. After umount /cdrom I could cdrwtool -d /dev/hdc -f filename and it seemed like it was writing. When I tried to mount to look at files copied I got error message cant read superblock etc. Why wont this work??? One of my problems has been the disk I had been using. I could cdrwtool -d /dev/hdc -i and see files listed but cdrwtool -d /dev/hdc -q would not write to the disk. I tried a different disk which cdrwtool -d /dev/hdc -q formated ok. I tried to cdrecord -d /dev/hdc -force blank all with no success. Then used windows to format the disk and then it would cdrwtool -q. Mike --- Graham Vincent <graham(a)gpv.co.nz> wrote: > Hello Mike. > > I don't think you are going to have much success changing between > the > 2.4 and 2.6 kernels - both work but there have been significant > changes > in the access methods written into the kernel. I sugggest you > decide > which one you want to get working and stick with that (I'd choose > 2.6.9 > if it's compatible with your distribution). > > the 1.0.0b3 version of udftools should be OK for 2.6.9 If you just > run > the command "pktsetup" what does it say? On my system I get: > > # pktsetup > For pktcdvd < 0.2.0: > pktsetup /dev/pktcdvd0 /dev/cdrom setup device > pktsetup -d /dev/pktcdvd0 tear down device > For pktcdvd >= 0.2.0: > pktsetup dev_name /dev/cdrom setup device > pktsetup -d dev_name tear down device > pktsetup -d major:minor tear down device > pktsetup -s show device mappings > > Note the different syntax. > > The dmesg you sent me is for a 2.4 boot. It says you have a command > line > option of hdc=ide-scsi set. Not sure if you are using lilo or grub > but > check the configuration file. > > The config-2.6.9 looks OK for packet writing. I've got packet > writing > configured as a module which may work a bit better than built into > the > kernel. > > Summary: 2.4 kernel use scsi emulation. > 2.6.9 kernel no scsi emulation. > > Do you have a 2.6.9 kernel that works with your distribution? > > Regards, > > Graham > > gm c wrote: > > Hello again > > I patched udftools and installed. No difference from what I had > > before. Do I have to do something in /etc/defaults/udftools?? The > > Instructions in packet-writing.txt show giving the comand > cdrwtool -d > > /dev/hdc -q before doing pktsetup. Will that work? I do a > cdrwtool > > -d /dev/hdc -i and get error mesg that dev does not exist. > > I am attaching copy of dmesg and config. I am confused about it > > showing hdc having attached ide-scsi. I dont have any scsi > configured > > in this kernel. > > mike > > --- Graham Vincent <graham(a)gpv.co.nz> wrote: > > > > > >>Hello Mike. > >> > >>gm c wrote: > >> > >>>I tried a year ago to get packet writing working with no success > >> > >>and > >> > >>>am trying again. I read the latest postings, patched kernel > >> > >>2.4.27 > >> > >>>with patch 2.4.27 and kernel 2.6.9 with patch 2.6.8-2. On 2.4.27 > >> > >>said > >> > >>>yes to pw on cd/dvd and udf filesystems and yes to scsi > >> > >>emulation.On > >> > >>>2.6 no scsi emulation and yes to packet-writing. > >>>My first try was with k 2.6.9. > >>>pksetup /dev/pktcdvd0 /dev/hdc > >>>mount -t udf /dev/pktcdvd0 /cdrw > >> > >>snip... > >> > >>There have been a few changes to the pktsetup program recently > for > >>the > >>newer 2.6 kernels that require an additional patch and a > different > >>syntax. > >> > >>Take a look at the packet-writing.txt file in the > >>Documentation/cdrom > >>directory of your kernel source tree after applying the 2.6.8-2 > >>patch. > >>The first section should help a lot :-) > >> > >>Regards, > >> > >>Graham > >> > > > > > > > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Mail Address AutoComplete - You start. We finish. > > http://promotions.yahoo.com/new_mail > > -- > Graham Vincent GPV Enterprises Limited > PO Box 5001, New Plymouth, New Zealand > Ph +64 21 046 8910 Fax +64 6 753 6970 > graham(a)gpv.co.nz http://www.gpv.co.nz > __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com

2 1