Re: nvidia way versus debian way of installing nvidia 3D graphics drivers in Lenny..

2008-04-13 Thread Dean Hamstead
you want the debian way definitely. rogue files in /lib etc will only 
cause you headaches in the future.


Dean

Simon Vos wrote:

The wiki is not out of date at all. By the way, this way of installing
the nvidia drivers has been around for some years now. I use
module-assistant in sid and it has worked fine for me from the first
moment I used it. Before that I used make-kpkg, this worked too, but the
module-assistant takes away a lot of work.

Michael Fothergill wrote:

Dear Debianists,

I have installed Debian Lenny on my HP G6062 laptop.  Xserver works reasonably 
using the vesa driver.  I couldn't get it to work with the nv driver.

It seems to see the nvidia network controller as well.

There is an nvidia 7000M graphics chip in the laptop.  I assume that it could 
do some 3D graphics processing.

But if I would want to use this capability I would need to install the 
proprietary nvidia drivers manually.

I Googled this and found quite a few web pages on this.

It seems that Nvidia have their own installer and guide on their own web site 
for Linux users but Debian also has its own Debian Way of installing the nvidia 
drivers.

There also seems to be other individuals with web pages giving advice on this 
subject.

Left to my own devices I would likely choose this site to get instructions on 
how to proceed here:

http://wiki.debian.org/NvidiaGraphicsDrivers

But this seems to be a fast moving subject and maybe this site is out of date 
now.

I would appreciate comments on which web sites provide the most up to date and 
appropriate way of doing it.

I will use those sites and ignore the other ones and install the drivers.

Regards

Michael Fothergill











_
Win 100’s of Virgin Experience days with BigSnapSearch.com
http://www.bigsnapsearch.com






--
http://fragfest.com.au


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Fw: Re: Problems installing amd64 with Supermicro motherboard

2008-04-13 Thread Francesco Pietra

The "aperture memory hole" issue was solved by changing the default "AGP 
present" for IOMMU Mode to "64 MB" (the option was from 32 MB to 1GB). AGP is 
not present in this board.

However the issue about memory

Memory: 20079812k/22544384k available remains. Actually, there are 2 + 2 + 1 GB 
at each node, so it should be 2400k.

I can't imagine if a fresh install of Debian can change the memory detection.

francesco

--- On Sun, 4/13/08, Francesco Pietra <[EMAIL PROTECTED]> wrote:

> From: Francesco Pietra <[EMAIL PROTECTED]>
> Subject: Fw: Re: Problems installing amd64 with Supermicro motherboard
> To: "amd64 Debian" 
> Cc: "Giacomo Mulas" <[EMAIL PROTECTED]>
> Date: Sunday, April 13, 2008, 7:07 AM
> The CD-ROM issue was solved. Now CD-ROM detected.
> 
> Concerning the "aperture memory hole" reported
> below, I forgot to mention:
> 
> $ dmesg | grep -i memory
> your BIOS doesn't leave a aperture memory hole.
> 
> 
> As to network, dmesg reports
> 
> e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network
> Connection.
> 
> 
> As the raid1 is in order, like my applications (Amber Dock
> NEChem), is it worth while to try recognizing the Gigabit
> or is it better to reinstall the system? With my previous
> 2-socket system I had no problems in installing etch with
> raid1.
> 
> Ciao
> francesco
> 
> 
> 
> --- On Sat, 4/12/08, Francesco Pietra
> <[EMAIL PROTECTED]> wrote:
> 
> > From: Francesco Pietra <[EMAIL PROTECTED]>
> > Subject: Fw: Re: Problems installing amd64 with
> Supermicro motherboard
> > To: "debian64"
> 
> > Cc: "Giacomo Mulas"
> <[EMAIL PROTECTED]>
> > Date: Saturday, April 12, 2008, 3:04 PM
> > Additional info related or not to
> "continuous" vs
> > "discrete" and memory problems reported
> below,
> > from running Debian and commanding
> > 
> > # dmesg
> > 
> > 
> > Checking aperture...
> > CPU 0: aperture too small (32 MB)
> > No AGP bridge found
> > Your BIOS doesn't leave a aperture memory hole
> > Please enable the IOMMU option in the BIOS setup
> > This costs you 64 MB of RAM
> Mapping aperture over 65536 KB of RAM @ 800
> > 
> > 
> > Memory: 20545780k/22020096k available (1929 kernel
> code,
> > 425288k reserved, 864k data, 176 init).
> > 
> > As to peripherals, floppy is detected by both BIOS and
> > dmesg, while cdrom is not detected by
> > 
> > $ dmesg
> > $ cat /proc/sys/dev/cdrom/info
> > $ cat /proc/ide/drivers
> > $ cat /proc/scsi/scsi
> > 
> > The DVD Pioneer DVR-110 (which was OK on my previous
> Tyan
> > S2895) was  IDE connected through the 80-wire ATA 133
> cable
> > furnished with the Supermicro motherboard. Is any
> jumper
> > setting needed?
> > 
> > 
> > Thanks
> > francesco
> > 
> > --- On Sat, 4/12/08, Francesco Pietra
> > <[EMAIL PROTECTED]> wrote:
> > 
> > > From: Francesco Pietra
> <[EMAIL PROTECTED]>
> > > Subject: Re: Problems installing amd64 with
> Supermicro
> > motherboard
> > > To: "Giacomo Mulas"
> > <[EMAIL PROTECTED]>
> > > Cc: debian-amd64@lists.debian.org, "A J
> > Stiles" <[EMAIL PROTECTED]>
> > > Date: Saturday, April 12, 2008, 10:17 AM
> > > Hi
> > > I finally succeeded in entering BIOS (although
> the
> > Intel
> > > Boot Agent is a pest that has still to be
> eliminated;
> > > thanks to "ael" for suggesting Freedos:
> not
> > yet
> > > tried, I first wanted to configure BIOS at least
> where
> > I am
> > > sure what I  am doing).
> > > 
> > > In configuring the CPU (4 dual-core amd 875 Rev
> E1:
> > cache
> > > L1 256KB, cache L2 2048KB) it is not clear to me
> how
> > to set
> > > the MTRR mapping. The choice is between
> > > "continuous" (which makes the PCI hole
> > > noncacheable) and "discrete" (which
> places
> > the
> > > PCI hole beloww the 4GB boundary).
> > > 
> > > Oddly, the System Memory is reported 20480MB
> (which
> > agrees
> > > with the result of command
> > > 
> > > $ cat /proc/meminfo
> > > 
> > > when Linux is launched. Actually, I installed
> aside
> > each
> > > socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so
> I
> > expected
> > > a total 24GB. All these memories were OK on a
> Tyan
> > S2895,
> > > and insertion on the Supermicro H8QCE board seems
> > correct.
> > > I did myself all the management of the 2GB, and I
> was
> > > carefully grounded.  Should the filling of the
> slots
> > be
> > > different?
> > > 
> > > Thanks
> > > 
> > > gfrancesco
> > > 
> > > 
> > > --- On Sat, 4/12/08, Giacomo Mulas
> > > <[EMAIL PROTECTED]> wrote:
> > > 
> > > > From: Giacomo Mulas
> <[EMAIL PROTECTED]>
> > > > Subject: Re: Problems installing amd64 with
> > Supermicro
> > > motherboard
> > > > To: "Francesco Pietra"
> > > <[EMAIL PROTECTED]>
> > > > Cc: debian-amd64@lists.debian.org, "A J
> > > Stiles" <[EMAIL PROTECTED]>
> > > > Date: Saturday, April 12, 2008, 12:20 AM
> > > > On Fri, 11 Apr 2008, Francesco Pietra wrote:
> > > > 
> > > > > No success in entering BIOS. It seems
> that
> > the
> > > > "Intel(R) Boot Agent"
> > > > > should be eliminated, to get free of
> their
> > PXE
> > > system.
> > > > Does anyone know
> > > > > 

Ambani Brothers & Lakshmi Mittal to Purchase Europe

2008-04-13 Thread The Career Pigeon
>>>the Career Pigeon<<<

The Career Pigeon Brings you exclusive, fabricated news intended to 
give you a breakfrom your long day at work. So if you have a career, a
nd a sense of humor, stop by everyweek for a laugh, and to see what's 
going on in your field. 

Know more about the Career Pigeon
http://news.techtribe.com/CareerPigeon/index.php#01


Incredible India

Mukesh and Anil Ambani Join Forces, Team up with Lakshmi Mittal 
to Purchase Europe


On the heels of Fortune Magazine rating 4 Indians among the 10 wealthiest 
people in the world, 3 of India’s wealthiest men, Mukesh Ambani, Anil Ambani, 
and Lakshmi Mittal announced a decision to collaborate on their next big 
venture;
Purchasing Europe.  The three tycoons have laid out a 7 step plan for the 
complete 
Indianization of the continent, except England, which they feel is likely to be 
completely Indianized by 2015 anyway without their plan.

Read more
http://news.techtribe.com/CareerPigeon/index.php#02

Latest Version of Google to Search Users Brain

In yet another impressive innovation, the search engine giant Google has 
announced
 that its latest upgrade.

Read more
http://news.techtribe.com/CareerPigeon/index.php#03

Job Interview Starts Off Weird, Ends with Dance Number

Ashish Babu, BPO Team Lead, while attempting to further his career, had an 
interview with a small tech company, that started out weird...

Read more
http://news.techtribe.com/CareerPigeon/index.php#03

Startup CEO Depicts Website Statistics Accurately

In an unprecedented move, techTribe’s president and CEO,Rohit Agarwal,
 actually used the accurate user statistics.

Read more
 http://news.techtribe.com/CareerPigeon/index.php#05


Poll – Celebrity Job Referrals
Looks like General Musharraf will be looking for a new job soon.
Read more
http://news.techtribe.com/CareerPigeon/index.php#06



To make sure you receive emails from The Career Pigeon in your Inbox, 
please add [EMAIL PROTECTED] to your
address book. To unsubscribe please email [EMAIL PROTECTED] 
If you have any questions, please contact [EMAIL PROTECTED] 
Please view our privacy policy at http://news.techtribe.com/privacy.html




Fw: Re: Problems installing amd64 with Supermicro motherboard

2008-04-13 Thread Francesco Pietra
The CD-ROM issue was solved. Now CD-ROM detected.

Concerning the "aperture memory hole" reported below, I forgot to mention:

$ dmesg | grep -i memory
your BIOS doesn't leave a aperture memory hole.


As to network, dmesg reports

e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection.


As the raid1 is in order, like my applications (Amber Dock NEChem), is it worth 
while to try recognizing the Gigabit or is it better to reinstall the system? 
With my previous 2-socket system I had no problems in installing etch with 
raid1.

Ciao
francesco



--- On Sat, 4/12/08, Francesco Pietra <[EMAIL PROTECTED]> wrote:

> From: Francesco Pietra <[EMAIL PROTECTED]>
> Subject: Fw: Re: Problems installing amd64 with Supermicro motherboard
> To: "debian64" 
> Cc: "Giacomo Mulas" <[EMAIL PROTECTED]>
> Date: Saturday, April 12, 2008, 3:04 PM
> Additional info related or not to "continuous" vs
> "discrete" and memory problems reported below,
> from running Debian and commanding
> 
> # dmesg
> 
> 
> Checking aperture...
> CPU 0: aperture too small (32 MB)
> No AGP bridge found
> Your BIOS doesn't leave a aperture memory hole
> Please enable the IOMMU option in the BIOS setup
> This costs you 64 MB of RAM
Mapping aperture over 65536 KB of RAM @ 800
> 
> 
> Memory: 20545780k/22020096k available (1929 kernel code,
> 425288k reserved, 864k data, 176 init).
> 
> As to peripherals, floppy is detected by both BIOS and
> dmesg, while cdrom is not detected by
> 
> $ dmesg
> $ cat /proc/sys/dev/cdrom/info
> $ cat /proc/ide/drivers
> $ cat /proc/scsi/scsi
> 
> The DVD Pioneer DVR-110 (which was OK on my previous Tyan
> S2895) was  IDE connected through the 80-wire ATA 133 cable
> furnished with the Supermicro motherboard. Is any jumper
> setting needed?
> 
> 
> Thanks
> francesco
> 
> --- On Sat, 4/12/08, Francesco Pietra
> <[EMAIL PROTECTED]> wrote:
> 
> > From: Francesco Pietra <[EMAIL PROTECTED]>
> > Subject: Re: Problems installing amd64 with Supermicro
> motherboard
> > To: "Giacomo Mulas"
> <[EMAIL PROTECTED]>
> > Cc: debian-amd64@lists.debian.org, "A J
> Stiles" <[EMAIL PROTECTED]>
> > Date: Saturday, April 12, 2008, 10:17 AM
> > Hi
> > I finally succeeded in entering BIOS (although the
> Intel
> > Boot Agent is a pest that has still to be eliminated;
> > thanks to "ael" for suggesting Freedos: not
> yet
> > tried, I first wanted to configure BIOS at least where
> I am
> > sure what I  am doing).
> > 
> > In configuring the CPU (4 dual-core amd 875 Rev E1:
> cache
> > L1 256KB, cache L2 2048KB) it is not clear to me how
> to set
> > the MTRR mapping. The choice is between
> > "continuous" (which makes the PCI hole
> > noncacheable) and "discrete" (which places
> the
> > PCI hole beloww the 4GB boundary).
> > 
> > Oddly, the System Memory is reported 20480MB (which
> agrees
> > with the result of command
> > 
> > $ cat /proc/meminfo
> > 
> > when Linux is launched. Actually, I installed aside
> each
> > socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so I
> expected
> > a total 24GB. All these memories were OK on a Tyan
> S2895,
> > and insertion on the Supermicro H8QCE board seems
> correct.
> > I did myself all the management of the 2GB, and I was
> > carefully grounded.  Should the filling of the slots
> be
> > different?
> > 
> > Thanks
> > 
> > gfrancesco
> > 
> > 
> > --- On Sat, 4/12/08, Giacomo Mulas
> > <[EMAIL PROTECTED]> wrote:
> > 
> > > From: Giacomo Mulas <[EMAIL PROTECTED]>
> > > Subject: Re: Problems installing amd64 with
> Supermicro
> > motherboard
> > > To: "Francesco Pietra"
> > <[EMAIL PROTECTED]>
> > > Cc: debian-amd64@lists.debian.org, "A J
> > Stiles" <[EMAIL PROTECTED]>
> > > Date: Saturday, April 12, 2008, 12:20 AM
> > > On Fri, 11 Apr 2008, Francesco Pietra wrote:
> > > 
> > > > No success in entering BIOS. It seems that
> the
> > > "Intel(R) Boot Agent"
> > > > should be eliminated, to get free of their
> PXE
> > system.
> > > Does anyone know
> > > > how to throw this agent away with Linux? The
> old
> > amd64
> > > installation is
> > > > recognized on the new system. Though the
> original
> > > installation was for a
> > > > dual socket machine, all new 875 CPUs are
> > recognized
> > > by
> > > >
> > > > $ cat /proc/cpuinfo
> > > >
> > > > so that I can expect to be able to clean
> things
> > with
> > > the previous Debian
> > > > amd64 installation, edit BIOS, and then
> > reinstalling
> > > amd64 in order that
> > > > all new hardware is properly taken into
> account.
> > > >
> > > > What Intel suggests to eliminate their Boot
> Agent
> > is
> > > to download a DOS
> > > > program (subjected to property restrictions;
> > curiously
> > > so because I want
> > > > to get free of their intruding program,
> which let
> > me
> > > think that
> > > > individuals are not properly defended by the
> laws
> > > against intruders). DOS
> > > > is something I am not familiar with and I
> > don't
> > > want to get involved in.
> > > > If not else I can't imagine how to get
> DOS on
> > my
> > > amd

Re: nvidia way versus debian way of installing nvidia 3D graphics drivers in Lenny..

2008-04-13 Thread Simon Vos
The wiki is not out of date at all. By the way, this way of installing
the nvidia drivers has been around for some years now. I use
module-assistant in sid and it has worked fine for me from the first
moment I used it. Before that I used make-kpkg, this worked too, but the
module-assistant takes away a lot of work.

Michael Fothergill wrote:
> Dear Debianists,
> 
> I have installed Debian Lenny on my HP G6062 laptop.  Xserver works 
> reasonably using the vesa driver.  I couldn't get it to work with the nv 
> driver.
> 
> It seems to see the nvidia network controller as well.
> 
> There is an nvidia 7000M graphics chip in the laptop.  I assume that it could 
> do some 3D graphics processing.
> 
> But if I would want to use this capability I would need to install the 
> proprietary nvidia drivers manually.
> 
> I Googled this and found quite a few web pages on this.
> 
> It seems that Nvidia have their own installer and guide on their own web site 
> for Linux users but Debian also has its own Debian Way of installing the 
> nvidia drivers.
> 
> There also seems to be other individuals with web pages giving advice on this 
> subject.
> 
> Left to my own devices I would likely choose this site to get instructions on 
> how to proceed here:
> 
> http://wiki.debian.org/NvidiaGraphicsDrivers
> 
> But this seems to be a fast moving subject and maybe this site is out of date 
> now.
> 
> I would appreciate comments on which web sites provide the most up to date 
> and appropriate way of doing it.
> 
> I will use those sites and ignore the other ones and install the drivers.
> 
> Regards
> 
> Michael Fothergill
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _
> Win 100’s of Virgin Experience days with BigSnapSearch.com
> http://www.bigsnapsearch.com
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]