Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper
On Fri, Aug 11, 2006 at 12:32:34AM +0200, Børge Holen wrote: On Friday 11 August 2006 00:17, Adam D wrote: Adam D wrote: BXrge Holen wrote: On Thursday 10 August 2006 23:53, Adam D wrote: OK, I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3 as the file system and it works for now instead of booting into xfs. Upon startup and starting the network interfaces and then the portmap the fan turns on full throttle and spins for a while. It is semi loud and is rather annoying. Is there a way not to have the fan spin when booting into Ubunto on startup? Is the fan a problem? As in; a fault that make it spin, instead of temp.? Anyway, I believe I had some sort of unagreement with my fan together with kernel 2.6.8, while at it, I'm not completely sure. -Adam Guess one would say it is not a problem however when booting into OSX the fan does not turn on unless of something really pushing the CPU hard. On Ubuntu the fan is extremely sensitive and turns on with the slightest thing running. Yes, that could be what I mentioned, I installed debian testing and a vanilla kernel, problem solved. Can you file a bug report, including a diff of your .config and the debian stock one, as well as the version used ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 17 Powerbook fan turns on when starting into Ubuntu Dapper
On Friday 11 August 2006 08:11, Sven Luther wrote: On Fri, Aug 11, 2006 at 12:32:34AM +0200, Børge Holen wrote: On Friday 11 August 2006 00:17, Adam D wrote: Adam D wrote: BXrge Holen wrote: On Thursday 10 August 2006 23:53, Adam D wrote: OK, I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3 as the file system and it works for now instead of booting into xfs. Upon startup and starting the network interfaces and then the portmap the fan turns on full throttle and spins for a while. It is semi loud and is rather annoying. Is there a way not to have the fan spin when booting into Ubunto on startup? Is the fan a problem? As in; a fault that make it spin, instead of temp.? Anyway, I believe I had some sort of unagreement with my fan together with kernel 2.6.8, while at it, I'm not completely sure. -Adam Guess one would say it is not a problem however when booting into OSX the fan does not turn on unless of something really pushing the CPU hard. On Ubuntu the fan is extremely sensitive and turns on with the slightest thing running. Yes, that could be what I mentioned, I installed debian testing and a vanilla kernel, problem solved. Can you file a bug report, including a diff of your .config and the debian stock one, as well as the version used ? Within the weekend. Dunno 'bout the ubuntu, but I'll fetch the stock deb. Both the 2.6.8 and 2.6.15, can't remember witch one I used, but the problems sounds just the same. Friendly, Sven Luther -- --- Børge Kennel Arivene http://www.arivene.net ---
Re: Quik and atyfb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10 Aug 2006, at 22:19, Holger Levsen wrote: Hi, On Saturday 15 July 2006 17:17, Ben Racher wrote: So my Powerbook G3 266mhz Wallstreet is now successfully running Debian, however its a little slow. And I suspect the culprit is the video acceleration that is issued by quik when you first load the kernel. I've been using: video=atyfb:vmode:16,cmode:32,mclk:67 However, it doesn't seem to let me boot, as a get a crazy mess of graphics going hangwire. Is there something in quik that needs to changed, or is the above command incorrect? have you tried just using video=atyfb ? According to http://www.jonh.net/lppcfom-serve/cache/1043.html you should use a cmode of 24 and probably also a lower vmode. Whats mclk? Yes, just using video=atyfb causes the same issue. There is a difference somewhere in the way quik configures stuff and the way BootX/miBoot do it, using video=atyfb (+ all the various gubbins) from a BootX / miBoot boot works fine and gives you accelerated video, the same from a quik boot results in garbage. It's a bit of a pain, to be frank, but I don't currently have the time to delve into the source of both to see what is happening. Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (Darwin) iEYEARECAAYFAkTcMrUACgkQRKxFDFDQaY0zHACgpwSOooWsX7NfqUQLu0N2Hqlt qlkAnRxViDx3yqM84/qtoxmrxsWQaCLd =Saox -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 17 Powerbook fan turns on when starting (possible initramfs-tools problem ?)
On Fri, Aug 11, 2006 at 08:15:50AM +0200, Børge Holen wrote: On Friday 11 August 2006 08:11, Sven Luther wrote: On Fri, Aug 11, 2006 at 12:32:34AM +0200, Børge Holen wrote: On Friday 11 August 2006 00:17, Adam D wrote: Adam D wrote: BXrge Holen wrote: On Thursday 10 August 2006 23:53, Adam D wrote: OK, I decided to just install Ubuntu on the 2nd Gen 17 powerbook with ext3 as the file system and it works for now instead of booting into xfs. Upon startup and starting the network interfaces and then the portmap the fan turns on full throttle and spins for a while. It is semi loud and is rather annoying. Is there a way not to have the fan spin when booting into Ubunto on startup? Is the fan a problem? As in; a fault that make it spin, instead of temp.? Anyway, I believe I had some sort of unagreement with my fan together with kernel 2.6.8, while at it, I'm not completely sure. -Adam Guess one would say it is not a problem however when booting into OSX the fan does not turn on unless of something really pushing the CPU hard. On Ubuntu the fan is extremely sensitive and turns on with the slightest thing running. Yes, that could be what I mentioned, I installed debian testing and a vanilla kernel, problem solved. Can you file a bug report, including a diff of your .config and the debian stock one, as well as the version used ? Within the weekend. Dunno 'bout the ubuntu, but I'll fetch the stock deb. Well, i don't particularly care about ubuntu kernels, especially as i can't do a thing about them :) Both the 2.6.8 and 2.6.15, can't remember witch one I used, but the problems sounds just the same. Please try out 2.6.16 and 2.6.17 in current etch/sid too, but if it is the same windfarm related bug, it is something which needs fixing in initramfs-tools. Adding the corresponding module to /etc/initramfs-tools/modules or whatever it is called should help. maks, can you provide more insight here ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some .debs are 404
Thanks, have you tried the sarge kernels 2.6.8, i believe that officially 2.4 support is plan to be drop in etch. my old worlds seeming to having trouble with latest kernels so i may have to go this route... (have two running sarge with 2.6.8 now ...) I have, but the main sticking point is the switch from BootX-quik to get initrd support (or so I recall). I did it once, but I've since had to reset my PRAM and that sent me back to BootX. I'll sort it out again when I can set aside the time for ''potential recovery operations'' in the event I bolix things up. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
yaboot.conf for dual disk, multi-boot systems?
Greetings- I have yaboot setup on a Pismo courtesy of Debian, a freshly downloaded copy of the Etch net-install CD, everything running fine with a multi-boot OSX/Debian configuration. Right now I'm experimenting with Pocket Linux, and thought I could utilize the Zip drive I have for the Pismo media bay to prepare various Linux configurations to experiment with. First task is/was to get yaboot to want to boot a Zip disk. I've been able to modify my yaboot.conf and install via ybin. What I get on boot when I select my Zip option at the boot: prompt is a file not found for /boot/vmlinux.zip. I tried manually typing in the OF device and partition, but it makes no difference. ofpath and the ofpath shell script both return the same thing. Below is my yaboot.conf. Any suggestions or pointers on how to achieve my goal? Many thanks! Charles Turner [EMAIL PROTECTED] --- yaboot.conf - boot=/dev/hda9 timeout=100 install=/usr/lib/yaboot/yaboot magicboot=/usr/lib/yaboot/ofboot enablecdboot macosx=/dev/hda13 image=/boot/vmlinux label=Linux read-only initrd=/boot/initrd.img device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: partition=11 root=/dev/hda11 image=/boot/vmlinux.zip label=Zip read-only initrd=/boot/initrd.img.zip device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]: partition=2 root=/dev/hde2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some .debs are 404
BootX supports initrd... Rick On Aug 11, 2006, at 9:04 AM, Rich Johnson wrote: Thanks, have you tried the sarge kernels 2.6.8, i believe that officially 2.4 support is plan to be drop in etch. my old worlds seeming to having trouble with latest kernels so i may have to go this route... (have two running sarge with 2.6.8 now ...) I have, but the main sticking point is the switch from BootX-quik to get initrd support (or so I recall). I did it once, but I've since had to reset my PRAM and that sent me back to BootX. I'll sort it out again when I can set aside the time for ''potential recovery operations'' in the event I bolix things up. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
InterScan MSS has quarantined a message
InterScan Messaging Security Suite notification -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some .debs are 404
BootX supports initrd... ... as long as it's named 'ramdisk' or some such, IIRC. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some .debs are 404
On Aug 11, 2006, at 11:08 AM, Michael Schmitz wrote: BootX supports initrd... ... as long as it's named 'ramdisk' or some such, IIRC. Ya' learn something new every day! Alas, it still doesn't sort out ftp.us.debian.org's issues. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some .debs are 404
On Aug 11, 2006, at 11:08 AM, Michael Schmitz wrote: BootX supports initrd... ... as long as it's named 'ramdisk' or some such, IIRC. Michael No... It can be named just about anything. It helps if you put it in the Linux Kernels folder, but even that's not strictly necessary. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some .debs are 404
On Aug 11, 2006, at 1:03 PM, Rich Johnson wrote: On Aug 11, 2006, at 11:08 AM, Michael Schmitz wrote: BootX supports initrd... ... as long as it's named 'ramdisk' or some such, IIRC. Ya' learn something new every day! Alas, it still doesn't sort out ftp.us.debian.org's issues. Indeed. They'll either get it sorted, or they won't. In either case, use a different mirror. Contact me privately (to avoid a /. effect) for a list of the mirrors I've had good luck with recently. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SCSI in alu-book 5.6/5,8 working
Hi all Has anybody been able to attach an external SCSI disk via Firewire 400 to one of the latest alubooks, with recent git-kernels? With this machine it does not work (it never did with any kernel I tried before, IIRC): $ cat /proc/cpuinfo processor : 0 cpu : 7447A, altivec supported clock : 833.333000MHz revision: 0.5 (pvr 8003 0105) bogomips: 16.57 timebase: 832 platform: PowerMac machine : PowerBook5,8 motherboard : PowerBook5,8 MacRISC3 Power Macintosh detected as : 287 (PowerBook G4 15) pmac flags : 0019 L2 cache: 512K unified pmac-generation : NewWorld The SCSI/FW stuff works like a charm on my old Macintosh titanium-IV with exactly the same fresh git-kernel that does not work on the PowerBook5,8 Here's what the failing machine says: --- $ sh kernel-factory/git.08102006/linux-2.6/scripts/ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux debby1-6 2.6.18-rc4-060811-dirty #1 Fri Aug 11 00:16:22 CEST 2006 ppc GNU/ Linux Gnu C 4.1.2 Gnu make 3.81 binutils 2.17 util-linux 2.12r mount 2.12r module-init-tools 3.2.2 e2fsprogs 1.39 pcmcia-cs 3.2.8 Linux C Library2.3.6 Dynamic linker (ldd) 2.3.6 Procps 3.2.7 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.97 udev 093 Modules Loaded raw1394 eth1394 ohci1394 ieee1394 sd_mod sg bluetooth rad eon drm nfs nfsd exportfs lockd nfs_acl sunrpc ipv6 therm_adt746x sr_mod cpufreq _powersave cpufreq_performance scsi_mod apm_emu joydev appletouch usbhid snd_aoa _codec_onyx snd_aoa_fabric_layout snd_aoa pcmcia firmware_class snd_aoa_i2sbus s nd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc sungem sungem_phy pmac _zilog serial_core evdev snd ehci_hcd yenta_socket ohci_hcd rsrc_nonstatic pcmci a_core uninorth_agp agpgart ide_cd soundcore snd_aoa_soundbus usbcore cdrom i2c_ -- SCSI/FW didn't work ever on the new PowerBook5,8. That's why I built this fresh git kernel on the alubook. The kernel built in the end. But no SCSI/FW. available so far. Here's a typical error message I get when plugging the SCSI disk via Firewire to the alubook: Aug 11 23:31:25 debby1-6 kernel: [ 9844.117914] ieee1394: Error parsing configrom for node 0-00:1023 Aug 11 23:31:25 debby1-6 kernel: [ 9844.118123] ieee1394: Node changed: 0-00:1023 - 0-02:1023 Sometimes (it doesn't happen often) the best I get is this when I attach the SCSI disk: - Aug 11 23:53:16 debby1-6 kernel: [11154.413116] ieee1394: Node changed: 0-02:102 3 - 0-00:1023 Aug 11 23:53:21 debby1-6 kernel: [11160.079353] PM: Adding info for ieee1394:003 0ffa046010cd5 Aug 11 23:53:21 debby1-6 kernel: [11160.079456] ieee1394: Node added: ID:BUS[0-0 0:1023] GUID[0030ffa046010cd5] Aug 11 23:53:21 debby1-6 kernel: [11160.079626] ieee1394: Node changed: 0-00:102 3 - 0-02:1023 Aug 11 23:53:21 debby1-6 kernel: [11160.081535] PM: Adding info for ieee1394:003 0ffa046010cd5-0 Aug 11 23:53:21 debby1-6 kernel: [11160.190054] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1) Aug 11 23:53:21 debby1-6 kernel: [11160.190070] ieee1394: sbp2: Try serialize_io =0 for better performance Aug 11 23:53:21 debby1-6 kernel: [11160.191555] scsi2 : SBP-2 IEEE-1394 Aug 11 23:53:21 debby1-6 kernel: [11160.191815] PM: Adding info for No Bus:host2 Aug 11 23:53:23 debby1-6 kernel: [11161.295090] ieee1394: sbp2: Logged into SBP- 2 device Aug 11 23:53:23 debby1-6 kernel: [11161.295728] ieee1394: Node 0-00:1023: Max sp eed [S400] - Max payload [2048] Aug 11 23:53:23 debby1-6 kernel: [11161.295932] PM: Adding info for No Bus:targe t2:0:0 Aug 11 23:53:23 debby1-6 kernel: [11161.301996] Vendor: LSILogic Model: SYM13 FW500-Disk Rev: 1.00 Aug 11 23:53:23 debby1-6 kernel: [11161.302026] Type: Direct-Access ANSI SCSI revision: 00 Aug 11 23:53:23 debby1-6 kernel: [11161.302323] PM: Adding info for scsi:2:0:0:0 Aug 11 23:53:26 debby1-6 udevd-event[5667]: wait_for_sysfs: waiting for '/sys/de vices/pci0002:24/0002:24:0e.0/fw-host0/0030ffa046010cd5/0030ffa046010cd5-0/host2 /target2:0:0/2:0:0:0/ioerr_cnt' failed Aug 11 23:53:53 debby1-6 kernel: [11191.302896] ieee1394: sbp2: aborting sbp2 command Aug 11 23:53:53 debby1-6 kernel: [11191.302912] sd 2:0:0:0: Aug 11 23:53:53 debby1-6 kernel: [11191.302915] command: Test Unit Ready: 00 00 00 00 00 00 Aug 11 23:54:03 debby1-6 kernel: [11201.302892] ieee1394: sbp2: aborting sbp2 command Aug 11 23:54:03 debby1-6 kernel: [11201.302909] sd 2:0:0:0: Aug 11 23:54:03 debby1-6 kernel: [11201.302913] command: Test Unit Ready: 00 00 00 00 00 00 Aug 11 23:54:03 debby1-6 kernel: [11201.302957]
Re: SCSI/Firewire in alu-book 5.6/5,8 not working
Sorry: In my first message I made a mistake in the subject line: It's corrected in this one ... Sorry Wolfgang On Sat, Aug 12, 2006 at 12:16:14AM +0200, Wolfgang Pfeiffer wrote: Hi all Has anybody been able to attach an external SCSI disk via Firewire 400 to one of the latest alubooks, with recent git-kernels? -- Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/ http://profiles.yahoo.com/wolfgangpfeiffer Key ID: E3037113 http://keyserver.mine.nu/pks/lookup?search=0xE3037113fingerprint=on -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI/Firewire in alu-book 5,8 not working
On Sat, Aug 12, 2006 at 12:21:53AM +0200, Wolfgang Pfeiffer wrote: Sorry: In my first message I made a mistake in the subject line: It's corrected in this one ... Still BS: I can only talk for the 5,8 one, *not* for the 5,6 one ... ... :/ Sorry #2. Wolfgang -- Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/ http://profiles.yahoo.com/wolfgangpfeiffer Key ID: E3037113 http://keyserver.mine.nu/pks/lookup?search=0xE3037113fingerprint=on -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
APM on new iBook G3 HD
Hi List, I have an iBook G3 700 Mhz here, running an 2.6.17.6 and a debian sid. Runs fine so far, sleepmode works etc. Unfortunately I had an HD failure and had to replace the HD. I bought an SAMSUNG MP0804H and replaced it. I have not been able to stop this disk from running so far! If I try to enable apm via hdparm, it gets me no errors: # hdparm -k 1 -B 150 /dev/hda /dev/hda: setting keep_settings to 1 (on) setting Advanced Power Management level to 0x96 (150) keepsettings = 1 (on) It prints no errors, neither on the terminal, nor in any logfile I checked. But still, it doesn't change the setting, the harddisk is running all the time and hdparm shows me, it changed nothing: # hdparm -i /dev/hda /dev/hda: Model=SAMSUNG MP0804H, FwRev=UE100-19, SerialNo=S042J10L253128 [...] AdvancedPM=yes: disabled (255) WriteCache=enabled [...] What can I do about it? It is not very healthy for the hd to run all the time, I can hear it scratching if I move the machine. Thanks for any help, Johannes -- Feel free – 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APM on new iBook G3 HD
At Sat, 12 Aug 2006 00:30:40 +0200, Johannes Volkmann wrote: I have an iBook G3 700 Mhz here, running an 2.6.17.6 and a debian sid. Runs fine so far, sleepmode works etc. Unfortunately I had an HD failure and had to replace the HD. I bought an SAMSUNG MP0804H and replaced it. I have not been able to stop this disk from running so far! If I try to enable apm via hdparm, it gets me no errors: # hdparm -k 1 -B 150 /dev/hda /dev/hda: setting keep_settings to 1 (on) setting Advanced Power Management level to 0x96 (150) keepsettings = 1 (on) It prints no errors, neither on the terminal, nor in any logfile I checked. But still, it doesn't change the setting, the harddisk is running all the time and hdparm shows me, it changed nothing: # hdparm -i /dev/hda /dev/hda: Model=SAMSUNG MP0804H, FwRev=UE100-19, SerialNo=S042J10L253128 [...] AdvancedPM=yes: disabled (255) WriteCache=enabled [...] Did this work with your previous harddrive? The harddrive in my iBook G4 (Toshiba) also lets me adjust the setting, but when using the '-i' option, I get this: AdvancedPM=yes: unknown setting WriteCache=enabled But I've never actually used the -B option. I always use the -S option of hdparm to specify a timeout for the drive to spin down after a given period of inactivity. What can I do about it? It is not very healthy for the hd to run all the time, I can hear it scratching if I move the machine. Are you using journalled file systems? If so, then it's possible that the harddrive never gets a chance to spin down, because the journal is committed regularly. You can try to explicitly specify the commit interval as a mount option. Or you can check out laptop-mode-tools: this is a script that relies on the laptop-mode feature in the Linux kernel to delay and group disk writes, so as to minimise the time that the disk is spun up. Ruben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
