Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 163776 - sys-apps/baselayout-1.13.0_alpha12 scripts(several bugs)
Summary: sys-apps/baselayout-1.13.0_alpha12 scripts(several bugs)
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:
Depends on:
Blocks:
 
Reported: 2007-01-25 17:22 UTC by GNUtoo
Modified: 2007-04-11 15:28 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GNUtoo 2007-01-25 17:22:15 UTC
i have a ralink card that is a rt2500 and i use the rt2500 drivers
i have some issues with the config files...here my config:
# cat /etc/conf.d/net
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d.  To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
dns_domain_lo="workgroup"

#modules=( "iwconfig" )
#config_linksys=("dhcp")

#Prefered acess points
preferred_aps=("wrt54gs")
blacklist_aps=("Hercules" "CAMBRIDGE")

#Acess points settings
config_wrt54gs=( "192.168.1.122/24 brd 192.168.0.255" )
routes_wrt54gs=( "default via 192.168.1.1" )
dns_servers_wrt54gs=( "212.68.193.110" "212.68.193.196" )
scans_ra0="5"

#cable settings
#config_eth1=( "192.168.1.122/24 brd 192.168.0.255" )
#routes_eth1=( "default via 192.168.1.1" )
#dns_servers_eth1=( "212.68.193.110" "212.68.193.196" )

#config_eth0=( "192.168.1.122/24 brd 192.168.0.255" )
#routes_eth0=( "default via 192.168.1.1" )
#dns_servers_eth0=( "212.68.193.110" "212.68.193.196" )

#port3 routing settings
#config_eth1=("192.168.0.1/24 brd 192.168.0.255")
#routes_eth1=("default via 192.168.0.2")
#dns_servers_eth1=("212.68.193.110" "212.68.193.196")

#10/100/1000
#config_eth0=("192.168.0.1/24 brd 192.168.0.255")


#tun device
#tuntap_tun0=("tun")
#config_tun0=("192.168.1.122/24")

#tap device
tuntap_tap0=("tap")
config_tap0=("192.168.1.122/24")




here the result:
#  /etc/init.d/net.ra0 start
 * Starting ra0
 *   Configuring wireless network for ra0
 *   Scanning for access points
 *     Found "wrt54gs" at 00:14:BF:E1:DA:DF (managed)
 *   Connecting to "wrt54gs" in managed mode (WEP Disabled) ...          [ ok ]
 *     ra0 connected to ESSID "CAMBRIDGE"
 *     in managed mode on channel 7 (WEP disabled)
 *   Configuration not set for ra0, assuming DHCP
 *   Bringing up ra0
 *     dhcp
 *       Running dhcpcd ...                                              [ ok ]
 *       ra0 received address 192.168.1.105/24

# iwconfig
bond0     no wireless extensions.

plip0     no wireless extensions.

eth0      no wireless extensions.

eth1      no wireless extensions.

lo        no wireless extensions.

shaper0   no wireless extensions.

dummy0    no wireless extensions.

teql0     no wireless extensions.

tunl0     no wireless extensions.

gre0      no wireless extensions.

sit0      no wireless extensions.

ip6tnl0   no wireless extensions.

ra0       RT2500 Wireless  ESSID:"wrt54gs"
          Mode:Managed  Frequency=2.442 GHz  Access Point: 00:14:BF:E1:DA:DF
          Bit Rate:54 Mb/s   Tx-Power:0 dBm
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=76/100  Signal level=-67 dBm  Noise level:-196 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:100 errors:0 dropped:0 overruns:0 frame:0
          TX packets:100 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6388 (6.2 Kb)  TX bytes:6388 (6.2 Kb)

ra0       Link encap:Ethernet  HWaddr 00:08:A1:A0:1B:B7
          inet addr:192.168.1.105  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::208:a1ff:fea0:1bb7/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1080 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5531 errors:7 dropped:7 overruns:0 carrier:0
          collisions:60 txqueuelen:1000
          RX bytes:925443 (903.7 Kb)  TX bytes:360774 (352.3 Kb)
          Interrupt:22 Base address:0xc000





that's not normal because:
*It says that it connect to CAMBRIDGE but in reality it connect ro wrt54gs
*it use dhcpcd instead of the configuration inside the /etc/conf.d/net file

before that i used had problem connecting and i needed to:
1)ifconfig ra0 up
2)Raconfig2500
3)select wrt54gs
4) /etc/init.d/net.ra0 start
and i was getting my connection with my settings

by the way there is another bug with the networking in baselayout:
# rc-update show
           alsasound | boot
            bootmisc | boot
             checkfs | boot
           checkroot | boot
               clock | boot
             codasrv |      default
         consolefont | boot
            hostname | boot
             keymaps | boot
               local |      default nonetwork
          localmount | boot
            mldonkey |      default
             modules | boot
               mysql |      default
              net.lo | boot
            netmount |      default
           rmnologin | boot
                sshd |      default
           syslog-ng |      default
             urandom | boot
             volumes | boot

and at boot it loads eth0 and eth1...but they are not in boot or anywhere else

Reproducible: Always
Comment 1 Roy Marples (RETIRED) gentoo-dev 2007-01-31 08:09:09 UTC
That looks more like a driver problem. I have 2 rt2500 cards and am using upstreams beta4 driver without this issue.

Could you test their nightly tarball please?
http://rt2x00.serialmonkey.com/rt2500-cvs-daily.tar.gz
Comment 2 GNUtoo 2007-01-31 20:54:31 UTC
he problem is that because of ide problems i am now using the new pata driver from the 2.6.19 kernel
and the rt2x00 driver is not yet compatible with the 2.6.19 kernel
i am also using upstream beta4 drivers...
Comment 3 Roy Marples (RETIRED) gentoo-dev 2007-04-11 15:28:32 UTC
Does this happen with baselayout-2?
If so, re-open.