Re: Problem with backlight control and question about kernel information and patches
Hi,
Bumping this quite old thread, but with a solution.
Le lundi 29 août 2011 à 09:45 +0200, Michel Dänzer a écrit :
On Mon, 2011-08-29 at 01:52 +0100, Clea F. Rees wrote:
uname info: 3.0.0-1-powerpc #1 Sun Jul 24 13:59:10 UTC 2011 ppc GNU/Linux
Machine is a 12 G4 Aluminium PowerBook with a 1.5 GHz processor and a
nvidia graphics card so I'm using the nouveau drivers.
Then it sounds like nouveau doesn't support backlight control on your
PowerBook yet. Or maybe the kernel is just missing some build
configuration. You should probably talk to the nouveau kernel
developers.
I just remembered getting the backlight to work some time ago with
nouveau on my powerbook. I looked around and found this message from
Andy Wingo: http://lkml.org/lkml/2008/1/12/170
This is his code that I used at the time, available here:
http://wingolog.org/pub/nvbacklight-0.1.tar.bz2
To get it to work on a recent kernel, I had to use this patch:
diff --git a/nvbacklight.c b/nvbacklight.c
index 927d36b..1af10e0 100644
--- a/nvbacklight.c
+++ b/nvbacklight.c
@@ -178,7 +178,7 @@ static struct fb_info *nvbacklight_attach(struct pci_dev
*pd)
par-fpSyncs = NV_RD32(par-PRAMDAC, 0x0848) 0x3033;
bd = backlight_device_register(nvbacklight, pd-dev, par,
- nvidia_bl_ops);
+ nvidia_bl_ops, NULL);
if (IS_ERR(bd)) {
printk(KERN_WARNING nvbacklight: registration failed\n);
goto bl_device_register_failed;
You'll have to install linux-headers-powerpc, but then a simple make and
insmod and it works nicely here.
Regards,
benjamin
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1320183727.1827.41.ca...@pbook.dolka.fr
Re: Using a second screen with an iBook G4
Hi Rogério, Le dimanche 24 avril 2011 à 05:00 -0300, Rogério Brito a écrit : * When I plug an external (1920x1080) monitor on it, I can only get 1024x768 on the external monitor, which is, of course, quite bad. More than that, I can only use the external monitor if I disable the internal monitor, because, otherwise, I get a message (paraphrased) that tells me that the largest screen that can be allocated is 1024x1024. I think this limitation is due to some Xorg configuration parameter. I think that with a Screen section with a larger virtual resolution you can solve this, as in this excerpt: Section Screen Identifier Default Screen […] SubSection Display Virtual 3360 1050 EndSubSection EndSection (Here, it's calculated for two 1680x1050 monitors side by side; do the math for your 1024x768 + 1920x1080) BTW, the “Open Firmware” limitation is just a hint for the OS, I think; you can get larger resolution in linux without this hack. It's just a soft limitation. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303658767.10770.88.ca...@nsk.dolka.fr
Re: Disk screwed up with ybin
Le jeudi 21 avril 2011 à 05:16 -0700, johnny-crash a écrit : So, next step failed. There is no target mode anymore ;-( You mean, it does nothing at all? So, yes, your disk appears no to work whatever the mean. Subsequently there is only one hope left. Maybe it is the controller and not the disk. Time to have a look at ifixit.com. Do you prefer that your disk controller is dead rather than the disk? It's part of the main bourd AFAIK, so it's a much bigger pain to change it… Anyway, you have to take the disk appart to check that. I'll check out the live-CD. Maybe it comes with tools I am not aware of yet. If not even Open-Firmware can detect the disk (as diagnosed by it not being able to boot in target mode), it's not worth trying that: there's definitly a hardware problem. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303388509.2196.6.ca...@nsk.dolka.fr
Re: Disk screwed up with ybin
Le mardi 19 avril 2011 à 16:46 -0700, johnny-crash a écrit :
boot=/dev/hda2
device=/pci@f400/ata-6@d/disk@0:
partition=3
root=/dev/hda3
timeout=100
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
enablecdboot
macosx=/dev/hda4
defaultos=macosx
image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img
append=quiet splash
My macosx is on /dev/hda3 (sure), linux on /dev/hda5 and 6 (not sure). The
important stuff is on the two macosx partitions.
Well, there's a problem then: your conf says that macosx in on /dev/hda4
and your linux /boot on /dev/hda3…
dmesg says:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
...
hda: no DMA mode selected
Dev hda: unable to read RDB block 0
Another idea if you think your drive is not faulty: maybe you didn't
plug the hard drive right? I had some problems with 2,5 IDE drives that
have hard to push connector. Maybe a shock caused it to move?
How do I get the partition table? I did dir hd:\ in OF and it crashed
imediately.
With mac-fdisk?
Yes target mode is much better but I doubt that I'll be able to read
anything ;-(
Why? You don't have any more access to any OS? What is exactly the
“white” screen you were talking about? When does it show up exactly?
benjamin
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1303289273.21604.23.ca...@nsk.dolka.fr
Re: Disk screwed up with ybin
Le mercredi 20 avril 2011 à 05:39 -0700, johnny-crash a écrit : Sorry that this was misleading. Ok, I see, no problem. Right, no yaboot, no OS at all. White screen means just a white screen. No apple logo, nothing. OpenFirmware works though. To be sure I understand: you used to be able to boot the apple rescue CD, but not anymore? So that is what I have in mind so far: - target mode with another mac It should tell if your disk and connection is OK or not. - disassambling the disk/checking the cable connections I think it's rather unlikely that this is the case, but yes, it may be worth checking. - putting the disk in another computer - checking it with testdisk (hope it can deal with macosx stuff) Yes it can (I already recovered parts of a disk with it). - putting my old disk (with macosx) or even a new one in the mac to see whether it has another hw- issue Seems a good procedure to me. Good luck! benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303303527.25361.9.ca...@nsk.dolka.fr
Re: Disk screwed up with ybin
Le mercredi 20 avril 2011 à 06:32 -0700, johnny-crash a écrit : Yes, I was able to boot the macosx and debian rescue CD but neither OS from disk. Thus I'll do my tests and post my findings. You could run smartctl from linux live CD, then, to see how bad is your disk. It's in the smartmontools package. benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303307451.25361.10.ca...@nsk.dolka.fr
Re: Disk screwed up with ybin
Hi, Le mardi 19 avril 2011 à 06:00 -0700, johnny-crash a écrit : […] the whole system froze and after a hard reset there was no yboot anymore. Just a white blank screen. I booted a macosx CD and wanted to repair the partitions but the 160 GB are just somehow 20 GB now. Thus I did nothing. Next I booted debian in rescue mode and had a look at the disk. There is nothing at all. dmsg complains about io-errors and block0 not readable ;-( What now? I do not dare to do anything without being very sure what might help. If someone has an idea I'd really appreciate it! This sounds like a faulty hard disk drive. I hope you have backups of your important data. If not, try booting any OS that work to recover as much as you can. I think your disk is dying. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303224989.32522.154.ca...@nsk.dolka.fr
Re: Disk screwed up with ybin
Le mardi 19 avril 2011 à 08:25 -0700, johnny-crash a écrit : The disk is quite new and I had never issues and just now after playing with ybin and rebooting a couple of times it dies? Seems to be a big coincidence but, on the other hand, who knows? Well, maybe I was a bit quick at diagnosing this. To know better, we would need the exact dmesg output, your yaboot.conf and the partition table of your drive. Maybe I put the disk into another (at best apple system) and see what options are left. If you don't want to remove the disk from your laptop but still use it as an external drive, you can boot in target mode (pressing “t” on boot) and connect it to some firewire-enabled machine. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1303240843.32522.158.ca...@nsk.dolka.fr
Re: iBook G3 Squeeze -- any hope?
Hi, Le mercredi 06 avril 2011 à 14:56 +0100, James Tappin a écrit : While the install went fine, on reboot I was unable to get any kind of desktop. With the default boot there was just a grey rectangle on the screen and a speckled bar near the bottom. Booting with video=ofonly, the boot messages got to an error about the governor timing out[*] and then it hung until I pressed the off switch at which point a normal shut down followed. The “problem” with the governor is just a warning; no need to worry for that, I think. Your problem must come from some Xorg configuration issues. You may try booting with “init 1” and try playing with Xorg from here (sorry, I don't know anything about your machine after this point). Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1302100349.1590.137.ca...@nsk.dolka.fr
Re: A short tutorial on running GRUB2 on a PPC
Hi, Le samedi 02 avril 2011 à 22:17 -0400, Super Bisquit a écrit : […] OpenBSD […] NetBSD […] FreeBSD […] Do you know we're on _debian_-powerpc ML? You may think I'm being an asshole to you; but, I am only giving you realistic arguments. What's the point of this rant? Please, be more kind and thoughtful next time you're writing here. Fortunately, Rogério is not subscribed… benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301837603.1590.67.ca...@nsk.dolka.fr
Re: A short tutorial on running GRUB2 on a PPC
Le dimanche 03 avril 2011 à 11:52 -0400, Super Bisquit a écrit : You do know that his question should have been forwarded to the yaboot mailing list? This is a question about firmware interfaces and not limited to Debian. The thing is, I don't see any bootloader-related question in his first message. You do know that other operating systems exist and that these problems must be dealt with when using any bootloader on any architecture? This is presenting a problem that will be so complex and convoluted no one will be able to fix it. I don't know what you're on, but I absolutely don't know what you are talking about. You do think my approach was wrong? At least I explained myself and let him know what would mess up. What would mess up what? He proposed some advices to people wanting to use grub2. That's all. You did not think of concentrating on helping him but on correcting me instead? He asked for help and feedback and you gave him none. Please, refrain from posting here anymore: the way you spoke to me, Rogério and Roger (publishing a private email in the latter case) show us a total lack of any respect and understanding. I personally think you are not welcome to debian-powerpc anymore. I will notify the listmasters of any further attempt to disturb this mailing list. benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301849007.1590.85.ca...@nsk.dolka.fr
Re: Yaboot
Hi Joseph, Le lundi 14 février 2011 à 09:04 -0500, Joseph Jezak a écrit : I've finally gotten around to patching the existing ofpath as requested here. If I could get some testing, that would be greatly appreciated! I've attached the whole ofpath program here. The patch against the yaboot git head can be found on the yaboot mailing list. It's unfortunate you didn't follow the lastest discussions on this matter, but Milan Kupcevic's patch, which has the same purpose as your ofpath replacement, has been integrated into Squeeze. You may have been misguided by Milan's lack of communication here, but I'll let you deal with him and Aurélien Gérôme about how this problem was handled (IMHO: not the best way) Regards and thanks for your efforts anyway, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1297699106.28255.15.camel@nsk
Re: Yaboot
Le lundi 14 février 2011 à 11:27 -0500, Joseph Jezak a écrit : I'll have to look back in the archives, but I haven't seen any upstream patches for this issue. I don't think there was any. It was just uploaded by Milan directly. I admit, I haven't followed the discussion on this list. Have the Debian fixes been pushed upstream? I'd really like to see us working together on the same code base to prevent waste, there already aren't enough PowerPC developers as it is. I agree, but not everyone seems to work the same way. benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1297706766.29506.4.camel@nsk
Re: Anybody know how to netboot Debian on a PowerMac?
Hi Rick, Le dimanche 06 février 2011 à 23:44 -0500, Rick Thomas a écrit : I'd like to setup a PowerMac to run diskless. […] Questions: I think almost all your questions are answered in a message by me to Patrick Boutet one month ago : http://lists.debian.org/debian-powerpc/2011/01/msg00013.html Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1297458544.25161.1647.camel@nsk
Re: trouble netbooting debian on xserver g4 ppc cluster node
Hi,
Netbooting iBook/PowerBook has always been strange to me, so here are my
advices :
Can anyone offer any guidance as to what files to
place in the tftpboot directory? We are assuming vmlinux, initrd.gz, yaboot,
yaboot.conf and boot.msg from
http://http.us.debian.org/debian/dists/lenny/main/installer-powerpc/current/images/powerpc/netboot/
is
this right or wrong? What should the directory structure look like?
All these files should just be at the root of your tftp directory. No
need for the gtk directory if you don't use the graphic installer.
Next, what do we do for the part that saysYou may have to make a link from
that file to the file which tftpd will use for booting a particular client.
Unfortunately, the file name is determined by the TFTP client, and there are
no strong standards. We really don't know what to do for this part. When
it mentions TFTP client does it mean the one that the xserver uses, does
OpenFirmware use a client somehow? Because were attempting to initiate
booting from TFTP through Open Firmware on the xserver via boot enet:0 and
boot enet:0,yaboot both of which did not work. Were assuming because we
don't have the right files and in the right structure in the tftpboot
directory.
I recall using boot enet:0,yaboot with succes (maybe with no 0? but
still, yaboot as a file name is needed, I think).
Any advice on how to get this xserver to netboot would be amazingly helpful,
we've been fighting with it for many weeks now and not getting anywhere :(
The main issue, for me, was the DHCP server configuration, as my
PowerBook seems to need some guidance. An excerpt from my dhcpd.conf
(using a 192.168.7.1/24 addressing on the server):
group {
option routers 192.168.7.1;
filename yaboot;
server-name myservername;
server-identifier 192.168.7.1;
next-server 192.168.7.1;
host powerbook {
hardware ethernet mac address of your G4;
}
}
Just replace myservername with the DNS name of your server, replace
powerbook with anything you like, and put the mac address of the
computer you're netbooting at the right place.
I'm not sure if everything is needed, but it's what I found lying in my
config file.
Regards,
benjamin
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1294791311.24314.49.ca...@nsk
Re: Unofficial Squeeze NetInst CDs: call for testers
Hi, Very nice to have an almost official iso! Le mardi 14 décembre 2010 à 04:22 +0100, Aurélien GÉRÔME a écrit : * yaboot-installer_1.1.19; Does this include the amiga partition map renumbering fix? (I'm just making sure you noticed it) * os-prober_1.42; * rootskel_1.93. Don't know what they're for. Oh, well… Please test both of them and tell us about it. I tested the 1.3.16 one and report a successful install on a Powerbook6,8! Thanks for your work. BTW, does anyone sometime have a black screen problem during install (particularly when I'm idle), i.e. backlight goes off and there's no way of getting it back on? I'm asking because my powerbook also seems to have hardware difficulties power-wise (look like it's going off when it's pumping too much current; it can't charge anymore while being on, etc) and I wondered if it was a software issue. [3] http://lists.debian.org/debian-boot/2010/12/msg00421.html I didn't follow that thread. Nice to know it's going forward, but I'll have to add something regarding Milan's work on sysfs-enabled ofpath: your work is great on this Milan, but is far more intrusive than the 1.3.16 upgrade, and as I see people more scared of the 1.3.16 transition as your patched 1.3.13a version, I'm a bit puzzled. Basically, you wiped away all the old SCSI/SATA detection code. It didn't work anymore because of /proc/scsi missing, but still, this is quite a change! Furthermore, you didn't push it upstream, and you wanted an upload without communicating with anyone here. And the way you introduced it in your answer to Aurélien was (to me) not the best one. OTOH, Aurélien, your lack of presence, to say the least, during the previous years didn't help. But it'd be very nice if you two could work together to get Milan's patch into 1.3.16 so that we get best of both words for squeeze. And I think everyone here would support any special request to get it accepted into squeeze, if there's people from release team wondering what's going on with this sudden version change. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1292483688.803.159.ca...@nsk
Re: Yaboot
Hi, Le jeudi 02 décembre 2010 à 02:30 -0500, Milan Kupcevic a écrit : Benjamin, I fully appreciate your attempts to do something about this. You really care about the state of Debian on PowerPC. Please note that Grub 2 works on exactly one PowerPC machine: Pegasos. It needs the most the same solution that would actually fix bug 572869: a new ofpath written from scratch that covers all PowerPC machines. I was under the impression that it was a bit more tested, as some people already reported success on Apple PPC here. Joseph Jezak actually realized the nature of this bug and did his best to produce a solution, but given the resources he had, he did not finalize the job. His code is currently in a half baked state. By just looking a bit at ofpathname implementation, it doesn't look like Joseph's one is better in any sense, technically. The only advantage it has is it's released under GPL. On Tue, Nov 30, 2010 at 02:17:01AM +0100, Benjamin Cama wrote: Well, I didn't see any message from him here regarding this issue. I can't guess what people are doing. Seeing this ML's activity recently, I was under the impression that everyone had let yaboot down. Nice to here someone is trying to improve it, but I wonder what solution he found. Refresh your memory, take a look at your message [2] where you ask questions that are answered in the message you replied to. OK. You seemed to be willing to collect information on every bit of PPC machine anywhere. It just seemed impossible to me. Sorry if I didn't clear that earlier. I'm working on the solution with people who answered my public and private calls for information and help [3][4], who understand that it takes more than google/copy/paste to create a fix, and who are actually devoting many hours of their valuable time and expertise to provide much needed information to actually fix the RC bug 572869. It's nice to be willing to fix that this way, but there are two problems: 1) to me, you'll never be exhaustive enough 2) you never published anything anywhere about that. The solution is almost production ready. Fully functional install cd with fixes for #572869, #580455, #572925 and #603981 is created and already successfully tested on many different Power and PowerPC machines. I was just waiting for final review and assurance that the code will actually get into Squeeze before I send final version patches to the relevant bug reports. But you never spoke about it anywhere I know until today. Which is why other people try to fix it another way. Milan, I'm thankful for you looking at this problem, but your lack of communication doesn't help. This problem is in need of coordination, and it's not by doing everything on your side that you'll help solve it. You didn't even spoke about your solution for SATA PPC: please at least comment on how your doing it. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1291341358.803.54.ca...@nsk
Re: Yaboot
Hi Aurélien, Le mercredi 01 décembre 2010 à 23:10 +0100, Aurélien GÉRÔME a écrit : Benjamin, rest assured your work has been very much appreciated, at least by me. :] Thanks ! Sorry I didn't finish everything I wanted to do, but it's nice to see you eventually made an upload to unstable ! When you talk about Joseph's code, do you talk about the changes in the Gentoo package or something elsewhere (which I have obviously missed)? The ofpath rewrite, as you noticed in your next email. It /may/ replace ofpath as-is, but as it has not been tested for backward compatibility. And TBH, if you want to replace ofpath altogether, better use ofpathname. The only way Joseph's code could be usefull and not too risky, to me, is to integrate sysfs path translation into existing ofpath (i.e. before or after /proc translation). (which is not possible with ofpathname due to licensing mismatch) Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1291247060.3049.65.ca...@nsk
Re: Yaboot
Hi, Le samedi 27 novembre 2010 à 13:22 +0100, Jeroen Diederen a écrit : What about yaboot? Does anyone have any update on this ongoing problem? There was some activity a while ago but it vanished after a few weeks. I have the idea that we won't have yaboot when Squeeze gets released. Any news on the debian-installer team with respect to this? About my work, I didn't have the time nor motivation to integrate Joseph Jezak work on sysfs enhanced ofpath. This needs some work, and as we had no news from either the yaboot maintainer, the d-i team nor the release-team (to know if this work is worth it if we can get it uploaded for squeeze), I don't know if we'll ever see a new yaboot version in Debian. I think this patch is absolutely needed as yaboot is still broken on SATA PowerPCs today. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1291040950.2906.53.ca...@nsk
Re: Yaboot
Hi, Le lundi 29 novembre 2010 à 22:55 +0100, Gaudenz Steinlin a écrit : Sorry, but that's not the way Free Software works. Don't wait for others to tell you what to do, show us the code! I'm not exactly waiting for anyone: I already integrated the latest yaboot version into the Debian package with some other patches, which took quite some time. I coded just a bit, though, but I was hoping that some people would follow. I'm no specialist at all about PPC and stuff, I did all by myself seeing that almost nobody did anything for some time. It's just that after some time, seeing you're alone integrating, coding, patching, fixing bugs in that package, you're a bit discouraged. There was a lot of people willing to test, but that's only part of the equation. And I'm not blaming anyone. And what you say is even not true. I already said that I will happily sponsor a yaboot upload if it fixes reported RC bugs. This is equally valid for all the other relevant packages. Also the release team will generally approve uploads that fix RC bugs. They want to release Debian after all. I don't see what I said that implied that. I know that you offered sponsoring, thanks, but the thing is, as of today, this new yaboot fixes no RC bug… So I was trying to do one last thing, which is integrating Joseph's code, before asking for you to sponsor me. This way, it would at least fix an RC bug and be accepted by the release team, I hope. My criticism was about not having answers to my questions about accepting such a package update (minor version change on a package not updated in years while debian is frozen). To fix this problem, other options are replacing ofpath altogether with Joseph's code, which is too much risky regarding backward compatibility, I think. Or use ofpathname, which will need some integration work, and even if it's been more trained than Joseph's code (it's used in GRUB 2), it could cause some quirks too. But if someone feels like it, let him code it! Milan Kupcevic sent me a yaboot package for review today. I'll look into it tomorrow. So your assumption that there is nothing going on is simply wrong. Well, I didn't see any message from him here regarding this issue. I can't guess what people are doing. Seeing this ML's activity recently, I was under the impression that everyone had let yaboot down. Nice to here someone is trying to improve it, but I wonder what solution he found. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1291079821.2906.83.ca...@nsk
Re: Fixing bug #572869: ofpath doesn't work in the absence of /proc/scsi/scsi
Hi, Le lundi 25 octobre 2010 à 03:11 -0400, Milan Kupcevic a écrit : Fixing bug #572869: ofpath doesn't work in the absence of /proc/scsi/scsi A fix (Joseph's ofpath rewrite) has already been proposed and only need to be incorporated into current ofpath for backward-compatibility. I wanted to do that but don't have time and motivation for now. I will need volunteer help to collect more information about SAS, SATA and SCSI hardware configurations on Power machines. Could we know exactly what are you aimed at ? Building a sysfs-only ofpath that is compatible with every known Power machine ? (would be amazing, but lot of work) benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1287996021.9620.75.ca...@nsk
Re: Debugging yaboot issues (was: Re: Call for testers: new yaboot package release - experimental installer)
Le mercredi 13 octobre 2010 à 10:32 -0700, Gary a écrit : Thanks for the sleuthing, Ben. But I can't help but wonder how the Lenny installer works to allow me to install unstable or testing on my G5 with SATA...? Am I missing something important in the multiple threads spawned by this issue over the past few months? Oh, sorry, I forgot that. But I just checked a lenny kernel (2.6.26-2) and saw that /proc/scsi _is_ present: $ grep SCSI /boot/config-2.6.26-2-686 |grep PROC CONFIG_SCSI_PROC_FS=y $ grep SCSI /boot/config-2.6.32-3-686 |grep PROC # CONFIG_SCSI_PROC_FS is not set So, I can now officially say that, as /proc/scsi has been disabled between lenny and squeeze, yaboot does not work anymore with SATA enabled PowerPCs. This is a big regression, and is worth a blocking BR for squeeze, maybe. Does anyone feel like it ? Thanks everybody for making that clear, and sorry for the guess try game that leaded to that. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1287063356.3143.91.ca...@nsk
Re: Debugging yaboot issues
Hi Joseph, thanks for answering ! Le mercredi 13 octobre 2010 à 14:18 -0400, Joseph Jezak a écrit : What devices don't work with the new ofpath? To be honest, I don't know. And it will be very hard for anyone to make a list of such devices. What benefit is there to keeping the old one around? Well, as always, backward compatibility. I'm sure there's a lot of people around that are very happy with yaboot currently, and the problems with more recent PPC should not impair them. I know a lot of people despise ofpath in its current state, but nobody that I know of has the knowledge, the ressources, and the time to correctly check if a brand knew ofpath would work on everything the old one has worked on. The closest attempt would be ofpathname, which I think is close to your ofpath technically, and we may try to switch to it (well, it would rather be an upstream decision: I saw some people discuss about it on the yaboot devs ML). But all of these things are a big of a change and I don't think it's the right time to do that, i.e. we'll never integrate such a change in squeeze. After squeeze, well, yes, we should try. Or even think about switching to GRUB 2. I've tested mine with a Powerbook G4 (old MacIO driver and the new PATA MacIO driver) and a Quad G5 with various kernels between 2.6.32 and 2.6.36. More testing would certainly be appreciated! Definitly. I'll try on mine too. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1287064003.3143.102.ca...@nsk
Re: Debugging yaboot issues (was: Re: Call for testers: new yaboot package release - experimental installer)
Hi, Le mercredi 13 octobre 2010 à 09:51 -0700, Gary a écrit : I tried to do this with Zsombor's recent build but, unfortunately, the network driver wasn't recognized Is it recognized with the original installer ? If it's the case, it means there's definitly something wrong with Zsombor image and that we can't report bug on it. I didn't look to see if a USB drive would show up as that's the only way I could provide a verbose listing of /sys/bus/scsi/devices. Should I try for the same output on an official testing or unstable weekly or nightly build? IIRC, I had a similar ofpath issues with those as well. I checked once again ofpath source code and saw that the information from /sys I asked is useless. Sorry for the trouble. Yaboot definitely doesn't work with the new ATA stack nor SCSI devices without /proc/scsi. The work from Joseph Jezak seen here: http://lists.ozlabs.org/pipermail/yaboot-devel/2010-September/000345.html is very interesting, but we must integrate it in the current ofpath; we can't wipe everything like that. Also, ofpathname is interesting, but it's a too big step to take, IMHO. Furthermore, I can't look up the code because of licensing issues. So, for now, no SATA for yaboot. Sorry it took so much time to understand it myself. I'll try to do something with Joseph's code, or, may I ask you directly : do you want to help on integrating your code to current ofpath, Joseph ? Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1286990386.3143.77.ca...@nsk
Re: Debugging yaboot issues (was: Re: Call for testers: new yaboot package release - experimental installer)
Hi Gaudenz, Le lundi 11 octobre 2010 à 09:41 +0200, Gaudenz Steinlin a écrit : Did you only modify the yaboot package or did you modify yaboot-installer as well? I only modified the yaboot package. From what I gathered regarding this update, yaboot-installer will need a small change too for Pegasos (partition numbering changed) but I don't think there is anyone left (and still active) to test on that arch anyway. I did not follow very closely how you built your test images, but testing a new bootloader package inside d-i is a bit tricky. I am not the one who built the images, it's Zsombor. And we actually realized it's tricky to test new bootloaders :-) - change to a shell in the installer after the package is installed from d-i, copy the new package into the installer environment, chroot /target, and then dpkg -i the new package. This has to be done before yaboot-installer runs. This is easier but less elegant than the first solution. Thanks a lot for this information, I was looking for something like that. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1286810195.3164.8.ca...@nsk
Debugging yaboot issues (was: Re: Call for testers: new yaboot package release - experimental installer)
Hi Zsombor, First, my apologies for being so slow to answer. And thank you for the custom installer you built. I am very thankfull for your enthusiasm, but I would like to point out some thing that you're doing wrong. I am saying that not to deter anyone to do anything, but to try to be more organized, as it has already been pointed out by other people from Debian : debian-powerpc is often a mess any nobody else will want to help us if we don't try to do things in a more organized way. We already had no help from the d-i team about this new yaboot release, let's hope that by making things the right way we'll get more help. Le dimanche 10 octobre 2010 à 12:42 +0200, Zsombor a écrit : * official 64-bit kernel replaced by a custom kernel [linux-image-2.6.32zsexp01] with CONFIG_SCSI_PROC_FS=y - an idea to make it work on Mac Don't do that. That /may/ work but it's not the right way to do that and won't ever be accepted by the kernel team. This option has already been deactivated years ago, and it's been years that yaboot should have adapted to /sys. BTW, the error message is wrong in that it also checks /sys for SCSI devices, but the /proc/scsi message has not been updated regarding this change. To help about this _specific_ issue, please report to #572869. Your SATA controller should have been supported by yaboot, as I thought that changes made to 1.3.16 fixed that, but it doesn't seem to be the case. To help diagnose the problem, to anyone having this issue on a G5, please also include the result of : ls /sys/bus/scsi/devices + added ehea nic module (for 64bit di-kernel only) - to support Power6 netcard A specific bug report should be opened to track that: Xavier, could you do that ? The problem is that it happens on a custom image you made Zsombor, and I'm not sure anyone will accept it as a valid BR. That's where I am asking for help from the d-i team: how could we test this new package from a d-i install disc ? Is there an easier and more officially-compliant way, so that we can report bugs without doubts ? Should we push the package to unstable directly ? Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1286749283.5299.45.ca...@nsk
Re: Installing nouveau hints?
Hi, Le samedi 09 octobre 2010 à 17:52 -0700, Gnu Turd a écrit : I chatted with a fellow over at the ubuntu-ppc IRC channel and apparently the PPC version is released at the same time as the regular Ubuntu releases (tomorrow, I gather). He also said that even with Ubuntu getting nouveau to work is hit or miss, depending upon you hardware. I was cautioned not to expect too much even if I did get it to work. I think I'll DL the Meercat PPC image and at least try the live boot on this box. If it works I will try to repartition the box and dual boot Debian Ubuntu. Just to let you know that I used to compile all the stuff from the nouveau howto (drm, libdri, nouveau DDX and maybe some other stuff) on my powerbook (NV34) and got this driver working quite well (even dual-screen); it's been something like two years ago, with a much more older kernel. So, it was possible, but I didn't try with newer release. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1286749782.5299.49.ca...@nsk
Re: Call for testers: new yaboot package release - power5 installation
Hi, Le mardi 05 octobre 2010 à 15:12 +0200, Zsombor a écrit : Oct 5 14:11:33 yaboot-installer: chroot: can't execute 'mkofboot': No such file or directory This is a packaging mistake, already reported here, and fixed in my git repo. But the package is not up to date. I included the official 2.6.32-5-powerpc64 kernel. Should I compile a custom one? Not needed, it's just a stupid mistake of mine. Retrying kernel-install on prep succeeded but the machine cannot boot from harddisk: Elapsed time since release of system processors: 116 mins 52 secs DEFAULT CATCH!, exception-handler=fff00400 at %SRR0: c000 %SRR1: 08003002 Open Firmware exception handler entered from non-OF code Client's Fix Pt Regs: 00 018fffe0 04 00c39a48 08 0c 10 14 00c0 0008 18 1c Special Regs: %IV: 0400 %CR: %XER: %DSISR: %SRR0: c000 %SRR1: 08003002 %LR: %CTR: %DAR: Virtual PID = 0 PFW: Unable to send error log! ofdbg 0 Do you have any advise? Maybe I missed something from the installer? Wow, no idea. I'm just merging patches and adding packaging, but I'm no expert in OF things. Did the previous yaboot (1.3.13a) work ? Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1286293098.3256.4.ca...@nsk
Re: Call for testers: new yaboot package release
Hi Aurélien, Le samedi 02 octobre 2010 à 19:33 +0200, Aurélien GÉRÔME a écrit : Can you please produce a standard debian package with quilt patches? I will try, but will need some time. I think some git util is able to do that automatically, isn't it ? It was like that previously and I did not intend to change it. I'm sorry, but I don't see any quilt patches in the old 1.3.13a. It would be a bonus to add that, but it is more work. Please update your debian/changelog, some fixes cannot be accepted as a valid changelog entry. This email seems quite a good starting point to fill it. It is also why quilt patches are nice, you can describe each patch in debian/changelog. Yes, the changelog definitly need some care. I will come back when it's done. benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1286139814.3120.105.ca...@nsk
Re: Call for testers: new yaboot package release - report installation PowerMac G5
Hi, Le jeudi 30 septembre 2010 à 22:29 +0200, Tiresia Giuno a écrit : I let just the package installer installing yaboot. After that I ran ofpath and it detected correctly my two SATA Drivers. Nice to know it works on SATA. Did the previous version (1.3.13a) work too ? After that I ran yabootconfig. It creates a yaboot.conf but it stops immediately without running mkofboot. Last massage: 'yabootconfig: yaboot is not installed correctly, not running mkofboot' Oops, actually mkofboot is linking to a wrong path. I will fix that. Thanks for pointing it out. Checking the generated yaboot.conf shows that it fails to detect the old kernel (no image=/boot/vmlinux.old section) and the MacOSX system. Well, I think yabootconfig is actually not supposed to detect that. It's done by the debian-installer scripts (comprising yaboot-installer). Then I ran 'ybin -v' that installed correctly the new generated yaboot.conf. As expected, the first yaboot prompt doesn't show any x option (for MacOSX) I resumed my old yaboot.conf running again 'ybin -v' - which worked correctly. Ok, I think it's all. Let me know, if I can help further Thanks for your report, It's enough for now, I think. I would like also to try to build myself an installer with this new patched yaboot - not sure that I have enough time right now... We got no answer from the installer team regarding an easy way to test it, so if someone feels like building a custom installer, let us know. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285930956.3120.14.ca...@nsk
Re: Call for testers: new yaboot package release
Hi, Le vendredi 01 octobre 2010 à 10:11 +0200, Thomas Constans a écrit : I'have tested your package on a ibook g4 with success I am using uuid as disc/partition identifier in yaboot.conf i am also using crypted root fs (luks) package installed, ybin ran, laptop successfully rebooted Thanks for your report. Nice to know it works here too. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285931137.3120.16.ca...@nsk
Re: Call for testers: new yaboot package release - report installation PowerMac G5
Hi, Le vendredi 01 octobre 2010 à 05:59 -0300, Gunther Furtado a écrit : Em 30Set2010 (quinta), Tiresia Giuno tires...@googlemail.com disse: After that I ran yabootconfig. It creates a yaboot.conf but it stops immediately without running mkofboot. Last massage: 'yabootconfig: yaboot is not installed correctly, not running mkofboot' same here! As said earlier, will be fixed. the newly generated yaboot.conf uses the old terminology: Yes, as always. The transition to labels/UUID is only done by linux-base, once. I didn't change yabootconfig in this regard. Thanks for your report. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285931404.3120.20.ca...@nsk
Re: Call for testers: new yaboot package release - report installation PowerMac G5
Hi Zsombor Le vendredi 01 octobre 2010 à 15:43 +0200, Zsombor a écrit : On Fri, Oct 1, 2010 at 1:02 PM, Benjamin Cama ben...@free.fr wrote: (...) We got no answer from the installer team regarding an easy way to test it, so if someone feels like building a custom installer, let us know. Actually, I'm on it. Nice. My IBM p550 has a squeeze on an ext3-fs but I prefer xfs. I don't want to disappoint you, but I don't see in the logs of 1.3.16 anything new regarding xfs: it ought to be the same as 1.3.13a. Maybe the fix in 4af82e0d5f0293d6aaf85c59981a4e0540891cf6 was not really a fix ? (revert the xfs part to see, maybe; upstream never applied it, maybe they forgot, maybe it's wrong). Anyway, you could always try with a separate /boot… Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285948478.3120.30.ca...@nsk
Re: Call for testers: new yaboot package release
Hi, Le mercredi 29 septembre 2010 à 21:52 +0200, Jeroen Diederen a écrit : I tested this new yaboot in my Squeeze partition on my PowerBook G3 Pismo. I installed it without problems and I issued a ybin -v. I rebooted and yaboot 1.3.16 smiled at me. I am back in my Squeeze partition, no problems!! Thanks for reporting. What would be a better test is to switch to UUID/label-based fstab by reconfiguring linux-base (dpkg-reconfigure linux-base, and answer yes when appropriate). Then report here or against #587290 and #580455. etc # ybin -v ybin: hfsutils is not installed or cannot be found ybin: Try --mount if Linux 2.6.32-5-powerpc supports HFS Strange you didn't have it already. Is this an old install upgraded to Squeeze ? Thanks for your detailed report again. benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285865189.3099.30.ca...@nsk
Re: Call for testers: new yaboot package release
Hi, Le mercredi 29 septembre 2010 à 00:24 -0400, Rick Thomas a écrit : Cool! Thanks. Now, how do we test it? Well, for now I was only thinking about testing it outside the installer… Can somebody from the installer group help us figure out how to get this code into the installer environment? Is it as simple as putting the .deb on a USB stick and breaking out to the Alt-F2 VT at some point in the install and do a dpkg -i ? Or is it going to be more complicated than that? I wish it would be that simple. I don't really know, though. BTW, yaboot-installer will have to be fixed regarding amiga partition table numbering : it has been fixed upstream, and there's no need for a workaround anymore. (well, just reading from the patch; I don't have such a machine to test on) Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285765452.3056.8.ca...@nsk
Re: ofpath is not compatible with non-builtin disk controllers
Hi Rick, Le vendredi 24 septembre 2010 à 15:53 -0400, Rick Thomas a écrit : First, let me apologize for the confusing non-specificity of my bug reports to you and everyone else who is following this (and related) bug(s). The only excuse I can offer is that at the time I was submitting them, I wasn't sure what was causing the symptoms I was seeing. All I knew was that I couldn't do a squeeze install or an upgrade from lenny to squeeze. And I was frustrated by the total lack of response. Well, even if you didn't mention it explicitly, it was listed in the lspci dump since the beginning and nobody saw it until now. And one may also find it disturbing that a piece of software doesn't work with an addon card on a machine that has free slots to add such cards ! But bootstrapping an OS on non-original hardware modification is always a bit hard. That said, and trying to go forward, the question now is Where do we stand on getting this fixed? If you are talking about this specific bug, the answer is fix ofpath. But actually, a more efficient thing to do would be to use ofpathname, or rather ofpathname + ofpath/yaboot fixes. Which was to be done by Aurélien more than 3 years ago, see #405337 … Anyway, grub2 uses ofpathname, so I think we should try to use it. Or, first, upgrade it, as it lacks a bit behind upstream (1.2.1 vs 1.1.0). Again, the maintainer is Aurélien, who didn't give signs of life since his email 2 weeks ago, so he may be MIA and the upgrade a bit harder than we can hope. Can we come up with a list of specific problems -- and a 'todo' list of release-critical things that need to be fixed for PowerPC Debian Squeeze? I see #587290 (merged with #580455) and #572869. I think the last one is no more related to yours, even if a patch to use ofpathname would easily fix it, I think. The first one should be fixed by your patch. In that line, we need a list of individual folks who are interested in contributing to this effort. Is this bug report (589701) a good one to encourage all these folks to subscribe to in the interest of centralized record-keeping? I am not sure that polluting this report is a good idea. I would prefer opening another one if there is a clearly defined point of view on that. Which we don't have for now, I fear, because of a lack of concrete result. Which may be partially solved with my next email… benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285716387.3108.138.ca...@nsk
Call for testers: new yaboot package release
Hi everyone, So, yaboot in debian is currently suffering from a lot of problems, and until now we were only talking about it. Here is some code to test it, now to really see what's still causing problems and what's solved. Here is the (temporary) place where you can find it : http://benoar.fdn.fr/yaboot/ It contains a .deb and the git repository I used to build it (beware, there's a lot of cruft in it caused by my experiments with git and debian packaging; I lack experience in both). It basically an up-to-date yaboot (1.3.16) + debian modifications from 1.3.13a (some were already integrated upstream) + Rogério Brito's debian packaging enhancements + some patches (namely Rick Thomas' quotes and spaces fix for latest linux-base, and the no /proc/ide fix (which IMHO fixes nothing interesting, but still)) + fixes of mine (mainly debian packaging). Everything should be nicely commited, and there's a separate branch with fixes but no debian stuff for upstream to pick up from (debian-yaboot) which was forked from repository's 1.3.13 (you'll see tags to get from here to the debian-1.3.13a version, then to this most recent debian-yaboot). The branch containing the full package stuff is debian-yaboot-packaging (yes, nothing standard) and master is actually the upstream (from ozlabs). And I forgot to merge the debian-yaboot-with-doc branch which contains the HTML documentation, please excuse me for that, it will be in the next one. If you want to build it yourself : git-buildpackage --git-upstream-branch=master \ --git-debian-branch=debian-yaboot-packaging Still, I may have done some mistakes, and need advices on packaging (I tried to listen to lintian as much as possible). Please test it and report bugs/suggestions on this ML. Message to Aurélien: it would be nice if you could comment on this and help getting yaboot updated. Uploading that without you would be painfull, please answer to this email. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285718209.3108.161.ca...@nsk
Re: Taking over maintainance of yaboot ?
Hi, Le lundi 20 septembre 2010 à 11:42 -0400, Milan Kupcevic a écrit : Debian is frozen for the Squeeze release. Suddenly updated packages to the latest upstream version will not make it into the Squeeze.[1] Yes, it's sad it only happens now, but I think yaboot is a very particular case: it has not been updated in 4 years (!!) despite some worrying bug reports, but today we have an active upstream, an awaken maintainer and a lot of testers willing to try it. This has not appeared in years here, and I think won't ever happen again. I think this is a rare opportunity to update yaboot to a better working version. Therefore, we should focus on RC bug-fixing only. More radical changes have to wait until the Squeeze gets released. We have 2 bugs that qualify for RC and that are related to the current concerns: #589701 and #572869. If these are not fixed, debian-ppc will be uninstalable (and un-upgradable) on many machines. This port already has enough problems on top of that. I think we /could/ try to only fix these two, but if we do that and are not able to at least push a more recent revision just after squeeze release (is it possible if it's just a revision upgrade ?) we won't find anyone left here to do the upgrade later. It's not like upgrading from 1.3.13 to 1.3.17 + bugfixes is a big change: I think the people upstream are very conservative in that yaboot is a software for dead machines desktop-wise and for big stable machines server-wise. I'd like to make an exception for it. I Cc'ed Aurélien Gérôme, the current active maintainer: do you agree with me about the exception ? I am currently looking at how to merge upstream with debian fixes (looking at Rogério's branch too) plus integrating patches sent here by Rick and Joseph (which doesn't seem to be included upstream BTW). benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1285017716.5520.34.ca...@nsk
Re: Taking over maintainance of yaboot ?
Hi, First, let me say that I'm glad to ear from you ! I think that other will agree too. Le vendredi 17 septembre 2010 à 22:05 +0200, Aurélien GÉRÔME a écrit : On Thu, Sep 16, 2010 at 02:01:52PM +0200, Benjamin Cama wrote: Then, updating yaboot to the latest known active development branch (http://yaboot.ozlabs.org/ ) would help a lot our port to stay alive, as many have noted that Debian on PPC looks a bit dead from outside. Indeed, I have been planning to do that for a very long time, but interrupting any Debian activity did not help in the matter. OK, it happens, but we must admit it has been very painfull for every PPC user not to have any active yaboot maintainer. Anyway, nobody overtook the package in between, so… Hopefully, now I can manage some Debian time, Do you plan on keeping maintaining yaboot for a rather long period, or is it just for this bugfix ? (even if, in the long run, I think we should be switching to grub2) so I will update, say this week, the package and any bits of d-i necessary for it to work. Very nice. Do you need help on that ? Here, I am mainly thinking about RAID, LVM, and crypto installations in yaboot-installer, as upstream did some changes in yaboot about them. Doesn't it seem a bit too much to do for now ? I think that what everybody wants for now is /just/ a working yaboot. Thanks, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284917467.3182.7.ca...@nsk
Re: [Debootloaders-yaboot] Bug#587290: How does linux-base modify /etc/yaboot.conf ?
Hi Ben, Le samedi 18 septembre 2010 à 22:11 +0100, Ben Hutchings a écrit : The value of the kernel (or rather initramfs) root parameter generally does need to include an '=' character and linux-base.postinst is correct to use it. It must then double-quote the value in yaboot.conf so that it is handled correctly by the main configuration parser in cfg.c. Therefore, ybin also needs to accept this format. Thanks for the check in cfg.c, I didn't have the idea to go there. I think most people relied on what ybin told them (i.e. I don't grok this). The problem being that ybin never ever understood this syntax, and the stricter simple one was the de-facto standard. This is why your change hurt so much (#580455 lists now at least 5 persons affected), and I'm generally reluctant to ancient file format change. But you're right in that ybin is buggy. I could change linux-base.postinst to avoid adding space between name, '=' and value when updating the configuration but it seems simple enough to make ybin accept that too. Yes, it's simple. And I think you can't avoid the quotes, because of spaces ? (I bet some people put spaces in FS labels ?). So yes, ybin needs fixing, I'll try having a look at that (and Rick's code). BTW, I'm very curious why we didn't get hit by that earlier. It seems your code affected yaboot around the time Debian switched to mandatory UUID/labels, right ? Is your script only triggered for that ? Is it only done once during the transition (as seems to imply the function's name from where it's called in your perl code) or on every kernel upgrade ? Yes, all parts of yaboot should really be using the same configuration parser. Reimplementing it is crazy. Well, I'm not sure anyone is able/willing to do that here… Let's just fix the most obvious bug for now, right ? By the way, I think this bug should be merged with #580455. Tried doing it, but didn't work; should I rather forcemerge or try setting both to the same severity first ? (I don't like messing with so high severity when it's not my bugs) Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284940121.3182.70.ca...@nsk
Re: netbooting
Hi, Le vendredi 17 septembre 2010 à 07:31 -0300, Gunther Furtado a écrit : I've compiled yaboot from http://yaboot.ozlabs.org/snapshots/yaboot-1.3.15-rc.tar.gz and copied to the server's /tftpboot directory and... it works! It takes a lot longer to get to bootprompt but it works. I've also been using a patched yaboot for some time, which I found on an Ubuntu bug report about the initrd size limit problem. Anyway, we must find some way to get this updated version to Debian… benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284726910.3106.96.ca...@nsk
Taking over maintainance of yaboot ?
Hi, I am trying to exactly understand the bugs that currently affect the Debian PPC port and particularly yaboot. There are many bugs around it, but even before trying to fix them, we should check if it's even possible to get them applied ! And as we saw (a lot due to Rick Thomas work) yaboot is currently unmaintained and as been so for a very long time (see http://packages.qa.debian.org/y/yaboot.html ). I am Cc'ing Aurélien Gérôme just in case, but without much hope, and Sven Luther has left for a long time. The problem is : who could take yaboot over ? There are no DD that I know of in the debian-ppc community and yaboot is quite arch-specific. Furthermore, I am not very familiar with how such a take-over could take place : I've had a look at http://www.debian.org/doc/developers-reference/beyond-pkging.html#mia-qa and I am planning to write to m...@qa.debian.org, but help on gathering information is welcome. I am also wondering if a NMU could be possible. Then, updating yaboot to the latest known active development branch (http://yaboot.ozlabs.org/ ) would help a lot our port to stay alive, as many have noted that Debian on PPC looks a bit dead from outside. Another problem is that a lot of information is lost because this mailing-list is one of the last place to get information about Linux on PPC for desktop users but digging in the archives is no always easy. I think we should try to gather information on the wiki : http://wiki.debian.org/PowerPC If anyone want to help have a correct PPC port for Squeeze, please join ! Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284638512.3106.27.ca...@nsk
#580455 yabootconfig does the correct thing, your yaboot.conf must be modified by something else
Hi, I just found by looking around that yabootconfig, the script used by the yaboot package (very important distinction) to generate /etc/yaboot.conf actually _knows_ how to handle LABEL and UUID; see http://svn.debian.org/wsvn/debootloaders/trunk/yaboot/ybin/yabootconfig . Furthermore, the yaboot package didn't change in 4 years, so everything is correct in yaboot ! But, as we recently saw again on the debian-ppc ML (see http://lists.debian.org/debian-powerpc/2010/09/msg00013.html ) _some_ script from _some other_ package does modify /etc/yaboot.conf ! And add spaces (very wrong) and does not interpret labels/uuids. The only other script I know that generates yaboot.conf is the postinst one in the yaboot-installer udeb (from the debian-installer) but I don't see how it could add spaces, looking at its code. So, that's now 3 people including you that stumble upon this, but this doesn't come from yaboot. So, could you please join the _full_ yaboot te see if the program that generates it leaves some traces, and please tell if you think you have any particular package installed that could affect that. I Cc the list, too, in case someone could look at that. Thanks, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284642004.3106.58.ca...@nsk
Re: How does linux-base modify /etc/yaboot.conf ?
Le jeudi 16 septembre 2010 à 15:12 +0200, Benjamin Cama a écrit : You mentioned that linux-base may modify /etc/yaboot.conf. I think it might be the culprit for this bug, but I would first like to know how and why it does that ? OK, I was right, thanks to your hint: see http://svn.debian.org/wsvn/kernel/dists/sid/linux-2.6/debian/linux-base.postinst The yaboot.conf is taken as if it has the lilo syntax. And this script adds spaces and quotes around key/value pairs and let /dev/disk/by-* names. This is not compatible with yaboot. I also saw that you filled this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581173 which make me think that your approach is to adapt every bootloader to this syntax. The problem is, not every bootloader maintainers or volunteer contributors have the resources to do so. Yaboot has not changed in 4 years, and even if Rick Thomas submitted a patch to handle that, I am not sure anything will be eventually integrated (I sent an email earlier on debian-ppc list to ask if someone would volunteer to take over yaboot maintenance, as the maintainers are unresponsive for so long). Furthermore, this change affected a lot of users since at least last may, and I just found it now ! In between, this was a major disruption for Debian on PPC (3 persons reported being affected by this bug, which is quite a lot for our architecture). Could you tell us (I Cc'ed debian-ppc) your view on this problem ? Is the workaround for 581173 I see in the code (removing spaces) a good idea to apply quickly to fix this bug too ? Thanks, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284644653.3106.87.ca...@nsk
Re: Font Led
Hi, Le mardi 14 septembre 2010 à 22:01 +0200, Elimar Riesebieter a écrit : $ cat/proc/version Linux version 2.6.36-rc4-aragorn (riese...@aragorn) (gcc version 4.4.5 20100909 (prerelease) (Debian 4.4.4-14) ) #1 Mon Sep 13 20:48:12 CEST 2010 Managing leds is done through /sys nowadays. I don't have my powerbook at hand so I don't know the exact entries, but look into /sys/class/leds. One directory should correspond to the front led, and will have a trigger entry that define which event make the led blink. Or just look at the documentation : http://www.mjmwired.net/kernel/Documentation/leds-class.txt Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284505671.5194.5.ca...@nsk
Unidentified modifications to yaboot.conf [Re: patches to ybin]
Hi, Le mercredi 28 juillet 2010 à 23:49 -0400, Rick Thomas a écrit : The kernel package just uses the yaboot.conf that's already there. Well, that can't be entirely true. If I install Lenny on one of my test machines then try to upgrade to Squeeze, I get a garbled yaboot.conf and the machine refuses to boot until I do some surgery with a rescue CD. I don't know whether it's the kernel package or something it drags in that is causing this. Any help will be much appreciated!!! I also came to this conclusion : something is touching yaboot.conf in a weird way. As Ben Hutchings told you in #587290, it might be yabootconfig, which generates yaboot.conf, but i see no way (by analyzing the code) it could add spaces around root= and boot=. So, this must be something else, that does it starting not so long ago as #580455 dates from beginning of may (BTW, I think you should not try filling so much bug reports about this; #589701, even if an installation report, is _again_ about the same problem. That's 3 bug reports …). Also, as yaboot hasn't been updated for ages, the modification mustn't come from yaboot. So this is some very nasty thing done by we don't know who. Hard to track. So, if someone more knowledgeable on recent modifications about boot/root parameters could help the PPC community, we'd be glad. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1280442590.6148.41.ca...@nsk
Re: Which module should one use for sound on pmacs? (was: Re: debian-testing-powerpc-xfce+lxde, 7/26/10)
Hi, Le mercredi 28 juillet 2010 à 16:02 -0300, Rogério Brito a écrit : Right. I am CC'ing some people that can potentially have answers to this question. If you have any comments, it would be nice to get this sorted out for the distributions. :-) As you stated earlier, this has been brought up many times already, without much result. Can I cite benh on this matter ? http://lists.debian.org/debian-powerpc/2009/09/msg00104.html How should the distribution side of this be handled (say, with the automatic loading of the proper module) with machines that use, say, tumbler? That's the question. Nobody knows. snd-aoa works great here on a PowerBook5,8 ;-) OK, fine that it works for you. :-) It would be nice if it worked for many others, though. :-) What about snd-powermac, OTOH? snd-aoa works for many people (including me) that simply had no sound at all before. This a driver for newer hardware, from what I understand. snd-powermac is for older ones (note that old may not be what you think: i have an iBook G4 with snd-powermac and a one year younger PowerBook that uses snd-aoa) The problem seems to be just in what machine has what chip, and what driver it should load. Please, if you think I am saying something wrong, correct me. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1280361654.5600.15.ca...@nsk
Re: Debian PowerPc installer initramfs-tools generates malformed yaboot.conf created when alternate partitions use UUID= in fstab
[Trying a repost, got blocked as spam ...] Hi, Le dimanche 27 juin 2010 à 22:01 -0300, Rogério Brito a écrit : We don't exactly need to have DD's to take care of the PPC problems. While that would make things easier, it is not a strict requirement, as long as one has a powerpc machine. Ideally, yes. The problem is that we tend to stumble upon almost unmaintained packages, strange unique bugs, and with not much people to test (take for example the snd-powermac vs snd-aoa problem that I think will never be solved, forever). That make us not able to have definitive clear statements on our problems, and we have no much authority to push changes that /may/ solve problems, etc. We have poor patches that don't look good, but that's the only things we have. I thought that having someone who'd be able to push that a bit more would help. That being said, I don't know if it would be worth investing some time more in the migration from yaboot to grub2, since the latter is supposed to have many features that the former doesn't. In a sense, yes, but isn't it too late for squeeze ? As Rick stated, this bug is a blocker ... Furthermore, I think that most people here left are newworld users ; what about the other subarches ? I have no idea what's needed for them. Which patch do you have? Did you push it to the maintainers of the util-linux package? Or to upstream? Just curious. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568204 Did not push upstream, actually... A quick look at other bug reports and I see no activity from the maintainer (Jones LaMont). I also Cc'ed the author of the original kernel breakage, and benh too, but nothing came back. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1277901546.5332.0.ca...@nsk
Re: Debian PowerPc installer initramfs-tools generates malformed yaboot.conf created when alternate partitions use UUID= in fstab
[Trying a repost, got blocked as spam ...] Hi, Le lundi 28 juin 2010 à 12:13 +0200, Michel Dänzer a écrit : On Mon, 2010-06-28 at 01:21 +0200, Benjamin Cama wrote: - there are currently no DD that care about powerpc problems (or we could rather say that no people who care about PPC are DDs) That's an over-generalization, though admittedly I don't personally care too much about installer or yaboot issues. I'm sorry, it was indeed a too broad statement. But I think you may be the only one left ... (from memory, on the activity of this list in the past monthes) I wanted to help for a problem with the buildd but Frans Pop told us that it needed a DD to be solved, What problem was that and what needs to be done? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572605 Kind of an incomprehensible bug, as often around D-I ... and I also have a patch for util-linux specific to PPC that is waiting for monthes. As Rogerio asked, what patch and where did you submit it? BTW, when filing bug reports affecting the powerpc port I think it's a good idea to tell reportbug to send the report to the debian-powerpc list as well, so we can get an idea of what issues there are. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568204 see previous email to Rogério. I Cc'ed debian-ppc at the time, but I don't remember any comment on it. benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1277901566.5332.1.ca...@nsk
Re: Debian PowerPc installer initramfs-tools generates malformed yaboot.conf created when alternate partitions use UUID= in fstab
Hi, Le dimanche 27 juin 2010 à 15:30 -0400, Rick Thomas a écrit : This is reported as Debian bug #587290 -- please followup to the bug report. The generated /etc/yaboot.conf contains lines append=root=UUID ro for partitions that have their /etc/fstab root line using UUID=... . This makes it impossible to boot into those partitions: the boot progresses to the point of trying to mount the root filesystem and dies with Begin: Running /scripts/local-premount ... done Mount: mounting UUID on /root failed: No such directory then a few more errors obviously caused by not having a mounted root and eventually dropping into the (initrd) BusyBox shell. When I went back and changed the offending line to append=root=/dev/hda6 ro and reran ybin, everything was fine. See bug # 580455 for another aspect of the switch to UUID naming being broken on powerPC. Thanks Rick for your perseverance, I hope this kind of bug could get solved more easily, but from what I *personally* realized : - maintenance of yaboot has always been flacky in the sense that maintainers seem to get hopeless on the lack of interest/motivation from powerpc devs/users - there are currently no DD that care about powerpc problems (or we could rather say that no people who care about PPC are DDs) I wanted to help for a problem with the buildd but Frans Pop told us that it needed a DD to be solved, and I also have a patch for util-linux specific to PPC that is waiting for monthes. But there are only users and simple developers left on the debian-powerpc ML, so we're a bit alone and hopeless ... Still, you're right that dropping ppc support for Lenny would be sad, so I may have a look a this, but being so close to the solution (as you were too when sending a patch for the second bug you described) just to be left without any news from anyone is a bit discouraging. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1277680862.5765.32.ca...@nsk
Re: Segmentation fault at start-up
Hi, Does this segfault also appear on an already booted system, after upgrading the package to the offending version ? This could help getting a backtrace from gdb. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1275245304.3988.4.ca...@nsk
Re: Auto-booting USB stick in OF
Hi Risto, Le mercredi 28 avril 2010 à 09:00 -0300, Gunther Furtado a écrit : 2010/4/28 Risto Suominen risto.suomi...@gmail.com: 2010/4/28, Gunther Furtado gunfurt...@gmail.com: have you tried to boot from a MacOS Classic cd holding down C as it chimes with(out) an usb stick present? I'm pretty sure I have. Looks like it hangs before it comes so far, I cannot even get into Open Firmware. just a wild guess: what would happen if you try to boot form a macos classic cd without any HD attached? Would it be possible to hot plug the HD if it boots from the cd? The reaction, when powering up by holding the power button until a beep, seems healthy: flashing the led, then after a few seconds a chime, when no Firmware image is available on the disk. This makes me think that a reflashing could take place, if a correctly formatted and named Firmaware image was present on the hard disk. I don't want to deter you from changing the disk and such, by if you don't even get to an Open Firmware prompt, you won't be able to boot from anything connected to your Mac. The OF is what will bootstrap the bootloader stored on some media ; if it doesn't come up, you won't be able to boot from anything. Something important must be broken ... Good luck trying to fix your problem, though. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1272462814.3036.10.ca...@nsk
Re: Partition and Boot loader for Squeeze on G4
Hi, Le lundi 26 avril 2010 à 13:54 -0400, Rick Thomas a écrit : Does yaboot know enough about LVMs and RAIDs to find the kernel and initrd in a root partition that's in a logical volume on a software raid-1? No, yaboot doesn't know how to do that. To be safe, I'd create a real, live, physical root (or at least a / boot -- not the same as the Apple_Bootstrap) on each of physical disks of the RAID-1, and periodically mirror them from the active one. Then if the disk with the active root (or /boot) goes south, you can manually tell yaboot to use one of the mirrors. I use a separate /boot (ext2) like you describe for my LVM on my G4, and it works nicely. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1272309946.3104.3.ca...@nsk
Re: Bug#572605: still present -- installation-reports: Sid d-i on PowerPC can not find driver for network interface
Hi, I don't know the exact cause of this bug, but there is not enough informations (for me) to try to understand this bug. Could you give at least a dmesg result when in the installer ? And what exact message does it outputs when looking for the adapter ? Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1269429817.3290.3.ca...@nsk
Re: Debian or ubuntu
Hi everyone, Le mardi 16 mars 2010 à 17:32 +0100, Brian Durant a écrit : it became a community effort. Gnash and swfdec are both terrible and the only way that you can view You Tube in a browser. Ubuntu hasn't even bothered to include these in the default Karmic PPC install. An alternative is to use Download Helper, a Firefox extension. Video I recently tested Youtube with html5 (http://youtube.com/html5 ) on my x86-64 and it works great with epiphany ! I just tried it on my PPC, the plugin loads but the video won't play ; as my PowerBook is in a strange state after some tests, it may be another problem, but it may still work for you. Try it ! Le mardi 16 mars 2010 à 08:24 -0700, Gary a écrit : Re sound, Ive been looking through the wiki for info on enabling sound on the Mac G5. Has anyone found the solution if so, did it work? This is a long known problem and I think it won't get fixed anymore. This is just a problem of detecting the correct platform and loading the appropriate driver : snd-aoa should be the way to go for most Macs (it's working fine on my alubook (Powerbook6,8)) but not enough people are motivated to debug the problem, and not enough knowledgeable people motivated to fix it. So, people prefer forcing the use of old snd-powermac. Both driver should handle everything fine, it's just that the platform-guessing code has some problems, I think. Le mardi 16 mars 2010 à 14:03 +0100, Robert Chamberlain a écrit : which they are written. I couldn't, for example, see any of the flash videos on the BBC site... And you can forget about using Gnash or swfdec. They're hopeless. Gnash seems to have the better prospects, I agree with you about Gnash swfdec : they are not worked on enough to get proper Flash support, sadly. Regarding the BBC, I recently discovered get-iplayer (package available in Debian) which works quite well for me (I only listen to radios, but it seems to work for videos too). Anyway, I also agree with everyone on saying that Debian still has a good enough support for PPC. I don't know about Ubuntu. BTW, the PPC platform is still kind of updated kernel-wise, as the macio libata driver landed in 2.6.33 thanks to benh. It allows to use the new ATA stack in the kernel, as the old one will disappear some day. I tested a patched 2.6.32 and it worked well. So the PPC platform for Mac is still not abandoned. I am interested in it to get proper support for new SSD features, since I installed one in my PowerBook (and it makes it quite fast compared to today average computers). Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1268768834.2897.100.ca...@nsk
Re: Debian or ubuntu
Le mercredi 17 mars 2010 à 01:10 +0100, nello martuscielli a écrit : On Tue, Mar 16, 2010 at 8:47 PM, Benjamin Cama ben...@free.fr wrote: BTW, the PPC platform is still kind of updated kernel-wise, as the macio libata driver landed in 2.6.33 thanks to benh. It allows to use the new ATA stack in the kernel, as the old one will disappear some day. I tested a patched 2.6.32 and it worked well. So the PPC platform for Mac is still not abandoned. I am interested in it to get proper support for new SSD features, since I installed one in my PowerBook (and it makes it quite fast compared to today average computers). ok, but what's about the bootloader? Is yaboot able to work with these new devices ? As Gary said, it's no different from a traditionnal PATA disk : it conforms to the ATA standard. I did everything as usual, just aligning correctly the partitions (I must say I did it manually). I also put btrfs on it instead of a more traditionnal FS. It works nicely. benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1268787681.2897.121.ca...@nsk
[PATCH] ignore invalid hw clock for non-interupt-based RTCs
Hi,
My previous comments for this bug report were not accurate : invalid
hardware clock (e.g. reset ones after battery ran out) are already
handled in hwclock, BUT _not_ for non-interrupt based RTCs, like the
ones on newworld PPCs, at least. It reads the clock in
synchronize_to_clock_tick_rtc() for the rtc-generic driver and errors
out from here (the usual invalid clock case is handled in
read_hardware_clock() later, but too late).
Before, hwclock ignored the error returned by the kernel for an invalid
hw clock (if returning EINVAL is the correct error code for an invalid
time -- I am not 100% sure of that, but Ben Hutchings' comment in
#542275 and looking at kernel drivers seem to imply that). It only used
the result from mktime() to check the date. But the kernel also has its
own routine. And this bug is also what cause a lot of drivers _not_ to
report any error when there is one, like I said in my previous comment.
I think this is quite serious.
The following patch fixes this bug (also including some error code enums
to be clearer) while trying not to be too intrusive.
This bug was introduced on powerpc when the default ppc RTC driver for
2.6.30 was changed to rtc-generic. Before that, RTC had been broken for
quite some time on PPC. And continues for people which have flacky
hardware (powerpc is mainly used on old machines today). This is why I
am CCing debian-powerpc : I think this is an important problem that
should really be fixed.
Regards,
benjamin
Signed-off-by: Benjamin Cama ben...@free.fr
---
diff --git a/hwclock/clock.h b/hwclock/clock.h
index e4eb7eb..a1d1bc9 100644
--- a/hwclock/clock.h
+++ b/hwclock/clock.h
@@ -23,6 +23,14 @@ extern struct clock_ops *probe_for_kd_clock(void);
typedef int bool;
+enum {
+ HWCLOCK_OK = 0,
+ HWCLOCK_ERROR,
+ HWCLOCK_SYNC_TIMEOUT,
+ HWCLOCK_KDGHWCLK_ERROR,
+ HWCLOCK_INVALID_TIME
+};
+
/* hwclock.c */
extern char *progname;
extern int debug;
diff --git a/hwclock/cmos.c b/hwclock/cmos.c
index 8b3495b..ecfdd53 100644
--- a/hwclock/cmos.c
+++ b/hwclock/cmos.c
@@ -431,13 +431,13 @@ synchronize_to_clock_tick_cmos(void) {
*/
for (i = 0; !cmos_clock_busy(); i++)
if (i = 1000)
- return 1;
+ return HWCLOCK_SYNC_TIMEOUT;
/* Wait for fall. Should be within 2.228 ms. */
for (i = 0; cmos_clock_busy(); i++)
if (i = 100)
- return 1;
- return 0;
+ return HWCLOCK_SYNC_TIMEOUT;
+ return HWCLOCK_OK;
}
diff --git a/hwclock/hwclock.c b/hwclock/hwclock.c
index ac1f7c8..aa6d6ee 100644
--- a/hwclock/hwclock.c
+++ b/hwclock/hwclock.c
@@ -440,8 +440,11 @@ read_hardware_clock(const bool universal, bool *valid_p,
time_t *systime_p){
int err;
err = ur-read_hardware_clock(tm);
- if (err)
- return err;
+ if (err) {
+if (err == HWCLOCK_INVALID_TIME)
+ *valid_p = FALSE;
+return err;
+ }
if (badyear)
read_date_from_file(tm);
@@ -1190,12 +1193,12 @@ manipulate_clock(const bool show, const bool adjust,
const bool noadjfile,
if (show || adjust || hctosys || (!noadjfile !systz)) {
/* data from HW-clock are required */
rc = synchronize_to_clock_tick();
- if (rc rc != 2) /* 2= synchronization timeout */
+ if (rc rc != HWCLOCK_SYNC_TIMEOUT rc != HWCLOCK_INVALID_TIME)
return EX_IOERR;
gettimeofday(read_time, NULL);
rc = read_hardware_clock(universal, hclock_valid, hclocktime);
- if (rc)
- return EX_IOERR;
+ if (rc rc != HWCLOCK_INVALID_TIME)
+return EX_IOERR;
}
if (show) {
diff --git a/hwclock/kd.c b/hwclock/kd.c
index 3da87ca..9071843 100644
--- a/hwclock/kd.c
+++ b/hwclock/kd.c
@@ -55,7 +55,7 @@ synchronize_to_clock_tick_kd(void) {
if (ioctl(con_fd, KDGHWCLK, start_time) == -1) {
outsyserr(_(KDGHWCLK ioctl to read time failed));
-return 3;
+return HWCLOCK_KDGHWCLK_ERROR;
}
/* Wait for change. Should be within a second, but in case something
@@ -73,18 +73,18 @@ synchronize_to_clock_tick_kd(void) {
if (ioctl(con_fd, KDGHWCLK, nowtime) == -1) {
outsyserr(_(KDGHWCLK ioctl to read time failed in loop));
- return 3;
+ return HWCLOCK_KDGHWCLK_ERROR;
}
if (start_time.tm_sec != nowtime.tm_sec)
break;
gettimeofday(now, NULL);
if (time_diff(now, begin) 1.5) {
fprintf(stderr, _(Timed out waiting for time change.\n));
- return 2;
+ return HWCLOCK_SYNC_TIMEOUT;
}
} while(1);
- return 0;
+ return HWCLOCK_OK;
}
diff --git a/hwclock/rtc.c b/hwclock/rtc.c
index 2e05385..84d85aa 100644
--- a/hwclock/rtc.c
+++ b/hwclock/rtc.c
@@ -177,10 +177,14 @@ do_rtc_read_ioctl(int rtc_fd, struct tm *tm) {
rc = ioctl(rtc_fd, RTC_RD_TIME, tm);
}
if (rc == -1) {
+ int err = -1;
+ /* special error case
Re: no keyboard during boot - fails (in: linux-image-2.6.32-trunk-powerpc_2.6.32-5_powerpc.deb)
Hi, Le mercredi 10 février 2010 à 14:22 +0100, Bernhard Reiter a écrit : Does no one have an idea on this one? Is this supposed to work? (I think I just file a report against the package then.) I did a small test here (PowerBook6,8) to see if I can have an USB keyboard working while still in initramfs : appended rootdelay=120 to the kernel command line, and hit some keys while it waits. Both the integrated keyboard (which is ADB on mine, I think) and my external USB keyboard work (at least, they display something on screen). Default 2.6.32 debian kernel, with default initramfs settings (so, modules=most). Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fan control ?
Niels S. Eliasen a écrit : interesting but must be something only available on newer PowerPC boxes... I have no such thing as /sys/devices/temperatures .. or anything remotely resembling this Yes, these entries are offered by the therm-adt746x module, which works only on: iBook G4, and the ATI based aluminium PowerBooks according to the module's documentation (though it also works on my 12 nVidia, from memory). Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: no sound on powermac3,3 (powerbook g4 550) debian502 gnome
Hi, Le lundi 14 septembre 2009 à 23:00 +0200, Gaudenz Steinlin a écrit : On Sun, Sep 13, 2009 at 10:27:01PM -0300, Rogério Brito wrote: So, for a distribution kernel, I guess that, once nobody complains about the problems, we can just standardize on snd-powermac (and have people have a working setup) and document the potential (perhaps nonexistent?) problem in the release notes for the arch. No, please not! At least on my powerbook5,8 snd-aoa works way better than snd-powerpc. And AFAIK this is true for all newer Powerbooks. It may be that snd-powermac is the only option for some of the older Apple powerpc based hardware. But please only enable it for devices that are not supported by snd-aoa. Completely agree with that. snd-aoa was made for newer Macs AFAIK, and it works very well here. The one that cause problem here is a powermac3,3 which is an old model, and which is not supported by snd-aoa according to http://johannes.sipsolutions.net/Projects/snd-aoa I am CC'ing Johannes, he may help us solve that long standing problem. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: no sound on powermac3,3 (powerbook g4 550) debian502 gnome
Le lundi 14 septembre 2009 à 15:09 -0700, Johannes Berg a écrit : On Tue, 2009-09-15 at 00:08 +0200, Benjamin Cama wrote: Completely agree with that. snd-aoa was made for newer Macs AFAIK, and it works very well here. The one that cause problem here is a powermac3,3 which is an old model, and which is not supported by snd-aoa according to http://johannes.sipsolutions.net/Projects/snd-aoa I am CC'ing Johannes, he may help us solve that long standing problem. And what _is_ the problem? AFAIK snd-aoa should work on all machines that it's auto-loaded on by the kernel. I'm sorry, I don't exactly know the current problem, but here on debian-ppc we keep having (as Rogério noted) people having problems with snd-aoa getting loaded instead of snd-powermac, as far as I understand. A quick search in my archives gives me the following threads : http://lists.debian.org/debian-powerpc/2009/09/msg00059.html http://lists.debian.org/debian-powerpc/2009/08/msg9.html http://lists.debian.org/debian-powerpc/2009/06/msg00034.html http://lists.debian.org/debian-powerpc/2009/05/msg00096.html http://lists.debian.org/debian-powerpc/2009/02/msg00083.html Just for 2009. I thought you could help, as there don't seem to be a lot of people left here that have the knowledge to solve that, appart from saying try modprobe snd-powermac. I think people on this list would be gratefull if you could help. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: 720p video on G4?
Hi, Just one remark made me tick : Le dimanche 13 septembre 2009 à 22:52 +0200, Rubén Gómez Antolí a écrit : Note: At this moment I'm using two monitors (using DVI output), Should be influenced in this test? I had problems with direct rendering on multiple-monitor setup because of the lack of video memory. Try with your laptop's screen only first. You could also look what exactly caused : (WW) RADEON(0): Direct rendering disabled in the logs, by looking the preceding lines. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: view flash website
Hi, the grv a écrit : You're right! Anyway, i'm a graphic designer. For my job I need a rule, a pencil, a sheet of paper, and unfortunely the Adobe tools. :) i MUST to view flash website because -as you known- Adobe fix some standards for the web market. [...] Repeat: i must. I hope that the future is better. Maybe am I stating the obvious, but as I didn't see it precisely mentionned : Adobe Flash is available only to x86 for linux and to PPC but for MacOS X. There is no way to make this plugin work on a PPC linux. Except maybe the qemu/nspluginwrapper trick but it looks far too hackish to me. And don't expect anything from Adobe for PPC, as this architecture is commercially dead for desktop use. The only solution, if you want the original Adobe stuff, would be for them to open-source it, but I am very doubtfull about it. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: view flash website
Shawn H. Corey a écrit : Benjamin Cama wrote: The only solution, if you want the original Adobe stuff, would be for them to open-source it, but I am very doubtfull about it. The strange thing is that Adobe did open source Postscript and PDF. Why don't they do Flash too? It depends on what do you mean by open, and what was opened. Postscript and PDF are open specifications : everyone is free to implement them. But Adobe didn't open any implementation : Adobe Acrobat Reader is proprietary software, for example. Concerning Flash, the specifications have recently been opened : they were already public before, but with restrictions on the implementations, like forbidding the implementation of a Flash player ... (Tough I don't understand how one can forbid anyone to implement something out of a specification ...). So, today, one could implement a Flash player freely. That's not simple as it bears a lot of backward-compatibility tricks, but it is theorically possible (look at gnash and swfdec). But that won't be enough for youtube videos : the proprietary Flash codec (don't know which one they're using today) is still a closed-source, closed specification one. You may have a better chance with H264 streams, though (I don't know how much of them youtube has as of today). Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Disable selecting with trackpad?
Matthias Grimm a écrit : Because you wrote that the option changed nothing, I assume you have an USB trackpad. Unfortunately I have no idea how to configure this thing. If it's the case and he uses synaptics, I would advise either : TouchpadOff 2 or TapButton1 0 in /etc/X11/xorg.conf in the synaptics section. man synaptics for more details. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian lenny installation on an ibook g4 keeps freezing
Amit Uttamchandani a écrit : On Thu, 18 Jun 2009 10:42:45 -0400 Tomislav V. Butkovic tomislav.butko...@gmail.com wrote: I'm installing debian lenny on an ibook g4 800mhz 360+mb ram and the Did you add the RAM yourself or was it added by your friend ? Do you know the brand, and its age ? installation process keeps freezing during various points of the installation during various installation attempts. Most commonly during the partintioning or during the installation of the base system. The farthest I've gotten in the installation of the base system is 98% then it froze. I am not sure what the problem here is. It seems that the longer period of time that the machine is off, the farther it can go through with the installation. To me this sounds like a faulty RAM problem. Try removing any additionnal RAM module and install Debian the usual way. I got the ibook from a friend with no hard drive. I put a 160gb seagate hard drive in, pata. I have tried installing ubuntu, opensuse, and now debian. Debian is the only installer that has gotten this far without any other problems. Has this iBook got any other problem before that you're aware of ? Any help would be appreciated. I am new to linux, though I strongly support the concept of community run open source software development and the free distribution of information. Thank You, tomislav [...] Instead of installing the whole base system. Simply use the net-install CD and install the most basic system. This means when you are asked to select what kind of install you want, disable the 'Desktop System'. Is there any memory testing tool for powerpc ? AFAIK, memtest is only for x86 ... Could be usefull to detect RAM problems. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian lenny installation on an ibook g4 keeps freezing
Le jeudi 18 juin 2009 à 15:06 -0400, Tomislav V. Butkovic a écrit : To me this sounds like a faulty RAM problem. Try removing any additionnal RAM module and install Debian the usual way. The additional RAM module is originally installed as the sticker on the ibook says: 800MHz/384MB/40GB/COMBO - Should I still try taking it out? I never saw an iBook with such an amount of RAM, but if the sticker says it so ... keep it that way. And as the others have deducted from your fan's activity, this may rather be an overheating problem. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: flashplugin and nspluginwrapper + qemu
Hi, drz a écrit : OK, I found the Better Youtube Addon in Iceweasel. That worked with every video so far ;) Its downloading the video from flashload first. I just wanted to point out that I use UnPlug, now that is has been made compatible with Iceweasel 3. It works on a lot of websites and doesn't depend on some server-side provider. https://addons.mozilla.org/en-US/firefox/addon/2254 Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: iBook G4 dual head
Le vendredi 08 mai 2009 à 21:44 -0700, Amit Uttamchandani a écrit : On Sat, 9 May 2009 12:47:30 +1200 Jamie Downs jamie.do...@gmail.com wrote: I have edited /etc/X11/xorg.conf It now has Virtual 2304 768 as explained below by Jos__ The command I use to enable dual head is xrandr --output LVDS --mode 1024x768 --output VGA-0 --mode 1280x1024 --left-of LVDS I'm still investigating ways to make the screen mode persistent after a reboot. It seems like I need to write a bash script. Yes, that is probably the simplest way. Depending on your desktop environment, you could add that line to your ~/.xinitrc. Or you could simply add an alias to it in your ~/.bashrc file and invoke it at will. The right way to do that is described here : http://wiki.debian.org/XStrikeForce/HowToRandR12 in section III. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: xorg.conf powerbook g4 kde 4.2.2
Le samedi 09 mai 2009 à 20:02 -0700, Amit Uttamchandani a écrit : On Sun, 10 May 2009 02:00:56 +0200 drz d...@rizzux.org wrote: 1. I havent worked on getting the wireless to go. Any Links to HOWTOs are welcome. Wireless should work out of the box. I never had an issue with wireless on this PB G4. What do you get when you type 'sudo iwlist scan'? Also, you might need to install wireless-tools if that command is not available. It works out of the box except for on thing : the proprietary firmware. You have to install b43-fwcutter, which will (normally) download and install it. You can look at the archive of this list for more information, quite a lot of people had this problem. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Xorg does not detect nvidia card
fight4por...@gmail.com a écrit : I could not get my card to work in lenny until I installed the NVIDIA Proprietary drivers. There's no such thing as a NVidia proprietary driver for powerpc, since you insist on using it. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: help installing on powerbook6,8 w/ dead cd drive
Le dimanche 22 mars 2009 à 10:48 -0500, Ross Gohlke a écrit : I also looked into netbooting, but documentation is inconsistent and I could not find netbootable binaries. I netbooted my powerbook to install Debian on it, and it went smoothly (I already had an experience by netbooting some OpenWrt router ; I also netbooted back my amd64 from my powerbook ... so I may be a bit more experienced, but with some docs it goes ok) The files used to netboot lenny and the documentation can be found here : http://www.debian.org/distrib/netinst#netboot I set up dhcp3-server, tftpd-hpa, and can then netboot my PB. The hardest part was finding the correct way to configure some quirks of Apple's way of netbooting. In the DHCP server config, you must specify both next-server and server-identifier to the IP of your netboot server. Also, setting a filename gets ignored by open-firmware's netbooting code. So, the correct command to use when in OF on your PB : boot enet:0,yaboot This should be enough to get you running the debian installer. Don't hesitate to ask if you need some more details. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: broadcom 4306 rev 3 ndiswrapper
stephen sefick a écrit : I have read that the b43 driver only allows 11mbs while the ndiswrapper procedure works at 54mbs. My wireless is running slow and I am trying to get it up to speed any help would be appreciated. Should I use ndiswrapper or am I out of luck. First, b43 indeed allows 54Mbps, and it wouldn't change anything anyway as the speed limiting factor would be your internet connection. Second, ndiswrapper can't work on PPC, as it uses DLL created for Windows on the x86 architecture. Your problem must come from somewhere else. I personnaly have no speed problem with b43. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: broadcom 4306 rev 3 ndiswrapper
stephen sefick a écrit : I have side by side my laptop (ibook G4 Debian GNU/Linux) and desktop (mac mini mac os x 10.5.6). I have found ethtools in debian and the connection speed is only 10Mb/s in the mac network utility the link speed is set at 54Mb/s. So what gives you said that 54Mb/s was allowed and side by side I am only getting 10Mb/s on my linux box. I don't know ethtools, but I don't think it is appropriate for wifi connections : there is no such thing as 10Mb/s 802.11 (wifi). I think that you are mesuring the speed of your wired connection ; recheck on what interface exactly you're running your tool. If you want to know the speed of you wifi connection, use 'iwconfig wlan0' as root. The 'Bit Rate' property should tell you at what speed you're connected. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is pbbuttonsd used for nowadays?
Le samedi 31 janvier 2009 à 21:38 +0100, Gerfried Fuchs a écrit : Thanks, I am reading the list I post to, otherwise I wouldn't had followed up to the thread. ;) No need to extra Cc me. I thought it was the policy on this list ... sorry for the annoyance. The unnamed desktop environment in the debian-installer installs the desktop environment that is the default for that CD. There are first CDs for gnome, KDE and xfce, so all three of them are default. Well, I installed debian by using the netboot image, which has no desktop environment on it. So this is why (again ...) I'm calling it default. I have no official URL to back it up, but I thought it was natural to have gnome as default, as it is today the DE of most distros (beware, I'm a gnome user, so I may not have an objective POV). but I didn't think of it because I never owned (or saw anyone using debian on his PB) a backlit PowerBook. Mostly because I only really use it when I'm lying in bed in the dark. Not completely sure if the usecases for that feature is much different for other people, but I highly doubt that you (or others) would be able to see me using that because of this. ;) Point taken :-) but what I meant by not seen anyone was rather not knowing anyone who used pbbutoonsd for his backlit PB, rather than actually seeing him. Excuse my english ... On the other hand, I haven't seen this on much other hardware platforms, and given that specific hardware features (like this) indeed _are_ hardware vendor specific, it shouldn't be considered too strange that there are special tools to support them for that architecture. Of course. Even if I seem to remember some very specific model with this feature, but it's not common at all. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is pbbuttonsd used for nowadays?
Le vendredi 30 janvier 2009 à 22:18 +0100, Børge Holen a écrit : Top posting. Gnome default? When did that happen? Never did a default, but how does gnome know I got backlit buttons on F9-11? As far as I remember, selecting the unnamed desktop environnement in the debian-installer installs Gnome. This is why I called it default, but you can of course not install any DE at all. I admit I forgot the backlit keys, that is still lacking in any default tool appart from the mac-specific ones (pbbuttonsd and the like). To all who made this remark (especially Gerfried), this is of course not acceptable not to fully support this hardware part, but I didn't think of it because I never owned (or saw anyone using debian on his PB) a backlit PowerBook. This is just a bit ackward, I think, to have this kind of particularity on the mac platform, and overlapping tools for the other jobs. But no offense here, pbbuttonsd is still a good tool for what it does. Regards, Benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RealPlayer audio streams
Hi, I don't want to sound too pedantic, bit I'd like to precise some things : Le mardi 27 janvier 2009 à 14:28 +0930, Mike Hore a écrit : Anyway, kplayer is happily handling real streams, MP3 and WMP with no problem. Hey, I'm not a purist, I just like to get the job done, any way that works :-) It's not about being a purist, it's just about not breaking the law. By using this software, you put yourself in an illegal position in your country, and I don't know why some people find it exciting to break the law (a famous example in our computer world being by using software they've obtained illegally), but that's not my case. I am fortunate enough to live in a country (France) where software patents are not recognized valid (well, appart from the schizophrenia of the European Patent Office accepting software patent applications although they're not valid according to the law), but I don't like the way some people want any work of thought to be patented in a lot of countries. Maybe Europe is coming next. Debian and a lot of FOSS projects/people don't like it too but try to play fair and show the people that in some country their work may be illegal. They show that some stupid law make them and their users be at risk of some legal action. I am not telling you not to use these software, on the contrary ! I think that you're just being reminded, by using this repository, that your act is condemned in some place like yours, because of these laws. And I think you should care, so that you can better fight these rules that hinders you from lawfully using some of the free-software that come with Debian. Regards, benjamin -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Tool for detecting partition superblocks needed
Le jeudi 02 octobre 2008 à 20:17 +0200, Wolfgang Pfeiffer a écrit : Could this also be a simple file system damage? Errors like that (i.e. in the middle of a DMA interrupt) are not simple FS damage, I am pretty sure. I was hoping it was just something like that, because this hopefully could be fixed with a reinstall, and with a previous low-level formatting like dd if=/dev/urandom of=/dev/hda (not being sure whether the syntax is correct .. ) For this kind of low level formatting, I would advise you to dd from /dev/zero, as the hard drive controller can try to replace bad sectors if needed when it sees that an all-0 block is written. But when some sectors begin to fail, others will soon come, in general. Oh, and the Fedora smartctrl found (surprise, surprise .. :) a failure on LBA 76724676 and 76724678, too (please see the old log above) ... Well, this confirm that the error lies in hardware, not in the file system itself. I attach the log made on the broken machine via smartctrl -a /dev/hda So, the very high numbers like Raw_Read_Error_Rate and Seek_Error_Rate are meaningless, I think, but the numbers in Offline_Uncorrectable and UDMA_CRC_Error_Count show that some sectors have already been lost. But what worries me most is the Load_Cycle_Count value : 2898441 is far too high for a disk, but may look real, as your disk as been spinning for quite some time (1+ hours). This roughly corresponds to a load/unload every 15s : do you here some light tic tac sound from your disk every 15s or so ? For reference, mine, which has a 8000+ hours lifetime, has a count of 268656 (ten times less ...). If you take the specs from seagate for your hard drive ( http://www.seagate.com/docs/pdf/datasheet/disc/ds_momentus5400.2_120gb.pdf ), you'll see it's made for at most 60 load/unload cycles. I am worried about it because this is what I saw from a lot of apple laptops, and as you may have understood, from one of my lost iBook's hard drive. This made the news some time ago, not especially for apple's disks, but when Ubuntu was said to be killing hard drives : some vendor BIOSes did not set the power saving mode of the hard drive correctly, which led them to load/unload too often, and kill the hard drive in a very short time. AFAIK, OpenFirmware does not set any power saving mode at all, and neither does OSX, and by default a lot of disk are in a maximum power saving mode, which unloads the hard drive head very often, thus consuming less energy but shortening the life of the hard drive. For some years, I've been seeing a lot (4 from my eyes, more from internet forums) of apple laptops fail after a bit more than a year (mostly on low end laptops, like the iBook, whose hard drive is made to bear no more than 30 load/unload cycles). Most of them were not using Linux, just OSX. I don't know if this information should be louder spoken, because I wasn't able to verify that on failing laptops I didn't handle but heard to be failing quite soon in their life. But this is, I think, one of the main reason hard drives seem so fragile today, as the autopsy shows that the number of load/unload cycles really exceeded what the vendor says, and as a lot of vendors want their laptop to save energy, they set aggressive settings to gain some battery life. You can change these settings with the -B option of hdparm, for example : hdparm -B254 /dev/hda disables power management on most hard drive (the value is drive dependant, most of the time 255 or 254 disables power savings). I think this is what is done in laptop-mode package when you set your hard drive in no PM mode. What do you mean by see hda7 ? to see in the sense of to detect ... mac-fdisk detected the damaged partition in the Debian installer, IIRC .. What I meant is that, if you can see some partition in mac-fdisk, you can see them all. But this doesn't mean the FS on them is not failing. When you said you didn't see hda7 but you did with the others, it sounded strange to me. No, not that easily .. It's a Powerbook5,8: if I manage to remove the disk from it (there must be instructions somewhere on www) I'll reinstall a new one. No time to waste, because my old tibook, where I'm typing this email, is making strange noises already. Looks like I'm in need of quick decisions, besides working hardware ... :) Well, the instructions from macfixit are good, I already disassembled a 12 iBook and a 15 PB with them. And it looks like you will need them soon ... BTW, how old is your powerbook ? a little more than 2.5 years. Still with the same disk installed that was shipped with the machine .. My iBook lasted a bit more than a year, with an hard drive spec'ed for half the load/unload cycle count ... make up your mind. Begards, benjamin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool for detecting partition superblocks needed
Le mercredi 01 octobre 2008 à 22:29 +0200, Wolfgang Pfeiffer a écrit :
Excerpt from the Debian install syslog, cut:
kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=76724680,
high=4, low=9615816, sector=76724680
kernel: ide: failed opcode was: unknown
kernel: end_request: I/O error, dev hda, sector 76724680
kernel: Buffer I/O error on device hda7, logical block 1
kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=76724676,
high=4, low=9615812, sector=76724676
kernel: ide: failed opcode was: unknown
kernel: end_request: I/O error, dev hda, sector 76724676
kernel: Buffer I/O error on device hda7, logical block 0
kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=76724680,
high=4, low=9615816, sector=76724680
kernel: ide: failed opcode was: unknown
kernel: end_request: I/O error, dev hda, sector 76724680
... and the errors on sectors 76724680 and 76724680 are reported again
and again ... and only these 2 sectors, IINM ..
These are quite severe hardware errors, I would advise you to do some
complete copy of your harddrive right now before it gets worse. Just dd
your hda, or use some other recovery software (like
http://www.garloff.de/kurt/linux/ddrescue/ ).
If only hda7 is affected, I think this is only the beginning, and if you
have backups it would be better.
Failing hda7 is the root partition. hda6, not being listed here, with
quite a few errors, was recoverable ... tho it's not quite clear
whether this hda6 errors started while I was playing with the Debian
Installer (Etch, IIRC) ...
This may not be related.
Maybe you could try to run smartctl -a from here, to get some
(hopefully) usefull stats from it.
IIRC:
the installer later on didn't even see hda7, whereas mac-fdisk did
(took quite some time for it to finish the detection ...).
What do you mean by see hda7 ? If (mac-)fdisk isn't even able to list
your partitions, one of the first blocks of your hard drive may be
damaged too.
Apple Hardware Test on the OS X install CD seems to hang/crash, or
simply does not load even after 15 Minutes or so ...
Well, being on the same IDE controller might not help. Can you remove
the HDD from your laptop for further analysis ?
BTW, how old is your powerbook ? I saw so many less-than-2-years iBook
fail, PBs might long longer but not that much ...
benjamin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Configuration wifi sur un PowerBook G4
Sorry for the french answer, I don't know if he speaks english. This is basically a missing firmware problem. Le samedi 16 août 2008 à 00:30 +0200, [EMAIL PROTECTED] a écrit : Bonsoir, Bonsoir, Tout d'abord, cette liste est anglaise, donc on parle anglais normalement :-) Je viens d'installer la Debian Etch sur mon PowerBook G4, et il s'agit donc de ma toute première intervention sur cette liste de diffusion. Tout est parfaitement (et facilement configuré), sauf la connexion sans-fil. J'ai laissé sur un site les résultats de différentes commandes entrées dans le Terminal pour résoudre le problème, mais là, je sèche... Vous trouverez ces indications sur le forum de Macbidouille : http://forum.macbidouille.com/index.php?showtopic=276610. Il te manque juste le firmware de la carte wifi, qui n'est pas libre, et donc n'est pas distribué avec Debian. Normalement, à l'installation du paquet bcm43-fwcutter, il a du te proposer d'aller le télécharger. Sinon, tu peux le trouver ici : http://www.linuxwireless.org/en/users/Drivers/b43?action=show#devicefirmware Accessoirement, la solution est dans les premiers résultats d'une recherche sur le message d'erreur dans Google ... C'est peut-être que tu ne parles pas anglais, dans ce cas je comprend ta difficulté quand il s'agit de bidouiller un peu ! Tout est souvent en anglais ... benjamin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sound output on PBs
Le dimanche 27 mai 2007 à 01:01 +0200, Børge Holen a écrit : Is it just me or is the audio output on the PB just a poor excuse for gettin an external usb soundcard. For certain aint handling any low/high frequezies without scrambling it. It for sure cant make my 300$ headphones work for the money. I've pretty much decided that I would like my PB to grow a pci slot for my live! soundblaster. I'm using VLC for audioplayback and the equalizer witch follows. Anyone got some clue on what to put my money on, both small, portable and something that I actually can use for audio listening. I got a Behringer UCA202 : http://www.behringer.com/UCA202/index.cfm?lang=eng (Burr-Brown/TI PCM2902 chip inside) which is low-end musician quality USB sound card and has quite a good sound quality (good SnR ratio, low THD and a wide frequency response : see the manual for the actual values). And it is pretty cheap, i found it for around 30€ in a music shop. Of course, working fine with linux-usb-audio. Except for a small bug that i could maybe point someone's attention on here : http://marc.info/?l=linux-usb-usersm=116791458129201w=2 which is quite annoying (appears only on ppc apparently). But the quality is worth it for such a cheap device. No more distortions in loud and high sections, a bit less background noise. Tested with a Sennheiser HD495 headset. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Random hang when waking from sleep on ibook G4 + 2.6.14.3 kernel
Le lundi 06 février 2006 à 14:52 +, Joerg Sommer a écrit :
Benjamin Cama [EMAIL PROTECTED] wrote:
- Did the 2.6.13.1 solve the oops problem when an USB peripheral was
plugged when sleeping ? (compared to my 2.6.12)
Yes. This was the reason I switched to the 2.6.13.1.
Ok. As this seems to be a strange problem, i'll try to explain what i
found when investigating the 2.6.12 oops (not the problem i experienced
with 2.6.14.3): this may have already been seen here on the list, but
i'd like to know what exactly caused this oops, and if its fix in
2.6.13.1 was intentional or not. Please correct me if you think i made
a mistake in my debugging process, as i'm new to kernel debugging...
The 2.6.12 kernel oopsed in the hid_resume() function in
drivers/usb/input/hid-core.c. I disassembled it with objdump and tried
to follow what happened; but i'm not very good at ppc assembly. What i
found is that the pointer returned by usb_get_intfdata(intf) was NULL,
and that it caused the oops when it was dereferenced in the if
statement. As a reminder, here is this function (hint: the intf
parameter was not null, according to the kernel registers dump):
static int hid_resume(struct usb_interface *intf)
{
struct hid_device *hid = usb_get_intfdata (intf);
int status;
intf-dev.power.power_state = PMSG_ON;
if (hid-open) // OOPS HERE
status = usb_submit_urb(hid-urbin, GFP_NOIO);
else
status = 0;
dev_dbg(intf-dev, resume status %d\n, status);
return status;
}
A naive answer would be to test if hid is null before dereferencing, but
naturally the problem lied elsewhere, as this piece of code seems to
work for 2.6.13.1, like Joerg said (the code is still the same for 14.3.
In fact this extract _is_ from 14.3 but i'm pretty sure it was the same
in 2.6.12).
So i'd like to know : did someone correct this very problem ? Or was it
fixed by some other change that wasn't aimed particulary at this bug ?
Or should i rather ask this to the usb mailing list ?
I don't know if this bug is related to my 2.6.14.3 (and later, according
to Joerg) problem, but as i don't know how to solve it, i try to do my
best to find anything that could help.
And as a side note, i recently got another oops when plugging my mouse
just after waking my ibook, but before the usb subsystem was initialised
(yes, i'm still unplugging my mouse on every sleep, because i don't want
to guess if my kernel will hang or not on the next wake). I'll try to
find more details on this later.
And thanks to Joerg for your answers.
Benjamin Cama
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Random hang when waking from sleep on ibook G4 + 2.6.14.3 kernel
Le dimanche 05 février 2006 à 19:56 +, Joerg Sommer a écrit : I can confirm this bug. I see it since the update from 2.6.13.1 to 15.1. $ cat /proc/cpuinfo cpu : 7455, altivec supported revision: 0.3 (pvr 8001 0303) motherboard : PowerBook6,3 MacRISC3 Power Macintosh detected as : 287 (iBook G4) Bye, Jörg. I forgot some details on my config : % cat /proc/cpuinfo processor : 0 cpu : 7455, altivec supported clock : 606MHz revision: 0.3 (pvr 8001 0303) bogomips: 610.30 machine : PowerBook6,3 motherboard : PowerBook6,3 MacRISC3 Power Macintosh detected as : 287 (iBook G4) pmac flags : 001b L2 cache: 256K unified memory : 640MB pmac-generation : NewWorld So this is basically the same, i think (mine is a 800MHz G4). The memory upgrade comes from a cheap brand, but i don't think it causes such crashes (i had about 2 strange crash in 2 years, on MacOS X, that may have been caused by bad RAM) as this problem occurs more often. Finally, my ibook had is hard drive replaced (after a HD crash), but i don't think i damaged anything... Some questions now : - Did the 2.6.13.1 solve the oops problem when an USB peripheral was plugged when sleeping ? (compared to my 2.6.12) - Did you activate PREEMPT in your 2.6.15.1 ? I'd be interested in this details. Thanks Benjamin Cama -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Random hang when waking from sleep on ibook G4 + 2.6.14.3 kernel
Hi, First, i must admit i'm using ubuntu, not debian. Hope this won't interfere with my problem, but i think it's kernel-related, and i know that most of the ppc kernel stuff takes place here. I'm also new to this list. I regularly use the sleep feature of my iBook, and it works quite well with a recent kernel, thanks to BenH patches. I used to have a ubuntu-built 2.6.12, but it oopsed when waking from sleep while an USB peripheral was plugged in (in my case, an USB mouse). I had to think to unplug it each time i put my ibook to sleep, which i didn't remember all the time... I found that this kernel had this problem, but that it was resolved in more recent ones. So i built a vanilla 2.6.14.3 kernel, and it worked well even when my mouse was plugged-in and that i put my ibook to sleep. But one day, it couldn't wake up, hanging on this screen : http://benoar.free.fr/ibook_hangs.jpg I tried to find the cause, but i couldn't reproduce this bug. I think it is still due to some USB-related problem (you can see on the top of the screen a previous wake-from-sleep that succeeded). It worked well for another period, but this bug reappeared after a while. It doesn't appear very often, and i can't reproduce this exactly, hence the random of the subject of this mail. I didn't try a more recent kernel (2.6.15 ?) but i could check, if someone thinks it comes from this particular version. Here's some detail : [EMAIL PROTECTED]:~% uname -a Linux benoar 2.6.14.3-benoar1 #1 PREEMPT Sun Dec 11 23:09:28 CET 2005 ppc GNU/Linux Well... i just remember i activated preempt... may this be the problem ? i think i already saw strange bug coming up when this option is activated, in some post on this list. The think is, if i check without preempt, how to check it won't happen again...? Sleep/wake a lot of times ? I'll be glad if someone could give me some advice. Thanks in advance. Benjamin Cama -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
