FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 04-07-2008, 10:15 PM
Bill Nottingham
 
Default stop neutering DRI

The attached patch makes anaconda stop neutering DRI/DRM (at least it should.)
It does it by including the DRI userspace modules (from mesa) and the kernel
DRM drivers.

Why do this?

To be more like the 'normal' installed system. Heck, if DRI's going to fail,
the system's just going to blow up on the first boot anyway. Furthermore,
there are cards/chips that do 2D accel via the 3D pipeline.

Plus, if we want to actually disable it in anaconda, we should do it
explicitly, not by accident as a consequence of some files not being
there.

Caveats:
- listing the kernel drivers explicitly is a hack
- this doesn't pull libGL onto the second stage. Assuming nothing dlopens()
it, that shouldn't be a problem

Bill
diff --git a/scripts/mk-images b/scripts/mk-images
index 9791067..34bcb1a 100755
--- a/scripts/mk-images
+++ b/scripts/mk-images
@@ -110,7 +110,8 @@ LVMMODS="dm-mod dm-zero dm-snapshot dm-mirror dm-multipath dm-round-robin dm-emc
RAIDMODS="md raid0 raid1 raid5 raid6 raid456 raid10 linear"
CRYPTOMODS="sha256_generic cbc aes_generic blkcipher crc32c"
PCMCIASOCKMODS="yenta_socket i82365 tcic pcmcia"
-INITRDMODS="$USBMODS $FIREWIREMODS $IDEMODS $SCSIMODS $FSMODS $LVMMODS $RAIDMODS $CRYPTOMODS $COMMONMODS $PCMCIASOCKMODS =scsi =net"
+DRMMODS="drm i810 i830 i915 mga nouveau r128 radeon savage sis tdfx via"
+INITRDMODS="$USBMODS $FIREWIREMODS $IDEMODS $SCSIMODS $FSMODS $LVMMODS $RAIDMODS $CRYPTOMODS $COMMONMODS $PCMCIASOCKMODS $DRMMODS =scsi =net"

. $(dirname $0)/buildinstall.functions

diff --git a/scripts/upd-instroot b/scripts/upd-instroot
index 62e4e50..242f3a8 100755
--- a/scripts/upd-instroot
+++ b/scripts/upd-instroot
@@ -612,6 +612,7 @@ usr/share/X11/locale
usr/share/X11/rgb*
usr/share/X11/xkb
usr/$LIBDIR/xserver/SecurityPolicy
+usr/$LIBDIR/dri
usr/$LIBDIR/xorg/modules
usr/bin/chattr*
usr/bin/gdialog
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
 
Old 04-08-2008, 12:21 AM
John Summerfield
 
Default stop neutering DRI

Bill Nottingham wrote:

The attached patch makes anaconda stop neutering DRI/DRM (at least it should.)
It does it by including the DRI userspace modules (from mesa) and the kernel
DRM drivers.

Why do this?

To be more like the 'normal' installed system. Heck, if DRI's going to fail,
the system's just going to blow up on the first boot anyway. Furthermore,
there are cards/chips that do 2D accel via the 3D pipeline.


G'day Bill.

Isn't Anaconda big enough and slow enough yet? Last time I did an
upgrade (as compared with an install) it ran for a good 12 hours.


If it's not essential for getting the install/upgrade done, _this_ user
doesn't want it.


--

Cheers
John

-- spambait
1aaaaaaa@coco.merseine.nu Z1aaaaaaa@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
 
Old 04-08-2008, 12:38 AM
Tracy R Reed
 
Default stop neutering DRI

John Summerfield wrote:
Isn't Anaconda big enough and slow enough yet? Last time I did an
upgrade (as compared with an install) it ran for a good 12 hours.


You really think anaconda itself chews up significant cpu time? If your
upgrade took 12 hours I really doubt it was spending all that time
crunching on anaconda. Disk or network IO is always the big slowdown.


_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
 
Old 04-08-2008, 01:20 AM
Bill Nottingham
 
Default stop neutering DRI

John Summerfield (debian@herakles.homelinux.org) said:
>> To be more like the 'normal' installed system. Heck, if DRI's going to fail,
>> the system's just going to blow up on the first boot anyway. Furthermore,
>> there are cards/chips that do 2D accel via the 3D pipeline.
>
> If it's not essential for getting the install/upgrade done, _this_ user
> doesn't want it.

Please read the last sentence again, then. Unless you want to force
everything through vesa (which can make it slower...)

Bill

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
 
Old 04-08-2008, 02:58 AM
John Summerfield
 
Default stop neutering DRI

Tracy R Reed wrote:

John Summerfield wrote:
Isn't Anaconda big enough and slow enough yet? Last time I did an
upgrade (as compared with an install) it ran for a good 12 hours.


You really think anaconda itself chews up significant cpu time? If your
upgrade took 12 hours I really doubt it was spending all that time
crunching on anaconda. Disk or network IO is always the big slowdown.


No, not CPU. Anaconda and its associates seem to take a lot of RAM
though, and that leads to excessive disk thrashing.


The computer concerned was doing a fine job of running FC3. After the
upgrade, I felt obliged to add RAM.


--

Cheers
John

-- spambait
1aaaaaaa@coco.merseine.nu Z1aaaaaaa@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
 
Old 04-08-2008, 03:10 AM
John Summerfield
 
Default stop neutering DRI

Bill Nottingham wrote:
John Summerfield (debian@herakles.homelinux.org) said:

To be more like the 'normal' installed system. Heck, if DRI's going to fail,
the system's just going to blow up on the first boot anyway. Furthermore,
there are cards/chips that do 2D accel via the 3D pipeline.
If it's not essential for getting the install/upgrade done, _this_ user
doesn't want it.


Please read the last sentence again, then. Unless you want to force
everything through vesa (which can make it slower...)


I commonly use vesa drivers. I don't do high-performance graphics work
at all, and I never thought of Anaconda as being demanding of graphics.
When it was being slow, I didn't think it was doing much graphics at
all, and the progress bars seem to zip along at a satisfying rate when
small packages are being installed.


I think Tracy's right, the bottleneck is disk and network I/o, and I'd
suggest more of the former, taking into account swap activity when
there's too little RAM.


Swap and/or rpm databases, see my very recent post "F9beta updates takes
forever" on fedora-test.


Something over two hours applying about 500 Mbytes of updated rpms on a
system sporting Intel(R) Core(TM)2 CPU and a new SATA drive.




--

Cheers
John

-- spambait
1aaaaaaa@coco.merseine.nu Z1aaaaaaa@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
 

Thread Tools




All times are GMT. The time now is 12:47 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org