Bug#394744: Package: installation-reports
reopen 394744 retitle 394744 provide a hint when unsupport hardware is detected severity 394744 wishlist thanks Op 23-10-2006 om 07:08 schreef Andreas Tille: The additional hint I wanted to give is that there should be some easily detectable information for newbies if something like that happens. I would think the following would be helpful (for instance in the case of a not detected NIC): Your computer contains a network card `output of lspci | grep Ethernet` This is card seems not to be supported by the current installation kernel of Debian GNU/Linux. (Don't know whether this is a reasonable guess because there might be other types of failure.) You might try to ask your favourite Search Engine to browse the internet for Debian Linux `string from above` or ask debian-user for further help. The problem is that I wanted to demonstrate a newbie how easy it is to install Debian on his fresh box, but failed and there was no clue given what to do next. I do not want to blame the installer for failing where it has no chance to success but we could try to give at least some information how to proceed now. I admit I have not read the installation manual and perhaps some information is given there. But even then my suggestion above should be turned into: Please read installation manual topic Trouble shooting (or whatever). Kind regards Andreas. Your wish is now again in the bug tracking system. Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394744: Package: installation-reports
Op 22-10-2006 om 21:46 schreef Andreas Tille: snip/ The consequence is IMHO that we should give some advise for people like me that are beaten by hardware that is not supported by vanilla kernel. [1] I'm completely lost with this machine and hope for a slight hint what to do next because all Google entries for compiling the driver point to some SuSE sites and it seems to work for these guys but not for me, because the make process stops like this: # make modules snip/ make[2]: *** No rule to make target `modules'. Stop. I followed some other hints to copy the contents of the tar file directly into the kernel tree but failed as well. Any hint that would help here? AFAIK is the package module-assistant made for such things. This is it's (long) description: Description: tool to make module package creation easier The module-assistant tool helps users and maintainers with managing external kernel modules packaged for Debian. It can do: . - automated preparation of build environment for modules compilation (eg. automatical detection and installation of required kernel source/headers) - automated module source downloads - configuring and keeping track of external and localy built modules packages - semi-automated multiple builds for multiple kernel versions . It also contains some framework to be used by the build-scripts in the accompanying modules-source packages in Debian. HtH GSt [1] Ask it in the computer shop or in the next computer shop. The largest profit for support in the kernel is for the hardware manufactors. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394744: Package: installation-reports
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso from Oct 17, 2006 Date: Oct 20, 2006 Machine: PC (assembled at local dealer) Processor: AMD Sempron AM2 3000+ 256kB (FSB 1600 MHz) Memory: 1024MB DDR2-533 CL4 Partitions: two partitions of the wrong OS (sorry my son buyed it ;-)) and /, /usr, /var, /home for Linux Output of lspci and lspci -n: lspci: 00:00.0 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:00.5 PIC: VIA Technologies, Inc. VT3351 I/O APIC Interrupt Controller 00:00.7 Host bridge: VIA Technologies, Inc. VT3351 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. [K8T890 North / VT8237 South] PCI Bridge 00:02.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:03.0 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:03.1 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:03.2 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:03.3 PCI bridge: VIA Technologies, Inc. K8T890 PCI to PCI Bridge Controller 00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev a0) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev a0) 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev a0) 00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev a0) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge 00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller 00:13.0 PCI bridge: VIA Technologies, Inc. VT8237A Host Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 02:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller (rev 10) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) 06:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02) 07:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 71c6 07:00.1 Display controller: ATI Technologies Inc Unknown device 71e6 lspci -n 00:00.0 0600: 1106:0351 00:00.1 0600: 1106:1351 00:00.2 0600: 1106:2351 00:00.3 0600: 1106:3351 00:00.4 0600: 1106:4351 00:00.5 0800: 1106:5351 00:00.7 0600: 1106:7351 00:01.0 0604: 1106:b999 00:02.0 0604: 1106:a238 00:03.0 0604: 1106:c238 00:03.1 0604: 1106:d238 00:03.2 0604: 1106:e238 00:03.3 0604: 1106:f238 00:0f.0 0101: 1106:0591 (rev 80) 00:0f.1 0101: 1106:0571 (rev 07) 00:10.0 0c03: 1106:3038 (rev a0) 00:10.1 0c03: 1106:3038 (rev a0) 00:10.2 0c03: 1106:3038 (rev a0) 00:10.3 0c03: 1106:3038 (rev a0) 00:10.4 0c03: 1106:3104 (rev 86) 00:11.0 0601: 1106:3337 00:11.7 0600: 1106:287e 00:13.0 0604: 1106:337b 00:18.0 0600: 1022:1100 00:18.1 0600: 1022:1101 00:18.2 0600: 1022:1102 00:18.3 0600: 1022:1103 02:01.0 0403: 1106:3288 (rev 10) 05:00.0 0200: 10ec:8168 (rev 01) 06:00.0 0101: 197b:2363 (rev 02) 07:00.0 0300: 1002:71c6 07:00.1 0380: 1002:71e6 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [E] Config network: [ ] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: Well, the kernel does not contain the driver for 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) Subsystem: ASRock Incorporation Unknown device 8168 Flags: bus master, fast devsel, latency 0, IRQ 10 I/O ports at c800 [size=256] Memory at fe9ff000 (64-bit, non-prefetchable) [size=4K] Expansion ROM at fe9c [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] Message Signalled
Bug#394744: Package: installation-reports
2006/10/22, Frans Pop [EMAIL PROTECTED]: I'm going to have to close this installation report as a successful install because AFAICT the installer did everything right. If a device is not supported in the kernel, there is very little we can do. Sure. My intention was to announce a success so far as you can do. The additional hint I wanted to give is that there should be some easily detectable information for newbies if something like that happens. I would think the following would be helpful (for instance in the case of a not detected NIC): Your computer contains a network card `output of lspci | grep Ethernet` This is card seems not to be supported by the current installation kernel of Debian GNU/Linux. (Don't know whether this is a reasonable guess because there might be other types of failure.) You might try to ask your favourite Search Engine to browse the internet for Debian Linux `string from above` or ask debian-user for further help. The problem is that I wanted to demonstrate a newbie how easy it is to install Debian on his fresh box, but failed and there was no clue given what to do next. I do not want to blame the installer for failing where it has no chance to success but we could try to give at least some information how to proceed now. I admit I have not read the installation manual and perhaps some information is given there. But even then my suggestion above should be turned into: Please read installation manual topic Trouble shooting (or whatever). Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
