Slitaz installer won't detect drives, while puppy-linuxs installer does

SliTaz Forum » English Support » Live and installation

Slitaz installer won't detect drives, while puppy-linuxs installer does

(4 posts) (2 voices)

Started 9 years ago by Zainka
Latest reply from Zainka
This topic is not a support question

Tags:

No tags yet.

Zainka

offline
Member

Hi

I have been strugling instaling Slitaz on a HP T5565 thin client. Slitaz simply won't find any drives attached thus gparted may not create any partitions and the installer have nothing to install Slitaz on. I gues there are some divers missing for the via chipset on these clients. Question is how may I add them so that I can install Slitaz on them. For curiousity I tried installing Puppy linux and it found the drives right away.

The chipset in T5565 is VIA VX900 Media System Processor north/south bridge unified, running on a VIA nano U3500.

I already have a t5545, fourty five that is, running an elderly variant of slitaz. The combination of these thin clients and slitaz are great and I would very much like to have the better spec'ed t5565 up and running with slitaz aswell so any help is greatly appreciated.

Posted 9 years ago #
mojo

offline
Key Master

The slitaz developers don't own your hardware.
I recall a previous post from a user being unable to install slitaz rolling 5.0 to an sd card.
I am assuming you are booting slitaz rolling/5.0 from usb flash drive and want to install to an sd card?
A driver that supports the interface adapter to the drive you boot from has to be compiled in the kernel.
The hardware must be identified so the kernel can be reconfigured with the correct driver enabled.
Post the output:
lspci -nn

Posted 9 years ago #
Zainka

offline
Member

For the moment i run from LiveCD from a usb dvd... The T5565 has a 1GB IDE FLash drive by default, and which is the drive I want to install. These flash drives shows up as regular PATA drives on most systems. In adition there is two SATA slots, one of which i have installed a 160GB drive.

Here is the output

00:00.0 Host bridge [0600]: VIA Technologies, Inc. Device [1106:0410] (rev 80)
00:00.1 Host bridge [0600]: VIA Technologies, Inc. Device [1106:1410]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. Device [1106:2410]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. Device [1106:3410]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. Device [1106:4410]
00:00.5 Host bridge [0600]: VIA Technologies, Inc. Device [1106:5410]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. Device [1106:6410]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. Device [1106:7410]
00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. Device [1106:7122]
00:01.1 Audio device [0403]: VIA Technologies, Inc. Device [1106:9170]
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:a410]
00:03.1 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:b410]
00:03.2 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:c410]
00:03.3 PCI bridge [0604]: VIA Technologies, Inc. Device [1106:d410]
00:03.4 Host bridge [0600]: VIA Technologies, Inc. Device [1106:e410]
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. Device [1106:9001]
00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.2 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.3 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0)
00:10.4 USB controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. Device [1106:8410]
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VX8xx South-North Module Interface Control [1106:a353]
00:13.0 PCI bridge [0604]: VIA Technologies, Inc. VX855/VX875 PCI to PCI Bridge [1106:b353]
00:14.0 Audio device [0403]: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller [1106:3288] (rev 20)
02:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
05:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe [14e4:1692] (rev 01)

Posted 9 years ago #
Zainka

offline
Member

Decided to go for the cooking version. It works well and have more driver options thus detecting the drives.

Could have built the kernel i guess with driver support but its a long time since I did anything like that (building Android for sonyericsson), not did I do any good, nor do I have the time. As long the cooking version behaves well i stick to that. When thinking of it I believe that I used the cooking version also when i got T5545 up'n running.

I also updated the status of this topic to "not support" so that noeone need to waste time on this i the do not want to.

Breg
Vidar

Posted 9 years ago #

RSS feed for this topic

Reply

You must log in to post.