bionic mini.iso dhcp falls

Bug #1748409 reported by gregrwm
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

dhcp works fine once xenial or bionic are installed, and the mini.iso manual network configuration works, but the mini.iso dhcp fails. the mini.iso was downloaded last night.

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1748409/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
gregrwm (gregrwm) wrote :

no surprise the installed bionic uses the same static ip address i gave for the mini.iso to use. same issue on desktop and laptop. for the desktop i expect i can just populate /etc/network/interfaces and uninstall NetworkManager. i don't think that's a good solution for the lappy tho. can anybody clue me to a workaround, to fix/complete my laptop bionic configuration? i think ssb is the broadcom wifi driver module, when running bionic it's already listed in lsmod but only eth0 shows up in the network applet or /sys/class/net, when running trusty the lappy wifi works, APs are listed and it connects to my modem just fine, seems likely i can just copy some missing bit of configuration from the trusty install, but what?

Revision history for this message
gregrwm (gregrwm) wrote :
Download full text (11.1 KiB)

i'm looking for a workaround.

retracing my steps, i try the full iso again, but i guess the fire's gone out of my cdburner:
$ cdrecord bionic-desktop-amd64.iso
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
Device was not specified. Trying to find an appropriate drive...
Looking for a DVD-R drive to store 1431.56 MiB...
Detected DVD-R drive: /dev/dvdrw
Using /dev/cdrom of unknown capabilities
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'TSSTcorp'
Identification : 'DVD+-RW TS-L633C'
Revision : 'D300'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd).
Driver flags : SWABAUDIO BURNFREE
Supported modes: PACKET SAO
Speed set to 11080 KB/s
Starting to write CD/DVD at speed 8.0 in real unknown mode for single session.
Last chance to quit, starting real write in 0 seconds. Operation starts.
Errno: 5 (Input/output error), reserve track scsi sendcmd: no error
CDB: 53 00 00 00 00 00 0B 2F 20 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 05 21 04 00 00 00 0E 09 0C 00 00 00 03 00 00
Sense Key: 0x1 Recovered Error, Segment 5
Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
Sense flags: Blk 67108864 (not valid) illegal block length
cmd finished after 40.725s timeout 40s
wodim: Cannot open new session.
$

well, so, that's what the mini.iso is for, right? as an alternative installation method.

so, but, the bionic mini.iso dhcp fails, tho manual network configuration works, and thus mini.iso installs a static ip configuration. well, on my desktop, i want a dhcp configuration. i figure why not just drop back to the simple way it was done before network manager, so, i uninstalled wpasupplicant, which took network manager out with it:
 Start-Date: 2018-02-20 12:41:02
 Commandline: apt-get --auto-remove purge wpasupplicant
 Purge: network-manager-pptp:amd64 (1.2.4-4), iputils-arping:amd64 (3:20161105-1ubuntu2), pptp-linux:amd64 (1.9.0+ds-2), dnsmasq-base:amd64 (2.78-1), network-manager-gnome:amd64 (1.8.10-2ubuntu1), network-manager :amd64 (1.8.4-1ubuntu4), lubuntu-desktop:amd64 (0.90), lubuntu-gtk-desktop:amd64 (0.90), wpasupplicant:amd64 (2:2.6-15ubuntu1), dns-root-data:amd64 (2018013001)
 End-Date: 2018-02-20 12:41:24

and edited /etc/network/interfaces to contain:
 auto lo
 iface lo inet loopback

 auto enp0s25
 iface enp0s25 inet dhcp

and there's nothing in /etc/udev/rules.d

clearly it still needs something, it boots up like this:
$ ip a
 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
        valid_lft forever preferred_lft forever
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
 2: enp0s25: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
     link/ether 00:21:70:32:6a:ee brd ff:ff:ff:ff:ff:ff

and i find these matches for either "eth" or "enp" in /var/log/sys...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.