| View previous topic :: View next topic |
| Author |
Message |
nadin
Tux's lil' helper
Joined: 05 Aug 2003
Posts: 103
|
 Posted: Mon Jul 10, 2006 3:29 am Post subject: Intel Matrix Technology |
 |
|
Hello,
I have a pentium D dual core 64bit chip. When I use the live AMD64 2006.0 live CD with the dodmraid option, I see the corresponding raid device in /dev/mapper
| Code: | control
isw_ihhjjdbde_Main
|
However when I compile the kernel (from stage1), including the device-mapper options and raid and all that fun stuff compiled in, I am unnable to find the device anymore. I currently have 3 sata drives, one for the OS and 2 mirrored for storage.
I have also tried the genkernel (with the dmraid option for initrd) with no success.
Is there any reason why it would work on the live cd but not on my actual machine?
I have also emerge dmraid and device-mapper. When I boot I see the following in dmesg
| Code: | nvidiafb: Actual id - 10de0161
nvidiafb: nVidia device/chipset 10DE0161
nvidiafb: CRTC0 analog found
nvidiafb: CRTC1 analog not found
nvidiafb: CRTC 0 appears to have a CRT attached
nvidiafb: Using CRT on CRTC 0
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 80x30
nvidiafb: PCI nVidia NV16 framebuffer (16MB @ 0xD0000000)
ACPI: Power Button (FF) [PWRF]
ACPI: Power Button (CM) [PWRB]
ACPI: Processor [CPU1] (supports 8 throttling states)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
mice: PS/2 mouse device common for all mice
loop: loaded (max 8 devices)
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 19 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:03:00.0 to 64
sky2 v1.4 addr 0xfa9fc000 irq 17 Yukon-EC (0xb6) rev 2
sky2 eth0: addr 00:17:31:bd:06:54
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:02:00.0 to 64
sky2 v1.4 addr 0xfa8fc000 irq 16 Yukon-EC (0xb6) rev 2
sky2 eth1: addr 00:17:31:bc:50:1a
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
GDT-HA: Storage RAID Controller Driver. Version: 3.04
GDT-HA: Found 0 PCI Storage RAID Controllers
libata version 1.20 loaded.
ahci 0000:00:1f.2: version 1.2
GSI 18 sharing vector 0xB9 and IRQ 18
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 23 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl RAID mode
ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part
ata1: SATA max UDMA/133 cmd 0xFFFFC2000000E900 ctl 0x0 bmdma 0x0 irq 18
ata2: SATA max UDMA/133 cmd 0xFFFFC2000000E980 ctl 0x0 bmdma 0x0 irq 18
ata3: SATA max UDMA/133 cmd 0xFFFFC2000000EA00 ctl 0x0 bmdma 0x0 irq 18
ata4: SATA max UDMA/133 cmd 0xFFFFC2000000EA80 ctl 0x0 bmdma 0x0 irq 18
ata1: SATA link up 3.0 Gbps (SStatus 123)
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01 87:4763 88:207f
ata1: dev 0 ATA-7, max UDMA/133, 312581808 sectors: LBA48
ata1: dev 0 configured for UDMA/133
scsi0 : ahci
ata2: SATA link down (SStatus 0)
scsi1 : ahci
ata3: SATA link up 3.0 Gbps (SStatus 123)
ata3: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01 87:4763 88:207f
ata3: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
ata3: dev 0 configured for UDMA/133
scsi2 : ahci
ata4: SATA link up 3.0 Gbps (SStatus 123)
ata4: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01 87:4763 88:207f
ata4: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
ata4: dev 0 configured for UDMA/133
scsi3 : ahci
isa bounce pool size: 16 pages
Vendor: ATA Model: Maxtor 6V160E0 Rev: VA11
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: Maxtor 7V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: Maxtor 7V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision: 05
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 sda3
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
sdb: unknown partition table
sd 2:0:0:0: Attached scsi disk sdb
SCSI device sdc: 586114704 512-byte hdwr sectors (300091 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
SCSI device sdc: 586114704 512-byte hdwr sectors (300091 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
sdc: unknown partition table
sd 3:0:0:0: Attached scsi disk sdc
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 3:0:0:0: Attached scsi generic sg2 type 0
usbmon: debugfs is not available
GSI 19 sharing vector 0xC1 and IRQ 19
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 19, io mem 0xfebfbc00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 19, io base 0x0000e480
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
GSI 20 sharing vector 0xC9 and IRQ 20
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 20, io base 0x0000e800
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
GSI 21 sharing vector 0xD1 and IRQ 21
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 21, io base 0x0000e880
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 17, io base 0x0000ec00
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
usb 2-2: new low speed USB device using uhci_hcd and address 2
sl811: driver sl811-hcd, 19 May 2005
Initializing USB Mass Storage driver...
usb 2-2: configuration #1 chosen from 1 choice
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
input: Logitech Logitech USB Keyboard as /class/input/input0
input: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-0000:00:1d.0-2
input: Logitech Logitech USB Keyboard as /class/input/input1
input: USB HID v1.10 Mouse [Logitech Logitech USB Keyboard] on usb-0000:00:1d.0-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: automatically using best checksumming function: generic_sse
generic_sse: 5222.000 MB/sec
raid5: using function: generic_sse (5222.000 MB/sec)
raid6: int64x1 1547 MB/s
raid6: int64x2 2164 MB/s
raid6: int64x4 2803 MB/s
raid6: int64x8 1811 MB/s
raid6: sse2x1 2531 MB/s
raid6: sse2x2 2262 MB/s
raid6: sse2x4 3238 MB/s
raid6: using algorithm sse2x4 (3238 MB/s)
md: raid6 personality registered for level 6
md: multipath personality registered for level -4
md: faulty personality registered for level -5
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com
device-mapper: dm-multipath version 1.0.4 loaded
device-mapper: dm-round-robin version 1.0.0 loaded
device-mapper: dm-emc version 0.0.3 loaded
Advanced Linux Sound Architecture Driver Version 1.0.11rc4 (Wed Mar 22 10:27:24 2006 UTC).
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 19 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1b.0 to 64
hda_codec: Unknown model for ALC882, trying auto-probe from BIOS...
ALSA device list:
#0: HDA Intel at 0xfebfc000 irq 17
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
ACPI wakeup devices:
P0P1 P0P3 P0P4 P0P5 P0P6 P0P7 P0P8 P0P9 UAR1 USB2 USB3 USB4 MC97 USB1 EUSB
ACPI: (supports S0 S1 S3 S4 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 204k freed
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
Adding 7823644k swap on /dev/sda2. Priority:-1 extents:1 across:7823644k
EXT3 FS on sda3, internal journal
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
device-mapper: dm-linear: Device lookup failed
device-mapper: error adding target to table
sky2 eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
|
any ideas? |
|
| Back to top |
|
 |
beatryder
Veteran
Joined: 08 Apr 2005
Posts: 1138
|
| Posted: Mon Jul 10, 2006 3:48 am Post subject: |
|
|
intel makes a 64bit chip?
_________________
Dont make it idiot proof, make it work.
Neucode.org
<suppressed key> |
|
| Back to top |
|
|
rhill
Retired Dev
Joined: 22 Oct 2004
Posts: 1629
Location: sk.ca
|
| Posted: Mon Jul 10, 2006 3:54 am Post subject: |
|
|
only since 2001.
_________________
by design, by neglect
for a fact or just for effect |
|
| Back to top |
|
|
nadin
Tux's lil' helper
Joined: 05 Aug 2003
Posts: 103
|
| Posted: Mon Jul 10, 2006 4:14 am Post subject: |
|
|
| It is a Intel Pentium D Dual-Core 950 - 64-bit |
|
| Back to top |
|
|
beatryder
Veteran
Joined: 08 Apr 2005
Posts: 1138
|
| Posted: Mon Jul 10, 2006 6:52 am Post subject: |
|
|
Can you link me to some documentation that confirms this? I am aware of the EMT64 features of that CPU, but AFAIK its only a 64bit memory addressing, not true 64bit computing like that of an amd64
Edit: Dont get me wrong, I am just curious.
_________________
Dont make it idiot proof, make it work.
Neucode.org
<suppressed key> |
|
| Back to top |
|
|
Phenax
l33t
Joined: 10 Mar 2006
Posts: 972
|
| Posted: Mon Jul 10, 2006 7:30 am Post subject: |
|
|
I believe that he means x86_64,
Anyways, Intel makes something called Itanium (ia64) that may be 'true' 64-bit. Never really looked at it. (For servers) |
|
| Back to top |
|
|
nadin
Tux's lil' helper
Joined: 05 Aug 2003
Posts: 103
|
|
| Back to top |
|
|
nadin
Tux's lil' helper
Joined: 05 Aug 2003
Posts: 103
|
| Posted: Mon Jul 10, 2006 4:27 pm Post subject: |
|
|
| Does software raid/dmraid only work with genkernel? |
|
| Back to top |
|
|
flysideways
Guru
Joined: 29 Jan 2005
Posts: 501
|
|
| Back to top |
|
|
Keruskerfuerst
Advocate
Joined: 01 Feb 2006
Posts: 2289
Location: near Augsburg, Germany
|
| Posted: Sat Jul 29, 2006 3:11 pm Post subject: |
|
|
AMD Athlon and Opteron are true 64 Bit CPUs (with a 32 Bit mode).
Intel Pentium D are 32 Bit CPUs with a 64 Bit emulation. |
|
| Back to top |
|
|
heipei
n00b
Joined: 09 Aug 2004
Posts: 45
Location: Germany
|
| Posted: Sat Jul 29, 2006 4:14 pm Post subject: |
|
|
you probably ran into the same problem like many other dmraid users. look here, you need a little tweaking to get kernels > 2.6.15 working with dmraid
https://forums.gentoo.org/viewtopic-t-482692-highlight-.html
edit: oops, sorry, didnt see it was posted before, nevermind 
_________________
hackvalue.de/heipei |
|
| Back to top |
|
|
Ast0r
Guru
Joined: 11 Apr 2006
Posts: 404
Location: Dallas, Tx - USA
|
| Posted: Sat Jul 29, 2006 7:05 pm Post subject: |
|
|
| Keruskerfuerst wrote: | AMD Athlon and Opteron are true 64 Bit CPUs (with a 32 Bit mode).
Intel Pentium D are 32 Bit CPUs with a 64 Bit emulation. |
What? x86_64 CPUs are x86 (32-bit) compatible with 64-bit extentions. The 64-bit Intel CPUs are essentially the same as the 64-bit AMD CPUs in terms of how they work (obvious the architechtures have some differences, but the implementation is similar ... the instructions are even compatible). The Athlons are faster than the Pentium D chips because they have better pipline/process design; it has nothing to do with "emulation". You can't "emulate" 64-bit memory access. You have to have 64 registers.
I don't know why it is that so many AMD64 users seem to think that somehow their 64-bit processor is somehow special. The only real difference is the additional registers which allow it to access 64-bit memory addresses. It doesn't give you any inherent advantages, other than the ability to address more than 4GB of memory. Yes, it is a nice processor, but it's not the end-all, be-all. AMD has moved to making only Athlon 64s in consumer products because it reduces their costs to deliver fewer product types.
The original 64-bit processor was the Itanium, btw.
Last edited by Ast0r on Sat Jul 29, 2006 7:12 pm; edited 1 time in total |
|
| Back to top |
|
|
fradkoquog
n00b
Joined: 29 Jul 2006
Posts: 4
Location: $HOME
|
|
| Back to top |
|
|
Ast0r
Guru
Joined: 11 Apr 2006
Posts: 404
Location: Dallas, Tx - USA
|
| Posted: Sat Jul 29, 2006 7:12 pm Post subject: |
|
|
| My bad. |
|
| Back to top |
|
|
FcukThisGame
l33t
Joined: 20 Apr 2005
Posts: 776
Location: /lost+found
|
| Posted: Fri Aug 04, 2006 12:51 pm Post subject: |
|
|
Your /dev/mapper does not carry over into your chrooted environment.
Inside your chrooted environment:
_________________
Sysadmin by trade, geek by choice
DESKTOP:
i7-3770K|8800GTS-512|32GB|1x256GB SSD|4x1TB|HD/BDROM|1920x1200+1680x1050
Win8 Pro w/ Hyper-V|Server 2012 VM|Ubuntu VM|Gentoo VM
TABLET: Samsung Ativ 700t
i5-3317U|4GB|128GB SSD|1920x1080 Touch
Win8 |
|
| Back to top |
|
|
|
Kernel & Hardware
