Last night I was about to install antiX-M7.01 Lysistrata onto a partition on an old Pentium II laptop. However, I decided not to after noticing a few worrisome issues.
The first thing that I was concerned about is antiX was saying my laptop's HDD is SCSI (incorrect) and setting it up as sda in fstab. Does anyone know why it did that? I did a brief search last night and found a little bit of info in a couple of forum posts indicating that the problem may be related to the kernel and/or libata. I haven't (yet) found a simple solution to the problem, though.
I also noticed some error messages when antiX was booting. If it would be helpful, I can dig through the logs and post whatever error messages I can find.
Phil
12 posts
• Page 1 of 1
-
Posts: 57
- Joined: 28 Jan 2008
-
Posts: 216
- Joined: 12 Sep 2007
#2
Just for comparison/diagnostic purposes, I wonder what happens if you try loading antiX 6.5?
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#3
The kernel used in antiX Lysistrata 2.6.22 'sees' the hd drives as sd not hd, so there is nothing to worry about there.
The 'error' maybe connected to antiX not finding 915 graphics (because there isn't one) and again, unless you have this one, there is nothing to worry about.
How does Lysistrata work as a livecd?
The 'error' maybe connected to antiX not finding 915 graphics (because there isn't one) and again, unless you have this one, there is nothing to worry about.
How does Lysistrata work as a livecd?
-
Posts: 57
- Joined: 28 Jan 2008
#4
Here are some excerpts from some of the logs. Although the ACPI error messages may be useful (not sure), I don't care too much about them because I always disable ACPI on this old laptop. To me, the ATA errors and those involving disk access are the most worrisome. They may also explain why antiX booted up rather slowly even though I wasn't using the CD, but used a GRUB boot floppy to start it from the ISO located on a HDD partition.
From the boot log:
From the kernel log:
I also looked in syslog and dmesg, but the error messages were similar (or identical) to what's already posted above.
Phil
From the boot log:
Code: Select all
Thu Feb 7 18:57:22 2008: Wrong chipset detected. 915resolution only works with Intel 800/900 series graphic chipsets.
Thu Feb 7 18:58:06 2008: error: libhal_device_get_property_type: org.freedesktop.Hal.NoSuchProperty: No property system.product on device with id /org/freedesktop/Hal/devices/computer
From the kernel log:
Code: Select all
Feb 7 18:57:22 mepis1 kernel: * Found PM-Timer Bug on the chipset. Due to workarounds for a bug,
Feb 7 18:57:22 mepis1 kernel: * this clock source is slow. Consider trying other clock sources
Feb 7 18:57:22 mepis1 kernel: PCI quirk: region 1000-103f claimed by PIIX4 ACPI
Feb 7 18:57:22 mepis1 kernel: PCI quirk: region 1400-140f claimed by PIIX4 SMB
Feb 7 18:57:22 mepis1 kernel: ACPI Exception (utmutex-0263): AE_BAD_PARAMETER, Thread CFD82A50 could not acquire Mutex [3] [20070126]
Feb 7 18:57:22 mepis1 kernel: pnp: 00:00: iomem range 0x0-0x9ffff could not be reserved
Feb 7 18:57:22 mepis1 kernel: pnp: 00:00: iomem range 0x100000-0xfffffff could not be reserved
Feb 7 18:57:22 mepis1 kernel: pnp: 00:00: iomem range 0xe0000-0xfffff could not be reserved
Feb 7 18:57:22 mepis1 kernel: pnp: 00:00: iomem range 0xcb000-0xcbfff could not be reserved
Feb 7 18:57:22 mepis1 kernel: pnp: 00:01: ioport range 0xcf8-0xcff could not be reserved
Feb 7 18:57:22 mepis1 kernel: input: Macintosh mouse button emulation as /class/input/input0
[Macintosh???]
Feb 7 18:57:22 mepis1 kernel: RAMDISK: Compressed image found at block 0
Feb 7 18:57:22 mepis1 kernel: EXT2-fs warning: maximal mount count reached, running e2fsck is recommended
Feb 7 18:57:22 mepis1 kernel: VFS: Mounted root (ext2 filesystem).
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=66, limit=2
Feb 7 18:57:22 mepis1 kernel: isofs_fill_super: bread failed, dev=sda2, iso_blknum=16, block=32
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=4, limit=2
Feb 7 18:57:22 mepis1 kernel: EXT3-fs: unable to read superblock
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=4, limit=2
Feb 7 18:57:22 mepis1 kernel: EXT2-fs: unable to read superblock
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=18, limit=2
Feb 7 18:57:22 mepis1 kernel: ReiserFS: sda2: warning: sh-2006: read_super_block: bread failed (dev sda2, block 8, size 1024)
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=130, limit=2
Feb 7 18:57:22 mepis1 kernel: ReiserFS: sda2: warning: sh-2006: read_super_block: bread failed (dev sda2, block 64, size 1024)
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=66, limit=2
Feb 7 18:57:22 mepis1 kernel: isofs_fill_super: bread failed, dev=sda2, iso_blknum=16, block=32
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=4, limit=2
Feb 7 18:57:22 mepis1 kernel: EXT3-fs: unable to read superblock
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=4, limit=2
Feb 7 18:57:22 mepis1 kernel: EXT2-fs: unable to read superblock
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=18, limit=2
Feb 7 18:57:22 mepis1 kernel: ReiserFS: sda2: warning: sh-2006: read_super_block: bread failed (dev sda2, block 8, size 1024)
Feb 7 18:57:22 mepis1 kernel: attempt to access beyond end of device
Feb 7 18:57:22 mepis1 kernel: sda2: rw=0, want=130, limit=2
Feb 7 18:57:22 mepis1 kernel: ReiserFS: sda2: warning: sh-2006: read_super_block: bread failed (dev sda2, block 64, size 1024)
Feb 7 18:57:22 mepis1 kernel: ISO 9660 Extensions: RRIP_1991A
Feb 7 18:57:22 mepis1 kernel: ISO 9660 Extensions: RRIP_1991A
NOTE: Most of the following lines are not error messages. I included this section because of the repetitive ATA error(s).
Feb 7 18:57:22 mepis1 kernel: ata1.00: limiting speed to UDMA/25:PIO4
Feb 7 18:57:22 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Feb 7 18:57:22 mepis1 kernel: ata1.00: (BMDMA stat 0x24)
Feb 7 18:57:22 mepis1 kernel: ata1.00: cmd c8/00:00:bd:73:71/00:00:00:00:00/e0 tag 0 cdb 0x0 data 131072 in
Feb 7 18:57:22 mepis1 kernel: res 51/84:00:bc:74:71/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Feb 7 18:57:22 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:22 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:22 mepis1 kernel: ata1: EH complete
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:22 mepis1 kernel: PCI: setting IRQ 5 as level-triggered
Feb 7 18:57:22 mepis1 kernel: PCI: Found IRQ 5 for device 0000:00:03.0
Feb 7 18:57:22 mepis1 kernel: es1968: not attempting power management.
Feb 7 18:57:22 mepis1 kernel: es1968: clocking to 48822
Feb 7 18:57:22 mepis1 kernel: Linux video capture interface: v2.00
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0x100-0x3af: excluding 0x2f8-0x2ff
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0x3e0-0x4ff: clean.
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0x820-0x8ff: clean.
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0xc00-0xcf7: clean.
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0xa00-0xaff: clean.
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0x100-0x3af: excluding 0x2f8-0x2ff
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0x3e0-0x4ff: clean.
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0x820-0x8ff: clean.
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0xc00-0xcf7: clean.
Feb 7 18:57:22 mepis1 kernel: cs: IO port probe 0xa00-0xaff: clean.
Feb 7 18:57:22 mepis1 kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Feb 7 18:57:22 mepis1 kernel: pcmcia: registering new device pcmcia1.0
Feb 7 18:57:22 mepis1 kernel: 8139too Fast Ethernet driver 0.9.28
Feb 7 18:57:22 mepis1 kernel: PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
Feb 7 18:57:22 mepis1 kernel: PCI: Setting latency timer of device 0000:01:00.0 to 64
Feb 7 18:57:22 mepis1 kernel: eth0: RealTek RTL8139 at 0x1800, 00:10:60:76:fd:89, IRQ 10
Feb 7 18:57:22 mepis1 kernel: eth0: Identified 8139 chip type 'RTL-8139C'
Feb 7 18:57:22 mepis1 kernel: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
Feb 7 18:57:22 mepis1 kernel: drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04F9 pid 0x010E
Feb 7 18:57:22 mepis1 kernel: usbcore: registered new interface driver usblp
Feb 7 18:57:22 mepis1 kernel: drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Feb 7 18:57:22 mepis1 kernel: 1.0: ttyS1 at I/O 0x3e8 (irq = 3) is a 16550A
Feb 7 18:57:22 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Feb 7 18:57:22 mepis1 kernel: ata1.00: (BMDMA stat 0x24)
Feb 7 18:57:22 mepis1 kernel: ata1.00: cmd c8/00:00:25:c3:71/00:00:00:00:00/e0 tag 0 cdb 0x0 data 131072 in
Feb 7 18:57:22 mepis1 kernel: res 51/84:00:24:c4:71/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Feb 7 18:57:22 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:22 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:22 mepis1 kernel: ata1: EH complete
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:22 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 7 18:57:22 mepis1 kernel: ata1.00: cmd c8/00:80:ed:cc:71/00:00:00:00:00/e0 tag 0 cdb 0x0 data 65536 in
Feb 7 18:57:22 mepis1 kernel: res 40/00:00:24:c4:71/00:00:00:00:00/e0 Emask 0x4 (timeout)
Feb 7 18:57:22 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:22 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:22 mepis1 kernel: ata1: EH complete
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:22 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Feb 7 18:57:22 mepis1 kernel: ata1.00: (BMDMA stat 0x24)
Feb 7 18:57:22 mepis1 kernel: ata1.00: cmd c8/00:00:8d:90:72/00:00:00:00:00/e0 tag 0 cdb 0x0 data 131072 in
Feb 7 18:57:22 mepis1 kernel: res 51/84:00:8c:91:72/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Feb 7 18:57:22 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:22 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:22 mepis1 kernel: ata1: EH complete
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:22 mepis1 kernel: device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
Feb 7 18:57:22 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Feb 7 18:57:22 mepis1 kernel: ata1.00: (BMDMA stat 0x24)
Feb 7 18:57:22 mepis1 kernel: ata1.00: cmd c8/00:80:35:af:72/00:00:00:00:00/e0 tag 0 cdb 0x0 data 65536 in
Feb 7 18:57:22 mepis1 kernel: res 51/84:00:b4:af:72/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Feb 7 18:57:22 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:22 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:22 mepis1 kernel: ata1: EH complete
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:22 mepis1 kernel: ndiswrapper version 1.47 loaded (smp=yes)
Feb 7 18:57:22 mepis1 kernel: usbcore: registered new interface driver ndiswrapper
Feb 7 18:57:22 mepis1 kernel: fuse init (API version 7.8)
Feb 7 18:57:22 mepis1 kernel: fuse distribution version: 2.7.0
Feb 7 18:57:22 mepis1 kernel: Adding 522072k swap on /dev/sda7. Priority:1 extents:1 across:522072k
Feb 7 18:57:22 mepis1 kernel: pcmcia: Detected deprecated PCMCIA ioctl usage from process: discover.
Feb 7 18:57:22 mepis1 kernel: pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
Feb 7 18:57:22 mepis1 kernel: pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
Feb 7 18:57:22 mepis1 kernel: cs: memory probe 0xa0000000-0xa0ffffff: excluding 0xa0000000-0xa00fffff
Feb 7 18:57:22 mepis1 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Feb 7 18:57:22 mepis1 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Feb 7 18:57:22 mepis1 kernel: eth0: link down
Feb 7 18:57:22 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 7 18:57:22 mepis1 kernel: ata1.00: cmd c8/00:80:bd:83:75/00:00:00:00:00/e0 tag 0 cdb 0x0 data 65536 in
Feb 7 18:57:22 mepis1 kernel: res 40/00:00:b4:af:72/00:00:00:00:00/e0 Emask 0x4 (timeout)
Feb 7 18:57:22 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:22 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:22 mepis1 kernel: ata1: EH complete
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:22 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Feb 7 18:57:22 mepis1 kernel: ata1.00: (BMDMA stat 0x24)
Feb 7 18:57:22 mepis1 kernel: ata1.00: cmd c8/00:00:75:fd:72/00:00:00:00:00/e0 tag 0 cdb 0x0 data 131072 in
Feb 7 18:57:22 mepis1 kernel: res 51/84:00:74:fe:72/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Feb 7 18:57:22 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:22 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:22 mepis1 kernel: ata1: EH complete
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:22 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 7 18:57:22 mepis1 kernel: ata1.00: cmd c8/00:00:b5:e2:73/00:00:00:00:00/e0 tag 0 cdb 0x0 data 131072 in
Feb 7 18:57:22 mepis1 kernel: res 40/00:00:74:fe:72/00:00:00:00:00/e0 Emask 0x4 (timeout)
Feb 7 18:57:22 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:22 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:22 mepis1 kernel: ata1: EH complete
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:22 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:22 mepis1 kernel: NET: Registered protocol family 10
Feb 7 18:57:22 mepis1 kernel: lo: Disabled Privacy Extensions
Feb 7 18:57:22 mepis1 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 7 18:57:23 mepis1 kernel: lp0: using parport0 (interrupt-driven).
Feb 7 18:57:23 mepis1 kernel: ppdev: user-space parallel port driver
Feb 7 18:57:55 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 7 18:57:55 mepis1 kernel: ata1.00: cmd c8/00:e8:f5:d3:74/00:00:00:00:00/e0 tag 0 cdb 0x0 data 118784 in
Feb 7 18:57:55 mepis1 kernel: res 40/00:00:74:fe:72/00:00:00:00:00/e0 Emask 0x4 (timeout)
Feb 7 18:57:55 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:55 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:55 mepis1 kernel: ata1: EH complete
Feb 7 18:57:55 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:55 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:55 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:55 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:55 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Feb 7 18:57:55 mepis1 kernel: ata1.00: (BMDMA stat 0x24)
Feb 7 18:57:55 mepis1 kernel: ata1.00: cmd c8/00:00:25:c8:71/00:00:00:00:00/e0 tag 0 cdb 0x0 data 131072 in
Feb 7 18:57:55 mepis1 kernel: res 51/84:00:24:c9:71/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Feb 7 18:57:55 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:55 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:55 mepis1 kernel: ata1: EH complete
Feb 7 18:57:55 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:55 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:55 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:55 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:57:55 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Feb 7 18:57:55 mepis1 kernel: ata1.00: (BMDMA stat 0x24)
Feb 7 18:57:55 mepis1 kernel: ata1.00: cmd c8/00:80:bd:0e:72/00:00:00:00:00/e0 tag 0 cdb 0x0 data 65536 in
Feb 7 18:57:55 mepis1 kernel: res 51/84:00:3c:0f:72/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Feb 7 18:57:55 mepis1 kernel: ata1: soft resetting port
Feb 7 18:57:56 mepis1 kernel: ata1.00: configured for UDMA/25
Feb 7 18:57:56 mepis1 kernel: ata1: EH complete
Feb 7 18:57:56 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:57:56 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:57:56 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:57:56 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 7 18:58:01 mepis1 kernel: powernow_k8: Unknown symbol acpi_processor_notify_smm
Feb 7 18:58:01 mepis1 kernel: powernow_k8: Unknown symbol acpi_processor_unregister_performance
Feb 7 18:58:01 mepis1 kernel: powernow_k8: Unknown symbol acpi_processor_register_performance
Feb 7 18:58:01 mepis1 kernel: powernow_k7: Unknown symbol acpi_processor_notify_smm
Feb 7 18:58:01 mepis1 kernel: powernow_k7: Unknown symbol acpi_processor_unregister_performance
Feb 7 18:58:01 mepis1 kernel: powernow_k7: Unknown symbol acpi_processor_register_performance
Feb 7 18:58:02 mepis1 kernel: acpi_cpufreq: Unknown symbol acpi_processor_notify_smm
Feb 7 18:58:02 mepis1 kernel: acpi_cpufreq: Unknown symbol acpi_processor_unregister_performance
Feb 7 18:58:02 mepis1 kernel: acpi_cpufreq: Unknown symbol acpi_processor_preregister_performance
Feb 7 18:58:02 mepis1 kernel: acpi_cpufreq: Unknown symbol acpi_processor_register_performance
Feb 7 18:58:03 mepis1 kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
Feb 7 18:58:04 mepis1 kernel: ata1.00: limiting speed to PIO4
Feb 7 18:58:04 mepis1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Feb 7 18:58:04 mepis1 kernel: ata1.00: (BMDMA stat 0x24)
Feb 7 18:58:04 mepis1 kernel: ata1.00: cmd c8/00:00:85:2e:74/00:00:00:00:00/e0 tag 0 cdb 0x0 data 131072 in
Feb 7 18:58:04 mepis1 kernel: res 51/84:00:84:2f:74/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
Feb 7 18:58:04 mepis1 kernel: ata1: soft resetting port
Feb 7 18:58:04 mepis1 kernel: ata1.00: configured for PIO4
Feb 7 18:58:04 mepis1 kernel: ata1: EH complete
Feb 7 18:58:04 mepis1 kernel: sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
Feb 7 18:58:04 mepis1 kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 7 18:58:04 mepis1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 7 18:58:04 mepis1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Phil
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#5
Unfortunately that message happens to some users as the 2.6.22 kernel in antiX uses libata and this may cause problems with some hardware, particularly cd players. (even though you didn't boot from cd, it still searches for it during boot)
Now, for some people, installation solves the slow boot, for others it didn't. If you want to try it out you can install from the iso on a hard drive and see what happens. (Booting maybe ok, just the cd won't work properly)
Now, for some people, installation solves the slow boot, for others it didn't. If you want to try it out you can install from the iso on a hard drive and see what happens. (Booting maybe ok, just the cd won't work properly)
-
Posts: 6
- Joined: 28 Jan 2008
#6
Wasn't there a note that Lysistrata was incompatible with PII machines? Just wondering if that has anything to do with the problems you are encountering. I am just going from my poor memory, so I'm sure someone will set me straight. __{{emoticon}}__
Greg in COLD West Michigan
Greg in COLD West Michigan
-
Posts: 10
- Joined: 06 Jan 2008
#7
I am successfully running Lysistrata on old PII laptop without a problem. I am not seeing log errors like the ones above. I did a full install, and in the process completely reformatted my hard drive. My recollection is that Lysistrata wanted ext3 or reiserfs. I created two ext3 partitions and a linux-swap area. I'm not sure how gracefully Lysistrata will deal with other partitions, if your hard drive is formatted in some other way.
-
Posts: 21
- Joined: 17 Jan 2008
#8
I'm running it on my PII IBM 600E (see my thread about it). I see some error messages on booting, MANY related to the sound issue that I have not yet resolved. However, it runs without problems. On my first install I was using EXT3 partitions ( / & /home) and swap, and attempted to keep my prior /home partition without formatting it. I could NOT use the graphical login - I needed to specify nogui in the boot parameters, then use startx after I logged in. I do not know if this problem was because of the EXT3 partitions or because of something in my prior home directory that was incompatible with the graphical login (if that's even possible). I have since wiped the hard drive clean, created newly formatted reiserfs / and /home, and know graphical login works.
I also saw the note about it not working on PII (along with an ambiguous note by someone suggesting that it does work on these machines). Apparently it works fine. Go for it!
I also saw the note about it not working on PII (along with an ambiguous note by someone suggesting that it does work on these machines). Apparently it works fine. Go for it!
-
Posts: 57
- Joined: 28 Jan 2008
#9
Phil
Yes, it's entirely possible. In fact, I'd say that an incompatible configuration found in your old home directory was the likely cause of the problem. Of course, I could be wrong, but it seems much more likely than anything having to do with ext3 partitions.tip184 wrote:I could NOT use the graphical login - I needed to specify nogui in the boot parameters, then use startx after I logged in. I do not know if this problem was because of the EXT3 partitions or because of something in my prior home directory that was incompatible with the graphical login (if that's even possible).
Phil
-
Posts: 57
- Joined: 28 Jan 2008
#10
Out of curiosity, I removed the floppy drive and connected it to the laptop with a cable. Then I inserted the DVD-ROM drive. I wanted to see if some of the errors could've been due to antiX looking for a CD-ROM or DVD-ROM drive and not finding one.
BIG mistake. The first time I tried, antiX died pretty soon into the boot process. There were lots of squashfs errors-- a page or more of them-- and then things just suddenly stopped. The second time I tried, the squashfs errors occurred again, but the boot process didn't stop. Slowly, after lots of segmentation faults, antiX presented me with a console log in prompt. I logged in, became root with su, and then issued the halt command. I could have tried to do more, but I didn't want to press my luck.
Phil
BIG mistake. The first time I tried, antiX died pretty soon into the boot process. There were lots of squashfs errors-- a page or more of them-- and then things just suddenly stopped. The second time I tried, the squashfs errors occurred again, but the boot process didn't stop. Slowly, after lots of segmentation faults, antiX presented me with a console log in prompt. I logged in, became root with su, and then issued the halt command. I could have tried to do more, but I didn't want to press my luck.
Phil
-
Posts: 57
- Joined: 28 Jan 2008
#11
Phil
I believe you are right that the kernel is what's causing the problem. Would it be possible to use an older kernel? And I don't mean installing antiX and then installing an older kernel. What I am talking about is mounting the ISO image, navigating to the /boot directory, and installing a Debian Etch kernel, or another suitable kernel that has a version number lower than 2.6.20.anticapitalista wrote:Unfortunately that message happens to some users as the 2.6.22 kernel in antiX uses libata and this may cause problems with some hardware, particularly cd players.
Phil
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#12
I'm not sure you can do it that way Phil, though it would be great if you succeed.
I know someone had the same problem that you are having (with a beta version of antiX-M7), but managed to install antiX to hd and then install a Debian 2.6.18 kernel.
You could even install a newer kernel version if you know what you are doing.
I know someone had the same problem that you are having (with a beta version of antiX-M7), but managed to install antiX to hd and then install a Debian 2.6.18 kernel.
You could even install a newer kernel version if you know what you are doing.