Jump to content

vashfish

Members
  • Posts

    16
  • Joined

  • Last visited

vashfish's Achievements

New Here

New Here (1/7)

0

Reputation

  1. I got my new motherboard. It didn't work at all. I sent that one back and got yet another one. It worked. It has a VIA chipset per one of the previous posts, and now the ATI Open GL drivers work perfectly (with kernel 2.6, no less).
  2. I got some good news... When I bought the mobo, it said "No refunds available" meaning if anything was wrong, I could only send it in for a replacement. I wished I could get a refund so I could buy a new one. When I sent it in, they were out of stock so they gave me a refund anyway! Now I'm getting an Asus board with a Via chipset. It should be here in a couple of days. I'm also waiting for a new thermal pad since the heat sink came off my processor when I was taking it off the mobo.
  3. First of all, let me say that there is something seriously wrong with my motherboard, and I'm waiting for a replacement (it crashed 3 different hard drives, one of them so badly that other computers won't even recognize it anymore). Anyway, I was using the 2.6 kernel that came with 10.0 Official. I know the ATI drivers were designed for 2.4 but, as I mentioned, they worked fine before I changed motherboards (maybe the replacement will work better). I don't want to use 2.4 because I can't stand its mouse driver. It gets very choppy even when all that's going on in the background is an instance of make. As far as your second question, the ATI drivers come with fglrxconfig which is just like the text mode X configurator plus a bunch of Radeon-specific options. In other words, it automatically generates /etc/XF86Config-4. Finally, the ATI drivers are the most recent ones from their website (as of 6/15, anyway).
  4. If only it were that easy. Do you have any idea why it might be acting like this (if only out of curiosity)?
  5. I had an old PIII 600 with an intel chipset and 2x AGP. The proprietary fglrx driver from ATI worked perfectly with MDK 10.0 and kernel 2.6.3-7mdk (I was able to play Tux Racer quite smoothly). Then I upgraded my computer to an Athlon XP 2600+ with an nForce2 chipset and 8x AGP and OpenGL stopped working. After getting a new hard drive, I decided to do a fresh install of MDK to see if that would fix it. It didn't. The installation from the RPM completes successfully with no error messages. Then I run fglrxconfig, and it also works fine. Then I reboot, and I could tell the driver changed because the visual area of the screen moved to the left (i also did an lsmod for all you sticklers :) ). Anyway, I tried one of the GL screensavers (euphoria) and it went about 1 frame every 1.5 seconds... I tried uninstalling/reinstalling it, I tried manually building it, I made absolute certain that my kernel source's .config matched my actual configuration. I even tried compiling DRI myself, all to no avail.
  6. Me too, but sometimes (like at three in the morning when my dexterity takes a vacation) it's nice be able to use chimpanzeeware... :D
  7. OK. That worked, mostly. It still asks for a password, and now, for some reason, only root can UNmount /mnt/anime...
  8. OK. I've tried all that now, and it still doesn't work properly. Here is all (AFAIK) of the relevant info: Windows XP computer: Name: anime Workgroup: NEATOPIA Simple file sharing: off Shares: C:\ = "C" (FAT32, so no security) Guest account: enabled, full permission, no password Other accounts: no password. Linux computer: Here is my /etc/samba/smb.conf (stripped of comments): [global] workgroup = NEATOPIA server string = Bob (Linux) printcap name = cups load printers = yes printing = cups printer admin = @adm log file = /var/log/samba/log.%m max log size = 50 map to guest = bad user security = share encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd username map = /etc/samba/smbusers socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = no [homes] comment = Home Directories browseable = no writable = yes [anime] path=/mnt/anime guest ok = yes writeable = yes [printers] comment = All Printers path = /var/spool/samba browseable = no # to allow user 'guest account' to print. guest ok = yes writable = no printable = yes create mode = 0700 print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers. [print$] path = /var/lib/samba/printers browseable = yes write list = @adm root guest ok = yes inherit permissions = yes [pdf-generator] path = /var/tmp guest ok = No printable = Yes comment = PDF Generator (only valid users) print command = /usr/share/samba/scripts/print-pdf %s ~%u //%L/%u %m %I "%J" & Here is my /etc/samba/smbusers root = administrator admin vash = Guest nobody = guest pcguest smbguest I used smb -n vash to remove vash's password. Also, the permissions/owners for /mnt/anime are "rwxrwxrwx nobody nogroup" Given all of this, here is a transcript (note it is almost identical to the previous one, except that this time it has smb.conf): [root@bob samba]# mount /mnt/anime Password: [root@bob samba]# ls /mnt/anime AUTOEXEC.BAT* CONFIG.SYS* MSDOS.SYS* RECYCLER/ Backups/ Documents and Settings/ NTDETECT.COM* System Volume Information/ BIOSID.TXT* Downloads/ ntldr* WINDOWS/ boot.ini* hiberfil.sys* pagefile.sys* WUTemp/ cabs/ IO.SYS* Program Files/ [root@bob samba]# umount /mnt/anime [root@bob samba]# exit exit [vash@bob vash]$ mount /mnt/anime Password: cannot mount on /mnt/anime: Operation not permitted smbmnt failed: 1 [vash@bob vash]$ /sbin/mount.smbfs3 //anime/c /mnt/anime Password: cannot mount on /mnt/anime: Operation not permitted smbmnt failed: 1 Finally, here is the relevant line from /etc/fstab: //anime/c /mnt/anime smbfs user,username=Guest,noauto,suid,exec,umask=0 0 0 So, I'm now back at the beginning. vash can't mount /mnt/anime, and I also have the new problem that it asks for a password (even for root). If there is any more information that would be helpful, let me know...
  9. I've got a slightly bigger problem now... I wanted to see if reinstalling samba would fix it. I went to the package manager and removed all of the samba packages (server, client, kde front-end). Then, in my infinite wisdom, I decided to remove all the files in /etc/samba/ and reinstalling samba didn't put any of them back... Anyway, I ran the samba mount utility in MCC, and it seemed to set it up OK. However, I have three problems now. 1: (from before) Only root can mount /mnt/anime (see excerpt below). 2: it isn't causing any immediate problems, but I'm sure the fact that smb.conf and others are missing can't help any, and 3: it asks me for a password (root or otherwise) even though the host computer (win XP) doesn't require one. [vash@bob /]$ su Password: [root@bob /]# mount /mnt/anime params.c:OpenConfFile() - Unable to open configuration file "/etc/samba/smb.conf": No such file or directory Can't load /etc/samba/smb.conf - run testparm to debug it Password: [root@bob /]# ls /mnt/anime AUTOEXEC.BAT* CONFIG.SYS* MSDOS.SYS* RECYCLER/ Backups/ Documents and Settings/ NTDETECT.COM* System Volume Information/ BIOSID.TXT* Downloads/ ntldr* WINDOWS/ boot.ini* hiberfil.sys* pagefile.sys* WUTemp/ cabs/ IO.SYS* Program Files/ [root@bob /]# umount /mnt/anime [root@bob /]# exit exit [vash@bob /]$ mount /mnt/anime params.c:OpenConfFile() - Unable to open configuration file "/etc/samba/smb.conf": No such file or directory Can't load /etc/samba/smb.conf - run testparm to debug it Password: cannot mount on /mnt/anime: Operation not permitted smbmnt failed: 1 [vash@bob /]$
  10. Success! (kind of). The excerpt from /var/log/messages I quoted above gave me an interesting clue: it used ifplugd instead of ifup. After a half an hour of newbieish wanderings through /etc, I finally came across /etc/init.d/network. It had the following: if [ "${DEVICE:0:3}" != "eth" -o ${DEVICE/:/} != ${DEVICE} -o ! -x /sbin/ifplugd ] || grep -q '^MII_NOT_SUPPORTED=yes' ifcfg-$i; then action "Bringing up interface %s: " $i ./ifup $DEVICE $boot else IFPLUGD_ARGS="${IFPLUGD_ARGS=-w -b}" action "Bringing up interface %s: " $i /sbin/ifplugd $IFPLUGD_ARGS -i $DEVICE fi Naively, I commented the whole thing out except for the line in the first if clause. To my amusement, it actually worked. Of course, that is probably not the best way to fix this problem, and I would be very interested to know what was causing it in the first place. But, for now, I don't have to open up a terminal every time I start up my computer just to go online...
  11. Well, you are partially correct. I am using a cable modem. However, it is always on. Also, it is hooked through a wireless router, so it always thinks there is an active connection, so this is unlikely to be the cause.
  12. No. Just a plain old RJ-45. The main thing that makes this weird is the fact that ifup eth0 from the command line works just fine. I even tried the hack from RedHat 9.0 and above where you put check_link_down() { return 1; } in /etc/sysconfig/network-scripts/ifcfg-eth0
  13. I'm trying to make it so that users have r/w access to samba mounts. No matter how I configure it, either mount complains about bad permissons, or smbmount says "Operation not permitted" when a user tries to mount the partition. If I mount it as root, no users have write access. Here is the line from fstab: //anime/c /mnt/anime smbfs user,credentials=/etc/samba/auth.anime.administrator,suid,exec,umask=0,noauto 0 0 I made sure that there were read permissions on /etc/samba/auth.anime.administrator. I'm not sure how to configure the other files in the samba directory, though.
  14. Well, it turns out that using the 2.6 kernel put the mouse back the way it was originally. It uses the Universal->Any PS/2 or USB Mouse driver instead of the PS/2->Automatic driver. As far as the ethernet thing goes, here is a quote from /var/log/syslog: Jun 2 06:31:00 bob ifplugd(eth0)[931]: ifplugd 0.21b initializing. Jun 2 06:31:00 bob ifplugd(eth0)[931]: Using interface eth0/00:60:97:B9:35:29 with driver <3c59x> (version: LK1.1.19) Jun 2 06:31:00 bob ifplugd(eth0)[931]: Using detection mode: SIOCGMIIPHY Jun 2 06:31:00 bob ifplugd(eth0)[931]: Initialization complete, link beat not detected. Jun 2 06:31:00 bob network: Bringing up interface eth0: failed Also, at this point--I intend to change this once I make sure some other programs are going to work--I don't have a subscription to MandrakeClub so I can't get the updates.
×
×
  • Create New...