Hi Vincent, Sounds like a bug report to me :)
Suggestions? Why not downgrade to 2.6.17 and lick your wounds while developers find what's amiss? YMMV but I've found 2.6.17.13 to be the most stable of kernels supporting Apple hardware.... They don't call it the bleeding edge for nothin'! :) Jay --- Vincent Rubiolo <[EMAIL PROTECTED]> wrote: > Hello list, > > My iMac running 2.6.18 (mactel-patchset minus sigmatel one) is slowly > > being becoming usable for a day-to day multimedia workstation. I > however > still have issues and I am looking for pointers to help me pinpoint > them. > > Here are the issues I have: > 1. The machine is slow to boot. It waits perhaps 30 secs probing the > SATA drive, telling me the drive is slow to respond: > > ata1: SATA max UDMA/133 cmd 0xE0836100 ctl 0x0 bmdma 0x0 irq 233 > > ata2: SATA max UDMA/133 cmd 0xE0836180 ctl 0x0 bmdma 0x0 irq 233 > > ata3: SATA max UDMA/133 cmd 0xE0836200 ctl 0x0 bmdma 0x0 irq 233 > > ata4: SATA max UDMA/133 cmd 0xE0836280 ctl 0x0 bmdma 0x0 irq 233 > > scsi0 : ahci > > ata1: SATA link down (SStatus 0 SControl 0) > > scsi1 : ahci > > ata2: SATA link down (SStatus 0 SControl 0) > > scsi2 : ahci > > ata3: port is slow to respond, please be patient > > ata3: port failed to respond (30 secs) > > ata3: softreset failed (device not ready) > > ata3: softreset failed, retrying in 5 secs > > ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > > ata3.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth > 31/32) > > ata3.00: ata3: dev 0 multi count 0 > > ata3.00: configured for UDMA/133 > > This did not occur w/ 2.6.17 AFAIK. > > 2. The GNOME automounters have issues. A newly inserted drive can > work > out of the box but most of the time it does not. I am greeted with a > nasty error when I try to access it (attached). This is surely > related > to the problem above. Note that command-line mount works fine; a > manually mounted drive will be fine (read/write) in GNOME. > > 3. I keep having an USB device which permanently connects/disconnects > > (see end of dmesg output). This can make a console inusable. I don't > know which one it is. > > That's it. I am looking for hints and pointers on where to go from > here > but I don't know where to start. > > Thanks for your suggestion experts, > > Vincent > > PS: as for the liveCD, only the last but one works. The last one > simply > does not boot. This might be related to the IDE problem above. > > libhal-storage.c 1344 : info: called libhal_free_dbus_error but > dbuserror was not set. > libhal-storage.c 1345 : info: called libhal_free_dbus_error but > dbuserror was not set. > libhal-storage.c 1401 : info: called libhal_free_dbus_error but > dbuserror was not set. > process 6439: applications must not close shared connections - see > dbus_connection_close() docs. this is a bug in the application. > mount: wrong fs type, bad option, bad superblock on /dev/sdb, > missing codepage or other error > in some cases useful info is found in syslog - try > dmesg | tail or so > mount: wrong fs type, bad option, bad superblock on /dev/sdb, > missing codepage or other error > in some cases useful info is found in syslog - try > dmesg | tail or so > erreur: impossible d'exécuter pmount > > # > # Automatically generated make config: don't edit > # Linux kernel version: 2.6.18-mactel > # Sun Oct 29 13:14:51 2006 ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mactel-linux-users mailing list Mactel-linux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mactel-linux-users
