SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You may be able to compile the driver as a module and then load it from the standard Slackware 13 Setup disc to install Slackware. Don't forget to create an initrd to load the module or compile the driver into the kernel that you use for booting.
An existing Slackware 13 system on some computer is required to compile the driver and create the module. You will need to compile the driver with the same kernel configuration as the kernel on the Slackware Setup CD if you want to load the module with the Setup CD.
The good news is that GRUB or LILO should work fine if the BIOS recognizes the hard disk. They do disk I/O using BIOS functions. If you have trouble getting LILO to work you may need to use GRUB. I installed GRUB using a GRUB boot disc because GRUB or LILO under Linux could not determine the correct BIOS drive ID assignments.
If you need more help I will be glad to build a driver module but I have no way to test it.
Location: so 34, hem 75, ngach 12 ngo 624, Minh Khai, Ha Noi , Viet Nam
Distribution: Slackware, slax, opensuse
Posts: 33
Rep:
are you sure that your jack is stick to you hard disk
I had met this before
I thought that the kernel had the problem
but in fact that I forgot to plug the jack
I do not intend to hijack this thread, just out of curiosity:
Erik_FL, how do you compile an external driver into the kernel?
Best regards,
Martin
Two ways that I know of are to replace an existing source file for the kernel with one that has the driver changes/additions, or patch/edit the kernel make files to include the new driver source file.
Some drivers don't provide any help for that and it's easier to just leave them as modules and use an initrd.
In this case I was thinking that the changes to support the device (if even necessary) were for an existing driver module in Linux.
I would certainly recommend exhausting the other choices such as kernel or driver options before making changes to the source files or adding third party drivers.
netpumber - You might try typing "dmesg | more" and looking for something that looks like a disk drive (e.g., "/dev/sda"). It's been a while, but I think you have to provide the device to "fdisk", not just type it by itself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.