Ok it downloads and unpacks fine, then it gets into trouble (see below). Any ideas?
Thanks, Ryan. [EMAIL PROTECTED]:/# dpkg -i linux-image*deb (Reading database ... 99891 files and directories currently installed.) Preparing to replace linux-image-2.6.27-4-generic 2.6.27-4.6 (using linux-image-2.6.27-4-generic_2.6.27-4.6_i386.deb) ... Done. Unpacking replacement linux-image-2.6.27-4-generic ... Running postrm hook script /sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub findfs: Unable to resolve 'UUID=ed2f6ce4-7e7c-4a78-8617-c5eb74d3f540' Cannot determine root device. Assuming /dev/hda1 This error is probably caused by an invalid /etc/fstab Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.27-4-generic Found kernel: /boot/last-good-boot/vmlinuz Updating /boot/grub/menu.lst ... done Setting up linux-image-2.6.27-4-generic (2.6.27-4.6) ... Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.27-4-generic grep: /proc/modules: No such file or directory grep: /proc/modules: No such file or directory grep: /proc/modules: No such file or directory grep: /proc/modules: No such file or directory grep: /proc/modules: No such file or directory grep: /proc/modules: No such file or directory grep: /proc/modules: No such file or directory Not updating initrd symbolic links since we are being updated/reinstalled (2.6.27-4.6 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.27-4.6 was configured last, according to dpkg) Running postinst hook script /sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub findfs: Unable to resolve 'UUID=ed2f6ce4-7e7c-4a78-8617-c5eb74d3f540' Cannot determine root device. Assuming /dev/hda1 This error is probably caused by an invalid /etc/fstab Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.27-4-generic Found kernel: /boot/last-good-boot/vmlinuz Updating /boot/grub/menu.lst ... done Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/nvidia-common pcilib: Cannot open /proc/bus/pci -----Original Message----- From: Emmet Hikory <[EMAIL PROTECTED]> To: Ubuntu Mobile <[email protected]> Subject: Re: Supporting Ubuntu Mobile Date: Fri, 26 Sep 2008 23:21:21 +0900 Steve Paine wrote: > I was proposing that I send an SC3 to Oliver (mainly as I know him and > he's not far from me in Germany) to help out with the SCH/Poulsbo > testing, not buying up the contents of Dynamism and shipping it to him ;-) > I doubt you'll find many devs with poulsbo/touch hardware out there to > be honest either so unless Canonical are sending engineers devices, > where do they start? Oh. Yeah. One device to Oliver is probably a good idea :) I'm a little lucky because of where I live, and got a Sharp D4 yesterday, on which I've been testing both Ubuntu Mobile and Ubuntu MID (although I think ultimately I'll be using Ubuntu MID, because of the DPI). > How many people on the Ubuntu Mobile (distro) team right now though? I > get the impression that its, er, not many more than Oliver? Well, Ubuntu Mobile is one of two flavours (Mobile and MID) created by the Ubuntu Mobile team. I think there are 5-6 people who actively contribute stuff, and about the same that spend time on IRC testing and sending patches. Not nearly enough :) > No problem. you tell me where people should gather. I'll try and promote > that meeting point. > Dont say IRC or mailing lists though. Open, easy to use forums is > probaly the best way to achieve the critical seeding process. You're probably right. While I live on IRC and mailing lits, forums are much more accessible. What do you think about using the Ubuntu Forums? > Dont forget, touch-interfaces are important here with the mid-range > devices. With either large or small screen, the finger doesnt change its > size so moving to desktop just because a device has a large screen is a > mistake. I see Ubuntu Mobile targeted at the nobile devices. Sub 1KG, > often without keyboards. Certainly not. The issue is mostly about DPI, not screen size. While I say "Ubuntu MID is for 4-6" devices, and Ubuntu Mobile is for 7-9" devices, and Ubuntu Desktop is a good choice for > 10" devices", what I'm really saying is if one more than 200 DPI, Ubuntu Mobile gets a little cramped, and when one drops below about 100 DPI, Ubuntu Mobile gets a little chunky. > OK. I'm happy to promote Ubuntu-Mobile for UMPC-sized Poulsbo devices > and very happy to see it happen. > Send me details of the ubuntu forum that people should plug into, > details of the team and its project wiki/plan and The wiki needs work. I'll see if I can spend some time on it, but if anyone else wants to flesh out more on wiki.ubuntu.com, that would be great. I'll approach the forums team to see how we can register a forum, but that will require some forum admins: any volunteers? > I'll create a news item to say that we're behind Ubuntu Mobile as our #1 > hope for UMPCs. Some promo work has to be done somewhere along the > lines, I hope this little bit will help to seed enough support and > action to get things moving quickly. Netbooks, MIDs and UMPCs are the > biggest chance that Linux has ever had to get into the hands of millions > but in my opinion, you havent got long before others come in on the scene. Thanks for this. Such an article would be a great help. I agree about timing, but there's some work needing doing on getting the wiki cleaned up and the forums staffed. Anyone is welcome to join and help with that, but until those are in place, I don't think there's anything but mailing lists and IRC channels. -- Emmet HIKORY
-- Ubuntu-mobile mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
