•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the *nix Hardware Configuration section within the Tech Talk category of DaniWeb, a massive community of 456,420 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,623 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our *nix Hardware Configuration advertiser: Lunarpages Linux Web Hosting
Views: 5206 | Replies: 12
 |
•
•
Join Date: Jul 2004
Posts: 89
Reputation: 
Rep Power: 5
Solved Threads: 0
Junior Poster in Training
Howdy,
I am a novice linux user, who recently tried to configure my wireless cards to work on a dual boot system of opensuse 10.2 and winxp.
The problem:
Suse 10.2 fails to boot correctly after the configuration of my wireless cards.
After GRUB loads, it doesn't matter if I try to start suse 10.2 or suse 10.2 (failsafe), suse cannot load.
It stops after it says:
The situation:
I got suse 10.2 and winxp dual booting on my system. I have two different wireless cards:
D-Link AirPlus G DWL-G510 Wireless PCI Card (revision A I think)
NETGEAR WG111 802.11g Wireless USB2.0 Adapter (version 1)
Both work on winxp.
After following these instructions:
http://nextgen.no-ip.org/~andrew/lin...rapperinfo.php
on how to setup ndiswrapper in order to use my winxp drivers to wirelessly connect to my router -- I have successfully installed the wrapper and verfied that my drivers were correctly installed using the: command.
After that, I start up Yast and attempt to configure my network (using the instructions as a guide). I could not configure my network properly. It was late, and I shut down my computer and resigned to finish troubleshooting the next day.
Next day, I have the bootup problems. I tried putting the dvd I used to install suse and use the "rescue system" option, but it goes straight to the rescue command-line which I am unfamiliar.
Any help is sincerely appreciated.
-Isaac
I am a novice linux user, who recently tried to configure my wireless cards to work on a dual boot system of opensuse 10.2 and winxp.
The problem:
Suse 10.2 fails to boot correctly after the configuration of my wireless cards.
After GRUB loads, it doesn't matter if I try to start suse 10.2 or suse 10.2 (failsafe), suse cannot load.
It stops after it says:
enabling syn flood protection done disabling ip forwarding done setting up hostname 'linux-ntvr' done setting up loopback interface done
The situation:
I got suse 10.2 and winxp dual booting on my system. I have two different wireless cards:
D-Link AirPlus G DWL-G510 Wireless PCI Card (revision A I think)
NETGEAR WG111 802.11g Wireless USB2.0 Adapter (version 1)
Both work on winxp.
After following these instructions:
http://nextgen.no-ip.org/~andrew/lin...rapperinfo.php
on how to setup ndiswrapper in order to use my winxp drivers to wirelessly connect to my router -- I have successfully installed the wrapper and verfied that my drivers were correctly installed using the:
ndiswrapper -l
After that, I start up Yast and attempt to configure my network (using the instructions as a guide). I could not configure my network properly. It was late, and I shut down my computer and resigned to finish troubleshooting the next day.
Next day, I have the bootup problems. I tried putting the dvd I used to install suse and use the "rescue system" option, but it goes straight to the rescue command-line which I am unfamiliar.
Any help is sincerely appreciated.
-Isaac
"Success is peace of mind
which is a direct result of self-satisfaction
in knowing you did your best to become the best
that you are capable of becoming."
~John Wooden
which is a direct result of self-satisfaction
in knowing you did your best to become the best
that you are capable of becoming."
~John Wooden
•
•
Join Date: Apr 2006
Location: Canada
Posts: 4,534
Reputation: 
Rep Power: 17
Solved Threads: 283
It's rather odd the way the system freezes without an error message. Perhaps there's one in the logs.
When you get to the recovery console, try typing the following:
Another good one is
See if there's any odd error messages that would relate to the freezing at startup. (Or you could just post anything suspicous-looking here.)
When you get to the recovery console, try typing the following:
dmesg | more
Another good one is
syslog
See if there's any odd error messages that would relate to the freezing at startup. (Or you could just post anything suspicous-looking here.)
tuxation.com - Linux articles, tutorials, and discussions
•
•
Join Date: Jul 2004
Posts: 89
Reputation:
Rep Power: 5
Solved Threads: 0
Junior Poster in Training
Thanks for the input.
Hmm... I can't seem to use either command...
Ok, so I put the dvd in, I boot using the "rescue system" option, the console shows up stating:
I type in my typical username, it asks for the password, I enter it, it does not work.
so then I am queried for a login again. This time I enter "root" and then it immediately brings me to:
I guess that means I am logged in as root?
However when I try both the
or the commands, it just states that these are not valid commands...
Any ideas?
-Isaac
Hmm... I can't seem to use either command...
Ok, so I put the dvd in, I boot using the "rescue system" option, the console shows up stating:
rescue login:
I type in my typical username, it asks for the password, I enter it, it does not work.
so then I am queried for a login again. This time I enter "root" and then it immediately brings me to:
Rescue:~#
I guess that means I am logged in as root?
However when I try both the
dmesg | more
syslog
Any ideas?
-Isaac
•
•
•
•
Originally Posted by joeprogrammer 
It's rather odd the way the system freezes without an error message. Perhaps there's one in the logs.
When you get to the recovery console, try typing the following:
dmesg | more
Another good one is
syslog
See if there's any odd error messages that would relate to the freezing at startup. (Or you could just post anything suspicous-looking here.)
"Success is peace of mind
which is a direct result of self-satisfaction
in knowing you did your best to become the best
that you are capable of becoming."
~John Wooden
which is a direct result of self-satisfaction
in knowing you did your best to become the best
that you are capable of becoming."
~John Wooden
•
•
Join Date: Apr 2006
Location: Canada
Posts: 4,534
Reputation:
Rep Power: 17
Solved Threads: 283
•
•
•
•
Originally Posted by Soral 3.0
Hmm... I can't seem to use either command...
I can't quite think of why the startup wouldn't work... what happens if you leave the frozen startup screen for like 3 hours or something?
tuxation.com - Linux articles, tutorials, and discussions
•
•
Join Date: Jul 2004
Posts: 89
Reputation:
Rep Power: 5
Solved Threads: 0
Junior Poster in Training
•
•
•
•
Originally Posted by joeprogrammer
Nevermind. Those commands won't do much good anyway, as they're only useful when run from the originating hard disk.
I can't quite think of why the startup wouldn't work... what happens if you leave the frozen startup screen for like 3 hours or something?
Well, I can't say I've counted, but I have tried just letting the dead compy sit on the startup screen for at least, say 30 minutes. It just sits there like... a dead compy.
Anyhow, do you have anymore suggestions on what I should do (or what I shouldn't do) before I resort to reinstalling suse? I was planning on that, but I'd thought I would come in here and ask for any opinions before I lose what little files I have on linux...
Also, did I do anything bad during the install of ndiswrapper+wireless drivers that could have caused t his?
-Isaac
Last edited by Soral 3.0 : Feb 23rd, 2007 at 6:15 pm.
"Success is peace of mind
which is a direct result of self-satisfaction
in knowing you did your best to become the best
that you are capable of becoming."
~John Wooden
which is a direct result of self-satisfaction
in knowing you did your best to become the best
that you are capable of becoming."
~John Wooden
•
•
Join Date: Apr 2006
Location: Canada
Posts: 4,534
Reputation:
Rep Power: 17
Solved Threads: 283
•
•
•
•
Originally Posted by Soral 3.0
Anyhow, do you have anymore suggestions on what I should do (or what I shouldn't do) before I resort to reinstalling suse? I was planning on that, but I'd thought I would come in here and ask for any opinions before I lose what little files I have on linux...
•
•
•
•
Also, did I do anything bad during the install of ndiswrapper+wireless drivers that could have caused t his?
Another thing you may want to try is only installing wireless cards one at a time; I've read that multiple wireless cards in the same computer can have problems (although that's unlikely to be the case, still do everything step-by-step; don't rush it).
tuxation.com - Linux articles, tutorials, and discussions
•
•
Join Date: Jul 2004
Posts: 89
Reputation:
Rep Power: 5
Solved Threads: 0
Junior Poster in Training
Those suggestions make a lot of sense. :-)
Allrighty then, thanks for your help, and wish me luck!
-Isaac
Allrighty then, thanks for your help, and wish me luck!
-Isaac
•
•
•
•
Originally Posted by joeprogrammer
No, I can't really think of much that you might have done wrong, although I can't say I saw you installing it, so there's always that possibility...
My theory is that there's something wrong with the kernel version. Next time try upgrading your kernel first. Once you're sure that's working, install ndiswrapper.
Another thing you may want to try is only installing wireless cards one at a time; I've read that multiple wireless cards in the same computer can have problems (although that's unlikely to be the case, still do everything step-by-step; don't rush it).
"Success is peace of mind
which is a direct result of self-satisfaction
in knowing you did your best to become the best
that you are capable of becoming."
~John Wooden
which is a direct result of self-satisfaction
in knowing you did your best to become the best
that you are capable of becoming."
~John Wooden
•
•
Join Date: May 2006
Location: Bellevue, WA
Posts: 1,548
Reputation:
Rep Power: 8
Solved Threads: 51
I think if you boot into your rescue mode and then mount and chroot to your install, then you'll be able to use dmesg and syslog. I can never remember how to chroot though, so you'd have to look around for instructions on that.
•
•
Join Date: Apr 2006
Location: Canada
Posts: 4,534
Reputation:
Rep Power: 17
Solved Threads: 283
•
•
•
•
Originally Posted by Infarction
I think if you boot into your rescue mode and then mount and chroot to your install, then you'll be able to use dmesg and syslog. I can never remember how to chroot though, so you'd have to look around for instructions on that.
chroot /mnt/volume /bin/bash
And to get out of the chrooted environment, simply type
exit, and you'll be back at the original prompt. tuxation.com - Linux articles, tutorials, and discussions
•
•
Join Date: May 2006
Location: Bellevue, WA
Posts: 1,548
Reputation:
Rep Power: 8
Solved Threads: 51
you'll want to bind /dev and create a /proc somewhere inside the chroot environment as well before you actually enter it. Might be handy to copy DNS information as well if your 'net is working from the rescue boot...
|
•
•
•
•
•
•
•
•
DaniWeb *nix Hardware Configuration Marketplace
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Linear Mode
•
•
•
•
amd apple chips console core data development drivers entertainment environment fedora free graphics hardware ibm infrastructure intel iphone ipod laptop laser law linux logitech memory mice microsoft mobile mouse news nintendo novell patents pc peripherals printer processor research science security sony storage suse technology toshiba tv usb via web wireless
- Previous Thread: Scroll wheel in Puppy Linux
- Next Thread: How To Configure Ntp (time Server) On Red Hat
