Release Candidates :: DSL-2.0RC1



Probably the biggest reason to have a public beta test is because John and I do no have access to every type of hardware to test on.
All I can say is that this kernel and modules was built using the knoppix .config file.

So when reporting problems with unsupported cards etc, that worked in 1.5 and earlier please try to say which module(s) worked in the past.

Use system stats modules tab or type the command lsmod
Then look for the module in /lib/modules/2.4.31 directory
If the module(s) is there try insmod command. Some modules may not be there in which case the kernel sources are available to create your custom module. Then use the boot option modules=hdaX which will insmod extra custom modules.

Let us know what you find.
2 things:

The madwifi drivers are not there anymore. I was hoping for a new version so it would recognize my card (D-Link DWL-650, rev.B5, Atheros based). I was hoping to avoid having to try to compile, since I'm not very linux-savvy...

Also, is there any way to dual-boot with 2 versions of DSL with grub in a frugal install? I tried but even though I specified the partition with the root (hd0,3) command and boot option root=/dev/hda4, it would invariably find the /dev/hda3 partition first and take this one instead. ???
I have intel 536 pci internal software modem(widely use by dell) and DSL does detect whe I run 'lspci' but dialup config does't show any link  to the nodem. Same with USR 5610B internal modem. The 'lsmod' shows no driver loaded. Anybody knows how to make this work.?

can you add driver for Intel 536 or 537ep internal modem , better USR 5610B pci internal modem with DSL 2.0 final. RC1 does't load drivers when it detect the modem.

Posts merged by SaidinUnleashed
Quote (_cd @ Nov. 04 2005,06:50)
Also, is there any way to dual-boot with 2 versions of DSL with grub in a frugal install? I tried but even though I specified the partition with the root (hd0,3) command and boot option root=/dev/hda4, it would invariably find the /dev/hda3 partition first and take this one instead. ???

You need to have a boot option of fromhd=/dev/hda4 to make this work. Knoppix wants to boot the first KNOPPIX image it sees so the fromhd command will point it to where you want to boot.

Chris
In reference to my previous post about network interface problems, I can only say :  "DOOOOH!"

It seems that my only hardware problem was a "short in the headset"!  I botched my frugal install upgrade.
Next Page...
original here.