WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Tiny core linux connect problem  (Read 1153 times)

Offline alperen76

  • Newbie
  • *
  • Posts: 4
Tiny core linux connect problem
« on: February 07, 2022, 11:08:59 PM »
İ want connect internet (20 megabyte tinycore current version) but not connecting
İmages link: newbielink:https://resimlink.com/ah65zNG [nonactive]
« Last Edit: February 07, 2022, 11:27:06 PM by alperen76 »

Offline NewUser

  • Full Member
  • ***
  • Posts: 146
Re: Tiny core linux connect problem
« Reply #1 on: February 07, 2022, 11:24:38 PM »
connecting via an Ethernet cable or wireless?

Offline alperen76

  • Newbie
  • *
  • Posts: 4
Re: Tiny core linux connect problem
« Reply #2 on: February 07, 2022, 11:28:13 PM »
ethernet cable

Offline NewUser

  • Full Member
  • ***
  • Posts: 146
Re: Tiny core linux connect problem
« Reply #3 on: February 07, 2022, 11:34:53 PM »
TCL should connect automagically. Show me what ipconfig returns.

Offline alperen76

  • Newbie
  • *
  • Posts: 4
Re: Tiny core linux connect problem
« Reply #4 on: February 07, 2022, 11:52:19 PM »
İmages

Offline alperen76

  • Newbie
  • *
  • Posts: 4
Re: Tiny core linux connect problem
« Reply #5 on: February 08, 2022, 12:39:51 AM »
Someone help?

Offline vinceASPECT

  • Hero Member
  • *****
  • Posts: 615
Re: Tiny core linux connect problem
« Reply #6 on: February 08, 2022, 02:58:40 AM »
HEllo

Yes,

also experienced the Repo being down.

Try  again.

thx.
C
« Last Edit: February 08, 2022, 07:11:26 AM by Rich »

Offline polikuo

  • Hero Member
  • *****
  • Posts: 669
Re: Tiny core linux connect problem
« Reply #7 on: February 08, 2022, 03:01:13 AM »
The ethernet card is not detected.
It has nothing to do with the repo.
What's your dmesg output ?
Code: [Select]
dmesg > dmesg.txt

Offline CentralWare

  • Administrator
  • Sr. Member
  • *****
  • Posts: 404
Re: Tiny core linux connect problem
« Reply #8 on: February 08, 2022, 06:55:41 PM »
@alperen76:
Code: [Select]
ifconfig -a to see if ethernet is simply "down" or if core needs a driver installed for your ethernet card.
If eth0 (for example) is shown with the -a switch, take out nodhcp from the boot codes or launch /etc/init.d/dhcp.sh manually.
If it's a driver issue, you'll want to find a way to get the extension pciutils.tcz onto your boot drive which can help identify your ethernet hardware (unless anyone knows of a method TC already has in its core image to identify make/model?)


Offline CNK

  • Jr. Member
  • **
  • Posts: 92
Re: Tiny core linux connect problem
« Reply #9 on: February 09, 2022, 11:37:10 PM »
you'll want to find a way to get the extension pciutils.tcz onto your boot drive which can help identify your ethernet hardware (unless anyone knows of a method TC already has in its core image to identify make/model?)

The list of PCI device descriptions (pci.ids.gz) comes from the pciutils.tcz extension, so there isn't alternative that works as easily as lspci. However it's possible to find vendor and device IDs by looking in /sys/bus/pci/devices then look them up manually.

For example, lspci returns this for my Ethernet interface (my particular model of which doesn't work at all with the Linux driver in TC11 and TC12 and needs the r8168-KERNEL.tcz extension with the official driver):
Code: [Select]
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

Without using lspci, I can find the vendor and device IDs as follows:
Code: [Select]
$ cat /sys/bus/pci/devices/0000:01:00.0/vendor /sys/bus/pci/devices/0000:01:00.0/device
0x10ec
0x8168

Now I can look up the vendor ID at the web interface to the PCI ID Repository which pci.ids.gz is sourced from (also more up to date than the 2017 copy in the pciutils.tcz extension). Entering "10ec" into the box at the bottom of the page and pressing "Jump" brings up the Realtek vendor section, then entering "8168" and pressing "Jump" at the bottom of that page brings up the device page, matching what lspci reported.

/sys/bus/pci/devices/0000:01:00.0/revision (0x0c) also shows that it is actually model 8168G, based on the comments on that device page.

Note that you'll have to do this for all the devices in /sys/bus/pci/devices, which might be a bit laborious. I think the Ethernet interface is most likely to be towards the end of the PCI IDs listed though, so start from the end of the list and work back.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 13941
Re: Tiny core linux connect problem
« Reply #10 on: February 10, 2022, 12:55:03 AM »
If you load curl and gzip, you can use "sudo update-pciids" to update to the latest pci-ids