Install debian on Acer Aspire 1 D257?
I'm installing debian on an Acer Aspire 1 D257 notebook for someone, and the installer won't recognise the hard disk. all i get from the installer is "No disk drive was detected. If you know the name of the driver needed by your disk drive, you can select it from the list." followed by a selectable list of mostly-ancient drivers, all irrelevant. i've tried the squeeze, wheezy, and sid installers (all pretty much the same, except for minor variations in the kernel*)...and tried both amd64 and i386 for each (the CPU is a 64-bit quad-core Atom N570). anyone have any ideas? lspci says: # lspci 00:00.0 Host bridge: Intel Corporation N10 Family DMI Bridge (rev 02) 00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation N10 Family Integrated Graphics Controller (rev 02) 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02) 00:1c.2 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 3 (rev 02) 00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02) 00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05) 02:00.0 Network controller: Atheros Communications Inc. Device 0032 (rev 01) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5209 (rev 01) the Intel ICH7 should be well-supported. here's the syslog from when i run the Detect Disks menu option: Feb 10 09:17:18 main-menu[4292]: INFO: Menu item 'disk-detect' selected Feb 10 09:17:19 net/hw-detect.hotplug: Detected hotpluggable network interface eth0 Feb 10 09:17:19 kernel: [ 407.101140] libata version 3.00 loaded. Feb 10 09:17:19 kernel: [ 407.116877] ahci 0000:00:1f.2: version 3.0 Feb 10 09:17:19 kernel: [ 407.116918] ahci 0000:00:1f.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17 Feb 10 09:17:19 kernel: [ 407.117004] alloc irq_desc for 28 on node -1 Feb 10 09:17:19 kernel: [ 407.117011] alloc kstat_irqs on node -1 Feb 10 09:17:19 kernel: [ 407.117038] ahci 0000:00:1f.2: irq 28 for MSI/MSI-X Feb 10 09:17:19 kernel: [ 407.117116] ahci: SSS flag set, parallel bus scan disabled Feb 10 09:17:19 kernel: [ 407.117172] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0x3 impl SATA mode Feb 10 09:17:19 kernel: [ 407.117184] ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led clo pmp pio slum part Feb 10 09:17:19 kernel: [ 407.117196] ahci 0000:00:1f.2: setting latency timer to 64 Feb 10 09:17:19 kernel: [ 407.117714] scsi0 : ahci Feb 10 09:17:19 kernel: [ 407.118134] scsi1 : ahci Feb 10 09:17:19 kernel: [ 407.118390] scsi2 : ahci Feb 10 09:17:19 kernel: [ 407.118661] scsi3 : ahci Feb 10 09:17:19 kernel: [ 407.119536] ata1: SATA max UDMA/133 abar m1024@0x56204000 port 0x56204100 irq 28 Feb 10 09:17:19 kernel: [ 407.119550] ata2: SATA max UDMA/133 abar m1024@0x56204000 port 0x56204180 irq 28 Feb 10 09:17:19 kernel: [ 407.119557] ata3: DUMMY Feb 10 09:17:19 kernel: [ 407.119562] ata4: DUMMY Feb 10 09:17:19 net/hw-detect.hotplug: Detected hotpluggable network interface lo Feb 10 09:17:19 kernel: [ 407.600033] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Feb 10 09:17:19 kernel: [ 407.601999] ACPI Warning for \_SB_.PCI0.SATA.PRT0._GTF: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) Feb 10 09:17:19 kernel: [ 407.602016] ata1.00: _GTF unexpected object type 0x1 Feb 10 09:17:19 kernel: [ 407.602351] ata1.00: ATA-8: WDC WD3200BPVT-22JJ5T0, 01.01A01, max UDMA/133 Feb 10 09:17:19 kernel: [ 407.602365] ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Feb 10 09:17:19 kernel: [ 407.604433] ata1.00: _GTF unexpected object type 0x1 Feb 10 09:17:19 kernel: [ 407.604796] ata1.00: configured for UDMA/133 Feb 10 09:17:19 kernel: [ 407.620280] scsi 0:0:0:0: Direct-Access ATA WDC WD3200BPVT-2 01.0 PQ: 0 ANSI: 5 Feb 10 09:17:19 kernel: [ 407.940034] ata2: SATA link down (SStatus 0 SControl 300) Feb 10 09:17:20 kernel: [ 407.965473] sd_mod: Unknown symbol scsi_verify_blk_ioctl Feb 10 09:17:20 kernel: [ 407.967957] sd_mod: Unknown symbol scsi_cmd_blk_ioctl Feb 10 09:17:20 hw-detect: Loading PCMCIA bridge driver module: i82365 Feb 10 09:17:20 hw-detect: FATAL: Module i82365 not found. Feb 10 09:17:21 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing those Unknown Symbol and/or the ACPI Warning lines are probably where the problem is. googling for the ACPI warning got me a page that suggested adding "acpi_apic_instance=2" to the kernel cmd line, but that made no difference. I'm beginning to think i'm going to have to re-learn the PITA procedure to make a custom kernel/initrd for d-i so i can boot with a 3.0.x or 3.2.x kernel. it's been a few years since i did it, but i remember that it was a tediously convoluted process that involved shaving far too many yaks (including a full d-i build when all i want is a suitable kernel+initrd to place on my tftp server). (*) for instance, the latest squeeze kernel/initrd has removed the firmware for the Realtek RTL8101E/RTL8102E NIC. hooray, i just love screwing around with USB sticks and windows-like hunts for missing drivers. I also love PXE-booting into an installer and then finding that a NIC that IPXE has no problem with won't work with the debian kernel. The sid and wheezy installers still have the firmware...boo for nasty un-PC kernels. maybe i should try Linux Mint. craig -- craig sanders <cas@taz.net.au>
On 10/02/2012, at 20:58, Craig Sanders <cas@taz.net.au> wrote:
I'm installing debian on an Acer Aspire 1 D257 notebook for someone, and the installer won't recognise the hard disk.
all i get from the installer is "No disk drive was detected. If you know the name of the driver needed by your disk drive, you can select it from the list." followed by a selectable list of mostly-ancient drivers, all irrelevant.
you may try the bios setting for the sata mode in use. ahci mode may be more easily detected in debian
On Fri, Feb 10, 2012 at 09:24:06PM +1100, hannah commodore wrote:
you may try the bios setting for the sata mode in use. ahci mode may be more easily detected in debian
it's already in ahci mode - and i didn't want to change it because there's an existing install of win7 that I shrunk with gparted...changing to IDE mode or whatever is likely to require a reinstall of windows. gparted's linux kernel can detect the disk with no problem, so it's d-i's kernel. craig -- craig sanders <cas@taz.net.au>
On Fri, Feb 10, 2012 at 11:31:19PM +1100, Craig Sanders wrote:
On Fri, Feb 10, 2012 at 09:24:06PM +1100, hannah commodore wrote:
you may try the bios setting for the sata mode in use. ahci mode may be more easily detected in debian
it's already in ahci mode - and i didn't want to change it because there's an existing install of win7 that I shrunk with gparted...changing to IDE mode or whatever is likely to require a reinstall of windows.
just tried changing it to IDE mode, made no difference. it was worth a try, i was hoping i could install as IDE then switch back to AHCI with a newer kernel. thanks anyway for giving me the idea. craig -- craig sanders <cas@taz.net.au> BOFH excuse #278: The Dilithium Crystals need to be rotated.
On Fri, Feb 10, 2012 at 08:58:43PM +1100, Craig Sanders wrote:
I'm beginning to think i'm going to have to re-learn the PITA procedure to make a custom kernel/initrd for d-i so i can boot with a 3.0.x or 3.2.x kernel.
or i could do a quick-and-dirty hack to update the d-i initrd with newer kernel modules (and firmware), like so: (i already have the netboot installer unpacked in /tftp/di/sid/amd64) cd /tftp/di/sid/amd64 mkdir orig mv linux initrd.gz orig/ cp -af /boot/vmlinuz-3.2.0-1-amd64 ./linux mkdir initrd cd initrd zcat ../orig/initrd.gz | cpio -i --no-absolute-filenames cp -af /lib/modules/3.2.0-1-amd64/ lib/modules/ cp -af /lib/firmware/ lib/ find . | cpio -o -H newc | gzip -c > ../initrd.gz this gives me a 43MB initrd.gz rather than 6.5MB, but that's not surprising - all the modules in the stock linux-image-3.2.0-1-amd64 package are there, plus about 5MB of firmware files from firmware-linux, firmware-linux-free, firmware-linux-nonfree, and firmware-realtek. There's also the original 2.6.32-5 modules (~8MB) which I forgot to delete :). doesn't matter, downloading a 43MB file over the local GB lan doesn't take significantly longer than downloading a 6.5MB file. ganesh:/tftp/di/sid/amd64# ls -lh initrd.gz orig/initrd.gz -rw-rw-r-- 1 root root 43M Feb 11 08:08 initrd.gz -rw-r--r-- 1 root root 6.5M Jan 18 2011 orig/initrd.gz the install seems to be working fine so far, and has almost completed. it detected the hard disk with no problems. No problems with firmware for the NIC either (it even detected the Atheros wireless NIC and offered that as an option along with the wired Realtek NIC). the installer did complain at one point about not being able to download kernel modules due to version mismatch, but that's not a problem because all the needed modules are already in the initrd. craig -- craig sanders <cas@taz.net.au>
Craig Sanders wrote:
On Fri, Feb 10, 2012 at 08:58:43PM +1100, Craig Sanders wrote:
I'm beginning to think i'm going to have to re-learn the PITA procedure to make a custom kernel/initrd for d-i so i can boot with a 3.0.x or 3.2.x kernel.
or i could do a quick-and-dirty hack to update the d-i initrd with newer kernel modules (and firmware), like so:
Obviously too late this time, but it sounds like you weren't aware of the daily builds, which are 3.2 already: root@alpha:/srv/tftp/debian# file -s *.kernel daily-amd64.kernel: Linux kernel x86 boot executable bzImage, version 3.2.0-1-amd64 (unknown@Debian) , RO-rootFS, swap_dev 0x2, Normal VGA daily-i386.kernel: Linux kernel x86 boot executable bzImage, version 2.6.37-2-486 (unknown@Debian) #, RO-rootFS, swap_dev 0x2, Normal VGA stable-amd64.kernel: Linux kernel x86 boot executable bzImage, version 2.6.32-5-amd64 (unknown@Debian), RO-rootFS, swap_dev 0x2, Normal VGA stable-i386.kernel: Linux kernel x86 boot executable bzImage, version 2.6.32-5-486 (unknown@Debian) #, RO-rootFS, swap_dev 0x2, Normal VGA testing-amd64.kernel: Linux kernel x86 boot executable bzImage, version 2.6.32-5-amd64 (unknown@Debian), RO-rootFS, swap_dev 0x2, Normal VGA testing-i386.kernel: Linux kernel x86 boot executable bzImage, version 2.6.32-5-486 (unknown@Debian) #, RO-rootFS, swap_dev 0x2, Normal VGA unstable-amd64.kernel: Linux kernel x86 boot executable bzImage, version 2.6.32-5-amd64 (unknown@Debian), RO-rootFS, swap_dev 0x2, Normal VGA unstable-i386.kernel: Linux kernel x86 boot executable bzImage, version 2.6.32-5-486 (unknown@Debian) #, RO-rootFS, swap_dev 0x2, Normal VGA Hmm, scratch that, it would seem only the x86-64 one is. URLs: http://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/{linux,initrd.gz} http://people.debian.org/~joeyh/d-i/images/daily/netboot/debian-installer/i386/{linux,initrd.gz}
On Sun, Feb 12, 2012 at 01:45:40AM +1100, Trent W. Buck wrote:
or i could do a quick-and-dirty hack to update the d-i initrd with newer kernel modules (and firmware), like so:
Obviously too late this time, but it sounds like you weren't aware of the daily builds, which are 3.2 already:
thanks for that. now that you mention it, i remember the daily builds from years ago. I'll have to write a script to fetch the daily builds and integrate them into my tftp d-i setup (i.e. fetch and unpack the netboot.tar.gz and generate a menu entry)....i've already done that for the release builds. no need to run it from cron, but nice to have it automated when i want to manually update the images. i probably would have had to modify the initrd anyway, for the NIC firmware. (there's something particularly annoying about a netboot installer that deliberately excludes firmware for common NICs. for me, on this issue, pragmatism wins and i don't see any real difference between firmware in rom versus firmware binary blobs in files...if it runs on the card and not in the kernel, then it's not worth worrying about. and i dislike having to stuff around with floppies or USB sticks - that's why i have a pxe/tftp netboot setup, to avoid that kind of hassle) BTW, the aspire1 install is finished and it's working fine now. it even reboots properly after i googled for and found out i had to add "reboot=efi" to the kernel command line (before that, linux would complete the shutdown process correctly, and then just hang with a blank screen instead of rebooting).
Hmm, scratch that, it would seem only the x86-64 one is. URLs:
http://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/{linux,initrd.gz} http://people.debian.org/~joeyh/d-i/images/daily/netboot/debian-installer/i386/{linux,initrd.gz}
not surprising. i386 is pretty much legacy these days, nearly everything x86 compatible is actually x86-64. probably the biggest reason for new i386 installs these days is VMs running 32 bit to save a bit of memory. craig -- craig sanders <cas@taz.net.au> BOFH excuse #98: The vendor put the bug there.
Craig Sanders wrote:
thanks for that. now that you mention it, i remember the daily builds from years ago. I'll have to write a script to fetch the daily builds and integrate them into my tftp d-i setup (i.e. fetch and unpack the netboot.tar.gz and generate a menu entry)....i've already done that for the release builds. no need to run it from cron, but nice to have it automated when i want to manually update the images.
FYI, mine are attached. Not pretty, but it does run daily, takes no action if there are no dl's (and emails me if there are), and rewrites the pxelinux menu.
On 12/02/2012, at 10:41, Craig Sanders <cas@taz.net.au> wrote:
I'll have to write a script to fetch the daily builds and integrate them into my tftp d-i setup (i.e. fetch and unpack the netboot.tar.gz and generate a menu entry)....i've already done that for the release builds. no need to run it from cron, but nice to have it automated when i want to manually update the images.
Neat. I'd very much like that script to integrate into my pxe rescue system. Would you mind sharing?
On 12/02/2012, at 12:11, hannah commodore <hannah@tinfoilhat.net> wrote:
On 12/02/2012, at 10:41, Craig Sanders <cas@taz.net.au> wrote:
I'll have to write a script to fetch the daily builds and integrate them into my tftp d-i setup (i.e. fetch and unpack the netboot.tar.gz and generate a menu entry)....i've already done that for the release builds. no need to run it from cron, but nice to have it automated when i want to manually update the images.
Neat. I'd very much like that script to integrate into my pxe rescue system. Would you mind sharing?
Sorry I spoke too soon, before. saw Trent's post. thanks
On Sun, Feb 12, 2012 at 12:14:52PM +1100, hannah commodore wrote:
Sorry I spoke too soon, before. saw Trent's post.
Trent's seem more comprehensive than mine. I'll read them in more detail and probably end up stealing some ideas from them. craig -- craig sanders <cas@taz.net.au> BOFH excuse #407: Route flapping at the NAP.
On Sun, Feb 12, 2012 at 12:11:19PM +1100, hannah commodore wrote:
On 12/02/2012, at 10:41, Craig Sanders <cas@taz.net.au> wrote:
I'll have to write a script to fetch the daily builds and integrate them into my tftp d-i setup (i.e. fetch and unpack the netboot.tar.gz and generate a menu entry)....i've already done that for the release builds. no need to run it from cron, but nice to have it automated when i want to manually update the images.
Neat. I'd very much like that script to integrate into my pxe rescue system. Would you mind sharing?
it's pretty basic and only semi-automated because I don't want to run it from cron but here it is. I also have very similar scripts for clonezilla and gparted. the basic idea of all of them is to fetch the .tar.gz or .zip file from the source site, extract the appropriate files from them (e.g. for clonezilla, extract only .../live/*) and then rename/move them into a consistent directory structure to enable generation of the menu. BTW, i'm using ipxe (and previously gpxelinux.0) because it allows me to use http:// URLs rather than tftp for the kernel and initrd, so tftp is really only used by the NIC's boot ROM to load ipxe, then it's http from that point. i have apache configured so that /tftp/ points to the tftp root dir (which has subdirectories ./di/ for debian installer, ./cz/ for clonezilla, ./gp/ for gparted), with appropriate allow/deny rules. if your pxeboot setup only supports tftp, you'll need to modify to suit. also BTW, the latest ipxe packages in debian can optionally add a "Network boot (iPXE)" entry to your grub menu. nice. and very useful if you miss the few second window for push F12 or whatever to bring up the BIOS boot device menu. also handy to use with grub-set-default and grub-reboot. anyway, there's actually two scripts. one to fetch the latest netboot installer from a nearby mirror. the second to generate the menu. the fetcher script uses snarf. easy to replace with wget or curl or whatever you prefer. i like snarf because it produces minimal output compared to wget or curl. ---cut here---fetch-di.sh---cut here--- #! /bin/bash # default to fetching sid installer DIST=${1:-sid} mkdir -p $DIST cd $DIST mkdir tmp # end result is /tftp/di/$DIST/$arch/linux and /tftp/di/$DIST/$arch/initrd.gz for arch in i386 amd64 ; do snarf "ftp://mirror.aarnet.edu.au/debian/dists/$DIST/main/installer-$arch/current/images/netboot/netboot.tar.gz" "netboot-$arch.tar.gz" cd tmp tar xfz "../netboot-$arch.tar.gz" mv debian-installer/$arch ../ cd .. #rm -f "netboot-$arch.tar.gz" done rm -rf tmp cd .. ---cut here---fetch-di.sh---cut here--- ---cut here---make-di-menu.sh---cut here--- #!/bin/bash IP='my.tftp.server.ip' cat default.head # the "$dist" directory names are arbitrary...allows me to have multiple # versions. e.g. i currently have a "squeeze" dir and a "squeeze.old" # as well as a "sid" and a "sid3.2.0" for my custom version. like i said, # only semi-automated...i find it's a useful balance between automation and # custom hacks. for dist in $(find . -maxdepth 1 -type d | sed -e 's:^./\?::' | xargs) ; do for arch in amd64 i386 ; do if [ -e $dist/$arch/linux ] ; then cat <<__EOF__ LABEL $dist-$arch MENU LABEL $dist Debian Installer $arch kernel http://$IP/tftp/di/$dist/$arch/linux append initrd=http://$IP/tftp/di/$dist/$arch/initrd.gz vga=normal priority=low preseed/url=http://$IP/tftp/di/preseed.cfg -- __EOF__ fi done done cat default.tail ---cut here---make-di-menu.sh---cut here--- the output goes to stdout. redirect as appropriate (in my case, to /tftp/di/default). default.tail is an empty file (just there for completeness in case i one day decide i need to append some static content to the bottom of the menu). default.head contains the following: ---cut here---default.head---cut here--- PROMPT 0 TIMEOUT 120 MENUROWS 16 MENU TITLE Debian Installer Menu MENU COLOR disabled 1;33;44 ---cut here---default.head---cut here--- craig -- craig sanders <cas@taz.net.au> BOFH excuse #47: Complete Transient Lockout
participants (3)
-
Craig Sanders -
hannah commodore -
Trent W. Buck