RE: X starts, but it displays strange things
Evening all. I'm experiencing the same thing on my blue iBook/Firewire. I'm running 2.4.1-test7 and 4.0.2-1puetzk. I get exactly the same results with 2.4.0-test10 and the straight Debian 4.0.2-1 or any combination of. The screen looks like theres a couple of extra bytes per row inserted, such that the second row starts 1cm from the left, the third row 2cm in, etc. The cursor comes up fine and moves fine, and if you pop up windows and pretend you can make them out and move them around. I am very suspicious of the (--) R128(0): Virtual size is 800x600 (pitch 832) line below. There is a 25 step staircase of black lines that seem to be due to the offsetting of each line, and 800/25 = 32. I'm going to have a look at the xf source next to see what 'pitch' means. -- Michael The output of startx follows (sorry). XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.18 ppc [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Sat Jan 20 17:11:39 2001 (==) Using config file: "/etc/X11/XF86Config-4" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Generic Monitor" (**) | |-->Device "Generic Graphics Device" (**) |-->Input Device "Generic Keyboard" (**) XKB: rules: "xfree86" (**) XKB: model: "macintosh" (**) XKB: layout: "us" (**) |-->Input Device "Generic Mouse" (**) FontPath set to "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/cyrillic,/usr/l ib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fo nts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts /75dpi" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 ioBase_phys = 0xf000 (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (--) PCI:*(0:16:0) ATI Rage 128 Mobility LF rev 2, Mem @ 0x9400/26, 0x90 00/14, I/O @ 0x0400/8 (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (WW) Warning, couldn't open module dri (EE) Failed to load module "dri" (module does not exist, 0) (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Module pex5: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.13.0 (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a (II) Module freetype: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.1.8 (II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a (II) Module speedo: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libint10.a (II) Module int10: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o (II) Module ati: vendor
RE: X starts, but it displays strange things: Success!
Yay! I trimmed back the monitor capabilities to something silly. This got rid of all the XF86 built in modes, making it use the frame buffer settings. I finally have accelerated support under X :) My Monitor section now looks like this: Section "Monitor" Identifier "Generic" HorizSync 28-38 VertSync43-50 EndSection Section "Device" Identifier "Generic" Driver "r128" BusID "PCI:0:16:0" Option "UseFBDev" EndSection -- Michael On Sat, 20 Jan 2001, Michael Hope wrote: > Evening all. I'm experiencing the same thing on my blue iBook/Firewire. > I'm running 2.4.1-test7 and 4.0.2-1puetzk. I get exactly the same results > with 2.4.0-test10 and the straight Debian 4.0.2-1 or any combination of. > The screen looks like theres a couple of extra bytes per row inserted, > such that the second row starts 1cm from the left, the third row 2cm in, > etc. The cursor comes up fine and moves fine, and if you pop up windows > and pretend you can make them out and move them around. > > I am very suspicious of the > > (--) R128(0): Virtual size is 800x600 (pitch 832) > > line below. There is a 25 step staircase of black lines that seem to be > due to the offsetting of each line, and 800/25 = 32. I'm going to have a > look at the xf source next to see what 'pitch' means. > > -- Michael > > The output of startx follows (sorry). > > XFree86 Version 4.0.2 / X Window System > (protocol Version 11, revision 0, vendor release 6400) > Release Date: 18 December 2000 > If the server is older than 6-12 months, or if your card is > newer than the above date, look for a newer version before > reporting problems. (See http://www.XFree86.Org/FAQ) > Operating System: Linux 2.2.18 ppc [ELF] > Module Loader present > (==) Log file: "/var/log/XFree86.0.log", Time: Sat Jan 20 17:11:39 2001 > (==) Using config file: "/etc/X11/XF86Config-4" > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (??) unknown. > (==) ServerLayout "Default Layout" > (**) |-->Screen "Default Screen" (0) > (**) | |-->Monitor "Generic Monitor" > (**) | |-->Device "Generic Graphics Device" > (**) |-->Input Device "Generic Keyboard" > (**) XKB: rules: "xfree86" > (**) XKB: model: "macintosh" > (**) XKB: layout: "us" > (**) |-->Input Device "Generic Mouse" > (**) FontPath set to > "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/cyrillic,/usr/l > ib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fo > nts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts > /75dpi" > (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (--) using VT number 7 > > ioBase_phys = 0xf000 > (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a > (II) Module bitmap: vendor="The XFree86 Project" > compiled for 4.0.2, module version = 1.0.0 > (II) Loading /usr/X11R6/lib/modules/libpcidata.a > (II) Module pcidata: vendor="The XFree86 Project" > compiled for 4.0.2, module version = 0.1.0 > (II) Loading /usr/X11R6/lib/modules/libscanpci.a > (II) Module scanpci: vendor="The XFree86 Project" > compiled for 4.0.2, module version = 0.1.0 > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > (--) PCI:*(0:16:0) ATI Rage 128 Mobility LF rev 2, Mem @ 0x9400/26, > 0x90 > 00/14, I/O @ 0x0400/8 > (II) Loading /usr/X11R6/lib/modules/libddc.a > (II) Module ddc: vendor="The XFree86 Project" > compiled for 4.0.2, module version = 1.0.0 > (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a > (II) Module GLcore: vendor="The XFree86 Project" > compiled for 4.0.2, module version = 1.0.0 > (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a > (II) Module dbe: vendor="The XFree86 Project" > compiled for 4.0.2, module version = 1.0.0 > (WW) Warning, couldn't open module dri > (EE) Failed to load module "dri" (module does not exist, 0) > (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a > (II) Module extmod: vendor="The XFree86 Project" > compiled for 4.0.2, module version = 1.0.0 > (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a > (II) Module glx: vendor="The XFree86 Project" > compiled for 4.0.2, module vers
Re: X starts, but it displays strange things
I've put a copy of my XF86Config-4 at http://juju.net.nz/michaelh/stuff/ Again, this is against kernel 2.4.0-test11 with xserver-xfree86-4.0.2-1. My yaboot.conf section is close to: image=/boot/vmlinux-2.4.0-test11-good label=good root=/dev/hda10 read-only append="video=aty128fb:vmode:10:depth:8:" -- Michael On Sun, 21 Jan 2001, Christian Pernegger wrote: > On Sat, Jan 20, 2001 at 07:19:01PM -0600, Michael Hope wrote: > > Evening all. I'm experiencing the same thing on my blue iBook/Firewire. > > I'm running 2.4.1-test7 and 4.0.2-1puetzk. I get exactly the same results > > with 2.4.0-test10 and the straight Debian 4.0.2-1 or any combination of. > > The screen looks like theres a couple of extra bytes per row inserted, > > such that the second row starts 1cm from the left, the third row 2cm in, > > etc. The cursor comes up fine and moves fine, and if you pop up windows > > and pretend you can make them out and move them around. > > Could you perhaps send me your X-Free configuration file and the > fb settings you use? I don't even get that far... > > Thanks > > Christian >
RE: X starts, but it displays strange things
On Mon, 22 Jan 2001, Bastien Nocera wrote: > Quoting Michael Schmitz <[EMAIL PROTECTED]>: > > > > > It's what you suspect: the offset between the start of consecutive > > scan > > > > lines in memory. No idea why the r128 driver would pick that pitch > > though. > > > > > > Perhaps because the RAGE128 needs line lenghts that are multiples of > > 64? > > > > Does it? If that's the case, why would the X server not honor the pitch > > (as it seems, from the description of the staircase effect)? > > > > But maybe that wasn't caused by the pitch/line_len but by weird mode > > settings. hsync 28-38 and vsync 43-50 still look crummy to me though. > > Definetely, > My XF86Config for iBook users (although you'll need to change r128 to ati as > I > understood) has the correct timings for the LCD screen. > That is: > Section "Monitor" > Identifier "Monitor0" > VendorName "Apple Computer" > ModelName"LCD Screen" > HorizSync30-40 > VertRefresh 60-70 > Mode "800x600" > DotClock 40.001 > HTimings 800 858 986 1056 > VTimings 600 601 605 628 > Flags "+HSync" "+VSync" > EndMode > EndSection No change, sorry. Still claims a pitch of 832, and the screen is still screwed up. Note that the vsync 43-50 was a hack to force the driver to use the fb settings by invalidating the built in modes. The r128 doesnt seem to require a multiple of 64 line width, as it works OK against the fb, but it may perfer it. -- Michael > I'd like both of the persons who had problems (I think Michael Hope got it to > work though) to test this with their machines. Before blaming the driver, we > must make sure that the user is not causing the error (don't take that as an > insult, it's not one). > These timings are the same for old iBooks (mach64 based) and the new ones > (r128 > based) as the LCD is the same. > > Cheers > > /Bastien Nocera, who wants a 15" LCD screen on his iBook >
Re: pmud on iBook questions
> On Tue, Jan 23, 2001 at 07:03:45PM +0100, Christian Pernegger wrote: > > The 'fbset 0' command does nothing useful. > > That should be 'fblevel off', I think. Would make more sense. On my machine, fblevel changes the backlight level with 'fblevel 1' turning it right down a'la MacOS and fblevel 0 turning it off. You may not have support for it turned on in your kernel. I'm running 2.4.0-test11 with these options under 'Macintosh Device Drivers' [*] Support for CUDA based PowerMacs [*] Support for PMU based PowerMacs [*]Power management support for PowerBooks [*]Backlight control for LCD screens -- Michael
Re: me too (X4.0.2 on iBook Firewire)
On Thu, 25 Jan 2001, Michel [iso-8859-1] Dänzer wrote: > Bastien Nocera wrote: > > > I also upgraded my iBook Firewire to sid, and I have the same pb as Michael > > Hope and Christian Pernegger. > > Pitch is also reported as 832. I tried disabling Acceleration, changing > > colour depths, "ati" and "r128" as the name of the driver. Using the fbdev > > driver works though. > > Have you tried Option "ProgramFPRegs" "No" instead of UseFBDev? I tried it a few days ago. No change, except for the server printing a big size warning about blowing up your flat panel :) -- Michael > > > > Could it be that the old ati driver (for mach64 cards) wants a pitch > > multiple of 64 to use the acceleration, and it's leaked to the r128 driver ? > > I mean that the r128 part of the driver is using a way of calculating the > > pitch that is different from what it was before. > > Very unlikely. The r128 part is basically the same as the old r128 driver. It > does all device dependent stuff. > > > Michel > > > -- > Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer > CS student, Free Software enthusiast \XFree86 and DRI project member > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: me too (X4.0.2 on iBook Firewire)
On Thu, 25 Jan 2001, Michel [iso-8859-1] Dänzer wrote: > Michael Hope wrote: > > > > On Thu, 25 Jan 2001, Michel [iso-8859-1] Dänzer wrote: > > > > > Bastien Nocera wrote: > > > > > > > I also upgraded my iBook Firewire to sid, and I have the same pb as > > > > Michael Hope and Christian Pernegger. > > > > Pitch is also reported as 832. I tried disabling Acceleration, changing > > > > colour depths, "ati" and "r128" as the name of the driver. Using the > > > > fbdev driver works though. > > > > > > Have you tried Option "ProgramFPRegs" "No" instead of UseFBDev? > > > > I tried it a few days ago. No change, except for the server printing a > > big size warning about blowing up your flat panel :) > > Strange, it worked for Bastien - did you really disable UseFBDev? No :) I probably tried it with both on. -- Michael > > > Michel > > > -- > Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer > CS student, Free Software enthusiast \XFree86 and DRI project member >
Re: 2nd and 3rd mouse buttons in XF4.0.2
> I'm trying to get a 2nd and 3rd mouse button working in XFree 4.0.2. I'm > running kernel 2.4.2-pre3 from bitkeeper's sources. I have the following > relevant options in my kerenl conifg: > > CONFIG_USB=y > CONFIG_USB_HID=y > CONFIG_INPUT_KEYBDEV=y > CONFIG_INPUT_MOUSEDEV=y > CONFIG_INPUT_EVDEV=y > CONFIG_INPUT_ADBHID=y > > > /etc/sysctl.conf: > > dev.mac_hid.mouse_button2_keycode = 101 > dev.mac_hid.mouse_button3_keycode = 109 > dev.mac_hid.mouse_button_emulation = 1 I did a grep for 101 and 109 across linux/include/input.h - 101 is the lineffed key (?) and 109 is the pagedown key. Personally I use echo 1 > /proc/sys/dev/mac_hid/mouse_button_emulation echo 87 > /proc/sys/dev/mac_hid/mouse_button2_keycode echo 88 > /proc/sys/dev/mac_hid/mouse_button3_keycode which sets F11 to the MMB and F12 to the RMB. -- Michael
Re: 2nd and 3rd mouse buttons in XF4.0.2
On Mon, 12 Mar 2001, Paolo Redaelli wrote: > Michael Hope wrote: > > > > > I'm trying to get a 2nd and 3rd mouse button working in XFree 4.0.2. I'm > > > running kernel 2.4.2-pre3 from bitkeeper's sources. I have the following > > > relevant options in my kerenl conifg: > > > > > > CONFIG_USB=y > > > CONFIG_USB_HID=y > > > CONFIG_INPUT_KEYBDEV=y > > > CONFIG_INPUT_MOUSEDEV=y > > > CONFIG_INPUT_EVDEV=y > > > CONFIG_INPUT_ADBHID=y > > > > > > > > > /etc/sysctl.conf: > > > > > > dev.mac_hid.mouse_button2_keycode = 101 > > > dev.mac_hid.mouse_button3_keycode = 109 > > > dev.mac_hid.mouse_button_emulation = 1 > > > > I did a grep for 101 and 109 across linux/include/input.h - 101 > > is the lineffed key (?) and 109 is the pagedown key. Personally I use > > > > echo 1 > /proc/sys/dev/mac_hid/mouse_button_emulation > > echo 87 > /proc/sys/dev/mac_hid/mouse_button2_keycode > > echo 88 > /proc/sys/dev/mac_hid/mouse_button3_keycode > > > > which sets F11 to the MMB and F12 to the RMB. > Mhmhm I've an iBook and I would prefer the small enter (near > spacebar) for 2nd button and right option for the 3rd. Does anyone know > their codes? > 10x in advance and cheers Here's what I found: showkeys maps the small enter as code 76 (0x4c) and the right option as code 58 (0x3a). According to src/linux/drivers/macintosh/mackeymap.map, 0x4c is mapped to KP_Enter and 0x3a is mapped to AltGr. According to src/linux/include/linux/input, KEY_KPENTER is code 96 and there is no AltGR. So the short version of the story is, use 96 for the small enter. I don't think you can get the right option as it has already been swallowed by a lower layer. I don't know much about this system, but you could try remapping the option key to something else like right alt and then use right alt's keycode. How I don't know :) -- Michael > -- > ++-+-+ > | Paolo Redaelli | [EMAIL PROTECTED] | http://redaelli.mine.nu/~paolo/ > | > ++-+-+ >
KDE 2.1 packages.
Sorry if this is covered in a FAQ somewhere, but I've managed to build KDE 2.1 for Debian PowerPC and I was wondering if anyone else is interested in them, or even if they could be used to replace the old ones in the main archive? There was some weird bug involving make and one of the language packages in kdelibs that I hacked around but did not fix. Who should I contact about the hack/fix? -- Michael
Re: 2nd and 3rd mouse buttons in XF4.0.2
On Tue, 13 Mar 2001, Grant Miller wrote: > On Sun, Mar 11, 2001 at 02:15:15PM -0600, Michael Hope wrote: > > > I'm trying to get a 2nd and 3rd mouse button working in XFree 4.0.2. I'm > > > running kernel 2.4.2-pre3 from bitkeeper's sources. I have the following > > > relevant options in my kerenl conifg: > > > > > > CONFIG_USB=y > > > CONFIG_USB_HID=y > > > CONFIG_INPUT_KEYBDEV=y > > > CONFIG_INPUT_MOUSEDEV=y > > > CONFIG_INPUT_EVDEV=y > > > CONFIG_INPUT_ADBHID=y > > > > > > > > > /etc/sysctl.conf: > > > > > > dev.mac_hid.mouse_button2_keycode = 101 > > > dev.mac_hid.mouse_button3_keycode = 109 > > > dev.mac_hid.mouse_button_emulation = 1 > > > > I did a grep for 101 and 109 across linux/include/input.h - 101 > > is the lineffed key (?) and 109 is the pagedown key. Personally I use > > > > echo 1 > /proc/sys/dev/mac_hid/mouse_button_emulation > > echo 87 > /proc/sys/dev/mac_hid/mouse_button2_keycode > > echo 88 > /proc/sys/dev/mac_hid/mouse_button3_keycode > > > > > I tried those numbers and 67 (F9) and 68 (F10) and that didn't work. I > press on those keys and I don't get a response from X. I ran xev (X event > viewer) and there were no events reported when I pressed on F9 or F10. Hmm. Something else is going on then. 67 and 68 work fine for me. Do the echo lines above do anything? -- Michael
Re: 2.4.19 -- no sound
On 28 Aug 2002, A.J. Rossini wrote: > > "rogério" == Rogério Brito <[EMAIL PROTECTED]> writes: > > rogério> On Aug 28 2002, Paul Talacko wrote: > >> As I posted in a previous thread, I've upgraded to 2.4.19 which has > >> got my RTL8029 working, but now I have no sound. > > rogério> Are you using the kernel from benh's tree or are you using a > rogério> stock kernel? You can get benh's kernel via rsync from > rogério> rsync.penguinppc.org. > > I'm seeing something similar; I can get beeps and such, but no "real" > audio (i.e. using arts or esd for mp3s in their respective user > environments). > > This was using benh's 2.4.19 (final) tree... > > (on the other hand, I've completely solved my X and "sleep" problems, > thanks to the list). I'm seeing the same on my iBook Firewire with 2.4.19-benh0 under Debian 3.0/KDE3.0. The console beeps work fine but xmms and mpg123 report that they can't open the dsp. The permissions are fine, it works if I revert to 2.4.18-pre, the node in /dev exists, and being root doesn't help. Perhaps it is something to do with devfsd? I thought in previous versions the dsp appeared on /dev/sound/dsp/0 but now it appears on /dev/sound/dsp. -- Michael
Re: how to downgrade
On Sat, 2002-11-30 at 22:00, Chris Tillman wrote: > On Sat, Nov 30, 2002 at 08:52:58PM -0800, Ashifi wrote: > > I just upgraded to the "unstable" branch, and although i've got Gnome 2 > > going, I can't get sawfish, nor any other window manager going. It > > tells me it had an error with the authentication method, hence all my > > applications open windowless (pretty annoying!) > > > > Should I downgrade? How can I install a window manager? Incidentally, I had similar problems. After upgrading to unstable about a month ago I couldn't get any display manager except gdm up and going. All others reported problems with authentication, especially X magic cookie authentication. I've never tried it, but dpkg does have a --force-downgrade option. I don't know how this interacts with apt (you may have to download the pacakges yourself) nor with meta packages such as gnome2. Sorry, not a helpful answer. -- Michael
Re: Mysterious drive access and battery life
Hi Mark. I had a fiddle with my machine a month ago, and here's what I found: 1. Most accesses are due to updating the file access time. Turning this off gets rid of alot of redundant writes. To turn it off, add the 'noatime' flag to your fstab and either reboot or re-mount the partition. 2. On Ext2 and probably XFS you can use the noflushd daemon. This changes the kernel operation so that dirty data isn't flushed to the hard disk unless the disk is running. This could lead to lost data and doesn't work with Ext3 or Reiser. -- Michael On Tuesday, December 17, 2002, at 04:16 PM, Mark Williams wrote: Hello all, I am the proud owner of a 700 MHz 12.1" iBook2. Debian sid is working perfectly on it (with sleep and dri and everything!) and running faster than MacOS X. Go figure. There's just one problem. After changing my setup in accordance with the information on http://bulmalug.net/body.phtml?nIdNoticia=1511 and http://bulmalug.net/body.phtml?nIdNoticia=1481&nIdPage=5, I was able to get pmud working. However, the hard drive is accessed once every couple of seconds, preventing it from spinning down properly. This knocks a good hour or so off my battery life. In an attempt to figure out exactly what's going on, I dropped into single user mode and set the drive spindown delay to 5 seconds. The clicks that accompany drive access continued... Has anyone had a similar experience? Thanks to everyone for all their help on this list! Cheers, Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] PGP.sig Description: PGP signature
Re: Mysterious drive access and battery life
On Tuesday, December 17, 2002, at 06:52 PM, Mark Williams wrote: Thanks for your response! I added noatime to the relevant fstab line: /dev/hda11 / ext2errors=remount-ro,noatime 0 1 but the drive still clicks to life every now and then. This is no good! Will noflushd have any more luck than hdparm? Just to check, did you restart or re-mount the drive? These options only take effect at mount time. How often does the drive click? On mine, which had a Toshiba drive in it, I'd hear it click as the heads parked about once every five seconds before making the changes. If it's not a regular five-ish seconds, what type of things are you doing when the drive runs? Are there any processes running that might be causing it? noflushd is a different approach to hdparm. From what I remember from the noflushd readme, the kernel has a set of disk block buffers in it. These buffers become dirty, i.e. out of date, whenever a process tries to write to disk. If it's a small write then these dirty buffers are allowed to build up until they are flushed out to the disk, which I think normally happens every five seconds. noflushd inhibits this automatic flush, leaving the dirty buffers in memory and letting the disk spin down. -- Michael PGP.sig Description: PGP signature
Unable to boot after lockup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry if this is the wrong list, but I've hit an interesting problem. My iBook Firewire locked up while I was working in Emacs, and now the machine won't boot any more. Specifically, I was in KDE with Emacs and a few shells open writing some code. On one operation the Emacs screen stopped painting. The shells would still paint, but no apps would load. 'ps' stopped one shell working, then the other stopped. I've seen similar before when the HDD wouldn't spin up ages ago. After powering down, the mac 'Can't find a startup disk' icon flashes. Booting the Mac restore CD and running the disk manager shows the main drive as uninitialised, and Apple System Profiler shows the disk as there but having no partitions. I can hear the disk spinning. The machine is running Mac OS 9.1, a recent Debian/unstable, a stock 2.4.17+ext3 kernel, and yaboot 1.3.3 patched for ext3. And, no, I wasn't doing anything evil before it happened :) It seems that I've lost my partition table, and perhaps more. Any suggestions for recovering my data? I have access to a x86 Linux machine, but I don't know if ext3 fiddles with the byte order. - -- Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (OpenBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxSUn4ACgkQ3L3H1ImjCiR0gwCfV+hUC7XI6/XlONyhJsyREjGp qrIAoIvvFQEOkQaBCOwlcpJc+bOfKDHm =JSaj -END PGP SIGNATURE-
Re: Noisy HD of an iBook
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 21 Feb 2002, [iso-8859-1] Rogério Brito wrote: > On Feb 22 2002, Woo-il Song wrote: > > My HDD seems to be *a little* noisy after I've changed filesystem > > from ext2 to ext3. Do you use ext3? > > Well, first of all, let me say that the noises the HD is > producing are similar to the noises produced by a Desktop HD > when its head is jumping in non-sequential reads. It could depend on who the original manufacturer of the drive is. My iBook FW started out with a nice and quiet Fujutisu. After a HDD failure it now has a Toshiba inside it, which is quieter in normal operation but has a noisy 'clunk' when the heads park shortly after an operation. I had another Toshiba drive that did the same thing, so I guess it's a feature. My iBook FW at work started out with a very noisy IBM drive - this thing had about three different sets of noises it made and would change through them during the day. It would be interesting to see (using hdparam) who makes your drive. Bets on it being IBM. - -- Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (OpenBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjx2dosACgkQ3L3H1ImjCiRkvgCfYtSzi8sUwYlbOCTDl0OXmzQa tjQAoKMGXCqgoJNUQMgnma9RxcDwkLAJ =L36+ -END PGP SIGNATURE-
