Re: current state of packet writing ??
Glenn wrote: Hello Jens and all, OK that did the trick for UDF. I had already compiled the test7 kernel with your patch and just made the udf module and did the modprobe thing. No problems yet. I was also able to format a CDRW just fine. My question/problem is in getting the new device to be recognized. I created it: mknod /dev/pktcdvd0 b 97 0 and verified that it existed after this problem: # ./pktsetup /dev/pktcdvd0 /dev/scd0 packet open: No such device [root@h000094b6613f /packages/udf/tools] I also get this when I tried to mount it, recognizing that this is probably foolish since it didn't set it up, but don't understand the file system not being supported since the module "udf" is installed and active. # mount -t udf /dev/pktcdvd0 /mnt/cdr mount: fs type udf not supported by kernel [root@h000094b6613f /dev] Appreciate any help that can be offered. Thanks, Glenn -----
Jens Axboe wrote:
On Mon, Sep 18 2000, Jens Axboe wrote:
You have an out-of-date UDF tree. For use with packet writing, current CDRW branch of the UDF tree is recommended.
Probably should have mentioned that the UDF page to go to is
http://sourceforge.net/projects/linux-udf/
-- * Jens Axboe
* SuSE Labs
Hi, I posted this question early this week and got no response. I'm wondering if anyone with Redhat has got this working? Perhaps there is a problem with the major device number assigned or my current setup for CD drives. lilo append ----------- append = "mem=128m,hdc=ide-scsi,hdd=ide-cd,ether=0,0,0x16,eth0,max_loop=32" fstab ----- /dev/hdd /mnt/cdrom iso9660 ro,user,noauto 0 0 /dev/scd0 /mnt/cdr iso9660 rw,user,noauto 0 0 Appreciate help with this since Deja News has yeilded nothing. Glenn ----- Glenn wrote:
Glenn wrote:
Hello Jens and all,
I was also able to format a CDRW just fine. My question/problem is in getting the new device to be recognized. I created it:
mknod /dev/pktcdvd0 b 97 0
and verified that it existed after this problem:
# ./pktsetup /dev/pktcdvd0 /dev/scd0 packet open: No such device [root@h000094b6613f /packages/udf/tools]
I also get this when I tried to mount it, recognizing that this is probably foolish since it didn't set it up, but don't understand the file system not being supported since the module "udf" is installed and active.
# mount -t udf /dev/pktcdvd0 /mnt/cdr mount: fs type udf not supported by kernel [root@h000094b6613f /dev]
On Sun, 24 Sep 2000, Glenn wrote:
Hi,
I posted this question early this week and got no response. I'm wondering if anyone with Redhat has got this working? Perhaps there is a problem with the major device number assigned or my current setup for CD drives.
lilo append -----------
append = "mem=128m,hdc=ide-scsi,hdd=ide-cd,ether=0,0,0x16,eth0,max_loop=32"
fstab -----
/dev/hdd /mnt/cdrom iso9660 ro,user,noauto 0 0 /dev/scd0 /mnt/cdr iso9660 rw,user,noauto 0 0
Appreciate help with this since Deja News has yeilded nothing.
Glenn -----
I got it working after a fashion. The formatted size of the disc was about 100Mb too small and when I tried to copy files to the mounted disk, I got lots of errors of the form: attempt to access beyond end of device 0b:00: rw=0, want=768, limit=2 huh, 1532 not uptodate The device I used was /dev/sr0 on RedHat 6.2 with a SCSI drive, if that makes any difference, rather than /dev/scd0 - isn't that for read-only drives? Adam
On Sun, Sep 24 2000, Adam Huffman wrote:
I got it working after a fashion. The formatted size of the disc was about 100Mb too small and when I tried to copy files to the mounted disk, I got lots of errors of the form:
Ben is looking into that, it's a bug in cdrwtool
attempt to access beyond end of device 0b:00: rw=0, want=768, limit=2 huh, 1532 not uptodate
AFAICR, this was caused by pktcdvd detecting a very small capacity of the disc, right? I'll look into this, I've got a 0.0.2d final release coming in the next couple of days (and yes, the corruption issue has finally been nailed 8)
The device I used was /dev/sr0 on RedHat 6.2 with a SCSI drive, if that makes any difference, rather than /dev/scd0 - isn't that for read-only drives?
No, it doesn't make a difference, they are indentical.
--
* Jens Axboe
On Sun, Sep 24 2000, Glenn wrote:
I was also able to format a CDRW just fine. My question/problem is in getting the new device to be recognized. I created it:
mknod /dev/pktcdvd0 b 97 0
That looks good
and verified that it existed after this problem:
# ./pktsetup /dev/pktcdvd0 /dev/scd0 packet open: No such device [root@h000094b6613f /packages/udf/tools]
Is the pktcdvd module loaded?
I also get this when I tried to mount it, recognizing that this is probably foolish since it didn't set it up, but don't understand the file system not being supported since the module "udf" is installed and active.
# mount -t udf /dev/pktcdvd0 /mnt/cdr mount: fs type udf not supported by kernel [root@h000094b6613f /dev]
And udf is not there, are you sure you booted the right kernel? If both
pktcdvd and udf is missing, something smells fishy.
--
* Jens Axboe
Jens Axboe wrote:
On Sun, Sep 24 2000, Glenn wrote:
I was also able to format a CDRW just fine. My question/problem is in getting the new device to be recognized. I created it:
mknod /dev/pktcdvd0 b 97 0
That looks good
and verified that it existed after this problem:
# ./pktsetup /dev/pktcdvd0 /dev/scd0 packet open: No such device [root@h000094b6613f /packages/udf/tools]
Is the pktcdvd module loaded?
I also get this when I tried to mount it, recognizing that this is probably foolish since it didn't set it up, but don't understand the file system not being supported since the module "udf" is installed and active.
# mount -t udf /dev/pktcdvd0 /mnt/cdr mount: fs type udf not supported by kernel [root@h000094b6613f /dev]
And udf is not there, are you sure you booted the right kernel? If both pktcdvd and udf is missing, something smells fishy.
-- * Jens Axboe
* SuSE Labs
Thanks for the response,
From my "/lib/modules/2.4.0-test7/modules.dep" file /lib/modules/2.4.0-test7/modules.dep the modules were created OK:
/lib/modules/2.4.0-test7/kernel/drivers/block/pktcdvd.o /lib/modules/2.4.0-test7/kernel/fs/udf/udf.o However if I do a "lsmod" it shows that the modules udf and pktcdvd0 aren't being loaded and I don't have a clue why they aren't So then I do a modprobe for both of them. # modprobe udf [root@h000094b6613f /lib/modules/2.4.0-test7] # modprobe pktcdvd [root@h000094b6613f /lib/modules/2.4.0-test7] # lsmod Module Size Used by pktcdvd 14180 0 cdrom 27452 0 [pktcdvd] <-------- udf 77648 0 (unused) --- snip # ls /dev/pktcdvd0 /dev/pktcdvd0 # cd /packages/udf/tools/ # ./pktsetup /dev/pktcdvd0 scd0 open device: No such file or directory [root@h000094b6613f /packages/udf/tools] I just noticed something from the above. I have a cdrom and a cdr on my machine. Both are IDE devices and I use scsi emulation for the cdr. pktcdvd is using the cdrom and it should be the cdr. Any suggestions? Thanks, Glenn -----
Hi, Well a little more progrees. I changed my sym link for my /dev/scd0 to /dev/cdrom. I was then able to: ./pktsetup /dev/pktcdvd0 /dev/scd0 without errors. However, when I attempt to mount I can't write: mount -t udf -o rw,user /dev/pktcdvd0 /mnt/cdrom mount: block device /dev/pktcdvd0 is write-protected, mounting read-only These are my current questions: 1) Why aren't udf and pktcdvd0 modules being auto loaded even though they appear in my modules.dep file? 2) How do I get pktcdvd to use cdr and not cdrom? 3) Why is it mounting as read only? I also noted the size difference as pointed out by Adam Huffman. # df /dev/pktcdvd0 447680 34 447646 1% /mnt/cdrom Glenn -----
Thanks for the response,
From my "/lib/modules/2.4.0-test7/modules.dep" file /lib/modules/2.4.0-test7/modules.dep the modules were created OK:
/lib/modules/2.4.0-test7/kernel/drivers/block/pktcdvd.o /lib/modules/2.4.0-test7/kernel/fs/udf/udf.o
However if I do a "lsmod" it shows that the modules udf and pktcdvd0 aren't being loaded and I don't have a clue why they aren't So then I do a modprobe for both of them.
# modprobe udf [root@h000094b6613f /lib/modules/2.4.0-test7] # modprobe pktcdvd [root@h000094b6613f /lib/modules/2.4.0-test7] # lsmod Module Size Used by pktcdvd 14180 0 cdrom 27452 0 [pktcdvd] <-------- udf 77648 0 (unused) --- snip # ls /dev/pktcdvd0 /dev/pktcdvd0 # cd /packages/udf/tools/ # ./pktsetup /dev/pktcdvd0 scd0 open device: No such file or directory [root@h000094b6613f /packages/udf/tools]
I just noticed something from the above. I have a cdrom and a cdr on my machine. Both are IDE devices and I use scsi emulation for the cdr. pktcdvd is using the cdrom and it should be the cdr.
Any suggestions?
Thanks, Glenn -----
mount -t udf -o rw,user /dev/pktcdvd0 /mnt/cdrom mount: block device /dev/pktcdvd0 is write-protected, mounting read-only
mabye b/c you compiled udf w/out "Write Support"? In order to get you need to enable 'experimental options' and then enabled 'UDF Write (Dangerous)"
1) Why aren't udf and pktcdvd0 modules being auto loaded even though they appear in my modules.dep file?
b/c modules.dep just lists intermodule dependencies. In order to have something call the module kernel/knod or whatver it is nowdays needs to know what to call for example if I do 'ifconfig eth0' then the "whatever" will check out /etc/modules.conf what eth0 is defined as [adam@pepsi licq]$ grep eth0 /etc/modules.conf alias eth0 tulip
3) Why is it mounting as read only?
see above -- Adam http://www.eax.com The Supreme Headquarters of the 32 bit registers
participants (4)
-
Adam
-
Adam Huffman
-
Glenn
-
Jens Axboe