Jump to content

83mercedes

Members
  • Posts

    266
  • Joined

  • Last visited

Posts posted by 83mercedes

  1. Ya know, I'm a little disappointed. The game plays no better as far as quality or fps with these binaries than it did running with cedega. I can run it at high quality, 1028x764 and it still lurches a bit when lots of stuff is going on. Same as with cedega. I expected an improvement. This is the one game I know of that runs better in my XP partition than on linux. What's going on?

     

    P4 3.0 gHz

    1.5 gig ram

    BFG nVidia 6800 GT

  2. cybrjackle

    Hope you didn't take that like RTM, I was just pointing out that is were I grabbed the info from. ;-)

     

    lol, not at all! Even though I would have deserved it! And by the way, if I had done that on the debian mailing list, I probably would have gotten a big fat RTFM. Those guys are tough.

     

    I was literally kicking myself, cuz I know better....and besides that, you and many other good people have helped me out immensely over the past couple of years, so just

    Thanks!

  3. Right.

    But I have to ask, (since I don't know), what are these commands that cybrjackle

    refers to:

    emerge sync && emerge -uDpv system

     

    Filter through, set your USE flags and "emerge -uD system"

     

    emerge -uDpv world after that.

     

    I just did 'emerge sync' then 'emerge --update world'

    and I *think* I have updated, correct?

  4. Well then, you can do that. Debian never said it was for everyone, and it is certainly not a "beginner's" OS.

    I don't know of anybody here or elsewhere who suggests installing debian stable, except for use as a server box, or on an older machine. Check the debian users mailing list.

    Stable is too old, and not able to support newer hardware. But, once it is installed and booted you WILL be dropped into a shell.

    If your knoppix works fine, that's great, but most people I have seen are having the exact same problems as the thread starter.

    I went through it as well, and have learned to use the debian installer to install testing on my machine, and can say that the ease of installing and maintaining packages is unbeatable. There is no rpm hell here.

    To each his own.

  5. Thanks for the replies, I gave up on that 2.6.6 kernel, couldn't get nvidia to work and ran out of patience (it works fine with the 2.4.26)

    For the sound, I recompiled the original kernel and now the sound works again...

    Now I'm gonna try installing alsa.

    As for the firewall not working because iptables, that is enabled in the kernel now, and I emerged the newest iptables, but firestarter still don't see iptables.

    Looking through the gentoo forums, it seems like a common problem, I guess.

     

    One thing I noticed about gentoo, it really boots fast!

  6. Hi all, now I have gentoo installed and running with kde, using kernel 2.4.26-gentoo-r3, (the only one I could get with my lack of knowledge).

    When I realized, upon trying to run firestarter, that I didn't build the kernel to enable iptables, so I emerged kernel-2.6.6 and compiled it as per the manual, and out of the blue, /boot/grub/grub.conf was GONE, all that was left in /boot was my 'new' kernel and System.map.

    So I make a NEW /boot/grub/grub.conf and make it reflect both kernels. Reboot, and only the old kernel is listed, as if I hadn't done anything. It boots OK, but now sound is gone, (/dev/dsp is also AWOL).

    lsmod shows no emu10k1, modprobe emu10k1 gives error and won't load.

    Trying to (again) emerge emu10k1 gets message that "is only for 2.4 kernels".

    uname -r shows kernel-2.4.26-gentoo-r3, the old kernel.

    Now, the sound I can do without for now, but how the heck can I get access to that new kernel?

    Thanks, I appreciate your help. By the way, to get this far took 4 days!

    :wall:

  7. Hello forum!

    If you look around this forum, you will see my name attached to some pretty desperate posts while trying out Debian. Mostly I knew nothing at the time what I was doing, and every little thing got me. I can now say that I learned a lot while learning to have a debian install.

    I am certainly not an expert, but here are my thoughts.

     

    One thing is, it is troublesome to install Knoppix to hard drive and expect it to act as a pure debian system, because it is a mix of testing and unstable, and it can break if upgraded.

     

    Debian doesn't do everything 'automatically' the way Mandrake, SuSE and others do, for example, if you apt-get install KDE it will NOT auto install all of the other things you need to make KDE run, such as X-window-system. This was really hard for me to understand, and was one of the major problems I had months ago (see debian newbie cant get into X).

     

    Another problem for me was upgrading my system then not being patient enough to wait for the occasional broken package to be fixed. When a broken package finds it's way into the mirrors, it will be discovered almost immediately by countless users, and a bug-fix will be made rather quickly.

     

    As for the Sarge or Sid? debate, you can find lots of reasons to run Sid, (such as broken packages get fixed quicker than in sarge) but I am finding sarge, or testing, to be more reliable, and that's just my opinion. Apparently, most folks agree that Woody or stable is best left to servers (Not me saying that, just what I have seen).

     

    The new debian installer gets better every week. You no longer have to acquire the 'stable' CDs and install from those, then update with apt. You can now download 'official' testing CDs which are updated weekly, and by the way now include kde3.2 and kernel 2.6.x. See this link for how to 'jigdo' debian testing CDs:

    http://www.debian.org/CD/jigdo-cd/

    It really isn't that hard to figure out and works very well. Oh, and most folks only need the first 3,4 or 5 of the 13 CD images.

     

    If your gonna try Debian, I suggest you subscribe to the debian users mailing list

    http://lists.debian.org/

    and get really familiar with google, cuz some of the people on the list really HATE it if you post a question without trying on your own to solve it. Trust me on this!

     

    I would recommend debian now, where before I wondered "what's the attraction?"

    I now have a solid debian testing system with all the apps and games I can run in Mandrake or SuSE.

    It took a while to get it that way, but it is a learning experience!

     

    Thanks for listening...

  8. Now, using Debian testing, with kernel 2.4.25-1-386, have installed gphoto,

    (and the front end gtkam).

    So I run gtkam and it will detect my camera, however there is an error:

     

    Could not initialize camera.

     

    If I try and use kde control center >peripherals >digital camera:

     

    Unable to initialize camera. Check your port settings and camera connectivity

    and try again.

     

    I have searched, and searched, and the best I can come up with is USB

    permissions, or needing SCSI emulation.

     

    I know this can work, because it works in Mandrake.

    Any ideas are appreciated.

    Thanks.

     

    I should say that my USB printer/scanner and USB mouse work fine.

  9. Man this is fun!

    I have determined that given the opportunity, I can wreck ANY system!

    :jester:

    Anyway this time I had Debian Sid up and running perfectly, (and not the Knoppix HD install.) This one I installed from a sarge netinst cd.

    So things are going very well, I even 'rolled my own' kernel-2.6.4 and had it working, Nvida and all!! :cheesy:

    Then I decide to re-compile that kernel, to add built-in ieee1394 support, and went to install it, and it failed with:

    /usr/sbin/mkinitrd: /dev/fd does not exist, mkinitrd failed.

     

    So I figure, oh well, it will still boot off the old kernel, right?

    Nope.It wont boot at all.

    :furious3:

    Now I cannot install ANY kernel, 2.4, 2.6, or anything, they all fail with that same error above.

    I know I'm asking a lot, but how the heck do I get out of this?

    (I have tried downgrading initrd-tools and kernel-package).No luck.

    (I hope DOlson don't see this!!!) :help:

  10. This may save someone some aggravation. the SCSI generic driver and the SCSI emulation driver must be selected as modules during the Debian Woody installation.

    When I installed Debian with the "sarge netinstall" disk, (kernel-2.4.25-1-386) there was no place to select these SCSI drivers as modules. (Or ANY drivers as modules... that step wasn't there).

    So I guess I don't have SCSI emulation for my CDRW drive.

    xcdroast tells me this, and suggests installing SCSI emulation, but really doesn't tell how.

    Also, dvd::rip will not burn a CD due to being unable to open SCSI.

    The good news is, k3b-0.11.7, installed from source, burns audio and data CDs just fine.

    So I am confused, cuz I always had SCSI emulation in Mandrake, and SuSE, but not in Debian, so do I need it? If yes, is there an easy to follow tutorial on how to get it done?

    Thanks, all.

  11. 1) When you do a Knoppix HDD install, always choose debian style. Knoppix style will not work when using apt-get

    Right, Igot that.

    2) Knoppix is created from the debian "unstable" directory.... why are you fooling with testing?

    I remember hearing you should not upgrade 2 steps at a time, ie from stable to unstable, because you can get more errors that way? At any rate, the sources.list had listings for stable, testing and unstable; what I did was comment out stable and unsatble, so I could dist-upgrade one step at a time.

    Hope that makes sense....I didn't realize I was actually dist-upgrading "backwards", so to speak..

    In any case, the Debian sarge netinst disk has worked for me as an alternate method of installing Debian, so I am grateful for that

    If you look around this forum for a post called

    "debian newbie can't get into x",

    you will be amazed at the rough time I was having trying to install the "old way".

    :D

  12. Just an update, I followed cyberjackle's link in this forum entitled 'debian installer -beta3' to get where I am now, with a fully functioning (almost) Debian install of Sarge, which I then upgraded to Sid.

    Risky, I know, but what the heck?

    It seems now that what the problem is, why I originally posted this topic, is that a Knoppix hd install won't upgrade to kde3.2 without that error I said at the beginning of this, (kdelibs-data) was the offending package, but when you just install with the Debian netinstall, it will upgrade fine.

    I have been playing with it for a couple days, and there is one more problem you guys will know about- when I type 'firestarter' as root (to try and start the firewall) I get this error:

     

    debian:/home/mike# firestarter

    Xlib: connection to ":0.0" refused by server

    Xlib: No protocol specified

     

     

    (firestarter:31109): Gtk-WARNING **: cannot open display:

    debian:/home/mike#

     

    Is this a permissions thing, or what do ya think?

     

    update again,

    Found out that by typing

    xhost +

    before su'ing to root will manage this problem.

    Thanks.

    (Oh- the same thing happens when I try to start xcdroast)

×
×
  • Create New...