You are not logged in.

Pages: 1

#1 2006-12-03 15:31:21

djclue917
Member
Registered: 2006-12-03
Posts: 121

linux 2.6.19 and Intel chipsets

The main change that I noticed since my upgrade to 2.6.19 (as stated in the front page news of Arch) is that devices would change/shift names.

My optical device (CDRW+DVD-ROM combo) in 2.6.18.x was named as /dev/hda, and in 2.6.19, its name changed to /dev/sr0. The main different aside from the name change is that my CDROM, which was previously "owned" by the IDE subsystem, is now "owned" by the SCSI subsystem.

Now here are the questions:

1. What concerns/issues would the change from IDE -> SCSI cause?
2. Do I need to include the ide-scsi module in /etc/rc.conf?
3. Would there be any performance hit/gain, cd writing issue, etc.?

One more thing.. I noticed that hdparm wouldn't give me any data about my optical device now. it says that "HDIO_GETGEO failed: Inappropriate ioctl for device". Is this normal?

Offline

#2 2006-12-03 16:31:10

bpisciot
Member
From: Flyover Land
Registered: 2004-12-16
Posts: 78

Re: linux 2.6.19 and Intel chipsets

A followup question: It appears that we also have to edit our fstab to use the newest kernel (2.6.19 series).  This presumably will have an effect on our ability to dual boot at the moment (stock kernel = 2.6.18 ).  Is that right?

"You're only young once, but you can always be immature."

Offline

#3 2006-12-03 16:40:03

lessthanjake
Member
From: Norway
Registered: 2005-11-09
Posts: 319
Website

Re: linux 2.6.19 and Intel chipsets

I think that is right! That's my situation as well, but it'doesn't really matter as I usually just use the beyond kernel, ant the stock kernel probably hits [current] soon.

Offline

#4 2006-12-04 01:35:38

brain0
Developer
From: Aachen - Germany
Registered: 2005-01-03
Posts: 1,382

Re: linux 2.6.19 and Intel chipsets

djclue917 wrote:

1. What concerns/issues would the change from IDE -> SCSI cause?
2. Do I need to include the ide-scsi module in /etc/rc.conf?
3. Would there be any performance hit/gain, cd writing issue, etc.?

The new pata subsystem has been introduced that starts migrating IDE devices to the better SCSI subsystem. Normally, nothing would change unless you want it to. But in case of the ata_piix driver, it is the only driver that now supports both ide and sata devices (which makes much more trouble for some other users and there is not much we can do about it). If you want your old names back, then force piix to load before ata_piix.

That is not related to ide-scsi at all, and the performance should be exactly the same as for the old ide drivers.

Offline

#5 2006-12-04 14:48:09

nggalai
Member
From: Switzerland
Registered: 2004-08-01
Posts: 215
Website

Re: linux 2.6.19 and Intel chipsets

I'm a bit mystified about what I am supposed to change. Could somebody please provide a sample grub menu.lst and fstab?

Thanks. smile

Cheers,
-Sascha

Sascha "nggalai" Erni, .rb
www.3dcenter.org | www.nggalai.com

Offline

#6 2006-12-04 15:43:05

wiremore
Member
Registered: 2005-08-23
Posts: 43

Re: linux 2.6.19 and Intel chipsets

I have an intel chipset on my laptop. Before the upgrade, I was using piix and now I still seem to have piix loaded (although mkinitcpio -M lists both piix and ata_piix)

I just updated to the 2.6.19-beyond kernel from 2.6.18ck. I followed the instructions (maybe wrong) and changed all /dev/hdans to /dev/sdan in fstab and also changed the root=/dev/hda3 line in menu.1st to root=/dev/sda3. However, all my device names did not change.

It seems to be working ok.

Offline

#7 2006-12-04 17:41:56

djclue917
Member
Registered: 2006-12-03
Posts: 121

Re: linux 2.6.19 and Intel chipsets

brain0 wrote:

The new pata subsystem has been introduced that starts migrating IDE devices to the better SCSI subsystem. Normally, nothing would change unless you want it to. But in case of the ata_piix driver, it is the only driver that now supports both ide and sata devices (which makes much more trouble for some other users and there is not much we can do about it). If you want your old names back, then force piix to load before ata_piix.

So in 2.6.19, IDE devices will be really under the SCSI subsystem? Does forcing piix to load before ata_pixx apply to systems which use Intel chipsets?

http://www.archlinux.org/news/273/

Offline

#8 2006-12-04 21:32:46

Eugenia
Member
From: Bay Area, CA, USA
Registered: 2005-03-08
Posts: 74
Website

Re: linux 2.6.19 and Intel chipsets

IMO, this is messy. Why couldn't they keep the naming compatibility and still use the new driver and such? I smell lots of migration problems for us who have old installations and keep upgrading to -current.

www.OSNews.com

Offline

#9 2006-12-05 01:10:50

brain0
Developer
From: Aachen - Germany
Registered: 2005-01-03
Posts: 1,382

Re: linux 2.6.19 and Intel chipsets

djclue917 wrote:

So in 2.6.19, IDE devices will be really under the SCSI subsystem? Does forcing piix to load before ata_pixx apply to systems which use Intel chipsets?

1) You can choose. But long-term, all IDE devices will move to SCSI subsystem and IDE subsystem will be removed (though I think it will stay there for another year at least)
2) Yes, it only applies to Intel chipsets. Users of other chipsets won't notice any changes now.

Offline

#10 2006-12-05 16:56:13

Warnaud
Member
From: /dev/random
Registered: 2006-03-02
Posts: 58
Website

Re: linux 2.6.19 and Intel chipsets

Here I have an i875P with two IDE HD and 2 SATA what a mess, I finally got it with the almighty fallback image.
I've removed autodetect and usb hooks, switch the ide hooks to pata.
I've modified grub (root=/dev/hda5 => root=/dev/sda5) and fstab, hopefully the order is the same ... hda -> sda,  hdb -> sdb, sdb -> sdc, sdc -> sdd

Everything seems stable here with kernel26beyond except for grub ...

install-grub /dev/hda
error: could not convert device to grub format: /dev/sda5
install-grub /dev/sda
error: could not convert device to grub format: /dev/sda5

roll

Hope I don't have to reinstall grub tongue

-=<>=-
Archlinux French site : http://www.archlinux.fr

Offline

#11 2006-12-05 17:06:37

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: linux 2.6.19 and Intel chipsets

Please post you entire menu.lst

http://phraktured.net

Offline

#12 2006-12-05 17:32:12

cougar
Member
From: France
Registered: 2006-06-24
Posts: 93

Re: linux 2.6.19 and Intel chipsets

That's weird ! I've the last beyond kernel and I didn't change anything.
Moreover, I don't understand what's the matter with GRUB. There's no link between updating a kernel and how grub is dealing with the menu.lst file ?


[dam@Avalon ~]$ mkinitcpio -M
Modules autodetected:
ahci
ata_generic
ata_piix
ide-core

Offline

#13 2006-12-05 20:02:51

Warnaud
Member
From: /dev/random
Registered: 2006-03-02
Posts: 58
Website

Re: linux 2.6.19 and Intel chipsets

phrakture wrote:

Please post you entire menu.lst

Here it is :

# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst

# DEVICE NAME CONVERSIONS 
#
#  Old /dev    DevFS                    Grub
# -----------------------------------------------
#  /dev/fd0    /dev/floppy/0            (fd0)
#  /dev/hda    /dev/discs/disc0/disc    (hd0)
#  /dev/hdb2   /dev/discs/disc1/part2   (hd1,1)
#  /dev/hda3   /dev/discs/disc0/part3   (hd0,2)
#

#  FRAMEBUFFER RESOLUTION SETTINGS
#     +-------------------------------------------------+
#          | 640x480    800x600    1024x768   1280x1024
#      ----+--------------------------------------------
#      256 | 0x301=769  0x303=771  0x305=773   0x307=775
#      32K | 0x310=784  0x313=787  0x316=790   0x319=793
#      64K | 0x311=785  0x314=788  0x317=791   0x31A=794
#      16M | 0x312=786  0x315=789  0x318=792   0x31B=795
#     +-------------------------------------------------+

# general configuration:
timeout   15
default   0
splashimage /boot/grub/splash.xpm.gz
color light-blue/black light-cyan/blue

# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
# TIP: To use udev, add "devfs=nomount" to your kernel line.
#
#-*

# (0) Sourcemage
title Source Mage GNU/Linux
kernel  (hd0,0)/boot/vmlinuz root=/dev/hda1 ro vga=790

# (1) Archlinux
title=Arch linux Beyond
root (hd0,4)
#kernel /boot/vmlinuz26beyond root=/dev/sda5 video=vesafb:ywrap,mtrr,1280x1024-32@60 splash=silent,theme:darch console=tty1 quiet
kernel (hd0,4)/boot/vmlinuz26beyond root=/dev/sda5 vga=795 video=vesafb:mtrr:3,ywrap splash=silent,kdgraphics,theme:darch console=tty1 quiet
initrd (hd0,4)/boot/kernel26beyond.img

title=Arch linux Beyond Save
root (hd0,4)
kernel (hd0,4)/boot/vmlinuz26beyond root=/dev/sda5 vga=795
initrd (hd0,4)/boot/kernel26beyond-fallback.img

# (2) Archlinux
title FreeBSD
rootnoverify (hd0,2)
chainloader +1
makeactive

Result of hwd -c :

IDE interface
  ata_piix        : Intel Corp.|82801EB ICH5 IDE
  ata_piix        : Intel Corp.|82801EB ICH5 IDE (SATA)
Ethernet controller
  skge            : 3Com Corp.|3C940 10/100/1000 LAN
VGA compatible controller
  vesa            : nVidia Corp.|NV35 [GeForce FX 5900 Ultra]
Multimedia audio controller
  snd-emu10k1     : Creative Labs|EMU10K2 Audigy Audio Processor
Host bridge
  intel-agp       : Intel Corp.|875 DRAM Controller / Host-Hub Interface
ISA bridge
  i810-tco        : Intel Corp.|82801EB ISA Bridge (LPC)
PCI bridge
  unknown         : Intel Corp.|875 Host-AGP Bridge
  hw_random       : Intel Corp.|82820 815e (Camino 2) Chipset PCI
Input device controller
  emu10k1-gp      : Creative Labs|EMU10K2 Audigy Gameport
FireWire (IEEE 1394)
  ohci1394        : VIA Technologies Inc.|OHCI Compliant IEEE 1394 Host Controller
  ohci1394        : Creative Labs|EMU10K2 Audigy IEEE1394 Firewire Controller
USB Controller
  uhci_hcd        : Intel Corp.|USB Controller
  uhci_hcd        : Intel Corp.|USB Controller
  ehci-hcd        : Intel Corp.|USB Enhanced Controller
SMBus
  i2c-i801        : Intel Corp.|82801EB SMBus
USB Human Interface Devices
  usbhid          : USB-PS/2 Optical Mouse [/dev/input/mice]
  usbhid          : Logitech Gaming Keyboard
  usbfs           : G15 Keyboard
USB Hub
  hub             : Virtual|Hub
  hub             : USB2.0 Hub
  hub             : Virtual|Hub
  hub             : Logitech G15 Keyboard
  hub             : Virtual|Hub
USB Vendor Specific Class
  unknown         : Camera
Mouse
  msintellips/2   : PS/2 Mouse port [/dev/psaux]

Anyway I can always use sourcemage to reinstall grub so no big troubles here.

-=<>=-
Archlinux French site : http://www.archlinux.fr

Offline

#14 2006-12-06 02:36:42

gee
Member
Registered: 2006-11-29
Posts: 313

Re: linux 2.6.19 and Intel chipsets

forget about this post, it was my mistake for having a bad menu.lst for month (still using the vmlinuz image files ...)

Offline

#15 2006-12-07 01:52:53

gee
Member
Registered: 2006-11-29
Posts: 313

Re: linux 2.6.19 and Intel chipsets

Actually, all is cool but my df is empty, do I have to modify mtab as well ?

Offline

#16 2006-12-10 15:54:39

newgargamel
Member
From: PL, CZ
Registered: 2005-08-28
Posts: 156

Re: linux 2.6.19 and Intel chipsets

Can someone tell me please how to compile new kernel with ata_piix only? Is it enough to remove this line "CONFIG_BLK_DEV_PIIX=y"? Do I have to do something else?
Thanks

# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
# CONFIG_CHR_DEV_SG is not set
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set

#
# Serial ATA (prod) and Parallel ATA (experimental) drivers
#
CONFIG_ATA=y
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SVW is not set
CONFIG_ATA_PIIX=y
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIL24 is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
CONFIG_SATA_INTEL_COMBINED=y
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_ISAPNP is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_QDI is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set

Offline

Pages: 1

Board footer

Powered by FluxBB