2.6.4 not detecting all ram on TiBook 4

2004-03-11 Thread Satadru Pramanik
I just upgraded the ram on my system from 512MB to 1024MB and the system when running in linux does not detect all the ram on the system. OS X recognizes that two 512 MB PC133 SDRAM chips are installed. dmesg shows this: Total memory = 768MB; using 2048kB for hash table (at c060) Linux vers

Re: Trouble getting Alsa to configure

2004-02-27 Thread Satadru Pramanik
installed. Would I need any others? Quoting Satadru Pramanik <[EMAIL PROTECTED]>: What command are you using to build the alsa modules? Do you have the debian kernel building packages installed? Satadru On Feb 27, 2004, at 1:07 AM, [EMAIL PROTECTED] wrote: Seems the more issues I

Re: Trouble getting Alsa to configure

2004-02-27 Thread Satadru Pramanik
What command are you using to build the alsa modules? Do you have the debian kernel building packages installed? Satadru On Feb 27, 2004, at 1:07 AM, [EMAIL PROTECTED] wrote: Seems the more issues I solve, the more pop up.I have downloaded and unpacked the alsa-driver source from alsa-proje

Re: It's ALIVE!!!!

2004-02-27 Thread Satadru Pramanik
I've put the .config up for that kernel up at http://pramanikconsulting.com/debianppc/kernel.config - if it helps. Satadru On Feb 27, 2004, at 12:54 AM, [EMAIL PROTECTED] wrote: Sure thing... I'm running the benh-2.6.3 kernel, as well as XF86Config, that satadru pramanik so kindl

Re: Debian install Tibook IV 1 Ghz

2004-02-26 Thread Satadru Pramanik
If by Powerbook G4 you refer to the 1ghz TiBook, here is what I can offer you: I am putting up some files from my working installation here (Including a working 2.6 series kernel and relevant modules): http://pramanikconsulting.com/debianppc/ I installed using I believe a testing tree insta

Re: Installing Debian using debian-sarge-netinst.iso (powerpc)

2004-02-22 Thread Satadru Pramanik
hdiutil burn cdiimage.iso On Feb 22, 2004, at 2:05 PM, Brad Lathem wrote: I kept getting the "Apple_Bootstrap" error when I was installing. It turned out that using a different version of the installation files fixed the problem. Of course, I was doing the installation without any physical