Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 196647 - ipw3945d problems with baselayout-2.0.0_rc5
Summary: ipw3945d problems with baselayout-2.0.0_rc5
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
: 179809 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-10-21 18:13 UTC by Francesco Piccinno
Modified: 2007-12-05 19:46 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Francesco Piccinno 2007-10-21 18:13:17 UTC 
ToSSiKa stack # /etc/init.d/ipw3945d restart
 * Stopping ipw3945d ...
 * start-stop-daemon: fopen `/var/run/ipw3945d/ipw3945d.pid': No such file or directory                                                                                   [ ok ]
 * Starting ipw3945d ...                                                                                                                                                  [ ok ]
ToSSiKa stack # /etc/init.d/ipw3945d restart
 * Stopping ipw3945d ...                                                                                                                                                  [ ok ]
 * Starting ipw3945d ...                                                                                                                                                  [ ok ]


Reproducible: Always
Comment 1 Andriy Baranskyy 2007-10-28 21:49:56 UTC 
Same here! It works perfectly well on 2.0.0_rc4-r1
Comment 2 Andriy Baranskyy 2007-11-01 00:37:39 UTC 
With the new rc6 release, the ipw3945d fails to start at boot time but starts fine after other modules have loaded. Again, this problem is not present for rc4-r1
Comment 3 Andriy Baranskyy 2007-11-01 00:39:30 UTC 
(In reply to comment #2)
> With the new rc6 release, the ipw3945d fails to start at boot time but starts
> fine after other modules have loaded. Again, this problem is not present for
> rc4-r1
> 
p.s. My rc-update:
 rc-update
                acpid |      default
            alsasound |      default
            bluetooth |      default
             bootmisc | boot
              checkfs | boot
            checkroot | boot
              chronyd |      default
                clock | boot
          consolefont | boot
                cupsd |      default
                 dbus |      default
                dcron |      default
        device-mapper | boot
             festival |      default
                  gpm |      default
                 hald |      default
             hostname | boot
              hotplug | boot
              keymaps | boot
                local |      default nonetwork
           localmount | boot
              modules | boot
               net.lo | boot
             netmount |      default
            rmnologin | boot
            syslog-ng |      default
              urandom | boot
                  xdm |      default
Comment 4 Roy Marples (RETIRED) gentoo-dev 2007-11-01 01:35:13 UTC 
Try adding "need localmount" to the init script depend function
Comment 5 Andriy Baranskyy 2007-11-01 01:46:12 UTC 
(In reply to comment #4)
> Try adding "need localmount" to the init script depend function
> 

Thanks! This fixes the problem. I found relevant page in Gentoo Handbook describing the problem: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=4

Should we file a separate bug for the init script to be fixed?
Comment 6 Roy Marples (RETIRED) gentoo-dev 2007-11-01 02:00:14 UTC 
No need, I've fixed it.
Thanks.
Comment 7 Jan Kundrát (RETIRED) gentoo-dev 2007-12-05 17:19:18 UTC 
*** Bug 179809 has been marked as a duplicate of this bug. ***
Comment 8 Renato Caldas 2007-12-05 17:26:09 UTC 
Now what I don't understand is how my _older_ report is marked as a duplicate of this _newer_ report. Maybe time has changed direction?? Anyway, sorry for this kind of comments on bugzilla, but I had to do it....
Comment 9 Roy Marples (RETIRED) gentoo-dev 2007-12-05 19:46:25 UTC 
(In reply to comment #8)
> Now what I don't understand is how my _older_ report is marked as a duplicate
> of this _newer_ report. Maybe time has changed direction?? Anyway, sorry for
> this kind of comments on bugzilla, but I had to do it....

Sometimes on newer bugs different information is given which enables developers to fix the actual problem. Or it's assigned to different people.

Just be glad it's fixed :)