Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hi folks,
slamd64-11.0
AMD Athlon64 x2 AM2 3800
Corsair PC-6400 (800) dual channel 1Gx2 (2G) RAM
HD - SATAI have the captioned DVD iso image download on Internet with md5sum checked without error. The image was burned on DVD with K3B.
I installed the OS twice but unable to boot displaying a black screen with "99 99 99 99 99 99 99 99 etc." on it. LILO bootloader has been installed. Reboted the DVD installer and started "setup" again. I was not allowed to evoke "Configure". Highlighting "Configure Reconfigure your Linux Sytem" and hitting "OK", it jumped to "Help" row.
Please help. Would it be the problem of the DVD installer? TIA.
I'm now downloading another DVD iso image.
Remark: The PC was previous running Slackware-11.0 (32bit) without problem.
B.R.
satimis
Make sure that lilo is installed to your MBR and not to a partition (eg in your /etc/lilo.conf file make sure that you have "boot=/dev/hda" rather than "boot=/dev/hda1" and then run lilo again). Also check that your root partition is marked as bootable (eg in cfdisk) and possibly also in your BIOS.
0 
Hi 3Dave,
Tks for your advice.I have my problem solved as follows:-
- rebooted PC with slamd64-11.0-installer
- saved LILO on floppy
- booted floppy to start slamd64-11.0
- edited /etc/lilo.conf
- changed "/dev/fd0" to "/dev/sda"
- ran "lilo -C /etc/lilo.conf
- removed the floppy and rebooted PC to runlevel 3
- Ran "startx". KDE startedslamd64-11.0 is now working.
How can the problem came is a mystery. The only suspected cause is I'm running SATA HD on the PC.
B.R.
satimis
0
I've often installed slack on SCSI (/dev/sda) and think that by default it assumes IDE (/dev/hda) so it's always worth double checking the config during setup, from memory I think it gives you a chance to view/edit the lilo.conf to be written.
0
Hi 3Dave,
I'm running SATA HD on this box. I read documnent mentioning its problem on Slackware/slamd64.
I made 2 installations both coming to the same problem, unable to boot on reboot after installation completed.
I booted the PC with the installer. Highlighted "Configure Reconfig ...". On clicking [Enter] it jumped to 'Help". This is quite strange to me, not being allowed to rerun "Configure ...."
I installed Slackware-11.0 on this box before slamd64-11.0. It did not come to uable to reboot problem.
B.R.
satimis
0
Are you able to install, then before rebooting or boot off either the installation CD or something like knoppix or toms rtbt, mount the root partition, chroot to it and then run liloconfig or run pkgtool and select Setup to re-run the slackware installation scripts, one of which includes liloconfig?
The chroot steps might be something like:
# mkdir /mnt/slack
# mount /dev/sda1 /mnt/slack
# mount --bind /proc /mnt/slack/proc
# mount --bind /dev /mnt/slack/dev
# chroot /mnt/slack /bin/bash
0
Hi 3Dave,
Referring to my recent new posting slamd64-11.0 failing to boot, I need to run "installpkg" on chroot environment to reinstall "sysvinit" and "tcpip". Will following steps be correct to create chroot environment for slamd64-11.0
# mkdir /mnt/slamd64
# mount /dev/sda2 /mnt/slamd64
(/dev/sda2 /root partition)
# mount --bind /proc /mnt/slamd64/proc
# mount --bind /dev /mnt/slamd64/dev
# chroot /mnt/slamd64 /bin/bashAfterwards can I start Firefox to download
"sysvinit" in mirror slackware/a
"tcpip" in mirror slackware/nand run
# installpkg /path/to/sysvinit
# installpkg /path/to/tcpip
overwriting the running/old packages.TIA
B.R.
satimis
0
Yep...that should work.
FYI the following two commands are valid too:
# mount -t proc none /mnt/slamd64/proc
# mount -o bind /dev /mnt/slamd64/dev
0
Hi 3Dave,
Failed to run chroot.
Steps performed as follows;
root@0[knoppix]# mkdir /mnt/slamd64
root@0[knoppix]# mount /dev/sda2 /mnt/slamd64
root@0[knoppix]# mount --bind /proc /mnt/slamd64/proc
root@0[knoppix]# mount --bind /dev /mnt/slamd64/dev
root@0[knoppix]# chroot /mnt/slamd64 /bin/bash
chroot: cannot run command `/bin/bash': Exec format errorPls advise. TIA
B.R.
satimis
0
Check that bash is indeed located under /mnt/slamd64/bin/ and that it is executable. Failing that it may be that by default tcsh, csh or ksh is enabled rather than bash. Instead try:
# chroot /mnt/slamd64 /bin/shI'm guessing that /dev/sda2 is indeed your root partition and not /boot or swap? If the mount proc and dev commands worked without error then it should be....
0
Hi 3Dave,
Strangely slamd64-11.0 booted to login. I did not touch anything.
While the screen hung on:
Starting Sendmail MTA daemon /usr/sbin/sendmail -L -sm -mta -bd -q25mI left the PC standing there and went to search for a 64 bit LiveCD for rescuing slamd64-11.0. I could not find it and came back to the PC. The screen booted to login.
Now slamd64-11.0 is working.
login and started X. Internet can be accessed.
On KDE desktop:
KStart --> Settings --> Internet & Network --> Network Settingsstarted "Configure - KDE Control Modules" and "Unsupported Platform-KDE Control" windows simultaneously.
On "Configure - KDE Control Modules" window, all empty entries under "Network Interfaces", "Routes", "Domain Name", "System Network" and "Profile" tags
On "Unsupported Platform-KDE Control" displaying:
Your Platform is not supportedDown on the list I can't find "slamd64-11.0". "slackware-10.0.0/10.1.0/10.2.0 were there etc.
Last time I played around here. I was not allowed to save any items of slackware-10.0.0 etc. selected. Finally it came to present situation hanging on :
Starting Sendmail MTA daemon /usr/sbin/sendmail -L -sm -mta -bd -q25mhere.
Any advice. TIA. I have no idea whether slamd64-11.0 will start again on next boot.
# ls /var/log/
Xorg.0.log apache/ cups/ faillog maillog packages/ sa/ setup/ wtmp
Xorg.0.log.old btmp debug iptraf/ messages removed_packages/ scripts/ spooler
acpid cron dmesg lastlog nfsd/ removed_scripts/ secure syslogPls advise which file holding the scrolling log at boot. Tks.
# mkdir /mnt/slamd64
# mount /dev/sda2 /mnt/slamd64
# mount -t proc non /mnt/slamd64/proc
# mount -o bind /dev /mnt/slamd64/dev
# chroot /mnt/slamd64 /bin/bash
chroot: cannot run command `/bin/bash': Exec format error
# chroot /mnt/slamd64 /bin/sh
chroot: cannot run command `/bin/sh': Exec format error# ls -l /mnt/slamd64/bin/bash
-rwxr-xr-x 1 root root 819784 May 22 2006 /mnt/slamd64/bin/bashI think I have to run 64 bit LiveCD to do the job?
B.R.
satimis
0
"...I think I have to run 64 bit LiveCD to do the job..."
Yes, trying to run 64bit apps (eg bash) with a 32bit CD is probably why you are getting Exec format errors.I am not familiar with the KDE network settings and Control Modules you mention as they don't appear on my gentoo install. It sounds as though sendmail is either not configured correctly or if it is can't get access to some server somewhere. Hence it hangs until it times out. I suggest you stop sendmail from starting at boot by removing the execute permission from /etc/rc.d/rc.sendmail:
# chmod -x /etc/rc.d/rc.sendmail
That should at least mean you can boot quicker.You say that you have network/internet access OK?
0
Hi 3Dave,
I made a mistake. slamd64-11.0 was not fail to boot just haning a while (3~4 min) on
"Starting Sendmail MTA daemon /usr/sbin/sendmail -L -sm -mta -bd -q25m"Then continue on;
"Starting Sendmail MSP queue runner: /usr/sbin/senmail -L Sm-mcp-queue -Ac -q25m"
hanging another 2~3 minutes to login prompt.I don't know why it hung there so long.
Can I add debugging 'echo' on /etc/rc.d/rc.M after sendmail to check the problem. If YES please advise how to make it
# cat /etc/rc.d/rc.M | grep sendmail
# authentication services for sendmail:
# Start the sendmail daemon:
if [ -x /etc/rc.d/rc.sendmail ]; then
. /etc/rc.d/rc.sendmail start
* end *
What shall I add. TIATks.
sendmail is default MTA of slamd64-11.0 I'll learn it. What is getmail for. It is also running on this box.# which getmail
/usr/bin/getmailB.R.
satimis
0  |
 Remote Desktop Fedora?
|
gateway solo 9300
|
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
