Slamd64 RC4 won't boot?

cheater1034 · 06-10-2005, 09:22 AM

Hi, I have slackware current installed, and I have an extra partition I was gonna try slamd64 on, but I downloaded the first 2 slamd64 isos, which I think is all I need, then I burned them as images in k3b, but for some reason they won't boot, do I have to do anything special with the iso images to make them boot, or what's going on with it?

heltreko · 06-10-2005, 10:50 AM

Hi

There should be no need to do anything special. I've burned and booted all cd's from RC1 to RC4 without problem.

A here's a small suggestion that may sound stupid. - Did you set the bios to boot from cd prior to hd?

cheater1034 · 06-10-2005, 10:59 AM

yeah I did, it checks the cdrom, then it sits there and hangs for a minute, then it just goes into lilo.
I downloaded the iso image twice, in case the md5sum was lying to me, and it still didnt boot.

Now if k3b worked, I'd try an older release, I downloaded the rc3 cd1, and am trying to get k3b or some other util to work again :X it's just strang, maybe it has something to do with k3b, it does burn as low as 3x, when I set it to 52x on my 52x burner.

Maybe it's just burning corrupt cds.

cheater1034 · 06-10-2005, 11:06 AM

nvm I know the reason, but not the solution, I burned it in xcdroast, to see if it would work, and when it completed, it said possibility of 25 buffer underruns, but it was the only thing I had open, so I'm going into windows to burn it, but does anyone know how to fix that problem?

That is * the problem of it burning slow, making the whole pc slow, and getting buffer underruns.

and it burns at under half the speed I tell it to.

heltreko · 06-10-2005, 02:46 PM

OK, the isos should be fine.

I downloaded and burned them using nero in windows.

Got a better connection at work and did it there.

I had some other problems with SLAMD64 linked to my seagate SATA hdd. Could for some reason not get the mkswap part to work and got a segmentation fault error. This is described in an other thread here at linuxquestions.org. Dodged the problem by keeping my existing Slack install and did not toutch the swap partition during the slamd64 install.

GlowGlow · 06-13-2005, 01:49 PM

I had the same problem with the RC4 ISO, it seems a problem some BIOSes and the El-Torito settings used on the ISO. You can boot the CD using Smart Bootmanager. Grab sbootmgr.dsk from the rootdisks/ directory on the Slack CDs or a Slack FTP site, and write the image to a floppy disk with:

Code:

dd if=sbootmgr.dsk of=/dev/fd0

Then boot with the floppy disk, and choose to boot the CD-ROM.

mdg · 06-14-2005, 01:02 AM

I couldn't boot with the first cd, but the second cd did boot and ran the install, which makes me think they might be wrongly labelled at the ftp site

chylde · 03-02-2006, 10:24 PM

Hello,

I just got a hp dv5k laptop, my old one was a compaq. I have slackware 10.1 and windows xp. Slackware boots fine, but it sucks not being able the additional 32 bits on my processor, which seems much slower in a 32-bit enviroment. So i tried installing slamd64 10.2, it gets to the boot prompt, loads the bare.i img, and init, then starts to detect hardware, then the screen goes blank, any suggestions?

Thanks,
Chylde