LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Getting the Tulip driver working again (https://www.linuxquestions.org/questions/linux-hardware-18/getting-the-tulip-driver-working-again-71100/)

jim64 07-08-2003 06:19 PM

Getting the Tulip driver working again
 
I need some assistence in getting my network card working. I know it uses the tulip driver but i am not sure how to get it installed. I checked the instructions on linksys.com and they were for kernel 2.2 on slackware 3.3, I am using 2.4.21 and slackware 9 (just a bit out of date). So any ways the slackware install discovered my card and configured the correct driver module to get it to work (which is tulip.o). However it did not get the sound card drivers right and i had no sound. So to fix this i had to recompile my kernel but slackware does not include the kernel source so i had to download kernel 2.4.21 from kernel.org. I compiled it and so on and sound worked but then network did not. I noticed that in the new 2.4.21 kernel source there is the sources for the tulip driver. How do i go about getting this tulip source to compile when i compile the kernel. I used "make menuconfig" to configure what i wanted compiled into the kernel but i never found any thing about the tulip driver or any thing close to my linksys LNE100tx card.
Also this may be 2 much to ask but before i compiled the new kernel i had a much smaller font or a larger resolution in the command line. It also had colors and a cute penguin at the top of my screen. How do i get this back?
I really miss that penguin...
my aim is p2prat
Thanks

finegan 07-09-2003 08:04 PM

The tulip card is a DEC chipset:

Network device support ---> Ethernet (10 or 100Mbit) ---> [*] EISA, VLB, PCI and on board controllers „_ „_
„_ „_< > AMD PCnet32 PCI support „_ „_
„_ „_< > AMD 8111 (new PCI lance) support „_ „_
„_ „_< > Adaptec Starfire/DuraLAN support „_ „_
„_ „_<M > DECchip Tulip (dc21x4x) PCI support „_ „_
„_ „_<M > Generic DECchip & DIGITAL EtherWORKS PCI/EISA

That's modular for both new and old tulip.

Also, Slackware has the kernel source, but online, Patrick just dropped it from the install CD for space reasons, at any given slackware mirror: slackware-9.0/slackware/k/

Also you will find there a patched 2.4.21 in: slackware-9.0/patches/packages/

The font and penguin disapeared for not compiling in framebuffering support. At the top make certain to add:

Code maturity level options --->[*] Prompt for development and/or incomplete code/drivers

Then under: Console drivers --->[*] Video mode selection support
Frame-buffer support ---> [*] VESA VGA graphics console
and...[*] Advanced low level driver options
and for the low level, just leave the defaults it brings up, 8,16,24,32....

Cheers,

Finegan

jim64 07-10-2003 01:09 PM

I always have problems when i compile a kernel from source that i have prevously used and i have to use the same but new source. In other words i am asking; is there something that i need to do before i compile for the second or third time from the same source. Like run "make clean" or any thing.
Thanks a ton for the help.

finegan 07-10-2003 02:52 PM

I always recycle source, heck sometimes I'm lazy and don't even do that...

make clean
make menuconfig
make bzImage
etc....

kernel.org source is the only way I've ever got anything to compile right, except for the slackware source... which is almost always just kernel.org source and you have to apply the slackware specific patches by hand.

Cheers,

Finegan

jim64 07-10-2003 04:57 PM

Ok i did that but when i compiled it or sorta it went well for a wile then threw this at me.
cd /lib/modules/2.4.21; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.21; fi
depmod: *** Unresolved symbols in /lib/modules/2.4.21/kernel/drivers/media/video/bttv.o
depmod: i2c_bit_del_bus_Rsmp_524ae534
depmod: i2c_master_send_Rsmp_1313dc33
depmod: i2c_bit_add_bus_Rsmp_baecbb4e
depmod: i2c_master_recv_Rsmp_f1041854
depmod: *** Unresolved symbols in /lib/modules/2.4.21/kernel/drivers/media/video/msp3400.o
depmod: i2c_master_send_Rsmp_1313dc33
depmod: i2c_probe_Rsmp_59b95524
depmod: i2c_attach_client_Rsmp_e230575f
depmod: i2c_detach_client_Rsmp_293e7552
depmod: i2c_transfer_Rsmp_da722bad
depmod: i2c_add_driver_Rsmp_6ec4580a
depmod: i2c_del_driver_Rsmp_37c75d23
depmod: *** Unresolved symbols in /lib/modules/2.4.21/kernel/drivers/media/video/tda7432.o
depmod: i2c_master_send_Rsmp_1313dc33
depmod: i2c_probe_Rsmp_59b95524
depmod: i2c_attach_client_Rsmp_e230575f
depmod: i2c_detach_client_Rsmp_293e7552
depmod: i2c_add_driver_Rsmp_6ec4580a
depmod: i2c_del_driver_Rsmp_37c75d23
depmod: *** Unresolved symbols in /lib/modules/2.4.21/kernel/drivers/media/video/tda9875.o
depmod: i2c_master_send_Rsmp_1313dc33
depmod: i2c_probe_Rsmp_59b95524
depmod: i2c_attach_client_Rsmp_e230575f
depmod: i2c_detach_client_Rsmp_293e7552
depmod: i2c_transfer_Rsmp_da722bad
depmod: i2c_add_driver_Rsmp_6ec4580a
depmod: i2c_del_driver_Rsmp_37c75d23
depmod: *** Unresolved symbols in /lib/modules/2.4.21/kernel/drivers/media/video/tda9887.o
depmod: i2c_master_send_Rsmp_1313dc33
depmod: i2c_probe_Rsmp_59b95524
depmod: i2c_attach_client_Rsmp_e230575f
depmod: i2c_detach_client_Rsmp_293e7552
depmod: i2c_add_driver_Rsmp_6ec4580a
depmod: i2c_del_driver_Rsmp_37c75d23
depmod: *** Unresolved symbols in /lib/modules/2.4.21/kernel/drivers/media/video/tuner.o
depmod: i2c_master_send_Rsmp_1313dc33
depmod: i2c_probe_Rsmp_59b95524
depmod: i2c_attach_client_Rsmp_e230575f
depmod: i2c_detach_client_Rsmp_293e7552
depmod: i2c_master_recv_Rsmp_f1041854
depmod: i2c_add_driver_Rsmp_6ec4580a
depmod: i2c_del_driver_Rsmp_37c75d23
depmod: *** Unresolved symbols in /lib/modules/2.4.21/kernel/drivers/media/video/tvaudio.o
depmod: i2c_master_send_Rsmp_1313dc33
depmod: i2c_probe_Rsmp_59b95524
depmod: i2c_attach_client_Rsmp_e230575f
depmod: i2c_detach_client_Rsmp_293e7552
depmod: i2c_transfer_Rsmp_da722bad
depmod: i2c_master_recv_Rsmp_f1041854
depmod: i2c_add_driver_Rsmp_6ec4580a
depmod: i2c_del_driver_Rsmp_37c75d23
root@lester:/usr/src/linux#

So wa u ting da meen? What is an unresolved symbol anyways? The only solution that i can come up with is that it is something to do with video for linux which i need to get my bt878 card working. I never really found bt878 in the kernel configuration i only found bt848 so i enabled it to try it thinking maybe that would be what i needed.
Any sugestions?

finegan 07-10-2003 05:07 PM

You somehow enabled all the tv4l goop without adding in i2c support, its under:

Character devices ---> I2C Support, enable all of the little sub-options I guess...

Cheers,

Finegan

jim64 07-10-2003 06:34 PM

Ok i tried that no success. Let me see if i unerstand you correctly. You said that under Character devices ---> to enable I2C Support and then allso enable ALL of the options that are under it. I still do not understand something: am i correct in thinking that i should enable V4L and also BT848 to get my BT878 based tv tuner card to work.
Here is the output:
make[1]: Entering directory `/usr/src/linux-2.4.21/arch/i386/mm'
make[1]: Nothing to be done for `modules_install'.
make[1]: Leaving directory `/usr/src/linux-2.4.21/arch/i386/mm'
make -C arch/i386/lib modules_install
make[1]: Entering directory `/usr/src/linux-2.4.21/arch/i386/lib'
make[1]: Nothing to be done for `modules_install'.
make[1]: Leaving directory `/usr/src/linux-2.4.21/arch/i386/lib'
cd /lib/modules/2.4.21; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.21; fi
depmod: *** Unresolved symbols in /lib/modules/2.4.21/kernel/drivers/i2c/scx200_i2c.o
depmod: scx200_gpio_base_Rsmp_254e5667
depmod: scx200_gpio_configure_Rsmp_80c65a79
depmod: scx200_gpio_shadow_Rsmp_9272bc53
root@lester:/usr/src/linux#
Thanks :)

finegan 07-10-2003 07:19 PM

Quote:

Originally posted by jim64
am i correct in thinking that i should enable V4L and also BT848 to get my BT878 based tv tuner card to work.

From the first set of errors, kinda, yes... I'm not certain the BT848 module covers the BT878 card, if the original slack 2.4.20 kernel module made the card work... then yeah its the same one, Slack isn't adding any patches with their version of 2.4.20, at least not in the way of device drivers.

I've never actually had a video capture card, all I know is that it requires some i2c support, which ones I'm at a bit of a loss to.

As far as I can tell, you can ignore the depmod error with this one, you compiled in some i2c support for some watchdog card called with scx200 without compiling in support for the scx200 itself, who cares, you haven't got one of those. At least, it looks like that... from a grep of the kernel source that's all I can find...

Yeah, don't sweat it, if the new kernel boots, see if the BT848 will load and recognize your capture card.

Cheers,

Finegan

jim64 07-10-2003 11:51 PM

No i never really tested the card b4 i started mucking with the kernel because i did not have sound so i did not really care about the tv tuner card. Hmm... well does any one out there have any experience with this (Compiling BTTV with the kernel). I am sorta a :newbie: to forum edicate and i am not sure if its worse to start a new thread for this bttv question or make this one kinda go off topic. I guess since you (finegan) are a moderator you would know.
thanks

finegan 07-11-2003 04:26 AM

Yeah, new question, new problem, new thread, its far from a double post, especially as threads that are 2 pages in are considered rather "underway" and aren't going to get many more replies.

From a grep through the kernel source:
drivers/media/video/bt848.h:33:#ifndef PCI_DEVICE_ID_BT878
drivers/media/video/bt848.h:34:#define PCI_DEVICE_ID_BT878 0x36e
drivers/media/video/bt848.h:350:/* Bt878 register */
drivers/media/video/bt848.h:352:#define BT878_DEVCTRL 0x40
drivers/media/video/bt848.h:353:#define BT878_EN_TBFX 0x02
drivers/media/video/bt848.h:354:#define BT878_EN_VSFX 0x04

I would assumer the 878 is considered a subset of the 848 board and therefore covered under the driver.

I would do a search first on how to configure BTTV stuff though, maybe some googling, but you've almost definately got the support for it.

Cheers,

Finegan

jim64 07-11-2003 06:39 PM

Whenever i enable the options listed below compile and boot i have a black screen. I can still boot the original slackware kernel and i can also boot other kernels but i still have never been able to get the penguin back on a self compiled kernel. Any ideas?

Then under: Console drivers --->[*] Video mode selection support
Frame-buffer support ---> [*] VESA VGA graphics console
and...[*] Advanced low level driver options
and for the low level, just leave the defaults it brings up, 8,16,24,32....

Thanks

finegan 07-12-2003 05:00 PM

Oh whoops...

sorry, the other option, compile that in:
<*> VGA 16-color graphics console

Slackware is using VGA modes, der...

Cheers,

Finegan

jim64 07-14-2003 01:03 AM

Ok almost there. Now the penquin is finally back but the really important thing is not. Its as if its a really low resolution in command line. Not that its not clear but the text is really big and i cant fit as much on the screen as i could b4 i changed kernels. Is this a setting or something else thats missing from the kernel.
Thanks so much its almost back and also thanks the tulip driver is working correctly. :)

finegan 07-14-2003 01:06 AM

As far as I know, its all the vga= line in /etc/lilo.conf, that's the only big one for me...

Cheers,

Finegan

jim64 07-14-2003 01:18 AM

Wow that was a fast reply. Ok i checked /etc/lilo.conf and it says vga = 773 which is 1024x768x256. It looks like 1024x768 when i boot the original slackware kernel but then when i boot the new kernel it looks more like 640x480. I should have probably started a new thread bc the topic has changed from the original title.
Thanks


All times are GMT -5. The time now is 11:47 AM.