Re: [gentoo-user] To Wifi or not to Wifi...
On 07/29/2015 05:42 AM, meino.cra...@gmx.de wrote:
<...snip...>
2) How I can assign a static IP to my tablet.
At the end of /etc/dhcp/dhcpd.conf add a line like
host mytablet { hardware ethernet xx:xx:xx:xx:xx:xx; fixed-address
xxx.xxx.xxx.xxx; }
3) How I can change the MAC on my tablet.
What is the OS on the tablet?
Re: [gentoo-user] To Wifi or not to Wifi...
On Wednesday 29 July 2015 06:40:51 Mick wrote: > On Wednesday 29 Jul 2015 03:42:56 meino.cra...@gmx.de wrote: > > Still I have to figure out: > > > > 1) What create_ap does differently (and more correctly). > > It also sets up a DNS repeater, DHCP server and configures iptables on your > PC. > > > 2) How I can assign a static IP to my tablet. > > There must be some config files to edit, but I'm guessing you won't have > access to these without rooting the tablet. I think Meino means how he should tell dhcpd to assign the same IP to his tablet every time it appears. This is easy in dnsmasq but I don't know dhcp. -- Rgds Peter
Re: [gentoo-user] Hubris?
On Tuesday 28 July 2015 21:18:43 Neil Bothwick wrote: > On Wed, 29 Jul 2015 05:29:18 +1000, Bruce Schultz wrote: > > >You may not need an initramfs to run root on btrfs as long as btrfs is > > >compiled into your kernel (I haven't looked into it closely though). > > > > But I think you do if your btrfs is raid 1. The kernel can't mount > > multidisk btrfs until it done a btrfs device scan in userspace, run > > from initramfs. > > According to the btrfs wiki you can pass > device=/dev/sda1,device=/dev/sdb1 on the kernel boot line. Thanks all. I think I'm going to dive straight in and build a new system. First I'll have another go at grub-2, then when that's working I'll start a new build. As far as I can see, /boot can just be on the single sda1, with a duplicate on sdb1 in reserve. -- Rgds Peter
Re: [gentoo-user] Hubris?
On Wed, 29 Jul 2015 09:13:50 +0100, Peter Humphrey wrote: > I think I'm going to dive straight in and build a new system. First > I'll have another go at grub-2, then when that's working I'll start a > new build. > > As far as I can see, /boot can just be on the single sda1, with a > duplicate on sdb1 in reserve. Yes, I set the boot partitions up as a RAID1 (MD RAID, not btrfs RAID). Then GRUB can read any one of them but they are all kept in sync. -- Neil Bothwick C:\DOS\SYSTEM\BATCH\UTILS\API\DOCS\READ\STORED\WHERE\THE\HELL\AM\I\? pgpUgIiQcwgOi.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Hubris?
On Wednesday 29 July 2015 00:40:41 Neil Bothwick wrote: > On Tue, 28 Jul 2015 22:59:40 +0100, Mick wrote: > > > > But I think you do if your btrfs is raid 1. The kernel can't mount > > > > multidisk btrfs until it done a btrfs device scan in userspace, run > > > > from initramfs. > > > > > > According to the btrfs wiki you can pass > > > device=/dev/sda1,device=/dev/sdb1 on the kernel boot line. > > > > Apologies if I have missed it, but what is wrong with using vanilla > > ext2 for /boot? > > The question is about the kernel mounting / from a multi-device btrfs, > without an initramfs - nothing to do with /boot. It's a good question all the same, tangential or not. -- Rgds Peter
Re: [gentoo-user] To Wifi or not to Wifi...
On Wednesday, July 29, 2015 10:54:53 AM Thanasis wrote:
> On 07/29/2015 05:42 AM, meino.cra...@gmx.de wrote:
> <...snip...>
>
> > 2) How I can assign a static IP to my tablet.
>
> At the end of /etc/dhcp/dhcpd.conf add a line like
>
> host mytablet { hardware ethernet xx:xx:xx:xx:xx:xx; fixed-address
> xxx.xxx.xxx.xxx; }
>
> > 3) How I can change the MAC on my tablet.
>
> What is the OS on the tablet?
If I read this right in this thread, I believe it's Android Lollipop.
In this case, without rooting, it definitely will not be possible.
I don't see why anyone would want to change the MAC on a tablet, other then
try to break into someone elses WIFI.
--
Joost
Re: [gentoo-user] Hubris?
On Wed, 29 Jul 2015 09:22:47 +0100, Peter Humphrey wrote: >> > Apologies if I have missed it, but what is wrong with using vanilla > > > ext2 for /boot? > > > > The question is about the kernel mounting / from a multi-device btrfs, > > without an initramfs - nothing to do with /boot. > > It's a good question all the same, tangential or not. Yes, and it's what I do on my desktop, which doesn't use UEFI. As we migrate to UEFI hardware the question becomes moot as we use FAT for /boot, and no longer have to deal with GRUB. -- Neil Bothwick Very funny Scotty.. now beam down my pants! pgp5StbQD4Gtv.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Hubris?
On 29 July 2015 6:18:43 AM AEST, Neil Bothwick wrote: >On Wed, 29 Jul 2015 05:29:18 +1000, Bruce Schultz wrote: > >> >You may not need an initramfs to run root on btrfs as long as btrfs >is >> >compiled into your kernel (I haven't looked into it closely though). > >> >> But I think you do if your btrfs is raid 1. The kernel can't mount >> multidisk btrfs until it done a btrfs device scan in userspace, run >> from initramfs. > >According to the btrfs wiki you can pass >device=/dev/sda1,device=/dev/sdb1 on the kernel boot line. I'd forgotten that option. Btrfs wiki also says this though: "Using device is not recommended, as it is sensitive to device names changing. You should really be using a initramfs. Most modern distributions will do this for you automatically if you install their own btrfs-progs package." https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices#Registration_in_.2Fetc.2Ffstab -- :b
Re: [gentoo-user] Testing SSD? (Somewhat OT)
On 07/28/2015 12:04 AM, Volker Armin Hemmann wrote: > > you know - this does not sound like ssd failure. Most SSDs bomb out by > just becoming completely unacessible. > > dmesg errors? Filled with /dev/sda errors when it "failed". > > are you using ecc ram? Nope. > > if not - maybe, just maybe it is your ram at fault. The stuff the kernel > sends and the stuff that end on the ssd might not be identical. > Ran memtest overnight on it, no errors. Dan
Re: [gentoo-user] To Wifi or not to Wifi...
Mick [15-07-29 16:38]: > On Wednesday 29 Jul 2015 03:42:56 meino.cra...@gmx.de wrote: > > Mick [15-07-29 03:32]: > > > On Tuesday 28 Jul 2015 20:35:55 Todd Goodman wrote: > > > > * meino.cra...@gmx.de [150728 15:31]: > > > > [..SNIP..] > > > > > > > > > Hi Todd, > > > > > > > > > > thanks for all your help and patience... :)) > > > > > > > > > > The recursive(recursive(recursive).problem.).problem).problem has > > > > > been solved by rebooting my PC (due to the new kernel) and restarting > > > > > the tablet PC. > > > > > > > > > > Now I am fighting against dhcpd...as sson as I want to start that > > > > > beast its telling me that dhcpd.ldap is missing. This was not > > > > > installed (at least as an example) by emerge. I have no idea what > > > > > is to get into that file. > > > > > > > > > > I will check create_ap...may be it is more intelligent than me in > > > > > writing config-files ;) > > > > > > > > > > But unfortunately I have to stop my journey here for today...it is > > > > > late here (9:00 pm) and I have to get out early tommorrow (4:00 am). > > > > > > > > > > But /I want/ to get this running finally. > > > > > We will see. > > > > > As soon I have something new, I will post more of the contents > > > > > of my harddisk ;) > > > > > > > > > > Best regards and thanks again! 8) > > > > > Meino > > > > > > > > Hi Meino, > > > > > > > > You're welcome. I'm sorry I couldn't be of more help (and get this > > > > solved!) > > > > > > > > I'm sure you will eventually. > > > > > > > > Please let us know how it goes once you get back to it. > > > > > > > > Good night, > > > > > > > > Todd > > > > > > A lot seems to have been progressed with since I last contributed to this > > > thread. Given that WiFi related problems were solved thanks to Todd's > > > good help, perhaps Meino should start a thread on setting up a local > > > dhcp server? > > > > > > However, I would recommend that you set a static route, gateway and IP > > > address on your tablet pointing to the PC and on the PC you configure IP > > > Masquerading, so that it can NAT connections from the tablet to the > > > Internet. > > > > > > However, if you must be running a dhcp server, then emerge and configure > > > net- misc/dhcp on the PC. > > > > Hi Todd, hi Mick, > > > > !YEAH! It works! > > create_ap did it! I have access to the internet on my tablet just by > > fireing up create_ap. > > > > There is one advantage of create_ap (beside creating a /working/ ap, > > which I was not able to...;) over the setup below /etc: One can give > > it an temporary SSID and password on the commandline - every > > configuration is temporary. In my case this is very handy, since I > > only need the AP for transferring files from and to my tablet. Makes > > the thing /a little/ more secure...a /little/. > > > > Still I have to figure out: > > > > 1) What create_ap does differently (and more correctly). > > It also sets up a DNS repeater, DHCP server and configures iptables on your > PC. > > > > 2) How I can assign a static IP to my tablet. > > There must be some config files to edit, but I'm guessing you won't have > access to these without rooting the tablet. > > > > 3) How I can change the MAC on my tablet. > > Ditto. > > -- > Regards, > Mick Hi Mick, thanks for your reply and answers! :) I have rooted the tablet, but I dont want to change "The inner core" (setup/boot scripts) until I know a little more about Android...it is quite a different Linux somehow. I thought of a temporary solution, which sets the MAC/IP from the commmandline until the tablet is booted again. create_ap is of great help for me...it be instructed to dump its configuration also, so I have a source for further inspections. Best regards, Meino
Re: [gentoo-user] To Wifi or not to Wifi...
Peter Humphrey [15-07-29 16:38]: > On Wednesday 29 July 2015 06:40:51 Mick wrote: > > On Wednesday 29 Jul 2015 03:42:56 meino.cra...@gmx.de wrote: > > > Still I have to figure out: > > > > > > 1) What create_ap does differently (and more correctly). > > > > It also sets up a DNS repeater, DHCP server and configures iptables on your > > PC. > > > > > 2) How I can assign a static IP to my tablet. > > > > There must be some config files to edit, but I'm guessing you won't have > > access to these without rooting the tablet. > > I think Meino means how he should tell dhcpd to assign the same IP to his > tablet every time it appears. This is easy in dnsmasq but I don't know dhcp. > > -- > Rgds > Peter > > Hi Peter, quite an easy answer: YESNO! ;) Until I read your mail, my thought of "statis IP" was: Server and client set their IPs for themselves statically and "know" of the IPs of the counterpart. Your mail gives (at least to me) a totally new aspect: DHCPd "dynamically" assigns the same IP to the client all the time. Which is an elegant solution around the problem of currently don't knowing how to set an IP on my tablet other than via DHCP. Downside: One still needs to configure DHCPd on the server side/site. Thanks for the new aspect! :) Best regards, Meino
Re: [gentoo-user] To Wifi or not to Wifi...
Thanasis [15-07-29 16:38]:
> On 07/29/2015 05:42 AM, meino.cra...@gmx.de wrote:
> <...snip...>
> >2) How I can assign a static IP to my tablet.
>
> At the end of /etc/dhcp/dhcpd.conf add a line like
>
> host mytablet { hardware ethernet xx:xx:xx:xx:xx:xx; fixed-address
> xxx.xxx.xxx.xxx; }
>
> >3) How I can change the MAC on my tablet.
>
> What is the OS on the tablet?
>
>
Hi Thanasis,
thanks for your help!
I didn't thought of "dynamically" assigning a fixed IP to
my tablet via DHCPd (my fault). But this is an elegant solution
for this!
The tablet runs Android Lollipop 5.0. The tablet is an
ASUS MeMO Pad 7 (ME176CX).
Best regards,
Meino
Re: [gentoo-user] To Wifi or not to Wifi...
J. Roeleveld [15-07-29 16:39]:
> On Wednesday, July 29, 2015 10:54:53 AM Thanasis wrote:
> > On 07/29/2015 05:42 AM, meino.cra...@gmx.de wrote:
> > <...snip...>
> >
> > > 2) How I can assign a static IP to my tablet.
> >
> > At the end of /etc/dhcp/dhcpd.conf add a line like
> >
> > host mytablet { hardware ethernet xx:xx:xx:xx:xx:xx; fixed-address
> > xxx.xxx.xxx.xxx; }
> >
> > > 3) How I can change the MAC on my tablet.
> >
> > What is the OS on the tablet?
>
> If I read this right in this thread, I believe it's Android Lollipop.
> In this case, without rooting, it definitely will not be possible.
>
> I don't see why anyone would want to change the MAC on a tablet, other then
> try to break into someone elses WIFI.
>
> --
> Joost
>
Hi Joost,
your are right: It is Android Lollipop 5.0 ! :)
I think specialists experienced in networks, Wlans, Wifis and
such know and are experienced in hacking into others devices. Changing
the MAC may or may not a tool for that ... I simply dont know. I am
just at the start to get Wifi working ... a very basic problem for
others like you I think. For me...it is just a challenge.
Are you experienced in breaking in someone elses WIFI via changing the
MAC? Where came your idea from?
Best regards,
Meino
Re: [gentoo-user] Wifi slow motion data transfer
J. Roeleveld [15-07-29 16:38]: > On Wednesday, July 29, 2015 05:18:25 AM meino.cra...@gmx.de wrote: > > Hi, > > > > the AP is now up and running ... but the the transfer rates are only > > about 80 Kb/sec (conky). > > > > I use an Atheros based USB wifi dongle, create_ap for setup and the > > internet connection goes via my PC. There are no other transfers > > running (check with wireshark), beside occassional dns and pop3 > > communications (very low data amounts) and the PC is nearly > > without load (ok...I am typing this email on it, but;) > > > > Any way to push this up...? > > > > Best regards > > Meino > > Which WIFI type are you using? > Which USB-type? (USB-1 is dead slow, for instance) > > Is this speed between both machines? Or to the internet? > > -- > Joost > Hi Joost, I fired up create_ip like this (just for testing and haveing at least ONE experienced succes with this Wifi stuff...): create_ap wlan0 eth1 How can I check for the type of WIFI after the connection has been established? USB is USB 2.0 The speed is measured by conky, which reads the transfer rate at eth0. At that tome, the tablet was getting a greater piece of tar archive (LInux for Android) and no other traffic other than this was there. The DSL was by far not saturated. So physically it is the speed of the internet but logically it is nearly identical to what happens at the Wifi interface (I think). I will check for an app which displays the speed measured on the tablets interface... Best regards, Meino
Re: [gentoo-user] Testing SSD? (Somewhat OT)
Am 29.07.2015 um 16:52 schrieb Daniel Frey: > On 07/28/2015 12:04 AM, Volker Armin Hemmann wrote: >> you know - this does not sound like ssd failure. Most SSDs bomb out by >> just becoming completely unacessible. >> >> dmesg errors? > Filled with /dev/sda errors when it "failed". oh the joy. > >> are you using ecc ram? > Nope. > >> if not - maybe, just maybe it is your ram at fault. The stuff the kernel >> sends and the stuff that end on the ssd might not be identical. >> > Ran memtest overnight on it, no errors. > > Dan > > > I had ram that passed memtest - and zfs detected errors. Went ecc ram, no more errors. With ram hammer as latest attack vector, ecc is even more worth its money.
[gentoo-user] Re: Wifi slow motion data transfer
gmx.de> writes: > > J. Roeleveld antarean.org> [15-07-29 16:38]: > > On Wednesday, July 29, 2015 05:18:25 AM Meino.Cramer gmx.de wrote: > > Is this speed between both machines? Or to the internet? Joost is exactly correct here. Test the links one connection at a time, not just all a once. You'll be able to get a 'sit of pants' feeling about the capabilities on each link (between devices). There are many many issues so let's first characterize each link by the bandwith. On ethernet interfaces this is a really cool tool:: net-analyzer/bwmon and net-analyzer/nbwmon > I fired up create_ip like this (just for testing and haveing at least > ONE experienced succes with this Wifi stuff...): > > create_ap wlan0 eth1 > > How can I check for the type of WIFI after the connection has been > established? 'ip link' and 'netstat -nr' are a good start. Later on we'll get you some gui tools and a monitoring software (a ton of options)... > USB is USB 2.0 > > The speed is measured by conky, which reads the transfer rate at eth0. > At that tome, the tablet was getting a greater piece of tar archive > (LInux for Android) and no other traffic other than this was there. > The DSL was by far not saturated. Really? How do you know. It take lots of experimenting and testing and data collection over time to figure our exactly what your ISp(s) are doing. Usually several ISPs are in a link until you hit a 'peering point' 'net-analyzer/traceroute' is your friend. At some point the ISPs will block traceroute info > So physically it is the speed of the internet but logically it is > nearly identical to what happens at the Wifi interface (I think). > I will check for an app which displays the speed measured on the > tablets interface... This is a very, very complicated issue. ISP(s) use devices to deliver and partition bandwidth; some with an incredible level of control (granularity). For instances they can 'port constrict' a service or a route to an endpoint or any number of things. So first fully study (characterize) the behavior of the links (connnections between devices) that you manage and develop that 'seat of pants' feeling about the network segments you manage. Then start sniffing up the outside folks, as best you can with the tools in the portage tree.(many). You need to also understand that Usb has it's own problems, protocols and issues depending on how it was implemented by the chipsets use and the firmware inside the product. Other protocol (latencies and such) are layered on top of that. Ju are 'full stack' wheelin and dealing as soon as your run gui apps across that link.brau. > Best regards, > Meino ttfn, Always your pal! James
Re: [gentoo-user] To Wifi or not to Wifi...
On Wednesday 29 Jul 2015 16:05:10 meino.cra...@gmx.de wrote:
> Thanasis [15-07-29 16:38]:
> > On 07/29/2015 05:42 AM, meino.cra...@gmx.de wrote:
> > <...snip...>
> >
> > >2) How I can assign a static IP to my tablet.
> >
> > At the end of /etc/dhcp/dhcpd.conf add a line like
> >
> > host mytablet { hardware ethernet xx:xx:xx:xx:xx:xx; fixed-address
> > xxx.xxx.xxx.xxx; }
> >
> > >3) How I can change the MAC on my tablet.
> >
> > What is the OS on the tablet?
>
> Hi Thanasis,
>
> thanks for your help!
> I didn't thought of "dynamically" assigning a fixed IP to
> my tablet via DHCPd (my fault). But this is an elegant solution
> for this!
If your client is running dhcpcd, then
--request 123.456.78.9 #will request this address from the server
--inform 123.456.78.9/24 #will inform the server of this address
> The tablet runs Android Lollipop 5.0. The tablet is an
> ASUS MeMO Pad 7 (ME176CX).
To set the IP address manually:
ifconfig wlan0 123.456.78.9
or
ip addr add 123.456.78.9 dev wlan0
depending on the commands that come with this distro.
To change the MAC address manually:
ifconfig wlan0 hw ether 00:AA:BB:CC:DD:FF
or
ip link set wlan0 address 00:AA:BB:CC:DD:FF
Reboot to get back what you had originally.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] trouble with wireless on new install
On Wednesday 29 Jul 2015 01:36:22 gottl...@nyu.edu wrote: > I am having trouble with wireless on a new install (gnome/systemd). > > lspci reports > 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) > > I looked this up and it requires the iwlwifi driver and iwlmvm, which I > enabled in the kernel (as modules). lsmod reports > Module Size Used by > iwlmvm142993 0 > mac80211 425803 1 iwlmvm > x86_pkg_temp_thermal 4567 0 > iwlwifi88075 1 iwlmvm > > I have merged linux-firmware and ls /lib/firmware/*7265* reports > /lib/firmware/iwlwifi-7265-10.ucode /lib/firmware/iwlwifi-7265-9.ucode > /lib/firmware/iwlwifi-7265-12.ucode > /lib/firmware/iwlwifi-7265D-10.ucode /lib/firmware/iwlwifi-7265-8.ucode > /lib/firmware/iwlwifi-7265D-12.ucode > > dmsg | grep iwl reports > [2.819953] iwlwifi :02:00.0: irq 48 for MSI/MSI-X > [2.824130] iwlwifi :02:00.0: loaded firmware version 23.11.10.0 > op_modeiwlmvm [2.836969] iwlwifi :02:00.0: Detected Intel(R) Dual > Band Wireless AC 7265, REV=0x210 [2.838620] iwlwifi :02:00.0: L1 > Disabled - LTR Enabled [2.838775] iwlwifi :02:00.0: L1 Disabled - > LTR Enabled [2.896168] ieee80211 phy0: Selected rate control algorithm > 'iwl-mvm-rs' [2.899325] iwlwifi :02:00.0 wlp2s0: renamed from > wlan0 > > The complaint seems to be "L1 disabled" > > NetworkManager started the wired network but failed with the wireless > E6430s ~ # systemctl -l status NetworkManager > ● NetworkManager.service - Network Manager >Loaded: loaded (/usr/lib64/systemd/system/NetworkManager.service; > enabled; vendor preset: enabled) Active: active (running) since Tue > 2015-07-28 19:56:57 EDT; 9min ago Main PID: 232 (NetworkManager) >CGroup: /system.slice/NetworkManager.service >├─232 /usr/sbin/NetworkManager --no-daemon >└─256 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf > /var/run/dhclient-eno1.pid -lf > /var/lib/NetworkManager/dhclient-0caab3d6-148f-416a-9906-547ed08596bf-eno1 > .lease -cf /var/lib/NetworkManager/dhclient-eno1.conf eno1 > > Jul 28 19:56:59 E6430s dhclient[256]: bound to 192.168.1.107 -- renewal in > 43096 seconds. Jul 28 19:56:59 E6430s NetworkManager[232]: > NetworkManager state is now CONNECTED_GLOBAL Jul 28 19:56:59 E6430s > NetworkManager[232]: Policy set 'Wired connection 1' (eno1) as > default for IPv4 routing and DNS. Jul 28 19:56:59 E6430s > NetworkManager[232]: (eno1): Activation: successful, device > activated. Jul 28 19:57:01 E6430s NetworkManager[232]: (wlp2s0): > supplicant interface state: disconnected -> inactive Jul 28 19:57:05 > E6430s NetworkManager[232]: startup complete Jul 28 19:57:31 > E6430s NetworkManager[232]: (eno1): Activation: Stage 4 of 5 (IPv6 > Configure Timeout) scheduled... Jul 28 19:57:31 E6430s > NetworkManager[232]: (eno1): Activation: Stage 4 of 5 (IPv6 > Configure Timeout) started... Jul 28 19:57:31 E6430s NetworkManager[232]: > (eno1): Activation: Stage 4 of 5 (IPv6 Configure Timeout) > complete. Jul 28 19:57:57 E6430s NetworkManager[232]: (wlp2s0): > supplicant interface state: inactive -> scanning > > What step did I forget? > > thanks in advance, > allan There are reports of driver problems, so you may not have forgotten anything. Usual suggestion is to run the latest kernel and firmware, but I don't have this card to know more about it. What happens after the 'inactive -> scanning' step above? Have you tried to disconnect the wired ethernet connection and wait a bit longer for the wireless? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Wifi slow motion data transfer
James [15-07-29 19:46]: > gmx.de> writes: > > > > > J. Roeleveld antarean.org> [15-07-29 16:38]: > > > On Wednesday, July 29, 2015 05:18:25 AM Meino.Cramer gmx.de wrote: > > > > Is this speed between both machines? Or to the internet? > > Joost is exactly correct here. Test the links one connection at > a time, not just all a once. You'll be able to get a 'sit of pants' feeling > about the capabilities on each link (between devices). There are many many > issues so let's first characterize each link by the bandwith. > > > On ethernet interfaces this is a really cool tool:: > > net-analyzer/bwmon and net-analyzer/nbwmon > > > I fired up create_ip like this (just for testing and haveing at least > > ONE experienced succes with this Wifi stuff...): > > > > create_ap wlan0 eth1 > > > > How can I check for the type of WIFI after the connection has been > > established? > > 'ip link' and 'netstat -nr' are a good start. Later on we'll get > you some gui tools and a monitoring software (a ton of options)... > > > > USB is USB 2.0 > > > > The speed is measured by conky, which reads the transfer rate at eth0. > > At that tome, the tablet was getting a greater piece of tar archive > > (LInux for Android) and no other traffic other than this was there. > > The DSL was by far not saturated. > > Really? How do you know. It take lots of experimenting and testing > and data collection over time to figure our exactly what your > ISp(s) are doing. Usually several ISPs are in a link until you hit > a 'peering point' > > 'net-analyzer/traceroute' > > is your friend. At some point the ISPs will block traceroute info > > > > So physically it is the speed of the internet but logically it is > > nearly identical to what happens at the Wifi interface (I think). > > I will check for an app which displays the speed measured on the > > tablets interface... > > This is a very, very complicated issue. ISP(s) use devices to deliver > and partition bandwidth; some with an incredible level of control > (granularity). For instances they can 'port constrict' a service > or a route to an endpoint or any number of things. So first fully > study (characterize) the behavior of the links (connnections between > devices) that you manage and develop that 'seat of pants' feeling about the > network segments you manage. Then start sniffing up the outside folks, > as best you can with the tools in the portage tree.(many). > > > You need to also understand that Usb has it's own problems, protocols and > issues depending on how it was implemented by the chipsets use and the > firmware inside the product. Other protocol (latencies and such) are layered > on top of that. Ju are 'full stack' wheelin and dealing as soon > as your run gui apps across that link.brau. > > > > Best regards, > > Meino > > ttfn, > Always your pal! > James > Hi James, :) The solution was as simple as follows: I did this: ./create_ap wlan0 eth1 and I was happy to have my first access point created... that one which seems to use morse code to transfer data. That was yesterday evenining. The I heard of different protocols from which one was old and slow and others speedy and "newer" Then I did this (a few miniutes ago): ./create_ap --ieee80211n wlan0 eth1 And TADA! the internet transfer rate measured with conky (as mentioned before) jumps from 80Kb/sec up to the most my DSL can delver (which is not that much, since I have choosen a cheap low end of transfer rates possible from my DSL provider. NOW the linux installation on my Android tablet show real progress (and fails for other reasons, I currently dont have figured out). I am happy with the result - except for the non working Linux installation, which is another problem...unfortunately I dont speak a single word Russian and the forum of the Android Installation tool is Russian spoken... We will see, James. Thank you very much for your detailed help!!! 8) Best regards, Meino
Re: [gentoo-user] To Wifi or not to Wifi...
Mick [15-07-29 20:08]:
> On Wednesday 29 Jul 2015 16:05:10 meino.cra...@gmx.de wrote:
> > Thanasis [15-07-29 16:38]:
> > > On 07/29/2015 05:42 AM, meino.cra...@gmx.de wrote:
> > > <...snip...>
> > >
> > > >2) How I can assign a static IP to my tablet.
> > >
> > > At the end of /etc/dhcp/dhcpd.conf add a line like
> > >
> > > host mytablet { hardware ethernet xx:xx:xx:xx:xx:xx; fixed-address
> > > xxx.xxx.xxx.xxx; }
> > >
> > > >3) How I can change the MAC on my tablet.
> > >
> > > What is the OS on the tablet?
> >
> > Hi Thanasis,
> >
> > thanks for your help!
> > I didn't thought of "dynamically" assigning a fixed IP to
> > my tablet via DHCPd (my fault). But this is an elegant solution
> > for this!
>
> If your client is running dhcpcd, then
>
> --request 123.456.78.9 #will request this address from the server
>
> --inform 123.456.78.9/24 #will inform the server of this address
>
>
> > The tablet runs Android Lollipop 5.0. The tablet is an
> > ASUS MeMO Pad 7 (ME176CX).
>
> To set the IP address manually:
>
> ifconfig wlan0 123.456.78.9
>
> or
>
> ip addr add 123.456.78.9 dev wlan0
>
> depending on the commands that come with this distro.
>
>
> To change the MAC address manually:
>
> ifconfig wlan0 hw ether 00:AA:BB:CC:DD:FF
>
> or
>
> ip link set wlan0 address 00:AA:BB:CC:DD:FF
>
>
> Reboot to get back what you had originally.
>
> --
> Regards,
> Mick
Hi Mick,
!!!GREAT!!! Exactly what I am searching for! BEST!
Thank you VERY much! :) 8)
Best regards,
Meino
Re: [gentoo-user] Re: Wifi slow motion data transfer
On Wednesday 29 Jul 2015 18:38:07 James wrote: > gmx.de> writes: > > J. Roeleveld antarean.org> [15-07-29 16:38]: > > > On Wednesday, July 29, 2015 05:18:25 AM Meino.Cramer gmx.de wrote: > > > > > > Is this speed between both machines? Or to the internet? > > Joost is exactly correct here. Test the links one connection at > a time, not just all a once. You'll be able to get a 'sit of pants' feeling > about the capabilities on each link (between devices). There are many many > issues so let's first characterize each link by the bandwith. > > > On ethernet interfaces this is a really cool tool:: > > net-analyzer/bwmon and net-analyzer/nbwmon > > > I fired up create_ip like this (just for testing and haveing at least > > ONE experienced succes with this Wifi stuff...): > > > > create_ap wlan0 eth1 > > > > How can I check for the type of WIFI after the connection has been > > established? > > 'ip link' and 'netstat -nr' are a good start. Later on we'll get > you some gui tools and a monitoring software (a ton of options)... > > > USB is USB 2.0 > > > > The speed is measured by conky, which reads the transfer rate at eth0. > > At that tome, the tablet was getting a greater piece of tar archive > > (LInux for Android) and no other traffic other than this was there. > > The DSL was by far not saturated. > > Really? How do you know. It take lots of experimenting and testing > and data collection over time to figure our exactly what your > ISp(s) are doing. Usually several ISPs are in a link until you hit > a 'peering point' > > 'net-analyzer/traceroute' > > is your friend. At some point the ISPs will block traceroute info > > > So physically it is the speed of the internet but logically it is > > nearly identical to what happens at the Wifi interface (I think). > > I will check for an app which displays the speed measured on the > > tablets interface... > > This is a very, very complicated issue. ISP(s) use devices to deliver > and partition bandwidth; some with an incredible level of control > (granularity). For instances they can 'port constrict' a service > or a route to an endpoint or any number of things. So first fully > study (characterize) the behavior of the links (connnections between > devices) that you manage and develop that 'seat of pants' feeling about the > network segments you manage. Then start sniffing up the outside folks, > as best you can with the tools in the portage tree.(many). > > > You need to also understand that Usb has it's own problems, protocols and > issues depending on how it was implemented by the chipsets use and the > firmware inside the product. Other protocol (latencies and such) are > layered on top of that. Ju are 'full stack' wheelin and dealing as soon > as your run gui apps across that link.brau. > > > Best regards, > > Meino > > ttfn, > Always your pal! > James It could also be that the tablet has a slow write speed, if you were downloading a file. Can you stream a video instead and see if this is achieving a higher speed? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] trouble with wireless on new install
Please see the addendum at the end. On Tue, Jul 28 2015, gottl...@nyu.edu wrote: > I am having trouble with wireless on a new install (gnome/systemd). > > lspci reports > 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) > > I looked this up and it requires the iwlwifi driver and iwlmvm, which I > enabled in the kernel (as modules). > lsmod reports > Module Size Used by > iwlmvm142993 0 > mac80211 425803 1 iwlmvm > x86_pkg_temp_thermal 4567 0 > iwlwifi88075 1 iwlmvm > > I have merged linux-firmware and ls /lib/firmware/*7265* reports > /lib/firmware/iwlwifi-7265-10.ucode /lib/firmware/iwlwifi-7265-9.ucode > /lib/firmware/iwlwifi-7265-12.ucode /lib/firmware/iwlwifi-7265D-10.ucode > /lib/firmware/iwlwifi-7265-8.ucode /lib/firmware/iwlwifi-7265D-12.ucode > > dmsg | grep iwl reports > [2.819953] iwlwifi :02:00.0: irq 48 for MSI/MSI-X > [2.824130] iwlwifi :02:00.0: loaded firmware version 23.11.10.0 > op_modeiwlmvm > [2.836969] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless > AC 7265, REV=0x210 > [2.838620] iwlwifi :02:00.0: L1 Disabled - LTR Enabled > [2.838775] iwlwifi :02:00.0: L1 Disabled - LTR Enabled > [2.896168] ieee80211 phy0: Selected rate control algorithm > 'iwl-mvm-rs' > [2.899325] iwlwifi :02:00.0 wlp2s0: renamed from wlan0 > > The complaint seems to be "L1 disabled" > > NetworkManager started the wired network but failed with the wireless > E6430s ~ # systemctl -l status NetworkManager > ● NetworkManager.service - Network Manager >Loaded: loaded (/usr/lib64/systemd/system/NetworkManager.service; enabled; > vendor preset: enabled) >Active: active (running) since Tue 2015-07-28 19:56:57 EDT; 9min ago > Main PID: 232 (NetworkManager) >CGroup: /system.slice/NetworkManager.service >├─232 /usr/sbin/NetworkManager --no-daemon >└─256 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf > /var/run/dhclient-eno1.pid -lf > /var/lib/NetworkManager/dhclient-0caab3d6-148f-416a-9906-547ed08596bf-eno1.lease > -cf /var/lib/NetworkManager/dhclient-eno1.conf eno1 > > Jul 28 19:56:59 E6430s dhclient[256]: bound to 192.168.1.107 -- renewal in > 43096 seconds. > Jul 28 19:56:59 E6430s NetworkManager[232]: NetworkManager state is > now CONNECTED_GLOBAL > Jul 28 19:56:59 E6430s NetworkManager[232]: Policy set 'Wired > connection 1' (eno1) as default for IPv4 routing and DNS. > Jul 28 19:56:59 E6430s NetworkManager[232]: (eno1): Activation: > successful, device activated. > Jul 28 19:57:01 E6430s NetworkManager[232]: (wlp2s0): supplicant > interface state: disconnected -> inactive > Jul 28 19:57:05 E6430s NetworkManager[232]: startup complete > Jul 28 19:57:31 E6430s NetworkManager[232]: (eno1): Activation: Stage > 4 of 5 (IPv6 Configure Timeout) scheduled... > Jul 28 19:57:31 E6430s NetworkManager[232]: (eno1): Activation: Stage > 4 of 5 (IPv6 Configure Timeout) started... > Jul 28 19:57:31 E6430s NetworkManager[232]: (eno1): Activation: Stage > 4 of 5 (IPv6 Configure Timeout) complete. > Jul 28 19:57:57 E6430s NetworkManager[232]: (wlp2s0): supplicant > interface state: inactive -> scanning > > What step did I forget? > > thanks in advance, > allan I should have mentioned that I installed linux on this machine last week and the wifi worked as soon as I built the correct driver (iwlwifi + iwlmvm). Dual booting windows poorly I made the system unbootable. So I reinstalled again (windows first) and everything is working except wifi
Re: [gentoo-user] Re: Wifi slow motion data transfer
Mick [15-07-29 20:16]: > On Wednesday 29 Jul 2015 18:38:07 James wrote: > > gmx.de> writes: > > > J. Roeleveld antarean.org> [15-07-29 16:38]: > > > > On Wednesday, July 29, 2015 05:18:25 AM Meino.Cramer gmx.de wrote: > > > > > > > > Is this speed between both machines? Or to the internet? > > > > Joost is exactly correct here. Test the links one connection at > > a time, not just all a once. You'll be able to get a 'sit of pants' feeling > > about the capabilities on each link (between devices). There are many many > > issues so let's first characterize each link by the bandwith. > > > > > > On ethernet interfaces this is a really cool tool:: > > > > net-analyzer/bwmon and net-analyzer/nbwmon > > > > > I fired up create_ip like this (just for testing and haveing at least > > > ONE experienced succes with this Wifi stuff...): > > > > > > create_ap wlan0 eth1 > > > > > > How can I check for the type of WIFI after the connection has been > > > established? > > > > 'ip link' and 'netstat -nr' are a good start. Later on we'll get > > you some gui tools and a monitoring software (a ton of options)... > > > > > USB is USB 2.0 > > > > > > The speed is measured by conky, which reads the transfer rate at eth0. > > > At that tome, the tablet was getting a greater piece of tar archive > > > (LInux for Android) and no other traffic other than this was there. > > > The DSL was by far not saturated. > > > > Really? How do you know. It take lots of experimenting and testing > > and data collection over time to figure our exactly what your > > ISp(s) are doing. Usually several ISPs are in a link until you hit > > a 'peering point' > > > > 'net-analyzer/traceroute' > > > > is your friend. At some point the ISPs will block traceroute info > > > > > So physically it is the speed of the internet but logically it is > > > nearly identical to what happens at the Wifi interface (I think). > > > I will check for an app which displays the speed measured on the > > > tablets interface... > > > > This is a very, very complicated issue. ISP(s) use devices to deliver > > and partition bandwidth; some with an incredible level of control > > (granularity). For instances they can 'port constrict' a service > > or a route to an endpoint or any number of things. So first fully > > study (characterize) the behavior of the links (connnections between > > devices) that you manage and develop that 'seat of pants' feeling about the > > network segments you manage. Then start sniffing up the outside folks, > > as best you can with the tools in the portage tree.(many). > > > > > > You need to also understand that Usb has it's own problems, protocols and > > issues depending on how it was implemented by the chipsets use and the > > firmware inside the product. Other protocol (latencies and such) are > > layered on top of that. Ju are 'full stack' wheelin and dealing as soon > > as your run gui apps across that link.brau. > > > > > Best regards, > > > Meino > > > > ttfn, > > Always your pal! > > James > > It could also be that the tablet has a slow write speed, if you were > downloading a file. Can you stream a video instead and see if this is > achieving a higher speed? > > -- > Regards, > Mick Hi Mick, thanks for your infos! :) yupp! Works like a charm (video streaming)! It was a default setting in create_ap which seems to select an old procotol based on drums and morse code... ;) After adding --ieee80211n to the commandline the problem vanished and the data transfer rate jumps up to a level, where the limiting device was my DSL provider :) I am happy with that now ! Best regards, Meino
Re: [gentoo-user] trouble with wireless on new install
On Wed, Jul 29 2015, Mick wrote:
> On Wednesday 29 Jul 2015 01:36:22 gottl...@nyu.edu wrote:
>> I am having trouble with wireless on a new install (gnome/systemd).
>>
>> lspci reports
>> 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
>>
>> I looked this up and it requires the iwlwifi driver and iwlmvm, which I
>> enabled in the kernel (as modules). lsmod reports
>> Module Size Used by
>> iwlmvm142993 0
>> mac80211 425803 1 iwlmvm
>> x86_pkg_temp_thermal 4567 0
>> iwlwifi88075 1 iwlmvm
>>
>> I have merged linux-firmware and ls /lib/firmware/*7265* reports
>> /lib/firmware/iwlwifi-7265-10.ucode /lib/firmware/iwlwifi-7265-9.ucode
>> /lib/firmware/iwlwifi-7265-12.ucode
>> /lib/firmware/iwlwifi-7265D-10.ucode /lib/firmware/iwlwifi-7265-8.ucode
>> /lib/firmware/iwlwifi-7265D-12.ucode
>>
>> dmsg | grep iwl reports
>> [2.819953] iwlwifi :02:00.0: irq 48 for MSI/MSI-X
>> [2.824130] iwlwifi :02:00.0: loaded firmware version 23.11.10.0
>> op_modeiwlmvm [2.836969] iwlwifi :02:00.0: Detected Intel(R) Dual
>> Band Wireless AC 7265, REV=0x210 [2.838620] iwlwifi :02:00.0: L1
>> Disabled - LTR Enabled [2.838775] iwlwifi :02:00.0: L1 Disabled -
>> LTR Enabled [2.896168] ieee80211 phy0: Selected rate control algorithm
>> 'iwl-mvm-rs' [2.899325] iwlwifi :02:00.0 wlp2s0: renamed from
>> wlan0
>>
>> The complaint seems to be "L1 disabled"
>>
>> NetworkManager started the wired network but failed with the wireless
>> E6430s ~ # systemctl -l status NetworkManager
>> ● NetworkManager.service - Network Manager
>>Loaded: loaded (/usr/lib64/systemd/system/NetworkManager.service;
>> enabled; vendor preset: enabled) Active: active (running) since Tue
>> 2015-07-28 19:56:57 EDT; 9min ago Main PID: 232 (NetworkManager)
>>CGroup: /system.slice/NetworkManager.service
>>├─232 /usr/sbin/NetworkManager --no-daemon
>>└─256 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf
>> /var/run/dhclient-eno1.pid -lf
>> /var/lib/NetworkManager/dhclient-0caab3d6-148f-416a-9906-547ed08596bf-eno1
>> .lease -cf /var/lib/NetworkManager/dhclient-eno1.conf eno1
>>
>> Jul 28 19:56:59 E6430s dhclient[256]: bound to 192.168.1.107 -- renewal in
>> 43096 seconds. Jul 28 19:56:59 E6430s NetworkManager[232]:
>> NetworkManager state is now CONNECTED_GLOBAL Jul 28 19:56:59 E6430s
>> NetworkManager[232]: Policy set 'Wired connection 1' (eno1) as
>> default for IPv4 routing and DNS. Jul 28 19:56:59 E6430s
>> NetworkManager[232]: (eno1): Activation: successful, device
>> activated. Jul 28 19:57:01 E6430s NetworkManager[232]: (wlp2s0):
>> supplicant interface state: disconnected -> inactive Jul 28 19:57:05
>> E6430s NetworkManager[232]: startup complete Jul 28 19:57:31
>> E6430s NetworkManager[232]: (eno1): Activation: Stage 4 of 5 (IPv6
>> Configure Timeout) scheduled... Jul 28 19:57:31 E6430s
>> NetworkManager[232]: (eno1): Activation: Stage 4 of 5 (IPv6
>> Configure Timeout) started... Jul 28 19:57:31 E6430s NetworkManager[232]:
>> (eno1): Activation: Stage 4 of 5 (IPv6 Configure Timeout)
>> complete. Jul 28 19:57:57 E6430s NetworkManager[232]: (wlp2s0):
>> supplicant interface state: inactive -> scanning
>>
>> What step did I forget?
>>
>> thanks in advance,
>> allan
>
> There are reports of driver problems, so you may not have forgotten anything.
>
> Usual suggestion is to run the latest kernel and firmware, but I don't have
> this card to know more about it. What happens after the 'inactive ->
> scanning' step above? Have you tried to disconnect the wired ethernet
> connection and wait a bit longer for the wireless?
I just wrote an addendum that crossed in the mail with your msg. This
kernel with these drivers worked last week. I just noticed that I
didn't have an /etc/wpa_supplicant so added the same trivial one I have
on my current machine
# The below line not be changed otherwise we refuse to work
ctrl_interface=/var/run/wpa_supplicant
network={
key_mgmt=NONE
priority=-999
}
Unplugging the wired enet didn't help (I waited a minute).
The trivial /etc/wpa_supplicant/wpa_supplicant.conf had no effect.
It looks strange. dmesg shows the iwlwifi driver responding,
recognizing the card, and loading the microcode using iwlmvm (see above)
What does L1 disabled mean? I googled and found other getting that msg
but no explanation of what it means.
thanks,
allan
Re: [gentoo-user] trouble with wireless on new install
On Tue, Jul 28 2015, Meino Cramer wrote: > > Hi Allan, > > I just in the beginning of "doing wifi" (see previous thread...) but > may be this is of help: > > https://bugzilla.kernel.org/show_bug.cgi?id=92541 > http://forums.fedoraforum.org/showthread.php?t=301637 > http://askubuntu.com/questions/616119/unstable-wireless-with-intel-7260-iwlwifi-after-upgrade-to-15-04 > > HTH! > Good luck! > Best regards, > Meino Thank you. I will track those references. allan
[gentoo-user] Solved: trouble with wireless on new install
I don't know what fixed it. I did add a trivial
/etc/wpa_supplicant/wpa_supplicant.conf
# The below line not be changed otherwise we refuse to work
ctrl_interface=/var/run/wpa_supplicant
network={
key_mgmt=NONE
priority=-999
}
But it might have been that I never went to the gui screen (gnome) and
selected the unencrypted access point.
Anyway, I just rebooted and wireless works fine.
Thanks for the help/encouragement.
allan
Re: [gentoo-user] Testing SSD? (Somewhat OT)
On 07/29/2015 08:34 AM, Volker Armin Hemmann wrote: > Am 29.07.2015 um 16:52 schrieb Daniel Frey: >> On 07/28/2015 12:04 AM, Volker Armin Hemmann wrote: >>> you know - this does not sound like ssd failure. Most SSDs bomb out by >>> just becoming completely unacessible. >>> >>> dmesg errors? >> Filled with /dev/sda errors when it "failed". > > oh the joy. Yeah. I don't remember what the exact error message was, other than it was filled with "can't read" and "can't write" in the messages. Booting from USB worked fine. Compiling while booted from USB worked until I chroot'ed to the failed SSD. Then a bunch of segfaults and other weird errors. I've seen this before both at home and work, where SSDs do this with no warning. IMO they're way too unreliable. I don't have one in my server or workstation at home. I had one in my server and it lasted two years before similar issues above. It (server SSD) was replaced with a spinning disk 3 years ago and it's still running today. I'm pretty sure if I replaced it with another SSD it would've failed already. > >> >>> are you using ecc ram? >> Nope. >> >>> if not - maybe, just maybe it is your ram at fault. The stuff the kernel >>> sends and the stuff that end on the ssd might not be identical. >>> >> Ran memtest overnight on it, no errors. >> >> Dan >> >> >> > > I had ram that passed memtest - and zfs detected errors. Went ecc ram, > no more errors. > > With ram hammer as latest attack vector, ecc is even more worth its money. > ECC is fine and dandy, but this motherboard doesn't support it. It's a desktop board from 2008. All it does is a frontend for mythtv, nothing else. Dan
Re: [gentoo-user] trouble with wireless on new install
On Wednesday 29 Jul 2015 19:35:57 gottl...@nyu.edu wrote:
> On Wed, Jul 29 2015, Mick wrote:
> > On Wednesday 29 Jul 2015 01:36:22 gottl...@nyu.edu wrote:
> >> I am having trouble with wireless on a new install (gnome/systemd).
> >>
> >> lspci reports
> >>
> >> 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
> >>
> >> I looked this up and it requires the iwlwifi driver and iwlmvm, which I
> >> enabled in the kernel (as modules). lsmod reports
> >>
> >> Module Size Used by
> >> iwlmvm142993 0
> >> mac80211 425803 1 iwlmvm
> >> x86_pkg_temp_thermal 4567 0
> >> iwlwifi88075 1 iwlmvm
> >>
> >> I have merged linux-firmware and ls /lib/firmware/*7265* reports
> >>
> >> /lib/firmware/iwlwifi-7265-10.ucode
> >> /lib/firmware/iwlwifi-7265-9.ucode
> >> /lib/firmware/iwlwifi-7265-12.ucode
> >>
> >> /lib/firmware/iwlwifi-7265D-10.ucode /lib/firmware/iwlwifi-7265-8.ucode
> >> /lib/firmware/iwlwifi-7265D-12.ucode
> >>
> >> dmsg | grep iwl reports
> >>
> >> [2.819953] iwlwifi :02:00.0: irq 48 for MSI/MSI-X
> >> [2.824130] iwlwifi :02:00.0: loaded firmware version
> >> 23.11.10.0
> >>
> >> op_modeiwlmvm [2.836969] iwlwifi :02:00.0: Detected Intel(R)
> >> Dual Band Wireless AC 7265, REV=0x210 [2.838620] iwlwifi
> >> :02:00.0: L1 Disabled - LTR Enabled [2.838775] iwlwifi
> >> :02:00.0: L1 Disabled - LTR Enabled [2.896168] ieee80211 phy0:
> >> Selected rate control algorithm 'iwl-mvm-rs' [2.899325] iwlwifi
> >> :02:00.0 wlp2s0: renamed from wlan0
> >>
> >> The complaint seems to be "L1 disabled"
> >>
> >> NetworkManager started the wired network but failed with the wireless
> >> E6430s ~ # systemctl -l status NetworkManager
> >> ● NetworkManager.service - Network Manager
> >>
> >>Loaded: loaded (/usr/lib64/systemd/system/NetworkManager.service;
> >>
> >> enabled; vendor preset: enabled) Active: active (running) since Tue
> >> 2015-07-28 19:56:57 EDT; 9min ago Main PID: 232 (NetworkManager)
> >>
> >>CGroup: /system.slice/NetworkManager.service
> >>
> >>├─232 /usr/sbin/NetworkManager --no-daemon
> >>└─256 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper
> >>-pf
> >>
> >> /var/run/dhclient-eno1.pid -lf
> >> /var/lib/NetworkManager/dhclient-0caab3d6-148f-416a-9906-547ed08596bf-en
> >> o1 .lease -cf /var/lib/NetworkManager/dhclient-eno1.conf eno1
> >>
> >> Jul 28 19:56:59 E6430s dhclient[256]: bound to 192.168.1.107 -- renewal
> >> in 43096 seconds. Jul 28 19:56:59 E6430s NetworkManager[232]:
> >> NetworkManager state is now CONNECTED_GLOBAL Jul 28 19:56:59 E6430s
> >> NetworkManager[232]: Policy set 'Wired connection 1' (eno1) as
> >> default for IPv4 routing and DNS. Jul 28 19:56:59 E6430s
> >> NetworkManager[232]: (eno1): Activation: successful, device
> >> activated. Jul 28 19:57:01 E6430s NetworkManager[232]: (wlp2s0):
> >> supplicant interface state: disconnected -> inactive Jul 28 19:57:05
> >> E6430s NetworkManager[232]: startup complete Jul 28 19:57:31
> >> E6430s NetworkManager[232]: (eno1): Activation: Stage 4 of 5
> >> (IPv6 Configure Timeout) scheduled... Jul 28 19:57:31 E6430s
> >> NetworkManager[232]: (eno1): Activation: Stage 4 of 5 (IPv6
> >> Configure Timeout) started... Jul 28 19:57:31 E6430s
> >> NetworkManager[232]: (eno1): Activation: Stage 4 of 5 (IPv6
> >> Configure Timeout) complete. Jul 28 19:57:57 E6430s
> >> NetworkManager[232]: (wlp2s0): supplicant interface state:
> >> inactive -> scanning
> >>
> >> What step did I forget?
> >>
> >> thanks in advance,
> >> allan
> >
> > There are reports of driver problems, so you may not have forgotten
> > anything. Usual suggestion is to run the latest kernel and firmware, but
> > I don't have this card to know more about it. What happens after the
> > 'inactive -> scanning' step above? Have you tried to disconnect the
> > wired ethernet connection and wait a bit longer for the wireless?
>
> I just wrote an addendum that crossed in the mail with your msg. This
> kernel with these drivers worked last week. I just noticed that I
> didn't have an /etc/wpa_supplicant so added the same trivial one I have
> on my current machine
> # The below line not be changed otherwise we refuse to work
> ctrl_interface=/var/run/wpa_supplicant
>
> network={
> key_mgmt=NONE
> priority=-999
> }
> Unplugging the wired enet didn't help (I waited a minute).
> The trivial /etc/wpa_supplicant/wpa_supplicant.conf had no effect.
I assume that you had restarted your wireless interface?
> It looks strange. dmesg shows the iwlwifi driver responding,
> recognizing the card, and loading the microcode using iwlmvm (see above)
> What does L1 disabled mean? I googled and found other getting that msg
> but no explanation of what it means.
>
> thanks,
> allan
I think (but
Re: [gentoo-user] trouble with wireless on new install
On Wed, Jul 29 2015, Mick wrote: > I think (but not sure) that L1 is a legacy power management feature of > PCIe. LTR is a more dynamic, latency based, power management > standard, which auto- adjusts the power on the device depending on how > long it takes to wake up. L1 on its own would consume more of your > battery (if it is a laptop), with LTR it would switch off the power of > parts of the circuit so as to avoid exceeding the latency requirement > of the device (not all devices take the same time to wake up). > > Could it be that MSWindows has set up on the hardware some aggressive power > management setting, which Linux cannot wake up the device from? > > Two things I would try: > > 1. In Linux - modinfo > > Check what options this gives and tweak the power settings accordingly > as your modprobe it, or add it in /etc/modprobe.d/.conf. > Also check the relevant kernel documentation in case it gives more > details. > > 2. In MSWindows - Device Manager > > Go into the Hardware/Device Manager and check the different tabs of > the driver. Make a note of the original settings and then tweak the > power settings so that the device does not go to sleep. Reboot into > MSWindows (for good luck) and then boot into Linux. > > Eventually, a more up to date driver ought to deal with this, if all my > suggestions fail. > > HTH. It looks like I must have made a simple mistake, perhaps not pointing network manager at the ssid of my router. All is well now. thanks again for your help. I appreciate it. allan
Re: [gentoo-user] Testing SSD? (Somewhat OT)
Am 29.07.2015 um 22:57 schrieb Daniel Frey: > On 07/29/2015 08:34 AM, Volker Armin Hemmann wrote: >> Am 29.07.2015 um 16:52 schrieb Daniel Frey: >>> On 07/28/2015 12:04 AM, Volker Armin Hemmann wrote: you know - this does not sound like ssd failure. Most SSDs bomb out by just becoming completely unacessible. dmesg errors? >>> Filled with /dev/sda errors when it "failed". >> oh the joy. > Yeah. I don't remember what the exact error message was, other than it > was filled with "can't read" and "can't write" in the messages. > > Booting from USB worked fine. Compiling while booted from USB worked > until I chroot'ed to the failed SSD. Then a bunch of segfaults and other > weird errors. > > I've seen this before both at home and work, where SSDs do this with no > warning. IMO they're way too unreliable. I don't have one in my server > or workstation at home. I had one in my server and it lasted two years > before similar issues above. It (server SSD) was replaced with a > spinning disk 3 years ago and it's still running today. I'm pretty sure > if I replaced it with another SSD it would've failed already. > are you using ecc ram? >>> Nope. >>> if not - maybe, just maybe it is your ram at fault. The stuff the kernel sends and the stuff that end on the ssd might not be identical. >>> Ran memtest overnight on it, no errors. >>> >>> Dan >>> >>> >>> >> I had ram that passed memtest - and zfs detected errors. Went ecc ram, >> no more errors. >> >> With ram hammer as latest attack vector, ecc is even more worth its money. >> > ECC is fine and dandy, but this motherboard doesn't support it. It's a > desktop board from 2008. All it does is a frontend for mythtv, nothing else. > > > > Dan > > are you sure? Asus boards usually support ECC (at least their AMD boards do) and many Gigabyte boards support ECC without telling about it (gigabyte user forums can usually answer that).
Re: [gentoo-user] Testing SSD? (Somewhat OT)
On 07/29/2015 04:55 PM, Volker Armin Hemmann wrote: > are you sure? Asus boards usually support ECC (at least their AMD boards > do) and many Gigabyte boards support ECC without telling about it > (gigabyte user forums can usually answer that). > Hmm, I went and looked some more into this, but all I found was support for non-ECC RAM. Both in my manual & online reflect this. The board I have is an Asus P5QL-E. Adding to that - 4GB of ECC budget RAM for my board is $200 here. I'm not about to spend that on an almost 8 year old machine. If it was $40 I'd try it, but not for $200. Dan
