DamageG Posted February 1, 2012 Share Posted February 1, 2012 I'm trying to install Debian on an IBM server and have not been able to create a boot disk that loads the install program correctly. I need some non-free drivers and loading them with the USB key confuses the system. What I've tried is to download the net install CD and then extract it into a directory with 7-Zip. Then I extracted the tar ball of non-free drivers into the firmware directory and built a bootable iso. I selected the isolinux image as the boot image and checked the Patch Boot Information Table box. I got the splash screen with the menu but was not able to get it to proceed. If I burn the iso directly without the extraction process, everything works fine. Any ideas? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 1, 2012 Share Posted February 1, 2012 Can you point me at the exact image file you downloaded? I assume you've tried building a new disc without changing anything (adding in your extra bits) and it still wouldn't boot? Link to comment Share on other sites More sharing options...
DamageG Posted February 1, 2012 Author Share Posted February 1, 2012 Thanks for your help on this. I burned the disk straight from the downloaded iso and that was no problem. Here is the install iso http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/firmware-6.0.4-amd64-netinst.iso Then the drivers are in this file. I'm extracting this to the firmware directory in the above file http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/squeeze/current/firmware.tar.gz Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 1, 2012 Share Posted February 1, 2012 Do you have the log from when you built the new ISO please? Link to comment Share on other sites More sharing options...
DamageG Posted February 1, 2012 Author Share Posted February 1, 2012 Here it is... I 08:06:34 Device Ready! I 08:06:37 Operation Started! I 08:06:37 Source Device: [0:0:0] HL-DT-ST DVD+-RW GH50N B104 (D:) (ATAPI) I 08:06:37 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: MCC 03RG20) I 08:06:37 Source Media Supported Write Speeds: 4x, 8x, 16x I 08:06:37 Image File: -==/\/[bUILD IMAGE]\/\==- I 08:06:37 Image File Sectors: 98,192 (MODE1/2048) I 08:06:37 Image File Size: 201,097,216 bytes I 08:06:37 Image File Volume Identifier: debian I 08:06:37 Image File Volume Set Identifier: 4041404300017F84 I 08:06:37 Image File Application Identifier: IMGBURN V2.5.6.0 - THE ULTIMATE IMAGE BURNER! I 08:06:37 Image File Implementation Identifier: ImgBurn I 08:06:37 Image File File System(s): ISO9660 (Bootable), UDF (1.02) I 08:06:37 Read Speed (Data/Audio): MAX / MAX I 08:06:38 Verifying Session 1 of 1... (1 Track, LBA: 0 - 98191) I 08:06:38 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 98191) I 08:07:05 Exporting Graph Data... I 08:07:05 Graph Data File: C:\Users\DamageG\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_DVD+-RW_GH50N_B104_WEDNESDAY-FEBRUARY-01-2012_8-02_AM_MCC_03RG20_4x.ibg I 08:07:05 Export Successfully Completed! I 08:07:05 Operation Successfully Completed! - Duration: 00:00:26 I 08:07:05 Average Verify Rate: 7,855 KB/s (5.7x) - Maximum Verify Rate: 10,351 KB/s (7.5x) Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 1, 2012 Share Posted February 1, 2012 That's not building it but don't worry now, I see the issue. It brings up the first menu but just keeps reloading it when you select an option from it. Link to comment Share on other sites More sharing options...
DamageG Posted February 1, 2012 Author Share Posted February 1, 2012 Thanks. That's exactly what I got - splash screen and a beep every time you hit enter. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 1, 2012 Share Posted February 1, 2012 I'm guessing the installer/bootloader doesn't work with Joliet (or UDF) and so relies on the Rock Ridge file system for long file names. As ImgBurn doesn't support that you're left with using ISO9660:1999. So set the 'File System' to 'ISO9660' and then click the '1999' link on Advanced -> Restrictions -> ISO9660. Build a new image and then try that one. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 1, 2012 Share Posted February 1, 2012 Correction, you need ISO9660:1999 and Joliet. Without Joliet the installer just fails a bit later on complaining about a 'Release' something or other. Link to comment Share on other sites More sharing options...
DamageG Posted February 1, 2012 Author Share Posted February 1, 2012 That worked. Thank you. Debian still won't read the firmware files on the disk but that's another issue. Great program by the way. I've used it for years. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted February 2, 2012 Share Posted February 2, 2012 I won't pretend to actually know what I'm doing here but maybe the obvious 'firmware' folder isn't actually the right place for them? Searching all files on the disc for 'firmware' seems to have loads of hits in the file 'dists\squeeze\non-free\binary-amd64\Packages' and opening that file in notepad shows it pointing at firmware files in the folder 'pool\non-free\f\firmware-nonfree'. Are you perhaps meant to put your files in there and add their info to the 'Packages' file so it knows they exist? Link to comment Share on other sites More sharing options...
Recommended Posts