Kiosk 3.1 can’t find network (wired) on HP Thin Client t510 (http://h20195.www2.hp.com/v2/GetDocumen ... c=ca&lc=en). That’s all I can say since I haven’t access to terminal via ssh.
Original HP system uses tg3 for Netlink Broadcom BCM57780 Gigabyte Ethernet NIC.
gmc
no network. kernel driver tg3 is needed
- fanthom
- Moderator Team
- Posts: 5618
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: no network. kernel driver tg3 is needed
tg3 driver is included by default in kiosk:
any chance to boot any other linux than kiosk on this PC and provide output of 'lspci -knn' command?
this way i could identify the chipset.
thanks
Code: Select all
grep tg3.ko lib/modules/3.12.20-porteus-kiosk/modules.dep
kernel/drivers/net/ethernet/broadcom/tg3.ko: kernel/drivers/ptp/ptp.ko kernel/drivers/pps/pps_core.ko kernel/drivers/net/phy/libphy.ko kernel/drivers/hwmon/hwmon.ko
this way i could identify the chipset.
thanks
Please add [Solved] to your thread title if the solution was found.
Re: no network. kernel driver tg3 is needed
00:00.0 Host bridge [0600]: VIA Technologies, Inc. Device [1106:0410] (rev 80)
Subsystem: VIA Technologies, Inc. Device [1106:0410]
00:00.1 Host bridge [0600]: VIA Technologies, Inc. Device [1106:1410]
Subsystem: VIA Technologies, Inc. Device [1106:1410]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. Device [1106:2410]
Subsystem: VIA Technologies, Inc. Device [1106:2410]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. Device [1106:3410]
Subsystem: VIA Technologies, Inc. Device [1106:3410]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. Device [1106:4410]
Subsystem: VIA Technologies, Inc. Device [1106:4410]
00:00.5 Host bridge [0600]: VIA Technologies, Inc. Device [1106:5410]
Subsystem: VIA Technologies, Inc. Device [1106:5410]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. Device [1106:6410]
Subsystem: VIA Technologies, Inc. Device [1106:6410]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. Device [1106:7410]
Subsystem: VIA Technologies, Inc. Device [1106:7410]
00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. Device [1106:7122]
Subsystem: VIA Technologies, Inc. Device [1106:7122]
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:a410]
Kernel driver in use: pcieport
00:03.1 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:b410]
Kernel driver in use: pcieport
00:03.2 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:c410]
Kernel driver in use: pcieport
00:03.3 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:d410]
Kernel driver in use: pcieport
00:03.4 Host bridge [0600]: VIA Technologies, Inc. Device [1106:e410]
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. Device [1106:9001]
Subsystem: VIA Technologies, Inc. Device [1106:9001]
Kernel driver in use: pata_via
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Kernel driver in use: uhci_hcd
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Kernel driver in use: uhci_hcd
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Kernel driver in use: uhci_hcd
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Kernel driver in use: uhci_hcd
00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90)
Subsystem: VIA Technologies, Inc. USB 2.0 [1106:3104]
Kernel driver in use: ehci-pci
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. Device [1106:8410]
Subsystem: VIA Technologies, Inc. Device [1106:8410]
Kernel modules: i2c-viapro
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 South-North Module Interface Control [1106:a353]
Subsystem: VIA Technologies, Inc. VX800/VX820 South-North Module Interface Control [1106:a353]
00:13.0 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:b353]
05:00.0 Ethernet controller [0200]: Broadcom Corporation Device [14e4:1692] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:9692]
Kernel driver in use: tg3
Kernel modules: tg3
thank you,
gmc
Subsystem: VIA Technologies, Inc. Device [1106:0410]
00:00.1 Host bridge [0600]: VIA Technologies, Inc. Device [1106:1410]
Subsystem: VIA Technologies, Inc. Device [1106:1410]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. Device [1106:2410]
Subsystem: VIA Technologies, Inc. Device [1106:2410]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. Device [1106:3410]
Subsystem: VIA Technologies, Inc. Device [1106:3410]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. Device [1106:4410]
Subsystem: VIA Technologies, Inc. Device [1106:4410]
00:00.5 Host bridge [0600]: VIA Technologies, Inc. Device [1106:5410]
Subsystem: VIA Technologies, Inc. Device [1106:5410]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. Device [1106:6410]
Subsystem: VIA Technologies, Inc. Device [1106:6410]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. Device [1106:7410]
Subsystem: VIA Technologies, Inc. Device [1106:7410]
00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. Device [1106:7122]
Subsystem: VIA Technologies, Inc. Device [1106:7122]
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:a410]
Kernel driver in use: pcieport
00:03.1 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:b410]
Kernel driver in use: pcieport
00:03.2 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:c410]
Kernel driver in use: pcieport
00:03.3 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:d410]
Kernel driver in use: pcieport
00:03.4 Host bridge [0600]: VIA Technologies, Inc. Device [1106:e410]
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. Device [1106:9001]
Subsystem: VIA Technologies, Inc. Device [1106:9001]
Kernel driver in use: pata_via
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Kernel driver in use: uhci_hcd
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Kernel driver in use: uhci_hcd
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Kernel driver in use: uhci_hcd
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
Kernel driver in use: uhci_hcd
00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90)
Subsystem: VIA Technologies, Inc. USB 2.0 [1106:3104]
Kernel driver in use: ehci-pci
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. Device [1106:8410]
Subsystem: VIA Technologies, Inc. Device [1106:8410]
Kernel modules: i2c-viapro
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 South-North Module Interface Control [1106:a353]
Subsystem: VIA Technologies, Inc. VX800/VX820 South-North Module Interface Control [1106:a353]
00:13.0 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:b353]
05:00.0 Ethernet controller [0200]: Broadcom Corporation Device [14e4:1692] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:9692]
Kernel driver in use: tg3
Kernel modules: tg3
thank you,
gmc
- fanthom
- Moderator Team
- Posts: 5618
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: no network. kernel driver tg3 is needed
please try this trick in /etc/rc.d/rc.local:
https://wiki.archlinux.org/index.php/Ne ... m_BCM57780
you may have to killall and start dhcpcd once eth0 becomes available or repeat manual network configuration.
https://wiki.archlinux.org/index.php/Ne ... m_BCM57780
you may have to killall and start dhcpcd once eth0 becomes available or repeat manual network configuration.
Please add [Solved] to your thread title if the solution was found.
Re: no network. kernel driver tg3 is needed
Hello,
Thank you very much for this hint. I'm going to test it although there is no warranty that this method will work on my hardware. It seems to me, that tests performed by creating new Kiosk-ISO file for every single trial could be too laborious. Simpler way seems to be dynamic testing via ssh access. In this case however, first I have to buy usb-WiFi card and to install AP. Of course if it's going to work .
From the above point of view maybe it is worth to consider adding in future the option of access to local system console in Kiosk wizard. Kiosk is so "lightweight" that even many much more additions could not to change it significantly. But it could help in many cases during installation on the new or not standard hardware.
thanks
gmc
Thank you very much for this hint. I'm going to test it although there is no warranty that this method will work on my hardware. It seems to me, that tests performed by creating new Kiosk-ISO file for every single trial could be too laborious. Simpler way seems to be dynamic testing via ssh access. In this case however, first I have to buy usb-WiFi card and to install AP. Of course if it's going to work .
From the above point of view maybe it is worth to consider adding in future the option of access to local system console in Kiosk wizard. Kiosk is so "lightweight" that even many much more additions could not to change it significantly. But it could help in many cases during installation on the new or not standard hardware.
thanks
gmc
- fanthom
- Moderator Team
- Posts: 5618
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: no network. kernel driver tg3 is needed
this wont be necessary as i have covered pretty much everything (VT switching included) in the Kiosk FAQ:From the above point of view maybe it is worth to consider adding in future the option of access to local system console in Kiosk wizard.
http://porteus-kiosk.org/faq.html
please follow it.
Please add [Solved] to your thread title if the solution was found.
Re: no network. kernel driver tg3 is needed
Hello
Thanks again. In fact, I'm sorry, I'm not too attentive reader of FAQ. I'll try to improve.
gmc
Thanks again. In fact, I'm sorry, I'm not too attentive reader of FAQ. I'll try to improve.
gmc