Linuxers January 2002

linuxers@mm.ilug-bom.org.in

88 participants
135 discussions

CD-ROm problems in RH7.2
by Anand Iyer 29 Jan '02

29 Jan '02

Please find the logged messages. Currently, i have abandned the use of CD drive on RH7.2, but go to caldera and scan CD's. This seems either a kernel issue or a package issue. i also tried NEC 250 CD changer system on the same setup and that is shown in hardware browser, but does not work. Anand

1 0

can't read vcd
by Manish Jethani 28 Jan '02

28 Jan '02

Just installed red hat 7.2. Things are ok, except for this. It's not able to read any of my video CDs. I'm able to mount the vcd, but I can't read a file (I can read directories). Here's the cdrom portion of my fstab: /dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0 Here's what I'm doing. # eject -t # mount /mnt/cdrom # ls /mnt/cdrom/mpegav avseq01.dat # cp /mnt/cdrom/mpegav/avseq01.dat . cp: reading `/mnt/cdrom/mpegav/avseq01.dat': Input/output error # echo $? 1 # umount /mnt/cdrom # eject # rm -rf / I tried with different video CDs (I have many =) but none of them seem to work. And the behaviour is the same - can read directories but can't read files. Also, other CDs (like the rh7.2 cd itself) work just fine. It's just with video CDs this problem. And the same video CDs were working ok with windows until last week when I removed windows. I have *enough* space on my disk. I can't even do something like this: # cat /mnt/cdrom/mpegav/avseq01.dat > /dev/null cat: /mnt/cdrom/mpegav/avseq01.dat: Input/output error Anyone faced this problemo? What do you do? Manish -- Today is the last day of your life so far.

3 3

Re: can't read vcd
by Abhir Joshi 28 Jan '02

28 Jan '02

Hi I had a same problem when reading three VCDs. 'plaympeg' said it cant find mpeg data. 'gtv' was unable to play it. 'cp' reported an I/O error. I tried to view it from Windows and it worked ! Then I tried to copy it using Windows. Almost the whole dat file was copied except the last 5 seconds saying that "the system can't read the specified device". This happened for all the VCDs. But the VCDs surface seemed to have no problem as they were newly written. And it looks very improbable that all the VCDs which i had, had errors in the *last* 5 seconds ! I think that there is some kind of protection mechanism built into the CD. But I could cheat it by using VCDGear (under windows). I first tried to use VCDGear under Linux with option 'dat2mpg' but it said that it couldn't find mpeg data. VCDGear under Windows converted the '<cdrom drive>:\mpegav\Avseq01.dat' file into "<dest drive>:\Movies\Avseq01.mpg' without any errors ! ! I used dat to mpg conversion option to achieve this. Now the mpg file plays fine in Linux. I think VCDClipper also could have done the job. Well, my guess... Since Windows could read *almost* the whole file (actually i think the whole file), it seems that there is some bit in the CD file system (or similar kind of information) that indicates whether it is legal (??) to copy the file or not. Now whether to make use of that or not might be upto the copying program. Now if the cdrom driver in Linux checks the info before copying and windows driver checks it after the data has been copied (before writing the directory entry), the situation seems to be consistentent. Now whether that kind of information really exists on a VCD FS is to be discovered....anybody knows ? Well, initially i thought of a long way... It could have been achieved this way....(in Windows) - First make a drive empty by moving all the data to a different drive. - Now, data if written on this drive, will start from cluster 2. - Then copy the dat file to this drive unitl it gives the error message. - Now the FAT entries have been made, only the directory entry needs to be written. - Next instead of saying OK to that error, cold reboot your PC by pressing directly the reset key (!!) - Goto to real mode. - unlock your disk using 'lock' - use Norton's Diskedit supporting FAT 32 to make a root directory entry which points to cluster 2 as starting cluster. Also the size of the file and attributes have to be written here. OR writing a C program to directly write the directry entry of 32 bytes to the root directory without using standard function or DOS services but by using bios interrupts. - Now after rebooting the PC the file should be playable (most probably ! Never tried actually) Abhir _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

3 2

Re: [ILUG-BOM] Re: can't read vcd
by Tahir Hashmi 28 Jan '02

28 Jan '02

On Sat, 26 Jan 2002 17:42:37 Abhir Joshi wrote: >Hi > >I had a same problem when reading three VCDs. 'plaympeg' [Snip] >Well, my guess... >Since Windows could read *almost* the whole file (actually i think the >whole file), it seems that there is some bit in the CD file system >(or similar kind of information) that indicates whether it is legal (??) >to copy the file or not. Now whether to make use of that or not might >be upto the copying program. Now if the cdrom driver in Linux checks >the info before copying and windows driver checks it after the data has >been copied (before writing the directory entry), the situation seems >to be consistentent. > >Now whether that kind of information really exists on a VCD FS is to be >discovered....anybody knows ? > [Snip] There's actually been an influx of ACDs and VCDs that are supposed to be non-piratable. The trick applied is to induce deliberate bit-errors and hope that the stronger error tolerance of CD players will allow them to carry on while the more finicky CD-ROM drives of the computers will complain. Philips, the co-inventor of the CD has been able to force companies making such CDs to print a warning stating that such products are not CDs. They can't even print the famous 'CD' logos. IMHO, this is the height of idioticity on part of the new CD makers because there are some CD players too that fail to play those CDs. Also, once your CD wears, there's a greater chance that your CD player may fail to recover from so many errors. Lastly, computer software that has strong error correction built-in will still be able to read the CDs A detailed article regarding this appeared a few weeks back on the _Business Times_ page of _The Times of India_ as the main headline and I've written what I understood from that article. Unfortunately, I forgot the date on which it appeared. --- Tahir Hashmi (VSE, NCST) http://tahirhashmi.scriptmania.com mailme(a)tahirhashmi.scriptmania.com __________________________________ We, the rest of humanity, wish GNU luck and Godspeed

1 0

COMMERCIAL -Affordabe Linux CDs in India
by Linux CDs 28 Jan '02

28 Jan '02

Hi, You can find the most affordable Linux CDs in India at http://www.linuxoncds.cjb.net Debian Linux 2.2r4 Three CD Set = Rs. 160.00 Mandrake Linux 8.1 Three CD Set = Rs. 180.00 Red Hat Linux 7.2 Two CD Set = Rs. 125.00 Shipping & Handling is extra Rs. 30.00 outside Mumbai per Set. Rs. 15.00 within Mumbai per Set. For all details including payments visit : http://www.linuxoncds.cjb.net Quality & Delivery is Gauranteed. Let me know if you are interested. Bye.

1 0

LindowsOS sneak preview -- it's not vaporware after all
by N.D. 28 Jan '02

28 Jan '02

http://www.newsforge.com/article.pl?sid=02/01/25/1811226 Conclusions This is a beta and Robertson cautions that it is not expected to work properly. I had many more problems with Wine than our anonymous tester did. And while I wouldn't spend the $99 to get LindowsOS, he would. "Slick installation, great Wine, very good integration," he says. But the fonts need work. "Wine fonts look horrible (especially on the popup boxes) even if you add your fonts to the X server." We both agree that the user management needs to change, and Lindows needs to add more configurability -- if Robertson is going for the Linux crowd, that is. If he's going for Windows market share, then he needs to cater to the people who are logging in, looking at the pretty KDE desktop, and wondering what to do next. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

CD ROm detection problem in RH 7.2
by Anand Iyer 26 Jan '02

26 Jan '02

Hi Kunal and others trying to help, I removed the append="hdc=ide-scsi" from lilo.conf. ran lilo. booted the machine. And inserted a PCQ CD inside the drive and tried mount when it did not automount. Then removed the fstab line for CDROM. Rebooted the machine. Still the same results. I am not worried about CD recording at this moment. Machine history: Loaded PCQ 7.1 in July and running smoothly since then. CDRecord and ordinary CD usage with the lilo line "append...." was there. Upgraded recently to RH 7.2 using Seascope CD's. The CD's are with me and the kernel being used is 2.4.7-10 . Initially I had a installation problem and I got another set of CD's with me now. The install has worked smoothly so far. But the CD ROM is not being read. I went to hardware browser in Gnome after logging in as root Window shows on left CDROM Devices Right Hand top side shows SAMSUND CD-R/RW DRIVE SW-208F Bottom right hand side window shows manufacturer: unknown driver: ignore Device: /dev/hdc So I am a bit confused. I believe his means that the CDROM is detected in /dev/hdc and ths SAMSUNG ... that is seen means that the CDROM drive is being properly detected by some software component however the bottom part of the window is worrying and shows that the CDROm detection has some problems. is this Kernel Related? Please note that the same system has caldera loaded in another partition with 2.4.2 and the system is running smoothly. Anand Message: 5 From: "Kunal Gangakhedkar" <kgangakhedkar(a)yahoo.com> <mailto:kgangakhedkar@yahoo.com> To: <linuxers(a)mm.ilug-bom.org.in> <mailto:linuxers@mm.ilug-bom.org.in> Subject: Re: [ILUG-BOM] CD ROM problems Kernel 2.4.7-10 Date: Tue, 22 Jan 2002 21:10:22 +0530 Reply-To: linuxers(a)mm.ilug-bom.org.in <mailto:linuxers@mm.ilug-bom.org.in> Well, as I can see from the scenario, your CDRW is getting detected as a SCSI drive. In fact, it is an IDE drive - am I right?? To get around with the problem, just remove the "append=...." line from lilo.conf 'coz you don't need it. Then update lilo using /sbin/lilo. The next time you boot into linux your CDRW should be detected as an ordinary IDE CDROM. But then, you won't be able to write CDs through linux, 'coz all the CD- Writing softwares in linux (including cdrecord and Xcdroast) need your drive to be SCSI. Now, to make your IDE CDRW (now detected as an IDE CDROM) work for writing CDs, what you can use is an emulation driver - ide-scsi. This is precisely what you've been seeing in your lilo.conf. This is a modular driver which can be used using modprobe or insmod. The advantage is - install when you want, uninstall after using it. I guess, you know how to uninstall / remove modules. When you add this driver, just check out the working of the driver using #cdrecord -scanbus If you get the output saying the HOST/DEVICE/LUN ids, then you can be pretty sure that the driver will work for you. The only problem I faced was that the normal IDE-CD emulation driver used to interfere with it. So, to be on a safer side, make sure that you remove ide-cd before inserting ide-scsi. The ide-scsi driver is available online or can be found at PCQ's wesite (in fact, it comes built into PCQ Linux Distro). After you're done with the CDRW for writing, remove the ide-scsi driver using #rmmod sg #rmmod ide-scsi These are dependant modules. Then insert the usual ide-cd driver using #modprobe ide-cd And you'll be back with your CDRW as IDE CDROM. For more information, pls. refer to CD-Writing HOWTO Kunal ------------------ The choice is yours, don't be late Take a rest as a friend as an old memory Nirvana - Come As You Are ----- Original Message ----- From: kishor bhagwat <aaaaarrrgghhh(a)yahoo.com> <mailto:aaaaarrrgghhh@yahoo.com> To: <linuxers(a)mm.ilug-bom.org.in> <mailto:linuxers@mm.ilug-bom.org.in> Sent: Tuesday, January 22, 2002 10:46 AM Subject: Re: [ILUG-BOM] CD ROM problems Kernel 2.4.7-10 >> >> --- Anand Iyer <akiyer(a)vsnl.com> <mailto:akiyer@vsnl.com> wrote: > >>> > My CDROm drive Samsung CD writer RW 8.4.32 is recognised >>> > by the kernel, >>> > but when i try to mount the CDROm, I get a message >>> > /dev/cdrom improper device or device does not exist. >>> > I have the following line in lilo.conf >>> > append="hdc=ide-scsi" >>> > This used to work and still works on Caldera with kernel >>> > 2.4.2 (PCQuest >>> > CD's)loaded in another partition. >> >> >> the append line in your lilo.conf means that scsi emulation >> is used for your drive(cd burning programs require it). >> try mounting /dev/scd0 as your cdrom drive.. >> >> regards, >> kishor >> >> >> >> >> >

2 1

Re: can't read vcd
by Abhir Joshi 26 Jan '02

26 Jan '02

Hi Manish Jethani Wrote ># rm -rf / man ! what are you doing !!! rm -rf <slash> as root !! I think it was a typo, and you meant 'rm -rf .' :-) Abhir _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

Icons for GNOME Tasklist
by Tahir Hashmi 26 Jan '02

26 Jan '02

Hi All Does any of you know how to assign mini-icons for the GNOME Tasklist to an application? Thanx in advance --- Tahir Hashmi (VSE, NCST) http://tahirhashmi.scriptmania.com mailme(a)tahirhashmi.scriptmania.com __________________________________ We, the rest of humanity, wish GNU luck and Godspeed

1 0

Problems with installing GCC
by Kinjal Sonpal 25 Jan '02

25 Jan '02

Hi Luggers ! I'm trying to install gcc-2.96-84.i386.rpm ( taken from the PCQ Linux CD) on a RHL 6.2 (zoot ?) m/c. The installation is almost a yr old and it does not have any of the development tools as well as compiler .. When I issue the following command $ rpm -i gcc-2.96-84.i386.rpm I get the following error Error : The current version of rpm only supports packages having major number <= 3. I checked up with rpm docs and cud understand that in the above rpm, _2.96_ is supposed to be the major number. Then in order to upgrade the current installation of rpm, which I thought cud be the cause of the trouble, I tried to use the rpm installation binary available from the same CD. I got the same error for it. In fact, I got the same error for all the packages that I tried to install/upgrade. What cud be wrong here? I'm not supposed to remove the current installation, nor do I have direct CD-Drive access to this m/c. Thanks a lot in advance Regards, Kinjal Sonpal

5 10

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Linuxers January 2002