[NITRO] ___Deprecated___

Message

smlgbl · Post by **smlgbl** » Mon Mar 20, 2006 8:09 pm

Maybe this is the wrong place for asking this, but how do you do it? Do you guys all just try out the new kernels on your normal, "everyday" desktops or do you use some other pc or do you have a second, stable linux running on the same machine?

I would also like to support this by trying the latest kernel aso. but i can't afford losing my pc for some days or be without network, as i need it for school!
Thanks in advance!

Tiger683 · Post by **Tiger683** » Mon Mar 20, 2006 9:11 pm

EDIT: FIXED in git

Phlogiston · Post by **Phlogiston** » Mon Mar 20, 2006 9:31 pm

Tiger683 wrote:Ok people...REISER4 is broken!!!!

If you already booted into this....well...do not reboot

I will commit a fix when i find it. Will keep you up2date.

If you have to reboot, change to runlevel 1 with init 1 and remount root readonly.... i didn't do it and nothing happened,
but something strange happens on shutdown when unmounting the partitions......

I think you should mention this in the first post

Phlogiston · Post by **Phlogiston** » Mon Mar 20, 2006 9:32 pm

haader wrote:Maybe this is the wrong place for asking this, but how do you do it? Do you guys all just try out the new kernels on your normal, "everyday" desktops or do you use some other pc or do you have a second, stable linux running on the same machine?

I would also like to support this by trying the latest kernel aso. but i can't afford losing my pc for some days or be without network, as i need it for school!
Thanks in advance!

Why do you mean losing the pc for some days? You always can have the stable kernel also in grub. And all in all these kernels are not that unstable. So just boot it and if everything works you're fine, if not just boot the old good kernel.

tagwar · Post by **tagwar** » Mon Mar 20, 2006 10:33 pm

so, since I don't use Reiser4, I did boot this beauty and it seems everything works just fine.
Emerged ieee80211 and ipw2200 --> works
Emerged fuse --> works
Emerged dazuko --> works

Next thing I will try is hibernating... so.. lets see.. yes.. works..

Thanks a lot Tiger!!

Edit: Btw.. the Logo is damn cool... but also damn big...

Cinder6 · Post by **Cinder6** » Mon Mar 20, 2006 11:05 pm

lol, it seems like I always have to wait when a new kernel release comes out, due to silly reiser4. Oh well.

Phlogiston · Post by **Phlogiston** » Mon Mar 20, 2006 11:07 pm

Cinder6 wrote:lol, it seems like I always have to wait when a new kernel release comes out, due to silly reiser4. Oh well.

reiser4 is not that stable we all should keep in mind. But it's techology quite rocks...

Tiger683 · Post by **Tiger683** » Mon Mar 20, 2006 11:07 pm

EDIT: FIXED in git

Phlogiston · Post by **Phlogiston** » Mon Mar 20, 2006 11:15 pm

Tiger683 wrote:Yeah I'm risking my data with this one every time i reboot
just to find out the patch didn't do the trick....i kind of got nowhere for now :/

You're using your data and root on reiser4?

Tiger683 · Post by **Tiger683** » Tue Mar 21, 2006 9:03 am

OK, the bug is now fixed, also added two stabilization patches for reiser4,
i think everyone should reemerge as the bug was probably affecting all filesystems
(although i didn't notice any damage when it was occuring)

cheers,

T

epic · Post by **epic** » Tue Mar 21, 2006 9:23 am

nice patch! emerging it now.
i can put up a mirror for you if you would like though(also sent a PM)..

epic · Post by **epic** » Tue Mar 21, 2006 10:27 am

one thing though, reiser4 related.
I am a happy reiser4 camper at 2.6.15-nitro3 atm.
but i guess this release is 1.0.5, which has reported trouble( see first lines of http://gentoo-wiki.com/HOWTO_Update_reiser4_partitions)
I have also heard and read in the reiserfs list that the first release of 1.0.5 was a real screwup,
but that later releases of 1.0.5 has fixed alot of the problems.
if 2.6.15-nitro3 is 1.0.4(which i kinda guess it is) and i want boot this kernel, would i need to use the method described in http://gentoo-wiki.com/HOWTO_Update_reiser4_partitions to upgrade to 1.0.5?
in that case i doubt i can find a livecd with a stable 1.0.5 on it(the newer 1.0.5 the more stable it is) to do the job.
So how should i go about running this kernel ? :P

Tiger683 · Post by **Tiger683** » Tue Mar 21, 2006 10:28 am

epic wrote:one thing though, reiser4 related.
I am a happy reiser4 camper at 2.6.15-nitro3 atm.
but i guess this release is 1.0.5, which has reported trouble( see first lines of http://gentoo-wiki.com/HOWTO_Update_reiser4_partitions)
I have also heard and read in the reiserfs list that the first release of 1.0.5 was a real screwup and that
later releases of 1.0.5 has fixed alot of the problems.
if 2.6.15-nitro3 is 1.0.4(which i kinda guess it is) and i want boot this kernel, would i need to use the method described in http://gentoo-wiki.com/HOWTO_Update_reiser4_partitions to upgrade to 1.0.5?
in that case i doubt i can find a livecd with a stable 1.0.5 on it(the newer 1.0.5 the more stable it is) to do the job.
So how should i go about running this kernel ?

All kernels after 2.6.12 have reiser4 1.0.5, so you already are a long-term 1.0.5 user

Robin79 · Post by **Robin79** » Tue Mar 21, 2006 12:21 pm

WTF is git?

pwe · Post by **pwe** » Tue Mar 21, 2006 12:26 pm

i dont have any files in /usr/src ... why?

epic · Post by **epic** » Tue Mar 21, 2006 12:30 pm

my emerge worked perfectly, took some time though.

up and running now w/ reiser4 and all.

Tiger683 · Post by **Tiger683** » Tue Mar 21, 2006 12:54 pm

Robin79 wrote:WTF is git?

http://www.kernel.org/pub/software/scm/git/docs/

pwe wrote:i dont have any files in /usr/src ... why?

Post output of emerge -p nitro-sources and emerge nitro-sources if it fails...

Notice that first emerge takes about 15 minutes.

pwe · Post by **pwe** » Tue Mar 21, 2006 2:15 pm

Code: Select all

gentoo64 pwe # emerge nitro-sources
Calculating dependencies... done!
>>> Emerging (1 of 1) sys-kernel/nitro-sources-2.6.16 to /
>>> checksums files   ;-) nitro-sources-2.6.16.ebuild
>>> checksums files   ;-) files/digest-nitro-sources-2.6.16
>>> Preparing to unpack ...
>>> Unpacking source...
 * Using GIT protocol: http/https

 * Resuming cogito checkout ------>

Fetching head...
Fetching objects...
Fetching tags...
Up to date.
 * Contents of repository
 *    http://nitro-sources.devserver.info/nitro-sources.git
 * are now in:
 *    /usr/portage/distfiles/git-src/nitro-sources

 * Copying source:
      moving ".git" into temporary...
      copying into sourcedir...
      moving ".git" back...
      done.
 *    exported to: /var/tmp/portage/nitro-sources-2.6.16/work/linux-2.6.16-nitro
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/nitro-sources-2.6.16/work/linux-2.6.16-nitro ...
>>> Source compiled.
>>> Test phase [not enabled]: sys-kernel/nitro-sources-2.6.16

>>> Install nitro-sources-2.6.16 into /var/tmp/portage/nitro-sources-2.6.16/image/ category sys-kern                                                                                                                el
>>> Copying sources ...
>>> Completed installing nitro-sources-2.6.16 into /var/tmp/portage/nitro-sources-2.6.16/image/

man:
>>> Merging sys-kernel/nitro-sources-2.6.16 to /
--- /usr/
--- /usr/src/
>>> /usr/src/linux-2.6.16-nitro/
>>> Safely unmerging already-installed instance...
<<<        dir /usr/src/linux-2.6.16-nitro
--- !empty dir /usr/src
--- !empty dir /usr
>>> Original instance of package unmerged safely.

 * After installing a new kernel of any version, it is important
 * that you have the appropriate /etc/modules.autoload.d/kernel-X.Y
 * created (X.Y is the first 2 parts of your new kernel version)

 * For example, this kernel will require:
 * /etc/modules.autoload.d/kernel-.

 * If you are upgrading from a previous kernel, you may be interested
 * in the following documents:
 *   - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml

 * IMPORTANT:
 * This release is from experimental branch of nitro-sources !
 * Therefore, there is no official support for the features included.

 * No responsibility for any damage, it is implied by the above...
 * Nitro-Sources is licenced under the same licence as the linux kernel,
 * You should read the GPL licence in kernel source directory for details ;)

 * Now compile this beauty, reboot, and fasten your seatbelts to experience the fastest desktop you'                                                                                                                ve ever seen!

>>> Regenerating /etc/ld.so.cache...
>>> sys-kernel/nitro-sources-2.6.16 merged.

>>> No packages selected for removal by clean.

>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.


 * GNU info directory index is up-to-date.

and nothing in /usr/src

Code: Select all

* dev-util/cogito 
     Available versions:  0.16.2 0.16.4 0.17
     Installed:           0.17

Code: Select all

* dev-util/git 
     Available versions:  1.1.6 1.2.3 1.2.4
     Installed:           1.2.4

Phlogiston · Post by **Phlogiston** » Tue Mar 21, 2006 2:36 pm

Kernel is running fine all in all, but I can't use the suspend2ui_text tool with it. I don't know why but it just displays nothing. The splash version works btw. Did you include any patch that could break this tool?

Tiger683 · Post by **Tiger683** » Tue Mar 21, 2006 2:41 pm

pwe wrote:and nothing in /usr/src

Code: Select all

* dev-util/cogito 
     Available versions:  0.16.2 0.16.4 0.17
     Installed:           0.17

Code: Select all

* dev-util/git 
     Available versions:  1.1.6 1.2.3 1.2.4
     Installed:           1.2.4

how long did the emerge take? this is kind of .... impossible

Try to remove /usr/portage/distfiles/git-src and emerge again.....

Phlogiston · Post by **Phlogiston** » Tue Mar 21, 2006 3:01 pm

Phlogiston wrote:Kernel is running fine all in all, but I can't use the suspend2ui_text tool with it. I don't know why but it just displays nothing. The splash version works btw. Did you include any patch that could break this tool?

Disabling splash support in kernel solves it!

Everything working now, GREAT work Tiger, especially if you remember that I am using uncivilized harware eh?

pwe · Post by **pwe** » Tue Mar 21, 2006 3:30 pm

Tiger683 wrote: Try to remove /usr/portage/distfiles/git-src and emerge again.....

thanks, it works now.

NiLuJe · Post by **NiLuJe** » Tue Mar 21, 2006 7:18 pm

Kernel running fine, except that libata pata via doesn't detect my _slaves_ devices on each IDE port, only the master ... o_O

dmesg extract:

Code: Select all

libata version 1.20 loaded.
pata_via 0000:00:0f.1: version 0.1.3
ata_pci_init_one: pci_dev class+intf: 0x1018a
ata_pci_init_one: NO_LEGACY == 0
ACPI (acpi_bus-0199): Device is not power manageable [20060210]
ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 16
PCI: Via IRQ fixup for 0000:00:0f.1, from 255 to 0
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xFC00 irq 14
ata1: dev 0 cfg 00:0c5a 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:203f 93:407b
ata1: dev 0 ATA-6, max UDMA/100, 312581808 sectors: LBA48
ata_acpi_push_id: skipping for PATA mode
via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
via_do_set_mode: Mode=69 ast broken=Y udma=133 mul=4
ata1: dev 0 configured for UDMA/100
pata_get_dev_handle: ENTER: dev->bus_id='0000:00:0f.1'
pata_get_dev_handle: dev_handle: 0xc14eb360, parent_handle: 0xc14e95c0
pata_get_dev_handle: for dev=0xf.1, addr=0xf0001, parent=0xdfe3cc00, *handle=0xc14eb360
do_drive_get_GTF:   drive w/ adr=0: v: 0xc14ebd20
ACPI Error (dsopcode-0460): Attempt to create_field of length zero [20060210]
ACPI Error (psparse-0522): Method parse/execution failed [\_SB_.PCI0.IDEC.RATA] (Node c14eb980), AE_AML_OPERAND_VALUE
ACPI Error (psparse-0522): Method parse/execution failed [\_SB_.PCI0.IDEC.CHN0.DRV0._GTF] (Node c14ebce0), AE_AML_OPERAND_VALUE
scsi0 : pata_via
  Vendor: ATA       Model: ST3160023A        Rev: 3.04
  Type:   Direct-Access                      ANSI SCSI revision: 05
pata_get_dev_handle: ENTER: dev->bus_id='0000:00:0f.1'
pata_get_dev_handle: dev_handle: 0xc14eb360, parent_handle: 0xc14e95c0
pata_get_dev_handle: for dev=0xf.1, addr=0xf0001, parent=0xdfe3cc00, *handle=0xc14eb360
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xFC08 irq 15
ata2: dev 0 cfg 00:8580 49:0b00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0407 93:0000
ata2: dev 0 ATAPI, max UDMA/33
ata_acpi_push_id: skipping for PATA mode
via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
via_do_set_mode: Mode=66 ast broken=Y udma=133 mul=4
ata2: dev 0 configured for UDMA/33
sata_get_dev_handle: SATA dev addr=0xf0001, handle=0xc14eb360
scsi1 : pata_via
  Vendor: _NEC      Model: DVD_RW ND-3520A   Rev: 1.04
  Type:   CD-ROM                             ANSI SCSI revision: 05
pata_get_dev_handle: ENTER: dev->bus_id='0000:00:0f.1'
pata_get_dev_handle: dev_handle: 0xc14eb360, parent_handle: 0xc14e95c0
pata_get_dev_handle: for dev=0xf.1, addr=0xf0001, parent=0xdfe3cc00, *handle=0xc14eb360
Driver 'sd' needs updating - please use bus_type methods
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 < sda5 sda6 sda7 sda8 > sda3 sda4
sd 0:0:0:0: Attached scsi disk sda
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
ACPI (acpi_bus-0199): Device is not power manageable [20060210]
ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 17
PCI: Via IRQ fixup for 0000:00:10.4, from 10 to 1

It's an Asus A7V880 (KT 880) motherboard, and pata via was working fine in 2.6.16-rc6-mm1 (actually, ck1 + a few mm patches, mainly git-alsa & libata) and 2.6.16-rc3-nitro1

dmesg from 2.6.16-rc6-mm1:

Code: Select all

Mar 16 01:02:08 Dhara libata version 1.20 loaded.
Mar 16 01:02:08 Dhara pata_via 0000:00:0f.1: version 0.1.2
Mar 16 01:02:08 Dhara ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 16
Mar 16 01:02:08 Dhara PCI: Via IRQ fixup for 0000:00:0f.1, from 255 to 0
Mar 16 01:02:08 Dhara ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xFC00 irq 14
Mar 16 01:02:08 Dhara ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:203f
Mar 16 01:02:08 Dhara ata1: dev 0 ATA-6, max UDMA/100, 312581808 sectors: LBA48
Mar 16 01:02:08 Dhara ata1: dev 1 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:407f
Mar 16 01:02:08 Dhara ata1: dev 1 ATA-7, max UDMA/133, 120103200 sectors: LBA
Mar 16 01:02:08 Dhara via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
Mar 16 01:02:08 Dhara via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
Mar 16 01:02:08 Dhara via_do_set_mode: Mode=69 ast broken=Y udma=133 mul=4
Mar 16 01:02:08 Dhara via_do_set_mode: Mode=69 ast broken=Y udma=133 mul=4
Mar 16 01:02:08 Dhara ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:203f
Mar 16 01:02:08 Dhara ata1: dev 0 configured for UDMA/100
Mar 16 01:02:08 Dhara ata1: dev 1 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:207f
Mar 16 01:02:08 Dhara ata1: dev 1 configured for UDMA/100
Mar 16 01:02:08 Dhara scsi0 : pata_via
Mar 16 01:02:08 Dhara Vendor: ATA       Model: ST3160023A        Rev: 3.04
Mar 16 01:02:08 Dhara Type:   Direct-Access                      ANSI SCSI revision: 05
Mar 16 01:02:08 Dhara Vendor: ATA       Model: Maxtor 6Y060L0    Rev: YAR4
Mar 16 01:02:08 Dhara Type:   Direct-Access                      ANSI SCSI revision: 05
Mar 16 01:02:08 Dhara ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xFC08 irq 15
Mar 16 01:02:08 Dhara ata2: dev 0 cfg 49:0b00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0407
Mar 16 01:02:08 Dhara ata2: dev 0 ATAPI, max UDMA/33
Mar 16 01:02:08 Dhara ata2: dev 1 cfg 49:0f00 82:0218 83:4000 84:4000 85:0218 86:0000 87:4000 88:0407
Mar 16 01:02:08 Dhara ata2: dev 1 ATAPI, max UDMA/33
Mar 16 01:02:08 Dhara via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
Mar 16 01:02:08 Dhara via_do_set_mode: Mode=12 ast broken=Y udma=133 mul=4
Mar 16 01:02:08 Dhara via_do_set_mode: Mode=66 ast broken=Y udma=133 mul=4
Mar 16 01:02:08 Dhara via_do_set_mode: Mode=66 ast broken=Y udma=133 mul=4
Mar 16 01:02:08 Dhara ata2: dev 0 cfg 49:0b00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0407
Mar 16 01:02:08 Dhara ata2: dev 0 configured for UDMA/33
Mar 16 01:02:08 Dhara ata2: dev 1 cfg 49:0f00 82:0218 83:4000 84:4000 85:0218 86:0000 87:4000 88:0407
Mar 16 01:02:08 Dhara ata2: dev 1 configured for UDMA/33
Mar 16 01:02:08 Dhara scsi1 : pata_via
Mar 16 01:02:08 Dhara Vendor: _NEC      Model: DVD_RW ND-3520A   Rev: 1.04
Mar 16 01:02:08 Dhara Type:   CD-ROM                             ANSI SCSI revision: 05
Mar 16 01:02:08 Dhara Vendor: PIONEER   Model: DVD-ROM DVD-117   Rev: 1.03
Mar 16 01:02:08 Dhara Type:   CD-ROM                             ANSI SCSI revision: 05
Mar 16 01:02:08 Dhara SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
Mar 16 01:02:08 Dhara sda: Write Protect is off
Mar 16 01:02:08 Dhara sda: Mode Sense: 00 3a 00 00
Mar 16 01:02:08 Dhara SCSI device sda: drive cache: write back
Mar 16 01:02:08 Dhara SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
Mar 16 01:02:08 Dhara sda: Write Protect is off
Mar 16 01:02:08 Dhara sda: Mode Sense: 00 3a 00 00
Mar 16 01:02:08 Dhara SCSI device sda: drive cache: write back
Mar 16 01:02:08 Dhara sda: sda1 sda2 < sda5 sda6 sda7 sda8 > sda3 sda4
Mar 16 01:02:08 Dhara sd 0:0:0:0: Attached scsi disk sda
Mar 16 01:02:08 Dhara SCSI device sdb: 120103200 512-byte hdwr sectors (61493 MB)
Mar 16 01:02:08 Dhara sdb: Write Protect is off
Mar 16 01:02:08 Dhara sdb: Mode Sense: 00 3a 00 00
Mar 16 01:02:08 Dhara SCSI device sdb: drive cache: write back
Mar 16 01:02:08 Dhara SCSI device sdb: 120103200 512-byte hdwr sectors (61493 MB)
Mar 16 01:02:08 Dhara sdb: Write Protect is off
Mar 16 01:02:08 Dhara sdb: Mode Sense: 00 3a 00 00
Mar 16 01:02:08 Dhara SCSI device sdb: drive cache: write back
Mar 16 01:02:08 Dhara sdb: sdb1 sdb2 < sdb5 >
Mar 16 01:02:08 Dhara sd 0:0:1:0: Attached scsi disk sdb
Mar 16 01:02:08 Dhara sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
Mar 16 01:02:08 Dhara Uniform CD-ROM driver Revision: 3.20
Mar 16 01:02:08 Dhara sr 1:0:0:0: Attached scsi CD-ROM sr0
Mar 16 01:02:08 Dhara sr1: scsi3-mmc drive: 49x/125x cd/rw xa/form2 cdda tray
Mar 16 01:02:08 Dhara sr 1:0:1:0: Attached scsi CD-ROM sr1
Mar 16 01:02:08 Dhara ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 17
Mar 16 01:02:08 Dhara PCI: Via IRQ fixup for 0000:00:10.4, from 10 to 1

Thanks!

Tiger683 · Post by **Tiger683** » Tue Mar 21, 2006 7:58 pm

NiLuJe wrote:Kernel running fine, except that libata pata via doesn't detect my _slaves_ devices on each IDE port, only the master ... o_O

I have the same problem... (also on via :/)
I'm working on it, will keep you uptodate on the progress

Tyler_Durden · Post by **Tyler_Durden** » Tue Mar 21, 2006 9:52 pm

Tiger683 wrote: NEW COMMITS SINCE 2.6.16-nitro_git2 (MOST RECENT FIRST):
...
*** release 2.6.16-nitro_git3
*** A small fix for device mapper
...

With git3 i can't mount my raid0 connected to the nforce4-chipset and initalized by dmraid anymore , syslog is showing:

Code: Select all

Mar 21 23:28:35 HAL9000 kernel: device-mapper: dm-stripe: Target length not divisible by chunk size
Mar 21 23:28:35 HAL9000 kernel: device-mapper: error adding target to table

with 2.6.15-nitro3:

Code: Select all

root@HAL9000 ~ 0 0.13 # ll /dev/mapper/
crw-rw---- 1 root root  10, 63 21. Mär 2006  control
brw------- 1 root root 254,  0 21. Mär 2006  nvidia_iecciaaf
brw------- 1 root root 254,  1 21. Mär 2006  nvidia_iecciaaf1
brw------- 1 root root 254,  2 21. Mär 2006  nvidia_iecciaaf2
brw------- 1 root root 254,  3 21. Mär 2006  nvidia_iecciaaf3

with 2.6.16-nitro:

Code: Select all

root@HAL9000 ~ 0 0.13 # ll /dev/mapper/
crw-rw---- 1 root root  10, 63 21. Mär 2006  control
brw------- 1 root root 254,  0 21. Mär 2006  nvidia_iecciaaf

Could there be a break with dmraid and/or device mapper?

[NITRO] _Deprecated_

reiser4 broken!!!

Re: reiser4 broken!!!

Re: [NITRO-GIT] Nitro-sources - 2.6.16 - latest commit: git3