I've been running Slack for >10 years and never had a problem that I couldn't resolve - till now.

I have been running the 10.0 release with the 2.6.x kernel (no problems) since it was released and finally decided to upgrade to 10.2.

I'm running on an ABIT NF7-s mobo with 1G of ram and an NVidia video card. SATA is disabled, and I am all SCSI (except the DVD burner) with 2 SCSI cards. ALL drives are on an ACARD SCSI3, and I have a BusLogic SCSI2 running my scanner and other SCSI devices.

Problems ---

Attempt to install with the test26.s kernel starts out fine. Ten or so packages install and then the system errors , saying that it cannot find a package. From that point on, NO packages are found and the hard drive access led is ON. It appears that the 'mount' has been lost???

The install of 2.4 kernel with scsi2.s works just fine.
- Reboot the system and start KDE - move the mouse or wait for a relatively short period of time and the system hangs.
- Reboot the system and DON'T start KDE - wait a relatively long time and the system hangs.
In both cases, the drive access led may end up ON or OFF, and the network connection is also frozen (i.e. I cannot access from another machine).

There is nothing obvious (to me anyway) in any of the logs.

Has anyone else seen this happen???

RonS

Welcome to LQ!

Originally posted by RonS1938
Did you upgrade your system? Or is this a fresh install?

This has happened to me when my install CD was bad.

Did you verify the md5sum of your ISO image?

Did you/can you verify the CD you burned?

I'm assuming this is a fresh install of 10.2 with scsi2.s and not
a kernel install after a system upgrade.

Just need a little clarification if you please.

Fresh install due to stupidity - I thought that I was wiping an old Slack 8.0 install and wiped my 10.0 configuration instead (I never back-up things that can be reinstalled). I currently have the 2.4.x kernel from the 10.0 release currently installed - without the system hang.

The CD's are O.K., I have installed the 2.6.13 kernel on my HP Pavilion zv6000 laptop from the same CD's. The laptop has an IDE drive of course, and the other difference is an Athlon64 on the laptop.

I'm still trying to get the 'wireless' working on the laptop, hence I'm using the WinXP (barf) boot to get on the net with the laptop.

RonS

Glad you got it fixed.

Perhaps Alien Bob's Networking articles on his Wiki can help you get wireless working.

It's not fixed, I still don't have the 2.6.13 kernel running on my primary machine.
RonS

Now, is your DVD drive IDE then? I've had the test26.s kernel give me some weird results, but worked fine on my laptop.

BTW, what wireless card are you trying to use ? It may even be worth your while instaling the 2.4 kernel, then compiling the 2.6.17 kernel, because it supports a great amount of WiFi and CDMA cards functionality.

I'm refering to 2 systems -

1) A tower with the Abit mobo that won't install with the test26.s kernel and 'hangs' at some point after bootup with the 2.4.31 kernel (yes it has an IDE DVD, but SCSI everything else - 3 hd's on an Acard SCSI3 controller, plus scanner, tape, and Syquest removable on a BusLogic controller). This system was running 2.6.7 since Slack 10.0 was released with no problems.

2) An HP Pavilion zv6000 laptop with a built in 'Broadcom 43xx' wireless. This one installed 2.6.13 with the test26.s kernel with no problems from the same disk set (i.e. the disk set is likely O.K.). I still cannot get the Broadcom to connect - this is dual boot with WinXP Home, where the wireless indicates an 'exellent' connection.

RonS

For 1) -- What you've posted is a wee bit confusing to me. Forgive me, and let's see if we can get it straight.

I assume you previously had Slackware-10.0 running on that system with one of the scsi kernels. That release had 2.4.26 as the default kernel. You also installed 2.6.13 from /testing and it ran fine.

Now you've installed Slackware-10.2, running 2.4.31, which is the 10.2 default kernel. But it hangs after you start KDE fairly quickly. If you don't start KDE, it hangs but takes longer.

This sounds like it could be hardware problems. What have you checked?

You also tried to install Slackware-10.2 with the test26.s kernel, but it failed to install all the packages. That has happened to me only with a bad CD. I'd still check the md5sums against Slackware's.


2) That driver has been in the Linux kernel since 2.6.17. You can either keep the kernel you have and use ndiswrapper to get that Broadcom working, or you can install a 2.6.17 > kernel. If you want to install the new kernel, it's quite easy to use the .config from your present 2.6.13 kernel and build a new kernel. Just a few steps.

If you want to use ndiswrapper and the Windows driver for that card, then look at Alien Bob's networking articles I referenced earlier.

One more attempt to clarify -
I have 1 copy of the Slack 10.2 distribution
I have multiple computers

-one of my desktops has been runing Slack 10.0 2.6.7 kernel flawlessly since it was released (Abit NF7-S mobo, all scsi drives on a Acard controller)
-attempt to upgrade with 10.2 2.6.13 kernel using test26.s seems to cause a disconnect of the scsi hard drive after several packages were successfully installed
-attempt to install 10.2 2.4.31 kernel using scsi2.s was 'successful', but the system will not run for a sustained time
-NOTE- The system seems to run forever (24 hours +) if I just let either the test26.s or scsi2.s kernel boot without doing an install
-I have now installed the 10.0 2.4.26 kernel to get this system back on line, and have not had the time to try to compile the 2.6.13 kernel to isolate the problem

-the same 10.2 disk set was successfully installed and running on my HP Pavilion zv6000 laptop using the test26.s kernel. This install plus the valid checksums should indicate that the disk set is O.K.

Separate problem ---
-the zv6000 has a built in Broadcom 46xx wireless controller that I have not been able to get to connect. I have tried everything that I can find on the problem. The info that I have found about the 2.6.17 kernel driver seems to indicate that the 46xx device is NOT supported. (I've downloaded the driver and it fails to function with my device.) The ndiswrapper solution seems to be happy loading the WinXP driver, I cannot find ANY error reports. I think that I have tried every suggestion on Alien Bob's site, including the driver that he has available - I have also downloaded wifi-radar. In WinXP the system finds 3 local access points (including mine), but in Linux it finds none - but someday...

RonS