FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i've upgraded my fc1 to fc3 and everythings seems to be great, but as soon as i updated my system (using up2date a couple of times) suddenly some issue come out. first of all i've lost my internet connection (i'm using a silver speedtouch adsl modem, i've tied to reinstall the drivers but the adsl led keeps remaining blinking without any connection). a little later i found out that i can use cdrecord any longer (the system cannot find the device even though i'm sure to enter the right one as shown launching cdrecord -scanbus).
i'm really frustrated.
help please
Originally posted by pirozzi i'll try the driver. any news abot the problem with cdrecord?
Starting with the 2.6 kernel, cdrecord doesn't use the "dev=n,n,n" anymore. It is "dev=/dev/hdc" or "dev=/dev/hdd", etc. Also, the need for the "ide-scsi" boot parameter in lilo or grub goes away.
Also, the soft link for "/dev/cdrom" should point to "/dev/hdc" , "/dev/hdd", or whatever your cdrom is called.
great, i did it. thanks a lot.
i've experienced similar issue with gui burning apllications like k3b. are this issues related? how can i solve also this?
thank you again
Ummm... Not strictly true about the cdrecord -dev=n,n,n. I'm not at home right now (stuck in naff Win2000 system, blah blah), but google up 'cdrecord command line burning' and check it out.
Seriously, you'll have to the <checks his memory> busscan option on cdrecord (is it cdrecord --scanbus ? Someone with a bloody linux box in front of them help me out here! LOL)
Then use that as the device on cdrecord. I used the same command last night to burn the 3 Mandrake ISOs for my son's PC (it's not happy with FC3 unfortunately...)
Also - the link to the sourceforge Speedtouch link is spot on - I use one myself and it works perfectly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.