Re: Fedora core 13 on Dell Vostro 3500 with i5 -- NVIDIA(R) Geforce™ 310M
by Miguel Ángel Pérez
Hello,
You'll have to give some more information. First how you installed nvidia
drivers and second what errors is throwing xorg in startup to not being able
to boot. You can use the next command in console and post/attach the output:
cat /var/log/Xorg.0.log | egrep "[E|W]{2}"
You can store it to a file this way (the last part is the path to the file):
cat /var/log/Xorg.0.log | egrep "[E|W]{2} > /tmp/xorg_errors.txt
Also you might found aditional configuration steps here:
http://forums.fedoraforum.org/showthread.php?t=204752
http://rpmfusion.org/Howto/nVidia#head-b52d8a785c3188f03b893e4f8c75f8d7e3...
Regards.
2010/10/25 Muhammad Uzair Khan <m.uzairkhan(a)gmail.com>
> hi again.
> I posted a day or two ago about my problems with trying to boot Fedora
> core 13 on a Dell vostro 3500. With help from this mailing list i
> managed to get the system installed.
>
> I tried to set my laptop to use a external monitor as well (dell), and
> had a very fuzzy output on the second (external) monitor. I installed
> nvidia-settings which asked me to install nvidia-config. Once i ran the
> nvidia.config everything went downhill from there. Now i cannot even
> boot my system (well i can get it to boot in single mode but thats about
> it).
> I have tried running Xorg -configure to generate a new xconfig.con file
> but nothing seems to be working. My laptop still gets stuck while
> booting, unless i use single mode. I am kinda sure that its a problem
> with the nvidia drivers but have no idea on what to do next.
>
> I am most grateful for any suggestions.
> regards
> khan
>
> _______________________________________________
> laptop mailing list
> laptop(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/laptop
>
--
Saludos,
Miguel Ángel Pérez
12 years, 11 months
Fedora core 13 on Dell Vostro 3500 with i5 -- NVIDIA® Geforce™ 310M
by Muhammad Uzair Khan
hi again.
I posted a day or two ago about my problems with trying to boot Fedora
core 13 on a Dell vostro 3500. With help from this mailing list i
managed to get the system installed.
I tried to set my laptop to use a external monitor as well (dell), and
had a very fuzzy output on the second (external) monitor. I installed
nvidia-settings which asked me to install nvidia-config. Once i ran the
nvidia.config everything went downhill from there. Now i cannot even
boot my system (well i can get it to boot in single mode but thats about
it).
I have tried running Xorg -configure to generate a new xconfig.con file
but nothing seems to be working. My laptop still gets stuck while
booting, unless i use single mode. I am kinda sure that its a problem
with the nvidia drivers but have no idea on what to do next.
I am most grateful for any suggestions.
regards
khan
12 years, 11 months
[SOLVED] F14: RTL 8192e WLAN driver
by Ron Leach
Neither F13 nor F14 ship with the RTL 8192e WLAN driver but, since so
many of the newer laptops and netbooks use this chipset, many of us
need the driver installed.
As a relative newbie to drivers, kernels, and sources (yes, all three
will matter), I found it a bit daunting especially since, on a clean
install (which is what many folk will use), some things that are
needed aren't there. Here's what worked for me, from a clean install
of F14 beta RC2.
There are 3 steps:
(1) Obtain the driver source
(2) Build the driver from source
(3) Install the driver and restart the machine
Everything came to life on the restart.
Step 1 Getting the driver
Realtek's site does offer a Linux driver, but for some reason my
browser wouldn't download it; I still don't know why. I managed to
obtain this file:
> rtl8192e_linux_2.6.0014.0401.2010.tar.gz
from, I think, the staging drivers from here:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f...
(click on 'snapshot' to obtain the file)
Step 2 Building the driver
I placed the gz file in a subdir 'rtl8192' in my home directory, and
extracted all the files (keeping the embedded directory hierarchy).
Then I read the README. (I did, really, because I simply didn't know
- then - what to do next. But it didn't tell me all I was to need or
do.) It said:
su
make
make install
So I did - you mustn't, you must do a couple of other things first, I
label them (2a), and (2b), below. And so I hit the first error,
something like:
'Subdirectory ...kernels/build does not exist'. (I cannot reproduce
the exact error, now, because my system now works, but after a clean
install of F14 you'll get something like that if you just do what the
README says, straightaway.)
If you look for the directory, it does exist. Sort of. It's a
symlink but, if you're new to these and use the Thunar file manager to
inspect it, it flashes very briefly and disappears. Turns out, it's a
symlink to a directory under the 'source' of 'whichever' kernel you
have had installed - but 'only' if you have the source of the kernel
installed, which you haven't, on a clean install.
2a Pre-step 2a - install the kernel source
You have to install the kernel source before you can build the
rtl8192e driver. You'll need to
(i) have an internet connection (hopefully you can use the eth0 wired
LAN port on your machine), and
(ii) you'll need to set up yum (or the graphical package manager - I
used this) to use the 'source' repository as well as the binary
repository. I don't know how to do that on the command line for yum,
so I used the graphical system and enabled the 'source' repository for
the fedora build I was using. You have to then let the package
manager download the repository index and, if you use yum, you'll have
to command it to do the same thing.
(iii) you'll need to find the kernel you're using, and select its
source for installation. Take care to choose the correct one if you
get offered a choice. On my F13 system - which was a clean install
and has not been upgraded, similar to the state yours should be in
when first trying to load the 8192e driver - there is only one kernel
listed, so it's easy to see. Select the kernel source for
installation. Don't click 'apply' just yet, though, because we need
something else installed as well.
2b Pre-step 2b - install gcc
If you just install the kernel source, the missing 'build' directory
appears, but the driver creation immediately fails again because the
machine cannot find the compiler, gcc. At least, that's the case on
my system which came from the XFCE CD which doesn't install gcc
automatically. Find gcc in the package manager, and mark it for
installation, as well. Now click 'apply', to install both the kernel
source, and the gcc compiler(s). The system will install a lot of
support files, just say OK to those. When done, we're good to go, and
can follow the instructions in the driver README
2c Driver build
In your subdirectory with the driver files that you've downloaded and
extracted, su to root
su
and type 'make'
make
There'll be a few messages, and look at them carefully to make sure
there are no errors. I didn't get any more errors but, if you do,
then don't panic, just search around the net for anything with the
[text of the error message], somebody is pretty likely to have hit
your problem before, and you'll find some ideas for getting round
them. If you cannot get round the problem. describing it on one of
the fedora lists usually turns up some very strong advice. No errors,
and we're on the last leg.
3 Install the driver
Do what the README says. Type 'make install' while still root
make install
A few more messages to look at, and we're done. Again, check for
errors. I didn't get any at this stage. I shut the machine down, and
restarted.
On restart, the machine connected automatically to a wireless network
(because way back, before I even realised I needed a driver, I'd been
trying to get wireless to work and I'd set up all the details for our
wifi APs, so it found those anyway and just connected itself. I've
since 'un-ticked' the 'connect automatically' option in network manager).
I was delighted. And very impressed that the README, and the make
files, worked as well as they did. They'd have worked perfectly,
anyway, on a fully configured development machine with kernel sources
and gcc compilers but, as I mentioned, those wouldn't normally exist
on a user's desktop machine (in my view). But getting things set up
isn't difficult, once you know what you need.
Hoping this helps others installing the 8182e driver on laptops and
netbooks.
regards, Ron
12 years, 11 months
Unable to install Fedora core 13 on Dell Vostro 3500 with i5
by Muhammad Uzair Khan
Hi,
I have been trying to install Fedora-Core 13 (live cd version) on Dell
Vostro 3500 laptop (with core i5 processor) without any luck. The laptop
boots from the live cd and then simply gets stuck. I initially thought
that there was some problem with the cd or the image, so have now wasted
around 5 cd's on various versions (the 32-bit as well as 64-bits, both
kde and gnome versions). The same problem occurs with the USB boot.
From what i can see there is some problem while attempting to boot up.
After removing the 'quiet' option from boot, what i can see is something
as follows
..
...
... [end trace...]
udevd-work[7941]: ' /sbin/modprobe -b pci:v0000d123.......' unexpected
exit with status 0x0009
[ok]
setting hostname localhost.localdomain [ok]
and before
usb_id[10371] unable to access
'/devices/pci0000.00/0000:00:1a............../input/input10/event10'
.............................
I know its not a complete report, but can any one tell if they have
tried installing fedora of this laptop? or How may i manage to install it?
Thankyou very much for your assistance.
regards
khan
12 years, 11 months
New lenovo battery won't charge (F13)
by William Henry
My brand spanking new lenovo battery (that I paid premium for because it's the only lenovo approved battery :) Won't charge past about 32%. After rebooting and powering off battery about 10 min ago I'm already down to 26%.
Is this a problem with the new battery or a problem with F13/T61 and charge calibration?
i.e. do I need to return this battery or can I do something about it with some patch or some other action?
Best,
William
13 years
