I am using a new Dell Latitude E6500.
Video Card is an NVIDIA Quadro NVS 160M
I believe it is a 256MB card.
I just installed my first drivers with ndiswrapper to get the system to recognize my wireless chip. Am I going to have to do something similar for this situation?
Basically, the system boots up with an odd resolution. It looks very late 90’s. YaST > Hardware > Graphics Card and Monitor reveals:
Card: VESA Framebuffer Graphics
Monitor: i set this personally to 1440 x 900 because thats what my actual monitor is. it was set to something lower initially. changing this setting earned me an error message about how something wasn’t supported.
the resolution defaults to 800x600 SVGA with 16-bit color.
I spent a very long time getting my system to recognize my wireless card. I tried updating the kernel at first, didnt work. then i realized a ton of stuff was wrong with my installation, so i reinstalled openSUSE. i was told not to update the kernel this time. it is all documented in the first 3 pages here…
linux-34ss:/home/music # sudo zypper ref
Repository ‘Updates for 11.0’ is up to date.
Repository ‘openSUSE-11.0-Non-Oss’ is up to date.
Repository ‘openSUSE-11.0-Oss’ is up to date.
Repository ‘11.0’ is up to date.
All repositories have been refreshed.
linux-34ss:/home/music # sudo zypper lu
Reading installed packages…
Warning: These are only the updates affecting the updater itself.
Other updates are available too.
Repository | Name | Version | Category | Status
Updates for 11.0 | PackageKit | 139 | recommended | Needed
Updates for 11.0 | libzypp | 53 | recommended | Needed
Updates for 11.0 | yast2-ncurses-pkg | 83 | recommended | Needed
Updates for 11.0 | zypper | 114 | recommended | Needed
the third zypper command returned a huge amount of output. here’s a synopsis…
linux-34ss:/home/music # sudo zypper up
Reading installed packages…
The following packages are going to be upgraded:
satsolver-tools libzypp yast2-pkg-bindings zypper yast2-ncurses-pkg
The following NEW patches are going to be installed:
PackageKit zypper yast2-ncurses-pkg libzypp
Overall download size: 3.0 M. After the operation, additional 21.0 K will be used.
Continue? [YES/no]: yes
Installing: yast2-ncurses-pkg-2.16.14-0.2 [done]
Warning: One of installed patches affects the package manager itself, thus it requires its restart before executing any further operations.
i dont know what that means, so i’m going to restart my computer. brb.
When you run those commands again, you should get a lot of updates
including the kernel which by the sounds of it you don’t want to
update? Else do you need to run through all the commands you did last
time to get the wireless to work?
i’m not sure i understand. i need to run the three zypper commands again? i have no problem with updating the kernel, as long as it won’t mess up the wireless driver that i used ndiswrapper to install.
ok, i guess a have a couple questions though (very new to linux). when i first installed openSUSE 11, as part of a dual-boot with vista, neither my wireless or my graphics card were properly recognized. i heard tons of rumors that all i needed to do was update the kernel to 2.6.27, so i did. and it was a ton of work, and it didnt help my wireless or graphics card. in fact, it shutdown my LAN.
i ended up reinstalling from DVD (had used liveCD originally), and instead, solved the wireless issue by using ndiswrapper.
why cant i use ndiswrapper to fix my graphics card as well?
why would updating the kernel undo my work fixing my wireless?
ndiswrapper is that a ndis wrapper around/using the windows sys and
inf files to activate your wirelss and nothing to do with graphics
There is however an ndiswrapper kernel module. If you use YaST and
the software management, search on ndis and you will see a
ndiswrapper-kmp-(your kernel type) is installed. Update the kernel and
that will get updated too
I see there are also a couple of GUI tools you can use to install as
well, but I digress…
I would imagine it should just work, but you never know I would
wait a day, as it looks like there is a new kernel out so it will need
to propagate to the mirrors, unless you see it 188.8.131.52-0.2.