Awesome how to:
http://suseforums.net/index.php?showtopic=36351
Peace.
Showing posts with label opensuse. Show all posts
Showing posts with label opensuse. Show all posts
Monday, September 3, 2007
Tuesday, August 14, 2007
Even Microsoft's mice are stupid!
For some reason the forward and back buttons on my Microsoft Intellimouse don't automatically work with my OpenSuSE 10.2 distro. So all you do to fix this is:
edit /etc/X11/XF86Config
and add a line under this section:
Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "7"
Option "Device" "/dev/input/mice"
Option "Name" "Microsoft IntelliMouse Optical"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7" #ADD THIS LINE
EndSection
Also, just as a small side note. Be sure to save a backup of XF86Config before making any changes so you don't mess something up and have to reinstall your OS (speaking from personal experience).
And I bid you all - a good day.
edit /etc/X11/XF86Config
and add a line under this section:
Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "Buttons" "7"
Option "Device" "/dev/input/mice"
Option "Name" "Microsoft IntelliMouse Optical"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
Option "ButtonMapping" "1 2 3 6 7" #ADD THIS LINE
EndSection
Also, just as a small side note. Be sure to save a backup of XF86Config before making any changes so you don't mess something up and have to reinstall your OS (speaking from personal experience).
And I bid you all - a good day.
Wednesday, June 27, 2007
Wireless on OpenSuSE 10.2 with Broadcom
Once again fighting the good fight and trying to get this chipset to work properly with OpenSuSE 10.2.
As always thanks to this skittle loving guy's website: http://nextgen.no-ip.org/~andrew/linux/ndiswrapper/ndiswrapperinfo-gui.php for not only explaining the process but having an explanation that was even specific to OpenSuSE 10.x (and in my case 10.2).
In addition to his instructions I would add not to use ndisgtk, just run the commands manually (as superuser of course):
'ndiswrapper -i bcmwl5a.inf'
'modprobe ndiswrapper'
And furthermore I took these steps to not only ensure a working card, but also have it accurately show link/signal quality and load at boot:
edit /etc/modprobe.d/ndiswrapper and add change 'wlan0' to 'eth1'
and
edit /etc/init.d/network adding 'modprobe ndiswrapper' somewhere in the beginning
**Added 14Aug07*** Make sure to configure the wireless device in YaST. Do not use the pre-configured card, make a new wireless device.
I will also mention that when I list installed ndiswrapped windows drivers I do get this annoying output: ndiswrapper -l
bcmwl5a : driver installed
device (14E4:4318) present (alternate driver: bcm43xx)
However as far I as can tell it seems to make no difference what-so-ever. In addition, I tried to correct this output by blacklisting 'bcm43xx' to which my computer said it was then 'ignoring blacklist rule bcm43xx' or something that effect. So whatever.
Do I absolutely now how what I did affected my computer? Absolutely not. Does my wireless start at boot and work with accurate link/signal quality? Yes.
As always thanks to this skittle loving guy's website: http://nextgen.no-ip.org/~andrew/linux/ndiswrapper/ndiswrapperinfo-gui.php for not only explaining the process but having an explanation that was even specific to OpenSuSE 10.x (and in my case 10.2).
In addition to his instructions I would add not to use ndisgtk, just run the commands manually (as superuser of course):
'ndiswrapper -i bcmwl5a.inf'
'modprobe ndiswrapper'
And furthermore I took these steps to not only ensure a working card, but also have it accurately show link/signal quality and load at boot:
edit /etc/modprobe.d/ndiswrapper and add change 'wlan0' to 'eth1'
and
edit /etc/init.d/network adding 'modprobe ndiswrapper' somewhere in the beginning
**Added 14Aug07*** Make sure to configure the wireless device in YaST. Do not use the pre-configured card, make a new wireless device.
I will also mention that when I list installed ndiswrapped windows drivers I do get this annoying output: ndiswrapper -l
bcmwl5a : driver installed
device (14E4:4318) present (alternate driver: bcm43xx)
However as far I as can tell it seems to make no difference what-so-ever. In addition, I tried to correct this output by blacklisting 'bcm43xx' to which my computer said it was then 'ignoring blacklist rule bcm43xx' or something that effect. So whatever.
Do I absolutely now how what I did affected my computer? Absolutely not. Does my wireless start at boot and work with accurate link/signal quality? Yes.
Monday, March 26, 2007
Correction...
On my last post I mentioned how quote "Linux working = No money for MS". Due to recent news I should now post a correction.
Because the machine I was posting about is using OpenSUSE (by Novell) and Novell was just bought out by Microsoft then my logic no longer stands.
Let's now go with: Non-Novell Distro's of Linux working = No money for MS.
Thanks to Eric for his copy of The Wall Street Journal's article publicizing the whole event.
Did I mention I was only like 4 or 5 months late on this story?
Because the machine I was posting about is using OpenSUSE (by Novell) and Novell was just bought out by Microsoft then my logic no longer stands.
Let's now go with: Non-Novell Distro's of Linux working = No money for MS.
Thanks to Eric for his copy of The Wall Street Journal's article publicizing the whole event.
Did I mention I was only like 4 or 5 months late on this story?
Thursday, March 22, 2007
WTF.
Seriously, WTF?
I decided to try using ndiswrapper to get my wireless working on my openSUSE 10.2 machine. Pain in the ...
It works, but for some god-forsaken reason it thinks the wireless card is an ethernet card and shows it as eth1 vs. wlan0.
To install the driver and use ndiswrapper I followed this gents page. Very nice page, excellent info, but it doesn't say one thing about having to reboot your computer to have it recognize your wireless card (which of course is true in my case). You should be able to just modprobe ndiswrapper as far as I understand. WTF. Then I followed some other helpful fellow's instructions on using bcm43xx-fwcutter in order to get my Broadcom wireless card to show up as wlan0 -- no dice. I even blacklisted bcm43xx in /etc/modprobe.d/blacklist (I think that's it) as another gent had mentioned still to no avail!
OpenSUSE vs. Broadcom -- Broadcom wins. OpenSUSE got in some excellent blows by being able to actually connect to the net, but Broadcom dominated the battle by never submitting to wlan0. Hope you didn't have money riding on that fight.
Whatever...
I'm so tired of screwing with it that as long as I have wireless I don't care. As far as I'm concerned I win.
The transitive property: a=b=c so a=c. My version:
Linux working = Not using MS Windows which = MS doesn't get my Money
so...
Linux working = No money for MS
Hooray for Linux. Job well done.
I decided to try using ndiswrapper to get my wireless working on my openSUSE 10.2 machine. Pain in the ...
It works, but for some god-forsaken reason it thinks the wireless card is an ethernet card and shows it as eth1 vs. wlan0.
To install the driver and use ndiswrapper I followed this gents page. Very nice page, excellent info, but it doesn't say one thing about having to reboot your computer to have it recognize your wireless card (which of course is true in my case). You should be able to just modprobe ndiswrapper as far as I understand. WTF. Then I followed some other helpful fellow's instructions on using bcm43xx-fwcutter in order to get my Broadcom wireless card to show up as wlan0 -- no dice. I even blacklisted bcm43xx in /etc/modprobe.d/blacklist (I think that's it) as another gent had mentioned still to no avail!
OpenSUSE vs. Broadcom -- Broadcom wins. OpenSUSE got in some excellent blows by being able to actually connect to the net, but Broadcom dominated the battle by never submitting to wlan0. Hope you didn't have money riding on that fight.
Whatever...
I'm so tired of screwing with it that as long as I have wireless I don't care. As far as I'm concerned I win.
The transitive property: a=b=c so a=c. My version:
Linux working = Not using MS Windows which = MS doesn't get my Money
so...
Linux working = No money for MS
Hooray for Linux. Job well done.
Subscribe to:
Posts (Atom)