Hello. This is a follow up to a question I posed about a reboot problem I had with Ubuntu 8.10 on a Toshiba Portege R100 laptop.
The problem is now resolved. It "went away" after the latest Kernel update from Ubuntu. Ubuntu kernel image vmlinuz-2.6.27-11 seems to do the trick. I never did try compiling my own kernel. Incidentally before the new kernel dropped I experimented with several other distributions and older kernel versions. All of them exhibited exactly the same behaviour. In any case it is fixed now. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gustin Johnson Sent: January 18, 2009 2:45 PM To: CLUG General Subject: Re: [clug-talk] Ubuntu Reboot Difficulties Craig McLean wrote: > Hello. > > I'm sitting at home because I'm on call tonight. So I did some more work on > the reboot and shutdown problem I'm having with my R100 laptop under Ubuntu > 8.10. > > Here is what I've found. > > The problem appears to be related to the WIFI adapter in the machine. There > is a switch on the side of the laptop which allows you to enable and disable > the WIFI adapter in the laptop. If the adapter is off then reboot and > shutdown work fine, if it is on then reboot and shutdown result in the blank > screen I described in my initial note. > > The laptop uses an Intel Pro/Wireless 2100b. The kernel module is ipw2100. > > I noticed whether the switch is on or off the kernel module remains loaded. > I also did some experiments with ifconfig. I left the switch on and > manually downed the wireless interface, which is eth1, using "ifconfig eth1 > down". I then attempted to reboot the laptop and had the same result, blank > screen no reboot. > > The only thing which seems to solve the issue is flipping the switch off > before rebooting or shutting down. > > Armed with this new information I did some more forum searches and found > some hints that it could be related to the ALSA sound subsystem. They > suggested putting explicit "ifconfig eth0 down" and "ifconfig eth1 down" > lines into the stop section of the ALSA-UTILS init script. That didn't fix > the issue. I didn't expect it would either since my system does > successfully halt. > > Based on this information does anybody else have any ideas on what might be > going on here? > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Greg King > Sent: January 17, 2009 1:35 PM > To: [email protected] > Subject: Re: [clug-talk] Ubuntu Reboot Difficulties > >> Date: Sat, 17 Jan 2009 00:31:21 -0700 >> From: "Craig McLean" <[email protected]> >> Subject: [clug-talk] Ubuntu Reboot Difficulties >> To: "'CLUG General'" <[email protected]> >> Message-ID: <90b9226ab74045bfa59428aa626bf...@wiseone> >> Content-Type: text/plain; charset="us-ascii" >> >> Hello. >> >> I just upgraded one of my laptops to Ubuntu 8.10. Whenever I try to >> reboot >> or shutdown I run into some trouble. >> >> Here is a sequence of events >> Within Gnome I do a restart or shutdown from the menu, the OS goes to the >> boot splash chugs away for awhile and then the screen blanks (even the >> back >> light turns off) however the system itself does not turn off or restart, >> there is no disk activity at all at this point, however the disk and fan >> are >> still spinning. I'm fairly certain the system has halted. I can manually >> turn the PC off by doing the usual power button for four seconds routine. >> When I restart the machine everything comes up clean. >> >> I turned off the boot splash and the last entry before the screen blanks >> is >> "acpid: exiting". The last entry in \var\log\messages before the reboot >> is >> <computer name> exiting on signal 15. >> >> All other power management operations work. Suspend, Hibernate, and >> Resume >> all work. The soft power button works (if you push it you get the >> shutdown >> menu) opening and closing the lid works as expected, disconnecting and >> reconnecting power also works (the laptops changes its power profile and >> dims or brightens the back light among other things). It is weird the >> only >> operations which don't work are the ones that usual do. >> >> Here are my details >> >> Ubuntu 8.10 with all Ubuntu patches as of January 17, 2009. Specifically >> kernel 2.6.27.19-generic. >> >> Trident graphics driver for X-Windows >> >> Laptop is a Toshiba R100 (model ppr10c-04m8z) BIOS 1.50 (there is a BIOS >> 1.60 available but it only has a microcode update for the processor). I >> also can't really install it right now since I don't have a USB floppy >> drive >> around. >> >> Does anybody have any clues or theories about why this might be happening? >> >> Craig >> > Yes, I ran into this running Kubuntu 8.10 under vmware. I googled around > and found a couple of potential fixes, one being a patch that was already > on, and the other an X system setting to restart X on logout which seemed to > work. I'm a little hazy on the detail now, but if you google "ubuntu > shutdown hang" I think you'll find quite a few folks have experienced it. > There is a lot of changes happening in the wifi stack right now (actually a lot of other things too). Also the 2.6.27 kernel has a number of issues. On my netbook wifi was completely broken for my Intel 4965. Building a 2.6.28 seems to have resolved this for me. This is a classic example of why the Ubuntu fixed release schedule is problematic. I have no problems with them having a schedule for the LTS versions, but 8.10 was released at a bad time with problems that needed to be fixed upstream. If this is really a problem, I would recommend sticking with 8.04 for now. You could also try building a 2.6.28 to see if that helps. Hth, _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
