Re: [lfs-support] status report about the nouveau driver

[Aleksandar Kuktin]

On Mon, 06 Feb 2012 22:28:25 -0500
Alain Toussaint alain.toussa...@securivm.ca wrote:

 Hello everyone,
   I still haven't done chapter 6 of the book but in
 preparation, I tried to test a git kernel (v3.3.0-rc2) along with the
 git sources of the nouveau driver for my nvidia card according to the
 instructions there:
 
 http://nouveau.freedesktop.org/wiki/InstallDRM (section 1.2 in
 particular).
 
 I also went ahead installing the latest version of the xorg-server
 software (version 1.11.4), xf86-video-nouveau (git sources from an
 hour ago) and the result is that the xorg-server sometime spin in an
 infinite loop after anything from startup to 35 minutes after having
 started up (listening to House,MD dvd's prove to be a good test for
 the stability of the X server).
 
 the error occur at random and isn't found in my latest log (cmdline:
 startx nouveau.log.txt) but the rest of the kernel run fine because
 i press the power button normally (i.e. not holding it for 4 seconds)
 and the kernel initiate an acpi shutdown event on lockup.
 
 for the next test, I will try a stock 3.3.0-rc2 kernel (sans the
 nouveau git source) and report back. this will happen either tomorrow
 or during next week-end.
 
 Alain
 

And a different experience from me: works fine.

Specifically: vanilla linux 3.2.0, kernel side of the nouveau driver
is in [device drivers]-[staging drivers] (you first need to enable
experimental features in the menuconfig); Mesa-7.11 holds the actual
Gallium 3d implementation, still a work in progress but works, mostly;
Mesa requires libdrm (I use 2.4.26) which must be configured with
--enable-nouveau-experimental-api; and finally the appropriate video
driver for X server, xf86-video-nouveau. X server is version 1.11.1.

Cue this discussion being booted to blfs-dev for being off-topic.

The above setup has not generated any instability that I have been able
to note. I was even able to hook it up with wine and play some 3D
games, but with mixed results. Some (older) work, some (newer) don't.

-- 
   Fourth law of programming:
   Anything that can go wrong wi
sendmail: segmentation violation - core dumped
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] udev issue

[Qrux]

Howdy, all.

This might be a bit OT, but does anyone have any clever ideas about how to name 
a drive with udev rules that doesn't have a ATTRS{serial} (or equivalent)?  I 
considered using PROGRAM=..., but the usual helpers don't seem much help here.

Here's some output:

 hdparm 
server# hdparm -I /dev/sdc

/dev/sdc:
 HDIO_DRIVE_CMD(identify) failed: Invalid argument

server# hdparm -i /dev/sdc

/dev/sdc:
 HDIO_DRIVE_CMD(identify) failed: Invalid argument
 HDIO_GET_IDENTITY failed: Invalid argument


 udevadm info 
server# udevadm info --query=all --path=/sys/block/sdc
P: 
/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/host6/target6:0:0/6:0:0:0/block/sdc
N: sdc
S: disk/by-path/pci-:02:02.0-scsi-0:0:0:0
E: UDEV_LOG=3
E: 
DEVPATH=/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/host6/target6:0:0/6:0:0:0/block/sdc
E: MAJOR=8
E: MINOR=32
E: DEVNAME=/dev/sdc
E: DEVTYPE=disk
E: SUBSYSTEM=block
E: ID_SCSI=1
E: ID_VENDOR=3ware
E: ID_VENDOR_ENC=3ware\x20\x20\x20
E: ID_MODEL=Logical_Disk_0
E: ID_MODEL_ENC=Logical\x20Disk\x200\x20\x20
E: ID_REVISION=1.2
E: ID_TYPE=disk
E: ID_BUS=scsi
E: ID_PATH=pci-:02:02.0-scsi-0:0:0:0
E: ID_PART_TABLE_TYPE=dos
E: UDISKS_PRESENTATION_NOPOLICY=0
E: UDISKS_PARTITION_TABLE=1
E: UDISKS_PARTITION_TABLE_SCHEME=mbr
E: UDISKS_PARTITION_TABLE_COUNT=0
E: DEVLINKS=/dev/disk/by-path/pci-:02:02.0-scsi-0:0:0:0


If it's not immediately obvious, it's a 3ware hardware raid volume.

Q

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page