sidux.com
Upgrade Warnings (EN & DE) - FIXED: 2.6.24.2.slh.11: VIA? problem solved with .12 upgrade
dzz - Feb 22, 2008 - 11:01 AM
Post subject: FIXED: 2.6.24.2.slh.11: VIA? problem solved with .12 upgrade
Code:
dzz@mainsnake3:~$ uname -r
2.6.24-2.6.24.2.slh.11-sidux-686
2.6.24 /VIA problem still not solved. It must surely be libata-related?
http://www.sidux.com/PNphpBB2-viewtopic-t-8911.html
Short dmesg extract (these errors go on and on)
Code:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.00: BMDMA stat 0x64
ata1.00: cmd c8/00:0f:80:e1:04/00:00:00:00:00/e0 tag 0 dma 7680 in
res 51/84:00:8e:e1:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.00: BMDMA stat 0x64
ata1.00: cmd c8/00:0f:80:e1:04/00:00:00:00:00/e0 tag 0 dma 7680 in
res 51/84:00:8e:e1:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.00: BMDMA stat 0x64
ata1.00: cmd c8/00:10:10:90:b5/00:00:00:00:00/e1 tag 0 dma 8192 in
res 51/84:00:1f:90:b5/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/33
ata1: EH complete
ata1.00: limiting speed to UDMA/66:PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata1.00: BMDMA stat 0x64
ata1.00: cmd c8/00:10:10:90:b5/00:00:00:00:00/e1 tag 0 dma 8192 in
res 51/84:00:1f:90:b5/00:00:00:00:00/e1 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }
ata1: soft resetting link
ata1.00: configured for UDMA/66
ata1.01: configured for UDMA/33
ata1: EH complete
Used smxi this time, the install itself went error-free.
michaa - Feb 22, 2008 - 01:40 PM
Post subject: 2.6.24-2.6.24.2.slh.11-sidux-686: VIA problem not yet solved
In the past, I had ata errors, too. I do NOT understand the background and/or the meaning of the error messages. But I could allways solve these problems by controling/changing the ide cables. Make sure they are pluged in really well and that the cable is not kinked. It seems to me, that this libata stuff gets more and more sensible to smallest hardware damages.
I had ata2.0 and ata3.1 errors. I do not understand the numbering, but maybe in the docs you may find information whether and how the numbers refere to ide channels and devices. To me it seems as if the numbers indicate ata_channel.subchannel:
Maybe those ata problems are NOT VIA related, but I do not know!
If I remeber well, you have a Western Digital disk. In past, there were WDhd_s with linux related problems. It could be helpfull to test this. Detach the other ide devices and try boot. Unfortunately we have no live cd with the new libata_via drivers, so you cannot test this with live cd until "nyx" comes out. Maybe you could test with a spare disc?
dzz - Feb 22, 2008 - 02:06 PM
Post subject: RE: 2.6.24-2.6.24.2.slh.11-sidux-686: VIA problem not yet so
Thanks michaa. This is my main system so swapping drives will be quite a disruption but I'll try a test install/upgrade with a spare disk at some stage. Something has changed with 2.6.24 that my box doesn't like.
There are 2x HDD, one is western digital. The same errors seem to be for both drives. The HD's are on each primary (master) channels and the CDROM's are slaves. Grub is on the first disk and main sidux / on the second
Code:
scsi 0:0:0:0: Direct-Access ATA WDC WD2000BB-00G 08.0 PQ: 0 ANSI: 5
scsi 0:0:1:0: CD-ROM LITE-ON DVDRW SOHW-1213S TS08 PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access ATA HDS722516VLAT20 V34O PQ: 0 ANSI: 5
scsi 1:0:1:0: CD-ROM LITE-ON LTR-52327S QS0A PQ: 0 ANSI: 5
michaa - Feb 22, 2008 - 02:57 PM
Post subject: RE: 2.6.24-2.6.24.2.slh.11-sidux-686: VIA problem not yet so
Where do those scsi messages come from? Do you have a real scsi system?
dmesg on my system:
Code:
...
ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.01: BMDMA stat 0x4
ata3.01: cmd c8/00:08:df:0d:6f/00:00:00:00:00/f1 tag 0 dma 4096 in
res 51/84:00:df:0d:6f/00:00:00:00:00/f1 Emask 0x10 (ATA bus error)
ata3.01: status: { DRDY ERR }
ata3.01: error: { ICRC ABRT }
ata3: soft resetting link
ata3.00: configured for UDMA/100
ata3.01: configured for UDMA/100
ata3: EH complete
...
I have those dmesg output, too. Only difference: At the end UDMA/100 works.
I know, all wroks with .23 kernels on your system. Nevertheless, while testing, try with your first hd only, detach other devices. Controll jumpers (master/lave; don't use "cable select") use different cables to exclude any possible demage.
And, maybe sounds stupid, but make sure you do not have dust bunnies in your cpu fan or around your power supply unit. This has been a reason for ata problems on my system!
dzz - Feb 22, 2008 - 03:13 PM
Post subject:
Quote:
Do you have a real scsi system?
No, all four IDE channels only
Box was recently stripped and cleaned out
To test without the western digital I'll have to do some grub mods first as that's where it is. Then put the box out of action, get it on the bench and start investigating. That won't happen today, it's in service!
Richard - Feb 22, 2008 - 04:07 PM
Post subject:
I now have a similar dmesg tail also.
Using the .7 kernel. My new box had been working well for a few days:
Host/Kernel/OS "eros45box" running Linux 2.6.24-2.6.24.2.slh.7-sidux-686 i686 [ sidux 2007-04.5 - Έρως christmas special - kde-full - (200712260138) ]
CPU Info
(1) Intel Core2 Duo E4500 @ 2048 KB cache flags( sse3 lm ) clocked at [ 2193.997 MHz ]
(2) Intel Core2 Duo E4500 @ 2048 KB cache flags( sse3 lm ) clocked at [ 2193.997 MHz ]
Videocard nVidia G72 [GeForce 7300 SE] X.Org 1.4.0.90 [ 1440x900@60.0hz ]
Network cards Realtek RTL8101E PCI Express Fast Ethernet controller, at port: e800
Processes 121 | Uptime 3:22 | Memory 140.7/2027.1MB | HDD ATA WDC WD1600AAJS-0,USB DISK Pro Size 160GB (18%used) | Client Shell | Infobash v3.01
Trouble began while copying some large files, moving some other things and surfing IW.
Locked up and began giving errors. Reboot failed the first couple of times.
Currently running, apparently OK. Running smartooltests at present.
So far no indication of problem. Just see those ata3.0 errors on boot, as follows:
...
libata version 3.00 loaded.
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
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 2
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d800
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 20
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 3
uhci_hcd 0000:00:1d.2: irq 20, io base 0x0000d880
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
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 4
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000dc00
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 1-1: new full speed USB device using uhci_hcd and address 2
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 18
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 5
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 18, io mem 0xfbefbc00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
ata_piix 0000:00:1f.1: version 2.12
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1f.1 to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
usb 1-1: device not accepting address 2, error -71
ata1.00: ATAPI: HL-DT-STDVD-RAM GSA-H55N, 1.03, max UDMA/66
ata1.00: configured for UDMA/66
ata2: port disabled. ignoring.
scsi 0:0:0:0: CD-ROM HL-DT-ST DVD-RAM GSA-H55N 1.03 PQ: 0 ANSI: 5
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0xd400 ctl 0xd080 bmdma 0xc880 irq 19
ata4: SATA max UDMA/133 cmd 0xd000 ctl 0xcc00 bmdma 0xc888 irq 19
ata3.00: ATA-7: WDC WD1600AAJS-00PSA0, 05.06H05, max UDMA/133
ata3.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access ATA WDC WD1600AAJS-0 05.0 PQ: 0 ANSI: 5
Driver 'sd' needs updating - please use bus_type methods
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3 sda4 <<4>Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 >
sd 2:0:0:0: [sda] Attached SCSI disk
sr 0:0:0:0: Attached scsi generic sg0 type 5
sd 2:0:0:0: Attached scsi generic sg1 type 0
usb 5-2: new high speed USB device using ehci_hcd and address 3
usb 5-2: configuration #1 chosen from 1 choice
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
Attempting manual resume
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
usb 1-1: new full speed USB device using uhci_hcd and address 4
usb 1-1: configuration #1 chosen from 1 choice
usb 2-1: new full speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.00: BMDMA stat 0x26
ata3.00: cmd ca/00:28:67:10:df/00:00:00:00:00/e2 tag 0 dma 20480 out
res 51/84:18:77:10:df/00:00:00:00:00/e2 Emask 0x30 (host bus error)
ata3.00: status: { DRDY ERR }
ata3.00: error: { ICRC ABRT }
ata3: soft resetting link
usb 2-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: C-Media USB Headphone Set as /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.3/input/input1
input,hidraw0: USB HID v1.00 Device [C-Media USB Headphone Set ] on usb-0000:00:1d.0-1
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
ata3.00: configured for UDMA/133
ata3: EH complete
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.00: BMDMA stat 0x26
ata3.00: cmd ca/00:08:cf:67:e1/00:00:00:00:00/e2 tag 0 dma 4096 out
res 51/84:01:d6:67:e1/00:00:00:00:00/e2 Emask 0x30 (host bus error)
ata3.00: status: { DRDY ERR }
ata3.00: error: { ICRC ABRT }
ata3: soft resetting link
ata3.00: configured for UDMA/133
ata3: EH complete
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.00: BMDMA stat 0x26
ata3.00: cmd ca/00:08:87:de:2b/00:00:00:00:00/e3 tag 0 dma 4096 out
res 51/84:01:8e:de:2b/00:00:00:00:00/e3 Emask 0x30 (host bus error)
ata3.00: status: { DRDY ERR }
ata3.00: error: { ICRC ABRT }
ata3: soft resetting link
ata3.00: configured for UDMA/133
ata3: EH complete
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kjournald starting. Commit interval 5 seconds
EXT3-fs: sda5: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 1039812
ext3_orphan_cleanup: deleting unreferenced inode 731475
ext3_orphan_cleanup: deleting unreferenced inode 731474
ext3_orphan_cleanup: deleting unreferenced inode 731473
ext3_orphan_cleanup: deleting unreferenced inode 731472
ext3_orphan_cleanup: deleting unreferenced inode 731471
ext3_orphan_cleanup: deleting unreferenced inode 634525
ext3_orphan_cleanup: deleting unreferenced inode 633321
ext3_orphan_cleanup: deleting unreferenced inode 925041
ext3_orphan_cleanup: deleting unreferenced inode 406965
ext3_orphan_cleanup: deleting unreferenced inode 633028
ext3_orphan_cleanup: deleting unreferenced inode 1039849
ext3_orphan_cleanup: deleting unreferenced inode 178488
ext3_orphan_cleanup: deleting unreferenced inode 178487
ext3_orphan_cleanup: deleting unreferenced inode 178485
EXT3-fs: sda5: 15 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /devices/platform/pcspkr/input/input2
parport_pc 00:08: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
NET: Registered protocol family 23
iTCO_vendor_support: vendor-support=0
input: Power Button (FF) as /devices/virtual/input/input3
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /devices/virtual/input/input4
ACPI: Power Button (CM) [PWRB]
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 19
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
usblp1: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x7304
usbcore: registered new interface driver usblp
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1b.0 to 64
input: PS2++ Logitech TrackMan as /devices/platform/i8042/serio1/input/input5
iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
intel_rng: FWH not detected
usbcore: registered new interface driver snd-usb-audio
Adding 2176796k swap on /dev/sda3. Priority:-1 extents:1 across:2176796k
EXT3 FS on sda5, internal journal
ata3.00: limiting speed to UDMA/100:PIO4
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.00: BMDMA stat 0x26
ata3.00: cmd ca/00:08:72:32:a0/00:00:00:00:00/e3 tag 0 dma 4096 out
res 51/84:01:79:32:a0/00:00:00:00:00/e3 Emask 0x30 (host bus error)
ata3.00: status: { DRDY ERR }
ata3.00: error: { ICRC ABRT }
ata3: soft resetting link
ata3.00: configured for UDMA/100
ata3: EH complete
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.00: BMDMA stat 0x26
ata3.00: cmd ca/00:08:4a:55:a2/00:00:00:00:00/e3 tag 0 dma 4096 out
res 51/84:01:51:55:a2/00:00:00:00:00/e3 Emask 0x30 (host bus error)
ata3.00: status: { DRDY ERR }
ata3.00: error: { ICRC ABRT }
ata3: soft resetting link
ata3.00: configured for UDMA/100
ata3: EH complete
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
fuse init (API version 7.9)
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda10, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda11, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda12, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Would appreciate knowing if there is actually a hardware problem or if it is software.
Currently running the .11 kernel on a Maxtor 40GB drive with no errors.
Will reconnect the WD160 to the net on Sat. and try the .11 kernel.
Is there a way to download a deb to install a new kernel, if not connected to the net?
regards,
Richard.
DeepDayze - Feb 22, 2008 - 04:13 PM
Post subject:
put the kernel debs onto a USB key or CDR from another machine and plug in the key then install the kernel debs
dzz - Feb 22, 2008 - 04:37 PM
Post subject:
Tried to edit my first post here as I put an incomplete URL
I am unable to do that, the entire text has now been deleted and no edit will stick!
Is there a gremlin about?
EDIT: Fixed!
Richard - Feb 22, 2008 - 04:39 PM
Post subject:
OK, I'll try that, I see the following debs:
kernel-2.6.24.2-slh-smp-8.zip
linux-headers-2.6.24-2.6.24.2.slh.11-common_2.6.24-10_i386.deb
linux-headers-2.6.24-2.6.24.2.slh.11-sidux-686_2.6.24-10_i386.deb
linux-image-2.6.24-2.6.24.2.slh.11-sidux-686_2.6.24-10_i386.deb
Thanks, I'll give that a shot before dragging cables about. 
DeepDayze - Feb 22, 2008 - 05:08 PM
Post subject:
usb keys are definitely very handy to have for such situations...sneakernet does still work
dzz - Feb 22, 2008 - 09:11 PM
Post subject:
Well if I start pulling my machine to bits it's out of action so I thought to try a recompile of vanilla 2.6.24.2 using "make oldconfig" and let it run while I went to the pub.
On my return I installed the awaiting debs. It booted to a command prompt only but:
Code:
dzz@mainsnake3:~$ uname -r
2.6.24.2dzz-custom
Then ran smxi for nvidia and successfully started X
Then "dpkg-reconfigure virtualbox"
and tested good my VM's
dmesg shows no significant errors and everything seems normal but no doubt there will be missing modules.
I am obviously now in sidux-unsupported land but had to do that and report the result which seems to prove that 2.6.24.2 itself is not the issue here, nor my machine's hardware.
I will also add that I'm no kernel expert and a simple custom compile is about my limit.
So I will leave others to draw any conclusion from my tests.
As I said before, I'm a persistent bugger and determined to run current sid/sidux by whatever means. But I would prefer to run a slh kernel.
EDIT:
Noticed that /dev mappings are to hdxx as before NOT sdxx as was forced with slh kernel. Don't understand what goes on there.
HarzG - Feb 22, 2008 - 11:07 PM
Post subject: 2.6.24.2.slh.11 & d-u fine, but siduxcc modules and OOca
Icedove/Iceweasel works fine, Virtualbox ose works fine.
Gimp and digiKam starts fast and they show pictures very fast.
But there are no modules in siduxcc. It's not possible to show kernelmodules in siduxcc for any kernel.
I have a lot of crashes in OpenOffice calc if I use the enter key to rewrite a value in a cell. btw: That's not a sidux item, but an OpenOffice 2.4 problem.
Code:
Host/Kernel/OS "HarzG" running Linux 2.6.24-2.6.24.2.slh.11-sidux-686 i686 [ sidux 2007-03 - Γαια - kde-full - (200708141236) ]
CPU Info (1) Intel Pentium 4 1024 KB cache flags( sse3 ) clocked at [ 3391.577 MHz ]
(2) Intel Pentium 4 1024 KB cache flags( sse3 ) clocked at [ 3391.577 MHz ]
Videocard nVidia NV43 [GeForce 6610 XL] X.Org 1.4.0.90 [
1280x1024@75.0hz ]
Network cards VIA VT6105 [Rhine-III], at port: d300
Processes 104 | Uptime 8min | Memory 712.2/1518.3MB | HDD ATA SAMSUNG HD161HJ,Generic CF Card CF,Generic MS/SD Combo MS,Generic SM/xD Combo SM Size 160GB (31%used) | Client Shell | Infobash v3.01
h2 - Feb 22, 2008 - 11:13 PM
Post subject: RE: 2.6.24.2.slh.11 & d-u fine, but siduxcc modules and
HarzG, smxi kernel install now has the full automatic module install support working, including building madwifi/ndiswrapper if needed.
UncleVom - Feb 22, 2008 - 11:15 PM
Post subject: RE: 2.6.24.2.slh.11 & d-u fine, but siduxcc modules and
My VIA chipset machines are working well with the kernel 2.6.24-2.6.24.2.slh.11-sidux-686
For example this box:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge [1106:3205]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI Bridge [1106:b198]
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 82)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177]
00:11.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06)
00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50)
00:12.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6102 [Rhine-II] [1106:3065] (rev 74)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV280 [Radeon 9200 PRO] [1002:5960] (rev 01)
01:00.1 Display controller [0380]: ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) [1002:5940] (rev 01)
UncleVom
michaa - Feb 23, 2008 - 12:45 AM
Post subject:
dzz wrote:
EDIT:
Noticed that /dev mappings are to hdxx as before NOT sdxx as was forced with slh kernel. Don't understand what goes on there.
You don't use the newest libata patches slh is using, I guess.
Crust - Feb 23, 2008 - 12:47 AM
Post subject:
Confirmed working with at least one VIA chipset:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge [1106:3188] (rev 01)
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] [1106:b188]
00:07.0 CardBus bridge [0607]: Texas Instruments PCI4510 PC card Cardbus Controller [104c:ac44] (rev 02)
00:07.1 FireWire (IEEE 1394) [0c00]: Texas Instruments PCI4510 IEEE-1394 Controller [104c:8029]
00:09.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
00:0b.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet [14e4:169c] (rev 03)
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 80)
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 82)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177]
00:11.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06)
00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 50)
00:11.6 Communication controller [0780]: VIA Technologies, Inc. AC'97 Modem Controller [1106:3068] (rev 80)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] [1002:4e50]
dzz - Feb 24, 2008 - 12:25 PM
Post subject: Fixed for now with 2.6.24.slh.12 !!
Code:
dzz@mainsnake3:~$ uname -r
2.6.24-2.6.24.2.slh.12-sidux-686
I'm pleased to say the repetitive error messages freezes and cpu overload have now all gone.
Thanks slh, whatever you have done allows me to run a sidux kernel again! Also h2 for updating smxi so quickly and efficiently
Code:
libata version 3.00 loaded.
hda: max request size: 512KiB
hda: 390721968 sectors (200049 MB) w/2048KiB Cache, CHS=24321/255/63
hda: cache flushes supported
hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 >
hdc: max request size: 512KiB
hdc: 321672960 sectors (164696 MB) w/1794KiB Cache, CHS=20023/255/63
hdb: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
hdc: cache flushes supported
hdc: hdc1 hdc2 < hdc5 hdc6 hdc7 hdc8 >
hdd: ATAPI 52X CD-ROM CD-R/RW drive, 2048kB Cache
Attempting manual resume
However I've noticed these warnings in dmesg output, although everything appears now to run normally. I have seen similar with other kernels but it's never caused any problem. It applies to both IDE channels. I wonder if this is the key to the cause of it all? Maybe there is some problem with cables or jumper settings. Maybe with a HDD master/CDROM slave configuration on each IDE channel one pulls down the other and the kernel can't cope with that?
Code:
hda: WDC WD2000BB-00GUA0, ATA DISK drive
hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hda: host side 80-wire cable detection failed, limiting max speed to UDMA33
hda: UDMA/33 mode selected
hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
I'm still not fully understanding why /dev mappings are still hdxx rather than sdxx as was forced with the previous 2.6.24's. I don't know anything about "latest libata patches" but obviously will need to. Has that made the difference? Maybe this will come back to bug me in future.
michaa - Feb 24, 2008 - 05:04 PM
Post subject: Fixed for now with 2.6.24.slh.12 !!
Hi dzz,
yes, we are back to hd instead sd ( I needed to "reinstall" my w2k VM in vbox again 
)
"hda: host side 80-wire cable detection failed, limiting max speed to UDMA33" really indicates a problem. Which UDMA version did you have with .23 kernel? UDMA33 or more?
But you should change the cabel anyway and look which UDMA mode you get with a new one.
DeepDayze - Feb 24, 2008 - 08:39 PM
Post subject: RE: Fixed for now with 2.6.24.slh.12 !!
i get that msg too...and I have a known-good 80 wire cable already installed...what gives?
michaa - Feb 24, 2008 - 09:05 PM
Post subject: Re: RE: Fixed for now with 2.6.24.slh.12 !!
DeepDayze wrote:
i get that msg too...and I have a known-good 80 wire cable already installed...what gives?
If those cables are good and working (as it seems) it would indicate a bug in the libata UDMA testing routines. They seem to be too sensible. That is what I noticed, too. I spent money for good new ide cables. But from time to time, I get some ata errors too, but never with such a negative result as dzz.
DeepDayze - Feb 24, 2008 - 09:18 PM
Post subject: RE: Re: RE: Fixed for now with 2.6.24.slh.12 !!
the 80 wire cables are attached to my PATA dvd writers...my hard drives are SATA.
dzz - Feb 24, 2008 - 10:28 PM
Post subject: RE: Re: RE: Fixed for now with 2.6.24.slh.12 !!
Well it's thanks to slh for the kernel............and michaa for pointing out I should check my cables.
I've just replaced them; now it's "UDMA/100 mode selected" in the dmesg. Haven't yet inspected the old ones.
I will run a test later on my "mirror sidux" on the other HD with the .11 kernel, out of curiosity to see if the same errors arise and post the result. It could be that the new kernel could not handle a hardware fault previously unnoticed and it was not a VIA issue after all.
Then this post can be marked with a big green tick!
dzz - Feb 25, 2008 - 04:50 PM
Post subject:
1.
The offending cables were old 40-wire, I can't explain why I had not noticed that before, it was me who put them there!
2.
I ran that test and booted .11 and .12 without error.
My "parallel sidux" still had /dev/hdxx mappings at first. .11 would not boot till fstab and menu.lst were changed to uuid (.12 did not care)
So unless something in dist-upgrade affected it, the conclusion is, the cables were the problem and something in the .11 went loopy while other kernels quietly slowed down the HD's.
And a warning to me for not keeping my hardware in good order! (all sorts of reclaimed junk around here)