Thanks for the reply. 1st time doing this for me, so pls bear with... Also, this might be the wrong list for this, but since its breaking the AutoYast installation (Well, no network support = no AutoYast)....
The x346 has the new BCM5721 chip. SLES8 does not have built in support for this chip, so to get network support into the install initrd I had to do the fillowing.
Build the new module against the same kernel tree as the install kernel. The one I was using happaned to be 2.4.21-138 (I also used the smp the 1st time by accident).
Save the original initrd
zcat initrd > rd
mount -oloop rd /mnt
copy the new .o file to /mnt/modules/
umount /mnt
gzip -9 rd
mv rd.gz initrd
So, now I had a initrd with the new bcm5700.o file (with support for the 5721 chip). The only modules.pcimap I could find was in /lib/modules/modules.pcimap in the build tree. Not in initrd. It didnt have an entry for the new chip. I know the vendor ID is 14e4 and the device ID is 1659. But I dont know the subvendor, sbudevice, class, class_mask or device_data. Im assuming this is the correct place to update. I am having difficulty finding docs for this. What I did find said the distro usually fills out this information.
Any more suggestions or links to Doc's I should read?
Thanks
Joseph V Moss jmoss@ichips.intel.com 12/29/2004 04:30 PM
To
Aaron Amauba aapa20032003@yahoo.com cc
suse-autoinstall@suse.com Subject
Re: Fw: [suse-autoinstall] customizing initrd
Update the modules.pcimap (in /lib/modules/<kernel_version>-default/ in the initrd) with the PCI ID of the new chip.
I am trying to do the same thing (except with a x346 instead). I added the new bcm5700.o file to the /modules directory in initrd. After I do that I have to add the module manually. Its nots found automatically. What else do I have to change?
Thomas Mieslinger Thomas.Mieslinger@gls-itservices.com 11/25/2004 12:26 PM
To
suse-autoinstall@suse.com cc
Subject
Re: [suse-autoinstall] customizing initrd
I'd like to install a new ibm x336 with bcm5721 network chips. These are not support by the standard kernel so I need to change the bcm5700.o. -- GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: thomas.mieslinger@gls-itservices.com
Anas Nashif nashif@suse.de schrieb am 25.11.2004 21:22:33:
The trailing garbage message can be ignored. I have no idea where it comes from, but after recreating the initrd as described earlier, it works. What exactly did you change in the initrd?
Anas
Thomas Mieslinger wrote:
Hi Andi,
this initrd is right off the SLES 8 SP3 cd. Without the trailing
garbage it
doesn't boot anymore. How can I re-add this to the initrd?
Thanks in advance
Thomas
GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: thomas.mieslinger@gls-itservices.com
Andi Kleen ak@suse.de schrieb am 25.11.2004 20:57:09:
On Thu, Nov 25, 2004 at 08:52:05PM +0100, Thomas Mieslinger wrote:
Well I think the problem is that during uncompression I get this
message.
root@deinst01> gzip -d initrd.gz
gzip: initrd.gz: decompression OK, trailing garbage ignored
when I recompress this file it is smaller than the original and doesn't boot anymore.
What is that "trailing garbage ignored"?
It's possible to append a custom DSDT to the initrd. DSDT is a BIOS ACPI table which is often buggy on laptops and can be replaced. But for non laptops that's rarely done and the installer never does it on its own.
-Andi
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
autoinstall@lists.opensuse.org
-
Aaron Amauba