chris z

FINAL UPDATE:all breathe a sigh of relief.......... :D i just finished updating the XFree86 packages via MCC->Mandrake Update. all installed without a hitch, X starts without a hitch. (or i wouldn't be posting this right now in GUI mode ) so, if any of ya wanna take the XFree plunge, all seems well & safe to do so. Chris

i have a TDK481648b cdrw. to echo llorge, use the generic-mmc driver & you should be fine. that's what i use. the "auto" setting always gave me fits. also, you may need scsi emulation enabled. if you find you do, search here in the forum for "k3b" &/or "scsi emulation". there are several threads concerning that. Chris

here's some good info on how to get various plugins working with Moz & Netscape....... Mozilla & Netscape Plugin Help if ya wanna try the easy method, do to the downloads section in the forum for some plugins in rpm format........ MDK Forum Plugins or, you could check out Texstar's stuff for some rpm plugins....... Texstar RPM's Chris

YET ANOTHER UPDATE:.........to anyone who cares.......... the correct XFree86 packages for MDK9.1 are now up on all of the mirrors except for 4.......... MDK Updates FTP Mirrors i haven't installed yet, but will be doing so tonight after work. so, if you are leary of these packages, sit tight & i'll be a guinea pig & post back the results tonight. Chris

UPDATE: i was just in the #mandrake board & i just finished speaking with one of the developers of the XFree86 update packages that are causing troubles in MDK9.1. they are now aware of the problem & are working on getting it straightened out. from what he said, the update mirrors apparently have 2 versions of the XFree86 packages on them. one bad version, one good version. but, nobody removed the bad version of the packages so they are the ones that are showing up as the update. the person i was speaking to doesn't have the neccessary security permissions to change things on the mirrors & he's trying to get a hold of somebody that can. but, he said the fix may not be able to be in place until tomorrow (Monday 12-22-03) unless he can find somebody to do it today. just to let you all know that this is being worked on & a fix should be in place soon. Chris

klemm........ ya, as you now know, the XFree86 security update for mdk9.1 is screwed up. why they haven't noticed this yet, or at least taken that update off the mirrors, i dunno. anywho, if you haven't been able to fix it yet, this is what ya need to do....... after you get the error message: you should be left at a login prompt. type in your password as you normally would, hit enter. su to root (su->enter->root password->enter) then, type the following (this is cap sensitive): urpmi XFree86 hit enter. it will now tell you that it found the following package XFree86(version number) do you want to install? answer yes, hit enter. it will then tell you that XFree86-server is also neccessary, do you want to continue/install. answer yes, hit enter. it will then ask you for your MDK Install CD1. pop that disc in, hit enter again, & let it install the XFree86 packages. when it's done, you'll be back at the user prompt. type reboot , then hit enter. you're machine will then reboot & you'll be back to normal. you will be now running an older version of XFree86 & server but they work just fine. if you want the latest bug free version of it, go to here for XFree86-4.3-8.2mdk.i586.rpm..., here for XFree86-server-4.3-8.2mdk.i586.rpm & here for XFree86-libs-4.3-8.2mdk.i586.rpm. download those packages, then install them in this order..........XFree86, XFree86libs, XFree86server. reboot after you install them (or just restart X) & that will give you the latest good version of XFree86 for MDK9.1. EDIT: actually, if you do get the latest XFree86 packages i lested above, the main XFree86 package will install the proper libs with it, so all you need to do after installing XFree86-4.3-8.2mdk.i586.rpm is install the server. just make sure you install the server package afterwards, because the first one removes the old server version during install. hope that helped.......... Chris

hmmm........ i just checked. the bad xfree update is still showing up. and, all the mirrors 'cept 2 or 3 are up to date as of 12-19. maybe try some other mirrors? Chris

ummm....... Linux_Learner..........i just checked updates & the same bad one is still listed for MDK9.1, which is what i'm running. i'm guessing you must be running 9.2. so, i'd still have to say, if anybody is running 9.1 & sees the update version of Xfree86 that i referenced in the first post of this thread, stay away from it, or at least proceed with caution. Chris

man...... i didn't mean to set off a bomb here! all i wanted to do was try to prevent others from getting this update, because it was obviously screwed up. seeing that they now have a different xfree version in the update along with the neccessary server package telles me that MDK recognized that, were on their toes, & fixed the goof quickly. it was by no means intended to slam MDK or Linux, nor did i even feel that way. it was just a buggered update, plain & simple, & i wanted to try to prevent others from having any headaches because of it. i mean, imagine if somebody who has little or no command line experience would have gotten this update, only to be faced with a black screen, blinking curser, & some errors scrolling by upon their next boot up? you probably would have had a flood of panicked people posting from Windows saying that all of a sudden they can't boot to their desktops & don't know what to do. in retrospect, maybe the CAPS i used in the topic was a bit excessive, but i just wanted to catch folks attention. i love my MDK, i have no gripes with it or with the MDK folks, or Linux in general. sorry if i came off that way, but that truly isn't the case. peace all, Chris

tried it again for shits & giggles. same result. something is really f'd up with this update. give it a whirl to see what i mean. you don't even have to install. just go for the xfree86 & watch when it tells you it needs to remove xfree86-server. same with the devel. you won't even be able to install it 'cause you don't have the libs & they're not part of the updates. Chris

well, i haven't done anything to or with k3b as far as changes, upgrades, or tweaking goes, for months now. and, xcdroast is the version that came with the mdk installation. that's what i thought at first too, but i honestly can't think of anything i installed, uninstalled, or upgraded that would screw with cdroms or the eject function. also, sarah31, i did think of uninstalling eject, but when i tried it wanted to take half of MDK with it! (drakconfig, draktools, any several other necessary apps........depends hell in reverse!) i may try playing with changing permissions later. or, tomorrow morn. time to take a break from geeking for the day & start drinking. Friday night, ya know. if you have any other ideas or thoughts, put 'em here. Chris

sarah31........ the problem isn't ejecting the drive from cli. i can do that. in fact, that's the only way i can do it, even when the drive is not mounted. you can't eject it via the eject button on the drive itself, nor with the right click eject option from the desktop shortcut. the burner works fine with all methods, so i wanted to figure out why the burner ejects via all methods, but why i need to cli eject as root for the cdrom. and, yes, i can eject with either eject /mnt/cdrom(2) or via eject /dev/scd0(1). Scoopy........ i don't know what else to point you to. (sorry) i mean, that's what i was sorta hoping for........for somebody to point me to the solution, based on the info i provided. if you need some more info, please let me know what & i'll post it. i doubt if i'll be awake, or at least sober enough :o to discuss this with you at midnight, but thanks for the offer. just post on here with anything you can tell me or need for me to tell you & i'll check back periodically. i really don't want to re-enable supermount as i like it disabled. it gave me lots of headaches concerning k3b a while back. Chris

NOTE: the following issue only seems to affect MDK9.1. if you are using a version of MDK other than 9.1, you should be okay with the XFree86 security update, AFAIK. i just ran MDK update. it said there were 2 XFree86 security related upgrades. xfree86-4.3-8.4.91mdk xfree86-devel-4.3-8.4.91mdk i did the xfree86 first. it told me before it could install, it needed to remove xfree86-server. i thought that's weird, but maybe a new version is part of the package. WRONG!!!! i then tried to install the devel package, but it told me i was missing xfree86=libs-4.3-8.4.91 & that it couldn't install. so i searched via urpmi for the libs, but they weren't found anywhere. went to rpmfind, they didn't have them. went to the xfree86 web site. couldn't find them there, either! so i cancelled the install of that. i rebooted to see what might happen. well, you can prolly guess what happened. no xfree86 server, no startx!!! i had to urpmi from terminal, uninstall the "upgrade" for xfree86, then install the older version from cd1 & the server along with it. has anybody else tried this update? if so, did you have the same poblems? if you didn't try this, anybody wanna try & verify that this wasn't just some weirdness on my end? let me know, please........ Chris

hmmm.......... what, change permissions for cdroms & scd1&0? currently here's what i have: /mnt/cdrom permissions:rwxr-xr-x owner:root group:root (this is my burner) /mnt/cdrom2 same as above (this is my cdrom) /dev/cdrom0 permissions:rw-rw---- owner:chris group:cdwriter (????) (this is my burner) /dev/cdrom2 same as above (this is my cdrom) /dev/scd0 (burner) same as above /dev/scd1 (cdrom) same as above why would they permissions/owners/groups be different in /dev from /mnt? also, why are the /dev groups cdwriter? maybe something to do with k3b/xcdroast settings? Chris

hi folks....... (brace yerselves. this is gonna be long, but thorough.) i asked around on musb about this & recieved several suggestions, but none have worked, so i'm gonna throw it out here & see if anybody has an answer. the problem: when i mount my cdrom with a data cd, after unmounting it i can't eject the cd via the physical eject button on the cdrom nor will it eject by right clicking my cdrom desktop icon & selecting eject. nor will it eject from terminal as user. the only way i can eject it is using the eject command as root from terminal. when i try right clicking the icon to eject, i get this message in a pop up box....... "eject /dev/scd1 failed!" here's what i get when i eject it from terminal as root in verbose mode. (which does eject the cd after this message scrolls) [root@default chris]# eject -v /dev/scd1 eject: device name is `/dev/scd1' eject: expanded name is `/dev/scd1' eject: `/dev/scd1' is a link to `/dev/scsi/host0/bus0/target1/lun0/cd' eject: `/dev/scsi/host0/bus0/target1/lun0/cd' is not mounted eject: `/dev/scsi/host0/bus0/target1/lun0/cd' is not a mount point eject: `/dev/scsi/host0/bus0/target1/lun0/cd' is not a multipartition device eject: trying to eject `/dev/scsi/host0/bus0/target1/lun0/cd' using CD-ROM eject command eject: CD-ROM eject command failed eject: trying to eject `/dev/scsi/host0/bus0/target1/lun0/cd' using SCSI commands eject: SCSI eject failed eject: trying to eject `/dev/scsi/host0/bus0/target1/lun0/cd' using floppy eject command eject: floppy eject command failed eject: trying to eject `/dev/scsi/host0/bus0/target1/lun0/cd' using tape offline command eject: tape offline command failed eject: unable to eject, last error: Invalid argument i get the same results if try ejecting using eject -v /mnt/cdrom2 which is the mount point for that device. some info: i'm trying to do this using Texstar's KDE3.1.4. this problem only started sometime in the past 2 weeks, or so, though i'm not sure of the exact date that this started. i know the eject functions (right click & push button) did work at one time in this version of KDE (i've had it since September), so i don't think it's a Texstar issue. i haven't done anything (that i can think of) that should/would affect the cdrom or the eject function. (IE: screwing around with device settings, installing any cd related apps, screwing around with mount points, etc...) the cdrom works fine, otherwise. i can mount it, read data from it, unmount it, all as user or via right click icon for mount/unmount or from terminal. my cd burner is not affected by this. i can mount/unmount the burner via both methods & i can eject from the burner via all mehtods described. technical stuff: cdrom: generic atapi that came with the pc. never had a problem with it & still don't as far as reading data cd's & playing music cd's go. mount points are /mnt/cdrom2 & /dev/scd1. the cdrom is slave. (hdb) cdburner: tdk cdrw 48x16x48. no problems with that performing nor ejecting. mount points are /mnt/cdrom0 & /dev/scd0. the cd burner is master. (hda) i DO have scsi emulation enabled for both drives (i need this due to k3b issues). i DO NOT have supermount or automount enabled for either drive. here's my fstab entries: [root@default chris]# cat /etc/fstab /dev/hdc7 / ext2 defaults 1 1 none /dev/pts devpts mode=0620 0 0 /dev/hdc10 /home ext2 defaults 1 2 /dev/scd0 /mnt/cdrom auto user,noauto,ro,exec 0 0 /dev/scd1 /mnt/cdrom2 auto user,noauto,ro,exec 0 0 none /mnt/floppy supermount dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0 /dev/hdc1 /mnt/win_c vfat iocharset=iso8859-1,codepage=850,umask=0 0 0 /dev/hdc5 /mnt/win_d vfat iocharset=iso8859-1,codepage=850,umask=0 0 0 /dev/hdc6 /mnt/win_e vfat iocharset=iso8859-1,codepage=850,umask=0 0 0 none /proc proc defaults 0 0 /dev/hdc9 /usr ext3 defaults 1 2 /dev/hdc8 swap swap defaults 0 0 here's my mtab entries: [root@default chris]# cat /etc/mtab /dev/hdc7 / ext2 rw 0 0 none /proc proc rw 0 0 none /proc/bus/usb usbdevfs rw 0 0 none /dev devfs rw 0 0 none /dev/pts devpts rw,mode=0620 0 0 /dev/hdc10 /home ext2 rw 0 0 none /mnt/floppy supermount rw,sync,dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,codepage=850,umask=0 0 0 /dev/hdc1 /mnt/win_c vfat rw,iocharset=iso8859-1,codepage=850,umask=0 0 0 /dev/hdc5 /mnt/win_d vfat rw,iocharset=iso8859-1,codepage=850,umask=0 0 0 /dev/hdc6 /mnt/win_e vfat rw,iocharset=iso8859-1,codepage=850,umask=0 0 0 /dev/hdc9 /usr ext3 rw 0 0 here's my lilo.conf entries: [root@default chris]# cat /etc/lilo.conf boot=/dev/hdc map=/boot/map vga=normal default="linux" keytable=/boot/us.klt prompt nowarn timeout=900 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hdc7 initrd=/boot/initrd.img append="quiet devfs=mount hda=ide-scsi hdb=ide-scsi acpi=off" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hdc7 initrd=/boot/initrd.img append="devfs=mount hda=ide-scsi acpi=off" read-only other=/dev/hdc1 label="windows" table=/dev/hdc other=/dev/fd0 label="floppy" unsafe image=/boot/vmlinuz label="failsafe" root=/dev/hdc7 initrd=/boot/initrd.img append="failsafe devfs=nomount hda=ide-scsi acpi=off" read-only image=/boot/vmlinuz-2.4.21-0.18mdk label="2421-18" root=/dev/hdc7 initrd=/boot/initrd-2.4.21-0.18mdk.img append="quiet devfs=mount hda=ide-scsi acpi=off" vga=788 read-only image=/boot/vmlinuz-2.4.21-0.25mdk label=2421-25 root=/dev/hdc7 read-only optional vga=788 append="quiet devfs=mount hda=ide-scsi hdb=ide-scsi acpi=off" initrd=/boot/initrd-2.4.21-0.25mdk.img image=/boot/vmlinuz-2.4.21-0.26mdk label=2421-26 root=/dev/hdc7 read-only optional vga=788 append=" quiet devfs=mount hda=ide-scsi hdb=ide-scsi acpi=off" initrd=/boot/initrd-2.4.21-0.26mdk.img and, yes, i do realize that my hard drive is secondary master, but that doesn't matter concerning the eject problem. that's how it's been set up for years. what i've tried so far: per some suggestions in musb, i've tried disabling scsi emulation. i've tried commenting out the line in fstab for both the cdrom & burner, one at a a time, rebooting & letting the new hardware be detected. i've tried enabling supermount/automount. i've tried changing permissions to user for eject, scd1, scd0, cdrom2, & cdrom0. none of those methods solved the problem. assorted weirdness: i have noticed that the eject command is some how defaulting to the cd burner. IE:, if i just type eject in terminal without a path to either device, it opens my cdburner by default. same goes for the KDE eject function (kdeeject). also, i can't even eject the cdrom by using the paper clip in the hole trick. ok, that's all the pertinent info i can think of that would be useful. so, if anybody has a suggestion or solution, i'm all ears. :P Chris

floyd........ we're trying to figure out if you can add "run" to the right click menu, not to the kicker menu. ya know, like if you right click a file or your desktop & one of the drop down options would be run. on that note, no luck here so far either. i also looked through many files in $/.kde/share/config but i haven't seen anything that will let you manipulate right click commands. maybe you just can't. again, if i do find a way, i'll post it here.......... Chris

hey bizkit, glad you got the first batch of problems fixed. as for the winmodem........ i use DSL, so i can't help much with modem issues. i do know that WinModems are very difficult to get working in Linux, if you can even get them working at all. the only thing i can suggest is, if you haven't done this already, go to MCC->network & internet->drakconnect & run the wizard from there & see if it detects your modem. if not, then i'd suggest starting a new thread in the hardware forum listing your specific modem problem(s), make/model of the modem, & any errors you are encountering. good luck.......... Chris

ok, i'm home............ i was slightly off as to where you set system security. to do that, go to....... MCC->security->DrakSec i'm guessing that you have might security levels set to "poor", which would allow common users more root priveledges than normal. if that's the case, then set the security level to "standard" from the drop down box where it says "security level". you can also change/set your security administrator there. i have mine set to user (me) since i'm the only user on my computer. you can set that to any user you like. also, after doing that, check the various tabs (network options, system options, periodic checks) at the top to make sure they all read "default". after that, click "ok" & try rebooting & see what the permission levels are like for each user. they should be as they are supposed to be after that, with normal users having some restrictions to files that only root can access. post back with your results........ Chris

hmmm....... every user on your system has root priveledges? well, (again) unless somebody has a better idea, check into this......... what security level are you booting into? you can find that info in one of the previous locations i pointed you to. (i think it's in drakboot???) there should be several different security levels listed. (i think it's 5???) you want to be set somewhere in the middle (level 3 or 2???) for reasonable security, but not going overboard. if security is set too low, essentially every user has root priveledges. set too high, & it's the opposite........you'll need root priveledges to do most anything. again, if nobody else chimes in until i can look at things at home, check into that for the moment. also, in userdrake, click on a listed user, click the edit button, & look in the "groups" column to see what groups that user is a member of. you can take membership of groups away from users that way, also add groups to users. if you make any changes, click the "save" button then exit. if you're unsure about things you changed it'll ask you if you wanna save the changes you made when you try to exit, so just click "no". but before dicking with that, i'd check the security levels. Chris

hi bizkit, it seems all of your problems are user/login related. it appears that you have set up for automatic login & not to show some settings & some permissions set wrong. it's nothing tragic & can be corrected easily enough. i'd suggest looking in 2 places to correct your issues.......... 1. Mandrake Control Center (aka MCC)->boot->drakboot to access MCC, you can do this....... (note: you will be asked for the root pasword to enter MCC) open a terminal-> type su hit enter type root password hit enter that will put you in root mode (it's also know as su to root in linux terminology) now type mcc hit enter that will open up MCC. go to where it says boot in the right column, then to drakboot. there you will be able to change/set different options for how your computer boots & some user settings. you can also look in the right column->system->userdrake to set some things. if all you need isn't there, do the following also. 2.in KDE (i'm assuming you're using KDE Desktop), click on the kicker icon in the lower left of the tool bar at the bottom->applications->KDE Control Center (KCC for short). look in the left hand column & go down to where it says "system". expand that tree, then go to "boot". you will have yet more options & controls for how you're computer boots & user info. you'lll need to also click the "adminstrator mode" button there & supply the root password to change things. there's also a "user" settings option in there too. i'm not on my Linux box at the moment, so i'm going from memory here, but i know i'm in the ballpark with the locations of those 2 control panels. if i'm not exactly correct, just use the kicker button & explore the various sections in there. you'll see what i'm talking about. maybe somebody sitting at their MDK/KDE box right now can be a bit more specific. if not, i'll give clearer instructions at some point tonight when i get home & can have a look at things. Chris

aze, where did you get the download for Flash from? if it's the tar.gz file from Macromedia, try this instead........... Flash RPM from the Forum downloads section that should automatically install to where it needs to be........ :D PS: uninstall (if it's a tar.gz just delete the Flash directory) you previous version of Flash first. Chris

just to let ya's know, i haven't found an easy way to manipulate the right click menu.....yet. :unsure: i've searched high & low, to no avail. i'm thinking there has to be some kind of text/conf file somehwere for those options & all you'd have to do is edit it. just haven't stumbled upon that mystery file. if i do come up with an answer (if there is an answer) i'll be sure to post it here. Chris

you won't be able to uninstall it that way since you installed it via a tar.gz file. if you wanna get rid of Moz1.6, just delete the main Mozilla install directory. not sure where that would be on your system. it's usually in /usr/lib, but it could be elsewhere, depending where you untarred the file. if you're not sure, just do a search for it. you will need to have root priveledges to delete that, so the easiest way would be to do it is in Konqueror Super User mode. (kicker->applications->file tools-file manager super user mode then root password when asked) or, you can open KDEsu via terminal, su to root, & type..... kdesu konqueror enter also, you will need to delete the hidden .mozilla directory in /home/user(you). if you don't have hidden file view enabled you won't be able to see it, so in Konqueror just click on "view" & check "show hidden files". you can delete this one as normal user, as it's in your home directory. Chris

sarah31 is correct........ if you didn't properly sym link the Java to Moz, that could be why it wasn't working. the instructions for doing that are in one of the Mozilla links i provided above. in a nutshell, you need to go to terminal->su to root> cd to /the/path/of/mozilla/plugins & type....... ln -s /path/of/your/proper/java/package/libjavaplugin_oji.so enter (substituting all of thsoe silly /words/with/ the proper paths to your respective installation directories) might be worth a shot before you get rid of Moz1.6 if you haven't gone that route yet. Chris

silverpenguin, i'm not sure how Moz1.4 is set up on the MDK9.2 cd's. i mean, i don't know if the Java is embedded & part of the install. what i would do is....... uninstall Moz1.6 beta. since it was a tar.gz installation, just delete the main Moz directory (probably /opt/mozilla) but it could be elsewhere, depending on your install path. then, delete the ./mozilla directory in your /home/(user=you) directory. then install Moz1.4 from the MDK discs & try a Java page, or just click "help" "about plug ins" & that will show what plugins are installed (java among them) if it doesn't show Java is installed, get the Sun Java rpm from the downloads section in the forum here & install that. the rpm from here works without any sym-linking or path editing. EDIT: NOTE: if you do find that you need to reinstall Java, you will also have to point any other browser you might use (IE: Konq, Opera, etc.) to your new Java installation path. Chris