Jump to content

JonEberger

Members
  • Posts

    625
  • Joined

  • Last visited

Everything posted by JonEberger

  1. when i did the network install last night for mandriva 2006, i chose the helios.__.utk mirrors and i got kde 3.5 with it. it's super smooth.
  2. JonEberger

    Webcams

    this is actually a really good thread. i know that earlier this summer i tried to make an old intel webcam work and it was "flakey' at best.
  3. hey guys. thanks for the comments. i got an easy fix on accident. i was sitting around running 2005 LE and figured, well, i've been wanting to get 2006 and give it a shot. if i've got issues, i'll have them there anyways and so i'll be troubleshooting there. so i got the images and did a net install. from there, the card worked both with ndiswrapper and then when i got the ipw2100 drivers/firmware, it worked with those too. that's a really sucky fix, but it's still a fix. thanks for the comments y'all.
  4. more information. here are the results of "dmesg | grep ndiswrapper' ndiswrapper version 1.0 loaded (preempt=no, smp=no) ndiswrapper: driver w70n51 (Intel, 07/31/2003, 1.2.0.58) added ndiswrapper: using irq 5 wlan0: ndiswrapper ethernet device 00:04:23:4b:5c:94 driver using w70n51 'lspci' gives 02:03.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) 'ndiswrapper -l' gives Installed ndis drivers: w70n51 driver present, hardware present
  5. hi everyone. me again asking yet another wireless network question. so the card i have in a laptop is an intel pro wireless 2100. doing an "lscpi" tells me that it's actually the 3b revision. mandriva comes with the ipw2100 driver but for some reason cannot activate the card. (perhaps this should've been a first tip of difficulties.) so after spending some amount of time with it (being recognized as eth1, but not activating the card), i give up and decide to use the ndiswrapper. so i go and get the proper windows driver (verified by intel and actually used by others on linux-laptop to make their nic work) and give the old "ndiswrapper -i driver name'. ndiswrapper was urpmi'd and so no compilation was needed. i then give 'ndiswrapper -l' and see that the proper drivers are loaded and the hardware is recognized and functioning. i modprobe ndiswrapper, add the appropriate alias to modprobe.conf and in modprobe.preload add an ndiswrapper command. further i go and allow the aliased nic to get through the firewall and then create the ifcfg-wlan0 in /etc/sysconfig/network-scripts. when i pipe dmesg to grep and look for ndiswrapper i get no warnings. the irqs are assigned and i know that ndiswrapper uses the appropriate drivers. everything seems to be fine. all the wireless-tools are installed btw. when i give the 'iwlist wlan0 scan' command i can see every wireless network around me. (at this point i thought i was in total business.) but i cannot obtain an ip address from any router. i've totally unsecured routers and cannot pull the ip. i set the essid and the channel, but on either an "ifup wlan0' command or 'dhclient wlan0' command, the nic will not obtain that address. i know the nic sends the request. what am i overlooking? i always need all the help i can get. anyone?
  6. what a rough article by a inux not-even-newbie. he is a complete suse fan too. don't get me wrong, suse is a good distro, but geez...i don't know that it's the standard either. arctic, i'm with you on the globe. i think it's a similar icon for it in fc4.
  7. i started either my sophomore or junior year of college. that would make me probably 19 or 20. i can't really remember whether it was because of a course that i was taking in my computer science curriculum or because it was installed in a computer lab on campus. either rate, i learned it when redhat 6.0 was out. but i first installed (on my home pc) mandrake 7.0. (in fact, i found that disc two days ago.) i know run linux on at least 4 pcs now and love it. i loathe windows and try to avoid it at all costs. im no "guru" (see other threads), but i enjoy the linux.
  8. here lately, gui as a complete last result. what i do believe is that there should be an excellent gui for every command so that everyone who is new to the linux world.
  9. so i love me some mandriva. but that' s not to say i don't like others also. i recently installed an OLD version of fedora core. 3 i think. it's smooth and pretty fast. it's also pretty. the default choices for everything are unobtrusive and clean. the biggest thing i don't like about 2005 (haven't given 2006 a shot yet) is the freaky penguin with stars in his eyes. i installed ubuntu a while back. it's clean and nice. apt is a wonderful application. the problem for me was that i just didn't have time to learn where files get placed when i already know them somewhere else. i gave pure debian a try a while ago on a laptop. it was my first foray into a non-rpm-based linux. it was clean and simple to use. suse is pretty too. the personal ed's are super slick. esp. if you're trying to push a windows friend into a linux. it works well.
  10. i went with junior. i'd be a weak junior. i've been using linux now for maybe 6 or 7 years. i know how to get around pretty well and see what's going on. i know how to change/edit files that i need to edit and can learn how to as that comes up. i need to experiment more and just in general be more of a "power-user". i still need to ask alot of questions and still do, hence my membership here. cheers to those seniors and up. you guys rock.
  11. has 2006 really improved support that much for windows modems? if so, i'd be convinced to switch.....now.
  12. i like kate bc i can have "projects" open. i haven't tried it on kwrite. i like quanta bc it auto-completes the tags for me. period. that's it. sometimes the ability to preview a page is nice. but not necessary at all. i like nedit. how do you get it to open separate documents on firefox-style tabs?
  13. i just posted (dumbly) to the old thread that ian gave about how to do it. i don't do it in a "slick" fashion. but it gets done. mine does involve editing the .xinitrc file. but that's pretty easily done from command-line with vi or anything else.
  14. so i know this is months behind the last reply but all my stuff is in the .xinitrc file. if you do exec (insert name of window manager of choice) or for KDE it's actually just startkde it works great. so for instance my .xinitrc is exec fluxbox and that's it. so to add those window manager (wmaker, enlightenment, etc.) just do a urpmi (name of wm to install)
  15. i've not given 2006 a try yet. don't quite have the time. but 2005 is still running like a clock for me.
  16. welcome to the board coffee! what type of hardware component are these two that you have mentioned?
  17. i have a d-link dl-514 which is the router that i want to pull the ip from my netgear. so the sequence that i'd love would be my computer-----[dl-514]-------(via wireless)--------[netgear router].
  18. that's exactly what i needed ian. i didn't know if there was any kind of an option that is deeply hidden which no one knows how to access or not.
  19. is there some way that i can set up a wireless router to pull an ip from another wireless router wirelessly? if this were between two computers, i would call this ad-hoc.... it would be absolutely beautiful if i could use my old router for this purpose. the goal would then be to set my old router to pull an ip (wireless) from my new router. i wouldn't be rebroadcasting anything, but i would have my box connected to the old router via cat 5. seems like a cool idea.
  20. postfix and sendmail are probably the two most widely used email servers that i know of. i'm sure there are others. i would imagine that having either some kind of a dynamic dns service or a static ip would be necessary though. i don't know. i've never done that before. but for local stuff, who cares? just set it up using internal addresses.
  21. uname -a will tell you that and more. just do a man uname.
  22. i think it's kinda nice. i didn't get kubuntu, but i was impressed (aesthetically) with the themes and such. i enjoyed apt-get, and i always enjoying seeing where different distros put their stuff. it picked up hardware well.
  23. if you can hit non-processor hardware as ^^^ mentions then this could defintely help. if you've got an nvidia card in that laptop, you'll be pleased by the nvidia drivers. i don't knwo about ati. an i686 optimized kernel might be a great idea. or even one that you build for your laptop. in other words, basically what gowator said.
×
×
  • Create New...